Energy monitoring

Abstract

One disclosure of the present specification (present disclosure) provides a method by which an AF performs communication. The method includes the steps of: transmitting an AF request to a core network, wherein the AF request includes energy-related information; and receiving an energy monitoring report, wherein the energy monitoring report includes a result of monitoring for energy use, and the monitoring is performed by the core network, a base station, or a user equipment (UE) on the basis of the energy-related information.

Description

Energy monitoring

[0001] This specification relates to mobile communications.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communications. Numerous approaches have been proposed to achieve LTE's goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE's high-level requirements include reduced cost per bit, improved service availability, flexible use of frequency bands, a simple architecture, open interfaces, and adequate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for new radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR in a timely manner, meeting both urgent market needs and the longer-term requirements outlined by the ITU-R (ITU radio communication sector) International Mobile Telecommunications (IMT)-2020 process. NR must also be able to utilize any spectrum band up to at least 100 GHz, ensuring that it remains available for wireless communications well into the future.

[0004] NR aims to be a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable and low latency communications (URLLC). NR must be inherently forward-compatible.

[0005] Energy monitoring is performed at the request of AF.

[0006] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0007] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0008] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0009] Figure 4 is a structural diagram of a next-generation mobile communications network.

[0010] Figure 5 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0011] Figures 6 and 7 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0012] Figure 8 shows a procedure diagram according to the disclosure of this specification.

[0013] Figure 9 shows a procedure diagram according to a first embodiment of the disclosure of the present specification.

[0014] Figure 10 shows a procedure diagram according to a second embodiment of the disclosure of the present specification.

[0015] Figure 11 illustrates the AF procedure for the disclosure of this specification.

[0016] Figure 12 illustrates the PCF procedure for the disclosure of this specification.

[0017] Figure 13 illustrates the UE's procedure for disclosure of this specification.

[0018] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multicarrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented via wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA can be implemented via wireless technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (evolved UTRA). UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of E-UMTS (evolved UMTS) that uses E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and / or 5G NR (new radio).

[0019] For convenience of explanation, the implementation of this specification is primarily described in relation to a 3GPP-based wireless communication system. However, the technical features of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system. However, aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

[0020] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0021] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Alternatively, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0022] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0023] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0024] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

[0025] Additionally, parentheses used herein may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information."

[0026] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0027] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0028] Hereinafter, the present specification will be described in more detail with reference to the drawings. In the following drawings and / or description, the same reference numbers may refer to the same or corresponding hardware blocks, software blocks, and / or functional blocks, unless otherwise indicated.

[0029] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0030] The 5G usage scenario shown in FIG. 1 is only an example, and the technical features of this specification can be applied to other 5G usage scenarios not shown in FIG. 1.

[0031] The three main requirement categories for 5G are (1) enhanced mobile broadband (eMBB), (2) massive machine type communication (mMTC), and (3) ultra-reliable and low latency communications (URLLC).

[0032] Referring to FIG. 1, a communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 illustrates a 5G network as an example of a network of the communication system (1), but the implementation of the present disclosure is not limited to a 5G system and can be applied to future communication systems beyond the 5G system.

[0033] The base station (200) and the network (300) may be implemented as wireless devices, and a particular wireless device may operate as a base station / network node in relation to other wireless devices.

[0034] Wireless devices (100a to 100f) refer to devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), extended reality (XR) devices (100c), portable devices (100d), home appliances (100e), IoT devices (100f), and artificial intelligence (AI) devices / servers (400). For example, vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices, and may be implemented in the form of head-mounted devices (HMDs) and heads-up displays (HUDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0035] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving functions, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a holographic device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

[0036] For example, a UAV may be an aircraft that is unmanned and navigated by radio control signals.

[0037] For example, a VR device may include a device for implementing objects or backgrounds in a virtual environment. For example, an AR device may include a device that implements objects or backgrounds in a virtual world by connecting them to objects or backgrounds in the real world. For example, an MR device may include a device that implements objects or backgrounds in a virtual world by merging them with objects or backgrounds in the real world. For example, a holographic device may include a device that implements 360-degree stereoscopic images by recording and reproducing three-dimensional information using the light interference phenomenon that occurs when two laser lights, called holograms, meet.

[0038] For example, a public safety device may include an image relay device or imaging device that can be worn on the user's body.

[0039] For example, MTC devices and IoT devices may be devices that do not require direct human intervention or manipulation. Examples include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.

[0040] For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, curing, or preventing a disease. For example, a medical device may be a device used for diagnosing, treating, alleviating, or correcting an injury or damage. For example, a medical device may be a device used for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device may be a device used for the purpose of regulating pregnancy. For example, a medical device may include a therapeutic device, a driving device, an (in vitro) diagnostic device, a hearing aid, or a surgical device.

[0041] For example, a security device may be a device installed to prevent potential hazards and maintain safety. For example, a security device may be a camera, closed-circuit television (CCTV), a recorder, or a black box.

[0042] For example, a fintech device may be a device capable of providing financial services, such as mobile payments. For example, a fintech device may include a payment device or a point-of-sale system.

[0043] For example, a weather / environment device may include a device that monitors or predicts the weather / environment.

[0044] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). AI technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0045] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and a base station (200) and / or between base stations (200). Here, the wireless communication / connection can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or, device-to-device (D2D) communication), and base station-to-base station communication (150c) (e.g., relay, integrated access and backhaul (IAB)). Through the wireless communication / connection (150a, 150b, 150c), the wireless devices (100a to 100f) and the base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of the various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present specification.

[0046] AI is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.

[0047] A robot can be defined as a machine that automatically processes or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making decisions, and performing actions on its own can be called an intelligent robot. Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with a drive unit, including an actuator or motor, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots include wheels, brakes, and propellers in their drive unit, enabling them to drive on the ground or fly in the air.

[0048] Autonomous driving refers to the technology of driving on one's own, while autonomous vehicles refer to vehicles that drive without, or with minimal, user intervention. For example, autonomous driving can include technologies such as lane keeping, automatic speed control like adaptive cruise control, autonomous driving along a set route, and autonomous driving based on a set destination. Vehicles encompass all types of vehicles: those with internal combustion engines, hybrid vehicles with both internal combustion engines and electric motors, and electric vehicles with only electric motors. These vehicles can include not only cars but also trains and motorcycles. Autonomous vehicles can be viewed as robots with autonomous driving capabilities.

[0049] Extended reality is a general term for VR, AR, and MR. VR technology provides real-world objects and backgrounds as CG images only, AR technology provides virtual CG images over images of real objects, and MR technology is a CG technology that mixes and combines virtual objects with the real world. MR technology is similar to AR in that it displays real and virtual objects together. However, there is a difference: while AR uses virtual objects to complement real objects, MR uses virtual and real objects equally.

[0050] NR supports multiple numerologies, or subcarrier spacing (SCS), to support diverse 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0051] The NR frequency band can be defined by two types of frequency ranges (FR1 and FR2). The numerical values ​​of the frequency ranges can be changed. For example, the two types of frequency ranges (FR1 and FR2) can be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in NR systems, FR1 can mean the "sub-6GHz range," and FR2 can mean the "above 6GHz range," which can be referred to as millimeter wave (mmW).

[0052] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0053] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 2 below. That is, FR1 may include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include unlicensed bands. Unlicensed bands may be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

[0054] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0055] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (low power wide area network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced MTC). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0056] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0057] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use case / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {the wireless devices (100a to 100f) and the base station (200)}, {the wireless devices (100a to 100f) and the wireless devices (100a to 100f)}, and / or {the base station (200) and the base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be configured by various components, devices / parts, and / or modules.

[0058] The first wireless device (100) may include at least one transceiver, such as a transceiver (106), at least one processing chip, such as a processing chip (101), and / or one or more antennas (108).

[0059] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or alternatively, the memory (104) may be located external to the processing chip (101).

[0060] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signal and transmit a wireless signal including the first information / signal via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

[0061] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

[0062] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). Each transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (radio frequency) unit. In the present specification, the first wireless device (100) may represent a communication modem / circuit / chip.

[0063] The second wireless device (200) may include at least one transceiver, such as a transceiver (206), at least one processing chip, such as a processing chip (201), and / or one or more antennas (208).

[0064] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be located external to the processing chip (201).

[0065] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signal and transmit a wireless signal including the third information / signal via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

[0066] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements instruction codes, commands and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

[0067] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). Each transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with the RF unit. In the present specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0068] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDUs), one or more service data units (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0069] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), and / or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a central processing unit (CPU), a graphic processing unit (GPU), and a memory control processor.

[0070] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0071] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0072] One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein via one or more antennas (108, 208). In the present specification, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0073] One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter. For example, one or more transceivers (106, 206) may up-convert an OFDM baseband signal to an OFDM signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) may receive an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0074] Although not illustrated in FIG. 2, the wireless device (100, 200) may further include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

[0075] In the implementation of the present specification, a UE can operate as a transmitter in the uplink (UL) and as a receiver in the downlink (DL). In the implementation of the present specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released in the first wireless device (100) can be configured to perform UE operations according to the implementation of the present specification or to control a transceiver (106) to perform UE operations according to the implementation of the present specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of the present specification or to control a transceiver (206) to perform base station operations according to the implementation of the present specification.

[0076] In this specification, a base station may be referred to as a Node B, an eNode B (eNB), or a gNB.

[0077] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0078] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0079] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0080] The UE (100) includes a processor (102), memory (104), a transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0081] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processors, EXYNOS made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors made by Intel® TM It can be found in the series processors or the corresponding next-generation processors.

[0082] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

[0083] A transceiver (106) is operably coupled to the processor (102) and transmits and / or receives a radio signal. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include a baseband circuit for processing a radio frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a radio signal.

[0084] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0085] The display (143) outputs the results processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0086] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

[0087] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0088] Figure 4 is a structural diagram of a next-generation mobile communications network.

[0089] 5GC (5G Core) may include various components, and in FIG. 5, some of them include AMF (Access and Mobility Management Function) (410), SMF (Session Management Function) (420), PCF (Policy Control Function) (430), UPF (User Plane Function) (440), AF (Application Function) (450), UDM (Unified Data Management) (460), and N3IWF (Non-3GPP (3rd Generation Partnership Project) Inter Working Function) (490).

[0090] The UE (100) is connected to a data network via UPF (440) through a Next Generation Radio Access Network (NG-RAN) including a gNB (20).

[0091] The UE (100) can also receive data services via untrusted non-3GPP access, such as a Wireless Local Area Network (WLAN). To connect the non-3GPP access to the core network, an N3IWF (490) may be deployed.

[0092] The illustrated N3IWF (490) performs the function of managing interworking between non-3GPP access and 5G system. When UE (100) is connected to non-3GPP access (e.g., WiFi, referred to as IEEE 801.11), UE (100) can be connected to 5G system through N3IWF (490). N3IWF (490) performs control signaling with AMF (410) and is connected to UPF (440) through N3 interface for data transmission.

[0093] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform functions to manage Non-Access Stratum (NAS) security. The AMF (410) can perform functions to handle mobility in the idle state.

[0094] The illustrated UPF (440) is a type of gateway through which user data is transmitted and received. The UPF node (440) can perform all or part of the user plane functions of the S-GW (Serving Gateway) and P-GW (Packet Data Network Gateway) of 4th generation mobile communications.

[0095] The UPF (440) acts as a boundary point between the next generation radio access network (NG-RAN) and the core network, and is an element that maintains a data path between the gNB (20) and the SMF (420). In addition, when the UE (100) moves across the area served by the gNB (20), the UPF (440) acts as a mobility anchor point. The UPF (440) can perform a function of handling PDUs. For mobility within the NG-RAN (Next Generation-Radio Access Network defined after 3GPP Release-15), the UPF can route packets. Additionally, the UPF (440) may also function as an anchor point for mobility with other 3GPP networks (RANs defined before 3GPP Release-15, e.g., UTRAN, E-UTRAN (Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network)) or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access Network). The UPF (440) may correspond to a termination point of a data interface toward a data network.

[0096] The illustrated PCF (430) is a node that controls the business operator's policy.

[0097] The illustrated AF (450) is a server for providing various services to the UE (100).

[0098] The illustrated UDM (460) is a type of server that manages subscriber information, such as the HSS (Home Subscriber Server) of 4th generation mobile communications. The UDM (460) stores and manages the subscriber information in a Unified Data Repository (UDR).

[0099] The illustrated SMF (420) can perform the function of allocating an IP (Internet Protocol) address of the UE. In addition, the SMF (420) can control a PDU (protocol data unit) session.

[0100] For reference, the drawing symbols for AMF (410), SMF (420), PCF (430), UPF (440), AF (450), UDM (460), N3IWF (490), gNB (20), or UE (100) may be omitted below.

[0101] 5G mobile communications support multiple numerologies, or subcarrier spacing (SCS), to support diverse 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands. A 30 kHz / 60 kHz SCS supports dense urban environments, lower latency, and wider carrier bandwidth. An SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0102] Figure 5 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0103] The 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function).

[0104] - AUSF (Authentication Server Function)

[0105] - AMF (Access and Mobility Management Function)

[0106] - DN (Data Network), 예를 들어 운영자 서비스, 인터넷 접속 또는 타사 서비스

[0107] - USDF (Unstructured Data Storage Function)

[0108] - NEF (Network Exposure Function)

[0109] - I-NEF (Intermediate NEF)

[0110] - NRF (Network Repository Function)

[0111] - NSSF (Network Slice Selection Function)

[0112] - PCF (Policy Control Function)

[0113] - SMF (Session Management Function)

[0114] - UDM (Unified Data Management)

[0115] - UDR (Unified Data Repository)

[0116] - UPF (User Plane Function)

[0117] - UCMF (UE radio Capability Management Function)

[0118] - AF (Application Function)

[0119] - UE (User Equipment)

[0120] - (R)AN ((Radio) Access Network)

[0121] - 5G-EIR (5G-Equipment Identity Register)

[0122] - NWDAF (Network Data Analytics Function)

[0123] - CHF (CHarging Function)

[0124] Additionally, the following network features may be considered:

[0125] - N3IWF (Non-3GPP InterWorking Function)

[0126] - TNGF (Trusted Non-3GPP Gateway Function)

[0127] - W-AGF (Wireline Access Gateway Function)

[0128] Figure 5 illustrates the 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0129] In Figure 5, for clarity of the point-to-point diagram, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0130] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in Fig. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in Fig. 4.

[0131] The 5G system architecture includes the following benchmarks:

[0132] - N1: Reference point between UE and AMF.

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

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

[0135] - N4: Reference point between SMF and UPF.

[0136] - N6: Reference point between UPF and data network.

[0137] - N9: Reference point between two UPFs.

[0138] The following benchmarks illustrate the interactions that exist between NF services in NF.

[0139] - N5: Reference point between PCF and AF.

[0140] - N7: Reference point between SMF and PCF.

[0141] - N8: Reference point between UDM and AMF.

[0142] - N10: Reference point between UDM and SMF.

[0143] - N11: Reference point between AMF and SMF.

[0144] - N12: Reference point between AMF and AUSF.

[0145] - N13: Reference point between UDM and AUSF.

[0146] - N14: Reference point between two AMFs.

[0147] - N15: Reference point between PCF and AMF for non-roaming scenarios, and reference point between PCF and AMF of visited network for roaming scenarios.

[0148] - N16: Reference point between two SMFs (in case of roaming, between the SMF of the visited network and the SMF of the home network)

[0149] - N22: Reference point between AMF and NSSF.

[0150] In some cases, two NFs may need to be interconnected to serve a UE.

[0151] <Registration Procedure>

[0152] Describes the registration procedure. See section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0153] Figures 6 and 7 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0154] A UE must register with the network to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration process using one of the following registration types:

[0155] - Initial registration for 5GS; or

[0156] - mobility registration update; or

[0157] - Periodic registration update; or

[0158] - Emergency registration

[0159] The general registration procedures of Figures 6 and 7 apply to all registration procedures described above, but periodic registration updates do not need to include all parameters used in other registration procedures.

[0160] The general registration procedures of Figures 6 and 7 can also be used when registering for a 3GPP connection when the UE is already registered for a non-3GPP connection, and vice versa. Registering for a 3GPP connection when the UE is already registered for a non-3GPP connection scenario may require an AMF change.

[0161] First, the procedure of Fig. 6 is described.

[0162] (1) Step 1: The UE transmits a Registration Request message to the (R)AN. The Registration Request message corresponds to an AN message.

[0163] The registration request message may include AN parameters. For NG-RAN, the AN parameters include, for example, the 5G SAE temporary mobile subscriber identity (5G-S-TMSI) or globally unique AMF ID (GUAMI), the selected public land mobile network (PLMN) ID (or PLMN ID and network identifier (NID)), and the requested network slice selection assistance information (NSSAI). The AN parameters also include an establishment cause. The establishment cause provides the reason for requesting establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the access stratum connection establishment NSSAI inclusion mode parameter.

[0164] A registration request message may include a registration type. The registration type indicates whether the UE wants to perform an initial registration (i.e., the UE is in RM-DEREGISTERED state), or a mobility registration update (i.e., the UE is in RM-REGISTERED state and the registration procedure is initiated because the UE moves, or the UE wants to update its capabilities or protocol parameters, or because the UE requests a change in the set of network slices it is allowed to use), or a periodic registration update (i.e., the UE is in RM-REGISTERED state and the registration procedure is initiated because the periodic registration update timer has expired), or an emergency registration (i.e., the UE is in restricted service state).

[0165] When a UE performs initial registration, the UE indicates its UE ID in the registration request message, listed in decreasing priority order.

[0166] i) If the UE has a valid evolved packet system (EPS) globally unique temporary identifier (GUTI), 5G-GUTI mapped from the EPS GUTI;

[0167] ii) Native 5G-GUTI (if available) allocated by the PLMN in which the UE is attempting to register;

[0168] iii) Native 5G-GUTI allocated by a PLMN equivalent to the PLMN in which the UE is attempting to register;

[0169] iv) Native 5G-GUTI allocated by another PLMN (if available);

[0170] v) Otherwise, the UE includes a subscriber concealed identifier (SUCI) in the registration request message.

[0171] If a UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE also indicates the native 5G-GUTI as an additional GUTI. If more than one native 5G-GUTI is available, the UE selects a 5G-GUTI from items (ii)-(iv) in decreasing priority order in the list above.

[0172] When the UE performs initial registration with native 5G-GUTI, the UE indicates the relevant GUAMI information in the AN parameters. When the UE performs initial registration with SUCI, the UE does not indicate the GUAMI information in the AN parameters.

[0173] For emergency registration, if the UE does not have a valid 5G-GUTI, the SUCI is included. If the UE does not have a subscriber permanent identifier (SUPI) and does not have a valid 5G-GUTI, the PEI (Permanent Equipment Identifier) ​​is included. Otherwise, the 5G-GUTI is included, indicating the last serving AMF.

[0174] The registration request message may also include security parameters, PDU session status, etc. Security parameters are used for authentication and integrity protection. The PDU session status indicates a previously established PDU session in the UE. When the UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the PDU session status indicates the PDU session currently established in the PLMN in the UE.

[0175] (2) Step 2: (R)AN selects AMF.

[0176] If 5G-S-TMSI or GUAMI is not included, or if 5G-S-TMSI or GUAMI does not indicate a valid AMF, the (R)AN selects an AMF based on the (R)AT and the requested NSSAI, if available.

[0177] When the UE is in CM-CONNECTED state, (R)AN can forward a registration request message to AMF based on the UE's N2 connection.

[0178] If the (R)AN cannot select an appropriate AMF, the (R)AN performs AMF selection by forwarding a registration request message to the AMF configured in the (R)AN.

[0179] (3) Step 3: (R)AN sends a registration request message to the new AMF. The registration request message corresponds to the N2 message.

[0180] The registration request message may contain all of the information and / or part of the information contained in the registration request message received from the UE described in step 1.

[0181] The registration request message may include an N2 parameter. When NG-RAN is used, the N2 parameter includes the selected PLMN ID (or PLMN ID and NID), location information and cell ID related to the cell where the UE is camping, and a UE context request indicating that a UE context including security information should be established in the NG-RAN. When NG-RAN is used, the N2 parameter also includes an establishment cause.

[0182] If the registration type indicated by the UE is periodic registration update, steps 4-19 described below may be omitted.

[0183] (4) Step 4: If the UE's 5G-GUTI is included in the registration request message and the serving AMF has changed since the last registration procedure, the new AMF may invoke the Namf_Communication_UEContextTransfer service operation to the previous AMF, including the full registration request non-access stratum (NAS) message to request the UE's SUPI and UE context.

[0184] (5) Step 5: The old AMF can respond to the new AMF for the Namf_Communication_UEContextTransfer call including the UE's SUPI and UE context.

[0185] (6) Step 6: If SUCI is not provided by the UE or not retrieved from the previous AMF, the new AMF may initiate an ID request procedure by sending an Identity Request message to request SUCI from the UE.

[0186] (7) Step 7: The UE may respond with an Identity Response message including the SUCI. The UE derives the SUCI using the provided public key of the home PLMN (HPLMN).

[0187] (8) Step 8: The new AMF may decide to initiate UE authentication by calling the AUSF. In this case, the new AMF selects the AUSF based on SUPI or SUCI.

[0188] (9) Step 9: Authentication / security can be established by UE, new AMF, AUSF and / or UDM.

[0189] (10) Step 10: If the AMF has changed, the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation to notify the old AMF that the UE registration with the new AMF is complete. If the authentication / security procedure fails, the registration is rejected and the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code to the old AMF. The old AMF may continue as if the UE context transfer service operation was not received.

[0190] (11) Step 11: If the PEI was not provided by the UE or was not retrieved from the previous AMF, the new AMF may initiate the ID request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted encrypted, except when the UE performs emergency registration and cannot be authenticated.

[0191] (12) Step 12: Optionally, the new AMF can initiate ME ID checking by calling the N5g-eir_EquipmentIdentityCheck_Get service operation.

[0192] Now, the procedure of Fig. 7 following the procedure of Fig. 6 is described.

[0193] (13) Step 13: If step 14 below is performed, the new AMF can select a UDM based on SUPI, and the UDM can select a UDR instance.

[0194] (14) Step 14: New AMFs can be registered with UDM.

[0195] (15) Step 15: New AMF can select PCF.

[0196] (16) Step 16: The new AMF may optionally perform AM policy association establishment / modification.

[0197] (17) Step 17: The new AMF can send update / release SM context messages (e.g., Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext) to the SMF.

[0198] (18) Step 18: If the new AMF and the old AMF are in the same PLMN, the new AMF may send a UE context modification request to the N3IWF / TNGF / W-AGF.

[0199] (19) Step 19: N3IWF / TNGF / W-AGF may send a UE context modification response to the new AMF.

[0200] (20) Step 20: After the new AMF receives the response message from N3IWF / TNGF / W-AGF in step 19, the new AMF can register with UDM.

[0201] (21) Step 21: The new AMF sends a Registration Accept message to the UE.

[0202] The new AMF sends the UE a Registration Accept message indicating that the registration request has been accepted. If the new AMF allocates a new 5G-GUTI, it includes the 5G-GUTI. If the UE is already in the RM-REGISTERED state through another connection to the same PLMN, the UE uses the 5G-GUTI received in the Registration Accept message for both registrations. If the Registration Accept message does not include a 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration. If the new AMF allocates a new registration area, it sends the registration area to the UE in the Registration Accept message. If the Registration Accept message does not include a registration area, the UE considers the previous registration area to be valid. Mobility Restrictions are included if mobility restrictions apply to the UE and the registration type is not emergency registration. The new AMF indicates the PDU sessions established for the UE in the PDU Session State. The UE locally removes internal resources associated with PDU sessions that are not marked as established in the received PDU Session State. When a UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the UE locally removes internal resources associated with PDU sessions in the current PLMN that are not marked as established in the received PDU session status. If PDU session status information is present in the Registration Accept message, the new AMF indicates the PDU session status to the UE.

[0203] The Allowed NSSAI provided in the Registration Accept message is valid for the registration area and applies to all PLMNs that have a tracking area included in the registration area. The Mapping of Allowed NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Allowed NSSAIs. The Mapping of Configured NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Configured NSSAI for the serving PLMN.

[0204] Additionally, optionally, the new AMF performs UE policy association establishment.

[0205] (22) Step 22: If the UE successfully updates itself, it can send a Registration Complete message to the new AMF.

[0206] The UE may send a registration complete message to the new AMF to confirm that a new 5G-GUTI has been allocated.

[0207] (23) Step 23: In case of registration via 3GPP connection, if the new AMF does not release the signaling connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN. In case of registration via non-3GPP connection, if the UE is in CM-CONTENED state on the 3GPP connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN.

[0208] (24) Step 24: AMF can perform information updates on UDM.

[0209] (25) Step 25: The UE may execute a network slice-specific authentication and authorization (NSSAA) procedure.

[0210] Research is being conducted on FS_EnergyServ (Study on Energy Efficiency as a service criteria).

[0211] Some of the use cases currently discussed involve exposure to energy efficiency related information.

[0212] In this specification, enhanced functions of network nodes (e.g., AF and NEF, PCF, etc.) can be proposed targeting 5G evolution / 6G systems in a zero-touch configuration / operation environment with expanded network automation.

[0213] The method proposed in this specification allows for monitoring energy-related information used in the system. Furthermore, this energy-related information can be transmitted to a third party for effective system management. This third party may be a vertical operator (a business partner of a network operator) providing the service.

[0214] Previously, mechanisms existed for monitoring network resource usage and determining whether to provide services based on related information. However, there was no mechanism for collecting and utilizing energy-related information.

[0215] Furthermore, conventional network resource usage monitoring has been performed on a per-UE basis. This specification proposes a method for energy monitoring / reporting across a wider range of applications.

[0216] Disclosure of energy-related information based on energy efficiency ratings (agreements / setting information between operators, third parties, regulations, etc.) according to the method proposed in this specification may be meaningful for network users in terms of securing information that can be used to obtain credits (e.g., tax reductions from government agencies).

[0217] According to the method proposed in this specification, by utilizing energy-related information based on energy efficiency ratings (agreement / setting information according to business operators, third parties, regulations, etc.), information can be obtained on how customers using the network can receive credits (tax reductions from government agencies, etc.).

[0218] Energy monitoring in this specification may be monitoring of energy consumption. This energy monitoring may be performed by 5GC. The target of energy monitoring may be the energy used by the core network and / or the energy used by terminals.

[0219] Figure 8 shows a procedure diagram according to the disclosure of this specification.

[0220] Step 1. The terminal can receive specific services by establishing a PDU session, etc. that can connect to any server through 5GS.

[0221] Step 2. AF can send an AF request to NEF for external parameter provision.

[0222] The above AF request may include energy related information.

[0223] Depending on the business prior agreement or business policy, the above AF request may be accepted by 5GC.

[0224] The energy-related information included in the above AF request may include the information described in Table 3. Alternatively, the energy-related information may include a combination of the information described in Table 3. The energy-related information is not limited to the information described in Table 3. The above AF request may include the information described in Table 3.

[0225] Energy related information: A profile of energy usage per subscriber or per group of subscribers. Consists of one or more of the following: Energy monitoring key: An identifier for an energy monitoring control instance that includes one or more PCC rules. Energy usage monitoring level: Indicates the scope of the usage monitoring instance (PDU session level, per service, per slice, per UE group, per NF, per NG-RAN, per network). (Indicates the scope of the usage monitoring instance (PDU Session level or per Service or per slice or per UE group per NF or per NG-RAN or per Network)(e.g. a specific NPN)) The granularity at which energy-related information is monitored. Start date: The start date and time when the usage monitoring profile applies. End date: The date and time when the usage monitoring profile applies. Energy efficiency limit: The energy efficiency of NF, 5GC, NG-RAN, etc. according to clauses 6 and 7 of TS 28.554 v15.7.0. Energy consumption limit: TS 28.554 v15.7.0 Energy consumption of NF, 5GC, NG-RAN, etc. according to clause 6,7 Energy grade limit Energy grade calculated as a combination of EE and EC (e.g. grade 1 / grade 2, grade defined by agreement / setting of operators, 3rd parties, regulations, etc.).

[0226] The energy usage monitoring level may include granular information about the target of energy usage monitoring. For example, if the energy usage monitoring level is per PDU session, energy monitoring may be performed per PDU session, and energy consumption per PDU session may be reported to AF.

[0227] The energy efficiency limit refers to the limit on the value of the total data volume processed divided by the energy consumption. It is used when the value of the data volume processed by the NG-RAN divided by the energy consumption of the NG-RAN is to be calculated and the value of that value is to be limited. For example, if the energy efficiency limit is set to x or more, the value of the data volume processed by the NG-RAN divided by the energy consumption of the NG-RAN can be maintained at x or more.

[0228] Energy consumption limit refers to the limit on the sum of the energy consumption of the component unit elements. When the energy consumption of the NG-RAN (the sum of the energy consumption of all physical or virtual nodes constituting the NG-RAN) must not exceed an arbitrary threshold x [J] (unit: joule), the energy consumption limit of the NG-RAN can be specified as x [J].

[0229] Energy rating restrictions refer to restrictions on ratings agreed upon or established in advance by government or corporate regulations. Energy rating restrictions can be used to maintain energy efficiency or consumption at a specific level. For example, Energy Grade 1 for NG-RAN may mean that energy efficiency is greater than or equal to x and energy consumption is less than or equal to y. In this case, if the energy rating is restricted to Grade 1, energy efficiency must be maintained at or above x, and energy consumption must be maintained at or below y.

[0230] Step 3. NEF can transmit the information contained in the AF request to UDM / UDR using the Nudm_ParameterProvision service operation.

[0231] The information transmitted may include energy-related information.

[0232] Step 4. UDM / UDR can add / update the relevant information (energy-related information) to subscriber information.

[0233] Through the subscriber information update process of the prior art, updated subscriber information can be transmitted to the AMF and / or SMF. Through this process, energy-related information received from the AF can be transmitted to the control network nodes of the 5GC. Each control network node can then apply / enforce energy-specific policies based on this information.

[0234] Step 5. Independently (independently of steps 2-4), AF can request energy monitoring from NEF via AF request.

[0235] The above AF request may include the information in Table 3 described above in step 2 and information indicating that it is a green energy service.

[0236] Step 6. Information included in the AF request received from AF can be transmitted to PCF.

[0237] Information (energy-related information) included in the above AF request can be used to create PCC rules.

[0238] That is, based on AF requests, PCC rules can be generated. Based on these PCC rules, energy-related information can be monitored and energy-related policies can be enforced.

[0239] Step 7. As an independent step, subscriber information can be passed to PCF via UDM / UDR.

[0240] Step 8. PCF can create PCC rules for monitoring / processing / reporting appropriate energy-related information.

[0241] Based on the AF request, PCF can generate PCC rules.

[0242] Step 9. Based on the AF request, PCF can forward the generated PCC rules to the appropriate network nodes and / or NG-RAN, OAM, UE, etc.

[0243] Step 10. The network (core network or base station) or terminal can perform energy monitoring. Based on the collected / monitored information and AF requests, the information can be transmitted (or exposed) to AF.

[0244] When a terminal performs energy monitoring, the terminal can report the monitoring results to a network node (e.g., AMF, SMF) of the 5GC. The 5GC can then report the monitoring results to the AF.

[0245] Alternatively, if the terminal performs energy monitoring, the terminal can report the monitoring results directly to the AF outside the 5GC through the user plane to the application layer.

[0246] Although not described in the drawings of this embodiment, the NWDAF of 5GC may be involved in collecting / monitoring / processing information. This may be based on the unique characteristics of the NWDAF, namely, the analytic (statistics and prediction) nature of information.

[0247] Figure 9 shows a procedure diagram according to a first embodiment of the disclosure of the present specification.

[0248] Describes the case where the AF request message is provisioned with 5GC UDM / UDR subscriber information.

[0249] Step 1- step 4. The contents of step 1- step 4 described in Fig. 8 can be applied.

[0250] Step 5. The information added / updated in Step 4 can be transmitted to the base station, OAM, and / or terminal. During transmission, the information can be transmitted transparently or in a processed form.

[0251] According to the disclosure of this specification, energy-related policies can be applied based on the above information.

[0252] This specification does not specify specific messages. However, existing AS / NAS / N2 messages, etc., or newly defined message procedures, etc. may be utilized.

[0253] A base station (e.g., NG-RAN) can receive energy-related configurations that the base station can understand via AMF / SMF.

[0254] The energy-related configuration transmitted to the base station may be included in a QoS profile and transmitted to the base station. Alternatively, the energy-related configuration may be transmitted to the base station through a newly defined, separate profile (e.g., an energy profile).

[0255] The energy-related configuration transmitted to the base station may include parameters and thresholds (if not pre-configured in the base station) for energy consumption that the base station is to monitor / report.

[0256] According to the above energy-related configuration, the base station can monitor energy-related information according to the granularity that the base station can measure, such as by specific UE or UE group, by bearer, by QFI, etc.

[0257] The terminal can receive energy-related configuration via AMF / SMF.

[0258] The energy-related configuration transmitted to the terminal may be included in a QoS rule and transmitted to the terminal. Alternatively, the energy-related configuration may be transmitted to the terminal through a newly defined, separate rule (e.g., an energy rule).

[0259] The energy-related configuration transmitted to the terminal may include parameters and thresholds (if not pre-configured in the terminal) for energy consumption that the terminal should monitor / report.

[0260] According to the above energy-related configuration, the terminal can monitor energy-related information according to measurable granularity.

[0261] When a terminal performs energy monitoring, the terminal can report the monitoring results to a network node (e.g., AMF, SMF) of the 5GC. The 5GC can then report the monitoring results to the AF.

[0262] Alternatively, if the terminal performs energy monitoring, the terminal can report the monitoring results directly to the AF outside the 5GC through the user plane to the application layer.

[0263] A control network node (e.g., an SMF) can send energy-related configurations to the UPF using conventional N4 messages. Based on the received energy-related configurations, the UPF can monitor energy-related information at a measurable granularity.

[0264] Step 6. The network or terminal can perform energy monitoring. Based on the collected / monitored information and AF requests, the information can be transmitted (or exposed) to AF.

[0265] Although not described in the drawings of this embodiment, the NWDAF of 5GC may be involved in collecting / monitoring / processing information. This may be based on the unique characteristics of the NWDAF, namely, the analytic (statistics and prediction) nature of information.

[0266] Figure 10 shows a procedure diagram according to a second embodiment of the disclosure of the present specification.

[0267] Describes when an AF request message is passed to the 5GC PCF to update the PCC rules.

[0268] Step 1. The contents of step 1 described in Fig. 8 can be applied.

[0269] Step 2. AF can send an AF request to NEF requesting energy monitoring.

[0270] The above AF request may include energy related information.

[0271] Depending on the business prior agreement or business policy, the above AF request may be accepted by 5GC.

[0272] Energy-related information may include the information described in Table 3. Alternatively, the energy-related information may include a combination of the information described in Table 3. Energy-related information is not limited to the information described in Table 3.

[0273] Step 3. Information included in the AF request received from AF can be transmitted to PCF.

[0274] The information contained in the above AF request can be used to create PCC rules.

[0275] That is, based on AF requests, PCC rules can be generated. Based on these PCC rules, energy-related information can be monitored and energy-related policies can be enforced.

[0276] Step 4. PCF can optionally use subscriber information from UDM / UDR.

[0277] Step 5. PCF can create PCC rules for monitoring / processing / reporting appropriate energy-related information.

[0278] Based on the AF request (energy-related information included in the AF request), the PCF can generate PCC rules.

[0279] The generated PCC rule may include the information described in Table 4. Alternatively, the generated PCC rule may include a combination of the information described in Table 4. The information included in the generated PCC rule is not limited to the information described in Table 4.

[0280] Information nameDescriptionCategoryPCF permitted to modify for a dynamic PCC rule in the SMFDifferences compared with table 6.3. in TS 23.203 [4]Rule identifierUniquely identifies the PCC rule, within a PDU Session.It is used between PCF and SMF for referencing PCC rules.MandatoryNoNone...Energy MonitoringThis part describes PCC rule information related with Energy Monitoring.Energy Monitoring parameter(s)Indicates the Energy Monitoring parameter(s) for which Energy Monitoring can be enabled YesAddedReporting frequencyDefines the frequency for the reporting, such as event triggered, periodic. YesAddedTarget of reportingDefines the target of the Energy Monitoring reports, it can be the NEF, the AF or the Local NEF. YesAddedIndication of direct event notificationIndicates that the Energy Monitoring event shall be reported by the UPF directly to the NF indicated by the Target of reporting. YesAdded

[0281] The generated PCC rule may include energy monitoring information. The energy monitoring information may be a PCC rule related to energy monitoring.

[0282] The generated PCC rules may include energy monitoring parameter(s).

[0283] The energy monitoring parameter(s) may represent energy monitoring parameters that can enable energy monitoring.

[0284] The parameters received from AF can be used as the energy monitoring parameter(s). Alternatively, the parameters received from AF can be changed / processed into interpretable parameters in 5GC and used as the energy monitoring parameter(s).

[0285] For example, if a network receives a request for Energy grade 1, the energy monitoring parameter(s) may be added to the PCC rules according to preset conditions to monitor the amount of energy consumed per PDU session / per slice / per node. The preset conditions may be conditions regarding energy efficiency and energy consumption set according to regulations / agreements, etc. to meet the energy grade.

[0286] The generated PCC rule may include a reporting frequency. The reporting frequency may be event-triggered, periodic, or other reporting frequencies.

[0287] The generated PCC rule may include a reporting target. The reporting target may refer to the entity reporting energy monitoring. For example, the reporting target may be a NEF, AF, or local NEF. A network node (or base station or terminal) that receives a PCC rule containing a reporting target may report the results of energy monitoring to the reporting target.

[0288] The generated PCC rule may include an indication of direct event notification. A direct event notification may indicate that the UPF should report an energy monitoring event directly to the NF specified in the reporting target.

[0289] A network node (or base station or terminal) that has received a PCC rule that includes a target of direct event notification display and reporting can report the results of energy monitoring to the UPF, and the UPF can directly report to the target of the report.

[0290] A control network node (e.g., SMF) can send energy-related configurations to the UPF using conventional N4 messages. The energy-related configurations can include information included in the aforementioned PCC rules.

[0291] Based on the received energy-related configuration, UPF can monitor energy-related information at measurable granularity.

[0292] Step 6. Based on the AF request, PCF can forward the generated PCC rules to the appropriate network nodes and / or NG-RAN, OAM, UE, etc.

[0293] A base station (e.g., NG-RAN) can receive a profile that the base station can understand via (or through) the AMF / SMF. The profile may include the PCC rules described above. Alternatively, the profile may include information included in the PCC rules described above.

[0294] The above profile transmitted to the base station may be included in a QoS profile and transmitted to the base station. Alternatively, the profile may be transmitted to the base station through a newly defined, separate profile (e.g., an energy profile).

[0295] The above profile transmitted to the base station may include parameters and thresholds (if not pre-configured in the base station) for energy consumption that the base station should monitor / report.

[0296] According to the above profile, the base station can monitor energy-related information according to the granularity that the base station can measure, such as by specific UE or UE group, by bearer, by QFI, etc.

[0297] The terminal can receive a UE policy. The UE policy may include information included in the PCC rule described above.

[0298] Alternatively, the terminal may receive energy-related rules via SMF. The energy-related rules may include information included in the aforementioned PCC rules.

[0299] The energy-related rules transmitted to the terminal may be included in a QoS rule and transmitted to the terminal. Alternatively, the energy-related configuration may be transmitted to the terminal through a newly defined, separate rule (e.g., an energy rule).

[0300] The energy-related rules transmitted to the terminal may include parameters and thresholds (if not pre-configured in the terminal) for energy consumption that the terminal should monitor / report.

[0301] When a terminal receives a threshold for energy consumption, it can monitor whether its energy consumption exceeds the threshold. If energy consumption exceeds the threshold, the terminal can notify the network through user equipment (UE). This can trigger a process to terminate sessions associated with less important services or transition to a charging system that allows for higher energy consumption.

[0302] According to the above energy-related rules, the terminal can monitor energy-related information according to measurable granularity.

[0303] When a terminal performs energy monitoring, the terminal can report the monitoring results to a network node (e.g., AMF, SMF) of the 5GC. The 5GC can then report the monitoring results to the AF.

[0304] Alternatively, if the terminal performs energy monitoring, the terminal can report the monitoring results directly to the AF outside the 5GC through the user plane to the application layer.

[0305] Step 7. The network or terminal can perform energy monitoring. Based on the collected / monitored information and AF requests, the information can be transmitted (or exposed) to AF.

[0306] Although not described in the drawings of this embodiment, the NWDAF of 5GC may be involved in collecting / monitoring / processing information. This may be based on the unique characteristics of the NWDAF, namely, the analytic (statistics and prediction) nature of information.

[0307] A network node (e.g., AF) can send a request to the 5GC network to measure and utilize energy-related information, along with information indicating that it is a green service for energy efficiency.

[0308] A network node (e.g., PCF) can generate PCC rules based on energy-related information or monitoring requests received from the AF via the NEF, and trigger other network nodes, NF-RAN, and / or UEs in the 5GC to perform energy-related information monitoring. The PCF can receive and analyze monitoring results from other network nodes in the 5GC and report them to the AF.

[0309] Energy grade information exposure is described below.

[0310] Information about the energy-related characteristics of the network for communication services (e.g., energy consumption, energy supply mix, carbon footprint, energy capacity and availability conditions) may be disclosed to authorized users or authorized third parties.

[0311] Changes in the energy-related characteristics of this service may result in dynamic adjustments (including service performance adjustments) of the communication services provided from a 5G system perspective.

[0312] Dynamic adjustments can be based on criteria such as network decisions, user preferences, or agreement between an authorized third party and the network.

[0313] Energy ratings may be established between network operators and third-party service providers based on pre-defined profiles regarding energy consumption and / or energy efficiency when providing services to a UE or group of UEs.

[0314] Energy Class 1 could be, for example:

[0315] - NF energy consumption related to the service is [X]J; and / or,

[0316] - Energy efficiency related to network slice service is [X] bits / J and / or,

[0317] - The energy efficiency of the 5GC service is [X] bit / J

[0318] To receive government benefits such as tax breaks, third-party service providers may require 5G systems to maintain a certain level of "energy rating" when providing services to a UE or group of UEs, an agreement between the network operator and the third-party service provider based on a pre-established profile of energy consumption and / or energy efficiency.

[0319] Applications from third-party service providers can request energy rating levels from the 5G system. The 5G system can perform this monitoring based on application requests and pre-emptive defense profiles regarding energy consumption and / or energy efficiency. The 5G system can determine the energy rating level required to provide the service provider's service and notify the service provider or inform them whether the requested energy rating level can be met.

[0320] The application server may request the 5G system to maintain or adjust the energy rating level at a specific time and / or location.

[0321] Application A (e.g., AF) on a third-party service provider's application server can enter into a business agreement with operator B (e.g., core network) based on a preemptive defense profile for energy consumption and / or energy efficiency according to energy rating levels.

[0322] The service flow might look like this:

[0323] - i. When application A of a third-party service provider provides services to a UE or group of UEs, it may request that the network of operator B maintain a certain level of energy rating.

[0324] - ii. Operator B, which operates the network, can collect / monitor energy rating information for the service and determine whether the requested energy rating level can be met.

[0325] - iii. Operator B's network can provide the determined information to Application A.

[0326] - iv. Application A can use the information for its own management and additionally request an energy rating level adjustment from the network of operator B. That is, application A (e.g., AF) can request operator B to maintain an energy rating different from the energy rating requested by i.

[0327] The operator B receiving the above request may be a specific network node (e.g., PCF) of a specific core network.

[0328] Depending on the specific energy rating level desired by the Third Party Service Provider, the Third Party Service Provider may provide services to the UE(s) through Operator B's network.

[0329] Depending on the carrier's policies and agreements with third parties, the 5G system may expose energy rating information to authorized third parties for service purposes and may provide means to adjust energy rating levels.

[0330] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0331] Figure 11 illustrates the AF procedure for the disclosure of this specification.

[0332] 1. AF can send AF requests to the core network.

[0333] The above AF request may include energy-related information.

[0334] 2. AF can receive energy monitoring reports.

[0335] The above energy monitoring report may include the results of monitoring energy usage.

[0336] The above monitoring can be performed by the core network, base station or UE (User Equipment) based on the energy-related information.

[0337] The step of transmitting the AF request may be that the AF transmits the AF request to a Network Exposure Function (NEF) of the core network.

[0338] The above energy-related information may include at least one of granularity, start time, end time, energy efficiency limit, energy consumption limit, and energy rating limit for the above monitoring.

[0339] The above granularity may be information about the object of the above monitoring.

[0340] Based on the above monitoring being performed by the UE, the step of receiving the energy monitoring report may be one in which the AF receives it directly from the UE.

[0341] Based on the above monitoring being performed by the core network or the base station, the step of receiving the energy monitoring report may be received by the AF from the core network.

[0342] The energy-related information may include a request for the core network to maintain a specific rating for energy usage.

[0343] The above energy monitoring report may include information on whether the above specific rating can be met.

[0344] Based on the above energy monitoring report, the AF may send a request to the core network to maintain a grade other than the specific grade.

[0345] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0346] Figure 12 illustrates the PCF procedure for the disclosure of this specification.

[0347] 1. PCF can receive AF requests from AF (Application Function).

[0348] The above AF request may include energy-related information.

[0349] 2. PCF can generate PCC (Policy and Charging Control) rules based on the above energy-related information.

[0350] The above PCC rules may include information enabling monitoring of energy usage.

[0351] 3. PCF can transmit the generated PCC rule to other network nodes, base stations, or UE (User Equipment).

[0352] The step of receiving the above AF request may be that the PCF receives the AF request through the NEF (Network Exposure Function) of the core network.

[0353] The above energy-related information may include at least one of granularity, start time, end time, energy efficiency limit, energy consumption limit, and energy rating limit for the above monitoring.

[0354] The above PCC rules may include information about the reporting cycle for the above AF requests.

[0355] The above AF request may include a target NF (Network Function) that must report the results of the above monitoring.

[0356] The above AF request may include information indicating that the User Plane Function (UPF) should report the results of the above monitoring directly to the target NF.

[0357] The above NF may be the above AF.

[0358] The energy-related information may include a request for the core network to maintain a specific rating for energy usage.

[0359] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0360] Figure 13 illustrates the UE's procedure for disclosure of this specification.

[0361] 1. The UE can receive PCC (Policy and Charging Control) rules from PCF (Policy Control Function).

[0362] The above PCC rules may be based on a request from an Application Function (AF) containing energy-related information.

[0363] The above PCC rules may include information enabling monitoring of energy usage.

[0364] The UE can monitor energy usage based on the above PCC rules.

[0365] The UE can transmit the results of the above monitoring to a network node or the AF.

[0366] The above PCC rule may include at least one of a parameter and a threshold for energy usage.

[0367] Hereinafter, a device for performing communication according to some embodiments of the present specification will be described.

[0368] For example, a device may include a processor, a transceiver, and memory.

[0369] For example, a processor may be configured to be operatively coupled with memory and a processor.

[0370] The operations performed by the above processor include: receiving a PCC (Policy and Charging Control) rule from a PCF (Policy Control Function); wherein the PCC rule is based on a request from an AF (Application Function) including energy-related information, wherein the PCC rule includes information for performing monitoring of energy usage, and performing monitoring of energy usage based on the PCC rule; and wherein the result of the monitoring can be transmitted to a network node or the AF.

[0371] Below, a processor of a device for providing communication according to some embodiments of the present specification is described.

[0372] The operations performed by the above processor include: receiving a PCC (Policy and Charging Control) rule from a PCF (Policy Control Function); wherein the PCC rule is based on a request from an AF (Application Function) including energy-related information, wherein the PCC rule includes information for performing monitoring of energy usage, and performing monitoring of energy usage based on the PCC rule; and wherein the result of the monitoring can be transmitted to a network node or the AF.

[0373] Hereinafter, a non-volatile computer-readable medium storing one or more commands for providing mobile communication according to some embodiments of the present specification is described.

[0374] According to some embodiments of the present disclosure, the technical features of the present disclosure may be implemented directly in hardware, software executed by a processor, or a combination of the two. For example, a method performed by a wireless device in wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, the software may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or other storage media.

[0375] Some examples of storage media are coupled to the processor, allowing the processor to read information from the storage media. Alternatively, the storage media may be integrated into the processor. The processor and storage media may reside in an ASIC. In other examples, the processor and storage media may reside as separate components.

[0376] Computer-readable media may include tangible and non-volatile computer-readable storage media.

[0377] For example, nonvolatile computer-readable media may include random access memory (RAM), such as synchronized dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), read-only memory (EEPROM), flash memory, magnetic or optical data storage media, or any other media that can be used to store instructions or data structures. Nonvolatile computer-readable media may also include combinations of the above.

[0378] Additionally, the methods described herein can be realized at least in part by a computer-readable communication medium that carries or transmits code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer.

[0379] According to some embodiments of the present disclosure, a non-transitory computer-readable medium has one or more instructions stored thereon. The one or more stored instructions can be executed by a processor of a base station.

[0380] One or more stored commands include: a step of receiving a PCC (Policy and Charging Control) rule from a PCF (Policy Control Function); the PCC rule is based on a request from an AF (Application Function) including energy-related information, the PCC rule includes information for performing monitoring of energy usage, and the step of performing monitoring of energy usage based on the PCC rule; and the result of the monitoring can be transmitted to a network node or the AF.

[0381] This specification may have various effects.

[0382] For example, through the procedures disclosed herein, monitoring of energy consumption can be performed at the request of the AF and the results can be transmitted to the AF.

[0383] The effects that can be achieved through specific examples of this specification are not limited to the effects listed above. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0384] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.

Claims

1. As a method for AF (Application Function) to perform communication, A step of sending an AF request to the core network; The above AF request includes energy-related information, comprising a step of receiving an energy monitoring report; The above energy monitoring report includes the results of monitoring energy usage, A method in which the above monitoring is performed by the core network, base station or UE (User Equipment) based on the above energy-related information.

2. In paragraph 1, A method wherein the step of transmitting the AF request comprises transmitting the AF request to a Network Exposure Function (NEF) of the core network.

3. In paragraph 1 or 2, The energy-related information includes at least one of granularity, start time, end time, energy efficiency limit, energy consumption limit, and energy rating limit for the monitoring. The above granularity is information about the object of the above monitoring.

4. In any one of the clauses 1 to 3, A method wherein the step of receiving the energy monitoring report is based on the monitoring performed by the UE, and the step of receiving the energy monitoring report is performed directly by the UE.

5. In any one of paragraphs 1 to 3, A method wherein the step of receiving the energy monitoring report is based on the monitoring being performed by the core network or the base station, and the core network receives the energy monitoring report.

6. In any one of paragraphs 1 to 5, The above energy-related information includes a request for the core network to maintain a specific rating for energy usage, A method wherein the energy monitoring report includes information on whether the above specific rating can be met.

7. In paragraph 6, A method further comprising the step of transmitting a request to the core network to maintain a grade other than the specific grade based on the energy monitoring report.

8. As a method for PCF (Policy Control Function) to perform communication, A step of receiving an AF request from an AF (Application Function); The above AF request includes energy-related information, A step of generating a PCC (Policy and Charging Control) rule based on the above energy-related information; The above PCC rules include information to enable monitoring of energy usage, A method comprising the step of transmitting the generated PCC rule to another network node, base station or UE (User Equipment).

9. In paragraph 8, A method wherein the step of receiving the AF request is to receive the AF request through a Network Exposure Function (NEF) of the core network.

10. In paragraph 8 or 9, A method wherein the energy-related information includes at least one of granularity, start time, end time, energy efficiency limit, energy consumption limit, and energy rating limit for the monitoring.

11. In any one of the clauses 8 to 10, The above PCC rule includes information about the reporting cycle for the above AF request.

12. In any one of the clauses 8 to 11, A method wherein the AF request includes a target NF (Network Function) that must report the results of the monitoring.

13. In paragraph 12, A method wherein the AF request includes information indicating that the UPF (User Plane Function) should report the results of the monitoring directly to the target NF.

14. In paragraph 13, The above NF is the method of the above AF.

15. In any one of the clauses 8 to 14, A method wherein the energy-related information includes a request for the core network to maintain a specific rating for energy usage.

16. A method for UE (User Equipment) to perform communication, A step of receiving a PCC (Policy and Charging Control) rule from a PCF (Policy Control Function); The above PCC rules are based on requests from AF (Application Function) containing energy-related information, The above PCC rules include information to enable monitoring of energy usage, A step of monitoring energy usage based on the above PCC rules; A method comprising a step of transmitting the results of the above monitoring to a network node or the AF.

17. In paragraph 16, A method wherein the above PCC rule includes at least one of a parameter and a threshold for energy usage.

18. As an AF (Application Function) that performs communication, Transmitter and receiver; Contains a processor, The operation performed by the above processor is a UPF method according to any one of claims 1 to 7.

19. As a PCF (Policy Control Function) that performs communication, Transmitter and receiver; Contains a processor, The operation performed by the above processor is a PCF method according to any one of claims 8 to 15.

20. As a UE (User Equipment) performing communication, Transmitter and receiver; Contains a processor, The operation performed by the above processor is a UE according to claim 16 or 17.

Images