WO2025053355A1

WO2025053355A1 - Method and apparatus for operations considering energy consumption in a wireless network system

Info

Publication number: WO2025053355A1
Application number: PCT/KR2024/001193
Authority: WO
Inventors: Daewook BYUN; Laeyoung Kim; Myungjune YOUN; Seokjung KIM
Original assignee: LG Electronics Inc
Current assignee: LG Electronics Inc
Priority date: 2023-09-04
Filing date: 2024-01-25
Publication date: 2025-03-13
Anticipated expiration: 2026-03-04

Abstract

A method and apparatus for operations considering energy consumption in a wireless network system is provided. A first RAN node receives, from an AMF, a first message including an energy efficiency configuration, wherein the energy efficiency configuration includes an energy consumption threshold per network slice and/or per wireless device. A first RAN node transmits, to a second RAN node, a second message requesting a handover, wherein the handover is determined based on the monitored energy consumption for the network slice or the wireless device and the energy consumption threshold.

Description

METHOD AND APPARATUS FOR OPERATIONS CONSIDERING ENERGY CONSUMPTION IN A WIRELESS NETWORK SYSTEM

The present disclosure relates to a method and apparatus for operations considering energy consumption in a wireless network system.

3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.

Work has started in international telecommunication union (ITU) and 3GPP to develop requirements and specifications for new radio (NR) systems. 3GPP has to identify and develop the technology components needed for successfully standardizing the new RAT timely satisfying both the urgent market needs, and the more long-term requirements set forth by the ITU radio communication sector (ITU-R) international mobile telecommunications (IMT)-2020 process. Further, the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.

The NR targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), etc. The NR shall be inherently forward compatible.

In NR, use cases and service requirements are being developed in relation to providing services considering energy efficiency. These use cases and service requirements are described in "Study on Energy Efficiency as a service criteria" in 3GPP documents (e.g., TR 22.882).

In these use cases, If the energy consumption rate exceeds the maximum energy consumption rate, or if total 'energy units' exceed the energy credit limit, the wireless devices may no longer receive service. Accordingly, specific methods for service restrictions are required.

Therefore, studies for operations considering energy consumption in a wireless network system are required.

In an aspect, a method performed by a first Radio Access Network (RAN) node in a wireless communication system is provided. The method comprises: receiving, from an Access and Mobility management Function (AMF), a first message including an energy efficiency configuration, wherein the energy efficiency configuration includes an energy consumption threshold per network slice and/or per wireless device; monitoring energy consumption for a network slice and/or a wireless device; and transmitting, to a second RAN node, a second message requesting a handover, wherein the handover is determined based on the monitored energy consumption for the network slice or the wireless device and the energy consumption threshold, and wherein the second message includes a cause value informing that the handover is performed for energy efficiency.

In another aspect, an apparatus for implementing the above method is provided.

The present disclosure can have various advantageous effects.

According to some embodiments of the present disclosure, the network could provide efficient operations considering energy consumption.

For example, based on the energy usage per slice or the energy usage per wireless device, the network can control or manage the energy efficiency per slice between neighbor base stations or the energy efficiency for a specific UE. In order to control or manage the energy efficiency per slice between neighbor base stations or the energy efficiency of a specific wireless device, the network can handover a wireless device using a specific slice or a specific wireless device to a neighbor base station supporting the same slice. Therefore, according to the present disclosure, the energy usage of a base station can be reduced for each service, or the energy usage of a specific UE can be reduced.

In other words, the network (that is, RAN node an/or CN node) can determine handover of wireless devices based on energy usage per slice or energy usage of each wireless device. Accordingly, the energy usage of the base station and/or the wireless device can be reduced.

Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and/or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.

FIG. 4 shows an example of UE to which implementations of the present disclosure is applied.

FIGS. 5 and 6 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

FIG. 7 shows an example of the overall architecture of an NG-RAN to which technical features of the present disclosure can be applied.

FIG. 8 shows an interface protocol structure for F1-C to which technical features of the present disclosure can be applied.

FIG. 9 shows an example of a successful operation for PDU session resource setup to which implementations of the present disclosure is applied.

FIG. 10 shows an example of a successful operation for Initial context setup to which implementations of the present disclosure is applied.

FIG. 11 shows an example of a successful operation for NG setup procedure to which implementations of the present disclosure is applied.

FIG. 12 shows an example of a successful operation for AMF Configuration Update procedure to which implementations of the present disclosure is applied.

FIG. 13 shows an example of a successful operation for Handover Preparation to which implementations of the present disclosure is applied.

FIG. 14 shows an example of a Resource Status Reporting Initiation to which implementations of the present disclosure is applied.

FIG. 15 shows an example of a successful operation for Resource Status Reporting procedure to which implementations of the present disclosure is applied.

FIG. 16 shows another use case on service energy monitoring by an application server to which to which implementations of the present disclosure is applied.

FIG. 17 shows an example of a method for operations considering energy consumption in a wireless network system, according to some embodiments of the present disclosure.

FIG. 18a and FIG. 18b show a flow chart for providing energy efficiency for a service, according to some embodiments of the present disclosure.

The following techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single carrier frequency division multiple access (SC-FDMA) system, and a multicarrier frequency division multiple access (MC-FDMA) system. CDMA may be embodied through radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be embodied through radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA may be embodied through radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or evolved UTRA (E-UTRA). UTRA is a part of a universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in DL and SC-FDMA in UL. Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and/or 5G NR (new radio).

For convenience of description, implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.

For terms and technologies which are not specifically described among the terms of and technologies employed in the present disclosure, the wireless communication standard documents published before the present disclosure may be referenced.

In the present disclosure, "A or B" may mean "only A", "only B", or "both A and B". In other words, "A or B" in the present disclosure may be interpreted as "A and/or B". For example, "A, B or C" in the present disclosure may mean "only A", "only B", "only C", or "any combination of A, B and C".

In the present disclosure, slash (/) or comma (,) may mean "and/or". For example, "A/B" may mean "A and/or B". Accordingly, "A/B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B or C".

In the present disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". In addition, the expression "at least one of A or B" or "at least one of A and/or B" in the present disclosure may be interpreted as same as "at least one of A and B".

In addition, in the present disclosure, "at least one of A, B and C" may mean "only A", "only B", "only C", or "any combination of A, B and C". In addition, "at least one of A, B or C" or "at least one of A, B and/or C" may mean "at least one of A, B and C".

Also, parentheses used in the present disclosure may mean "for example". In detail, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, "control information" in the present disclosure is not limited to "PDCCH" and "PDCCH" may be proposed as an example of "control information". In addition, even when shown as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information".

Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.

Although not limited thereto, various descriptions, functions, procedures, suggestions, methods and/or operational flowcharts of the present disclosure disclosed herein can be applied to various fields requiring wireless communication and/or connection (e.g., 5G) between devices.

Hereinafter, the present disclosure will be described in more detail with reference to drawings. The same reference numerals in the following drawings and/or descriptions may refer to the same and/or corresponding hardware blocks, software blocks, and/or functional blocks unless otherwise indicated.

The 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1.

Three main requirement categories for 5G include (1) a category of enhanced mobile broadband (eMBB), (2) a category of massive machine type communication (mMTC), and (3) a category of ultra-reliable and low latency communications (URLLC).

Partial use cases may require a plurality of categories for optimization and other use cases may focus only upon one key performance indicator (KPI). 5G supports such various use cases using a flexible and reliable method.

eMBB far surpasses basic mobile Internet access and covers abundant bidirectional work and media and entertainment applications in cloud and augmented reality. Data is one of 5G core motive forces and, in a 5G era, a dedicated voice service may not be provided for the first time. In 5G, it is expected that voice will be simply processed as an application program using data connection provided by a communication system. Main causes for increased traffic volume are due to an increase in the size of content and an increase in the number of applications requiring high data transmission rate. A streaming service (of audio and video), conversational video, and mobile Internet access will be more widely used as more devices are connected to the Internet. These many application programs require connectivity of an always turned-on state in order to push real-time information and alarm for users. Cloud storage and applications are rapidly increasing in a mobile communication platform and may be applied to both work and entertainment. The cloud storage is a special use case which accelerates growth of uplink data transmission rate. 5G is also used for remote work of cloud. When a tactile interface is used, 5G demands much lower end-to-end latency to maintain user good experience. Entertainment, for example, cloud gaming and video streaming, is another core element which increases demand for mobile broadband capability. Entertainment is essential for a smartphone and a tablet in any place including high mobility environments such as a train, a vehicle, and an airplane. Other use cases are augmented reality for entertainment and information search. In this case, the augmented reality requires very low latency and instantaneous data volume.

In addition, one of the most expected 5G use cases relates a function capable of smoothly connecting embedded sensors in all fields, i.e., mMTC. It is expected that the number of potential Internet-of-things (IoT) devices will reach 204 hundred million up to the year of 2020. An industrial IoT is one of categories of performing a main role enabling a smart city, asset tracking, smart utility, agriculture, and security infrastructure through 5G.

URLLC includes a new service that will change industry through remote control of main infrastructure and an ultra-reliable/available low-latency link such as a self-driving vehicle. A level of reliability and latency is essential to control a smart grid, automatize industry, achieve robotics, and control and adjust a drone.

5G is a means of providing streaming evaluated as a few hundred megabits per second to gigabits per second and may complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such fast speed is needed to deliver TV in resolution of 4K or more (6K, 8K, and more), as well as virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games. A specific application program may require a special network configuration. For example, for VR games, gaming companies need to incorporate a core server into an edge network server of a network operator in order to minimize latency.

Automotive is expected to be a new important motivated force in 5G together with many use cases for mobile communication for vehicles. For example, entertainment for passengers requires high simultaneous capacity and mobile broadband with high mobility. This is because future users continue to expect connection of high quality regardless of their locations and speeds. Another use case of an automotive field is an AR dashboard. The AR dashboard causes a driver to identify an object in the dark in addition to an object seen from a front window and displays a distance from the object and a movement of the object by overlapping information talking to the driver. In the future, a wireless module enables communication between vehicles, information exchange between a vehicle and supporting infrastructure, and information exchange between a vehicle and other connected devices (e.g., devices accompanied by a pedestrian). A safety system guides alternative courses of a behavior so that a driver may drive more safely drive, thereby lowering the danger of an accident. The next stage will be a remotely controlled or self-driven vehicle. This requires very high reliability and very fast communication between different self-driven vehicles and between a vehicle and infrastructure. In the future, a self-driven vehicle will perform all driving activities and a driver will focus only upon abnormal traffic that the vehicle cannot identify. Technical requirements of a self-driven vehicle demand ultra-low latency and ultra-high reliability so that traffic safety is increased to a level that cannot be achieved by human being.

A smart city and a smart home/building mentioned as a smart society will be embedded in a high-density wireless sensor network. A distributed network of an intelligent sensor will identify conditions for costs and energy-efficient maintenance of a city or a home. Similar configurations may be performed for respective households. All of temperature sensors, window and heating controllers, burglar alarms, and home appliances are wirelessly connected. Many of these sensors are typically low in data transmission rate, power, and cost. However, real-time HD video may be demanded by a specific type of device to perform monitoring.

Consumption and distribution of energy including heat or gas is distributed at a higher level so that automated control of the distribution sensor network is demanded. The smart grid collects information and connects the sensors to each other using digital information and communication technology so as to act according to the collected information. Since this information may include behaviors of a supply company and a consumer, the smart grid may improve distribution of fuels such as electricity by a method having efficiency, reliability, economic feasibility, production sustainability, and automation. The smart grid may also be regarded as another sensor network having low latency.

Mission critical application (e.g., e-health) is one of 5G use scenarios. A health part contains many application programs capable of enjoying benefit of mobile communication. A communication system may support remote treatment that provides clinical treatment in a faraway place. Remote treatment may aid in reducing a barrier against distance and improve access to medical services that cannot be continuously available in a faraway rural area. Remote treatment is also used to perform important treatment and save lives in an emergency situation. The wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

Wireless and mobile communication gradually becomes important in the field of an industrial application. Wiring is high in installation and maintenance cost. Therefore, a possibility of replacing a cable with reconstructible wireless links is an attractive opportunity in many industrial fields. However, in order to achieve this replacement, it is necessary for wireless connection to be established with latency, reliability, and capacity similar to those of the cable and management of wireless connection needs to be simplified. Low latency and a very low error probability are new requirements when connection to 5G is needed.

Logistics and freight tracking are important use cases for mobile communication that enables inventory and package tracking anywhere using a location-based information system. The use cases of logistics and freight typically demand low data rate but require location information with a wide range and reliability.

Referring to FIG. 1, the communication system 1 includes wireless devices 100a to 100f, base stations (BSs) 200, and a network 300. Although FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.

The BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS/network node with respect to other wireless devices.

The wireless devices 100a to 100f represent devices performing communication using radio access technology (RAT) (e.g., 5G new RAT (NR)) or LTE) and may be referred to as communication/radio/5G devices. The wireless devices 100a to 100f may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device/server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an AR/VR/Mixed Reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter.

In the present disclosure, the wireless devices 100a to 100f may be called user equipments (UEs). A UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather/environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.

The UAV may be, for example, an aircraft aviated by a wireless control signal without a human being onboard.

The VR device may include, for example, a device for implementing an object or a background of the virtual world. The AR device may include, for example, a device implemented by connecting an object or a background of the virtual world to an object or a background of the real world. The MR device may include, for example, a device implemented by merging an object or a background of the virtual world into an object or a background of the real world. The hologram device may include, for example, a device for implementing a stereoscopic image of 360 degrees by recording and reproducing stereoscopic information, using an interference phenomenon of light generated when two laser lights called holography meet.

The public safety device may include, for example, an image relay device or an image device that is wearable on the body of a user.

The MTC device and the IoT device may be, for example, devices that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device may include smartmeters, vending machines, thermometers, smartbulbs, door locks, or various sensors.

The medical device may be, for example, a device used for the purpose of diagnosing, treating, relieving, curing, or preventing disease. For example, the medical device may be a device used for the purpose of diagnosing, treating, relieving, or correcting injury or impairment. For example, the medical device may be a device used for the purpose of inspecting, replacing, or modifying a structure or a function. For example, the medical device may be a device used for the purpose of adjusting pregnancy. For example, the medical device may include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for procedure.

The security device may be, for example, a device installed to prevent a danger that may arise and to maintain safety. For example, the security device may be a camera, a closed-circuit TV (CCTV), a recorder, or a black box.

The FinTech device may be, for example, a device capable of providing a financial service such as mobile payment. For example, the FinTech device may include a payment device or a point of sales (POS) system.

The weather/environment device may include, for example, a device for monitoring or predicting a weather/environment.

The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200/network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200/network 300. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

Wireless communication/

connections

150a, 150b and 150c may be established between the wireless devices 100a to 100f and/or between wireless device 100a to 100f and BS 200 and/or between BSs 200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc. The wireless devices 100a to 100f and the BSs 200/the wireless devices 100a to 100f may transmit/receive radio signals to/from each other through the wireless communication/

connections

150a, 150b and 150c. For example, the wireless communication/

connections

150a, 150b and 150c may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/de-mapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.

AI refers to the field of studying artificial intelligence or the methodology that can create it, and machine learning refers to the field of defining various problems addressed in the field of AI and the field of methodology to solve them. Machine learning is also defined as an algorithm that increases the performance of a task through steady experience on a task.

Robot means a machine that automatically processes or operates a given task by its own ability. In particular, robots with the ability to recognize the environment and make self-determination to perform actions can be called intelligent robots. Robots can be classified as industrial, medical, home, military, etc., depending on the purpose or area of use. The robot can perform a variety of physical operations, such as moving the robot joints with actuators or motors. The movable robot also includes wheels, brakes, propellers, etc., on the drive, allowing it to drive on the ground or fly in the air.

Autonomous driving means a technology that drives on its own, and autonomous vehicles mean vehicles that drive without user's control or with minimal user's control. For example, autonomous driving may include maintaining lanes in motion, automatically adjusting speed such as adaptive cruise control, automatic driving along a set route, and automatically setting a route when a destination is set. The vehicle covers vehicles equipped with internal combustion engines, hybrid vehicles equipped with internal combustion engines and electric motors, and electric vehicles equipped with electric motors, and may include trains, motorcycles, etc., as well as cars. Autonomous vehicles can be seen as robots with autonomous driving functions.

Extended reality is collectively referred to as VR, AR, and MR. VR technology provides objects and backgrounds of real world only through computer graphic (CG) images. AR technology provides a virtual CG image on top of a real object image. MR technology is a CG technology that combines and combines virtual objects into the real world. MR technology is similar to AR technology in that they show real and virtual objects together. However, there is a difference in that in AR technology, virtual objects are used as complementary forms to real objects, while in MR technology, virtual objects and real objects are used as equal personalities.

NR supports multiples numerologies (and/or multiple subcarrier spacings (SCS)) to support various 5G services. For example, if SCS is 15 kHz, wide area can be supported in traditional cellular bands, and if SCS is 30 kHz/60 kHz, dense-urban, lower latency, and wider carrier bandwidth can be supported. If SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.

The NR frequency band may be defined as two types of frequency range, i.e., FR1 and FR2. The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 1 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean "sub 6 GHz range", FR2 may mean "above 6 GHz range," and may be referred to as millimeter wave (mmW).

As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410MHz to 7125MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).

Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include narrowband internet-of-things (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of low power wide area network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and/or LTE Cat NB2, and may not be limited to the above-mentioned names. Additionally and/or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented in at least one of the various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M, and may not be limited to the above-mentioned names. Additionally and/or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may include at least one of ZigBee, Bluetooth, and/or LPWAN which take into account low-power communication, and may not be limited to the above-mentioned names. For example, ZigBee technology may generate personal area networks (PANs) associated with small/low-power digital communication based on various specifications such as IEEE 802.15.4 and may be called various names.

Referring to FIG. 2, a first wireless device 100 and a second wireless device 200 may transmit/receive radio signals to/from an external device through a variety of RATs (e.g., LTE and NR).

In FIG. 2, {the first wireless device 100 and the second wireless device 200} may correspond to at least one of {the wireless device 100a to 100f and the BS 200}, {the wireless device 100a to 100f and the wireless device 100a to 100f} and/or {the BS 200 and the BS 200} of FIG. 1.

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

The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. It is exemplarily shown in FIG. 2 that the memory 104 is included in the processing chip 101. Additional and/or alternatively, the memory 104 may be placed outside of the processing chip 101.

The processor 102 may control the memory 104 and/or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor 102 may process information within the memory 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver 106. The processor 102 may receive radio signals including second information/signals through the transceiver 106 and then store information obtained by processing the second information/signals in the memory 104.

The memory 104 may be operably connectable to the processor 102. The memory 104 may store various types of information and/or instructions. The memory 104 may store a software code 105 which implements instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 105 may control the processor 102 to perform one or more protocols. For example, the software code 105 may control the processor 102 to perform one or more layers of the radio interface protocol.

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

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

The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. It is exemplarily shown in FIG. 2 that the memory 204 is included in the processing chip 201. Additional and/or alternatively, the memory 204 may be placed outside of the processing chip 201.

The processor 202 may control the memory 204 and/or the transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor 202 may process information within the memory 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver 206. The processor 202 may receive radio signals including fourth information/signals through the transceiver 106 and then store information obtained by processing the fourth information/signals in the memory 204.

The memory 204 may be operably connectable to the processor 202. The memory 204 may store various types of information and/or instructions. The memory 204 may store a software code 205 which implements instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may control the processor 202 to perform one or more protocols. For example, the software code 205 may control the processor 202 to perform one or more layers of the radio interface protocol.

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

Hereinafter, hardware elements of the

wireless devices

100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or

more processors

102 and 202. For example, the one or

more processors

102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer). The one or

more processors

102 and 202 may generate one or more protocol data units (PDUs) and/or one or more service data unit (SDUs) according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The one or

more processors

102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The one or

more processors

102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or

more transceivers

106 and 206. The one or

more processors

102 and 202 may receive the signals (e.g., baseband signals) from the one or

more transceivers

106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.

The one or

more processors

102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or

more processors

102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or

more processors

102 and 202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be included in the one or

more processors

102 and 202 or stored in the one or

more memories

104 and 204 so as to be driven by the one or

more processors

102 and 202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and/or a set of commands.

The one or

more memories

104 and 204 may be connected to the one or

more processors

102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or

more memories

104 and 204 may be configured by read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or

more memories

104 and 204 may be located at the interior and/or exterior of the one or

more processors

102 and 202. The one or

more memories

104 and 204 may be connected to the one or

more processors

102 and 202 through various technologies such as wired or wireless connection.

The one or

more transceivers

106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or

more transceivers

106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or

more transceivers

106 and 206 may be connected to the one or

more processors

102 and 202 and transmit and receive radio signals. For example, the one or

more processors

102 and 202 may perform control so that the one or

more transceivers

106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or

more processors

102 and 202 may perform control so that the one or

more transceivers

106 and 206 may receive user data, control information, or radio signals from one or more other devices.

The one or

more transceivers

106 and 206 may be connected to the one or

more antennas

108 and 208 and the one or

more transceivers

106 and 206 may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, through the one or

more antennas

108 and 208. In the present disclosure, the one or

more antennas

108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

The one or

more transceivers

106 and 206 may convert received user data, control information, radio signals/channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc., using the one or

more processors

102 and 202. The one or

more transceivers

106 and 206 may convert the user data, control information, radio signals/channels, etc., processed using the one or

more processors

102 and 202 from the base band signals into the RF band signals. To this end, the one or

more transceivers

106 and 206 may include (analog) oscillators and/or filters. For example, the one or

more transceivers

106 and 206 can up-convert OFDM baseband signals to OFDM signals by their (analog) oscillators and/or filters under the control of the one or

more processors

102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The one or

more transceivers

106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and/or filters under the control of the one or

more processors

102 and 202.

In the implementations of the present disclosure, a UE may operate as a transmitting device in uplink (UL) and as a receiving device in downlink (DL). In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device 100 acts as the UE, and the second wireless device 200 acts as the BS. For example, the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be configured to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior according to an implementation of the present disclosure. The processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be configured to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.

In the present disclosure, a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB.

The wireless device may be implemented in various forms according to a use-case/service (refer to FIG. 1).

Referring to FIG. 3,

wireless devices

100 and 200 may correspond to the

wireless devices

100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules. For example, each of the

wireless devices

100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit 110 may include a communication circuit 112 and transceiver(s) 114. For example, the communication circuit 112 may include the one or

more processors

102 and 202 of FIG. 2 and/or the one or

more memories

104 and 204 of FIG. 2. For example, the transceiver(s) 114 may include the one or

more transceivers

106 and 206 of FIG. 2 and/or the one or

more antennas

108 and 208 of FIG. 2. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140 and controls overall operation of each of the

wireless devices

100 and 200. For example, the control unit 120 may control an electric/mechanical operation of each of the

wireless devices

100 and 200 based on programs/code/commands/information stored in the memory unit 130. The control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface or store, in the memory unit 130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit 110.

The additional components 140 may be variously configured according to types of the

wireless devices

100 and 200. For example, the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit (e.g., audio I/O port, video I/O port), a driving unit, and a computing unit. The

wireless devices

100 and 200 may be implemented in the form of, without being limited to, the robot (100a of FIG. 1), the vehicles (100b-1 and 100b-2 of FIG. 1), the XR device (100c of FIG. 1), the hand-held device (100d of FIG. 1), the home appliance (100e of FIG. 1), the IoT device (100f of FIG. 1), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a FinTech device (or a finance device), a security device, a climate/environment device, the AI server/device (400 of FIG. 1), the BSs (200 of FIG. 1), a network node, etc. The

wireless devices

100 and 200 may be used in a mobile or fixed place according to a use-example/service.

In FIG. 3, the entirety of the various elements, components, units/portions, and/or modules in the

wireless devices

100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the

wireless devices

100 and 200, the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit/portion, and/or module within the

wireless devices

100 and 200 may further include one or more elements. For example, the control unit 120 may be configured by a set of one or more processors. As an example, the control unit 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory unit 130 may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.

Referring to FIG. 4, a UE 100 may correspond to the first wireless device 100 of FIG. 2 and/or the

wireless device

100 or 200 of FIG. 3.

A UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 110, a battery 112, a display 114, a keypad 116, a subscriber identification module (SIM) card 118, a speaker 120, and a microphone 122.

The processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The processor 102 may be configured to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include ASIC, other chipset, logic circuit and/or data processing device. The processor 102 may be an application processor. The processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator). An example of the processor 102 may be found in SNAPDRAGON^TM series of processors made by Qualcomm^®, EXYNOS^TM series of processors made by Samsung^®, A series of processors made by Apple^®, HELIO^TM series of processors made by MediaTek^®, ATOM^TM series of processors made by Intel^® or a corresponding next generation processor.

The memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102. The memory 104 may include ROM, RAM, flash memory, memory card, storage medium and/or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The modules can be stored in the memory 104 and executed by the processor 102. The memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.

The transceiver 106 is operatively coupled with the processor 102, and transmits and/or receives a radio signal. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include baseband circuitry to process radio frequency signals. The transceiver 106 controls the one or more antennas 108 to transmit and/or receive a radio signal.

The power management module 110 manages power for the processor 102 and/or the transceiver 106. The battery 112 supplies power to the power management module 110.

The display 114 outputs results processed by the processor 102. The keypad 116 receives inputs to be used by the processor 102. The keypad 116 may be shown on the display 114.

The SIM card 118 is an　integrated circuit　that is intended to　securely store the　international mobile subscriber identity　(IMSI) number and its related　key, which are used to identify and authenticate subscribers on　mobile telephony　devices (such as　mobile phones　and　computers). It is also possible to store contact information on many SIM cards.

The speaker 120 outputs sound-related results processed by the processor 102. The microphone 122 receives sound-related inputs to be used by the processor 102.

In particular, FIG. 5 illustrates an example of a radio interface user plane protocol stack between a UE and a BS and FIG. 6 illustrates an example of a radio interface control plane protocol stack between a UE and a BS. The control plane refers to a path through which control messages used to manage call by a UE and a network are transported. The user plane refers to a path through which data generated in an application layer, for example, voice data or Internet packet data are transported. Referring to FIG. 5, the user plane protocol stack may be divided into Layer 1 (i.e., a PHY layer) and Layer 2. Referring to FIG. 6, the control plane protocol stack may be divided into Layer 1 (i.e., a PHY layer), Layer 2, Layer 3 (e.g., an RRC layer), and a non-access stratum (NAS) layer. Layer 1, Layer 2 and Layer 3 are referred to as an access stratum (AS).

In the 3GPP LTE system, the Layer 2 is split into the following sublayers: MAC, RLC, and PDCP. In the 3GPP NR system, the Layer 2 is split into the following sublayers: MAC, RLC, PDCP and SDAP. The PHY layer offers to the MAC sublayer transport channels, the MAC sublayer offers to the RLC sublayer logical channels, the RLC sublayer offers to the PDCP sublayer RLC channels, the PDCP sublayer offers to the SDAP sublayer radio bearers. The SDAP sublayer offers to 5G core network quality of service (QoS) flows.

In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing/de-multiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels; scheduling information reporting; error correction through hybrid automatic repeat request (HARQ) (one HARQ entity per cell in case of carrier aggregation (CA)); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of one UE by means of logical channel prioritization; padding. A single MAC entity may support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritization control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use.

Different kinds of data transfer services are offered by MAC. To accommodate different kinds of data transfer services, multiple types of logical channels are defined, i.e., each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for the transfer of control plane information only, and traffic channels are used for the transfer of user plane information only. Broadcast control channel (BCCH) is a downlink logical channel for broadcasting system control information, paging control channel (PCCH) is a downlink logical channel that transfers paging information, system information change notifications and indications of ongoing public warning service (PWS) broadcasts, common control channel (CCCH) is a logical channel for transmitting control information between UEs and network and used for UEs having no RRC connection with the network, and dedicated control channel (DCCH) is a point-to-point bi-directional logical channel that transmits dedicated control information between a UE and the network and used by UEs having an RRC connection. Dedicated traffic channel (DTCH) is a point-to-point logical channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. In downlink, the following connections between logical channels and transport channels exist: BCCH can be mapped to broadcast channel (BCH); BCCH can be mapped to downlink shared channel (DL-SCH); PCCH can be mapped to paging channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In uplink, the following connections between logical channels and transport channels exist: CCCH can be mapped to uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

The RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged node (AM). The RLC configuration is per logical channel with no dependency on numerologies and/or transmission durations. In the 3GPP NR system, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper layer PDUs; sequence numbering independent of the one in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDU (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).

In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using robust header compression (ROHC); transfer of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in case of split bearers); retransmission of PDCP SDUs; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; duplication of PDCP PDUs and duplicate discard indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-order delivery; duplication of PDCP PDUs and duplicate discard indication to lower layers.

In the 3GPP NR system, the main services and functions of SDAP include: mapping between a QoS flow and a data radio bearer; marking QoS flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each individual PDU session.

In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance and release of an RRC connection between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS message transfer to/from NAS from/to UE.

Referring to FIG. 7, a gNB may include a gNB-CU (hereinafter, gNB-CU may be simply referred to as CU) and at least one gNB-DU (hereinafter, gNB-DU may be simply referred to as DU).

The gNB-CU is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or an RRC and PDCP protocols of the en-gNB. The gNB-CU controls the operation of the at least one gNB-DU.

The gNB-DU is a logical node hosting RLC, MAC, and physical layers of the gNB or the en-gNB. The operation of the gNB-DU is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU.

The gNB-CU and gNB-DU are connected via an F1 interface. The gNB-CU terminates the F1 interface connected to the gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. One gNB-DU is connected to only one gNB-CU. However, the gNB-DU may be connected to multiple gNB-CUs by appropriate implementation. The F1 interface is a logical interface. For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For E-UTRAN-NR dual connectivity (EN-DC), the S1-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

Functions of the F1 interface includes F1 control (F1-C) functions as follows.

(1) F1 interface management function

The error indication function is used by the gNB-DU or gNB-CU to indicate to the gNB-CU or gNB-DU that an error has occurred.

The reset function is used to initialize the peer entity after node setup and after a failure event occurred. This procedure can be used by both the gNB-DU and the gNB-CU.

The F1 setup function allows to exchange application level data needed for the gNB-DU and gNB-CU to interoperate correctly on the F1 interface. The F1 setup is initiated by the gNB-DU.

The gNB-CU configuration update and gNB-DU configuration update functions allow to update application level configuration data needed between gNB-CU and gNB-DU to interoperate correctly over the F1 interface, and may activate or deactivate cells.

The F1 setup and gNB-DU configuration update functions allow to inform the single network slice selection assistance information (S-NSSAI) supported by the gNB-DU.

The F1 resource coordination function is used to transfer information about frequency resource sharing between gNB-CU and gNB-DU.

(2) System Information management function

Scheduling of system broadcast information is carried out in the gNB-DU. The gNB-DU is responsible for transmitting the system information according to the scheduling parameters available.

The gNB-DU is responsible for the encoding of NR master information block (MIB). In case broadcast of system information block type-1 (SIB1) and other SI messages is needed, the gNB-DU is responsible for the encoding of SIB1 and the gNB-CU is responsible for the encoding of other SI messages.

(3) F1 UE context management function

The F1 UE context management function supports the establishment and modification of the necessary overall UE context.

The establishment of the F1 UE context is initiated by the gNB-CU and accepted or rejected by the gNB-DU based on admission control criteria (e.g., resource not available).

The modification of the F1 UE context can be initiated by either gNB-CU or gNB-DU. The receiving node can accept or reject the modification. The F1 UE context management function also supports the release of the context previously established in the gNB-DU. The release of the context is triggered by the gNB-CU either directly or following a request received from the gNB-DU. The gNB-CU request the gNB-DU to release the UE Context when the UE enters RRC_IDLE or RRC_INACTIVE.

This function can be also used to manage DRBs and SRBs, i.e., establishing, modifying and releasing DRB and SRB resources. The establishment and modification of DRB resources are triggered by the gNB-CU and accepted/rejected by the gNB-DU based on resource reservation information and QoS information to be provided to the gNB-DU. For each DRB to be setup or modified, the S-NSSAI may be provided by gNB-CU to the gNB-DU in the UE context setup procedure and the UE context modification procedure.

The mapping between QoS flows and radio bearers is performed by gNB-CU and the granularity of bearer related management over F1 is radio bearer level. For NG-RAN, the gNB-CU provides an aggregated DRB QoS profile and QoS flow profile to the gNB-DU, and the gNB-DU either accepts the request or rejects it with appropriate cause value. To support packet duplication for intra-gNB-DU carrier aggregation (CA), one data radio bearer should be configured with two GPRS tunneling protocol (GTP)-U tunnels between gNB-CU and a gNB-DU.

With this function, gNB-CU requests the gNB-DU to setup or change of the special cell (SpCell) for the UE, and the gNB-DU either accepts or rejects the request with appropriate cause value.

With this function, the gNB-CU requests the setup of the secondary cell(s) (SCell(s)) at the gNB-DU side, and the gNB-DU accepts all, some or none of the SCell(s) and replies to the gNB-CU. The gNB-CU requests the removal of the SCell(s) for the UE.

(4) RRC message transfer function

This function allows to transfer RRC messages between gNB-CU and gNB-DU. RRC messages are transferred over F1-C. The gNB-CU is responsible for the encoding of the dedicated RRC message with assistance information provided by gNB-DU.

(5) Paging function

The gNB-DU is responsible for transmitting the paging information according to the scheduling parameters provided.

The gNB-CU provides paging information to enable the gNB-DU to calculate the exact paging occasion (PO) and paging frame (PF). The gNB-CU determines the paging assignment (PA). The gNB-DU consolidates all the paging records for a particular PO, PF and PA, and encodes the final RRC message and broadcasts the paging message on the respective PO, PF in the PA.

(6) Warning messages information transfer function

This function allows to cooperate with the warning message transmission procedures over NG interface. The gNB-CU is responsible for encoding the warning related SI message and sending it together with other warning related information for the gNB-DU to broadcast over the radio interface.

A transport network layer (TNL) is based on Internet protocol (IP) transport, comprising a stream control transmission protocol (SCTP) layer on top of the IP layer. An application layer signaling protocol is referred to as an F1 application protocol (E1AP).

Hereinafter, technical features related to Setup operations are described. Sections of 3GPP TS 38.413 v17.5.0 and 3GPP TS 38.423 v17.5.0 may be referred.

The purpose of the PDU Session Resource Setup procedure is to assign resources on Uu and NG-U for one or several PDU sessions and the corresponding QoS flows, and to setup corresponding DRBs for a given UE. The procedure uses UE-associated signalling.

The AMF initiates the procedure by sending a PDU SESSION RESOURCE SETUP REQUEST message to the NG-RAN node.

The PDU SESSION RESOURCE SETUP REQUEST message shall contain the information required by the NG-RAN node to setup the PDU session related NG-RAN configuration consisting of at least one PDU session resource and include each PDU session resource to setup in the PDU Session Resource Setup Request List IE.

Upon reception of the PDU SESSION RESOURCE SETUP REQUEST message, if resources are available for the requested configuration, the NG-RAN node shall execute the requested NG-RAN configuration and allocate associated resources over NG and over Uu for each PDU session listed in the PDU Session Resource Setup Request List IE.

If the RAN Paging Priority IE is included in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node may use it to determine a priority for paging the UE in RRC_INACTIVE state.

For each requested PDU session, if resources are available for the requested configuration, the NG-RAN node shall establish at least one DRB and associate each accepted QoS flow of the PDU session which is not associated with an MBS QoS flow to a DRB established.

For each PDU session successfully established the NG-RAN node shall pass to the UE the PDU Session NAS- PDU IE, if included. The NG-RAN node shall not send to the UE the PDU Session NAS PDUs associated to the failed PDU sessions.

If the NAS- PDU IE is included in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall pass it to the UE.

For each PDU session the NG-RAN node shall store the UL NG -U UP TNL Information IE included in the PDU Session Resource Setup Request Transfer IE contained in the PDU SESSION RESOURCE SETUP REQUEST message and use it as the uplink termination point for the user plane data for this PDU session.

Interactions with Handover Preparation procedure:

If a handover becomes necessary during the PDU Session Resource Setup procedure, the NG-RAN node may interrupt the ongoing PDU Session Resource Setup procedure and initiate the Handover Preparation procedure as follows:

1. The NG-RAN node shall send the PDU SESSION RESOURCE SETUP RESPONSE message in which the NG-RAN node shall indicate, if necessary, all the PDU session resources which failed to be setup with an appropriate cause value, e.g. "NG intra-system handover triggered", "NG inter-system handover triggered" or "Xn handover triggered".

2. The NG-RAN node shall trigger the handover procedure.

The purpose of the Initial Context Setup procedure is to establish the necessary overall initial UE context at the NG-RAN node, when required, including PDU session context, the Security Key, Mobility Restriction List, UE Radio Capability and UE Security Capabilities, etc. The AMF may initiate the Initial Context Setup procedure if a UE-associated logical NG-connection exists for the UE or if the AMF has received the RAN UE NGAP ID IE in an INITIAL UE MESSAGE message or if the NG-RAN node has already initiated a UE-associated logical NG-connection by sending an INITIAL UE MESSAGE message via another NG interface instance. The procedure uses UE-associated signalling.

For signalling only connections and if the UE Context Request IE is not received in the Initial UE Message, the AMF may be configured to trigger the procedure for all NAS procedures or on a per NAS procedure basis depending on operator's configuration.

In case of the establishment of a PDU session the 5GC shall be prepared to receive user data before the INITIAL CONTEXT SETUP RESPONSE message has been received by the AMF. If no UE-associated logical NG-connection exists, the UE-associated logical NG-connection shall be established at reception of the INITIAL CONTEXT SETUP REQUEST message.

The INITIAL CONTEXT SETUP REQUEST message shall contain the Index to RAT/Frequency Selection Priority IE, if available in the AMF.

If the NAS- PDU IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall pass it transparently towards the UE.

If the Masked IMEISV IE is contained in the INITIAL CONTEXT SETUP REQUEST message the target NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling.

Upon receipt of the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall

- attempt to execute the requested PDU session configuration;

- store the received UE Aggregate Maximum Bit Rate in the UE context, and use the received UE Aggregate Maximum Bit Rate for Non-GBR QoS flows for the concerned UE;

- store the received Mobility Restriction List in the UE context;

- store the received UE Radio Capability in the UE context;

- store the received Index to RAT/Frequency Selection Priority in the UE context and use it;

- store the received UE Security Capabilities in the UE context;

- store the received Security Key in the UE context and, if the NG-RAN node is required to activate security for the UE, take this security key into use;

- if supported, store the received SRVCC Operation Possible in the UE context and use it;

- store the received NR V2X Services Authorization information, if supported, in the UE context;

- store the received LTE V2X Services Authorization information, if supported, in the UE context;

- store the received NR UE Sidelink Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE's sidelink communication in network scheduled mode for NR V2X services;

- store the received LTE UE Sidelink Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE's sidelink communication in network scheduled mode for LTE V2X services;

- store the received PC5 QoS Parameters, if supported, in the UE context and use it;

- store the received Management Based MDT PLMN List information, if supported, in the UE context;

- if supported, store the received IAB Authorization information in the UE context, and use it accordingly for the IAB-MT;

- store the received 5G ProSe Authorization information in the UE context, if supported, and use it for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services;

- store the 5G ProSe UE PC5 Aggregate Maximum Bit Rate in the UE context, if supported, and use it for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services;

- store the 5G ProSe PC5 QoS Parameters, if supported, in the UE context and use it.

Interactions with Initial UE Message procedure:

The NG-RAN node shall use the AMF UE NGAP ID IE and RAN UE NGAP ID IE received in the INITIAL CONTEXT SETUP REQUEST message as identification of the logical connection even if the RAN UE NGAP ID IE had been allocated in an INITIAL UE MESSAGE message sent over a different NG interface instance.

Interactions with RRC Inactive Transition Report procedure:

If the RRC Inactive Transition Report Request IE is included in the INITIAL CONTEXT SETUP REQUEST message and set to "subsequent state transition report", the NG-RAN node shall, if supported, send the RRC INACTIVE TRANSITION REPORT message to the AMF to report the RRC state of the UE when the UE enters or leaves RRC_INACTIVE state.

The purpose of the NG Setup procedure is to exchange application level data needed for the NG-RAN node and the AMF to correctly interoperate on the NG-C interface. This procedure shall be the first NGAP procedure triggered after the TNL association has become operational. The procedure uses non-UE associated signalling.

This procedure erases any existing application level configuration data in the two nodes, replaces it by the one received and clears AMF overload state information at the NG-RAN node. If the NG-RAN node and AMF do not agree on retaining the UE contexts this procedure also re-initialises the NGAP UE-related contexts (if any) and erases all related signalling connections in the two nodes like an NG Reset procedure would do.

The NG-RAN node initiates the procedure by sending an NG SETUP REQUEST message including the appropriate data to the AMF. The AMF responds with an NG SETUP RESPONSE message including the appropriate data.

If the Configured TAC Indication IE set to "true" is included for a Tracking Area contained in the Supported TA List IE in the NG SETUP REQUEST message, the AMF may take it into account to optimise NG-C signalling towards this NG-RAN node.

If the UE Retention Information IE set to "ues-retained" is included in the NG SETUP REQUEST message, the AMF may accept the proposal to retain the existing UE related contexts and signalling connections by including the UE Retention Information IE set to "ues-retained" in the NG SETUP RESPONSE message.

If the AMF supports IAB, the AMF shall include the IAB Supported IE in the NG SETUP RESPONSE message. If the IAB Supported IE is included in the NG SETUP RESPONSE message, the NG-RAN node shall, if supported, store this information and use it for further AMF selection for the IAB-MT.

The AMF shall include the Backup AMF Name IE, if available, in the Served GUAMI List IE in the NG SETUP RESPONSE message. The NG-RAN node shall, if supported, consider the AMF as indicated by the Backup AMF Name IE when performing AMF reselection.

The purpose of the AMF Configuration Update procedure is to update application level configuration data needed for the NG-RAN node and AMF to interoperate correctly on the NG-C interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non UE-associated signalling.

The AMF initiates the procedure by sending an AMF CONFIGURATION UPDATE message including the appropriate updated configuration data to the NG-RAN node. The NG-RAN node responds with an AMF CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. Unless stated otherwise, if an information element is not included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall interpret that the corresponding configuration data is not changed and shall continue to operate the NG-C interface with the existing related configuration data.

If the PLMN Support List IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall overwrite the whole list of supported PLMN/SNPN Identities and the corresponding list of AMF slices and, if present, other associated information for each PLMN/SNPN Identity and use the received values for further network slice selection and AMF selection.

If the AMF TNL Association to Add List IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall, if supported, use it to establish the TNL association(s) with the AMF. If the AMF TNL Association to Add List IE is included in the AMF CONFIGURATION UPDATE message, and if the AMF TNL Association Address IE does not include the Port Number IE, the NG-RAN node shall assume that port number value 38412 is used for the endpoint. The NG-RAN node shall report to the AMF, in the AMF CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the AMF as follows:

- A list of successfully established TNL associations shall be included in the AMF TNL Association Setup List IE;

- A list of TNL associations that failed to be established shall be included in the AMF TNL Association Failed to Setup List IE.

If the AMF CONFIGURATION UPDATE message includes the AMF TNL Association to Remove List IE, the NG-RAN node shall, if supported, initiate removal of the TNL association(s) indicated by AMF TNL endpoint(s) and NG-RAN node TNL endpoint(s) if the TNL Association Transport Layer Address NG -RAN IE is present, or the TNL association(s) indicated by AMF TNL endpoint(s) if the TNL Association Transport Layer Address NG -RAN IE is absent:

- if the received AMF TNL Association Address IE includes the Port Number IE, the AMF TNL endpoint is identified by the Endpoint IP Address IE and the Port Number IE. Otherwise, the AMF TNL endpoints correspond to all AMF TNL endpoints identified by the Endpoint IP Address IE and any port number(s).

- if the received TNL Association Transport Layer Address NG -RAN IE includes the Port Number IE, the NG-RAN node TNL endpoint is identified by the Endpoint IP Address IE and the Port Number IE. Otherwise, the NG-RAN node TNL endpoints correspond to all NG-RAN node TNL endpoints identified by the Endpoint IP Address IE and any port number(s).

This procedure is used to establish necessary resources in an NG-RAN node for an incoming handover. If the procedure concerns a conditional handover, parallel transactions are allowed. Possible parallel requests are identified by the target cell ID when the source UE AP IDs are the same.

The procedure uses UE-associated signalling.

The source NG-RAN node initiates the procedure by sending the HANDOVER REQUEST message to the target NG-RAN node. When the source NG-RAN node sends the HANDOVER REQUEST message, it shall start the timer TXn_RELOCprep _.

If the Conditional Handover Information Request IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall consider that the request concerns a conditional handover and shall include the Conditional Handover Information Acknowledge IE in the HANDOVER REQUEST ACKNOWLEDGE message.

If the Target NG -RAN node UE XnAP ID IE is contained in the Conditional Handover Information Request IE included in the HANDOVER REQUEST message, then the target NG-RAN node shall remove the existing prepared conditional HO identified by the Target NG -RAN node UE XnAP ID IE and the Target Cell Global ID IE. It is up to the implementation of the target NG-RAN node when to remove the HO information.

Upon reception of the HANDOVER REQUEST ACKNOWLEDGE message, the source NG-RAN node shall stop the timer TXn_RELOCprep and terminate the Handover Preparation procedure. If the procedure was initiated for an immediate handover, the source NG-RAN node shall start the timer TXn_RELOCoverall. The source NG-RAN node is then defined to have a Prepared Handover for that Xn UE-associated signalling.

For each E- RAB ID IE included in the QoS Flow To Be Setup List IE in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store the content of the IE in the UE context and use it for subsequent inter-system handover.

If the Masked IMEISV IE is contained in the HANDOVER REQUEST message the target NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling.

At reception of the HANDOVER REQUEST message the target NG-RAN node shall prepare the configuration of the AS security relation between the UE and the target NG-RAN node by using the information in the UE Security Capabilities IE and the AS Security Information IE in the UE Context Information IE.

Upon reception of the PDU Session Resource Setup List IE, contained in the HANDOVER REQUEST message, the target NG-RAN node shall behave the same for the PDU Session Resource Setup procedure. The target NG-RAN node shall report in the HANDOVER REQUEST ACKNOWLEDGE message the successful establishment of the result for all the requested PDU session resources. When the target NG-RAN node reports the unsuccessful establishment of a PDU session resource, the cause value should be precise enough to enable the source NG-RAN node to know the reason for the unsuccessful establishment.

This procedure is used by an NG-RAN node to request the reporting of load measurements to another NG-RAN node.

The procedure uses non UE-associated signalling.

NG-RAN node₁ initiates the procedure by sending the RESOURCE STATUS REQUEST message to NG-RAN node₂ to start a measurement, stop a measurement or add cells to report for a measurement. Upon receipt, NG-RAN node₂:

- shall initiate the requested measurement according to the parameters given in the request in case the Registration Request IE set to "start"; or

- shall stop all cells measurements and terminate the reporting in case the Registration Request IE is set to "stop"; or

- shall add cells indicated in the Cell To Report List IE to the measurements initiated before for the given measurement IDs, in case the Registration Request IE is set to "add". If measurements are already initiated for a cell indicated in the Cell To Report List IE, this information shall be ignored.

If the Registration Request IE is set to "start" in the RESOURCE STATUS REQUEST message and the Report Characteristics IE indicates cell specific measurements, the Cell To Report List IE shall be included.

If Registration Request IE is set to "add" in the RESOURCE STATUS REQUEST message, the Cell To Report List IE shall be included.

If NG-RAN node₂ is capable to provide all requested resource status information, it shall initiate the measurement as requested by NG-RAN node₁ and respond with the RESOURCE STATUS RESPONSE message.

Interaction with other procedures

When starting a measurement, the Report Characteristics IE in the RESOURCE STATUS REQUEST indicates the type of objects NG-RAN node₂ shall perform measurements on. For each cell, NG-RAN node₂ shall include in the RESOURCE STATUS UPDATE message:

- the Radio Resource Status IE, if the first bit, "PRB Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1". If NG-RAN node₂ is a gNB and if the cell for which Radio Resource Status IE is requested to be reported supports more than one SSB, the Radio Resource Status IE for such cell shall include the SSB Area Radio Resource Status Item IE for all SSB areas supported by the cell. If the SSB To Report List IE is included for a cell, the Radio Resource Status IE for such cell shall include the requested SSB Area Radio Resource Status List IE; If the cell for which Radio Resource Status IE is requested to be reported supports more than one slice, and if the Slice To Report List IE is included for a cell, the Radio Resource Status IE for such cell shall, if supported, include the requested Slice Radio Resource Status Item IE;

- the TNL Capacity Indicator IE, if the second bit, "TNL Capacity Ind Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1". The received TNL Capacity Indicator IE represents the lowest TNL capacity available for the cell, only taking into account interfaces providing user plane transport.

- the Composite Available Capacity Group IE, if the third bit, "Composite Available Capacity Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1". If the Cell Capacity Class Value IE is included within the Composite Available Capacity Group IE, this IE is used to assign weights to the available capacity indicated in the Capacity Value IE. If NG-RAN node₂ is a gNB and if the cell for which Composite Available Capacity Group IE is requested to be reported supports more than one SSB, the Composite Available Capacity Group IE for such cell shall include the SSB Area Capacity Value List for all SSB areas supported by the cell, providing the SSB area capacity with respect to the Cell Capacity Class Value. If the SSB To Report List IE is included for a cell, the Composite Available Capacity Group IE for such cell shall include the requested SSB Area Capacity Value List IE.

If the cell for which Composite Available Capacity Group IE is requested to be reported supports more than one slice, and if the Slice To Report List IE is included for a cell, the Slice Available Capacity IE for such cell shall include the requested Slice Available Capacity Value Downlink IE and Slice Available Capacity Value Uplink IE, providing the slice capacity with respect to the Cell Capacity Class Value.

- the Number of Active UEs IE, if the fourth bit, "Number of Active UEs Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1";

- the RRC Connections IE, if the fifth bit, "RRC Connections Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1".

- the NR -U Channel List IE, if the sixth bit, "NR-U Channel List Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1".

If the Reporting Periodicity IE in the RESOURCE STATUS REQUEST is present, this indicates the periodicity for the reporting of periodic measurements. the NG-RAN node₂ shall report only once, unless otherwise requested within the Reporting Periodicity IE.

NG-RAN node₂ shall report the results of the admitted measurements in RESOURCE STATUS UPDATE message. The admitted measurements are the measurements that were successfully initiated during the preceding Resource Status Reporting Initiation procedure.

If some results of the admitted measurements in RESOURCE STATUS UPDATE message are missing, NG-RAN node₁ shall consider that these results were not available at NG-RAN node₂.

Meanwhile, in NR, use cases and service requirements are being developed in relation to providing services considering energy efficiency. These use cases and service requirements are described in "Study on Energy Efficiency as a service criteria" in 3GPP documents (e.g. TR 22.882).

For example, a use case on energy consumption as a performance criteria for best effort communication is described.

Currently energy consumption and efficiency can be monitored and considered through O&M and network operation, but not as a service performance criterion, as for example bit rate, latency or availability. Guidance from SA to all working groups in states:

"The EE -specific efforts so far undertaken e.g., in SA5 have aimed mostly at improving the energy efficiency by impacting the operations of the system. As we now are starting to specify the 5G-Advanced features, TSG SA kindly requests the recipient WGs and TSGs to consider EE even more as a guiding principle when developing new solutions and evolving the 3GPP systems specification, in addition to the other established principles of 3GPP system design.

TSG SA clarifies that in addition to EE , other system level criteria shall continue to be met (i.e. the energy efficiency aspects of a solution defined in 3GPP is not to be interpreted to take priority or to be alternative to security, privacy, complexity etc. and to meeting the requirements and performance targets of the specific feature(s) the solution addresses)."

There is an important type of traffic where energy efficiency policy, for example a maximum amount of energy to be utilized could be applied without conflict with this guidance. Best effort traffic is a type of traffic that is provided as a service to customers everything else being equal. Of course, security, privacy and complexity principles will not be sacrificed, but there is no conflict between a service policy that constrains performance (e.g. latency, throughput, even availability) on the basis of energy consumption and a best effort service, since there are no guarantees in the case of best effort traffic. We can say that best effort traffic is not associated with QoS policy service performance level criteria.

Today the 5G system works to support services efficiently, though does not take into account energy consumption at the service level. The use case explores a particular opportunity to identify this information and use it to make more efficient use of all network resources without sacrificing service quality. In particular, information gathered through O&M, and in the future possibly from the network (see 5.1.5 which identifies a gap and opportunity), can be leveraged to make it possible to employ energy consumption information as part of service delivery.

In the following use case, the possibility of using energy consumption as a new service criterion for this less constrained type of mobile telecommunication service is explored.

A large-scale logistics company L has deployed a large number of communicating components. These are integrated into vehicles, palettes, facilities, etc. Essentially, IoT terminals enable remote tracking and monitoring functions. The information gathered is relevant, but not constrained with respect to latency. In fact, eventual delivery (e.g. after hours or even a full day) of communication is entirely acceptable for L. The MNO M offers a 'green service' which limits the rate of energy utilized for communication over a particular time interval (e.g. per day) and this service is appropriate for L, whose overall corporate goals are also served by 'green service,' as they strive to operate with energy efficiency.

In this scenario, a service provider monitors events resulting from energy consumption policy triggers in the 5G system. These triggers correspond to monitoring policy in the 5G system as well as energy enforcement policies.

In FIG. 16, the application server AS obtains information corresponding to the energy consequences of a UE 'A' served by the 5G network.

This use case will provide a description of a scenario in which the service provider (who operates an application server) cares about energy consumption in the 5G system as a result of the service to UE A. This could be for 3 reasons:

- the service provider needs to show they are saving energy;

- the service has an associated energy cost, and the service provider wants to reduce it. This is analogous to the use of industrial or consumer electronics when energy rates are lower, and also as an incentive to operate more efficiently;

- the service provider recognizes that there are policies that limit energy use (such as aggregate energy use of a slice) and controls the overall use of the service to operate within those constraints.

The use case introduces five new concepts related to new energy events and energy event monitoring:

a) the ability for the network operator to create a 'maximum energy credit' policy, after which services are gated;

b) the ability for the network operator to inform an AS of the 'maximum energy credit expired' event;

c) the ability for the 5G system to calculate 'energy credit' use;

d) the ability to monitor and provide to the AS the use of 'energy credits' (or other energy 'quantum');

e) the support a new policy that establishes the energy consequence for charging control - either charging for use of energy or establishing an 'energy credit limit' for enforcement by the 5G system.

Hereinafter, a method for operations considering energy consumption in a wireless network system, according to some embodiments of the present disclosure, will be described with reference to the following drawings.

The following drawings are created to explain specific embodiments of the present disclosure. The names of the specific devices or the names of the specific signals/messages/fields shown in the drawings are provided by way of example, and thus the technical features of the present disclosure are not limited to the specific names used in the following drawings. Herein, a wireless device may be referred to as a user equipment (UE).

In particular, FIG. 17 shows an example of a method performed by a first Radio Access Network (RAN) node.

In step S1701, the first RAN node may receive, from an Access and Mobility management Function (AMF), a first message including an energy efficiency configuration.

For example, the energy efficiency configuration may include an energy consumption threshold per network slice and/or per wireless device.

In step S1702, the first RAN node may monitor energy consumption for a network slice and/or a wireless device.

In step S1703, the first RAN node may transmit, to a second RAN node, a second message requesting a handover.

For example, the handover may be determined based on the monitored energy consumption for the network slice or the wireless device and the energy consumption threshold.

For example, the second message may include a cause value informing that the handover is performed for energy efficiency.

For example, the first RAN node may receive, from the AMF, an Initial Context Setup Request message including (i) a Per Slice Energy Efficiency Policy Applied Authorization and/or (ii) an Energy Efficiency Configuration.

In this case, the second message may include (i) the Per Slice Energy Efficiency Policy Applied Authorization, (ii) the Energy Efficiency Configuration, and/or (iii) the Reporting Indication.

According to some embodiments of the present disclosure, before transmitting the second message requesting the handover, the first RAN node may transmit, to the second RAN node, a Resource Status Request message including indication requesting measurements of Per Slice Energy Consumption Rate. The first RAN node may receive, from the second RAN node, a Resource Status Update message including measurements results of the Per Slice Energy Consumption Rate.

In this case, the handover may be determined by the first RAN node based on the measurements results of the Per Slice Energy Consumption Rate. That is, the first RAN node may determine the handover of the wireless device based on the measurements results of the Per Slice Energy Consumption Rate.

According to some embodiments of the present disclosure, before transmitting the second message requesting the handover, the first RAN node may receive, from the AMF, a Per Slice Reporting Indication. For example, the Per Slice Reporting Indication may be included in the first message.

The first RAN node may transmit, to the AMF, a report including information on energy consumption per slice. For example, the first RAN node may report the energy consumption per slice periodically. For example, the first RAN node may report the energy consumption per slice when the energy consumption per slice reaches a threshold value.

For example, the first RAN node may receive, from the AMF, a Reporting Indication. The Reporting Indication may be included in an Initial Context Setup Request message to establish a UE Context for the wireless device.

The first RAN node may report, to the AMF, energy consumption rate for the wireless device. That is, the first RAN node may report, to the AMF, energy consumption rate per wireless device (or per UE) based on receiving the Reporting Indication.

In this case, the handover may be determined by the AMF based on the energy consumption rate for the wireless device. For example, the handover may be determined by the AMF based on the energy consumption rate per wireless device. Then, the first RAN node may receive, from the AMF, a Mobility Request message for the wireless device.

According to some embodiments of the present disclosure, the wireless device may be is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

In order to control or manage energy efficiency per slice between neighbor base stations, or energy efficiency of a specific UE, at least one wireless device using a specific slice or a specific wireless device may be handed over to a neighbor base station supporting the same slice. In this case, before performing the handover, the source base station can receive, from the AMF, (i) configuration information related to energy efficiency per slice or per wireless device and (ii) information on reporting indication for requesting a report to the AMF. In addition, the source base station can receive the energy consumption rate per slice from the target base station, based on a request from the source base station.

The energy efficiency-related configuration provided at this time may include maximum energy consumption rate and maximum energy credit limit values. Additionally, the reporting indication may include a threshold value or period value for triggering reporting.

Furthermore, a new cause value to indicate that the UE's handover is performed for energy efficiency may be provided at the time of handover from the source base station to the target base station. At this time, configuration and reporting indication related to energy efficiency owned by the source base station may also be provided.

In particular FIG. 18a and FIG. 18b illustrate a method for handover of at least one UE using a specific slice or a specific UE to gNB2 supporting the same slice in order to control or manage the energy efficiency per slice or the energy efficiency of a specific UE in gNB1.

In step S1801, gNB1 sends an NG Setup Request message for NG setup with an AMF.

In step S1802, upon receiving the NG Setup Request, the AMF sends an NG Setup Response message to gNB1 in response.

This message may include Per Slice Energy Efficiency Configuration for gNB1 to control or manage energy usage for each slice.

Per Slice Energy Efficiency Configuration may include slice information (for example, S-NSSAI), Maximum Energy Consumption Rate per slice, and Maximum Energy Credit Limit per slice. Additionally, Per Slice Energy Efficiency Configuration may include information (for example, corresponding to ARP priority level, ARP pre-emption capability, and ARP pre-emption vulnerability) such as slice priority per slice, slice pre-emption capability indicating whether the energy consumption of other slices can be reduced for the energy consumption of the current slice, slice pre-emption vulnerability indicating whether the energy consumption of the current slice can be reduced for the energy consumption of other slices (this can be defined as E-ARP (Energy Allocation and Retention Priority), respectively).

Here, 'Maximum Energy Credit Limit' refers to the maximum upper limit of the amount of energy used to provide to a specific user or the amount of energy used to provide services per user.

Additionally, this message may include Per Slice Reporting Indication to allow gNB1 to report energy usage per slice to AMF.

Reports to AMF can be provided when a certain threshold is crossed, or has been reached. Otherwise, reports to AMF can be provided periodically.

The indication may include slice information and a threshold value or period value for each slice for report trigger.

Additionally, the indication may indicate to include associated UE(s)/user(s) information in the reports when reporting to AMF.

After receiving the NG Setup Response message, gNB1 can store information included in Per Slice Energy Efficiency Configuration and Per Slice Reporting Indication included in the message. If Per Slice Energy Efficiency Configuration and/or Per Slice Reporting Indication changes, changes can be provided using the AMF Configuration Update message.

In step S1803, gNB1 transmits a Resource Status Request message to gNB2, which is a neighbor base station.

This message may include Measurement of Per Slice Energy Consumption Rate to request information on the energy consumption per slice of gNB2. Measurement of Per Slice Energy Consumption Rate may include slice information.

In step S1804, after receiving the request message from gNB1, gNB2 accepts gNB1's request and sends a Resource Status Response message in response.

In step S1805, gNB2 transmits a Resource Status Update message to gNB1.

This message may include Measured Per Slice Energy Consumption Rate to inform gNB2's energy consumption per slice requested by gNB1. Measured Per Slice Energy Consumption Rate may include slice information and Measured Slice Energy Consumption Rate per slice requested by gNB1.

In step S1806, the UE requests gNB1 to establish a new RRC connection.

In steps S1807 and S1808, gNB1 completes the RRC Connection Setup procedure.

In step S1809, the first NAS message piggybacked in the RRCSetupComplete message sent by the UE is included in the Initial UE Message message and transmitted to the AMF.

In step S1810, the AMF sends an Initial Context Setup Request message to create a UE context to gNB1.

This message may include Per Slice Energy Efficiency Policy Applied Authorization.

Additionally, this message may include Energy Efficiency Configuration for gNB1 to control or manage the energy usage of the UE.

Energy Efficiency Configuration may include the Maximum Energy Consumption Rate of the corresponding UE and the Maximum Energy Credit Limit of the corresponding UE.

Additionally, this message may include a Reporting Indication to allow gNB1 to report the energy usage of the UE to AMF.

Reporting to AMF can be provided when a certain threshold is crossed, or has been reached. Otherwise reporting to AMF can be provided periodically.

The Indication may include the threshold value or cycle value of the UE for report trigger.

After receiving the Initial Context Setup Request message, gNB1 can save the information included in the Energy Efficiency Configuration and Reporting Indication included in the message.

Additionally, if there is a change in Per Slice Energy Efficiency Policy Applied Authorization, Efficiency Configuration, and Reporting Indication, the corresponding change may be provided from AMF to gNB1 through a UE Context Modification Request message.

Additionally, Per PDU Energy Consumption Rate can be provided from SMF to gNB1 via AMF through a PDU Session Resource Setup/Modify Request message.

The Energy Efficiency-related information provided by the above-mentioned AMF or SMF to the gNB can be generated based on one or more of subscriber information (subscriber information stored in UDM and/or subscriber information stored in UDR), local configuration information, information provided by PCF, and information provided by Application Function (AF).

In step S1811 and step S1812, gNB1 activates AS security with the UE.

In step S1813 and step S1814, gNB1 performs reconfiguration to set up SRB and DRB for the UE.

In step S1815, gNB1 sends an Initial Context Setup Response message to inform AMF that UE context generation has been completed.

According to the energy usage of each slice or the UE, depending on the node that triggers the handover from gNB1 to gNB2 for the UE(s) receiving services through a specific slice (or a specific UE), one of the following two methods can be used.

Option 1:

In step S1816a-1, based on the information reported by the report request received from AMF in step S1802 and step S1810, in order to reduce energy usage for each slice of gNB1 or for a specific UE, AMF can decide the handover of the corresponding UE(s) to gNB2.

In order for gNB1 to perform handover, AMF transmits an existing NGAP message or a new NGAP message (for example, Mobility Request) to gNB1.

At this time, AMF can provide updated UE-Slice-MBR information. This can be determined directly by the AMF or through interaction with the PCF, and it can be determined by considering the energy usage for each slice of the UE.

In step S1816a-2, after receiving an existing NGAP or new NGAP message from AMF, in response, gNB1 may transmit an existing NGAP message or a new NGAP message (for example, Mobility Response) to AMF.

Option 2:

In step S1816b, based on the (Per Slice) Energy Efficiency Configuration information received from AMF in S1802 and S1810 and the Measured Per Slice Energy Consumption Rate information received from gNB2 in step S1805, in order to reduce energy usage for each slice of gNB1 or for a specific UE, gNB1 decides the handover of the corresponding UE(s) to gNB2.

At this time, gNB1 can decide which slices should be maintained in the target among slices by considering E-ARP, updated UE-Slice-MBR, etc.

In step S1817, gNB1 transmits an XnAP Handover Request message to gNB2.

This message may include a new cause value to indicate that the UE's handover is performed for energy efficiency.

After receiving the cause value, the target base station can make actions/decisions such as not handover the handovered UE(s) back to the source base station.

In addition, in order for gNB2 to control or manage the energy usage of the handovered UE and report the energy usage of the handovered UE to the AMF, this message may include information received in step S1810 (for example, Per Slice Energy Efficiency Policy Applied Authorization, Energy Efficiency Configuration, Reporting Indication).

In step S1818, after receiving the XnAP Handover Request message from gNB1, gNB2 performs admission control and sends an XnAP Handover Request Acknowledge message including the new RRC configuration to gNB1 in response.

In step S1819, gNB1 provides the UE with the RRCReconfiguration message included in the message received from gNB2.

In step S1820, the UE changes RRC connection to gNB2.

In step S1821, the UE sends an RRCReconfigurationComplete message to gNB2 in response to the message received from gNB1.

In step S1822, gNB2 sends a Path Switch Request message to AMF. If gNB1 did not transmit a message in step S1816a-2, the AMF can be considered to have received a response to step S1816a-1 by receiving this message.

In step S1823, AMF sends a Path Switch Request Acknowledge message to gNB2 in response to the request message received from gNB2.

At this time, AMF can provide updated UE-Slice-MBR information. This can be determined directly by the AMF or determined through interaction with the PCF. This can be determined by considering the energy usage for each slice of the wireless device.

In step S1824, gNB2 sends a UE Context Release message to gNB1 to delete the UE context of the UE held by gNB1.

In FIG. 18a and FIG. 18b, Xn HO is assumed, but some embodiments of the present disclosure can be similarly applied to the case of NG HO.

Some of the detailed steps shown in the examples of FIG. 17, FIG. 18a, and FIG. 18b may not be essential steps and may be omitted. In addition to the steps shown in FIG. 17, FIG. 18a, and FIG. 18b, other steps may be added, and the order of the steps may vary. Some of the above steps may have their own technical meaning.

Hereinafter, an apparatus for operations considering energy consumption in a wireless network system, according to some embodiments of the present disclosure, will be described.

Herein, the first RAN node may be the gNB in FIG. 7. The first RAN node may comprise a transceiver, a memory, and at least one processor. The at least one processor may be operatively coupled to the memory and the transceiver.

The at least one processor may be adapted to receive, from an Access and Mobility management Function (AMF), a first message including an energy efficiency configuration. The energy efficiency configuration may include an energy consumption threshold per network slice and/or per wireless device. The at least one processor may be adapted to monitor energy consumption for a network slice and/or a wireless device. The at least one processor may be adapted to transmit, to a second RAN node, a second message requesting a handover. The handover may be determined based on the monitored energy consumption for the network slice or the wireless device and the energy consumption threshold. The second message may include a cause value informing that the handover is performed for energy efficiency.

For example, the at least one processor may be adapted to transmit, to the second RAN node, a Resource Status Request message including indication requesting measurements of Per Slice Energy Consumption Rate.

For example, the at least one processor may be adapted to receive, from the second RAN node, a Resource Status Update message including measurements results of the Per Slice Energy Consumption Rate.

For example, the handover may be determined by the first RAN node based on the measurements results of the Per Slice Energy Consumption Rate.

For example, the first message may include a Per Slice Reporting Indication.

For example, the at least one processor may be adapted to transmit, to the AMF, a report including information on energy consumption per slice.

For example, the at least one processor may be adapted to receive, from the AMF, a Reporting Indication.

For example, the Reporting Indication may be included in an Initial Context Setup Request message to establish a UE Context for the wireless device.

For example, the at least one processor may be adapted to report, to the AMF, energy consumption rate for the wireless device.

For example, the at least one processor may be adapted to the handover may be determined by the AMF based on the energy consumption rate for the wireless device.

For example, the at least one processor may be adapted to receive, from the AMF, a Mobility Request for the wireless device.

For example, the at least one processor may be adapted to receive, from the AMF, an Initial Context Setup Request message including (i) a Per Slice Energy Efficiency Policy Applied Authorization and/or (ii) an Energy Efficiency Configuration.

For example, the second message may include (i) the Per Slice Energy Efficiency Policy Applied Authorization, (ii) the Energy Efficiency Configuration, and/or (iii) the Reporting Indication.

For example, the wireless device may be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

Hereinafter, a processor for a first RAN for operations considering energy consumption in a wireless network system, according to some embodiments of the present disclosure, will be described.

The processor may be configured to control the first RAN node to receive, from an Access and Mobility management Function (AMF), a first message including an energy efficiency configuration. The energy efficiency configuration may include an energy consumption threshold per network slice and/or per wireless device. The processor may be configured to control the first RAN node to monitor energy consumption for a network slice and/or a wireless device. The processor may be configured to control the first RAN node to transmit, to a second RAN node, a second message requesting a handover. The handover may be determined based on the monitored energy consumption for the network slice or the wireless device and the energy consumption threshold. The second message may include a cause value informing that the handover is performed for energy efficiency.

For example, the processor may be configured to control the first RAN node to transmit, to the second RAN node, a Resource Status Request message including indication requesting measurements of Per Slice Energy Consumption Rate.

For example, the processor may be configured to control the first RAN node to receive, from the second RAN node, a Resource Status Update message including measurements results of the Per Slice Energy Consumption Rate.

For example, the first message may include a Per Slice Reporting Indication.

For example, the processor may be configured to control the first RAN node to transmit, to the AMF, a report including information on energy consumption per slice.

For example, the processor may be configured to control the first RAN node to receive, from the AMF, a Reporting Indication.

For example, the processor may be configured to control the first RAN node to report, to the AMF, energy consumption rate for the wireless device.

For example, the processor may be configured to control the first RAN node to the handover may be determined by the AMF based on the energy consumption rate for the wireless device.

For example, the processor may be configured to control the first RAN node to receive, from the AMF, a Mobility Request for the wireless device.

For example, the processor may be configured to control the first RAN node to receive, from the AMF, an Initial Context Setup Request message including (i) a Per Slice Energy Efficiency Policy Applied Authorization and/or (ii) an Energy Efficiency Configuration.

Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for operations considering energy consumption in a wireless network system, according to some embodiments of the present disclosure, will be described.

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

Some example of storage medium is coupled to the processor such that the processor can read information from the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. For another example, the processor and the storage medium may reside as discrete components.

The computer-readable medium may include a tangible and non-transitory computer-readable storage medium.

For example, non-transitory computer-readable media may include random access memory (RAM) such as synchronous dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), FLASH memory, magnetic or optical data storage media, or any other medium that can be used to store instructions or data structures. Non-transitory computer-readable media may also include combinations of the above.

In addition, the method described herein may be realized at least in part by a computer-readable communication medium that carries or communicates code in the form of instructions or data structures and that can be accessed, read, and/or executed by a computer.

According to some embodiment of the present disclosure, a non-transitory computer-readable medium has stored thereon a plurality of instructions. The stored a plurality of instructions may be executed by a processor of a first RAN node.

The stored a plurality of instructions may cause the first RAN node to receive, from an Access and Mobility management Function (AMF), a first message including an energy efficiency configuration. The energy efficiency configuration may include an energy consumption threshold per network slice and/or per wireless device. The stored a plurality of instructions may cause the first RAN node to monitor energy consumption for a network slice and/or a wireless device. The stored a plurality of instructions may cause the first RAN node to transmit, to a second RAN node, a second message requesting a handover. The handover may be determined based on the monitored energy consumption for the network slice or the wireless device and the energy consumption threshold. The second message may include a cause value informing that the handover is performed for energy efficiency.

For example, the stored a plurality of instructions may cause the first RAN node to transmit, to the second RAN node, a Resource Status Request message including indication requesting measurements of Per Slice Energy Consumption Rate.

For example, the stored a plurality of instructions may cause the first RAN node to receive, from the second RAN node, a Resource Status Update message including measurements results of the Per Slice Energy Consumption Rate.

For example, the first message may include a Per Slice Reporting Indication.

For example, the stored a plurality of instructions may cause the first RAN node to transmit, to the AMF, a report including information on energy consumption per slice.

For example, the stored a plurality of instructions may cause the first RAN node to receive, from the AMF, a Reporting Indication.

For example, the stored a plurality of instructions may cause the first RAN node to report, to the AMF, energy consumption rate for the wireless device.

For example, the stored a plurality of instructions may cause the first RAN node to the handover may be determined by the AMF based on the energy consumption rate for the wireless device.

For example, the stored a plurality of instructions may cause the first RAN node to receive, from the AMF, a Mobility Request for the wireless device.

For example, the stored a plurality of instructions may cause the first RAN node to receive, from the AMF, an Initial Context Setup Request message including (i) a Per Slice Energy Efficiency Policy Applied Authorization and/or (ii) an Energy Efficiency Configuration.

Hereinafter, a wireless device for operations considering energy consumption in a wireless network system, according to some embodiments of the present disclosure, will be described.

The wireless device may include a transceiver, a memory, and a processor operatively coupled to the transceiver and the memory. For example, the wireless device may be the first wireless device 100 or the second wireless device 200 of FIGS. 2 and 3, or the UE 100 of FIG. 4.

The processor may be adapted to transmit, to a first Radio Access Network (RAN) node, a Radio Resource Control (RRC) Setup Request message. The processor may be adapted to receive, from the first RAN node, an RRC Setup message. The processor may be adapted to transmit, to the first RAN node, an RRC Setup Complete message. The processor may be adapted to receive, from the first RAN node, an RRC reconfiguration. The processor may be adapted to perform handover from the first RAN node to a second RAN node. The handover may be determined based on energy consumption per network slice or energy consumption per wireless device.

Hereinafter, a method performed by a wireless device for operations considering energy consumption in a wireless network system, according to some embodiments of the present disclosure, will be described.

The wireless device may transmit, to a first Radio Access Network (RAN) node, a Radio Resource Control (RRC) Setup Request message. The wireless device may receive, from the first RAN node, an RRC Setup message. The wireless device may transmit, to the first RAN node, an RRC Setup Complete message. The wireless device may receive, from the first RAN node, an RRC reconfiguration. The wireless device may perform handover from the first RAN node to a second RAN node. The handover may be determined based on energy consumption per network slice or energy consumption per wireless device.

The present disclosure can have various advantageous effects.

Claims in the present disclosure can be combined in a various way. For instance, technical features in method claims of the present disclosure can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims.

Claims

A method performed by a first Radio Access Network (RAN) node in a wireless communication system, the method comprising:

receiving, from an Access and Mobility management Function (AMF), a first message including an energy efficiency configuration,

wherein the energy efficiency configuration includes an energy consumption threshold per network slice and/or per wireless device;

monitoring energy consumption for a network slice and/or a wireless device; and

transmitting, to a second RAN node, a second message requesting a handover,

wherein the handover is determined based on the monitored energy consumption for the network slice or the wireless device and the energy consumption threshold, and

wherein the second message includes a cause value informing that the handover is performed for energy efficiency.
The method of claim 1, wherein the method further comprises,

transmitting, to the second RAN node, a Resource Status Request message including indication requesting measurements of Per Slice Energy Consumption Rate.
The method of claim 2, wherein the method further comprises,

receiving, from the second RAN node, a Resource Status Update message including measurements results of the Per Slice Energy Consumption Rate.
The method of claim 3,

wherein the handover is determined by the first RAN node based on the measurements results of the Per Slice Energy Consumption Rate.
The method of claim 1,

wherein the first message includes a Per Slice Reporting Indication.
The method of claim 5,

transmitting, to the AMF, a report including information on energy consumption per slice.
The method of claim 1, wherein the method further comprises,

receiving, from the AMF, a Reporting Indication.
The method of claim 7,

wherein the Reporting Indication is included in an Initial Context Setup Request message to establish a UE Context for the wireless device.
The method of claim 7, wherein the method further comprises,

reporting, to the AMF, energy consumption rate for the wireless device.
The method of claim 9,

wherein the handover is determined by the AMF based on the energy consumption rate for the wireless device.
The method of claim 10, wherein the method further comprises,

receiving, from the AMF, a Mobility Request for the wireless device.
The method of claim 1, wherein the method further comprises,

receiving, from the AMF, an Initial Context Setup Request message including (i) a Per Slice Energy Efficiency Policy Applied Authorization and/or (ii) an Energy Efficiency Configuration.
The method of claim 1,

wherein the second message includes (i) a Per Slice Energy Efficiency Policy Applied Authorization, (ii) a Energy Efficiency Configuration, and/or (iii) a Reporting Indication.
The method of claim 1,

wherein the wireless device is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.
A first Radio Access Network (RAN) node in a wireless communication system comprising:

a transceiver;

a memory; and

at least one processor operatively coupled to the memory and the transceiver, and adapted to:

receive, from an Access and Mobility management Function (AMF), a first message including an energy efficiency configuration,

wherein the energy efficiency configuration includes an energy consumption threshold per network slice and/or per wireless device;

monitor energy consumption for a network slice and/or a wireless device; and

transmit, to a second RAN node, a second message requesting a handover,

wherein the handover is determined based on the monitored energy consumption for the network slice or the wireless device and the energy consumption threshold, and

wherein the second message includes a cause value informing that the handover is performed for energy efficiency.
The first RAN node of claim 15, wherein the at least one processor is further adapted to:

transmit, to the second RAN node, a Resource Status Request message including indication requesting measurements of Per Slice Energy Consumption Rate.
The first RAN node of claim 16, wherein the at least one processor is further adapted to:

receive, from the second RAN node, a Resource Status Update message including measurements results of the Per Slice Energy Consumption Rate.
The first RAN node of claim 17,

wherein the handover is determined by the first RAN node based on the measurements results of the Per Slice Energy Consumption Rate.
The first RAN node of claim 15,

wherein the first message includes a Per Slice Reporting Indication.
The first RAN node of claim 19, wherein the at least one processor is further adapted to:

transmit, to the AMF, a report including information on energy consumption per slice.
The first RAN node of claim 15, wherein the at least one processor is further adapted to:

receive, from the AMF, a Reporting Indication.
The first RAN node of claim 21,

wherein the Reporting Indication is included in an Initial Context Setup Request message to establish a UE Context for the wireless device.
The first RAN node of claim 21, wherein the at least one processor is further adapted to:

report, to the AMF, energy consumption rate for the wireless device.
The first RAN node of claim 23,

wherein the handover is determined by the AMF based on the energy consumption rate for the wireless device.
The first RAN node of claim 24, wherein the at least one processor is further adapted to:

receive, from the AMF, a Mobility Request for the wireless device.
The first RAN node of claim 15, wherein the at least one processor is further adapted to:

receive, from the AMF, an Initial Context Setup Request message including (i) a Per Slice Energy Efficiency Policy Applied Authorization and/or (ii) an Energy Efficiency Configuration.
The first RAN node of claim 15,

wherein the second message includes (i) a Per Slice Energy Efficiency Policy Applied Authorization, (ii) a Energy Efficiency Configuration, and/or (iii) a Reporting Indication.
The first RAN node of claim 15,

wherein the wireless device is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.
A processor for a first Radio Access Network (RAN) node in a wireless communication system, wherein the processor is configured to control the first RAN node to perform operations comprising:

receiving, from an Access and Mobility management Function (AMF), a first message including an energy efficiency configuration,

wherein the energy efficiency configuration includes an energy consumption threshold per network slice and/or per wireless device;

monitoring energy consumption for a network slice and/or a wireless device; and

transmitting, to a second RAN node, a second message requesting a handover,

wherein the handover is determined based on the monitored energy consumption for the network slice or the wireless device and the energy consumption threshold, and

wherein the second message includes a cause value informing that the handover is performed for energy efficiency.
A non-transitory computer-readable medium having stored thereon a plurality of instructions, which, based on executed by a processor of a first Radio Access Network (RAN) node, perform operations, the operations comprises,

receiving, from an Access and Mobility management Function (AMF), a first message including an energy efficiency configuration,

wherein the energy efficiency configuration includes an energy consumption threshold per network slice and/or per wireless device;

monitoring energy consumption for a network slice and/or a wireless device; and

transmitting, to a second RAN node, a second message requesting a handover,

wherein the handover is determined based on the monitored energy consumption for the network slice or the wireless device and the energy consumption threshold, and

wherein the second message includes a cause value informing that the handover is performed for energy efficiency.
A method for a wireless device in a wireless communication system, the method comprising,

transmitting, to a first Radio Access Network (RAN) node, a Radio Resource Control (RRC) Setup Request message;

receiving, from the first RAN node, an RRC Setup message;

transmitting, to the first RAN node, an RRC Setup Complete message; and

receiving, from the first RAN node, an RRC reconfiguration;

performing handover from the first RAN node to a second RAN node,

wherein the handover is determined based on energy consumption per network slice or energy consumption per wireless device.
A wireless device in a wireless communication system comprising:

a transceiver;

a memory; and

a processor operatively coupled to the transceiver and the memory, and adapted to:

transmit, to a first Radio Access Network (RAN) node, a Radio Resource Control (RRC) Setup Request message;

receive, from the first RAN node, an RRC Setup message;

transmit, to the first RAN node, an RRC Setup Complete message; and

receive, from the first RAN node, an RRC reconfiguration;

perform handover from the first RAN node to a second RAN node,

wherein the handover is determined based on energy consumption per network slice or energy consumption per wireless device.