Method and apparatus for uplink data compression algorithm based on drop operation in wireless communication system

Abstract

This disclosure relates to a method for operation of a user equipment (UE) in a wireless communication system. Specifically, the method includes the following steps: starting a discard timer for the SDU based on receiving a Service Data Unit (SDU) from an upper layer; applying a compression algorithm to the SDU using a compression buffer; resetting the compression buffer used for the compression algorithm based on the discard timer expiring before transmitting the SDU; and sending an indication indicating that the compression buffer has been reset.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to methods and apparatus for processing uplink data compression (UDC) algorithms based on drop operations in wireless communication systems. Background Technology

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

[0003] [Technical Issues]

[0004] Therefore, the purpose of this disclosure is to provide a method and apparatus for processing uplink data compression (UDC) algorithms based on drop operations in a wireless communication system.

[0005] [Technical Solution]

[0006] The above-mentioned objective of this disclosure can be achieved by a method for operating a user equipment (UE) in a wireless communication system, the method comprising the steps of: starting a discard timer for the SDU based on receiving a Service Data Unit (SDU) from an upper layer; applying a compression algorithm to the SDU using a compression buffer; resetting the compression buffer used for the compression algorithm based on the discard timer expiring before transmitting the SDU; and sending an indication indicating that the compression buffer has been reset.

[0007] Furthermore, a user equipment (UE) in a wireless communication system is proposed, comprising: at least one processor; and at least one computer memory storing instructions that, when executed by the at least one processor, cause the UE to perform the following operations: starting a discard timer for an SDU based on receiving a Service Data Unit (SDU) from an upper layer; applying a compression algorithm to the SDU using a compression buffer; resetting the compression buffer used for the compression algorithm based on the discard timer expiring before transmitting the SDU; and transmitting an indication that the compression buffer has been reset.

[0008] Preferably, based on the timer expiring before the SDU is sent, the UE discards the SDU and triggers a sequence number (SN) gap report associated with the SDU.

[0009] Preferably, based on the existence of at least one subsequent SDU to which the compression algorithm is applied before the compression buffer is reset, the UE discards at least one subsequent SDU without transmission.

[0010] Preferably, the compression algorithm includes an uplink data compression (UDC) algorithm.

[0011] Preferably, based on receiving subsequent SDUs from the upper layer after resetting the compression buffer, the UE applies a compression algorithm to the subsequent SDUs using the reset compression buffer. In this case, the instruction is sent along with the subsequent SDUs.

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

[0013] [Beneficial Effects]

[0014] According to this disclosure, when configuring UDC for a PDCP entity, the PDCP entity can avoid sending PDCP SN gap reports by discarding PDCPSDUs that do not need to be sent, since they would be discarded at the receiver side even if they were successfully sent. In other words, radio resources can be used efficiently.

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

[0016] The accompanying drawings are provided to give a further understanding of this disclosure. The drawings illustrate embodiments of this disclosure and, together with the description, serve to explain the principles of this disclosure: Figure 1 The illustration shows an example of a communication system 1 that applies an embodiment of the present disclosure; Figure 2 This is a block diagram illustrating an example of a communication device capable of performing the methods according to this disclosure; Figure 3 The diagram illustrates an example of a frame structure in a 3GPP-based wireless communication system. Figure 4 The illustration shows an example of a protocol stack in a wireless communication system based on the 3rd Generation Partnership Project (3GPP). Figure 5 This diagram illustrates an example of data flow in a 3GPP New Radio (NR) system. Figure 6 The illustration shows an example of time-domain resource allocation via PDSCH through PDCCH and an example of time-domain resource allocation via PUSCH through PDCCH. Figure 7The diagram illustrates an example of physical layer processing on the transmitting side. Figure 8 The illustration shows an example of physical layer processing at the receiving side; Figure 9 This illustrates the transmission of SN gap reports according to the 3GPP NR standard; Figure 10 An example of a processing compression algorithm according to a first embodiment of the present disclosure is shown; Figure 11 Examples of processing compression algorithms according to a second embodiment of the present disclosure are shown; and Figure 12 A flowchart for operation according to this disclosure is shown. Detailed Implementation

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

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

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

[0020] 3GPP LTE

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

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

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

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

[0025] -3GPP TS 36.300: General Description

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

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

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

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

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

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

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

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

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

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

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

[0037] - 3GPP TS 38.215: Physical Layer Measurements

[0038] - 3GPP TS 38.300: General Description

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

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

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

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

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

[0044] - 3GPP TS 37.324: Service Data Adaptive Protocol (SDAP)

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

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

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

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

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

[0050] In carrier aggregation (CA), two or more carriers (CCs) are aggregated. The UE can receive or transmit simultaneously on one or more CCs, depending on its capabilities. CA supports both continuous and discontinuous CCs. When CA is configured, the UE has only one Radio Point Resource Control (RRC) connection to the network. During RRC connection establishment / re-establishment / handover, one serving cell provides Non-Access Stratum (NAS) mobility information, while during RRC connection re-establishment / handover, another serving cell provides security input. This cell is called the primary cell (PCell). A PCell is a cell operating on the primary frequency, where the UE performs the initial connection establishment procedure or initiates a connection re-establishment procedure. Depending on the UE's capabilities, secondary cells (SCells) can be configured to form a set of serving cells together with the PCell. An SCell is a cell that provides additional radio resources on top of a special cell. Therefore, the set of serving cells configured for a UE always consists of one PCell and one or more SCells. In this disclosure, for dual connectivity (DC) operation, the term "special cell" refers to the PCell of the primary cell group (MCG) or the PSCell of the secondary cell group (SCG), and otherwise the term "special cell" refers to the PCell. The SpCell supports Physical Uplink Control Channel (PUCCH) transmission and contention-based random access and is always active. The MCG is a set of serving cells associated with the primary node, comprising the SpCell (PCell) and optionally one or more SCells. The SCG is a subset of serving cells associated with the secondary node, comprising the PSCell and zero or more SCells, for UEs configured with DC. For UEs in RRC_CONNECTED without CA / DC, only one serving cell consisting of the PCell exists. For UEs in RRC_CONNECTED with CA / DC, the term "serving cell" is used to refer to the set of cells consisting of the SpCell and all SCells.

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

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

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

[0054] Figure 1 The illustration shows an example of a communication system 1 in which embodiments of the present disclosure are applied.

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

[0056] Some use cases may require multiple categories for optimization, while others may focus on only one key performance indicator (KPI). 5G uses a flexible and reliable approach to support such a variety of use cases.

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

[0058] Additionally, one of the most anticipated 5G use cases involves the ability to seamlessly connect embedded sensors across all sectors, known as mMTC (modular machine-type communications). The number of potential IoT devices is expected to reach 20.4 billion by 2020. Industrial IoT is one of the key categories performing key roles in enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure through 5G.

[0059] URLLC includes new services that will transform industries such as autonomous vehicles through remote control of key infrastructure and ultra-reliable / available low-latency links. These levels of reliability and latency are essential for controlling smart grids, automating industry, enabling robotics, and controlling and managing drones.

[0060] 5G is a means of providing streaming speeds rated at hundreds of megabits per second to gigabits per second and can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Delivering TVs with resolutions of 4K or higher (6K, 8K, etc.) as well as virtual reality and augmented reality require such speeds. Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games. Certain applications may require special network configurations. For example, for VR games, game companies need to integrate their core servers into the network operator's edge network servers to minimize latency.

[0061] Along with many use cases for vehicular mobility communications, automobiles are expected to become a significant new driving force in 5G. For example, passenger entertainment demands high-mobility, high-synchronization capacity, and mobile broadband. This is because future users continue to expect high-quality connectivity regardless of their location and speed. Another use case in the automotive sector is AR dashboards. AR dashboards enable drivers to identify objects in the dark in addition to those visible through the windshield, and display distances and movement of objects by overlaying information from conversations with the driver. In the future, wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure, and information exchange between vehicles and other connected devices, such as pedestrian-accompanying devices. Safety systems will guide alternative routes, allowing drivers to drive more safely and reducing the risk of accidents. The next stage will be remotely controlled or autonomous vehicles. This requires very high reliability and very fast communication between different autonomous vehicles and between vehicles and infrastructure. In the future, autonomous vehicles will perform all driving activities, and drivers will only focus on abnormal traffic conditions that vehicles cannot identify. The technological requirements for autonomous vehicles necessitate ultra-low latency and ultra-high reliability, enabling traffic safety to reach levels unattainable by humans.

[0062] Smart cities and smart homes / buildings, as mentioned in the context of a smart society, will be embedded in high-density wireless sensor networks. Distributed networks of smart sensors will identify cost and energy efficiency maintenance conditions in cities or homes. Similar configurations can be implemented for individual households. All temperature sensors, window and heating controllers, burglar alarms, and home appliances will be wirelessly connected. Many of these sensors are typically low in data transmission rate, power, and cost. However, certain types of devices may require real-time HD video for monitoring.

[0063] The highly distributed nature of energy consumption and distribution, including heat and gas, necessitates automated control of distribution sensor networks. Smart grids use digital information and communication technologies to collect information and interconnect sensors to take action based on the collected data. Since this information may include the behavior of supply companies and consumers, smart grids can improve the distribution of fuels such as electricity through methods that are efficient, reliable, economically feasible, production sustainable, and automated. A smart grid can also be viewed as another sensor network with low latency.

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

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

[0066] Logistics and freight tracking is a key use case for mobile communications that utilizes location-based information systems to enable inventory and package tracking anywhere. Logistics and freight use cases typically require low data rates but demand location information with wide coverage and reliability.

[0067] refer to Figure 1 Communication system 1 includes wireless equipment, base stations (BS), and a network. Although Figure 1 The 5G network is illustrated as an example of a network for communication system 1, but the embodiments of this disclosure are not limited to 5G systems and can be applied to future communication systems beyond 5G systems.

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

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

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

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

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

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

[0074] refer to Figure 2 The first wireless device 100 and the second wireless device 200 can send / receive radio signals to / from external devices via various RATs (e.g., LTE and NR). Figure 2 In this context, {first wireless device 100 and second wireless device 200} can correspond to Figure 1 {Wireless devices 100a to 100f and BS 200} and / or {Wireless devices 100a to 100f and Wireless devices 100a to 100f}.

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

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

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

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

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

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

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

[0082] In this disclosure, at least one memory (e.g., 104 or 204) may store instructions or programs that, when executed, cause at least one processor operatively connected thereto to perform operations according to some embodiments or implementations of this disclosure.

[0083] In this disclosure, a computer-readable storage medium stores at least one instruction or computer program that, when executed by at least one processor, causes the at least one processor to perform operations according to some embodiments or implementations of this disclosure.

[0084] In this disclosure, a processing device or apparatus may include at least one processor and at least one computer memory connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some embodiments or implementations of this disclosure.

[0085] Figure 3 The diagram illustrates an example of a frame structure in a 3GPP-based wireless communication system.

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

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

[0088] Table 1

[0089] The table below is based on subcarrier spacing Δf = 2 u 15 kHz, showing the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe used for extended CP.

[0090] Table 2

[0091] A time slot comprises multiple symbols in the time domain (e.g., 14 or 12 symbols). For each parameter set (e.g., subcarrier spacing) and carrier, a definition is defined. Nsize,u grid,x N RB sc Subcarriers and N subframe,u symb A resource grid of OFDM symbols, which begins at a Common Resource Block (CRB) indicated by higher-level signaling (e.g., Radio Resource Control (RRC) signaling). N start,u grid ,in N start,u grid It represents the number of resource blocks in the resource grid, and the index x is DL for downlink and UL for uplink. N RB sc This refers to the number of subcarriers per resource block. In 3GPP-based wireless communication systems, N RB sc Typically 12. For a given antenna port p Subcarrier spacing configuration u A resource grid exists for both the transmission direction (DL or UL) and the subcarrier spacing configuration. u carrier bandwidth N size,u grid Given by higher-level parameters (e.g., RRC parameters). Used for antenna ports. p and subcarrier spacing configuration u Each element in the resource grid is called a resource element (RE), and a complex symbol can be mapped to each RE. Each RE in the resource grid is indexed in the frequency domain. k The index represents the sign position relative to the reference point in the time domain. l Unique identifier. In 3GPP-based wireless communication systems, a resource block is defined by 12 consecutive subcarriers in the frequency domain.

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

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

[0094] Table 3

[0095] Figure 4 The diagram illustrates an example of a protocol stack in a 3GPP-based wireless communication system.

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

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

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

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

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

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

[0102] The RLC sublayer supports three transmission modes: Transparent Mode (TM); Non-Acknowledgment Mode (UM); and Acknowledgment Mode (AM). RLC configuration is based on logical channels, independent of parameter sets and / or transmission duration. In 3GPP NR systems, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper-layer PDUs; sequence numbering independent of sequence numbering in PDCP (UM and AM); error correction via ARQ (AM only); RLC SDU segmentation (AM and UM) and re-segmentation (AM only); SDU reassembly (AM and UM); duplicate detection (AM only); RLC SDU discarding (AM and UM); RLC re-establishment; and protocol error detection (AM only).

[0103] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing MAC SDUs belonging to one or different logical channels into transport blocks (TBs) delivered to the physical layer on the transport channel / demultiplexing MAC SDUs belonging to one or different logical channels from transport blocks (TBs) delivered from the physical layer on the transport channel; scheduling information reporting; error correction via HARQ (one HARQ entity per cell in the case of carrier aggregation (CA); priority handling between UEs via dynamic scheduling; priority handling between logical channels of a UE via logical channel prioritization; and padding. A single MAC entity can support multiple parameter sets, transmission timings, and cells. Mapping restrictions in logical channel prioritization control which parameter set(s), cell(s), and transmission timing(s) a logical channel(s) can use. Different types of data transfer services are provided by the MAC. To accommodate different types of data transfer services, several types of logical channels are defined, each supporting the transfer of a specific type of information. Each logical channel type is defined by the type of information transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used only for transferring control plane information, while traffic channels are used only for transferring user plane information. The Broadcast Control Channel (BCCH) is a downlink logical channel used for broadcasting system control information. The Paging Control Channel (PCCH) is a downlink logical channel used for transferring paging information, system information change notifications, and indications of ongoing PWS broadcasts. The Common Control Channel (CCCH) is a logical channel used to transmit control information between the UE and the network, and is used by UEs without an RRC connection to the network. The Dedicated Control Channel (DCCH) is a point-to-point bidirectional logical channel used between the UE and the network to transmit dedicated control information, 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 transferring user information. DTCH can exist in both the uplink and downlink. In the downlink, the following connections exist between the logical channel and the transport channel: BCCH can be mapped to BCH; BCCH can be mapped to the downlink shared channel (DL-SCH); PCCH can be mapped to PCH; CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In the uplink, the following connections exist between the logical channel and the transport channel: CCCH can be mapped to the uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

[0104] Figure 5 The diagram illustrates a data flow example in a 3GPP NR system.

[0105] exist Figure 5 In this code, "RB" stands for 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 sent to and received from external devices via the PHY layer using radio resources. MAC PDUs arrive at the PHY layer in the form of transport blocks.

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

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

[0108] In UL, the BS can dynamically allocate resources to the UE via the Cell Radio Network Temporary Identifier (C-RNTI) on the PDCCH. The UE constantly monitors the PDCCH to find possible licenses for uplink transmissions when its downlink reception is enabled (an activity managed by Discontinuous Receive (DRX) at configuration time). Furthermore, through the configured licenses, the BS can allocate uplink resources to the UE for initial HARQ transmissions. Two types of configured uplink licenses are defined: Type 1 and Type 2. For Type 1, the RRC directly provides the configured uplink licenses (including periodicity). For Type 2, the RRC defines the period of the configured uplink license, and the PDCCH addressed to the configured scheduling RNTI (CS-RNTI) can signal and activate the configured uplink license, or deactivate it; that is, the PDCCH addressed to the CS-RNTI indicates that the uplink license can be implicitly reused according to the period defined by the RRC until it is deactivated.

[0109] In DL, the BS can dynamically allocate resources to the UE via C-RNTI on the PDCCH. When its downlink reception is enabled (an activity managed by DRX at configuration time), the UE constantly monitors the PDCCH to find possible assignments. Furthermore, through semi-persistent scheduling (SPS), the BS can allocate downlink resources to the UE for initial HARQ transmission: the RRC defines the period for configured downlink assignments, and the PDCCH addressed to the CS-RNTI can signal and activate the configured downlink assignment, or deactivate it. In other words, the PDCCH addressed to the CS-RNTI indicates that the downlink assignment can be implicitly reused according to the period defined by the RRC until it is deactivated.

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

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

[0112] Figure 6 The illustrations show examples of time-domain resource allocation via PDSCH through PDCCH and examples of time-domain resource allocation via PUSCH through PDCCH.

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

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

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

[0116] Resource allocation via RRC

[0117] As described above, in the uplink, there are two types of transmissions without dynamic clearance: configured clearance type 1, where the uplink clearance is provided by the RRC and stored as a configured clearance; and configured clearance type 2, where the uplink clearance is provided by the PDCCH and stored or cleared as a configured uplink clearance based on L1 signaling indicating activation or deactivation of the configured uplink clearance. Type 1 and Type 2 are configured by the RRC per serving cell and per BWP. Multiple configurations can only be activated simultaneously on different serving cells. For Type 2, activation and deactivation are independent within the serving cell. For the same serving cell, the MAC entity is configured with either Type 1 or Type 2.

[0118] When license type 1 is configured, at least the following parameters are provided to the UE via RRC signaling from the BS: - cs-RNTI, which is the CS-RNTI used for retransmission; - Periodicity, which provides periodicity for configured license type 1; - timeDomainOffset, which represents the offset of the resource in the time domain relative to SFN=0; - The timeDomainAllocation value m provides a row index m+1 pointing to the allocation table, indicating the combination of the start symbol S, length L, and PUSCH mapping type; - frequencyDomainAllocation, which provides frequency domain resource allocation; and - mcsAndTBS, which provides IMCS representing modulation order, target code rate, and transport block size. When the RRC configures license type 1 for the serving cell, the UE stores the uplink license provided by the RRC as the uplink license configured for the indicated serving cell, and initializes or reinitializes the configured uplink license. The uplink license can begin in the symbol according to timeDomainOffset and S (derived from SLIV) and repeats periodically. After configuring the uplink license for the configured license type 1, the UE considers the uplink license recurrence to be associated with each symbol: [(SFN [numberOfSlotsPerFrame (numberOfSymbolsPerSlot) + (number of slots in the frame × numberOfSymbolsPerSlot) + number of symbols in the slots] = (timeDomainOffset) numberOfSymbolsPerSlot + S + N Periodic) modulus (1024) numberOfSlotsPerFrame (numberOfSymbolsPerSlot), for all N >= 0.

[0119] When license type 2 is configured, the UE provides at least the following parameters via RRC signaling from the BS: - cs-RNTI, which is used to activate, deactivate, and retransmit CS-RNTI; and - Periodicity, which provides the periodicity of configured license type 2. The actual uplink license is provided to the UE by the PDCCH (addressed to CS-RNTI). After configuring the uplink license for configured license type 2, the UE considers the uplink license recurrence to be associated with each symbol: [(SFN numberOfSlotsPerFrame (numberOfSymbolsPerSlot) + (number of time slots in the frame) [numberOfSymbolsPerSlot + Number of symbols in slot] = [(SFN) 开始时间 numberOfSlotsPerFrame numberOfSymbolsPerSlot + time slot 开始时间 numberOfSymbolsPerSlot + symbol 开始时间 )+ N [Periodic] Modulus (1024 × numberOfSlotsPerFrame) (numberOfSymbolsPerSlot), for all N >= 0, where SFN 开始时间 Time slot 开始时间 and symbols 开始时间These are the SFN, slot, and symbol for the first transmission opportunity of the PUSCH, which is (re)initialized with configured uplink permissions. `numberOfSlotsPerFrame` and `numberOfSymbolsPerSlot` refer to the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively.

[0120] For a configured uplink license, the HARQ process ID associated with the first symbol of the UL transmission is derived from the following equation: HARQ process ID = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes Where CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + number of slots in the frame × numberOfSymbolsPerSlot + number of symbols in the slots), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the number of consecutive slots per frame and the number of consecutive symbols per slot, respectively, as specified in TS 38.211. CURRENT_symbol refers to the symbol index of the first transmission timing of the repeated bundle. If the configured uplink license is activated and the associated HARQ process ID is less than nrofHARQ-Processes, then a HARQ process is configured for the configured uplink license.

[0121] For the downlink, the UE can be configured with Semi-Persistent Scheduling (SPS) by serving cell and by BWP via RRC signaling from the BS. Multiple configurations can only be active simultaneously on different serving cells. Activation and deactivation of DL SPS are independent within the serving cell. For DL ​​SPS, DL assignment is provided to the UE by the PDCCH and is stored or cleared based on L1 signaling indicating SPS activation or deactivation. When SPS is configured, the following parameters are provided to the UE via RRC signaling from the BS: - cs-RNTI, which is used to activate, deactivate and retransmit CS-RNTI; - nrofHARQ-Processes: This specifies the number of HARQ processes configured for SPS; - Periodicity, which provides the periodicity of downlink assignments for SPS configuration.

[0122] When the SPS is released by the upper layer, all corresponding configurations must be released.

[0123] After configuring downlink assignment for SPS, the UE continues to assume that the Nth downlink assignment occurs in the following time slots: (numberOfSlotsPerFrame) SFN + number of slots in the frame) = [(numberOfSlotsPerFrame)] SFN 开始时间 + Time Slot 开始时间 )+N Periodic numberOfSlotsPerFrame / 10] modulo (1024 numberOfSlotsPerFrame), where SFN 开始时间 and time slot 开始时间 These are the SFN and time slot of the first transmission of PDSCH, where the configured downlink assignments are (re)initialized.

[0124] For the configured downlink assignment, the HARQ process ID associated with the slot where DL transmission begins is derived from the following equation: HARQ process ID = [floor (CURRENT_slot × 10 / (numberOfSlotsPerFrame × periodicity))] modulo nrofHARQ-Processes Where CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + number of slots in the frame] and numberOfSlotsPerFrame refers to the number of consecutive slots per frame, as specified in TS 38.211.

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

[0126] [Table 4]

[0127] [Table 5]

[0128] The resource assignment fields in the DCI format carried by the uplink license type 2 and DL SPS activated by the scheduling (e.g., the time-domain resource assignment field providing the time-domain resource assignment value m, the frequency-domain resource assignment field providing the frequency resource block allocation, and the modulation and coding scheme field) provide the actual DL assignment and the actual uplink license, as well as the corresponding modulation and coding scheme. If the verification is successful, the UE will treat the information in the DCI format as a valid activation or release of the DL SPS or the configured uplink license type 2.

[0129] For UL, the processor 102 of this disclosure can transmit (or control transceiver 106 to transmit) the data elements of this disclosure based on uplink clearance available to the UE. The processor 202 of this disclosure can receive (or control transceiver 206 to receive) the data elements of this disclosure based on uplink clearance available to the UE.

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

[0131] The data units of this disclosure undergo physical layer processing at the transmitting side before transmission via the radio interface, and the radio signals carrying the data units of this disclosure undergo physical layer processing at the receiving side. For example, a MAC PDU including a PDCP PDU according to this disclosure may undergo the following physical layer processing.

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

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

[0134] [Table 6]

[0135] [Table 7]

[0136] [Table 8]

[0137] [Table 9]

[0138] <encoding>

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

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

[0141] [Table 10]

[0142] [Table 11]

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

[0144] <Scrambling and Modulation>

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

[0146] <Layer Mapping>

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

[0148] <Transform Precoding>

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

[0150] The UL transmission waveform uses conventional OFDM with CP (Converter-Based Function) featuring transform precoding, which performs DFT (Distributed Fourier Transform) extension that can be disabled or enabled. In 3GPP NR systems, transform precoding can be optionally applied to UL if enabled. Transform precoding extends UL data in a specific way to reduce the peak-to-average power ratio (PAPR) of the waveform. Transform precoding is a form of DFT. In other words, 3GPP NR systems support two options for UL waveforms: CP-OFDM (the same as DL waveforms) and DFT-s-OFDM. Whether the UE must use CP-OFDM or DFT-s-OFDM is configured by the BS via RRC parameters.

[0151] Subcarrier mapping

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

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

[0154] <OFDM modulation>

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

[0156] <Up-conversion>

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

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

[0159] Figure 8 An example of physical layer processing at the receiving side is illustrated.

[0160] The physical layer processing at the receiving side is substantially the inverse of the physical layer processing at the transmitting side.

[0161] <Down-conversion>

[0162] The communication device at the receiving side receives the RF signal at the carrier frequency via the antenna. Transceivers 106 and 206 that receive the RF signal at the carrier frequency down-convert the carrier frequency of the RF signal to baseband to obtain the OFDM baseband signal.

[0163] <OFDM demodulation>

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

[0165] <subcarrier demapping>

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

[0167] <transformed precoding decoding>

[0168] If transform precoding is enabled for the uplink physical channel, transform precoding decoding (for example, IDFT) is performed on the complex-valued modulation symbols of the uplink physical channel. For uplink physical channels and downlink physical channels for which transform precoding is deactivated, transform precoding decoding is not performed.

[0169] <layer demapping>

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

[0171] <demodulation and descrambling>

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

[0173] <decoding>

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

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

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

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

[0178] <Disposal of UDC Algorithm Based on Drop Operation>

[0179] Recently, the 3GPP NR standard has stipulated that when there are buffered SDUs associated with an SN (Sequence Number) higher than the SN of an SDU that was discarded due to the expiration of the discard timer, and these SDUs have not yet been submitted to the lower layer by the RLC, the PDCP Tx entity triggers a PDCP SN gap report.

[0180] In addition, a new PDCP control PDU is introduced. For this new PDCP control PDU, it is assumed that a bitmap indicator is used for PDCP SN gap reporting, the COUNT value is used to indicate the first missing SN, and the receiver state variables are updated when a PDCP SN gap report is received.

[0181] The above convention means that when there are buffered SDUs associated with a PDCP SN higher than that of an SDU that was discarded due to a drop timer expiration, and these SDUs have not yet been submitted to the lower layer by the RLC, the PDCP entity generates a PDCP SN gap report. In other words, the PDCP entity cannot reassign the SN to a newly received PDCP SDU.

[0182] Figure 9 This illustrates the situation where SN gap reports are transmitted according to the 3GPP NR standard.

[0183] Reference Figure 9The PDCP entity submits SDUs associated with SNs 1-3 to the lower layer, but does not submit SDUs associated with SNs 4-9. In this case, if the discardTimer for SDUs associated with SNs 1-6 expires, the PDCP entity cannot reassign SNs 4-6 to newly received SDUs because it has already assigned SNs 7-9. In this situation, the PDCP entity reports a PDCP SN gap.

[0184] However, even if the PDCP entity reports a PDCP SN gap, if the UDC is configured with the PDCP entity, consecutive dropped operation packets may still be lost due to UDC decompression failure. This is because UDC decompression failure can occur even if at least one PDCP SDU compressed by the UDC is not successfully received. In other words, if the PDC PSDU associated with SN 4~SN 6 is dropped before transmission, UDC decompression failure will always occur in the network.

[0185] Therefore, SDUs associated with SN 7 to SN 9 do not need to be transmitted to the network. This is because they are discarded due to UDC decompression failure. There are two options for this situation.

[0186] The first option is for the PDCP entity to discard the SDUs associated with SNs 7 through SN 9, and then reassign SNs 4 through SN 9 to the newly received PDCP SDUs. Furthermore, the PDCP entity resets the UDC compression buffer before reassigning the SNs. This option does not require reporting SN gaps, as no SN gaps will occur.

[0187] The second option is that the PDCP entity does not discard SDUs associated with SNs 6 through SN 9. Then, when an SN gap report is triggered, the PDCP entity resets the UDC compression buffer. This option requires reporting the SN gap. Details of each option are suggested in this disclosure.

[0188] (1) First embodiment (first option)

[0189] According to a first embodiment of this disclosure, the PDCP entity discards the SDU that has been compressed by the compressor, and the PDCP entity reassigns the SN associated with the discarded SDU to the newly received SDU. Furthermore, the PDCP entity resets the compression buffer or context before reassigning the SN.

[0190] Specifically, the PDCP entity is configured with a compression algorithm. This compression algorithm can be UDC, RoHC, EHC, etc.

[0191] When the PDCP entity receives an SDU from the upper layer, it follows the legacy process. During the legacy process, the PDCP entity performs compression / encryption / integrity protection and assigns a serial number (SN) to the SDU. The PDCP entity starts a discard timer for the SDU upon receiving it from the upper layer.

[0192] After executing the legacy procedure, the PDCP entity determines whether to submit the SDU to the lower layer. When to submit the SDU depends on the UE implementation.

[0193] When the discard timer for a given SDU expires, if the SDU was not submitted to a lower layer before the discard timer expired, the PDCP entity checks whether there is a buffered SDU with a higher SN than the SDU that was discarded due to the discard timer expiring. Preferably, the discard timer is started per SDU.

[0194] If there is at least one buffered SDU associated with a SN higher than the one being dropped, the PDCP entity only drops these buffered SDUs for those SDUs for which compression has been performed but not yet committed, even if the drop timer for the buffered SDU has not yet expired. The PDCP entity then performs a reset procedure for the compression buffer or context. Furthermore, the PDCP entity reassigns the SN associated with the buffered SDU.

[0195] When the UDC reset process is executed, the PDCP entity resets the UDC compression buffer to all zeros.

[0196] After resetting the UDC compression buffer, the PDCP entity uses the FR bit in the UDC header to indicate whether the UDC compression buffer has been reset. A value of '1' for the FR bit indicates that this is the first compressed packet after the UDC buffer has been reset.

[0197] When the ROHC reset process is executed, the PDCP entity resets the ROHC protocol used for the uplink and starts in IR state in U mode.

[0198] Figure 10 An example of a processing compression algorithm according to a first embodiment of the present disclosure is shown.

[0199] Reference Figure 10 At T1, the PDCP entity receives three SDUs. The PDCP entity assigns SN 1 to SN 3 to the three received SDUs and starts a discard timer for each SDU associated with SN 1 to SN 3.

[0200] At T2, the PDCP entity submits SDUs associated with SN 1 through SN 3. The PDCP entity then receives three SDUs. The PDCP entity assigns SN 4 through SN 6 to the three received SDUs and starts a discard timer for each SDU associated with SN 4 through SN 6.

[0201] At T3, the PDCP entity receives three SDUs. The PDCP entity assigns SNs 7 through SN 9 to the three received SDUs and starts a discard timer for each SDU associated with SNs 7 through SN 9. Since the discard timer for the SDUs associated with SNs 1 through SN 3 expires, the PDCP entity discards the SDUs associated with SNs 1 through SN 3. The PDCP entity then submits the SDUs associated with SNs 4 through SN 6.

[0202] At T4, the PDCP entity discards the SDUs associated with SNs 4 through SN 6 because their discard timers have expired. Furthermore, the PDCP entity discards the SDUs associated with SNs 7 through SN 9 even if their discard timers have not yet expired. The PDCP entity then performs a reset procedure for the compression buffer or context.

[0203] Finally, at T5, the PDCP entity receives two SDUs. The PDCP entity reassigns SN 7 to SN 8 to the two received SDUs. In this case, the SDU associated with SN 4 is compressed using the compression buffer that was initialized (reset) at T4.

[0204] (2) Second embodiment (second option)

[0205] According to a second embodiment of this disclosure, the PDCP entity discards the SDU that has been compressed by the compressor, and the PDCP entity reassigns the SN associated with the discarded SDU to the newly received SDU. Furthermore, the PDCP entity resets the compression buffer or context before reassigning the SN.

[0206] When the PDCP entity receives an SDU from the upper layer, it follows the legacy process. During the legacy process, the PDCP entity performs compression / encryption / integrity protection / assigns a serial number (SN) to the SDU. The PDCP entity starts a discard timer for the SDU upon receiving it from the upper layer.

[0207] After executing the legacy procedure, the PDCP entity determines whether to submit the SDU to the lower layer. When to submit the SDU depends on the UE implementation.

[0208] When the discard timer for a given SDU expires, if the SDU was not submitted to a lower layer before the discard timer expired, the PDCP entity checks if there is a buffered SDU with a higher SN than the SDU that was discarded due to the discard timer expiring. A discard timer is started for each SDU.

[0209] If at least one buffered SDU is associated with an SDU whose SN is higher than the dropped SDU, the PDCP entity triggers an SN gap report. The SN gap report is sent using a PDCP control PDU, similar to a PDCP status report. The PDCP entity performs a reset procedure for the compression buffer or context.

[0210] When the reset procedure for UDC is performed, the PDCP entity resets the compressed buffer to all zeros.

[0211] After resetting the UDC compression buffer, the PDCP entity uses the FR bit in the UDC header to indicate whether the UDC compression buffer has been reset.

[0212] When the reset procedure for ROHC is executed, the PDCP entity resets the ROHC protocol used for the uplink and starts in IR state in U mode.

[0213] Figure 11 An example of a processing compression algorithm according to a second embodiment of the present disclosure is shown.

[0214] Reference Figure 11 At T1, the PDCP entity receives three SDUs. The PDCP entity assigns SN 1 to SN 3 to the three received SDUs and starts a discard timer for each SDU associated with SN 1 to SN 3.

[0215] At T2, the PDCP entity submits SDUs associated with SN 1 through SN 3. The PDCP entity then receives three SDUs. The PDCP entity assigns SN 4 through SN 6 to the three received SDUs and starts a discard timer for each SDU associated with SN 4 through SN 6.

[0216] At T3, the PDCP entity receives three SDUs. The PDCP entity assigns SNs 7 through SN 9 to the three received SDUs and starts a discard timer for each SDU associated with SNs 7 through SN 9. Since the discard timer for the SDUs associated with SNs 1 through SN 3 expires, the PDCP entity discards the SDUs associated with SNs 1 through SN 3.

[0217] At T4, the PDCP entity triggers an SN gap report because the discard timer for the SDUs associated with SN 4 to SN 6 expires. Additionally, the PDCP entity performs a reset procedure for the compression buffer or context.

[0218] Finally, at T5, the PDCP entity receives two SDUs. The PDCP entity assigns SN 10 to SN 11 to the two received SDUs. In this case, the SDU associated with SN 10 is compressed using the compression buffer that was initialized (reset) at T4.

[0219] Figure 12 A flowchart for operation according to this disclosure is shown.

[0220] Reference Figure 12 At S1201, the UE receives an SDU from the upper layer. Upon receiving the SDU, the UE starts a discard timer for that SDU at S1203.

[0221] Next, at S1205, the UE applies a compression algorithm to the SDU using a compression buffer. Preferably, the compression algorithm includes an uplink data compression (UDC) algorithm.

[0222] Next, at S1207, if the discard timer expires before the SDU is sent, the UE resets the compression buffer used for the compression algorithm. Furthermore, the UE discards the SDU and triggers a sequence number (SN) gap report associated with the SDU.

[0223] Furthermore, if at least one subsequent SDU to which the compression algorithm is applied exists before the compression buffer is reset, the UE discards the at least one subsequent SDU without transmission.

[0224] Finally, at S1209, the UE sends an indication that the compression buffer has been reset.

[0225] According to this disclosure, when configuring UDC for a PDCP entity, the PDCP entity can avoid sending PDCP SN gap reports by discarding SDUs that do not need to be transmitted, because these SDUs would be discarded on the receiver side even if they were successfully transmitted. In other words, radio resources can be used efficiently.

Claims

1. A method comprising: Based on the Service Data Unit (SDU) received from the upper layer, the User Equipment (UE) initiates a discard timer for the SDU; The UE applies a compression algorithm to the SDU using a compression buffer; Based on the expiration of the discard timer before the SDU is sent, the UE resets the compression buffer used for the compression algorithm; as well as The UE sends an indication that the compression buffer has been reset.

2. The method according to claim 1, further comprising: Based on the expiration of the discard timer before the SDU is sent, the SDU is discarded and a sequence number (SN) gap report associated with the SDU is triggered.

3. The method according to claim 1, further comprising: Based on the existence of at least one subsequent SDU to which the compression algorithm is applied before the compression buffer is reset, the at least one subsequent SDU is discarded without transmission.

4. The method according to claim 1, wherein, The compression algorithm includes the uplink data compression (UDC) algorithm.

5. The method according to claim 1, further comprising: Based on the subsequent SDU received from the upper layer after resetting the compression buffer, the compression algorithm is applied to the subsequent SDU using the reset compression buffer. The instruction is sent together with the subsequent SDU.

6. A user equipment (UE), comprising: At least one processor; as well as At least one computer memory storing instructions that, when executed by the at least one processor, cause the UE to perform operations, the operations including: Based on the Service Data Unit (SDU) received from the upper layer, a discard timer is started for the SDU; A compression algorithm is applied to the SDU using a compression buffer; Based on the expiration of the discard timer before sending the SDU, the compression buffer used for the compression algorithm is reset; and Send an indication that the compression buffer has been reset.

7. The UE according to claim 6, wherein, The operation also includes: Based on the expiration of the discard timer before the SDU is sent, the SDU is discarded and a sequence number (SN) gap report associated with the SDU is triggered.

8. The UE according to claim 6, wherein, The operation also includes: Based on the existence of at least one subsequent SDU to which the compression algorithm is applied before the compression buffer is reset, the at least one subsequent SDU is discarded without transmission.

9. The UE according to claim 6, wherein, The compression algorithm includes the uplink data compression (UDC) algorithm.

10. The UE according to claim 6, wherein, The operation also includes: Based on the subsequent SDU received from the upper layer after resetting the compression buffer, the compression algorithm is applied to the subsequent SDU using the reset compression buffer. The instruction is sent together with the subsequent SDU.

11. An apparatus for a user equipment (UE), the apparatus comprising: At least one processor; as well as At least one computer memory storing instructions that, when executed by the at least one processor, cause the UE to perform operations, the operations including: Based on the Service Data Unit (SDU) received from the upper layer, a discard timer is started for the SDU; A compression algorithm is applied to the SDU using a compression buffer; Based on the expiration of the discard timer before sending the SDU, the compression buffer used for the compression algorithm is reset; and Send an indication that the compression buffer has been reset.

12. A non-transitory computer-readable storage medium comprising program instructions that, when executed by at least one processor, cause a user equipment (UE) to perform operations, the operations including: Based on the Service Data Unit (SDU) received from the upper layer, a discard timer is started for the SDU; A compression algorithm is applied to the SDU using a compression buffer; The compression buffer used for the compression algorithm is reset based on the expiration of the discard timer before the SDU is sent; as well as Send an indication that the compression buffer has been reset.

Images