EP4233399A1

EP4233399A1 - Method and apparatus for performing measurement in a deactivated state or a dormant state in a wireless communication system

Info

Publication number: EP4233399A1
Application number: EP21883047.9A
Authority: EP
Inventors: Sangwon Kim
Original assignee: LG Electronics Inc
Current assignee: LG Electronics Inc
Priority date: 2020-10-20
Filing date: 2021-09-29
Publication date: 2023-08-30
Also published as: WO2022085975A1; KR20230091864A

Abstract

A method and apparatus for performing measurement in a deactivated state or a dormant state in a wireless communication system is provided. A wireless device receives, from a cell group, a measurement configuration including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state. A wireless device enters the specific state, wherein Physical Downlink Control Channel (PDCCH) monitoring is not performed for all cells belonging to the cell group while in the specific state. A wireless device determines whether to perform measurement on the at least one measurement object in the specific state based on the received information.

Description

METHOD AND APPARATUS FOR PERFORMING MEASUREMENT IN A DEACTIVATED STATE OR A DORMANT STATE IN A WIRELESS COMMUNICATION SYSTEM

The present disclosure relates to a method and apparatus for performing measurement in a deactivated state or a dormant state in a wireless communication system.

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

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

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

NR is a technology that operates on a very wideband compared with LTE. In order to support flexible broadband operation, NR has the following design principles different from LTE in terms of broadband support.

- The ability of the network and the user equipment (UE) to support the bandwidth may be different.

- The bandwidth capabilities of the downlink and uplink supported by the UE may be different.

- The capabilities of the bandwidths supported by each UE may differ, so that UEs supporting different bandwidths may coexist within one network frequency band.

- In order to reduce the power consumption of the UE, the UE may be configured with different bandwidth depending on the traffic load state of the UE, etc.

In order to satisfy the above-mentioned design principles, NR newly introduced a concept of bandwidth part (BWP) in addition to carrier aggregation (CA) of existing LTE.

A new state may be supported in NR. When a cell group enters the new state (for example, the deactivated state or the dormant state), the UE may not perform the PDCCH monitoring for all cells belonging to the cell group for power saving. If UE keeps performing the measurements according to the configuration from a cell group while the cell group is in the new state (for example, the deactivated state or the dormant state), the UE may need to spend lots of power for the measurement. Then, it may decrease the gain of dormant cell group. On the contrary, if UE doesn't perform the measurement for the cell group in dormant state, the UE may keep the bad serving cell even after the serving cell quality becomes worse than a threshold. In this case, the serving cell cannot be used for data reception/transmission, and it may cause that the UE cannot achieve the sufficient user throughput when the corresponding cell group becomes normal state from the new state (for example, a deactivated state or a dormant state).

Therefore, studies for performing measurement in a new state (for example, a deactivated state or a dormant state) in a wireless communication system are required.

In an aspect, a method performed by a wireless device in a wireless communication system is provided. A wireless device receives, from a cell group, a measurement configuration including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state. A wireless device enters the specific state, wherein Physical Downlink Control Channel (PDCCH) monitoring is not performed for all cells belonging to the cell group while in the specific state. A wireless device determines whether to perform measurement on the at least one measurement object in the specific state based on the received information.

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

The present disclosure can have various advantageous effects.

According to some embodiments of the present disclosure, a wireless device could minimize the power consumption for measurement in a new state (for example, a deactivated state or a dormant state).

For example, a wireless device may efficiently perform measurement when a cell group becomes the dormant state, by determining whether to perform the measurement for the configured measurement object based on the measurement indication.

Since, a wireless device may not perform measurement on all measurement objects in the new state and only perform measurement on a part of the measurement objects in the new state, the wireless device could reduce the power consumption for measurement in the new state.

According to some embodiments of the present disclosure, a wireless communication system could efficiently support measurement in a new state (for example, a deactivated state or a dormant state).

For example, a network may not need to re-configure the measurement object whenever the state of a cell group is changed to reduce the power consumption for measurements.

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

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

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

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

FIG. 4 shows another example of wireless devices to which implementations of the present disclosure is applied.

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

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

FIG. 8 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

FIG. 9 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.

FIG. 10 shows an example of bandwidth part (BWP) configurations to which implementations of the present disclosure is applied.

FIG. 11 shows an example of contiguous BWPs and non-contiguous BWPs to which implementations of the present disclosure is applied

FIG. 12 shows an example of multiple BWPs to which implementations of the present disclosure is applied.

FIG. 13 shows an example of a method for performing measurement in a deactivated state or a dormant state in a wireless communication system, according to some embodiments of the present disclosure.

FIG. 14 shows an example of a method for performing measurement in a deactivated state or a dormant state in a wireless communication system, according to some embodiments of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Wireless communication/connections 150a, 150b and 150c may be established between the wireless devices 100a to 100f and/or between wireless device 100a to 100f and BS 200 and/or between BSs 200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc. The wireless devices 100a to 100f and the BSs 200/the wireless devices 100a to 100f may transmit/receive radio signals to/from each other through the wireless communication/connections 150a, 150b and 150c. For example, the wireless communication/connections 150a, 150b and 150c may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/de-mapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.

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

Referring to FIG. 2, a first wireless device 100 and a second wireless device 200 may transmit/receive radio signals to/from an external device through a variety of RATs (e.g., LTE and NR). In FIG. 2, {the first wireless device 100 and the second wireless device 200} may correspond to at least one of {the wireless device 100a to 100f and the BS 200}, {the wireless device 100a to 100f and the wireless device 100a to 100f} and/or {the BS 200 and the BS 200} of FIG. 1.

The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and/or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor(s) 102 may process information within the memory(s) 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) 106. The processor(s) 102 may receive radio signals including second information/signals through the transceiver(s) 106 and then store information obtained by processing the second information/signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102. For example, the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. Herein, the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 106 may be connected to the processor(s) 102 and transmit and/or receive radio signals through one or more antennas 108. Each of the transceiver(s) 106 may include a transmitter and/or a receiver. The transceiver(s) 106 may be interchangeably used with radio frequency (RF) unit(s). In the present disclosure, the first wireless device 100 may represent a communication modem/circuit/chip.

The second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally further include one or more transceivers 206 and/or one or more antennas 208. The processor(s) 202 may control the memory(s) 204 and/or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor(s) 202 may process information within the memory(s) 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s) 206. The processor(s) 202 may receive radio signals including fourth information/signals through the transceiver(s) 106 and then store information obtained by processing the fourth information/signals in the memory(s) 204. The memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202. For example, the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. Herein, the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive radio signals through one or more antennas 208. Each of the transceiver(s) 206 may include a transmitter and/or a receiver. The transceiver(s) 206 may be interchangeably used with RF unit(s). In the present disclosure, the second wireless device 200 may represent a communication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer). The one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and/or one or more service data unit (SDUs) according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.

The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102 and 202. descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and/or a set of commands.

The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories 104 and 204 may be configured by read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

The one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.

The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208. In the present disclosure, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

The one or more transceivers 106 and 206 may convert received radio signals/channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters. For example, the transceivers 106 and 206 can up-convert OFDM baseband signals to a carrier frequency by their (analog) oscillators and/or filters under the control of the processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and/or filters under the control of the transceivers 102 and 202.

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

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

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

Referring to FIG. 3, wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit 110 may include a communication circuit 112 and transceiver(s) 114. For example, the communication circuit 112 may include the one or more processors 102 and 202 of FIG. 2 and/or the one or more memories 104 and 204 of FIG. 2. For example, the transceiver(s) 114 may include the one or more transceivers 106 and 206 of FIG. 2 and/or the one or more antennas 108 and 208 of FIG. 2. The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140 and controls overall operation of each of the wireless devices 100 and 200. For example, the control unit 120 may control an electric/mechanical operation of each of the wireless devices 100 and 200 based on programs/code/commands/information stored in the memory unit 130. The control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface or store, in the memory unit 130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit 110.

The additional components 140 may be variously configured according to types of the wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit (e.g., audio I/O port, video I/O port), a driving unit, and a computing unit. The wireless devices 100 and 200 may be implemented in the form of, without being limited to, the robot (100a of FIG. 1), the vehicles (100b-1 and 100b-2 of FIG. 1), the XR device (100c of FIG. 1), the hand-held device (100d of FIG. 1), the home appliance (100e of FIG. 1), the IoT device (100f of FIG. 1), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a FinTech device (or a finance device), a security device, a climate/environment device, the AI server/device (400 of FIG. 1), the BSs (200 of FIG. 1), a network node, etc. The wireless devices 100 and 200 may be used in a mobile or fixed place according to a use-example/service.

In FIG. 3, the entirety of the various elements, components, units/portions, and/or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit/portion, and/or module within the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be configured by a set of one or more processors. As an example, the control unit 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory 130 may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.

Referring to FIG. 4, wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules.

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

The second wireless device 200 may include at least one transceiver, such as a transceiver 206, and at least one processing chip, such as a processing chip 201. The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. The memory 204 may be operably connectable to the processor 202. The memory 204 may store various types of information and/or instructions. The memory 204 may store a software code 205 which implements instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may control the processor 202 to perform one or more protocols. For example, the software code 205 may control the processor 202 may perform one or more layers of the radio interface protocol.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The frame structure shown in FIG. 8 is purely exemplary and the number of subframes, the number of slots, and/or the number of symbols in a frame may be variously changed. In the 3GPP based wireless communication system, OFDM numerologies (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) may be differently configured between a plurality of cells aggregated for one UE. For example, if a UE is configured with different SCSs for cells aggregated for the cell, an (absolute time) duration of a time resource (e.g., a subframe, a slot, or a TTI) including the same number of symbols may be different among the aggregated cells. Herein, symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols).

Referring to FIG. 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 of the half-frames has 5ms duration. Each half-frame consists of 5 subframes, where the duration T_sf per subframe is 1ms. Each subframe is divided into slots and the number of slots in a subframe depends on a 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 numerology is based on exponentially scalable subcarrier spacing △f = 2^u*15 kHz.

Table 1 shows the number of OFDM symbols per slot N^slot _symb, the number of slots per frame N^frame,u _slot, and the number of slots per subframe N^subframe,u _slot for the normal CP, according to the subcarrier spacing △f = 2^u*15 kHz.

u	N ^slot _symb	N ^frame,u _slot	N ^subframe,u _slot
0	14	10	1
1	14	20	2
2	14	40	4
3	14	80	8
4	14	160	16

Table 2 shows the number of OFDM symbols per slot N^slot _symb, the number of slots per frame N^frame,u _slot, and the number of slots per subframe N^subframe,u _slot for the extended CP, according to the subcarrier spacing △f = 2^u*15 kHz.

u	N ^slot _symb	N ^frame,u _slot	N ^subframe,u _slot
2	12	40	4

A slot includes plural symbols (e.g., 14 or 12 symbols) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a resource grid of N ^size,u _grid,x*N ^RB _sc subcarriers and N ^subframe,u _symb OFDM symbols is defined, starting at common resource block (CRB) N ^start,u _grid indicated by higher-layer signaling (e.g., RRC signaling), where N ^size,u _grid,x is the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink. N ^RB _sc is the number of subcarriers per RB. In the 3GPP based wireless communication system, N ^RB _sc is 12 generally. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). The carrier bandwidth N ^size,u _grid for subcarrier spacing configuration u is given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna port p and the subcarrier spacing configuration u is referred to as a resource element (RE) and one complex symbol may 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 a symbol location relative to a reference point in the time domain. In the 3GPP based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain.

In the 3GPP NR system, RBs are classified into CRBs and physical resource blocks (PRBs). CRBs are numbered from 0 and upwards 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' which serves as a common reference point for resource block grids. In the 3GPP NR system, PRBs are defined within a bandwidth part (BWP) and numbered from 0 to N ^size _BWP,i-1, where i is the number of the bandwidth part. The relation between the physical resource block n_PRB in the bandwidth part i and the common resource block n_CRB is as follows: n_PRB = n_CRB + N ^size _BWP,i, where N ^size _BWP,i is the common resource block where bandwidth part starts relative to CRB 0. The BWP includes a plurality of consecutive RBs. A carrier may include a maximum of N (e.g., 5) BWPs. A UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.

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

Frequency Range designation	Corresponding frequency range	Subcarrier Spacing
FR1	450MHz - 6000MHz	15, 30, 60kHz
FR2	24250MHz - 52600MHz	60, 120, 240kHz

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

Frequency Range designation	Corresponding frequency range	Subcarrier Spacing
FR1	410MHz - 7125MHz	15, 30, 60kHz
FR2	24250MHz - 52600MHz	60, 120, 240kHz

In the present disclosure, the term "cell" may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources. A "cell" as a geographic area may be understood as coverage within which a node can provide service using a carrier and a "cell" as radio resources (e.g., time-frequency resources) is associated with bandwidth which is a frequency range configured by the carrier. The "cell" associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a DL component carrier (CC) and a UL CC. The cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depends upon a carrier carrying the signal, the coverage of the node may be associated with coverage of the "cell" of radio resources used by the node. Accordingly, the term "cell" may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times.

In CA, two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs. When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment/re-establishment/handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment/handover, one serving cell provides the security input. This cell is referred to as the primary cell (PCell). The PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on UE capabilities, secondary cells (SCells) can be configured to form together with the PCell a set of serving cells. An SCell is a cell providing additional radio resources on top of special cell (SpCell). The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. For dual connectivity (DC) operation, the term SpCell refers to the PCell of the master cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG). An SpCell supports PUCCH transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node, comprised of the SpCell (PCell) and optionally one or more SCells. The SCG is the subset of serving cells associated with a secondary node, comprised of the PSCell and zero or more SCells, for a UE configured with DC. For a UE in RRC_CONNECTED not configured with CA/DC, there is only one serving cell comprised of the PCell. For a UE in RRC_CONNECTED configured with CA/DC, the term "serving cells" is used to denote the set of cells comprised of the SpCell(s) and all SCells. In DC, two MAC entities are configured in a UE: one for the MCG and one for the SCG.

Referring to FIG. 9, "RB" denotes a radio bearer, and "H" denotes a header. Radio bearers are categorized into two groups: DRBs for user plane data and SRBs for control plane data. The MAC PDU is transmitted/received using radio resources through the PHY layer to/from an external device. The MAC PDU arrives to the PHY layer in the form of a transport block.

In the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to their physical channels PUSCH and PRACH, respectively, and the 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 PUCCH, and downlink control information (DCI) is mapped to PDCCH. A MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant, and a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment.

Hereinafter, technical features related to measurements are described. Section 5.5 of 3GPP TS 38.331 v16.1.0 may be referred.

The network may configure an RRC_CONNECTED UE to perform measurements. The network may configure the UE to report them in accordance with the measurement configuration or perform conditional reconfiguration evaluation in accordance with the conditional reconfiguration. The measurement configuration is provided by means of dedicated signalling i.e. using the RRCReconfiguration or RRCResume .

The network may configure the UE to perform the following types of measurements:

- NR measurements;

- Inter-RAT measurements of E-UTRA frequencies.

- Inter-RAT measurements of UTRA-FDD frequencies.

The network may configure the UE to report the following measurement information based on SS/PBCH block(s):

- Measurement results per SS/PBCH block;

- Measurement results per cell based on SS/PBCH block(s);

- SS/PBCH block(s) indexes.

The network may configure the UE to report the following measurement information based on CSI-RS resources:

- Measurement results per CSI-RS resource;

- Measurement results per cell based on CSI-RS resource(s);

- CSI-RS resource measurement identifiers.

The network may configure the UE to perform the following types of measurements for sidelink:

- CBR measurements.

The network may configure the UE to report the following measurement information based on SRS resources:

- Measurement results per SRS resource;

- SRS resource(s) indexes.

The network may configure the UE to report the following measurement information based on CLI-RSSI resources:

- Measurement results per CLI-RSSI resource;

- CLI-RSSI resource(s) indexes.

The measurement configuration includes the following parameters:

1. Measurement objects: A list of objects on which the UE shall perform the measurements.

- For intra-frequency and inter-frequency measurements a measurement object indicates the frequency/time location and subcarrier spacing of reference signals to be measured. Associated with this measurement object, the network may configure a list of cell specific offsets, a list of 'blacklisted' cells and a list of 'whitelisted' cells. Blacklisted cells are not applicable in event evaluation or measurement reporting. Whitelisted cells are the only ones applicable in event evaluation or measurement reporting.

- The measObjectId of the MO which corresponds to each serving cell is indicated by servingCellMO within the serving cell configuration.

- For inter-RAT E-UTRA measurements a measurement object is a single E-UTRA carrier frequency. Associated with this E-UTRA carrier frequency, the network can configure a list of cell specific offsets, a list of 'blacklisted' cells and a list of 'whitelisted' cells. Blacklisted cells are not applicable in event evaluation or measurement reporting. Whitelisted cells are the only ones applicable in event evaluation or measurement reporting.

- For inter-RAT UTRA-FDD measurements a measurement object is a set of cells on a single UTRA-FDD carrier frequency.

- For CBR measurement of NR sidelink communication, a measurement object is a set of transmission resource pool(s) on a single carrier frequency for NR sidelink communication.

- For CLI measurements a measurement object indicates the frequency/time location of SRS resources and/or CLI-RSSI resources, and subcarrier spacing of SRS resources to be measured.

2. Reporting configurations: A list of reporting configurations where there can be one or multiple reporting configurations per measurement object. Each measurement reporting configuration consists of the following:

- Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description.

- RS type: The RS that the UE uses for beam and cell measurement results (SS/PBCH block or CSI-RS).

- Reporting format: The quantities per cell and per beam that the UE includes in the measurement report (e.g. RSRP) and other associated information such as the maximum number of cells and the maximum number beams per cell to report.

In case of conditional reconfiguration triggering configuration, each configuration consists of the following:

- Execution criteria: The criteria that triggers the UE to perform conditional reconfiguration execution.

- RS type: The RS that the UE uses for beam and cell measurement results (SS/PBCH block or CSI-RS) for conditional reconfiguration execution condition.

3. Measurement identities: For measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities, it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object. The measurement identity is also included in the measurement report that triggered the reporting, serving as a reference to the network. For conditional reconfiguration triggering, one measurement identity links to exactly one conditional reconfiguration trigger configuration. And up to 2 measurement identities can be linked to one conditional reconfiguration execution condition.

4. Quantity configurations: The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement. For NR measurements, the network may configure up to 2 quantity configurations with a reference in the NR measurement object to the configuration that is to be used. In each configuration, different filter coefficients can be configured for different measurement quantities, for different RS types, and for measurements per cell and per beam.

5. Measurement gaps: Periods that the UE may use to perform measurements.

A UE in RRC_CONNECTED maintains a measurement object list, a reporting configuration list, and a measurement identities list according to signalling and procedures in this specification. The measurement object list possibly includes NR measurement object(s) , CLI measurement object(s) and inter-RAT objects. Similarly, the reporting configuration list includes NR and inter-RAT reporting configurations. Any measurement object can be linked to any reporting configuration of the same RAT type. Some reporting configurations may not be linked to a measurement object. Likewise, some measurement objects may not be linked to a reporting configuration.

The measurement procedures distinguish the following types of cells:

1. The NR serving cell(s) - these are the SpCell and one or more SCells.

2. Listed cells - these are cells listed within the measurement object(s).

3. Detected cells - these are cells that are not listed within the measurement object(s) but are detected by the UE on the SSB frequency(ies) and subcarrier spacing(s) indicated by the measurement object(s).

For NR measurement object(s), the UE measures and reports on the serving cell(s), listed cells and/or detected cells. For inter-RAT measurements object(s) of E-UTRA, the UE measures and reports on listed cells and detected cells and, for RSSI and channel occupancy measurements, the UE measures and reports on the configured resources on the indicated frequency. For inter-RAT measurements object(s) of UTRA-FDD, the UE measures and reports on listed cells. For CLI measurement object(s), the UE measures and reports on configured CLI measurement resources (i.e. SRS resources and/or CLI-RSSI resources).

Whenever the procedural specification refers to a field it concerns a field included in the VarMeasConfig unless explicitly stated otherwise i.e. only the measurement configuration procedure covers the direct UE action related to the received measConfig.

In NR-DC, the UE may receive two independent measConfig:

- a measConfig, associated with MCG, that is included in the RRCReconfiguration message received via SRB1; and

- a measConfig, associated with SCG, that is included in the RRCReconfiguration message received via SRB3, or, alternatively, included within a RRCReconfiguration message embedded in a RRCReconfiguration message received via SRB1.

In this case, the UE maintains two independent VarMeasConfig and VarMeasReportList, one associated with each measConfig, and independently performs all the procedures for each measConfig and the associated VarMeasConfig and VarMeasReportList, unless explicitly stated otherwise.

The configurations related to CBR measurements are only included in the measConfig associated with MCG.

Measurement configuration may be described.

The network applies the procedure as follows:

- to ensure that, whenever the UE has a measConfig associated with a CG, it includes a measObject for the SpCell and for each NR SCell of the CG to be measured;

- to configure at most one measurement identity across all CGs using a reporting configuration with the reportType set to reportCGI ;

- to configure at most one measurement identity per CG using a reporting configuration with the ul - DelayValueConfig ;

- to ensure that, in the measConfig associated with a CG:

- for all SSB based measurements there is at most one measurement object with the same ssbFrequency;

- an smtc1 included in any measurement object with the same ssbFrequency has the same value and that an smtc2 included in any measurement object with the same ssbFrequency has the same value;

- to ensure that all measurement objects configured in this specification with the same ssbFrequency have the same ssbSubcarrierSpacing;

- to ensure that, if a measurement object associated with the MCG has the same ssbFrequency as a measurement object associated with the SCG:

- for that ssbFrequency, the measurement window according to the smtc1 configured by the MCG includes the measurement window according to the smtc1 configured by the SCG, or vice-versa, with an accuracy of the maximum receive timing difference.

- if both measurement objects are used for RSSI measurements, bits in measurementSlots in both objects corresponding to the same slot are set to the same value. Also, the endSymbol is the same in both objects.

- to ensure that, if a measurement object has the same ssbFrequency as a measurement object:

- for that ssbFrequency, the measurement window according to the smtc includes the measurement window according to the smtc1, or vice-versa, with an accuracy of the maximum receive timing difference.

- when the UE is in NE-DC, NR-DC, or NR standalone, to configure at most one measurement identity across all CGs using a reporting configuration with the reportType set to reportSFTD;

For CSI-RS resources, the network applies the procedure as follows:

- to ensure that all CSI-RS resources configured in each measurement object have the same center frequency, (startPRB+floor(nrofPRBs/2))

Measurement identity removal is described.

The UE shall:

1> for each measId included in the received measIdToRemoveList that is part of the current UE configuration in VarMeasConfig:

2> remove the entry with the matching measId from the measIdList within the VarMeasConfig;

2> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

2> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId.

The UE does not consider the message as erroneous if the measIdToRemoveList includes any measId value that is not part of the current UE configuration.

Measurement identity addition/modification is described.

The network applies the procedure as follows:

- configure a measId only if the corresponding measurement object, the corresponding reporting configuration and the corresponding quantity configuration, are configured.

The UE shall:

1> for each measId included in the received measIdToAddModList:

2> if an entry with the matching measId exists in the measIdList within the VarMeasConfig:

3> replace the entry with the value received for this measId;

2> else:

3> add a new entry for this measId within the VarMeasConfig;

2> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId;

2> if the reportType is set to reportCGI in the reportConfig associated with this measId:

3> if the measObject associated with this measId concerns E-UTRA:

4> if the useAutonomousGaps is included in the reportConfig associated with this measId:

5> start timer T321 for this measId;

4> else:

5> start timer T321 with the timer value set to 1 second for this measId;

3> if the measObject associated with this measId concerns NR:

4> if the measObject associated with this measId concerns FR1:

5> if the useAutonomousGaps is included in the reportConfig associated with this measId:

6> start timer T321 with the timer value set to 2 seconds for this measId;

5> else:

6> start timer T321 with the timer value set to 2 seconds for this measId;

4> if the measObject associated with this measId concerns FR2:

6> start timer T321 for this measId;

5> else:

6> start timer T321 with the timer value set to 16 seconds for this measId.

2> if the reportType is set to reportSFTD in the reportConfigNR associated with this measId and the drx - SFTD - NeighMeas is included:

3> if the measObject associated with this measId concerns FR1:

4> start timer T322 with the timer value set to 3 seconds for this measId;

3> if the measObject associated with this measId concerns FR2:

4> start timer T322 with the timer value set to 24 seconds for this measId.

Measurement object removal is described.

The UE shall:

1> for each measObjectId included in the received measObjectToRemoveList that is part of measObjectList in VarMeasConfig:

2> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;

2> remove all measId associated with this measObjectId from the measIdList within the VarMeasConfig, if any;

2> if a measId is removed from the measIdList:

3> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

3> stop the periodical reporting timer or timer T321 or timer T322, whichever is running, and reset the associated information (e.g. timeToTrigger) for this measId.

The UE does not consider the message as erroneous if the measObjectToRemoveList includes any measObjectId value that is not part of the current UE configuration.

Measurement object addition/modification is described.

The UE shall:

1> for each measObjectId included in the received measObjectToAddModList:

2> if an entry with the matching measObjectId exists in the measObjectList within the VarMeasConfig, for this entry:

3> reconfigure the entry with the value received for this measObject, except for the fields cellsToAddModList, blackCellsToAddModList, whiteCellsToAddModList, cellsToRemoveList, blackCellsToRemoveList and whiteCellsToRemoveList;

3> if the received measObject includes the cellsToRemoveList:

4> for each physCellId included in the cellsToRemoveList:

5> remove the entry with the matching physCellId from the cellsToAddModList;

3> if the received measObject includes the cellsToAddModList:

4> for each physCellId value included in the cellsToAddModList:

5> if an entry with the matching physCellId exists in the cellsToAddModList:

6> replace the entry with the value received for this physCellId;

5> else:

6> add a new entry for the received physCellId to the cellsToAddModList;

3> if the received measObject includes the blackCellsToRemoveList:

4> for each pci - RangeIndex included in the blackCellsToRemoveList:

5> remove the entry with the matching pci - RangeIndex from the blackCellsToAddModList;

For each pci - RangeIndex included in the blackCellsToRemoveList that concerns overlapping ranges of cells, a cell is removed from the blacklist of cells only if all PCI ranges containing it are removed.

3> if the received measObject includes the blackCellsToAddModList:

4> for each pci - RangeIndex included in the blackCellsToAddModList:

5> if an entry with the matching pci - RangeIndex is included in the blackCellsToAddModList:

6> replace the entry with the value received for this pci -RangeIndex;

5> else:

6> add a new entry for the received pci - RangeIndex to the blackCellsToAddModList;

3> if the received measObject includes the whiteCellsToRemoveList:

4> for each pci - RangeIndex included in the whiteCellsToRemoveList:

5> remove the entry with the matching pci - RangeIndex from the whiteCellsToAddModList;

For each pci - RangeIndex included in the whiteCellsToRemoveList that concerns overlapping ranges of cells, a cell is removed from the whitelist of cells only if all PCI ranges containing it are removed.

3> if the received measObject includes the whiteCellsToAddModList:

4> for each pci - RangeIndex included in the whiteCellsToAddModList:

5> if an entry with the matching pci - RangeIndex is included in the whiteCellsToAddModList:

6> replace the entry with the value received for this pci -RangeIndex;

5> else:

6> add a new entry for the received pci - RangeIndex to the whiteCellsToAddModList

3> for each measId associated with this measObjectId in the measIdList within the VarMeasConfig, if any:

4> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

4> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId;

3> if the received measObject includes the tx- PoolMeasToRemoveList:

4> for each transmission resource pool indicated in tx-PoolMeasToRemoveList:

5> remove the entry with the matching identity of the transmission resource pool from the tx- PoolMeasToAddModList;

3> if the received measObject includes the tx- PoolMeasToAddModList:

4> for each transmission resource pool indicated in tx-PoolMeasToAddModList:

5> if an entry with the matching identity of the transmission resource pool exists in the tx- PoolMeasToAddModList:

6> replace the entry with the value received for this transmission resource pool;

5> else:

6> add a new entry for the received identity of the transmission resource pool to the tx- PoolMeasToAddModList;

3> if the received measObject includes the ssb - PositionQCL -CellsToRemoveList:

4> for each physCellId included in the ssb - PositionQCL -CellsToRemoveList:

5> remove the entry with the matching physCellId from the ssb -PositionQCL-CellsToAddModList;

3> if the received measObject includes the ssb - PositionQCL -CellsToAddModList:

4> for each physCellId included in the ssb - PositionQCL -CellsToAddModList:

5> if an entry with the matching physCellId exists in the ssb -PositionQCL-CellsToAddModList:

6> replace the entry with the value received for this physCellId;

5> else:

6> add a new entry for the received physCellId to the ssb -PositionQCL-CellsToAddModList;

2> else:

3> add a new entry for the received measObject to the measObjectList within VarMeasConfig.

Performing measurements is described.

An RRC_CONNECTED UE shall derive cell measurement results by measuring one or multiple beams associated per cell as configured by the network. For all cell measurement results and CLI measurement results in RRC_CONNECTED, except for RSSI, the UE applies the layer 3 filtering, before using the measured results for evaluation of reporting criteria, measurement reporting or the criteria to trigger conditional reconfiguration execution. For cell measurements, the network can configure RSRP, RSRQ, SINR, RSCP or EcN0 as trigger quantity. For CLI measurements, the network can configure SRS-RSRP or CLI-RSSI as trigger quantity. For cell and beam measurements, reporting quantities can be any combination of quantities (i.e. only RSRP; only RSRQ; only SINR; RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR; only RSCP; only EcN0; RSCP and EcN0), irrespective of the trigger quantity, and for CLI measurements, reporting quantities can be only SRS-RSRP or only CLI-RSSI. For conditional reconfiguration execution, the network can configure up to 2 quantities, both using same RS type. The UE does not apply the layer 3 filtering to derive the CBR measurements.

The network may also configure the UE to report measurement information per beam (which can either be measurement results per beam with respective beam identifier(s) or only beam identifier(s)). If beam measurement information is configured to be included in measurement reports, the UE applies the layer 3 beam filtering. On the other hand, the exact L1 filtering of beam measurements used to derive cell measurement results is implementation dependent.

The UE shall:

1> whenever the UE has a measConfig, perform RSRP and RSRQ measurements for each serving cell for which servingCellMO is configured as follows:

2> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains an rsType set to ssb and ssb -ConfigMobility is configured in the measObject indicated by the servingCellMO:

3> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains a reportQuantityRS -Indexes and maxNrofRS - IndexesToReport and contains an rsType set to ssb:

4> derive layer 3 filtered RSRP and RSRQ per beam for the serving cell based on SS/PBCH block;

3> derive serving cell measurement results based on SS/PBCH block;

2> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains an rsType set to csi - rs and CSI-RS-ResourceConfigMobility is configured in the measObject indicated by the servingCellMO:

3> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains a reportQuantityRS -Indexes and maxNrofRS - IndexesToReport and contains an rsType set to csi - rs:

4> derive layer 3 filtered RSRP and RSRQ per beam for the serving cell based on CSI-RS;

3> derive serving cell measurement results based on CSI-RS;

1> for each serving cell for which servingCellMO is configured, if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains SINR as trigger quantity and/or reporting quantity:

2> if the reportConfig contains rsType set to ssb and ssb -ConfigMobility is configured in the servingCellMO:

3> if the reportConfigcontains a reportQuantityRS -Indexes and maxNrofRS-IndexesToReport:

4> derive layer 3 filtered SINR per beam for the serving cell based on SS/PBCH block;

3> derive serving cell SINR based on SS/PBCH block;

2> if the reportConfig contains rsType set to csi - rs and CSI- RS -ResourceConfigMobility is configured in the servingCellMO:

4> derive layer 3 filtered SINR per beam for the serving cell based on CSI-RS;

3> derive serving cell SINR based on CSI-RS;

1> for each measId included in the measIdList within VarMeasConfig:

2> if the reportType for the associated reportConfig is set to reportCGI and timer T321 is running:

3> if useAutonomousGaps is configured for the associated reportConfig:

4> perform the corresponding measurements on the frequency and RAT indicated in the associated measObject using autonomous gaps as necessary;

3> else:

4> perform the corresponding measurements on the frequency and RAT indicated in the associated measObject using available idle periods;

3> if the cell indicated by reportCGI field for the associated measObject is an NR cell and that indicated cell is broadcasting SIB1:

4> try to acquire SIB1 in the concerned cell;

3> if the cell indicated by reportCGI field is an E-UTRA cell:

4> try to acquire SystemInformationBlockType1 in the concerned cell;

2> if the ul - DelayValueConfig is configured for the associated reportConfig:

3> ignore the measObject ;

3> for each of the configured DRBs, configure the PDCP layer to perform corresponding average UL PDCP packet delay measurement per DRB;

2> if the reportType for the associated reportConfig is periodical, eventTriggered or condTriggerConfig:

3> if a measurement gap configuration is setup, or

3> if the UE does not require measurement gaps to perform the concerned measurements:

4> if s- MeasureConfig is not configured, or

4> if s- MeasureConfig is set to ssb - RSRP and the NR SpCell RSRP based on SS/PBCH block, after layer 3 filtering, is lower than ssb - RSRP , or

4> if s- MeasureConfig is set to csi - RSRP and the NR SpCell RSRP based on CSI-RS, after layer 3 filtering, is lower than csi - RSRP:

5> if the measObject is associated to NR and the rsType is set to csi-rs:

6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:

7> derive layer 3 filtered beam measurements only based on CSI-RS for each measurement quantity indicated in reportQuantityRS -Indexes;

6> derive cell measurement results based on CSI-RS for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject;

5> if the measObject is associated to NR and the rsType is set to ssb:

7> derive layer 3 beam measurements only based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS -Indexes;

6> derive cell measurement results based on SS/PBCH block for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject;

5> if the measObject is associated to E-UTRA:

6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concerned measObject;

5> if the measObject is associated to UTRA-FDD:

4> if the measRSSI - ReportConfig is configured in the associated reportConfig:

5> perform the RSSI and channel occupancy measurements on the frequency indicated in the associated measObject;

2> if the reportType for the associated reportConfig is set to reportSFTD and the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than one:

3> if the reportSFTD - Meas is set to true:

4> if the measObject is associated to E-UTRA:

5> perform SFTD measurements between the PCell and the E-UTRA PSCell;

5> if the reportRSRP is set to true;

6> perform RSRP measurements for the E-UTRA PSCell;

4> else if the measObject is associated to NR:

5> perform SFTD measurements between the PCell and the NR PSCell;

5> if the reportRSRP is set to true;

6> perform RSRP measurements for the NR PSCell based on SSB;

3> else if the reportSFTD - NeighMeas is included:

4> if the measObject is associated to NR:

5> if the drx - SFTD - NeighMeas is included:

6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associated measObject using available idle periods;

5> else:

6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associated measObject;

5> if the reportRSRP is set to true:

6> perform RSRP measurements based on SSB for the NR neighbouring cell(s) detected based on parameters in the associated measObject;

2> if the reportType for the associated reportConfig is cli -Periodical or cli - EventTriggered:

3> perform the corresponding measurements associated to CLI measurement resources indicated in the concerned measObjectCLI;

2> perform the evaluation of reporting criteria, except if reportConfig is condTriggerConfig.

The UE capable of CBR measurement when configured to transmit NR sidelink communication shall:

1> If the frequency used for NR sidelink communication is included in sl - FreqInfoToAddModList in sl - ConfigDedicatedNR within RRCReconfiguration message or included in sl - ConfigCommonNR within SIB12:

2> if the UE is in RRC_IDLE or in RRC_INACTIVE:

3> if the cell chosen for NR sidelink communication provides SIB12 which includes sl - TxPoolSelectedNormal or sl - TxPoolExceptional for the concerned frequency:

4> perform CBR measurement on pools in sl - TxPoolSelectedNormal and sl-TxPoolExceptional for the concerned frequency in SIB12;

2> if the UE is in RRC_CONNECTED:

3> if tx- PoolMeasToAddModList is included in VarMeasConfig:

4> perform CBR measurements on each transmission resource pool indicated in the tx- PoolMeasToAddModList;

3> if sl - TxPoolSelectedNormal, sl - TxPoolScheduling or sl -TxPoolExceptional is included in sl-ConfigDedicatedNR for the concerned frequency within RRCReconfiguration:

4> perform CBR measurement on pools in sl - TxPoolSelectedNormal, sl -TxPoolScheduling or sl - TxPoolExceptional if included in sl - ConfigDedicatedNR for the concerned frequency within RRCReconfiguration;

3> else if the cell chosen for NR sidelink communication provides SIB12 which includes sl - TxPoolSelectedNormal or sl - TxPoolExceptional for the concerned frequency:

1> else:

2> perform CBR measurement on pools in sl - TxPoolSelectedNormal and sl-TxPoolExceptional in SL - PreconfigurationNR for the concerned frequency.

In case the configurations for NR sidelink communication and CBR measurement are acquired via the E-UTRA, configurations for NR sidelink communication in SIB12, sl - ConfigDedicatedNR within RRCReconfiguration used in this subclause are provided by the configurations in SystemInformationBlockType28, sl - ConfigDedicatedNR within RRCConnectionReconfiguration, respectively.

If a UE that is configured by upper layers to transmit V2X sidelink communication is configured by NR with transmission resource pool(s) and the measurement objects concerning V2X sidelink communication (i.e. by sl-ConfigDedicatedEUTRA), it shall perform CBR measurement, based on the transmission resource pool(s) and the measurement object(s) concerning V2X sidelink communication configured by NR.

For V2X sidelink communication, each of the CBR measurement results is associated with a resource pool, as indicated by the poolReportId, that refers to a pool as included in sl - ConfigDedicatedEUTRA or SIB13.

Hereinafter, technical features related to a new state (for example, a deactivated state or a dormant state) are described. For example, sections 7.5, 7.6, and 11.2 of 3GPP TS 36.300 v16.2.0 may be referred.

Carrier Aggregation is described.

When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment/re-establishment/handover, one serving cell provides the NAS mobility information (e.g. TAI), and at RRC connection re-establishment/handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell). In the downlink, the carrier corresponding to the PCell is the Downlink Primary Component Carrier (DL PCC) while in the uplink it is the Uplink Primary Component Carrier (UL PCC).

Depending on UE capabilities, Secondary Cells (SCells) can be configured to form together with the PCell a set of serving cells. In the downlink, the carrier corresponding to an SCell is a Downlink Secondary Component Carrier (DL SCC) while in the uplink it is an Uplink Secondary Component Carrier (UL SCC).

The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells:

- For each SCell the usage of uplink resources by the UE in addition to the downlink ones is configurable (the number of DL SCCs configured is therefore always larger than or equal to the number of UL SCCs and no SCell can be configured for usage of uplink resources only);

- An SCell may be configured to start in either deactivated, dormant or activated mode;

- From a UE viewpoint, each uplink resource only belongs to one serving cell;

- The number of serving cells that can be configured depends on the aggregation capability of the UE;

- PCell can only be changed with handover procedure (i.e. with security key change and, unless RACH-less HO is configured, with RACH procedure);

- PCell is used for transmission of PUCCH;

- If DC is not configured one additional PUCCH can be configured on an SCell, the PUCCH SCell;

- Unlike SCells, PCell cannot be de-activated or be in dormant SCell state;

- Re-establishment is triggered when PCell experiences RLF, not when SCells experience RLF;

- NAS information is taken from PCell.

The reconfiguration, addition and removal of SCells can be performed by RRC. During connection resume from suspended RRC connection or from RRC_INACTIVE, the network may decide to keep or release any previously configured SCells from the UE context. At intra-LTE handover and during connection resume from RRC_INACTIVE, the network can also add, remove, or reconfigure SCells for usage with the target PCell. When adding a new SCell, dedicated RRC signalling is used for sending all required system information of the SCell i.e. while in connected mode, UEs need not acquire broadcasted system information directly from the SCells. A common configuration, applicable for multiple SCells, may be provided in addition to dedicated SCell configuration.

When a PUCCH SCell is configured, RRC configures the mapping of each serving cell to Primary PUCCH group or Secondary PUCCH group, i.e., for each SCell whether the PCell or the PUCCH SCell is used for the transmission of ACK/NAKs and CSI reports. A PUCCH SCell cannot be in dormant state.

For LAA SCell the following additional principles are applied:

- The eNB can configure whether the data of a logical channel can be transferred via LAA SCells.

Dual Connectivity is described.

In DC, the configured set of serving cells for a UE consists of two subsets: the Master Cell Group (MCG) containing the serving cells of the MeNB, and the Secondary Cell Group (SCG) containing the serving cells of the SeNB.

When a UE is configured with CA in the MCG, the same principles apply to MCG.

For SCG, the following principles are applied:

- At least one cell in SCG has a configured UL CC and one of them, named PSCell, is configured with PUCCH resources;

- When SCG is configured, there is always at least one SCG bearer or one Split bearer;

- Upon detection of a physical layer problem or a random access problem on PSCell, or the maximum number of RLC retransmissions has been reached associated with the SCG, or upon detection of an access problem on PSCell (T307 expiry) during SCG change, or when exceeding the maximum transmission timing difference between CGs:

- RRC connection Re-establishment procedure is not triggered;

- All UL transmissions towards all cells of the SCG are stopped;

- MeNB is informed by the UE of SCG failure type;

- For split bearer, the DL data transfer over the MeNB is maintained.

- Only the RLC AM bearer can be configured for the split bearer;

- Like PCell, PSCell cannot be de-activated and cannot be in dormant SCell state;

- PSCell can only be changed with SCG change (i.e. with security key change and, unless RACH-less HO is configured, with RACH procedure);

- Neither direct bearer type change between Split bearer and SCG bearer nor simultaneous configuration of SCG and Split bearer are supported.

With respect to the interaction between MeNB and SeNB, the following principles are applied:

- Logical channel identities are independently allocated by the MeNB and the SeNB.

- The MeNB maintains the RRM measurement configuration of the UE and may, e.g. based on received measurement reports or traffic conditions or bearer types, decide to ask a SeNB to provide additional resources (serving cells) for a UE.

- Upon receiving the request from the MeNB, a SeNB may create the container that will result in the configuration of additional serving cells for the UE (or decide that it has no resource available to do so).

- For UE capability coordination, the MeNB provides (part of) the AS configuration and the UE capabilities to the SeNB.

- The MeNB and the SeNB exchange information about UE configuration by means of RRC containers (inter-node messages) carried in X2 messages.

- The SeNB may initiate a reconfiguration of its existing serving cells (e.g., PUCCH towards the SeNB).

- The SeNB decides which cell is the PSCell within the SCG.

- The MeNB does not change the content of the RRC configuration provided by the SeNB.

- In the case of the SCG addition and SCG SCell addition, the MeNB may provide the latest measurement results for the SCG cell(s).

- Both MeNB and SeNB know the SFN and subframe offset of each other by OAM or UE measurement, e.g., for the purpose of DRX alignment and identification of measurement gap.

When adding a new SCG SCell, dedicated RRC signalling is used for sending all required system information of the cell as for CA, except for the SFN acquired from MIB of the PSCell of SCG.

Activation/Deactivation Mechanism is described.

To enable reasonable UE battery consumption when CA is configured, an activation/deactivation mechanism of SCells is supported (i.e. activation/deactivation does not apply to PCell). When an SCell is deactivated, the UE does not need to receive the corresponding PDCCH or PDSCH, cannot transmit in the corresponding uplink, nor is it required to perform CQI measurements. Conversely, when an SCell is active, the UE shall receive PDSCH and PDCCH (if the UE is configured to monitor PDCCH from this SCell), and is expected to be able to perform CQI measurements. To enable faster CQI reporting, a temporary CQI reporting period (called short CQI period) can be supported during SCell activation period. E-UTRAN ensures that while PUCCH SCell is deactivated, SCells of secondary PUCCH group should not be activated or dormant. E-UTRAN ensures that SCells mapped to PUCCH SCell are deactivated before the PUCCH SCell is changed or removed.

To enable faster transition to activated state, a dormant state for SCells (i.e. not PCell or PSCell) is supported. When an SCell is in dormant state, the UE does not need to receive the corresponding PDCCH or PDSCH, cannot transmit in the corresponding uplink, but is required to perform CQI measurements. A PUCCH SCell cannot be in dormant state.

The activation/deactivation mechanism is based on the combination of a MAC control element and deactivation timers. The MAC control element carries a bitmap for the activation and deactivation of SCells: a bit set to 1 denotes activation of the corresponding SCell, while a bit set to 0 denotes deactivation. With the bitmap, SCells can be activated and deactivated individually, and a single activation/deactivation command can activate/deactivate a subset of the SCells. One deactivation timer is maintained per SCell but one common value is configured per UE by RRC.

The state transitions to and from dormant SCell state use MAC control elements.

At reconfiguration without mobility control information:

- SCells added to the set of serving cells are initially "deactivated", "dormant" or "activated";

- SCells which remain in the set of serving cells (either unchanged or reconfigured) do not change their activation status ("activated", "deactivated" or "dormant").

At reconfiguration with mobility control information (i.e. handover) or connection resume from RRC_INACTIVE:

- SCells are "deactivated", "dormant" or "activated".

In DC, the serving cells of the MCG other than the PCell can only be activated/deactivated by the MAC Control Element received on MCG, and the serving cells of the SCG other than PSCell can only be activated/ deactivated by the MAC Control Element received on SCG. The MAC entity applies the bitmap for the associated cells of either MCG or SCG. PSCell in SCG is always activated like the PCell (i.e. deactivation timer is not applied to PSCell). With the exception of PUCCH SCell, one deactivation timer is maintained per SCell but one common value is configured per CG by RRC.

Reception of an RRCConnectionReconfiguration including the mobilityControlInfo by the UE (handover) is described.

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> for each SCell configured for the UE other than the PSCell:

2> if the received RRCConnectionReconfiguration message includes sCellState for the SCell and indicates activated:

3> configure lower layers to consider the SCell to be in activated state;

2> else if the received RRCConnectionReconfiguration message includes sCellState for the SCell and indicates dormant:

3> configure lower layers to consider the SCell to be in dormant state;

2> else:

3> configure lower layers to consider the SCell to be in deactivated state;

SCell addition/ modification procedure is described.

The UE shall:

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell, both included either in the sCellToAddModList or in the sCellToAddModListSCG;

2> if sCellState is configured for the SCell and indicates activated:

3> configure lower layers to consider the SCell to be in activated state;

2> else if sCellState is configured for the SCell and indicates dormant:

3> configure lower layers to consider the SCell to be in dormant state;

2> else:

3> configure lower layers to consider the SCell to be in deactivated state;

2> for each measId included in the measIdList within VarMeasConfig:

3> if SCells are not applicable for the associated measurement; and

3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:

4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the radioResourceConfigDedicatedSCell, included either in the sCellToAddModList or in the sCellToAddModListSCG;

2> if the sCellToAddModList was received within an RRCConnectionResume or an NR RRCResume message:

3> if the sCellState is configured for the SCell and indicates activated:

4> configure lower layers to consider the SCell to be in activated state;

3> else if sCellState is configured for the SCell and indicates dormant:

4> configure lower layers to consider the SCell to be in dormant state;

3> else:

4> configure lower layers to consider the SCell to be in deactivated state;

Technical features related to Physical downlink control channels are described.

The Physical Downlink Control Channel (PDCCH) can be used to schedule DL transmissions on PDSCH and UL transmissions on PUSCH, where the Downlink Control Information (DCI) on PDCCH includes:

- Downlink assignments containing at least modulation and coding format, resource allocation, and hybrid-ARQ information related to DL-SCH;

- Uplink scheduling grants containing at least modulation and coding format, resource allocation, and hybrid-ARQ information related to UL-SCH.

In addition to scheduling, PDCCH can be used to for

- Activation and deactivation of configured PUSCH transmission with configured grant;

- Activation and deactivation of PDSCH semi-persistent transmission;

- Notifying one or more UEs of the slot format;

- Notifying one or more UEs of the PRB(s) and OFDM symbol(s) where the UE may assume no transmission is intended for the UE;

- Transmission of TPC commands for PUCCH and PUSCH;

- Transmission of one or more TPC commands for SRS transmissions by one or more UEs;

- Switching a UE's active bandwidth part;

- Initiating a random access procedure;

- Indicating the UE(s) to monitor the PDCCH during the next occurrence of the DRX on-duration;

- In IAB context, indicating the availability for soft symbols of an IAB-DU.

A UE monitors a set of PDCCH candidates in the configured monitoring occasions in one or more configured COntrol REsource SETs (CORESETs) according to the corresponding search space configurations.

A CORESET consists of a set of PRBs with a time duration of 1 to 3 OFDM symbols. The resource units Resource Element Groups (REGs) and Control Channel Elements (CCEs) are defined within a CORESET with each CCE consisting a set of REGs. Control channels are formed by aggregation of CCE. Different code rates for the control channels are realized by aggregating different number of CCE. Interleaved and non-interleaved CCE-to-REG mapping are supported in a CORESET.

Polar coding is used for PDCCH.

Hereinafter, Bandwidth part is described.

A bandwidth part is a subset of contiguous common resource blocks for a given numerology in bandwidth part on a given carrier.

A UE can be configured with up to four bandwidth parts in the downlink with a single downlink bandwidth part being active at a given time. The UE is not expected to receive PDSCH, PDCCH, or CSI-RS (except for RRM) outside an active bandwidth part.

A UE can be configured with up to four bandwidth parts in the uplink with a single uplink bandwidth part being active at a given time. If a UE is configured with a supplementary uplink, the UE can in addition be configured with up to four bandwidth parts in the supplementary uplink with a single supplementary uplink bandwidth part being active at a given time. The UE shall not transmit PUSCH or PUCCH outside an active bandwidth part. For an active cell, the UE shall not transmit SRS outside an active bandwidth part.

Referring to FIG. 10, BWP consists of a group of contiguous physical resource blocks (PRBs). The bandwidth (BW) of BWP cannot exceed the configured component carrier (CC) BW for the UE. The BW of the BWP must be at least as large as one synchronization signal (SS) block BW, but the BWP may or may not contain SS block. Each BWP is associated with a specific numerology, i.e., sub-carrier spacing (SCS) and cyclic prefix (CP) type. Therefore, the BWP is also a means to reconfigure a UE with a certain numerology.

As illustrated in the right figure of FIG. 10, the network can configure multiple BWPs to a UE via radio resource control (RRC) signaling, which may overlap in frequency. The granularity of BWP configuration is one PRB. For each serving cell, DL and UL BWPs are configured separately and independently for paired spectrum and up to four BWPs can be configured for DL and UL each. For unpaired spectrum, a DL BWP and a UL BWP are jointly configured as a pair and up to 4 pairs can be configured. There can be maximally 4 UL BWPs configured for a supplemental UL (SUL) as well.

Referring to FIG. 11, for serving cell measurements, a UE may be configured with multiple BWPs contiguously or non-contiguously. In order to derive quality of the serving cell, the UE measures only configured BWPs, not all BWPs that belongs to the serving cell.

Each configured DL BWP includes at least one control resource set (CORESET) with UE-specific search space (USS). The USS is a searching space for UE to monitor possible reception of control information destined for the UE. In the primary carrier, at least one of the configured DL BWPs includes one CORESET with common search space (CSS). The CSS is a searching space for UE to monitor possible reception of control information common for all UEs or destined for the particular UE. If the CORESET of an active DL BWP is not configured with CSS, the UE is not required to monitor it. Note that UEs are expected to receive and transmit only within the frequency range configured for the active BWPs with the associated numerologies. However, there are exceptions. A UE may perform Radio Resource Management (RRM) measurement or transmit sounding reference signal (SRS) outside of its active BWP via measurement gap.

Referring to FIG. 12, 3 BWPs may be configured. The first BWP may span 40 MHz band, and a subcarrier spacing of 15 kHz may be applied. The second BWP may span 10 MHz band, and a subcarrier spacing of 15 kHz may be applied. The third BWP may span 20 MHz band and a subcarrier spacing of 60 kHz may be applied. The UE may configure at least one BWP among the 3 BWPs as an active BWP, and may perform UL and/or DL data communication via the active BWP.

The BWP is also a tool to switch the operating numerology of a UE. The numerology of the DL BWP configuration is used at least for the Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH) and corresponding demodulation RS (DMRS). Likewise, the numerology of the UL BWP configuration is used at least for the Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH) and corresponding DMRS. On the other hand, it is noted that there is a restriction in the configuration of numerology at least in the early version of NR. That is, the same numerology shall be used within the same PUCCH group including both DL and UL.

With Bandwidth Adaptation (BA), the receive and transmit bandwidth of a UE need not be as large as the bandwidth of the cell and can be adjusted: the width can be ordered to change (e.g. to shrink during period of low activity to save power); the location can move in the frequency domain (e.g. to increase scheduling flexibility); and the subcarrier spacing can be ordered to change (e.g. to allow different services). A subset of the total cell bandwidth of a cell is referred to as a Bandwidth Part (BWP) and BA is achieved by configuring the UE with BWP(s) and telling the UE which of the configured BWPs is currently the active one.

Referring to FIG. 12, there are 3 different BWPs are configured:

- BWP₁ with a width of 40 MHz and subcarrier spacing of 15 kHz;

- BWP₂ with a width of 10 MHz and subcarrier spacing of 15 kHz;

- BWP₃ with a width of 20 MHz and subcarrier spacing of 60 kHz.

As described above, a new state may be supported in NR. For example, the new state may be referred as a deactivated state or a dormant state. For example, the new state may be called as a specific state or a special state, in the present disclosure.

When a cell group enters the new state (for example, the deactivated state or the dormant state), the UE may not perform the PDCCH monitoring for all cells belonging to the cell group for power saving. If UE keeps performing the measurements according to the configuration from a cell group while the cell group is in the new state (for example, the deactivated state or the dormant state), the UE may need to spend lots of power for the measurement. Then, it may decrease the gain of dormant cell group. On the contrary, if UE doesn't perform the measurement for the cell group in dormant state, the UE may keep the bad serving cell even after the serving cell quality becomes worse than a threshold. In this case, the serving cell cannot be used for data reception/transmission, and it may cause that the UE cannot achieve the sufficient user throughput when the corresponding cell group becomes normal state from the new state (for example, a deactivated state or a dormant state).

Hereinafter, a method for performing measurement in a deactivated state or a dormant state in a wireless communication system, according to some embodiments of the present disclosure, will be described with reference to the following drawings.

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

In particular, FIG. 13 shows an example of a method performed by a wireless device in a wireless communication system.

In step S1301, a wireless device may receive, from a cell group, a measurement configuration including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state.

For example, the specific state may be a new state (for example, a dormant state or a deactivated state), as described above.

For example, the specific state may be a deactivated state where a primary cell of the cell group is deactivated.

For example, the specific state may be a dormant state where a dormant Bandwidth Part (BWP) for a primary cell of the cell group is activated.

For example, the dormant BWP for the primary cell of the cell group may be activated (i) by an indication via a PDCCH, (ii) by using a BWP Inactivity Timer, (iii) by a Radio Resource Control (RRC) signalling, or (iv) a signal on a Media Access Control (MAC) layer.

For example, the at least one measurement object may include frequency with subcarrier spacing 15 kHz.

In step S1302, a wireless device may enter the specific state. Physical Downlink Control Channel (PDCCH) monitoring may not be performed for all cells belonging to the cell group while in the specific state.

For example, a wireless device may establish a Carrier Aggregation (CA) or Dual Connectivity (DC) with multiple cell groups. For example, the multiple cell groups may include a primary cell group and a secondary cell group.

For example, the wireless device may enter the specific state, when one cell group among the multiple cell groups enters into the specific state (for example, the deactivated state or the dormant state). For example, the wireless device may consider to be entered into the specific state, when only the secondary cell group may be in the specific state. For example, the wireless device may receive, from a network, a signal informing that the secondary cell group is in the specific state or enters into the specific state. The wireless device may enter the specific state based on the received signal. For example, the wireless device may receive the signal informing that the secondary cell group is in the specific state (or enters into the specific state) from the primary cell group or the secondary cell group. For example, the signal may be a command for the wireless device to enter the specific state.

In other words, if a certain cell group among the multiple cell groups enters or is in the deactivated state or the dormant state, the network may inform the wireless device that the certain cell group is in or enters the deactivated state or the dormant state. The wireless device may enter the specific state corresponding to the certain cell group. Simultaneously, the wireless device may perform PDCCH monitoring for at least one cell included in other cell groups except the certain cell group.

That is, when the wireless device enters the specific state, it may not be necessary that all cell groups are in the specific state. When only one cell group for the CA or DC is in or enters the specific state, the wireless device may consider to be in or enter the specific state.

In step S1303, a wireless device may determine whether to perform measurement on the at least one measurement object in the specific state based on the received information.

For example, the wireless device may perform the measurement based on the determination while in the specific state.

According to some embodiments of the present disclosure, a wireless device may leave the specific state and enter a normal state. PDCCH monitoring may be performed for at least one cell included in the cell group while in the normal state. For example, a wireless device may perform measurement on all of the measurement object included in the measurement configuration while in the normal state.

For example, the specific state may be a deactivated state. In this case, the primary cell of the cell group may be (re)activated in the normal state.

For example, the specific state may be a dormant state. In this case, an active BWP, which is different from a dormant BWP, for a primary cell of the cell group may be activated in the normal state.

According to some embodiments of the present disclosure, the measurement configuration may include a measurement indication configured only for a certain measurement object to be measured in the specific state.

For example, the measurement configuration may include 1) a first measurement object with a first measurement indication, 2) a second measurement object with a second measurement indication, and 3) a third measurement object without a third measurement indication.

In this case, a wireless device may perform measurement on the first measurement object and the second measurement object while in the specific state, based on the first measurement indication and the second measurement indication. In addition, a wireless device may skip to perform measurement on the third measurement object.

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

According to some embodiments of the present disclosure, when a cell group is in dormant state, UE may perform the measurement based on an indication for a measurement objects (for example, frequency or cell) configured by the cell group. The indication may indicate whether to measure the corresponding measurement object when the cell group that configures the measurement object is in a dormant state or a deactivated state. The indication can be configured per cell/per frequency or per measurement object. For a measurement object for which the indication is configured, the UE may perform the measurement when the corresponding cell group is in dormant state. For a measurement object for which the indication is not configured, the UE may not perform the measurement when the corresponding cell group is in dormant state, but may perform the measurement when the corresponding cell group is not in dormant state.

According to some embodiments of the present disclosure, when the dormant downlink BWP of SpCell, i.e. PCell or PSCell, is activated, the UE may consider the corresponding cell group is in a dormant state or a deactivated state. For example, if the dormant downlink BWP is activated for PSCell, the UE may consider the secondary cell group is in a dormant state or a deactivated state.

The downlink BWP which is not configured with PDCCH may be a dormant downlink BWP. The dormant downlink BWP may be at least one BWP among configured multiple BWPs (for example, four BWPs). The dormant downlink BWP may be pre-configured. The dormant downlink BWP may be activated by the BWP switching, which is controlled by the PDCCH indicating a downlink assignment or an uplink grant, by the bwp - InactivityTimer, by RRC signalling, or by the MAC entity itself upon initiation of Random Access procedure. Upon activation of the dormant bandwidth part, the UE does not need to monitor PDCCH for the corresponding cell.

Referring to FIG. 14, in step S1401, a UE may receive the measurement configuration from a cell group.

UE may receive the measurement configuration from secondary cell group. The measurement configuration may include two measurement objects as follows:

- The first measurement object indicates frequency A with subcarrier spacing 15 kHz. The measurement indication is configured.

- The second measurement object indicates frequency B with subcarrier spacing 15 kHz. The measurement indication is not configured.

The measurement indication may indicate whether to measure the corresponding measurement object when the cell group that configures the measurement object is in a dormant state or a deactivated state. The measurement indication may be configured only for the first measurement object, i.e. frequency A.

UE may performs the measurement for frequency A and frequency B in normal state.

In step S1402, a UE may enter a dormant state or a deactivated state.

For example, the dormant BWP of the PSCell may be activated and the secondary cell group may become dormant cell group.

For example, the secondary cell group may become a deactivated cell group.

In step S1403, a UE may determine whether to perform the measurement for measurement objects configured by the dormant cell group or the deactivated cell group (for example, the cell group in the dormant state or the deactivated state) based on the measurement indication.

In step S1404, a UE may perform the measurement based on the determination.

While the secondary cell group is in a dormant state or a deactivated state, the UE performs the measurement only for the frequency A. That is, the UE doesn't perform the measurement for frequency B indicated by the second measurement object. Since the measurement indication is only configured for the first measurement object (i.e., frequency A), but the measurement indication is not configured for the second measurement object (i.e., frequency B).

In step S1405, a UE may leave the dormant state or the deactivated state.

For example, the non-dormant BWP of the PSCell may be activated and the secondary cell group may not be dormant cell group any more.

For example, the secondary cell group may not be deactivated cell group any more.

In step S1406, a UE may perform the measurement according to the measurement configuration.

For example, UE may perform the measurement for all measurement objects configured by the secondary cell group.

According to some embodiments of the present disclosure, a wireless device may receive, on a cell group, a measurement configuration including an indication indicating whether to measure a measurement object in a dormant state or a deactivated state. A wireless device may activate a dormant downlink BWP for the cell group upon which the cell group is in the dormant state or the deactivated state. A wireless device may determine whether to measure the measurement object in the dormant state or the deactivated state based on the indication.

Some of the detailed steps shown in the example of FIGS. 13 and 14 may not be essential steps and may be omitted. In addition, steps other than the steps shown in FIGS. 13 and 14 may be added, and the order of the steps may vary. Some of the above steps may have their own technical meaning.

Hereinafter, an apparatus for performing measurement in a deactivated state or a dormant state in a wireless communication system, according to some embodiments of the present disclosure, will be described. Herein, the apparatus may be a wireless device (100 or 200) in FIGS. 2, 3, and 5.

For example, a wireless device may perform methods described in FIGS. 13 and 14. The detailed description overlapping with the above-described contents could be simplified or omitted.

Referring to FIG. 5, a wireless device 100 may include a processor 102, a memory 104, and a transceiver 106.

According to some embodiments of the present disclosure, the processor 102 may be configured to be coupled operably with the memory 104 and the transceiver 106.

The processor 102 may be configured to control the transceiver 106 to receive, from a cell group, a measurement configuration including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state. The processor 102 may be configured to enter the specific state. Physical Downlink Control Channel (PDCCH) monitoring may not be performed for all cells belonging to the cell group while in the specific state. The processor 102 may be configured to determine whether to perform measurement on the at least one measurement object in the specific state based on the received information.

For example, the specific state may be a dormant state where a dormant Bandwidth Part (BWP) for a primary cell of the cell group is activated. For example, the dormant BWP for the primary cell of the cell group may be activated (i) by an indication via a PDCCH, (ii) by using a BWP Inactivity Timer, (iii) by a Radio Resource Control (RRC) signalling, or (iv) a signal on a Media Access Control (MAC) layer.

For example, the processor 102 may be configured to perform the measurement based on the determination while in the specific state.

For example, the processor 102 may be configured to leave the specific state and enter a normal state. PDCCH monitoring may be performed for at least one cell included in the cell group while in the normal state. The processor 102 may be configured to perform measurement on all of the measurement object included in the measurement configuration while in the normal state.

For example, a primary cell of cell group may be activated in the normal state.

For example, an active BWP, which is different from a dormant BWP, for a primary cell of the cell group may be activated in the normal state.

In this case, the processor 102 may be configured to perform measurement on the first measurement object and the second measurement object while in the specific state, based on the first measurement indication and the second measurement indication. The processor 102 may be configured to skip to perform measurement on the third measurement object.

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

Hereinafter, a processor for a wireless device for performing measurement in a deactivated state or a dormant state in a wireless communication system, according to some embodiments of the present disclosure, will be described.

The processor may be configured to control the wireless device to receive, from a cell group, a measurement configuration including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state. The processor may be configured to control the wireless device to enter the specific state. Physical Downlink Control Channel (PDCCH) monitoring may not be performed for all cells belonging to the cell group while in the specific state. The processor may be configured to control the wireless device to determine whether to perform measurement on the at least one measurement object in the specific state based on the received information.

For example, the processor may be configured to control the wireless device to perform the measurement based on the determination while in the specific state.

For example, the processor may be configured to control the wireless device to leave the specific state and enter a normal state. PDCCH monitoring may be performed for at least one cell included in the cell group while in the normal state. The processor may be configured to control the wireless device to perform measurement on all of the measurement object included in the measurement configuration while in the normal state.

For example, a primary cell of the cell group may be activated in the normal state.

In this case, the processor may be configured to control the wireless device to perform measurement on the first measurement object and the second measurement object while in the specific state, based on the first measurement indication and the second measurement indication. The processor may be configured to control the wireless device to skip to perform measurement on the third measurement object.

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

Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for performing measurement in a deactivated state or a dormant state in a wireless communication system, according to some embodiments of the present disclosure, will be described.

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

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

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

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

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

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

The stored a plurality of instructions may cause the wireless device to receive, from a cell group, a measurement configuration including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state. The stored a plurality of instructions may cause the wireless device to enter the specific state. Physical Downlink Control Channel (PDCCH) monitoring may not be performed for all cells belonging to the cell group while in the specific state. The stored a plurality of instructions may cause the wireless device to determine whether to perform measurement on the at least one measurement object in the specific state based on the received information.

For example, the stored a plurality of instructions may cause the wireless device to perform the measurement based on the determination while in the specific state.

For example, the stored a plurality of instructions may cause the wireless device to leave the specific state and enter a normal state. PDCCH monitoring may be performed for at least one cell included in the cell group while in the normal state. The stored a plurality of instructions may cause the wireless device to perform measurement on all of the measurement object included in the measurement configuration while in the normal state.

In this case, the stored a plurality of instructions may cause the wireless device to perform measurement on the first measurement object and the second measurement object while in the specific state, based on the first measurement indication and the second measurement indication. The stored a plurality of instructions may cause the wireless device to skip to perform measurement on the third measurement object.

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

Hereinafter, a method performed by a base station (BS) for measurement in a deactivated state or a dormant state in a wireless communication system, according to some embodiments of the present disclosure, will be described.

The BS may transmit, to a wireless device, a measurement configuration for a cell group including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state. Physical Downlink Control Channel (PDCCH) monitoring may not be performed, by the wireless device, for all cells belonging to the cell group while in the specific state. The BS may transmit, to the wireless device, a signal informing that the cell group is in or enters into the specific state.

Hereinafter, a base station (BS) for measurement in a deactivated state or a dormant state in a wireless communication system, according to some embodiments of the present disclosure, will be described.

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

The processor may be configured to control the transceiver to transmit, to a wireless device, a measurement configuration for a cell group including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state. Physical Downlink Control Channel (PDCCH) monitoring may not be performed, by the wireless device, for all cells belonging to the cell group while in the specific state. The processor may be configured to control the transceiver to transmit, to the wireless device, a signal informing that the cell group is in or enters into the specific state.

The present disclosure can have various advantageous effects.

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

Claims

A method performed by a wireless device in a wireless communication system, the method comprising:

receiving, from a cell group, a measurement configuration including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state;

entering the specific state, wherein Physical Downlink Control Channel (PDCCH) monitoring is not performed for all cells belonging to the cell group while in the specific state; and

determining whether to perform measurement on the at least one measurement object in the specific state based on the received information.
The method of claim 1, wherein the specific state is a deactivated state where a primary cell of the cell group is deactivated.
The method of claim 1, wherein the specific state is a dormant state where a dormant Bandwidth Part (BWP) for a primary cell of the cell group is activated.
The method of claim 3, wherein the dormant BWP for the primary cell of the cell group is activated (i) by an indication via a PDCCH, (ii) by using a BWP Inactivity Timer, (iii) by a Radio Resource Control (RRC) signalling, or (iv) a signal on a Media Access Control (MAC) layer.
The method of claim 1, wherein the at least one measurement object includes frequency with subcarrier spacing 15 kHz.
The method of claim 1, wherein the method further comprises,

performing the measurement based on the determination while in the specific state.
The method of claim 1, wherein the method further comprises,

leaving the specific state and entering a normal state, wherein PDCCH monitoring is performed for at least one cell included in the cell group while in the normal state; and

performing measurement on all of the measurement object included in the measurement configuration while in the normal state.
The method of claim 7, wherein a primary cell of the cell group is activated in the normal state.
The method of claim 7, wherein an active BWP, which is different from a dormant BWP, for a primary cell of the cell group is activated in the normal state.
The method of claim 1, wherein the measurement configuration includes a measurement indication configured only for a certain measurement object to be measured in the specific state.
The method of claim 10, wherein the measurement configuration includes 1) a first measurement object with a first measurement indication, 2) a second measurement object with a second measurement indication, and 3) a third measurement object without a third measurement indication.
The method of claim 11, wherein the method further comprises,

performing measurement on the first measurement object and the second measurement object while in the specific state, based on the first measurement indication and the second measurement indication; and

skipping to perform measurement on the third measurement object.
The method of claim 1, wherein the wireless device is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.
A wireless device in a wireless communication system comprising:

a transceiver;

a memory; and

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

control the transceiver to receive, from a cell group, a measurement configuration including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state;

enter the specific state, wherein Physical Downlink Control Channel (PDCCH) monitoring is not performed for all cells belonging to the cell group while in the specific state; and

determine whether to perform measurement on the at least one measurement object in the specific state based on the received information.
The wireless device of claim 14, wherein the specific state is a deactivated state where a primary cell of the cell group is deactivated.
The wireless device of claim 14, wherein the specific state is a dormant state where a dormant Bandwidth Part (BWP) for a primary cell of the cell group is activated.
The wireless device of claim 16, wherein the dormant BWP for the primary cell of the cell group is activated (i) by an indication via a PDCCH, (ii) by using a BWP Inactivity Timer, (iii) by a Radio Resource Control (RRC) signalling, or (iv) a signal on a Media Access Control (MAC) layer.
The wireless device of claim 14, wherein the at least one measurement object includes frequency with subcarrier spacing 15 kHz.
The wireless device of claim 14, wherein the at least one processor is further configured to,

perform the measurement based on the determination while in the specific state.
The wireless device of claim 14, wherein the at least one processor is further configured to,

leave the specific state and enter a normal state, wherein PDCCH monitoring is performed for at least one cell included in the cell group while in the normal state; and

perform measurement on all of the measurement object included in the measurement configuration while in the normal state.
The wireless device of claim 20, wherein a primary cell of the cell group is activated in the normal state.
The wireless device of claim 20, wherein an active BWP, which is different from a dormant BWP, for a primary cell of the cell group is activated in the normal state.
The wireless device of claim 14, wherein the measurement configuration includes a measurement indication configured only for a certain measurement object to be measured in the specific state.
The wireless device of claim 23, wherein the measurement configuration includes 1) a first measurement object with a first measurement indication, 2) a second measurement object with a second measurement indication, and 3) a third measurement object without a third measurement indication.
The wireless device of claim 24, wherein the at least one processor is further configured to,

perform measurement on the first measurement object and the second measurement object while in the specific state, based on the first measurement indication and the second measurement indication; and

skip to perform measurement on the third measurement object.
The wireless device of claim 14, wherein the at least one processor is further configured to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.
A processor for a wireless device in a wireless communication system, wherein the processor is configured to control the wireless device to perform operations comprising:

receiving, from a cell group, a measurement configuration including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state;

entering the specific state, wherein Physical Downlink Control Channel (PDCCH) monitoring is not performed for all cells belonging to the cell group while in the specific state; and

determining whether to perform measurement on the at least one measurement object in the specific state based on the received information.
A non-transitory computer-readable medium having stored thereon a plurality of instructions, which, when executed by a processor of a wireless device, cause the wireless device to:

receive, from a cell group, a measurement configuration including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state;

enter the specific state, wherein Physical Downlink Control Channel (PDCCH) monitoring is not performed for all cells belonging to the cell group while in the specific state; and

determine whether to perform measurement on the at least one measurement object in the specific state based on the received information.
A method performed by a base station in a wireless communication system, the method comprising,

transmitting, to a wireless device, a measurement configuration for a cell group including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state, wherein Physical Downlink Control Channel (PDCCH) monitoring is not performed, by the wireless device, for all cells belonging to the cell group while in the specific state; and

transmitting, to the wireless device, a signal informing that the cell group is in the specific state.
A base station in a wireless communication system comprising:

a transceiver;

a memory; and

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

control the transceiver to transmit, to a wireless device, a measurement configuration for a cell group including 1) at least one measurement object, and 2) an information informing whether to perform measurement on the at least one measurement object in a specific state, wherein Physical Downlink Control Channel (PDCCH) monitoring is not performed, by the wireless device, for all cells belonging to the cell group while in the specific state; and

control the transceiver to transmit, to the wireless device, a signal informing that the cell group is in the specific state.