Method and device for managing energy policy in wireless communication system

The method and apparatus in wireless communication systems manage energy consumption by determining energy policies for PDU sessions, optimizing energy usage across network entities, thus addressing the challenge of energy management in high-frequency bands and supporting increased device connectivity.

WO2024237720A1PCT designated stage expired Publication Date: 2024-11-21SAMSUNG ELECTRONICS CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/006696
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-18
Filing Date
2024-05-17
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in managing energy consumption effectively, particularly in high-frequency bands, which affects transmission distance and reliability, and there is a need for efficient energy management as the number of connected devices increases.

Method used

A method and apparatus that utilize a policy control function (PCF) to monitor and control energy usage in wireless communication systems by determining an energy policy for packet data units (PDU) sessions, allowing for the allocation and adjustment of energy budgets across network entities such as UE, RAN, and UPF to optimize energy consumption.

Benefits of technology

This approach enables controlled energy consumption, ensuring that energy usage remains below maximum values, enhancing the efficiency and reliability of wireless communication systems, especially in scenarios with a large number of connected devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006696_21112024_PF_FP_ABST
    Figure KR2024006696_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. A method for processing a control signal in a wireless communication system, of the present disclosure, comprises the steps of: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting, to the base station, a second control signal generated on the basis of the processing.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for managing energy policy in a wireless communication system

[0001] The present disclosure relates to a wireless communication system or a mobile communication system. Specifically, it relates to a method and device for applying energy policy information in a wireless communication system.

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

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

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

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

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

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

[0008] The present disclosure proposes a method and device for applying a policy to control the energy consumption consumed for traffic transmission / reception in a wireless communication system or mobile communication system. The technical challenges addressed by the present disclosure are not limited to those mentioned above, and other technical challenges not mentioned will be readily apparent to those skilled in the art, based on the description below.

[0009] According to one embodiment of the present disclosure, a method performed by a policy control function (PCF) entity in a wireless communication system is characterized by the steps of: receiving a first message requesting policy information for a packet data unit (PDU) session from a session management function (SMF) entity; determining an energy policy associated with the PDU session; and transmitting a second message including the energy policy associated with the PDU session to the SMF entity.

[0010] In the wireless communication system proposed in this disclosure, the energy usage consumed for traffic transmission / reception can be controlled to below a maximum value by monitoring the energy usage consumed for traffic transmission / reception and controlling it according to a policy.

[0011] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0012] FIG. 1 illustrates the structure of a 5G system according to various embodiments of the present disclosure.

[0013] FIG. 2 illustrates a process in which a PCF determines an energy budget policy and provides energy budget information according to various embodiments of the present disclosure.

[0014] FIG. 3 illustrates a process in which a UE / RAN / UPF transmits an Energy report to a PCF or EBC (energy budget control) NF according to various embodiments of the present disclosure, and the PCF or EBC NF updates an Energy Policy or other policy based on the Energy report.

[0015] FIG. 4 illustrates the structure of a base station according to various embodiments of the present disclosure.

[0016] FIG. 5 illustrates the structure of a terminal according to various embodiments of the present disclosure.

[0017] FIG. 6 illustrates the structure of a network function (or network entity) according to various embodiments of the present disclosure.

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

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

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

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

[0022] FIG. 1 illustrates the structure of a 5G system according to various embodiments of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0038] - N14: Reference point between two AMFs

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

[0040] In 5G systems, network slicing technology refers to the technology and architecture that enables multiple virtualized, independent, logical networks within a single physical network. To meet the specialized requirements of services / applications, network operators configure virtual end-to-end networks called network slices to provide services. At this time, network slices are identified by an identifier called single-network slice selection assistance information (S-NSSAI). During the UE registration procedure (e.g., UE registration procedure), the network transmits a set of allowed slices (e.g., allowed NSSAI(s)) to the UE, and the UE transmits and receives application data through a PDU (protocol data unit) session created through one of these S-NSSAIs (i.e., network slices).

[0041] The mobile communication system receives identifier information and QoS (quality of service) requirements of terminals that can participate in federated learning from an external third-party server (application function, AF), and the mobile communication system selects terminals that can allocate network resources based on the requirements and allocates self-network resources (i.e., QoS Flows), and transmits the results to the AF. Among the terms used in the description of the present disclosure, aggregated QoS can be used and interpreted with the same meaning as same QoS, identical QoS, and group QoS. For example, aggregated QoS request indicator and same QoS request indicator, aggregated QoS information and same QoS information, and aggregated QoS notification indicator and same QoS notification indicator can be interpreted and used with the same meaning, respectively.

[0042] In the present disclosure, EBC NF(s) may be located in one of the following NFs: PCF, NWDAF, OAM, but is not limited thereto.

[0043] FIG. 2 illustrates a process in which a PCF determines an energy budget policy and provides energy budget information according to various embodiments of the present disclosure.

[0044] Referring to FIG. 2, in step 201, the UE may transmit a PDU session creation request for transmitting application traffic. The UE may transmit the PDU session establishment request to the network including the following information:

[0045] S-NSSAI (single network slice selection assistance information): The S-NSSAI of one of the allowed slices may be included.

[0046] UE Requested DNN: DNN (Data network name) may be included.

[0047] PDU Session ID: Indicates the PDU session identifier.

[0048] N1 SM container (PDU Session Establishment request): Information transmitted to the SMF, which may include a PDU session establishment request.

[0049] However, the information included is not limited to this.

[0050] In step 203, the AMF may include information contained in a message received from the UE via the RAN in a message to be transmitted to the SMF. The message may include information such as SUPI (an identifier for subscriber information of the UE), selected DNN, UE requested DNN, S-NSSAI(s), PDU Session ID, Request Type, N1 SM container (PDU Session Establishment Request), Access Type, and Energy budget request, but is not limited thereto.

[0051] AMF may include an Energy budget request based on AMF configuration information or information received from the UE.

[0052] In step 203, the AMF may send an SM Context Create request message to the SMF. At this time, the SM Context Create request message may include one or more of the information PDU Session ID, DNN, S-NSSAI, Access Type, and Energy Budget request received in step 201.

[0053] At step 205, the SMF may send a response message to the AMF in response to the SM Context Create request message received from the AMF.

[0054] In step 207, the SMF may transmit a Subscription info request message requesting Session Management Subscription data from the UDM. The Subscription info request message may include an indicator indicating the Session Management Subscription data, a DNN, an S-NSSAI of the HPLMN, a Serving PLMN ID, and a SUPI. Afterwards, when the UDM receives the Subscription info request message from the SMF, the UDM may include the Session Management Subscription data corresponding to the SUPI, DNN, S-NSSAI, and PLMN ID requested by the SMF in a Subscription info response message, which is a response message transmitted to the SMF. The UDM may obtain the corresponding information from the UDR.

[0055] In steps 209 and 211, the SMF may send a policy creation or update request message to the PCF to receive policy information for the PDU session. The message may include, but is not limited to, the following information:

[0056] -S-NSSAI: S-NSSAI received in step 203

[0057] -DNN: DNN received in step 203

[0058] -SUPI: SUPI received in step 203

[0059] - Energy budget request: May be included if the information was received in step 203.

[0060] In step 213, if the PCF receives a policy request message for a PDU session from the SMF in step 211, it may request policy information related to the session from the UDM or UDR. Subsequently, the PCF may receive policy information related to the session from the UDM or UDR. The policy information related to the session may include, but is not limited to, the following information:

[0061] ● Energy budget information:

[0062] - The total energy usage (e.g., maximum value) allowed for the UE to transmit and receive traffic may be included (i.e., UE Energy budget).

[0063] -RAN may include the total energy usage (e.g., maximum) allowed when transmitting and receiving traffic (i.e., RAN Energy budget).

[0064] -RAN and UPF may include the total energy usage allowed when transmitting and receiving traffic (i.e. Network Energy budget).

[0065] -The total energy usage allowed by the UE, RAN, and UPF when transmitting and receiving traffic for the application may be included (i.e., Total Energy budget).

[0066] ● UEs subject to energy control: Information indicating the UEs to which the energy budget is to be applied, which may include, for example, one or more of Group ID, a list of UE ID(s), and AF ID.

[0067] ● Application subject to energy control: Information indicating the target traffic to which the energy budget is to be applied (e.g., Application Service Provider (ASP) ID, App ID, server MAC address, or IP 3 tuples (i.e., server IP address, port number, protocol information) may be included).

[0068] ● Time information: The energy budget may include applicable time information. An indicator indicating whether to apply periodically may be included along with the time information. Alternatively, information in the form of a period (e.g., from 2023 / 3 / 10 to 2023 / 3 / 28) may be included.

[0069] ● Area information: May include information about the area to which the energy budget is applicable. Area information may consist of TAI(s), cell ID(s), and / or geographical location information.

[0070] In step 215, the PCF may determine to apply an energy policy to the PDU session (or to specific traffic within the PDU session) if the information received in step 213 includes energy budget or energy profile information, or if the information received in step 211 includes energy budget request information, or based on its own configuration information. If the PCF determines to apply an energy policy based on the information received in step 213, it may compare the SUPI and UE location included in the information received from the SMF in step 211 with the UEs subject to energy control and area information received in step 213 to determine whether to apply the energy policy.

[0071] When the PCF decides to apply an energy policy, it may request the EBC NF to determine energy policy information.

[0072] Specifically, the PCF may transmit to the EBC NF one or more of the application subject to energy control, UEs subject to energy control, and Area information received in step 213 along with energy budget information.

[0073] Additionally, the PCF may include one or more of an energy profile mapping request indicator and an energy budget information conversion request indicator in the message transmitted to the EBC NF.

[0074] In step 215, the EBC NF may determine an energy policy based on a message received from the PCF, and when a message is received from the PCF, the EBC NF may convert the energy budget information included in the message received from the PCF into an energy budget for a smaller entity unit (e.g., an energy budget for a UPF, a UE, or a RAN). At this time, the EBC NF may utilize one or more of the other information included in step 215. In addition, the conversion may be performed when the information received in step 215 includes an energy budget information conversion request indicator, or may be performed at the discretion of the EBC NF even if the indicator is not included.

[0075] For example, if the information received in step 215 includes a Network Energy Budget (or Network Energy Budget for application), it can be converted into a RAN Energy Budget (or RAN Energy Budget for application) or a UPF Energy Budget (or UPF Energy Budget for application).

[0076] Alternatively, for example, if the information received in step 215 includes Total Energy budget (for application), it can be converted into UE Energy budget (or UE Energy budget for application), RAN Energy Budget (or RAN Energy Budget for application), and UPF Energy Budget (or UPF Energy Budget for application).

[0077] For this conversion, the EBC NF can utilize statistical information representing the energy consumed by the UE (or the UE for the application) during a certain period of time when transmitting and receiving traffic, statistical information representing the energy consumed by the RAN (or the RAN for the application) during a certain period of time when transmitting and receiving traffic, and statistical information representing the energy consumed by the UPF (or the UPF for the application) during a certain period of time when transmitting and receiving traffic.

[0078] EBC NF can calculate the allowable energy budget(s) in the network based on the information contained in the energy budget information received in step 215 (or the information in a converted form) for each entity.

[0079] Meanwhile, EBC NF can map the allowable entity-specific energy budget to Energy Profile(s). At this time, EBC NF can utilize one or more of the other information included in step 215. This can be performed if the information received in step 215 includes an energy profile mapping request indicator, or can be performed at EBC NF's discretion even if the indicator is not included.

[0080] A set of Energy Profiles represents a set of intervals of energy consumption used by an entity (e.g., UE, RAN, UPF, network (i.e., RAN and UPF), or entire entity (i.e., UE, RAN, UPF)) when transmitting and receiving traffic, and each Energy profile can be expressed as a minimum energy consumption and a maximum energy consumption. The unit of energy consumption can be Joule (or Watt).

[0081] An entity can be configured with one of the Energy profiles included in the Set of Energy profiles, and if configured, can adjust its energy consumption according to that Energy profile. There may also be an Energy profile indicating that the device is powered off for transmitting and receiving traffic.

[0082] For example, Energy profile 1 can be expressed in the form of 0.5 to 1.0 kilo Joule (or kilo Watt), Energy profile 2 can be expressed in the form of 1.0 to 1.5 kilo Joule (or kilo Watt), etc. In the example, an entity set to Energy profile 1 can control energy consumption between 0.5 to 1.0 kilo Joule (or kilo Watt) when transmitting and receiving traffic.

[0083] For example, when deriving UPF Energy Profile(s) for a UPF Energy budget, EBC NF can include nearby Energy Profiles in the UPF Energy Profile(s) along with Energy Profiles that represent the intervals that include the energy usage included in the UPF Energy budget.

[0084] A set of Energy Profiles may be stored in the EBC NF independently for each UE, RAN, UPF, network (i.e., RAN and UPF), and overall (i.e., UE, RAN, UPF).

[0085] An Energy Profile for a specific entity can be set for all traffic transmitted by the entity or for specific traffic (e.g., traffic for a specific application).

[0086] EBC NF can obtain and store the Set of Energy Profile for each entity through OAM (not shown) or NWDAF (network data analytics function) (not shown) at a point in time prior to receiving the message of step 215.

[0087] EBC NF may include the following information in the response message sent to PCF:

[0088] - candidate energy budget(s): Candidate energy budget(s): Can contain a set of per-entity allowed energy budgets for one or more entities.

[0089] - Energy Profile(s): One or more entities may contain per-entity allowed Energy profile(s).

[0090] - result: May contain the processing result (e.g., success or failure) for energy budget conversion and / or energy profile mapping. If failure is indicated, information indicating the cause of failure may be included.

[0091] In step 217, the PCF may determine an Energy Policy based on the candidate energy budget(s) and / or Energy Profile(s) if the message received from the EBC NF in step 215 includes the candidate energy budget(s).

[0092] The determined Energy Policy can be in the form of a candidate energy budget or Energy Profile for each entity.

[0093] PCF can generate PCC rule(s) and include them in a message sent to SMF. In step 219, the message sent by PCF to SMF can include the following information:

[0094] - PCC rule id

[0095] - service data flow (SDF) template (which may include, for example, IP filter information representing traffic)

[0096] - 5G QoS Identifier (5QI) (e.g. authorized 5QI for SDF)

[0097] - Energy Policy: The energy policy determined in step 217 may be included. The energy policy may be included in the PCC rule and transmitted.

[0098] - Energy Notification: This can be included if an Energy Policy requires notification for entities (e.g., UE, RAN, UPF) to which an energy budget or energy profile should be applied. Energy Notification can be configured for each entity. Energy Notification can be transmitted by being included in a PCC rule.

[0099] At step 221, the SMF may select a UPF based on the S-NSSAI and DNN for the PDU session.

[0100] At step 223, the SMF may send an N4 message to the UPF based on the PCC rule. This information may include the following:

[0101] - UPF Energy Profile and / or UPF Energy Budget: If the message received in step 219 includes an Energy Profile for UPF, that information may be included. Alternatively, if the message received in step 219 includes an Energy Budget for UPF, that information may be included.

[0102] - N4 session ID: N4 session identifier may be included:

[0103] - S-NSSAI, DNN

[0104] - application descriptor: Information indicating the target traffic to which the UPF Energy Profile and / or UPF Energy Budget will be applied (e.g., Application Service Provider (ASP) ID, App ID, server MAC address, or IP 3 tuples (i.e., server IP address, port number, protocol information) may be included).

[0105] - N4 rule: May include packet processing rules created based on PCC rules.

[0106] - Energy Notification Endpoint: If the PCC rule includes UPF Energy notification, this can include an address to receive energy usage notifications from UPF. This address can be the address of the PCF or the address of the EBC NF.

[0107] When the UPF receives a UPF Energy Profile and / or a UPF Energy Budget, the UPF monitors the amount of energy used for transmitting and receiving traffic for the corresponding PDU session (or, when an application descriptor is received, for transmitting and receiving traffic corresponding to the application descriptor in the PDU session) and adjusts the energy usage in consideration of the UPF Energy Profile and / or the UPF Energy Budget. If the usage is close to or reaches the maximum value included in the received UPF Energy Profile and / or UPF Energy Budget, this can be notified to the PCF or EBC NF.

[0108] UPF can periodically send energy usage information to an Energy Notification Endpoint address if the received message contains that address.

[0109] Afterwards, the UPF can send an N4 response message to the SMF. The N4 response message can include CN tunnel information for the PDU session.

[0110] At step 225, the SMF may include the following information in the message it transmits to the AMF. Here, N2 SM information represents information transmitted to the RAN, and N1 SM Container represents information transmitted to the UE:

[0111] PDU Session ID: Contains the PDU session identifier.

[0112] N2 message (PDU Session ID, QFI(s) (i.e. QoS Flow identifier), QoS Profile(s) (information including requirements of QoS Flow), CN Tunnel Info (e.g., address to which RAN will transmit data plane data received from UE for PDU session), S-NSSAI from the Allowed NSSAI, Session-AMBR (aggregate maximum bit rate) (maximum bit rate agreement for session), RAN Energy Profile, RAN Energy Budget (set based on Energy Policy received from PCF in step 219), Energy Notification Endpoint (if PCC rule includes Energy notification for RAN, it may include an address to receive energy usage notification from RAN. The address may include the address of PCF or the address of EBC NF.)

[0113] N1 message (PDU Session Establishment Accept): The PDU session establishment accept message includes QoS rule, DNN, S-NSSAI, and UE Energy Profile, UE Energy Budget (based on the Energy Policy received from the PCF in step 219), Energy Notification Endpoint (if the PCC rule includes Energy notification for the UE, it may include an address to receive energy usage notifications from the UE. The address may include the address of the PCF or the address of the EBC NF).

[0114] In step 227, the N1 message received from the SMF may be included in the N2 message received from the SMF. The AMF may transmit the information included in the N2 message to the RAN.

[0115] When the RAN receives a RAN Energy Profile and / or a RAN Energy Budget, the RAN monitors the amount of energy used for transmitting and receiving traffic for the corresponding PDU session (or, when an application descriptor is received, for transmitting and receiving traffic corresponding to the application descriptor within the PDU session) and adjusts the energy usage based on the RAN Energy Profile and / or the RAN Energy Budget. If the usage is close to or reaches the maximum value included in the received RAN Energy Profile and / or RAN Energy Budget, this can be notified to the PCF or EBC NF.

[0116] RAN can periodically transmit energy usage to an Energy Notification Endpoint address if the received message contains that address.

[0117] At step 229, the RAN may forward the information contained in the N1 message included in the N2 message received from the AMF to the UE.

[0118] If the UE also receives the UE Energy Profile and / or UE Energy Budget, it may behave in the same manner as if the RAN received the RAN Energy Profile and / or RAN Energy Budget.

[0119] At step 231, the remaining PDU session creation procedure may be performed.

[0120] FIG. 3 illustrates a process in which a UE / RAN / UPF transmits an Energy report to a PCF or EBC NF according to various embodiments of the present disclosure, and the PCF or EBC NF updates an Energy Policy or other policy based on the Energy report.

[0121] Referring to FIG. 3, at step 301, the RAN may transmit a message to the AMF to notify the PCF or EBC NF of energy usage or energy usage warning via the AMF. The message may include the following information:

[0122] - PDU Session ID: May contain a PDU session identifier.

[0123] - application descriptor: may contain information indicating application traffic (IP-tuple, etc.).

[0124] - RAN Energy Warning information: RAN may include information indicating a warning when the amount of energy used for transmitting or receiving traffic for a PDU session that is the target of Energy Policy (or transmitting or receiving traffic corresponding to an application descriptor within a PDU session) does not satisfy the configured RAN Energy Profile (or the received RAN Energy Budget) (e.g., when more energy is expected to be used for transmitting or receiving the traffic or when all energy has already been used).

[0125] - RAN Energy Usage: This may include the amount of energy used for transmitting and receiving traffic for a PDU session (or transmitting and receiving traffic corresponding to an application descriptor within a PDU session). This information may be included when the RAN receives an Energy Notification Endpoint from the AMF.

[0126] In step 303, the AMF may transmit the information received in step 301 to the SMF. The message may include the SM context ID for the PDU session ID received in step 301.

[0127] At step 305, the SMF may send a response message to the AMF.

[0128] In step 307, the SMF may forward the message received in step 303 to the PCF. The message may include a Policy Association ID.

[0129] In step 309, if the RAN supports direct reporting to the PCF, the RAN may send a message to the PCF to notify the PCF or EBC NF of energy usage or energy usage warning. The message may contain the same information as the information the RAN sent to the AMF in step 301.

[0130] At step 311, the UPF may send a message to the SMF to notify the PCF or EBC NF of energy usage or an energy usage warning via the SMF. The message may include the following information:

[0131] - PDU Session ID or N4 session: PDU session identifier (or N4 session identifier) ​​may be included.

[0132] - application descriptor: may contain information indicating application traffic (IP-tuple, etc.).

[0133] - UPF Energy Warning information: UPF may include information indicating a warning when the amount of energy used for transmitting or receiving traffic for a PDU session that is the target of the Energy Policy (or transmitting or receiving traffic corresponding to the application descriptor within the PDU session) does not satisfy the configured UPF Energy Profile (or the received UPF Energy Budget) (for example, when more energy is expected to be used for transmitting or receiving the traffic or when all energy has already been used).

[0134] - UPF Energy Usage: May contain the amount of energy used to transmit and receive traffic for a PDU session (or to transmit and receive traffic corresponding to an application descriptor within a PDU session). This information may be included when the UPF receives an Energy Notification Endpoint.

[0135] In step 313, the SMF may include the information received from the UPF in a message to be transmitted to the PCF. This may include a Policy Association ID for the PDU Session ID.

[0136] In step 315, if the UPF supports direct reporting to the PCF, the UPF may send a message to the PCF to notify the PCF or EBC NF of energy usage or energy usage warning. The message may contain the same information as the information sent by the UPF to the SMF in step 311.

[0137] In step 317, if the PCF receives a message in step 307, step 309, step 313, or step 315, and if the message includes entity-specific Energy Usage information (e.g., RAN or UPF), it may internally update the entity-specific Energy Usage information corresponding to the corresponding PDU session or the application description within the corresponding PDU session.

[0138] Meanwhile, if the EBC NF manages entity-specific Energy Usage information, the PCF can include Energy Usage information for the entity (e.g., RAN or UPF) in the message it transmits to the EBC NF.

[0139] If the PCF receives a message in step 307, step 309, step 313, or step 315, and if the message contains Energy Warning information for an entity (e.g., RAN or UPF), the PCF may decide to update the Energy Policy or update another policy (e.g., update QoS parameters). If it decides to update the Energy Policy, it may send a message requesting the Energy Policy to the EBC NF. The message may contain Energy Warning information for the entity (e.g., RAN or UPF).

[0140] In step 319, if the message received from the PCF includes information indicating a PDU Session and application description (e.g., PDU session ID and IP tuples) along with Energy Usage information for an entity (e.g., RAN or UPF), the EBC NF may update and then store the stored energy usage for the PDU session of the entity.

[0141] The EBC NF can re-determine the energy policy for a Session if the message received from the PCF contains information indicating the PDU Session and application description (e.g., PDU session ID and IP tuples), along with Energy Usage information for the entity (e.g., RAN or UPF), and Energy Warning information for the entity (e.g., RAN or UPF).

[0142] EBC NF can also re-determine the Energy Profile for other entities when it receives Energy Warning information for one entity (e.g., UPF).

[0143] EBC NF can recalculate entity-specific Energy Profile(s) and / or entity-specific Energy Budget(s) and include them in the response message sent to PCF.

[0144] In step 321, the PCF may re-determine the Energy policy by considering the information received in step 307, the information received in step 309, the information received in step 313, or the information received in step 315. If entity-specific Energy Profile(s) and / or entity-specific Energy Budget(s) are received from the EBC NF in step 319, the PCF may utilize the information to determine the entity-specific Energy Profile and / or entity-specific Energy Budget.

[0145] In step 323, if the Energy Policy and / or other Policies (e.g., UL / DL Session AMBR, and other QoS parameters, etc.) for the PDU session ID and the application description within the corresponding PDU session are updated, the PCF transmits the updated PCC rule to the SMF, and the SMF may transmit new Energy Profile (or Energy Budget) and / or QoS information (QoS rule for UE, QoS Profile, Session AMBR for RAN, N4 rule, Session AMBR for UPF, etc.) to the UPF, RAN, and / or UE in the same manner as steps 219 to 229 of FIG. 2.

[0146] At step 325, the remaining PDU session modification procedures can be performed.

[0147] FIG. 4 illustrates the structure of a base station according to various embodiments of the present disclosure.

[0148] Referring to FIG. 4, the base station may include a transceiver (410), a control unit (420), and a storage unit (430). The transceiver (410), the control unit (420), and the storage unit (430) may operate according to the communication method of the base station described above. The network device may also correspond to the structure of the base station. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. For example, the base station may include a transceiver (410) and a control unit (420). In addition, the transceiver (410), the control unit (420), and the storage unit (430) may be implemented in the form of a single chip.

[0149] The transceiver (410) is a general term for the receiving unit and the transmitting unit of the base station, and can transmit and receive signals with terminals, other base stations, or other network devices. At this time, the transmitted and received signals may include control information and data. The transceiver (410) may, for example, transmit system information to the terminal, and transmit a synchronization signal or a reference signal. To this end, the transceiver (410) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-down-converts a received signal. However, this is only one embodiment of the transceiver (410), and the components of the transceiver (410) are not limited to the RF transmitter and RF receiver. The transceiver (410) may include wired and wireless transceivers, and may include various configurations for transmitting and receiving signals. In addition, the transceiver (410) can receive a signal through a communication channel (e.g., a wireless channel) and output it to the control unit (420), and transmit the signal output from the control unit (420) through the communication channel. In addition, the transceiver (410) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a terminal, another base station, or another entity through a wired or wireless network.

[0150] The storage unit (430) can store programs and data required for the operation of the base station. In addition, the storage unit (430) can store control information or data included in signals acquired from the base station. The storage unit (430) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, the storage unit (430) can store at least one of information transmitted and received through the transceiver unit (410) and information generated through the control unit (420).

[0151] In the present disclosure, the control unit (420) may be defined as a circuit or application-specific integrated circuit, or at least one processor. The processor may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. The control unit (420) may control the overall operation of the base station according to the embodiment proposed in the present disclosure. For example, the control unit (420) may control the signal flow between each block to perform operations according to the flowchart described above.

[0152] FIG. 5 illustrates the structure of a terminal according to various embodiments of the present disclosure.

[0153] Referring to FIG. 5, the terminal may include a transceiver (510), a control unit (520), and a storage unit (530). The transceiver (510), the control unit (520), and the storage unit (530) may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. For example, the terminal may include a transceiver (510) and a control unit (520). In addition, the transceiver (510), the control unit (520), and the storage unit (530) may be implemented in the form of a single chip.

[0154] The transceiver (510) is a general term for the receiving unit and the transmitting unit of the terminal, and can transmit and receive signals with a base station, another terminal, or a network entity. The signals transmitted and received with the base station may include control information and data. The transceiver (510) may, for example, receive system information from the base station and may receive a synchronization signal or a reference signal. To this end, the transceiver (510) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-downconverts the received signal. However, this is only one embodiment of the transceiver (510), and the components of the transceiver (510) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (510) may include wired and wireless transceivers, and may include various configurations for transmitting and receiving signals. In addition, the transceiver (510) can receive a signal through a wireless channel and output it to the control unit (520), and transmit the signal output from the control unit (520) through the wireless channel. In addition, the transceiver (510) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a network entity through a wired or wireless network.

[0155] The storage unit (530) can store programs and data necessary for the operation of the terminal. In addition, the memory (530) can store control information or data included in signals obtained from the terminal. The storage unit (530) can be configured as a storage medium such as a ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0156] In the present disclosure, the control unit (520) may be defined as a circuit or application-specific integrated circuit, or at least one processor. The processor may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. The control unit (520) may control the overall operation of the terminal according to the embodiment proposed in the present disclosure. For example, the control unit (520) may control the signal flow between each block to perform operations according to the flowchart described above.

[0157] FIG. 6 illustrates the structure of a network function (or network entity) according to various embodiments of the present disclosure. The network function (or network entity) illustrated in FIG. 6 may correspond to various functions or entities of the core network described above in FIGS. 1 to 3.

[0158] As illustrated in FIG. 6, the network function (NF) (or network entity) of the present disclosure may include a transceiver (610), a memory (620), and an NF control unit (or processor, 630). The NF control unit (630), the transceiver (610), and the memory (620) of the network function (or network entity) may operate according to the communication method of the network function (or network entity) described above. However, the components of the network function (or network entity) are not limited to the examples described above. For example, the network function (or network entity) may include more or fewer components than the components described above.

[0159] The transceiver (610) is a general term for the receiving unit of a network function (or network entity) and the transmitting unit of a base station, and can transmit and receive signals with a terminal, a base station, and / or other network functions (or network entities). At this time, the transmitted and received signals may include control information and data. For this purpose, the transceiver (610) can communicate with nodes or base stations of the core network through a wired or wireless transceiver. However, this is only one embodiment of the transceiver (610), and the components of the transceiver (610) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, an RF receiver that low-noise amplifies a received signal and down-converts the frequency, and may include various configurations for transmitting and receiving signals.

[0160] In addition, the transceiver (610) can receive a signal through a communication channel (e.g., a wireless channel or a channel of a core network) and output it to the NF control unit (630), and transmit the signal output from the NF control unit (630) through the communication channel. In addition, the transceiver (610) can receive a communication signal and output it to the NF control unit (630), and transmit the signal output from the NF control unit (630) to a terminal, a base station, or a network entity through a wired or wireless network.

[0161] The memory (620) can store programs and data required for the operation of a network function (or network entity). In addition, the memory (620) can store control information or data included in signals obtained from the network function (or network entity). The memory (620) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD.

[0162] The NF control unit (630) may control a series of processes so that a network function (or network entity) can operate according to the embodiments of the present disclosure described above. The NF control unit (630) may include at least one processor. The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

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

[0164] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present invention.

[0165] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

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

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

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

Claims

1. A method performed by a PCF (policy control function) entity in a wireless communication system, A step of receiving a first message requesting policy information for a PDU (packet data unit) session from an SMF (session management function) entity; A step of determining an energy policy related to the above PDU session; and A method comprising the step of transmitting a second message including an energy policy associated with the PDU session to the SMF entity.

2. In claim 1, A method wherein the second message includes information related to a policy and charging control (PCC) rule ID, quality of service (QoS), and energy budget.

3. In claim 1, the method comprises: A step of transmitting a third message requesting information related to an energy policy based on the first message to a UDR (unified data repository) entity; and A step of receiving a fourth message including information associated with the energy policy from the UDR entity, A method wherein information related to the energy policy includes energy budget information and information on a target to which the energy policy is to be applied.

4. In claim 3, the method comprises: A step of transmitting a fifth message including a conversion indicator for energy budget information to an EBC (energy budget control) NF (network function) entity; and Further comprising the step of receiving a sixth message from the EBC NF entity, wherein the sixth message includes at least one entity-specific allowed energy budget information; A method wherein the second message comprises at least one entity-specific allowed energy budget information.

5. A method performed by an SMF (session management function) entity in a wireless communication system, A step of transmitting a first message requesting policy information for a PDU (packet data unit) session to a PCF (policy control function) entity; and A method comprising the step of receiving a second message from the PCF entity, the second message including an energy policy associated with the PDU session.

6. In claim 5, A method wherein the second message includes information related to a policy and charging control (PCC) rule ID, quality of service (QoS), and energy budget.

7. In claim 5, the method comprises: A method further comprising the step of transmitting a third message including energy budget information related to the UPF entity based on the second message to the UPF (user plane function) entity.

8. In claim 5, the method comprises: A method further comprising the step of transmitting, to the AMF entity, a fourth message including energy budget information related to a base station and energy budget information related to a terminal based on the second message.

9. In a wireless communication system, in the PCF (policy control function) entity, transceiver; and A controller coupled with the above transmitter and receiver is included, The above controller, Receives a first message requesting policy information for a PDU (packet data unit) session from an SMF (session management function) entity, Determine the energy policy related to the above PDU session, A PCF entity configured to transmit a second message containing an energy policy associated with the PDU session to the SMF entity.

10. In claim 9, The second message is a PCF entity that includes information related to PCC (policy and charging control) rule ID, QoS (quality of service), and energy budget.

11. In claim 9, the controller, Send a third message to the UDR (unified data repository) entity requesting information related to energy policy based on the first message, Further configured to receive a fourth message from the UDR entity, the fourth message including information associated with the energy policy; Information related to the above energy policy is a PCF entity including energy budget information and information on the target to which the above energy policy is to be applied.

12. In claim 11, the controller, Transmits a fifth message containing a conversion indicator for energy budget information to the EBC (energy budget control) NF (network function) entity, is configured to receive a sixth message from the EBC NF entity, the sixth message including at least one entity-specific allowed energy budget information; The second message comprises information about the allowed energy budget for at least one entity, the PCF entity.

13. In a wireless communication system, in the SMF (session management function) entity, transceiver; and A controller coupled with the above transmitter and receiver is included, The above controller, Send a first message to the PCF (policy control function) entity requesting policy information for a PDU (packet data unit) session, An SMF entity configured to receive a second message from the PCF entity, the second message including an energy policy associated with the PDU session.

14. In claim 13, The second message is an SMF entity that includes information related to PCC (policy and charging control) rule ID, QoS (quality of service), and energy budget.

15. In claim 13, the controller, Transmitting a third message including energy budget information related to the UPF entity based on the second message to the UPF (user plane function) entity, An SMF entity further configured to transmit, to the AMF entity, a fourth message including energy budget information related to a base station and energy budget information related to a terminal based on the second message.

Citation Information

Patent Citations

  • Data transmission method and device, computer readable medium and electronic equipment

    CN112787945A

  • Method and Apparatus for Establishing Guaranteed Bit Rate (GBR) Quality of Service (QoS) Flow in Session

    US20210076252A1

  • KR20230020870A