Communication device, processing device and method for sending data unit
By designing an optimized RLC PDU construction and transmission strategy in a wireless communication system, the problems of low data transmission efficiency and large latency caused by limited base station resources are solved, and more efficient data transmission and reduced latency are achieved.
Patent Information
- Application Number
- CN202211679990.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-01-07
- Filing Date
- 2019-01-07
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2039-01-07
AI Technical Summary
After the introduction of new radio communication technology, the number of user equipment provided by the base station to the user equipment increased, resulting in an increase in the amount of data and control information, limited existing resources, making it difficult to efficiently receive and send uplink/downlink data and control information. , especially in latency-sensitive applications, latency becomes an important challenge.
Design a communication device and processing device to create a protocol data unit (PDU) of multiple radio link control service data units (RLC SDUs), and at the time of sending the opportunity, the RLC PDU with the lowest serial number is preferred and the wheel is started The retransmission timer is inquired. When the timer expires or there is no new data, an RLC SDU with the highest serial number is built and sent to improve data transmission efficiency.
The overall throughput of the radio communication system is improved, the latency between the user equipment and the base station is reduced, and more efficient signal transmission and reception is achieved.
Smart Images

Figure CN116032435B_ABST
Abstract
Description
[0001] This application is a divisional application of the invention patent application with the original application number 201980007278.2 (International application number: PCT / KR2019 / 000189, application date: January 7, 2019, invention name: Communication equipment, processing equipment and method for sending data units). Technical Field
[0002] The present disclosure relates to a wireless communication system. Background Art
[0003] As an example of a mobile communication system to which the present disclosure is applicable, a 3rd Generation Partnership Project Long Term Evolution (hereinafter referred to as LTE) communication system is briefly described.
[0004] Figure 1 : is a diagram illustrating an example of a network structure of an E-UMTS as an exemplary radio communication system. The Evolved Universal Mobile Telecommunications System (E-UMTS) is an advanced version of the Universal Mobile Telecommunications System (UMTS), and its basic standardization is currently being performed in 3GPP. The E-UMTS may generally be referred to as a Long Term Evolution (LTE) system. For details of the technical specifications of the UMTS and the E-UMTS, reference can be made to Release 7 and Release 8 of the "3rd Generation Partnership Project; Technical Specification Group Radio Access Network".
[0005] Reference Figure 1 , E-UMTS includes User Equipment (UE), eNode B (eNB) and Access Gateway (AG) located at the end of the network (E-UTRAN) and connected to the external network. The eNB can simultaneously send multiple data streams for broadcast services, multicast services and / or unicast services.
[0006] One or more cells may exist for each eNB. The cell is set to operate in one of the bandwidths such as 1.25, 2.5, 5, 10, 15 and 20 MHz, and provides downlink (DL) or uplink (UL) transmission services to multiple UEs with the bandwidth. Different cells may be set to provide different bandwidths. The eNB controls the transmission of data to multiple UEs or the reception of data from multiple UEs. The eNB sends DL scheduling information of DL data to the corresponding UE to inform the UE of the time domain / frequency domain, coding, data size and information related to hybrid automatic repeat request (HARQ) to send DL data. In addition, the eNB sends UL scheduling information of UL data to the corresponding UE to inform the UE of the time domain / frequency domain, coding, data size and HARQ related information that can be used by the UE. An interface for transmitting user services or controlling services may be used between eNBs. The core network (CN) may include an AG and a network node for user registration of the UE, etc. The AG manages the mobility of the UE on the basis of the tracking area (TA). A TA includes multiple cells. Summary of the invention
[0007] Technical issues
[0008] The introduction of new radio communication technologies has resulted in an increase in the number of user equipments (UEs) to which a base station (BS) provides services in a specified resource area, and has also resulted in an increase in the amount of data and control information sent by the BS to the UE. Since the resources available to the BS for communication with the UE are generally limited, new technologies are needed by which the BS utilizes limited radio resources to efficiently receive / send uplink / downlink data and / or uplink / downlink control information. In particular, overcoming delay or latency becomes an important challenge in applications where performance depends heavily on latency / delay.
[0009] The technical objectives that can be achieved by the present invention are not limited to the contents specifically described above, and based on the following detailed description, those skilled in the art will more clearly understand other technical objectives not described herein.
[0010] Technical Solution
[0011] In one aspect of the present disclosure, there is provided a communication device for transmitting data units in a wireless communication system. The communication device includes a transceiver and a processor configured to control the transceiver. The processor is configured to: construct M radio link control (RLC) protocol data units (PDUs) each including M radio link control (RLC) service data units (SDUs), where M is greater than 1; for a transmission opportunity, deliver to the media access control (MAC) layer only L RLC PDUs of L RLC SDUs having the lowest L sequence numbers (SNs) among the M RLC PDUs, where L < M, and the L RLC PDUs include a first RLC PDU having a poll to trigger a status report at a receiving device; once the first RLC PDU having the poll is delivered to the MAC layer, start a poll retransmission timer; control the transceiver to send the L RLC PDUs to the receiving device; when the poll retransmission timer expires and no new RLC SDU or RLC SDU segment can be sent, construct a second RLC PDU including a second RLC SDU having the highest SN among the SNs of the RLC SDUs delivered to the MAC layer; and control the transceiver to send the second RLC PDU including the second RLC SDU.
[0012] In another aspect of the present disclosure, there is provided a processing device including: at least one processor; and at least one computer memory operatively coupled to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations include: construct M radio link control (RLC) protocol data units (PDUs) each including M radio link control (RLC) service data units (SDUs), where M is greater than 1; for a transmission opportunity, deliver to the media access control (MAC) layer only L RLC PDUs of L RLC SDUs having the lowest L sequence numbers (SNs) among the M RLC PDUs, where L < M and the L RLC PDUs include a first RLC PDU having a poll to trigger a status report at a receiving device; once the first RLC PDU having the poll is delivered to the MAC layer, start a poll retransmission timer; send the L RLC PDUs to the receiving device; when the poll retransmission timer expires and no new RLC SDU can be sent, construct a second RLC PDU including a second RLC SDU having the highest SN among the SNs of the RLC SDUs delivered to the MAC layer; and send the second RLC PDU including the second RLC SDU.
[0013] In another aspect of the present disclosure, there is provided a method for a communication device to transmit data units in a wireless communication system. The method includes: constructing M radio link control (RLC) protocol data units (PDUs) each including M radio link control (RLC) service data units (SDUs), where M is greater than 1; for a transmission opportunity, delivering to a media access control (MAC) layer only L RLC PDUs among the M RLC PDUs that have the lowest L sequence numbers (SNs), where L < M, and the L RLC PDUs include a first RLC PDU having a poll to trigger a status report at a receiving device; once the first RLC PDU having the poll is delivered to the MAC layer, starting a poll retransmission timer; sending the L RLC PDUs to the receiving device; when the poll retransmission timer expires and no new RLC SDUs can be sent, constructing a second RLC PDU including a second RLC SDU having the highest SN among the SNs of the RLC SDUs delivered to the MAC layer; and sending the second RLC PDU including the second RLC SDU.
[0014] In each aspect of the present disclosure, the poll may be included in the second RLC PDU.
[0015] In each aspect of the present disclosure, a status variable may be set to 1 plus the highest SN among the SNs of the M RLC PDUs. The status variable holds the SN to be assigned to a newly generated RLC PDU, and the status variable is updated whenever an RLC PDU including an RLC SDU or the last segment of an RLC SDU with SN = status variable is constructed.
[0016] In each aspect of the present disclosure, a MAC PDU including L RLC PDUs may be constructed. The MAC PDU including L RLC PDUs may be sent during a transmission opportunity.
[0017] In each aspect of the present disclosure, the highest SN among the SNs of the RLC SDUs delivered to the MAC layer is less than the highest SN among the SNs of the M RLC SDUs.
[0018] The above technical solutions are only some parts of the implementation of the present disclosure. Those skilled in the art can obtain and understand various implementations of the technical features incorporated into the present disclosure from the following detailed description of the present disclosure.
[0019] Technical Effects
[0020] In some scenarios, embodiments of the present disclosure may provide one or more of the following advantages. In some scenarios, radio communication signals can be sent and / or received more efficiently. Therefore, the overall throughput of the radio communication system can be improved.
[0021] According to some implementations of the present disclosure, delay / latency occurring during communication between a user equipment and a BS may be reduced.
[0022] Furthermore, signals in new radio access technology systems can be transmitted and / or received more efficiently.
[0023] Those skilled in the art will appreciate that the effects that can be achieved by the present disclosure are not limited to what has been specifically described above, and other advantages of the present disclosure will be more clearly understood from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] The accompanying drawings are included to provide a further understanding of the invention and illustrate embodiments of the invention and together with the description serve to explain the principle of the invention.
[0025] Figure 1 is a diagram illustrating an example of a network structure of an Evolved Universal Mobile Telecommunications System (E-UMTS) as an exemplary radio communication system;
[0026] Figure 2 is a block diagram illustrating an example of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN);
[0027] Figure 3 is a block diagram depicting an example of the architecture of a typical E-UTRAN and a typical EPC;
[0028] Figure 4 An example of a protocol stack for a 3GPP-based communication system is illustrated;
[0029] Figure 5 An example of a frame structure in a 3GPP-based wireless communication system is illustrated;
[0030] Figure 6 An example of data flow in a 3GPP LTE system is illustrated;
[0031] Figure 7 An example of data flow in a 3GPP NR system is illustrated;
[0032] Figure 8 A model of an Acknowledged Mode (AM) Radio Link Control (RLC) entity in a 3GPP LTE system is illustrated;
[0033] Fig. 9 illustrates a model of an AM RLC entity that may be used in an implementation of the present disclosure;
[0034] Fig.10 An example of data transmission according to an implementation of the present disclosure is illustrated; and
[0035] Fig.11 is a block diagram illustrating an example of a communication device that can perform the method of the present disclosure. DETAILED DESCRIPTION
[0036] Although wireless communication technology has been developed as LTE based on Wideband Code Division Multiple Access (WCDMA), the demands and expectations of users and service providers are rising. In addition, considering other radio access technologies being developed, new technology development is needed to ensure high competitiveness in the future. It is necessary to reduce the cost per bit, increase service availability, flexibly use frequency bands, simplify the structure, open interface, appropriate power consumption of UE, etc.
[0037] As more and more communication devices require greater communication capacity, improved mobile broadband communication is required compared to existing RATs. In addition, massive machine type communication (MTC) that provides various services by connecting many devices and objects is one of the main issues to be considered in next-generation communications. In addition, communication system design considering services / UEs that are sensitive to reliability and latency is under discussion. The introduction of next-generation RATs that consider such advanced mobile broadband communication, massive MTC (mMTC), and ultra-reliable and low-latency communication (URLLC) is under discussion.
[0038] Reference will now be made in detail to exemplary implementations of the present disclosure, examples of which are illustrated in the accompanying drawings. The detailed description given below with reference to the accompanying drawings is intended to explain exemplary implementations of the present disclosure, rather than to illustrate the only implementations that can be implemented according to the present disclosure. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, it will be apparent to those skilled in the art that the present disclosure may be practiced without these specific details.
[0039] The following techniques, devices and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented by radio technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented by radio technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of the Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE uses OFDMA in DL and SC-FDMA in UL. LTE-Evolution (LTE-A) is an evolved version of 3GPP LTE. For ease of description, the implementation of the present disclosure is described for a 3GPP-based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP-based system, various aspects of the present disclosure not limited to a 3GPP-based system are applicable to other mobile communication systems.
[0040] For example, the present disclosure can be applied to contention-based communications such as Wi-Fi, and non-contention-based communications, such as in a 3GPP-based system, where the BS allocates DL / UL time / frequency resources to the UE, and the UE receives DL signals and sends UL signals according to the resource allocation of the BS. In a non-contention-based communication scheme, an access point (AP) or a control node for controlling the AP allocates resources for communication between the UE and the AP, while in a contention-based communication scheme, communication resources are occupied by competition between UEs that wish to access the AP. A contention-based communication scheme will now be briefly described. One type of contention-based communication scheme is carrier sense multiple access (CSMA). CSMA refers to a probabilistic medium access control (MAC) protocol for a node or communication device to confirm that there is no other service on the same shared transmission medium before sending a service on a shared transmission medium (also called a shared channel) such as a frequency band. In CSMA, before attempting to send a service to a receiving device, the sending device determines whether another transmission is being performed. In other words, before attempting to perform a transmission, the sending device attempts to detect whether there is a carrier from another sending device. When the carrier is intercepted, the transmitting device waits for another transmitting device that is performing transmission to complete transmission before executing its transmission. Therefore, CSMA can be a communication scheme based on the principle of "listen before sending" or "listen before speaking". The scheme for avoiding conflicts between transmitting devices in the contention-based communication system using CSMA includes carrier sense multiple access with collision detection (CSMA / CD) and / or carrier sense multiple access with collision avoidance (CSMA / CA). CSMA / CD is a collision detection scheme in a wired local area network (LAN) environment. In CSMA / CD, a personal computer (PC) or server that wishes to communicate in an Ethernet environment first confirms whether communication occurs on the network, and if another device carries data on the network, the PC or server waits and then sends data. That is, when two or more users (e.g., PC, UE, etc.) send data simultaneously, conflicts occur between simultaneous transmissions, and CSMA / CD is a scheme for flexibly sending data by monitoring conflicts. The transmitting device using CSMA / CD adjusts its data transmission by using specific rules to intercept the data transmission performed by another device. CSMA / CA is a MAC protocol specified in the IEEE 802.11 standard. A wireless LAN (WLAN) system that complies with the IEEE 802.11 standard does not use CSMA / CD, which has been used in the IEEE 802.3 standard, but uses CA, a collision avoidance scheme. A transmitting device always listens to the carrier of the network, and if the network is empty, the transmitting device waits for a determined time according to its registered position in the list, and then transmits data. Various methods are used to determine the priority of the transmitting device in the list and reconfigure the priority.In systems according to certain versions of the IEEE 802.11 standard, collisions may occur, and in such cases, a collision sensing process is performed. A transmitting device using CSMA / CA uses specific rules to avoid collisions between its data transmission and that of another transmitting device.
[0041] For the terms and techniques used in the present disclosure and not specifically described in the terms of the present disclosure, reference may be made to wireless communication standard documents published before the present disclosure. For example, reference may be made to the following documents.
[0042] 3GPP LTE
[0043] -3GPP TS 36.211: Physical channels and modulation
[0044] -3GPP TS 36.212: Multiplexing and channel coding
[0045] -3GPP TS 36.213: Physical layer processing
[0046] -3GPP TS 36.214: Physical layer; Measurement
[0047] -3GPP TS 36.300: General description
[0048] -3GPP TS 36.304: User Equipment (UE) processing in idle mode
[0049] -3GPP TS 36.314: Layer 2 - Measurement
[0050] -3GPP TS 36.321: Medium Access Control (MAC) Protocol
[0051] -3GPP TS 36.322: Radio Link Control (RLC) protocol
[0052] -3GPP TS 36.323: Packet Data Convergence Protocol (PDCP)
[0053] -3GPP TS 36.331: Radio Resource Control (RRC) protocol
[0054] 3GPP NR
[0055] -3GPP TS 38.211: Physical channels and modulation
[0056] -3GPP TS 38.212: Multiplexing and channel coding
[0057] -3GPP TS 38.213: Physical layer processing for control
[0058] -3GPP TS 38.214: Physical layer processing for data
[0059] -3GPP TS 38.215: Physical layer measurements
[0060] -3GPP TS 38.300: General description
[0061] -3GPP TS 38.304: User Equipment (UE) handling in idle mode and RRC inactive state
[0062] -3GPP TS 38.321: Medium Access Control (MAC) Protocol
[0063] -3GPP TS 38.322: Radio Link Control (RLC) protocol
[0064] -3GPP TS 38.323: Packet Data Convergence Protocol (PDCP)
[0065] -3GPP TS 38.331: Radio Resource Control (RRC) protocol
[0066] -3GPP TS 37.324: Service Data Adaptation Protocol (SDAP)
[0067] -3GPP TS 37.340: Multiple Connectivity; General Description
[0068] In the present disclosure, a user equipment (UE) may be a fixed or mobile device. Examples of UE include various devices that send user data and / or various control information to a base station (BS) and receive user data and / or various control information from a base station (BS). UE may be referred to as a terminal equipment (TE), a mobile station (MS), a mobile terminal (MT), a user terminal (UT), a subscriber station (SS), a wireless device, a personal digital assistant (PDA), a wireless modem, a handheld device, etc. In addition, in the present disclosure, a BS generally refers to a fixed station that communicates with a UE and / or another BS and exchanges various data and control information with the UE and / or another BS. A BS may be referred to as an advanced base station (ABS), a node B (NB), an evolved node B (eNB), a base transceiver system (BTS), an access point (AP), a processing server, etc. In particular, a BS of UMTS is referred to as an NB, a BS of EPC / LTE is referred to as an eNB, and a BS of a new radio (NR) system is referred to as a gNB.
[0069] In the present disclosure, a node refers to a fixed point that can send / receive a radio signal through communication with a UE. Various types of BSs can be used as nodes regardless of their terms. For example, a BS, a nodeB (NB), an e-nodeB (eNB), a micro cell eNB (PeNB), a home eNB (HeNB), a repeater, a transponder, etc. can be a node. In addition, a node may not be a BS. For example, a node may be a radio remote head (RRH) or a radio remote unit (RRU). An RRH or RRU generally has a power level lower than that of a BS. Since an RRH or RRU (hereinafter, RRH / RRU) is generally connected to a BS via a dedicated line such as an optical cable, cooperative communication between RRH / RRU and a BS can be smoothly performed compared to cooperative communication between BSs connected via radio lines. Each node is equipped with at least one antenna. The antenna may include a physical antenna or represent an antenna port or a virtual antenna.
[0070] In the present disclosure, the term "cell" may refer to a geographical area to which one or more nodes provide a communication system, or to a radio resource. A "cell" of a geographical area may be understood as a coverage range in which a node can use a carrier to provide a service, 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 resources and uplink resources (e.g., a combination of a downlink (DL) component carrier (CC) and an uplink (UL) CC). A cell may be configured only by downlink resources, or may be configured by downlink resources and uplink resources. Since the DL coverage range as a range in which a node can send a valid signal and the UL coverage range as a range in which a node can receive a valid signal from a UE depend on the carrier that carries the signal, the coverage range of a node may be associated with the coverage range of a "cell" of the radio resource used by the node. Therefore, the term "cell" may sometimes be used to represent the service coverage range of a node, to represent a radio resource at other times, or to represent the range in which a signal using a radio resource can reach an effective strength at other times.
[0071] In carrier aggregation (CA), two or more CCs are aggregated. The UE can receive or transmit simultaneously on one or more CCs depending on its capabilities. CA is supported for both continuous CCs and non-continuous CCs. When CA is configured, the UE has only one radio resource control (RRC) connection with the network. During RRC connection establishment / reconstruction / switching, one serving cell provides non-access stratum (NAS) mobility information, and during RRC connection reconstruction / switching, one serving cell provides security input. This cell is called a primary cell (PCell). A PCell is a cell operating on a primary frequency on which the UE performs an initial connection establishment process or initiates a connection reconstruction process. Depending on the capabilities of the UE, a secondary cell (SCell) 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 the UE always consists of one PCell and one or more SCells. For dual-connection operation, the term "Special Cell (SpCell)" refers to a PCell of a primary cell group (MCG) or a PSCell of a secondary cell group (SCG). SpCell supports PUCCH transmission and contention-based random access and is always activated. MCG is a set of serving cells associated with the master node, including SpCell (PCell) and optionally one or more SCells. For UEs configured with dual connectivity (DC), SCG is a subset of serving cells associated with the secondary node, including PSCell and zero or more SCells. For UEs in RRC_CONNECTED that are not configured with CA / DC, there is only one serving cell consisting of PCell. For UEs in RRC_CONNECTED that are configured with CA / DC, the term "serving cell" is used to refer to the set of cells including SpCell and all SCells. In DC, two MAC entities are configured in the UE: one for MCG and one for SCG.
[0072] In the present disclosure, "PDCCH" may refer to PDCCH, EPDCCH (in a subframe when configured), MTC PDCCH (MPDCCH), for RN to R-PDCCH with a configured and unsuspended R-PDCCH, or for NB-IoT to narrowband PDCCH (NPDCCH).
[0073] In the present disclosure, monitoring a channel means attempting to decode the channel. For example, monitoring a PDCCH means attempting to decode a PDCCH (or a PDCCH candidate).
[0074] In the present disclosure, for dual connectivity (DC) operation, the term "special cell" refers to the PCell of the main cell group (MCG) or the PSCell of the secondary cell group (SCG), otherwise the term special cell refers to the PCell. The MCG is a group of service cells associated with a main BS that terminates at least the S1-MME, and the SCG is a group of service cells associated with a secondary BS that provides additional radio resources to the UE but is not the main BS. The SCG includes a primary SCell (PSCell) and optionally one or more SCells. In dual connectivity, two MAC entities are configured in the UE: one for the MCG and one for the SCG. Each MAC entity is configured with a service cell that supports PUCCH transmission and contention-based random access through RRC. In this specification, the term SpCell refers to such a cell, and the term SCell refers to other service cells. The term SpCell refers to the PCell of the MCG or the PSCell of the SCG, depending on whether the MAC entity is associated with the MCG or SCG, respectively.
[0075] In the present disclosure, "C-RNTI" refers to cell RNTI, "SI-RNTI" refers to system information RNTI, "P-RNTI" refers to paging RNTI, "RA-RNTI" refers to random access RNTI, "SC-RNTI" refers to single cell RNTI, "SL-RNTI" refers to side link RNTI, "SPS C-RNTI" refers to semi-persistent scheduling C-RNTI, and "CS-RNTI" refers to configured scheduling RNTI.
[0076] Figure 2 1 is a block diagram illustrating an example of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UMTS may also be referred to as an LTE system. Communication networks are widely deployed to provide various communication services such as voice over IMS and packet data (VoIP).
[0077] like Figure 2 As shown, the E-UMTS network includes an evolved UMTS terrestrial radio access network (E-UTRAN), an evolved packet core (EPC), and one or more user equipments. The E-UTRAN may include one or more evolved NodeBs (eNodeBs) 20, and a plurality of user equipments (UEs) 10 may be located in one cell. One or more E-UTRAN mobility management entities (MMEs) / system architecture evolution (SAE) gateways 30 may be located at the end of the network and connected to an external network.
[0078] As used herein, "downlink" refers to communications from the eNB 20 to the UE 10, and "uplink" refers to communications from the UE to the eNB.
[0079] Figure 3 is a block diagram depicting an example of the architecture of a typical E-UTRAN and a typical EPC.
[0080] like Figure 3 As shown in FIG, eNB 20 provides endpoints of a user plane and a control plane for UE 10. MME / SAE gateway 30 provides endpoints of session and mobility management functions for UE 10. eNB and MME / SAE gateway may be connected via an S1 interface.
[0081] The eNB 20 is generally a fixed station that communicates with the UE 10 and may also be referred to as a base station (BS) or an access point. One eNB 20 may be deployed per cell. An interface for transmitting user traffic or control traffic may be used between the eNBs 20.
[0082] The MME provides various functions including: NAS signaling to the eNB 20, NAS signaling security, AS security control, CN node inter-signaling for mobility between 3GPP access networks, idle mode UE reachability (including control and execution of paging retransmission), tracking area list management (for UEs in idle and active modes), PDN GW and serving GW selection, MME selection for handover with MME change, SGSN selection for handover to 2G or 3G 3GPP access network, roaming, authentication, bearer management functions including dedicated bearer establishment, support for PWS (including ETWS and CMAS) message transmission. The SAE gateway host provides various functions including: packet filtering based on each user (through, for example, deep packet inspection), lawful interception, UE IP address allocation, transport layer packet marking in the downlink, UL and DL service layer charging, gates and rate implementation, DL rate implementation based on APN-AMBR. For clarity, the MME / SAE gateway 30 will be referred to as a "gateway" in this article, but it should be understood that the entity includes the MME and the SAE gateway.
[0083] A plurality of nodes may be connected via an S1 interface between the eNB 20 and the gateway 30. The eNBs 20 may be connected to each other via an X2 interface, and neighboring eNBs may have a mesh network structure having the X2 interface.
[0084] As shown, the eNB 20 may perform the following functions: selection of a gateway 30, routing, scheduling and transmission of paging messages to the gateway during radio resource control (RRC) activation, scheduling and transmission of broadcast channel (BCCH) information, dynamic allocation of resources in uplink and downlink to UEs, configuration and provision of eNB measurements, radio bearer control, radio admission control (RAC), and connection mobility control in the LTE_ACTIVE state. In the EPC, and as described above, the gateway 30 may perform the following functions: paging initiation, LTE-IDLE state management, encryption of the user plane, system architecture evolution (SAE) bearer control, and encryption and integrity protection of non-access stratum (NAS) signaling.
[0085] EPC includes Mobility Management Entity (MME), Serving Gateway (S-GW) and Packet Data Network Gateway (PDN-GW). MME has information about the connection and capabilities of UE and is mainly used to manage the mobility of UE. S-GW is a gateway with E-UTRAN as the endpoint, while PDN-GW is a gateway with Packet Data Network (PDN) as the endpoint.
[0086] It is expected that in the near future, a fully mobile and connected society will be characterized by a huge increase in connectivity, traffic, and a wider range of usage scenarios. Some typical trends include the explosive growth of data services, the massive increase in connected devices, and the continuous emergence of new services. In addition to market demand, the mobile communication society itself requires the sustainable development of the ecosystem, which creates a need to further improve system efficiency, such as spectrum efficiency, energy efficiency, operational efficiency, and cost efficiency. In order to meet the above growing needs of the market and the mobile communication society, the next generation of access technology is expected to appear in the near future.
[0087] Building on the success of IMT-2000 (3G) and IMT-Evolution (4G), 3GPP has been working on the development of IMT-2020 (5G) since September 2015. 5G New Radio (NR) is expected to extend and support diverse use cases and applications that will continue to exceed the current IMT-Evolution standards, such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), and massive machine type communications (mMTC). eMBB targets high data rate mobile broadband services, such as seamless data access indoors and outdoors, and augmented reality (AR) / virtual reality (VR) applications; URLLC is defined for applications with strict latency and reliability requirements, such as vehicle communications that enable autonomous driving and control networks in factories; and mMTC is the foundation for IoT (Internet of Things) connectivity, allowing for infrastructure management, environmental monitoring, and healthcare applications.
[0088] Figure 4 An example of a protocol stack in a 3GPP-based wireless communication system is illustrated.
[0089] Specifically, Figure 4 (a) in FIG. 1 illustrates an example of a radio interface user plane protocol stack between a UE and a base station (BS), and Figure 4 (b) in FIG. 1 illustrates a radio interface control plane protocol stack between a UE and a base station (BS). The control plane refers to a path for transmitting control messages used to manage calls by the UE and the network. The user plane refers to a path for transmitting data generated in the application layer (e.g., voice data or Internet packet data). Figure 4 In (a), the user plane protocol stack can be divided into the first layer (layer 1) (ie, the physical (PHY) layer) and the second layer (layer 2). Figure 4 In (b), the control plane protocol stack can be divided into layer 1 (ie, PHY layer), layer 2, layer 3 (eg, radio resource control (RRC) layer), and non-access stratum (NAS) layer. Layer 1, layer 2, and layer 3 are called access stratum (AS).
[0090] In 3GPP LTE system, layer 2 is divided into the following sublayers: medium access control (MAC), radio link control (RLC), and packet data convergence protocol (PDCP). In 3GPP New Radio (NR) system, 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 QoS flows to the 5G core network.
[0091] In 3GPP NR systems, the main services and functions of SDAP include: mapping between QoS flows and data radio bearers; marking QoS flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each separate PDU session.
[0092] 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 5GC or NG-RAN; establishing, maintaining and releasing RRC connections between UE and NG-RAN; security functions including key management; establishing, configuring, maintaining and releasing signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (including: handover and context transfer; UE cell selection and reselection and control of cell selection and reselection; inter-RAT mobility); QoS management functions; UE measurement reporting and control of reporting; detecting and recovering from radio link failures; NAS message transmission from UE to NAS / from NAS to UE.
[0093] 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; transmission of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in the case of split bearer); retransmission of PDCP SDU; encryption, decryption and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status report for RLC AM; PDCP PDU duplication and duplicate discard indication to the lower layer. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; encryption, decryption and integrity protection; transmission of control plane data; reordering and duplicate detection; in-order delivery; PDCP PDU duplication and duplicate discard indication to the lower layer.
[0094] In 3GPP NR systems, the RLC sublayer supports the following three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC configuration is for each logical channel and does not depend on 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: delivery of upper layer PDUs; sequence numbering independent of sequence numbering in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDUs (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC reconstruction; and protocol error detection (AM only).
[0095] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing of MAC SDUs belonging to one or different logical channels in transport blocks (TBs) delivered to the physical layer on the transport channel / demultiplexing of 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 through HARQ (one HARQ entity per cell in the case of carrier aggregation (CA); priority handling between UEs with the help of dynamic scheduling; priority handling between logical channels of a UE with the help of logical channel prioritization; padding. A single MAC entity can support multiple parameter sets, transmission timings, and cells, and the mapping restrictions in the logical channel prioritization control which parameter sets, cells, and transmission timings the logical channel can use. Different types of data transmission services are provided by MAC. In order to accommodate different types of data transmission services, multiple types of logical channels are defined, that is, each supports the transmission of specific types of information. Each logical channel type is defined by the type of information transmitted. Logical channels are divided into two groups: control channels and traffic channels. The control channel is used only for the transmission of control plane information, while the traffic channel is used only for the transmission of user plane information. The Broadcast Control Channel (BCCH) is a downlink logical channel used to broadcast system control information, the Paging Control Channel (PCCH) is a downlink logical channel that transmits paging information, system information change notifications, and indications of ongoing PWS broadcasts, the Common Control Channel (CCCH) is a logical channel used to transmit control information between the UE and the network and is used by UEs that do not have an RRC connection with the network, and the Dedicated Control Channel (DCCH) is a point-to-point bidirectional logical channel that transmits dedicated control information between the UE and the network and is used by UEs with an RRC connection. The Dedicated Traffic Channel (DTCH) is a point-to-point logical channel dedicated to one UE for transmitting user information. The DTCH can exist in both the uplink and downlink at the same time. In the downlink, the following connections exist between logical channels and transport channels: BCCH can be mapped to BCH; BCCH can be mapped to downlink shared channel (DL-SCH); PCCH can be mapped to PCH; CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In the uplink, the following connections exist between logical channels and transport channels: CCCH can be mapped to uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.
[0096] Figure 5 An example of a frame structure in a 3GPP-based wireless communication system is illustrated.
[0097] Figure 5 The frame structure shown is only exemplary, and the number of subframes, the number of time slots and / or the number of symbols in a frame may vary in various ways. In a 3GPP-based wireless communication system, OFDM parameter sets (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) may be configured differently between multiple cells aggregated for one UE. For example, if the UE is configured with different SCSs for cells aggregated for the cell, the (absolute time) duration of time resources (e.g., subframes, time slots, or TTIs) including the same number of symbols may be different among the aggregated cells. In this article, symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols).
[0098] Reference Figure 5 , downlink and uplink transmissions are organized into frames. Each frame has T f =10ms duration. Each frame is divided into two half-frames, where each half-frame has a duration of 5ms. Each half-frame consists of 5 sub-frames, where the duration of each sub-frame is T sf 1ms. Each subframe is divided into slots, and the number of slots in a subframe depends on the subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on a cyclic prefix (CP). In a normal CP, each slot includes 14 OFDM symbols, and in an extended CP, each slot includes 12 OFDM symbols. The parameter set is based on an exponentially scalable subcarrier spacing Δf=2 u *15kHz. The following table shows the subcarrier spacing Δf = 2 u *15kHz for the number of OFDM symbols per slot, number of slots per frame and number of slots per subframe for normal CP.
[0099] [Table 1]
[0100] u <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16
[0101] The following table shows the subcarrier spacing Δf = 2 u *15kHz for the number of OFDM symbols per slot, number of slots per frame, and number of slots per subframe for extended CP.
[0102] [Table 2]
[0103] u <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 2 12 40 4
[0104] A slot includes a plurality of symbols (e.g., 14 or 12 symbols) in the time domain. For each parameter set (e.g., subcarrier spacing) and carrier, a common resource block (CRB) N indicated by higher layer signaling (e.g., radio resource control (RRC) signaling) is allocated. start,u grid To begin, we define N size,u grid,x *N RB sc subcarriers and N subframe,u symb OFDM symbol resource grid, where N size,u grid,x is the number of resource blocks (RBs) in the resource grid, and the subscript x is DL for the downlink and UL for the uplink. N RB sc is the number of subcarriers per RB. In 3GPP-based wireless communication systems, N RB sc Typically 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL), there is one resource grid. The carrier bandwidth N for subcarrier spacing configuration u size,u grid Given by high-level parameters (e.g., RRC parameters). Each element in the resource grid for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and one complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l representing the symbol position in the time domain relative to a reference point. In a 3GPP-based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain. In a 3GPP NR system, RBs are classified into CRBs and physical resource blocks (PRBs). For subcarrier spacing configuration u, CRBs are numbered upward from 0 in the frequency domain. The center 0 of the subcarrier of CRB 0 for subcarrier spacing configuration u coincides with "point A" used as a common reference point for the resource block grid. In a 3GPP NR system, PRBs are defined within a bandwidth part (BWP) and are numbered from 0 to N. size BWP,i -1 numbering, where i is the number of the bandwidth part. Physical resource block n in bandwidth part i PRB With common resource block n CRB The relationship between is as follows: PRB =n CRB +N size BWP,i , where N size BWP,iIt is a common resource block where the bandwidth part starts relative to CRB 0. A BWP includes multiple consecutive RBs. A carrier can include up to N (e.g., 5) BWPs. A UE can be configured with one or more BWPs on a given component carrier. Among the BWPs configured for a UE, only one BWP can be active at a time. The active BWP defines the operating bandwidth of the UE within the operating bandwidth of the cell.
[0105] Figure 6 An example of data flow in a 3GPP LTE system is illustrated, and Figure 7 An example of data flow in a 3GPP NR system is illustrated. Figure 6 and Figure 7 In the header, "H" indicates the header and subheader.
[0106] MAC PDU is sent / received to / from external devices through the PHY layer using radio resources. MAC PDU arrives at the PHY layer in the form of a transport block. In the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to their physical channels PUSCH and PRACH, respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to PDSCH, PBCH and PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to PUCCH, and downlink control information (DCI) is mapped to PDCCH. The MAC PDU related to UL-SCH is sent by the UE via PUSCH based on UL grant, while the MAC PDU related to DL-SCH is sent by the BS via PDSCH based on DL assignment.
[0107] The functions of the RLC sublayer are performed by the RLC entity. For an RLC entity configured at the BS, there is a peer RLC entity configured at the UE, and vice versa. The RLC entity receives / delivers RLC SDUs from / to the upper layer, and sends / receives RLC PDUs to / from its peer RLC entity via the lower layer. The RLC entity can be configured to perform data transmission in one of the following three modes: transparent mode (TM), unacknowledged mode (UM), or acknowledged mode (AM). Therefore, the RLC entity is classified as a TM RLC entity, a UM RLC entity, or an AM RLC entity according to the mode of data transmission that the RLC entity is configured to provide. The TM RLC entity is configured to send a TM RLC entity or a receiving TM RLC entity. The sending TM RLC entity receives RLC SDUs from the upper layer and sends RLC PDUs to its peer receiving TM RLC entity via the lower layer. The receiving TM RLC entity delivers RLC SDUs to the upper layer and receives RLC PDUs from its peer sending TM RLC entity via the lower layer. A UM RLC entity is configured as a transmitting UM RLC entity or a receiving UM RLC entity. A transmitting UM RLC entity receives RLC SDUs from upper layers and sends RLC PDUs to its peer receiving UM RLC entity via lower layers. A receiving UM RLC entity delivers RLC SDUs to upper layers and receives RLC PDUs from its peer transmitting UM RLC entity via lower layers. An AM RLC entity consists of a transmitting side and a receiving side. The transmitting side of an AM RLC entity receives RLC SDUs from upper layers and sends RLC PDUs to its peer AM RLC entity via lower layers. The receiving side of an AM RLC entity delivers RLC SDUs to upper layers and receives RLC PDUs from its peer AM RLC entity via lower layers.
[0108] In an implementation of the present disclosure, the RLC expects the following services from the lower layer (ie, MAC): data transfer; and notification of a transmission opportunity and the total size of the RLC PDU to be transmitted in the transmission opportunity.
[0109] Figure 8 A model of an Acknowledged Mode (AM) Radio Link Control (RLC) entity in a 3GPP LTE system is illustrated.
[0110] In the 3GPP LTE system, byte-aligned (i.e., multiples of 8 bits) variable-sized RLC SDUs are supported for all RLC entity types (TM, UM, and AM RLC entities). RLC PDUs are formed only when the lower layer (i.e., MAC) has notified the transmission opportunity, and then the RLC PDUs are delivered to the lower layer. In the 3GPP LTE system, the main services and functions of the AM RLC entity include: transmission of upper layer PDUs; error correction through ARQ; concatenation, segmentation, and reassembly of RLC SDUs; resegmentation of RLC data PDUs; and reordering of RLC data PDUs.
[0111] Reference Figure 8 , the AM RLC entity in the 3GPP LTE system (hereinafter referred to as the LTE AM RLC entity) can be configured to deliver / receive RLC PDUs through the following logical channels: DL / UL DCCH or DL / UL DTCH. The LTE AM RLC entity delivers / receives the following RLC data PDUs: Acknowledged Mode Data (AMD) PDU and AMD PDU segments. The LTE AM RLC entity delivers / receives the following RLC control PDUs: STATUS PDU. When the transmitting side of the LTE AM RLC entity forms an AMD PDU from an RLC SDU, it should perform segmentation and / or concatenation of the RLC SDU so that the AMD PDU conforms to the total size of the RLC PDU indicated by the lower layer at a specific transmission opportunity notified by the lower layer. After the LTE AM RLC entity performs the segmentation / concatenation process, it adds an RLC header to form an AMD PDU.
[0112] The LTE AM RLC entity delivers (submits) the AMD PDU to the lower layer (MAC). If the LTE AM RLC entity receives a NACK for the transmitted RLC PDU or does not receive any response to the transmitted RLC PDU from the peer LTE AM RLC entity using polling for a certain period of time, the LTE AM RLC entity considers the RLC PDU stored in the transmission buffer for retransmission and stores the RLC PDU belonging to the transmission window in the retransmission buffer. If the LTE AM RLC entity gets an ACK for the RLC PDU in the retransmission buffer, the LTE AM RLC entity updates the state variable and moves the transmission window forward.
[0113] Alternatively, when an AMD PDU is delivered to the lower layer (MAC), the LTE AM RLC entity may generate identical copies of each AMD PDU to deliver one of the two copies to the lower layer (MAC) and send its copy to the retransmission buffer. If the LTE AM RLC entity receives a NACK for the transmitted RLC PDU or does not receive any response to the transmitted RLC PDU from the peer LTE AM RLC entity using polling for a certain period of time, the LTE AM RLC entity considers the RLC PDU stored in the retransmission buffer for retransmission. If the LTE AM RLC entity gets an ACK for the RLC PDU transmitted from the retransmission buffer, the RLC PDU may be discarded.
[0114] The transmitting side of the LTE AM RLC entity supports retransmission of RLC data PDUs (ARQ). If the RLC data PDU to be retransmitted does not conform to the total size of the RLC PDU indicated by the lower layer under a specific transmission opportunity notified by the lower layer, the LTE AM RLC entity may re-segment the RLC data PDU into AMD PDU segments, where the number of re-segments is not restricted. When the transmitting side of the LTE AM RLC entity forms an AMD PDU from an RLC SDU received from the upper layer or forms an AMD PDU segment from an RLC data PDU to be retransmitted, it shall include the relevant RLC header in the RLC data PDU.
[0115] In the 3GPP LTE system, as described below, AM data is transferred between the transmitting side of the LTE RLC entity and the receiving side of the LTE RLC entity. The transmitting side of the LTE AM RLC entity prioritizes the transmission of RLC control PDUs over RLC data PDUs. The transmitting side of the LTE AM RLC entity prioritizes the retransmission of RLC data PDUs over the transmission of new AMD PDUs. The transmitting side of the LTE AM RLC entity shall maintain the transmission window as follows according to the state variables VT(A) and VT(MS):
[0116] - If VT(A) <= SN < VT(MS), then SN falls within the transmission window;
[0117] - Otherwise, SN falls outside the transmission window.
[0118] The transmitting entity of each LTE AM RLC entity shall maintain VT(A) and VT(MS). VT(A) is an acknowledgement state variable holding the SN value of the next AMD PDU to receive a positive acknowledgement in sequence, and it is used as the lower edge of the transmit window. VT(A) is initially set to 0, and is updated whenever the LTE AM RLC entity receives a positive acknowledgement of an AMD PDU with SN=VT(A). VT(MS) is the maximum transmit state variable equal to VT(A)+AM_Window_Size, and it is used as the upper edge of the transmit window. AM_Window_Size is a constant used by both the transmitting and receiving sides of each LTE AM RLC entity for calculating VT(MS) from VT(A) and VR(MR) from VR(R). When a 10-bit SN is used, AM_Window_Size=512, and when a 16-bit SN is used, AM_Window_Size=32768. The receiving entity of each LTE AM RLC entity shall maintain VR(R) and VR(MR). VR(R) is a receive state variable that holds the SN value following the last fully received AMD PDU in sequence, and it is used as the low edge of the receive window. VR(R) is initially set to 0, and is updated whenever the AM RLC entity receives an AMD PDU with SN=VR(R). VR(MR) is the maximum acceptable receive state variable equal to VR(R)+AM_Window_Size, and it holds the SN value of the first AMD PDU beyond the receive window, and is used as the high edge of the receive window.
[0119] The transmitting side of the LTE AM RLC entity shall not pass to the lower layer any RLC data PDU whose SN falls outside the transmit window. When passing a new AMD PDU to the lower layer, the transmitting side of the AM RLC entity shall set the SN of the AMD PDU to VT(S) and then increment VT(S) by 1. The transmitting side of each LTE AM RLC entity shall maintain VT(S). VT(S) is a transmit state variable that holds the SN value to be assigned to the next newly generated AMD PDU. VT(S) is initially set to 0 and is updated whenever the AM RLC entity passes an AMD PDU with SN = VT(S).
[0120] The transmitting side of the LTE AM RLC entity may receive a positive acknowledgement of the RLC data PDU from its peer LTE AM RLC entity by a STATUS PDU (confirming that its peer AM RLC entity has successfully received it). Upon receiving a positive acknowledgement of the AMD PDU with SN=VT(A), the transmitting side of the LTE AM RLC entity shall:
[0121] - Set VT(A) equal to the SN of the AMD PDU with the minimum SN, whose SN falls within the range of VT(A) <= SN <= VT(S) and for which a positive acknowledgement has not been received.
[0122] - If positive acknowledgements for all AMD PDUs associated with the transmitted RLC SDU have been received, send an indication to the upper layer that the RLC SDU has been successfully delivered.
[0123] The transmitting side of the LTE AM RLC entity can receive a negative acknowledgement for an AMD PDU or a partial AMD PDU from its peer LTE AM RLC entity by means of a STATUS PDU (notifying the receiving failure to its peer LTE AM RLC entity). When a negative acknowledgement for an AMD PDU or a partial AMD PDU is received by the transmitting side of the LTE AM RLC entity from its peer LTE AM RLC entity by means of a STATUS PDU, the transmitting side of the LTE AM RLC entity shall:
[0124] - If the SN of the corresponding AMD PDU falls within the range of VT(A) <= SN < VT(S), consider the AMD PDU or the partial AMD PDU for which the negative acknowledgement has been received for retransmission.
[0125] When considering retransmission of an AMD PDU or a partial AMD PDU, the transmitting side of the LTE AM RLC entity shall:
[0126] - If an AMD PDU is considered for retransmission for the first time, set the RETX_COUNT associated with the AMD PDU to zero;
[0127] - Otherwise, if it (the AMD PDU or the partial AMD PDU being considered for retransmission) is not ready for retransmission or a part of it is not ready for retransmission, increment RETX_COUNT;
[0128] - If RETX_COUNT = maxRetxThreshold, indicate to the upper layer that the maximum number of retransmissions has been reached. RETX_COUNT is a counter maintained by the transmitting side of each LTE AM RLC entity. RETX_COUNT is initially set to 0 and counts the number of AMD PDUs transmitted since the most recent transmission of a poll bit. maxRetxThreshold is a parameter configured by RRC and used by the transmitting side of each LTE AM RLC entity to limit the number of retransmissions of AMD PDUs. If the transmitting side of the LTE AM RLC entity is a UE, the UE is configured with maxRetxThreshold by receiving maxRetxThreshold from the network (e.g., the BS) via RRC signaling.
[0129] When retransmitting an AMD PDU, the transmitting side of the LTE AM RLC entity shall:
[0130] - If the AMD PDU can completely fit into the total size of the RLC PDU indicated by the lower layer at a specific transmission opportunity, the AMD PDU other than the P field is passed to the lower layer as is;
[0131] - Otherwise, segment the AMD PDU to form new AMD PDU segments that will fit into the total size of the RLC PDU indicated by the lower layer at the specific transmission opportunity, and pass the new AMD PDU segments to the lower layer.
[0132] When retransmitting a portion of an AMD PDU, the transmitting side of the LTE AM RLC entity shall segment the portion of the AMD PDU as needed, form new AMD PDU segments that will conform to the total size of the RLC PDU indicated by the lower layer at a specific transmission opportunity, and pass the new AMD PDU segments to the lower layer.
[0133] When forming a new AMD PDU segment, the transmitting side of the AM RLC entity shall only map the Data field of the original AMD PDU to the Data field of the new AMD PDU segment, set the header of the new AMD PDU segment; and set the P field as described in the polling process below.
[0134] The AMD PDU consists of a Data field and an AMD PDU header. The AMD PDU header includes a P field and an SN field. In the 3GPP LTE system, the SN field indicates the SN of the corresponding AMD PDU. For an AMD PDU segment, the SN field indicates the SN of the original AMD PDU from which the AMD PDU segment is constructed. The P field indicates whether the transmitting side of the LTE AM RLC entity requests a STATUS report from its peer LTE AM RLC entity. In the 3GPP LTE and NR systems, an explanation of the P field is provided in the following table.
[0135] [Table 3]
[0136] value describe 0 No status report requested 1 Request Status Report
[0137] The LTE AM RLC entity may poll its peer AM RLC entity to trigger a STATUS report at the peer LTE AM RLC entity. Upon assembling a new AMD PDU, the transmitting side of the LTE AM RLC entity shall: > increment PDU_WITHOUT_POLL by 1;
[0138] > Increment BYTE_WITHOUT_POLL for each new byte of the Data field element mapped to the Data field of the RLC data PDU;
[0139] >if PDU_WITHOUT_POLL>=pollPDU; or
[0140] >if BYTE_WITHOUT_POLL >= pollByte;
[0141] >> Include polling in the RLC data PDU as described below.
[0142] Once an AM PDU or AMD PDU segment has been assembled, the transmitting side of the AM RLC entity shall:
[0143] > after sending an RLC data PDU, if both the transmit buffer and the retransmit buffer become empty (excluding sent RLC data PDUs awaiting acknowledgment); or
[0144] > if no new RLC data PDUs can be sent after sending an RLC data PDU (e.g. due to window stall);
[0145] >> Include polling in the RLC data PDU as described below.
[0146] The transmitting side of each LTE AM RLC entity shall maintain PDU_WITHOUT_POLL and BYTE_WITHOUT_POLL. PDU_WITHOUT_POLL is a counter that is initially set to 0 and counts the number of AMD PDUs sent since the last polling bit was sent. BYTE_WITHOUT_POLL is a counter that is initially set to 0 and counts the number of data bytes sent since the last polling bit was sent. pollPDU and pollByte are parameters configured by RRC. pollPDU is a parameter used by the transmitting side of each LTE AM RLC entity to trigger the polling of each pollPDU PDU, and pollByte is a parameter used by the transmitting side of each LTE AM RLC entity to trigger the polling of each pollByte byte. If the transmitting side of the LTE AM RLC entity is a UE, the UE is configured with pollPDU and pollByte by receiving pollPDU and pollByte from the network (e.g., BS) via RRC signaling.
[0147] To include a poll in an RLC data PDU, the transmitting side of the LTE AM RLC entity shall set the P field of the RLC data PDU to "1"; PDU_WITHOUT_POLL to 0; BYTE_WITHOUT_POLL to 0. After delivering the RLC data PDU including a poll to the lower layers and after VT(S) is incremented (if necessary), the transmitting side of the AM RLC entity shall:
[0148] >Set POLL_SN to VT(S)-1;
[0149] >If t-PollRetransmit is not running:
[0150] >>Start t-PollRetransmit;
[0151] Otherwise:
[0152] >>Restart t-PollRetransmit.
[0153] The transmitting side of each LTE AM RLC entity shall maintain POLL_SN. POLL_SN is a polling transmit state variable that holds the value of VT(S)-1 when the most recent RLC data PDU with the poll bit set to "1" was transmitted. POLL_SN is initially set to 0. t-PollRetransmit is a timer configured by RRC and used by the transmitting side of each LTE AM RLC entity to retransmit polls. If the transmitting side of the LTE AM RLC entity is a UE, the UE is configured with t-PollRetransmit by receiving it from the network (e.g., BS) via RRC signaling. Upon receiving the STATUS report from the receiving RLC AM entity, the transmitting side of the LTE AM RLC entity shall:
[0154] If the STATUS report includes a positive or negative acknowledgement for an RLC data PDU with sequence number equal to POLL_SN:
[0155] >>If t-PollRetransmit is running:
[0156] >>>Stop and reset t-PollRetransmit.
[0157] Once t-PollRetransmit expires, the transmitting side of the AM RLC entity shall:
[0158] > if both the transmit buffer and the retransmit buffer are empty (excluding sent RLC data PDUs awaiting acknowledgment); or
[0159] If no new RLC data PDUs can be sent (e.g. due to window stall):
[0160] >> Consider retransmitting the AMD PDU with SN = VT(S)-1; or
[0161] >> Consider retransmitting AMD PDUs that have not been positively acknowledged;
[0162] > Include polling in RLC data PDU as described above.
[0163] The LTE AM RLC entity sends a STATUS PDU to its peer LTE AM RLC entity to provide positive and / or negative acknowledgement of the RLC PDU (or part thereof). Triggering the start of STATUS reporting in the LTE AM RLC entity includes polling from its peer LTE AM RLC entity.
[0164] As described above, in the 3GPP LTE system, a new AM data PDU (AMD PDU) can be constructed only when a notification of a transmission opportunity is received from the lower layer (MAC). When there is a notification of a transmission opportunity, a single AMD PDU is constructed and delivered to the MAC. The sequence number (SN) of the newly constructed AMD PDU is set to VT(S), which is a transmission state variable holding the SN value to be assigned to the next newly generated AMD PDU. In the 3GPP LTE system, VT(S)-1 represents the SN of the last constructed AMD PDU on the transmitting side of the AM RLC entity. Under this condition, when the polling retransmission timer (t-PollRetransmit) expires, the transmitting side of the AM RLC entity can consider retransmitting the AMD PDU with SN=VT(S)-1, where VT(S)-1 represents the SN of the last constructed AMD PDU.
[0165] In 3GPP NR systems, similar to 3GPP LTE systems, byte-aligned (i.e., multiples of 8 bits) variable-sized RLC SDUs are supported for all RLC entity types (TM, UM, and AM RLC entities). However, in 3GPP NR systems, each RLC SDU is used to construct an RLC PDU without waiting for notification of a transmit opportunity from the lower layers (i.e., by MAC). In the case of UM and AM RLC entities, as in Figure 7As shown, two or more RLC PDUs can be used to segment and transmit the RLC SDU based on the notification from the lower layer. The RLC PDU is delivered to the lower layer only when the transmission opportunity has been notified by the lower layer (i.e., by MAC). In other words, in the 3GPP NR system, the RLC entity is allowed to pre-build the RLC data PDU even if there is no notification of the transmission opportunity from the lower layer, that is, the pre-construction of the RLC data PDU is allowed. When to pre-construct and how many RLC data PDUs to pre-construct is left to the UE to implement. Therefore, whenever a new AMD PDU is constructed without notification of the transmission opportunity by the lower layer, the transmission state variable (hereinafter referred to as TX_Next) holding the SN value to be assigned to the next newly generated AMD PDU can be incremented. Under this condition, if the RLC SDU with SN=TX_Next-1 is considered for retransmission once t-PollRetransmit expires as in the 3GPP LTE system, the transmitting side of the AM RLC entity will attempt to retransmit the last pre-constructed AMD PDU that has not been sent and is not on the transmission window. This means that the transmitting side of the AM RLC entity may select an erroneous RLC SDU that is outside the transmit window for retransmission. If no new RLC SDU can be sent (for example, due to a window stall), the transmitting side of the AM RLC entity cannot retransmit the RLC SDU because the selected RLC SDU is not on the transmit window and there is no space on the transmit window to send an AMD PDU containing the selected RLC SDU. In other words, the window stall cannot be resolved. Therefore, in NR, the RLC SDU with SN=TX_Next-1 should not be considered for retransmission, but a new RLC SDU selection rule for retransmission should be introduced to solve this problem.
[0166] In an implementation of the present disclosure, when the poll retransmission timer (t-PollRetransmit) expires, if both the transmit buffer and the retransmission buffer are empty (except for the transmitted RLC SDU or RLC SDU segment that is waiting for confirmation), or if no new RLC SDU can be sent (for example, due to a window stall), the transmitting side of the AM RLC entity considers the RLC SDU with the highest SN among the RLC SDUs delivered to the lower layer (i.e., MAC) for retransmission. In other words, the RLC SDU with the highest SN among the RLC SDUs sent by the transmitting device to the receiving device is considered for retransmission. In this implementation, the RLC SDU with the highest SN among the RLC SDUs delivered to the lower layer may or may not be the RLC SDU delivered with polling.
[0167] Alternatively, in another implementation of the present disclosure, when the poll retransmission timer (t-PollRetransmit) expires, if both the send buffer and the retransmission buffer are empty (except for the sent RLC SDU or RLC SDU segment waiting for confirmation), or if no new RLC SDU can be sent (for example, due to a window stall), the sending side of the AM RLC entity considers the following RLC SDU for retransmission, which RLC SDU corresponds to the highest SN of the polled AMD PDU among the set of polled AMD PDUs delivered to the lower layer (i.e., MAC).
[0168] The implementation of the present disclosure can be applied to any type of UE, for example, a machine type communication (MTC) UE, a narrowband Internet of Things (NB-IoT) UE, or a normal UE.
[0169] The transmitting side of the AM RLC entity uses a polling retransmission timer (which is t-PollRetransmit) to retransmit polling. t-PollRetransmit is configured by RRC. If the transmitting side of the AM RLC entity is a UE, the UE is configured with t-PollRetransmit by receiving t-PollRetransmit from a network (e.g., BS) via RRC signaling.
[0170] In the present disclosure, a transmitted RLC SDU or RLC SDU segment awaiting confirmation means that the transmitting side of the AM RLC entity has transmitted the RLC SDU and RLC SDU segment and awaits a STATUS report for the transmitted RLC SDU and RLC SDU segment.
[0171] In the present disclosure, "window pause" means stopping the sending window of the RLC or means pausing to advance the sending window. For example, if the sending window becomes full, the RLC entity may not send any new RLC PDUs until the lower edge of the sending window moves forward. This situation may be referred to as window pause. In other words, window pause means that the sending side of the AM RLC entity sends all RLC SDUs and RLC SDU segments within the sending window, but has not yet received any confirmation of the sent RLC SDUs and RLC SDU segments. Therefore, because the sending side of the AM RLC entity should not deliver an AM PDU with an RLC SDU whose SN falls outside the sending window to the lower layer, the sending side of the AM RLC entity cannot send a new RLC SDU.
[0172] In the present disclosure, the highest SN is the highest SN based on a modulus operation. For example, when the SN can be assigned from 0 to 1023, if the currently assigned SN starts from 1000 and ends at 1, the highest SN is 1 because the modulus operation sets 1024 and 1025 to 0 and 1, respectively. However, if the currently assigned SN starts from 1 and ends at 500, the highest SN is 500.
[0173] In the present disclosure, an AMD PDU including polling means an AMD PDU whose polling bit is set to "1". In other words, in the present disclosure, including polling in an RLC PDU means including a value "1" in a P field included in the RLC PDU, and an RLC PDU including polling means an RLC PDU whose P field includes a value "1".
[0174] In an embodiment of the present disclosure, the transmitting side of the AM RLC entity is configured with a timer and parameters for the polling process by receiving polling configuration information including the following from the network:
[0175] -t-PollRetransmit, so that the poll is retransmitted after t-PollRetransmit expires;
[0176] -pollPDU is used to trigger the polling of each pollPDU PDU;
[0177] -pollByte is used to trigger polling for each pollByte byte. pollPDU is the parameter used by the transmitting side of each AM RLC entity to trigger polling for each pollPDU PDU, while pollByte is the parameter used by the transmitting side of each AM RLC entity to trigger polling for each pollByte byte.
[0178] In an implementation of the present disclosure, the transmitting side of the AM RLC entity manages the following counters:
[0179] -PDU_WITHOUT_POLL counts the number of AMD PDUs that have been sent since the last poll bit was sent, and the counter is initially set to 0;
[0180] - BYTE_WITHOUT_POLL counts the number of data bytes sent since the last poll bit was sent, and the counter is initially set to zero.
[0181] In an implementation of the present disclosure, when the transmitting side of the AM RLC entity delivers a set of AMD PDUs after being notified of a transmission opportunity by a lower layer (i.e., MAC), the transmitting side of the AM RLC entity may deliver the AMD PDUs to the lower layer (i.e., MAC) in ascending order of SN. Alternatively, the transmitting side of the AM RLC entity may deliver multiple AMD PDUs to the lower layer at the same time.
[0182] In this disclosure, all state variables and all counters are non-negative integers.
[0183] Fig. 9 A model of an AM RLC entity that can be used in an implementation of the present disclosure is illustrated.
[0184] Reference Fig. 9 , the AM RLC entity can be configured to deliver / receive RLC PDUs through the following logical channels: DL / UL DCCH or DL / UL DTCH. The AM RLC entity delivers / receives the following RLC data PDUs: AMD PDU. The AMD PDU contains a complete RLC SDU or an RLC SDU segment. The AM RLC entity delivers / receives the STATUS PDU as an RLC control PDU.
[0185] In an implementation of the present disclosure, the transmitting side of the AM RLC entity generates an AMD PDU for each RLC SDU. When notified of a transmission opportunity by a lower layer, the transmitting AM RLC entity (if necessary) segments the RLC SDU so that the corresponding AMD PDU (with an updated RLC header as needed) conforms to the total size of the RLC PDU indicated by the lower layer. The transmitting side of the AM RLC entity supports retransmission of RLC SDUs or RLC SDU segments (ARQ). If the RLC SDU or RLC SDU segment to be retransmitted (including the RLC header) does not conform to the total size of the RLC PDU indicated by the lower layer at a specific transmission opportunity notified by the lower layer, the AM RLC entity may segment the RLC SDU or resegment the RLC SDU segment into RLC SDU segments, wherein the number of resegments is not limited. When the transmitting side of the AM RLC entity forms an AMD PDU from an RLC SDU or an RLC SDU segment, it includes the relevant RLC header in the AMD PDU.
[0186] In the implementation of the present disclosure, the AMD PDU consists of a Data field and an AMD PDU header. The AM RLC entity can be configured by RRC to use a 12-bit SN or an 18-bit SN. The AMD PDU header contains a P field and an SN field. The SN field indicates the SN of the corresponding RLC SDU. For RLC AM, the SN of each RLC SDU is incremented by 1.
[0187] In an implementation of the present disclosure, the data transmission process between the transmitting side of the RLC entity and the receiving side of the RLC entity is as follows.
[0188] The transmitting side of the AM RLC entity prioritizes the transmission of RLC control PDUs over the transmission of AMD PDUs. The transmitting side of the AM RLC entity prioritizes the transmission of AMD PDUs containing previously transmitted RLC SDUs or RLC SDU segments over the transmission of AMD PDUs not containing previously transmitted RLC SDUs or RLC SDU segments.
[0189] The transmitting side of the AM RLC entity shall maintain a transmission window according to the status variable TX_Next_Ack as follows:
[0190] - If TX_Next_Ack <= SN < TX_Next_Ack + AM_Window_Size, then SN falls within the transmission window;
[0191] - Otherwise, SN falls outside the transmission window. TX_Next_Ack is an acknowledgment status variable maintained at the transmitting side of each AM RLC entity and holds the value of the SN of the next RLC SDU to be received an affirmative acknowledgment in sequence, and it serves as the lower edge of the transmission window. It is initially set to 0 and is updated whenever the AM RLC entity receives an affirmative acknowledgment of an RLC SDU with SN = TX_Next_Ack. AM_Window_Size is a constant used by both the transmitting side and the receiving side of each AM RLC entity. AM_Window_Size = 2048 when using 12-bit SN, and AM_Window_Size = 131072 when using 18-bit SN.
[0192] The transmitting side of the AM RLC entity does not deliver any AMD PDU whose SN falls outside the transmit window to the lower layer. For each RLC SDU received from the upper layer (e.g., PDCP), the AM RLC entity associates the SN with the RLC SDU equal to TX_Next, and constructs the AMD PDU by setting the SN of the AMD PDU to TX_Next, and increments TX_Next by 1. TX_Next is a state variable maintained on the transmitting side of each AM RLC entity, and holds the SN value to be assigned to the next newly generated AMD PDU. TX_Next is initially set to 0, and is updated whenever the AM RLC entity constructs an AMD PDU with SN=TX_Next containing the last segment of the RLC SDU or the RLC SDU. In other words, because the SN field in the AMD PDU indicates the SN of the corresponding RLC PDU, TX_Next will be updated whenever the AM RLC entity constructs an AMD PDU containing the last segment of the RLC SDU or the RLC SDU with SN=TX_Next.
[0193] When delivering an AMD PDU containing a segment of an RLC SDU to a lower layer, the transmitting side of the AM RLC entity sets the SN of the AMD PDU to the SN of the corresponding RLC SDU.
[0194] The transmitting side of the AM RLC entity may receive a positive acknowledgement of the RLC SDU from its peer AM RLC entity via a STATUS PDU (acknowledging successful reception by its peer AM RLC entity). Upon receiving a positive acknowledgement of the RLC SDU with SN=x, the transmitting side of the AM RLC entity sends an indication of successful delivery of the RLC SDU to the upper layer; and sets TX_Next_Ack equal to the SN of the RLC SDU with the smallest SN whose SN falls within the range of TX_Next_Ack<=SN<=TX_Next and for which a positive acknowledgement has not yet been received. In other words, upon receiving a positive acknowledgement of the RLC SDU with SN=x, the transmitting side of the AM RLC entity moves the lower edge of the transmit window toward the smallest SN of the RLC SDUs within the transmit window for which a positive acknowledgement has not yet been received.
[0195] The transmitting side of the AM RLC entity may receive a negative acknowledgement of an RLC SDU or an RLC SDU segment from its peer AM RLC entity via a STATUS PDU (notifying its peer AM RLC entity of a reception failure). When a negative acknowledgement of an RLC SDU or an RLC SDU segment is received from its peer AM RLC entity via a STATUS PDU, the transmitting side of the AM RLC entity may consider retransmitting the RLC SDU or RLC SDU segment for which the negative acknowledgement has been received if the SN of the corresponding RLC SDU falls within the range of TX_Next_Ack <= SN < TX_Next.
[0196] When considering retransmission of an RLC SDU or an RLC SDU segment, the transmitting side of the AM RLC entity:
[0197] - if a RLC SDU or an RLC SDU segment is considered for retransmission for the first time, the RETX_COUNT associated with the RLC SDU is set to zero;
[0198] - if it (the RLC SDU or RLC SDU segment being considered for retransmission) is not yet ready for retransmission and the RETX_COUNT associated with the RLC SDU is not incremented due to another negative acknowledgement in the same STATUS PDU, then the RETX_COUNT is incremented;
[0199] - If RETX_COUNT = maxRetxThreshold, an indication is given to the upper layer that the maximum retransmission has been reached. RETX_COUNT is a counter maintained by the transmitting side of each AM RLC entity and counts the number of retransmissions of an RLC SDU or an RLC SDU segment. One RETX_COUNT counter is maintained per RLC SDU. maxRetxThreshold is a parameter configured by RRC and is used by the transmitting side of each AM RLC entity to limit the number of retransmissions corresponding to an RLC SDU (including RLC SDU segments). If the transmitting side of the AM RLC entity is a UE, the UE is configured with maxRetxThreshold by receiving maxRetxThreshold from the network (e.g., BS) via RRC signaling.
[0200] When retransmitting an RLC SDU or an RLC SDU segment, the transmitting side of the AM RLC entity:
[0201] - segment the RLC SDU or RLC SDU segment if necessary;
[0202] - forming a new AMD PDU that will fit within the total size of the AMD PDU indicated by lower layers at a particular transmission opportunity; and
[0203] - Deliver new AMD PDU to lower layers.
[0204] When forming a new AMD PDU, the transmitting side of the AM RLC entity:
[0205] - Mapping only the original RLC SDU or RLC SDU segment to the Data field of the new AMD PDU; and
[0206] - Modify the header of the new AMD PDU. Modifying the header of the new AMD PDU includes setting the P field as described below.
[0207] Once notified of a transmit opportunity by the lower layers (i.e., MAC), for each AMD PDU delivered for transmission, such that the AMD PDU contains a previously unsent RLC SDU or an RLC SDU segment containing a previously unsent byte segment, the transmitting side of the AM RLC entity:
[0208] >Increment PDU_WITHOUT_POLL by 1;
[0209] > Increment BYTE_WITHOUT_POLL for each new byte of the Data field element that is mapped to the Data field of the AMD PDU;
[0210] >if PDU_WITHOUT_POLL>=pollPDU; or
[0211] >if BYTE_WITHOUT_POLL >= pollByte;
[0212] >>Set the P field of AMD PDU to "1";
[0213] >>Set PDU_WITHOUT_POLL to 0;
[0214] >>Set BYTE_WITHOUT_POLL to 0;
[0215] >Deliver AMD PDU to lower layers.
[0216] Once notified of a transmit opportunity by lower layers, for each AMD PDU delivered for transmission, the transmitting side of the AM RLC entity:
[0217] > if after sending the AMD PDU, both the transmit buffer and the retransmit buffer become empty (except for the transmitted RLC SDU or RLC SDU segment that is awaiting acknowledgment); or
[0218] If no new RLC SDU can be sent after the AMD PDU (e.g. due to window stall);
[0219] >>Set the P field of AMD PDU to "1";
[0220] >>Set PDU_WITHOUT_POLL to 0;
[0221] >>Set BYTE_WITHOUT_POLL to 0;
[0222] >Deliver AMD PDU to lower layers.
[0223] It is required that an empty RLC buffer (except for transmitted RLC SDUs or RLC SDU segments that are waiting for acknowledgment) does not cause unnecessary polling when data is waiting at upper layers (e.g., PDCP, SDAP, RRC). In order to keep an empty RLC buffer (except for transmitted RLC SDUs or RLC SDU segments that are waiting for acknowledgment) from causing unnecessary polling, the transmitting side of the AM RLC entity may set the P field of the AMD PDU to "0" even if the RLC buffer becomes empty after transmitting the AMD PDU.
[0224] When the transmitting side of the AM RLC entity delivers an AMD PDU to the lower layer, the transmitting side of the AM RLC entity:
[0225] >If an AMD PDU including a poll is delivered to the lower layer, POLL_SN is set to the SN of the AMD PDU including the poll;
[0226] >>If t-PollRetransmit is not running, start t-PollRetransmit;
[0227] >>If t-PollRetransmit is running, restart t-PollRetransmit.
[0228] When the poll retransmission timer t-PollRetransmit expires, the transmitting side of the AM RLC entity performs a transmission or retransmission process to retransmit the poll.
[0229] When t-PollRetransmit expires, the transmitting side of the AM RLC entity:
[0230] > if both the transmit buffer and the retransmit buffer are empty (except for transmitted RLC SDU or RLC SDU segments awaiting acknowledgment); and / or
[0231] If no new RLC SDU or RLC SDU segment can be sent (e.g. due to window stall):
[0232] >> Consider retransmitting the RLC SDU with the highest SN among the RLC SDUs delivered to the lower layer;
[0233] > Include polling in AMD PDU as described above.
[0234] Specifically, in an implementation of the present disclosure, once t-PollRetransmit expires, when the RLC buffer (except for the transmitted RLC SDU or RLC SDU segment that is waiting for confirmation) is empty and / or when no new RLC SDU or RLC SDU segment can be sent (e.g., due to a window pause), the transmitting side of the AM RLC entity considers the RLC SDU with the highest SN among the RLC SDUs delivered to the MAC for retransmission. When there is a transmission opportunity, the transmitting side of the AM RLC entity includes a poll in the AMD PDU containing the RLC SDU considered for retransmission and delivers the AMD PDU to the MAC for transmission. In an implementation of the present disclosure, once t-PollRetransmit expires and when the RLC buffer (except for the transmitted RLC SDU or RLC SDU segment that is waiting for confirmation) is empty or when no new RLC SDU or RLC SDU segment can be sent (e.g., due to a window pause), the RLC SDU considered for retransmission may or may not be an RLC SDU with a poll that has been delivered to the MAC. In an implementation of the present disclosure, the RLC SDU considered for retransmission once t-PollRetransmit expires and no new RLC SDU or RLC SDU segment can be sent (e.g., due to a window pause) may not be an RLC SDU included in the last constructed AMD PDU. The advantage of this implementation of the present disclosure is that the transmitting side of the AM RLC entity requests the receiving side of the AM RLC entity to send a status report on the RLC SDU actually sent by the transmitting side of the AM RLC entity up to the last RLC SDU to the transmitting side of the AM RLC entity.
[0235] When the transmitting side of the AM RLC entity receives a STATUS report containing a positive or negative acknowledgement of an RLC SDU with SN equal to POLL_SN, the transmitting side of the AM RLC entity shall stop and reset t-PollRetransmit if it is running.
[0236] Fig.10 An example of data transmission according to the implementation of the present disclosure is illustrated. Fig.10, assuming that all RLC SDUs have the same size, which is 100 bytes, pollPDU is 3, polleByte is 400 bytes, and the sending window size is 8.
[0237] Fig.10 (a) in FIG. 1 illustrates a case where t-PollRetransmit expires and both the transmit buffer and the retransmit buffer are empty (except for the transmitted RLC SDU or RLC SDU segment that is waiting for acknowledgment). Fig.10 In (a), when the transmitting side of the AM RLC entity receives a notification of a transmission opportunity from a lower layer (e.g., MAC), the transmitting side of the AM RLC entity:
[0238] - For the AMD PDU of the RLC SDU containing SN4: increment PDU_WITHOUT_POLL by 1; increment BYTE_WITHOUT_POLL by 100 bytes; and deliver the AMD PDU of the RLC SDU containing SN4 to the lower layer;
[0239] - For the AMD PDU of the RLC SDU containing SN5: increment PDU_WITHOUT_POLL by 1; increment BYTE_WITHOUT_POLL by 100 bytes; and deliver the AMD PDU of the RLC SDU containing SN5 to the lower layer;
[0240] -For the AMD PDU of the RLC SDU containing SN6: increment PDU_WITHOUT_POLL by 1; increment BYTE_WITHOUT_POLL by 100 bytes; since PDU_WITHOUT_POLL is equal to pollPDU=3, set the P field of the AMD PDU of the RLC SDU containing SN6 to "1"; set PDU_WITHOUT_POLL to 0; set BYTE_WITHOUT_POLL to 0; and deliver the AMD PDU of the RLC SDU containing SN6 to the lower layer; set POLL_SN to SN6; start t-PollRetransmit; increment PDU_WITHOUT_POLL by 1;
[0241] - For the AMD PDU of the RLC SDU containing SN7: increment BYTE_WITHOUT_POLL by 100 bytes; deliver the AMD PDU of the RLC SDU containing SN7 to the lower layer; increment PDU_WITHOUT_POLL by 1;
[0242] -For the AMD PDU of the RLC SDU containing SN8: increment BYTE_WITHOUT_POLL by 100 bytes; set the P field of the AMD PDU of the RLC SDU containing SN8 to "1" because both the send buffer and the retransmission buffer (except for the sent RLC SDU or RLC SDU segment waiting for confirmation) are empty after sending the AMD PDU; set PDU_WITHOUT_POLL to 0; set BYTE_WITHOUT_POLL to 0; deliver the AMD PDU of the RLC SDU containing SN8 to the lower layer; set POLL_SN to SN8; and restart t-PollRetransmit.
[0243] All RLC SDUs from SN4 to SN8 are sent and await acknowledgment. Fig.10 As shown in (a), when t-PollRetransmit expires, the sending side of the AM RLC entity:
[0244] > Check if the send buffer and retransmit buffer are empty;
[0245] > If the transmit buffer and the retransmission buffer are empty, then the RLC SDU with SN8 is considered for retransmission because SN8 is the highest SN among the RLC SDUs delivered to the lower layer (i.e., MAC);
[0246] >Retransmit the selected RLC SDU with SN8.
[0247] Fig.10 (b) in FIG. 4 shows an example in which t-PollRetransmit expires and no new RLC SDU can be sent (eg, due to a window stall). Fig.10 In (b), when the transmitting side of the AM RLC entity receives a notification of a transmission opportunity from a lower layer (e.g., MAC), the transmitting side of the AM RLC entity:
[0248] - For the AMD PDU of the RLC SDU containing SN1: increment PDU_WITHOUT_POLL by 1; increment BYTE_WITHOUT_POLL by 100 bytes; and deliver the AMD PDU of the RLC SDU containing SN1 to the lower layer;
[0249] - For the AMD PDU of the RLC SDU containing SN2: increment PDU_WITHOUT_POLL by 1; increment BYTE_WITHOUT_POLL by 100 bytes; and deliver the AMD PDU of the RLC SDU containing SN2 to the lower layer;
[0250] -For the AMD PDU of the RLC SDU containing SN3: increment PDU_WITHOUT_POLL by 1; increment BYTE_WITHOUT_POLL by 100 bytes; since PDU_WITHOUT_POLL is equal to pollPDU=3, set the P field of the AMD PDU of the RLC SDU containing SN3 to "1"; set PDU_WITHOUT_POLL to 0; set BYTE_WITHOUT_POLL to 0; deliver the AMD PDU of the RLC SDU containing SN3 to the lower layer; set POLL_SN to SN3; and start t-PollRetransmit;
[0251] - For the AMD PDU of the RLC SDU containing SN4: increment PDU_WITHOUT_POLL by 1; increment BYTE_WITHOUT_POLL by 100 bytes; and deliver the AMD PDU of the RLC SDU containing SN4 to the lower layer;
[0252] - For the AMD PDU of the RLC SDU containing SN5: increment PDU_WITHOUT_POLL by 1; increment BYTE_WITHOUT_POLL by 100 bytes; and deliver the AMD PDU of the RLC SDU containing SN5 to the lower layer;
[0253] -For the AMD PDU of the RLC SDU containing SN6: increment PDU_WITHOUT_POLL by 1; increment BYTE_WITHOUT_POLL by 100 bytes; since PDU_WITHOUT_POLL is equal to pollPDU=3, set the P field of the AMD PDU of the RLC SDU containing SN6 to "1"; set PDU_WITHOUT_POLL to 0; set BYTE_WITHOUT_POLL to 0; deliver the AMD PDU of the RLC SDU containing SN6 to the lower layer; and set POLL_SN to SN6; and restart t-PollRetransmit;
[0254] - For the AMD PDU of the RLC SDU containing SN7: increment PDU_WITHOUT_POLL by 1; increment BYTE_WITHOUT_POLL by 100 bytes; and deliver the AMD PDU of the RLC SDU containing SN7 to the lower layer;
[0255] -For the AMD PDU of the RLC SDU containing SN8: increment PDU_WITHOUT_POLL by 1; increment BYTE_WITHOUT_POLL by 100 bytes; because no new RLC SDU can be sent after sending the AMD PDU (for example, due to window pause), set the P field of the AMD PDU of the RLC SDU containing SN8 to "1"; set PDU_WITHOUT_POLL to 0; set BYTE_WITHOUT_POLL to 0; deliver the AMD PDU of the RLC SDU containing SN8 to the lower layer; set POLL_SN to SN8; and restart t-PollRetransmit.
[0256] All RLC SDUs from SN1 to SN8 are sent and await acknowledgment. Fig.10 As shown in (b), when t-PollRetransmit expires, the sending side of the AM RLC entity:
[0257] Check if no new RLC SDUs can be sent (e.g. due to window stall);
[0258] > If no new RLC SDU can be sent (e.g. due to window stall), then the RLC SDU with SN8 is considered for retransmission because SN8 is the highest SN among the RLC SDUs delivered to the lower layer (i.e., MAC);
[0259] >Retransmit the selected RLC SDU with SN8.
[0260] exist Fig.10 (a) and Fig.10 In (b), when t-PollRetransmit expires, if both the send buffer and the retransmission buffer are empty (except for the sent RLC SDU or RLC SDU segment waiting for confirmation), or if no new RLC SDU can be sent (for example, due to window pause), then because SN8 is the highest SN of the AMD PDU among the set of AMD PDUs delivered to the lower layer (i.e., MAC) for transmission, the transmitting side of the AM RLC entity can consider the RLC SDU with SN8 for retransmission.
[0261] Fig.11 is a block diagram illustrating an example of a communication device capable of performing the method of the present disclosure.
[0262] exist Fig.11In the present disclosure, one of the communication device 1100 and the communication device 1200 may be a user equipment (UE), and the other may be a base station (BS). Alternatively, one of the communication device 1100 and the communication device 1200 may be a UE, and the other may be another UE. Alternatively, one of the communication device 1100 and the communication device 1200 may be a network node, and the other may be another network node. In the present disclosure, the network node may be a base station (BS). In some scenarios, the network node may be a core network device (e.g., a network device with a mobility management function, a network device with a session management function, etc.).
[0263] In some scenarios of the present disclosure, one of the communication devices 1100, 1200, or each of the communication devices 1100, 1200 may be a wireless communication device configured to send / receive radio signals to / from an external device, or be equipped with a wireless communication module that sends / receives radio signals to / from an external device. The wireless communication module may be a transceiver 1113 or 1213. The wireless communication device is not limited to a UE or a BS, and the wireless communication device may be any suitable mobile computing device configured to implement one or more implementations of the present disclosure, such as a vehicle communication system or device, a wearable device, a laptop computer, a smart phone, etc. The communication device mentioned as a UE or a BS in the present disclosure may be replaced by any wireless communication device such as a vehicle communication system or device, a wearable device, a laptop computer, a smart phone, etc.
[0264] In the present disclosure, the communication device 1100, 1200 includes a processor 1111, 1211 and a memory 1112, 1212. The communication device 1100 may further include a transceiver 1113, 1213 or be configured to be operatively connected to the transceiver 1113, 1213.
[0265] Processors 1111, 1211 implement the functions, processes and / or methods disclosed in the present disclosure. One or more protocols may be implemented by processors 1111, 1211. For example, processors 1111, 1211 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). Processors 1111, 1211 may generate protocol data units (PDUs) and / or service data units (SDUs) according to the functions, processes and / or methods disclosed in the present disclosure. Processors 1111, 1211 may generate messages or information according to the functions, processes and / or methods disclosed in the present disclosure. Processors 1111, 1211 may generate signals (e.g., baseband signals) containing PDUs, SDUs, messages or information according to the functions, processes and / or methods disclosed in the present disclosure, and provide signals to transceivers 1113 and / or 1213 connected thereto. The processor 1111 , 1211 may receive a signal (eg, a baseband signal) from the transceiver 1113 , 1213 connected thereto, and obtain a PDU, an SDU, a message, or information according to the functions, processes, and / or methods disclosed in the present disclosure.
[0266] Processors 1111, 1211 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. Processors 1111, 1211 may be implemented by hardware, firmware, software, or a combination thereof. In hardware configuration, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), or a field programmable gate array (FPGA) may be included in processors 1111, 1211. The present disclosure may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, functions, etc. that perform functions or operations of the present disclosure. Firmware or software configured to perform the present disclosure may be included in processors 1111, 1211, or stored in memories 1112, 1212 so as to be driven by processors 1111, 1211.
[0267] The memory 1112, 1212 is connected to the processor of the network node and stores various types of PDUs, SDUs, messages, information and / or instructions. The memory 1112, 1212 may be arranged inside or outside the processor 1111, 1211, or may be connected to the processor 1111, 1211 via various technologies such as wired or wireless connection.
[0268] The transceiver 1113, 1213 is connected to the processor 1111, 1211, and can be controlled by the processor 1111, 1211 to send and / or receive signals to / from an external device. The processor 1111, 1211 can control the transceiver 1113, 1213 to initiate communication and send or receive signals including various types of information or data sent or received through a wired interface or a wireless interface. The transceiver 1113, 1213 includes a receiver to receive signals from an external device and to send signals to an external device. The transceiver 1113, 1213 can up-convert the OFDM baseband signal to a carrier frequency under the control of the processor 1111, 1211, and send the up-converted OFDM signal at the carrier frequency. The transceiver 1113, 1213 may include an (analog) oscillator, and the OFDM baseband signal is up-converted to a carrier frequency by the oscillator. The transceivers 1113 and 1213 may receive OFDM signals of a carrier frequency and down-convert the OFDM signals into OFDM baseband signals under the control of the processors 1111 and 1211. The transceivers 1113 and 1213 may down-convert the OFDM signals of a carrier frequency into OFDM baseband signals through an oscillator.
[0269] In a wireless communication device such as a UE or BS, an antenna assists in the transmission and reception of a radio signal (i.e., a wireless signal). In a wireless communication device, a transceiver 1113, 1213 transmits and / or receives a wireless signal such as a radio frequency (RF) signal. For a communication device that is a wireless communication device (e.g., a BS or UE), a transceiver 1113, 1213 may be referred to as a radio frequency (RF) unit. In some implementations, the transceiver 1113, 1213 may forward a baseband signal provided by a processor 1111, 1211 connected thereto and convert the baseband signal into a radio signal with a radio frequency. In a wireless communication device, the transceiver 1113, 1213 may transmit or receive a radio signal containing a PDU, SDU, message or information according to the functions, processes and / or methods disclosed in the present disclosure via a radio interface (e.g., time / frequency resources). In some implementations of the present disclosure, upon receiving a radio signal having a radio frequency from another communication device, the transceiver 1113, 1213 may forward the radio signal and convert the radio signal into a baseband signal for processing by the processor 1111, 1211. The radio frequency may be referred to as a carrier frequency. In the UE, the processed signal may be processed according to various techniques such as conversion into audible or readable information for output via a speaker of the UE.
[0270] In some scenarios of the present disclosure, the functions, processes and / or methods disclosed in the present disclosure may be implemented by a processing device. The processing device may be a system on chip (SoC). The processing device may include a processor 1111, 1211 and a memory 1112, 1212, and may be installed in, placed on, or connected to a communication device 1100, 1200. The processing device may be configured to execute or control one of the methods and / or processes described herein, and / or to cause such a method and / or process to be executed by a communication device to which the processing device is installed, placed, or connected. The memory 1112, 1212 in the processing device may be configured to store software codes including instructions, which, when executed by the processor 1111, 1211, cause the processor 1111, 1211 to execute some or all of the functions, methods, or processes discussed in the present disclosure. The memory 1112, 1212 in the processing device may store or buffer information or data generated by the processor of the processing device or information recovered or obtained by the processor of the processing device. One or more processes involving the transmission or reception of information or data may be performed by the processor 1111, 1211 of the processing device, or may be performed under the control of the processor 1111, 1211 of the processing device. For example, the transceiver 1113, 1213 operatively connected or coupled to the processing device may transmit or receive a signal containing information or data under the control of the processor 1111, 1211 of the processing device.
[0271] In the implementation of the present disclosure, the UE operates as a transmitting device in the uplink (UL) and operates as a receiving device in the downlink (DL). In the implementation of the present disclosure, the BS operates as a receiving device in the UL and operates as a transmitting device in the DL. In the present disclosure, the processor, transceiver, and memory included in or installed on the UE are respectively referred to as the UE processor, the UE transceiver, and the UE memory, and the processor, transceiver, and memory included in or installed on the BS are respectively referred to as the BS processor, the BS transceiver, and the BS memory.
[0272] The AM RLC entity according to the implementation of the present disclosure is implemented by the processors 1111 , 1211 .
[0273] The processors 1111 and 1211 may be configured to construct M RLC PDUs each including M RLC SDUs before there is a transmission opportunity. When a transmission opportunity (hereinafter referred to as the first transmission opportunity) available to the processors 1111 and 1211 occurs, the processors may transmit some or all of the M RLC PDUs. When the total size of the RLC PDUs to be transmitted in the transmission opportunity is sufficient to accommodate all the M RLC PDUs and when all the SNs of the M RLC PDUs fall within the transmission window, the processors 1111 and 1211 may transmit all the M RLC PDUs. In some cases, the processors 1111 and 1211 may transmit only L RLC PDUs in the first transmission opportunity, where L<M. For example, if the M RLC PDUs include an RLC PDU whose SN falls outside the transmission window, the processors 1111 and 1211 do not deliver / transmit the RLC SDU whose SN falls outside the transmission window. The SNs of the L RLC PDUs fall within the transmission window. The MAC entity configured in the processors 1111 and 1211 may notify the RLC entity of the first transmission opportunity, and the RLC entity configured in the processors 1111 and 1211 may deliver only L RLC PDUs among the M RLC PDUs for the first transmission opportunity. The L RLC PDUs include corresponding L RLC SDUs having the lowest L SNs among the SNs of the M RLC SDUs included in the M RLC PDUs. Each of the L RLC SDUs may be a (complete) RLC SDU or an RLC SDU segment.
[0274] Processors 1111, 1211 may include polling in at least one RLC PDU (hereinafter referred to as the first RLC PDU) among the L RLC PDUs to be sent in the first transmission opportunity. Processors 1111, 1211 may be configured to set POLL_SN to the SN of the first RLC PDU when delivering the RLC PDU to MAC. In detail, the RLC entity may include polling in the first RLC PDU among the L RLC PDUs, and once the first RLC PDU including the polling is delivered to MAC, the polling retransmission timer is started. Processors 1111, 1211 may construct a MAC PDU including the L RLC PDUs for the first transmission opportunity. Processors 1111, 1211 may send (or control a transceiver operably connected or connected to processors 1111, 1211 to send) the MAC PDU in the first transmission opportunity. Once the RLC PDU is delivered to MAC, the RLC entity may set POLL_SN to the SN of the first RLC PDU.
[0275] The polling retransmission timer will not be restarted or stopped unless another transmission opportunity occurs or the processor 1111, 1211 receives a STATUS report including a positive or negative acknowledgement of the RLC SDU with SN equal to POLL_SN. The polling retransmission timer started based on the first RLC PDU may expire over time. The expiration of the polling retransmission timer may indicate that there is no transmission opportunity between the first transmission opportunity and the expiration of the polling retransmission timer, and the processor 1111, 1211 has not received a STATUS report including a positive or negative acknowledgement of the RLC SDU with SN equal to POLL_SN.
[0276] Once the polling retransmission timer expires, the processor 1111, 1211 may determine whether the RLC buffer (e.g., the transmission buffer and the retransmission buffer) is empty except for the transmitted RLC SDU or RLC SDU segment waiting for confirmation. In this example, because only L RLC PDUs of the M RLC PDUs are delivered and transmitted and there are no other transmission opportunities after the first transmission opportunity and before the polling retransmission timer expires, the RLC buffer will have at least one RLC PDU. Once the polling retransmission timer expires, the processor 1111, 1211 may determine whether a new RLC SDU can be sent. In an implementation of the present disclosure, the new RLC SDU may represent a previously unsent RLC SDU or a previously unsent RLC SDU segment. The remaining RLC SDUs among the M RLC SDUs except the L RLC SDUs that have been delivered / sent, and / or other RLC SDUs with SNs higher than the highest SN of the M RLC SDUs may be new RLC SDUs that can be used for transmission, unless there is a reason that prevents them from being transmitted (e.g., a window pause). For example, if the SN of the remaining RLC SDUs is outside the sending window, the processors 1111 and 1211 may determine that the RLC SDUs in the RLC buffer that have not been delivered to the MAC or have not been sent cannot be sent. In this case (or in the case of a window pause), the processors 1111 and 1211 may determine that no new RLC SDUs or RLC segments can be sent. The processors 1111 and 1211 are configured to consider retransmitting the RLC SDU with the highest SN among the RLC SDUs delivered to the MAC (or among the RLC SDUs sent to the receiving device) when the polling retransmission timer expires and when no new RLC SDUs or RLC SDU segments can be sent. In other words, the processors 1111 and 1211 are configured to select the RLC SDU with the highest SN among the RLC SDUs delivered to the MAC (or among the RLC SDUs sent to the receiving device) for retransmission when the polling retransmission timer expires and no new RLC SDUs or RLC SDU segments can be sent. Since the last transmission opportunity is the first transmission opportunity, the highest SN among the RLC SDUs delivered to the MAC (or sent to the receiving side) is the same as the highest SN among the SNs of the L RLC SDUs delivered / sent in the first transmission opportunity. In other words, the RLC SDU with the highest SN among the L RLC SDUs is selected as the RLC SDU to be retransmitted.
[0277] The processors 1111 and 1211 may form a new RLC PDU (hereinafter referred to as the second RLC PDU) including the second RLC SDU. The processors 1111 and 1211 may form a second RLC PDU including the poll and the second RLC SDU. When a transmission opportunity (hereinafter referred to as the second transmission opportunity) occurs, the processors 1111 and 1211 may deliver the second RLC PDU to the MAC. The processors 1111 and 1211 construct a MAC PDU including the second RLC PDU and transmit (or control the transceiver to transmit) the MAC PDU in the second transmission opportunity.
[0278] When constructing M RLC PDUs, once the M RLC PDUs are constructed, or while constructing the M RLC PDUs, the processor 1111, 1211 may update the state variable TX_Next. Just after constructing the M RLC PDUs, TX_Next will hold a value equal to "the highest SN of the M RLC PDUs + 1". The processor 1111, 1211 may be configured to update TX_Next whenever the processor 1111, 1211 constructs an RLC SDU containing SN = TX_Next or an RLC PDU of the last segment of an RLC SDU containing SN = TX_Next.
[0279] As described above, a detailed description of the preferred implementations of the present disclosure has been given to enable those skilled in the art to implement and practice the present disclosure. Although the present disclosure has been described with reference to exemplary implementations, it will be understood by those skilled in the art that various modifications and variations may be made to the present disclosure without departing from the spirit or scope of the present disclosure described in the appended claims. Therefore, the present disclosure should not be limited to the specific implementations described herein, but should be given the broadest scope consistent with the principles and novel features disclosed herein.
[0280] Industrial Applicability
[0281] Implementations of the present disclosure may be applied to a network node (eg, a BS), a UE, or other devices in a wireless communication system.
Claims
1. A communication device for sending a radio link control RLC protocol data unit PDU in a wireless communication system, the communication device comprising: Transceiver; at least one processor; as well as at least one computer memory operatively connectable to the at least one processor and having stored thereon instructions that, when executed, cause the at least one processor to perform operations comprising: constructing an RLC PDU for an RLC service data unit (SDU) at an RLC entity of the communication device, wherein each RLC PDU is constructed for a corresponding RLC SDU without waiting for a notification of a transmission opportunity from a medium access control (MAC) layer of the communication device; delivering one or more RLC PDUs for the transmission opportunity among the constructed RLC PDUs to the MAC layer of the communication device; Based on the one or more RLC PDUs delivered to the MAC layer for the transmit opportunity including a first RLC PDU with a poll to trigger a status report at a receiving RLC entity: based on delivering the first RLC PDU with the poll to the MAC layer, starting a polling retransmission timer; Based on the state that (i) the polling retransmission timer expires and (ii) no new RLC SDU can be sent: selecting, by the RLC entity of the communication device, an RLC SDU for retransmission, wherein the RLC SDU selected for retransmission has a highest sequence number SN among one or more RLC SDUs included in the one or more RLC PDUs delivered to the MAC layer; constructing a second RLC PDU including the selected RLC SDU; and The second RLC PDU including the selected RLC SDU is delivered to the MAC layer of the communication device.
2. The communication device according to claim 1, wherein: Constructing the second RLC PDU includes: The poll is included in the second RLC PDU.
3. The communication device according to claim 1, wherein: The operations also include: setting a state variable to 1 + the highest SN among the RLC PDUs constructed at the RLC entity, wherein the state variable holds the SN to be assigned to the newly generated RLC PDU, and Wherein, each time an RLC PDU including an RLC SDU or a last segment of an RLC SDU is constructed to have an SN equal to the state variable, the state variable is updated.
4. The communication device according to any one of claims 1 to 3, wherein: A highest SN among the one or more RLC SDUs delivered to the MAC layer for the transmission opportunity is smaller than a highest SN among RLC SDUs included in the RLC PDU constructed at the RLC entity.
5. The communication device according to any one of claims 1 to 3, in, In a state where the one or more RLC PDUs delivered to the MAC layer include more than one RLC PDU with the polling, the one or more RLC PDUs delivered to the MAC layer for the transmission opportunity are delivered to the MAC layer in response to a notification of the transmission opportunity from the MAC layer.
6. A processing device, the processing device comprising: at least one processor; as well as at least one computer memory operatively connectable to the at least one processor and having stored thereon instructions that, when executed, cause the at least one processor to perform operations comprising: constructing, at a radio link control RLC entity of the processing device, RLC protocol data units (PDUs) for RLC service data units (SDUs), wherein each RLC PDU is constructed for a corresponding RLC SDU without waiting for a notification about a transmission opportunity from a medium access control MAC layer of the processing device; delivering one or more RLC PDUs for the transmission opportunity among the constructed RLC PDUs to the MAC layer of the processing device; Based on the one or more RLC PDUs delivered to the MAC layer for the transmit opportunity including a first RLC PDU with a poll to trigger a status report at a receiving RLC entity: based on delivering the first RLC PDU with the poll to the MAC layer, starting a polling retransmission timer; Based on a state that (i) the polling retransmission timer expires and (ii) no new RLC SDU can be sent: selecting, by the RLC entity of the processing device, an RLC SDU for retransmission, wherein the RLC SDU selected for retransmission has a highest sequence number SN among one or more RLC SDUs included in the one or more RLC PDUs delivered to the MAC layer; constructing a second RLC PDU including the selected RLC SDU; and The second RLC PDU including the selected RLC SDU is delivered to the MAC layer of the processing device.
7. The processing device according to claim 6, wherein: Constructing the second RLC PDU includes: The poll is included in the second RLC PDU.
8. The processing device according to claim 6, wherein: The operations also include: setting a state variable to 1 + the highest SN among the RLC PDUs constructed at the RLC entity, wherein the state variable holds the SN to be assigned to the newly generated RLC PDU, and Wherein, each time an RLC PDU including an RLC SDU or a last segment of an RLC SDU is constructed to have an SN equal to the state variable, the state variable is updated.
9. A processing device according to any one of claims 6 to 8, wherein: A highest SN among the one or more RLC SDUs delivered to the MAC layer for the transmission opportunity is smaller than a highest SN among RLC SDUs included in the RLC PDU constructed at the RLC entity.
10. The processing device according to any one of claims 6 to 8, in, In a state where the one or more RLC PDUs delivered to the MAC layer include more than one RLC PDU with the polling, the one or more RLC PDUs delivered to the MAC layer for the transmission opportunity are delivered to the MAC layer in response to a notification of the transmission opportunity from the MAC layer.
11. A method for transmitting a radio link control (RLC) protocol data unit (PDU) by a communication device in a wireless communication system, the method comprising the following steps: constructing an RLC PDU for an RLC service data unit (SDU) at an RLC entity of the communication device, wherein each RLC PDU is constructed for a corresponding RLC SDU without waiting for a notification of a transmission opportunity from a medium access control (MAC) layer of the communication device; delivering one or more RLC PDUs for the transmission opportunity among the constructed RLC PDUs to the MAC layer of the communication device; Based on the one or more RLC PDUs delivered to the MAC layer for the transmit opportunity including a first RLC PDU with a poll to trigger a status report at a receiving RLC entity: based on delivering the first RLC PDU with the poll to the MAC layer, starting a polling retransmission timer; Based on the state that (i) the polling retransmission timer expires and (ii) no new RLC SDU can be sent: selecting, by the RLC entity of the communication device, an RLC SDU for retransmission, wherein the RLC SDU selected for retransmission has a highest sequence number SN among one or more RLC SDUs included in the one or more RLC PDUs delivered to the MAC layer; constructing a second RLC PDU including the selected RLC SDU; and The second RLC PDU including the selected RLC SDU is delivered to the MAC layer of the communication device.
12. The method according to claim 11, wherein: The step of constructing the second RLC PDU comprises the following steps: The poll is included in the second RLC PDU.
13. The method according to claim 11, further comprising the steps of: setting a state variable to 1 + the highest SN among the RLC PDUs constructed at the RLC entity, wherein the state variable holds the SN to be assigned to the newly generated RLC PDU, and Wherein, each time an RLC PDU including an RLC SDU or a last segment of an RLC SDU is constructed to have an SN equal to the state variable, the state variable is updated.
14. The method according to any one of claims 11 to 13, wherein: A highest SN among the one or more RLC SDUs delivered to the MAC layer for the transmission opportunity is smaller than a highest SN among SNs of RLC SDUs included in the RLC PDU constructed at the RLC entity.
15. The method according to any one of claims 11 to 13, in, In a state where the one or more RLC PDUs delivered to the MAC layer include more than one RLC PDU with the polling, the one or more RLC PDUs delivered to the MAC layer for the transmission opportunity are delivered to the MAC layer in response to a notification of the transmission opportunity from the MAC layer.
