A method for canceling a buffer status report procedure in a wireless communication system and an apparatus for doing so.

Abstract

This disclosure relates to a method by which User Equipment (UE) performs an operation in a wireless communication system. In particular, the method includes the steps of: receiving at least one Service Data Unit (SDU) from a higher layer, starting at least one discard timer associated with the at least one SDU; triggering a status report procedure based on the remaining time of the at least one discard timer associated with the at least one SDU being less than or equal to a threshold; and canceling the triggered status report procedure based on the expiration of all of the at least one discard timers.

Description

[Technical Field]

[0001] This disclosure relates to a wireless communication system, and more particularly to a method and apparatus for canceling a buffer status report procedure in a wireless communication system. [Background technology]

[0002] With the introduction of new wireless communication technologies, not only is the number of UEs (Users) that a base station provides services to increasing within a given resource area, but the amount of data and control information that the base station sends and receives with the UEs it provides services to is also increasing. Since the amount of radio resources available to a base station for communication with UEs is finite, new methods are needed for base stations to efficiently send and receive uplink / downlink data and / or uplink / downlink control information to and from UEs using these finite radio resources. In particular, there is an increasing number of applications whose performance is heavily dependent on delay. Therefore, methods are needed to reduce delay compared to conventional systems. [Overview of the project] [Problems that the invention aims to solve]

[0003] The object of the present invention is to provide a method for canceling a buffer status report procedure in a wireless communication system and an apparatus for doing so. [Means for solving the problem]

[0004] The object of the present invention is achieved by a method relating to an operation performed by user equipment (UE), the method including the steps of: receiving at least one Service Data Unit (SDU) from a higher hierarchy, starting at least one discard timer associated with the at least one SDU; triggering a status report procedure based on the remaining time of the at least one discard timer associated with the at least one SDU being less than or equal to a threshold; and canceling the triggered status report procedure based on the expiration of all of the at least one discard timers.

[0005] Furthermore, a user equipment (UE) is proposed for a wireless communication system, the UE comprising at least one transceiver, at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions for causing the at least one processor to perform an operation, the operation comprising the steps of: receiving at least one Service Data Unit (SDU) from a higher hierarchy, starting at least one discard timer associated with the at least one SDU; triggering a status report procedure based on the remaining time of the at least one discard timer associated with the at least one SDU being less than or equal to a threshold; and canceling the triggered status report procedure based on the expiration of all of the at least one discard timers.

[0006] Preferably, the triggered status report procedure is canceled when a status report MAC CE (control element) containing information about all of the at least one SDU is transmitted.

[0007] Preferably, if the triggered status report procedure is not cancelled and an uplink grant related to the at least one SDU is available, the UE transmits a status report MAC CE (control element) including information about the at least one SDU.

[0008] Preferably, if the at least one discard timer expires, the at least one MAC SDU is discarded.

[0009] Preferably, if the number of MAC SDUs received from the upper layer is two or more, a discard timer related to each of the two or more MAC SDUs is started.

[0010] The effects achievable by the present invention are not limited to the content mentioned above, and other advantages of the present invention will be clearly understood by those skilled in the art from the following detailed description.

Effects of the Invention

[0011] According to the present disclosure, the UE does not cancel the BSR procedure even if it is triggered until it transmits the MAC CE for the BSR via a new UL grant that permits retransmission after the RTT. This enables stable transmission of the BSR, so that the network can schedule the UL grant for the UE.

[0012] Also, if all MAC SDUs related to the BSR have expired, the UE cancels the triggered BSR. This can prevent unnecessary MAC CE transmission for the BSR.

[0013] The effects obtained by the present invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those having ordinary knowledge in the technical field to which the present invention belongs from the following description.

Brief Description of the Drawings

[0014] The drawings attached below are intended to aid in understanding the present invention, and the principles of the present invention will be explained along with a detailed description.

[0015] [Figure 1] This figure shows an example of a communication system to which the present invention is applied. [Figure 2] This is a block diagram showing an example of a communication device that implements the method according to the present invention. [Figure 3] This figure shows an example of a frame structure in a 3GPP®-based wireless communication system. [Figure 4] This figure shows an example of a protocol stack in a wireless communication system based on 3GPP (third generation partnership project). [Figure 5] This figure shows an example of data flow in a 3GPP NR system. [Figure 6] This figure shows an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time resource allocation by PDCCH. [Figure 7] This figure shows an example of physical layer processing on the transmitting side. [Figure 8] This figure shows an example of physical layer processing on the receiving end. [Figure 9] Examples of cases where retransmission is not permitted in relation to this disclosure are shown below. [Figure 10] The first example of canceling a BSR in relation to this disclosure is shown below. [Figure 11] A second example of canceling a BSR in relation to this disclosure is shown. [Figure 12] A third example of canceling a BSR in relation to this disclosure is shown. [Figure 13] A fourth example of canceling a BSR in relation to this disclosure is shown. [Modes for carrying out the invention]

[0016] The following description will elaborate on exemplary embodiments of the present invention with reference to the accompanying drawings. The detailed description provided with the accompanying drawings is intended to illustrate exemplary embodiments of the present invention and is not the only possible embodiment. The following detailed description includes specific details to provide a complete understanding of the present invention. However, it will be apparent to those skilled in the art that the invention can be implemented without such specific details.

[0017] The following technologies can be used in various wireless connectivity systems such as CDMA (Code Division Multiple Access), FDMA (Frequency Division Multiple Access), TDMA (Time Division Multiple Access), OFDMA (Orthogonal Frequency Division Multiple Access), and SC-FDMA (Single Carrier Frequency Division Multiple Access). CDMA can be implemented using radio technology such as UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA can be implemented using radio technology such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented using radio technology such as IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802-20, and E-UTRA (Evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e. UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is part of E-UMTS (Evolved UMTS) which uses E-UTRA, employing OFDMA for the downlink and SC-FDMA for the uplink. LTE-A (Advanced) is an evolution of 3GPP LTE.

[0018] For the sake of clarity, this specification will be described below in relation to 3GPP-based communication systems. However, the technical features of this specification are not limited thereto. For example, even if the following detailed description is based on a mobile communication system corresponding to a 3GPP-based system, it is applicable to any other mobile communication system except for matters specific to 3GPP-based systems. For terms and technologies described in this specification that are not specifically mentioned, refer to the radio communication standards documents prior to the publication of this specification. For example, refer to the following documents.

[0019] 3GPP LTE

[0020] - 3GPP TS36.211:Physical channels and modulation

[0021] - 3GPP TS36.212:Multiplexing and channel coding

[0022] - 3GPP TS36.213:Physical layer procedures

[0023] - 3GPP TS36.214:Physical layer; Measurements

[0024] - 3GPP TS36.300:Overall description

[0025] - 3GPP TS36.304:User Equipment(UE) procedures in idle mode

[0026] - 3GPP TS36.314:Layer 2-Measurements

[0027] - 3GPP TS36.321:Medium Access Control (MAC) protocol

[0028] - 3GPP TS36.322:Radio Link Control(RLC) protocol

[0029] - 3GPP TS36.323:Packet Data Convergence Protocol(PDCP)

[0030] - 3GPP TS36.331:Radio Resource Control(RRC) protocol

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

[0032] - 3GPP TS38.211:Physical channels and modulation

[0033] - 3GPP TS38.212:Multiplexing and channel coding

[0034] - 3GPP TS38.213:Physical layer procedures for control

[0035] - 3GPP TS38.214:Physical layer procedures for data

[0036] - 3GPP TS38.215:Physical layer measurements

[0037] - 3GPP TS38.300:Overall description

[0038] - 3GPP TS38.304:User Equipment(UE) procedures in idle mode and in RRC inactive state

[0039] - 3GPP TS38.321:Medium Access Control(MAC) protocol

[0040] - 3GPP TS38.322:Radio Link Control(RLC) protocol

[0041] - 3GPP TS38.323:Packet Data Convergence Protocol(PDCP)

[0042] - 3GPP TS38.331:Radio Resource Control(RRC) protocol

[0043] - 3GPP TS37.324:Service Data Adaptation Protocol(SDAP)

[0044] - 3GPP TS37.340:Multi-connectivity;Overall description

[0045] In this specification, UE refers to various devices that may be fixed or mobile and communicate with a base station (BS) to send and receive user data and / or various control information. UE can also be called Terminal Equipment, MS (Mobile Station), MT (Mobile Terminal), UT (User Terminal), SS (Subscribe Station), wireless device, PDA (Personal Digital Assistant), wireless modem, handheld device, etc. In this specification, BS generally refers to a fixed station that communicates with UE and / or other BSs, exchanging various data and control information with UE and other BSs. BS can also be called by other terms such as ABS (Advanced Base Station), NB (Node-B), eNB (evolved-Node-B), BTS (Base Transceiver System), Access Point, PS (Processing Server), etc. Specifically, BS in UMTS is called NB, BS in EPC / LTE is called eNB, and BS in NR (new radio) systems is called gNB.

[0046] In this specification, a node refers to a fixed point that can communicate with a UE to send / receive wireless signals. Various forms of eNBs can be used as nodes, regardless of their name. For example, BS, NB, eNB, picocell eNB (PeNB), home eNB (HeNB), relay, repeater, etc., can be used as nodes. Furthermore, a node does not have to be an eNB. For example, a radio remote head (RRH) or radio remote unit (RRU) can also be used. RRHs and RRUs generally have a lower power level than the eNB. Since RRHs or RRUs (hereinafter, RRH / RRU) are generally connected to the eNB by a dedicated line such as an optical cable, cooperative communication between RRHs / RRUs and eNBs can generally be performed more smoothly than cooperative communication by eNBs connected by wireless lines. At least one antenna is installed at each node. The term "antenna" above can refer to a physical antenna, an antenna port, a virtual antenna, or an antenna group.

[0047] In this specification, "cell" refers to a specific geographical area where one or more nodes provide communication services, or to a radio resource. A geographical "cell" can be understood as the coverage over which a node can provide services using a carrier wave, while a "cell" as a radio resource (e.g., a time-frequency resource) is related to the bandwidth (BW), which is the frequency range configured by the carrier wave. A "cell" associated with a radio resource is defined by a combination of downlink and uplink resources, for example, a combination of a downlink (DL) component carrier (CC) and an uplink (UL) CC. A cell can be configured as a downlink resource alone, or as a combination of downlink and uplink resources. Downlink coverage, which is the range over which a node can transmit a valid signal, and uplink coverage, which is the range over which a node can receive a valid signal from a UE, depend on the carrier wave carrying the signal; therefore, a node's coverage may also be related to the coverage of the "cell" of the radio resource used by that node. Therefore, the term "cell" can sometimes refer to the service coverage provided by a node, sometimes to wireless resources, and sometimes to the range over which signals using those wireless resources can reach with effective strength.

[0048] In this invention, 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) that carry downlink control information (DCI), and a set of time-frequency resources or REs that carry downlink data, respectively. Similarly, 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 that carry uplink control information (UCI), a set of time-frequency resources or REs that carry uplink data, and a set of time-frequency resources or REs that carry random access signals, respectively.

[0049] In carrier aggregation (CA), two or more CCs are aggregated. Depending on its capabilities, a UE can simultaneously receive or transmit one or more CCs. CA supports both continuous and discontinuous CCs. Once a CA is configured, only the UE forms a single 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 a cell that operates at the primary frequency, at which the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on the UE's capabilities, secondary cells (SCells) may be configured to form a set of serving cells together with the PCell. SCells are cells that provide additional radio resources in addition to the special cells. Therefore, the set of serving cells configured for a UE always consists of one PCell and one or more SCells. For dual connectivity operation, the term special cell (SpCell) refers to a PCell in a master cell group (MCG) or a PSCell in a secondary cell group (SCG). SpCells support any connection of PUCCH transmission and competitive infrastructure and are always activated. An MCG is a serving cell group associated with a master node and includes SpCells (PCells) and optionally one or more SCells. An SCG is a subset of serving cells associated with a secondary node and consists of a PSCell and zero or more SCells for UEs configured in dual connectivity (DC). For RRC_CONNECTED UEs not configured in CA / DC, there is only one serving cell consisting of a PCell.For UEs with RRC_CONNECTED set in CA / DC, the term "serving cell" is used to refer to the cell set consisting of SpCell and all SCells.

[0050] The MCG is a group of serving cells associated with a master BS that terminates at least S1-MME, while the SCG is a group of serving cells associated with a secondary BS that is not the master BS but provides additional radio resources for the UE. The SCG consists of a primary SCell (PSCell) and optionally one or more SCells. In the DC, two MAC entities, namely the MAC entity for the MCG and the MAC entity for the SCG, are configured at the UE. Each MAC entity is a serving cell configured by the RRC to support PUCCH transmission and optional connections of the competitive infrastructure. In this invention, the term SPCell refers to such a cell, while the term SCell refers to the other serving cell. The term SPCell indicates either the PCell of the MCG or the PSCell of the SCG, depending on whether the MAC entity is associated with the MCG or the SCG, respectively.

[0051] In this invention, channel monitoring means attempting to decode a channel. For example, PDCCH monitoring means attempting to decode a PDCCH (or a candidate PDCCH).

[0052] In this specification, "C-RNTI" indicates a cell RNTI, "SI-RNTI" indicates a system information RNTI, "P-RNTI" indicates a paging RNTI, "RA-RNTI" indicates an arbitrary connection RNTI, "SC-RNTI" indicates a single cell RNTI, "SL-RNTI" indicates a sidelink RNTI, "SPS C-RNTI" indicates a semi-persistent scheduling C-RNTI, and "CS-RNTI" indicates a configured scale RNTI.

[0053] Figure 1 illustrates a communication system to which the present invention applies.

[0054] The three main requirements areas for 5G include (1) Enhanced Mobile Broadband (eMBB), (2) Massive Machine Type Communication (mMTC), and (3) Ultra-reliable and Low Latency Communications (URLLC).

[0055] In some use cases, optimization may require addressing multiple domains, while in others, the focus may be on only a single key performance indicator (KPI). 5G supports these diverse use cases in a flexible and reliable manner.

[0056] eMBB goes far beyond basic mobile internet access, covering rich two-way communication, cloud, or augmented reality media and entertainment applications. Data is one of the core drivers of 5G, and for the first time in the 5G era, we may not see dedicated voice services. In 5G, voice is expected to be processed as an application program using the data connectivity provided by the communication system. The main causes of the increased traffic volume are the increasing size of content and the increasing number of applications that demand high data transmission rates. Streaming services (audio and video), conversational video, and mobile internet connectivity will be used more widely as more devices connect to the internet. Many of these applications require always-on connectivity to push real-time information and notifications to users. Cloud storage and applications are rapidly increasing on mobile communication platforms, and this is applicable to both business and entertainment. Cloud storage is also a particular use case that drives the growth of uplink data transmission rates. 5G will also be used for cloud-based remote work, requiring even lower end-to-end latency to maintain a superior user experience when haptic interfaces are used. Entertainment, such as cloud gaming and video streaming, is another core element increasing the demand for mobile highband capacity. Entertainment is essential on smartphones and tablets everywhere, including in highly mobile environments such as trains, cars, and airplanes. Another use case is augmented reality and information retrieval for entertainment, where augmented reality requires very low latency and instantaneous data volumes.

[0057] Furthermore, one of the most anticipated use cases for 5G is its ability to seamlessly connect embedded sensors across all sectors, namely mMTC (Mechanical Microcontrollers). The potential number of IoT devices is projected to reach 20.4 billion by 2020. Industrial IoT is one area where 5G will play a key role in enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure.

[0058] URLLCs include new services that will transform industries through ultra-reliable / available low-latency links for remote control of critical infrastructure and self-driving vehicles. Levels of reliability and latency are essential for smart grid control, industrial automation, robotics, and drone control and coordination.

[0059] 5G is a means of delivering streams rated at hundreds of megabits per second to gigabits per second, and can complement FTTH (fiber-to-the-home) and cable-based broadband (or DOCSIS). Such high speeds are required not only for virtual and augmented reality but also for transmitting TV at resolutions of 4K and above (6K, 8K and beyond). VR (Virtual Reality) and AR (Augmented Reality) applications mostly include immersive sports competitions. Certain application programs may require special network configurations. For example, in the case of VR games, game companies must integrate their core servers with the network operator's edge network servers to minimize latency.

[0060] Automotive is expected to be a key new driving force in 5G, along with numerous use cases for mobile communications within vehicles. For example, passenger entertainment requires high simultaneous capacity and high mobile broadband bandwidth. This is because future users will expect high-quality connectivity regardless of their location and speed. Another use case in the automotive sector is augmented reality dashboards, which overlay information on what the driver sees through the windshield, identifying objects in the dark and telling the driver about their distance and movement. In the future, wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure structures, and information exchange between vehicles and other connected devices (e.g., devices accompanied by pedestrians). Safety systems will guide drivers to alternative routes of action to enable safer driving and reduce the risk of accidents. The next stage will be remotely controlled or self-driven vehicles, which will require extremely reliable and very fast communication between different self-driven vehicles and between vehicles and infrastructure. In the future, self-driving vehicles will perform all driving activities, allowing drivers to concentrate only on traffic anomalies that the vehicle itself cannot identify. The technical requirements for self-driving vehicles demand ultra-low latency and ultra-high-speed reliability so that traffic safety increases to a level unattainable by humans.

[0061] Smart cities and smart homes, often referred to as smart societies, are embedded in high-density wireless sensor networks. A distributed network of intelligent sensors identifies the cost and energy-efficient maintenance requirements for a city or home. Similar setups can be made for individual homes. Temperature sensors, window and heating controllers, burglar alarms, and household appliances are all connected wirelessly. Many of these sensors are typically low data transmission speeds, low power consumption, and low cost. However, real-time HD video, for example, may be required for certain types of devices for surveillance purposes.

[0062] The consumption and distribution of energy, including heat or gas, is highly decentralized, requiring automated control of a distributed sensor network. Smart grids interconnect such sensors, using digital information and communication technologies to collect information and act accordingly. This information can include the behavior of suppliers and consumers, enabling smart grids to improve the efficiency, reliability, economics, production sustainability, and automated distribution of fuels like electricity. Smart grids can also be viewed as other low-latency sensor networks.

[0063] Mission-critical applications (e.g., e-health) are one of the 5G use scenarios. The healthcare sector has many application programs that can benefit from mobile communications. Communication systems can support telemedicine, which provides clinical care in remote locations. This helps reduce the barrier of distance and can improve access to medical services that are not sustainably available in remote rural areas. This can also be used to save lives in critical medical and emergency situations. Mobile communication-based wireless sensor networks can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

[0064] Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. Therefore, the possibility of replacing cables with reconfigurable wireless links presents an attractive opportunity in many industrial sectors. However, achieving this requires wireless connections to operate with similar latency, reliability, and capacity to cables, and to simplify their management. Low latency and extremely low error rates are new requirements that must be met by 5G.

[0065] Logistics and freight tracking are important use cases for mobile communications, using location-based information systems to enable inventory and package tracking anywhere. Logistics and freight tracking use cases typically require low data speeds but demand wide-area and reliable location information.

[0066] Referring to Figure 1, communication system 1 includes wireless equipment, base stations (BS), and a network. Although Figure 1 shows a 5G network as an example of the network of communication system 1, the embodiment of the present invention is not limited to 5G systems and can be applied to next-generation communication systems beyond 5G systems.

[0067] BS and networks are embodied in wireless devices, and certain wireless devices 200a can operate as BS / network nodes for other wireless devices.

[0068] Wireless devices refer to devices that communicate using wireless access technology (RAT) (e.g., 5G NR, LTE), and can be called communication / wireless / 5G devices. However, wireless devices include, but are not limited to, robots 100a, vehicles 100b-1, 100b-2, XR (eXtended Reality) devices 100c, handheld devices 100d, home appliances 100e, IoT (Internet of Things) devices 100f, and AI devices / servers 400. For example, vehicles include vehicles equipped with wireless communication capabilities, autonomous vehicles, and vehicles capable of vehicle-to-vehicle communication. Here, vehicles include UAVs (Unmanned Aerial Vehicles) (e.g., drones). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and are embodied in forms such as HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) installed in vehicles, TVs, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, and robots. Portable devices include smartphones, smart pads, wearable devices (e.g., smartwatches, smart glasses), and computers (e.g., notebook computers). Home appliances include TVs, refrigerators, and washing machines. IoT devices include sensors and smart meters.

[0069] In this invention, wireless devices 100a to 100f are also called UEs. UEs include, for example, mobile phones, smartphones, notebook computers, digital broadcasting terminals, PDAs (personal digital assistants), PMPs (portable multimedia players), car navigation systems, slate PCs, tablet PCs, ultrabooks, vehicles, vehicles with autonomous driving capabilities, connected cars, UAVs, AI (artificial intelligence) modules, robots, AR (augmented reality) devices, VR (virtual reality) devices, MR (mixed reality) devices, hologram devices, devices for public safety, MTC devices, IoT devices, medical devices, fintech devices (or financial devices), security devices, weather / environmental devices, devices related to 5G services, or devices related to the field of the Fourth Industrial Revolution. A UAV is, for example, an aircraft that flies using wireless control signals without carrying a person. A VR device includes, for example, a device for representing objects or backgrounds in a virtual world. AR devices include, for example, devices that embody objects or backgrounds in a virtual world to link them to objects or backgrounds in the real world. MR devices include, for example, devices that embody objects or backgrounds in a virtual world to merge them with objects or backgrounds in the real world. Holographic devices include, for example, devices for embodying 360° stereoscopic images by recording and reproducing three-dimensional information using a phenomenon called holography, which is the interference of light produced when two lasers meet. Public safety devices include, for example, wearable video relay devices or video devices. MTC devices and IoT devices include devices that do not require direct human interference or operation. For example, MTC devices and IoT devices include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors. Medical devices are, for example, devices used for diagnosis, treatment, palliative care, therapy, and disease prevention. Medical devices are, for example, devices for diagnosing, treating, palliative care, or correcting injuries or disabilities.For example, medical devices are devices used to rescue or examine, replace, or modify functions. For example, medical devices are devices for pregnancy control. For example, medical devices include devices for medical treatment, devices for surgery, devices for (in vitro) diagnosis, hearing aids, and devices for procedures. Safety devices are devices installed to prevent potential hazards and ensure safety. For example, safety devices include cameras, CCTV, recording devices (recorders), or black boxes. Fintech devices are devices that provide financial services, such as mobile payments. For example, fintech devices include payment devices or POS (point of sales) systems. Weather / environmental devices include devices for monitoring weather / environment.

[0070] Wireless devices 100a to 100f are connected to network 300 via BS200. Artificial Intelligence (AI) technology is applied to wireless devices 100a to 100f, and wireless devices 100a to 100f are connected to AI server 400 via network 300. Network 300 is composed of 3G networks, 4G (e.g., LTE) networks, or 5G (e.g., NR) networks, and beyond 5G networks. Wireless devices 100a to 100f can communicate with each other via BS200 / network 300, but can also communicate directly without going through BS / network (e.g., side-link communication). For example, vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Furthermore, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a~100f.

[0071] Wireless communication / coupling 150a and 150b are performed between wireless devices 100a-100f / BS200-BS200. Here, wireless communication / coupling is performed by various RATs (e.g., 5G NR) such as uplink / downlink communication 150a and sidelink communication 150b (or D2D communication). Wireless communication / coupling 150a and 150b allow wireless devices and BS / wireless devices to send / receive wireless signals from each other. For example, wireless communication / coupling 150a and 150b can send / receive signals via various physical channels. To this end, based on various proposals of the present invention, one of the following is performed: a process of setting various configuration information for sending / receiving wireless signals, a process of various signal processing (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), or a resource allocation process.

[0072] Figure 2 is a block diagram showing an example of a communication device that implements the method according to the present invention.

[0073] Referring to Figure 2, the first wireless device 100 and the second wireless device 200 can send and receive wireless signals to and from external devices via various RATs (e.g., LTE, NR). In Figure 2, {the first wireless device 100 and the second wireless device 200} correspond to {wireless devices 100a~100f and BS200} and / or {wireless devices 100a~100f and wireless devices 100a~100f} in Figure 1.

[0074] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 controls the memory 104 and / or the transceivers 106 and is configured to embody the functions, procedures and / or methods disclosed in this specification. For example, the processor 102 processes information in the memory 104 to generate first information / signals, and then the transceiver 106 transmits a wireless signal containing the first information / signals. The processor 102 also receives a wireless signal containing second information / signals at the transceiver 106 and then stores the information obtained from signal processing of the second information / signals in the memory 104. The memory 104 is linked to the processor 102 and stores various information related to the operation of the processor 102. For example, the memory 104 stores software code containing instructions for performing some or all of the processes controlled by the processor 102, or for performing the procedures and / or methods disclosed in this specification. Here, the processor 102 and memory 104 are part of a communication modem / circuit / chip designed to embody a RAT (e.g., LTE, NR). The transceiver 106 is coupled to the processor 102 and transmits and / or receives radio signals via one or more antennas 108. The transceiver 106 includes a transmitter and / or receiver. The transceiver 106 can also be mixed with an RF (radio frequency) unit. In this disclosure, the term "radio equipment" can also mean a communication modem / circuit / chip.

[0075] The second radio device 200 includes one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 controls the memory 204 and / or the transceivers 206 and is configured to embody the functions, procedures and / or methods disclosed in this specification. For example, the processor 202 processes information in the memory 204 to generate third information / signals, and then transmits a radio signal containing the third information / signals with the transceiver 206. The processor 202 also receives a radio signal containing fourth information / signals with the transceiver 206, and then stores the information obtained from signal processing of the fourth information / signals in the memory 204. The memory 204 is linked to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code containing instructions for performing some or all of the processes controlled by the processor 202, or for performing the procedures and / or methods disclosed in this specification. Here, the processor 202 and memory 204 are part of a communication modem / circuit / chip designed to embody a RAT (e.g., LTE, NR). A transceiver 206 is coupled to the processor 202 and transmits and / or receives radio signals via one or more antennas 208. The transceiver 206 includes a transmitter and / or receiver. The transceiver 206 can also be mixed with an RF unit. In this disclosure, radio equipment can also mean a communication modem / circuit / chip.

[0076] The hardware elements of the wireless devices 100 and 200 will be described in more detail below. However, one or more protocol layers are embodied by one or more processors 102 and 202. For example, one or more processors 102 and 202 embody one or more layers (e.g., a physical PHY layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a functional layer such as a Service data adaptation protocol (SDAP)). One or more processors 102 and 202 generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) by means of the descriptions, functions, procedures, suggestions, and / or methods disclosed in this specification. One or more processors 102 and 202 generate messages, control information, data, or information by means of the functions, procedures, suggestions, and / or methods disclosed in this specification. One or more processors 102, 202 generate signals (e.g., baseband signals) containing PDUs, SDUs, messages, control information, data, or information by the functions, procedures, suggestions, and / or methods disclosed in this specification and provide them to one or more transceivers 106, 206. One or more processors 102, 202 receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data, or information by the descriptions, functions, procedures, suggestions, and / or methods disclosed in this specification.

[0077] One or more processors 102, 202 are also referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 are embodied by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) are included in one or more processors 102, 202. The functions, procedures, suggestions, and / or methods disclosed in this specification are embodied using firmware or software, and the firmware or software is embodied to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, suggestions, and / or methods disclosed in this specification is included in one or more processors 102, 202, or stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The functions, procedures, suggestions, and / or methods disclosed in this specification are embodied using firmware or software in the form of code, instructions, and / or sets of instructions.

[0078] One or more memory units 104, 204 are connected to one or more processors 102, 202 and store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memory units 104, 204 consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memory units 104, 204 are located inside and / or outside one or more processors 102, 202. Furthermore, one or more memory units 104, 204 are connected to one or more processors 102, 202 by various technologies such as wired or wireless connections.

[0079] One or more transceivers 106, 206 can transmit user data, control information, radio signals / channels, etc., as described in the methods and / or flowcharts of this specification to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, radio signals / channels, etc., as described in the descriptions, functions, procedures, suggestions, methods and / or flowcharts of this specification from one or more other devices. For example, one or more transceivers 106, 206 can be connected to one or more processors 102, 202 to transmit and receive radio signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information or radio signals to one or more other devices. Also, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information or radio signals from one or more other devices. One or more transceivers 106, 206 are connected to one or more antennas 108, 208, and are configured by one or more antennas 108, 208 to transmit and receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed in this specification. In this specification, one or more antennas are multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing by one or more processors 102, 202. One or more transceivers 106, 206 convert the user data, control information, radio signals / channels, etc., processed by one or more processors 102, 202, from baseband signals to RF band signals. For this purpose, one or more transceivers 106, 206 include (analog) oscillators and / or filters.For example, under the control of processors 102 and 202, transceivers 106 and 206 convert the OFDM baseband signal up to the carrier frequency using their (analog) oscillators and / or filters, and transmit the OFDM signal converted up to the carrier frequency. Transceivers 106 and 206 receive the OFDM signal at the carrier frequency and, under the control of processors 102 and 202, can convert the OFDM signal down to the OFDM baseband signal using their (analog) oscillators and / or filters.

[0080] In the embodiment of the present invention, the UE operates as a transmitter on the uplink and as a receiver on the downlink. In the embodiment of the present invention, the BS operates as a receiver on the uplink and as a transmitter on the downlink. Hereafter, for the sake of convenience of explanation, unless otherwise specified, the first wireless device 100 will operate as the UE and the second wireless device 200 will operate as the BS. For example, a processor 102 connected to, mounted on, or launched in the first wireless device 100 will perform UE operation according to the embodiment of the present invention, or will be configured to control the transceiver 106 to perform UE operation according to the embodiment of the present invention. A processor 202 connected to, mounted on, or launched in the second wireless device 200 will perform BS operation according to the embodiment of the present invention, or will be configured to control the transceiver 206 to perform BS operation according to the embodiment of the present invention.

[0081] In the present invention, at least one memory (e.g., 104 or 204) stores instructions or programs that, when executed, cause at least one processor operably coupled thereto to perform some embodiment or operation of the present invention.

[0082] In the present invention, a computer-readable storage medium stores at least one instruction or computer program that, when executed by at least one processor, causes at least one processor to perform any of the embodiments or operations of the present invention.

[0083] In the present invention, the processing device or apparatus includes at least one processor and at least one computer memory that is connectable to the at least one processor and, when executed, stores instructions causing the at least one processor to perform some embodiment or operation of the present invention.

[0084] Figure 3 illustrates the frame structure in a 3GPP-based wireless communication system.

[0085] The frame structure in Figure 3 is merely an example, and the number of subframes, slots, and / or symbols in a frame can be varied in various ways. In 3GPP-based wireless communication systems, OFDM numerology (e.g., subcarrier spacing (SCS), transmission time interval (TTI) intervals) are set to differ between multiple cells aggregated for a single UE. For example, if a UE is configured with different SCSs for cells aggregated for a cell, the (absolute time) intervals of time resources (e.g., subframes, slots, or TTI) consisting of the same number of symbols can differ between the aggregated cells. Here, symbols include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or DFT-s-OFDM (discrete Fourier transform-spread-OFDM) symbols).

[0086] Referring to Figure 3, uplink and downlink transmissions consist of frames. Each frame is T f = has a 10ms interval, which is divided into two half-frames of 5ms each. Each half-frame consists of five subframes, and each subframe has an interval (T sf) is 1 ms. Each subframe is divided into slots, and the number of slots in a subframe varies depending on the subcarrier spacing. Each slot is composed of 14 or 12 OFDM symbols based on the CP (cyclic prefix). In the case of normal CP, each slot is composed of 14 OFDM symbols, and in the case of extended CP, each slot is composed of 12 OFDM symbols. Numerology is based on a subcarrier spacing (△f = 2u * 15 kHz) that is exponentially scalable. The following table shows the number of OFDM symbols per slot, the number of slots per frame, and the number of slots according to the subcarrier spacing (△f = 2u * 15 kHz) for normal CP.

[0087]

Table 1

[0088] The following table shows the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe for extended CP according to the subcarrier spacing (△f = 2 u * 15 kHz).

[0089]

Table 2

[0090] A slot contains a plurality (e.g., 14 or 12) of symbols in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a common resource block (CRB) (N start,u grid ) starting from, N size,u grid,x * N RB sc subcarriers and N subframe,usymb A resource grid of OFDM symbols is defined, where N size,u grid,x is the number of resource blocks (RB) in the resource grid, and the subscript x is DL for downlinks and UL for uplinks. RB sc This is the number of subcarriers per RB. In a 3GPP-based wireless communication system, N RB sc It is generally 12. For a given antenna port (p), subcarrier spacing configuration (u), and transmission direction (DL or UL), there is one resource grid. Carrier bandwidth (N) for subcarrier spacing configuration (u) size,u grid The RB is given by higher-level parameters (e.g., RRC parameters). Each element in the resource grid for the antenna port (p) and subcarrier spacing setting (u) is called a Resource Element (RE), and each resource element is mapped to a single complex symbol. Each resource element in the resource grid is uniquely identified by an index (k) in the frequency domain and an index (l) in the time domain that indicates the symbol position relative to a reference point. In 3GPP-based wireless communication systems, RB is defined by 12 consecutive subcarriers in the frequency domain.

[0091] In the 3GPP NR system, RBs are classified into Common Resource Blocks (CRBs) and Physical Resource Blocks (PRBs). CRBs are numbered in an increasing direction from 0 in the frequency domain relative to the subcarrier spacing setting (u). The center of subcarrier 0 of CRB 0 relative to the subcarrier spacing setting (u) coincides with 'point A', which is a common reference point for the resource block grid. In the 3GPP NR system, PRBs are defined within the bandwidth part (BWP) and numbered from 0 to N size BWP,iNumbered down to -1, where i is the number of the bandwidth part. The physical resource blocks (n) within the bandwidth part (i) PRB ) and common resource blocks (n CRB The relationship between ) is as follows: n PRB =n CRB +N size BWP,i Here, N size BWP,i The bandwidth part is a common resource block that starts with CRB 0. A BWP contains multiple consecutive RBs in the frequency domain. A carrier wave contains up to N (e.g., 5) BWPs. An UE is configured as one or more BWPs with a given configuration carrier wave. Of the BWPs configured for an UE, only one is activated at a time. The activated BWP defines the operating bandwidth of the UE within the cell's operating bandwidth.

[0092] The NR frequency band is defined by two types of frequency ranges, FR1 and FR2. FR2 is also called millimeter wave (mmW). The frequency ranges in which NR can operate are distinguished as shown in Table 3.

[0093] [Table 3]

[0094] Figure 4 illustrates a protocol stack in a 3GPP-based wireless communication system.

[0095] Specifically, Figure 4(a) illustrates the user-plane protocol stack of the radio interface between the UE and the base station (BS), and Figure 4(b) illustrates the control-plane protocol stack of the radio interface between the UE and the BS. The control plane refers to the pathway through which control messages used by the UE and the network to manage a call are transmitted. The user plane refers to the pathway through which data generated in the application layer, such as voice data or internet packet data, is transmitted. Referring to Figure 4(a), the user-plane protocol stack is divided into the first layer (layer 1) (i.e., the physical (PHY) layer) and the second layer (layer 2). Referring to Figure 4(b), the control-plane protocol stack is 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 stratum (NAS) layer). Layers 1, 2, and 3 are called the access stratum (AS).

[0096] The NAS control protocol is terminated by the network-side access management function (AMF), which handles authentication, mobility management, security control, and other related functions.

[0097] In 3GPP LTE systems, Layer 2 is divided into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP). In 3GPP NR (New Radio) systems, Layer 2 is divided into the following sublayers: MAC, RLC, PDCP, and Service Data Adaptation Protocol (SDAP). The PHY layer provides the transmission channel to the MAC sublayer, the MAC sublayer provides the logical channel to the RLC sublayer, the RLC sublayer provides the RLC channel to the PDCP sublayer, and the PDCP sublayer provides the radio bearer to the SDAP sublayer. The SDAP sublayer provides QoS flow to the 5G core network.

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

[0099] In a 3GPP NR system, the main services and functions of the RRC sub-tier include: broadcasting system information related to the AS and NAS; paging disclosed by 5GC or NG-RAN; setting up, maintaining, and disconnecting RRC connections between the UE and NG-RAN; security functions including key management; setting up, maintaining, and disconnecting signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (including handover and context transmission; UE cell selection, reselection, and control of cell selection and reselection; mobility between RATs); QoS management functions, UE measurement reporting, and reporting control; detection and recovery from radio link failures; and transmission of NAS messages from the UE to the NAS and from the NAS to the UE.

[0100] In a 3GPP NR system, the main services and functions of the PDCP sub-tier for the user plane include: sequence numbering; header compression and decompression (only in the case of robust header compression (ROHC)); user data transmission; reordering and duplicate detection; sequential transmission; PDCP PDU routing (in the case of split bearer); PDCP SDU retransmission; encryption, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCH status report for RLC AM; PDCP PDU duplication and duplicate discard instructions to lower tiers. The main services and functions of the PDCP sub-tier for the control plane include: sequence numbering; encryption, deciphering and integrity protection; control plane data transmission; reordering and duplicate detection; sequential transmission; PDCP PDU duplication and duplicate discard instructions to lower tiers.

[0101] In the 3GPP NR system, the RLC sub-tier supports three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC settings are applied per logical channel, independent of the pneumatics and / or transmission interval. In the 3GPP NR system, the main services and functions of the RLC sub-tier depend on the transmission mode and include: transmission of higher-tier PDUs; sequence numbering independent of numbering in PDCP (for UM and AM); error correction by ARQ (automatic repeat request) (for AM only); RLC SDU segmentation (for UM and AM) and re-segmentation (for AM only); SDU reassembly (for UM and AM); RLC SDU discard (for UM and AM); RLC re-establishment; and protocol error detection (for AM only).

[0102] In the 3GPP NR system, the main services and functions of the MAC sub-tier include: mapping between logical channels and transmit channels; multiplexing / demultiplexing of MAC SDUs belonging to one or more logical channels to / from transport blocks (TBs) transmitted to / from the PHY tier via the transmit channel; scale information reporting; error correction by HARQ (hybrid automatic repeat request) (one HARQ entity per cell in the case of CA); priority handling between UEs using dynamic scheduling; priority handling between logical channels of a single UE using logical channel priority; and padding. A single MAC entity supports multiple pneumatics, transmit timings, and cells. In logical channel priority, mapping constraints control which pneumatics, cells, and transmit timings a logical channel uses. Different types of data transmission services are provided by MAC. To accommodate these different types of data transmission services, a number of logical channel types are defined, each supporting a specific type of information transmission. Each logical channel type is defined by the type of information transmitted. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used to transmit only control-plane information, while traffic-control channels are used to transmit only user-plane information.The broadcast control channel (BCCH) is a downlink logical channel for broadcasting system control information; the paging control channel (PCCH) is a downlink logical channel for transmitting paging information, system information change notifications, and instructions for ongoing PWS broadcasts; the common control channel (CCCH) is a logical channel for transmitting control information between the UE and the network, and is used by UEs that do not have an RRC connection with the network; the dedicated control channel (DCCH) is a point-to-point bidirectional logical channel for transmitting dedicated control information between the UE and the network, and is used by UEs with an RRC connection; the dedicated traffic channel (DTCH) is a point-to-point logical channel dedicated to a single UE for transmitting user information. DTCHs exist on both uplink and downlink. On the downlink, the connections between logical channels and transmit channels are as follows: BCCH is mapped to BCH; BCCH is mapped to the downlink shared channel (DL-SCH); PCCH is mapped to PCH; CCCH is mapped to DL-SCH; DCCH is mapped to DL-SCH; DTCH is mapped to DL-SCH. On the uplink, the connections between logical channels and transmit channels are as follows: CCCH is mapped to the uplink shared channel (UL-SCH); DCCH is mapped to UL-SCH; DTCH is mapped to UL-SCH.

[0103] Figure 5 shows an example of data flow in a 3GPP NR system.

[0104] In Figure 5, "RB" represents the radio bearer and "H" represents the header. Radio bearers are classified into two groups: data radio bearers (DRBs) for user plane data and signaling radio bearers (SRBs) for control plane data. MAC PDUs are transmitted and received with external devices via the PHY hierarchy using radio resources. MAC PDUs reach the PHY hierarchy in the form of transport blocks.

[0105] In the PHY hierarchy, the uplink transport channels UL-SCH and RACH are mapped to PUSCH and PRACH, respectively, while the downlink transport channels DL-SCH, BCH, and PCH are mapped to PDSCH, the physical broadcast channel (PBCH), and PDSCH, respectively. In the PHY hierarchy, uplink control information (UCI) is mapped to PUCCH, and downlink control information (DCI) is mapped to PDCCH. MAC PDUs related to UL-SCH are transmitted by the UE via PUSCH based on uplink grants, and MAC PDUs related to DL-SCH are transmitted by the BS via PDSCH based on downlink assignments.

[0106] To transmit the data unit of the present invention via the UL-SCH, the UE must have uplink resources available to the UE. To receive the data unit of the present invention via 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 the present invention, uplink resource allocation is also referred to as uplink grant, and downlink resource allocation is also referred to as downlink allocation. Uplink grant is dynamically received by the UE via the PDCCH in an arbitrary connection response, or quasi-persistently configured to the UE by RRC signaling. Downlink allocation is dynamically received by the UE via the PDCCH, or quasi-persistently configured to the UE by RRC signaling from the BS.

[0107] On the uplink, the BS can dynamically allocate resources to the UE via a cell radio network temporary identifier (C-RNTI) on the PDCCH. When the UE's downlink reception is enabled (activity controlled by discontinuous reception, DRX), the UE constantly monitors the PDCCH to find possible grants for uplink transmission. Using the configured grants, the BS can also allocate uplink resources to the UE for initial HARQ transmissions. Two types of configured uplink grants are defined: Type 1 and Type 2. In Type 1, the RRC directly provides the configured uplink grant (including its period). In Type 2, the RRC defines the period of the configured uplink grant while the PDCCH addressed to the configured scheduling RNTI (CS-RNTI) signals and activates or deactivates the configured uplink grant. In other words, PDCCH addressed to CS-RNTI indicates that the upstream link grant can be implicitly reused by a period defined by RRC until the upstream link grant is deactivated.

[0108] In the downlink, the BS can dynamically allocate resources to the UE by means of the C-RNTI on the PDCCH. The UE always monitors the PDCCH to search for possible grants when the UE's downlink reception is enabled (at setup, activity controlled by DRX). Also, using semi-persistent scheduling (SPS), the BS can allocate downlink resources to the UE for initial HARQ transmissions. The RRC signals and activates or deactivates a configured downlink allocation while the PDCCH addressed to the CS-RNTI defines the period of the configured downlink allocation. That is, the PDCCH addressed to the CS-RNTI indicates that the downlink allocation can be implicitly reused according to the period defined by the RRC until the downlink allocation is deactivated.

[0109] <Resource Allocation by PDCCH (i.e., Resource Allocation by DCI)>

[0110] The PDCCH is used to schedule downlink transmissions on the PDSCH and uplink transmissions on the PUSCH, where the DCI on the PDCCH includes: a downlink allocation related to the DL-SCH, at least including modulation and coding format (e.g., modulation and coding scheme (MCS) index (IMCS)), resource allocation, and hybrid ARQ information; or an uplink scheduling grant related to the UL-SCH, including modulation and coding format, resource allocation, and hybrid ARQ information. The size and use of the DCI carried by one PDCCH vary according to the DCI format. For example, in the 3GPP NR system, DCI format 0_0 or DCI format 0_1 is used for scheduling the PUSCH in one cell, and DCI format 1_0 or DCI format 1_1 is used for scheduling the PDSCH in one cell.

[0111] Figure 6 shows examples of PDSCH time domain resource allocation by PDCCH and PUSCH time resource allocation by PDCCH.

[0112] To schedule a PDSCH or PUSCH, the DCI carried by the PDCCH includes a value m for row index m+1 in the allocation table for the PDSCH or PUSCH. Either a predetermined default PDSCH time domain allocation A, B, or C is applied to the allocation table for the PDSCH, or an RRC-configured PDSCH-TimeDomainAllocationList is applied to the allocation table for the PDSCH. Either a predetermined default PUSCH time domain allocation A is applied to the allocation table for the PUSCH, or an RRC-configured PUSCH-TimeDomainAllocationList is applied to the allocation table for the PUSCH. Which PDSCH time domain resource allocation setting to apply and which PUSCH time domain resource allocation table to apply is determined by fixed / predetermined rules (e.g., Table 5.1.2.1.1-1 of 3GPP TS 38.214 v15.3.0, Table 6.1.2.1.1-1 of 3GPP TS 38.214 v15.3.0).

[0113] In the setting of PDSCH time-domain allocation, each indexed row directly defines the slot offset K0, the start and length indicator SLIV or the start symbol S and the allocation length L, and the PDSCH mapping type assumed for PDSCH reception. In the setting of PUSCH time-domain allocation, each indexed row directly defines the slot offset K2, the start and length indicator SLIV or the start symbol S and the allocation length L, and the PUSCH mapping type assumed for PUSCH reception. K0 for PDSCH or K2 for PUSCH is the time difference between the slot where the PDCCH is located and the slot where the PDSCH or PUSCH corresponding to the PDCCH is located. SLIV is a joint indicator of the start symbol S regarding the start of the slot where the PDSCH or PUSCH is located and the number L of consecutive symbols counted from symbol S. In the case of the PDSCH / PUSCH mapping type, there are two mapping types: one is mapping type A where the demodulation reference signal (DMRS) is located in the third or fourth symbol of the slot by mapping RRC signaling, and the other is mapping type B where the DMRS is located in the first allocated symbol.

[0114] The scheduling DCI includes a frequency-domain resource allocation field that provides allocation information regarding the resource blocks used for PDSCH or PUSCH. For example, the frequency-domain resource allocation field provides the UE with information regarding the cell for PDSCH or PUSCH transmission, information regarding the bandwidth part for PDSCH or PUSCH transmission, and information regarding the resource blocks for PDSCH or PUSCH transmission.

[0115] <Resource Allocation by RRC>

[0116] As described above, there are two types of transmissions without dynamic grants on the uplink: configured grant type 1 and configured grant type 2. In the case of configured grant type 1, the uplink grant is provided by the RRC and stored as a configured grant. In the case of configured grant type 2, the uplink grant is provided by the PDCCH and stored or cleared as a configured uplink grant based on L1 signaling that instructs the activation or deactivation of the configured uplink grant. Types 1 and 2 are configured by RRC signaling per serving cell and per BWP. Multiple configurations can be activated simultaneously only on different serving cells. In the case of type 2, activation and deactivation are independent between serving cells. For the same serving cell, the MAC entity is configured as either type 1 or type 2.

[0117] When a set grant type 1 is configured, the UE is provided with at least the following parameters from the BS via RRC signaling:

[0118] - s-RNTI is CS-RNTI for retransmission;

[0119] - Provides a periodicity that gives a set grant type 1 period;

[0120] -timeDomainOffset indicates the resource offset for System frame number (SFN) = 0 in the time domain;

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

[0122] - frequencyDomainAllocation, which provides frequency domain resource allocation; and

[0123] -mcsAndTBS provides IMCS indicating the number of modulations, target code rate, and transport block size. When RRC sets up a set grant type 1 for a serving cell, the UE stores the uplink grant provided by RRC as the set uplink grant for the indicated serving cell and initializes or re-initializes the set uplink grant so that the uplink grant set by timeDomainOffset and S (induced from SLIV) starts and re-occurs periodically. After an uplink grant is set for grant type 1, the UE assumes that the uplink grant recurs in relation to each symbol that satisfies the following: [(SFN*numberOfSlotsPerFrame (numberOfSymbolsPerSlot)+(Slot number in the frame×numberOfSymbolsPerSlot)+symbol number in the slot]=(timeDomainOffset*numberOfSymbolsPerSlot+S+N*periodicity) modulo (1024*numberOfSlotsPerFrame*numberOfSymbolsPerSlot), for all N>=0.

[0124] When a set grant type 2 is configured, the UE is provided with at least the following parameters from the BS via RRC signaling:

[0125] - CS-RNTI is a CS-RNTI for activation, deactivation, and retransmission; and

[0126] -periodicity that provides the period of the set grant type 2. The actual uplink grant is provided to the UE by PDCCH (addressed to CS-RNTI). After the uplink grant is set for the set grant type 2, the UE considers the uplink grant to recur in relation to each symbol that satisfies the following: [(SFN*numberOfSlotsPerFrame*numberOfSymbolsPerSlot)+(Slot number in the frame*numberOfSymbolsPerSlot)+symbol number in the slot]=[(SFNstart time*numberOfSlotsPerFrame*numberOfSymbolsPerSlot+slotstart time*numberOfSymbolsPerSlot+symbol start time )+N*periodicity] modulo (1024×numberOfSlotsPerFrame*numberOfSymbolsPerSlot), for all N>=0, where SFN start time , slot start time and symbol start time These represent the SFN, slot, and symbol of the first transmission opportunity of PUSCH when the configured grant is (re)initialized, respectively. numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively.

[0127] For a configured uplink grant, the HARQ process ID associated with the first symbol of the uplink transmission is derived from the following formula:

[0128] HARQ Process ID=[floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes

[0129] Here, CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slot number in the frame × numberOfSymbolsPerSlot + symbol number in the slot), where numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots and the number of consecutive symbols per slot, respectively, as explicitly stated in TS 38.211. CURRENT_symbol indicates the symbol index of the first transmission opportunity in the recurring sequence. HARQ processes are configured for configured uplink grants if configured uplink grants are activated, and the associated HARQ process ID is smaller than nrofHARQ-Processes.

[0130] For downlinks, the UE is configured from the BS via RRC signaling with SPS for each serving cell and each BWP. Multiple configurations are activated simultaneously on different serving cells. Activation or deactivation of downlink SPS is independent between serving cells. For downlink SPS, the downlink assignment is provided to the UE by the PDCCH and stored or removed based on L1 signaling indicating SPS activation or deactivation. When an SPS is configured, the UE is provided with the following parameters from the BS via RRC signaling:

[0131] - CS-RNTI is a type of CS-RNTI used for activation, deactivation, and retransmission;

[0132] -nrofHARQ-Processe provides the number of HARQ processes configured for SPS;

[0133] - A periodicity that provides the set downlink allocation period for SPS.

[0134] When SPS is deactivated by a higher level, all corresponding settings must also be deactivated.

[0135] After a downlink assignment is set for SPS, the UE assumes that the Nth downlink assignment will occur sequentially in slots that satisfy the following condition: (numberOfSlotsPerFrame*SFN+slot number in the frame)=[(numberOfSlotsPerFrame*SFN] start time +slot start time )+N*periodicity*numberOfSlotsPerFrame / 10] modulo (1024*numberOfSlotsPerFrame), where SFN start time and slot start time These represent the SFN, slot, and symbol of the first transmit of the PDSCH, after the configured downlink assignment has been (re)initialized.

[0136] For configured downlink assignments, the HARQ process ID associated with the slot in which downlink transmission begins is derived from the following formula:

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

[0138] Here, CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + slot number in the frame], where numberOfSlotsPerFrame indicates the number of consecutive slots per frame, as explicitly stated in TS38.211.

[0139] If the cyclic redundancy check (CRC) for the relevant DCI format has been scrambled with 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 that the downlink SPS assigned PDCCH or the configured uplink grant type 2 PDCCH is enabled for scheduling activation or descheduling. DCI format validity verification is achieved when all fields for the DCI format are set according to Table 4 or Table 5. Table 4 exemplifies the specific fields for verifying the validity of the downlink SPS and uplink grant type 2 scheduling activated PDCCH, and Table 5 exemplifies the specific fields for verifying the validity of the downlink SPS and uplink grant type 2 descheduled PDCCH.

[0140] [Table 4]

[0141] [Table 5]

[0142] The actual downlink allocation and actual uplink grant, as well as the corresponding modulation and coding scheme, are provided by resource allocation fields (e.g., a time domain resource allocation field providing a time domain allocation value m, a frequency domain resource allocation field providing frequency resource block allocations, and a modulation and coding scheme field) within the DCI format carried by the scheduling activation PDCCH of the downlink SPS or uplink grant type 2. Once validity is achieved, the UE considers the information in the DCI format to be a valid activation or deactivation of the downlink SPS or the configured uplink grant type 2.

[0143] In the case of an uplink, the processor 102 of the present invention transmits (or controls the transceiver 106 to transmit) a data unit of the present invention based on an uplink grant available to the UE. The processor 202 of the present invention receives (or controls the transceiver 206 to receive) a data unit of the present invention based on an uplink grant available to the UE.

[0144] In the case of a downlink, the processor 102 of the present invention receives (or controls the transceiver 106 to receive) the downlink data of the present invention based on the downlink allocation available to the UE. The processor 202 of the present invention transmits (or controls the transceiver 206 to transmit) the downlink data of the present invention based on the downlink allocation available to the UE.

[0145] Before the data unit of the present invention is transmitted via a wireless interface, physical hierarchical processing is performed on the transmitting side, and the wireless signal carrying the data unit of the present invention is subjected to physical hierarchical processing on the receiving side. For example, a MAC PDU including a PDCP PDU according to the present invention is subjected to physical hierarchical processing as follows.

[0146] Figure 7 shows an example of physical layer processing on the transmitting side.

[0147] The following tables show how transport channels (TrCH) and control information are mapped to the corresponding physical channels. Specifically, Table 6 shows how uplink transport channels are mapped to the corresponding physical channels, Table 7 shows how uplink control channel information is mapped to the corresponding physical channels, Table 8 shows how downlink transport channels are mapped to the corresponding physical channels, and Table 9 shows how downlink control channel information is mapped to the corresponding physical channels.

[0148] [Table 6]

[0149] [Table 7]

[0150] [Table 8]

[0151] [Table 9]

[0152] <encoding>

[0153] Data and control streams to and from the MAC hierarchy are encoded and provided with transport and control services via the radio transmit link at the PHY hierarchy. For example, transport blocks from the MAC hierarchy are encoded into codewords at the transmitting end. Channel coding schemes include miss detection, miss correction, rate matching, interleaving, and a combination of transport channels or control information that are mapped to or separated from physical channels.

[0154] In 3GPP NR systems, the following channel coding schemes are used for different types of TrCHs and different types of control information.

[0155] [Table 10]

[0156] [Table 11]

[0157] For the transmission of downlink transport blocks (i.e., DL MAC PDUs) or uplink transport blocks (i.e., UL MAC PDUs), a transport block CRC sequence is attached to provide miss detection to the receiver. In the 3GPP NR system, communication equipment uses low-density parity check (LDPC) codes when encoding / decoding UL-SCH and DL-SCH. The 3GPP NR system supports two LDPC base graphs (i.e., two LDPC base matrices): LDPC base graph 1 optimized for smaller transport blocks and LDPC base graph 2 optimized for larger transport blocks. LDPC base graph 1 or 2 is selected based on the size of the transport block and the coding rate R. The coding rate R is indicated by the MCS index (IMCS). The MCS index is provided to the UE by a PDCCH that activates or (re)initializes an uplink-configured Grant 2 or downlink SPS, or is provided to the UE by RRC signaling associated with an uplink-configured Grant Type 1, and is dynamically applied to the UE by a PDCCH that schedules a PUSCH or PDSCH. If a transport block with a CRC attached is larger than the maximum code block size for the selected LDPC base graph, the transport block with the CRC attached is divided into code blocks, each code block having an additional CRC sequence attached. The maximum code block sizes for LDPC base graph 1 and LDPC base graph 2 are 8448 bits and 3480 bits, respectively. If a transport block with a CRC attached is not larger than the maximum code block size for the selected LDPC base graph, the transport block with the CRC attached is encoded using the selected LDPC base graph. Each code block of the transport block is encoded using the selected LDPC base graph. The LDPC-coded blocks are then individually rate-matched. Code block concatenation is performed to generate a codeword for transmission on the PDSCH or PUSCH.In the case of PDSCH, up to two codewords (i.e., up to two transmission blocks) are transmitted simultaneously on the PDSCH. PUSCH can be used to transmit UL-SCH data and Layer 1 / 2 control information. Although not shown in Figure 8, Layer 1 / 2 control information can be multiplexed with the codeword for the UL-SCH data.

[0158] <Scrambling and Modulation>

[0159] The bits of the codeword are scrambled and modulated to generate a block of complex-valued modulated symbols.

[0160] <Layer Mapping>

[0161] The complex numerical modulation symbols of a codeword are mapped to one or more multiple input multiple output (MIMO) hierarchies. A codeword can be mapped to up to four layers. Since PDSCH can transmit two codewords, it can support up to eight-layer transmission. Since PUSCH supports a single codeword, it can support up to four-layer transmission.

[0162] <Transform Precoding>

[0163] The downlink transmit waveform is a conventional OFDM using a cyclic prefix (CP). For downlinks, transform precoding (i.e., discrete Fourier transform, DFT) is not applied.

[0164] The uplink transmission waveform is a conventional OFDM that uses a CP with a conversion precoding function that can perform DFT spreading that can be made invalid or valid. In the 3GPP NR system, in the case of the uplink, conversion precoding is selectively applied when it is enabled. Conversion precoding is to spread uplink data in a special manner to reduce the peak-to-average power ratio (PAPR) of the waveform. Conversion precoding is a form of DFT. That is, the 3GPP NR system supports two options for the uplink waveform: one is CP-OFDM (the same as the downlink waveform), and the other is DFT-s-OFDM. Whether the UE uses CP-OFDM or DFT-s-OFDM is set by the BS according to the RRC parameter.

[0165] <Subcarrier mapping>

[0166] Layers are mapped to antenna ports. In the downlink, a mapping in a manner transparent to the layer-antenna port mapping (non-codebook based) is supported, and how beamforming or MIMO precoding is performed is transparent to the UE. In the uplink, both non-codebook based mapping and codebook based mapping are supported for the layer-antenna port mapping.

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

[0168] <OFDM modulation>

[0169] The transmitting communication equipment adds a CP and performs an inverse fast Fourier transform (IFFT) to generate a time-continuous OFDM baseband signal with a TTI for the physical channel and antenna port p and subcarrier spacing u for the OFDM symbol l. For example, for each OFDM symbol, the transmitting communication equipment can perform an IFFT on the complex-valued modulation symbol mapped to the resource block for that OFDM symbol, and then add a CP to the IFFT-generated signal to generate an OFDM baseband signal.

[0170] Upward conversion

[0171] On the transmitting side, the communication equipment converts the OFDM baseband signal for the antenna port p, subcarrier interval setting u, and OFDM symbol l up to the carrier frequency f0 of the cell to which the physical channel is assigned.

[0172] In Figure 2, processors 102 and 202 are configured to perform coding, scrambling, modulation, hierarchical mapping, (uplink) conversion precoding, subcarrier mapping, and OFDM modulation. Processors 102 and 202 control transceivers 106 and 206 connected to them to convert the OFDM baseband signal up to the carrier frequency and generate a radio frequency (RF) signal. The radio frequency signal is transmitted to external devices via antennas 108 and 208.

[0173] Figure 8 shows an example of physical layer processing on the receiving side.

[0174] Physical hierarchical processing on the receiving end is essentially the reverse of physical hierarchical processing on the transmitting end.

[0175] <Frequency down-conversion>

[0176] The communication device on the receiving side receives an RF signal at the carrier frequency via 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.

[0177] <OFDM Demodulation>

[0178] The communication device on the receiving side obtains complex-valued modulation symbols by CP separation (detachment) and FFT. For example, for each OFDM symbol, on the receiving side, the communication device removes the CP from the OFDM baseband signal and performs FFT on the OFDM baseband signal from which the CP has been removed to obtain complex-valued modulation symbols for the antenna port p, the subcarrier spacing u, and the OFDM symbol l.

[0179] <Subcarrier Demapping>

[0180]

[0181] [[ID=X]]

[0182]

[0183] <Multilayer Demapping>

[0184] Subcarrier demapping is performed on the complex-valued modulation symbols to obtain the complex-valued modulation symbols of the corresponding physical channel. For example, the 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 BWP. As another example, the 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 BWP.

[0181] <Inverse Transform Decoding>

[0182] Inverse transform decoding (e.g., IDFT) is performed on the complex-valued modulation symbols of the uplink physical channel when transform precoding is enabled for the uplink physical channel. Inverse transform decoding is not performed for the downlink physical channel and the uplink physical channel for which transform precoding is disabled.

[0183] <Multilayer Demapping>

[0184] Complex-valued modulation symbols are demmapped to one or two codewords.

[0185] <Recovery and Descrambling>

[0186] The complex numerical modulation symbols of the codeword are demodulated into the bits of the codeword and then descrambled.

[0187] <decrypt>

[0188] The codeword is decoded into a transport block. For UL-SCH and DL-SCH, LDPC base graph 1 or 2 is selected based on the size and coding rate of the transport block. The codeword contains one or more coded blocks. Each coded block is decoded into a code block with a CRC attached or a transport block with a CRC attached using the selected LDPC base graph. If the sender splits a code block into a transport block with a CRC attached, the CRC sequence is removed from each of the code blocks with a CRC attached to obtain a code block. The code block is concatenated to the transport block with a CRC attached. The transport block CRC sequence is removed from the transport block with a CRC attached to obtain a transport block. The transport block is transmitted to the MAC hierarchy.

[0189] In the physical hierarchical processing at the transmitting and receiving ends described above, time and frequency domain resources (e.g., OFDM symbols, subcarriers, carrier frequencies) related to subcarrier mapping, OFDM modulation, and frequency up / down conversion are determined based on resource allocation (e.g., uplink grants, downlink allocations).

[0190] For uplink data transmission, the processor 102 of the present invention applies the above-described physical hierarchical processing on the transmitting side to the data unit of the present invention (or controls the transceiver 106 to apply it) and transmits the data unit wirelessly. For downlink data reception, the processor 102 of the present invention applies the above-described physical hierarchical processing on the receiving side to the received wireless signal (or controls the transceiver 106 to apply it) and obtains the data unit of the present invention.

[0191] For downlink data transmission, the processor 202 of the present invention applies the above-described physical hierarchical processing on the transmitting side to the data unit of the present invention (or controls the transceiver 206 to apply it) and transmits the data unit wirelessly. For uplink data reception, the processor 202 of the present invention applies the above-described physical hierarchical processing on the receiving side to the received wireless signal (or controls the transceiver 206 to apply it) and obtains the data unit of the present invention.

[0192] <LCP(Logical channel prioritization)>

[0193] The following section explains Logical Channel Prioritization (LCP) in NR systems.

[0194] The LCP procedure is applied when a new transmission is performed. RRC controls the scheduling of uplink data by signaling for each logical channel: priority, where the priority level decreases as the priority value increases; priorityBitRate, which sets the Prioritized Bit Rate (PBR); and bucketSizeDuration, which sets the Bucket Size Duration (BSD).

[0195] A MAC entity must maintain a variable Bj for each logical channel j. The value of Bj can be negative.

[0196] The MAC entity initializes Bj to 0 when the associated logical channel is configured.

[0197] For each logical channel j, the MAC entity must increment Bj by the product of PBR × T before every instance of the LCP procedure, where T is the elapsed time since Bj was last incremented.

[0198] If the value of Bj is greater than the bucket size (i.e., PBR × BSD), the MAC entity must set Bj to the bucket size.

[0199] When a new transmission is initiated, the MAC entity must allocate resources to the logical channel as follows:

[0200] - Logical channels selected for an uplink grant where Bj > 0 are allocated resources in decreasing priority order. If a logical channel's PBR is set to infinity, the MAC entity must allocate resources for all data available for transmission on that logical channel before satisfying the PBR of the lower-priority logical channels.

[0201] - Reduce Bj by the total size of the MAC SDU provided to the logical channel j mentioned above.

[0202] - If resources remain, all selected logical channels will be applied in descending order of priority (regardless of the Bj value) until all data or uplink grants to the logical channel are consumed (until one of both is consumed first). Logical channels configured with the same priority will be applied similarly.

[0203] If a MAC entity is requested to transmit multiple MAC PDUs simultaneously, or if a MAC entity receives multiple uplink grants within one or more matching PDCCH occasions (in different serving cells), the order in which the grants are processed depends on the UE's implementation.

[0204] Furthermore, the UE must adhere to the following rules a) through d) in the scheduling procedure described above.

[0205] a) If the entire SDU (or partially transmitted SDU or retransmitted RLC PDU) fits the remaining resources of the relevant MAC entity, the UE shall not split the RLC SDU (or partially transmitted SDU or retransmitted RLC PDU).

[0206] b) When the UE partitions an RLC SDU in a logical channel, it must maximize the size of the segment and fill as many grants of the associated MAC entities as possible.

[0207] c) The UE must maximize data transmission.

[0208] d) If a MAC entity is granted a UL grant size of 4 bytes or more while there is data that can be transmitted (except when the UL grant size is less than 7 bytes and an AMD PDU segment must be transmitted), the MAC entity shall not transmit the padding BSR and / or padding alone.

[0209] If an enhancedSkipUplinkTxDynamic is set to true in a MAC entity and the grant pointing to that MAC entity is addressed by C-RNTI, or if an enhancedSkipUplinkTxDynamic is set to true in a MAC entity and the grant pointing to that MAC entity is an uplink CG (Configured grant), then the MAC entity will not generate a MAC PDU for the HARQ entity if there is no multiplexed UCI in the PUSCH transmission, there are no aperiodic CSI requests for that PUSCH, the MAC PDU does not contain a MAC SDU, the MAC PDU contains only periodic BSRs, there is no available data for any LCG (Logical Channel Group), or the MAC PDU contains only padding BSRs.

[0210] If a MAC entity has a skipUplinkTxDynamic setting with a value of true, and the grant pointing to that MAC entity is addressed by C-RNTI, or if the grant pointing to that MAC entity is an uplink CG (Configured grant), and there are no aperiodic CSI requests for that PUSCH, the MAC PDU does not contain a MAC SDU, the MAC PDU contains only periodic BSRs, there is no available data for any LCG (Logical Channel Group), or the MAC PDU contains only padding BSRs, then the MAC entity will not generate a MAC PDU for the HARQ entity.

[0211] <BSR(Buffer Status Reporting)>

[0212] The following section explains BSR (Buffer Status Reporting) in NR systems.

[0213] The BSR procedure is used to provide the serving gNB with information about the uplink data volume of the MAC entity.

[0214] RRC configures the following parameters to control BSR:

[0215] - periodicBSR-Timer;

[0216] - retxBSR-Timer;

[0217] - logicalChannelSR-DelayTimerApplied;

[0218] - logicalChannelSR-DelayTimer;

[0219] -logicalChannelSR-Mask;

[0220] - Logical ChannelGroup.

[0221] Each logical channel can be assigned to an LCG using logicalChannelGroup. The maximum number of LCGs is 8. The MAC entity determines the amount of uplink data available for a logical channel by following the data volume calculation procedures in 3GPP TS 38.322 and 3GPP TS 38.323.

[0222] BSR is triggered when any of the following events 1) through 4) occur.

[0223] 1) When uplink data for a logical channel belonging to a Logical Channel Group (LCG) is available in a MAC entity, but the uplink data belongs to a logical channel with a higher priority than all the logical channels belonging to the LCG that contain the available uplink data, or when none of the logical channels belonging to the LCG contain any available uplink data. In this case, the BSR will be referred to as a "general BSR" below.

[0224] 2) When a UL resource is allocated and the number of padding bits is greater than or equal to the size of the Buffer Status Report (BSR) MAC CE plus the subheader. In this case, the BSR will be referred to as the "Padding BSR" below.

[0225] 3) When the retxBSR-Timer expires and at least one of the logical channels belonging to the LCG contains uplink data. In this case, the BSR will be referred to as the "general BSR" below.

[0226] 4) When the periodicBSR-Timer expires. In this case, the BSR will be referred to as the "periodic BSR" below.

[0227] In particular, if a general BSR triggering event occurs simultaneously for multiple logical channels, each logical channel will trigger a separate general BSR.

[0228] In the case of a general BSR, a MAC entity must start or restart a logicalChannelSR-DelayTimer when a BSR is triggered on a logical channel where logicalChannelSR-DelayTimerApplied is set by a higher level. Otherwise, if logicalChannelSR-DelayTimer is running, the MAC entity must abort it.

[0229] For general and periodic BSRs, when a MAC PDU containing a BSR is constructed, if one or more LCGs have transmittable data, the MAC entity must report a long BSR to all LCGs that have transmittable data. Otherwise, the MAC entity reports a short BSR.

[0230] In the case of a padded BSR, if the number of padding bits is greater than or equal to the size of the short BSR plus the subheader, and less than the size of the long BSR plus the subheader, and if there is data available for transmission when the BSR is constructed in one or more LCGs, and if the number of padding bits is equal to the size of the short BSR plus the subheader, then the MAC entity must report the short truncated BSR of the LCG that has the highest priority logical channel containing data available for transmission. However, if the number of padding bits is not equal to the size of the short BSR plus the subheader, then the MAC entity must report the long truncated BSRs of the LCGs that have logical channels containing data available for transmission in descending order from the highest priority logical channel (whether or not it contains data available for transmission), but in ascending order of LCGID if the priorities are the same.

[0231] Furthermore, if one or more LCGs do not have transmittable data when the BSR is constructed, the MAC entity must report a short BSR. Finally, if the number of padding bits is equal to or greater than the size of the long BSR plus the subheader, the MAC entity must report a long BSR for all LCGs that have transmittable data.

[0232] In the case of a BSR triggered by the expiration of the retxBSR-Timer, the MAC entity considers the logical channel that triggered the BSR to be the highest-priority logical channel with data available for transmission at the time the BSR was triggered.

[0233] If the buffer status report procedure determines that at least one BSR has been triggered and not canceled, and as a result of logical channel prioritization, a UL-SCH resource is available for the new transmission and the UL-SCH resource can accommodate the BSR MAC CE and its subheaders, the MAC entity instructs the multiplexing and assembly procedure to generate the BSR MAC CE, and starts (or restarts) the periodicBSR-Timer and the retxBSR-Timer unless all generated BSRs are long or short truncated BSRs. However, if a general BSR has been triggered and logicalChannelSR-DelayTimer is not running, if there are no UL-SCH resources available for the new transmission, or if a MAC entity is configured on the uplink CG and a general BSR has been triggered on a logical channel where logicalChannelSR-Mask is set to False, or if the UL-SCH resources available for the new transmission do not meet the LCP mapping limits configured for the logical channel that triggered the BSR, the MAC entity must trigger a scheduling request.

[0234] A UL-SCH resource is considered available if the MAC entity has an active configuration for an uplink CG type, or if the MAC entity receives a dynamic uplink grant, or if both of these conditions are met. If the MAC entity determines that a UL-SCH resource is available at a given time, it does not necessarily mean that the UL-SCH resource is available at that time.

[0235] Even if multiple events trigger a BSR, the MAC PDU should contain at most one BSR MAC CE. General BSRs and periodic BSRs take precedence over padding BSRs.

[0236] When the MAC entity receives a grant for new data transmission in any UL-SCH, it shall restart the retxBSR-Timer.

[0237] All triggered BSRs can accommodate all buffered data for which an uplink grant is available for transmission, but may be cancelled if they are not sufficient to additionally accommodate the BSR MAC CE and its sub-header. All BSRs triggered prior to MAC PDU assembly must be cancelled when the MAC PDU is transmitted, and this PDU shall contain a long or short BSR MAC CE including the buffer status up to and including the last event that triggered the BSR prior to MAC PDU assembly.

[0238] The assembly of the MAC PDU can be performed at any time between the reception of the uplink grant and the actual transmission of the MAC PDU. The BSR and SR can be triggered after the assembly of the MAC PDU including the BSR MAC CE and before the transmission of the MAC PDU. Also, the BSR and SR can be triggered during the assembly of the MAC PDU.

[0239] <BSR Enhancement>

[0240] In XR, consideration is being given to whether to introduce a new buffer status report. The new buffer status report reports the buffer status for packets whose remaining time is shorter than or equal to a specific time. The main purpose of the new buffer status report is to schedule as quickly as possible before packets whose remaining time is below a specific time expire. Packets whose remaining time is below a specific time are considered emergency packets.

[0241] Furthermore, in XR, there are plans to consider whether or not to introduce Retransmission-less Configured Grant (CG) for transmitting pose / control data. Retransmission-less CG means that the network does not schedule retransmissions for uplink grants associated with retransmission-less CG after the round trip time (RTT). This means that stable transmission is not guaranteed if data is transmitted during a configured grant occasion associated with retransmission-less CG.

[0242] Considering the above, if a BSR is transmitted during a CG opportunity related to a non-retransmitted CG, the network may not be able to receive the BSR due to poor radio conditions. In this case, the network cannot determine whether the UE has an emergency packet expiring in a short time and cannot schedule an uplink grant for the emergency packet to the UE.

[0243] Therefore, if the UE transmits a BSR during a CG opportunity related to a no-retransmission CG, it is undesirable for the BSR procedure to be canceled.

[0244] Additionally, a BSR is transmitted if all MAC SDUs associated with a new buffer status report are outdated. For example, a BSR is triggered if the remaining discardTimer for MAC SDU 1 through MAC SDU 3 is less than a threshold. However, if the discardTimers for MAC SDU 1 through MAC SDU 3 expire before the uplink grant is received, the UE does not need to transmit a BSR to the network. In this case, the UE should cancel the triggered BSR procedure.

[0245] This disclosure describes the behavior of the UE (or the MAC entities of the UE). In the following description, MAC entities related to the behavior of the UE refer to the UE itself or the MAC entities of the UE.

[0246] According to this disclosure, the UE will not cancel the triggered BSR procedure until it transmits a MAC CE related to the BSR on a new uplink grant that allows retransmission after the Round Trip Time (RTT). Furthermore, the UE will cancel the triggered BSR procedure if all MAC SDUs related to the BSR are outdated.

[0247] The UE triggers a BSR when any of the following conditions are met:

[0248] 1) When the uplink data of a logical channel belonging to a logical channel group (LCG) is available in the MAC entity, but the uplink data belongs to a logical channel with a higher priority than all the logical channels belonging to the LCG that contain the available uplink data.

[0249] 2) When none of the logical channels belonging to the LCG contain any available uplink data.

[0250] 3) When the remaining MAC SDU time is less than the time threshold.

[0251] The remaining time for a MAC SDU may be the remaining discardTimer for the MAC SDU. The discardTimer is started when a PDCP entity receives a PDCP SDU. A MAC SDU is an RLC PDU, and an RLC SDU is a PDCP PDU. A PDU is generated when each entity processes an SDU (e.g., attaches a header). A time threshold can be set in RRC, and the threshold may be in milliseconds.

[0252] If the BSR procedure is triggered and not canceled, the UE transmits a MAC CE related to the BSR to the next uplink grant. In other words, if the BSR is not canceled, each MAC PDU for a new uplink grant will continue to include a MAC CE related to the BSR.

[0253] The MAC CE related to the BSR can be transmitted through all uplink grants (e.g., CG (Configured grant) or DG (Dynamic grant)). For example, if the MAC CE related to the BSR is transmitted through a dynamic uplink grant and the BSR is not cancelled, the MAC CE related to the BSR will be transmitted again through another DG (Dynamic grant) or CG (Configured grant).

[0254] Whether to permit retransmission for the uplink grant can be determined for each HARQ process ID.

[0255] Specifically, whether to permit uplink retransmission is configured for each HARQ process ID for DG (Dynamic grant) and CG (Configured grant). Or, whether to permit retransmission for the uplink grant can be configured for each CG (Configured grant) setting. The meaning of "permit retransmission" refers to the assumption that the UE receives an uplink grant for retransmission after the RTT. That is, if the uplink grant does not permit retransmission, the UE can receive a retransmission grant within the RTT, but cannot receive a retransmission grant after the RTT.

[0256] FIG. 9 shows an example of not permitting retransmission according to the present disclosure. In FIG. 9, it is assumed that the HARQ process ID 1 is set as not permitting retransmission.

[0257] Referring to FIG. 9, at T1, the UE receives a new uplink grant using the HARQ process ID 1.

[0258] At T2, the UE receives an uplink grant using the HARQ process ID 1 for retransmission. In this case, even if the RTT is not over, the UE can receive an uplink grant using the HARQ process ID 1 for retransmission.

[0259] At T3, the UE transmits the MAC PDU to the network.

[0260] At T4, the network does not schedule a retransmission grant using HARQ process ID 1. That is, it is assumed that the UE does not receive an uplink grant using HARQ process ID 1 for retransmission.

[0261] The BSR is cancelled if any of the following conditions (A) to (C) are met.

[0262] (A) When the MAC CE for the BSR is transmitted on the uplink grant using the HARQ process ID for which retransmission is permitted.

[0263] FIG. 10 shows a first example of cancelling the BSR according to the present disclosure. In FIG. 10, it is assumed that HARQ process ID 1 is set to not permit retransmission and HARQ process ID 2 is set to permit retransmission.

[0264] At T1, the BSR is triggered.

[0265] At T2, a new uplink grant associated with HARQ process ID 1 is received, and MAC PDU 1 including the BSR MAC CE is transmitted.

[0266] At T3, a new uplink grant associated with HARQ process ID 2 is received.

[0267] At T4, MAC PDU 2 including the BSR MAC CE is transmitted and the BSR is cancelled.

[0268] At T5, a retransmission uplink grant associated with HARQ process ID 2 is received.

[0269] At T6, MAC PDU 2 is retransmitted.

[0270] (B) If the number of times MAC CEs for BSRs have been transmitted on the uplink grant using HARQ process IDs for which retransmission is not permitted exceeds a threshold. This threshold can be set by RRC signaling or provided by RAN1 signaling.

[0271] Figure 11 shows a second example of canceling the BSR in accordance with this disclosure.

[0272] Referring to Figure 11, we can see that the threshold is set to 3. Also, HARQ process ID 1 is set to disallow retransmissions, while HARQ process ID 2 is set to allow retransmissions.

[0273] At T1, BSR is triggered.

[0274] At T2, a new uplink grant associated with HARQ process ID 1 is received, and a MAC PDU containing the BSR MAC CE is transmitted. That is, the number of transmissions for the BSR MAC CE is 1.

[0275] At T3, a new uplink grant associated with HARQ process ID 1 is received, and a MAC PDU containing a BSR MAC CE is transmitted. In other words, the number of BSR MAC CE transmissions is 2.

[0276] In T4, a new uplink grant associated with HARQ process ID 1 is received, and a MAC PDU containing a BSR MAC CE is transmitted. That is, the number of transmissions for the BSR MAC CE is 3. In this case, since the number of transmissions for the BSR MAC CE is greater than or equal to the threshold, the BSR is canceled.

[0277] (C) When all data in the MAC CE for BSR is outdated. This means canceling the BSR when all data in the MAC CE for BSR is no longer needed for transmission. That is, it means when all discardTimers of all data in the MAC CE for BSR have expired.

[0278] FIG. 12 shows a third example of canceling the BSR according to the present disclosure.

[0279] Referring to FIG. 12, at T1, since the remaining times of MAC SDU 1, MAC SDU 2, and MAC SDU 3 are less than the threshold, the BSR is triggered.

[0280] At T2, since the discardTimer of the PDCP SDU corresponding to MAC SDU 1 has expired, MAC SDU 1 is considered to be outdated.

[0281] At T3, since the discardTimers of the PDCP SDUs corresponding to MAC SDU 2 and MAC SDU 3 have expired, MAC SDU 2 and MAC SDU 3 are considered to be outdated. As a result, since all MAC SDUs related to the triggered BSR have become outdated, the MAC entity cancels the BSR procedure.

[0282] FIG. 13 shows a fourth example of canceling the BSR according to the present disclosure. In FIG. 13, it is assumed that a time threshold is set, the HARQ process ID 1 is set to not allow retransmission, and the HARQ process ID 2 is set to allow retransmission.

[0283] At T1, since the remaining times of MAC SDU 1, MAC SDU 2, and MAC SDU 3 are less than the time threshold, the BSR is triggered.

[0284] At T2, a new uplink grant associated with HARQ process ID 1 is received, and MAC PDU 1, including BSR MAC CE, is transmitted.

[0285] In T3, the discardTimer for the PDCP SDUs corresponding to MAC SDU 1, MAC SDU 2, and MAC SDU 3 has expired, so MAC SDU 1, MAC SDU 2, and MAC SDU 3 are considered outdated. As a result, the MAC entity cancels the BSR procedure because all MAC SDUs associated with the triggered BSR have outdated.

[0286] At T4, a new uplink grant associated with HARQ process ID 2 is received, and MAC PDU 2 without BSR MAC CE is transmitted.

[0287] According to this disclosure, the UE will not cancel the BSR procedure even if it is triggered, until it transmits the MAC CE for the BSR through a new UL grant that allows retransmission after RTT. This enables stable transmission of the BSR, and the network can schedule uplink grants to the UE.

[0288] Furthermore, if all MAC SDUs associated with the BSR are outdated, the UE cancels the triggered BSR. This prevents unnecessary MAC CE transmissions to the BSR.

Claims

1. A method by which a UE (User Equipment) performs an operation in a wireless communication system, When receiving at least one Service Data Unit (SDU) from a higher level, the step of starting at least one discard timer associated with the at least one SDU, The steps include: triggering a status report procedure based on the remaining time of the at least one discard timer associated with the at least one SDU being less than or equal to a threshold; and canceling the triggered status report procedure based on the expiration of all of the at least one discard timers. method.

2. Based on the transmission of a status report MAC CE (control element) containing information about all of the at least one SDU, the triggered status report procedure is canceled. The method according to claim 1.

3. The step further includes transmitting a status report MAC CE (control element) containing information about the at least one SDU, based on the fact that the triggered status report procedure is not canceled and an uplink grant associated with the at least one SDU is available. The method according to claim 1.

4. Based on the expiration of the at least one discard timer, the at least one MAC SDU is discarded. The method according to claim 1.

5. Based on the fact that the number of MAC SDUs received from the higher layer is two or more, the discard timer associated with each of the two or more MAC SDUs is started. The method according to claim 1.

6. UE (User Equipment), At least one processor, and When executed by the aforementioned at least one processor, it includes at least one memory that stores instructions that cause the UE to perform an action, The aforementioned operation is, When receiving at least one Service Data Unit (SDU) from a higher level, the step of starting at least one discard timer associated with the at least one SDU, A step of triggering a status report procedure based on the remaining time of the at least one discard timer associated with the at least one SDU being less than or equal to a threshold, and The step of canceling the triggered status reporting procedure based on the expiration of all of the aforementioned at least one discard timers, UE.

7. Based on the transmission of a status report MAC CE (control element) containing information about all of the at least one SDU, the triggered status report procedure is canceled. The UE according to claim 6.

8. The aforementioned operation is, The step further includes transmitting a status report MAC CE (control element) containing information about the at least one SDU, based on the fact that the triggered status report procedure is not canceled and an uplink grant associated with the at least one SDU is available. The UE according to claim 6.

9. Based on the expiration of the at least one discard timer, the at least one MAC SDU is discarded. The UE according to claim 6.

10. Based on the fact that the number of MAC SDUs received from the higher layer is two or more, the discard timer associated with each of the two or more MAC SDUs is started. The UE according to claim 6.

11. A device for UE (User Equipment), At least one processor, and When executed by the at least one processor, it includes at least one memory that stores instructions for causing the UE to perform an operation, and the operation is When receiving at least one Service Data Unit (SDU) from a higher level, the step of starting at least one discard timer associated with the at least one SDU, A step of triggering a status report procedure based on the remaining time of the at least one discard timer associated with the at least one SDU being less than or equal to a threshold, and The step of canceling the triggered status reporting procedure based on the expiration of all of the aforementioned at least one discard timers, Device.

12. A computer-readable storage medium, The computer-readable storage medium, when executed by at least one processor, includes program instructions that cause a UE (User Equipment) to perform an action. The aforementioned operation is, When receiving at least one Service Data Unit (SDU) from a higher level, the step of starting at least one discard timer associated with the at least one SDU, A step of triggering a status report procedure based on the remaining time of the at least one discard timer associated with the at least one SDU being less than or equal to a threshold, and The step of canceling the triggered status reporting procedure based on the expiration of all of the aforementioned at least one discard timers, A computer-readable storage medium.

Images