Method and apparatus for providing energy allowance information in wireless communication system
The method of negotiating energy policies between NEF and PCF entities in 5G systems addresses the challenge of managing energy consumption across RAN and UPF entities, optimizing energy usage and improving system performance.
Patent Information
- Application Number
- PCT/KR2024/006667
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-18
- Filing Date
- 2024-05-16
- Publication Date
- 2024-11-21
AI Technical Summary
Current 5G mobile communication systems face challenges in managing energy consumption effectively across radio access networks and user plane functions, particularly in supporting the increasing demand for data transmission and reception with varying energy requirements.
A method and apparatus that utilize a network exposure function (NEF) entity to negotiate energy policies with a policy control function (PCF) entity, receiving and transmitting information about the maximum allowable energy consumption of radio access network (RAN) or user plane function (UPF) entities, allowing for dynamic energy budget management and optimization.
This approach enables efficient energy usage management, limiting maximum energy consumption and optimizing energy allocation for data transmission and reception, thereby enhancing the performance and sustainability of 5G mobile communication systems.
Smart Images

Figure KR2024006667_21112024_PF_FP_ABST
Abstract
Description
Method and device for providing energy allowance information in a wireless communication system
[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for providing energy allowance 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] According to one embodiment of the present disclosure, a device and method for effectively providing a service in a mobile communication system are provided.
[0009] According to one embodiment, a method performed by a network exposure function (NEF) entity in a mobile communication system comprises the steps of: receiving, from an application function (AF) entity, a message requesting negotiation of at least one policy associated with energy, the message including information on a maximum allowable energy consumption of at least one of a radio access network (RAN) or a user plane function (UPF) entity; transmitting, to a policy control function (PCF) entity, a first message including the information on the maximum allowable energy consumption; and receiving, from the PCF entity, a second message in response to the first message, the second message including information on the at least one policy associated with energy, wherein the at least one policy associated with energy can be based on the information on the maximum allowable energy consumption.
[0010] According to one embodiment of the present disclosure, a device and method for effectively providing a service in a wireless communication system can be provided.
[0011] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.
[0012] Figure 1 illustrates a 5G system architecture according to one embodiment.
[0013] Figure 2 illustrates a method by which an AF negotiates an energy budget with a 5G core network according to one embodiment.
[0014] Figure 3 illustrates how AF applies the Energy Policy negotiated with the 5G core network.
[0015] FIG. 4 illustrates an example of a functional structure of a base station according to an embodiment of the present disclosure.
[0016] FIG. 5 illustrates an example of a functional structure of a terminal according to an embodiment of the present disclosure.
[0017] FIG. 6 illustrates an example of a functional structure of a core network object according to one embodiment of the present disclosure.
[0018] The operating principles of the present disclosure are described in detail with reference to the attached drawings. The terms described below are defined based on the functions described in the present disclosure. Since the terms described in the present disclosure may vary depending on the intent or custom of the user or operator, their definitions should be determined based on the overall content of the present disclosure.
[0019] The terms used in this disclosure to refer to network entities or network functions, terms used to refer to messages, terms used to refer to identification information, and the like are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms used to refer to objects with equivalent technical meanings may be used.
[0020] For convenience, the present invention uses terms and names defined in the 5G system standards, but is not limited by the terms and names, and can be equally applied to systems conforming to other standards.
[0021] The operating principle of the present invention is described in detail with reference to the attached drawings below.
[0022] In describing embodiments of the present disclosure, 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 may be omitted. This is to ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.
[0023] 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 may be assigned the same reference number.
[0024] 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 present disclosure is complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined solely by the scope of the claims. Like reference numerals designate like elements throughout the specification.
[0025] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. Since these computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, a means for performing the functions described in the flowchart block(s) can be created by the instructions executed through the processor of the computer or other programmable data processing equipment. Since these computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the function in a specific manner, the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).
[0026] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.
[0027] Here, the term '~ unit' used in this embodiment means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to regenerate one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in the embodiment, '~bu' may include one or more processors.
[0028] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.
[0029] For convenience of explanation, this disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP) LTE (3rd Generation Partnership Project Long Term Evolution) standards and the 3GPP 5G standards. However, the present invention is not limited by these terms and names and can be equally applied to systems conforming to other standards.
[0030] 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, the attached drawings of the present disclosure are provided to aid understanding of the present disclosure, and it should be noted that the present invention is not limited to the forms or arrangements illustrated in the drawings.
[0031] In this disclosure, we propose a method for an application service provider to provide energy usage consumed for transmitting / receiving traffic to a 5G network.
[0032] This disclosure proposes a method for an application service provider to provide the energy usage consumed for traffic transmission and reception to a 5G network. Specifically, it proposes a method for storing the energy usage provided by the application service provider in a form acceptable to the network.
[0033] This disclosure allows for limiting the maximum energy usage used when transmitting and receiving data to an application service provider. Furthermore, the present invention allows for the network to store the energy usage allowed for data transmission and reception for specific traffic.
[0034] The present disclosure proposes a method and device for providing energy allowance information in a wireless communication system.
[0035] Figure 1 illustrates a 5G system architecture according to one embodiment.
[0036] Referring to FIG. 1, a mobile communication network (e.g., a 5G mobile communication network) according to an embodiment may be composed of a 5G user equipment (UE, terminal), a 5G radio access network (RAN, base station), a next generation nodeB (gNB), an evolved nodeB (eNB, etc.), and a 5G core network. For example, the 5G core network may include network functions (NFs) such as an access and mobility management function (AMF) (120) that provides a mobility management function of the UE, a session management function (SMF) (135) that provides a session management function, a user plane function (UPF) (130) that performs a data transfer role, a policy control function (PCF) (140) that provides a policy control function, and / or a unified data repository (UDR) that stores data of various network functions (NFs), such as a unified data management (UDM) (145) that provides a data management function such as subscriber data and policy control data.
[0037] The network structure of a 5G system according to one embodiment may include various network entities. For example, the 5G system may include an authentication server function (AUSF) (not shown), an access and mobility management function (AMF) (120), a session management function (SMF) (135), a policy control function (PCF) (140), an application function (AF) (170), a unified data management (UDM) (145), a data network (DN) (175), a network exposure function (NEF) (not shown), a network slicing selection function (NSSF) (160), an edge application service domain repository (EDR) (not shown), an edge application server (EAS, not shown), an EAS discovery function (EASDF, not shown), and a network data analytics function (NWDAF, (not shown), a user plane function (UPF) (130), a (radio) access network ((R)AN) (110), and a terminal, i.e., a user equipment (UE) (100).
[0038] According to one embodiment, each NF of the 5G system can support the following functions:
[0039] According to one embodiment, AUSF can process and store data for authentication of UE (100).
[0040] According to one embodiment, AMF (120) provides functions for access and mobility management per UE, and one UE can be connected to one AMF by default. Specifically, the AMF (120) provides signaling between core network (CN) nodes for mobility between 3GPP access networks, termination of a radio access network (RAN) control plane (CP) interface (i.e., N2 interface), termination (N1) of non-access stratum (NAS) signaling, NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE reachability (including control and performance of paging retransmission), mobility management control (subscription and policy), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (for AMF events and interfaces to the LI system), provision of forwarding of session management (SM) messages between UE and SMF, transparent proxy for SM message routing, access authentication, and roaming. It may support functions such as access authorization including authorization check, provision of short message service (SMS) message transmission between UE and SMSF, security anchor function (SAF) and / or security context management (SCM). Some or all of the functions of AMF (120) may be supported within a single instance of one AMF.
[0041] According to one embodiment, DN (175) may be referenced, for example, as an operator service, an Internet connection, or a third-party service. DN (175) may transmit a downlink protocol data unit (PDU) to UPF (130) or receive a PDU transmitted from UE (100) from UPF (130).
[0042] According to one embodiment, PCF (140) may provide a function to determine policies such as mobility management, session management, etc. by receiving information about packet flow from an application server. For example, PCF (140) may support functions such as supporting a unified policy framework for controlling network operations, providing policy rules so that control plane functions (e.g., AMF, SMF, etc.) can enforce the policy rules, and implementing a front end for accessing relevant subscription information for policy determination within a user data repository (UDR).
[0043] According to one embodiment, the SMF (135) may provide a session management function. When a UE has multiple sessions, the SMF (135) may be managed by a different SMF for each session. For example, the SMF (135) may support functions such as session management (e.g., session establishment, modification, and termination, including tunnel maintenance between UPF (130) and (R)AN (110) nodes), UE IP (internet protocol) address allocation and management (optionally including authentication), selection and control of UP functions, traffic steering setup to route traffic from the UPF (130) to the appropriate destination, termination of the interface to policy control functions, enforcement of the control portion of policies and quality of service (QoS), lawful intercept (for SM events and interfaces to the LI system), termination of the SM portion of non-access stratum (NAS) messages, downlink data notification, initiator of AN specific SM information (e.g., forwarding it to the (R)AN (110) via N2 via the AMF (120)), determination of the SSC mode of the session, roaming functions, etc. Some or all of the functions of SMF (135) may be supported within a single instance of an SMF.
[0044] According to one embodiment, the UDM (145) may store user subscription data, policy data, etc. The UDM (145) may include two parts, namely, an application front end (FE) (not shown) and a user data repository (UDR) (not shown).
[0045] In one embodiment, the FE may include a UDM FE responsible for location management, subscription management, and credential processing, and a PCF responsible for policy control. The UDR may store data required for functions provided by the UDM-FE and policy profiles required by the PCF. Data stored in the UDR may include user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data. The UDM-FE may access subscription information stored in the UDR and support functions such as authentication credential processing, user identification handling, access authentication, registration / mobility management, subscription management, and / or SMS management.
[0046] According to one embodiment, the UPF (130) may forward a downlink PDU received from the DN (175) to the UE (100) via the (R)AN (radio access network) (110). The UPF (130) forwards an uplink PDU received from the UE (100) to the DN (175) via the (R)AN (110). For example, the UPF (130) may support functions such as an anchor point for intra / inter RAT (radio access technology) mobility, an external PDU session point for interconnection to a data network, a user plane portion of packet routing and forwarding, packet inspection and policy rule enforcement, an uplink classifier to support lawful intercept, traffic usage reporting, and routing of traffic flows to the data network, a branching point to support multi-homed PDU sessions, QoS handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement), uplink traffic validation (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and / or downlink data notification triggering. Some or all of the functions of UPF (130) may be supported within a single instance of a UPF.
[0047] In one embodiment, the AF (170) interacts with a 3GPP core network to provide services. For example, the AF (170) may interact with a 3GPP core network to support functions such as application impact on traffic routing, access to network capability exposure, and / or interaction with a policy framework for policy control.
[0048] According to one embodiment, (R)AN (110) refers to a new radio access network that supports both evolved E-UTRA, which is an evolved version of 4G radio access technology, and new radio (NR) (e.g., gNB).
[0049] According to one embodiment, the gNB may support functions for radio resource management. For example, the gNB may support functions of radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in uplink / downlink (i.e., scheduling), IP (internet protocol) header compression, and encryption and / or integrity protection of user data streams. For example, the gNB may support functions such as selection of an AMF upon UE attachment, routing of user plane data to UPF(s), routing of control plane information to AMF, connection setup and teardown, scheduling and transmission of paging messages (originating from AMF), scheduling and transmission of system broadcast information (originating from AMF or operating and maintenance (O&M)), measurement and measurement reporting setup for mobility and scheduling, transport level packet marking in uplink, session management, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in inactive mode, distribution of NAS messages, NAS node selection, sharing of radio access networks, dual connectivity, and tight interworking between NR and E-UTRA.
[0050] According to one embodiment, the UE (100) may be referred to as a user device. The user device may be referred to by terms such as terminal, mobile equipment (ME), mobile station (MS), etc. In addition, the user device may be a portable device such as a laptop, mobile phone, personal digital assistant (PDA), smartphone, multimedia device, etc., or may be a non-portable device such as a personal computer (PC) or vehicle-mounted device.
[0051] According to one embodiment, the NEF may provide a means to securely expose services and capabilities provided by 3GPP network functions, such as third party, internal exposure / re-exposure, application functions, and Edge Computing. The NEF may receive information from other NF(s) (based on the exposed capability(s) of the other NF(s)). The NEF may store the received information as structured data using a standardized interface to a data storage network function. The stored information may be re-exposed by the NEF to other NF(s) and AF(s) (170) and used for other purposes, such as analysis.
[0052] According to one embodiment, NRF can support a service discovery function. It can receive NF discovery requests from NF instances and provide information about discovered NF instances to the NF instances. It can also maintain a list of available NF instances and the services they support.
[0053] Meanwhile, for convenience of explanation, FIG. 1 illustrates a reference model for a case where a UE (100) accesses one DN (175) using one PDU session, but the present disclosure is not limited thereto.
[0054] According to one embodiment, a UE (100) can access two (i.e., local and central) data networks simultaneously using multiple PDU sessions. In this case, two SMFs can be selected for different PDU sessions. However, each SMF can have the ability to control both the local UPF and the central UPF within the PDU session.
[0055] According to one embodiment, the UE (100) may simultaneously access two (i.e., local and central) data networks provided within a single PDU session.
[0056] According to one embodiment, NSSF (160) may select a set of network slice instances serving UE (100). In addition, NSSF (160) may determine allowed network slice selection assistance information (NSSAI) and, if necessary, perform mapping to subscribed single-network slice selection assistance information (S-NSSAI). In addition, NSSF (160) may determine configured NSSAI and, if necessary, perform mapping to subscribed S-NSSAI. In addition, NSSF (160) may determine a set of AMFs used to serve UE or, depending on the configuration, may inquire NRF to determine a list of candidate AMFs.
[0057] According to one embodiment, NRF can support a service discovery function. It can receive NF discovery requests from NF instances and provide information about discovered NF instances to the NF instances. It can also maintain a list of available NF instances and the services they support.
[0058] In the 3GPP system, a conceptual link connecting NFs within a 5G system can be defined as a reference point. Reference points included in the 5G system architecture depicted in Figure 1 are exemplified below.
[0059] - N1: Reference point between UE and AMF
[0060] - N2: Reference point between (R)AN and AMF
[0061] - N3: Reference point between (R)AN and UPF
[0062] - N4: Reference point between SMF and UPF
[0063] - N5: Reference point between PCF and AF
[0064] - N6: Reference point between UPF and DN
[0065] - N7: Reference point between SMF and PCF
[0066] - N8: Reference point between UDM and AMF
[0067] - N9: Reference point between two core UPFs
[0068] - N10: Reference point between UDM and SMF
[0069] - N11: Reference point between AMF and SMF
[0070] - N12: Reference point between AMF and AUSF
[0071] - N13: Reference point between UDM and authentication server function (AUSF)
[0072] - N14: Reference point between two AMFs
[0073] - N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF in visited network for roaming scenarios.
[0074] According to one embodiment, network slicing in a 5G system may be referred to as a technology and architecture that enables multiple virtualized, independent logical networks within a single physical network. Network operators can provide services by configuring virtual end-to-end networks called network slices to meet the specialized requirements of services / applications.
[0075] According to one embodiment, a network slice may be identified by an identifier called single-network slice selection assistance information (S-NSSAI). The network transmits a set of allowed slices (e.g., allowed NSSAI(s)) to the UE during a UE registration procedure (e.g., UE registration procedure), and the UE may transmit and / or receive application data through a protocol data unit (PDU) session generated through one of the transmitted slice sets (i.e., network slice).
[0076] According to one embodiment, a mobile communication system can receive 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). The mobile communication system can select terminals capable of network resource allocation based on the requirements and allocate self-network resources (i.e., QoS Flows), and transmit the resource allocation 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.
[0077] In the present disclosure, the EBC (energy budget control) NF(s) may be located in one of the following NFs: PCF, NWDAF, OAM
[0078] Figure 2 illustrates a method by which an AF negotiates an energy budget with a 5G core network according to one embodiment.
[0079] Referring to FIG. 2, in step 201 according to one embodiment, the AF (application function) (170) may send a message to the NEF for energy negotiation (Nnef_EBNegotiation_Create).
[0080] For example, a message sent to NEF (or a message for energy negotiation) may include at least some of the following information:
[0081] ◆ Energy budget information:
[0082] ■ When information of application traffic subject to energy control is included, the energy budget information may include at least some of the following information:
[0083] - The total energy usage (e.g., maximum) allowed for the UE to transmit and receive traffic for the application may be included (i.e., UE Energy Budget for Application). (e.g., information about the UE's total energy usage)
[0084] - The total energy usage allowed for the RAN to transmit and receive traffic for the application may be included (i.e., RAN Energy Budget for Application). (e.g., information about the total energy usage of the RAN)
[0085] - The total energy usage allowed for the UPF to transmit and receive traffic for the application may be included (i.e., the UPF energy budget for the application). (e.g., information about the total energy usage of the UPF)
[0086] - The total energy usage allowed for the RAN and UPF to transmit and receive traffic for the application may be included (i.e., the Network Energy Budget for the application). (e.g., information about the total energy usage of the RAN and UPF)
[0087] - The total energy usage allowed for the UE, RAN, and UPF to transmit and receive traffic for the application may be included (i.e., the Total Energy Budget for the application). (e.g., information about the total energy usage of the UE, RAN, and UPF)
[0088] ■ If information of application traffic subject to energy control is not included, the energy budget information may include at least some of the following information:
[0089] - The total energy usage (e.g., maximum) allowed for the UE to transmit and receive traffic may be included (i.e., UE Energy Budget). (e.g., information about the UE's total energy usage)
[0090] - The total energy usage (e.g., maximum) allowed for the RAN to transmit and receive traffic may be included (i.e., RAN Energy Budget). (e.g., information about the total energy usage of the RAN)
[0091] - The total energy usage allowed for the RAN and UPF to transmit and receive traffic may be included (i.e., the User Plane Energy Budget). (e.g., information about the total energy usage of the RAN and UPF)
[0092] ◆ UPF may include the total energy usage allowed when transmitting and receiving traffic for the application (i.e., UPF Energy Budget) information).
[0093] ◆ Information about UEs subject to energy control or UEs subject to energy control:
[0094] For example, information about UEs may be referenced as information indicating UEs to which an energy budget is applied. For example, information about UEs may include one or more of a Group ID, a list of UE ID(s), or an AF ID.
[0095] ◆ Information about the application subject to energy control or information of application traffic subject to energy control:
[0096] For example, information about an application can be referenced as information indicating the traffic to which an energy budget is applied. For example, information about an application can include the Application Service Provider (ASP) ID, App ID, server MAC (medium access control) address, and / or IP 3 tuples (i.e., server IP address, port number, and protocol information).
[0097] ◆ Time information:
[0098] For example, time information may include information about the time period during which the energy budget is applicable. For example, an indicator indicating whether to apply periodically may be included along with the time information. Another example may include information in the form of a period (e.g., from March 10, 2023, to March 28, 2023).
[0099] ◆ Area information: This may include information about the area to which the energy budget is applicable. Area information may consist of tracking area identities (TAIs), cell IDs, and / or geographical location information.
[0100] ◆ Information for notification request or Request for notification: This can be included if the AF wants to be notified when the energy budget is completely or nearly exhausted.
[0101] According to one embodiment, a message for energy negotiation may include energy budget information, UPF energy budget information, information about UEs subject to energy control, information about applications subject to energy control, time information, area information, and / or information for a notification request.
[0102] According to one embodiment, a message for energy negotiation may include different information depending on whether an application subject to energy control is included. For example, if the message for energy negotiation includes an application subject to energy control, the message for energy negotiation may include information about the total energy usage of the UE, information about the total energy usage of the RAN, information about the total energy usage of the UPF, information about the total energy usage of the RAN and the UPF, and / or information about the total energy usage of the UE, the RAN, and the UPF.
[0103] As another example, if the message for energy negotiation does not include an application that is the target of energy control, the message for energy negotiation may include information about the total energy usage of the UE, information about the total energy usage of the RAN, and information about the total energy usage of the RAN and UPF.
[0104] Although the message transmitted in step 201 of this disclosure is described as a message for energy negotiation, this is merely an example and may be replaced with various terms. For example, the message transmitted in step 201 may be replaced with a message for energy adjustment, a message for energy reduction, a message for energy control, or a message for energy determination.
[0105] According to one embodiment, NEF (183) may perform authentication on the request (or message of AF) received in step 201 from AF (170). In addition, NEF (183) may include information included in the message received in step 201 (e.g., energy budget information, information of application traffic subject to energy control, Request for notification, etc.) in the message transmitted to PCF (140). For example, NEF (183) may transmit at least a part of the information included in the message for energy negotiation received from AF (170) to PCF (140). (Npcf_EBPolicyControl_Create request)
[0106] According to one embodiment, in step 203, if the PCF (140) receives an authorization request message associated with the generation of an energy budget policy in step 202 or if the received message includes an energy budget, the PCF (140) may transmit a message including energy budget data and / or policy data to the UDR (181). (Nudr_DM_Query request)
[0107] According to one embodiment, in step 204, if the message received in step 203 includes energy budget data and / or policy data, UDR (181) may provide or transmit to PCF (140) all information about energy budget data and policy data (i.e., energy budget policy information for all application service providers (ASPs)). (Nudr_DM_Query_response)
[0108] According to one embodiment, in step 205a, if the energy budget information received in step 202 includes one or more of a network energy budget, a total energy budget, a network energy budget for application, or a total energy budget for application, the PCF (140) may transmit, to the EBC NF (s) (182), the energy budget information, together with information of application traffic subject to energy control, UEs subject to energy control, and / or area information received in step 202.
[0109] According to one embodiment, the PCF (140) may include one or more of an energy profile mapping request indicator or an energy budget information conversion request indicator in the message transmitted to the EBC NF (182).
[0110] According to one embodiment, when the EBC NF (182) receives a message from the PCF (140) in step 205a, in step 205b, the EBC NF (182) may convert the energy budget information included in the message received in step 205a into smaller entity units. For example, the EBC NF (182) may convert or change the energy budget information into an energy budget for the UPF, an energy budget for the UE, and / or an energy budget for the RAN. At this time, the EBC NF (182) may utilize at least some of the other information included in the message received in step 205a. That is, the EBC NF (182) may convert the energy budget information into energy budget information in smaller entity units based on at least some of the information included in the received message.
[0111] According to one embodiment, the conversion may be performed when the information received in step 205a includes an energy budget information conversion request indicator, or may be performed at the discretion of the EBC NF (182) even if the indicator is not included. That is, the conversion of the EBC NF (182) may be triggered by the energy budget information conversion request indicator or may be triggered based on the discretion of the EBC NF (182) when a preset condition is satisfied.
[0112] For example, if the information received in step 205a includes a Network Energy Budget (or Network Energy Budget for application), the EBC NF (182) may convert the Network Energy Budget into a RAN Energy Budget (or RAN Energy Budget for application) and / or a UPF Energy Budget (or UPF Energy Budget for application).
[0113] For example, if the information received in step 205a includes a Total Energy budget (for application), the EBC NF (182) may convert the Total Energy budget into a UE Energy budget (or UE Energy budget for application), a RAN Energy Budget (or RAN Energy Budget for application), and / or a UPF Energy Budget (or UPF Energy Budget for application).
[0114] According to one embodiment, the EBC NF (182) may utilize statistical information representing energy consumed by the UE (100) for a specified period of time when transmitting and receiving traffic (or the UE (100) for an application), statistical information representing energy consumed by the RAN (110) for a specified period of time when transmitting and receiving traffic (or the RAN for an application), and / or statistical information representing energy consumed by the UPF (or the UPF for an application) for a specified period of time when transmitting and receiving traffic. That is, the EBC NF (182) may perform the conversion based on statistical information of the UE, statistical information of the RAN, and / or statistical information of the UPF.
[0115] In one embodiment, the EBC NF (182) may calculate or identify several allowable energy budgets in the network based on the information contained in the energy budget information (or the information in a converted form) received in step 205a, for each entity. For example, the EBC NF (182) may calculate or identify several UPF Energy Budget(s) for the UPF Energy Budget.
[0116] According to one embodiment, the EBC NF (182) can map an allowable energy budget for each entity to an Energy Profile(s). At this time, the EBC NF (182) can utilize at least some of the other information included in step 205a. The operation of matching the energy budget to the energy profile can be performed if the information received in step 205a includes an energy profile mapping request indicator, or can be performed at the discretion of the EBC NF (182) even if the information received does not include an energy profile mapping indicator.
[0117] According to one embodiment, a set of energy profiles may represent a set of intervals of energy consumption that an entity (e.g., one of UE (100), RAN (110), UPF (130), network (i.e., RAN (110) and UPF (130)), or the entire network (i.e., UE (100), RAN (110), UPF (130)) uses when transmitting and / or receiving traffic. Each energy profile may be expressed in terms of a minimum energy consumption and / or a maximum energy consumption. For example, the unit of energy consumption may be Joule (or Watt).
[0118] According to one embodiment, at least one entity may be configured with one of the energy profiles included in a set of energy profiles. If an energy profile is configured, the at least one entity may adjust its energy consumption based on the configured energy profile. For example, an energy profile indicating that a device is powered off for transmitting and / or receiving traffic may also exist.
[0119] 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. For example, an entity (e.g., UPF) configured with Energy profile 1 can regulate its energy consumption between 0.5 to 1.0 kilo Joule (or kilo Watt) when transmitting and / or receiving traffic.
[0120] According to one embodiment, when deriving a UPF Energy Profile(s) for a UPF Energy budget, the EBC NF (182) may include nearby Energy Profiles in the UPF Energy Profile(s), along with an Energy Profile representing an interval including energy usage included in the UPF Energy budget. That is, when determining the UPF Energy Profile, the EBC NF (182) may determine the energy profiles of the UPF based on a first Energy Profile that matches the energy usage included in the UPF Energy budget and at least one additional Energy Profile that is similar to the first Energy Profile in terms of energy usage.
[0121] According to one embodiment, each of a core network entity, a base station (e.g., gNB, eNB) and / or a UE (100) included in a network (e.g., a 5G network) may correspond to at least one energy profile.
[0122] According to one embodiment, a set of energy profiles may be stored in the EBC NF (182) independently for each of the UE (100), the RAN (110), the UPF (130), the network (i.e., the RAN (110) and the UPF (130)), and the entirety (i.e., the UE (100), the RAN (110), the UPF (130)).
[0123] According to one embodiment, an energy profile for a specific entity may be set for all traffic transmitted by the entity or for specific traffic (e.g., traffic for a specific application). For example, an energy profile for a UE (100) may be set for all traffic transmitted by the UE (100), and an energy profile for the UE (100) may be set for a specific type of traffic (e.g., corresponding to a specific application) among various types of traffic transmitted by the UE (100). That is, an energy profile may be set for each type of traffic transmitted by a specific entity, or may be set for all traffic.
[0124] However, the two methods described as methods for setting energy profiles are not exclusive. For example, the energy profile set for a UE (100) may be set for the total traffic transmitted by the UE (100), or may be set for designated traffic corresponding to a specific application among the traffic transmitted by the UE (100).
[0125] According to one embodiment, the EBC NF (182) may obtain a set of energy profiles for each entity through OAM (not shown) or NWDAF (not shown) at a point in time prior to receiving the message of step 205a, and may store the obtained set of profiles.
[0126] In the present disclosure, at least one profile, a set of profiles, and a plurality of profiles may be replaced with various terms to refer to configuration information for energy control. For example, at least one profile may be replaced with various terms such as entity-specific configuration information, entity-specific energy mapping information, and entity-specific energy information.
[0127] According to one embodiment, the EBC NF (182) may transmit a response message to the PCF (140). The response message transmitted by the EBC NF (182) to the PCF (140) may include at least some of the following information:
[0128] - Candidate energy budget(s): A set of allowed energy budgets per entity may be included for one or more entities (e.g., candidate energy budget information).
[0129] - Energy Profile(s): One or more entities may contain per-entity allowed Energy profile(s). (e.g., Energy Profile Information)
[0130] - Result: This may include the processing result (e.g., success or failure) for energy budget conversion and / or energy profile mapping. For example, if the result indicates a failure, the result may include information indicating the cause of the failure (e.g., result information).
[0131] According to one embodiment, in step 205c, the PCF (140) may determine an energy policy based on the received candidate energy budget(s) and / or at least one energy profile(s), if the message received from the EBC NF (182) in step 205b includes candidate energy budget(s) and / or at least one energy profile(s). (Energy Budget Policy decision)
[0132] According to one embodiment, the determined energy policy may be in the form of at least one candidate energy budget(s) or at least one energy profile(s) per entity.
[0133] According to one embodiment, in step 206, PCF (140) may transmit a response message to NEF (183). The transmitted response message may include energy policy information and / or an energy budget reference ID determined in step 205c. (Npcf_EBPolicyControl_Creat_response)
[0134] According to one embodiment, in step 207, NEF (183) may include the information received from PCF in step 206 in a response message transmitted to AF (170). (Nnef_EBNegotiation_Create response)
[0135] According to one embodiment, in step 208, AF (170) may include the following information in the message transmitted to NEF (183) if the message received in step 207 includes an Energy Policy and / or an Energy Budget Reference ID: (Nef_EBNegotiation_Update)
[0136] - Energy Budget Reference ID: May include the Energy Budget Reference ID received in step 207.
[0137] - Selected Energy Policy:
[0138] According to one embodiment, if the Energy Policy information received in step 207 includes at least one candidate energy budget(s), the AF (170) may select one energy budget from among at least one candidate energy budget(s) per entity (e.g., one of UE (100), RAN (110), UPF (130), network (i.e., RAN and UPF), and entire (i.e., UE, RAN, UPF)) and the AF (170) may include the energy budget for the selected entity together with an Energy Budget Reference ID in the message transmitted to the NEF (183) in the Selected Energy Policy.
[0139] According to one embodiment, when NEF (183) receives an update request message from AF (170) in step 208 in step 209, it may include the information included in the update request message in a message transmitted to PCF (140). (Npcf_EBPolicyControl_Update request)
[0140] According to one embodiment, in step 210a, the PCF (140) may transmit to the EBC NF (182) one of the following: an Energy Budget Reference ID, UEs subject to energy control corresponding to the Energy Budget Reference ID, information of Application traffic subject to energy control, time information, area information, or Energy Budget Reference ID, along with the selected energy policy.
[0141] According to one embodiment, in step 210b, the EBC NF (182) may store the information received from the PCF (140) and then transmit a response message to the PCF (140).
[0142] According to one embodiment, in step 211, PCF (140) may send an ACK (acknowledge) message to NEF (183). (Npcf_EBPolicyControl_Update response)
[0143] According to one embodiment, at step 212, NEF (183) may send an ACK (acknowledge) message to AF (170). (Nnef_EBNegotiation_Update response)
[0144] According to one embodiment, in step 213, the PCF (140) may transmit a Nudr_DM_Update message to the UDR (181) to store the selected energy policy for the selected energy budget reference ID (Energy Budget Reference ID). The Nudr_DM_Update message may include the following information:
[0145] - Energy Budget Reference ID: May include the Energy Budget Reference ID received in step 209.
[0146] - Key information: May include data key information representing policy data and / or energy budget.
[0147] - Selected Energy Policy: The Selected Energy Policy received in step 209 may be included.
[0148] - It may include one of the following: UEs subject to energy control corresponding to the Energy Budget Reference ID, information of application traffic subject to energy control, time information, or area information. (Nudr_DM_Update request)
[0149] According to one embodiment, in step 214, UDR (181) may store the information received in step 211 and then transmit an ACK message (acknowledge message) to PCF (140). (Nudr_DM_Update response)
[0150] FIG. 3 illustrates a method for an AF to apply an energy policy negotiated with a 5G core network according to one embodiment.
[0151] Referring to FIG. 3, in step 300a according to one embodiment, a PCF(s)(140) or EBC NF(s)(182) may perform a subscription request for a change in an AF(170) request stored in a UDR(181). The subscription request message may include the following information:
[0152] - Information indicating energy policy,
[0153] - Subscription target information: For example, subscription target information may include a Group ID, a list of UE ID(s), AF ID, Application Service Provider (ASP) ID, App ID, server MAC address, and / or IP 3 tuples (e.g., server IP address, port number, protocol information). (Nudr_DM_subscribe)
[0154] According to one embodiment, in step 300b, the AF (170) performs policy negotiation for energy budget information. (The AF previously negotiated policy for energy budget information)
[0155] According to one embodiment, in step 301, AF (170) creates an AF request to apply the agreed energy policy. (Creation of the AF request)
[0156] According to one embodiment, in step 302, AF (170) may transmit a request message to apply the agreed energy policy to a group of UE(s) or any UE. The request message may include at least some of the following information: (Nnef_ApplyPolicy_Create)
[0157] - UEs subject to energy control:
[0158] Information on UEs subject to energy control may be information indicating UEs to which an energy budget is applied. For example, information on UEs subject to energy control may include at least one of a Group ID, a list of UE ID(s), or an AF ID.
[0159] - Information of application traffic subject to energy control:
[0160] Information about the application subject to energy control may be information indicating the traffic to which the energy budget is applied. For example, information about the application subject to energy control may include the Application Service Provider (ASP) identifier (ID), the App (application) ID, the server MAC address, and / or IP 3 tuples (e.g., the server IP address, port number, and protocol information).
[0161] - Time information: Time information may include time information to which the energy budget is applicable.
[0162] At this time, the message may include an indicator indicating whether to apply periodically or not, along with time information.
[0163] Alternatively, the time information may include information in the form of a period (e.g., from 2023 / 3 / 10 to 2023 / 3 / 28).
[0164] - Area information: Area information may include information about the area to which the energy budget is applicable. For example, area information may include TAI(s), cell ID(s) and / or geographical location information.
[0165] - Energy budget reference ID: In step 300, the Energy Budget Reference ID received by AF (170) through NEF (183) from PCF (170) (or Energy Budget Control NF) through consultation may be included.
[0166] According to one embodiment, when NEF (183) receives a request message from AF (170), it may assign a Transaction Reference ID to the request message. In addition, NEF (170) may perform authentication on the request message and store the AF Identifier and Transaction Reference ID.
[0167] According to one embodiment, in step 303, when the NEF (183) receives the External Identifier(s), it transmits a request message including the Identifier Translation to the UDM (145) to obtain the Internal Identifier(s) (e.g., SUPI(s)) from the UDM (145). (Resolve the external ID to the internal ID via UDM)
[0168] According to one embodiment, when NEF (183) receives External Group Identifier(s), it can transmit a request message including Group Identifier Translation to UDM (145) and obtain corresponding Internal Group Identifier(s) from UDM (145).
[0169] According to one embodiment, in step 304a, the NEF (183) may store the request information received from the AF (170) in the UDR (181). For example, the information to be stored may be an Energy Budget Reference ID and a target to which the Energy Budget Reference ID is applied (e.g., an Internal Group Identifier or SUPI(s)). For example, the information to be stored may be stored in the UDR in the following format: Data Set = Application Data; Data Subset = Energy Budget reference ID, Data Key = Internal Group Identifier or SUPI (Storing / updating / removing the information)
[0170] According to one embodiment, in step 304b, NEF (183) transmits a response message to AF (170). The transmitted response message may include a Transaction Reference ID. (Nnef_ApplyPolicy_Create response)
[0171] According to one embodiment, if the PCF(s)(140) requests a subscription for a change in the AF(170) request stored in the UDR(181) in step 300a in step 305, the UDR(181) may send a message notifying the changed information to the corresponding PCF(s)(140). (Nudr_DM_Notify)
[0172] In one embodiment, if the EBC NF(s)(182) requests a subscription for a change in the AF(170) request stored in the UDR(181) in step 300a, the UDR(181) may transmit a message notifying the changed information to the corresponding EBC NF(s)(182).
[0173] FIG. 4 illustrates an example of a functional structure of a base station according to an embodiment of the present disclosure.
[0174] Referring to FIG. 4, the configuration illustrated in FIG. 4 according to one embodiment can be understood as the configuration of the RAN (110) (e.g., gNB, eNB) of FIG. 1. Terms such as "...unit" and "...unit" used hereinafter mean a unit that processes at least one function or operation, which can be implemented by hardware, software, or a combination of hardware and software.
[0175] According to one embodiment, the base station includes a communication unit (405), a storage unit (410), and / or a control unit (415).
[0176] The communication unit (405) performs functions for transmitting and receiving signals via a wireless channel. For example, the communication unit (405) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (405) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the communication unit (405) restores a reception bit stream by demodulating and decoding the baseband signal. In addition, the communication unit (405) upconverts a baseband signal into an RF band signal and transmits it through an antenna, and downconverts an RF band signal received through the antenna into a baseband signal. For example, the communication unit (405) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.
[0177] In addition, the communication unit (405) may include a plurality of transmit / receive paths. Furthermore, the communication unit (405) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit (405) may be composed of digital circuits and analog circuits (e.g., radio frequency integrated circuits (RFIC)). Here, the digital circuits and analog circuits may be implemented in a single package. In addition, the communication unit (405) may include a plurality of RF chains. Furthermore, the communication unit (405) may perform beamforming.
[0178] The communication unit (405) transmits and receives signals as described above. Accordingly, all or part of the communication unit (405) may be referred to as a "transmitter," a "receiver," or a "transmitting and receiving unit." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that the communication unit (405) performs the processing described above.
[0179] The storage unit (410) stores data such as basic programs, application programs, and setting information for the operation of the base station. The storage unit (410) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (410) provides stored data upon request from the control unit (415).
[0180] The control unit (415) controls the overall operations of the base station. For example, the control unit (415) transmits and receives signals through the communication unit (405). In addition, the control unit (415) records and reads data in the storage unit (410). In addition, the control unit (415) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (415) may include at least one processor or microprocessor, or may be a part of a processor. In addition, a part of the communication unit (405) and the control unit (415) may be referred to as a CP (communication processor). According to various embodiments, the control unit (415) may control to perform synchronization using a wireless communication network. For example, the control unit (415) may control the base station to perform operations according to the various embodiments described above.
[0181] FIG. 5 illustrates an example of the functional structure of a terminal according to an embodiment of the present disclosure. The configuration illustrated in FIG. 5 can be understood as the configuration of the UE (100) of FIG. 1. Terms such as "... unit" and "... device" used hereinafter refer to a unit that processes at least one function or operation, which can be implemented by hardware, software, or a combination of hardware and software.
[0182] Referring to FIG. 5, the terminal includes a communication unit (505), a storage unit (510), and / or a control unit (515).
[0183] The communication unit (505) performs functions for transmitting and receiving signals via a wireless channel. For example, the communication unit (505) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (505) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the communication unit (505) restores a reception bit stream by demodulating and decoding the baseband signal. In addition, the communication unit (505) upconverts a baseband signal to an RF band signal and then transmits it through an antenna, and downconverts an RF band signal received through the antenna to a baseband signal. For example, the communication unit (505) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.
[0184] In addition, the communication unit (505) may include a plurality of transmit / receive paths. Furthermore, the communication unit (505) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit (505) may be composed of digital circuits and analog circuits (e.g., a radio frequency integrated circuit (RFIC)). Here, the digital circuits and analog circuits may be implemented in a single package. In addition, the communication unit (505) may include a plurality of RF chains. Furthermore, the communication unit (505) may perform beamforming.
[0185] The communication unit (505) transmits and receives signals as described above. Accordingly, all or part of the communication unit (505) may be referred to as a "transmitter," a "receiver," or a "transmitting and receiving unit." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that the communication unit (505) performs the processing described above.
[0186] The storage unit (510) stores data such as basic programs, application programs, and setting information for the operation of the terminal. The storage unit (510) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (510) provides stored data upon request from the control unit (515).
[0187] The control unit (515) controls the overall operations of the terminal. For example, the control unit (515) transmits and receives signals through the communication unit (505). In addition, the control unit (515) records and reads data in the storage unit (510). In addition, the control unit (515) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (515) may include at least one processor or microprocessor, or may be a part of a processor. In addition, a part of the communication unit (505) and the control unit (515) may be referred to as a CP (communication processor). According to various embodiments, the control unit (515) may control to perform synchronization using a wireless communication network. For example, the control unit (515) may control the terminal to perform operations according to various embodiments described below.
[0188] FIG. 6 illustrates an example of a functional structure of a core network object according to an embodiment of the present disclosure. It illustrates a configuration of a core network object in a wireless communication system according to various embodiments of the present disclosure. The configuration illustrated in FIG. 6 can be understood as a configuration of a device having the function of at least one of the network entities of FIG. 1 (e.g., NWDAF (165), AMF (120), SMF (135)). Terms such as '... unit', '... device', etc. used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware, software, or a combination of hardware and software.
[0189] Referring to FIG. 6, the core network object may include a communication unit (640), a storage unit (645), and / or a control unit (650).
[0190] The communication unit (640) provides an interface for communicating with other devices within the network. That is, the communication unit (640) converts a bit string transmitted from the core network object to another device into a physical signal, and converts a physical signal received from another device into a bit string. That is, the communication unit (640) can transmit and receive signals. Accordingly, the communication unit (640) may be referred to as a modem, a transmitter, a receiver, or a transceiver. In this case, the communication unit (640) enables the core network object to communicate with other devices or systems via a backhaul connection (e.g., a wired backhaul or a wireless backhaul) or via a network.
[0191] The storage unit (645) stores data such as basic programs, application programs, and configuration information for the operation of the core network object. The storage unit (645) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (645) provides the stored data upon request from the control unit (650).
[0192] The control unit (650) controls the overall operations of the core network object. For example, the control unit (650) transmits and receives signals through the communication unit (640). In addition, the control unit (650) records and reads data from the storage unit (645). For this purpose, the control unit (650) may include at least one processor. According to various embodiments of the present disclosure, the control unit (650) may control synchronization using a wireless communication network. For example, the control unit (650) may control the core network object to perform operations according to various embodiments described below.
[0193] According to one embodiment, a method performed by NWDAF in a mobile communication system may include the steps of: obtaining information related to a network slice in response to identifying an analysis request for the network slice; obtaining information related to at least one network entity included in the network slice based on the information related to the network slice; and generating an analysis result for the network slice based on the information related to the at least one network entity obtained.
[0194] While the detailed description of the present invention has described specific embodiments, it should be understood 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.
[0195] 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 above description.
[0196] 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.
[0197] 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 embodiments described in the claims or specification of the present disclosure.
[0198] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, 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 a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.
[0199] Additionally, the program may be stored on 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 disclosure 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 disclosure.
[0200] In the specific embodiments of the present disclosure described above, components included in the invention are expressed singularly or plurally, 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 disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.
[0201] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help the understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modified examples based on the technical idea of the present disclosure are possible. In addition, each embodiment can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and another embodiment can be combined with each other to operate a base station and a terminal. In addition, other modified examples based on the technical idea of the embodiments can be implemented in various systems such as an FDD LTE system, a TDD LTE system, a 5G or NR system, etc.
Claims
1. A method performed by a network exposure function (NEF) entity in a mobile communication system, A step of receiving a message from an application function (AF) entity requesting negotiation of at least one policy related to energy, the message including information on a maximum allowable energy consumption of at least one of a radio access network (RAN) or a user plane function (UPF) entity; A step of transmitting a first message including information about the maximum allowable energy consumption to a PCF (policy control function) entity; and A step of receiving, from the PCF entity, a second message comprising information about at least one policy associated with the energy in response to the first message, A method wherein said at least one policy associated with said energy is based on said information about said maximum allowable energy consumption.
2. In claim 1, A method further comprising the step of transmitting, to the AF entity, information about the at least one policy associated with the energy in response to the message.
3. In claim 1, A method wherein the message includes at least one of information about the number of UEs (user equipment) associated with the at least one policy, information about an address of an application server, information about a time associated with the at least one policy, or information about a region associated with the at least one policy.
4. In claim 1, A step of receiving a message from the AF entity, wherein the information about the at least one policy includes a plurality of policies, and the message includes information about a policy for the AF entity among the plurality of policies; and A method comprising the step of transmitting, to the PCF entity, a message including information about the policy for the AF entity.
5. In the NEF (network exposure function) entity in the mobile communication system, transceiver; and A controller coupled with the above transceiver, The above controller: Receive a message from an application function (AF) entity requesting negotiation of at least one policy related to energy, wherein the message includes information on a maximum allowable energy consumption of at least one of a radio access network (RAN) or a user plane function (UPF) entity; Transmitting a first message including the information about the maximum allowable energy consumption to a PCF (policy control function) entity, is configured to receive from said PCF entity a second message comprising information about said at least one policy associated with said energy in response to said first message; A NEF entity, wherein at least one policy associated with said energy is based on said information about said maximum allowable energy consumption.
6. In claim 5, The above controller: A NEF entity configured to transmit, to the AF entity, information about the at least one policy associated with the energy in response to the message.
7. In claim 5, An NEF entity, wherein the message includes at least one of information about the number of UEs (user equipment) associated with the at least one policy, information about an address of an application server, information about a time associated with the at least one policy, or information about a region associated with the at least one policy.
8. In claim 5, The above controller: From the AF entity, if the information about the at least one policy includes a plurality of policies, receiving a message including information about a policy for the AF entity among the plurality of policies, A NEF entity configured to transmit a message containing the information about the policy for the AF entity to the PCF entity.
9. A method performed by a PCF (policy control function) entity in a mobile communication system, A step of receiving a first message from a network exposure function (NEF) entity, wherein the first message includes information on a maximum allowable energy consumption of at least one of a radio access network (RAN) or a user plane function (UPF) entity; and comprising the step of transmitting to the NEF entity a second message comprising information about at least one policy associated with energy in response to the first message; A method wherein said at least one policy associated with said energy is based on said information about said maximum allowable energy consumption.
10. In claim 9, A method wherein the first message includes at least one of information about the number of UEs (user equipment) associated with the at least one policy, information about an address of an application server, information about a time associated with the at least one policy, or information about a region associated with the at least one policy.
11. In claim 9, A method comprising the step of receiving, from the NEF entity, a message including information about a policy for the AF entity among the plurality of policies, if the information about the at least one policy includes a plurality of policies.
12. In claim 11, A step of sending a message requesting storage of the information about the policy to a UDR (unified data repository) entity; and A method comprising the step of receiving, from the UDR entity, a response message to the message requesting storage of the information for the policy.
13. In a PCF (policy control function) entity in a mobile communication system, transceiver; and A controller coupled with the above transceiver, The above controller: Receive a first message from a network exposure function (NEF) entity, wherein the first message includes information about a maximum allowable energy consumption of at least one of a radio access network (RAN) or a user plane function (UPF) entity, is configured to transmit to the NEF entity a second message comprising information about at least one policy associated with energy in response to the first message; A PCF entity wherein at least one policy associated with said energy is based on said information about said maximum allowable energy consumption.
14. In claim 13, A PCF entity, wherein the first message includes at least one of information about the number of user equipments (UEs) associated with the at least one policy, information about an address of an application server, information about a time associated with the at least one policy, or information about a region associated with the at least one policy.
15. In claim 13, The above controller: From the NEF entity, if the information about the at least one policy includes a plurality of policies, receiving a message including information about a policy for the AF entity among the plurality of policies, Send a message to the UDR (unified data repository) entity requesting storage of the above information for the above policy, A PCF entity configured to receive a response message to the message requesting storage of the information for the policy from the UDR entity.
Citation Information
Cited By
Communication methods and apparatuses, and communication device and storage medium
WO2026153292A1
