Communication method and apparatus, and computer storage medium
By updating state variables in RLC AM mode to optimize the triggering of state reports, unnecessary retransmissions are avoided, thus improving the reliability and efficiency of data transmission.
Patent Information
- Application Number
- PCT/CN2026/079747
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-06-25
- Filing Date
- 2026-02-24
- Publication Date
- 2026-11-12
AI Technical Summary
In the existing RLC AM mode, the status report triggering mechanism may lead to unnecessary retransmissions, affecting data transmission efficiency.
Before constructing and sending control packets, update the state variables to ensure that ACK_SN reaches the maximum SN of a fully received RLC SDU, thus avoiding unnecessary retransmissions.
This effectively avoids unnecessary retransmissions and improves the reliability and efficiency of data transmission.
Smart Images

Figure CN2026079747_12112026_PF_FP_ABST
Abstract
Description
A communication method, apparatus, and computer storage medium
[0001] This application claims priority to Chinese Patent Application No. 202510603885.2, filed on May 9, 2025, entitled "A Communication Method, Apparatus and Computer Storage Medium", and to Chinese Patent Application No. 202510869367.5, filed on June 25, 2025, entitled "A Communication Method, Apparatus and Computer Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of communication technology, and in particular to a communication method, apparatus and computer storage medium. Background Technology
[0003] Extended Reality (XR) is an innovative digital experience platform that integrates Virtual Reality (VR) and Augmented Reality (AR) technologies. To better support XR services, 3GPP Release 19's Radio Link Control (RLC) layer initiated enhancement research, primarily focusing on enhancing the RLC acknowledged mode (AM). Specifically, RLC AM mode requires the RLC transmitting entity to receive an acknowledgment report from the receiving end before ceasing to maintain the data packet.
[0004] RLC AM relies on feedback (status reports: a type of control PDU) and retransmissions to ensure transmission reliability. In existing schemes, a status report is triggered when the timer t-Reassembly times out and when the timer t-RxDiscard times out. Furthermore, to ensure successful transmission before data packets expire, the sender can initiate enhanced polling to request the receiver to return a status report in a timely manner, which may also trigger a status report. These status report triggering mechanisms may cause unnecessary retransmissions. Summary of the Invention
[0005] To address the aforementioned issues, this application provides a communication method, apparatus, and computer storage medium that are optimized for different triggering scenarios of status reports, thereby avoiding unnecessary retransmissions.
[0006] In a first aspect, this application provides a communication method applied to the receiving end of a Radio Link Control (RLC) entity, comprising: constructing and transmitting control data packets.
[0007] Before the control data packet is triggered, the first state variable is updated. The first state variable stores the next SN of the maximum sequence number SN of the SDU that determines the reception status. By updating the first state variable in advance, it is ensured that the ACK_SN in the constructed data packet can reach the maximum SN of the fully received RLC SDU, thus avoiding unnecessary retransmissions.
[0008] Alternatively, control packets can be constructed based on different state variables. Specifically, when constructing a control packet based on a first state variable and the first field indicates the packet type, the ACK_SN during control packet construction can reach the maximum SN of the fully received RLC SDU. Furthermore, the first field indicates that the control packet is triggered by a timer timeout, thus avoiding unnecessary retransmissions. When constructing a control packet based on a second state variable and the first field indicates the control packet type, the second state variable stores the next SN of the maximum SN of the SDU determining the reception status, as well as the SN of the next SDU expected to be received in sequence. The second state variable maintains the maximum value of the ACK_SN in the control packet, ensuring that the maximum value of the ACK_SN during control packet construction can reach the maximum SN of the fully received RLC SDU. The control packet is constructed based on the maximum SN of the SDU, and the first field indicates that the control packet is triggered by a timer timeout, thus avoiding unnecessary retransmissions. When the control packet is constructed based on the third state variable and the first field indicates the type of control packet, the third state variable stores the SN of the next SDU expected to be received in order, and the first field indicates whether the timer for triggering the control packet is t-RxDiscard or t-reassembly, thus avoiding unnecessary retransmissions in the case of timer timeout. When the control packet is constructed based on the third and fourth state variables, the fourth state variable stores the next SN of the SDU with the highest SN among the confirmed received RLC SDUs. At this time, the ACK_SN can be determined based on the third and fourth state variables, as well as the SN of the successfully received SDUs whose SN is greater than or equal to the third state variable and less than the fourth state variable, thus avoiding unnecessary retransmissions.
[0009] In summary, the method provided in this application can update the first state variable used to construct the control data packet in advance before the control data packet is triggered, or can construct and send control data packets of the corresponding type using different state variables, so as to avoid unnecessary retransmissions.
[0010] In one possible implementation, the control packet can be triggered by a timer timeout, or by an enhanced polling indication or a polling indication. The timer can be a first timer or a second timer. The first timer starts when a SN gap exists, and upon timeout, any SDUs not successfully received within the SN gap are considered outdated; that is, the first timer is t-RxDiscard. The second timer starts when a SN gap exists, and upon timeout, any SDUs not successfully received within the SN gap are considered reception failures; that is, the second timer is t-reassembly. The first field can be used to indicate the triggering condition of the control packet.
[0011] In one possible implementation, when the first state variable is updated before the control packet is triggered, if the first timer times out and the first state variable is not greater than the third state variable, or not greater than the fifth state variable, or not greater than the minimum of the third and fifth state variables, the first state variable is updated to the SN of the first RLC SDU that is not fully received, and is not less than the third state variable, or not less than the fifth state variable, or not less than the maximum of the third and fifth state variables. In this implementation, the first timer is t-RxDiscard, the third state variable is RX_Next, and the fifth state variable is RX_Next_Discard_Trigger. By updating the first state variable in advance, it is ensured that the ACK_SN in the constructed packet can reach the maximum SN of the fully received RLC SDU, avoiding unnecessary retransmissions.
[0012] In one possible implementation, before the trigger packet is generated, the first state variable is updated as follows: When the first timer expires, the first state variable is updated to a value not less than the current first state variable, and not less than the third state variable, or not less than the fifth state variable, or not less than the maximum value of the third and fifth state variables, and the SN of the first RLC SDU that has not been fully received; when the second timer expires and the receiver of the RLC entity has enabled the first timer, the first state variable is updated to a value not less than the current first state variable, and not less than the third state variable, or not less than the sixth state variable, or not less than the maximum value of the third and sixth state variables, and the SN of the first RLC SDU that has not been fully received. In this implementation, the fifth state variable is RX_Next_Discard_Trigger, the sixth state variable is RX_Next_Status_Trigger, and the second timer is t-reassembly.
[0013] In one possible implementation, when the third state variable is not greater than the first state variable, when constructing and sending the control data packet, the first data packet is constructed based on the updated first and third state variables, so that the ACK_SN in the first data packet can reach the maximum SN of the fully received RLC SDU, thus avoiding unnecessary retransmissions.
[0014] In one possible implementation, the control data packet is constructed based on a second state variable. When the second state variable is not less than the first state variable, the next SN of the maximum SN of the SDU with the determined reception state in the constructed first data packet is determined based on the second state variable; then the first data packet is sent. In this implementation, the second state variable can be an updated definition of the existing RX_Next variable, allowing RX_Next to additionally store the next SN of the maximum SN of the SDU with the determined reception state. Using the second state variable, the ACK_SN in the first data packet can reach the maximum SN of the fully received RLC SDU, avoiding unnecessary retransmissions.
[0015] In one possible implementation, when the third state variable is greater than or equal to the first state variable, a control data packet is constructed and sent as a second data packet. This second data packet indicates the next SN after the largest SN of the SDU determining the reception status, but does not include information indicating the SN of the SDU that failed to receive. That is, the status report triggered by the t-RxDiscard timeout only contains ACK information, not NACK. The ACK_SN in the second data packet can be maintained by RX_Next, allowing the ACK_SN in the second data packet to be set to the maximum possible value, thereby avoiding unnecessary retransmissions.
[0016] In one possible implementation, constructing and sending the second data packet includes: when the first timer expires, determining the next SN of the largest SN of the SDU determining the reception status in the second data packet based on a third state variable; when the third timer is not running or expires, if the third state variable is greater than the first state variable, assembling the second data packet at the first transmission opportunity indicated by the lower layer and submitting it to the lower layer for transmission to the receiving end of the RLC entity. In this implementation, the second data packet and the first data packet can be limited by the same third timer t-StatusProhibit, avoiding the introduction of additional timers and simplifying control.
[0017] In one possible implementation, constructing and sending the second data packet includes: when the first timer times out, determining the next SN of the largest SN of the SDU with the determined reception state in the second data packet based on a third variable; assembling the second data packet and submitting it to the lower layer for transmission to the receiving end of the RLC entity. In this implementation, the transmission of the second data packet is not limited by any timer and does not affect the operation of any timer, avoiding the introduction of additional timers and simplifying control.
[0018] In one possible implementation, constructing and sending the second data packet includes: when the first timer expires, determining the next SN of the maximum SN of the SDU with a determined reception state in the second data packet based on a third variable; when the fourth timer is not running or expires, assembling the second data packet at the first transmission opportunity indicated by the lower layer and submitting it to the lower layer for transmission to the receiving end of the RLC entity; and when the second data packet has been submitted to the lower layer, starting the fourth timer; when the fourth timer is running, after the fourth timer expires, assembling the second data packet at the first transmission opportunity indicated by the lower layer and submitting it to the lower layer for transmission to the receiving end of the RLC entity.
[0019] In this implementation, the transmission of the second data packet is restricted by a separate fourth timer. This fourth timer is a new timer added specifically for the second data packet and is not the same timer as the third timer t-StatusProhibit. This approach not only restricts the frequent transmission of the second data packet but also avoids affecting the transmission of the first data packet due to sharing the third timer.
[0020] In one possible implementation, when the third state variable is greater than or equal to the first state variable, a third data packet is constructed and sent. The third data packet indicates the SN of the SDU that determines the reception status, but does not include indication information for the SN of the SDU that determines the reception failure.
[0021] In one possible implementation, the maximum SN of the SDU indicating the receiving state as indicated by the third data packet is equal to the third state variable when the enhanced polling indication or polling indication is received; the SN of other SDUs indicating the receiving state as indicated by the third data packet is greater than or equal to the third state variable when the enhanced polling indication or polling indication is received, and less than the fourth state variable.
[0022] The third data packet indicates the SN of the SDU that determines the reception status, but does not include the indication information for the SN of the SDU that failed to receive. Furthermore, the first ACK_SN indicated by it is maintained by the third state variable when the enhanced polling indication or polling indication is received, so that the first ACK_SN in the third data packet can be set to the maximum possible value, thereby avoiding unnecessary retransmissions.
[0023] In one possible implementation, the third data packet and the first data packet can be restricted by the same third timer t-StatusProhibit, avoiding the introduction of additional timers and simplifying control. Specifically, when the third timer is not running or the third timer expires, if the third status variable is greater than the first status variable, the third data packet is assembled and delivered to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity.
[0024] In one possible implementation, the transmission of the third data packet can be unrestricted by any timer and does not affect the operation of any timer, thus avoiding the introduction of additional timers and simplifying control. Specifically, upon receiving an increment instruction or polling instruction, the third data packet is assembled and sent.
[0025] In one possible implementation, the transmission of the third data packet is restricted by a separate fifth timer. This fifth timer is a new timer added specifically for the third data packet and is not the same timer as the third timer t-StatusProhibit. This approach limits the frequent transmission of the third data packet while preventing the first data packet from being affected by sharing the third timer. Specifically, when the fifth timer is not running or has expired, the third data packet is assembled and submitted to the lower layer at the first transmission opportunity indicated by the lower layer and transmitted to the receiving end of the RLC entity. Conversely, when the third data packet has already been submitted to the lower layer, the fifth timer is started. When the fifth timer is running, after its expiration, the third data packet is assembled and submitted to the lower layer at the first transmission opportunity indicated by the lower layer and transmitted to the receiving end of the RLC entity.
[0026] In one possible implementation, the third data packet further includes at least one of the following indication fields: a second field, a third field, a fourth field, a fifth field, a sixth field, and a seventh field. The second field indicates whether there is another set of SDUs with a determined reception state following the SN of the corresponding SDU with a determined reception state, or the second field, the third field, or the fourth field; the third field indicates whether there is a set of fifth and sixth fields following the SN of the corresponding SDU with a determined reception state; the fourth field indicates whether there are consecutively received SDUs following the SN of the corresponding SDU with a determined reception state; the fifth field indicates the start position of the received SDU portion whose SN is equal to the SN of the corresponding SDU with a determined reception state; the sixth field indicates the end position of the received SDU portion whose SN is equal to the SN of the corresponding SDU with a determined reception state; and the seventh field indicates the number of consecutive RLC SDUs with a determined reception state.
[0027] In one possible implementation, if the receiving end of the RLC entity determines that no SDU with a larger ACK_SN than the one in the previous data packet has been successfully received, the size and complexity of the data packet can be reduced by sending a fourth data packet. In this implementation, the receiving end of the RLC entity uses a seventh state variable to store the next SN of the largest SN of the SDU that determined the reception status of the last sent control data packet.
[0028] In one possible implementation, the transmission of the fourth data packet can be unrestricted by any timer and does not affect the operation of any timer, thus avoiding the introduction of additional timers and simplifying control. In this case, the transmission conditions for the fourth data packet can be: the first timer times out, the second timer times out, or the receipt of the enhanced polling instruction or polling instruction.
[0029] In one possible implementation, the fourth data packet and the first data packet can be restricted by the same third timer t-StatusProhibit, avoiding the introduction of additional timers and simplifying control. In this case, the transmission conditions of the fourth data packet can be: the first timer expires, and the third timer expires or is not started; or, the second timer expires, and the third timer expires or is not started; or, an enhanced polling indication or a polling indication is received, and the third timer expires or is not started.
[0030] In one possible implementation, the transmission of the fourth data packet is restricted by a separate sixth timer. This sixth timer is a new timer added specifically for the fourth data packet and is not the same timer as the third timer t-StatusProhibit. This approach limits the frequent transmission of the fourth data packet while preventing the first data packet from being affected by sharing the third timer. In this case, the transmission conditions for the fourth data packet can be: the first timer times out, and the sixth timer times out or is not started; or, the second timer times out, and the sixth timer times out or is not started; or, an enhanced polling instruction or a polling instruction is received, and the sixth timer times out or is not started.
[0031] Secondly, this application provides a communication method applied to the sending end of an RLC entity, comprising: receiving a control data packet, wherein, before the control data packet is triggered, a first state variable is updated; or, the control data packet is constructed based on the first state variable, or based on a second state variable, or based on a third state variable, or based on a third state variable and a fourth state variable, wherein the type of the constructed control data packet is indicated by a first field.
[0032] In this implementation, the first state variable used to construct the control data packet can be updated in advance before the control data packet is triggered, or different state variables can be used to construct and send control data packets of the corresponding type to avoid unnecessary retransmissions.
[0033] In one possible implementation, for the sending end of the RLC entity, when it is determined that the first data packet has been received based on the first field, the first indication information is submitted to the upper layer based on the first data packet. The first indication information indicates the SN of the SDU that determines the reception status.
[0034] In one possible implementation, for the sending end of the RLC entity, when it is determined that the second data packet has been received based on the first field, the second indication information is submitted to the upper layer based on the second data packet. The second indication information indicates the SN of the SDU that determines the reception status.
[0035] In one possible implementation, for the sender of the RLC entity, when it is determined, based on the first field, that a third data packet has been received, third indication information is submitted to the upper layer based on the third data packet. The third indication information indicates the SN of the SDU that determines the reception status and / or the received SDU portion of the SDU that determines the reception status.
[0036] In one possible implementation, for the sender of the RLC entity, when the control data packet is determined to be the fourth data packet based on the first field, the fourth indication information is submitted to the upper layer based on the fourth data packet. The fourth indication information indicates that the SN is less than the next SN of the largest SN of the SDU indicating the reception status as indicated by the previously received control data packet, and that the SDU reception is successful if it is not the largest SN of the SDU indicating the reception failure as indicated by the previously received control data packet.
[0037] Thirdly, this application also provides a communication device, which includes a processor and a memory. The processor is coupled to the memory; the memory is used to store instructions; the processor is used to execute the computer program or instructions stored in the memory to implement the methods described above.
[0038] In one possible implementation, the communication device is a terminal device.
[0039] In one possible implementation, the communication device is a network device.
[0040] Fourthly, this application also provides a computer storage medium for storing a computer program, which, when executed, implements the method described above.
[0041] Fifthly, this application also provides a communication system that includes the terminal equipment and network equipment described above. Optionally, the communication system may further include other equipment that communicates with the terminal equipment and / or network equipment.
[0042] Sixthly, this application also provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform a method in any of the possible implementations of any of the above aspects.
[0043] Seventhly, this application also provides a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices.
[0044] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data. Attached Figure Description
[0045] Figure 1 is a schematic diagram of a communication system applied in an embodiment of this application;
[0046] Figure 2 is a schematic diagram of an application scenario applicable to this application;
[0047] Figure 3 is a schematic diagram of another application scenario applicable to this application;
[0048] Figure 4 is a schematic diagram of the user plane protocol stack provided in this application;
[0049] Figure 5 is a schematic diagram of the control plane protocol stack provided in this application;
[0050] Figure 6 is a schematic diagram of the format of the status report provided in this application;
[0051] Figure 7 is a flowchart of a communication method provided in an embodiment of this application;
[0052] Figure 8 is a flowchart of another communication method provided in an embodiment of this application;
[0053] Figure 9 is a flowchart of another communication method provided in an embodiment of this application;
[0054] Figure 10 is a flowchart of another communication method provided in an embodiment of this application;
[0055] Figure 11 is a flowchart of another communication method provided in an embodiment of this application;
[0056] Figure 12 is a schematic diagram of the format of a second data packet provided in an embodiment of this application;
[0057] Figure 13 is a flowchart of another communication method provided in an embodiment of this application;
[0058] Figure 14 is a flowchart of another communication method provided in an embodiment of this application;
[0059] Figure 15 is a flowchart of another communication method provided in an embodiment of this application;
[0060] Figure 16 is a schematic diagram of the format of the third data packet provided in an embodiment of this application;
[0061] Figure 17 is a flowchart of another communication method provided in an embodiment of this application;
[0062] Figure 18 is a schematic diagram of the format of the fourth data packet provided in an embodiment of this application;
[0063] Figure 19 is a schematic diagram of a communication device provided in an embodiment of this application;
[0064] Figure 20 is a schematic diagram of a network device provided in an embodiment of this application;
[0065] Figure 21 is a schematic diagram of another network device provided in an embodiment of this application;
[0066] Figure 22 is a schematic diagram of a terminal device provided in an embodiment of this application. Detailed Implementation
[0067] The terminology used in the following embodiments is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to also include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, “one or more” means one, two, or more; “and / or” describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character “ / ” generally indicates that the preceding and following related objects are in an “or” relationship.
[0068] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.
[0069] In this application, "multiple" refers to two or more embodiments. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for descriptive purposes and should not be construed as indicating or implying relative importance, nor as indicating or implying order.
[0070] The technical solutions provided in this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) systems, General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of these applications.
[0071] Referring to Figure 1, this figure is a schematic diagram of a communication system applied in an embodiment of this application.
[0072] The wireless communication system includes an access network 400 and a core network 200. Optionally, the communication system may also include an Internet 300.
[0073] The radio access network 100 can be a next-generation (e.g., 6G or higher) radio access network or a traditional (e.g., 5G, 4G, 3G or 2G) radio access network.
[0074] One or more terminal devices 420 (only one is shown in the figure) can be interconnected or connected to one or more network devices in the access network 400. In Figure 1, the access network 400 includes network devices 410a and 410b as an example.
[0075] The network equipment in this application can be network-side equipment such as access network equipment and core network equipment. Access network equipment is sometimes also called access node. Access network equipment has wireless transceiver capabilities and is used to communicate with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the above-mentioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units that can implement some of the functions of a base station. Access network equipment can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, access network equipment can also be a server, wearable device, or vehicle-mounted equipment, etc. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology or device form used in the access network equipment. In this application, the access network equipment is referred to as a network device.
[0076] In this application, the means for implementing the functions of a network device can be a network device itself, or a means capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This means can be installed in or connected to the network device. In the technical solutions provided in this application, the example of a network device being used to implement the functions of a network device is used to describe the technical solutions provided in this application.
[0077] The terminal device in this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The wireless terminal device can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the terminal device.
[0078] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solutions provided in this application, the example of a terminal device being used to implement the functions of a terminal device is used to describe the technical solutions provided in this application.
[0079] Access network devices and / or terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network devices and terminals. Access network devices and terminal devices can be deployed in the same or different scenarios; for example, both can be deployed on land; or the access network device can be deployed on land, and the terminal device on water, etc., and so on.
[0080] In practical applications, multiple network devices can collaborate to assist terminals in achieving wireless access, with different network devices each implementing some of the functions of a base station. For example, network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).
[0081] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.
[0082] See Figure 2, which is a schematic diagram of an application scenario applicable to this application.
[0083] As shown in Figure 2, the embodiments of this application can be applied to the field of extended reality (XR) business.
[0084] XR is an innovative digital experience platform that integrates Virtual Reality (VR) and Augmented Reality (AR) technologies. By utilizing computer graphics, perception technology, and human-computer interaction technology, XR merges virtual information with real-world scenes, enabling users to interact with the virtual world in real time. XR service data packets mainly consist of video / images and interactive commands, and their network requirements include high throughput, low latency, and high reliability.
[0085] The business scenario includes AF network elements and multiple XR devices, such as XR device 1 and XR device 2.
[0086] In this example, the AF network element can be an XR server, and the XR device can be an XR head-mounted display (HMD) or XR glasses. The XR device can also include a controller, such as a gamepad. In this example, XR device 1 can be XR glasses, and XR device 2 can be a gamepad. Users can wear XR glasses and hold the gamepad to play cloud games.
[0087] The XR server can receive video frames, audio data, haptic data, or pose and control data from the XR device, such as video frames and audio data captured by the XR glasses, and haptic data and pose and control data captured by the controller. It then returns the processed video frames, audio data, haptic data, or pose and control data to the XR device. The XR server and XR device interact with each other through communication links in the network architecture, forming a global control loop. The video frames mentioned above can also be referred to as video data or video frame data.
[0088] In multimodal service application scenarios, multiple data streams are required, such as QoS streams, to transmit different data types, including video, audio, haptic feedback, or gesture and control data. These data streams are spatially and temporally correlated.
[0089] In the example of Figure 2, data collected by the XR device, such as video frames, audio data, haptic data, gesture and control data, can be transmitted from the terminal device to the access network, for example, to an access network device, such as a gNB. The access network device can transmit the above data to the 5GC through QoS flow, and then the 5GC transmits the above data to the XR server.
[0090] It should be noted that XR devices can also communicate directly with access network devices. For example, if an XR device integrates an eSIM or UE functionality, it can directly connect to the access network device. Consequently, the XR device can directly transmit collected data to the access network device, for example, via QoS flow, without going through the UE. Alternatively, the terminal can be located inside the XR device. For example, terminal 1 can be located inside XR device 1, and terminal 2 can be located inside XR device 2. XR devices 1 and 2 can then directly interact with the access network device.
[0091] Correspondingly, the XR server can return multimodal data streams to the XR device. Specifically, the XR server can first return multimodal data streams to the 5GC, which then transmits the multimodal data streams to the access network device via QoS flow. The access network device then transmits the multimodal data streams to the corresponding UEs, and the UEs finally transmit the received data streams to the XR device. Multimodal data streams can be transmitted using PDU sets. PDU sets can package data from different modalities together for transmission as a whole, simplifying data processing and transmission, improving efficiency, and ensuring synchronous transmission and processing of data from different modalities.
[0092] It should be noted that Figure 2 illustrates a multimodal scenario where multiple XR devices connect to the network through different terminals, such as an inter-UE multimodal scenario. In other possible implementations of this application, the application scenario may also include a multimodal scenario where multiple XR devices connect to the network through the same terminal, such as an intra-UE multimodal scenario.
[0093] As shown in Figure 3, multiple XR devices can connect to the network through the same terminal. This terminal can serve as a unified entry or exit point for the multiple XR devices, enabling interaction with the XR server. The multiple XR devices can include XR Device 1 and XR Device 2. In the example in Figure 3, XR Device 1 can be XR glasses, which can collect video and audio data. XR Device 2 can be a controller, which can collect tactile, posture, and control data. XR Device 1 and XR Device 2 are connected to the same terminal, and the data collected by XR Device 1 and XR Device 2 can be transmitted to the access network device through the terminal.
[0094] Figures 2 and 3 above illustrate only two XR devices. This application can be applied to multiple XR devices, and is not limited to two. Furthermore, the XR devices described above can also be replaced with other sensing devices, and this application does not impose any restrictions on this.
[0095] Besides the application scenarios involving the architecture between the application server and terminal devices described above, the application scenarios of this application can also be constructed using multiple terminal devices. In a scenario constructed using multiple terminal devices, one terminal device may include an Extended Reality Head-Mounted Display (XR HMD) and a controller, while the other terminal device may include a remote robot. Users can control the remote robot through the controller, combining the content presented by the XR HMD. The construction of the application scenarios of this application is not limited to the above scenarios; all application scenarios applicable to the technical solutions of this application are within the protection scope of this application.
[0096] In addition to the above scenarios, this application solution can also be applied to scenarios with multimodal services such as healthcare, road traffic, and distance education, which will not be elaborated on again.
[0097] The data transmission methods in the above scenarios are explained below, along with a brief explanation of the relevant data. Optionally, explanations of some terms can also be found in the 3rd Generation Partnership Project (3GPP) standard protocol.
[0098] See Figure 4, which is a schematic diagram of the user plane protocol stack provided in this application.
[0099] The user plane protocol stack is used to transmit service data and includes the Physical Layer (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP).
[0100] Specifically, the physical layer provides a transmission channel for the MAC layer; the MAC layer provides a logical channel for the RLC layer; the RLC layer provides an RLC channel for the PDCP layer; the PDCP layer provides a radio bearer for the SDAP layer; and the SDAP layer provides a Quality of Service (QoS) flow for the 5GC.
[0101] The technical solution of this application mainly involves the PDCP layer and RLC layer of the user plane protocol stack.
[0102] Service Data Unit (SDU):
[0103] An SDU is a data packet received by this layer from the upper layer. For example, a data packet received by the RLC layer from the upper PDCP layer is called an RLC SDU.
[0104] Protocol Data Unit (PDU):
[0105] A PDU is a data packet processed by this layer after processing an SDU (adding header information, etc.). For example, the data packet that RLC processes an RLC SDU and delivers to the lower-layer MAC is an RLC PDU. The RLC layer has three transport modes: transport mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). Therefore, RLC PDUs can be referred to as TMD PDU, UMD PDU, and AMD PDU according to their mode.
[0106] See also Figure 5, which is a schematic diagram of the control plane protocol stack provided in this application.
[0107] The control plane protocol stack is used to transmit control data. This application mainly involves the Radio Resource Control (RRC) layer, the PDCP layer, and the RLC layer. The network side can configure the characteristics and related parameters of PDCP and RLC through RRC signaling, such as configuring timer durations and various threshold values.
[0108] PDU Set:
[0109] One or more PDUs are used to carry the payload of an information unit generated at the application layer (e.g., a frame or video clip of an XR service). PDUs belonging to the same set generally have the same QoS requirements, such as the same Packet Delay Budget (PDB), which can also be understood as the remaining time. PDUs in a PDU set correspond to PDCP SDUs.
[0110] pdu-SetDiscard:
[0111] The PDCP entity, PDU, has a drop parameter. If this parameter is configured, all packets in a PDU set will be processed in the same way.
[0112] discardTimer:
[0113] The PDCP entity discards a timer, which is configured only for the data radio bearer (DRB), and the duration of the timer is configured by the upper layer RRC TS 38.331[3]. In the transmitting end, a new timer is started when an SDU is received from the upper layer.
[0114] The following explains the behavior of enabling discardTimer.
[0115] When a PDCP SDU is received from the upper layer, the sending PDCP entity should:
[0116] If discardTimerForLowImportance is configured, and SDU discarding behavior based on PDU Set Importance (PSI) is activated, and the PDCP SDU belongs to a low-importance PDU set, then discardTimerForLowImportance associated with the PDCP SDU is enabled; otherwise, discardTimer associated with the PDCP SDU is enabled.
[0117] The PSI parameter indicates the relative importance of a PDU set within the QoS flow. Generally, a larger PSI value indicates a lower PDU set importance, and a smaller PSI value indicates a higher PDU set importance. For example, a PSI value of 0 indicates the highest importance PDU set, and a PSI value of 15 indicates the lowest importance PDU set. In the event of congestion, the PSI can be used to determine whether a PDU set should be dropped; for instance, packets with lower importance as indicated by the PSI value can be dropped during congestion.
[0118] The following explains the timeout behavior of discardTimer.
[0119] When the discardTimer or discardTimerForLowImportance of a PDCP SDU expires, the sending PDCP entity should: if pdu-SetDiscard is configured, discard all PDCP SDUs belonging to the PDU set to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs; if subsequent PDCP SDUs received from the upper layer belong to the same PDU set, they should also be discarded; otherwise, discard the PDCP SDU and the corresponding PDCP data PDUs.
[0120] If the corresponding PDCP data PDU has been submitted to the lower layer, PDCP provides a discard instruction to the lower layer.
[0121] Segmentation:
[0122] When the underlying MAC layer provides transmission opportunities (transmission resource size, etc.), it may not be sufficient to transmit the entire Found Mode Data (AMD) PDU. This can result in a situation where the final resource size is only enough to transmit a portion of the AMD PDU. In this case, it is necessary to segment the RLC SDU within the AMD PDU and then generate new, different AMD PDUs with the same serial number.
[0123] Polling mechanism:
[0124] An AM RLC entity (sender) can poll its peer AM RLC entity (receiver) to trigger a status report at the peer AM RLC entity (the status report contains information on the success / failure of receiving some SDUs).
[0125] The following explains the triggering conditions for Poll.
[0126] When a lower layer notifies of a transmission opportunity, for each AMD PDU submitted for transmission, if the AMD PDU contains an RLC SDU that has not been previously transmitted or an RLC SDU segment containing a previously untransmitted byte segment, the transmitter of the AM RLC entity should:
[0127] Increment PDU_WITHOUT_POLL by one. PDU_WITHOUT_POLL is initially set to 0. It calculates the number of AMD PDUs sent since the transmission of the most recent polling bit.
[0128] Add BYTE_WITHOUT_POLL to each new data field element byte that it maps to in the AMD PDU data field. BYTE_WITHOUT_POLL is initially set to 0 and it calculates the number of data bytes sent since the transmission of the most recent polling bit.
[0129] If PDU_WITHOUT_POLL >= pollPDU, or if BYTE_WITHOUT_POLL >= pollByte: Polling is included in the AMD PDU. Here, pollPDU is the parameter used by the sender of each RLC entity to trigger polling for each pollPDU PDU, and pollByte is the parameter used by the sender of each RLC entity to trigger polling for each pollByte byte. If the sender of the RLC entity is a UE, the UE receives the configured pollPDU and pollByte from the network side (e.g., BS) via RRC signaling.
[0130] When the lower layer notifies of a transmission opportunity, for each AMD PDU that submits a transmission, the transmission party of the AM RLC entity should:
[0131] If, after transmitting the AMD PDU, both the transfer buffer and the retransmission buffer become empty (excluding transmitted RLC SDUs or RLC SDU segments awaiting acknowledgment); or,
[0132] If a new RLC SDU cannot be transferred after the AMD PDU is transferred (e.g., due to window freeze);
[0133] Polling is included in AMD PDU.
[0134] When data is waiting at the upper layer, an empty RLC buffer (excluding transmitted RLC SDUs or RLC SDU segments awaiting acknowledgment) should not cause unnecessary polling.
[0135] All RLC SDUs received from the upper layer are placed in the transmission buffer, and the transmitted RLC SDUs are placed in the retransmission buffer.
[0136] Discard Instructions:
[0137] When an upper layer (e.g., PDCP) instructs the discard of a specific RLC SDU, if neither the RLC SDU nor its fragments have been committed to the lower layer, the sender of the AM RLC entity or the sending UM RLC entity should discard the instructing RLC SDU. The sender of the AM RLC entity should not introduce an RLC SN gap when discarding the RLC SDU.
[0138] If the RLC AM entity supports "avoid unnecessary retransmissions," then all SDUs transmitted by that TX RLC entity must adhere to this feature. When the TX RLC entity receives a discard instruction for an SDU (an SDU that has been submitted to the MAC layer) from the PDCP, the TX RLC entity will treat that SDU as an obsolete SDU. The TX RLC entity will not perform any transmission or retransmission of that SDU / SDU segment.
[0139] The following diagram illustrates the format of the existing Status Report (SR).
[0140] See Figure 6, which is a schematic diagram of the format of the status report provided in this application.
[0141] The SR includes the payload and the RLC control PDU header. 1 Oct in Figure 6 is 8 bits. The formats shown in parts (A) and (B) of Figure 6 are identical except for the SN length. The SN of the STATUS PDU in part (A) is 12 bits, and the SN of the STATUS PDU in part (B) is 18 bits.
[0142] RLC control PDU header: Includes D / C and the type of control PDU (Control PDU Type, CPT), totaling 4 bits. D / C is 1 bit, indicating whether the PDU is a Data PDU or a Control PDU, with a value of 0 / 1.
[0143] CPT: 3 bits in length, currently 000, indicating STATUS Report. Other values 001-111 are invalid.
[0144] Payload: Valid control information within the control PDU. Currently, only 000 (STATUS Report) is valid in the CPT. Its payload carries information about the RLC AM receiver's reception of data packets.
[0145] ACK_SN: The largest SN of the SDU used to determine the reception status. It can be understood that, excluding the SDUs with NACK_SN, all SDUs with SNs less than ACK_SN have been successfully received. Therefore, ACK_SN can represent the SN of the next SDU that has not yet been received.
[0146] E1: 1 bit. Indicates whether to follow a set of NACK_SN, E1, E2 and E3.
[0147] R: Reserved bit. Used for byte alignment.
[0148] NACK_SN: Indicates the SN of the SDU that failed to receive.
[0149] E2 indicates whether there is segmentation (a set of SOstart and SOend), mainly used for handling incomplete reception scenarios. SOstart indicates the starting byte of the original SDU for a lost SDU portion where SN equals NACK_SN, and SOend indicates the ending byte of the original SDU for a lost SDU portion where SN equals NACK_SN.
[0150] E3 indicates whether there are consecutive SN SDU reception failures (NACK range).
[0151] The NACK range field indicates that there are several consecutive RLC SDUs lost from NACK_SN.
[0152] Take (A) as an example:
[0153] Oct1-3 includes: RLC control PDU header (D / C and CPT) and information on successful SDU reception (ACK_SN, E1, and reserved bit R);
[0154] Oct4-5, Oct6-12, Oct13-… represent the scenarios of a failed SDU reception, such as all SDU reception failures, partial reception failures, and several consecutive SDU reception failures (corresponding to the NACK range) for an SDU with SN=NACK_SN.
[0155] The following describes how to generate the content in an SR.
[0156] TX sends data packets in order (the order is marked by SN), and RX expects to receive them in order. However, due to the passage through a wireless air interface, RX may not be able to receive data packets in order.
[0157] When there is a gap in the RX receiving data packets (SN gap, for example, receiving 8 after 5), the RX does not immediately confirm that the SDU reception within the gap has failed, but waits for a period of time (starting a timer t-Reassembly).
[0158] If the t-Reassembly timeout occurs and the SDU is still not fully received within the interval (e.g., SDUs 5, 6, and 8 are fully received, but SDU 7 is still not successfully received), a status report will be triggered. SDUs that are not successfully received are confirmed as reception failures.
[0159] If sending status reports is permitted at this point (a prohibition timer, t-StatusProhibit, prevents excessive SR transmission; multiple triggers may occur during the prohibition timer's operation, and the SR only assembles the latest result when transmission is permitted), status report assembly begins. Continuing with the previous example, ACK_SN is the first unreceived SN not less than the upper boundary of the gap (SN=8) (while waiting for the gap SDU to be received, other SDUs are still being received; when the quiescent timer expires, 9 and 10 may also be successfully received. In this case, ACK_SN can be set to 11). NACK_SN is the SDU information that was not successfully received (i.e., the SDU corresponding to SN 7; depending on whether all or part of the reception failed, it determines whether to fill in other fields SOstart, SOend, and NACK range).
[0160] To better support XR services, 3GPP Release 19's RLC layer initiated enhancement technology research, primarily focusing on enhancing RLC AM mode. RLC AM refers to a mechanism where the RLC transmitting entity only ceases to maintain the data packet after receiving an acknowledgment report from the receiving end following data transmission.
[0161] RLC AM relies on feedback (status reports: a type of control PDU) and retransmission to ensure transmission reliability. A packet containing the NACK_SN from a status report will only be retransmitted when the TX receives the status report.
[0162] Short-latency XR packets don't have time to wait for status reports and may expire before retransmission, thus failing to meet quality of service (low latency) requirements. To ensure successful transmission before packet expiration, timely retransmission is necessary. Current timely retransmission schemes trigger either autonomous retransmission or enhanced polling when the remaining time of a packet is below a certain threshold. Autonomous retransmission without a status report means retransmission is no longer triggered by a status report; the sender doesn't need to wait for a status report, thus reducing retransmission latency. Enhanced polling is initiated by the sender, requesting the receiver to return a status report promptly, allowing the sender to retransmit faster based on the status report. In RX, a status report isn't sent immediately upon receiving a TX request; it's limited by timers. Therefore, to maximize the potential benefits of enhanced polling, the status report and its sending mechanism need adjustment.
[0163] On the other hand, XR data may become outdated during transmission, and there is currently no way to avoid retransmitting this data. The transmission of a large number of outdated SDUs consumes transmission resources, and due to the short latency of XR data packets, even more subsequent data packets may become outdated before successful transmission. To avoid retransmitting outdated data, the existing joint scheme between the sender (TX) and receiver (RX) sides is as follows:
[0164] When the TX RLC entity receives a discard instruction for an SDU from the PDCP, the TXR entity will treat the SDU as an expired SDU, and the TX RLC entity will not perform any transmission or retransmission of the SDU / SDU segment.
[0165] The RX RLC entity introduces a new RLC timer t-RxDiscard to determine obsolete RLC SDUs. The timer is activated when a gap is detected in the RLC layer.
[0166] When t-RxDiscard times out, the RX RLC entity triggers a Status Report (RS). The obsolete RLC SDU determined by t-RxDiscard receives a positive acknowledgment (ACK) in the SR.
[0167] In the existing scheme, a status report is triggered when t-Reassembly times out and when the new timer t-RxDiscard times out. The above status report triggering mechanism may affect the timely retransmission of data packets before they expire and the stopping of retransmission of expired data packets, for example, it may cause unnecessary retransmission.
[0168] To address the above technical problems, this application provides a communication method, device, and computer storage medium that can reduce unnecessary retransmissions.
[0169] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., terminal devices, network devices) as examples of the execution subjects of this interactive illustration to illustrate the method, but this application does not limit the execution subjects of the interactive illustrations. For example, the devices (e.g., terminal devices, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software that can implement all or part of the functions of the device.
[0170] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.
[0171] The following section will first discuss the state variables involved in this application.
[0172] 1. RX_Next: Receive status variable. This variable stores the serial number (SN) of the next SDU expected to be received in sequence and serves as the lower boundary of the receive window. Its initial value is 0. This variable is updated whenever the AM RLC entity receives an RLC SDU with SN = RX_Next.
[0173] 2. RX_Next_Status_Trigger: t-Reassembly status variable, which stores the SN value after the SN of the RLC SDU that triggers t-Reassembly.
[0174] 3. RX_Next_Discard_Trigger: t-RxDiscard status variable, which stores the SN value after the SN of the RLC SDU that triggers t-RxDiscard.
[0175] 4. RX_Highest_Status: The highest possible STATUS transfer status variable. This variable stores the highest possible value of the SN that can be indicated by "ACK_SN" when a STATUS PDU needs to be constructed. The initial value is 0.
[0176] 5. RX_Next_Highest: The highest received status variable. This variable stores the value of the next SN of the SDU with the highest SN among the received RLC SDUs. The initial value is 0.
[0177] Referring to Figure 7, this figure is a flowchart of a communication method provided in an embodiment of this application.
[0178] The method specifically includes the following steps:
[0179] S11: The receiving end of the RLC entity constructs a control data packet, wherein, before the control data packet is triggered, the first state variable is updated; or, the control data packet is constructed based on the first state variable, or based on the second state variable, or based on the third state variable, or based on the third state variable and the fourth state variable, and the type of the constructed control data packet is indicated by the first field.
[0180] The first state variable stores the next SN of the highest SN of the SDU that determines the reception status. That is, the first state variable is RX_Highest_Status, which is used to maintain the "ACK_SN" in the control data packet.
[0181] The second state variable stores the next SN of the maximum SN of the SDU that determines the reception status, and also stores the SN of the next SDU expected to be received in sequence. In this embodiment, the second state variable can be considered a modified RX_Next. Specifically, in the prior art, RX_Next stores the SN of the next SDU expected to be received in sequence; this implementation adjusts the definition of RX_Next so that the modified RX_Next also stores the next SN of the maximum SN of the SDU that determines the reception status. That is, if RX_Next is updated when t-RxDiscard expires, RX_Next will store the maximum possible value of ACK_SN when a STATUS PDU needs to be constructed.
[0182] It is understandable that the second state variable can also exist independently as a new state variable.
[0183] The third state variable stores the SN of the next SDU to be received in sequence, i.e., the third state variable is RX_Next.
[0184] The fourth state variable stores the next SN of the SDU with the highest SN among the confirmed received RLC SDUs, i.e., the fourth state variable is RX_Next_Highest.
[0185] In this embodiment, the control data packets constructed based on different state variables may be of different types, and the information indicated in different types of control data packets may differ. In this embodiment, the type of the constructed control data packet is indicated by a first field.
[0186] In one possible implementation, the first field can reuse an existing field, thereby avoiding the introduction of additional fields and reducing the size or complexity of the control data packet. For example, the CPT field can be reused. In this implementation, reserved values of the CPT field can be assigned meaning to indicate the specific type of control data. The original CPT = 000 still represents an existing control data packet triggered by t-reassembly, while other reserved values 001-111 can be used to indicate the specific type of control data packet. The specific correspondence between reserved values and control data packets is not limited in the embodiments of this application.
[0187] In another possible implementation, the first field can also be a newly set field.
[0188] S12: The receiver of the RLC entity sends a control data packet to the sender of the RLC entity.
[0189] After the receiving end of an RLC entity completes the construction of the control data packet, it can send the control data packet to the sending end of the RLC entity at an appropriate time.
[0190] In this embodiment of the application, the receiving end of the RLC entity can update the first state variable in advance before the control data packet is triggered, and construct and send the corresponding type of control data packet using different state variables to avoid unnecessary retransmissions. These are described in detail below.
[0191] In one possible implementation, before the control packet is triggered, the first state variable of the next SN (i.e., ACK_SN) of the maximum sequence number SN of the SDU used to determine the determined reception state of the control packet is updated in advance.
[0192] In existing technologies, to confirm SDU expiration, the receiver of an RLC entity introduces a timer t-RxDiscard. When t-RxDiscard times out, a status report is triggered, i.e., a control packet is triggered. However, the ACK_SN in the current control packet is maintained by the first status variable RX_Highest_Status. When t-RxDiscard times out, the updated RX_Next is greater than RX_Highest_Status. Constructing a control packet at this time would prevent the maximum value of ACK_SN from being set to the maximum possible value. Therefore, in this implementation, RX_Highest_Status is updated before the control packet is triggered to ensure that the ACK_SN can reach the maximum SN of a fully received RLC SDU when constructing the control packet. Furthermore, the first field in the control packet can indicate the type of control packet, allowing the sender of the RLC entity to determine whether the control packet is triggered by a timer timeout, rather than by polling or enhanced polling, thus avoiding unnecessary retransmissions.
[0193] In another possible implementation, the control packet is constructed based on the first state variable RX_Highest_Status, and the type of the constructed control packet is indicated by the first field. In this implementation, the construction of the control packet is triggered when the first timer t-RxDiscard times out. If the first state variable is greater than or equal to RX_Next, the control packet can be constructed based on the first state variable. This ensures that the ACK_SN can reach the maximum SN of a fully received RLC SDU when constructing the control packet. The first field in the control packet indicates the type of the control packet, effectively distinguishing control packets. This allows the sender of the RLC entity to determine whether the control packet is triggered by a timer timeout, rather than by polling or enhanced polling, based on the first field in the packet, thus avoiding unnecessary retransmissions.
[0194] In another possible implementation, the control data packet is constructed based on a second state variable. In this implementation, by storing the next SN of the maximum SN of the SDU that determines the reception state in the second state variable, when the control data packet is triggered and assembled, the maximum value of the ACK_SN in the control data packet is maintained by the second state variable. This ensures that the maximum value of the ACK_SN when constructing the control data packet can reach the maximum SN of the RLC SDU received in sequence. The first field in the control data packet can indicate the type of the control data packet, achieving effective differentiation of control data packets. This allows the sender of the RLC entity to determine, based on the first field in the data packet, whether the control data packet is triggered by a timer timeout, rather than by polling or enhanced polling, thus avoiding unnecessary retransmissions.
[0195] In another possible implementation, when the third state variable is greater than or equal to the first state variable, the control data packet is constructed based on the third state variable. In this implementation, the first field indicates that the control data packet type is a second data packet, which is triggered when the first timer t-RxDiscard times out. Taking the first field as the CPT field as an example, the original CPT=000 still represents an existing control data packet triggered by t-reassembly. A set value of 001-111, such as 001, can indicate that the control data packet type is a second data packet. This implementation achieves effective differentiation of control data packets, allowing the sender of the RLC entity to determine whether the timer triggering the control data packet is t-RxDiscard or t-reassembly based on the CPT field in the control data packet, thereby avoiding unnecessary retransmissions in timer timeout scenarios.
[0196] In another possible implementation, the control data packet can be constructed based on the third and fourth state variables. In this case, the first field indicates that the control data packet type is a third data packet. When constructing the third data packet, based on the third and fourth state variables, the ACK_SN can be determined, as well as the SN of the successfully received SDU that is greater than or equal to the third state variable and less than the fourth state variable. In this case, the third data packet can be used to indicate the successfully received SDU and / or a portion of the successfully received SDU, which differs from the format of the existing control data packet shown in Figure 6. The sender of the RLC entity can distinguish the different data packet types to avoid unnecessary retransmissions.
[0197] In another possible implementation, the control data packet constructed based on the first state variable, or the second state variable, or the third state variable, or both the third and fourth state variables, may only include information indicating the SN of the SDU that failed to receive the data. That is, it may only include the NACK_SN indication, excluding the ACK_SN indication. This differs from the existing control data packet shown in Figure 6, which includes the ACK_SN indication, giving this implementation a unique control data packet. The control data packet can also indicate that it only includes the NACK_SN indication through its first field. Taking the CPT field as an example, this implementation can assign a reserved value to the CPT field, using this reserved value to indicate that the control data packet only indicates the SN of the SDU that failed to receive the data. This implementation does not limit the specific reserved value used, while the original CPT=000 still represents the existing control data packet triggered by t-reassembly. This implementation achieves effective differentiation of control data packets, allowing the RLC entity's transmitter to determine whether the control data packet indicates the ACK_SN indication based on the first field in the data packet. This distinguishes it from existing control data packets in timer timeout and enhanced polling scenarios, thus avoiding unnecessary retransmissions.
[0198] In summary, the receiving end of the RLC entity in this application embodiment can update the first state variable used to construct the control data packet in advance before the control data packet is triggered, or it can construct and send the corresponding type of control data packet using different state variables, so as to avoid unnecessary retransmissions.
[0199] The triggering conditions for the control data packets in this application can be any of the following: a first timer timeout, where the first timer starts when there is an SN gap and the SDU that was not successfully received within the SN gap is confirmed as outdated when the timeout occurs; a second timer timeout, where the second timer starts when there is an SN gap and the SDU that was not successfully received within the SN gap is confirmed as a reception failure when the timeout occurs; or an enhanced polling indication or a polling indication is received. Here, the first timer is t-RxDiscard, and the second timer is t-reassembly. The construction and transmission process of the control data packets will be specifically explained below in conjunction with the above triggering methods.
[0200] First, let's explain how the first state variable is updated before the control data packet is triggered.
[0201] Referring to Figure 8, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0202] The method includes the following steps:
[0203] S21: When the first timer expires and the first state variable is not greater than the third state variable, or not greater than the fifth state variable, or not greater than the minimum value among the third and fifth state variables, the receiver of the RLC entity updates the first state variable to the SN of the first RLC SDU that is not less than the third state variable, or not less than the fifth state variable, or not less than the maximum value among the third and fifth state variables, and has not been fully received.
[0204] The first timer starts when a signal gap (SN) exists, and if an SDU that was not successfully received within the SN gap times out, it is considered outdated. The first timer is t-RxDiscard. The third state variable is RX_Next. The fifth state variable stores the first signal (SN) after the SN of the RLC SDU that triggered the first timer, i.e., RX_Next_Discard_Trigger.
[0205] In this embodiment of the application, for the receiver of the RLC entity, when t-RxDiscard times out, the variables are updated as follows:
[0206] Update RX_Next to the SN of the first RLC SDU that has not yet received all bytes, which is greater than or equal to RX_Next_Discard_Trigger.
[0207] If RX_Highest_Status is not greater than RX_Next, or not greater than RX_Next_Discard_Trigger, or not greater than the minimum of RX_Next and RX_Next_Discard_Trigger, update RX_Highest_Status to be not less than RX_Next, or not less than RX_Next_Discard_Trigger, or not less than the maximum of RX_Next and RX_Next_Discard_Trigger, and the SN of the first RLC SDU that has not been fully received.
[0208] By updating RX_Highest_Status, the ACK_SN in the first data packet can be set to the maximum possible value when the first data packet is constructed based on RX_Highest_Status.
[0209] For the receiver of the RLC entity, when the second timer t-reassembly times out, the variables are updated as follows:
[0210] Update RX_Highest_Status to be greater than or equal to the fifth status variable RX_Next_Status_Trigger, but the SN of the first RLC SDU with all bytes has not yet been received.
[0211] S22: The receiver of the RLC entity constructs the first data packet based on the updated first and third state variables.
[0212] The construction and transmission of the first data packet in this embodiment are restricted by a third timer, t-StatusProhibit. t-StatusProhibit is a disable timer that is activated when the previous first data packet is delivered to the lower layer.
[0213] When the first data packet is triggered, the receiver of the RLC entity, if t-StatusProhibit is not running or has timed out, constructs a first data packet based on the updated first and third status variables and submits it to the lower layer during the first transmission opportunity indicated by the lower layer. The updated first status variable is used to determine the ACK_SN in the first data packet, and the third status variable, combined with the updated first status variable, can be used to determine the NACK_SN.
[0214] When the first data packet is triggered, the receiver of the RLC entity, while t-StatusProhibit is running, needs to wait for t-StatusProhibit to time out, and then, during the first transmission opportunity indicated by the lower layer, construct a first data packet based on the updated first and third status variables and submit it to the lower layer. It is important to note that even if status reports are triggered multiple times during t-StatusProhibit's operation, a first data packet should still be constructed and submitted to the lower layer.
[0215] When the first data packet has been submitted to the lower layer, the receiving end of the RLC entity should initiate t-StatusProhibit.
[0216] S23: The receiver of the RLC entity sends the first data packet to the sender of the RLC entity.
[0217] S24: When the sending end of the RLC entity determines that it has received the first data packet based on the first field, it submits the first indication information to the upper layer based on the first data packet. The first indication information indicates the SN of the SDU that determines the reception status.
[0218] The sending end of the RLC entity can interpret the first data packet and determine the successfully received SDU based on the ACK_SN field in the first data packet, that is, the SDU whose SN is less than ACK_SN but not equal to NACK_SN is successfully received. The sending end of the RLC entity sends the first indication information of the SN of the SDU that determines the reception status to the upper layer, as well as the SDU that considers retransmission of NACK_SN.
[0219] In summary, the solution provided in this application constructs and sends a first data packet when the third state variable is not greater than the first state variable. By updating the first state variable in advance, the ACK_SN in the first data packet triggered by the t-RxDiscard timeout can be set to the maximum possible value, thereby avoiding unnecessary retransmissions.
[0220] The following describes another way to update the first state variable before the control data packet is triggered.
[0221] Referring to Figure 9, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0222] The method includes the following steps:
[0223] S31: When the first timer expires, the receiver of the RLC entity updates the first state variable to a value that is not less than the current first state variable, and not less than the third state variable, or not less than the fifth state variable, or not less than the maximum value among the third and fifth state variables, and the first SN of the first RLC SDU that has not been fully received; when the second timer expires and the receiver of the RLC entity has enabled the first timer, it updates the first state variable to a value that is not less than the current first state variable, and not less than the third state variable, or not less than the sixth state variable, or not less than the maximum value among the third and sixth state variables, and the first SN of the first RLC SDU that has not been fully received.
[0224] In this embodiment of the application, the first timer is started when there is a SN gap, and if the timer expires, the SDU that was not successfully received within the SN gap is confirmed to be outdated, that is, the first timer is t-RxDiscard.
[0225] The third state variable stores the SN of the next SDU to be received in sequence; the third state is RX_Next.
[0226] The fifth state variable stores the first SN after the SN of the RLC SDU that triggered the second timer, namely RX_Next_Discard_Trigger.
[0227] The sixth status variable stores the first SN after the SN of the RLC SDU that triggered the second timer, namely RX_Next_Status_Trigger.
[0228] The second timer starts when there is a SN gap, and if the timer expires, any SDU that was not successfully received within the SN gap is considered a reception failure, i.e., t-reassembly.
[0229] In this embodiment of the application, for the receiver of the RLC entity, when t-RxDiscard times out, the variables are updated as follows:
[0230] Update RX_Next to be greater than or equal to RX_Next_Discard_Trigger, but the SN of the first RLC SDU with all bytes not yet received;
[0231] Update RX_Highest_Status to be greater than or equal to the current RX_Highest_Status, and greater than or equal to RX_Next, or greater than or equal to RX_Next_Discard_Trigger, or greater than or equal to the maximum value of RX_Next_Discard_Trigger and RX_Next, and the SN of the first RLC SDU that has not yet received all bytes, by updating the first status variable RX_Highest_Status so that the ACK_SN in the first packet determined based on the first status variable can be set to the maximum possible value.
[0232] For the receiver of the RLC entity, when the t-reassembly times out, the variables are updated as follows:
[0233] If the receiver of the RLC entity configures / enables t-RxDiscard, it updates RX_Highest_Status to be greater than or equal to the current RX_Highest_Status, and not less than RX_Next, or not less than RX_Next_Status_Trigger, or not less than the maximum value of RX_Next and RX_Next_Status_Trigger, and has not yet received the SN of the first RLC SDU with all bytes. If the receiver of the RLC entity does not configure / enable t-RxDiscard, it updates RX_Highest_Status to be greater than or equal to RX_Next_Status_Trigger, but has not yet received the SN of the first RLC SDU with all bytes. In this case, the ACK_SN in the first data packet determined based on the first state variable when the second timer times out can also be set to the maximum possible value.
[0234] S32: The receiver of the RLC entity constructs the first data packet based on the updated first and third state variables.
[0235] The construction and transmission of the first data packet in this embodiment are restricted by a third timer, t-StatusProhibit. t-StatusProhibit is a disable timer that is activated when the previous first data packet is delivered to the lower layer.
[0236] When the first data packet is triggered, the receiver of the RLC entity, if t-StatusProhibit is not running or has timed out, constructs a first data packet based on the updated first and third status variables and submits it to the lower layer during the first transmission opportunity indicated by the lower layer. The updated first status variable is used to determine the ACK_SN in the first data packet, and the third status variable, combined with the updated first status variable, can be used to determine the NACK_SN.
[0237] When the first data packet is triggered, the receiver of the RLC entity, while t-StatusProhibit is running, waits for t-StatusProhibit to time out, and then, at the first transmission opportunity indicated by the lower layer, constructs a first data packet based on the updated first and third status variables and submits it to the lower layer. It is important to note that even if status reports are triggered multiple times during t-StatusProhibit's operation, a first data packet should still be constructed and submitted to the lower layer.
[0238] When the first data packet has been submitted to the lower layer, the receiving end of the RLC entity should initiate t-StatusProhibit.
[0239] S33: The receiver of the RLC entity sends the first data packet to the sender of the RLC entity.
[0240] S34: When the sending end of the RLC entity determines that it has received the first data packet based on the first field, it submits the first indication information to the upper layer based on the first data packet. The first indication information indicates the SN of the SDU that determines the reception status.
[0241] The sending end of the RLC entity can interpret the first data packet and determine the successfully received SDU based on the ACK_SN field in the first data packet, that is, the SDU whose SN is less than ACK_SN but not equal to NACK_SN is successfully received. The sending end of the RLC entity sends the first indication information of the SN of the SDU that determines the reception status to the upper layer, as well as the SDU that considers retransmission of NACK_SN.
[0242] In summary, the solution provided in this application constructs and sends a first data packet when the third state variable is not greater than the first state variable. By updating the first state variable in advance, the ACK_SN in the first data packet triggered by the t-RxDiscard timeout can be set to the maximum possible value, thereby avoiding unnecessary retransmissions.
[0243] The following describes how to construct control data packets based on the second state variable.
[0244] Referring to Figure 10, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0245] The method includes the following steps:
[0246] S41: When the first timer of the RLC entity's receiver expires, the first data packet is triggered.
[0247] The first timer, t-RxDiscard, triggers the construction of the first data packet when an outdated RLC SDU is present.
[0248] S42: When the second state variable is not less than the first state variable, the receiver of the RLC entity determines the next SN of the largest SN of the SDU in the first data packet with a determined reception state based on the second state variable.
[0249] In this embodiment, the second state variable is the adjusted RX_Next. In addition to storing the SN of the next SDU expected to be received in sequence, the existing RX_Next also stores the next SN of the SDU with the largest SN that determines the reception status. That is, in this embodiment, RX_Next is updated when t-RxDiscard expires, storing the maximum possible value of "ACK_SN" when a STATUS PDU needs to be constructed.
[0250] For the receiver of an RLC entity, when t-RxDiscard times out, RX_Next is updated to be greater than or equal to the fifth state variable RX_Next_Discard_Trigger, and the SN of the first RLC SDU that has not yet received all bytes.
[0251] For the receiver of the RLC entity, when the t-reassembly timeout occurs, RX_Highest_Status is updated to be greater than or equal to the sixth status variable RX_Next_Status_Trigger, but the SN of the first RLC SDU with all bytes not yet received has been obtained.
[0252] When the first data packet is triggered, the receiving end of the RLC entity, when the third timer t-StatusProhibit expires or is not running, constructs a first data packet and submits it to the lower layer during the first transmission opportunity indicated by the lower layer; when the third timer t-StatusProhibit is running, after the third timer t-StatusProhibit expires, constructs a first data packet and submits it to the lower layer during the first transmission opportunity indicated by the lower layer.
[0253] Specifically, when constructing the first data packet, the maximum possible value of "ACK_SN" is maintained by the second state variable to ensure that the ACK_SN in the first data packet can be set to the maximum possible value.
[0254] S43: The receiver of the RLC entity sends the first data packet to the sender of the RLC entity.
[0255] When the first data packet has been submitted to the lower layer, the receiver of the RLC entity starts the third timer t-StatusProhibit.
[0256] S44: When the sending end of the RLC entity determines that it has received the first data packet based on the first field, it submits the first indication information to the upper layer based on the first data packet. The first indication information indicates the SN of the SDU that determines the reception status.
[0257] The sending end of the RLC entity can interpret the first data packet and determine the successfully received SDU based on the ACK_SN field in the first data packet, that is, the SDU whose SN is less than ACK_SN but not equal to NACK_SN is successfully received. The sending end of the RLC entity sends the first indication information of the SN of the SDU that determines the reception status to the upper layer, as well as the SDU that considers retransmission of NACK_SN.
[0258] In summary, the solution provided by the embodiments of this application constructs and sends a first data packet based on the second state variable when the second state variable is not less than the first state variable, so that the ACK_SN in the first data packet triggered by the t-RxDiscard timeout can be set to the maximum possible value, thereby avoiding unnecessary retransmissions.
[0259] The following explains how the second data packet is triggered when the t-RxDiscard timeout occurs.
[0260] Referring to Figure 11, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0261] The method includes the following steps:
[0262] S51: When the first timer of the RLC entity's receiver expires, it triggers the second data packet.
[0263] In one possible implementation, when the first timer times out, if the third state variable RX_Next is greater than or equal to the first state variable RX_Highest_Status, the data packet constructed and sent is the second data packet.
[0264] The second data packet indicates the next SN after the largest SN of the SDU that determined the reception status, but does not include the indication information of the SN of the SDU that determined the reception failure. That is, the status report triggered by the t-RxDiscard timeout only contains ACK information, not NACK, which will be explained in detail below with reference to the attached diagram.
[0265] Referring to Figure 12, this figure is a schematic diagram of the format of the second data packet provided in an embodiment of this application.
[0266] Based on the status report format shown in Figure 6, the second data packet only needs to include Oct1-3. Furthermore, since it only includes ACK information, the E1 field is useless and can be deleted or removed to reduce the size or complexity of the second data packet.
[0267] The data packet can use a first field to indicate the type of the data packet. This first field can reuse the CPT field to reduce the size and complexity of the data packet. In Figure 6, when the CPT field is 000, it indicates that the data packet is the first data packet triggered by the t-reassembly timeout; other values are reserved. In this embodiment, the reserved values of the CPT field are given meaning; for example, when the CPT field is 001-111, it indicates that the data packet is the second data packet.
[0268] The ACK_SN value in the second data packet is not less than the SN of the first SDU that was not fully received in RX_Next.
[0269] S52: Determine the next SN of the largest SN of the SDU with a determined reception state in the second data packet based on the third state variable.
[0270] When the first timer t-RxDiscard times out, the receiver of the RLC entity updates the third state variable to the SN of the first RLC SDU that is greater than or equal to the fifth state variable RX_Next_Discard_Trigger and has not yet received all bytes. Based on the updated third state variable, it determines the next SN of the SDU with the largest SN in the constructed second data packet that determines the reception state. That is, the ACK_SN in the second data packet is maintained by RX_Next.
[0271] Understandably, when the second timer t-reassembly times out, the receiver of the RLC entity will update the SN of the first RLC SDU that is greater than or equal to the sixth state variable RX_Next_Status_Trigger and has not yet received all bytes, and trigger the first data packet.
[0272] S53: When the receiver of the RLC entity does not run the third timer or the third timer expires, if the third state variable is greater than or equal to the first state variable, it will assemble and send the second data packet at the first transmission opportunity indicated by the lower layer.
[0273] In this embodiment, the transmission of the second data packet is restricted by a third timer t-StatusProhibit. The third timer t-StatusProhibit is a prohibition timer. The third timer t-StatusProhibit is started when the previous first data packet is delivered to the lower layer, and the transmission of the first data packet is prohibited before the third timer expires. The first data packet is assembled when the third state variable is less than or equal to the first state variable.
[0274] That is, the second data packet and the first data packet can be restricted by the same third timer t-StatusProhibit.
[0275] Specifically, when the third timer t-StatusProhibit is not running, if the third status variable RX_Next is greater than the first status variable RX_Highest_Status, the second data packet is assembled and delivered to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity; if the third status variable RX_Next is less than or equal to the first status variable RX_Highest_Status, the first data packet is assembled and delivered to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity.
[0276] When the third timer t-StatusProhibit runs, after the third timer expires, the second data packet is assembled and delivered to the lower layer during the first transmission opportunity indicated by the lower layer, and then transmitted to the receiving end of the RLC entity.
[0277] Furthermore, after the second data packet is successfully sent, the receiving end of the RLC entity should start the third timer t-StatusProhibit.
[0278] S54: When the sending end of the RLC entity determines that it has received the second data packet based on the first field, it submits the second indication information to the upper layer based on the second data packet. The second indication information indicates the SN of the SDU that determines the reception status.
[0279] The sending end of the RLC entity can interpret the received data packets. When it is determined that the second data packet has been received based on the first field in the data packet, it can determine the successfully received SDU based on the ACK_SN field in the second data packet. That is, data packets with SN less than ACK_SN are all outdated, and the successful transmission indication of these SDUs is submitted to the upper layer.
[0280] In summary, the solution provided in this application embodiment allows the ACK_SN in the second data packet triggered by the t-RxDiscard timeout to be maintained by RX_Next, so that the ACK_SN in the second data packet can be set to the maximum possible value, thereby avoiding unnecessary retransmissions.
[0281] In another possible implementation, the transmission of the second data packet can be unrestricted by t-StatusProhibit and will not affect the operation of t-StatusProhibit, as detailed below with reference to the accompanying drawings.
[0282] Referring to Figure 13, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0283] The method includes the following steps:
[0284] S61: When the first timer of the RLC entity's receiver expires, it triggers the second data packet.
[0285] The format of the second data packet can be seen in Figure 12, and will not be described again here.
[0286] S62: Determine the next SN of the largest SN of the SDU with a determined reception state in the second data packet based on the third state variable.
[0287] S63: The receiving end of the RLC entity assembles and sends the second data packet.
[0288] In this implementation, at the receiving end of the RLC entity, when the first timer t-RxDiscard times out, the third status variable RX_Next is updated to the SN of the first RLC SDU that is greater than or equal to the fifth status variable RX_Next_Discard_Trigger and has not yet fully received all bytes. Then, the second data packet is assembled and delivered to the lower layer and sent to the sending end of the RLC entity. The sending or delivery of the second data packet will not start the first timer t-StatusProhibit.
[0289] When the second timer t-reassembly times out, the first status variable RX_Highest_Status is updated to the SN of the first RLC SDU that is greater than or equal to the sixth status variable RX_Next_Status_Trigger and has not yet fully received all bytes. Then the first data packet is triggered, and the transmission of the first data packet is limited by the first timer t-RxDiscard.
[0290] When the first data packet is triggered, the receiver of the RLC entity shall construct a first data packet and submit it to the lower layer during the first transmission opportunity indicated by the lower layer when the first timer t-RxDiscard is not running; otherwise, after the first timer t-RxDiscard expires, a first data packet shall be constructed during the first transmission opportunity indicated by the lower layer. Even if the first data packet is triggered multiple times while t-StatusProhibit is running, a first data packet shall be constructed and submitted to the lower layer.
[0291] S64: When the sending end of the RLC entity determines that it has received the second data packet based on the first field, it submits the second indication information to the upper layer based on the second data packet. The second indication information indicates the SN of the SDU that determines the reception status.
[0292] The sending end of the RLC entity can interpret the received data packets. When it is determined that the second data packet has been received based on the first field in the data packet, it can determine the successfully received SDU based on the ACK_SN field in the second data packet. That is, data packets with SN less than ACK_SN are all outdated, and the successful transmission indication of these SDUs is submitted to the upper layer.
[0293] In another possible implementation, the transmission of the second data packet is restricted by a separate fourth timer, which is a new timer added specifically for the second data packet and is not the same timer as the third timer t-StatusProhibit. This will be explained in detail below with reference to the accompanying drawings.
[0294] Referring to Figure 14, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0295] The method includes the following steps:
[0296] S71: When the first timer of the RLC entity's receiver expires, it triggers the second data packet.
[0297] The format of the second data packet can be seen in Figure 12, and will not be described again here.
[0298] S72: Determine the next SN of the largest SN of the SDU with a determined reception state in the second data packet based on the third state variable.
[0299] S73: When the fourth timer is not running or has expired, the second data packet is assembled and sent at the first transmission opportunity indicated by the lower layer; when the fourth timer is running, the second data packet is assembled and sent at the first transmission opportunity indicated by the lower layer after the fourth timer has expired.
[0300] In this embodiment, the transmission of the second data packet is restricted by a fourth timer. The network side can configure a fourth timer for the RLC entity. The fourth timer is a disable timer that starts when the previous second data packet is delivered to the lower layer, and the assembly and delivery of the second data packet are prohibited before the fourth timer expires.
[0301] When the first timer t-RxDiscard times out, the third state variable is updated to the SN of the first RLC SDU that is greater than or equal to the fifth state variable and has not yet received all bytes, and the second data packet is triggered.
[0302] When the second timer t-reassembly times out, the first status variable RX_Highest_Status is updated to the SN of the first RLC SDU that is greater than or equal to the sixth status variable RX_Next_Status_Trigger and has not yet received all bytes, and the first data packet is triggered.
[0303] When the first data packet is triggered, the receiver of the RLC entity, when the third timer t-StatusProhibit is not running, shall construct a first data packet and submit it to the lower layer during the first transmission opportunity indicated by the lower layer; when the third timer is running, after waiting for the third timer t-StatusProhibit to expire, shall construct a first data packet during the first transmission opportunity indicated by the lower layer. Even if the status report is triggered multiple times while the third timer t-StatusProhibit is running, a first data packet should still be constructed and submitted to the lower layer.
[0304] When the second data packet is triggered, the receiver of the RLC entity, while the fourth timer is not running, should construct a second data packet and submit it to the lower layer during the first transmission opportunity indicated by the lower layer. When the fourth timer is running, it should wait for the fourth timer to expire and then construct a second data packet during the first transmission opportunity indicated by the lower layer. Even if the second data packet is triggered multiple times while the fourth timer is running, a second data packet should still be constructed and submitted to the lower layer. Furthermore, when the second data packet has already been submitted to the lower layer, the receiver of the RLC entity should restart the fourth timer. During the operation of the fourth timer, it is prohibited to assemble and submit the second data packet again.
[0305] S74: When the sending end of the RLC entity determines that it has received the second data packet based on the first field, it submits the second indication information to the upper layer based on the second data packet. The second indication information indicates the SN of the SDU that determines the reception status.
[0306] The sending end of the RLC entity can interpret the received data packets. When it is determined that the second data packet has been received based on the first field in the data packet, it can determine the successfully received SDU based on the ACK_SN field in the second data packet. That is, data packets with SN less than ACK_SN are all outdated, and the successful transmission indication of these SDUs is submitted to the upper layer.
[0307] The above describes the triggering, assembly, and sending process of the second data packet. The following describes the implementation method when the data packet is the third data packet in the enhanced polling scenario.
[0308] The enhanced polling scheme involves the TX triggering polling based on the remaining time of a data packet. The RX receives the polling and only triggers the first data packet when the reception status (ACK / NACK) of the data packet carrying the poll is clear (delay 1). Sending a status report also depends on the running status of t-StatusProhibit (delay 2); a status report can only be sent if t-StatusProhibit is not running or has timed out.
[0309] Only after TX receives the first data packet can it retransmit the NACK data packet if there is not much time left.
[0310] However, due to delays 1 and 2 mentioned above, RX cannot send the first data packet in a timely manner upon receiving the enhanced Poll. If the first data packet is sent immediately upon receiving the enhanced Poll, data packets during transmission will be incorrectly identified as NACK, causing TX to perform unnecessary retransmissions.
[0311] This application embodiment introduces a new control data packet to enhance Poll, namely the third data packet.
[0312] Referring to Figure 15, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0313] The method includes the following steps:
[0314] S81: The receiver of the RLC entity assembles a third data packet after receiving an enhanced polling instruction or a polling instruction.
[0315] In the embodiments of this application, the third data packet indicates the SN of the SDU that determines the reception status, but does not include indication information of the SN of the SDU that determines the reception failure. This will be described in detail below with reference to the accompanying drawings.
[0316] Referring to Figure 16, this figure is a schematic diagram of the format of the third data packet provided in an embodiment of this application.
[0317] The type of data packet can be indicated by the first field in the data packet. The first field can be reused from the CPT field to reduce the size and complexity of the data packet.
[0318] In this embodiment, the CPT field can be assigned a reserved value with a meaning. When the CPT field takes a value from 001 to 111, it indicates that the data packet is a third data packet. It is understood that the CPT field value indicating a third data packet is different from the value indicating a first or second data packet. For example, when the CPT field value is 000, it indicates that the data packet is a first data packet triggered by a t-reassembly timeout; when the CPT field value is 001, it indicates that the data packet is a second data packet triggered by a t-RxDiscard timeout; then, when the CPT field value is 010, it indicates that the data packet is a third data packet. These are merely examples and do not constitute a specific limitation on the CPT field.
[0319] The maximum SN of the SDU indicating the third data packet reception state is equal to the third state variable when the enhanced polling indication or polling indication is received. That is, the value of the first ACK_SN in Figure 16 is equal to the value of the third state variable RX_Next when the enhanced polling indication or polling indication is received.
[0320] The SN of the other SDU indicating the third data packet is greater than or equal to the third state variable RX_Next when the enhanced polling indication or polling indication is received, and less than the fourth state variable RX_Next_Highest.
[0321] The third data packet also includes at least one of the following indication fields: second field, third field, fourth field, fifth field, sixth field, and seventh field, which are described below.
[0322] The second field E1 is used to indicate whether there is another set of SDU SNs with a confirmed reception status after the corresponding SDU SN, or the second field, the third field, or the fourth field.
[0323] The third field, E2, is used to indicate whether there is a fifth and sixth field after the SN of the corresponding SDU that determines the reception status, that is, to indicate whether a set of SOstart / SOend follows the ACK_SN.
[0324] The fourth field, E3, is used to indicate whether there are continuously received SDUs after the SN of the corresponding SDU with a confirmed reception status. In other words, it is used to indicate whether there is an ACK range (continuous reception) starting from ACK_SN.
[0325] Field R is a reserved bit for easy byte alignment.
[0326] The fifth field, SOstart, indicates the start position of the received SDU portion when the SN is equal to the SN of the corresponding SDU with a defined reception status.
[0327] The sixth field, SOend, indicates the end of the reception position of the SDU portion of the SDU when the SN is equal to the SN of the corresponding SDU with a defined reception status.
[0328] The seventh field, ACK range, is used to indicate the number of consecutive RLC SDUs that determine the reception status.
[0329] S82: The receiver of the RLC entity sends a third data packet to the sender of the RLC entity.
[0330] The transmission of the third data packet in this embodiment may be subject to a timer or may not be subject to a timer, as will be explained below.
[0331] First, let's explain how to implement the sending of the third data packet when it is not limited by the timer.
[0332] In one possible implementation, the sender of the RLC entity can trigger an enhanced poll upon receiving the first data packet, sending an enhanced poll instruction to the receiver of the RLC entity.
[0333] When the receiver of an RLC entity receives an enhanced Poll instruction, it assembles and sends a third data packet. Alternatively, the receiver of an RLC entity can also assemble and send a third data packet when it receives a Poll instruction. In this case, the transmission of the third data packet is not restricted by any timers, and no new timer is started after the third data packet is transmitted.
[0334] The following describes how to implement the sending of the third data packet when it is limited by a timer.
[0335] In one possible implementation, the prohibition timer used to restrict the third data packet can be a third timer t-StatusProhibit. The third timer t-StatusProhibit starts when a first data packet has been submitted to the lower layer, and prohibits the transmission of the first data packet until the third timer t-StatusProhibit times out. The first data packet is assembled when the third state variable is less than or equal to the first state variable. That is, in this implementation, an existing third timer is reused.
[0336] When the third timer t-StatusProhibit is not running or the third timer t-StatusProhibit times out, if the third status variable RX_Next is greater than the first status variable RX_Highest_Status, the receiver of the RLC entity will assemble and send the third data packet at the first transmission opportunity indicated by the lower layer and deliver it to the lower layer for transmission to the receiver of the RLC entity.
[0337] When the third timer t-StatusProhibit is running, the receiver of the RLC entity waits for the third timer t-StatusProhibit to time out, then assembles the third data packet at the first transmission opportunity indicated by the lower layer and submits it to the lower layer for transmission to the receiver of the RLC entity.
[0338] Understandably, when the receiver of an RLC entity sends a third data packet or a first data packet, it starts a third timer t-StatusProhibit. During the operation of the third timer t-StatusProhibit, it is prohibited to reassemble and send the third data packet again.
[0339] In another possible implementation, the prohibition timer used to restrict third packets can be a fifth timer. The fifth timer and the third timer t-StatusProhibit are different timers and do not affect each other.
[0340] When the fifth timer is not running or the fifth timer expires, the receiver of the RLC entity assembles the third data packet and submits it to the lower layer at the first transmission opportunity indicated by the lower layer, and transmits it to the receiver of the RLC entity. When the third data packet has been submitted to the lower layer, the fifth timer is started.
[0341] When the fifth timer runs, after the fifth timer expires, the third data packet is assembled and delivered to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity.
[0342] The fifth timer and the third timer t-StatusProhibit do not affect each other. During the operation of the fifth timer, the third timer t-StatusProhibit can start and run normally.
[0343] S83: When the sending end of the RLC entity determines that a third data packet has been received based on the first field, it submits third indication information to the upper layer based on the third data packet. The third indication information indicates the SN of the SDU that determines the reception status and / or the received SDU portion of the SN of the SDU that determines the reception status.
[0344] The sending end of the RLC entity can interpret the received data packets. When it is determined that the first data packet has been received based on the first field in the data packet, it can operate according to the existing mechanism, including: submitting a successful transmission indication (SN is less than ACK_SN but not equal to NACK_SN) to the upper layer to confirm successful reception of the SDU; and considering retransmission of the SDU of NACK_SN.
[0345] When the sending end of the RLC entity determines that it has received the second data packet based on the first field in the data packet, it can determine that the data packets with SN less than ACK_SN have all expired, and submit the successful transmission indication of these SDUs to the upper layer.
[0346] When the sending end of the RLC entity determines that it has received the third data packet based on the first field in the data packet, it can determine that all data packets with SN less than ACK_SN have been successfully received, and the remaining ACK_SN have been successfully received according to the information carried (field 5 SOstart / field 6 SOend / field 7 ACK range). It then submits a successful transmission indication of these SDUs to the upper layer. That is, the third indication information indicates the SN of the SDU that determined the reception status and / or the received SDU portion with the SN of the SDU that determined the reception status.
[0347] In summary, the solution provided in this application embodiment can assemble and send a third data packet after receiving an enhanced polling instruction or a polling instruction. The third data packet indicates the SN of the SDU in the reception state, but does not include the indication information of the SN of the SDU that failed to receive. Furthermore, the first ACK_SN indicated by the third data packet is maintained by the third state variable when the enhanced polling instruction or polling instruction is received, so that the first ACK_SN in the third data packet can be set to the maximum possible value, thereby avoiding unnecessary retransmissions.
[0348] This application also provides another control data packet, namely the fourth control data packet. When the receiving end of the RLC entity determines that no SDU with a value greater than ACK_SN in the previous data packet has been successfully received, the size and complexity of the data packet can be reduced by sending the fourth data packet. The following is a detailed description in conjunction with the accompanying drawings.
[0349] Referring to Figure 17, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0350] The method includes the following steps:
[0351] S91: When the first state variable is greater than or equal to the seventh state variable, construct the fourth data packet.
[0352] In this embodiment, the receiver of the RLC entity can store the next SN of the largest SN of the SDU that determined the reception status of the last transmitted control data packet through the seventh state variable RX_Last_ACK_SN. This embodiment does not specifically limit the type of the last transmitted control data packet; for example, it can be a first data packet or a second data packet.
[0353] The fourth data packet includes indication information to determine the SN of the SDU that failed to be received, but does not include indication information to determine the SN of the SDU that was received. This will be explained in detail below with reference to the accompanying drawings.
[0354] Referring to Figure 18, this figure is a schematic diagram of the format of the fourth data packet provided in an embodiment of this application.
[0355] The difference between the fourth data packet shown in Figure 18 and the state shown in Figure 6 is that it does not include the ACK_SN related fields, but only includes the indication information of the SN of the SDU that was determined to have failed to be received. For a detailed explanation of each field in Figure 18, please refer to Figure 6, which will not be repeated here.
[0356] S92: The receiver of the RLC entity sends the fourth data packet to the sender of the RLC entity.
[0357] The scenario in this application embodiment where the fourth data packet is used is when it has the same first ACK_SN as the previously sent first / second control data packet report.
[0358] The technical advantage of the fourth control data packet using the above design is that, since the fourth data packet does not include the indication information of the received SDU's SN, the size and complexity of the fourth data packet are lower.
[0359] Based on the above description, in this embodiment of the application, when the sending condition is met, the fourth data packet is assembled and delivered to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity.
[0360] Sending conditions may include at least one of the following:
[0361] When the first timer t-RxDiscard times out, the transmission of the fourth data packet is not restricted by a separate disable timer, and the disable timer will not be started after the fourth data packet is transmitted.
[0362] When the second timer t-reassembly times out, the fourth data packet replaces the first data packet to reduce the size and complexity of the transmitted data packets. Furthermore, the sending of the fourth data packet is not restricted by a separate prohibition timer, and the prohibition timer will not be started after the fourth data packet is sent.
[0363] Upon receiving an enhanced polling instruction or a polling instruction, the transmission of the fourth data packet is not restricted by a separate prohibition timer, and the prohibition timer will not be started after the fourth data packet is transmitted.
[0364] If the first timer t-RxDiscard times out and the third timer t-StatusProhibit times out or is not started, the sending of the fourth data packet is restricted by the third timer t-StatusProhibit. After the fourth data packet is sent, the third timer t-StatusProhibit will be started. During the operation of the third timer t-StatusProhibit, it is prohibited to reassemble and send the fourth data packet again.
[0365] If the second timer t-reassembly times out and the third timer t-StatusProhibit times out or is not started, the fourth data packet replaces the first data packet described above to reduce the size and complexity of the transmitted data packets. Furthermore, the transmission of the fourth data packet is limited by the third timer t-StatusProhibit, which will not be elaborated here.
[0366] If an enhanced polling instruction or a polling instruction is received, and the third timer t-StatusProhibit times out or is not started, the transmission of the fourth data packet will be restricted by the third timer t-StatusProhibit, which will not be elaborated here.
[0367] If the first timer t-RxDiscard times out and the sixth timer times out or is not started, the transmission of the fourth data packet is restricted by a separate sixth timer. The sixth timer is different from the third timer t-StatusProhibit. The sixth timer will be started after the fourth data packet is sent. During the operation of the sixth timer, it is prohibited to reassemble and send the fourth data packet again.
[0368] If the second timer t-reassembly times out, and the sixth timer times out or does not start, the fourth data packet replaces the first data packet described above to reduce the size and complexity of the transmitted data packets. Furthermore, the transmission of the fourth data packet is limited by the sixth timer, which will not be elaborated further here.
[0369] If an enhanced polling instruction or a polling instruction is received, and the sixth timer times out or is not started, the transmission of the fourth data packet will be limited by the sixth timer, which will not be elaborated further here.
[0370] S93: When the sending end of the RLC entity determines that the control data packet is the fourth data packet based on the first field, it submits the fourth indication information to the upper layer based on the fourth data packet.
[0371] The sending end of the RLC entity can interpret the received data packets. When it is determined from the first field in the data packet that the fourth data packet has been received, it can be determined that no SDU with a value greater than ACK_SN in the previously received data packet has been successfully received. That is, no SDU with a value less than ACK_SN in the previously received data packet and not NACK_SN in the previously received data packet has been successfully received. Therefore, the retransmission of the NACK_SN SDU should be considered.
[0372] Specifically, the fourth indication information submitted by the sender of the RLC entity indicates that the SDU reception is successful if the SN is less than the next SN of the SDU with the largest SN of the SDU indicating the reception status as indicated by the last received control data packet, and is not the SDU with the largest SN of the SDU indicating the reception failure as indicated by the last received control data packet.
[0373] In summary, by using the solution provided in the embodiments of this application, it is possible to determine that no SDU with a value greater than ACK_SN in the previous data packet was successfully received when the first state variable is greater than or equal to the seventh state variable. By sending a fourth data packet, the size and complexity of the data packet are reduced. Furthermore, based on the first NACK_SN of the fourth data packet, the maximum SN value of the SDU that determines the reception status can be determined, thereby avoiding unnecessary retransmissions.
[0374] It is understood that the AM RLC sender entity TX and AM RLC receiver entity RX in the above embodiments can be located in terminal devices, such as XR devices, or in network devices, such as base stations.
[0375] Referring to Figure 19, this figure is a schematic diagram of a communication device provided in an embodiment of this application.
[0376] The communication device 40 includes a processing module 41 and a transceiver module 42.
[0377] In one possible implementation, the communication device 40 is the receiver of the RLC entity. The processing module 41 is used to construct control data packets, and the transceiver module 42 is used to send control data packets.
[0378] In another possible implementation, the communication device 40 is the transmitter of the RLC entity, the transceiver module 42 is used to receive control data packets, and the processing module 41 is used to interpret the received control data packets.
[0379] Based on the communication methods provided in the above embodiments, this application also provides a network device, which will be described in detail below with reference to the accompanying drawings.
[0380] Referring to Figure 20, this figure is a schematic diagram of a network device provided in an embodiment of this application.
[0381] Network device 50 includes a processor 51, a communication interface 52, a memory 53, and a bus 54. The number of processor 51, communication interface 52, and memory 53 can be one or more. Processor 51 and memory 53 communicate with each other via bus 54, and network device 50 communicates via communication interface 52.
[0382] Processor 51 may include one or more processing units, such as a modem processor, a baseband processor, etc. Different processing units may be independent devices or integrated into one or more processors. Processor 51 may also include memory for storing instructions and data.
[0383] In one possible implementation, the network device can be a base station, and the processor 51 is used to call program instructions in the memory 53 to execute the method steps of the receiving end and / or the transmitting end of the RLC entity in the above embodiments.
[0384] Referring to Figure 21, this figure is a schematic diagram of another network device provided in an embodiment of this application.
[0385] Taking a network device as an example, the network device includes a processor 1110, a memory 1120, and a transceiver 1130.
[0386] The processor 1110 is mainly used for baseband processing and controlling the base station. The processor 1110 is usually the control center of the base station, used to control the base station to execute the method steps of the receiving end and / or transmitting end of the RLC entity in the above method embodiments.
[0387] The memory section 1120 is mainly used to store computer program code and data.
[0388] The transceiver 1130 section is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals to baseband signals; the transceiver 1130 section is also commonly referred to as a transceiver module, transceiver, transceiver circuit, etc.
[0389] The network device also includes an antenna 1133 and radio frequency (RF) circuitry (not shown in the figure), where the RF circuitry is mainly used for RF processing. Optionally, the device in the transceiver 1130 section used to implement the receiving function can be regarded as a receiver 1032, and the device used to implement the transmitting function can be regarded as a transmitter 1031; that is, the transceiver 1130 includes a receiver 1132 and a transmitter 1131. The receiver 1032 can also be called a receiving module, receiver, or receiving circuit, etc., and the transmitter 1131 can be called a transmitting module, transmitter, or transmitting circuit, etc.
[0390] The processor 1110 section and the memory 1120 section may include one or more circuit boards, each circuit board may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control the base station. If multiple circuit boards exist, they can be interconnected to enhance processing capabilities. As an optional implementation, multiple circuit boards may share one or more processors, multiple circuit boards may share one or more memories, or multiple circuit boards may simultaneously share one or more processors.
[0391] It should be understood that Figure 21 is merely an example and not a limitation, and the network device described above, including processor 1110, memory 1120 and transceiver 1130, may not depend on the structure shown in Figure 21.
[0392] Based on the communication methods provided in the above embodiments, this application also provides a terminal device.
[0393] Referring to Figure 22, this figure is a schematic diagram of a terminal device provided in an embodiment of this application.
[0394] The terminal device 60 includes a processor 61, a communication interface 62, a memory 63, and a bus 64. The number of processor 61, communication interface 62, and memory 63 can be one or more.
[0395] The processor 61 and memory 63 communicate with each other via bus 64, and the terminal device 60 communicates with the network device via communication interface 62.
[0396] Processor 61 may include one or more processing units, such as a modem processor, a baseband processor, etc. Different processing units may be independent devices or integrated into one or more processors. Processor 61 may also include memory for storing instructions and data.
[0397] The processor 61 is used to call program instructions in the memory 63 to execute the steps of the receiving end and / or the transmitting end of the RLC entity in the above-described communication method.
[0398] Terminal device 60 can be an XR device, or a mobile phone, tablet computer, computer with wireless transceiver function, VR terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, vehicle terminal device, wireless terminal in autonomous driving, wireless terminal in telemedicine, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, wearable terminal device, etc.
[0399] This application also provides a processor, including an input circuit, an output circuit, and a processing circuit. The processing circuit receives signals through the input circuit and transmits signals through the output circuit, causing the processor to execute the above-described communication method. It should be understood that the processor can be one or more chips. The input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, gate circuit, flip-flop, and various logic circuits, etc. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver; the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter; and the input circuit and output circuit can be the same circuit, which is used as the input circuit and output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.
[0400] For example, the processor can be a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.
[0401] This application also provides a communication system that may include the network devices and terminal devices described above.
[0402] Furthermore, embodiments of this application also provide a computer-readable storage medium storing a program that, when executed by a processor, implements the method executed at the receiving end of the RLC entity or at the transmitting end of the RLC entity as described in the above embodiments.
[0403] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0404] Specifically, the computer-readable storage medium includes program instructions that instruct an electronic device to perform the above-described method, or instruct a network device to perform the above-described method.
[0405] This application also provides a computer program product containing instructions. The computer program product may be software or program products containing instructions, capable of running on a terminal device or network device, or stored on any usable medium. When the computer program product runs on a terminal device, it causes the terminal device to perform the above-described method; or, when the computer program product runs on a network device, it causes the network device to perform the above-described method.
[0406] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.
[0407] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.
[0408] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.
[0409] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.
[0410] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0411] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0412] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.
Claims
1. A communication method, characterized in that, The receiver used in the Radio Link Control (RLC) entity includes: A control data packet is constructed and sent. Before the control data packet is triggered, a first state variable is updated; or, the control data packet is constructed based on the first state variable, or based on the second state variable, or based on the third state variable, or based on the third state variable and the fourth state variable, and the type of the constructed control data packet is indicated by a first field. The first state variable stores the next SN of the maximum sequence number SN of the Service Data Unit (SDU) that has determined the reception status; the second state variable stores the next SN of the maximum SN of the SDU that has determined the reception status, and stores the SN of the next SDU that is expected to be received in sequence; the third state variable stores the SN of the next SDU that is expected to be received in sequence; and the fourth state variable stores the next SN of the SDU with the highest SN among the RLC SDUs that have been determined to be received.
2. The method according to claim 1, characterized in that, The triggering conditions for the control data packet include any one of the following: The first timer expires. The first timer is started when there is a SN gap, and if the timer expires, the SDU that was not successfully received within the SN gap is confirmed to be outdated. The second timer times out. The second timer starts when there is an SN gap, and if the timer times out, any SDU that is not successfully received within the SN gap is considered a reception failure. Received an enhanced polling instruction or a polling instruction.
3. The method according to claim 1, characterized in that, Before the control data packet is triggered, the first state variable is updated in the following way: When the first timer times out and the first state variable is not greater than the third state variable or the fifth state variable or the minimum value among the third state variable and the fifth state variable, the first state variable is updated to the SN of the first RLC SDU that is not less than the third state variable or the fifth state variable or the maximum value among the third state variable and the fifth state variable and has not been fully received. The first timer is started when there is a SN gap, and if the timer expires, the SDU that was not successfully received within the SN gap is confirmed as outdated. The third state variable stores the SN of the last SDU that was received in sequence. The fifth state variable stores the first SN after the SN of the RLC SDU that triggered the first timer.
4. The method according to claim 1, characterized in that, Before the control data packet is triggered, the first state variable is updated in the following way: When the first timer expires, the first state variable is updated to be no less than the current first state variable, and no less than the third state variable or no less than the fifth state variable or no less than the maximum value of the third state variable and the fifth state variable, and the SN of the first RLC SDU that has not been fully received. When the second timer expires and the receiver of the RLC entity enables the first timer, the first state variable is updated to be no less than the current first state variable, and no less than the third state variable or the sixth state variable or the maximum value of the third state variable and the sixth state variable, and the first SN of the first RLC SDU that has not been fully received. Specifically, the first timer starts when there is a SN gap, and if an SDU that is not successfully received within the SN gap times out, it is considered outdated. The third state variable stores the SN of the next SDU expected to be received in sequence. The fifth state variable stores the first SN after the SN of the RLC SDU that triggered the second timer. The sixth state variable stores the first SN after the SN of the RLC SDU that triggered the second timer. The second timer starts when there is a SN gap, and if an SDU that is not successfully received within the SN gap times out, it is considered a reception failure.
5. The method according to claim 3 or 4, characterized in that, When the third state variable is not greater than the first state variable, the construction and transmission of the control data packet includes: The first data packet is constructed based on the updated first state variable and the third state variable; Send the first data packet.
6. The method according to claim 1, characterized in that, The control data packet is constructed based on the second state variable. When the second state variable is not less than the first state variable, the construction and transmission of the control data packet includes: Based on the second state variable, determine the next SN of the largest SN of the SDU in the first data packet that determines the reception state; Send the first data packet.
7. The method according to claim 1, characterized in that, When the third state variable is greater than or equal to the first state variable, the construction and transmission of the control data packet includes: A second data packet is constructed and sent, the second data packet indicating the next SN of the largest SN of the SDU that determines the reception status, and not including the indication information of the SN of the SDU that determines the reception failure.
8. The method according to claim 7, characterized in that, The construction and transmission of the second data packet includes: When the first timer times out, the next SN of the maximum SN of the SDU with the determined reception state in the second data packet is determined based on the third state variable; When the third timer is not running or the third timer expires, if the third state variable is greater than the first state variable, the second data packet is assembled and delivered to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity. The first timer is started when there is an SN gap, and if the timer expires, the SDU that was not successfully received within the SN gap is confirmed as outdated. The third timer is started when a first data packet has been submitted to the lower layer, and the first data packet is prohibited from being sent before the third timer expires. The first data packet is assembled when the third state variable is less than or equal to the first state variable.
9. The method according to claim 7, characterized in that, The construction and transmission of the second data packet includes: When the first timer times out, the next SN of the largest SN of the SDU with the determined reception state in the second data packet is determined based on the third variable; The second data packet is assembled and submitted to the lower layer for transmission to the receiving end of the RLC entity.
10. The method according to claim 7, characterized in that, The construction and transmission of the second data packet includes: When the first timer times out, the next SN of the largest SN of the SDU with the determined reception state in the second data packet is determined based on the third variable; When the fourth timer is not running or the fourth timer expires, the second data packet is assembled and submitted to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity; and when the second data packet has been submitted to the lower layer, the fourth timer is started. When the fourth timer is running, after the fourth timer expires, the second data packet is assembled and delivered to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity. The first timer is started when there is a SN gap, and if the timer expires, the SDU that was not successfully received within the SN gap is considered outdated.
11. The method according to claim 1, characterized in that, When the third state variable is greater than or equal to the first state variable, the construction and transmission of the control data packet includes: A third data packet is constructed and sent, the third data packet indicating the SN of the SDU that determines the reception status, but not including indication information of the SN of the SDU that determines the reception failure.
12. The method according to claim 11, characterized in that, The maximum SN of the SDU indicating the determination of the reception state in the third data packet is equal to the third state variable when the enhanced polling indication or polling indication is received. The SN of the other SDU indicating the receiving state as specified in the third data packet is greater than or equal to the third state variable when the enhanced polling indication or polling indication is received, and less than the fourth state variable.
13. The method according to claim 11 or 12, characterized in that, The third data packet also includes at least one of the following indication fields: Second field, third field, fourth field, fifth field, sixth field, seventh field; The second field is used to indicate whether there is another set of SDU SNs with a determined reception status after the corresponding SDU SN with a determined reception status, or the second field, or the third field, or the fourth field; The third field is used to indicate whether there is a set of the fifth and sixth fields after the SN of the corresponding SDU that determines the reception status; The fourth field is used to indicate whether there are continuously received SDUs after the SN of the corresponding SDU with the determined reception status; The fifth field is used to indicate the start position of the received SDU portion when the SN is equal to the SN of the corresponding SDU with the determined reception state; The sixth field is used to indicate the end of reception position of the SDU portion of the received data when the SN is equal to the SN of the corresponding SDU with the determined reception status. The seventh field is used to indicate the number of consecutive RLC SDUs that determine the reception status.
14. The method according to claim 11 or 12, characterized in that, The construction and transmission of the third data packet includes: Upon receiving the enhanced polling instruction or polling instruction, the third data packet is assembled and sent.
15. The method according to claim 11 or 12, characterized in that, The construction and transmission of the third data packet includes: When the third timer is not running or the third timer expires, if the third state variable is greater than the first state variable, the third data packet is assembled and delivered to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity. The third timer is started when a first data packet has been submitted to the lower layer, and the first data packet is prohibited from being sent before the third timer expires. The first data packet is assembled when the third state variable is less than or equal to the first state variable.
16. The method according to claim 11 or 12, characterized in that, The construction and transmission of the third data packet includes: When the fifth timer is not running or the fifth timer expires, the third data packet is assembled and submitted to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity; and when the third data packet has been submitted to the lower layer, the fifth timer is started. When the fifth timer runs, after the fifth timer expires, the third data packet is assembled and delivered to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity.
17. The method according to claim 1, characterized in that, The receiving end of the RLC entity uses a seventh state variable to store the next SN of the largest SN of the SDU that determined the reception state of the control data packet sent in the last transmission. The construction and transmission of the control data packet includes: When the first state variable is greater than or equal to the seventh state variable, a fourth data packet is constructed and sent. The fourth data packet includes indication information for determining the SN of the SDU that failed to be received, but does not include indication information for determining the SN of the SDU that was received.
18. The method according to claim 17, characterized in that, The construction and transmission of the fourth data packet specifically includes: When the transmission conditions are met, the fourth data packet is assembled and delivered to the lower layer at the first transmission opportunity indicated by the lower layer, and transmitted to the receiving end of the RLC entity. The sending condition is any one of the following: The first timer expires. The first timer is started when there is a SN gap, and if the timer expires, the SDU that was not successfully received within the SN gap is confirmed to be outdated. The second timer times out. The second timer starts when there is an SN gap, and if the timer times out, any SDU that is not successfully received within the SN gap is considered a reception failure. Received the enhanced polling instruction or polling instruction; The first timer times out, and the third timer times out or is not started. The third timer starts when a first data packet has been submitted to the lower layer, and the first data packet is prohibited from being sent before the third timer times out. The first data packet is assembled when the third state variable is less than or equal to the first state variable. The second timer times out, and the third timer times out or is not started; The enhanced polling instruction or polling instruction is received, and the third timer times out or is not started; The first timer expired, and the sixth timer expired or did not start; The second timer expires, and the sixth timer expires or is not started; The enhanced polling instruction or polling instruction is received, and the sixth timer times out or is not started.
19. A communication method, characterized in that, The sending end applied to RLC entities includes: Receive a control data packet, wherein, before the control data packet is triggered, a first state variable is updated; or, the control data packet is constructed based on the first state variable, or based on a second state variable, or based on a third state variable, or based on a third state variable and a fourth state variable, and the type of the constructed control data packet is indicated by a first field. The first state variable stores the next SN of the maximum sequence number SN of the Service Data Unit (SDU) that has determined the reception status; the second state variable stores the next SN of the maximum SN of the SDU that has determined the reception status, and stores the SN of the next SDU that is expected to be received in sequence; the third state variable stores the SN of the next SDU that is expected to be received in sequence; and the fourth state variable stores the next SN of the SDU with the highest SN among the RLC SDUs that have been determined to be received.
20. The method according to claim 19, characterized in that, Before the control data packet is triggered, the first state variable is updated in the following way: When the first timer times out and the first state variable is not greater than the third state variable or the fifth state variable or the minimum value among the third state variable and the fifth state variable, the first state variable is updated to the SN of the first RLC SDU that is not less than the third state variable or the fifth state variable or the maximum value among the third state variable and the fifth state variable and has not been fully received. The first timer is started when there is a SN gap, and if the timer expires, the SDU that was not successfully received within the SN gap is confirmed as outdated. The third state variable stores the SN of the last SDU that was received in sequence. The fifth state variable stores the first SN after the SN of the RLC SDU that triggered the first timer.
21. The method according to claim 20, characterized in that, Before the control data packet is triggered, the first state variable is updated in the following way: When the first timer expires, the first state variable is updated to be no less than the current first state variable, and no less than the third state variable or no less than the fifth state variable or no less than the maximum value of the third state variable and the fifth state variable, and the SN of the first RLC SDU that has not been fully received. When the second timer times out and the receiver of the RLC entity enables the first timer, the first state variable is updated to be no less than the current first state variable, and no less than the third state variable or the sixth state variable or the maximum value of the third state variable and the sixth state variable, and the first SN of the first RLC SDU that has not been fully received. Specifically, the first timer starts when there is a SN gap, and if an SDU that is not successfully received within the SN gap times out, it is considered outdated. The third state variable stores the SN of the next SDU expected to be received in sequence. The fifth state variable stores the first SN after the SN of the RLC SDU that triggered the second timer. The sixth state variable stores the first SN after the SN of the RLC SDU that triggered the second timer. The second timer starts when there is a SN gap, and if an SDU that is not successfully received within the SN gap times out, it is considered a reception failure.
22. The method according to claim 20 or 21, characterized in that, The method further includes: When it is determined that the first data packet has been received based on the first field, the first indication information is submitted to the upper layer based on the first data packet. The first indication information indicates the SN of the SDU that determines the reception status. Wherein, the first data packet is constructed based on the updated first state variable and the third state variable when the third state variable is not greater than the first state variable.
23. The method according to claim 19, characterized in that, The method further includes: When it is determined that the first data packet has been received based on the first field, the first indication information is submitted to the upper layer based on the first data packet. The first indication information indicates the SN of the SDU that determines the reception status. The first data packet is constructed based on the second state variable. When the second state variable is not less than the first state variable, the next SN of the largest SN of the SDU with the determined reception state in the constructed first data packet is determined based on the second state variable.
24. The method according to claim 19, characterized in that, The method further includes: When it is determined that a second data packet has been received based on the first field, a second indication information is submitted to the upper layer based on the second data packet. The second indication information indicates the SN of the SDU that determines the reception status. The second data packet is constructed and sent when the third state variable is greater than or equal to the first state variable. The second data packet indicates the next SN of the largest SN of the SDU that determines the reception status, and does not include indication information of the SN of the SDU that determines the reception failure.
25. The method according to claim 19, characterized in that, The method further includes: When it is determined that a third data packet has been received based on the first field, third indication information is submitted to the upper layer based on the third data packet. The third indication information indicates the SN of the SDU that determines the reception status and / or the received SDU portion of the SN of the SDU that determines the reception status. The third data packet is constructed and sent when the third state variable is greater than or equal to the first state variable. The third data packet indicates the SN of the SDU that determines the reception status, but does not include indication information of the SN of the SDU that determines the reception failure.
26. The method according to claim 25, characterized in that, The third data packet also includes at least one of the following indication fields: Second field, third field, fourth field, fifth field, sixth field, seventh field; The second field is used to indicate whether there is another set of SDU SNs with a determined reception status after the corresponding SDU SN with a determined reception status, or the second field, or the third field, or the fourth field; The third field is used to indicate whether there is a set of the fifth and sixth fields after the SN of the corresponding SDU that determines the reception status; The fourth field is used to indicate whether there are continuously received SDUs after the SN of the corresponding SDU with the determined reception status; The fifth field is used to indicate the start position of the received SDU portion when the SN is equal to the SN of the corresponding SDU with the determined reception state; The sixth field is used to indicate the end of reception position of the SDU portion of the received data when the SN is equal to the SN of the corresponding SDU with the determined reception status. The seventh field is used to indicate the number of consecutive RLC SDUs that determine the reception status.
27. The method according to claim 19, characterized in that, The method further includes: When the control data packet is determined to be the fourth data packet based on the first field, the fourth indication information is submitted to the upper layer based on the fourth data packet. The fourth indication information indicates that the SN is less than the next SN of the maximum SN of the SDU indicating the reception status indicated by the control data packet in the previous received data packet, and is not the SDU reception success of the maximum SN of the SDU indicating the reception failure indicated by the control data packet in the previous received data packet. The fourth data packet is constructed and sent when the first state variable is greater than or equal to the seventh state variable. The seventh state variable stores the next SN of the largest SN of the SDU with the determined reception status of the control data packet sent in the last time. The fourth data packet includes indication information of the SN of the SDU with the determined reception failure, but does not include indication information of the SN of the SDU with the determined reception.
28. A communication device, characterized in that, The terminal device includes a processor and a memory; The processor is coupled to the memory; The memory is used to store instructions; The processor is used to execute computer programs or instructions stored in the memory to implement the method as described in any one of claims 1-27.
29. A computer storage medium, characterized in that, The computer storage medium is used to store a computer program, which, when executed, implements the method as described in any one of claims 1-27.
30. A computer program product, characterized in that, When the computer program product is run on the communication device, the communication device enables the communication device to implement the method as described in any one of claims 1-27.
