WO2021118202A1

WO2021118202A1 - Method and apparatus for declaring early rlf in a wireless communication system

Info

Publication number: WO2021118202A1
Application number: PCT/KR2020/017858
Authority: WO
Inventors: Sangwon Kim; Sunghoon Jung
Original assignee: LG Electronics Inc
Current assignee: LG Electronics Inc
Priority date: 2019-12-09
Filing date: 2020-12-08
Publication date: 2021-06-17
Anticipated expiration: 2022-06-09

Abstract

A method and apparatus for declaring early RLF in a wireless communication system is provided. Early Radio Link Failure (RLF) timer is configured for the measurement report. A wireless device starts a periodical reporting timer upon performing the transmission of the measurement report. A wireless device starts an RLF timer based on that a physical layer problem is detected after starting the periodical reporting timer. A wireless device starts the early RLF timer upon expiry of the periodical reporting timer. A wireless device declares RLF for the at least one cell group upon expiry of the early RLF timer.

Description

METHOD AND APPARATUS FOR DECLARING EARLY RLF IN A WIRELESS COMMUNICATION SYSTEM

The present disclosure relates to a method and apparatus for declaring early RLF 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.

A wireless device may use a radio link failure (RLF) timer (for example, T310) to declare an RLF on a connection with a network. When the wireless device declares the RLF on the connection with the network, the wireless device may perform connection re-establishment procedure to the network.

However, using only the RLF timer may cause huge service interruption time. For example, a wireless device may need to wait the expiry of the RLF timer to declare the RLF and perform re-establishment procedure, even though the link quality is bad.

Therefore, studies for declaring early RLF in a wireless communication system are required.

In an aspect, a method performed by a wireless device in a wireless communication system is provided. Early Radio Link Failure (RLF) timer is configured for the measurement report. A wireless device starts a periodical reporting timer upon performing the transmission of the measurement report. A wireless device starts an RLF timer based on that a physical layer problem is detected after starting the periodical reporting timer. A wireless device starts the early RLF timer upon expiry of the periodical reporting timer. A wireless device declares RLF for the at least one cell group upon expiry of the early RLF timer.

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 declare an early RLF efficiently in a wireless communication system.

For example, even though the physical layer problem is detected after transmitting an event-based measurement reporting, a wireless device may declare early RLF.

For example, a wireless device could reduce the service interruption time by declaring the early RLF and initiating the recovery procedure early.

For example, a wireless device could reduce the service interruption time by declaring the early RLF and initiating RRC re-establishment or SCG failure reporting, early.

According to some embodiments of the present disclosure, a wireless communication system could provide a method to a wireless device for declaring an early RLF efficiently.

For example, a wireless communication system could could reduce the service interruption time by declaring the early RLF and initiating the recovery procedure, for example, RRC re-establishment or SCG failure reporting, early.

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 a method for declaring early RLF in a wireless communication system, according to some embodiments of the present disclosure.

FIG. 11 shows an example of a method for triggering early RLF using periodical reporting timer in a wireless communication system, according to some embodiments of the present disclosure.

FIG. 12 shows an example of declaring early RLF in a wireless communication system, according to some embodiments of the present disclosure.

FIG. 13 shows an example of declaring early RLF 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.

Table 5 shows example of timers to which implementations of the present disclosure is applied. For example, Table 5 shows information of timers as below.

Timer	Start	Stop	At expiry
T310	Upon detecting physical layer problems for the PCell i.e. upon receiving N310 consecutive out-of-sync indications from lower layers	Upon receiving N311 consecutive in-sync indications from lower layers for the PCell, upon triggering the handover procedure and upon initiating the connection re-establishment procedure	If security is not activated and the UE is not a NB-IoT UE that supports RRC connection re-establishment for the Control Plane CIoT EPS optimisation: go to RRC_IDLE else: initiate the connection re-establishment procedure
T312	Upon triggering a measurement report for a measurement identity for which T312 has been configured, while T310 is running	Upon receiving N311 consecutive in-sync indications from lower layers, upon triggering the handover procedure, upon initiating the connection re-establishment procedure, and upon the expiry of T310	If security is not activated: go to RRC_IDLE else: initiate the connection re-establishment procedure

Hereinafter, radio link failure related actions is described. The operations described below could be applied to implementations of the present disclosure. Section 5.3.11 of 3GPP TS 36.331 V15.6.0 may be referred.Detection of physical layer problems in RRC_CONNECTED is described.

The UE shall:

1> upon receiving N310 consecutive "out-of-sync" indications for the PCell from lower layers while neither T300, T301, T304 nor T311 is running:

2> start timer T310;

1> upon receiving N313 consecutive "out-of-sync" indications for the PSCell from lower layers while T307 is not running:

2> start T313;

Physical layer monitoring and related autonomous actions do not apply to SCells except for the PSCell.

Early detection of physical layer problems in RRC_CONNECTED is described.

The UE shall:

1> upon receiving N310 consecutive "early-out-of-sync" indications for the PCell from lower layers:

2> start timer T314 with the timer value set to the value of T310;

Recovery of physical layer problems are described.

Upon receiving N311 consecutive "in-sync" indications for the PCell from lower layers while T310 is running, the UE shall:

1> stop timer T310;

1> stop timer T312, if running;

In this case, the UE maintains the RRC connection without explicit signalling, i.e. the UE maintains the entire radio resource configuration.

Periods in time where neither "in-sync" nor "out-of-sync" is reported by layer 1 do not affect the evaluation of the number of consecutive "in-sync" or "out-of-sync" indications.

Upon receiving N314 consecutive "in-sync" indications for the PSCell from lower layers while T313 is running, the UE shall:

1> stop timer T313;

Recovery of early detection of physical layer problems is described.

Upon receiving N311 consecutive "in-sync" indications for the PCell from lower layers while T314 is running, the UE shall:

1> stop timer T314;

Detection of radio link failure is described.

The UE shall:

1> upon T310 expiry; or

1> upon T312 expiry; or

1> upon random access problem indication from MCG MAC while neither T300, T301, T304 nor T311 is running; or

1> upon indication from MCG RLC, which is allowed to be send on PCell, that the maximum number of retransmissions has been reached for an SRB or DRB:

2> consider radio link failure to be detected for the MCG i.e. RLF;

2> except for NB-IoT, store the following radio link failure information in the VarRLF-Report by setting its fields as follows:

3> clear the information included in VarRLF-Report, if any;

3> set the plmn - IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);

3> set the measResultLastServCell to include the RSRP and RSRQ, if available, of the PCell based on measurements collected up to the moment the UE detected radio link failure;

3> set the measResultNeighCells to include the best measured cells, other than the PCell, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected radio link failure, and set its fields as follows;

4> if the UE was configured to perform measurements for one or more EUTRA frequencies, include the measResultListEUTRA;

4> if the UE was configured to perform measurement reporting for one or more neighbouring UTRA frequencies, include the measResultListUTRA;

4> if the UE was configured to perform measurement reporting for one or more neighbouring GERAN frequencies, include the measResultListGERAN;

4> if the UE was configured to perform measurement reporting for one or more neighbouring CDMA2000 frequencies, include the measResultsCDMA2000;

4> for each neighbour cell included, include the optional fields that are available;

The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Blacklisted cells are not required to be reported.

3> if available, set the logMeasResultListWLAN to include the WLAN measurement results, in order of decreasing RSSI for WLAN APs;

3> if available, set the logMeasResultListBT to include the Bluetooth measurement results, in order of decreasing RSSI for Bluetooth beacons;

3> if detailed location information is available, set the content of the locationInfo as follows:

4> include the locationCoordinates;

4> include the horizontalVelocity, if available;

3> set the failedPCellId to the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;

3> set the tac- FailedPCell to the tracking area code, if available, of the PCell where radio link failure is detected;

3> if an RRCConnectionReconfiguration message including the mobilityControlInfo was received before the connection failure:

4> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned an intra E-UTRA handover:

5> include the previousPCellId and set it to the global cell identity of the PCell where the last RRCConnectionReconfiguration message including mobilityControlInfo was received;

5> set the timeConnFailure to the elapsed time since reception of the last RRCConnectionReconfiguration message including the mobilityControlInfo;

4> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned a handover to E-UTRA from UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO:

5> include the previousUTRA - CellId and set it to the physical cell identity, the carrier frequency and the global cell identity, if available, of the UTRA Cell in which the last RRCConnectionReconfiguration message including mobilityControlInfo was received;

3> if the UE supports QCI1 indication in Radio Link Failure Report and has a DRB for which QCI is 1:

4> include the drb-EstablishedWithQCI-1;

3> set the connectionFailureType to rlf;

3> set the c-RNTI to the C-RNTI used in the PCell;

3> set the rlf -Cause to the trigger for detecting radio link failure;

2> if AS security has not been activated:

3> if the UE is a NB-IoT UE:

4> if the UE supports RRC connection re-establishment for the Control Plane CIoT EPS optimisation:

5> initiate the RRC connection re-establishment procedure;

4> else:

5> perform the actions upon leaving RRC_CONNECTED, with release cause 'RRC connection failure';

3> else:

4> perform the actions upon leaving RRC_CONNECTED, with release cause 'other';

2> else:

3> initiate the connection re-establishment procedure;

In case of DC or NE-DC, the UE shall:

1> upon T313 expiry; or

1> upon random access problem indication from SCG MAC; or

1> upon indication from SCG RLC, which is allowed to be sent on PSCell, that the maximum number of retransmissions has been reached for an SCG, for a split DRB or for a split SRB:

2> consider radio link failure to be detected for the SCG i.e. SCG-RLF;

2> initiate the SCG failure information procedure to report SCG radio link failure;

The UE may discard the radio link failure information, i.e. release the UE variable VarRLF -Report, 48 hours after the radio link failure is detected, upon power off or upon detach.

Hereinafter, measurement report triggering is described. The operations described below could be applied to implementations of the present disclosure. Section 5.5.4 of 3GPP TS 36.331 V15.6.0 may be referred.

If security has been activated successfully, the UE shall:

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

2> if the corresponding reportConfig includes a purpose set to reportStrongestCellsForSON:

3> consider any neighbouring cell detected on the associated frequency to be applicable;

2> else if the corresponding reportConfig includes a purpose set to reportCGI:

3> consider any neighbouring cell detected on the associated frequency/ set of frequencies (GERAN) which has a physical cell identity matching the value of the cellForWhichToReportCGI included in the corresponding measObject within the VarMeasConfig to be applicable;

2> else:

3> if the corresponding measObject concerns E-UTRA:

4> if the ue - RxTxTimeDiffPeriodical is configured in the corresponding reportConfig:

5> consider only the PCell to be applicable;

4> else if the reportSSTD - Meas is set to true in the corresponding reportConfig:

5> consider the PSCell to be applicable;

4> else if the eventA1 or eventA2 is configured in the corresponding reportConfig:

5> consider only the serving cell to be applicable;

4> else if eventC1 or eventC2 is configured in the corresponding reportConfig; or if reportStrongestCSI - RSs is included in the corresponding reportConfig:

5> consider a CSI-RS resource on the associated frequency to be applicable when the concerned CSI-RS resource is included in the measCSI - RS -ToAddModList defined within the VarMeasConfig for this measId;

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

5> consider the resource indicated by the rmtc - Config on the associated frequency to be applicable;

4> else:

5> if useWhiteCellList is set to TRUE:

6> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is included in the whiteCellsToAddModList defined within the VarMeasConfig for this measId;

5> else:

6> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;

5> for events involving a serving cell on one frequency and neighbours on another frequency, consider the serving cell on the other frequency as a neighbouring cell;

4> if the corresponding reportConfig includes alternativeTimeToTrigger and if the UE supports alternativeTimeToTrigger:

5> use the value of alternativeTimeToTrigger as the time to trigger instead of the value of timeToTrigger in the corresponding reportConfig for cells included in the altTTT - CellsToAddModList of the corresponding measObject;

3> else if the corresponding measObject concerns UTRA or CDMA2000:

4> consider a neighbouring cell on the associated frequency to be applicable when the concerned cell is included in the cellsToAddModList defined within the VarMeasConfig for this measId (i.e. the cell is included in the white-list);

The UE may also consider a neighbouring cell on the associated UTRA frequency to be applicable when the concerned cell is included in the csg -allowedReportingCells within the VarMeasConfig for this measId, if configured in the corresponding measObjectUTRA (i.e. the cell is included in the range of physical cell identities for which reporting is allowed).

3> else if the corresponding measObject concerns GERAN:

4> consider a neighbouring cell on the associated set of frequencies to be applicable when the concerned cell matches the ncc -Permitted defined within the VarMeasConfig for this measId;

3> else if the corresponding measObject concerns WLAN:

4> consider a WLAN on the associated set of frequencies, as indicated by carrierFreq or on all WLAN frequencies when carrierFreq is not present, to be applicable if the WLAN matches all WLAN identifiers of at least one entry within wlan-Id-List for this measId;

3> else if the corresponding measObject concerns NR:

4> if the reportSFTD - Meas is set to pSCell in the corresponding reportConfigInterRAT:

5> consider the PSCell to be applicable;

4> else if the reportSFTD - Meas is set to neighborCells in the corresponding reportConfigInterRAT:

5> if cellsForWhichToReportSFTD is configured in the corresponding measObjectNR:

6> consider any neighbouring NR cell on the associated frequency that is included in cellsForWhichToReportSFTD to be applicable;

5> else:

6> consider up to 3 strongest neighbouring NR cells detected on the associated frequency to be applicable when the concerned cells are not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;

4> else:

5> if the eventB1 or eventB2 is configured in the corresponding reportConfig:

6> consider a serving cell, if any, on the associated NR frequency as neighbouring cell;

5> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;

2> if tx- ResourcePoolToAddList is configured in the measObject, and if the corresponding reportConfig includes a purpose set to sidelink or includes eventV1 or eventV2:

3> consider the transmission resource pools indicated by the tx-ResourcePoolToAddList defined within the VarMeasConfig for this measId to be applicable;

2> if the corresponding reportConfig includes a purpose set to reportLocation:

3> consider only the PCell to be applicable;

2> if the triggerType is set to event, and if the corresponding reportConfig does not include numberOfTriggeringCells , and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the event):

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

3> if the UE supports T312 and if useT312 is included for this event and if T310 is running:

4> if T312 is not running:

5> start timer T312 with the value configured in the corresponding measObject;

3> initiate the measurement reporting procedure;

2> if the triggerType is set to event, and if the corresponding reportConfig does not include numberOfTriggeringCells , and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells not included in the cellsTriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent cell triggers the event):

4> if T312 is not running:

3> initiate the measurement reporting procedure;

Hereinafter, measurements are described. The operations described below could be applied to implementation of the present disclosure. Section 5.5 of 3GPP TS 38.331 V15.7.0 may be referred.

The network may configure an RRC_CONNECTED UE to perform measurements and report them in accordance with the measurement configuration. 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.

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 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.

2. Reporting configurations: A list of reporting configurations where there can be one or multiple reporting configurations per measurement object. Each 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.

3. Measurement identities: 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.

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) 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.

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.

Measurement configuration is 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 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))

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 in RRC_CONNECTED the UE applies the layer 3 filtering, before using the measured results for evaluation of reporting criteria and measurement reporting. For cell measurements, the network can configure RSRP, RSRQ or SINR as trigger quantity. 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), irrespective of the trigger quantity.

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.

Layer 3 filtering is described.

The UE shall:

1> for each cell measurement quantity and for each beam measurement quantity that the UE performs measurements:

2> filter the measured result, before using for evaluation of reporting criteria or for measurement reporting

Derivation of cell measurement results is described.

The network may configure the UE to derive RSRP, RSRQ and SINR measurement results per cell associated to NR measurement objects based on parameters configured in the measObject (e.g. maximum number of beams to be averaged and beam consolidation thresholds) and in the reportConfig (rsType to be measured, SS/PBCH block or CSI-RS).

Measurement report triggering is described.

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

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

2> if the corresponding reportConfig includes a reportType set to eventTriggered or periodical:

3> if the corresponding measObject concerns NR:

4> if the eventA1 or eventA2 is configured in the corresponding reportConfig:

5> consider only the serving cell to be applicable;

4> if the eventA3 or eventA5 is configured in the corresponding reportConfig:

5> if a serving cell is associated with a measObjectNR and neighbours are associated with another measObjectNR, consider any serving cell associated with the other measObjectNR to be a neighbouring cell as well;

4> if corresponding reportConfig includes reportType set to periodical; or

4> for measurement events other than eventA1 or eventA2:

5> if useWhiteCellList is set to true:

6> consider any neighbouring cell detected based on parameters in the associated measObjectNR to be applicable when the concerned cell is included in the whiteCellsToAddModList defined within the VarMeasConfig for this measId;

5> else:

6> consider any neighbouring cell detected based on parameters in the associated measObjectNR to be applicable when the concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;

3> else if the corresponding measObject concerns E-UTRA:

4> if eventB1 or eventB2 is configured in the corresponding reportConfig:

5> consider a serving cell, if any, on the associated E-UTRA frequency as neighbour cell;

4> else:

5> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in the blackCellsToAddModListEUTRAN defined within the VarMeasConfig for this measId;

2> else if the corresponding reportConfig includes a reportType set to reportCGI:

3> consider the cell detected on the associated measObject which has a physical cell identity matching the value of the cellForWhichToReportCGI included in the corresponding reportConfig within the VarMeasConfig to be applicable;

2> else if the corresponding reportConfig includes a reportType set to reportSFTD:

3> if the corresponding measObject concerns NR:

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

5> consider the NR PSCell to be applicable;

4> else if the reportSFTD-NeighMeas is included:

5> if cellsForWhichToReportSFTD is configured in the corresponding reportConfig:

6> consider any NR neighbouring cell detected on the associated measObjectNR which has a physical cell identity that is included in the cellsForWhichToReportSFTD to be applicable;

5> else:

6> consider up to 3 strongest NR neighbouring cells detected based on parameters in the associated measObjectNR to be applicable when the concerned cells are not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;

3> else if the corresponding measObject concerns E-UTRA:

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

5> consider the E-UTRA PSCell to be applicable;

2> if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the event):

3> initiate the measurement reporting procedure;

2> else if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells not included in the cellsTriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent cell triggers the event):

3> initiate the measurement reporting procedure;

2> else if the reportType is set to eventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event:

3> remove the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

3> if reportOnLeave is set to true for the corresponding reporting configuration:

4> initiate the measurement reporting procedure;

3> if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty:

4> remove the measurement reporting entry within the VarMeasReportList for this measId;

4> stop the periodical reporting timer for this measId, if running;

2> if reportType is set to periodical and if a (first) measurement result is available:

3> if the reportAmount exceeds 1:

4> initiate the measurement reporting procedure immediately after the quantity to be reported becomes available for the NR SpCell;

3> else (i.e. the reportAmount is equal to 1):

4> initiate the measurement reporting procedure immediately after the quantity to be reported becomes available for the NR SpCell and for the strongest cell among the applicable cells;

2> upon expiry of the periodical reporting timer for this measId:

3> initiate the measurement reporting procedure.

2> if the corresponding reportConfig includes a reportType is set to reportSFTD:

3> if the corresponding measObject concerns NR:

4> initiate the measurement reporting procedure immediately after the quantity to be reported becomes available for each requested pair of PCell and NR cell or the maximal measurement reporting delay;

3> else if the corresponding measObject concerns E-UTRA:

4> initiate the measurement reporting procedure immediately after the quantity to be reported becomes available for the pair of PCell and E-UTRA PSCell or the maximal measurement reporting delay;

2> if reportType is set to reportCGI:

3> if the UE acquired the SIB1 or SystemInformationBlockType1 for the requested cell; or

3> if the UE detects that the requested NR cell is not transmitting SIB1:

4> stop timer T321;

4> include a measurement reporting entry within the VarMeasReportList for this measId;

4> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

4> initiate the measurement reporting procedure;

2> upon the expiry of T321 for this measId:

3> initiate the measurement reporting procedure;

Event A1 (Serving becomes better than threshold) is described.

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A1-2, as specified below, is fulfilled;

1> for this measurement, consider the NR serving cell corresponding to the associated measObjectNR associated with this event.

Inequality A1-1 (Entering condition)

Ms - Hys > Thresh

Inequality A1-2 (Leaving condition)

Ms + Hys < Thresh

The variables in the formula are defined as follows:

Ms is the measurement result of the serving cell, not taking into account any offsets.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).

Thresh is the threshold parameter for this event (i.e. a1-Threshold as defined within reportConfigNR for this event).

Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

Event A2 (Serving becomes worse than threshold) is described.

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A2-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A2-2, as specified below, is fulfilled;

1> for this measurement, consider the serving cell indicated by the measObjectNR associated to this event.

Inequality A2-1 (Entering condition)

Ms + Hys < Thresh

Inequality A2-2 (Leaving condition)

Ms - Hys > Thresh

The variables in the formula are defined as follows:

Thresh is the threshold parameter for this event (i.e. a2-Threshold as defined within reportConfigNR for this event).

Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

Event A3 (Neighbour becomes offset better than SpCell) is described.

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled;

1> use the SpCell for Mp, Ofp and Ocp.

The cell(s) that triggers the event has reference signals indicated in the measObjectNR associated to this event which may be different from the NR SpCell measObjectNR.

Inequality A3-1 (Entering condition)

Mn + Ofn + Ocn - Hys > Mp + Ofp + Ocp + Off

Inequality A3-2 (Leaving condition)

Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off

The variables in the formula are defined as follows:

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

Ofn is the measurement object specific offset of the reference signal of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.

Mp is the measurement result of the SpCell, not taking into account any offsets.

Ofp is the measurement object specific offset of the SpCell (i.e. offsetMO as defined within measObjectNR corresponding to the SpCell).

Ocp is the cell specific offset of the SpCell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell.

Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigNR for this event).

Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.

Event A4 (Neighbour becomes better than threshold) is described.

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A4-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A4-2, as specified below, is fulfilled.

Inequality A4-1 (Entering condition)

Mn + Ofn + Ocn - Hys > Thresh

Inequality A4-2 (Leaving condition)

Mn + Ofn + Ocn + Hys < Thresh

The variables in the formula are defined as follows:

Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).

Ocn is the measurement object specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).

Thresh is the threshold parameter for this event (i.e. a4-Threshold as defined within reportConfigNR for this event).

Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Ofn, Ocn, Hys are expressed in dB.

Thresh is expressed in the same unit as Mn.

Event A5 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2) is described.

The UE shall:

1> consider the entering condition for this event to be satisfied when both condition A5-1 and condition A5-2, as specified below, are fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A5-3 or condition A5-4, i.e. at least one of the two, as specified below, is fulfilled;

1> use the SpCell for Mp.

The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the measObjectNR associated to the event which may be different from the measObjectNR of the NR SpCell.

Inequality A5-1 (Entering condition 1)

Mp + Hys < Thresh1

Inequality A5-2 (Entering condition 2)

Mn + Ofn + Ocn - Hys > Thresh2

Inequality A5-3 (Leaving condition 1)

Mp - Hys > Thresh1

Inequality A5-4 (Leaving condition 2)

Mn + Ofn + Ocn + Hys < Thresh2

The variables in the formula are defined as follows:

Mp is the measurement result of the NR SpCell, not taking into account any offsets.

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.

Thresh1 is the threshold parameter for this event (i.e. a5- Threshold1 as defined within reportConfigNR for this event).

Thresh2 is the threshold parameter for this event (i.e. a5- Threshold2 as defined within reportConfigNR for this event).

Ofn, Ocn, Hys are expressed in dB.

Thresh1is expressed in the same unit as Mp.

Thresh2 is expressed in the same unit as Mn.

Event A6 (Neighbour becomes offset better than SCell) is described.

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A6-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A6-2, as specified below, is fulfilled;

1> for this measurement, consider the (secondary) cell corresponding to the measObjectNR associated to this event to be the serving cell.

The reference signal(s) of the neighbour(s) and the reference signal(s) of the SCell are both indicated in the associated measObjectNR.

Inequality A6-1 (Entering condition)

Mn + Ocn - Hys > Ms + Ocs + Off

Inequality A6-2 (Leaving condition)

Mn + Ocn + Hys < Ms + Ocs + Off

The variables in the formula are defined as follows:

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within the associated measObjectNR), and set to zero if not configured for the neighbour cell.

Ocs is the cell specific offset of the serving cell (i.e. cellIndividualOffset as defined within the associated measObjectNR), and is set to zero if not configured for the serving cell.

Off is the offset parameter for this event (i.e. a6-Offset as defined within reportConfigNR for this event).

Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Ocn, Ocs, Hys, Off are expressed in dB.

Event B1 (Inter RAT neighbour becomes better than threshold) is described.

The UE shall:

1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled.

Inequality B1-1 (Entering condition)

Mn + Ofn + Ocn - Hys > Thresh

Inequality B1-2 (Leaving condition)

Mn + Ofn + Ocn + Hys < Thresh

The variables in the formula are defined as follows:

Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets.

Ofn is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. eutra -Q- OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the neighbour inter-RAT cell).

Ocn is the cell specific offset of the inter-RAT neighbour cell (i.e. cellIndividualOffset as defined within the measObjectEUTRA corresponding to the neighbour inter-RAT cell), and set to zero if not configured for the neighbour cell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).

Thresh is the threshold parameter for this event (i.e. b1-ThresholdEUTRA as defined within reportConfigInterRAT for this event).

Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell.

Ofn, Ocn, Hys are expressed in dB.

Thresh is expressed in the same unit as Mn.

Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2) is described.

The UE shall:

1> consider the entering condition for this event to be satisfied when both condition B2-1 and condition B2-2, as specified below, are fulfilled;

1> consider the leaving condition for this event to be satisfied when condition B2-3 or condition B2-4, i.e. at least one of the two, as specified below, is fulfilled;

Inequality B2-1 (Entering condition 1)

Mp + Hys < Thresh1

Inequality B2-2 (Entering condition 2)

Mn + Ofn + Ocn - Hys > Thresh2

Inequality B2-3 (Leaving condition 1)

Mp - Hys > Thresh1

Inequality B2-4 (Leaving condition 2)

Mn + Ofn + Ocn + Hys < Thresh2

The variables in the formula are defined as follows:

Mp is the measurement result of the PCell, not taking into account any offsets.

Ofn is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. eutra -Q- OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the inter-RAT neighbour cell).

Thresh1 is the threshold parameter for this event (i.e. b2- Threshold1 as defined within reportConfigInterRAT for this event).

Thresh2 is the threshold parameter for this event (i.e. b2-Threshold2EUTRA as defined within reportConfigInterRAT for this event).

Mp is expressed in dBm in case of RSRP, or in dB in case of RSRQ and SINR.

Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbour cell.

Ofn, Ocn, Hys are expressed in dB.

Thresh1 is expressed in the same unit as Mp.

Thresh2 is expressed in the same unit as Mn.

Measurement reporting is described.

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

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

1> set the measId to the measurement identity that triggered the measurement reporting;

1> for each serving cell configured with servingCellMO:

2> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType:

3> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available:

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

2> else:

3> if SSB based serving cell measurements are available:

4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;

3> else if CSI-RS based serving cell measurements are available:

4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;

1> set the servCellId within measResultServingMOList to include each NR serving cell that is configured with servingCellMO, if any;

1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS -Indexes and maxNrofRS -IndexesToReport:

2> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig;

1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

2> for each measObjectId referenced in the measIdList which is also referenced with servingCellMO, other than the measObjectId corresponding with the measId that triggered the measurement reporting:

3> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig:

4> set the measResultBestNeighCell within measResultServingMOList to include the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR;

4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS -Indexes and maxNrofRS -IndexesToReport:

5> for each best non-serving cell included in the measurement report:

6> include beam measurement information according to the associated reportConfig;

1> if the reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5, or eventB1, or eventB2:

2> if the UE is in NE-DC and the measurement configuration that triggered this measurement report is associated with the MCG:

3> set the measResultServFreqListEUTRA - SCG to include an entry for each E-UTRA SCG serving frequency with the following:

4> include carrierFreq of the E-UTRA serving frequency;

4> set the measResultServingCell to include the available measurement quantities that the UE is configured to measure by the measurement configuration associated with the SCG;

4> if reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

5> set the measResultServFreqListEUTRA - SCG to include within measResultBestNeighCell the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;

1> if reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5:

2> if the UE is in NR-DC and the measurement configuration that triggered this measurement report is associated with the MCG:

3> set the measResultServFreqListNR - SCG to include for each NR SCG serving cell that is configured with servingCellMO, if any, the following:

4> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType:

5> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available according to the measurement configuration associated with the SCG:

6> set the measResultServingCell within measResultServFreqListNR - SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the rsType included in the reportConfig that triggered the measurement report;

4> else:

5> if SSB based serving cell measurements are available according to the measurement configuration associated with the SCG:

6> set the measResultServingCell within measResultServFreqListNR - SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;

5> else if CSI-RS based serving cell measurements are available according to the measurement configuration associated with the SCG:

6> set the measResultServingCell within measResultServFreqListNR - SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;

4> if results for the serving cell derived based on SSB are included:

5> include the ssbFrequency to the value indicated by ssbFrequency as included in the MeasObjectNR of the serving cell;

4> if results for the serving cell derived based on CSI-RS are included:

5> include the refFreqCSI - RS to the value indicated by refFreqCSI - RS as included in the MeasObjectNR of the serving cell;

4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS -Indexes and maxNrofRS -IndexesToReport:

5> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig, where availability is considered according to the measurement configuration associated with the SCG;

5> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig:

6> set the measResultBestNeighCellListNR within measResultServFreqListNR-SCG to include one entry with the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR, where availability is considered according to the measurement configuration associated with the SCG;

7> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS -Indexes and maxNrofRS -IndexesToReport:

8> for each best non-serving cell included in the measurement report:

9> include beam measurement information according to the associated reportConfig, where availability is considered according to the measurement configuration associated with the SCG;

1> if there is at least one applicable neighbouring cell to report:

2> if the reportType is set to eventTriggered or periodical:

3> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following:

4> if the reportType is set to eventTriggered:

5> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId;

4> else:

5> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

4> for each cell that is included in the measResultNeighCells, include the physCellId;

4> if the reportType is set to eventTriggered or periodical:

5> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:

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

7> if rsType in the associated reportConfig is set to ssb:

8> set resultsSSB -Cell within the measResult to include the SS/PBCH block based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in decreasing order of the sorting quantity i.e. the best cell is included first;

8> if reportQuantityRS -Indexes and maxNrofRS - IndexesToReport are configured, include beam measurement information;

7> else if rsType in the associated reportConfig is set to csi-rs:

8> set resultsCSI - RS -Cell within the measResult to include the CSI-RS based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in decreasing order of the sorting quantity i.e. the best cell is included first;

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

7> set the measResult to include the quantity(ies) indicated in the reportQuantity within the concerned reportConfigInterRAT in decreasing order of the sorting quantity i.e. the best cell is included first;

2> else:

3> if the cell indicated by cellForWhichToReportCGI is an NR cell:

4> if plmn - IdentityInfoList of the cgi -Info for the concerned cell has been obtained:

5> include the plmn - IdentityInfoList including plmn - IdentityList, trackingAreaCode (if available), ranac (if available) and cellIdentity for each entry of the plmn-IdentityInfoList;

5> include frequencyBandList if available;

4> else if MIB indicates the SIB1 is not broadcast:

5> include the noSIB1 including the ssb - SubcarrierOffset and pdcch -ConfigSIB1 obtained from MIB of the concerned cell;

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

4> if all mandatory fields of the cgi -Info-EPC for the concerned cell have been obtained:

5> include in the cgi -Info-EPC the fields broadcasted in E-UTRA SystemInformationBlockType1 associated to EPC;

4> if the UE is E-UTRA/5GC capable and all mandatory fields of the cgi-Info-5GC for the concerned cell have been obtained:

5> include in the cgi -Info- 5GC the fields broadcasted in E-UTRA SystemInformationBlockType1 associated to 5GC;

4> if the mandatory present fields of the cgi -Info for the cell indicated by the cellForWhichToReportCGI in the associated measObject have been obtained:

5> include the freqBandIndicator;

5> if the cell broadcasts the multiBandInfoList, include the multiBandInfoList;

5> if the cell broadcasts the freqBandIndicatorPriority, include the freqBandIndicatorPriority;

1> if the corresponding measObject concerns NR:

2> if the reportSFTD - Meas is set to true within the corresponding reportConfigNR for this measId:

3> set the measResultSFTD-NR in accordance with the following:

4> set sfn - OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers;

4> if the reportRSRP is set to true;

5> set rsrp -Result to the RSRP of the NR PSCell derived based on SSB;

2> else if the reportSFTD - NeighMeas is included within the corresponding reportConfigNR for this measId:

3> for each applicable cell which measurement results are available, include an entry in the measResultCellListSFTD - NR and set the contents as follows:

4> set physCellId to the physical cell identity of the concered NR neighbour cell.

4> if the reportRSRP is set to true:

5> set rsrp -Result to the RSRP of the concerned cell derived based on SSB;

1> else if the corresponding measObject concerns E-UTRA:

2> if the reportSFTD - Meas is set to true within the corresponding reportConfigInterRAT for this measId:

3> set the measResultSFTD-EUTRA in accordance with the following:

4> if the reportRSRP is set to true;

5> set rsrpResult-EUTRA to the RSRP of the EUTRA PSCell;

1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

1> stop the periodical reporting timer, if running;

1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId:

2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;

1> else:

2> if the reportType is set to periodical:

3> remove the entry within the VarMeasReportList for this measId;

3> remove this measId from the measIdList within VarMeasConfig;

1> if the UE is in (NG)EN-DC:

2> if SRB3 is configured:

3> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;

2> else:

3> submit the MeasurementReport message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC.

1> else if the UE is in NR-DC:

2> if the measurement configuration that triggered this measurement report is associated with the SCG:

3> if SRB3 is configured:

4> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;

3> else:

4> submit the MeasurementReport message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC;

1> else:

2> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.

Hereinafter, RRC Connection Release procedure is described.

The purpose of this procedure is:

- to release the RRC connection, which includes the release of the established radio bearers as well as all radio resources; or

- to suspend the RRC connection only if Signalling Radio Bearer 2 (SRB2) and at least one Data Radio Bearer (DRB) are setup, which includes the suspension of the established radio bearers.

The network initiates the RRC connection release procedure to transit a UE in RRC_CONNECTED to RRC_IDLE; or to transit a UE in RRC_CONNECTED to RRC_INACTIVE only if SRB2 and at least one DRB is setup in RRC_CONNECTED; or to transit a UE in RRC_INACTIVE back to RRC_INACTIVE when the UE tries to resume; or to transit a UE in RRC_INACTIVE to RRC_IDLE when the UE tries to resume. The procedure can also be used to release and redirect a UE to another frequency.

The purpose of RRC connection release requested by upper layers is to release the RRC connection. Access to the current Primary Cell (PCell) may be barred as a result of this procedure.

The UE initiates the procedure when upper layers request the release of the RRC connection. The UE shall not initiate the procedure for power saving purposes.

Meanwhile, a wireless device may use a radio link failure (RLF) timer (for example, T310) to declare an RLF on a connection with a network. When the wireless device declares the RLF on the connection with the network, the wireless device may perform connection re-establishment procedure to the network.

In order to reduce the service interruption time, a wireless device may use an early RLF timer (For example, T312). A wireless device may declare the RLF and recovery the connection early by using the early RLF timer.

For example, a wireless device may start an early RLF timer upon transmitting an event based measurement reporting, after an RLF timer is started. When the early RLF timer is expired, a wireless device may declare the RLF, while the RLF timer is still running.

However, there is no procedure to use the early RLF timer, when the RLF timer is started after transmitting the event based measurement reporting. The early RLF timer may only start upon triggering measurement report for a measurement identity while the RLF timer is running.

Considering that the reason to declare the early RLF is that a wireless device is not expected to be able to receive the handover command successfully after transmitting the measurement report due to the bad link quality, the wireless device should be able to start the early RLF timer in such a case.

Hereinafter, a method for declaring early RLF 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. 10 shows an example of a method performed by a wireless device.

In step S1001, a wireless device may receive measurement reporting configuration from a network.

For example, the measurement reporting configuration may include at least one of reporting events.

For example, the reporting events may include at least one of (1) that measurement results on a serving cell becomes worse than a first threshold, or (2) that measurement results on a primary cell (PCell) becomes worse than a second threshold and measurement results on inter-Radio Access Technology (RAT) neighbor cells becomes better than a third threshold.

For example, the reporting events may include at least one of (1) event A1 (Serving becomes better than threshold), (2) event A2 (Serving becomes worse than threshold), (3) event A3 (Neighbour becomes offset better than SpCell), (4) event A4 (Neighbour becomes better than threshold), (5) event A5 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2), (6) event A6 (Neighbour becomes offset better than SCell), (7) event B1 (Inter RAT neighbour becomes better than threshold), and (8) event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2) described above.

For example, a wireless device may perform measurement on a serving frequency and/or at least one of neighbor frequencies. For example, a wireless device may receive a measurement configuration from the network and perform the measurement based on the measurement configuration. For other example, a wireless device may perform measurement based on the measurement reporting configuration received from the network.

According to some embodiments of the present disclosure, a wireless device may store the measurement reporting configuration. In this case a wireless device may configure the measurement reporting configuration, without receiving the measurement reporting configuration from the network.

In step S1002, a wireless device may perform a transmission of a measurement report based on the measurement reporting configuration. An early Radio Link Failure (RLF) timer may be configured for the measurement report.

For example, a wireless device may perform the transmission of the measurement report based on that the measurement results satisfy the reporting event.

For example, the early RLF timer may be configured per cell group. For example, one early RLF timer may be configured for PCell and another early RLF timer may be configured for PSCell.

In step S1003, a wireless device may start a periodical reporting timer upon performing the transmission of the measurement report.

For example, the periodical reporting timer may be configured for the measurement report. For example, a wireless device may perform multiple transmission of the measurement report upon multiple expiry of the periodical reporting timer. For example, the periodical reporting timer may restart upon performing the transmission of the measurement report until the wireless device performs predefined number of transmissions of the measurement report.

For example, the measurement reporting configuration may include (1) a number of the transmission of the measurement report and/or (2) a predefined interval of the periodical reporting timer.

In step S1004, a wireless device may start an RLF timer based on that a physical layer problem is detected after starting the periodical reporting timer.

For example, the physical layer problem may be detected upon receiving, by an upper layer of the wireless device, consecutive "out-of-sync" indications from a physical layer of the wireless device. For example, the upper layer may be an RRC layer.

For example, the RLF timer may be configured per cell group. For example, one RLF timer may be configured for PCell and another RLF timer may be configured for PSCell.

According to some embodiments of the present disclosure, a wireless device may stop the RLF timer based on that a recovery of physical layer problems is detected. For example, a wireless device may stop the RLF timer upon receiving consecutive "in-sync" indications.

In step S1005, a wireless device may start the early RLF timer upon expiry of the periodical reporting timer.

For example, the early RLF timer may be started while the RLF timer is running.

According to some embodiments of the present disclosure, a wireless device may perform another transmission of the measurement report to the network and re-start the periodical reporting timer upon the expiry of the periodical reporting timer.

For example, a wireless device may perform multiple transmissions of the measurement report. The periodical measurement reporting timer may be (re)start upon each of the multiple transmissions of the measurement report. In other words, each of the multiple transmission of the measurement report may be performed with an interval corresponding to the periodical reporting timer.

For example, a wireless device may perform a first transmission of the measurement results and start the periodical measurement timer.

When the periodical measurement timer is expired, the wireless device may perform a second transmission of the measurement report and re-start the periodical measurement timer.

In this case, a wireless device may start the early RLF timer upon expiry of the re-started periodical measurement timer, if the RLF timer has been started after re-starting the periodical reporting timer.

According to some embodiments of the present disclosure, a wireless device may stop the early RLF timer based on that a recovery of physical layer problems is detected. For example, a wireless device may stop the early RLF timer upon receiving consecutive "in-sync" indications.

In step S1006, a wireless device may declare RLF for the at least one cell group upon expiry of the early RLF timer.

For example, a wireless device may perform connection re-establishment procedure upon declaring the RLF.

According to some embodiments of the present disclosure, 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.

In particular, in FIG. 11, UE may start the early RLF timer for a cell group based on the radio link condition of the cell group and periodical reporting timer configured by the cell group.

In step S1101, UE may receive measurement configuration from network.

For example, the measurement configuration may be configured by a cell group and/or for a cell group and/or per cell group.

In step S1102, UE may perform the serving cell and/or the neighbour cell measurement according to the measurement configuration.

In step S1103, UE may perform the measurement reporting when the measurement result of serving cell and/or neighbour cell satisfies the reporting event.

For example, the reporting event may be configured in the measurement reporting configuration.

For example, if a measurement reporting condition is fulfilled for measurement result of an applicable cell during a certain period of time (for example, timeToTrigger), UE may perform the measurement reporting.

In step S1104, UE may start a corresponding periodical reporting timer for the measurement reporting.

For example, the periodical reporting timer may be configured in the measurement configuration.

For example, the periodical reporting timer may start upon performing the measurement reporting. The periodical reporting timer may be related to the number of event-based measurement reporting. The periodical reporting timer and/or the number of event-based measurement reporting may be configured by the network. For example, the number of event-based measurement reporting may be configured as a number equal to and/or larger than 2.

In step S1105, UE may start an RLF timer (for example, T310) when the physical layer problem is detected.

For example, the RLF timer can be configured per cell group, for example, one for PCell and another for PSCell. In this case, UE may start the RLF timer for PCell when the physical layer problem is detected for PCell. UE may start the RLF timer for PSCell when the physical layer problem is detected for PSCell.

For example, when the RLF timer expires, UE may declare RLF for the corresponding cell group. For example, if the RLF timer for PCell expires, UE may declare RLF for MCG. If the RLF timer for PSCell expires, UE may declare RLF for SCG.

For example, upon receiving N310 consecutive "out-of-sync" indications for the SpCell from physical layers, UE may start the RLF timer for the corresponding SpCell.

In step S1106, UE may start an early RLF timer (for example, T312), if the periodical reporting timer expires while the RLF timer is running, and if the early RLF timer is configured for the corresponding measurement reporting.

For example, when the periodical reporting timer expires, UE may (re)start the periodical reporting timer and may transmit a corresponding measurement report. Upon transmitting the corresponding measurement report, since the RLF timer has already been running, the early RLF timer can be started.

For example, the early RLF timer can be configured per cell group, for example, one for PCell and another for PSCell.

For example, UE may start the early RLF timer for PCell if the periodical reporting timer expires while the RLF timer for PCell is running, and if the early RLF timer is configured for the corresponding measurement report.

For example, UE may start the early RLF timer for PSCell if the periodical reporting timer expires while the RLF timer for PSCell is running, and if the early RLF timer is configured for the corresponding measurement report.

For example, when the early RLF timer expires, UE may declare RLF for the corresponding cell group.

For example, if the early RLF timer for PCell expires, UE may declare RLF for MCG. If the early RLF timer for PSCell expires, UE may declare RLF for SCG.

In step S1107, upon declaring RLF, UE may perform connection re-establishment procedure, at least for PCell.

In particular, FIG. 12 shows an example of method performed by a wireless device.

In step S1201, a wireless device may transmit a measurement report. For example, a wireless device may transmit the measurement report when a measurement event is satisfied.

In step S1201, upon transmitting the measurement report, the wireless device may start a periodical reporting timer. For example, the periodical reporting timer may be configured for the measurement report.

For example, a number of transmission of the measurement report and the periodical timer for the measurement report may be configured by a network.

In step S1202, a wireless device may start an RLF timer. For example, a wireless device may start the RLF timer based on that a physical layer problem is detected.

In step S1203, a wireless device may start an early RLF timer upon expiry of the periodical reporting timer.

For example, the wireless device may start the early RLF timer upon expiry of the periodical reporting timer while the RLF timer is running.

In step S1204, a wireless device may perform another transmission of the measurement report upon expiry of the periodical reporting timer started in step S1204.

For example the wireless device may re-start the periodical reporting timer upon transmitting the measurement report.

For example, the transmitted measurement report in S1204 may include same measurement results included in the measurement report transmitted in S1201.

In step S1205, a wireless device may declare an RLF upon expiry of the early RLF timer.

In step S1301, a wireless device may perform a first transmission of a measurement report. Upon transmitting the measurement report, the wireless device may start a periodical reporting timer.

In step S1302, a wireless device may perform a second transmission of the measurement report upon expiry of the periodical reporting timer.

A wireless device may re-start the periodical reporting timer upon performing the second transmission of the measurement report.

In step S1303, a wireless device may start an RLF timer. For example, a wireless device may start the RLF timer based on that a physical layer problem is detected.

In step S1304, a wireless device may start an early RLF timer upon expiry of the periodical reporting timer.

In step S1305, a wireless device may perform a third transmission of the measurement report upon expiry of the re-started periodical reporting timer started in step S1303.

In step S1306, a wireless device may declare an RLF upon expiry of the early RLF timer.

Hereinafter, an apparatus for declaring early RLF 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. 10 to 12. 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 measurement reporting configuration from a network. The processor 102 may be configured to perform a transmission of a measurement report based on the measurement reporting configuration. An early Radio Link Failure (RLF) timer may be configured for the measurement report. The processor 102 may be configured to start a periodical reporting timer upon performing the transmission of the measurement report. The processor 102 may be configured to start an RLF timer based on that a physical layer problem is detected after starting the periodical reporting timer. The processor 102 may be configured to start the early RLF timer upon expiry of the periodical reporting timer. The processor 102 may be configured to declare RLF for the at least one cell group upon expiry of the early RLF timer.

For example, the measurement reporting configuration may include a reporting event based on measurement results.

For example, the reporting event may include at least one of (1) that measurement results on a serving cell becomes worse than a first threshold, or (2) that measurement results on a primary cell (PCell) becomes worse than a second threshold and measurement results on inter-Radio Access Technology (RAT) neighbor cells becomes better than a third threshold.

For example, the processor 102 may be configured to perform the transmission of the measurement report based on that the measurement results satisfy the reporting event.

For example, the early RLF timer may be started while the RLF timer is running.

For example, the early RLF timer may be configured per cell group.

For example, the processor 102 may be configured to perform another transmission of the measurement report to the network and re-start the periodical reporting timer upon the expiry of the periodical reporting timer.

For example, the periodical reporting timer may be configured for the measurement report.

For example, the processor 102 may be configured to detect the physical layer problem upon receiving, by an upper layer of the wireless device, consecutive "out-of-sync" indications from a physical layer of the wireless device.

For example, the RLF timer may be configured per cell group.

For example, the processor 102 may be configured to perform connection re-establishment procedure upon declaring the RLF.

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 declaring early RLF 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 control the transceiver 106 to receive measurement reporting configuration from a network. The processor may be configured to control the wireless device to perform a transmission of a measurement report based on the measurement reporting configuration. An early Radio Link Failure (RLF) timer may be configured for the measurement report. The processor may be configured to control the wireless device to start a periodical reporting timer upon performing the transmission of the measurement report. The processor may be configured to control the wireless device to start an RLF timer based on that a physical layer problem is detected after starting the periodical reporting timer. The processor may be configured to control the wireless device to start the early RLF timer upon expiry of the periodical reporting timer. The processor may be configured to control the wireless device to declare RLF for the at least one cell group upon expiry of the early RLF timer.

For example, the processor may be configured to control the wireless device to perform the transmission of the measurement report based on that the measurement results satisfy the reporting event.

For example, the early RLF timer may be started while the RLF timer is running.

For example, the early RLF timer may be configured per cell group.

For example, the processor may be configured to control the wireless device to perform another transmission of the measurement report to the network and re-start the periodical reporting timer upon the expiry of the periodical reporting timer.

For example, the processor may be configured to control the wireless device to detect the physical layer problem upon receiving, by an upper layer of the wireless device, consecutive "out-of-sync" indications from a physical layer of the wireless device.

For example, the RLF timer may be configured per cell group.

For example, the processor may be configured to control the wireless device to perform connection re-establishment procedure upon declaring the RLF.

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 declaring early RLF 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 control the transceiver 106 to receive measurement reporting configuration from a network. The stored a plurality of instructions may cause the wireless device to perform a transmission of a measurement report based on the measurement reporting configuration. An early Radio Link Failure (RLF) timer may be configured for the measurement report. The stored a plurality of instructions may cause the wireless device to start a periodical reporting timer upon performing the transmission of the measurement report. The stored a plurality of instructions may cause the wireless device to start an RLF timer based on that a physical layer problem is detected after starting the periodical reporting timer. The stored a plurality of instructions may cause the wireless device to start the early RLF timer upon expiry of the periodical reporting timer. The stored a plurality of instructions may cause the wireless device to declare RLF for the at least one cell group upon expiry of the early RLF timer.

For example, the stored a plurality of instructions may cause the wireless device to perform the transmission of the measurement report based on that the measurement results satisfy the reporting event.

For example, the early RLF timer may be started while the RLF timer is running.

For example, the early RLF timer may be configured per cell group.

For example, the stored a plurality of instructions may cause the wireless device to perform another transmission of the measurement report to the network and re-start the periodical reporting timer upon the expiry of the periodical reporting timer.

For example, the stored a plurality of instructions may cause the wireless device to detect the physical layer problem upon receiving, by an upper layer of the wireless device, consecutive "out-of-sync" indications from a physical layer of the wireless device.

For example, the RLF timer may be configured per cell group.

For example, the stored a plurality of instructions may cause the wireless device to perform connection re-establishment procedure upon declaring the RLF.

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 for declaring early RLF performed by a base station (BS) in a wireless communication system, according to some embodiments of the present disclosure, will be described.

The BS may transmit, to a wireless device, measurement reporting configuration including (1) a reporting event, and (2) information on an early RLF timer, and (3) information on a periodical reporting timer.

The BS may receive, from the wireless device, a connection re-establishment request upon expiry of the early RLF timer. The early RLF timer might be started upon expiry of the periodical reporting timer for an event based measurement report, while an RLF timer is running.

The BS may perform connection re-establishment procedure with the wireless device.

The early RLF timer may be configured for the event based measurement report.

Hereinafter, a base station (BS) for declaring early RLF 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, measurement reporting configuration including (1) a reporting event, and (2) information on an early RLF timer, and (3) information on a periodical reporting timer.

The processor may be configured to control the transceiver to receive, from the wireless device, a connection re-establishment request upon expiry of the early RLF timer. The early RLF timer might be started upon expiry of the periodical reporting timer for an event based measurement report, while an RLF timer is running.

The processor may be configured to perform connection re-establishment procedure with the wireless device.

The early RLF timer may be configured for the event based measurement report.

The present disclosure can have various advantageous effects.

For example, even though the physical layer problem is detected after transmitting the first event-based measurement reporting, a wireless device could declare early RLF.

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 measurement reporting configuration from a network;

performing a transmission of a measurement report based on the measurement reporting configuration, wherein an early Radio Link Failure (RLF) timer is configured for the measurement report;

starting a periodical reporting timer upon performing the transmission of the measurement report;

starting an RLF timer based on that a physical layer problem is detected after starting the periodical reporting timer;

starting the early RLF timer upon expiry of the periodical reporting timer; and

declaring RLF for the at least one cell group upon expiry of the early RLF timer.
The method of claim 1, wherein the measurement reporting configuration includes a reporting event based on measurement results.
The method of claim 2, wherein the reporting event includes at least one of (1) that measurement results on a serving cell becomes worse than a first threshold, or (2) that measurement results on a primary cell (PCell) becomes worse than a second threshold and measurement results on inter-Radio Access Technology (RAT) neighbor cells becomes better than a third threshold.
The method of claim 2, wherein the transmission of the measurement report is performed, based on that the measurement results satisfy the reporting event.
The method of claim 1, wherein the early RLF timer is started while the RLF timer is running.
The method of claim 1, wherein the early RLF timer is configured per cell group.
The method of claim 1, wherein the method further comprises,

performing another transmission of the measurement report to the network and re-starting the periodical reporting timer upon the expiry of the periodical reporting timer.
The method of claim 1, wherein the periodical reporting timer is configured for the measurement report.
The method of claim 1, wherein the measurement reporting configuration includes (1) a number of the transmission of the measurement report and/or (2) a predefined interval of the periodical reporting timer.
The method of claim 1, wherein the physical layer problem is detected upon receiving, by an upper layer of the wireless device, consecutive "out-of-sync" indications from a physical layer of the wireless device.
The method of claim 1, wherein the RLF timer is configured per cell group.
The method of claim 1, wherein the method further comprises,

performing connection re-establishment procedure upon declaring the RLF.
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 measurement reporting configuration from a network;

perform a transmission of a measurement report based on the measurement reporting configuration, wherein an early Radio Link Failure (RLF) timer is configured for the measurement report;

start a periodical reporting timer upon performing the transmission of the measurement report;

start an RLF timer based on that a physical layer problem is detected after starting the periodical reporting timer;

start the early RLF timer upon expiry of the periodical reporting timer; and

declare RLF for the at least one cell group upon expiry of the early RLF timer.
The wireless device of claim 14, wherein the measurement reporting configuration includes a reporting event based on measurement results.
The wireless device of claim 15, wherein the reporting event includes at least one of (1) that measurement results on a serving cell becomes worse than a first threshold, or (2) that measurement results on a primary cell (PCell) becomes worse than a second threshold and measurement results on inter-Radio Access Technology (RAT) neighbor cells becomes better than a third threshold.
The wireless device of claim 15, wherein the transmission of the measurement report is performed, based on that the measurement results satisfy the reporting event.
The wireless device of claim 14, wherein the early RLF timer is started while the RLF timer is running.
The wireless device of claim 14, wherein the early RLF timer is configured per cell group.
The wireless device of claim 14, wherein the at least one processor is further configured to,

perform another transmission of the measurement report to the network and re-starting the periodical reporting timer upon the expiry of the periodical reporting timer.
The wireless device of claim 14, wherein the periodical reporting timer is configured for the measurement report.
The wireless device of claim 14, wherein the measurement reporting configuration includes (1) a number of the transmission of the measurement report and/or (2) a predefined interval of the periodical reporting timer.
The wireless device of claim 14, wherein the physical layer problem is detected upon receiving, by an upper layer of the wireless device, consecutive "out-of-sync" indications from a physical layer of the wireless device.
The wireless device of claim 14, wherein the RLF timer is configured per cell group.
The wireless device of claim 14, wherein the at least one processor is further configured to,

perform connection re-establishment procedure upon declaring the RLF.
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 measurement reporting configuration from a network;

performing a transmission of a measurement report based on the measurement reporting configuration, wherein an early Radio Link Failure (RLF) timer is configured for the measurement report;

starting a periodical reporting timer upon performing the transmission of the measurement report;

starting an RLF timer based on that a physical layer problem is detected after starting the periodical reporting timer;

starting the early RLF timer upon expiry of the periodical reporting timer; and

declaring RLF for the at least one cell group upon expiry of the early RLF timer.
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 measurement reporting configuration from a network;

perform a transmission of a measurement report based on the measurement reporting configuration, wherein an early Radio Link Failure (RLF) timer is configured for the measurement report;

start a periodical reporting timer upon performing the transmission of the measurement report;

start an RLF timer based on that a physical layer problem is detected after starting the periodical reporting timer;

start the early RLF timer upon expiry of the periodical reporting timer; and

declare RLF for the at least one cell group upon expiry of the early RLF timer.
A method performed by a base station in a wireless communication system, the method comprising,

transmitting, to a wireless device, measurement reporting configuration including (1) a reporting event, and (2) information on an early RLF timer, and (3) information on a periodical reporting timer;

receiving, from the wireless device, a connection re-establishment request upon expiry of the early RLF timer, wherein the early RLF timer was started upon expiry of the periodical reporting timer for an event based measurement report, while an RLF timer is running; and

performing connection re-establishment procedure with the wireless device,

wherein the early RLF timer is configured for the event based measurement report.
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, measurement reporting configuration including (1) a reporting event, and (2) information on an early RLF timer, and (3) information on a periodical reporting timer;

control the transceiver to receive, from the wireless device, a connection re-establishment request upon expiry of the early RLF timer, wherein the early RLF timer had been started upon expiry of the periodical reporting timer for an event based measurement report, while an RLF timer is running; and

perform connection re-establishment procedure with the wireless device,

wherein the early RLF timer is configured for the event based measurement report.