Method and apparatus for collecting energy consumption information of new session in wireless communication system
Patent Information
- Application Number
- PCT/KR2026/095290
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-03-27
- Filing Date
- 2026-03-27
- Publication Date
- 2026-10-01
Smart Images
Figure KR2026095290_01102026_PF_FP_ABST
Abstract
Description
Method and apparatus for collecting energy consumption information of a new session in a wireless communication system
[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method for collecting energy consumption information of a new session in a wireless communication system and an apparatus capable of performing the same.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.
[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.
[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.
[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.
[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.
[0008] As one aspect of the present disclosure, a method is provided to be performed by an Energy Information Function (EIF) in a wireless communication system, the method comprising: receiving a subscription message requesting Energy Consumption Information (ECI) for a terminal from a network entity; obtaining information of an Access and Mobility Management Function (AMF) responsible for the terminal from a Unified Data Management (UDM) based on the subscription message; transmitting a first response message to the network entity based on the information obtained from the UDM; transmitting a subscription request message to the AMF to obtain information of a new Session Management Function (SMF) for the terminal; receiving a first notification message from the AMF based on the establishment of a new Protocol Data Unit (PDU) session for the terminal and the addition of a new SMF for the terminal; transmitting a second subscription request message to the SMF for calculating the ECI based on the notification message; and calculating the energy consumption of the terminal based on the second notification message received from the SMF.
[0009] As one aspect of the present disclosure, an Energy Information Function (EIF) in a wireless communication system is provided, wherein the EIF comprises: at least one transceiver; and at least one processor connected to communicate with the transceiver. The device includes at least one memory connected to communicate with at least one processor and storing instructions that can be executed by said at least one processor individually or in any combination thereof, and said EIF receives a subscription message requesting Energy Consumption Information (ECI) for a terminal from a network entity, and based on the subscription message, obtains information of an Access and Mobility Management Function (AMF) responsible for the terminal from a Unified Data Management (UDM), and based on the information obtained from the UDM, transmits a first response message to the network entity, transmits a first subscription request message to the AMF to obtain information of a new Session Management Function (SMF) for the terminal, receives a first notification message from the AMF based on the establishment of a new Protocol Data Unit (PDU) session for the terminal and the addition of a new SMF for the terminal, transmits a second subscription request message to the SMF for calculating ECI based on the notification message, and calculates the energy consumption of the terminal based on the second notification message received from the SMF.
[0010] FIG. 1 illustrates a 5G system architecture according to one embodiment of the present disclosure.
[0011] FIG. 2 is a diagram illustrating a method for obtaining SMF information for a novel AMF-based PDU session according to one embodiment of the present disclosure.
[0012] FIG. 3 is a diagram illustrating a method for collecting ECI for a new session based on UDM / UDR according to one embodiment of the present disclosure.
[0013] FIG. 4 is a diagram illustrating a method for collecting ECI information for a new PCF-based session according to one embodiment of the present disclosure.
[0014] FIG. 5 is a block diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.
[0015] FIG. 6 is a block diagram illustrating the structure of a network entity according to one embodiment of the present disclosure.
[0016] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0017] While various details have been described for the purpose of facilitating understanding in describing the embodiments, it will be understood that some aspects of the present disclosure may be practiced without including all such details. Furthermore, various modifications and alternatives are possible regarding the details presented herein, and all of these should be considered to be included within the scope of the present disclosure. Meanwhile, descriptions of technical content that are widely known in the art and may unnecessarily obscure the understanding of the present disclosure may be appropriately omitted, and such omitted descriptions should also be understood to be included within the scope of the present disclosure.
[0018] 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 or different reference numbers.
[0019] The advantages and features of the present disclosure, and the methods for achieving them, will become clear through the embodiments described below in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments presented below and may be implemented in various forms. Other features, aspects, and advantages disclosed in the present disclosure will become more clear through the following description of the present disclosure. The following embodiments are merely illustrative to aid in understanding the present disclosure and should not be interpreted in any way as limiting the scope or spirit of the present disclosure. Rather, the present disclosure includes all modifications, changes, and alternatives made within the spirit and scope of the present disclosure as defined by the appended claims and their equivalents. Identical or similar components throughout the disclosure are assigned identical or similar reference numerals. Furthermore, terms described below are defined with consideration of their function in the present disclosure and may be used differently depending on the user, operator, or convention. Accordingly, the definitions of terms should be interpreted based on the content of the entire present disclosure.
[0020] In the present disclosure, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams may be performed based on computer program instructions. Since these computer program instructions may be optionally loaded into at least one processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions performed through any one or any combination of at least one processor of the computer or other programmable data processing equipment create means for performing the functions described in the flow diagram block(s). Since these computer program instructions may 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 functions in a specific manner, the instructions stored in computer-available or computer-readable memory may also produce a manufactured item containing means of instruction for performing the functions 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).
[0021] 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 example, two blocks (or functions) described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to the corresponding function.
[0022] As used in the embodiments of the present disclosure, the term “part / module” refers to a software or hardware component such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the “part / module” performs certain roles. However, the term including “part / module” is not limited to software or hardware. The “part / module” may be configured to reside in an addressable storage medium or may be configured to run one or more processors. Accordingly, by example, the “part / module” 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 / modules' may be combined into a smaller number of components and 'parts / modules' or further separated into additional components and 'parts / modules'. In addition, the components and 'parts / modules' may be implemented to utilize one or more CPUs (central processing units) within the device or secure multimedia card. Furthermore, in the embodiments, the 'parts / modules' may include one or more processors.
[0023] The entirety of one or more computer programs may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored across multiple memory devices.
[0024] Additionally, any / any function or operation described in this disclosure may be processed by a single processor or a combination of processors. The single processor or combination of processors may be a circuitry that performs processing, and may include an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural network processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor, a microcontroller, a digital signal processor, an FPGA, an ASIC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, or similar circuitry. The single processor or combination of processors described above can control the overall operation of an electronic device by executing instructions, such as an operating system, that can be stored in memory. Additionally, the processor or combination of processors can execute other processes or programs residing in memory (e.g., processes related to the present disclosure).
[0025] Additionally, it should be noted that various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0026] Such software may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium stores one or more computer programs (software modules), said one or more computer programs include computer-executable instructions that operate an electronic device to perform a method according to the present disclosure when executed individually or collectively by one or more processors of an electronic device. Alternatively, said software may be a computer program (or product) that includes instructions that operate an electronic device to perform a method according to the present disclosure when executed individually or collectively by one or more processors of an electronic device.
[0027] The software may be stored in a transient or non-transient storage device, for example, in the form of read-only memory (ROM) (whether or not it is erasable or rewritable), or random access memory (RAM), memory chips, devices, or integrated circuits (ICs). Additionally, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital multifunction disc (DVD), a magnetic disc, or a magnetic tape. It should be understood that the storage device and the storage medium are examples of non-transient machine-readable storage media suitable for storing programs for implementing various embodiments of the present disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing an apparatus or method according to any one of the claims of the present disclosure, and a non-transient machine-readable storage medium storing such program.
[0028] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.
[0029] Hereinafter, 'A or B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.
[0030] Additionally, 'at least one of A, B, and C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.
[0031] Additionally, 'at least one of A, B, or C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.
[0032] Additionally, 'A / B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.
[0033] Additionally, 'A, B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.
[0034] Additionally, 'A and B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.
[0035] Furthermore, the phrase "when conditions A and B are satisfied" as described in the present disclosure is not necessarily limited to cases where both conditions A and B are satisfied, but may be understood to include cases where either condition A or condition B is satisfied individually, cases where both conditions A and B are satisfied, or cases where one or more additional conditions are satisfied together.
[0036] Furthermore, throughout this disclosure, ordinal terms (and similar modifiers) such as 'first', 'second', 'third', etc. are used solely for the purpose of distinguishing various instances, occurrences, configurations, messages, stages, elements, or aspects of elements, operations, or information, as described below. Unless clearly required otherwise by the context, the use of such ordinal terms does not require that the elements, operations, or information distinguished by such terms be structurally different, numerically distinct, or substantially different. For example, 'first signal' and 'second signal' may represent instances of the same signal transmitted at different times, signals containing the same core information even with some variations, or signals having different content or characteristics depending on the specific context. Similarly, 'first value' and 'second value' may represent the same size measured or applied in different situations, or they may represent different sizes. Such interpretation must be determined based on the specific technical context, function, and relationship described in the relevant parts of the disclosure and claims.
[0037] Furthermore, although terms such as "first," "second," etc., as used in this disclosure are used for various elements such as information, objects, actions, and sequences, they are not intended to limit such elements to a specific order. These terms may be understood merely as distinguishing one element from another. For example, a first element may be referred to as a second element, and likewise, a second element may be referred to as a first element.
[0038] Additionally, the terms 'first' and 'second' described in this disclosure may be understood to refer to identical or different elements. For example, if an element is information, the first information and the second information may both be information, and depending on the case, they may be the same information or different information.
[0039] Furthermore, expressions such as "if" and "in case that" as described in the present disclosure or claims may be interpreted, depending on the context, as meaning "when or upon," "in response to," "based on," or "according to," and these expressions may be used interchangeably. In addition, other expressions having substantially the same meaning may be used as substitutes for these expressions, provided that they do not impair the technical features of the present disclosure. Furthermore, if a method step (e.g., a step of transmitting a signal) is performed in relation to such terms (e.g., "in case that" or similar expressions) in accordance with the disclosure of the present specification, this may be interpreted as the method step being performed in response to a prior determination that a specific element has a specific state (e.g., bit length exceeding X).
[0040] For example, physical layer signaling may be referred to as L1 (Layer 1) signaling and may include downlink control information (DCI). Additionally, upper layer signaling may include at least one of a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (Layer 3) signaling. However, upper layer signaling is not limited to the above examples.
[0041] Additionally, the term "not perform" as used in this disclosure or claims may be understood, depending on the context, to mean to omit or skip the corresponding step. Such a term may be replaced with other terms having the same or substantially similar meaning.
[0042] Additionally, the phrase “transmitting a message containing A and B” as described in the present disclosure may be interpreted to include not only (i) cases where A and B are transmitted as a single message, but also (ii) cases where A and B are transmitted individually through multiple messages (e.g., transmitting a first message containing A and a second message containing B). This interpretation may also apply to cases where messages containing two or more items, such as A, B, and C, are transmitted together or individually.
[0043] In addition, 'transmitting a message containing A and transmitting a message containing B' can also be interpreted as transmitting a single message containing A and B.
[0044] In the embodiments described in this disclosure, terms or components included in the disclosure may be expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the context presented for convenience of explanation, and the disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, and even if a component is expressed in the singular form, it may be composed in the plural form.
[0045] The drawings or flowcharts described in this disclosure illustrate exemplary methods that may be implemented according to the principles of this disclosure, and various modifications may be made to the methods illustrated in the flowcharts of this disclosure. For example, although illustrated as a series of steps, the various steps of each drawing or flowchart may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, any step may be omitted or replaced with another step.
[0046] Additionally, the process of the flowchart can be performed by an electronic device, and one or more steps of the flowchart can be implemented by one or more processors that execute instructions to perform specific functions.
[0047] The methods and apparatus proposed in the embodiments of the present disclosure may be disclosed together with drawings including flowcharts to illustrate exemplary methods that may be implemented according to the principles of the present disclosure. Such flowcharts may include different branches and / or sub-branches. It should be understood that the principles of the present disclosure are not limited to combinations of all branches and sub-branches disclosed in the embodiments, and may consist of at least one individual branch or individual sub-branch, in particular only a single branch or a single sub-branch.
[0048] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each embodiment and may be utilized as a combination of all or part of the embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope that does not deviate significantly from the scope of the present disclosure, at the judgment of a person skilled in the art.
[0049] In this case, any wording mentioned in different embodiments may be used interchangeably, combined, or substituted if the concepts correspond. For example, regarding the same or corresponding concepts, even if the expression 'A' is used in one embodiment and the expression 'B' is used in another embodiment, they may be understood by interchangeably, substituted, or combined.
[0050] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. Furthermore, where appropriate, such terms may be replaced with terms defined in similar technical specifications of standardization organizations such as 3GPP (3rd generation partnership project) Technical Specifications (TS) or ETSI (European Telecommunications Standards Institute).
[0051] Hereinafter, the base station is an entity that performs resource allocation of the terminal and may be at least one of gNode B, eNode B, Node B, BS (base station), wireless access unit, base station controller, or a node on the network.
[0052] In addition, the base station of the present disclosure may include a structure split into a central unit (CU) and a distributed unit (DU). In such a structure, the CU is responsible for the upper layer of the control and user plane, and the DU is responsible for the processing of wireless resources in the lower layer. The embodiments of the present disclosure can be equally applied to a 5G base station structure in which functions are split into the CU and DU as described above.
[0053] The terminal may include at least one of user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, tablet, wearable device, Internet of Things (IoT) device, or other device / system capable of performing communication functions.
[0054] In the present 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.
[0055] In addition, while a 5th generation mobile communication system (5G, new radio, NR) and a 6th generation mobile communication system (6G) may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, new advanced mobile communication systems developed after 5G and 6G may be included therein. Furthermore, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications made in the judgment of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.
[0056] In the following description, the terms "physical channel" and "signal" may be used interchangeably with "data" or "control signal." For example, PDSCH (physical downlink shared channel) is a term referring to a physical channel through which data is transmitted, but PDSCH may also be used to refer to data. That is, in this disclosure, the expression "transmits a physical channel" may be interpreted as equivalent to the expression "transmits data or a signal through a physical channel."
[0057] In describing the present disclosure below, the term "upper layer signaling" may be a signaling corresponding to at least one or a combination of at least one of MIB (master information block), SIB (system information block), SIB M (M=1, 2, ...), RRC, MAC CE, NAS (non-access stratum) signaling, or application layer messages. The RRC signaling may also be referred to as L3 signaling (layer 3 signaling).
[0058] Additionally, L1 signaling may be a signaling method corresponding to at least one or a combination of at least one of the following: a physical layer channel or signaling of a PDCCH (physical downlink control channel), a DCI, a UE-specific DCI, a group common DCI, a common DCI, a scheduling DCI (e.g., a DCI used for the purpose of scheduling downlink or uplink data), a non-scheduling DCI (e.g., a DCI not used for the purpose of scheduling downlink or uplink data), a PUCCH (physical uplink control channel), or an UCI (uplink control information). The above L1 signaling may also be referred to as physical layer signaling.
[0059] Hereinafter, the expression in the present disclosure or claims that information can be configured from a base station may mean that, depending on the context, a terminal receives said information from a base station through physical layer signaling or upper layer signaling, and such expression may be replaced with other terms having the same or substantially similar meaning.
[0060] The operating principle of the present disclosure will be explained in detail below with reference to the attached drawings.
[0061] FIG. 1 illustrates a 5G system architecture according to one embodiment of the present disclosure.
[0062] A 5G mobile communication network consists of a 5G UE (user equipment, terminal) (100), a 5G RAN (radio access network, base station, gNB (5G nodeB), eNB (evolved nodeB, etc.)) (110), 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, 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 (145). However, it is not limited to these and may include more or fewer configurations.
[0063] 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.
[0064] - N1: Reference point between UE (100) and AMF (120)
[0065] - N2: Reference point between (R)AN(110) and AMF(120)
[0066] - N3: Reference point between (R)AN(110) and UPF(130)
[0067] - N4: Reference point between SMF (135) and UPF (130)
[0068] - N5: Reference point between PCF (140) and AF (application function) (170)
[0069] - N6: Reference point between UPF (130) and DN (data network) (175)
[0070] - N7: Reference point between SMF (135) and PCF (140)
[0071] - N8: Reference point between UDM (145) and AMF (120)
[0072] - N9: Reference point between 2 core UPFs (130)
[0073] - N10: Reference point between UDM (145) and SMF (135)
[0074] - N11: Reference point between AMF (120) and SMF (135)
[0075] - N12: Reference point between AMF(120) and AUSF
[0076] - N13: Reference point between UDM (145) and authentication server function (AUSF)
[0077] - N14: Reference point between 2 AMFs (120)
[0078] - N15: Reference point between PCF (140) and AMF (120) in the case of a non-roaming scenario, reference point between PCF (140) and AMF (120) within the visited network in the case of a roaming scenario
[0079] In a 5G system, network slicing technology refers to a technology and structure that enables multiple virtualized, independent logical networks within a single physical network. To satisfy the specialized requirements of a service / application, a network operator provides services by configuring a virtual end-to-end network called a network slice. At this time, the network slice is distinguished by an identifier called S-NSSAI (single-network slice selection assistance information). The network transmits a set of allowed slices (e.g., allowed NSSAI(s)) to a terminal (100) during a terminal registration procedure (e.g., UE registration procedure), and the terminal (100) transmits and receives application data through a PDU (protocol data unit) session created through one of these S-NSSAIs (i.e., network slice).
[0080] The present disclosure proposes a discovery method for an energy information function in a 5G system. An energy information function (EIF) (or energy monitoring function (EMF)) is defined to collect energy consumption information (ECI) related to a UE, calculate energy consumption information at a UE (100), PDU session and / or Service Data Flow (or QoS Flow), NF node, base station node, etc., and expose the energy consumption information to authorized consumer NF(s) (AF (170) / NEF (network exposure function) or 5GC NF) according to the operator's policy.
[0081] Energy consumption information can be used by the consumer NF to control the energy consumption of the UE (100). The function for controlling energy consumption may be installed in the EIF or located in another NF. If the function for controlling energy consumption is installed in the EIF, the EIF may perform energy control for the UE (100) based on the energy collection information for the UE (100).
[0082] FIG. 2 is a diagram illustrating a method for obtaining SMF (135) information for a new PDU session based on AMF (120) according to one embodiment of the present disclosure.
[0083] Step 1. A Consumer NF (e.g., NEF, AF (170), PCF (140), AMF (120), NWDAF (network data analytics function) (165), etc.) may send a subscription message to the EIF requesting energy consumption information for the UE (100). The message may include the following information.
[0084] - Event ID: Event ID representing energy consumption
[0085] - UE ID: May include terminal identifier information.
[0086] - S-NSSAI(s): When requesting energy consumption information for specific S-NSSAI(s) used by the terminal (100), the S-NSSAI may be included.
[0087] - S-NSSAI / DNN(data network name): When requesting energy consumption information for a specific S-NSSAI and DNN used by the terminal (100), the S-NSSAI and DNN may be included.
[0088] - IP Filter: When requesting information on energy consumption for a specific traffic flow used by the terminal (100), a corresponding IP filter (e.g., source IP address / port, destination IP / port, protocol type, etc.) may be included. One or more IP Filter information may be included.
[0089] - access type: If you intend to collect ECI for a specific access type, you may include the access type. It may include 3GPP access, non-3GPP access, or both.
[0090] - Reporting frequency: May include the frequency for receiving energy consumption information notifications.
[0091] - Area information: When requesting energy consumption information for a specific area, the relevant area information may be included. TAI(s) or geographical information may be included.
[0092] - New PDU session indication: If you wish to collect energy consumption information for a new PDU session, the relevant indicator may be included.
[0093] Step 2. When the EIF receives the message of Step 1 (e.g., if the message of Step 1 contains a New PDU session indication), it may send a request message to the UDM (145) to receive information about the AMF (120) responsible for the UE (100). 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 contains an access type, the corresponding access type may be included.
[0094] Step 3. If the UDM (145) has received a message from the EIF containing UE ID, S-NSSAI, DNN, (additionally access type), and if the corresponding AMF ID / address(s) is stored, the UDM may include AMF ID / address(es) (additionally access type) in a response message sent to the EIF.
[0095] Step 4. The EIF may send a response message to the Consumer NF (e.g., NEF). The message may include the following information. If it fails, the remaining steps are not performed.
[0096] - (If successful) result=success, subscription correlation ID, expiry time, first corresponding energy related information report (eg, UE location information (TAI and cell ID), gNB ID, UPF ID, SMF ID)
[0097] - (If it fails, according to the response message received from the UDM (145) in step 3) result=failed, cause = UE is not registered (or serving AMF for UE is not found)
[0098] - (If it fails, according to the response message received from the UDM (145) in step 3) result=failed, no PDU session established for the UE
[0099] Step 5. The EIF may send a subscription request message to the AMF (120) to obtain a new serving SMF ID / address for the UE ID. The message may include the UE ID, S-NSSAI, DNN, and event ID (an event ID representing information about the UE session or SMF information).
[0100] Step 6. A new PDU session can be established for UE (100).
[0101] Step 7. When a new PDU session is established for UE (100) (or S-NSSAI, DNN) and a new serving SMF is added for UE (100) (e.g., when a new SMF ID / address is added within the UE context), and when there is a subscription for information about the UE session or SMF information event for the corresponding UE (100) (or for UE (100) and S-NSSAI, DNN) (i.e., when a subscription request message containing the corresponding UE ID, S-NSSAI, DNN is received in Step 5), the AMF (120) may send a notification message to the EIF containing one or more of the subscription notification ID, SMF ID / address, an indicator indicating that a new serving SMF has been added for UE (100), S-NSSAI, DNN, and PDU Session ID.
[0102] Step 8. If the notification message received in Step 7 contains an indicator indicating that a new serving SMF has been added for the UE (100) or an indicator indicating that a new PDU Session has been established, the EIF may send a subscription request message for ECI calculation containing the UE ID to the SMF (135) to the SMF ID / address included in the message.
[0103] If the EIF receives a subscription request message for energy consumption information in step 1, it may include an event ID in the message sent to the SMF (135). For example, it may include an event ID indicating data usage or an event ID indicating information for ECI calculation.
[0104] If the message received by the EIF in step 1 contains one or more of the UE ID, S-NSSAI, DNN, and IP Filter, the EIF may include the corresponding parameters in the message sent to the SMF (135).
[0105] If the EIF receives a message in step 1 that contains an access type, the EIF may include the corresponding access type in a message sent to the SMF (135).
[0106] The EIF may include a reporting period and notification information in a message sent to the SMF (135). If the EIF wants to directly receive information for energy consumption calculation from the UPF (130) (e.g., user data usage information, such as UL / DL data volume information for a certain period of time), it may include address information (e.g., FQDN or IP Address) to receive the notification in the notification information along with a direct notification indicator in the message sent to the SMF (135).
[0107] Step 9. When the SMF (135) receives a subscription request message from the EIF, it may send a subscription request message to the corresponding UPF(s) (130) to collect data volume (or information needed to calculate ECI) for the target included in the message (e.g., UE ID, S-NSSAI, DNN, IP Filter, App ID included in the message). The message may include a time period. Based on the target information received from the SMF (135), the UPF (130) may collect data volume usage (or information needed to calculate ECI) according to the time period and send an event notification message to the SMF (135).
[0108] SMF (135) sends a notification message to EIF based on the notification message received from UPF (130), including UE ID, S-NSSAI, DNN, IP Filter, App ID, and list of data volume entry<UL / DL data volume, UPF ID(s), gNB ID(s), reference time internval> It can include.
[0109] A reference time interval represents information indicating the time at which a measurement was taken for a measurement performed during the time interval. For example, it may include timestamp information (e.g., if the measurement during the time interval represents the Nth measurement, it represents the Nth measurement).
[0110] The SMF (135) can determine the gNB ID for the UE (100) based on UE location information (ULI) (e.g., tracking area identifier (TAI) and cell ID) received from the AMF (120) or information received from the UPF (130) (e.g., ULI or gNB ID(s)). If the gNB ID has changed, the SMF (135) can add a new data volume entry containing the previous gNB ID and the new gNB ID to the notification message. Additionally, the SMF (135) can include an indicator indicating that the gNB ID has changed (e.g., an indicator indicating a handover) and / or information about the time the handover occurred (e.g., within a time interval) in the notification message sent to the EIF. If the message received by the EIF from the SMF (135) contains gNB ID and / or UPF ID(s) and there is no associated node-level energy consumption information and node-level data volume, the EIF may send a message to the OAM (operation, administration, and 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 (135) in the request message sent to the OAM. When the OAM receives a request message containing gNB ID from the EIF, it may include the Data Volume and energy consumption measured at specific intervals for the gNB ID in a message sent to the EIF to be transmitted.
[0111] When the OAM receives a request message containing a UPF ID from the EIF, it can include the Data Volume and energy consumption measured at a specific period for the UPF ID in the message sent to the EIF to be transmitted.
[0112] The EIF can obtain the data volume consumed by the gNB (110), N3IWF (non-3GPP interworking function), and UPF (130) of the UE (100) during a specific time period based on the notification message received from each SMF (135). Additionally, it can obtain the node-level data volume and node-level energy consumption consumed by the gNB (110), N3IWF, and UPF (130) from the OAM. For granularity G (e.g., one of UE (100), UE (100), and S-NSSAI, PDU Session, Traffic Flow), the EIF can calculate the energy consumption (i.e., E_G,N) at each node N (e.g., N can be one of gNB (110), N3IWF, or UPF (130)) as follows.
[0113] - E_G,N = (Energy consumption of G) * (Data volume transmitted by N to G) / (Data volume transmitted by N)
[0114] When EIF calculates the energy consumption for granularity G (e.g., UE (100), UE (100) and one of 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 (130), N3IWF, gNB (110)) that handle the traffic of UE (100).
[0115] If the message received from the SMF (135) contains a handover indicator and / or contains two or more gNB IDs, the EIF may send a message to the OAM to request energy consumption information and data volume information at the time of handover for the new gNB ID. The message may include one or more indicators requesting the new gNB ID, the measurement time (e.g., information indicating the time from when the handover occurred during the time interval to when the time interval ended), energy consumption, and data volume information.
[0116] Based on the information received from the OAM, the EIF can calculate energy consumption information for granularity G for the reference time interval during which the handover occurred. The EIF can include the energy consumption for granularity G (e.g., UE (100), UE (100) and one of S-NSSAI, PDU Session, Traffic Flow) subscribed to by the Consumer NF in a notification message sent to the Consumer NF.
[0117] Step 10. The PDU session is released for UE (100).
[0118] Step 11a. If the PDU session for UE (100) (or S-NSSAI, DNN) is released and / or existing serving SMF information for UE (100) is deleted, and if there is a subscription for information about the UE session or SMF information event for the corresponding UE (or S-NSSAI, DNN) (i.e., received a subscription request message containing the corresponding UE ID in Step 5), the AMF (120) may send a notification message to the EIF subscribed to for the corresponding UE ID (and S-NSSAI and / or DNN) including a subscription notification ID, deleted SMF ID(s), an indicator indicating that the SMF information responsible for UE (100) has been deleted (or an indicator indicating that the PDU Session has been released), and one or more of S-NSSAI, DNN, and PDU Session IDs.
[0119] 11b. If the information contained in the message of step 11a includes an indicator that the responsible SMF information has been deleted (or an indicator that the PDU Session has been released), the EIF may send a subscription unsubscribe request message containing a subscription correlation ID to the corresponding SMF (135).
[0120] Step 11c. If the PDU session for the UE ID (or S-NSSAI, DNN) that the EIF is subscribed to in Step 9 is released, the SMF (135) may send a message to the EIF to cancel the subscription of information for ECI calculation. The message may include a subscription correlation ID, a subscription termination indication, and a cause (e.g., all corresponding PDU session(s) have been released). If the message received from the SMF (135) includes a subscription termination indication, the EIF may delete the subscription information for the subscription correlation ID included in the message.
[0121] Additionally, SMF (135) can send a message to UPF (130) to cancel the information subscription (or data volume / usage subscription) for ECI calculation.
[0122] FIG. 3 is a diagram illustrating a method for collecting ECI for a new session based on UDM (145) / UDR according to one embodiment of the present disclosure.
[0123] Step 1. A Consumer NF (e.g., NEF, AF (170), PCF (140), AMF (120), NWDAF (165), etc.) may send a subscription message to the EIF requesting information on energy consumption for the UE (100). The message may include the following information.
[0124] - Event ID: Event ID representing energy consumption
[0125] - UE ID: May include terminal identifier information.
[0126] - S-NSSAI(s): When requesting energy consumption information for specific S-NSSAI(s) used by the terminal (100), the S-NSSAI may be included.
[0127] - S-NSSAI / DNN: When requesting energy consumption information for a specific S-NSSAI and DNN used by the terminal (100), the S-NSSAI and DNN may be included.
[0128] - IP Filter: When requesting information on energy consumption for a specific traffic flow used by the terminal (100), a corresponding IP filter (e.g., source IP address / port, destination IP / port, protocol type, etc.) may be included. One or more IP Filter information may be included.
[0129] - access type: If you intend to collect ECI for a specific access type, you may include the access type. It may include 3GPP access, non-3GPP access, or both.
[0130] - Reporting frequency: May include the frequency for receiving energy consumption information notifications.
[0131] - Area information: When requesting energy consumption information for a specific area, the relevant area information may be included. TAI(s) or geographical information may be included.
[0132] - New PDU session indication: If you wish to collect energy consumption information for a new PDU session, the relevant indicator may be included.
[0133] Step 2. When the EIF receives the message of Step 1 (for example, if the message of Step 1 contains a New PDU session indication), the EIF may send a request message to the UDM (145) or UDR to subscribe to information about the SMF (135) responsible for the UE (100).
[0134] The request message may be a Nudm_EventExposure_Subscribe or Nudm_UECM_Get message.
[0135] The message may include the UE ID (or S-NSSAI, DNN) included in the message received in step 1. Additionally, the message may include notification information (e.g., EIF address).
[0136] If the message received in Step 1 includes an access type, the corresponding access type may be included.
[0137] When the UDM (145) receives the message of step 2, it may include a Data type identifier (e.g., PDU Session status, SMF information) in the message sent to the UDR to request a subscription. It may also include a UE ID, S-NSSAI, DNN, and notification information in the message. The message may be Nudr_DM_Subscribe.
[0138] When EIF sends a subscription request message to UDR, it may also send a subscription message to UDR via PCF (140).
[0139] Step 3. UDM (145) can send a response message to the EIF for the subscription request message received from the EIF.
[0140] Step 4. The EIF may send a response message to the Consumer NF (e.g., NEF). The message may include the following information. If it fails, the remaining steps are not performed.
[0141] - (If successful) result=success, subscription correlation ID, expiry time, first corresponding energy related information report (eg, UE location information (TAI and cell ID), gNB ID, UPF ID, SMF ID)
[0142] - (If it fails, according to the response message received from the UDM (145) in step 3) result=failed, cause = UE is not registered (or serving AMF for UE is not found)
[0143] - (If it fails, according to the response message received from the UDM (145) in step 3) result=failed, no PDU session established for the UE
[0144] Step 6. A new PDU session can be established for UE (100).
[0145] Step 7. When a new serving SMF is added for UE (100) (or S-NSSAI, DNN) (e.g., when a new SMF ID / address is added to the UE context), and when there is a subscription for information or SMF information events for the UE session for the corresponding UE (100) (or for UE (100) and S-NSSAI, DNN) (i.e., when a subscription request message containing the corresponding UE ID, S-NSSAI, DNN is received in Step 2), the UDM (145) may send a notification message to the EIF containing one or more of the subscription notification ID, SMF ID / address, an indicator indicating that a new serving SMF has been added for UE (100), S-NSSAI, DNN, and PDU Session ID.
[0146] In another embodiment, if in step 2 the EIF requests a subscription from the UDR through the UDM (145) (i.e., the UDM (145) sends a subscription request message containing notification information to the UDR), the UDR may send a notification message to the information (e.g., EIF address) included in the notification information received in step 2 when a new serving SMF is added for the UE (100) (or S-NSSAI, DNN) (e.g., when a new SMF ID / address is added to the UE context), and when there is a subscription for information about the UE session or SMF information event for the corresponding UE (100) (or for the UE and S-NSSAI, DNN) (i.e., when a subscription request message including the corresponding UE ID, S-NSSAI, DNN is received in step 2). UDR can send a notification message to EIF containing one or more of a subscription notification ID, an SMF ID / address, an indicator that a new serving SMF has been added for UE (100), an S-NSSAI, a DNN, and a PDU Session ID.
[0147] Step 8. If the notification message received in Step 7 contains an indicator that a new serving SMF has been added for the UE (100), the EIF may send a subscription request message for ECI calculation containing the UE ID to the SMF (135) to the SMF ID / address included in the message.
[0148] If the EIF receives a subscription request message for energy consumption information in step 1, it may include an event ID in the message sent to the SMF (135). For example, it may include an event ID indicating data usage or an event ID indicating information for ECI calculation.
[0149] If the message received by the EIF in step 1 contains one or more of the UE ID, S-NSSAI, DNN, and IP Filter, the EIF may include the corresponding parameters in the message sent to the SMF (135).
[0150] If the EIF receives a message in step 1 that contains an access type, the EIF may include the corresponding access type in a message sent to the SMF (135).
[0151] The EIF may include a reporting period and notification information in a message sent to the SMF (135). If the EIF wants to directly receive information for energy consumption calculation from the UPF (130) (e.g., user data usage information, such as UL / DL data volume information for a certain period of time), it may include address information (e.g., FQDN or IP Address) to receive the notification in the notification information along with a direct notification indicator in the message sent to the SMF (135).
[0152] Step 9. When the SMF (135) receives a subscription request message from the EIF, it may send a subscription request message to the corresponding UPF(s) (130) to collect data volume (or information needed to calculate ECI) for the target included in the message (e.g., UE ID, S-NSSAI, DNN, IP Filter, App ID included in the message). The message may include a time period. Based on the target information received from the SMF (135), the UPF (130) may collect data volume usage (or information needed to calculate ECI) according to the time period and send an event notification message to the SMF (135).
[0153] SMF (135) sends a notification message to EIF based on the notification message received from UPF (130), including UE ID, S-NSSAI, DNN, IP Filter, App ID, and list of data volume entry<UL / DL data volume, UPF ID(s), gNB ID(s), reference time internval> It can include.
[0154] A reference time interval represents information indicating the time at which a measurement was taken for a measurement performed during the time interval. For example, it may include timestamp information (e.g., if the measurement during the time interval represents the Nth measurement, it represents the Nth measurement).
[0155] The SMF (135) can determine the gNB ID for the UE (100) based on UE location information (ULI) (e.g., tracking area identifier (TAI) and cell ID) received from the AMF (120) or information received from the UPF (130) (e.g., ULI or gNB ID(s)). If the gNB ID has changed, the SMF (135) can add a new data volume entry containing the previous gNB ID and the new gNB ID to the notification message. Additionally, the SMF (135) can include an indicator indicating that the gNB ID has changed (e.g., an indicator indicating a handover) and / or information about the time the handover occurred (e.g., within a time interval) in the notification message sent to the EIF.
[0156] If the message received by the EIF from the SMF (135) contains gNB ID and / or UPF ID(s) and there is no associated node-level energy consumption information and node-level data volume, the EIF may send a message to the OAM to request such information. The EIF may include the gNB ID(s) and / or UPF ID(s) contained in the message received from the SMF (135) in the request message sent to the OAM. When the OAM receives a request message from the EIF containing gNB ID, it may include the Data Volume and energy consumption measured at specific intervals for the gNB ID in the message sent to the EIF.
[0157] When the OAM receives a request message containing a UPF ID from the EIF, it can include the Data Volume and energy consumption measured at a specific period for the UPF ID in the message sent to the EIF to be transmitted.
[0158] The EIF can obtain the data volume consumed by the gNB (110), N3IWF, and UPF (130) of the UE (100) during a specific time period based on the notification message received from each SMF (135). Additionally, it can obtain the node-level data volume and node-level energy consumption consumed by the gNB (110), N3IWF, and UPF (130) from the OAM. For granularity G (e.g., one of UE (100), UE (100), and S-NSSAI, PDU Session, Traffic Flow), the EIF can calculate the energy consumption (i.e., E_G,N) at each node N (e.g., N can be one of gNB (110), N3IWF, and UPF (130)) as follows.
[0159] - E_G,N = (Energy consumption of G) * (Data volume transmitted by N to G) / (Data volume transmitted by N)
[0160] When EIF calculates the energy consumption for granularity G (e.g., UE (100), UE (100) and one of 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 (130), N3IWF, gNB (110)) that handle the traffic of UE (100).
[0161] If the message received from the SMF (135) contains a handover indicator and / or contains two or more gNB IDs, the EIF may send a message to the OAM to request energy consumption information and data volume information at the time of handover for the new gNB ID. The message may include one or more indicators requesting the new gNB ID, the measurement time (e.g., information indicating the time from when the handover occurred during the time interval to when the time interval ended), energy consumption, and data volume information.
[0162] Based on information received from the OAM, the EIF can calculate energy consumption information regarding granularity G for the reference time interval during which the handover occurred.
[0163] The EIF can include the energy consumption of granularity G (e.g., UE (100), UE (100) and one of S-NSSAI, PDU Session, Traffic Flow) that the Consumer NF subscribes to in a notification message sent to the Consumer NF.
[0164] Step 10. The PDU session is released for UE (100).
[0165] Step 11a. If a PDU session for UE (100) (or S-NSSAI, DNN) is released and / or existing serving SMF information for UE (100) is deleted, and if there is a subscription for information about the UE session or SMF information event for the corresponding UE (100) (or S-NSSAI, DNN) (i.e., received a subscription request message containing the corresponding UE ID in Step 1), the UDM (145) / UDR may send a notification message to the EIF subscribed to the corresponding UE ID (and S-NSSAI and / or DNN) containing a subscription notification ID, deleted SMF ID(s), an indicator indicating that the SMF information responsible for UE (100) has been deleted (or an indicator indicating that the PDU Session has been released), and one or more of S-NSSAI, DNN, and PDU Session IDs.
[0166] 11b. If the information contained in the message of step 11a includes an indicator that the responsible SMF information has been deleted (or an indicator that the PDU Session has been released), the EIF may send a subscription unsubscribe request message containing a subscription correlation ID to the corresponding SMF (135).
[0167] Step 11c. If the PDU session for the UE ID (or S-NSSAI, DNN) that the EIF is subscribed to in Step 9 is released, the SMF (135) may send a message to the EIF to cancel the subscription to information for ECI calculation. The message may include a subscription correlation ID, a subscription termination indication, and a cause (e.g., all corresponding PDU session(s) have been released). If the message received from the SMF (135) includes a subscription termination indication, the EIF may delete the subscription information for the subscription correlation ID included in the message.
[0168] Additionally, SMF (135) can send a message to UPF (130) to cancel the information subscription (or data volume / usage subscription) for ECI calculation.
[0169] FIG. 4 is a diagram illustrating a method for collecting ECI information for a new session based on PCF (140) according to one embodiment of the present disclosure.
[0170] Step 1. A Consumer NF (e.g., NEF, AF (170), PCF (140), AMF (120), NWDAF (165), etc.) may send a subscription message to the EIF requesting information on energy consumption for the UE (100). The message may include the following information.
[0171] - Event ID: Event ID representing energy consumption
[0172] - UE ID: May include terminal identifier information.
[0173] - S-NSSAI(s): When requesting energy consumption information for specific S-NSSAI(s) used by the terminal (100), the S-NSSAI may be included.
[0174] - S-NSSAI / DNN: When requesting energy consumption information for a specific S-NSSAI and DNN used by the terminal (100), the S-NSSAI and DNN may be included.
[0175] - IP Filter: When requesting information on energy consumption for a specific traffic flow used by the terminal (100), a corresponding IP filter (e.g., source IP address / port, destination IP / port, protocol type, etc.) may be included. One or more IP Filter information may be included.
[0176] - access type: If you intend to collect ECI for a specific access type, you may include the access type. It may include 3GPP access, non-3GPP access, or both.
[0177] - Reporting frequency: May include the frequency for receiving energy consumption information notifications.
[0178] - Area information: When requesting energy consumption information for a specific area, the relevant area information may be included. TAI(s) or geographical information may be included.
[0179] - New PDU session indication: If you wish to collect energy consumption information for a new PDU session, the relevant indicator may be included.
[0180] Step 2. When the EIF receives the message from Step 1 (for example, if the message from Step 1 contains a New PDU session indication), the EIF may send a request message to the binding support function (BSF) to obtain the PCF ID / address responsible for the UE (100).
[0181] The message may include the UE ID (or S-NSSAI, DNN) included in the message received in step 1. Additionally, the message may include notification information (e.g., EIF address).
[0182] Step 3. The BSF may include the PCF ID / address for the UE ID included in the request message received from the EIF in the response message sent to the EIF.
[0183] Step 4. The EIF may send a response message to the Consumer NF (e.g., NEF). The message may include the following information. If it fails, the remaining steps are not performed.
[0184] - (If successful) result=success, subscription correlation ID, expiry time, first corresponding energy related information report (eg, UE location information (TAI and cell ID), gNB ID, UPF ID, SMF ID)
[0185] - (If it fails, depending on the response message received from the BSF in Step 3) result=failed, cause = UE is not registered (or serving AMF for UE is not found)
[0186] - (If it fails, depending on the response message received from the BSF in Step 3) result=failed, no PDU session established for the UE
[0187] Step 5. The EIF can send a message to the PCF (140) for the UE (100) to subscribe to the PDU Session or SMF information for the UE (100).
[0188] In another embodiment, the EIF may send a request message to store the following information in the UDR via the PCF (140). The message may include a UE ID, S-NSSAI, DNN, notification information (e.g., an ECI address), and an event ID (an event for information regarding ECI calculation or an event for a data volume).
[0189] Step 6. A new PDU session can be established for UE (100).
[0190] Step 7. If a new SM Policy association is established for UE (100) (or S-NSSAI, DNN) and if there is a subscription for information about UE sessions or SMF information events for the corresponding UE (100) (or for UE (100) and S-NSSAI, DNN) (i.e., if a subscription request message containing the corresponding UE ID, S-NSSAI, DNN is received in Step 5), PCF (140) may send a notification message to EIF containing one or more of a subscription notification ID, SMF ID / address, an indicator indicating that a new serving SMF has been added for UE (100), S-NSSAI, DNN, and PDU Session ID.
[0191] In another embodiment, if in step 5 the EIF stores subscription information for information for ECI calculation in the UDR via the PCF (140), the PCF (140) can receive such information from the UDR in the SM policy association procedure. If the message received from the UDR contains a UE ID, S-NSSAI, DNN, event ID, and notification correlation ID, and if the event ID is an event ID for the SMF (135), the PCF (140) can send a request message to the SMF (135) to subscribe to information for ECI on behalf of the EIF. The information received from the UDR may be used in the message.
[0192] When SMF (135) receives a subscription request message for ECI from PCF (140), it may send a notification message for the subscription to the EIF address included in the message (i.e., the address included in the notification information). In this case, step 9 is performed.
[0193] Step 8. If the notification message received in Step 7 contains an indicator that a new serving SMF has been added for the UE (100), the EIF may send a subscription request message for ECI calculation containing the UE ID to the SMF (135) to the SMF ID / address included in the message.
[0194] If the EIF receives a subscription request message for energy consumption information in step 1, it may include an event ID in the message sent to the SMF (135). For example, it may include an event ID indicating data usage or an event ID indicating information for ECI calculation.
[0195] If the message received by the EIF in step 1 contains one or more of the UE ID, S-NSSAI, DNN, and IP Filter, the EIF may include the corresponding parameters in the message sent to the SMF (135).
[0196] If the EIF receives a message in step 1 that contains an access type, the EIF may include the corresponding access type in a message sent to the SMF (135).
[0197] The EIF may include a reporting period and notification information in a message sent to the SMF (135). If the EIF wants to directly receive information for energy consumption calculation from the UPF (130) (e.g., user data usage information, such as UL / DL data volume information for a certain period of time), it may include address information (e.g., FQDN or IP Address) to receive the notification in the notification information along with a direct notification indicator in the message sent to the SMF (135).
[0198] Step 9. When the SMF (135) receives a subscription request message from the EIF, it may send a subscription request message to the corresponding UPF(s) (130) to collect data volume (or information needed to calculate ECI) for the target included in the message (e.g., UE ID, S-NSSAI, DNN, IP Filter, App ID included in the message). The message may include a time period. Based on the target information received from the SMF (135), the UPF (130) may collect data volume usage (or information needed to calculate ECI) according to the time period and send an event notification message to the SMF (135).
[0199] SMF (135) sends a notification message to EIF based on the notification message received from UPF (130), including UE ID, S-NSSAI, DNN, IP Filter, App ID, and list of data volume entry<UL / DL data volume, UPF ID(s), gNB ID(s), reference time internval> It can include.
[0200] A reference time interval represents information indicating the time at which a measurement was taken for a measurement performed during the time interval. For example, it may include timestamp information (e.g., if the measurement during the time interval represents the Nth measurement, it represents the Nth measurement).
[0201] The SMF (135) can determine the gNB ID for the UE (100) based on UE location information (ULI) (e.g., tracking area identifier (TAI) and cell ID) received from the AMF (120) or information received from the UPF (130) (e.g., ULI or gNB ID(s)). If the gNB ID has changed, the SMF (135) can add a new data volume entry containing the previous gNB ID and the new gNB ID to the notification message. Additionally, the SMF (135) can include an indicator indicating that the gNB ID has changed (e.g., an indicator indicating a handover) and / or information about the time the handover occurred (e.g., within a time interval) in the notification message sent to the EIF.
[0202] If the message received by the EIF from the SMF (135) contains gNB ID and / or UPF ID(s) and there is no associated node-level energy consumption information and node-level data volume, the EIF may send a message to the OAM to request such information. The EIF may include the gNB ID(s) and / or UPF ID(s) contained in the message received from the SMF (135) in the request message sent to the OAM. When the OAM receives a request message from the EIF containing gNB ID, it may include the Data Volume and energy consumption measured at specific intervals for the gNB ID in the message sent to the EIF.
[0203] When the OAM receives a request message containing a UPF ID from the EIF, it can include the Data Volume and energy consumption measured at a specific period for the UPF ID in the message sent to the EIF to be transmitted.
[0204] The EIF can obtain the data volume consumed by the gNB (110), N3IWF, and UPF (130) of the UE (100) during a specific time period based on the notification message received from each SMF (135). Additionally, it can obtain the node-level data volume and node-level energy consumption consumed by the gNB (110), N3IWF, and UPF (130) from the OAM. For granularity G (e.g., one of UE (100), UE (100), and S-NSSAI, PDU Session, Traffic Flow), the EIF can calculate the energy consumption (i.e., E_G,N) at each node N (e.g., N can be one of gNB (110), N3IWF, and UPF (130)) as follows.
[0205] - E_G,N = (Energy consumption of G) * (Data volume transmitted by N to G) / (Data volume transmitted by N)
[0206] When EIF calculates the energy consumption for granularity G (e.g., UE (100), UE (100) and one of 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 (130), N3IWF, gNB (110)) that handle the traffic of UE (100).
[0207] If the message received from the SMF (135) contains a handover indicator and / or contains two or more gNB IDs, the EIF may send a message to the OAM to request energy consumption information and data volume information at the time of handover for the new gNB ID. The message may include one or more indicators requesting the new gNB ID, the measurement time (e.g., information indicating the time from when the handover occurred during the time interval to when the time interval ended), energy consumption, and data volume information.
[0208] Based on information received from the OAM, the EIF can calculate energy consumption information regarding granularity G for the reference time interval during which the handover occurred.
[0209] The EIF can include the energy consumption of granularity G (e.g., UE (100), UE (100) and one of S-NSSAI, PDU Session, Traffic Flow) that the Consumer NF subscribes to in a notification message sent to the Consumer NF.
[0210] Step 10. The PDU session is released for UE (100).
[0211] Step 11a. If the SM Policy association for UE (100) (or S-NSSAI, DNN) is released and / or the existing serving SMF information for UE (100) is deleted, and if there is a subscription for information or SMF information events for the UE session for the corresponding UE (100) (or S-NSSAI, DNN) (i.e., received a subscription request message containing the corresponding UE ID in Step 5), the PCF (140) may send a notification message to the EIF subscribed to for the corresponding UE ID (and S-NSSAI and / or DNN) including a subscription notification ID, deleted SMF ID(s), an indicator indicating that the SMF information responsible for UE (100) has been deleted (or an indicator indicating that the PDU Session has been released), and one or more of the S-NSSAI, DNN, and PDU Session IDs.
[0212] 11b. If the information contained in the message of step 11a includes an indicator that the responsible SMF information has been deleted (or an indicator that the PDU Session has been released), the EIF may send a subscription unsubscribe request message containing a subscription correlation ID to the corresponding SMF (135).
[0213] Step 11c. If the PDU session for the UE ID (or S-NSSAI, DNN) that the EIF is subscribed to in Step 9 is released, the SMF (135) may send a message to the EIF to cancel the subscription to information for ECI calculation. The message may include a subscription correlation ID, a subscription termination indication, and a cause (e.g., all corresponding PDU session(s) have been released). If the message received from the SMF (135) includes a subscription termination indication, the EIF may delete the subscription information for the subscription correlation ID included in the message.
[0214] Additionally, SMF (135) can send a message to UPF (130) to cancel the information subscription (or data volume / usage subscription) for ECI calculation.
[0215] FIG. 5 is a block diagram of a terminal (100) or user equipment (100) according to one embodiment of the present disclosure.
[0216] The terminal (100) is an electronic device capable of wireless communication and may have various form factors. Examples of the terminal may include at least one of a user device (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or other devices / systems capable of performing wireless communication with a base station (BS) and / or other terminals via a wireless channel.
[0217] Referring to FIG. 5, the terminal (100) may include at least one transceiver (or transceiver) (520) (hereinafter, transceiver), at least one processor (510) (hereinafter, processor), and at least one memory (530) (hereinafter, memory). According to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure, the transceiver (520), processor (510), and memory (530) of the terminal (100) may be operated. However, the components of the terminal (100) are not limited to the examples of components shown in FIG. 5. In other embodiments, the terminal (100) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (520), processor (510), or memory (530) may be integrated into a single component.
[0218] The transceiver (520) may be a basic communication circuit or communication circuitry that enables the terminal (100) to perform wireless communication with a node or entity of a network. For example, the transceiver (520) may enable the terminal (100) to transmit and receive signals with a base station via cellular wireless communication or to transmit and receive signals with another terminal via cellular wireless communication. For example, the transceiver (520) may be 3G (3rd generation), 4G (4th generation), LTE (long-term evolution), 5G (5th generation), NR (new radio), 6G (6th It can support at least one of various cellular wireless communication technologies including generation, etc., and the various cellular wireless communication technologies supported by the transceiver (520) may include all subsequent evolved generations of wireless communication.
[0219] According to one embodiment, the terminal (100) may include a plurality of transceivers, and for example, when supporting EN-DC (E-UTRA (evolved-universal terrestrial radio access) - NR dual connectivity), it may include a first transceiver supporting 4G LTE wireless communication and a second transceiver supporting 5G NR wireless communication. According to another embodiment, when the terminal (100) supports NR-DC (NR Dual Connectivity), the terminal (100) may include a plurality of transceivers supporting 5G NR wireless communication. According to another embodiment, when the terminal (100) supports short-range wireless communication, the terminal (100) may separately include a transceiver that supports at least one of a group of wireless communication protocol standards such as Bluetooth®, wireless LAN or WLAN (wireless local area network) network (including, but not limited to, IEEE (institute of electrical and electronics engineer) 802.11-2016 standard or modifications thereof such as 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be).
[0220] According to one embodiment, the transceiver (520) may include various circuit structures used to transmit and receive signals through a base station and a wireless channel. The signals may include control information and data. For example, the transceiver (520) may be configured to include an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (520) may output a signal received through a wireless channel to a processor (510) and transmit a signal output from the processor (510) through a wireless channel.
[0221] The processor (510) can control the overall operation of the terminal (100) according to an embodiment of the present disclosure. The processor (510) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may execute various data processing operations. The processor (510) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (530) individually, collectively, or in any combination. Additionally, the processor (510) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.
[0222] The processor (510) is electrically, operatively, and / or communicatively coupled to the transceiver (520) so as to control the transceiver (520).
[0223] The processor (510) may include at least one processor (or, processing circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. For example, the processor (510) may include a communication processor (CP) that controls communication operations and an application processor (AP) that controls the execution of an upper layer (e.g., an application layer). In a specific embodiment, at least one part of the processor (510) may be included in one chip (or, IC), and another part of the processor (510) may be included in a separate chip (or, IC). Alternatively, at least one processor may be included in other components, e.g., a transceiver (520) or a memory (530).
[0224] The processor (510) may perform, cause, or control the operation of a terminal to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (510) may control the operation of a terminal to process a downlink signal received from a base station or to generate an uplink signal and transmit it to a base station. To this end, the processor (510) may control other components of the terminal (100) to perform various operations by executing computer programs, code, or instructions stored in memory (530).
[0225] Memory (530) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (530) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.
[0226] The memory (530) can be electrically, operatively, and / or communicatively coupled to the processor (510) and can be accessed by the processor (510).
[0227] A computer program, code, or instruction that can be executed by a processor (510) may be stored in the memory (530). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (510) may be stored in a single memory device or may be separated and distributed across two or more memory devices. The processor (510) may perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (530).
[0228] According to one embodiment of the present disclosure, the operation of the terminal (100) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (530), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.
[0229] A terminal or base station can perform various communication procedures related to the control plane or user plane by interacting with network entities based on communication through a wireless channel. For example, the terminal can communicate with network entities such as an access and mobility management function (AMF) (120) and a session management function (SMF) (135) through the base station. Alternatively, the base station can perform at least one communication procedure by directly transmitting and receiving signals to or relaying signals with network entities. The structure of the above network entities will be explained in more detail through the drawings below.
[0230] FIG. 6 is a block diagram of a network entity (600) that performs network functions according to one embodiment of the present disclosure.
[0231] A network entity (600) may include one or more network functions (NF) that constitute a core network (e.g., 5G (5th generation) core, 5GC) in a communication system, or entities (devices, devices, nodes, or servers, etc.) that perform part of a network function. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across multiple network entities. Additionally, when an NF is implemented within a network entity, the NF may be implemented in the form of software, and in such cases, a program for running the NF may be loaded into the memory of the network entity (600).
[0232] A single NF can be implemented as one or more instances and can operate by being distributed across the same network entity or multiple network entities. Here, the instance is a software unit that logically executes a specific network function and may be separate from physical hardware resources. Additionally, one or more NFs may be implemented as a single network slice to operate in order to satisfy the specifications required by a specific service.
[0233] The above NF includes an access and mobility management function (AMF) (120), a session management function (SMF) (135), a local session management function (L-SMF), a user plane function (UPF) (130), a local user plane function (L-UPF), a policy control function (PCF) (140), unified data management (UDM) (145), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF) (170), a network slice selection function (NSSF) (160), a network data analytics function (NWDAF) (165), a network slice admission control function (NSACF) (180), and an authentication server function, It may include any one of AUSF), data network (DN) (175), OAM, EIF, EMF, NEF, AUSF, N3IWF, or BSF.
[0234] Referring to FIG. 6, a network entity (600) may include at least one transceiver (620) (hereinafter, transceiver), at least one processor (610) (hereinafter, processor), and at least one memory (630) (hereinafter, memory). As described above, the NF may be implemented in the form of a physical device such as the network entity (600), or may be implemented and executed in the form of a virtualized instance. When the NF is implemented in the form of an instance, it may not necessarily include physical components as shown in FIG. 6. In such cases, the instance may be composed of one or more logical functional units and may be logically represented.
[0235] According to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure, the transceiver (620), processor (610), and memory (630) of the network entity (600) may be operated. However, the components of the network entity (600) are not limited to the examples of components shown in FIG. 6. In other embodiments, the network entity (600) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in one embodiment, the transceiver (620), processor (610), or memory (630) may be implemented as a single component.
[0236] The transceiver (620) is a collective term for the transceiver and receiver of a network entity (600) and may be a communication circuit for transmitting and receiving signals with a terminal (user equipment, UE), a base station, or another network entity. In this case, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for wired communication. For example, the transceiver (620) may include circuits, logic, hardware, etc. configured to exchange control plane messages or user plane messages with a terminal, a base station, or other core network entities via wireless or wired communication. The transceiver (620) may operate using various protocols (e.g., NAS (Non-Access Stratum) protocol). Depending on the convenience of explanation and technical implementation, the transceiver (620) may be referred to as a transceiver, a network interface, a communication circuitry, a network interface circuitry, or a communication interface circuitry.
[0237] The processor (610) may control the overall operation of the network entity (600) according to an embodiment of the present disclosure. In one embodiment, the processor (610) may be implemented as one or more IC (integrated circuit or circuitry) chips and may execute various data processing operations. The processor (610) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (630) individually, collectively, or in any combination. Additionally, the processor (610) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits. Additionally, it should be noted that the processor (610) may not necessarily be composed of physical hardware when the network function (600) is implemented in an instance form according to another embodiment.
[0238] According to one embodiment, the processor (610) is electrically, operatively, and / or communicatively coupled to the transceiver (620) so as to control the transceiver (620).
[0239] The processor (610) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a specific embodiment, at least one part of the processor (610) may be included in one chip (or IC), and another part of the processor (610) may be included in a separate chip (or IC). Alternatively, at least one processor may be included in other components, such as a transceiver (620) or a memory (630).
[0240] The processor (610) may perform or control the operation of a network entity (600) to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (610) may control the operation of the network entity (600) to exchange control plane messages or user plane messages with terminals, base stations, or other core network entities via wireless or wired communication using various protocols (e.g., NAS protocols). To this end, the processor (610) may control other components of the network entity (600) to perform various operations by executing computer programs, code, or instructions stored in memory (630).
[0241] Memory (630) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (630) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.
[0242] According to one embodiment, the memory (630) may be electrically, operatively, and / or communicatively coupled to the processor (610) and may be accessed by the processor (610).
[0243] A computer program, code, or instruction that can be executed by a processor (610) may be stored in the memory (630). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (610) may be stored in a single memory or separated and distributed across two or more memories. The processor (610) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (630).
[0244] According to one embodiment of the present disclosure, the operation of a network entity (600) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (630), based on a processing circuitry not configured to execute instructions, and / or based on a component of a processing circuitry not configured to execute instructions.
[0245] Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0246] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.
[0247] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), magnetic disc storage devices, CD-ROM (Compact Disc-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.
[0248] Additionally, the above program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.
[0249] In the specific embodiments of the present disclosure described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, or even if a component is expressed in the singular form, it may be composed of a plural form.
[0250] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.
[0251] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment may be combined to operate a base station and a terminal. For example, parts of one embodiment of the present disclosure and another embodiment may be combined to operate a base station and a terminal. In addition, other variations based on the technical concept of the above embodiments may be implemented in other systems, such as FDD LTE systems, TDD LTE systems, 5G or NR systems.
[0252] Meanwhile, the order of description in the drawings illustrating the method of the present invention does not necessarily correspond to the order of execution, and the order of execution may be changed or executed in parallel.
[0253] Alternatively, drawings describing the method of the present invention may omit some components and include only some components to the extent that the essence of the present invention is not impaired.
[0254] In addition, the method of the present invention may be implemented by combining some or all of the contents included in each embodiment within a scope that does not impair the essence of the invention.
[0255] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only and is not limited to the embodiments disclosed. Those skilled in the art will understand that other specific forms can be easily modified without altering the technical spirit or essential features of the present disclosure. The scope of the present disclosure is defined by the claims set forth below rather than by the foregoing detailed description, and all modifications or variations derived from the meaning and scope of the claims and equivalent concepts should be interpreted as being included within the scope of the present disclosure.
Claims
1. A method performed by the Energy Information Function (EIF) in a wireless communication system, A step of receiving a subscription message requesting Energy Consumption Information (ECI) for a terminal from a network entity; Based on the above subscription message, a step of obtaining information of the Access and Mobility Management Function (AMF) responsible for the terminal from the Unified Data Management (UDM); A step of transmitting a first response message to the network entity based on information obtained from the above UDM; A step of transmitting a first subscription request message to the above AMF to obtain new SMF (Session Management Function) information for the terminal; A step of receiving a first notification message from the AMF based on the establishment of a new PDU (Protocol Data Unit) session for the terminal and the addition of a new SMF for the terminal; Based on the above notification message, the step of sending a second subscription request message for ECI calculation to SMF; and A method comprising the step of calculating the energy consumption of the terminal based on a second notification message received from the above SMF.
2. The method of claim 1, wherein the subscription message comprises at least one of an event ID, a terminal ID, S-NSSAI (single-network slice selection assistance information), DNN (data network name), an IP (internet protocol) filter, an access type, a reporting period, area information, or a new PDU session indicator.
3. In claim 2, the step of obtaining information of the AMF responsible for the terminal from the UDM is: A step of transmitting a request message to the UDM to obtain information of the AMF in charge of the terminal, wherein the request message includes at least one of the terminal ID, the S-NSSAI, the DNN, or the access type; and A method comprising the step of receiving a second response message from the above UDM that includes ID or address information of the above AMF.
4. A method according to claim 1, wherein the first response message comprises at least one of success information, a subscription-related ID, an expiration time, terminal location information, a gNB ID, a UPF (user plane function) ID, an SMF ID, or failure cause information.
5. The method of claim 1, wherein the first subscription request message comprises at least one of a terminal ID, S-NSSAI, DNN, or event ID.
6. The method of claim 1, wherein the first notification message comprises at least one of a subscription notification ID, SMF information, an indicator indicating the addition of a new SMF, S-NSSAI, DNN, or PDU session ID.
7. The method of claim 2, wherein the second subscription request message comprises at least one of the event ID, the terminal ID, the S-NSSAI, the DNN, the IP filter, the access type, the reporting period, the notification information, the direct notification indicator, or the notification receiving address information.
8. The method of claim 1, wherein the second notification message comprises at least one of terminal ID, S-NSSAI, DNN, IP filter, application ID, data volume information, UPF ID, gNB ID, measurement time information, handover indicator, or handover occurrence time information.
9. In the Energy Information Function (EIF) of a wireless communication system, At least one transmitting and receiving unit; At least one processor connected to communicate with the above-mentioned transceiver; and It includes at least one memory connected to communicate with the at least one processor and storing instructions that can be executed by the at least one processor individually or in any combination thereof. The above EIF is, Receives a subscription message requesting Energy Consumption Information (ECI) for a terminal from a network entity, and Based on the above subscription message, information of the Access and Mobility Management Function (AMF) responsible for the terminal is obtained from the Unified Data Management (UDM), and Based on the information obtained from the above UDM, a first response message is transmitted to the above network entity, and A first subscription request message is transmitted to the above AMF to obtain new SMF (Session Management Function) information for the terminal, and Based on the establishment of a new PDU (Protocol Data Unit) session for the terminal and the addition of a new SMF for the terminal, a first notification message is received from the AMF, and Based on the above notification message, a second subscription request message for ECI calculation is sent to SMF, and EIF that calculates the energy consumption of the terminal based on the second notification message received from the above SMF.
10. In claim 9, the subscription message comprises at least one of an event ID, terminal ID, S-NSSAI (single-network slice selection assistance information), DNN (data network name), IP (internet protocol) filter, access type, reporting period, area information, or new PDU session indicator, EIF.
11. In Paragraph 10, The above EIF is, A request message is transmitted to the above UDM to obtain information of the above AMF responsible for the above terminal, and the request message includes at least one of the above terminal ID, the above S-NSSAI, the above DNN, or the above access type, and EIF receiving a second response message containing ID or address information of the AMF from the above UDM.
12. In claim 9, the first subscription request message comprises an EIF including at least one of a terminal ID, S-NSSAI, DNN, or event ID.
13. In claim 9, the first notification message comprises at least one of a subscription notification ID, SMF information, an indicator indicating the addition of a new SMF, an S-NSSAI, a DNN, or a PDU session ID, EIF.
14. In claim 10, the second subscription request message comprises at least one of the event ID, the terminal ID, the S-NSSAI, the DNN, the IP filter, the access type, the reporting period, the notification information, the direct notification indicator, or the notification receiving address information, EIF.
15. In claim 9, the second notification message comprises at least one of terminal ID, S-NSSAI, DNN, IP filter, application ID, data volume information, UPF ID, gNB ID, measurement time information, handover indicator, or handover occurrence time information, EIF.