Method and apparatus for transmitting beam failure recovery information by user equipment in a wireless communication system

Abstract

Method and apparatus for transmitting beam failure recovery information by a user equipment in a wireless communication system. A method for transmitting a truncated beam failure recovery (BFR) medium access control (MAC) control element (CE) by a user equipment (UE) is disclosed. The method includes the steps of: generating a truncated BFR MAC CE while not exceeding an available grant size upon detecting a beam failure on a plurality of serving cells; and transmitting the truncated BFR MAC CE to a network, wherein the step of generating the BFR MAC CE includes: including BFR information of a special cell (SpCell) into the truncated beam failure MAC CE first based on detecting a beam failure on the SpCell; and including first BFR information of each of at least one secondary cell (SCell) into the truncated beam failure MAC CE in an ascending order of serving cell index and including second BFR information of each of the at least one SCell into the truncated beam failure MAC CE in the ascending order of serving cell index based on detecting a beam failure on the at least one SCell.

Description

Technical Field

[0001] The present invention relates to a wireless communication system, and more specifically, to a method and apparatus thereof for transmitting beam fault recovery (BFR) information by a user equipment (UE) in a wireless communication system. Background Technology

[0002] The introduction of new radio communication technologies has led to an increase in the number of user equipments (UEs) that a base station (BS) provides services to within a designated resource area, and also an increase in the amount of control information and data that the BS sends to the UEs. Since the resources typically available for communication between the BS and the UE are limited, new technologies are needed to enable the BS to efficiently receive / transmit uplink / downlink data and / or uplink / downlink control information using limited radio resources. Specifically, in applications where performance is critically dependent on latency, overcoming latency has become a significant challenge. Summary of the Invention

[0003] Technical issues

[0004] Therefore, this disclosure relates to a method for transmitting beam fault recovery (BFR) information by a user equipment (UE) in a wireless communication system, which substantially eliminates one or more problems caused by the limitations and disadvantages of the prior art.

[0005] Technical solution

[0006] Additional advantages, objects, and features of this specification will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following, or may be learned by practice of the specification. The objects and other advantages of the specification may be realized and obtained by means of the structures particularly pointed out in the written description, its claims, and the accompanying drawings.

[0007] A method for transmitting a truncated beam fault recovery (BFR) medium access control (MAC) element (CE) by a user equipment (UE) in a wireless communication system according to an embodiment of the present invention includes the following steps: when a beam fault is detected on a plurality of serving cells, generating a truncated BFR MAC CE without exceeding the available license size; and transmitting the truncated BFR MAC CE to the network, wherein the step of generating the BFR MAC CE includes: based on the detection of a beam fault on a specific cell (SpCell) among the plurality of serving cells, first including the BFR information of the SpCell among the plurality of serving cells into the truncated beam fault MAC CE; and based on the detection of a beam fault on at least one secondary cell (SCell) among the plurality of serving cells, including first BFR information of each of the at least one SCell in ascending order of serving cell index into the truncated beam fault MAC CE, and including second BFR information of each of the at least one SCell in ascending order of serving cell index into the truncated beam fault MAC CE.

[0008] Furthermore, a user equipment (UE) in a wireless communication system according to the present invention includes: at least one transceiver; at least one processor; and at least one computer memory, the at least one computer memory being operatively connected to the at least one processor and storing instructions, the instructions, when executed, causing the at least one processor to perform an operation, the operation including: generating a truncated beam fault (BFR) medium access control (MAC) element (CE) without exceeding the available license size when a beam fault is detected on a plurality of serving cells; and transmitting the truncated BFR MAC CE to the network, wherein the operation of generating the BFR MAC CE includes: firstly including the BFR information of the SpCell among the plurality of serving cells into the truncated beam fault MAC CE based on the detection of a beam fault on a special cell (SpCell) among the plurality of serving cells; and secondly including the first BFR information of each of the at least one SCell in ascending order of serving cell index into the truncated beam fault MAC CE based on the detection of a beam fault on at least one secondary cell (SCell) among the plurality of serving cells. In the CE, the second BFR information of each of the at least one SCell is included in the truncated beam fault MAC CE in ascending order of the serving cell index.

[0009] Preferably, the plurality of serving cells are configured with a plurality of transmit and receive points (TRPs), and the first BFR information is associated with one of the plurality of TRPs, and the second BFR information is associated with another of the plurality of TRPs.

[0010] More preferably, based on the detection of the beam fault on at least two TRPs of the SpCell, the first BFR information and the second BFR information of the SpCell are first included in the truncated beam fault MAC CE before including the first BFR information and the second BFR information of the at least one SCell.

[0011] More preferably, the first BFR information and the second BFR information include fields indicating the corresponding TRP.

[0012] Preferably, the truncated BFR MAC CE includes bitmap information indicating whether the beam fault was detected in each of the plurality of serving cells.

[0013] Those skilled in the art will understand that the effects achievable by the present invention are not limited to those specifically described above, and that other advantages of the present invention will become clearer from the following detailed description.

[0014] Beneficial effects

[0015] According to this disclosure, the truncated enhanced BFR MAC CE includes BFR information for a larger number of cells within a TRP, allowing the network to know the BFR information of more cells and recover from their beam faults. Therefore, in terms of the number of available cells, the UE can inter-communicate data through a larger number of cells.

[0016] The effects obtainable from this invention are not limited to those described above. Furthermore, those skilled in the art to which this invention pertains will clearly understand other effects not mentioned in the following description. Attached Figure Description

[0017] The accompanying drawings, included to provide a further understanding of the invention, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention:

[0018] Figure 1 Examples of communication systems that apply the implementation of this disclosure are illustrated;

[0019] Figure 2 This is a block diagram illustrating an example of a communication device capable of performing the methods according to this disclosure;

[0020] Figure 3Another example of a wireless device that can implement the present invention is illustrated;

[0021] Figure 4 An example of a protocol stack in a wireless communication system based on the 3rd Generation Partnership Project (3GPP) is shown;

[0022] Figure 5 An example of a frame structure in a 3GPP-based wireless communication system is shown;

[0023] Figure 6 An example of data flow in a 3GPP New Radio (NR) system is shown;

[0024] Figure 7 Examples of PDSCH time domain resource allocation via PDCCH and PUSCH time resource allocation via PDCCH are shown.

[0025] Figure 8 An example of physical layer processing at the transmitting side is shown;

[0026] Figure 9 An example of physical layer processing at the receiving side is shown;

[0027] Figure 10 The operation of a wireless device based on an implementation of this disclosure is illustrated;

[0028] Figure 11 and Figure 12 An example of a random access procedure supported by an NR system is shown;

[0029] Figure 13 and Figure 14 Examples of SCell BFR and truncated SCell BFR MAC CE are shown;

[0030] Figure 15 An example of a truncated enhanced BFR MAC CE according to this disclosure is shown; and

[0031] Figure 16 Another example of a truncated enhanced BFR MAC CE according to this disclosure is shown. Detailed Implementation

[0032] Exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. The detailed description given below with reference to the drawings is intended to explain exemplary embodiments of the present disclosure, and not to illustrate the only embodiments that may be implemented according to the present disclosure. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, it will be apparent to those skilled in the art that the present disclosure may be practiced without these specific details.

[0033] The following technologies, devices, and systems can be applied to a variety of wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using radio technologies such as Global System for Mobile Communications (GSM), Universal Packet Radio Service (GPRS), or Enhanced Data Rate Evolution of GSM (EDGE). OFDMA can be implemented using radio technologies such as IEEE 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 Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE uses OFDMA in DL and SC-FDMA in UL. LTE-Advanced (LTE-A) is an evolution of 3GPP LTE.

[0034] For ease of description, the implementation of this disclosure is primarily described with respect to 3GPP-based wireless communication systems. However, the technical features of this disclosure are not limited thereto. For example, although the following detailed description is based on a mobile communication system corresponding to a 3GPP-based wireless communication system, aspects of this disclosure that are not limited to 3GPP-based wireless communication systems are applicable to other mobile communication systems. For terms and techniques used in this disclosure that are not specifically described in this disclosure, reference can be made to wireless communication standards documents published prior to this disclosure. For example, the following documents may be referenced.

[0035] 3GPP LTE

[0036] -3GPP TS 36.211: Physical Channels and Modulation

[0037] -3GPP TS 36.212: Multiplexing and Channel Coding

[0038] -3GPP TS 36.213: Physical Layer Procedures

[0039] -3GPP TS 36.214: Physical Layer; Measurement

[0040] -3GPP TS 36.300: General Description

[0041] -3GPP TS 36.304: User Equipment (UE) Procedures in Idle Mode

[0042] -3GPP TS 36.314: Layer 2 Measurement

[0043] -3GPP TS 36.321: Media Access Control (MAC) Protocol

[0044] -3GPP TS 36.322: Radio Link Control (RLC) Protocol

[0045] -3GPP TS 36.323: Packet Data Convergence Protocol (PDCP)

[0046] -3GPP TS 36.331: Radio Resource Control (RRC) Protocol

[0047] 3GPP NR (e.g., 5G)

[0048] -3GPP TS 38.211: Physical Channels and Modulation

[0049] -3GPP TS 38.212: Multiplexing and Channel Coding

[0050] -3GPP TS 38.213: Physical layer procedures for control

[0051] -3GPP TS 38.214: Physical Layer Procedures for Data

[0052] -3GPP TS 38.215: Physical Layer Measurement

[0053] -3GPP TS 38.300: General Description

[0054] -3GPP TS 38.304: User Equipment (UE) Procedures in Idle Mode and RRC Inactive State

[0055] -3GPP TS 38.321: Media Access Control (MAC) Protocol

[0056] -3GPP TS 38.322: Radio Link Control (RLC) Protocol

[0057] -3GPP TS 38.323: Packet Data Convergence Protocol (PDCP)

[0058] -3GPP TS 38.331: Radio Resource Control (RRC) Protocol

[0059] -3GPP TS 37.324: Service Data Adaptation Protocol (SDAP)

[0060] -3GPP TS 37.340: Multiple Connectivity; General Description

[0061] In this disclosure, a User Equipment (UE) can be a fixed or mobile device. Examples of UEs include various devices that transmit user data and / or various control information to and from a Base Station (BS). In this disclosure, a BS generally refers to a fixed station that communicates with and / or exchanges various data and control information with the UE and other BSs. A BS can be referred to as an Advanced Base Station (ABS), Node B (NB), Evolved Node B (eNB), Base Transceiver System (BTS), Access Point (AP), Processing Server (PS), etc. In particular, a BS for UMTS is referred to as an NB, a BS for Enhanced Packet Core (EPC) / Long Term Evolution (LTE) systems is referred to as an eNB, and a BS for New Radio (NR) systems is referred to as a gNB.

[0062] In this disclosure, a node refers to a point capable of transmitting / receiving radio signals by communicating with a UE. Various types of BSs can be used as nodes regardless of their terminology. For example, a BS, Node B (NB), e-Node B (eNB), picocell eNB (PeNB), home eNB (HeNB), repeater, transponder, etc., can be nodes. Alternatively, a node may not be a BS. For example, a node can be a Radio Remote Headend (RRH) or Radio Remote Unit (RRU). The power level of an RRH or RRU is typically lower than that of a BS. Since an RRH or RRU (hereinafter referred to as RRH / RRU) is typically connected to a BS via a dedicated line such as fiber optic cable, cooperative communication between an RRH / RRU and a BS can be performed smoothly compared to cooperative communication between BSs connected via radio lines. Each node is equipped with at least one antenna. The antenna may include a physical antenna, an antenna port, or a dummy antenna.

[0063] In this disclosure, the term "cell" can refer to a geographical area to which one or more nodes provide a communication system, or it can refer to radio resources. A "cell" of a geographical area can be understood as the coverage area to which a node can provide services using a carrier, and a "cell" as a radio resource (e.g., time-frequency resource) is associated with a bandwidth (BW) as a frequency range configured by a carrier. A "cell" associated with radio resources is defined by a combination of downlink and uplink resources (e.g., a combination of downlink (DL) component carriers (CC) and uplink (UL) CCs). A cell can be configured by downlink resources only, or it can be configured by both downlink and uplink resources. Since the DL coverage area, which is the range to which a node can transmit valid signals, and the UL coverage area, which is the range to which a node can receive valid signals from a UE, depend on the carrier carrying the signal, a node's coverage area can be associated with the coverage area of ​​the "cell" of the radio resources used by the node. Therefore, the term "cell" can sometimes be used to refer to the service coverage area of ​​a node, sometimes to a radio resource, or sometimes to the range to which a signal using a radio resource can reach with effective strength.

[0064] In this disclosure, the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH) refer to a set of time-frequency resources or resource elements (REs) carrying downlink control information (DCI), and a set of time-frequency resources or REs carrying downlink data, respectively. Furthermore, the Physical Uplink Control Channel (PUCCH), the Physical Uplink Shared Channel (PUSCH), and the Physical Random Access Channel (PRACH) refer to a set of time-frequency resources or REs carrying uplink control information (UCI), a set of time-frequency resources or REs carrying uplink data, and a set of time-frequency resources or REs carrying random access signals, respectively.

[0065] In carrier aggregation (CA), two or more radio resources (CCs) are aggregated. A UE can simultaneously receive or transmit on one or more CCs, depending on its capabilities. Both continuous and non-contiguous CCs support CA. 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 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, where the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on the UE's capabilities, secondary cells (SCells) can be configured to form a group of serving cells together with the PCell. An SCell is a cell that provides additional radio resources on a special cell. Therefore, a group of serving cells configured for a UE always consists of one PCell and one or more SCells. In this disclosure, for dual connectivity (DC) operation, the term "special cell" refers to the PCell of the primary cell group (MCG) or the PSCell of the secondary cell group (SCG), and otherwise the term "special cell" refers to the PCell. SpCell supports Physical Uplink Control Channel (PUCCH) transmission and contention-based random access, and is always active. MCG is a set of serving cells associated with the primary node, including the SpCell (PCell) and one or more optional SCells. SCG is a subset of serving cells associated with the secondary node, including the PSCell and zero or more SCells, for a UE configured with a DC. For a UE in RRC CONNECTED without a CA / DC, there is only one serving cell consisting of the PCell. For a UE in RRC_CONNECTED with a CA / DC, the term "serving cell" is used to refer to a set of cells consisting of the SpCell and all SCells.

[0066] MCG is a set of serving cells associated with a primary BS that terminates at least an S1-MME, and SCG is a set of serving cells associated with a secondary BS that provides additional radio resources to the UE but is not a primary BS. An SCG includes a primary SCell (PSCell) and one or more optional SCells. In the DC, two MAC entities are configured in the UE: one for the MCG and one for the SCG. Each MAC entity is configured by the RRC with serving cells supporting PUCCH transmission and contention-based random access. In this disclosure, the term SpCell refers to such a cell, while the term SCell refers to other serving cells. Depending on whether the MAC entity is associated with the MCG or the SCG, the term SpCell refers to the PCell of the MCG or the PSCell of the SCG.

[0067] In this disclosure, monitoring a channel means attempting to decode a channel. For example, monitoring the Physical Downlink Control Channel (PDCCH) means attempting to decode the PDCCH (or a PDCCH candidate).

[0068] In this disclosure, “C-RNTI” refers to cell RNTI, “SI-RNTI” refers to system information RNTI, “P-RNTI” refers to paging RNTI, “RA-RNTI” refers to random access RNTI, “SC-RNTI” refers to single cell RNTI, “SL-RNTI” refers to sidelink RNTI, “SPS C-RNTI” refers to semi-persistent scheduling C-RNTI, and “CS-RNTI” refers to configured scheduling RNTI.

[0069] Figure 1 An example of a communication system that applies the implementation of this disclosure is illustrated.

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

[0071] Some use cases may require multiple categories for optimization, while others can focus on just one key performance indicator (KPI). 5G supports a wide variety of such use cases using flexible and reliable methods.

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

[0073] Additionally, one of the most anticipated 5G use cases involves the ability to seamlessly connect embedded sensors across all sectors, namely, mMTC. The expected number of potential IoT devices is projected to reach 204 billion by 2020. Industrial IoT is one of the key categories performing key roles in enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure through 5G.

[0074] URLLC encompasses new services that will transform industry (such as autonomous vehicles) through remote control of the main infrastructure and ultra-reliable / available low-latency links. Levels of reliability and latency are essential for controlling smart grids, automating industry, enabling robotics, and controlling and adapting drones.

[0075] 5G is the means to deliver streams assessed at hundreds of megabits per second to gigabits per second and can complement fiber-to-the-home (FTTH) and wired broadband (or DOCSIS). Such speeds are needed to deliver TV at 4K or higher resolutions (6K, 8K, and more), as well as virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include almost immersive motion games. Specific applications may require special network configurations. For example, for VR games, game companies need to integrate their core servers into the network operator's edge network servers to minimize latency.

[0076] The automotive industry, along with numerous use cases for mobile communications in vehicles, is expected to be a significant new driving force in 5G. For example, passenger entertainment requires high concurrent capacity and highly mobile broadband. This is because future users continue to expect high-quality connectivity regardless of their location and speed. Another use case in the automotive sector is AR dashboards. AR dashboards allow drivers to identify objects in the dark in addition to those seen through the front window, displaying distances and movement of objects by overlaying information spoken to the driver. In the future, wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure, and information exchange between vehicles and other connected devices (e.g., pedestrian-accompanied devices). Safety systems will guide alternative routes, allowing drivers to drive more safely and thus reducing the risk of accidents. The next stage will be remotely controlled or self-driving vehicles. This requires very high reliability and very fast communication between different self-driving vehicles and between vehicles and infrastructure. In the future, self-driving vehicles will perform all driving activities, and drivers will only focus on abnormal traffic that vehicles cannot recognize. The technological requirements for self-driving vehicles necessitate ultra-low latency and ultra-high reliability, increasing traffic safety to levels that cannot be achieved by humans.

[0077] Smart cities and smart homes / buildings, touted as part of a smart society, will be embedded in high-density wireless sensor networks. These distributed networks of smart sensors will identify conditions for cost- and energy-efficient maintenance in cities or homes. Similar configurations can be implemented for specific homes. All temperature sensors, window and heating controllers, burglar alarms, and home appliances will be wirelessly connected. Many of these sensors are typically low in terms of data transmission rates, power consumption, and cost. However, certain types of devices may require real-time HD video for monitoring.

[0078] The consumption and distribution of energy, including heat and gases, at a higher level necessitates automated control of distribution sensor networks. Smart grids collect information and use digital information and communication technologies to connect sensors to each other, thereby enabling actions based on the collected information. Because this information can include the behavior of supply companies and consumers, smart grids can improve the distribution of fuels such as electricity through methods that are efficient, reliable, economically feasible, production sustainable, and automated. Smart grids can also be considered as another type of sensor network with low latency.

[0079] Mission-critical applications (such as e-health) are one of the use cases for 5G. The health component includes many applications that can benefit from mobile communications. Communication systems can support telemedicine, enabling the delivery of clinical care in remote locations. Telemedicine can help reduce barriers of distance and improve access to healthcare services that are not readily available in remote rural areas. Telemedicine is also used to administer vital treatments and save lives in emergency situations. Mobile communication-based wireless sensor networks can provide remote monitoring and sensing of parameters such as heart rate and blood pressure.

[0080] Wireless and mobile communications are becoming increasingly important in industrial applications. Cabling is costly in terms of installation and maintenance. Therefore, the possibility of replacing cables with reconfigurable wireless links presents an attractive opportunity in many industrial sectors. However, to achieve this replacement, wireless connections need to have similar latency, reliability, and capacity to cables, and simplified wireless connection management is required. When connecting to 5G, low latency and a very low error probability become new requirements.

[0081] Logistics and freight tracking are important use cases for mobile communications, allowing inventory and packages to be tracked anywhere using location-based information systems. Logistics and freight tracking use cases typically require low data rates but demand location information with wide coverage and reliability.

[0082] Reference Figure 1 The communication system 1 includes wireless devices, base stations (BS), and a network. Although Figure 1 An example of a 5G network as a network of communication system 1 is illustrated, but the implementation of this disclosure is not limited to 5G systems and can be applied to future communication systems other than 5G systems.

[0083] The BS and network can be implemented as wireless devices, and a particular wireless device 200a can operate as a BS / network node relative to other wireless devices.

[0084] A wireless device refers to a device that uses a radio access technology (RAT) (e.g., 5G New RAT (NR) or Long Term Evolution LTE) to perform communication, and may be referred to as a communication / wireless / 5G device. Wireless devices may include, but are not limited to, robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, Internet of Things (IoT) devices 100f, and artificial intelligence (AI) devices / servers 400. For example, a vehicle may include a vehicle with wireless communication capabilities, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. A vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and may be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0085] In this disclosure, wireless devices 100a to 100f may be referred to as user equipment (UE). User equipment (UE) may include, for example, cellular phones, smartphones, laptop computers, digital broadcasting terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), navigation systems, tablet PCs, ultrabooks, vehicles, vehicles with autonomous driving capabilities, connected cars, unmanned aerial vehicles (UAVs), artificial intelligence (AI) modules, robots, augmented reality (AR) devices, virtual reality (VR) devices, mixed reality (MR) devices, holographic devices, public safety devices, MTC devices, IoT devices, medical devices, Fintech devices (or financial devices), security devices, weather / environment devices, devices related to 5G services, or devices related to the fourth industrial evolution. Unmanned aerial vehicles (UAVs) may be, for example, aircraft piloted by wireless control signals without human passengers. VR devices may include, for example, devices for realizing objects or backgrounds in a virtual world. AR devices may include, for example, devices implemented by attaching objects or backgrounds in a virtual world to objects or backgrounds in the real world. MR devices can include, for example, devices that integrate virtual world objects or backgrounds into real world objects or backgrounds. Holographic devices can include, for example, devices for creating 360-degree stereoscopic images by recording and reproducing stereoscopic information, utilizing the interference phenomenon of light generated when two lasers, known as holographic imaging, meet. Public safety devices can include, for example, image relay devices or imaging devices wearable on a user's body. MTC devices and IoT devices can be, for example, devices that do not require direct human intervention or manipulation. For example, MTC devices and IoT devices can include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors. Medical devices can be, for example, devices for the purpose of diagnosing, treating, alleviating, curing, or preventing disease. For example, a medical device can be a device for the purpose of diagnosing, treating, alleviating, or correcting damage or injury. For example, a medical device can be a device for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device can be a device for the purpose of regulating pregnancy. For example, medical devices can include devices for treatment, devices for operation, devices for (in vitro) diagnosis, hearing aids, or devices for surgery. Security devices can be, for example, devices installed to prevent potential hazards and maintain security. For example, security devices can be cameras, CCTV, recorders, or black boxes. Fintech devices can be, for example, devices capable of providing financial services such as mobile payments. For example, Fintech devices can include payment devices or point-of-sale (POS) systems. Weather / environment devices can include, for example, devices used to monitor or predict weather / environment.

[0086] Wireless devices 100a to 100f can connect to network 300 via BS200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using 3G networks, 4G (e.g., LTE) networks, 5G (e.g., NR) networks, and super 5G networks. Although wireless devices 100a to 100f can communicate with each other via BS200 / network 300, wireless devices 100a to 100f can also perform direct communication with each other without going through the BS / network (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0087] Wireless communication / connections 150A and 150b can be established between wireless devices 100a to 100f / BS200-BS200. In this document, wireless communication / connections can be established via various RATs (e.g., 5G NR), such as uplink / downlink communication 150a and sidelink communication 150b (or D2D communication). The wireless devices and the BS / wireless devices can transmit / receive radio signals to / from each other via wireless communication / connections 150a and 150b. For example, wireless communication / connections 150a and 150b can transmit / receive signals via various physical channels. To this end, at least a portion of various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes for transmitting / receiving radio signals can be performed based on various proposals of this disclosure.

[0088] Figure 2 This is a block diagram illustrating an example of a communication device capable of performing the methods according to this disclosure.

[0089] Reference Figure 2 The first wireless device 100 and the second wireless device 200 can transmit / receive radio signals to / from external devices via various RATs (e.g., LTE and NR). Figure 2 In this context, {the first wireless device 100 and the second wireless device 200} can be connected with... Figure 1 The {wireless devices 100a to 100f and BS200} and / or {wireless devices 100a to 100f and wireless devices 100a to 100f} correspond to each other.

[0090] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and additionally include one or more transceivers 106 and / or one or more antennas 108. The processors 102 may control the memories 104 and / or the transceivers 106 and may be configured to implement the functions, processes, and / or methods described in this disclosure. For example, the processors 102 may process information in the memories 104 to generate first information / signals, and then transmit a radio signal including the first information / signals via the transceivers 106. The processors 102 may receive radio signals including second information / signals via the transceivers 106, and then store the information obtained by processing the second information / signals in the memories 104. The memories 104 may be connected to the processors 102 and may store various information related to the operation of the processors 102. For example, the memories 104 may store software code including commands for performing some or all of the processes controlled by the processors 102 or for performing the processes and / or methods described in this disclosure. In this document, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each of transceivers 106 may include a transmitter and / or a receiver. Transceivers 106 may be used interchangeably with radio frequency (RF) units. In this invention, a wireless device may represent a communication modem / circuit / chip.

[0091] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and additionally include one or more transceivers 206 and / or one or more antennas 208. The processors 202 may control the memories 204 and / or the transceivers 206 and may be configured to implement the functions, processes, and / or methods described in this disclosure. For example, the processors 202 may process information in the memories 204 to generate third information / signals, and then transmit radio signals including the third information / signals via the transceivers 206. The processors 202 may receive radio signals including fourth information / signals via the transceivers 206, and then store the information obtained by processing the fourth information / signals in the memories 204. The memories 204 may be connected to the processors 202 and may store various information related to the operation of the processors 202. For example, the memories 204 may store software code including commands for performing some or all of the processes controlled by the processors 202 or for performing the processes and / or methods described in this disclosure. In this document, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each of transceivers 206 may include a transmitter and / or a receiver. Transceivers 206 may be used interchangeably with RF units. In this invention, a wireless device may represent a communication modem / circuit / chip.

[0092] The hardware elements of wireless devices 100 and 200 will be described in more detail below. One or more protocol layers may be implemented by, but are not limited to, one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the functions, procedures, proposals, and / or methods disclosed in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this disclosure. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this disclosure and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) from one or more transceivers 106 and 206 and acquire PDUs, SDUs, messages, control information, data, or information in accordance with the functions, processes, proposals, and / or methods disclosed in this disclosure.

[0093] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field-programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The functions, processes, proposals, and / or methods disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to perform the functions, processes, proposals, and / or methods disclosed in this disclosure may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 for drive by one or more processors 102 and 202. The functions, processes, proposals, and / or methods disclosed in this disclosure may be implemented using firmware or software in the form of code, commands, and / or command sets.

[0094] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories 104 and 204 may be configured with read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104 and 204 may be located internally and / or externally to one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0095] One or more transceivers 106 and 206 can transmit user data, control information, and / or radio signals / channels as mentioned in the methods and / or operation flowcharts of this disclosure to one or more other devices. One or more transceivers 106 and 206 can receive user data, control information, and / or radio signals / channels as mentioned in the functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure from one or more other devices. For example, one or more transceivers 106 and 206 can be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 can perform control to enable one or more transceivers 106 and 206 to transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 can perform control to enable one or more transceivers 106 and 206 to receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels mentioned in the functional, process, proposal, method, and / or operational flowcharts disclosed in this disclosure via one or more antennas 108 and 208. In this disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc., from RF band signals to baseband signals for processing by one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc., processed by one or more processors 102 and 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, transceivers 106 and 206, under the control of processors 102 and 202, may upconvert OFDM baseband signals to a carrier frequency using their (analog) oscillators and / or filters and transmit the upconverted OFDM signal at the carrier frequency. Transceivers 106 and 206 may receive OFDM signals at the carrier frequency and, under the control of processors 102 and 202, downconvert OFDM signals to OFDM baseband signals using their (analog) oscillators and / or filters.

[0096] In the implementations of this disclosure, the UE can be used as a transmitting device in the uplink (UL) and a receiving device in the downlink (DL). In the implementations of this disclosure, the BS can be used as a receiving device in the UL and a transmitting device in the DL. Hereinafter, for ease of description, unless otherwise stated or described, it is generally assumed that the first wireless device 100 is used as the UE and the second wireless device 200 is used as the BS. For example, a processor 102 connected to, installed on, or started in the first wireless device 100 can be configured to perform UE actions according to the implementations of this disclosure or to control the transceiver 106 to perform UE actions according to the implementations of this disclosure. A processor 202 connected to, installed on, or started in the second wireless device 200 can be configured to perform BS actions according to the implementations of this disclosure or to control the transceiver 206 to perform BS actions according to the implementations of this disclosure.

[0097] Figure 3 Another example of a wireless device that can implement the present invention is illustrated. The wireless device can be implemented in various forms depending on the use case / service (see reference). Figure 1 ).

[0098] Reference Figure 3 Wireless devices 100 and 200 can correspond to Figure 2 The wireless devices 100 and 200 can be configured from various elements, components, units / parts, and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include... Figure 2 One or more processors 102 and 202 and / or Figure 2 One or more memories 104 and 204. For example, transceiver 114 may include... Figure 2 One or more transceivers 106 and 206 and / or Figure 2 One or more antennas 108 and 208. Control unit 120 is electrically connected to communication unit 110, memory unit 130, and add-on components 140, and controls the overall operation of the wireless device. For example, control unit 120 can control the electrical / mechanical operation of the wireless device based on programs / code / commands / information stored in memory unit 130. Control unit 120 can transmit information stored in memory unit 130 to an external source (e.g., other communication devices) via communication unit 110 through a wireless / wired interface, or store information received from an external source (e.g., other communication devices) via wireless / wired interface in memory unit 130 via communication unit 110.

[0099] The add-on component 140 can be configured differently depending on the type of wireless device. For example, the add-on component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit (e.g., an audio I / O port, a video I / O port), a drive unit, and a computing unit. The wireless device can be, but is not limited to, a robot ( Figure 1 100a), vehicles ( Figure 1 100b-1 and 100b-2), XR device ( Figure 1 100c), handheld device ( Figure 1 100d), home appliances ( Figure 1 100e), IoT devices ( Figure 1 100f), digital broadcasting terminals, holographic devices, public safety devices, MTC devices, medical devices, Fintech devices (or financial devices), security devices, climate / environment devices, AI servers / devices ( Figure 1 400), BS ( Figure 1 This can be achieved through methods such as 200 network nodes, etc. Wireless devices can be used in mobile or fixed locations depending on the use case / service.

[0100] exist Figure 3 In wireless devices 100 and 200, the various elements, components, units / parts, and / or modules as a whole can be connected to each other via a wired interface, or at least a portion thereof can be wirelessly connected via communication unit 110. For example, in each of wireless devices 100 and 200, control unit 120 and communication unit 110 can be wired connected, and control unit 120 and first units (e.g., 130 and 140) can be wirelessly connected via communication unit 110. Each element, component, unit / part, and / or module within wireless devices 100 and 200 may also include one or more elements. For example, control unit 120 may be configured by a group of one or more processors. As an example, control unit 120 may be configured by a group of communication control processors, application processors, electronic control units (ECUs), graphics processing units, and memory control processors. As another example, memory unit 130 may be configured by random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), flash memory, volatile memory, non-volatile memory, and / or combinations thereof.

[0101] Figure 4 An example of a protocol stack in a 3GPP-based wireless communication system is shown.

[0102] Specifically, Figure 4 (a) illustrates an example of the user plane protocol stack for the radio interface between the UE and the base station (BS), and Figure 4(b) illustrates an example of the radio interface control plane protocol stack between the UE and the BS. The control plane refers to the path through which control messages for calls managed by the UE and the network are transmitted. The user plane refers to the path through which data generated in the application layer (e.g., voice data or Internet packet data) is transmitted. See also... Figure 4 (a) The user plane protocol stack can be divided into a first layer (layer 1) (i.e., the physical (PHY) layer) and a second layer (layer 2). See [reference] Figure 4 (b) The control plane protocol stack can be divided into Layer 1 (i.e., the PHY layer), Layer 2, Layer 3 (e.g., the Radio Resource Control (RRC) layer) and the Non-Access Layer (NAS). Layers 1, 2, and 3 are referred to as the Access Layer (AS).

[0103] The NAS control protocol terminates at the Access Management Function (AMF) on the network side and performs functions such as authentication, mobility management, and security control.

[0104] In 3GPP LTE systems, Layer 2 is separated into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP). In 3GPP New Radio (NR) systems, Layer 2 is separated into the following sublayers: MAC, RLC, PDCP, and SDAP. The PHY layer provides transport channels to the MAC sublayer, the MAC sublayer provides logical channels to the RLC sublayer, the RLC sublayer provides RLC channels to the PDCP sublayer, and the PDCP sublayer provides radio bearers to the SDAP sublayer. The SDAP sublayer provides Quality of Service (QoS) streams to the 5G core network.

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

[0106] In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcasting system information related to AS and NAS; paging initiated by the 5G core (5GC) or NG-RAN; establishment, maintenance, and release of RRC connections between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers (SRB) and data radio bearers (DRB); mobility functions (including: handover and context transfer; UE cell selection and reselection and control of cell selection and reselection; inter-RAT mobility); QoS management functions; control of UE measurement reports and reports; detection and recovery of radio link failures; and NAS message transmission from UE to NAS and from NAS to UE.

[0107] In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression: ROHC only; user data transmission; reordering and deduplication detection; in-order delivery; PDCP PDU routing (in the case of separate bearers); PDCP SDU retransmission; encryption, decryption, and integrity protection; PDCP SDU discarding; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; and PDCP PDU duplication and lower-layer duplication discarding indication. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; encryption, decryption, and integrity protection; control plane data transmission; reordering and deduplication detection; in-order delivery; and PDCP PDU duplication and lower-layer duplication discarding indication.

[0108] The RLC sublayer supports three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM). RLC configuration is per logical channel and is independent of parameter sets and / or transmission duration. In 3GPP NR systems, the main services and functions of the RLC sublayer depend on the transmission mode and include: transmission of upper-layer PDUs; sequence numbering 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 discarding (AM and UM); RLC reconstruction; and protocol error detection (AM only).

[0109] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing / demultiplexing MAC SDUs belonging to one or different logical channels to / from the transport channel to the physical layer / from the physical layer to transport blocks (TBs); scheduling information reporting; error correction via HARQ (one HARQ entity per cell in the case of carrier aggregation (CA); priority handling between UEs via dynamic scheduling; priority handling between logical channels of a UE via logical channel priority ordering; and padding. A single MAC entity can support multiple parameter sets, transmission timings, and cells. Mapping restrictions in logical channel priority ordering control which parameter set(s), cell(s), and transmission timing(s) a logical channel(s) can use. MAC provides different types of data transmission services. To accommodate different types of data transmission services, various types of logical channels are defined, i.e., each logical channel supports the transmission of a specific type of information. Each logical channel type is defined by the type of information being transmitted. Logical channels are divided into two groups: control channels and traffic channels. Control channels are used only for the transmission of control plane information, and traffic channels are used only for the transmission of user plane information. The Broadcast Control Channel (BCCH) is a downlink logical channel used for broadcasting system control information. The Paging Control Channel (PCCH) is a downlink logical channel that transmits paging information, system information change notifications, and indications of ongoing PWS broadcasts. The Common Control Channel (CCCH) is a logical channel used by UEs without an RRC connection to the network to transmit control information. The Dedicated Control Channel (DCCH) is a point-to-point bidirectional logical channel used by UEs with an RRC connection to transmit dedicated control information between the UE and the network. The Dedicated Traffic Channel (DTCH) is a point-to-point logical channel dedicated to a single UE for transmitting user information. The DTCH can exist in both the uplink and downlink. In the downlink, the following connections exist between logical channels and transport channels: BCCH can be mapped to BCH; BCCH can be mapped to Downlink Shared Channel (DL-SCH); PCCH can be mapped to PCH; CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In the uplink, there are the following connections between logical channels and transport channels: CCCH can be mapped to the uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

[0110] Figure 5 An example of a frame structure in a 3GPP-based wireless communication system is shown.

[0111] Figure 5The frame structure shown is merely exemplary, and the number of subframes, the number of time slots, and / or the number of symbols in a frame can vary. In 3GPP-based wireless communication systems, OFDM parameter sets (e.g., subcarrier spacing (SCS), transmission time interval (TTI) durations) can be configured differently across multiple cells aggregated for a UE. For example, if the UE is configured with different SCSs for cells aggregated for cell aggregation, the (absolute time) duration of time resources (e.g., subframes, time slots, or TTIs) comprising the same number of symbols can be different among the aggregated cells. In this document, symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or Discrete Fourier Transform-Extended-OFDM (DFT-s-OFDM) symbols).

[0112] Reference Figure 5 Downlink and uplink transmissions are organized into frames. Each frame has a T f =10ms duration. Each frame is divided into two half-frames, each half-frame having a duration of 5ms. Each half-frame consists of 5 subframes, where the duration T of each subframe is... sf It is 1ms. Each subframe is divided into time slots, and the number of time slots in a subframe depends on the subcarrier spacing. Each time slot includes 14 or 12 OFDM symbols based on the cyclic prefix (CP). In normal CP, each time slot includes 14 OFDM symbols, and in extended CP, each time slot includes 12 OFDM symbols. The parameter set is based on an exponentially scalable subcarrier spacing Δf = 2. u *15kHz. The following table shows the values ​​based on the subcarrier spacing Δf = 2. u *Number of OFDM symbols per slot at 15kHz, number of slots per frame, and number of slots per subframe for normal CP.

[0113] [Table 1]

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

[0115] The following table shows the subcarrier spacing Δf = 2 u *Number of OFDM symbols per slot at 15kHz, number of slots per frame, and number of slots per subframe for extended CP.

[0116] [Table 2]

[0117] u <![CDATA[N slob symb ]]> <![CDATA[N frame.u slot ]]> <![CDATA[N subframe,u slot ]]> 2 12 40 4

[0118] A time slot comprises multiple symbols (e.g., 14 or 12 symbols) in the time domain. For each parameter set (e.g., subcarrier spacing) and carrier, a Common Resource Block (CRB) is generated from the common resource block (CRB) indicated by higher-layer signaling (e.g., Radio Resource Control (RRC) signaling). start,u grid Initially, N was defined. size,u grid,x *N RB sc Subcarriers and N subframe,u symb A resource grid of N OFDM symbols, where N size,u grid,x N represents the number of resource blocks in the resource grid, where the subscript x represents the downlink DL and the uplink UL. RB sc N is the number of subcarriers in each resource block. In 3GPP-based wireless communication systems, N... RB sc Typically, it is 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL), there exists a resource grid. The carrier bandwidth N for the subcarrier spacing configuration u is... size,u grid 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 a complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l representing the symbol position relative to a reference point in the time domain. In 3GPP-based wireless communication systems, a resource block is defined by 12 consecutive subcarriers in the frequency domain.

[0119] In 3GPP NR systems, resource blocks are classified into CRBs and Physical Resource Blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain based on subcarrier spacing configuration u. The center of subcarrier 0 in CRB 0 for subcarrier spacing configuration u coincides with "point A," which serves as the common reference point for the resource block grid. In 3GPP NR systems, PRBs are defined within the Bandwidth Part (BWP) and numbered from 0 to N. size BWP,i -1 is the number, where i is the number of the bandwidth section. The physical resource block n within bandwidth section i... PRB With public resource block n CRB The relationship between n is as follows: PRB =n CRB +N size BWP,i , where N size BWP,iA BWP is a common resource block relative to CRB 0. A BWP comprises multiple consecutive resource blocks. A carrier can include up to N (e.g., 5) BWPs. A UE can be configured with one or more BWPs on a given component carrier. Only one BWP can be active at a time among those configured for the UE. The active BWP is defined within the UE's operating bandwidth of the cell.

[0120] The NR band can be defined as two types of frequency ranges, FR1 and FR2. FR2 can also be referred to as millimeter wave (mmW). The frequency range in which NR can operate is shown as described in Table 3.

[0121] [Table 3]

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

[0123] Figure 6 An example of a data flow in a 3GPP NR system is shown.

[0124] exist Figure 6 In this code, "RB" represents a radio bearer, and "H" represents 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 sent / received to / from external devices via the PHY layer using radio resources. MAC PDUs arrive at the PHY layer in the form of transport blocks.

[0125] At the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to the Physical Uplink Shared Channel (PUSCH) and Physical Random Access Channel (PRACH), respectively, and the downlink transport channels DL-SCH, BCH, and PCH are mapped to the Physical Downlink Shared Channel (PDSCH), Physical Broadcast Channel (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 UE transmits MAC PDUs related to UL-SCH via PUSCH based on UL grant, and the BS transmits MAC PDUs related to DL-SCH via PDSCH based on DL assignment.

[0126] To transmit the data elements of this disclosure on the UL-SCH, the UE must have uplink resources available to the UE. To receive the data elements of this disclosure on the DL-SCH, the UE must have downlink resources available to the UE. Resource allocation includes time-domain resource allocation and frequency-domain resource allocation. In this disclosure, uplink resource allocation is also referred to as uplink grant, and downlink resource allocation is also referred to as downlink assignment. Uplink grant is either dynamically received by the UE on the PDCCH in a random access response or semi-persistently configured to the UE by RRC. Downlink assignment is either dynamically received by the UE on the PDCCH or semi-persistently configured to the UE by RRC signaling from the BS.

[0127] In UL, the BS can dynamically allocate resources to the UE via the Cell Radio Network Temporary Identifier (C-RNTI) on the PDCCH. The UE constantly monitors the PDCCH to find possible grants for uplink transmissions when its downlink reception is enabled (when configured by Discontinuous Receive (DRX) control activity). Furthermore, by configuring grants, the BS can allocate uplink resources for the initial HARQ transmission to the UE. Two types of configured uplink grants are defined: Type 1 and Type 2. For Type 1, the RRC directly provides the configured uplink grants (including periodicity). For Type 2, the RRC defines the periodicity of the configured uplink grants, and the PDCCH addressed to the configured Scheduling RNTI (CS-RNTI) can signal and activate, or deactivate, the configured uplink grant; that is, the PDCCH addressing to the CS-RNTI indicates that the uplink grant can be implicitly reused according to the periodicity defined by the RRC until deactivation.

[0128] In DL, the BS can dynamically allocate resources to the UE via C-RNTI on the PDCCH. The UE constantly monitors the PDCCH to find possible assignments when its downlink reception is enabled (configuration activity is controlled by DRX). Additionally, through semi-persistent scheduling (SPS), the BS can allocate downlink resources to the UE for initial HARQ transmissions: the RRC defines the periodicity of configured downlink assignments, and the PDCCH addressed to the CS-RNTI can signal and activate, or deactivate, the configured downlink assignment. In other words, the PDCCH addressing the CS-RNTI implicitly reuses downlink assignments according to the periodicity defined by the RRC until deactivation.

[0129] Resource allocation via PDCCH (i.e., resource allocation via DCI)

[0130] The PDCCH can be used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH. The downlink control information (DCI) on the PDCCH includes: downlink assignment containing at least the modulation and coding scheme (MCS) associated with the DL-SCH (e.g., Modulation and Coding Scheme (MCS) Index IMCS), resource allocation, and hybrid ARQ information; or uplink scheduling authorization containing at least the modulation and coding scheme, resource allocation, and hybrid ARQ information associated with the UL-SCH. The size and purpose of the DCI carried by a PDCCH vary depending on the DCI format. For example, in a 3GPP NR system, DCI format 0_0 or DCI format 0_1 ​​is used for scheduling PUSCHs within a cell, and DCI format 1_0 or DCI format 1_1 is used for scheduling PDSCHs within a cell.

[0131] Figure 7 Examples of PDSCH time domain resource allocation via PDCCH and PUSCH time resource allocation via PDCCH are shown.

[0132] The downlink control information (DCI) carried by the PDCCH for scheduling PDSCH or PUSCH includes the value m of row index m+1 of the allocation table for PDSCH or PUSCH. A predefined default PDSCH time domain allocation A, B, or C is applied as the PDSCH allocation table, or the pdsch-TimeDomainAllocationList configured by RRC is applied as the PDSCH allocation table. Similarly, a predefined default PUSCH time domain allocation A is applied as the PUSCH allocation table, or the pusch-TimeDomainAllocationList configured by RRC is applied as the PUSCH allocation table. Which PDSCH time domain resource allocation configuration and which PUSCH time domain resource allocation table is applied is determined according to fixed / predefined rules (e.g., Table 5.1.2.1.1-1 in 3GPP TS 38.214v15.3.0, Table 6.1.2.1.1-1 in 3GPP TS 38.214v15.3.0).

[0133] Each index row in the PDSCH time-domain allocation configuration defines a slot offset K0, a start and length indicator SLIV, or directly defines the start symbol S and allocation length L, as well as the PDSCH mapping type assumed in PDSCH reception. Each index row in the PUSCH time-domain allocation configuration defines a slot offset K2, a start and length indicator SLIV, or directly defines the start symbol S and allocation length L, as well as the PUSCH mapping type assumed in PUSCH reception. K0 for PDSCH or K2 for PUSCH is the timing difference between a slot with a PDCCH and a slot with a corresponding PDSCH or PUSCH. SLIV is a joint indication of the start symbol S relative to the start of the slot with the PDSCH or PUSCH and the number L of consecutive symbols counted from symbol S. For PDSCH / PUSCH mapping types, there are two mapping types: one is mapping type A, where the demodulation reference signal (DMRS) is located in the 3rd or 4th symbol of the time slot according to the RRC signaling; and the other is mapping type B, where the DMRS is located in the first assigned symbol.

[0134] The scheduling DCI includes a frequency domain resource assignment field that provides assignment information about resource blocks used for PDSCH or PUSCH. For example, the frequency domain resource assignment field can provide the UE with information about the cell for PDSCH or PUSCH transmission, information about the bandwidth portion for PDSCH or PUSCH transmission, and information about the resource blocks for PDSCH or PUSCH transmission.

[0135] Resource allocation via RRC

[0136] As described above, in the uplink, there are two types of transmissions without dynamic grants: Configured Grant Type 1, where the uplink grant is provided by the RRC and stored as a configured grant; and Configured Grant Type 2, where the uplink grant is provided by the PDCCH, and L1 signaling indicating activation or deactivation of the configured uplink grant is stored or cleared as a configured uplink grant. Type 1 and Type 2 are configured by the RRC for each serving cell and each BWP. Multiple configurations are only active simultaneously on different serving cells. For Type 2, activation and deactivation between serving cells are independent. For the same serving cell, the MAC entity is configured as either Type 1 or Type 2.

[0137] When the configured authorization type 1 is configured, the UE is provided with at least the following parameters via RRC signaling from the BS:

[0138] -cs-RNTI, which is CS-RNTI for retransmission;

[0139] - Periodicity, which provides periodicity for configured license type 1;

[0140] -timeDomainOffset represents the offset of the resource in the time domain relative to SFN=0;

[0141] The -timeDomainAllocation value m provides a row index m+1 pointing to the allocation table, indicating the combination of the start symbol S, length L, and PUSCH mapping type;

[0142] -frequencyDomainAllocation provides frequency domain resource allocation; and

[0143] -mcsAndTBS provides the IMCS representing the modulation order, target code rate, and transport block size. When the RRC configures a configured license type 1 for the serving cell, the UE stores the uplink license provided by the RRC as a configured uplink license for the indicated serving cell, and initializes or reinitializes the configured uplink license to start in the symbol according to timeDomainOffset and S (derived from SLIV), and reappears periodically. After configuring uplink grant for the configured grant type 1, the UE considers the uplink grant to be associated with each symbol, where: [(SFN*numberOfSlotsPerFrame(numberOfSymbolsPerSlot)+(number of slots in the frame × numberOfSymbolsPerSlot)+number of symbols in the slot]=(timeDomainOffset*numberOfSymbolsPerSlot+S+N*periodicity)modulo(1024*numberOfSlotsPerFrame*numberOfSymbolsPerSlot), for all N>=0.

[0144] When the configured authorization type 2 is configured, at least the following parameters are provided to the UE via RRC signaling from the BS:

[0145] -cs-RNTI, which is CS-RNTI for activation, deactivation, and retransmission; and

[0146] - Periodicity, which provides periodicity for configured license type 2. The uplink license is actually provided to the UE via PDCCH (addressed to CS-RNTI). After configuring uplink license for configured license type 2, the UE considers the uplink license to be associated with each symbol, where: [(SFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot) + (number of slots in the frame * numberOfSymbolsPerSlot) + number of symbols in the slot] = [(SFN start time *numberOfSlotsPerFrame*numberOfSymbolsPerSlot+slot start time *numberOfSymbolsPerSlot+symbol start time )+N*periodic]modulo(1024×numberOfSlotsPerFrame*numberOfSymbolsPerSlot), for all N>=0, where SFN start time slot start time and symbol start time These are the SFN, slot, and symbol of the first transmission opportunity of the (re)initialized PUSCH for the configured uplink link. `numberOfSlotsPerFrame` and `numberOfSymbolsPerSlot` refer to the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively.

[0147] For configured uplink grants, the HARQ process ID associated with the first symbol of the UL transmission is derived from the following equation:

[0148] HARQ process ID = [floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes

[0149] Where CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + number of slots in the frame × numberOfSymbolsPerSlot + number of symbols in the slots), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the number of consecutive slots per frame and the number of consecutive symbols per slot as specified in TS 38.211, respectively. CURRENT_symbol refers to the symbol index of the first transmission at which duplicate binding occurs. If the configured uplink grant is activated and the associated HARQ process ID is less than nrofHARQ-Processes, then a HARQ process is configured for the configured uplink grant.

[0150] For the downlink, the UE can configure semi-persistent scheduling (SPS) for each serving cell and each BWP via RRC signaling from the BS. Multiple configurations can only be active simultaneously on different serving cells. Activation and deactivation of DL SPS are independent between serving cells. For DL ​​SPS, DL assignment is provided to the UE via PDCCH and stored or cleared based on L1 signaling indicating SPS activation or deactivation. When configuring SPS, the following parameters are provided to the UE via RRC signaling from the BS:

[0151] -cs-RNTI, which is CS-RNTI for activation, deactivation and retransmission;

[0152] -nrofHARQ-Processes: This specifies the number of HARQ processes configured for SPS;

[0153] - Periodicity, which provides periodicity for downlink assignment for SPS configuration.

[0154] When the SPS is released by the upper layer, all corresponding configurations should be released as well.

[0155] After configuring downlink assignment for SPS, the UE considers the Nth downlink assignment to occur in the following time slots: (numberOfSlotsPerFrame*SFN + number of time slots in the frame) = [(numberOfSlotsPerFrame*SFN] start time +slot start time )+N*periodic*numberOfSlotsPerFrame / 10]modulo(1024*numberOfSlotsPerFrame), where SFN starttim e and slot start time These are the SFN and time slot of the first transmission of the (re)initialized PDSCH, which is configured for downlink assignment.

[0156] For the configured downlink assignment, the HARQ process ID associated with the time slot where the DL transmission begins is derived from the following equation:

[0157] HARQ process ID = [floor(CURRENT_slot × 10 / (numberOfSlotsPerFrame × periodicity))]modulo nrofHARQ-Processes

[0158] Wherein, CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + number of slots in the frame], and numberOfSlotsPerFrame refers to the number of consecutive slots per frame as specified in TS 38.211.

[0159] If the Cyclic Redundancy Check (CRC) for the corresponding DCI format is scrambled by the CS-RNTI provided by the RRC parameter cs-RNTI and the New Data Indicator field for the enabled transport block is set to 0, the UE verifies the DL SPS assigned PDCCH or the configured UL license type 2 PDCCH for schedule activation or schedule release. Verification of the DCI format is implemented if all fields for the DCI format are set according to Table 4 or Table 5. Table 4 shows the specific fields for PDCCH verification for DL ​​SPS and UL license type 2 schedule activation, and Table 5 shows the specific fields for PDCCH verification for DL ​​SPS and UL license type 2 schedule release.

[0160] [Table 4]

[0161]

[0162] [Table 5]

[0163]

[0164]

[0165] The actual DL assignment and actual UL grant, along with the corresponding modulation and coding scheme, are provided by the resource assignment fields (e.g., time-domain resource assignment fields providing the time-domain resource assignment value m, frequency-domain resource assignment fields providing frequency resource block allocation, and modulation and coding scheme fields) in the DCI format carried by the DL SPS and UL grant type 2 scheduling activation PDCCH. If authentication is implemented, the UE treats the information in the DCI format as a valid activation or release of the DL SPS or the configured UL grant type 2.

[0166] Regarding UL, the processor 102 of this disclosure can transmit (or control transceiver 106 to transmit) the data units of this disclosure based on the UL authorization available to the UE. The processor 202 of this disclosure can receive (or control transceiver 206 to receive) the data units of this disclosure based on the UL authorization available to the UE.

[0167] For DL, the processor 102 of this disclosure can receive (or control transceiver 106 to receive) the DL data of this disclosure based on the DL assignment available to the UE. The processor 202 of this disclosure can send (or control transceiver 206 to send) the DL data of this disclosure based on the DL assignment available to the UE.

[0168] The data units of this disclosure are processed by the physical layer at the transmitting side before being transmitted via the radio interface, and the radio signals carrying the data units of this disclosure are processed by the physical layer at the receiving side. For example, a MAC PDU including a PDCP PDU according to this disclosure can be processed by the physical layer as follows.

[0169] Figure 8 An example of physical layer processing at the transmitting side is shown.

[0170] The following tables show the mapping of transport channels (TrCH) and control information to their corresponding physical channels. Specifically, Table 6 specifies the mapping of uplink transport channels to their corresponding physical channels, Table 7 specifies the mapping of uplink control channel information to their corresponding physical channels, Table 8 specifies the mapping of downlink transport channels to their corresponding physical channels, and Table 9 specifies the mapping of downlink control channel information to their corresponding physical channels.

[0171] [Table 6]

[0172] TrCH physical channel UL-SCH PUSCH RACH PRACH

[0173] [Table 7]

[0174] Control Information physical channel UCI PUCCH, PUSCH

[0175] [Table 8]

[0176]

[0177]

[0178] [Table 9]

[0179] Control Information physical channel DCI PDCCH

[0180] <encoding>

[0181] Data and control flows from / to the MAC layer are encoded to provide transmission and control services via the radio transmission link in the PHY layer. For example, transport blocks from the MAC layer are encoded into codewords at the transmitting side. The channel coding scheme is a combination of error detection, error correction, rate matching, interleaving, and mapping to / from the physical channel of transport channel or control information.

[0182] In the 3GPP NR system, the following channel coding schemes are used for different types of TrCH and different control information types.

[0183] [Table 10]

[0184]

[0185] [Table 11]

[0186]

[0187] For transmissions of DL transport blocks (i.e., DL MAC PDUs) or UL transport blocks (i.e., UL MAC PDUs), a transport block CRC sequence is appended to provide error detection for the receiving side. In 3GPP NR systems, communication devices use low-density parity-check (LDPC) codes when encoding / decoding UL-SCH and DL-SCH. 3GPP NR systems support two LDPC base maps (i.e., two LDPC base matrices): an LDPC base optimized for small transport blocks. Figure 1 and LDPC base optimized for larger transport blocks Figure 2 The LDPC base is selected based on the transport block size and code rate R. Figure 1 or LDPC base Figure 2 The code rate R is indicated by the Modulation and Coding Scheme (MCS) index IMCS. The MCS index is dynamically provided to the UE via the PDCCH that schedules the PUSCH or PDSCH, via the PDCCH that activates or (re)initializes the UL-configured license 2 or DL ​​SPS, or via RRC signaling associated with UL-configured license type 1. If the CRC-attached transport block is larger than the maximum block size for the selected LDPC base map, the CRC-attached transport block can be segmented into blocks, and an additional CRC sequence is attached to each block. For the LDPC base map... Figure 1and LDPC basis Figure 2 The maximum block sizes are 8448 bits and 3480 bits, respectively. If the CRC-attached transport block is no larger than the maximum block size of the selected LDPC base map, the CRC-attached transport block is encoded using the selected LDPC base map. Each block of the transport block is encoded using the selected LDPC base map. The LDPC-encoded blocks are then rate-matched individually. Block concatenation is performed to create codewords for transmission on PDSCH or PUSCH. For PDSCH, a maximum of two codewords (i.e., a maximum of two transport blocks) can be transmitted simultaneously on PDSCH. PUSCH can be used for the transmission of UL-SCH data and Layer 1 / 2 control information. Although in Figure 8 Although not shown in the diagram, the layer 1 / 2 control information can be multiplexed with the codewords for UL-SCH data.

[0188] <Scrambling and Modulation>

[0189] The bits of the codeword are scrambled and modulated to generate blocks of complex-valued modulated symbols.

[0190] <Layer Mapping>

[0191] The complex-valued modulation symbols of a codeword are mapped to one or more Multiple-Input Multiple-Output (MIMO) layers. A codeword can be mapped to a maximum of four layers. A PDSCH can carry two codewords, and therefore can support up to eight layers of transmission. A PUSCH supports a single codeword, and therefore can support up to four layers of transmission.

[0192] <Transform Precoding>

[0193] The DL transmission waveform is a regular OFDM using a cyclic prefix (CP). For DL, no transform precoding (in other words, Discrete Fourier Transform (DFT)) is applied.

[0194] UL transmission waveforms are regular OFDM using CP, where transform precoding, which performs DFT extension, can be disabled or enabled. In 3GPP NR systems, transform precoding can be selectively applied to UL waveforms if enabled. Transform precoding extends UL data in a special way to reduce the peak-to-average power ratio (PAPR) of the waveform. Transform precoding is a form of DFT. In other words, 3GPP NR systems support two options for UL waveforms: CP-OFDM (the same as DL waveforms) and DFT-s-OFDM. Whether the UE must use CP-OFDM or DFT-s-OFDM is configured by the BS via RRC parameters.

[0195] Subcarrier mapping

[0196] Layers are mapped to antenna ports. In DL, for the mapping from layers to antenna ports, transparent (non-codebook-based) mapping is supported, and how beamforming or MIMO precoding is performed is transparent to the UE. In UL, for the mapping from layers to antenna ports, both non-codebook-based mapping and codebook-based mapping are supported.

[0197] For each antenna port (i.e., layer) used for the transmission of a physical channel (e.g., PDSCH, PUSCH), complex-valued modulation symbols are mapped to subcarriers in the resource blocks allocated to the physical channel.

[0198] <OFDM modulation>

[0199] The communication device on the transmitting side generates a time-continuous OFDM baseband signal on subcarrier spacing configuration u and antenna port p for OFDM symbol l in the TTI for the physical channel by adding a cyclic prefix (CP) and performing an IFFT. For example, for each OFDM symbol, the communication device on the transmitting side can perform an inverse fast Fourier transform (IFFT) on the complex-valued modulation symbols mapped to the resource blocks in the corresponding OFDM symbol, and add a CP to the IFFT'ed signal to generate the OFDM baseband signal.

[0200] <Up-conversion>

[0201] The communication device on the transmitting side up-converts the OFDM baseband signal for antenna port p, subcarrier spacing configuration u, and OFDM symbol l to the carrier frequency f0 of the cell assigned to the physical channel.

[0202] Figure 2 The processors 102 and 202 in [device name] can be configured to perform encoding, scrambling, modulation, layer mapping, transform precoding (for UL), subcarrier mapping, and OFDM modulation. The processors 102 and 202 can control the transceivers 106 and 206 connected to the processors 102 and 202 to up-convert the OFDM baseband signal to the carrier frequency to generate a radio frequency (RF) signal. The RF signal is transmitted to an external device through antennas 108 and 208.

[0203] Figure 9 An example of physical layer processing on the receiving side is illustrated.

[0204] The physical layer processing on the receiving side is basically the inverse processing of the physical layer processing on the transmitting side.

[0205] <Down-conversion>

[0206] The communication device on the receiving side receives an RF signal at the carrier frequency through an antenna. The transceivers 106 and 206 that receive the RF signal at the carrier frequency down-convert the carrier frequency of the RF signal to the baseband to obtain an OFDM baseband signal.

[0207] <OFDM Demodulation>

[0208] At the receiving side, the communication device obtains complex-valued modulation symbols via CP separation and FFT. For example, for each OFDM symbol, the communication device at the receiving side removes the CP from the OFDM baseband signal and performs FFT on the OFDM baseband signal with the CP removed to obtain the complex-valued modulation symbols for antenna port p, subcarrier spacing u, and OFDM symbol l.

[0209] <Subcarrier Demapping>

[0210] Subcarrier demapping is performed on the complex-valued modulation symbols to obtain the complex-valued modulation symbols of the corresponding physical channel. For example, processor 102 can obtain the complex-valued modulation symbols mapped to the subcarriers belonging to the PDSCH from the complex-valued modulation symbols received in the bandwidth part. For another example, processor 202 can obtain the complex-valued modulation symbols mapped to the subcarriers belonging to the PUSCH from the complex-valued modulation symbols received in the bandwidth part.

[0211] <Transform Demaprecoding>

[0212] If transform precoding has been enabled for the uplink physical channel, transform demaprecoding (e.g., IDFT) is performed on the complex-valued modulation symbols of the uplink physical channel. For the downlink physical channel and the uplink physical channel with transform precoding disabled, transform demaprecoding is not performed.

[0213] <Layer Demapping>

[0214] The complex-valued modulation symbols are demapped into one or two codewords.

[0215] <Demodulation and Descrambling>

[0216] The complex-valued modulation symbols of the codeword are demodulated and descrambled into the bits of the codeword.

[0217] <Decoding>

[0218] The codeword is decoded into a transport block. For UL-SCH and DL-SCH, the LDPC base is selected according to the size of the transport block and the code rate R Figure 1 or LDPC base Figure 2A codeword may include one or more coded blocks. Each coded block is decoded using the selected LDPC base graph into either a CRC-attached code block or a CRC-attached transport block. If code block segmentation is performed on the CRC-attached transport block at the transmitting side, the CRC sequence is removed from each of the CRC-attached code blocks to obtain the code block. The code blocks are concatenated into a CRC-attached transport block. The transport block CRC sequence is removed from the CRC-attached transport block to obtain the transport block. The transport block is then passed to the MAC layer.

[0219] In the physical layer processing at the transmitting and receiving sides described above, the time-domain and frequency-domain resources (e.g., OFDM symbols, subcarriers, carrier frequencies) related to subcarrier mapping, OFDM modulation, and frequency up-conversion / down-conversion can be determined based on resource allocation (e.g., UL licensing, DL assignment).

[0220] For uplink data transmission, the processor 102 of this disclosure can apply (or control transceiver 106 to) the aforementioned physical layer processing on the transmitting side to the data unit of this disclosure to wirelessly transmit the data unit. For downlink data reception, the processor 102 of this disclosure can apply (or control transceiver 106 to) the aforementioned physical layer processing on the receiving side to the received radio signal to obtain the data unit of this disclosure.

[0221] For downlink data transmission, the processor 202 of this disclosure can apply the aforementioned physical layer processing on the transmitting side (or control the transceiver 206 to apply it) to the data unit of this disclosure to wirelessly transmit the data unit. For uplink data reception, the processor 202 of this disclosure can apply the aforementioned physical layer processing on the receiving side (or control the transceiver 206 to apply it) to the received radio signal to obtain the data unit of this disclosure.

[0222] Figure 10 The operation of a wireless device based on an implementation of this disclosure is illustrated.

[0223] Figure 2 The first wireless device 100 can generate first information / signal according to the functions, processes and / or methods described in this disclosure, and then wirelessly transmit a radio signal including the first information / signal to... Figure 2The second wireless device 200 (S10). The first information / signal may include data elements of this disclosure (e.g., PDU, SDU, RRC message). The first wireless device 100 may receive a radio signal including the second information / signal from the second wireless device 200 (S30), and then perform an operation based on or according to the second information / signal (S50). The second information / signal may be transmitted from the second wireless device 200 to the first wireless device 100 in response to the first information / signal. The second information / signal may include data elements of this disclosure (e.g., PDU, SDU, RRC message). The first information / signal may include content request information, and the second information / signal may include content specifically for the purposes of the first wireless device 100. Some examples of operations specifically for the purposes of wireless devices 100 and 200 will be described below.

[0224] In some scenarios, the first wireless device 100 can be Figure 1 The handheld device 100d performs the functions, processes, and / or methods described in this disclosure. The handheld device 100d can acquire information / signals input by a user (e.g., touch, text, voice, image, or video) and convert the acquired information / signals into a first information / signal. The handheld device 100d can transmit the first information / signal to a second wireless device 200 (S10). The second wireless device 200 may be... Figure 1 The second information / signal can be received from the second wireless device 200 (S30) or the BS. The handheld device 100d can receive the second information / signal from the second wireless device 200 and perform an operation based on the second information / signal (S50). For example, the handheld device 100d can output the content of the second information / signal to the user (e.g., in the form of text, voice, image, video, or haptic feedback) through its I / O unit.

[0225] In some scenarios, the first wireless device 100 may be a vehicle or an autonomous vehicle 100b performing the functions, processes, and / or methods described in this disclosure. The vehicle 100b may communicate via its communication unit (e.g., Figure 3The communication unit 110 transmits signals (e.g., data and control signals) to external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers (S10) and receives signals (e.g., data and control signals) from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers (S30). The vehicle 100b may include a drive unit that enables the vehicle 100b to travel on a road. The drive unit of the vehicle 100b may include an engine, motor, powertrain, wheels, brakes, steering mechanism, etc. The vehicle 100b may include sensor units for acquiring vehicle status, surrounding environment information, user information, etc. The vehicle 100b may generate a first information / signal and transmit it to a second wireless device 200 (S10). The first information / signal may include vehicle status information, surrounding environment information, user information, etc. The vehicle 100b may receive a second information / signal from the second wireless device 200 (S30). The second information / signal may include vehicle status information, surrounding environment information, user information, etc. Vehicle 100b can drive, stop, or adjust its speed on the road based on the second information / signal (S50). For example, vehicle 100b can receive the second information / signal, including map data, traffic information data, etc., from an external server (S30). Vehicle 100b can generate an autonomous driving path and driving plan based on the second information / signal, and can move along the autonomous driving path according to the driving plan (e.g., speed / direction control) (S50). For another example, the control unit or processor of vehicle 100b can generate a virtual object based on map information, traffic information, and vehicle location information obtained through the GPS sensor of vehicle 100b, and the I / O unit 140 of vehicle 100b can display the generated virtual object in a window of vehicle 100b (S50).

[0226] In some scenarios, the first wireless device 100 can be Figure 1 The XR device 100c performs the functions, processes, and / or methods described in this disclosure. The XR device 100c can communicate via its communication unit (e.g., Figure 3The communication unit 110 transmits signals (e.g., media data and control signals) to external devices such as other wireless devices, handheld devices, or media servers (S10) and receives signals (e.g., media data and control signals) from external devices such as other wireless devices, handheld devices, or media servers (S30). For example, the XR device 100c sends content request information to another device or media server (S10) and downloads / streams content such as movies or news from another device or media server (S30), and generates, outputs, or displays XR objects (e.g., AR / VR / MR objects) through the I / O unit of the XR device based on the second information / signal received wirelessly (S50).

[0227] In some scenarios, the first wireless device 100 can be Figure 1 The robot 100a performs the functions, processes, and / or methods described in this disclosure. The robot 100a can be classified as an industrial robot, medical robot, household robot, military robot, etc., depending on its intended use or field. The robot 100a can communicate via its communication unit (e.g., Figure 3 The communication unit 110 sends signals (e.g., drive information and control signals) to external devices such as other wireless devices, other robots, or control servers (S10) and receives signals (e.g., drive information and control signals) from external devices such as other wireless devices, other robots, or control servers (S30). The second information / signal may include drive information and control signals for robot 100a. The control unit or processor of robot 100a can control the movement of robot 100a based on the second information / signal.

[0228] In some scenarios, the first wireless device 100 can be Figure 1 AI device 400. Artificial intelligence devices can be implemented through fixed or mobile devices such as televisions, projectors, smartphones, PCs, laptops, digital broadcasting terminals, tablet PCs, wearable devices, set-top boxes (STBs), radios, washing machines, refrigerators, digital signage, robots, vehicles, etc. AI device 400 can use wired / wireless communication technologies to communicate with other AI devices (e.g., Figure 1 (e.g., 100a, ..., 100f, 200 or 400) or AI servers (e.g., Figure 1 Sending wired / radio signals (e.g., sensor information, user input, learning models, or control signals) from external devices such as (e.g., 400) (S10) and from other AI devices (e.g., Figure 1 (e.g., 100a, ..., 100f, 200 or 400) or AI servers (e.g., Figure 1The AI ​​device 400 receives wired / radio signals (e.g., sensor information, user input, learning models, or control signals) from an external device such as an AI device 400 (S30). The control unit or processor of the AI ​​device 400 can determine at least one feasible operation of the AI ​​device 400 based on information determined or generated using data analysis algorithms or machine learning algorithms. The AI ​​device 400 can request external devices such as other AI devices or AI servers to provide sensor information, user input, learning models, control signals, etc. (S10). The AI ​​device 400 can receive second information / signals (e.g., sensor information, user input, learning models, or control signals) (S30), and the AI ​​device 400 can perform a predicted operation or be determined as the preferred operation among at least one feasible operation based on the second information / signals (S50).

[0229] The random access (RA) procedure of the NR system is described below.

[0230] In the NR system, two types of random access procedures are supported: the 4-step RA type using Msg1 and the 2-step RA type using MsgA.

[0231] Figure 11 and Figure 12 An example of the random access procedure supported by the NR system is shown. Both types of RA procedures support contention-based random access (CBRA) and contention-free random access (CFRA), as follows: Figure 11 As shown.

[0232] The UE selects the type of random access when initiating a random access procedure based on network configuration. More specifically, when no CFRA resources are configured, the UE uses the RSRP threshold to select between a 2-step RA type and a 4-step RA type. When CFRA resources for the 4-step RA type are configured, the UE selects the 4-step RA type. Furthermore, when CFRA resources for the 2-step RA type are configured, the UE selects the 2-step RA type.

[0233] The network does not simultaneously configure CFRA resources for 4-step RA type and 2-step RA type for the Bandwidth Part (BWP), and CFRA with 2-step RA type is only supported for handover.

[0234] The 2-step RA type MsgA includes a preamble on the PRACH and a payload on the PUSCH. After the MsgA transmission, the UE monitors for responses from the network within a configured window.

[0235] For CFRA, upon receiving a network response, such as Figure 11As shown in (d), the UE terminates the random access procedure. For CBRA, if the contention resolution is successful after receiving the network response, then as... Figure 11 As shown in (b), the UE terminates the random access procedure.

[0236] Furthermore, if a rollback instruction is received in MsgB, then as follows Figure 12 As shown, the UE performs a MsgB transmission and monitors for contention resolution. If the contention resolution is unsuccessful during the Msg3 (re)transmission, the UE returns to the MsgA transmission.

[0237] If a 2-step random access procedure is not completed after multiple MsgA transmissions, the UE can be configured to switch to a 4-step CBRA procedure.

[0238] In addition, the 2-step RA is used for the UE to send small and infrequent data when it is in the RRC_INACTIVE state.

[0239] In a 2-step RA, after the UE sends data with an RA preamble (which is called MsgA), the UE starts a RAR window (by using a timer called msgB-ResponseWindow) and monitors for a response from the network within the RAR window (which is called MsgB, where MsgB includes successRAR or fallbackRAR or both).

[0240] If a successRAR is received within the RAR window, the UE considers the transmission of data in MsgA to be successful.

[0241] Otherwise, if a fallbackRAR is received within the RAR window, the UE considers the transmission of the RA preamble in MsgA to be successful, but the transmission of the data in MsgA to be unsuccessful, and retransmits the data using the UL authorization included in the fallbackRAR.

[0242] Otherwise, if neither a success RAR nor a fallback RAR is received within the RAR window, the UE will reselect the RA preamble and retransmit the data and the reselected RA preamble in MsgA.

[0243] In addition, when the random access (RA) procedure is triggered, the UE selects a cell and the bandwidth portion (BWP) of that cell, and performs the RA procedure on the selected BWP.

[0244] If the UE receives a BWP handover indication (via PDCCH or RRC signaling) while the RA procedure is in progress, the UE can ignore the BWP handover indication or switch to the new BWP indicated by the BWP handover indication.

[0245] When the UE decides to ignore the BWP handover instruction, the UE continues to perform the RA procedure on the selected BWP. However, when the UE decides to switch to the new BWP, the UE stops the ongoing RA procedure on the selected BWP and initiates a new RA procedure on the new BWP.

[0246] The beam fault detection and recovery process is described below.

[0247] The MAC entity can be configured by the RRC of each serving cell using a beam fault recovery procedure, which is used to indicate a new SSB or CSI-RS to the serving gNB when a beam fault is detected on the serving SSB / CSI-RS. Beam faults are detected by counting beam fault instance indications from lower layers up to the MAC entity.

[0248] If beamFailureRecoveryConfig is reconfigured by the upper layer during an ongoing random access procedure for beam failure recovery of SpCell, the MAC entity will stop the ongoing random access procedure and initiate a random access procedure with the new configuration.

[0249] RRC configures the following parameters in BeamFailureRecoveryConfig and RadioLinkMonitoringConfig, which are used for beam failure detection and recovery processes.

[0250] - beamFailureInstanceMaxCount used for beam failure detection;

[0251] - beamFailureDetectionTimer for beam failure detection;

[0252] - beamFailureRecoveryTimer used for beam failure recovery process;

[0253] -rsrp-ThresholdSSB: The RSRP threshold used for beam fault recovery;

[0254] -powerRampingStep: PowerRampingStep is used for SpCell beam fault recovery;

[0255] -powerRampingStepHighPriority: PowerRampingStepHighPriority is used for Scell ​​beam fault recovery.

[0256] -preambleReceivedTargetPower: PreambleReceivedTargetPower used for SpCell beam fault recovery;

[0257] -preambleTransMax: preambleTransMax used for SpCell beam fault recovery;

[0258] -scalingFactorBI: scalingFactorBI for SpCell beam fault recovery;

[0259] -ssb-perRACH-Occasion: ssb-perRACH-Occasion used for SpCell beam fault recovery;

[0260] -ra-ResponseWindow: The time window for monitoring the response to SpCell beam fault recovery using contention-free random access preamble;

[0261] -prach-ConfigurationIndex: The prach-ConfigurationIndex used for SpCell beam fault recovery;

[0262] -ra-ssb-OccassionMaskIndex: ra-ssb-OccassionMaskIndex used for SpCell beam fault recovery;

[0263] -ra-OccasionList: ra-OccasionList used for SpCell beam fault recovery.

[0264] In addition, BFI_COUNTER (per serving cell) is a UE variable used in the beam fault detection process. Specifically, BFI_COUNTER represents a counter indicating the beam fault instance that was initially set to 0.

[0265] For each serving cell configured for beam fault detection, the MAC entity will perform the following procedure.

[0266] If a beam failure instance indication has been received from a lower layer, the MAC entity will start or restart the beamFailureDetectionTimer and increment BFI_COUNTER by 1. Furthermore, when BFI_COUNTER >= beamFailureInstanceMaxCount, if the serving cell is an SCell, the MAC entity will trigger a BFR for that serving cell. If the serving cell is not an SCell, the MAC entity will initiate a random access procedure on the SpCell.

[0267] If beamFailureDetectionTimer expires or if beamFailureDetectionTimer, beamFailureInstanceMaxCount, or any reference signal used for beam failure detection is reconfigured by the upper layer associated with the serving cell, the MAC entity sets BFI_COUNTER to 0.

[0268] If the serving cell is SpCell and the random access procedure initiated for SpCell beam failure recovery is successfully completed, the MAC entity should set BFI_COUNTER to 0, stop beamFailureRecoveryTimer (if configured), and consider the beam failure recovery procedure to have been successfully completed.

[0269] Otherwise, if the serving cell is a SCell, and the HARQ process for a transmission containing beam fault recovery information for that serving cell, or a truncated BFR MAC CE, receives a PDCCH addressed to a C-RNTI indicating uplink grant for the new transmission; or if the SCell is deactivated, the MAC entity sets BFI_COUNTER to 0; and considers the beam fault recovery process successfully completed and cancels all triggered BFRs for that serving cell.

[0270] When the beam fault recovery process determines that at least one BFR has been triggered and not canceled, if the UL-SCH resources are available for a new transmission and if the UL-SCH resources can accommodate the BFR MAC CE subheader as a result of the LCP plus the BFR MAC CE, the MAC entity will instruct the multiplexing and reassembly process to generate the BFR MAC CE.

[0271] Otherwise, if the UL-SCH resource is available for the new transmission, and if the UL-SCH resource can accommodate the truncated BFR MAC CE subheader as a result of LCP plus the truncated BFR MAC CE, the MAC entity will instruct the multiplexing and reassembly process to generate the truncated BFR MAC CE.

[0272] Otherwise, the MAC entity will trigger the SR for SCell beam fault recovery for each SCell for which the BFR has been triggered and not canceled.

[0273] When a MAC PDU is sent, all BFRs triggered before the assembly of the MAC PDU for beam fault recovery of the SCell will be cancelled, and the PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information for that SCell.

[0274] The MAC CE used for BFR consists of either a BFR MAC CE or a truncated BFR MAC CE.

[0275] Figure 13 and Figure 14 Examples of SCellBFR and truncated SCellBFR MAC CE are shown. Specifically, Figure 13 This illustrates the case where the highest ServCellIndex of the SCell of this MAC entity configured with BFD is less than 8. Furthermore, Figure 14 This illustrates the case where the highest ServCellIndex of the SCell of the MAC entity configured with BFD is equal to or greater than 8.

[0276] BFR MAC CE and truncated BFR MAC CE are identified by a MAC subheader with LCID / eLCID.

[0277] The BFR MAC CE and the truncated BFR MAC CE have variable sizes. They include a bitmap and include beam fault recovery information (i.e., an eight-bit byte containing the candidate beam availability indication (AC) of the SCell indicated in the bitmap) in ascending order based on the ServCellIndex.

[0278] For BFR MAC CE, when the highest ServCellIndex of the SCell of the MAC entity that detects a beam fault is less than 8, use methods such as Figure 13 A single octet bitmap. Otherwise, use, for example... Figure 14 The MAC PDU should contain at most one BFR MAC CE.

[0279] For truncated BFR MAC CE, a single octet bitmap is used for, for example... Figure 13 The following situations apply.

[0280] - The highest ServCellIndex of the SCell for the MAC entity where a beam fault is detected is less than 8; or

[0281] - If SpCell detects a beam fault (as specified in Clause 5.17) and indicates SpCell in a truncated BFR MACCE, and the UL-SCH resources available for transmission cannot accommodate a truncated BFR MAC CE subheader with a four-octet bitmap as a result of LCP, plus the truncated BFR MAC CE.

[0282] Otherwise, in the truncated BFR MAC CE, use, for example Figure 1 Four octets.

[0283] BFR MAC CE or truncated BFR MAC CE includes fields containing SP, Ci, AC, candidate RS ID, and R.

[0284] -SP is a field indicating beam fault detection for the SpCell of this MAC entity. The SP field is set to 1 to indicate that a beam fault is detected for the SpCell only if a BFR MAC CE or a truncated BFR MAC CE will be included in the MAC PDU as part of the random access procedure; otherwise, it is set to 0.

[0285] - In BFR MAC CE, C i This is a field indicating the presence of beam fault detection for an SCell with ServCellIndex i and an octet containing the AC field. i A field set to 1 indicates that a beam fault was detected for the SCell with ServCellIndex i and that an octet containing the AC field is present. i A field set to 0 indicates that no beam fault was detected, and that the octet containing the AC field does not exist for the SCell with ServCellIndex i. The octet containing the AC field exists in ascending order based on ServCellIndex.

[0286] In the truncated BFR MAC CE, C i This is a field indicating beam fault detection for an SCell with ServCellIndex i. iA field set to 1 indicates that a beam fault was detected for an SCell with ServCellIndex i, and an octet containing the AC field may exist. i Setting the field to 0 indicates that no beam fault was detected for the SCell with ServCellIndex i and that there is no octet containing the AC field. If present, the octet containing the AC field is included in ascending order based on ServCellIndex. The number of included octets containing the AC field is maximized without exceeding the available license size.

[0287] The number of octets containing the AC field in a truncated BFR MAC CE can be zero.

[0288] AC is a field indicating the presence of a candidate RS ID field in this octet. The AC field is set to 1 if at least one of the SSBs in candidateBeamRSSellList with an SS-RSRP higher than rsrp-ThresholdBFR or the CSI-RS in candidateBeamRSSellList with a CSI-RS higher than rsrp-ThresholdBFR is available; otherwise, it is set to 0. If the AC field is set to 1, the candidate RS ID field exists. If the AC field is set to 0, an R bit is present instead.

[0289] The candidate RS ID is a field set to the index of the SSB in the candidateBeamRSSellList that has an SS-RSRP higher than rsrp-ThresholdBFR, or set to the index of the CSI-RS in the candidateBeamRSSellList that has a CSI-RS higher than rsrp-ThresholdBFR. This field is 6 bits long.

[0290] Finally, R represents the reserved bit, which is set to 0.

[0291] The 3GPP NR standard supports several MIMO features to facilitate the utilization of a large number of antenna elements at the base station. Specifically, multiple transmit and receive points (mTRPs) are used to mitigate interference through dynamic coordination among multiple TRPs to provide joint scheduling and transmit / receive. UEs at the cell edge can be served by mTRPs to improve their signal transmission / reception, thereby increasing throughput.

[0292] Recently, we have considered enhancing support for multi-TRP deployments, including inter-cell mTRP operations. In inter-cell mTRP operations, two TRPs are configured for the serving cell and the non-serving cell, and the non-serving cell is associated with the serving cell. When the UE communicates with the serving cell in inter-cell mTRP operations, the UE sends data to / receives data from both the serving and non-serving cells using both TRPs.

[0293] By leveraging inter-cell mTRP operations, channels other than PDSCH can benefit from multi-TRP transmissions between cells with different Physical Cell Identifiers (PCIs). This includes some new use cases for multi-TRP, such as dense UL deployments within macrocells and / or heterogeneous network type deployment scenarios.

[0294] In addition, for inter-cell mTRP operations, the introduction of enhanced BFR MAC CE is also considered, including beam fault recovery information for two faulty TRPs, and both truncated and untruncated enhanced BFR MAC CEs are also supported.

[0295] In the current MAC specification of the NR system, when the UE generates a truncated BFR MAC CE, it includes as much BFR information as possible to fit the UL license size in ascending order based on the serving cell index. That is, the number of octets including the AC field is maximized based on the ServCellIndex in ascending order while not exceeding the available license size.

[0296] Therefore, by utilizing inter-cell mTRP operations, if BFR information is included in the truncated enhanced BFR MAC CE in ascending order based on the serving cell index as in the conventional approach, the BFR information of the two TRPs of the serving cell is included as much as possible in ascending order based on the serving cell index to suit the UL authorized size.

[0297] For some cells, if the remaining UL grant size can no longer accommodate BFR information, the BFR information for some cells' TRPs will not be included in the truncated BFR MAC CE. The network is unaware of the cell's TRP BFR information and may not recover from beam faults, and the UE will not be able to receive any information from the cell.

[0298] However, if the network knows the BFR information of a TRP for a larger number of cells, the network can recover beam faults in more cells and transmit data through a larger number of cells. Therefore, in terms of the number of available cells, a truncated BFR MAC CE that includes the BFR information of more cells (even for at least one TRP) may be better than one that includes the BFR information of two TRPs that include a smaller number of cells.

[0299] Therefore, in this disclosure, in order to include BFR information of the TRPs for the maximum number of cells in the truncated enhanced BFR MAC CE, it is recommended that for each cell in which a beam fault is detected, if a beam fault is detected on two TRPs, the truncated enhanced BFR MAC CE should include the BFR information of the TRP corresponding to the serving cell's TRP, and if a beam fault is detected on one TRP, the truncated enhanced BFR MAC CE should include the BFR information of the corresponding TRP while not exceeding the available license size.

[0300] Then, for each cell where a beam fault is detected and BFR information is not included in the truncated enhanced BFR MAC CE, the truncated enhanced BFR MAC CE includes the remaining BFR information while not exceeding the available licensed size.

[0301] For inter-cell mTRP operations, the UE is configured with multiple serving cells and non-serving cells. Each non-serving cell is associated with at least one serving cell.

[0302] Two TRPs are configured for each serving cell. One TRP (TRP 1) is configured to send data to / receive data from each serving cell, and the other TRP (TRP 2) is configured to send data to / receive data from each non-serving cell associated with each serving cell. When the UE operates in the inter-cell mTRP operation within the serving cell, the UE uses both TRPs to send data to / receive data from the serving cell and its associated non-serving cells.

[0303] When a beam fault is detected in the TRP for a cell (i.e., BFI_COUNTER is equal to or greater than beamFailureInstanceMaxCount), the UE triggers beam fault recovery (BFR) for the TRP for the cell.

[0304] If at least one BFR of the TRP is triggered and not canceled, and if the UL-SCH resource is available for the new transmission, and if the UL-SCH resource can accommodate the sub-header of the enhanced BFR MAC CE as a result of the LCP, and the enhanced BFR MAC CE, then the UE generates the enhanced BFR MAC CE.

[0305] If at least one BFR of the TRP is triggered and not canceled, and if the UL-SCH resource is available for the new transmission, and if the UL-SCH resource can accommodate the subheader of the truncated enhanced BFR MAC CE as a result of the LCP, and the truncated enhanced BFR MAC CE instead of the enhanced BFR MAC CE, then the UE generates the truncated enhanced BFR MAC CE.

[0306] When the UE generates a truncated enhanced BFR MAC CE, the truncated enhanced BFR MAC CE includes BFR information as follows:

[0307] <Step 1>

[0308] For each cell where a beam fault is detected on at least one TRP, sorted in ascending order of the serving cell's ServCellIndex, while not exceeding the available license size:

[0309] If a beam fault is detected on both TRPs, the truncated enhanced BFR MAC CE includes the BFR information for TRP 1.

[0310] If a beam fault is detected on a TRP, the truncated enhanced BFR MAC CE includes the BFR information for the corresponding TRP.

[0311] Step 2

[0312] For each cell where a beam fault is detected, the BFR information not included in the truncated enhanced BFR MAC CE is maintained in ascending order of the serving cell's ServCellIndex, while not exceeding the available license size:

[0313] The truncated enhanced BFR MAC CE includes the BFR information of TRP 2.

[0314] BFR information includes candidate beam information represented by the candidate RS ID field. The presence of the candidate RS ID field in the BFR information is indicated by the candidate beam availability indicator (AC). The AC field is also included in the BFR information. Therefore, the eight bytes of BFR information for each cell include either i) the AC field and the candidate RS ID field or ii) the AC field and the R field.

[0315] The truncated enhanced BFR MAC CE is multiplexed with a MAC subheader that includes the LCID indicating the truncated enhanced BFR MAC CE, and is transmitted using UL resources.

[0316] Figure 15 An example of a truncated enhanced BFR MAC CE according to this disclosure is shown.

[0317] Reference Figure 15 Assume the UE is configured with 1 SpCell (ServCellIndex=0) and 7 SCells (ServCellIndex=1...7). Each serving cell is configured with two TRPs for inter-cell mTRP operations.

[0318] The T field indicates the TRS_ID. TRS_ID = 0 indicates that the octet is used for the TRP of the serving cell (i.e., TRP 1), and TRS_ID = 1 indicates that the octet is used for the TRP of a non-serving cell (i.e., TRP 2).

[0319] In addition, Figure 15 In this context, it is assumed that a beam fault is detected on two TRPs used for SCell 1 (C1), SCell 2 (C2), and SCell 5 (C5), and a beam fault is detected on TRP2 used for SCell 4 (C4).

[0320] If the available UL resources are only 6 bytes for the enhanced BFR MAC CE, the UE determines to generate a truncated enhanced BFR MAC CE. Therefore, fields C1, C2, C4, and C5 are set to 1, and fields for other cells are set to 0.

[0321] For SCell 1, SCell 2, SCell 4, and SCell 5, in ascending order of ServCellIndex, if a beam fault is detected on both TRPs used for the serving cell, then eight bytes of BFR information are included for TRP 1; and if a beam fault is detected on one TRP used for the serving cell, then eight bytes of BFR information are included for that TRP. That is, the BFR information is included in the following order:

[0322] 1) Includes BFR information for TRP 1 of SCell 1.

[0323] 2) Includes BFR information for TRP 1 of SCell 2.

[0324] 3) Includes BFR information for TRP 2 of SCell 4.

[0325] 4) Includes BFR information for TRP 1 of SCell 5.

[0326] Then, since the remaining UL resource is 1 byte, only for SCell1, the remaining TRP BFR information (eight bytes) is included, in ascending order of the serving cell's ServCellIndex. That is, the BFR information is included in the following order:

[0327] 5) Includes BFR information for TRP 2 of SCell 1.

[0328] Finally, the UE sends a truncated BFR MAC CE to the network.

[0329] If a beam fault is detected in two TRPs for a specific cell (SpCell), the truncated enhanced BFR MACCE can first include the BFR information of the two TRPs of the SpCell, and then include the BFR information of TRP 1 of each serving cell and the BFR information of TRP 2 of each non-serving cell.

[0330] Figure 16 Another example of a truncated enhanced BFR MAC CE according to this disclosure is shown.

[0331] Similarly, in Figure 16 In this scenario, assume the UE is configured with 1 SpCell (ServCellIndex = 0) and 7 SCells (ServCellIndex = 1..7). Each serving cell is configured with two TRPs for inter-cell mTRP operations. Beam faults are detected on two TRPs for SpCell (SP), SCell 1 (C1), and SCell 5 (C5), and a beam fault is detected on TRP 2 for SCell 4 (C4). Therefore, the fields for SP, C1, C4, and C5 are set to 1, and the fields for the other cells are set to 0.

[0332] Reference Figure 16 The T field indicates the TRS_ID. TRS_ID = 0 is assigned to the TRP of the serving cell (TRP 1), and TRS_ID = 1 is assigned to the TRP of the non-serving cell (TRP 2).

[0333] If the available UL resources are only 6 bytes for the enhanced BFR MAC CE, the UE generates a truncated enhanced BFR MAC CE.

[0334] Specifically, it first includes eight bytes of BFR information for the two TRPs used in SpCell. That is, the BFR information is included in the following order:

[0335] 1) Includes BFR information for TRP 1 of SpCell.

[0336] 2) Includes BFR information for TRP 2 of SpCell.

[0337] For SCell1, SCell4, and SCell5, in ascending order of ServCellIndex, if a beam fault is detected on two TRPs of the serving cell, then eight bytes of BFR information are included for TRP1; and if a beam fault is detected on one TRP of the serving cell, then eight bytes of BFR information are included for that TRP. That is, the BFR information is included in the following order:

[0338] 3) Includes BFR information for TRP 1 of SCell 1.

[0339] 4) Includes BFR information for TRP 2 of SCell 4.

[0340] 5) Includes BFR information for TRP 1 of SCell 5.

[0341] Finally, the UE sends a truncated BFR MAC CE to the network.

[0342] Furthermore, in the MAC standard of the NR system, the SP field and C field of the truncated BFR MAC CE field should be modified. i Definition.

[0343] More specifically, SP is a field indicating beam fault detection for the SpCell of this MAC entity. The SP field is set to 1 to indicate that a beam fault is detected for two TRPs of the SpCell when an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE is included in the MAC PDU as part of the random access procedure, or when a beam fault is detected for at least one TRP, the evaluation of candidate beams has been completed as required, and an octet containing the AC field exists for the SpCell. Otherwise, it is set to 0. If a beam fault is detected for two TRPs of the SpCell, the octets containing the AC field for the two TRPs of the SpCell exist first in ascending order of TRS_ID compared to other cells.

[0344] In the truncated BFR MAC CE, C i This is a field indicating beam fault detection for an SCell with ServCellIndex i. Setting C to 1... i The field indicates that a beam fault was detected for at least one TRP, that candidate beams have been evaluated for the TRP as required, and that an eight-bit byte containing the AC field may exist for a TRP with an SCell having ServCellIndex i. A setting of 0 for C... iThe field indicates that no beam fault was detected at two TRPs, or that a beam fault was detected at at least one TRP, but candidate beam evaluation for the TRP as required has not yet been completed, and that for the TRP with SCell i, there is no octet containing the AC field. Based on ServCellIndex in ascending order, if a beam fault is detected on two TRPs, an octet containing the AC field is first present for TRP_ID=0 (if it already exists), and if a beam fault is detected on one TRP, an octet containing the AC field is first present for the corresponding TRP (if it already exists). Then, if the truncated enhanced BFR MAC CE does not include the remaining BFR information, an octet containing the AC field is present for TRP_ID=1 in ascending order based on ServCellIndex. The number of octets containing the AC field is maximized while not exceeding the available license size.

[0345] According to this disclosure, the truncated enhanced BFR MAC CE includes BFR information for a larger number of cells even for a single TRP, allowing the network to know the BFR information of more cells and recover from their beam faults. Therefore, in terms of the number of available cells, the UE can interoperate with a larger number of cells.

Claims

1. A method for recovering a truncated beam fault (BFR) medium access control (MAC) control element (CE) transmitted by a user equipment (UE) in a wireless communication system, the method comprising the following steps: Based on beam fault detection across multiple serving cells, a truncated BFRMAC CE is generated, wherein the truncated BFRMAC CE does not exceed the available license size; and Send the truncated BFR MAC CE to the network. The steps for generating the truncated BFR MAC CE include: i) First, the BFR information for the specific SpCell among the multiple serving cells is included in the truncated BFR MAC CE; ii) Including the first BFR information for each of at least one secondary cell SCell among the plurality of serving cells in ascending order of the serving cell index into the truncated BFR MAC CE; and iii) The second BFR information for each of the at least one SCell is included in the truncated BFR MAC CE in ascending order of the serving cell index.

2. The method according to claim 1, wherein, The multiple serving cells are configured with multiple Transmitting and Receiving Points (TRPs), and The first BFR information is associated with one of the plurality of TRPs, and the second BFR information is associated with another of the plurality of TRPs.

3. The method according to claim 2, wherein, Based on the detection of the beam fault on at least two TRPs of the SpCell, the first BFR information for the SpCell and the second BFR information for the SpCell are first included in the truncated BFR MAC CE before including the first BFR information and the second BFR information for the at least one SCell.

4. The method according to claim 2, wherein, The first BFR information and the second BFR information include fields indicating the corresponding TRP.

5. The method according to claim 1, wherein, The truncated BFR MAC CE includes bitmap information indicating whether the beam fault was detected on each of the plurality of serving cells.

6. A user equipment (UE) in a wireless communication system, the UE comprising: At least one processor; as well as At least one computer memory storing instructions that, when executed by the at least one processor, cause the UE to perform an operation, the operation including: Based on beam fault detection across multiple serving cells, a truncated beam fault recovery (BFR) medium access control (MAC) control element (CE) is generated, wherein the truncated BFR MAC CE does not exceed the available license size; and Send the truncated BFR MAC CE to the network. The operation of generating the truncated BFR MAC CE includes: i) First, the BFR information of the special cell SpCell among the multiple serving cells is included in the truncated BFRMAC CE; ii) Including the first BFR information for each of at least one secondary cell SCell among the plurality of serving cells in ascending order of the serving cell index into the truncated BFR MAC CE; and iii) The second BFR information for each of the at least one SCell is included in the truncated BFR MAC CE in ascending order of the serving cell index.

7. The UE according to claim 6, wherein, The multiple serving cells are configured with multiple Transmitting and Receiving Points (TRPs), and The first BFR information is associated with one of the plurality of TRPs, and the second BFR information is associated with another of the plurality of TRPs.

8. The UE according to claim 7, wherein, Based on the detection of the beam fault on at least two TRPs of the SpCell, the first BFR information for the SpCell and the second BFR information for the SpCell are first included in the truncated BFR MAC CE before including the first BFR information and the second BFR information for the at least one SCell.

9. The UE according to claim 7, wherein, The first BFR information and the second BFR information include fields indicating the corresponding TRP.

10. The UE according to claim 6, wherein, The truncated BFR MAC CE includes bitmap information indicating whether the beam fault was detected on each of the plurality of serving cells.

Images