Method and apparatus for network power saving in wireless communication system

Abstract

A method and apparatus for network power saving in a wireless communication system are provided. The method comprises the steps of: receiving a configuration for conditional mobility to a target cell, where the configuration comprises a first condition and a second condition; evaluating whether the target cell satisfies a first condition for conditional mobility to the target cell; determining to apply a second condition based on receiving the indication to notify the serving cell to use the network energy saving scheme; and evaluating whether the target cell satisfies a second condition for conditional mobility.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for network energy saving in a wireless communication system. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology that allows high-speed packet communications. Many solutions have been proposed for the LTE goal, including those aimed at reducing user and supplier costs, improving service quality, and expanding and improving coverage and system capacity. As upper layer requirements, 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of frequency bands, simple structure, open interfaces, and appropriate power consumption of terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components required for successful standardization of new RATs that will meet both urgent market needs and longer-term requirements set forth by the ITU Radiocommunication Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process in a timely manner. In addition, NR should be able to use any spectrum band up to at least the 100 GHz range that can be used for wireless communications even in the more distant future.

[0004] The goal of NR is to be a single technology framework that addresses all use cases, requirements and deployment scenarios, including enhanced mobile broadband (eMBB), massive machine type communications (mMTC), ultra-reliable and low latency communications (URLLC), etc. NR should be inherently forward compatible. Summary of the invention

[0005] Technical issues

[0006] With Release (Rel)-16 and Rel-17, conditional mobility (such as CHO, CPC, and CPA) is introduced to improve mobility robustness and reduce the latency of mobility execution. If the network configures one or more candidate target cells to the UE in the configuration for conditional mobility, the UE evaluates the conditions of each configured candidate target cell. If the execution condition for conditional mobility is met with respect to one of the target cells, the UE performs conditional mobility to the cell.

[0007] In Rel-18 Network Energy Saving (NES) WI, the use of group common signaling to trigger HO / CHO and pre-configure candidate target cells is being discussed. This is for fast Pcell changes when the NES state is activated (e.g., cell shutdown). As one of the solutions, a new CHO event trigger considering the cell NES state is proposed. In this case, if the NES state is activated in the network, the UE performs CHO to the neighbor cell based on the cell quality.

[0008] However, if the UE does not find a suitable cell among the candidates for CHO, it cannot perform CHO, which results in the following connection failure: (i) the UE receives an indication that the NES state is activated (the cell will be shut down soon), (ii) the UE searches for a cell that meets the execution conditions, (iii) the UE stays on the cell until a suitable cell for CHO execution is found, (iv) the connection failure is declared after the cell is shut down, (v) the UE performs RRC re-establishment due to the connection failure.

[0009] Even if the network configures appropriate CHO configuration based on the UE's measurements, it cannot guarantee that there will always be cells that meet the CHO execution conditions when the NES state is activated.

[0010] As a result, changing Pcell may take more time compared to a regular HO procedure. It may also have an impact on data performance and mobility robustness caused by connection failures.

[0011] Therefore, there is a need for research on network energy saving in wireless communication systems.

[0012] Solution to the problem

[0013] In one aspect, a method performed by a wireless device in a wireless communication system is provided. The method includes the following steps: receiving a configuration for conditional mobility to a target cell from a serving cell, wherein the configuration includes a first condition and a second condition; evaluating whether the target cell satisfies the first condition for the conditional mobility to the target cell; determining to apply the second condition based on receiving an indication notifying the serving cell to use a network energy saving scheme; and evaluating whether the target cell satisfies the second condition for the conditional mobility.

[0014] In another aspect, a device for implementing the above method is provided.

[0015] Advantageous Effects of the Invention

[0016] The present disclosure may have various beneficial effects.

[0017] According to some embodiments of the present disclosure, when a network uses a power saving scheme, a wireless device may efficiently perform conditional switching and fast recovery procedures.

[0018] For example, the UE may minimize the impact on data performance and mobility robustness caused by connection failures due to NES state changes (eg, cell closure) either autonomously or by quick action of the network.

[0019] For example, if a Pcell change cannot be made quickly through CHO, the terminal can take action itself or through the network quickly. When a cell is turned off, interruptions due to connection failures can be prevented, thereby minimizing the impact on data performance and mobility robustness.

[0020] According to some embodiments of the present disclosure, a wireless network system may provide an efficient solution for activating or deactivating a network energy scheme by receiving a predictive data traffic report.

[0021] The beneficial effects that can be obtained by the specific embodiments of the present disclosure are not limited to the beneficial effects listed above. For example, there may be various technical effects that a person of ordinary skill in the relevant field can understand and / or derive from the present disclosure. Therefore, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 An example of a communication system to which an implementation of the present disclosure is applied is shown.

[0023] Figure 2 An example of a wireless device to which an implementation of the present disclosure is applied is shown.

[0024] Figure 3 An example of a wireless device to which an implementation of the present disclosure is applied is shown.

[0025] Figure 4 Another example of a wireless device to which an implementation of the present disclosure is applied is shown.

[0026] Figure 5 An example of a UE to which an implementation of the present disclosure is applied is shown.

[0027] Figure 6 and Figure 7 An example of a protocol stack in a 3GPP-based wireless communication system to which an implementation of the present disclosure is applied is shown.

[0028] Figure 8 The frame structure in a 3GPP-based wireless communication system to which the implementation of the present disclosure is applied is shown.

[0029] Fig. 9 An example of data flow in a 3GPP NR system to which an implementation of the present disclosure is applied is shown.

[0030] Fig.10 An example of a measurement report is shown.

[0031] Fig.11 An example of a method for network energy saving in a wireless communication system is shown.

[0032] Fig.12 An example of a method for network energy saving in a wireless communication system is shown.

[0033] Fig.13 An example of a method using only the CHO configuration associated with the NES state (utilizing T1) is shown.

[0034] Fig.14 An example of a method using all CHO configurations regardless of NES status (utilizing T1) is shown.

[0035] Fig.15 An example of a method for early RLF (not utilizing T1) when a cell is switched off is shown.

[0036] Fig.16 An example of a method for early recovery (utilizing T1) utilizing a switching situation is shown.

[0037] Fig.17 An example of a method for early recovery (utilizing T1) utilizing a switching situation is shown. DETAILED DESCRIPTION

[0038] The following techniques, devices and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented by radio technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented by radio technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of 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 adopts OFDMA in DL and SC-FDMA in UL. LTE-Advanced (LTE-A) is an evolved version of 3GPP LTE.

[0039] For ease of description, the implementation of the present disclosure is mainly described with respect 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 a 3GPP-based wireless communication system are applicable to other mobile communication systems.

[0040] For terms and techniques not specifically described in the terms and techniques adopted in the present disclosure, reference may be made to wireless communication standard documents issued prior to the present disclosure.

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

[0042] In the present disclosure, a slash ( / ) or a comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0043] 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 being the same as "at least one of A and B".

[0044] 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".

[0045] In addition, the brackets 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, in the present disclosure, "control information" is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when it is shown as "control information (ie, PDCCH)", "PDCCH" may be proposed as an example of "control information".

[0046] The technical features described separately in one figure in the present disclosure can be implemented separately or simultaneously.

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

[0048] Hereinafter, the present disclosure will be described in more detail with reference to the accompanying drawings. Unless otherwise specified, 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.

[0049] Figure 1 An example of a communication system to which an implementation of the present disclosure is applied is shown.

[0050] exist Figure 1 The 5G usage scenarios shown in the present disclosure are only exemplary, and the technical features of the present disclosure may be applied to Figure 1 Other 5G usage scenarios shown in .

[0051] The three main demand categories for 5G include: (1) enhanced mobile broadband (eMBB) category, (2) massive machine type communication (mMTC) category, and (3) ultra-reliable and low-latency communication (URLLC) category.

[0052] Some use cases may require multiple categories for optimization, and other use cases may focus on only one key performance indicator (KPI). 5G supports such various use cases using a flexible and reliable approach.

[0053] eMBB goes far beyond basic mobile Internet access and covers rich two-way work and media and entertainment applications in the cloud and augmented reality. Data is one of the core driving forces of 5G, and in the 5G era, dedicated voice services may not be provided for the first time. In 5G, it is expected that voice will be simply processed as an application using a data connection provided by the communication system. The main reason for increasing business capacity is due to the increase in content size and the increase in the number of applications requiring high data transfer rates. As more and more devices are connected to the Internet, streaming services (audio and video), conversational video, and mobile Internet access will be more widely used. Many of these applications require a connection that is always on in order to push real-time information and alerts to users. Cloud storage and applications are rapidly increasing in mobile communication platforms and can be applied to both work and entertainment. Cloud storage is a special use case that accelerates the growth of uplink data transfer rates. 5G is also used for remote work in the cloud. When using a tactile interface, 5G requires much lower end-to-end latency to maintain a good user experience. Entertainment, such as cloud gaming and video streaming, is another core element that increases the demand for mobile broadband capabilities. Entertainment is essential for smartphones and tablets anywhere including high mobility environments such as trains, vehicles and airplanes. Other use cases are augmented reality for entertainment and information search. In this case, augmented reality requires very low latency and instantaneous data capacity.

[0054] Additionally, one of the most anticipated 5G use cases involves the ability to smoothly connect embedded sensors in all fields, i.e., mMTC. It is expected that the number of potential Internet of Things (IoT) devices will reach 204 billion by 2020. Industrial IoT is one of the categories that performs a major role in enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure through 5G.

[0055] URLLC includes remote control and ultra-reliable / available low-latency links over the main infrastructure that will transform new services in industry (such as autonomous vehicles). The level of reliability and latency is necessary to control smart grids, automate industry, enable robotics, and control and adjust drones.

[0056] 5G is a means of providing streams estimated to be hundreds of megabits per second to gigabits per second, and can complement fiber to the home (FTTH) and cable-based broadband (or DOCSIS). Such fast speeds are needed to deliver TV at a 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. Specific applications may require special network configurations. For example, for VR games, game companies need to merge core servers into the network operator's edge network servers to minimize latency.

[0057] It is expected that cars, together with many use cases for mobile communications for vehicles, are new and important motivating forces in 5G. For example, the entertainment of passengers requires high simultaneous capacity and mobile broadband with high mobility. This is because future users continue to expect high-quality connections, regardless of their location and speed. Another use case in the automotive field is the AR dashboard. The AR dashboard enables the driver to identify objects in the dark in addition to the objects seen from the front window, and displays the distance to the object and the movement of the object by overlapping the information told by the driver. In the future, the wireless module realizes the communication between vehicles, the information exchange between the vehicle and the supporting infrastructure, and the information exchange between the vehicle and other connected devices (e.g., devices accompanied by pedestrians). The safety system guides the alternative route of the behavior so that the driver can drive more safely, thereby reducing the risk of accidents. The next stage will be remotely controlled or self-driving vehicles. This requires very high reliability and very fast communication between different self-driving vehicles and between vehicles and infrastructure. In the future, self-driving vehicles will perform all driving activities, and the driver will only focus on abnormal traffic that the vehicle cannot recognize. The technical requirements of self-driving vehicles require ultra-low latency and ultra-high reliability, so that traffic safety is increased to a level that cannot be achieved by humans.

[0058] Smart cities and smart homes / buildings, referred to as smart societies, will be embedded in high-density wireless sensor networks. Distributed networks of smart sensors will identify conditions for cost and energy efficient maintenance of cities or homes. Similar configurations can be performed for corresponding homes. All temperature sensors, window and heating controllers, burglar alarms and home appliances are wirelessly connected. Many of these sensors are typically low in data transfer rate, power and cost. However, certain types of devices may require real-time HD video to perform monitoring.

[0059] The consumption and distribution of energy, including heat or gas, is distributed at a higher level, making it necessary to automatically control the distribution sensor network. Smart grids collect information and use digital information and communication technologies to connect sensors to each other, so as to act according to the collected information. Since this information can include the behavior of supply companies and consumers, smart grids can improve the distribution of fuels such as electricity by methods with efficiency, reliability, economic feasibility, production sustainability and automation. Smart grids can also be considered as another sensor network with low latency.

[0060] Mission-critical applications (e.g., e-health) are one of the 5G use cases. The health section includes many applications that can enjoy the benefits of mobile communications. Communication systems can support telemedicine that provides clinical treatment in remote locations. Telemedicine can help reduce barriers to distance and improve access to medical services that are not continuously available in remote rural areas. Telemedicine is also used to perform important treatments and save lives in emergency situations. Wireless sensor networks based on mobile communications can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

[0061] Wireless and mobile communications are becoming increasingly important in the field of industrial applications. Cabling is expensive in terms of installation and maintenance. Therefore, the possibility of replacing cables with reconfigurable radio links is an attractive opportunity in many industrial fields. However, in order to achieve this replacement, wireless connections need to be established with latency, reliability and capacity similar to cables, and the management of wireless connections needs to be simplified. When it comes to connecting to 5G, low latency and very low error probability are new requirements.

[0062] Logistics and freight tracking are important use cases for mobile communications, which allow inventory and packages to be tracked anywhere using location-based information systems. The use cases for logistics and freight tracking typically require low data rates but require location information with wide range and reliability.

[0063] Reference Figure 1 , the communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Figure 1 A 5G network is illustrated as an example of a network of the communication system 1, but implementations of the present disclosure are not limited to the 5G system and may be applied to future communication systems other than the 5G system.

[0064] BS 200 and network 300 may be implemented as wireless devices, and a specific wireless device may operate as a BS / network node relative to other wireless devices.

[0065] The wireless devices 100a to 100f represent devices that perform communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or LTE), and may be referred to as communication / wireless / 5G devices. The wireless devices 100a to 100f may include, but are not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. A vehicle 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) installed in a vehicle, a television, a smart phone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, and the like. Handheld devices may include smart phones, smart tablets, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0066] In the present disclosure, the wireless devices 100a to 100f may be referred to as user equipment (UE). For example, the UE may include a cellular phone, a smart phone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a plate-shaped personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle with an autonomous driving function, a connected car, a 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 / environmental device, a device related to 5G services, or a device related to the fourth industrial evolution field.

[0067] A UAV may be, for example, an aerial vehicle that is piloted by wireless control signals without a human on board.

[0068] VR devices may include, for example, devices for realizing objects or backgrounds of a virtual world. AR devices may include, for example, devices realized by connecting objects or backgrounds of a virtual world to objects or backgrounds of a real world. MR devices may include, for example, devices realized by merging objects or backgrounds of a virtual world into objects or backgrounds of a real world. Hologram devices may include, for example, devices for realizing a 360-degree stereoscopic image by recording and reproducing stereoscopic information, which uses the interference phenomenon of light generated when two lasers meet, which is called holographic imaging.

[0069] Public safety devices may include, for example, image relay devices or image devices wearable on a user's body.

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

[0071] The medical device may be, for example, a device for the purpose of diagnosing, treating, alleviating, curing or preventing a disease. For example, the medical device may be a device for the purpose of diagnosing, treating, alleviating or correcting an injury or harm. For example, the medical device may be a device for the purpose of inspecting, replacing or modifying a structure or function. For example, the medical device may be a device for the purpose of regulating 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 surgery.

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

[0073] Fintech devices may be devices that can provide financial services such as mobile payments, for example. For example, Fintech devices may include payment devices or point-of-sale (POS) systems.

[0074] Weather / environmental devices may include, for example, devices for monitoring or predicting weather / environmental conditions.

[0075] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. 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 super 5G network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without passing through the BS 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). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0076] Wireless communication / connection 150a, 150b, and 150c may be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS200 and / or between BS200. In this document, wireless communication / connection 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. Wireless devices 100a to 100f and BS200 / wireless devices 100a to 100f may send / receive radio signals to each other through wireless communication / connection 150a, 150b, and 150c. For example, wireless communication / connection 150a, 150b, and 150c may send / receive signals through various physical channels. To this end, various configuration information configuration processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and at least a portion of the resource allocation process can be performed based on various proposals of the present disclosure.

[0077] Here, the radio communication technology implemented in the wireless device 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, which may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the above names. Additionally and / or alternatively, the radio communication technology implemented in the wireless device in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology, and may be referred to as various names such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented in at least one of 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 names. Additionally and / or alternatively, the radio communication technology implemented in the wireless device in the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN considered as low-power communication, and may not be limited to the above names. For example, ZigBee technology may generate a personal area network (PAN) associated with small / low-power digital communication based on various specifications such as IEEE 802.15.4, and may be referred to as various names.

[0078] Figure 2An example of a wireless device to which an implementation of the present disclosure is applied is shown.

[0079] Reference Figure 2 , the first wireless device 100 and the second wireless device 200 can transmit / receive radio signals to / from an external device through various RATs (eg, LTE and NR). Figure 2 In the example, {the first wireless device 100 and the second wireless device 200} may correspond to the attached Figure 1 At least one of {wireless devices 100a to 100f and BS200}, {wireless devices 100a to 100f and wireless devices 100a to 100f} and / or {BS200 and BS200}.

[0080] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts described in the present disclosure. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then transmit a radio signal including the first information / signals through the transceiver 106. The processor 102 may receive a radio signal 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 connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including commands for executing part or all of the processes controlled by the processor 102 or for executing the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts described in the present disclosure. In this document, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a 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 transceivers 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In the present disclosure, the first wireless device 100 may represent a communication modem / circuit / chip.

[0081] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in the present disclosure. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a radio signal including the third information / signals through the transceiver 206. The processor 202 may receive a radio signal 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 connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including commands for executing part or all of the processes controlled by the processor 202 or for executing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in the present disclosure. Herein, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a 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 transceivers 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, the second wireless device 200 may represent a communication modem / circuit / chip.

[0082] In the following, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by, but not limited to, one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). According to the description, function, process, suggestion, method, and / or operation flowchart disclosed in the present disclosure, one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs). One or more processors 102 and 202 may generate messages, control information, data, or information according to the description, function, process, suggestion, method, and / or operation flowchart disclosed in the present disclosure. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, function, process, suggestion, method, and / or operational flowchart disclosed in the present disclosure, and provide the generated signal to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206, and obtain the PDU, SDU, message, control information, data, or information according to the description, function, process, suggestion, method, and / or operational flowchart disclosed in the present disclosure.

[0083] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. 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 one or more processors 102 and 202. The descriptions, functions, processes, suggestions, methods, and / or operational flow charts disclosed in the present disclosure may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operational flow charts disclosed in the present disclosure may be included in one or more processors 102 and 202, or stored in one or more memories 104 and 204, thereby being driven by one or more processors 102 and 202. The descriptions, functions, processes, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of codes, commands and / or command sets.

[0084] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories 104 and 204 may be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, register, cache memory, computer-readable storage medium, and / or a combination thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 by various technologies such as wired or wireless connections.

[0085] One or more transceivers 106 and 206 can send user data, control information and / or radio signals / channels mentioned in the description, function, process, suggestion, method and / or operation flow chart disclosed in the present disclosure to one or more other devices. One or more transceivers 106 and 206 can receive user data, control information and / or radio signals / channels mentioned in the description, function, process, suggestion, method and / or operation flow chart disclosed in the present disclosure from one or more other devices. For example, one or more transceivers 106 and 206 can be connected to one or more processors 102 and 202 and send and receive radio signals. For example, one or more processors 102 and 202 can perform control so that one or more transceivers 106 and 206 can send user data, control information or radio signals to one or more other devices. One or more processors 102 and 202 can perform control so that one or more transceivers 106 and 206 can receive user data, control information or radio signals from one or more other devices.

[0086] One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and 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, processes, suggestions, methods, and / or operational flow charts disclosed in the present disclosure through one or more antennas 108 and 208. In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0087] One or more transceivers 106 and 206 can convert the received radio signal / channel, etc. from the RF band signal to the baseband signal in order to process the received user data, control information, radio signal / channel, etc. One or more transceivers 106 and 206 can convert the user data, control information, radio signal / channel, etc. processed by one or more processors 102 and 202 from the baseband signal to the RF band signal. To this end, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, transceivers 106 and 206 can up-convert the OFDM baseband signal to the carrier frequency through their (analog) oscillators and / or filters under the control of processors 102 and 202, and send the up-converted OFDM signal of the carrier frequency. Transceivers 106 and 206 can receive the OFDM signal of the carrier frequency, and down-convert the OFDM signal to the OFDM baseband signal through their (analog) oscillators and / or filters under the control of processors 102 and 202.

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

[0089] In the present disclosure, the BS is also referred to as a Node B (NB), an eNodeB (eNB) or a gNB.

[0090] Figure 3 An example of a wireless device to which an implementation of the present disclosure is applied is shown.

[0091] The wireless device may be implemented in various forms depending on the use case / service (see Figure 1 ).

[0092] Reference Figure 3 , the wireless devices 100 and 200 may correspond to Figure 2 The wireless devices 100 and 200 of the present invention may be configured by various elements, components, units / parts 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 an additional component 140. The communication unit 110 may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Figure 2 One or more processors 102 and 202 and / or Figure 2 One or more memories 104 and 204. For example, the transceiver 114 may include Figure 2 One or more transceivers 106 and 206 and / or Figure 2The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140, and controls the overall operation of each of the wireless devices 100 and 200. For example, the control unit 120 may control the electrical / mechanical operation of each of the wireless devices 100 and 200 based on the program / code / command / information stored in the memory unit 130. The control unit 120 may transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) through a wireless / wired interface via the communication unit 110, or store information received from the outside (e.g., other communication devices) through a wireless / wired interface in the memory unit 130 via the communication unit 110.

[0093] The additional component 140 may be configured differently depending on the type of the wireless device 100 and 200. For example, the additional component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit (e.g., an audio I / O port, a video I / O port), a driving unit, and a computing unit. The wireless device 100 and 200 may be in the form of, but not limited to, a robot ( Figure 1 100a), vehicles ( Figure 1 100b-1 and 100b-2), XR devices ( Figure 1 100c), handheld device ( Figure 1 100d), household appliances ( Figure 1 100e), IoT devices ( Figure 1 100f), digital broadcast terminal, hologram device, public safety device, MTC device, medical device, Fintech device (or financial device), security device, climate / environmental device, AI server / device ( Figure 1 400), BSS( Figure 1 The wireless devices 100 and 200 may be implemented in the form of a wireless device 200 , a network node, etc. The wireless devices 100 and 200 may be used in a mobile or fixed location depending on the usage example / service.

[0094] exist Figure 3In the wireless devices 100 and 200, the entirety of the various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface, or at least a portion 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 the first unit (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit / part and / or module within the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured by a group of one or more processors. As an example, the control unit 120 may be configured by a group of communication control processors, application processors (APs), electronic control units (ECUs), graphics processing units, and memory control processors. As another example, the memory unit 130 may be configured by RAM, DRAM, ROM, flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0095] Figure 4 Another example of a wireless device to which an implementation of the present disclosure is applied is shown.

[0096] Reference Figure 4 , the wireless devices 100 and 200 may correspond to Figure 2 The wireless devices 100 and 200 may be configured by various elements, components, units / portions and / or modules.

[0097] The first wireless device 100 may include at least one transceiver such as a transceiver 106, and at least one processing chip such as a processing chip 101. The processing chip 101 may include at least one processor such as a processor 102 and at least one memory such as a memory 104. The memory 104 may be operably connected to the processor 102. The memory 104 may store various types of information and / or instructions. The memory 104 may store software code 105, which implements instructions for executing the description, function, process, suggestion, method and / or operation flow chart disclosed in the present disclosure when executed by the processor 102. For example, the software code 105 may implement instructions for executing the description, function, process, suggestion, method and / or operation flow chart disclosed in the present disclosure when executed by the processor 102. For example, the software code 105 may control the processor 102 to execute one or more protocols. For example, the software code 105 may control the processor 102 to execute one or more layers of the radio interface protocol.

[0098] The second wireless device 200 may include at least one transceiver such as the transceiver 206 and at least one processing chip such as the processing chip 201. The processing chip 201 may include at least one processor such as the processor 202 and at least one memory such as the memory 204. The memory 204 may be operably connected to the processor 202. The memory 204 may store various types of information and / or instructions. The memory 204 may store software code 205, which implements instructions for executing the description, function, process, suggestion, method and / or operation flow chart disclosed in the present disclosure when executed by the processor 202. For example, the software code 205 may implement instructions for executing the description, function, process, suggestion, method and / or operation flow chart disclosed in the present disclosure when executed by the processor 202. For example, the software code 205 may control the processor 202 to execute one or more protocols. For example, the software code 205 may control the processor 202 to execute one or more layers of the wireless interface protocol.

[0099] Figure 5 An example of a UE to which an implementation of the present disclosure is applied is shown.

[0100] Reference Figure 5 , UE 100 may correspond to the attached Figure 2 The first wireless device 100 and / or Figure 4 A first wireless device 100 is provided.

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

[0102] The processor 102 may be configured to implement the descriptions, functions, processes, suggestions, methods and / or operational flow charts 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, processes, suggestions, methods and / or operational flow charts disclosed in the present disclosure. The layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor 102 may be an application processor. The processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator). Examples of the processor 102 can be found at MANUFACTURED BY SNAPDRAGON TM Series processors, Manufactured by EXYNOSTM Series processors, A series processors manufactured by Made by HELIO TM Series processors, ATOM manufactured TM series processors or corresponding to the next generation processors.

[0103] The memory 104 is operatively coupled to 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 devices. When the embodiment is implemented in software, the techniques described herein may be implemented with modules (e.g., processes, functions, etc.) that execute the descriptions, functions, processes, suggestions, methods, and / or operational flow charts disclosed in the present disclosure. The modules may be stored in the memory 104 and executed by the processor 102. The memory 104 may be implemented within the processor 102 or outside the processor 102, in which case the memory 104 may be communicatively coupled to the processor 102 via various means known in the art.

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

[0105] The power management module 110 manages power to the processor 102 and / or the transceiver 106. The battery 112 provides power to the power management module 110.

[0106] The display 114 outputs the results processed by the processor 102. The keyboard 116 receives input to be used by the processor 102. The keyboard 116 may be displayed on the display 114.

[0107] The SIM card 118 is an integrated circuit designed to securely store an International Mobile Subscriber Identity (IMSI) number and its associated keys, which are used to identify and authenticate subscribers on mobile telephony devices such as mobile phones and computers. Contact information can also be stored on many SIM cards.

[0108] Speaker 120 outputs sound related results processed by processor 102. Microphone 122 receives sound related input to be used by processor 102.

[0109] Figure 6 and Figure 7 An example of a protocol stack in a 3GPP-based wireless communication system to which an implementation of the present disclosure is applied is shown.

[0110] Specifically, Figure 6 An example of a radio interface user plane protocol stack between a UE and a BS is illustrated, and Figure 7 An example of a radio interface control plane protocol stack between a UE and a BS is illustrated. The control plane refers to a path through which control messages for managing calls made between a UE and a network are transmitted. The user plane refers to a path through which data generated in an application layer (e.g., voice data or Internet packet data) is transmitted. Figure 6 , the user plane protocol stack can be divided into layer 1 (ie, PHY layer) and layer 2. Figure 7 , the control plane protocol stack can be divided into layer 1 (ie, PHY layer), layer 2, layer 3 (eg, RRC layer), and non-access stratum (NAS) layer. Layer 1, layer 2, and layer 3 are called access stratum (AS).

[0111] In the 3GPP LTE system, Layer 2 is separated into the following sublayers: MAC, RLC, and PDCP. In the 3GPP NR system, Layer 2 is separated into the following sublayers: MAC, RLC, PDCP, and SDAP. The PHY layer provides transport channels to the MAC sublayer, the MAC sublayer provides logical channels to the RLC sublayer, the RLC sublayer provides RLC channels to the PDCP sublayer, and the PDCP sublayer provides radio bearers to the SDAP sublayer. The SDAP sublayer provides Quality of Service (QoS) flows to the 5G core network.

[0112] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing / demultiplexing MAC SDUs belonging to one or different logical channels to / from transport blocks (TBs) delivered to / from the physical layer on the transport channel; scheduling information reporting; error correction through hybrid automatic repeat request (HARQ) (one HARQ entity per cell in the case of carrier aggregation (CA); priority handling between UEs through dynamic scheduling; priority handling between logical channels of one UE through logical channel prioritization; padding. A single MAC entity can support multiple parameter sets, transmission timings, and cells. The mapping restrictions in the logical channel prioritization control which parameter set(s), cell, and transmission timing can be used by the logical channel.

[0113] MAC provides different kinds of data transmission services. In order to accommodate different kinds of data transmission services, multiple types of logical channels are defined, that is, each logical channel supports the transmission of a specific type of information. Each logical channel type is defined by what type of information is transmitted. Logical channels are divided into two groups: control channels and traffic channels. Control channels are used only for the transmission of control plane information, and traffic channels are used only for the transmission of user plane information. The broadcast control channel (BCCH) is a downlink logical channel for broadcasting system control information, the paging control channel (PCCH) is a downlink logical channel for transmitting paging information, system information change notifications, and indications of ongoing public warning services (PWS) broadcasts, the common control channel (CCCH) is a logical channel used to send control information between the UE and the network and is used by UEs that do not have an RRC connection with the network, and the dedicated control channel (DCCH) is a point-to-point bidirectional logical channel used by UEs with RRC connections to send dedicated control information between the UE and the network. The dedicated traffic channel (DTCH) is a point-to-point logical channel dedicated to one UE for transmitting user information. DTCH can exist in both the uplink and downlink. In the downlink, there are the following connections between logical channels and transport channels: BCCH can be mapped to the broadcast channel (BCH); BCCH can be mapped to the downlink shared channel (DL-SCH); PCCH can be mapped to the 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 the uplink, there are the following connections between logical channels and transport channels: CCCH can be mapped to the uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

[0114] The RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM). The RLC configuration is per logical channel without dependency on parameter sets and / or transmission duration. In 3GPP NR systems, the main services and functions of the RLC sublayer depend on the transmission mode and include: delivery of upper layer PDUs; sequence numbering independent of sequence numbering 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 SDUs (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).

[0115] 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); transmission of user data; reordering and duplicate detection; in-sequence delivery; PDCP PDU routing (in the case of split bearers); retransmission of PDCP SDU; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status report for RLC AM; duplication of PDCP PDU 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; transmission of control plane data; reordering and duplicate detection; in-sequence delivery; duplication of PDCP PDU and duplicate discard indication to lower layers.

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

[0117] 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 RRC connection between 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 reporting; detection and recovery of radio link failures; NAS message transmission from UE to NAS / from NAS to UE.

[0118] Figure 8 The frame structure in a 3GPP-based wireless communication system to which the implementation of the present disclosure is applied is shown.

[0119] Figure 8The frame structure shown in is merely exemplary, and the number of subframes, the number of time slots, and / or the number of symbols in a frame may vary. In a 3GPP-based wireless communication system, OFDM parameter sets (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) may be configured differently between multiple cells aggregated for one UE. For example, if the UE is configured with different SCSs for cells aggregated for the cell, the (absolute time) duration of time resources (e.g., subframes, time slots, or TTIs) including the same number of symbols may be different among the aggregated cells. In this article, the symbol may include an OFDM symbol (or CP-OFDM symbol), an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol).

[0120] Reference Figure 8 , downlink and uplink transmissions are organized into frames. Each frame has T f = 10ms duration. Each frame is divided into two half-frames, where each half-frame has a duration of 5ms. Each half-frame includes 5 sub-frames, where the duration of each sub-frame is T sf is 1 ms. Each subframe is divided into slots, and the number of slots in a subframe depends on the subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on a cyclic prefix (CP). In a normal CP, each slot includes 14 OFDM symbols, and in an extended CP, each slot includes 12 OFDM symbols. The parameter set is based on an exponentially scalable subcarrier spacing Δf=2 u *15kHz.

[0121] Table 1 shows the subcarrier spacing according to Δf=2 u *N is the number of OFDM symbols per time slot of 15kHz slot symb , the number of time slots per frame N frame,u slot , and the number of time slots N per subframe for normal CP subframe,u slot .

[0122] [Table 1]

[0123] u <![CDATA[N slot symb ]]> <![CDATA[N frame，u slot ]]> <![CDATA[N subframe，u slot ]]> 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

[0124] Table 2 shows the subcarrier spacing according to Δf=2 u *N is the number of OFDM symbols per time slot of 15kHz slot symb , the number of time slots per frame N frame,u slot , and the number of slots N per subframe for the extended CPsubframe,u slot .

[0125] [Table 2]

[0126] u <![CDATA[N slot symb ]]> <![CDATA[N frame，u slot ]]> <![CDATA[N subframe,u slot ]]> 2 12 40 4

[0127] A slot includes a plurality of symbols (e.g., 14 or 12 symbols) in the time domain. For each parameter set (e.g., subcarrier spacing) and carrier, a common resource block (CRB) N indicated by higher layer signaling (e.g., RRC signaling) is allocated. start,u grid To begin, we define N size,u grid,x *N RB sc subcarriers and N subframe,u symb OFDM symbol resource grid, where N size,u grid,x is the number of resource blocks (RBs) in the resource grid, and the subscript x is DL for the downlink and UL for the uplink. N RB sc is the number of subcarriers per RB. In 3GPP-based wireless communication systems, N RB sc Typically 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL), there is one resource grid. The carrier bandwidth N for subcarrier spacing configuration u size,u grid Given by high-level parameters (e.g., RRC parameters). Each element in the resource grid for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and one complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l representing the symbol position relative to a reference point in the time domain. In a 3GPP-based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain.

[0128] In 3GPP NR systems, RBs are classified into CRBs and physical resource blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain for subcarrier spacing configuration u. The center of subcarrier 0 of CRB 0 for subcarrier spacing configuration u coincides with "point A" used as a common reference point for the resource block grid. In 3GPP NR systems, PRBs are defined within bandwidth parts (BWPs) and are numbered from 0 to N. size BWP,i -1 numbering, where i is the number of the bandwidth part. Physical resource block n in bandwidth part i PRB With common resource block n CRB The relationship between is as follows:PRB =n CRB +N size BWP,i , where N size BWP,i It is a common resource block where the bandwidth part starts relative to CRB 0. A BWP includes multiple consecutive RBs. A carrier can include up to N (e.g., 5) BWPs. A UE can be configured with one or more BWPs on a given component carrier. Only one BWP can be activated at a time among the BWPs configured for a UE. The active BWP defines the operating bandwidth of the UE within the operating bandwidth of the cell.

[0129] The NR frequency band may be defined as two types of frequency ranges, namely, FR1 and FR2. The numerical values ​​of the frequency ranges may vary. For example, the two types of frequency ranges (FR1 and FR2) may be as shown in Table 3 below. For ease of explanation, in the frequency range 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).

[0130] [Table 3]

[0131] Frequency range name Corresponding frequency range Subcarrier spacing FR1 450MHz-6000MHz 15,30,60kHz FR2 24250MHz-52600MHz 60,120,240kHz

[0132] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a frequency band of 410 MHz to 7125 MHz, as shown in Table 4 below. That is, FR1 may include a frequency band of 6 GHz (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 frequency band. The unlicensed frequency band may be used for various purposes, such as for communication of vehicles (e.g., autonomous driving).

[0133] [Table 4]

[0134] Frequency range name Corresponding frequency range Subcarrier spacing FR1 410MHz-7125MHz 15,30,60kHz FR2 24250MHz-52600MHz 60,120,240kHz

[0135] In the present disclosure, the term "cell" may refer to a geographical area where one or more nodes provide a communication system or to a radio resource. "Cell" as a geographical area can be understood as a coverage range in which a node can provide services using a carrier, and "cell" as a radio resource (e.g., time-frequency resource) is associated with a bandwidth, which is a frequency range configured by a carrier. A "cell" associated with a radio resource is defined by a combination of downlink resources and uplink resources (e.g., a combination of DL component carriers (CCs) and UL CCs). A cell may be configured only by downlink resources, or may be configured by downlink resources and uplink resources. Since the DL coverage (which is the range in which a node can send a valid signal) and the UL coverage (which is the range in which a node can receive a valid signal from a UE) depend on the carrier that carries the signal, the coverage of a node may be associated with the coverage of a "cell" of a radio resource used by the node. Therefore, the term "cell" may be used to sometimes represent the service coverage of a node, to represent a radio resource at other times, or to represent the range in which a signal using a radio resource can reach with effective strength at other times.

[0136] In CA, two or more CCs are aggregated. The UE can receive or transmit on one or more CCs simultaneously according to its capabilities. CA is supported for both continuous CCs and non-contiguous CCs. When CA is configured, the UE has only one RRC connection with the network. When the RRC connection is established / reestablished / switched, one serving cell provides NAS mobility information, and when the RRC connection is reestablished / switched, one serving cell provides security input. This cell is called the primary cell (PCell). PCell is a cell operating on the primary frequency, where the UE performs an initial connection establishment process or initiates a connection reestablishment process. Depending on the UE capabilities, the secondary cell (SCell) can be configured to form a set of serving cells together with the PCell. SCell is a cell that provides additional radio resources on top of a special cell (PCell). Therefore, the set of configured serving cells for the UE always consists of one PCell and one or more SCells. For dual connection (DC) operation, the term "PCell" refers to the PCell of the primary cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG). SpCell supports PUCCH transmission and contention-based random access and is always activated. MCG is a set of serving cells associated with the master node, which includes SpCell (PCell) and optionally one or more SCells. For UEs configured with DC, SCG is a subset of serving cells associated with the secondary node, which includes PSCell and zero or more SCells. For UEs in RRC_CONNECTED that are not configured with CA / DC, there is only one serving cell consisting of PCell. For UEs in RRC_CONNECTED that are configured with CA / DC, the term "serving cell" is used to refer to the set of cells consisting of SpCell and all SCells. In DC, two MAC entities are configured in the UE: one for MCG and one for SCG.

[0137] Fig. 9 An example of data flow in a 3GPP NR system to which an implementation of the present disclosure is applied is shown.

[0138] Reference Fig. 9 , "RB" means radio bearer, and "H" means header. Radio bearers are classified into two groups: DRB for user plane data and SRB for control plane data. MAC PDU is transmitted / received to / from an external device through the PHY layer using radio resources. MAC PDU arrives at the PHY layer in the form of a transport block.

[0139] In the PHY layer, uplink transport channels UL-SCH and RACH are mapped to their physical channels PUSCH and PRACH, respectively, and downlink transport channels DL-SCH, BCH and PCH are mapped to PDSCH, PBCH and PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to physical PUCCH, and downlink control information (DCI) is mapped to PDCCH. MAC PDU related to UL-SCH is sent by UE via PUSCH based on UL grant, and MAC PDU related to DL-SCH is sent by BS via PDSCH based on DL assignment.

[0140] In the following, technical features related to the network energy saving solution are described.

[0141] In NR, methods for NES state activation / deactivation are being discussed.

[0142] - Adaptation of BS inactivity state: Supporting the gNB to enter sleep mode for a period of time along with the indication of activity / inactivity state (e.g. in terms of start time and duration) is expected to provide flexible adaptation at the gNB and potentially offer higher power saving gains.

[0143] Switching / fast PCell change for NES

[0144] 1)Group HO / CHO

[0145] - Introduction: Candidate target cells are preconfigured to the UE (eg, via RRC), and HO / CHO is triggered using group common signaling (eg, L1 / L2).

[0146] -Scenario: single carrier, multi-carrier; UE in connected state

[0147] -NES Gain: Reduces HO commands; allows the network to enter sleep mode in a timely manner. In multi-carrier deployments, it also allows coverage cells to be unloaded back to small cells that were turned off but are now turned on.

[0148] - Impact on legacy UEs: Depends on the cell energy saving state after sending group common signaling

[0149] -UE assistance information candidates: UE location, mobility status, measurement reports of small cells with reduced SSB (e.g. with scheme 2) on covering cells

[0150] - RAN2 impact: details of group common HO / CHO signaling, details of pre-configuration for candidate cells, etc., FFS handling of T304, whether / how to send a response to group common signaling, security update after receiving group common signaling.

[0151] NES Sense CHO

[0152] -Introduction: New CHO event trigger considering the NES status of the cell

[0153] -Scenario: single carrier, multi-carrier; UE in connected state

[0154] -NES gain: better control of cell load; avoid low-load cells serving new UEs

[0155] - Impact on legacy UE: Not applicable to legacy UE

[0156] -UE assistance required: None

[0157] -RAN2 impact: Define new trigger conditions based on the relative quality of neighboring cells or cell-specific priorities.

[0158] In the following, technical features related to measurement reporting are described. Reference may be made to section 5.5.4 and part of section 5.5.5 of 3GPP TS 38.331 v17.0.0.

[0159] Measurement report trigger

[0160] If AS security has been successfully activated, the UE shall:

[0161] 1>For each measId included in measIdList in VarMeasConfig:

[0162] 2> If the corresponding reportConfig includes a reportType set to eventTriggered or periodical:

[0163] 3>If the corresponding measObject involves NR:

[0164] 4> If the corresponding reportConfig includes measRSSI-ReportConfig:

[0165] 5> The resources indicated by rmtc-Config on the associated frequency are considered applicable;

[0166] 4>If eventA1 or eventA2 is configured in the corresponding reportConfig:

[0167] 5> It is considered that only the service cell is applicable;

[0168] 4>If eventA3 or eventA5 is configured in the corresponding reportConfig:

[0169] 5> If a serving cell is associated with a measObjectNR and a neighbor is associated with another measObjectNR, any serving cell associated with the other measObjectNR is considered to be also a neighboring cell;

[0170] 4> If the corresponding reportConfig includes a reportType set to periodical; or

[0171] 4>For measurement events other than eventA1 or eventA2:

[0172] 5>If useAllowedCellList is set to true:

[0173] 6> When the relevant cell is included in the allowedCellsToAddModList defined in the VarMeasConfig for this measId, any neighboring cell detected based on the parameters in the associated measObjectNR is considered applicable;

[0174] 5> Otherwise:

[0175] 6> When the relevant cell is not included in the excludedCellsToAddModList defined in the VarMeasConfig for this measId, any neighboring cell detected based on the parameters in the associated measObjectNR is considered applicable;

[0176] 3> Otherwise, if the corresponding measObject involves E-UTRA:

[0177] 4>If eventB1 or eventB2 is configured in the corresponding reportConfig:

[0178] 5> Treat the serving cell (if any) on the associated E-UTRA frequency as a neighbor cell;

[0179] 4> When the relevant cell is not included in the excludedCellsToAddModListEUTRAN defined in VarMeasConfig for this measId, any neighboring cell detected on the associated frequency is considered applicable;

[0180] 3> Otherwise, if the corresponding measObject involves UTRA-FDD:

[0181] 4> If eventB1-UTRA-FDD or eventB2-UTRA-FDD is configured in the corresponding reportConfig; or

[0182] 4>If the corresponding reportConfig includes a reportType set to periodical:

[0183] 5> When the relevant cell is included in the cellsToAddModList defined in the VarMeasConfig for this measId, the neighboring cell on the associated frequency is considered applicable;

[0184] 3> Otherwise, if the corresponding measObject involves L2 U2N relay UE:

[0185] 4>If eventY1-Relay is configured in the corresponding reportConfig; or

[0186] 4>If the corresponding reportConfig includes a reportType set to periodical:

[0187] 5> Any L2 U2N relay UE detected on the associated frequency is considered to be applicable to this measId;

[0188] 2> Otherwise, if the corresponding reportConfig includes a reportType set to reportCGI:

[0189] 3> Cells detected on the associated measObject with a physical cell identity matching the value of cellForWhichToReportCGI included in the corresponding reportConfig within VarMeasConfig are considered applicable;

[0190] 2> Otherwise, if the corresponding reportConfig includes reportType set to reportSFTD:

[0191] 3>If the corresponding measObject involves NR:

[0192] 4>If reportSFTD-meas is set to true:

[0193] 5>NR PSCell is considered applicable;

[0194] 4> Otherwise, if reportSFTD-NeighMeas is included:

[0195] 5>If cellsForWhichToReportSFTD is configured in the corresponding reportConfig:

[0196] 6> Any NR neighbor cell detected on the associated measObjectNR with a physical cell identity included in cellsForWhichToReportSFTD is considered applicable;

[0197] 5> Otherwise:

[0198] 6> When the relevant cell is not included in the excludedCellsToAddModList defined in the VarMeasConfig for this measId, up to 3 strongest NR neighboring cells detected based on the parameters in the associated measObjectNR are considered applicable;

[0199] 3> Otherwise, if the corresponding measObject involves E-UTRA:

[0200] 4>If reportSFTD-Meas is set to true:

[0201] 5> E-UTRAPSCell is considered applicable;

[0202] 2> Otherwise, if the corresponding reportConfig includes a reportType set to cli-Periodical or cli-EventTriggered:

[0203] 3> All CLI measurement resources included in the corresponding measObject are considered applicable;

[0204] 2> Otherwise, if the corresponding reportConfig includes reportType set to rxTxPeriodical:

[0205] 3> All Rx-Tx time difference measurement resources included in the corresponding measObject are considered applicable;

[0206] 2> If the corresponding reportConfig involves a report for NR sidelink communication (i.e., reportConfigNR-SL):

[0207] 3> The transmission resource pool indicated by tx-PoolMeasToAddModList defined in VarMeasConfig for this measId is considered applicable;

[0208] 2> If reportType is set to eventTriggered, and if the entry conditions applicable to the event are met for one or more applicable cells for all measurements after layer 3 filtering made during timeToTrigger defined for the event in VarMeasConfig (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig), and VarMeasReportList does not include a measurement report entry for that measId (the first cell triggers the event):

[0209] 3> Include the measurement report entry in the VarMeasReportList for the measId;

[0210] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0211] 3> Include the relevant cells in the cellsTriggeredList defined in the VarMeasReportList for the measId;

[0212] 3> If useT312 is set to true in reportConfig for the event:

[0213] 4> If the T310 for the corresponding SpCell is running; and

[0214] 4> If T312 is not running for the corresponding SpCell:

[0215] 5> Start timer T312 for the corresponding SpCell, where the value of T312 is configured in the corresponding measObjectNR;

[0216] 3>Initiate measurement report process;

[0217] 2> Otherwise, if reportType is set to eventTriggered, and if the entry conditions applicable to the event (i.e., the events corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) are met for all measurements after layer 3 filtering made during timeToTrigger defined for the event in VarMeasConfig for one or more applicable cells not included in cellsTriggeredList (subsequent cells trigger the event):

[0218] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0219] 3> Include the relevant cells in the cellsTriggeredList defined in the VarMeasReportList for the measId;

[0220] 3> If useT312 is set to true in reportConfig for the event:

[0221] 4> If the T310 for the corresponding SpCell is running; and

[0222] 4> If T312 is not running for the corresponding SpCell:

[0223] 5> Start timer T312 for the corresponding SpCell, where the value of T312 is configured in the corresponding measObjectNR;

[0224] 3>Initiate measurement report process;

[0225] 2> Otherwise, if reportType is set to eventTriggered, and if the leaving condition applicable to the event is met for all measurements after layer 3 filtering made during timeToTrigger defined in VarMeasConfig for the event for one or more cells included in cellsTriggeredList defined in VarMeasReportList for the measId:

[0226] 3>Remove the relevant cells in cellsTriggeredList defined in VarMeasReportList for the measId;

[0227] 3> If reportOnLeave is set to true for the corresponding report configuration:

[0228] 4>Initiate measurement report process;

[0229] 3> If the cellsTriggeredList defined in the VarMeasReportList for the measId is empty:

[0230] 4> Remove the measurement report entry in VarMeasReportList for the measId;

[0231] 4> If it is running, stop the periodic report timer for the measId;

[0232] 2> If reportType is set to eventTriggered, and if the entry conditions applicable to the event are met for one or more applicable L2 U2N relay UEs for all measurements after layer 3 filtering made during timeToTrigger defined for the event in VarMeasConfig (i.e. the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig), and VarMeasReportList does not include a measurement report entry for that measId (first L2 U2N relay UE triggering event):

[0233] 3> Include the measurement report entry in the VarMeasReportList for the measId;

[0234] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0235] 3> Include the relevant L2 U2N relay UE in the relaysTriggeredList defined in the VarMeasReportList for this measId;

[0236] 3>Initiate measurement report process;

[0237] 2> Otherwise, if reportType is set to eventTriggered, and if the entry conditions applicable to the event are met for all measurements after layer 3 filtering made during timeToTrigger defined for this event in VarMeasConfig for one or more applicable L2 U2N relay UEs not included in relaysTriggeredList (i.e., events corresponding to eventId of corresponding reportConfig in VarMeasConfig) (subsequent L2 U2N relay UE triggered event):

[0238] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0239] 3> Include the relevant L2 U2N relay UE in the relaysTriggeredList defined in the VarMeasReportList for this measId;

[0240] 3>Initiate measurement report process;

[0241] 2> Otherwise, if reportType is set to eventTriggered, and if the leaving condition applicable to the event is met for all measurements after layer 3 filtering made during timeToTrigger defined in VarMeasConfig for the event for one or more of the L2U2N relay UEs included in the relaysTriggeredList defined in VarMeasReportList for the measId:

[0242] 3> Remove the relevant L2 U2N relay UE in the relaysTriggeredList defined in the VarMeasReportList for the measId;

[0243] 3> If reportOnLeave is set to true for the corresponding report configuration:

[0244] 4>Initiate measurement report process;

[0245] 3> If the relaysTriggeredList defined in the VarMeasReportList for the measId is empty:

[0246] 4> Remove the measurement report entry in VarMeasReportList for the measId;

[0247] 4> If it is running, stop the periodic report timer for the measId;

[0248] 2> Otherwise, if reportType is set to eventTriggered, and if the entry conditions applicable to the event are met for all measurements made during timeToTrigger defined for the event in VarMeasConfig for one or more applicable transport resource pools (i.e., events corresponding to eventId of the corresponding reportConfig in VarMeasConfig), and VarMeasReportList does not include a measurement report entry for that measId (first transport resource pool triggering event):

[0249] 3> Include the measurement report entry in the VarMeasReportList for the measId;

[0250] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0251] 3> Include the relevant transmission resource pools in the poolsTriggeredList defined in the VarMeasReportList for the measId;

[0252] 3>Initiate measurement report process;

[0253] 2> Otherwise, if reportType is set to eventTriggered, and if the entry conditions applicable to the event are met for all measurements made during timeToTrigger defined for this event in VarMeasConfig for one or more applicable transport resource pools not included in poolsTriggeredList (i.e., events corresponding to eventId of the corresponding reportConfig in VarMeasConfig) (subsequent transport resource pool triggering event):

[0254] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0255] 3> Include the relevant transmission resource pools in the poolsTriggeredList defined in the VarMeasReportList for the measId;

[0256] 3>Initiate measurement report process;

[0257] 2> Otherwise, if reportType is set to eventTriggered, and if the leaving condition applicable to the event is met for all measurements made during timeToTrigger defined in VarMeasConfig for the event for one or more applicable transport resource pools included in poolsTriggeredList defined in VarMeasReportList for the measId:

[0258] 3> Remove the relevant transmission resource pools in poolsTriggeredList defined in VarMeasReportList for the measId;

[0259] 3> If the poolsTriggeredList defined in the VarMeasReportList for the measId is empty:

[0260] 4> Remove the measurement report entry in VarMeasReportList for the measId;

[0261] 4> If it is running, stop the periodic report timer for the measId;

[0262] 2> Otherwise, if reportType is set to eventTriggered, and if eventId is set to eventD1, and if the entry condition applicable to the event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) is met during the timeToTrigger defined in the VarMeasConfig for the event:

[0263] 3> Include the measurement report entry in the VarMeasReportList for the measId;

[0264] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0265] 3>Initiate measurement report process;

[0266] 2> If reportType is set to periodical and if the (first) measurement result is available:

[0267] 3> Include the measurement report entry in the VarMeasReportList for the measId;

[0268] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0269] 3> If the corresponding reportConfig includes measRSSI-ReportConfig:

[0270] 4> When the RSSI sample value is reported by the physical layer after the first L1 measurement duration, the measurement reporting process is immediately initiated;

[0271] 3> Otherwise, if the corresponding reportConfig includes ul-DelayValueConfig:

[0272] 4> Initiate the measurement reporting procedure immediately after the first measurement result is provided from the lower layer associated with the DRB identity;

[0273] 3> Otherwise, if the corresponding reportConfig includes ul-ExcessDelayConfig:

[0274] 4> Initiate the measurement reporting procedure immediately after the first measurement result is provided from the lower layer associated with the DRB identity according to the configured threshold per DRB identity;

[0275] 3> Otherwise, if reportAmount exceeds 1:

[0276] 4> Initiate the measurement reporting procedure immediately after the quantity to be reported becomes available for the NR SpCell or available for serving the L2 U2N relay UE (if the UE is a L2U2N remote UE);

[0277] 3> Otherwise (that is, reportAmount is equal to 1):

[0278] 4> Initiate the measurement reporting procedure immediately after the quantity to be reported becomes available for the NR SpCell and for the strongest cell among the applicable cells, or available for the NR SpCell and for the strongest L2 U2N relay UE among the applicable L2 U2N relay UEs; or initiate the measurement reporting procedure immediately after the quantity to be reported becomes available for serving the L2 U2N relay UE and for the strongest cell among the applicable cells (if the UE is a L2 U2N remote UE);

[0279] 2> If, in the case where the corresponding reportConfig relates to a report for NR sidelink communication, reportType is set to periodical and if the (first) measurement result is available:

[0280] 3> Include the measurement report entry in the VarMeasReportList for the measId;

[0281] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0282] 3> Initiate the measurement reporting procedure immediately after the quantity to be reported becomes available for the NR SpCell and the CBR measurement results become available;

[0283] 2> If reportType is set to cli-EventTriggered, and if the entry conditions applicable to the event are met for one or more applicable CLI measurement resources for all measurements after layer 3 filtering made during timeToTrigger defined for the event in VarMeasConfig (i.e., events corresponding to eventId of the corresponding reportConfig in VarMeasConfig), and VarMeasReportList does not include a measurement report entry for that measId (first CLI measurement resource triggering event):

[0284] 3> Include the measurement report entry in the VarMeasReportList for the measId;

[0285] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0286] 3> Include the relevant CLI measurement resources in the cli-TriggeredList defined in the VarMeasReportList for this measId;

[0287] 3>Initiate measurement report process;

[0288] 2> Otherwise, if reportType is set to cli-EventTriggered, and if the entry conditions applicable to the event are met for all measurements after layer 3 filtering made during timeToTrigger defined for this event in VarMeasConfig for one or more CLI measurement resources not included in cli-TriggeredList (i.e., events corresponding to eventId of the corresponding reportConfig in VarMeasConfig) (subsequent CLI measurement resource triggering event):

[0289] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0290] 3> Include the relevant CLI measurement resources in the cli-TriggeredList defined in the VarMeasReportList for this measId;

[0291] 3>Initiate measurement report process;

[0292] 2> Otherwise, if reportType is set to cli-EventTriggered, and if the leaving conditions applicable to the event are met for all measurements after layer 3 filtering made during timeToTrigger defined in VarMeasConfig for the event for one or more of the CLI measurement resources included in the cli-TriggeredList defined in VarMeasReportList for the measId:

[0293] 3> Remove the relevant CLI measurement resources in the cli-TriggeredList defined in the VarMeasReportList for the measId;

[0294] 3> If reportOnLeave is set to true for the corresponding report configuration:

[0295] 4>Initiate measurement report process;

[0296] 3> If the cli-TriggeredList defined in the VarMeasReportList for the measId is empty:

[0297] 4> Remove the measurement report entry in VarMeasReportList for the measId;

[0298] 4> If it is running, stop the periodic report timer for the measId;

[0299] 2> If reportType is set to cli-Periodical and if the (first) measurement result is available:

[0300] 3> Include the measurement report entry in the VarMeasReportList for the measId;

[0301] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0302] 3> Initiate the measurement reporting procedure immediately after the quantity to be reported becomes available for at least one CLI measurement resource;

[0303] 2> If reportType is set to rxTxPeriodical and if the (first) measurement result is available:

[0304] 3> Include the measurement report entry in the VarMeasReportList for the measId;

[0305] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0306] 3>Initiate measurement report process;

[0307] 2> When the periodic reporting timer for this measId expires:

[0308] 3>Initiate measurement reporting process.

[0309] 2> If the corresponding reportConfig includes reportType is set to reportSFTD:

[0310] 3>If the corresponding measObject involves NR:

[0311] 4> If drx-SFTD-NeighMeas is included:

[0312] 5> If the quantity to be reported becomes available for each requested PCell and NR cell pair:

[0313] 6> Stop timer T322;

[0314] 6>Initiate measurement report process;

[0315] otherwise

[0316] 5> Initiate the measurement reporting procedure immediately after the quantity to be reported becomes available for each requested PCell and NR cell pair or the maximum measurement reporting delay;

[0317] 3> Otherwise, if the corresponding measObject involves E-UTRA:

[0318] 4> Initiate the measurement reporting procedure immediately after the quantity to be reported becomes available for a pair of PCell and E-UTRA PSCell or after the maximum measurement reporting delay;

[0319] 2>If reportType is set to reportCGI:

[0320] 3> If the UE obtains SIB1 or SystemInformationBlockType1 for the requested cell; or

[0321] 3> If the UE detects that the requested NR cell does not send SIB1:

[0322] 4> Stop timer T321;

[0323] 4> Include the measurement report entry in the VarMeasReportList for the measId;

[0324] 4> Set numberOfReportsSent defined in VarMeasReportList for this measId to 0;

[0325] 4>Initiate measurement report process;

[0326] 2> When T321 for this measId expires:

[0327] 3> Include the measurement report entry in the VarMeasReportList for the measId;

[0328] 3> Set numberOfReportsSent defined in VarMeasReportList for the measId to 0;

[0329] 3>Initiate measurement report process;

[0330] 2> When T322 for this measId expires:

[0331] 3>Initiate measurement reporting process.

[0332] The events are as follows:

[0333] - Event A1: Service becomes better than threshold

[0334] - Event A2: Service becomes worse than threshold

[0335] - Event A3: Neighbor becomes better offset than SpCell

[0336] - Event A4: Neighbor becomes better than threshold

[0337] - Event A5: SpCell becomes worse than threshold 1, and the neighbor becomes better than threshold 2

[0338] - Event A6: Neighbor becomes better offset than SCell

[0339] - Event B1: Inter-RAT neighbor becomes better than the threshold

[0340] - Event B2: PCell becomes worse than threshold 1, and inter-RAT neighbors become better than threshold 2

[0341] - Event I1: Interference becomes above the threshold

[0342] - Event C1: NR side link channel busy rate is higher than the threshold

[0343] - Event C2: NR side link channel busy rate is lower than the threshold

[0344] - Event X1: The serving L2 U2N relay UE becomes worse than threshold 1, and the NR cell becomes better than threshold 2

[0345] - Event X2: Serving L2 U2N relay UE becomes worse than threshold

[0346] - Event Y1: PCell becomes worse than threshold 1, and candidate L2 U2N relay UE becomes better than threshold 2

[0347] - Event Y2: Candidate L2 U2N relay UE becomes better than the threshold

[0348] Fig.10 An example of a measurement report is shown.

[0349] The purpose of this procedure is to transfer measurement results from the UE to the network. The UE shall initiate this procedure only after successful AS security activation.

[0350] For the measId for which the measurement report procedure is triggered, the UE sets the measResults in the MeasurementReport message as follows:

[0351] 1> Set measId to the measurement identifier that triggers the measurement report;

[0352] 1> For each serving cell configured with servingCellMO:

[0353] 2> If the reportConfig associated with the measId that triggered the measurement report includes rsType:

[0354] 3> If serving cell measurement based on rsType included in reportConfig that triggers the measurement report is available:

[0355] 4> Set measResultServingCell in measResultServingMOList to include the RSRP, RSRQ and available SINR of the serving cell derived based on the rsType included in reportConfig that triggered the measurement report;

[0356] 2> Otherwise:

[0357] 3> If SSB-based serving cell measurement is available:

[0358] 4> Set measResultServingCell in measResultServingMOList to include RSRP, RSRQ and available SINR of the serving cell derived based on SSB;

[0359] 3> Otherwise, if CSI-RS based serving cell measurement is available:

[0360] 4> Set measResultServingCell in measResultServingMOList to include the RSRP, RSRQ and available SINR of the serving cell derived based on CSI-RS;

[0361] 1> Set servCellId in measResultServingMOList to include each NR serving cell configured with servingCellMO (if any);

[0362] 1> If the reportConfig associated with the measId that triggers the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0363] 2> For each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig;

[0364] 1> If the reportConfig associated with the measId that triggered the measurement report includes reportAddNeighMeas:

[0365] 2> For each measObjectId referenced in measIdList that is also referenced by servingCellMO, except the measObjectId corresponding to the measId that triggered the measurement report:

[0366] 3> If the measObjectNR indicated by servingCellMO includes the RS resource configuration corresponding to the rsType indicated in reportConfig:

[0367] 4> If the RSRP measurement result is available for the cell corresponding to the relevant measObjectNR with the highest measured RSRP, then the measResultBestNeighCell in measResultServingMOList is set to include the physCellId and the available measurement quantity based on the reportQuantityCell and rsType indicated in the reportConfig of the non-serving cell corresponding to the measObjectNR, otherwise if the RSRQ measurement result is available for the cell corresponding to the measObjectNR, it will be the cell with the highest measured RSRQ, otherwise it will be the cell with the highest measured SINR;

[0368] 4> If the reportConfig associated with the measId that triggers the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0369] 5> For each best non-serving cell included in the measurement report:

[0370] 6> Includes beam measurement information according to the associated reportConfig;

[0371] Reporting of beam measurement information

[0372] For the beam measurement information to be included in the measurement report, the UE shall:

[0373] 1>If reportType is set to eventTriggered:

[0374] 2> If available, the trigger quantity is considered as the ranking quantity, otherwise, if available, RSRP is considered as the ranking quantity, otherwise, if available, RSRQ is considered as the ranking quantity, otherwise, SINR is considered as the ranking quantity;

[0375] 1>If reportType is set to periodical:

[0376] 2>If single report quantity is set to true in reportQuantityRS-Indexes;

[0377] 3> The single quantity configured is considered as the sorted quantity;

[0378] 2> Otherwise:

[0379] 3>If rsrp is set to true;

[0380] 4> RSRP is considered as the ranking quantity;

[0381] 3> Otherwise:

[0382] 4> RSRQ is considered as the ranking quantity;

[0383] 1> Set rsIndexResults to include up to maxNrofRS-IndexesToReport SS / PBCH block indices or CSI-RS indices in order of decreasing sort amount as follows:

[0384] 2> If the measurement information to be included is based on SS / PBCH blocks:

[0385] 3> Include in resultsSSB-Indexes the index associated with the best beam for this SS / PBCH block ranking amount, and if absThreshSS-BlocksConsolidation is included in the VarMeasConfig for the measObject associated with the cell to report the beam, the remaining beams with a ranking amount higher than absThreshSS-BlocksConsolidation;

[0386] 3> If includeBeamMeasurements is set to true, include the SS / PBCH-based measurements for quantity in reportQuantityRS-Indexes for each SS / PBCH block index;

[0387] 2> Otherwise, if the beam measurement information to be included is based on CSI-RS:

[0388] 3> include in resultsCSI-RS-Indexes the index associated with the best beam for that CSI-RS ranking amount, and if absThreshCSI-RS-Consolidation is included in the VarMeasConfig for the measObject associated with the cell for which the beam is to be reported, the remaining beams with a ranking amount higher than absThreshCSI-RS-Consolidation;

[0389] 3> If includeBeamMeasurements is set to true, the CSI-RS based measurements for quantity are included in reportQuantityRS-Indexes for each CSI-RS index.

[0390] Conditional Reconfiguration

[0391] The network configures one or more candidate target SpCells to the UE in conditional reconfiguration. The UE evaluates the conditions of each configured candidate target SpCell. The UE applies the conditional reconfiguration associated with one of the target SpCells that satisfies the associated execution condition. The network provides configuration parameters for the target SpCell in the ConditionalReconfiguration IE.

[0392] The UE performs the following actions based on the received ConditionalReconfiguration IE:

[0393] 1> If ConditionalReconfiguration contains condReconfigToRemoveList:

[0394] 2>Execute the conditional reconfiguration removal process;

[0395] 1> If ConditionalReconfiguration contains condReconfigToAddModList:

[0396] 2>Perform conditional reconfiguration additions / modifications;

[0397] Conditional reconfiguration removal

[0398] The UE shall:

[0399] 1> For each condReconfigId value included in condReconfigToRemoveList that is part of the current UE conditional reconfiguration in VarConditionalReconfig:

[0400] 2> Remove the entry with matching condReconfigId from VarConditionalReconfig;

[0401] If the condReconfigToRemoveList includes any condReconfigId value that is not part of the current UE configuration, the UE does not consider the message to be erroneous.

[0402] Conditional reconfiguration additions / modifications

[0403] For each condReconfigId received in the condReconfigToAddModList IE, the UE shall:

[0404] 1> If an entry with a matching condReconfigId exists in condReconfigToAddModList within VarConditionalReconfig:

[0405] 2> If the entries in condReconfigToAddModList include condExecutionCond or condExecutionCondSCG;

[0406] 3>Replace condExecutionCond or condExecutionCondSCG in VarConditionalReconfig with the value received for this condReconfigId;

[0407] 2> If the entries in condReconfigToAddModList include condRRCReconfig;

[0408] 3>Replace condRRCReconfig in VarConditionalReconfig with the value received for this condReconfigId;

[0409] 1> Otherwise:

[0410] 2> Add a new entry in VarConditionalReconfig for the condReconfigId;

[0411] 1>Perform conditional reconfiguration evaluation;

[0412] Conditional Reconfiguration Evaluation

[0413] The UE shall:

[0414] 1>For each condReconfigId in VarConditionalReconfig:

[0415] 2> If the RRCReconfiguration in condRRCReconfig includes a masterCellGroup with reconfigurationWithSync, the cell with a physical cell identity matching the value indicated in ServingCellConfigCommon included in reconfigurationWithSync in the masterCellGroup in the received condRRCReconfig is considered an applicable cell;

[0416] 2> If the RRCReconfiguration in condRRCReconfig includes a secondaryCellGroup with reconfigurationWithSync, the cell having a physical cell identity matching the value indicated in ServingCellConfigCommon included in reconfigurationWithSync in the secondaryCellGroup in the received condRRCReconfig is considered an applicable cell;

[0417] 2> If condExecutionCondSCG is configured:

[0418] 3> In the remaining process, each measId indicated in condExecutionCondSCG is regarded as a measId in VarMeasConfig associated with SCGmeasConfig;

[0419] 2>If condExecutionCond is configured:

[0420] 3> If it is configured via SRB3 or configured via SRB1 in nr-SCG or in nr-SecondaryCellGroupConfig:

[0421] 4> In the remaining process, each measId indicated in condExecutionCond is regarded as a measId in VarMeasConfig associated with SCGmeasConfig;

[0422] 3>Otherwise:

[0423] 4> In the remaining process, each measId indicated in condExecutionCond is treated as a measId in VarMeasConfig associated with MCGmeasConfig;

[0424] 2> For each measId included in the measIdList within the VarMeasConfig indicated in the condExecutionCond or condExecutionCondSCG associated with condReconfigId:

[0425] 3> if condEventId is associated with condEventT1 and the entry conditions applicable to the event associated with condReconfigId are met for the applicable cell, i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig within VarConditionalReconfig; or

[0426] 3> if condEventId is associated with condEventD1, and if the entry conditions applicable to the event associated with condReconfigId are met for the applicable cell during the corresponding timeToTrigger defined for that event in VarConditionalReconfig, i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig in VarConditionalReconfig; or

[0427] 3> If condEventId is associated with condEventA3, condEventA4, or condEventA5, and if the entry conditions applicable to the event associated with condReconfigId are met for all measurements after layer 3 filtering made during the corresponding timeToTrigger defined for that event in VarConditionalReconfig for the applicable cell (i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig in VarConditionalReconfig):

[0428] 4> Consider the events associated with the measId to be satisfied;

[0429] 3> if the measId for the event associated with condReconfigId has been modified; or

[0430] 3> if condEventId is associated with condEventT1 and the leaving condition applicable to the event associated with condReconfigId is met for the applicable cell, i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig within VarConditionalReconfig; or

[0431] 3> if condEventId is associated with condEventD1, and if the leaving condition applicable to the event associated with condReconfigId is satisfied for the applicable cell during the corresponding timeToTrigger defined for that event in VarConditionalReconfig, i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig in VarConditionalReconfig; or

[0432] 3> If condEventId is associated with condEventA3, condEventA4, or condEventA5, and if the leaving condition applicable to the event associated with condReconfigId (i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig in VarConditionalReconfig) is met for all measurements after layer 3 filtering made during the corresponding timeToTrigger defined for that event in VarConditionalReconfig for the applicable cell:

[0433] 4> The event associated with the measId is considered not to be satisfied;

[0434] 2> If the events associated with all measIds in condTriggerConfig of the target candidate cell in the stored condRRCReconfig are met:

[0435] 3> The target candidate cell in the stored condRRCReconfig associated with the condReconfigId is regarded as the triggering cell;

[0436] 3>Initiate conditional reconfiguration execution;

[0437] Up to 2 MeasIds can be configured for each condReconfigId. The conditional reconfiguration events of the 2 MeasIds can have the same or different event conditions, trigger quantities, trigger times, and trigger thresholds.

[0438] Evaluation of SN-initiated conditional reconfiguration of inter-SN CPC for EN-DC

[0439] The UE shall:

[0440] 1>For each condReconfigId in VarConditionalReconfig:

[0441] 1> In the remaining process, each measId indicated in the IE of CondReconfigExecCondSN contained in triggerConditionSN is regarded as a measId in VarMeasConfig associated with SCG measConfig;

[0442] 1> For each measId included in the measIdList within the VarMeasConfig indicated in the CondReconfigExecCondSN contained in the triggerConditionSN associated with the condReconfigurationId:

[0443] 2> If the entry condition applicable to the event associated with this measId is met for the applicable cell for all measurements after layer 3 filtering made during the corresponding timeToTrigger defined for this event associated with this measId:

[0444] 3> Consider satisfying the event;

[0445] 2>If the measId for the event has been modified; or

[0446] 2> If the leaving condition applicable to the event associated with the measId is met for the applicable cell for all measurements after layer 3 filtering made during the corresponding timeToTrigger defined for the event associated with the measId:

[0447] 3> The event associated with the measId is considered not to be satisfied;

[0448] 1> If the trigger conditions for all events associated with the measId indicated in the IE of CondReconfigExecCondSN contained in triggerConditionSN are met:

[0449] 2> The target cell candidate in the RRCReconfiguration message contained in the nr-SecondaryCellGroupConfig in the RRCConnectionReconfiguration message contained in the stored condReconfigurationToApply associated with the condReconfigurationId is regarded as the triggering cell;

[0450] 2>Initiate conditional reconfiguration execution;

[0451] If multiple NR cells are triggered in the conditional reconfiguration execution, it depends on which UE implementation is selected, for example, the UE selects one of the triggered cells for execution considering the beam and beam quality.

[0452] Conditional reconfiguration execution

[0453] The UE shall:

[0454] 1> If there is more than one triggering cell:

[0455] 2> Select one of the triggering cells as the selected cell for conditional reconfiguration execution;

[0456] 1> Otherwise:

[0457] 2> Treat the triggering cell as the selected cell for conditional reconfiguration execution;

[0458] 1> For the selected cell executed for conditional reconfiguration:

[0459] 2> Apply the stored condRRCReconfig of the selected cell and perform the action;

[0460] If multiple NR cells are triggered in the conditional reconfiguration execution, it depends on which UE implementation is selected, for example, the UE selects one of the triggered cells for execution considering the beam and beam quality.

[0461] For example, the ReportConfigNR information element may include distanceThresFromReference1, distanceThresFromReference2. It may indicate the distance from the reference position configured with reference position 1 or reference position 2. Each step size represents 50m.

[0462] In the following, technical features related to the network energy saving solution are described.

[0463] For example, techniques and enhancements for assisting information from UE to assist gNB in ​​performing energy saving techniques are as follows.

[0464] Some examples of auxiliary information are, but are not limited to:

[0465] - Preferred SSB configuration,

[0466] - indication of semi-static UL channel transmission,

[0467] - an indication of the UE buffer status for UL channel transmissions,

[0468] -UE traffic information, such as service priority, delay tolerance, data rate, data volume, traffic type, time criticality and packet size,

[0469] - Coverage, mobility status, location.

[0470] -Conditions for triggering assistance information from the UE

[0471] Network energy saving:

[0472] Millions of base stations (BS) are being deployed to meet the critical performance requirements of 5G networks and the unprecedented growth in mobile subscribers. This rapid growth brings high energy consumption, CO 2 Energy saving is therefore an important use case that may involve different layers of the network, where mechanisms operate at different time scales.

[0473] Cell activation / deactivation is an energy saving scheme in the spatial domain that utilizes traffic offloading in a hierarchical structure to reduce the energy consumption of the entire Radio Access Network (RAN). When the expected traffic volume is below a fixed threshold, the cell can be turned off and the served UEs can be offloaded to a new target cell.

[0474] Efficient energy consumption can also be achieved by other means, such as load reduction, coverage modification or other RAN configuration adjustments. The best energy saving decision depends on many factors, including load conditions at different RAN nodes, RAN node capabilities, KPI / QoS requirements, number of active UEs and UE mobility, cell utilization, etc.

[0475] However, identification of actions aimed at energy efficiency improvement is not a trivial task. Since the remaining active cells need to serve additional services, erroneous deactivation of cells may seriously deteriorate network performance. Erroneous traffic offloading actions may lead to deterioration of energy efficiency rather than improvement. Current energy saving schemes are susceptible to potential problems listed below:

[0476] - Inaccurate cell load prediction: Currently, energy-saving decisions rely on current traffic load without considering future traffic load.

[0477] - Conflicting goals between system performance and energy efficiency. The key performance indicators (KPIs) of a system are often maximized at the expense of energy efficiency. Similarly, the most energy-efficient solution may affect system performance. Therefore, the trade-off between the two needs to be balanced and managed.

[0478] - Conventional energy saving related parameter adjustment. Energy saving related parameter configuration is set by conventional operations, for example, based on different thresholds of cell load for cell on / off, which is a rigid mechanism to some extent because it is difficult to set reasonable thresholds.

[0479] - Actions that may produce local (e.g. limited to a single RAN node) energy efficiency improvements while producing global (e.g. involving multiple RAN nodes) energy efficiency degradations.

[0480] To deal with the problems listed above, ML techniques can be used to optimize energy-saving decisions by leveraging data collected in the RAN network. ML algorithms can predict the energy efficiency and load status of the next period, which can be used to make better decisions for cell activation / deactivation for energy saving. Based on the predicted load, the system can dynamically configure energy-saving strategies (e.g., shutdown timing and granularity, offloading actions) to maintain a balance between system performance and energy efficiency and reduce energy consumption.

[0481] In addition, with Release (Rel)-16 and Rel-17, conditional mobility (such as CHO, CPC, and CPA) is introduced to improve mobility robustness and reduce the latency of mobility execution. If the network configures one or more candidate target cells to the UE in the configuration for conditional mobility, the UE evaluates the conditions of each configured candidate target cell. If the execution condition for conditional mobility is met with respect to one of the target cells, the UE performs conditional mobility to the cell.

[0482] In Rel-18 Network Energy Saving (NES) WI, it is being discussed to pre-configure candidate target cells and trigger HO / CHO using group common signaling. This is for fast Pcell changes when the NES state is activated (e.g., cell shutdown). As one of the solutions, a new CHO event trigger considering the cell NES state is proposed. In this case, if the NES state is activated in the network, the UE performs CHO to the neighbor cell based on the cell quality.

[0483] However, if the UE does not find a suitable cell among the candidates for CHO, it cannot perform CHO, which results in the following connection failure: (i) the UE receives an indication that the NES state is activated (the cell will be shut down soon), (ii) the UE searches for a cell that meets the execution conditions, (iii) the UE stays on the cell until a suitable cell for CHO execution is found, (iv) the connection failure is declared after the cell is shut down, (v) the UE performs RRC re-establishment due to the connection failure.

[0484] Even if the network configures appropriate CHO configuration based on the UE's measurements, it cannot guarantee that there will always be cells that meet the CHO execution conditions when the NES state is activated.

[0485] As a result, changing Pcell may take more time compared to a regular HO procedure. It may also have an impact on data performance and mobility robustness caused by connection failures.

[0486] Therefore, there is a need for research on network energy saving in wireless communication systems.

[0487] Hereinafter, a method for network energy saving in a wireless communication system according to some embodiments of the present disclosure will be described with reference to the following drawings.

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

[0489] Fig.11 An example of a method for network energy saving in a wireless communication system is shown.

[0490] Specifically, Fig.11 An example of a method performed by a wireless device in a wireless communication system is shown.

[0491] In step S1101 , the wireless device may receive configuration for conditional mobility to a target cell from a serving cell.

[0492] For example, a configuration may include a first condition and a second condition.

[0493] For example, the first condition may be a condition for not applying the network energy saving solution, and the second condition may be a condition for applying the network energy saving solution.

[0494] In other words, the second condition is a more relaxed condition than the first condition. The first condition can be called a normal condition. The second condition can be called a relaxed condition.

[0495] For example, at the same time point, the target cell meets the second condition, while the target cell does not meet the first condition. That is, even if the target cell does not meet the first condition (that is, the normal condition), when the network uses the energy-saving solution, the target cell can also meet the second condition (that is, the relaxed condition).

[0496] In other words, the wireless device may use conditional handover in the event that the source cell is using a network power saving scheme.

[0497] In step S1102 , the wireless device may evaluate whether the target cell satisfies a first condition for conditional mobility to the target cell.

[0498] For example, when the target cell satisfies a first condition, the wireless device may perform conditional mobility to the target cell.

[0499] For example, when the target cell does not satisfy the first condition, the wireless device may not perform conditional mobility to the target cell.

[0500] In step S1103 , the wireless device may determine to apply the second condition based on receiving an indication informing the serving cell to use a network energy saving solution.

[0501] For example, the wireless device may receive an indication informing the serving cell to use a network energy saving solution. The wireless device may determine to use the second condition after receiving the indication.

[0502] For example, the indication may also inform the serving cell of the time point at which the network energy saving scheme is started to be used. For example, the indication may include information about the time point at which the serving cell is turned off.

[0503] For example, the network energy saving solution may include shutting down the serving cell. That is, the network may shut down the serving cell as a network energy saving solution.

[0504] For example, the network energy saving scheme may include activating a network energy saving state of a serving cell. That is, when the network uses the energy saving scheme, this may mean that the network activates the energy saving state of the serving cell (that is, the serving cell enters the energy saving state).

[0505] In step S1104 , the wireless device may evaluate whether the target cell satisfies a second condition for conditional mobility.

[0506] For example, based on the target cell satisfying the second condition, the wireless device may perform conditional mobility to the target cell based on the target cell satisfying the second condition.

[0507] For example, based on the target cell not satisfying the second condition, the wireless device may perform a fast recovery process. For example, the fast recovery process may include sending an indication to the serving cell notifying that the target cell does not satisfy the second condition. In other words, based on the target cell not satisfying the second condition, the wireless device may send an indication to the serving cell notifying that the target cell does not satisfy the second condition.

[0508] For example, the fast recovery process may include immediately performing the RRC reestablishment process when evaluating that the target cell does not satisfy the second condition. In other words, when evaluating that the target cell does not satisfy the second condition, the wireless device may immediately perform the RRC reestablishment process.

[0509] For example, regardless of whether a radio link failure (RLF) caused by detecting at least one out-of-sync (OOS) from a physical (PHY) layer of the wireless device is declared, a fast recovery process may be performed. That is, the wireless device may perform a fast recovery process without declaring an RLF caused by an OOS from the PHY layer.

[0510] According to some embodiments of the present disclosure, the wireless device may identify a point in time when the serving cell starts using a network energy saving solution based on the received indication.

[0511] In this case, the wireless device may determine whether the target cell satisfies the second condition for conditional mobility until the time point. Based on the fact that no target cell satisfies the second condition until the time point, the wireless device performs a fast recovery process. For example, based on the fact that the target cell satisfies the second condition until the time point, the wireless device performs conditional mobility to the target cell.

[0512] According to some embodiments of the present disclosure, a wireless device may communicate with at least one of a user device other than the wireless device, a network, or an autonomous vehicle.

[0513] In the following, some embodiments of a method for network energy saving in a wireless communication system are described.

[0514] In the present disclosure, a method is provided for realizing fast cell recovery when a UE does not perform CHO within a certain period of time based on an NES state.

[0515] To this end, the UE may be configured with a CHO configuration, which includes candidates and execution conditions for CHO. Among the execution conditions, the NES state may be one of the conditions. If the network sends an indication indicating that the NES state will be activated in the serving cell, the UE evaluates whether the measurement result satisfies the CHO execution condition in the NES state.

[0516] For example, if a suitable cell is found, the UE performs CHO to the cell. For other examples, if no suitable cell is found, the UE declares "fast cell change failure" and immediately performs RRC reestablishment or sends an indication to the network indicating that there is no suitable CHO configuration.

[0517] As a result, if the PCell change cannot be completed quickly through CHO, the UE can take fast action by itself or through the network. It can also minimize the impact on data performance and mobility robustness caused by connection failures due to NES state changes (e.g., cell closure).

[0518] According to some embodiments of the present disclosure, a wireless device may receive a conditional reconfiguration for a cell from a network. For example, the configuration may include a first execution condition and a second execution condition. For example, if the second execution condition is not configured, the second execution condition may be the same as the first execution condition. The wireless device may apply the first execution condition to perform measurements of the cell. The wireless device may receive an indication that network energy saving is to be activated. The wireless device may apply the second execution condition to perform measurements of the cell. If the measurement result does not meet the second execution condition within a certain time, the wireless device may perform a recovery process. For example, the recovery process may include one of the following items: (i) an RRC reconstruction process, and (ii) sending an indication to the network. For example, the time may be configured from the network.

[0519] Fig.12 An example of a method for network energy saving in a wireless communication system is shown.

[0520] Specifically, Fig.12 An example of a method performed by a UE in a wireless communication system is shown.

[0521] In step S1201, the UE may receive configuration for conditional reconfiguration including information on execution of conditional mobility from a network.

[0522] That is, the network may configure conditional reconfiguration for execution of conditional mobility for the UE.

[0523] 1> Conditional mobility configuration may include conditional reconfiguration and execution conditions for candidate target cells.

[0524] 2>Execution conditions can include NES status conditions

[0525] 3> For example, the NES state condition is on (activated) or off (deactivated).

[0526] 3> If the NES state does not exist, when the UE receives the NES activation state indication, the conditional mobility configuration associated with the execution condition may not be used

[0527] 2>Execution conditions can include one or more thresholds

[0528] 3> The first threshold is for the case where the UE does not receive the NES activation status indication

[0529] 3> The second threshold is for the case where the UE receives the NES activation status indication

[0530] 3> If the second threshold does not exist, the second threshold is the same as the first threshold

[0531] 1> For example, the conditional mobility configuration may include the following items:

[0532] 2>CondRRCReconfig#1

[0533] 3>Conditional reconfiguration parameters in TS 38.331v17.0.0

[0534] 2>CondRRCReconfig#2

[0535] 3>Conditional reconfiguration parameters in TS 38.331v17.0.0

[0536] 2>CondExecutionCond#1

[0537] 3>Conditional execution parameters in TS 38.331v17.0.0

[0538] 2>CondExecutionCond#2

[0539] 3>The first conditional execution condition parameter in TS 38.331v17.0.0

[0540] 3> The second conditional execution condition parameter in TS 38.331v17.0.0

[0541] 3>NES status condition: "Activated"

[0542] 2>CondReconfigId#1

[0543] 3>CondRRCReconfig#1

[0544] 3>CondExecutionCond#1

[0545] 2>CondReconfigId#2

[0546] 3>CondRRCReconfig#2

[0547] 3>CondExecutionCond#2

[0548] 2> In this example,

[0549] 3> Based on conditional reconfiguration ID #1, conditional reconfiguration #1 is associated with conditional execution condition #1. Since there is no NES state condition, when the UE does not receive the NES activation state indication, execution condition #1 is applied to the measurement result.

[0550] 3> Based on conditional reconfiguration ID #2, conditional reconfiguration #2 is associated with conditional execution condition #2. When the UE does not receive the NES activation status indication, the first execution condition is applied to the measurement result. When the UE receives the NES activation status indication, the second execution condition is applied to the measurement result.

[0551] In step S1202, the UE may evaluate a first measurement result based on a first execution condition.

[0552] In step S1203, the UE may receive an indication of NES activation status from the network.

[0553] 1> Indicates that NES time information may be included

[0554] 2> The predicted time information may include the start time value T1

[0555] 2> The predicted time information may include duration T2

[0556] In step S1204, the UE may evaluate the second measurement result based on the second execution condition and the NES time information.

[0557] 1> The second execution condition can be applied from the current time to the time associated with T1

[0558] 2> For example, the time is t+T1, where t is the current time

[0559] 2>For example, time is T1

[0560] In step S1205-1, the UE may perform CHO to a cell that satisfies an execution condition associated with the cell.

[0561] In step S1205-2, if the UE fails to find a cell that meets the execution condition within a certain period of time, the UE may declare that the fast cell change has failed.

[0562] 1> The time may be the time for the UE to complete all cell evaluations based on conditional reconfiguration.

[0563] 1>Time can be related to T1

[0564] 2> For example, the time is t+T1, where t is the current time

[0565] 2> For example, the time is T1

[0566] 1>Time can be related to a preconfigured or predefined time value, for example, T3XX

[0567] 2> Since the UE has received the NES activation status indication, it can be started. If the timer expires, the UE can declare that the fast cell change has failed.

[0568] 2> It can be the interval from T1. At time T1-T3, UE can declare fast cell change failure

[0569] 1>UE can immediately perform the RRC reestablishment process

[0570] 2> The UE may stop (expire) timers associated with radio link failure (such as T310 and T312)

[0571] 1> The UE may send an indication that there is no suitable cell for performing conditional mobility

[0572] 2>Indication can be sent via RRC message

[0573] 3> For example, UE assistance information message

[0574] 3> For example, failure information message (SCG or MCG)

[0575] 3> For example, UE information response message

[0576] 2> Indication can be sent via L1 / L2 signaling

[0577] 2> Indication can be sent via inter-CG signaling

[0578] 2> The indication may include at least one of the following:

[0579] 3> Indication of "No suitable cell"

[0580] 3>UE receives the cell ID and / or cell quality of the cell indicated by the NES activation status

[0581] 3> Cell ID and / or cell quality measured by UE

[0582] 3> Information indicating NES activation status

[0583] 4> For example, time information, such as T1 and T2.

[0584] 4> For example, the time when the UE receives the indication

[0585] In step S1205-3, if the UE does not receive a handover command within a certain period of time, the UE may declare that the fast cell change has failed.

[0586] 1> The same conditions as step S1205-2 can be applied.

[0587] If the network receives an indication that there is no suitable cell for performing conditional mobility, it can help the network decide whether the network can turn it off. It can also be used to receive a handover command from the network.

[0588] In the following, some examples of fast cell recovery from cell change failure based on NES state are described.

[0589] Fig.13 An example of a method using only the CHO configuration associated with the NES state (utilizing T1) is shown.

[0590] Specifically, Fig.13 An example of a method performed by a UE in a wireless communication system is shown.

[0591] In step S1301, the UE may receive a conditional mobility configuration from a network, the conditional mobility configuration including information on conditional reconfiguration and execution conditions for candidates for a target cell.

[0592] That is, the network may configure conditional mobility configuration of a cell, including conditional reconfiguration and execution conditions for candidates for a target cell.

[0593] >Conditional mobility configuration includes two execution conditions for conditional reconfiguration.

[0594] >>First execution condition

[0595] >>Second execution condition

[0596] >>NES Status: Activated

[0597] In step S1302, the UE may evaluate a first measurement result based on a first execution condition.

[0598] In step S1303 , the UE may receive an NES activation status indication with T1 .

[0599] In step S1304, the UE may evaluate the second measurement result based on the second execution condition.

[0600] In step S1305 - 1 , if the second measurement result satisfies the second execution condition within T1 , the UE may perform conditional mobility to a target cell associated with the conditional reconfiguration.

[0601] In step S1305 - 2 , if the second measurement result does not satisfy the second execution condition within T1 , the UE may immediately perform the RRC reestablishment procedure.

[0602] In step S1305-3, if the second measurement result does not meet the second execution condition within T1, the UE may immediately send an indication to the network.

[0603] Fig.14 An example of a method using all CHO configurations regardless of NES status (utilizing T1) is shown.

[0604] Specifically, Fig.14 An example of a method performed by a UE in a wireless communication system is shown.

[0605] In step S1401, the UE may receive a conditional mobility configuration from a network, the conditional mobility configuration including information on conditional reconfiguration and execution conditions for candidates for a target cell.

[0606] That is, the network configures a conditional mobility configuration of a cell, which includes conditional reconfiguration and execution conditions for candidates of a target cell.

[0607] >The conditional mobility configuration includes one or more execution conditions for conditional reconfiguration.

[0608] In step S1402, the UE may evaluate the first measurement result based on the execution condition.

[0609] In step S1403, the UE may receive an NES activation status indication with T1.

[0610] In step S1404, the UE may evaluate the second measurement result based on the execution condition.

[0611] In step S1405 - 1 , if the second measurement result satisfies the execution condition within T1 , the UE may perform conditional mobility to the target cell associated with the conditional reconfiguration.

[0612] In step S1405-2, if the second measurement result does not satisfy the execution condition within T1, the UE may immediately perform the RRC reestablishment procedure.

[0613] In step S1405-3, if the second measurement result does not meet the execution condition within T1, the UE may immediately send an indication to the network.

[0614] Fig.15 An example of a method for early RLF (not utilizing T1) when a cell is switched off is shown.

[0615] Specifically, Fig.15 An example of a method performed by a UE in a wireless communication system is shown.

[0616] In step S1501, the UE may receive a conditional mobility configuration from a network, the conditional mobility configuration including information on conditional reconfiguration and execution conditions for candidates for a target cell.

[0617] That is, the network may configure a conditional mobility configuration of a cell, the conditional mobility configuration including conditional reconfiguration and execution conditions for candidates of a target cell.

[0618] In step S1502, the UE may receive an NES activation status indication.

[0619] >NES activated state may mean that the cell is off.

[0620] >NES activated state may mean that the cell will be shut down at T1.

[0621] In step S1503, the UE may evaluate the measurement result based on the execution condition.

[0622] In step S1504-1, if the measurement result satisfies the execution condition, the UE may perform conditional mobility to a target cell associated with the conditional reconfiguration.

[0623] In step S1504-2, if the second measurement result does not satisfy the second execution condition and if the cell is turned off, the UE may immediately perform the RRC reestablishment procedure.

[0624] Fig.16 An example of a method for early recovery (utilizing T1) utilizing a switching situation is shown.

[0625] Specifically, Fig.16 An example of a method performed by a UE in a wireless communication system is shown.

[0626] In step S1601, the UE may receive a measurement configuration of a cell from a network, where the measurement configuration includes a measurement object and a reporting condition.

[0627] That is, the network may configure the measurement configuration of the cell, which measurement configuration includes the measurement object and the reporting condition.

[0628] In step S1602, the UE may evaluate a first measurement result based on the measurement configuration.

[0629] In step S1603, the UE may receive an NES activation status indication with T1.

[0630] In step S1604, the UE may evaluate the second measurement result based on the measurement configuration.

[0631] In step S1605, the UE may determine whether to send a measurement report based on the second measurement result.

[0632] In step S1605-1, if the second measurement result meets the reporting condition, the UE may send a measurement report.

[0633] In step S1605-2, if the second measurement result meets the reporting condition, the UE may not send a measurement report.

[0634] In step S1606-1, if the UE receives a handover command from the network, the UE may perform handover to a target cell associated with the handover command.

[0635] In step S1606-2, if the UE does not receive a handover command within T1, the UE may immediately perform an RRC reestablishment procedure.

[0636] In step S1606-3, if the UE does not receive a handover command within T1, the UE may immediately send an indication to the network.

[0637] Fig.17 An example of a method for early recovery (utilizing T1) utilizing a switching situation is shown.

[0638] Specifically, Fig.17 An example of a method performed by a UE in a wireless communication system is shown.

[0639] In step S1701, the UE may receive a measurement configuration of a cell from a network, where the measurement configuration includes a measurement object and a reporting condition.

[0640] That is, the network may configure the measurement configuration of the cell, which measurement configuration includes the measurement object and the reporting condition.

[0641] In step S1702, the UE may evaluate a first measurement result based on the measurement configuration.

[0642] In step S1703, the UE may receive an NES activation status indication (cell off).

[0643] In step S1704, the UE may immediately perform the RRC reestablishment procedure.

[0644] Fig.11 , Fig.12 , Fig.13 , Fig.14 , Fig.15 , Fig.16 and Fig.17 Some of the detailed steps shown in the examples may not be necessary steps and may be omitted. Fig.11 , Fig.12 , Fig.13 , Fig.14 , Fig.15 , Fig.16 and Fig.17 In addition to the steps shown, other steps may be added and the order of the steps may be changed. Some of the above steps may have their own technical meanings.

[0645] In the following, a device for network energy saving in a wireless communication system according to some embodiments of the present disclosure will be described. In this article, the device may be Figure 2 , Figure 3 and Figure 5 A wireless device (100 or 200) in.

[0646] For example, the wireless device may perform the above method. Detailed descriptions overlapping with the above content may be simplified or omitted.

[0647] Reference Figure 5 , the wireless device 100 may include a processor 102 , a memory 104 , and a transceiver 106 .

[0648] According to some embodiments of the present disclosure, the processor 102 may be configured to be operatively coupled to the memory 104 and the transceiver 106 .

[0649] The processor 102 may be configured to control the transceiver 106 to receive a configuration for conditional mobility to a target cell from a serving cell. For example, the configuration may include a first condition and a second condition. The processor 102 may be configured to evaluate whether the target cell satisfies the first condition for conditional mobility to the target cell. The processor 102 may be configured to determine to apply the second condition based on receiving an indication notifying the serving cell to use a network energy saving solution. The processor 102 may be configured to evaluate whether the target cell satisfies the second condition for conditional mobility.

[0650] For example, the processor 102 may be configured to perform conditional mobility to the target cell based on the target cell satisfying the second condition.

[0651] For example, the processor 102 may be configured to perform a fast recovery process based on the target cell not satisfying the second condition.

[0652] For example, the fast recovery process may include sending an indication to the serving cell informing the target cell that the second condition is not satisfied.

[0653] For example, the fast recovery process may include immediately performing an RRC reestablishment process when it is evaluated that the target cell does not satisfy the second condition.

[0654] For example, regardless of whether a radio link failure (RLF) caused by detecting at least one out-of-sync (OOS) from a physical layer of a wireless device is declared, a fast recovery procedure may be performed.

[0655] For example, the indication may also inform the serving cell of the time point to start using the network energy saving solution.

[0656] For example, the processor 102 may be configured to determine whether the target cell satisfies the second condition for conditional mobility until a point in time.

[0657] For example, based on the fact that no target cell satisfies the second condition up to the time point, the processor 102 may be configured to perform a fast recovery process.

[0658] For example, a network energy saving scheme may include shutting down a serving cell.

[0659] For example, the network energy saving scheme may include activating a network energy saving state of a serving cell.

[0660] For example, at the same time point, the target cell may satisfy the second condition, while the target cell may not satisfy the first condition.

[0661] For example, the first condition may be a condition that the network energy saving scheme is not applied, and the second condition may be a condition that the network energy saving scheme is applied.

[0662] For example, the processor 102 may be adapted to control the transceiver 106 to communicate with at least one of a user device other than a wireless device, a network, or an autonomous vehicle.

[0663] Hereinafter, a processor of a wireless device for network energy saving in a wireless communication system according to some embodiments of the present disclosure will be described.

[0664] The processor may be configured to control the wireless device to receive a configuration for conditional mobility to a target cell from a serving cell. For example, the configuration may include a first condition and a second condition. The processor may be configured to control the wireless device to evaluate whether the target cell satisfies the first condition for conditional mobility to the target cell. The processor may be configured to control the wireless device to determine to apply the second condition based on receiving an indication notifying the serving cell to use a network energy saving scheme. The processor may be configured to control the wireless device to evaluate whether the target cell satisfies the second condition for conditional mobility.

[0665] For example, the processor may be configured to control the wireless device to perform conditional mobility to the target cell based on the target cell satisfying the second condition.

[0666] For example, the processor may be configured to control the wireless device to perform a fast recovery process based on the target cell not satisfying the second condition.

[0667] For example, the fast recovery process may include sending an indication to the serving cell informing the target cell that the second condition is not satisfied.

[0668] For example, the fast recovery process may include immediately performing an RRC reestablishment process when it is evaluated that the target cell does not satisfy the second condition.

[0669] For example, regardless of whether a radio link failure (RLF) caused by detecting at least one out-of-sync (OOS) from a physical layer of a wireless device is declared, a fast recovery procedure may be performed.

[0670] For example, the indication may also inform the serving cell of the time point to start using the network energy saving solution.

[0671] For example, the processor may be configured to control the wireless device to determine whether the target cell satisfies the second condition for conditional mobility until the point in time.

[0672] For example, based on the fact that no target cell satisfies the second condition until the point in time, the processor may be configured to control the wireless device to perform a fast recovery process.

[0673] For example, a network energy saving scheme may include shutting down a serving cell.

[0674] For example, the network energy saving scheme may include activating a network energy saving state of a serving cell.

[0675] For example, at the same time point, the target cell may satisfy the second condition, while the target cell may not satisfy the first condition.

[0676] For example, the first condition may be a condition that the network energy saving scheme is not applied, and the second condition may be a condition that the network energy saving scheme is applied.

[0677] For example, the processor may be configured to control the wireless device to communicate with at least one of a user device other than the wireless device, a network, or an autonomous vehicle.

[0678] Hereinafter, a non-transitory computer-readable medium having stored thereon a plurality of instructions for network energy saving in a wireless communication system according to some embodiments of the present disclosure will be described.

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

[0680] Some examples of storage media are coupled to a processor so that the processor can read information from the storage media. In an alternative, the storage medium can be integrated into the processor. The processor and the storage medium can reside in an ASIC. For another example, the processor and the storage medium can reside as discrete components.

[0681] The computer-readable medium may include tangible and non-transitory computer-readable storage media.

[0682] 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 foregoing.

[0683] Additionally, the methods described herein may be implemented 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.

[0684] According to some embodiments of the present disclosure, a plurality of instructions are stored on a non-transitory computer-readable medium, and the plurality of stored instructions may be executed by a processor of a wireless device.

[0685] The stored multiple instructions may cause the wireless device to receive a configuration for conditional mobility to a target cell from a serving cell. For example, the configuration may include a first condition and a second condition. The stored multiple instructions may cause the wireless device to evaluate whether the target cell satisfies the first condition for conditional mobility to the target cell. The stored multiple instructions may cause the wireless device to determine to apply the second condition based on receiving an indication notifying the serving cell to use a network energy saving scheme. The stored multiple instructions may cause the wireless device to evaluate whether the target cell satisfies the second condition for conditional mobility.

[0686] For example, the stored plurality of instructions may cause the wireless device to perform conditional mobility to a target cell based on the target cell satisfying a second condition.

[0687] For example, the stored plurality of instructions may cause the wireless device to perform a fast recovery procedure based on the target cell not satisfying the second condition.

[0688] For example, the fast recovery process may include sending an indication to the serving cell informing the target cell that the second condition is not satisfied.

[0689] For example, the fast recovery process may include immediately performing an RRC reestablishment process when it is evaluated that the target cell does not satisfy the second condition.

[0690] For example, regardless of whether a radio link failure (RLF) caused by detecting at least one out-of-sync (OOS) from a physical layer of a wireless device is declared, a fast recovery procedure may be performed.

[0691] For example, the indication may also inform the serving cell of the time point to start using the network energy saving solution.

[0692] For example, the stored plurality of instructions may cause the wireless device to determine whether the target cell satisfies the second condition for conditional mobility until a point in time.

[0693] For example, based on no target cell satisfying the second condition up to the point in time, the stored plurality of instructions may cause the wireless device to perform a fast recovery procedure.

[0694] For example, a network energy saving scheme may include shutting down a serving cell.

[0695] For example, the network energy saving scheme may include activating a network energy saving state of a serving cell.

[0696] For example, at the same time point, the target cell may satisfy the second condition, while the target cell may not satisfy the first condition.

[0697] For example, the first condition may be a condition that the network energy saving scheme is not applied, and the second condition may be a condition that the network energy saving scheme is applied.

[0698] According to some embodiments of the present disclosure, the stored plurality of instructions may enable the wireless device to communicate with at least one of a user device other than the wireless device, a network, or an autonomous vehicle.

[0699] Hereinafter, a method for network energy saving in a wireless communication system performed by a base station (BS) according to some embodiments of the present disclosure will be described.

[0700] The BS may send a configuration for conditional mobility to a target cell to a wireless device in a serving cell. For example, the configuration may include a first condition and a second condition. The BS may send an indication notifying the serving cell to use a network energy saving solution.

[0701] Hereinafter, a base station (BS) for network energy saving in a wireless communication system according to some embodiments of the present disclosure will be described.

[0702] The BS may include a transceiver, a memory, and a processor operatively coupled to the transceiver and the memory.

[0703] The processor may be configured to control the transceiver to provide the wireless device with a configuration for the data service assistance information message. For example, the configuration may include a trigger condition for the data service assistance information message.

[0704] The processor may be configured to control the transceiver to send a configuration for conditional mobility to a target cell to a wireless device in a serving cell. For example, the configuration may include a first condition and a second condition. The processor may be configured to control the transceiver to send an indication to the wireless device notifying the serving cell to use a network energy saving scheme.

[0705] The present disclosure may have various beneficial effects.

[0706] According to some embodiments of the present disclosure, when a network uses a power saving scheme, a wireless device may efficiently perform conditional switching and fast recovery procedures.

[0707] For example, the UE may minimize the impact on data performance and mobility robustness caused by connection failures due to NES state changes (eg, cell closure) either autonomously or by quick action of the network.

[0708] For example, if a Pcell change cannot be made quickly through CHO, the terminal can take action by itself or through the network. When a cell is turned off, interruptions due to connection failures can be prevented, thereby minimizing the impact on data performance and mobility robustness.

[0709] According to some embodiments of the present disclosure, a wireless network system may provide an efficient solution for activating or deactivating a network energy scheme by receiving a predictive data traffic report.

[0710] The beneficial effects that can be obtained by the specific embodiments of the present disclosure are not limited to the beneficial effects listed above. For example, there may be various technical effects that can be understood by a person skilled in the relevant art and / or inferred from the present disclosure. Therefore, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that can be understood or inferred from the technical features of the present disclosure.

[0711] The claims in this disclosure may be combined in various ways. For example, the technical features in the method claims of this disclosure may be combined to be implemented or performed in a device, and the technical features in the device claims may be combined to be implemented or performed in a method. In addition, the technical features in the method claims and the device claims may be combined to be implemented or performed in a device. In addition, the technical features in the method claims and the device claims may be combined to be implemented or performed in a method. Other implementations are within the scope of the appended claims.

Claims

1. A method performed by a wireless device in a wireless communication system, the method comprising the steps of: receiving, from a serving cell, a configuration for conditional mobility to a target cell, wherein the configuration includes a first condition and a second condition; evaluating whether the target cell meets the first condition for the conditional mobility to the target cell; determining to apply the second condition based on receiving an indication notifying the serving cell to use a network energy saving scheme; and evaluating whether the target cell meets the second condition for the conditional mobility.

2. The method according to claim 1, wherein the method further comprises the steps of: performing the conditional mobility to the target cell based on the target cell meeting the second condition.

3. The method according to claim 1, wherein the method further comprises the steps of: performing a fast recovery process based on the target cell not meeting the second condition.

4. The method according to claim 3, wherein the fast recovery process includes sending an indication to the serving cell notifying that the target cell does not meet the second condition.

5. The method according to claim 3, wherein the fast recovery process includes immediately performing an RRC reestablishment process when it is evaluated that the target cell does not meet the second condition.

6. The method according to claim 3, wherein the fast recovery process is performed regardless of whether a radio link failure RLF caused by detecting at least one out-of-sync OOS from the physical layer of the wireless device is declared.

7. The method according to claim 1, wherein the indication further notifies the serving cell of the time point to start using the network energy saving scheme.

8. The method according to claim 7, wherein the method further comprises the steps of: determining whether the target cell meets the second condition for the conditional mobility until the time point.

9. The method according to claim 8, wherein the method further comprises the steps of: performing a fast recovery process based on no target cell meeting the second condition until the time point.

10. The method according to claim 1, wherein the network energy saving scheme includes shutting down the serving cell.

11. The method according to claim 1, wherein the network energy saving scheme includes activating the network energy saving state of the serving cell.

12. The method according to claim 1, wherein at the same time point, the target cell meets the second condition while the target cell does not meet the first condition.

13. The method according to claim 1, wherein the first condition is a condition where the network energy saving scheme is not applied; and wherein the second condition is a condition where the network energy saving scheme is applied.

14. The method according to claim 1, wherein the wireless device communicates with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

15. A wireless device in a wireless communication system, the wireless device comprising: a transceiver; a memory; and At least one processor, the at least one processor being operatively coupled to the transceiver and the memory, and the at least one processor being adapted to: Control the transceiver to receive a configuration for conditional mobility to a target cell from a serving cell, wherein the configuration includes a first condition and a second condition; Evaluate whether the target cell satisfies the first condition for the conditional mobility to the target cell; Based on receiving an indication notifying that the serving cell uses a network energy saving scheme, determine to apply the second condition; and Evaluate whether the target cell satisfies the second condition for the conditional mobility.

16. The wireless device according to claim 15, wherein, the at least one processor is further adapted to: Based on the target cell satisfying the second condition, perform the conditional mobility to the target cell.

17. The wireless device according to claim 15, wherein, the at least one processor is further adapted to: Based on the target cell not satisfying the second condition, perform a fast recovery process.

18. The wireless device according to claim 17, wherein, the fast recovery process includes sending an indication to the serving cell notifying that the target cell does not satisfy the second condition.

19. The wireless device according to claim 17, wherein, the fast recovery process includes immediately performing an RRC reconstruction process when it is evaluated that the target cell does not satisfy the second condition.

20. The wireless device according to claim 17, wherein, Regardless of whether a radio link failure (RLF) caused by detecting at least one out-of-sync (OOS) from the physical layer of the wireless device is declared, the fast recovery process is performed.

21. The wireless device according to claim 15, wherein, the indication further notifies the serving cell of the time point to start using the network energy saving scheme.

22. The wireless device according to claim 21, wherein, the at least one processor is further adapted to: Determine whether the target cell satisfies the second condition for the conditional mobility until the time point.

23. The wireless device according to claim 22, wherein, the at least one processor is further adapted to: Based on no target cell satisfying the second condition until the time point, perform a fast recovery process.

24. The wireless device according to claim 15, wherein, the network energy saving scheme includes shutting down the serving cell.

25. The wireless device according to claim 15, wherein, the network energy saving scheme includes activating the network energy saving state of the serving cell.

26. The wireless device according to claim 15, wherein, At the same time point, the target cell satisfies the second condition while the target cell does not satisfy the first condition.

27. The wireless device according to claim 15, wherein, the first condition is a condition where the network energy saving scheme is not applied; and wherein the second condition is a condition where the network energy saving scheme is applied.

28. The wireless device according to claim 15, wherein, The wireless device communicates with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

29. A processor for a wireless device in a wireless communication system, wherein, the processor is configured to control the wireless device to perform operations, the operations including: receiving, from a serving cell, a configuration for conditional mobility to a target cell, wherein the configuration includes a first condition and a second condition; evaluating whether the target cell satisfies the first condition for the conditional mobility to the target cell; determining to apply the second condition based on receiving an indication notifying that the serving cell uses a network energy saving scheme; and evaluating whether the target cell satisfies the second condition for the conditional mobility.

30. A non-transitory computer-readable medium storing a plurality of instructions, the plurality of instructions, when executed by a processor of a wireless device, cause the wireless device to perform operations, the operations including: receiving, from a serving cell, a configuration for conditional mobility to a target cell, wherein the configuration includes a first condition and a second condition; evaluating whether the target cell satisfies the first condition for the conditional mobility to the target cell; determining to apply the second condition based on receiving an indication notifying that the serving cell uses a network energy saving scheme; and evaluating whether the target cell satisfies the second condition for the conditional mobility.

31. A method performed by a base station in a wireless communication system, the method including the steps of: sending, to a wireless device in a serving cell, a configuration for conditional mobility to a target cell, wherein the configuration includes a first condition and a second condition; and sending to the wireless device an indication notifying that the serving cell uses a network energy saving scheme.

32. A base station in a wireless communication system, the base station including: a transceiver; a memory; and a processor, the processor being operatively coupled to the transceiver and the memory, and the processor being adapted to: send, to a wireless device in a serving cell, a configuration for conditional mobility to a target cell, wherein the configuration includes a first condition and a second condition; and send to the wireless device an indication notifying that the serving cell uses a network energy saving scheme.

Images