Anomaly detection and recovery in wireless communications

Abstract

According to an embodiment of the present disclosure, when an anomaly is detected in a cell group, a user equipment (UE) starts transmitting anomaly information to the cell group, and determines whether to stop transmission to the cell group based on a cause of starting the transmission of the anomaly information.

Description

[Technical Field]

[0001] The present disclosure relates to anomaly detection and recovery in wireless communications. [Background technology]

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology that enables high-speed packet communications. Many methods have been proposed to achieve the LTE goals of reducing user and operator costs, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE requires the following high-level requirements: reduced cost per bit, improved service availability, flexible use of frequency bands, simple architecture, open interfaces, and reasonable terminal power consumption.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work to develop requirements and specifications for the New Radio (NR) system. 3GPP must identify and develop the technical components necessary to successfully standardize NR in a timely manner that meets all immediate market needs and the longer-term requirements presented by the ITU-R (ITU Radio Communication Sector) IMT (International Mobile Telecommunications)-2020 process. NR must also be able to use any spectrum bands up to at least 100 GHz that are available for wireless communications well into the distant future.

[0004] NR targets a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type-Communications), URLLC (Ultra-Reliable and Low Latency Communications), etc. NR must be inherently forward compatible.

[0005] In a wireless communication system, a user equipment (UE) can detect an abnormality in a cell group such as a master cell group (MCG) and / or a secondary cell group (SCG). For example, if the UE detects an abnormality in the SCG, the UE can initiate an SCG abnormality information procedure to recover from the abnormality in the SCG. Summary of the Invention [Problem to be solved by the invention]

[0006] An object of the present disclosure is to provide a method and apparatus for anomaly detection and recovery in a wireless communication system.

[0007] Another object of the present disclosure is to provide a method and apparatus for detecting and recovering from an SCG abnormality in a wireless communication system.

[0008] Another object of the present disclosure is to provide a method and apparatus for SCG anomaly information procedure in a wireless communication system. [Means for solving the problem]

[0009] According to an embodiment of the present disclosure, a method performed by a UE (user equipment) configured to operate in a wireless communication system includes the steps of entering a deactivated state for a cell group, initiating transmission of abnormality information for the cell group while the cell group is in the deactivated state, and suspending transmission for the cell group based on a cause for initiating transmission of abnormality information for the cell group, wherein transmission for the cell group is not suspended based on the first cause being that a beam abnormality has been detected for the cell group while the cell group is in the deactivated state, and transmission for the cell group is suspended based on the second cause other than the first cause.

[0010] According to an embodiment of the present disclosure, a method performed by a network node configured to operate in a wireless communication system includes the steps of transmitting a deactivation command to a UE (user equipment) to enter a deactivated state for a cell group; receiving abnormality information for the cell group from the UE while the cell group is in the deactivated state; and transmitting the abnormality information to other network nodes associated with the cell group, wherein whether transmission for the cell group is suspended is determined based on a cause that initiated transmission of the abnormality information, and if the cause is a first cause, that is, a beam abnormality is detected for the cell group while the cell group is in the deactivated state, transmission for the cell group is not suspended, and if the cause is a second cause that is not the first cause, transmission for the cell group is suspended.

[0011] According to various embodiments, an apparatus is provided for implementing the method.

[0012] The present disclosure has various beneficial effects.

[0013] For example, a UE in an SCG inactive state can further check the cause of the SCG transmission interruption and transmit SCG abnormality information to the network even if SCG transmission is interrupted. Therefore, the present disclosure supports more time-efficient UE operation because the UE can more appropriately indicate to the network that recovery is required before SCG activation than legacy.

[0014] The effects that can be obtained through the specific examples of the present disclosure are not limited to the effects listed above. For example, there may be various technical effects that a person having ordinary skill in the related art can understand or derive from the present disclosure. Therefore, the specific effects of the present disclosure are not limited to those explicitly described in the present disclosure, but may include various effects that can be understood or derive from the technical features of the present disclosure. [Brief explanation of the drawings]

[0015] [Figure 1] 1 illustrates an example of a communication system in which implementations of the present disclosure may be applied. [Figure 2] 1 illustrates an example of a wireless device to which implementations of the present disclosure may be applied. [Figure 3] 1 illustrates an example of a wireless device to which implementations of the present disclosure may be applied. [Figure 4] 1 illustrates another example of a wireless device to which implementations of the present disclosure may be applied. [Figure 5] 1 illustrates an example of a UE to which implementations of the present disclosure may be applied. [Figure 6] 1 illustrates an example of a protocol stack in a 3GPP-based wireless communication system to which the present disclosure may be applied. [Figure 7] 1 illustrates an example of a protocol stack in a 3GPP-based wireless communication system to which the present disclosure may be applied. [Figure 8] 1 illustrates a frame structure in a 3GPP-based wireless communication system to which the present disclosure may be applied. [Figure 9]1 illustrates an example of data flow in a 3GPP NR system to which the present disclosure may be applied. [Figure 10] 1 illustrates an example of a dual connectivity (DC) architecture to which the technical features of the present disclosure are applied. [Figure 11] 10 illustrates an example of a procedure for transmitting SCG abnormality information according to an embodiment of the present disclosure. [Figure 12] 1 illustrates an example of a method performed by a UE according to an embodiment of the present disclosure. [Figure 13] 1 illustrates an example of a method performed by a network node according to an embodiment of the present disclosure. [Figure 14] 1 illustrates an example of an SCG anomaly information procedure according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0016] The following techniques, devices, and systems may be applied to various wireless multiple-access systems. Examples of multiple-access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multicarrier frequency division multiple access (MC-FDMA) systems. CDMA may be implemented over wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented over wireless technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA may be implemented over wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or evolved UTRA (E-UTRA). UTRA is part of the universal mobile telecommunications system (UMTS). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of evolved UMTS (E-UMTS) that uses E-UTRA. 3GPP LTE uses OFDMA on the downlink (DL) and SC-FDMA on the uplink (UL).LTE-A (advanced) is an evolved version of 3GPP LTE.

[0017] For convenience of explanation, the implementation of the present disclosure will be mainly described with reference to a 3GPP-based wireless communication system. However, the technical characteristics of the present disclosure are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system, but aspects of the present disclosure, not limited to a 3GPP-based wireless communication system, can be applied to other mobile communication systems.

[0018] For terms and technologies used in this disclosure that are not specifically described, reference may be made to wireless communication standard documents published prior to this disclosure.

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

[0020] As used in this disclosure, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Thus, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0021] In the present disclosure, "at least one of A and B" can mean "only A," "only B," or "both A and B." Furthermore, in the present disclosure, the expressions "at least one of A or B" and "at least one of A and / or B" can be interpreted in the same way as "at least one of A and B."

[0022] Additionally, in this disclosure, "at least one of A, B, and C" can mean "only A," "only B," "only C," or "any combination of A, B, and C." Additionally, "at least one of A, B, or C" or "at least one of A, B, and / or C" can mean "at least one of A, B, and C."

[0023] Furthermore, parentheses used in the present disclosure may mean "for example." Specifically, when displayed in "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, "control information" in the present disclosure is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, when displayed in "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0024] Technical features described separately in one drawing in this disclosure can be implemented separately or simultaneously.

[0025] In this disclosure, the terms "radio access network (RAN) node," "base station," "gNB," and "cell" may be used interchangeably. Additionally, a UE is a type of wireless device, and in this disclosure, the terms "UE" and "wireless device" may be used interchangeably.

[0026] In this disclosure, the terms "cell quality," "signal strength," "signal quality," "channel condition," "channel quality," "channel condition / reference signal received power (RSRP)," and "reference signal received quality (RSRQ)" may be used interchangeably.

[0027] Without being limited thereto, the various descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in this disclosure may be applied to various fields where device-to-device wireless communication and / or connectivity (e.g., 5G) is required.

[0028] The present disclosure will now be described in more detail with reference to the drawings, in which like reference numerals may refer to like or corresponding hardware, software, and / or functional blocks unless otherwise indicated.

[0029] FIG. 1 illustrates an example of a communication system in which implementations of the present disclosure may be applied.

[0030] The 5G usage scenario shown in FIG. 1 is merely an example, and the technical features of the present disclosure may be applied to other 5G usage scenarios not shown in FIG. 1.

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

[0032] Some use cases may require multiple categories for optimization, while others may focus on only one KPI (key performance indicator). 5G supports these various use cases in a flexible and reliable way.

[0033] eMBB far surpasses basic mobile Internet connections and covers a wide range of interactive and media / entertainment applications in the cloud and augmented reality. Data is one of the core drivers of 5G, and for the first time in the 5G era, dedicated voice services may not be available. 5G is expected to simplify voice processing as applications utilize the data connections provided by the communications system. The increase in traffic is primarily due to the increasing size of content and the rise in applications requiring high data transmission rates. As more devices connect to the Internet, streaming services (audio and video), conversational video, and mobile Internet connections become more widely used. Many of these applications require always-on connections to push real-time information and alerts to users. Cloud storage and applications are rapidly increasing on mobile communication platforms and can be applied to both work and entertainment. Cloud storage is a specific use case that accelerates the increase in uplink data transmission rates. 5G will also be used for remote cloud work. When using haptic interfaces, 5G requires significantly lower end-to-end latency to maintain a good user experience. Entertainment, for example, cloud gaming and video streaming, is another key factor driving demand for mobile broadband capabilities. Smartphones and tablets are essential for entertainment everywhere, including in highly mobile environments such as trains, cars, and airplanes. Another use case is augmented reality for entertainment and information retrieval. In this case, augmented reality requires very low latency and instantaneous data volume.

[0034] One of the most promising use cases for 5G involves the seamless connectivity of embedded sensors across all sectors, or mMTC. Potentially, the number of IoT (internet-of-things) devices is expected to reach 240 million by 2020. Industrial IoT is one of the key roles that will enable smart cities, asset tracking, smart utilities, agriculture, and security infrastructure through 5G.

[0035] URLLC encompasses ultra-reliable, low-latency links that will enable new services and autonomous vehicles that will transform industries through remote control of key infrastructure. Reliability and latency are essential for controlling smart grids, automating industries, achieving robotics, and controlling and coordinating drones.

[0036] 5G is a means of delivering gigabits per second, rated at hundreds of megabits per second, and can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). These high speeds are necessary to deliver 4K and higher (6K, 8K, and higher) resolution TV, as well as virtual and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include immersive sports games. Certain application programs may require specialized network configurations. For example, in the case of VR games, gaming companies need to integrate their core servers with the network operator's edge network servers to minimize latency.

[0037] Automotive is expected to be a key new driver of 5G, with many use cases for vehicular mobile communications. For example, passenger entertainment demands high-speed, high-concurrency mobile communications, as users expect continuous, high-quality connectivity regardless of location or speed. Another use case in the automotive field is AR dashboards. AR dashboards allow drivers to identify objects in the dark outside of their front window and provide overlapping information to the driver, showing the distance and movement of the object. In the future, wireless modules will enable communication between vehicles, between vehicles and supporting infrastructure, and between vehicles and other connected devices (e.g., devices accompanying pedestrians). Safety systems will guide drivers through alternative behavioral processes to drive more safely and reduce the risk of accidents. The next step will be remotely controlled or autonomous vehicles. This requires extremely reliable and fast communication between each other and between vehicles and infrastructure. In the future, autonomous vehicles will perform all driving activities, leaving drivers to focus solely on traffic rather than identifying other vehicles. The technical requirements for autonomous vehicles demand ultra-low latency and ultra-high reliability to enhance road safety to levels unattainable by humans.

[0038] Smart cities and smart homes / buildings, referred to as smart societies, are equipped with high-density wireless sensor networks. A distributed network of intelligent sensors identifies the cost and energy-efficient maintenance requirements of a city or a home. A similar configuration can be implemented for each home. All temperature sensors, window and heating controllers, burglar alarms, and home appliances are wirelessly connected. Many of these sensors typically have low data transmission speeds, power consumption, and cost. However, real-time HD video is required for monitoring by certain types of devices.

[0039] The more energy consumption and distribution, including heat and gas, is decentralized, requiring automated control over distribution sensor networks. Smart grids use digital information and communication technology to collect information, connect sensors to each other, and act on the information collected. Because this information can include supplier and consumer actions, smart grids can improve the distribution of fuels like electricity in ways that are more efficient, reliable, economical, sustainable, and automated. Smart grids can be thought of as another sensor network with low latency.

[0040] Mission-critical applications (e.g., e-health) are one of the 5G usage scenarios. The health sector includes many applications that can take advantage of the benefits of mobile communications. Communication systems can support telemedicine, which provides clinical care in remote locations. Telemedicine helps reduce the barrier of distance and improves access to medical services that are not continuously available in remote rural areas. Telemedicine can also be used in emergency situations to provide critical care and save lives. Mobile communications-based wireless sensor networks can provide remote monitoring and sensing of parameters such as heart rate and blood pressure.

[0041] Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. The possibility of replacing cables with reconfigurable wireless links is therefore an attractive opportunity in many industrial sectors. However, this requires creating wireless connections with similar latency, reliability and capacity to cables, while simplifying their management. When 5G connections are needed, low latency and very low error probability are new requirements.

[0042] Logistics and cargo tracking are important use cases for mobile communications using location-based information systems to enable inventory and package tracking anywhere. Logistics and cargo use cases typically require low data rates but require location information with wide range and reliability.

[0043] 1, a communication system (1) includes wireless devices 100a to 100f, a base station (BS; 200), and a network 300. While FIG. 1 illustrates a 5G network as an example of the network of the communication system (1), implementation of the present disclosure is not limited to the 5G system and can be applied to future communication systems beyond the 5G system.

[0044] The base station 200 and network 300 may be implemented in a wireless device, and a particular wireless device may act as a base station / network node in relation to other wireless devices.

[0045] The wireless devices 100a to 100f represent devices that communicate using a wireless access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. The wireless devices 100a to 100f may include, but are not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a mobile device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, the vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of vehicle-to-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices can include AR / VR / mixed reality (MR) devices and can be implemented in the form of head-mounted devices (HMDs) and head-up displays (HUDs) attached to vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital displays, vehicles, robots, etc. Mobile devices include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances include TVs, refrigerators, and washing machines. IoT devices include sensors and smart meters.

[0046] In the present disclosure, the wireless devices 100a to 100f may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, an autonomous vehicle, a connected automobile, a UAV, an AI module, a robot, an AR device, a VR device, a MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather / environment device, a 5G service-related device, or a fourth industrial revolution-related device.

[0047] For example, a UAV may be an aircraft without personnel on board that navigates by radio control signals.

[0048] For example, a VR device may include a device for implementing objects or backgrounds in a virtual environment. For example, an AR device may include a device that implements objects or backgrounds in a virtual world by connecting them to objects or backgrounds in the real world. For example, an MR device may include a device that implements objects or backgrounds in a virtual world by merging them with objects or backgrounds in the real world. For example, a hologram device may include a device that implements 360-degree 3D images by recording and reproducing 3D information using the optical interference phenomenon that occurs when two laser lights, which can be called a hologram, meet.

[0049] For example, public safety devices may include image relay devices or image devices that can be worn on the user's body.

[0050] For example, MTC and IoT devices may be devices that do not require direct human intervention or operation, such as smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.

[0051] Here, the wireless communication technology implemented in the wireless device of the present disclosure may include not only LTE, NR, and 6G, but also narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology is an example of low-power wide-area network (LPWAN) technology and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology is an example of LPWAN technology and may be referred to by various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE CAT M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present disclosure may include at least one of ZigBee (registered trademark), Bluetooth (registered trademark), and / or LPWAN, which consider low-power communication, but are not limited to the above names. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.

[0052] For example, a medical device may be a device used for the purposes of diagnosing, treating, ameliorating, curing, or preventing disease. For example, a medical device may be a device used to diagnose, treat, ameliorate, or correct an injury or damage. For example, a medical device may be a device used for the purposes of examining, replacing, or modifying a structure or function. For example, a medical device may be a device used for fertility control purposes. For example, medical devices may include therapeutic devices, driving devices, (in vitro) diagnostic devices, hearing aids, or treatment devices.

[0053] For example, a security device may be a device installed to prevent possible danger and maintain safety. For example, a security device may be a camera, a closed circuit television (CCTV), a recorder, or a black box.

[0054] For example, a PIN tech device may be a device capable of providing financial services such as mobile payments. For example, a PIN tech device may include a payment device or a POS system.

[0055] For example, weather / environment devices may include devices that monitor or predict the weather / environment.

[0056] The wireless devices 100a to 100f can be connected to a network 300 via a base station 200. AI technology can be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f can be connected to an AI server 400 via the network 300. The network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, or a network beyond 5G. The wireless devices 100a to 100f can communicate with each other via the base station 200 / network 300, but can also communicate directly (e.g., sidelink communication) without going through the base station 200 / network 300. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (vehicle-to-vehicle) / V2X (vehicle-to-everything) communication). Furthermore, an IoT device (for example, a sensor) can directly communicate with another IoT device (for example, a sensor) or other wireless devices 100a to 100f.

[0057] Wireless communications / connections 150a, 150b, and 150c are established between the wireless devices 100a-100f and / or between the wireless devices 100a-100f and the base station 200 and / or between the base stations 200. Here, the wireless communications / connections are established via various RATs (e.g., 5G NR), such as uplink / downlink communications 150a, sidelink communications 150b (or device-to-device (D2D) communications), and inter-base station communications 150c (e.g., relaying, integrated access and backhaul (IAB)). Through the wireless communications / connections 150a, 150b, and 150c, the wireless devices 100a-100f and the base station 200 can transmit / receive wireless signals to / from each other. For example, the wireless communications / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. For this purpose, based on the various proposals of the present disclosure, at least some of the following processes are performed: various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes.

[0058] FIG. 2 illustrates an example of a wireless device to which the present disclosure may be implemented.

[0059] Referring to FIG. 2, a first wireless device 100 and a second wireless device 200 can transmit and receive wireless signals to / from external devices via various RATs (e.g., LTE and NR).

[0060] 2, {first wireless device 100 and second wireless device 200} may correspond to at least one of {wireless devices 100a-100f and base station 200}, {wireless devices 100a-100f and wireless devices 100a-100f}, and / or {base station 200 and base station 200} in FIG. 1. The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured / set to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. For example, the processor 102 may process information in the memory 104 to generate first information / signals and transmit a wireless signal including the first information / signals via the transceiver 106. The processor 102 can receive a wireless signal containing second information / signal via the transceiver 106 and store information obtained by processing the second information / signal in the memory 104. The memory 104 is connected to the processor 102 and can store various information related to the operation of the processor 102. For example, the memory 104 can execute part or all of the processor controlled by the processor 102 or store software code including instructions for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams described in this disclosure. Here, the processor 102 and the memory 104 can be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 is connected to the processor 102 and can transmit and / or receive wireless signals via one or more antennas 108. Each transceiver 106 can include a transmitter and / or a receiver. The transceiver 106 can be used interchangeably with an RF (radio frequency) unit. In this disclosure, the first wireless device 100 can refer to a communication modem / circuit / chip.

[0061] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured / set to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. For example, the processor 202 may process information in the memory 204 to generate third information / signals and transmit a wireless signal including the third information / signals via the transceiver 206. The processor 202 may receive a wireless signal including fourth information / signals via the transceiver 206 and store information obtained by processing the fourth information / signals in the memory 204. The memory 124 may be coupled to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may execute part or all of the processes controlled by the processor 202 or store software code including instructions for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams described in this disclosure. Here, the processor 202 and memory 204 may be part of a communications modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 is connected to the processor 202 and can transmit and / or receive radio signals via one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In this disclosure, the second wireless device 200 may refer to a communications modem / circuit / chip.

[0062] The hardware elements of the wireless devices 100, 200 will be described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a serviced at an adaptation protocol (SDAP) layer). The one or more processors 102, 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. The one or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. The one or more processors 102, 202 may generate and provide 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 flow diagrams disclosed in this disclosure to the one or more transceivers 106, 206. The one or more processors 102, 202 may receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure.

[0063] The one or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, and / or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, and / or combinations thereof. As an example, the one or more processors 102, 202 may include 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), and / or one or more field programmable gate arrays (FPGAs). The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be implemented using firmware and / or software, and the firmware and / or software may be implemented to include modules, procedures, and functions. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in this disclosure may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in this disclosure may be implemented using firmware or software in the form of code, instructions and / or sets of instructions.

[0064] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, code, instructions, and / or instructions. The one or more memories 104, 204 may be configured as read-only memory (ROM), random access memory (RAM), erasable programmable ROM (EPROM), flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various technologies, such as wired or wireless connections.

[0065] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure from one or more other devices. For example, one or more transceivers 106, 206 can be coupled to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, wireless signals, etc., to one or more other devices. Also, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, wireless signals, etc., from one or more other devices.

[0066] One or more transceivers 106, 206 may be coupled to one or more antennas 108, 208. The one or more transceivers 106, 206 may be configured to transmit or receive user data, control information, radio signals / channels, etc., referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure via one or more antennas 108, 208. In this disclosure, the one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0067] One or more transceivers 106, 206 may convert received user data, control information, radio signals / channels, etc., in RF band signals to baseband signals for processing by one or more processors 102, 202. One or more transceivers 106, 206 may convert processed user data, control information, radio signals / channels, etc., in baseband signals to RF band signals by one or more processors 102, 202. To this end, one or more transceivers 106, 206 may include an (analog) oscillator and / or a filter. For example, the transceiver 106, 206 may up-convert an OFDM baseband signal to a carrier frequency via an (analog) oscillator and / or a filter under the control of the processor 102, 202, and transmit the up-converted OFDM signal at the carrier frequency. The transceiver 106, 206 receives the OFDM signal at the carrier frequency and can down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or a filter under the control of the transceiver 102, 202.

[0068] In an implementation of the present disclosure, a UE can operate as a transmitter in an uplink (UL) and as a receiver in a downlink (DL). In an implementation of the present disclosure, a base station can operate as a receiver in an UL and as a transmitter in a DL. For convenience of technical explanation, the following mainly assumes that the first wireless device 100 operates as a UE and the second wireless device 200 operates as a base station. For example, a processor 102 connected to, mounted on, or exposed to the first wireless device 100 can be configured to perform UE operations according to an implementation of the present disclosure or to control the transceiver 106 to perform UE operations according to an implementation of the present disclosure. A processor 202 connected to, mounted on, or exposed to the second wireless device 200 can be configured to perform base station operations according to an implementation of the present disclosure or to control the transceiver 206 to perform base station operations according to an implementation of the present disclosure.

[0069] In this disclosure, a base station may be referred to as a Node B, eNode B (eNB), or gNB.

[0070] FIG. 3 illustrates an example of a wireless device to which the present disclosure may be implemented.

[0071] The wireless device can be implemented in different ways depending on the use case / service (see Figure 1).

[0072] Referring to Figure 3, wireless devices 100, 200 may correspond to wireless devices 100, 200 of Figure 2 and may be configured with various components, devices / portions, and / or modules. For example, each wireless device 100, 200 may include a communication device 110, a control device 120, a memory device 130, and additional components 140. The communication device 110 may include communication circuitry 112 and a transceiver 114. For example, the communication circuitry 112 may include one or more processors 102, 202 of Figure 2 and / or one or more memories 104, 204 of Figure 2. For example, the transceiver 114 may include one or more transceivers 106, 206 of Figure 2 and / or one or more antennas 108, 208 of Figure 2. The control device 120 is electrically connected to the communication device 110, the memory device 130, and the additional components 140 and controls the overall operation of each wireless device 100, 200. For example, the control device 120 can control the electrical / mechanical operation of each of the wireless devices 100, 200 based on the programs / codes / instructions / information stored in the memory device 130. The control device 120 can transmit information stored in the memory device 130 to the outside (e.g., other communication devices) via the communication device 110 via the wireless / wired interface, or can store information received from the outside (e.g., other communication devices) via the communication device 110 via the wireless / wired interface in the memory device 130.

[0073] The additional component 140 may be configured in various ways depending on the type of the wireless device 100, 200. For example, the additional component 140 may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. The wireless device 100, 200 may be implemented in the form of, but is not limited to, a robot (100a in FIG. 1), a vehicle (100b-1 and 100b-2 in FIG. 1), an XR device (100c in FIG. 1), a mobile device (100d in FIG. 1), a home appliance (100e in FIG. 1), an IoT device (100f in FIG. 1), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a financial technology device (or financial device), a security device, a climate / environment device, an AI server / device (400 in FIG. 1), a base station (200 in FIG. 1), or a network node. The wireless devices 100, 200 can be used in mobile or fixed locations depending on the application / service.

[0074] 3, the various components, devices / portions, and / or modules of the wireless devices 100, 200 may be connected to each other via a wired interface, or at least some of them may be connected wirelessly via the communication device 110. For example, in each of the wireless devices 100, 200, the control device 120 and the communication device 110 may be connected via a wired interface, and the control device 120 and a first device (e.g., 130 and 140) may be connected wirelessly via the communication device 110. Each component, device / portion, and / or module within the wireless devices 100, 200 may further include one or more elements. For example, the control device 120 may be configured with a set of one or more processors. As one example, the control device 120 may be configured with a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphics processing unit, and a memory control processor. As another example, the memory device 130 may be configured with RAM, DRAM, ROM, flash memory, volatile memory, non-volatile memory, and / or combinations thereof.

[0075] FIG. 4 illustrates another example of a wireless device to which the present disclosure may be implemented.

[0076] Referring to FIG. 4, the wireless devices 100, 200 may correspond to the wireless devices 100, 200 of FIG. 2 and may be organized into various components, devices / portions and / or modules.

[0077] The first wireless device 100 may include at least one transceiver, such as transceiver 106, and at least one processing chip, such as processing chip 101. The processing chip 101 may include at least one processor, such as processor 102, and at least one memory, such as memory 104. The memory 104 may be operatively connected to the processor 102. The memory 104 may store various types of information and / or instructions. The memory 104 may store software code 105 that, when executed by the processor 102, implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. For example, the software code 105 may implement instructions that, when executed by the processor 102, implements the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. For example, the software code 105 may control the processor 102 to execute one or more protocols. For example, the software code 105 may control the processor 102 to execute one or more air interface protocol layers.

[0078] The second wireless device 200 may include at least one transceiver, such as transceiver 206, and at least one processing chip, such as processing chip 201. The processing chip 201 may include at least one processor, such as processor 202, and at least one memory, such as memory 204. The memory 204 may be operatively connected to the processor 202. The memory 204 may store various types of information and / or instructions. The memory 204 may store software code 205 that, when executed by the processor 202, implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. For example, the software code 205 may implement instructions that, when executed by the processor 202, implements the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. For example, the software code 205 may control the processor 202 to execute one or more protocols. For example, the software code 205 may control the processor 202 to execute one or more air interface protocol layers.

[0079] FIG. 5 illustrates an example of a UE to which the implementation of the present disclosure may be applied.

[0080] Referring to FIG. 5, UE 100 may correspond to first wireless device 100 of FIG. 2 and / or first wireless device 100 of FIG.

[0081] The 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 SIM (subscriber identification module) card 118 , a speaker 120 , and a microphone 122 .

[0082] The processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this 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 flow diagrams disclosed in this disclosure. A layer of an air interface protocol may be implemented in the processor 102. The processor 102 may include an 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), and a modem (modulator and demodulator). An example of the processor 102 is the SNAP DRAGON made by Qualcomm®. TM EXYNOS series processor, made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors, made by Intel® TM series processors or corresponding next generation processors.

[0083] Memory 104 is operatively coupled to processor 102 and stores various information for operating processor 102. Memory 104 may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. The modules may be stored in memory 104 and executed by processor 102. Memory 104 may be implemented within processor 102 or external to processor 102, in which case it may be communicatively coupled to processor 102 via various methods known in the art.

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

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

[0086] The display 114 outputs the results processed by the processor 102. The keypad 116 receives input for use in the processor 102. The keypad 116 is displayed on the display 114.

[0087] SIM card 118 is an integrated circuit for securely storing an international mobile subscriber identity (IMSI) and associated keys, which are used to identify and authenticate subscribers to mobile devices such as cell phones and computers. Many SIM cards can also store contact information.

[0088] A speaker 120 outputs sound-related results processed by the processor 102. A microphone 122 receives sound-related input for use by the processor 102.

[0089] 6 and 7 show examples of protocol stacks in a 3GPP-based wireless communication system to which the present disclosure may be applied.

[0090] In particular, FIG. 6 shows an example of a user plane protocol stack for the air interface between a UE and a BS, and FIG. 7 shows an example of a control plane protocol stack for the air interface between a UE and a BS. The control plane refers to a path over which control messages used by the UE and the network to manage a call are transmitted. The user plane refers to a path over which data generated in the application layer, such as voice data or internet packet data, is transmitted. Referring to FIG. 6, the user plane protocol stack can be divided into layer 1 (i.e., the PHY layer) and layer 2. Referring to FIG. 7, the control plane protocol stack can be divided into layer 1 (i.e., the PHY layer), layer 2, layer 3 (e.g., the RRC layer), and the NAS (Non-Access Stratum) layer. Layers 1, 2, and 3 are referred to as the AS (Access Stratum).

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

[0092] In a 3GPP NR system, the main services and functions of the MAC sublayer include mapping between logical channels and transport channels, multiplexing / demultiplexing MAC SDUs belonging to one or other logical channels to / from transport blocks (TBs) delivered to / from the physical layer on the transport channel, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ) (one HARQ object per cell in the case of Carrier Aggregation (CA)), priority handling between UEs for dynamic scheduling, priority handling between logical channels of one UE for logical channel prioritization, and padding. A single MAC object can support multiple numerologies, transmission timings, and cells. The mapping restrictions for logical channel prioritization control the numerologies, cells, and transmission timings that a logical channel can use.

[0093] The MAC provides various types of data transmission services. Various types of logical channels are defined to allow for different types of data transmission services. That is, each logical channel supports a specific type of information transmission. Each logical channel type is defined by the type of information transmitted. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used only for transmitting control plane information, while traffic channels are used only for transmitting user plane information. The Broadcast Control Channel (BCCH) is a downlink logical channel for broadcasting system control information. The Paging Control Channel (PCCH) is a downlink logical channel for transmitting paging information, system information change notifications, and indications of ongoing Public Warning Service (PWS) broadcasts. The Common Control Channel (CCCH) is a logical channel for transmitting control information between the UE and the network and is used for UEs that do not have an RRC connection with the network. The Dedicated Control Channel (DCCH) is a point-to-point bidirectional logical channel that transmits dedicated control information between the UE and the network and is used by UEs that have an RRC connection. The Dedicated Traffic Channel (DTCH) is a point-to-point logical channel dedicated to one UE for transmitting user information. DTCH exists in both uplink and downlink. In the downlink, the following connections exist between logical channels and transmission channels: BCCH is mapped to BCH (Broadcast Channel), BCCH is mapped to DL-SCH (Downlink Shared Channel), PCCH is mapped to PCH (Paging Channel), CCCH is mapped to DL-SCH, DCCH is mapped to DL-SCH, and DTCH is mapped to DL-SCH. In the uplink, the following connections exist between logical channels and transmission channels:The CCCH is mapped to an Uplink Shared Channel (UL-SCH), the DCCH is mapped to the UL-SCH, and the DTCH is mapped to the UL-SCH.

[0094] The RLC sublayer supports three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). RLC configuration is based on logical channels independent of numerology and / or transmitters. In 3GPP NR systems, the main services and functions of the RLC sublayer vary depending on the transmission mode and include transmission of upper layer PDUs, sequence number assignment independent of PDCP (UM and AM), error correction via ARQ (AM only), RLC SDU segmentation (AM and UM) and re-segmentation (AM only), SDU reassembly (AM and UM), duplicate detection (AM only), RLC SDU discard (AM and UM), RLC re-establishment, and protocol error detection (AM only).

[0095] In a 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane are sequence numbering, header compression and decompression using ROHC (Robust Header Compression), user data transmission, reordering and duplicate detection, in-order delivery, PDCP PDU routing (in case of split bearer), PDCP SDU retransmission, ciphering, deciphering and completeness The main services and functions of the PDCP sublayer for the control plane include protection, PDCP SDU discard, PDCP re-establishment and data recovery for RLC AM, PDCP status reporting for RLC AM, PDCP PDU duplication and duplicate discard indication to the lower layer. completeness It includes protection, control plane data transmission, reordering and duplicate detection, in-order delivery, duplication of PDCP PDUs and indication of duplicate discard to lower layers.

[0096] In 3GPP NR systems, the main services and functions of SDAP include mapping between QoS flows and data radio bearers, and indicating QoS Flow ID (QFI) in all DL and UL packets. A single protocol object in SDAP is configured for each individual PDU session.

[0097] In a 3GPP NR system, the main services and functions of the RRC sublayer include broadcasting of system information related to the AS and NAS, paging initiated by 5GC or NG-RAN, establishment, maintenance and release of the RRC connection between the UE and the 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, and inter-RAT mobility), QoS management functions, UE side information notification and reporting control, radio link failure detection and recovery, and NAS message transmission from / to the UE to / from the NAS.

[0098] FIG. 8 illustrates a frame structure in a 3GPP-based wireless communication system to which the present disclosure is applied.

[0099] The frame structure shown in Figure 8 is purely exemplary, and the number of subframes, the number of slots, and / or the number of symbols in a frame can vary. In a 3GPP-based wireless communication system, the OFDM numerology (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) can be configured to be different among multiple cells for one UE. For example, if a UE is configured with different SCSs for the cell and for aggregated cells, the duration (in absolute time) of time resources (e.g., subframes, slots, or TTIs) containing the same number of symbols can be different among the aggregated cells. Herein, a symbol can include an OFDM symbol (or a CP-OFDM symbol), an SC-FDMA symbol (or a Discrete Fourier Transform-Spread-OFDM (DFT-s-OFDM) symbol).

[0100] Referring to Figure 8, downlink and uplink transmissions are organized into frames. Each frame has a duration of Tf = 10 ms. Each frame is divided into two half-frames, each with a duration of 5 ms. Each half-frame consists of five subframes, with a duration of 1 ms per subframe. Each subframe is divided into slots, and the number of slots within a subframe varies depending on the subcarrier spacing. Each slot contains 14 or 12 OFDM symbols based on the cyclic prefix (CP). With normal CP, each slot contains 14 OFDM symbols, and with extended CP, each slot contains 12 OFDM symbols. The above numerology is based on an exponentially scalable subcarrier spacing of Δf = 2u * 15 kHz. The following table shows the number of OFDM symbols per slot, the number of slots per frame, and the number of slots for normal CP according to a subcarrier spacing of Δf = 2u * 15 kHz.

[0101] Table 1 shows the subcarrier spacing. Number of OFDM symbols per slot for normal CP according to JPEG0007747887000001.jpg4170Nslot symb , number of slots per frame Nframe,u slot , and the number of slots per subframe Nsubframe,u slot This shows:

[0102] [Table 1]

[0103] Table 2 shows the subcarrier spacing. Number of OFDM symbols per slot for extended CP according to JPEG0007747887000003.jpg4170 slot symb , the number of slots per frame N frame,u slot , and the number of slots per subframe for the extended CP, N subframe,u slot This shows:

[0104] [Table 2]

[0105] A slot contains a number of symbols (e.g., 14 or 12 symbols) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a resource grid of Nsize,ugrid,x*NRBsc subcarriers and Nsubframe,usymb OFDM symbols is defined, starting with a common resource block (CRB) Nstart,ugrid specified by higher layer signaling (e.g., radio resource control (RRC) signaling), where Nsize,ugrid,x is the number of resource blocks (RBs) in the resource grid, and the subscript x is DL for the downlink and UL for the uplink. NRBsc is the number of subcarriers per RB. In 3GPP-based wireless communication systems, NRBsc is typically 12. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). The carrier bandwidth Nsize,ugrid for the subcarrier spacing configuration u is given by higher layer parameters (e.g., RRC parameters). Each element in the resource grid for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and one complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l indicating the symbol position relative to a reference point in the time domain. In a 3GPP-based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain. In a 3GPP NR system, RBs are classified into CRBs and physical resource blocks (PRBs). For subcarrier spacing configuration u, CRBs are numbered from 0 upward in the frequency domain. The center of subcarrier 0 of CRB 0 for subcarrier spacing configuration u coincides with 'point A', which acts as a common reference point for the resource block grid. In a 3GPP NR system, PRBs are defined within a bandwidth portion (BWP) and are numbered from 0 to NsizeBWP, i-1, where i is the number of bandwidth portions.The relationship between physical resource blocks nPRB and common resource blocks nCRB ​​in a bandwidth portion i is as follows: nPRB = nCRB ​​+ NsizeBWP,i, where NsizeBWP,i is the common resource block of the bandwidth portion starting from CRB 0. The BWP includes a number of consecutive RBs. A carrier can include up to N (e.g., 5) BWPs. A UE can be configured with one or more BWPs on a given component carrier. Of the BWPs, only one BWP configured for the UE can be activated at a time. The activated BWP defines the UE's operating bandwidth within the cell's operating bandwidth.

[0106] The NR frequency band can be defined as two types of frequency ranges, i.e., FR1 and FR2. The numerical values ​​of these frequency ranges can be changed; for example, the frequency ranges of the two types (FR1 and FR2) can be the same as those shown in Table 1 below. For ease of explanation, in the frequency ranges used in NR systems, FR1 can mean "below 6 GHz range" and FR2 can mean "above 6 GHz range" and can be referred to as millimeter wave (mmW).

[0107] [Table 3]

[0108] As mentioned above, the numerical values ​​of the frequency ranges of the NR system can be changed. For example, FR1 can include the frequency band from 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 can include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included in FR1 can include an unlicensed band. The unlicensed band can be used for various purposes, such as for vehicle (e.g., unmanned driving) communications.

[0109] [Table 4]

[0110] In the present invention, the term "cell" refers to a geographical region or radio resource in which one or more nodes provide a communication system. A "cell" in a geographical region can be understood as the coverage within which a service can be provided using a carrier, and a "cell" as a radio resource (e.g., time-frequency resource) is associated with a bandwidth (BW), which is the frequency range configured by the carrier. A "cell" associated with radio resources is defined by a combination of downlink and uplink resources, for example, a combination of a downlink (DL) component carrier (CC) and an uplink (UL) CC. The cell can be composed of only downlink resources or downlink and uplink resources. Since DL coverage, which is the range within which a node can transmit a valid signal, and UL coverage, which is the range within which the node can receive a valid signal from a UE, depend on the carrier transmitting the signal, the coverage of the node can be associated with the coverage of the "cell" of radio resources used by the node. Thereby, the term "cell" can sometimes be used to refer to the service coverage of a node, and in other cases to a radio resource, or in other cases to the range that a signal using said radio resource can reach with effective strength.

[0111] In carrier aggregation (CA), two or more CCs are aggregated. A UE can simultaneously receive or transmit on one or multiple CCs depending on its capacity. CA is supported for both contiguous and non-contiguous CCs. When CA is configured, the UE has only one radio resource control (RRC) connection with the network. During RRC connection establishment / re-establishment / handover, one serving cell provides non-access stratum (NAS) mobility information, and during RRC connection establishment / re-establishment / handover, one serving cell provides security input. This cell is called the primary cell (PCell). The PCell is the cell operating on the primary frequency, and it is within the cell that the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on the UE's capacity, a secondary cell (SCell) can be configured to form a serving cell set together with the PCell. An SCell is a cell that provides additional radio resources at the top edge of a particular cell. Therefore, the set of serving cells configured for a UE always consists of one PCell and one or more SCells. For dual connectivity operation, the term special cell (SPCell) refers to the PCell of the master cell group (MCG) or the PSCell of the secondary cell group (SCG). The SPCell supports PUCCH transmission and contention-based voluntary access and is always activated. The MCG is a group of serving cells associated with the master node and consists of an SPCell (PCell) and optionally one or more SCells. The SCG is a subset of serving cells associated with a secondary node and consists of a PSCell and zero or more SCells for a UE configured with dual connectivity (DC). For a UE in RRC_CONNECTED that is not configured with CA / DC, there is only one serving cell including the PCell. For a UE in RRC_CONNECTED that is configured with CA / DC, the term "serving cell" is used to refer to the set of cells including the SPCell and all SCells. In DC, two MAC objects are configured in a UE: one for the MCG and one for the SCG.

[0112] FIG. 9 illustrates an example of data flow in a 3GPP NR system.

[0113] In Figure 9, "RB" indicates a radio bearer, and "H" indicates a header. Radio bearers are classified into two groups: data radio bearers (DRBs) for user plane data and signaling radio bearers (SRBs) for control plane data. MAC PDUs are transmitted / received to / from external devices through the PHY layer using radio resources. Such MAC PDUs arrive at the PHY layer in the form of transport blocks.

[0114] At the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to their own physical channels PUSCH and PRACH, respectively, and the downlink transport channels DL-SCH, BCH, and PCH are mapped to PDSCH, PBCH, and PDSCH, respectively. At the PHY layer, uplink control information (UCI) is mapped to PUCCH, and downlink control information (DCI) is mapped to PDCCH. The MAC PDU associated with the UL-SCH is transmitted by the UE via the PUSCH based on an UL grant, and the MAC PDU associated with the DL-SCH is transmitted by the BS via the PDSCH based on a DL assignment.

[0115] FIG. 10 illustrates an example of a dual connectivity (DC) architecture to which the technical features of the present disclosure can be applied.

[0116] 10 illustrates an MN 1011, an SN 1021, and a UE 1030 communicating with the MN 1011 and the SN 1021. As shown in FIG. 10, DC refers to a scheme in which a UE (e.g., UE 1030) uses radio resources provided by at least two RAN nodes including an MN (e.g., MN 1011) and one or more SNs (e.g., SN 1021). In other words, DC refers to a scheme in which a UE is connected to an MN and one or more SNs and communicates with the MN and one or more SNs. Because the MN and the SNs may be located in different locations, the backhaul between the MN and the SNs can be understood as a non-ideal backhaul (e.g., a relatively large delay between nodes).

[0117] MN (e.g., MN 1011) refers to the main RAN node that serves the UE in a DC situation. SN (e.g., SN 1021) refers to an additional RAN node that serves the UE together with the MN in a DC situation. When one RAN node serves the UE, the RAN node may be the MN. The SN may exist when the MN exists.

[0118] For example, an MN may be associated with a macrocell, which has relatively greater coverage than a small cell. However, an MN does not necessarily have to be associated with a macrocell—i.e., an MN may be associated with a small cell. Throughout this disclosure, a RAN node associated with a macrocell may be referred to as a “macrocell node.” An MN includes a macrocell node.

[0119] For example, an SN may be associated with a small cell (e.g., a microcell, picocell, or femtocell) that has relatively smaller coverage than a macrocell. However, an SN does not necessarily have to be associated with a small cell—i.e., an SN may be associated with a macrocell. Throughout this disclosure, a RAN node associated with a small cell may be referred to as a "small cell node." An SN includes a small cell node.

[0120] An MN may be associated with a master cell group (MCG). The MCG refers to a group of serving cells associated with the MN, including a primary cell (PCell) and optionally one or more secondary cells (SCells). User plane data and / or control plane data are transmitted from the core network to the MN via an MCG bearer. The MCG bearer refers to a bearer in which a radio protocol is located in the MN to use MN resources. As shown in Figure 10, the radio protocol of the MCG bearer includes PDCP, RLC, MAC, and / or PHY.

[0121] An SN may be associated with a secondary cell group (SCG). The SCG refers to a group of serving cells associated with an SN, including a primary secondary cell (PSCell) and optionally one or more secondary cells (SCells). User plane data is transmitted from the core network to the SN via an SCG bearer. The SCG bearer refers to a bearer in which a radio protocol resides in the SN to use SN resources. As shown in Figure 10, the radio protocols of the SCG bearer include PDCP, RLC, MAC, and PHY.

[0122] User plane data and / or control plane data are transmitted from the core network to the MN, split up / duplicated in the MN, and at least a portion of the split / duplicated data is transmitted to the SN via a split bearer. A split bearer refers to a bearer in which radio protocols are located in both the MN and the SN to use both MN resources and SN resources. As shown in Figure 10, the radio protocols of the split bearer located in the MN include PDCP, RLC, MAC, and PHY. The radio protocols of the split bearer located in the SN include RLC, MAC, and PHY.

[0123] According to various embodiments, a PDCP anchor / PDCP anchor point / PDCP anchor node refers to a RAN node that includes a PDCP entity that splits and / or replicates data and transmits at least a portion of the split / replicated data to other RAN nodes via the X2 / Xn interface. In the example of Figure 10, the PDCP anchor node may be a MN.

[0124] According to various embodiments, the MN for a UE can be changed, which is called a handover or MN handover.

[0125] According to various embodiments, an SN may newly begin providing radio resources to a UE, establish a connection with the UE, and / or communicate with the UE (i.e., an SN for a UE may be newly added), which is referred to as an "SN addition."

[0126] According to various embodiments, the SN for a UE can be changed while the MN for the UE is maintained, which is referred to as an SN change.

[0127] According to various embodiments, DC includes E-UTRAN NR-DC (EN-DC) and / or multiple radio access technology (RAT)-DC (MR-DC). EN-DC refers to a DC situation in which a UE uses radio resources provided by an E-UTRAN node and an NR RAN node. MR-DC refers to a DC situation in which a UE uses radio resources provided by RAN nodes of different RATs.

[0128] The radio link failure (RLF) related operations will now be described.

[0129] The UE can detect a physical layer problem in RRC_CONNECTED. To detect a physical layer problem, the UE:

[0130] 1> If any DAPS bearer is established, T304 is executed and N310 consecutive "out-of-sync" indications are received from lower layers for the source SpCell:

[0131] 2> Start timer T310 for the source SpCell.

[0132] 1> When receiving N310 consecutive "out of sync" indications for the SpCell from the lower layer while T300, T301, T304, T311, T316 or T319 are not being executed:

[0133] 2> Start timer T310 for the SpCell in question.

[0134] The UE can recover from the physical layer problem if it receives N311 consecutive "in-sync" indications for the SpCell from the lower layers while T310 is being executed. If it receives N311 consecutive "in-sync" indications for the SpCell from the lower layers while T310 is being executed, the UE shall:

[0135] 1> Stop timer T310 for the SpCell in question.

[0136] 1> If it is running, stop timer T312 for the SpCell in question.

[0137] In this case, the UE maintains the RRC connection without explicit signaling, i.e., the UE maintains the entire radio resource configuration.

[0138] Periods in which neither "in" nor "out of sync" is reported by L1 do not affect the assessment of the number of consecutive "in" or "out of sync" times.

[0139] To detect RLF the UE must:

[0140] 1> If any DAPS bearer is configured and T304 is operational:

[0141] 2> When T310 expires in the source SpCell; or

[0142] 2> Upon a random access problem indication from the source MCG MAC; or

[0143] 2> Upon a source MCG RLC indication that the maximum number of retransmissions has been reached; or

[0144] 2> When the source MCG MAC indicates a continuous uplink LBT error:

[0145] 3>Consider that a radio link failure (i.e., source RLF) has been detected for the source MCG;

[0146] 3> Suspend all DRB transmission and reception in the source MCG;

[0147] 3>Reconfigure MAC for source MCG;

[0148] 3>Disconnect the source.

[0149] 1>If not:

[0150] 2> During DAPS handover: The following applies only to the target PCell;

[0151] 2> When T310 expires in the PCell; or

[0152] 2> When T312 expires in the PCell; or

[0153] 2> When there is a random access problem indication from the MCG MAC when T300, T301, T304, T311 and T319 have not all been executed; or

[0154] 2> Upon MCG RLC indication that the maximum number of retransmissions has been reached; or

[0155] 2> If connected to an IAB-node, a BH RLF indication is received from the MCG to the BAP entity; or

[0156] 2>When there is a continuous uplink LBT abnormal indication from the MCG MAC while T304 is not executed:

[0157] 3> If the indication is from MCG RLC and CA duplication is configured and activated for the MCG and only allowedServingCells for the logical channel in question contains SCell(s):

[0158] 4>Initiate the anomaly information procedure to report the RLC anomaly.

[0159] 3>If not:

[0160] 4>Consider that a radio link failure to the MCG (i.e., MCG RLF) has been detected;

[0161] 4> Discard any splits of the split RRC message;

[0162] 4>If AS Security is not activated:

[0163] 5> Set the release cause to "Other" and execute the action when going to RRC_IDLE;

[0164] 4> Else, if AS security is activated but SRB2 and at least one DRB or IAB, SRB2 was not configured:

[0165] 5>Store the radio link failure information in VarRLF-Report;

[0166] 5> Set the release cause to "RRC connection abnormality" and execute the action when going to RRC_IDLE;

[0167] 4>If not:

[0168] 5>Store the radio link failure information in VarRLF-Report;

[0169] 5>If T316 is set; and

[0170] 5> If the SCG transmission was not interrupted; and

[0171] 5> If neither PSCell change nor PSCell addition is in progress (i.e., in the case of NR-DC, timer T304 for NR PSCell is not executed or timer T307 for E-UTRA PSCell is not executed in NE-DC):

[0172] 6>Initiate MCG Anomaly Information procedure to report MCG radio link failure.

[0173] 5>If not:

[0174] 6> Initiate the connection re-establishment procedure.

[0175] UE:

[0176] 1> When T310 expires in the PSCell; or

[0177] 1> When T312 expires in the PSCell; or

[0178] 1> When a random access problem indication is received from the SCG MAC; or

[0179] 1> Upon SCG RLC indication that the maximum number of retransmissions has been reached; or

[0180] 1> When connected to an IAB-node, if a BH RLF indication is received from the SCG for the BAP entity; or

[0181] 1>When there is a continuous uplink LBT abnormal indication from the SCG MAC:

[0182] 2> If the indication is from the SCG RLC and CA duplication is configured and activated for the SCG; allowedServingCells contains only SCell(s) for the logical channel in question:

[0183] 3> Initiate the anomaly information procedure to report the RLC anomaly.

[0184] 2>If not:

[0185] 3>Consider that a radio link failure (i.e., SCG RLF) has been detected for the SCG.

[0186] 3> If MCG transmission is not interrupted:

[0187] 4> Initiate SCG Anomaly Information procedure to report SCG radio link failure.

[0188] 3>If not:

[0189] 4>If the UE is in NR-DC:

[0190] 5> Initiate connection re-establishment procedure;

[0191] 4> Otherwise (UE is in (NG)EN-DC):

[0192] 5> Initiate connection re-establishment procedure;

[0193] Beam anomaly related operations are described below.

[0194] The MAC entity is configured by RRC for each serving cell with a beam failure recovery procedure that is used to indicate a new SSB or CSI-RS to the serving gNB when a beam failure is detected in the serving SSB(s) / CSI-RS(s). A beam failure is detected by counting beam failure instance indications to the MAC entity at lower layers. If the beamFailureRecoveryConfig is reconfigured at higher layers during an ongoing random access procedure for beam failure recovery for an SpCell, the MAC entity must abort the ongoing random access procedure and start the random access procedure using the new configuration.

[0195] RRC configures BeamFailureRecoveryConfig, BeamFailureRecoverySCellConfig and RadioLinkMonitoringConfig for beam failure detection and recovery procedures.

[0196] - BFI_COUNTER: A counter for beam anomaly instance indications initially set to 0.

[0197] For each serving cell configured for beam anomaly detection, the MAC entity shall:

[0198] 1> When a beam abnormality instance indication is received from the lower layer:

[0199] 2>Start or restart the beamFailureDetectionTimer;

[0200] 2>Increment BFI_COUNTER by 1;

[0201] 2>If BFI_COUNTER>=beamFailureInstanceMaxCount:

[0202] 3> If the serving cell is an SCell:

[0203] 4>Trigger BFR for this serving cell;

[0204] 3>If not:

[0205] 4> Start the random access procedure in the SpCell.

[0206] 1> if the beamFailureDetectionTimer expires; or

[0207] 1>When beamFailureDetectionTimer, beamFailureInstanceMaxCount, or any reference signal used for beam failure detection is reconfigured by higher layers associated with this serving cell:

[0208] 2>Set BFI_COUNTER to 0.

[0209] 1> If the serving cell is an SpCell and the random access procedure initiated for SpCell beam abnormality recovery is completed successfully:

[0210] 2>Set BFI_COUNTER to 0;

[0211] 2> Abort beamFailureRecoveryTimer if set;

[0212] 2> The beam anomaly recovery procedure is deemed to have been completed successfully.

[0213] 1> Otherwise, if the serving cell is an SCell and a PDCCH addressed to the C-RNTI indicating an uplink grant for a new transmission is received for a BFR MAC CE containing beam abnormality recovery information of this serving cell or a HARQ process used for the transmission of a disconnected BFR MAC CE; or

[0214] 1> When SCell is deactivated:

[0215] 2>Set BFI_COUNTER to 0;

[0216] 2> The beam abnormality recovery procedure is considered to have been completed successfully and all BFRs triggered for this serving cell are cancelled.

[0217] In the above, the UE variable BFI_COUNTER is a counter for indicating a beam abnormality instance, which is defined for each serving cell and is initially set to 0.

[0218] The MAC entity:

[0219] 1> If the beam abnormality recovery procedure determines that at least one BFR has been triggered and not canceled for a SCell for which evaluation of candidate beams has been completed:

[0220] 2> If UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the LCP result in a BFR MAC CE and its subheader:

[0221] 3> Instruct the multiplexing and assembly procedure to generate the BFR MAC CE.

[0222] 2> If UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the BFR MAC CE and its subheader truncated as a result of the LCP:

[0223] 3> Instruct the multiplexing and assembly procedure to generate the truncated BFR MAC CE.

[0224] 2>If not:

[0225] 3> Trigger SR for SCell beam abnormality recovery for each SCell for which BFR is not canceled and triggered and evaluation of candidate beams is completed.

[0226] All BFRs triggered for the SCell must be cancelled when a MAC PDU is sent, which includes a BFR MAC CE containing beam abnormality information for the SCell or a disconnected BFR MAC CE.

[0227] The SCG abnormality information procedure is described below.

[0228] The purpose of the SCG Anomaly Information procedure is to inform the E-UTRAN or NR MN of any SCG anomalies experienced by the UE.

[0229] FIG. 11 illustrates an example of a procedure for transmitting SCG abnormality information according to an embodiment of the present disclosure.

[0230] Referring to FIG. 11, in step S1101, the UE may receive an RRC reconfiguration from the network.

[0231] In step S1103, the UE may detect an abnormality for the SCG (ie, an SCG abnormality). The UE may detect the SCG abnormality based on the RRC reconfiguration.

[0232] In step S1105, the UE can send SCG abnormality information to the MCG. The SCG abnormality information can be conveyed to the SCG by the MCG. The UE can start sending SCG abnormality information after / immediately after detecting the SCG abnormality.

[0233] According to various embodiments, the SCG abnormality may be an SCG radio link failure, a synchronized SCG reconfiguration abnormality, an SCG configuration abnormality for an RRC message in SRB3, an SCG completeness This may include at least one of a test abnormality or a consistent uplink LBT abnormality in the PSCell for shared spectrum channel access operation.

[0234] In some implementations, the UE may consider the BWP to be in a deactivated / suspended state for power saving purposes. For example, if the UE receives a command from the network via MAC CE or DCI, the UE may consider the BWP to be in a deactivated / suspended state. For other examples, the UE may consider the BWP to be in a deactivated / suspended state if a predetermined condition is met (e.g., if there is no traffic activity on the UL and / or DL ​​in the BWP for a predetermined period). If the UE receives a command from the network via MAC CE or DCI, if the BWP deactivation / suspended period expires, or if a random access (RA) is triggered in the BWP during the deactivated / suspended state, the UE may consider the BWP to be in an activated state.

[0235] The activated state may refer to a state in which the UE monitors a first set of resources for control channels on a cell group / BWP. For example, in the activated state, the UE has the opportunity to monitor a downlink control channel (physical downlink control channel, PDCCH) for downlink scheduling, perform CSI measurements, perform CSI reporting if necessary, and / or request uplink scheduling if necessary.

[0236] The inactive state may refer to a state in which the UE monitors a second resource set for a control channel on a cell group / BWP or does not monitor a control channel on a cell group / BWP. For example, in the inactive state, the UE does not monitor a PDCCH for downlink scheduling, does not perform CSI measurement, and / or does not perform CSI reporting.

[0237] The first / second set of resources for the control channel may include a control resource set (CORESET) and / or one or more PDCCHs. The second resource set may include sparser resources than the first resource set.

[0238] The idle state may refer to a state in which the UE performs CSI measurement without monitoring the Downlink Control Channel (PDCCH) for downlink scheduling. The UE may not request CSI reporting in the idle state to reduce power consumption. The idle state may be classified as a substate of the active state.

[0239] For a UE configured with an MCG and an SCG, the UE can deactivate the SCG (i.e., consider the SCG to be in a deactivated / stopped state) to save power. While the SCG is deactivated, the UE may need to maintain radio link monitoring to ensure the SCG is available. If an anomaly (e.g., SCG anomaly / beam anomaly) is detected, the UE may need to report the anomaly to the network via the MCG or perform a recovery procedure. Because radio link monitoring requires consistent UE power consumption, power-efficient radio link monitoring is advantageous for a deactivated SCG. Because link anomaly reporting can require additional UE power consumption for uplink transmissions, relaxing the link anomaly criteria for a deactivated SCG can help save power.

[0240] Upon receiving RRCReconfiguration, the UE shall:

[0241] 1> If the UE is configured with E-UTRAnr-Secondary Cell Group Config (UE in (NG)EN-DC):

[0242] 2> If an RRCReconfiguration message is received via E-UTRA SRB1; or

[0243] 2> If an RRCReconfiguration message is received via the E-UTRA RRC message RRCConnectionReconfiguration within MobilityFromNRCommand (handover to (NG)EN-DC in NR stand alone);

[0244] 3> If scg-State is not included in an E-UTRA RRCConnectionReconfiguration message or an E-UTRA RRCConnectionResume message containing an RRCReconfiguration message:

[0245] 4>Perform SCG activation;

[0246] 4>If reconfigurationWithSync is included in spCellConfig of SCG:

[0247] 5>Start the random access procedure in the PSCell;

[0248] 4> Otherwise, if the SCG was deactivated before receiving an E-UTRA RRC message containing an RRCReconfiguration message:

[0249] 5> If bfd-and-RLM is not set to true before receiving an E-UTRA RRCConnectionReconfiguration or RRCConnectionResume message containing an RRCReconfiguration message or if lower layers indicate that a random access procedure is required for SCG activation:

[0250] 6>Start the random access procedure in SpCell;

[0251] 3>If not:

[0252] 4>Perform SCG deactivation.

[0253] 1> When an RRCReconfiguration message is received via SRB1 in the nr-SCG in the mrdc-Secondary Cell Group (for NR-DC UEs, the mrdc-Secondary Cell Group must be received in RRCReconfiguration or RRCResume via SRB1):

[0254] 2> If RRCReconfiguration is applied to perform conditional reconfiguration for a CPC configured via conditionalReconfiguration included in nr-SCG in mrdc-Secondary Cell Group:

[0255] 3> Submit the RRCReconfigurationComplete message embedded in the NR RRC message ULInformationTransferMRDC via the NR MCG.

[0256] 2> If scg-State is not included in the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message:

[0257] 3> If the SCG is deactivated before receiving an NR RRC message containing an RRCReconfiguration message:

[0258] 4>Perform SCG activation;

[0259] 3>If reconfigurationWithSync is included in spCellConfig in nr-SCG:

[0260] 4> Start the random access procedure in the PSCell;

[0261] 3> Otherwise, if the SCG is deactivated before receiving an NR RRC message containing an RRCReconfiguration message:

[0262] 4> bfd-and-RLM was not set to true before receiving an RRCReconfiguration or RRCResume message containing an RRCReconfiguration message; or

[0263] 4> If the lower layer indicates that a random access procedure is required for SCG activation:

[0264] 5>Start the random access procedure in the PSCell;

[0265] 2> If not

[0266] 3>Perform SCG deactivation.

[0267] 1>If RRCReconfiguration is received via SRB1:

[0268] 2>If the UE is in NR-DC;

[0269] 2> If RRCReconfiguration does not include mrdc-Secondary Cell GroupConfig:

[0270] 3>If RRCReconfiguration includes scg-State:

[0271] 4> Perform SCG deactivation;

[0272] 3>If not:

[0273] 4> Perform SCG activation without SN messages.

[0274] On reception of RRCResume, the UE shall:

[0275] 1>If RRCResume includes mrdc-Secondary Cell Group:

[0276] 2> If the received mrdc-Secondary Cell Group is set to nr-SCG:

[0277] 3>If RRRCResume contains scg-State:

[0278] 4> Perform SCG deactivation;

[0279] 3>If not:

[0280] 4>Perform SCG activation.

[0281] When initiating SCG activation and / or while performing SCG activation, the UE shall:

[0282] 1> If the UE is configured to an SCG after receiving a message that initiates the procedure:

[0283] 2> If the UE was configured with a deactivated SCG before receiving the message initiating the procedure:

[0284] 3>Consider SCG activated;

[0285] 3>Restart radio link monitoring execution in SCG if previously stopped;

[0286] 3> Instruct lower layers to resume beam anomaly detection in the PSCell if previously aborted;

[0287] 3> Indicate to lower layers that the SCG has been activated.

[0288] When initiating and / or while performing SCG deactivation, the UE shall:

[0289] 1>SCG is considered inactivated;

[0290] 1>Indicates to lower layers that the SCG has been deactivated;

[0291] 1>If bfd-and-RLM is set to true:

[0292] 2>Perform radio link monitoring in SCG;

[0293] 2> Instruct lower layers to perform beam anomaly detection in the PSCell;

[0294] 1>If not:

[0295] 2>Stop radio link monitoring in SCG;

[0296] 2> Instruct lower layers to suspend beam abnormality detection in the PSCell;

[0297] 2> Abort timer T310 for that cell group if it is running;

[0298] 2> Stop timer T312 for that cell group if it is running;

[0299] 2>Reset counters N310 and N311;

[0300] 1> If the UE is in RRC_CONNECTED and the SCG is activated before receiving the message initiating the procedure:

[0301] 2> If SRB3 is configured before receiving RRCReconfiguration or RRCConnectionReconfiguration and SRB3 is not released by any RadioBearerConfig included in RRCReconfiguration or RRCConnectionReconfiguration:

[0302] 3>Trigger the PDCP entity in SRB3 to perform SDU discard;

[0303] 3>Re-establish the RLC entity of SRB3.

[0304] When initiating SCG activation without an SN message and / or while performing SCG activation without an SN message, the UE shall:

[0305] 1> If the SCG is deactivated before receiving the RRCReconfiguration message or E-UTRA RRCConnectionReconfiguration message for which this procedure is executed:

[0306] 2>Consider SCG activated;

[0307] 2>Indicates to lower layers that the SCG has been activated;

[0308] 2> bfd-and-RLM was not set to true before the reception of the RRCReconfiguration message or E-UTRA RRCConnectionReconfiguration message in which the procedure including this clause is executed; or

[0309] 2> If the lower layer indicates that a random access procedure is required for SCG activation:

[0310] 3> Start the random access procedure in the PSCell.

[0311] For a configured SCG, the MAC entity:

[0312] 1> If the upper layer indicates that the SCG is activated:

[0313] 2>BFI_COUNTER>=beamFailureInstanceMaxCount for the PSCell or timeAlignmentTimer associated with the PTAG is not running:

[0314] 3> Indicate to higher layers that a random access procedure is required for SCG activation.

[0315] 2>If not:

[0316] 3> Activate SCG by timing for direct SCG activation.

[0317] 2> To (re)initialize any interrupted configured uplink grants of configured grant type 1 associated with this PSCell according to the stored configuration (if any) and start at symbol:

[0318] 2> Apply normal SCG operations, including:

[0319] 3>SRS transmission via PSCell;

[0320] 3>CSI report for PSCell;

[0321] 3>PDCCH monitoring for PSCell;

[0322] 3>PUCCH transmission via PSCell;

[0323] 3>Transmit via RACH in PSCell;

[0324] 3> Initialize Bj for each logical channel to 0.

[0325] 1> Otherwise, if the upper layer indicates that the SCG has been deactivated:

[0326] 2> Deactivate all SCells in the SCG;

[0327] 2> Deactivating SCG by timing;

[0328] 2> clear any configured downlink allocation and any configured uplink grant type 2 associated with the PSCell respectively;

[0329] 2> Abort any configured uplink grant type 1 associated with the PSCell;

[0330] 2>Reconfigure your MAC.

[0331] 1> When SCG is inactivated:

[0332] 2>Do not transmit SRS in PSCell;

[0333] 2>Do not report CSI for PSCell;

[0334] 2>Do not transmit via UL-SCH in the PSCell;

[0335] 2>Do not transmit PUCCH in the PSCell;

[0336] 2>Do not transmit via RACH in PSCell;

[0337] 2>Do not monitor PDCCH in the PSCell.

[0338] Meanwhile, the PSCell is suspended due to SCG deactivation. SCG deactivation allows the UE to easily reuse the previously applied SCG configuration, reducing the activation time and enabling time-efficient SCG operation. Furthermore, by not monitoring the PDCCH and not transmitting PDSCH and PUSCH transmissions for the PSCell, power-efficient SCG operation is also possible. In other words, while the SCG is deactivated, the UE can maintain the SCG configuration but does not perform DL and UL data transmissions via the SCG. Therefore, the UE can suspend transmission to the SCG while the SCG is deactivated.

[0339] In addition, when a beam abnormality is detected in a PSCell, a UE in an SCG inactive state can transmit SCG abnormality information to the network (e.g., MCG) to save power by keeping the SCG in an inactive state instead of initiating a random access procedure for beam abnormality recovery.

[0340] In some situations, it may be necessary to determine the reason for the SCG being suspended for transmission on the SCG due to conditions. Therefore, if SCG transmission is suspended due to receipt of an SCG deactivation command, the UE may not transmit SCG abnormality information while the SCG is deactivated.

[0341] Furthermore, if the UE does not perform beam abnormality recovery and transmits SCG abnormality information due to beam abnormality, when a supplemental radio link failure (S-RLF) (i.e., SCG RLF) is later detected, the UE cannot transmit SCG abnormality information (e.g., SCG RLF) to notify the network of a PSCell link problem.

[0342] In the present disclosure, if an SCG abnormality is detected when the SCG is deactivated and SCG transmission is interrupted, the UE can confirm the cause of the transmission interruption. That is, the UE can confirm whether the interruption is due to an SCG abnormality, for example, by sending SCG abnormality information via the MCG. If the interruption is not due to an SCG abnormality, the UE can start reporting SCG abnormality information to the network even if transmission via the SCG is interrupted. When reporting the SCG abnormality information to the network, the UE can change the cause of the transmission interruption to an SCG abnormality. After sending the SCG abnormality information to the network, the UE does not start reporting SCG abnormality information before receiving RRC signaling from the network for SCG recovery because the cause of the transmission interruption is an SCG abnormality.

[0343] SCG abnormalities can occur due to one or more of the following conditions:

[0344] -When a radio link failure is detected in the SCG and / or

[0345] -When the execution of a PSCell change command to the SCG is abnormal; and / or

[0346] -SCG setting abnormality and / or

[0347] -From the lower SCG levels against SRB3 completeness When an abnormal test result is indicated.

[0348] If a beam abnormality for the SCG is detected while the SCG is deactivated, the UE can start reporting SCG abnormality information to the network even while transmission through the SCG is interrupted. However, the UE does not change the cause of the transmission interruption to the SCG abnormality because beam abnormality detection is not a cell-level issue. That is, if the SCG abnormality information is initiated due to a beam abnormality, the UE does not set the cause of the transmission interruption to the SCG abnormality. Therefore, after sending SCG abnormality information due to beam abnormality detection, the UE can start reporting SCG abnormality information again before receiving RRC signaling from the network for SCG recovery because the cause of the transmission interruption is not an SCG abnormality.

[0349] 12 illustrates an example method performed by a UE according to an embodiment of the present disclosure, which may also be performed by a wireless device.

[0350] Referring to FIG. 12, in step S1201, the UE may enter a deactivated state for a cell group.

[0351] In step S1203, the UE may start transmitting abnormal information for the cell group while the cell group is in a deactivated state.

[0352] In step S1205, the UE may suspend transmission to the cell group based on the cause of initiating the transmission of abnormality information to the cell group.

[0353] According to various embodiments, the UE may not suspend transmission for the cell group based on the first cause being that a beam abnormality for the cell group is detected while the cell group is in a deactivated state, and may suspend transmission for the cell group based on the second cause being that the cause is not the first cause. In the present disclosure and various embodiments, the first cause is that a beam abnormality for the cell group is detected while the cell group is in a deactivated state, and the second cause is another initiating cause that is not the first cause.

[0354] According to various embodiments, the UE may suspend transmission in the cell group based on the initiation cause being the first cause as well as the second cause. In this case, the UE may consider the suspension cause differently. For example, based on the initiation cause being the first cause, the UE may consider transmission in the cell group to be suspended due to the first cause, but not suspended due to the second cause. As another example, based on the initiation cause being the second cause, the UE may consider transmission in the cell group to be suspended due to the second cause.

[0355] According to various embodiments, the cell group may include a secondary cell group (SCG) including a primary secondary cell (PSCell). The beam abnormality for the cell group may include a beam abnormality for the PSCell.

[0356] According to various embodiments, the second cause may be a radio link failure (RLF) for the cell group, an abnormal execution of a mobility command for the cell group, a configuration abnormality for the cell group, or a failure of the mobile station for the cell group. completeness This may include at least one of a test abnormality, or a continuous uplink LBT (Listen-Before-Talk) abnormality for the cell group due to unlicensed band operation.

[0357] According to various embodiments, a UE may detect a beam abnormality for the cell group while the cell group is in an inactive state. If a beam abnormality for the cell group is detected while the cell group is in an inactive state, the UE may initiate transmission of first abnormality information for the cell group. If a beam abnormality for the cell group is detected while the cell group is in an inactive state, transmission for the cell group is not suspended based on initiating transmission of the first abnormality information. The UE may transmit the first abnormality information to a network (e.g., MCG) based on initiating transmission of the first abnormality information.

[0358] According to various embodiments, the first anomaly information may indicate that a beam anomaly has been detected in the cell group.

[0359] According to various embodiments, after transmitting the first anomaly information, the UE may start transmitting second anomaly information for the cell group while transmission for the cell group is not interrupted. The UE may transmit the second anomaly information to the network (e.g., MCG) based on starting transmission of the second anomaly information.

[0360] According to various embodiments, transmission of the second anomaly information can be initiated when the UE detects the second cause, and the second anomaly information can indicate that an anomaly related to the second cause has been detected in the cell group.

[0361] According to various embodiments, transmission of the second anomaly information can be initiated when the UE detects a beam anomaly for the cell group when the cell group is in a deactivated state. The second anomaly information can indicate that a beam anomaly has been detected in the cell group.

[0362] According to various embodiments, after transmitting the first anomaly information, signaling for beam anomaly recovery for the cell group may be received from the network (e.g., MCG), and transmission of the second anomaly information may begin before receiving signaling for beam anomaly recovery for the cell group.

[0363] According to various embodiments, the UE may initiate transmission of the anomaly information if the second cause is detected. The UE may transmit the anomaly information to a network (e.g., MCG) and, if the second cause is detected, may suspend transmission to the cell group based on the initiation of transmission of the anomaly information.

[0364] According to various embodiments, the UE may suspend transmission to the cell group based on the fact that transmission of the abnormality information was not initiated when the UE detects a beam abnormality for the cell group while the cell group is in a deactivated state.

[0365] According to various embodiments, the deactivated state may include a state in which the UE does not monitor the control channel of the cell group or monitors resources for the control channel of the cell group less frequently than in the activated state.

[0366] According to various embodiments, a UE may receive an instruction to deactivate a cell group from a network and deactivate the cell group. The UE may detect a condition among a plurality of conditions for transmitting cell group abnormality information to the network while the cell group is deactivated. The UE may check whether transmission for the cell group is suspended. If transmission in the cell group is suspended, the UE may check whether there is a cause for suspension. If the cause of suspension is not related to the conditions for transmitting the cell group abnormality information, the UE may transmit the cell group abnormality information to the network. After transmitting the cell group abnormality information, the UE may receive RRC signaling from the network to restore the cell group.

[0367] 13 illustrates an example of a method performed by a network node according to an embodiment of the present disclosure. The network node includes a base station (BS) and is associated with an MCG.

[0368] Referring to FIG. 13, in step S1301, the network may send a deactivation command to a UE (user equipment) to enter a deactivation state for a cell group.

[0369] In step S1303, the network node may receive abnormal information for the cell group from the UE while the cell group is in a deactivated state.

[0370] In step S1305, the network node may transmit the anomaly information to other network nodes associated with the cell group.

[0371] In Figure 13, whether transmission to the cell group is suspended is determined based on the cause of initiating transmission of the anomaly information. For example, if the cause is a first cause, such as a beam anomaly being detected for the cell group while the cell group is in a deactivated state, transmission to the cell group is not suspended. As another example, if the cause is a second cause other than the first cause, transmission to the cell group is suspended.

[0372] According to an embodiment of the present disclosure, when a UE receives an RRCReconfiguration or performs a conditional reconfiguration (CHO or CPC), the UE needs to perform the following actions:

[0373] 1> If RRCReconfiguration indicates that the UE considers the SCG to be deactivated:

[0374] 2> If present, discontinue SCG transmission for all SRBs and DRBs.

[0375] FIG. 14 illustrates an example of an SCG anomaly information procedure according to an embodiment of the present disclosure.

[0376] 14, in step S1401, the UE and the network may perform RRC reconfiguration. The UE may receive an RRC reconfiguration message from the network.

[0377] In step S1403, the UE may send an SCG exception information message to the network. The UE may perform an SCG exception information procedure based on RRC reconfiguration.

[0378] The purpose of the SCG Anomaly Information procedure is to inform the UE of SCG anomalies experienced by the UE (i.e., SCG radio link failures), synchronized SCG reconfiguration anomalies, SCG configuration anomalies for RRC messages of SRB3, and SCG completenessThis is to inform the E-UTRAN or NRMN that a test abnormality, a consistent uplink LBT abnormality in the PSCell for operation via shared spectrum channel access, and / or a beam abnormality has occurred while the SCG is deactivated.

[0379] According to an embodiment of the present disclosure, the UE may initiate an SCG Anomaly Information procedure to report an SCG anomaly if the SCG is not suspended or the SCG transmission is suspended due to other procedures, if the MCG is not suspended, and one of the following conditions is met:

[0380] 1>When a radio link failure is detected for SCG;

[0381] 1> When SCG synchronization resetting error occurs;

[0382] 1>SCG setting abnormality;

[0383] 1> From the lower SCG layer to SRB3 completeness When an abnormal test is indicated; and / or

[0384] 1> When the first beam abnormality is detected for a PSCell before beam abnormality recovery while the SCG is inactive.

[0385] When initiating the SCG Anomaly Information procedure, the UE shall:

[0386] 1> If the SCG was not suspended, suspend SCG transmission for all SRB, DRB and BHRLC channels.

[0387] 1> If the SCG is deactivated and detects a beam abnormality to the PSCell and the procedure is not initiated:

[0388] 2>This procedure, i.e., SCG is considered to have been interrupted due to SCG abnormality.

[0389] 1>Reconfigure the SCG MAC.

[0390] 1> Abort T304 for SCG if running.

[0391] 1> If set, halt conditional reset evaluation for CPC.

[0392] 1>If the UE is in (NG)EN-DC:

[0393] 2>Start sending SCGFailureInformationNR message.

[0394] 1>If not:

[0395] 2>Start sending SCGFailureInformation message.

[0396] According to an embodiment of the present disclosure, the UE may initiate an SCG Anomaly Information procedure to report an SCG anomaly if all MCG and SCG transmissions are not interrupted and one of the following conditions is met:

[0397] 1>When a radio link failure to the SCG is detected;

[0398] 1>When detecting beam abnormality of PSCell while SCG is inactivated;

[0399] 1> When SCG synchronization resetting error occurs;

[0400] 1>SCG setting abnormality; and / or

[0401] 1> From the lower SCG layer to SRB3 completeness When an abnormal test result is indicated.

[0402] When initiating the SCG Anomaly Information procedure, the UE shall:

[0403] 1> If the procedure was not initiated due to a PSCell beam abnormality while the SCG was inactivated:

[0404] 2> Suspend SCG transmission for all SRB, DRB and BHRLC channels (if any).

[0405] 2>Reconfigure the SCG MAC.

[0406] 1> Abort T304 for SCG if running.

[0407] 1> If set, suspend the conditional reset evaluation for the CPC or CPA.

[0408] 1>If the UE is in (NG)EN-DC:

[0409] 2>Start sending SCGFailureInformationNR message.

[0410] 1>If not:

[0411] 2>Start sending SCGFailureInformation message.

[0412] Furthermore, the method from the perspective of a UE described above in FIG. 12 may be performed by the first radio device 100 shown in FIG. 2, the radio device 100 shown in FIG. 3, the first radio device 100 shown in FIG. 4 and / or the UE 100 shown in FIG. 5.

[0413] More specifically, the UE includes at least one transceiver, at least one processor, and at least one computer memory operatively coupled to the at least one processor and storing instructions that perform operations based on being executed by the at least one processor.

[0414] The operations include an operation of entering a deactivated state for a cell group, an operation of initiating transmission of abnormality information for the cell group while the cell group is in the deactivated state, and an operation of suspending transmission for the cell group based on a cause of initiating transmission of abnormality information for the cell group. If the cause is a first cause, that is, a beam abnormality is detected for the cell group while the cell group is in the deactivated state, transmission for the cell group is not suspended. If the cause is a second cause other than the first cause, transmission for the cell group is suspended.

[0415] Furthermore, the method from the UE perspective described above in FIG. 12 may be performed by software code 105 stored in memory 104 included in the first wireless device 100 shown in FIG.

[0416] More specifically, at least one computer-readable medium (CRM) stores instructions that, when executed by at least one processor, perform operations including entering a deactivated state for a cell group, initiating transmission of anomaly information for the cell group while the cell group is in the deactivated state, and suspending transmission for the cell group based on a cause for initiating transmission of anomaly information for the cell group. When the cause is a first cause, that is, a beam abnormality is detected for the cell group while the cell group is in the deactivated state, transmission for the cell group is not suspended. When the cause is a second cause other than the first cause, transmission for the cell group is suspended.

[0417] Furthermore, the method from the perspective of a UE as described above in FIG. 12 may be performed under control of the processor 102 included in the first radio device 100 shown in FIG. 2, under control of the communication unit 110 and / or control unit 120 included in the radio device 100 shown in FIG. 3, under control of the processor 102 included in the first radio device 100 shown in FIG. 4 and / or under control of the processor 102 included in the UE 100 shown in FIG. 5.

[0418] More specifically, an apparatus (e.g., wireless device / UE) configured to operate in a wireless communication system includes at least one processor and at least one computer memory operatively coupled to the at least one processor. The at least one processor is configured / set to perform operations including entering a deactivated state for a cell group, initiating transmission of anomaly information for the cell group while the cell group is in the deactivated state, and suspending transmission for the cell group based on a cause that initiated the transmission of the anomaly information for the cell group. Transmission for the cell group is not suspended based on a first cause, that is, a beam abnormality is detected for the cell group while the cell group is in the deactivated state. Transmission for the cell group is suspended based on a second cause that is not the first cause.

[0419] Furthermore, the method from the perspective of the network node described above in FIG. 13 may be performed by the second radio device 100 shown in FIG. 2, the radio device 100 shown in FIG. 3 and / or the second radio device 200 shown in FIG. 4.

[0420] More specifically, a network node includes at least one transceiver, at least one processor, and at least one computer memory operatively coupled to the at least one processor and storing instructions that perform operations based on being executed by the at least one processor.

[0421] The operations include transmitting a deactivation command to a user equipment (UE) to enter a deactivated state for a cell group, receiving abnormality information for the cell group from the UE while the cell group is in the deactivated state, and transmitting the abnormality information to other network nodes associated with the cell group. Whether transmission for the cell group is suspended is determined based on a cause for initiating transmission of the abnormality information. If the cause is a first cause, that is, a beam abnormality is detected for the cell group while the cell group is in the deactivated state, transmission for the cell group is not suspended. If the cause is a second cause other than the first cause, transmission for the cell group is suspended.

[0422] The present disclosure has various beneficial effects.

[0423] For example, a UE in an SCG inactive state can further check the cause of the SCG transmission interruption and transmit SCG abnormality information to the network even if SCG transmission is interrupted. Therefore, the present disclosure supports more time-efficient UE operation because the UE can more appropriately indicate to the network that recovery is required before SCG activation than legacy.

[0424] The effects that can be obtained through the specific examples of the present disclosure are not limited to the effects listed above. For example, there may be various technical effects that a person having ordinary skill in the related art can understand or derive from the present disclosure. Therefore, the specific effects of the present disclosure are not limited to those explicitly described in the present disclosure, but may include various effects that can be understood or derive from the technical features of the present disclosure.

[0425] The claims herein may be combined in various ways. For example, technical features in method claims herein may be combined to be embodied or performed in an apparatus, and technical features in apparatus claims may be combined to be embodied or performed in a method. Also, technical features in method claims and apparatus claims may be combined to be embodied or performed in an apparatus. Also, technical features in method claims and apparatus claims may be combined to be embodied or performed in a method. Other implementations are within the scope of the following claims.

Claims

1. 1. A method performed by a user equipment (UE) in a wireless communication system, comprising: Detecting that a secondary cell group (SCG) including a primary secondary cell (PSCell) is deactivated; When an abnormality related to the SCG is detected, starting to transmit SCG abnormality information; transmitting the SCG abnormality information to a master cell group (MCG) including a primary cell (PCell); Based on the fact that the transmission of the SCG abnormality information is initiated due to a beam abnormality of the PSCell while the SCG is deactivated, transmission to the SCG is not interrupted; A method in which transmission to the SCG is interrupted based on the fact that the transmission of the SCG anomaly information is initiated due to an anomaly related to the SCG that is not the beam anomaly.

2. The abnormality associated with the SCG that is not the beam abnormality is: RLF (Radio link failure) for the SCG, a synchronization re-setting error of the SCG; Abnormal setting of the SCG, an abnormal integrity test for the SCG; or 2. The method of claim 1, further comprising at least one of: a continuous uplink LBT (Listen-Before-Talk) failure to the SCG for operation in an unlicensed band;

3. The method described in claim 1, wherein the transmission of the SCG anomaly information is initiated due to a beam anomaly of the PSCell while the SCG is deactivated.

4. The method of claim 3 , wherein the SCG anomaly information indicates that the beam anomaly has been detected in the SCG.

5. The method described in claim 3, further comprising a step of receiving signaling for recovery of the beam abnormality of the PSCell after transmitting the SCG abnormality information.

6. The method described in claim 1, wherein the transmission of the SCG anomaly information is initiated for an anomaly related to the SCG that is not a beam anomaly while the transmission to the SCG is not interrupted.

7. The method described in claim 6, wherein the SCG abnormality information indicates that an abnormality related to the SCG that is not a beam abnormality has been detected.

8. The method described in claim 1, wherein the UE does not monitor a control channel in the SCG while the SCG is deactivated.

9. The method of claim 1 , wherein the UE communicates with at least one of a mobile device, a network, or an autonomous vehicle that is not the UE.

10. 1. A user equipment (UE) adapted to operate in a wireless communication system, comprising: at least one transceiver; at least one processor; at least one computer memory operatively coupled to the at least one processor and storing instructions that perform operations based on being executed by the at least one processor; The operation is Detecting that a secondary cell group (SCG) including a primary secondary cell (PSC) is deactivated; When an abnormality related to the SCG is detected, transmission of SCG abnormality information is initiated; transmitting the SCG abnormality information to an MCG (master cell group) including a PCell (primary cell); Based on the fact that the transmission of the SCG abnormality information is initiated due to a beam abnormality of the PSCell while the SCG is deactivated, transmission to the SCG is not interrupted; The UE interrupts transmission to the SCG based on the fact that the transmission of the SCG abnormality information is initiated due to an abnormality related to the SCG that is not the beam abnormality.

11. at least one computer readable medium (CRM) storing instructions for performing operations upon being executed by at least one processor; The operation is Detecting that a secondary cell group (SCG) including a primary secondary cell (PSC) is deactivated; When an abnormality related to the SCG is detected, transmission of SCG abnormality information is initiated; transmitting the SCG abnormality information to an MCG (master cell group) including a PCell (primary cell); Based on the fact that the transmission of the SCG abnormality information is initiated due to a beam abnormality of the PSCell while the SCG is deactivated, transmission to the SCG is not interrupted; The CRM interrupts transmission to the SCG based on the fact that the transmission of the SCG anomaly information is initiated due to an anomaly related to the SCG that is not the beam anomaly.

12. 1. An apparatus configured to operate in a wireless communication system, comprising: at least one processor; at least one memory operably coupled to the at least one processor; The at least one processor Detecting that a secondary cell group (SCG) including a primary secondary cell (PSC) is deactivated; When an abnormality related to the SCG is detected, transmission of SCG abnormality information is initiated; transmitting the SCG abnormality information to a master cell group (MCG) including a primary cell (PCell); Based on the fact that the transmission of the SCG abnormality information is initiated due to a beam abnormality of the PSCell while the SCG is deactivated, transmission to the SCG is not interrupted; The apparatus, wherein transmission to the SCG is interrupted based on the fact that the transmission of the SCG anomaly information is initiated due to an anomaly related to the SCG that is not the beam anomaly.

Images