Wireless communication method and related device

Abstract

According to the wireless communication method and the related device provided by the embodiment of the invention, the serial number of the to-be-sent key data is embedded in advance when the sending end generates the currently transmitted data packet, and the receiving end can obtain the serial number of the key data in advance by analyzing the currently received data packet, so that the monitoring delay for the key data is avoided. A receiving end determines that the key data starts to be transmitted or lost according to the serial number of the key data, a first timer is started, the timing duration of the first timer is smaller than the timing duration of a recombination timer, if the key data is not completely received until the first timer is overtime, a state report is immediately returned to a sending end, and the sending end sends the key data to the receiving end. Therefore, the time delay of key data state feedback is reduced, namely the time delay of sensing the key data state by the sending end is shortened, the retransmission of the key data is triggered in time, and the retransmission response of the key data is improved.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a wireless communication method and related apparatus. Background Technology

[0002] As 5G-Advanced and future networks deepen their support for critical services such as ultra-reliable low-latency communication (URLLC), XR, industrial control, and vehicle-to-everything (V2X), the radio link control (RLC) layer is required to meet millisecond-level latency and reliability standards. However, the automatic repeat request (ARQ) mechanism used in the current acknowledged mode (AM) of the RLC layer leads to increased latency and reduced reliability of critical data. Summary of the Invention

[0003] In view of the above, this application provides a wireless communication method and related apparatus to solve at least some of the aforementioned problems, and the disclosed technical solution is as follows:

[0004] In a first aspect, this application provides a wireless communication method executed by a transmitting end. The method includes: transmitting first data to a receiving end, the first data including a first sequence number corresponding to the first data and a second sequence number of second data to be transmitted, the second sequence number being used to instruct the receiving end to monitor the second data in a directional manner; transmitting the second data in ascending order of sequence numbers in a transmission window, the second data including the second sequence number; receiving a first status report from the receiving end, the first status report including a negative status and a second sequence number, generated by the receiving end when it detects that the second data has not arrived completely before a first timer expires, the first timer being started when the receiving end detects that data with a sequence number greater than or equal to the second sequence number has arrived, the timing duration of the first timer being less than the timing duration of the reassembly timer; and triggering retransmission of the second data in response to the first status report.

[0005] As can be seen, in this method, the sending end pre-embeds the sequence number of the key data to be sent when generating the currently transmitted data packet. The receiving end can obtain the sequence number of the key data in advance by parsing the currently received data packet, avoiding monitoring delays for key data. The receiving end determines whether the key data has started transmission or has been lost based on the sequence number of the key data, and starts a first timer. The duration of the first timer is shorter than the duration of the reassembly timer. If the key data is not fully received before the first timer expires, a status report is immediately returned to the sending end without waiting for the reassembly timer to expire. This reduces the latency of key data status feedback and promptly triggers the retransmission of key data, improving the retransmission response of key data.

[0006] In one possible implementation, sending first data to the receiving end includes: receiving second data to be processed from an upper protocol layer; assigning a second sequence number corresponding to the current protocol layer to the second data to be processed; the second data to be processed includes key data indication information, which is used to indicate that the second data to be processed is key data; when generating the first data, embedding the second sequence number into the first data, and sending the first data to the receiving end; the first data includes a first sequence number field and a second sequence number field, the first sequence number field is filled with the sequence number of the first data, and the second sequence number field is filled with the sequence number corresponding to the second data.

[0007] As can be seen, in this scheme, the upper-layer protocol layer adds critical data indication information to the critical data to indicate that the data is critical. In this way, the current protocol layer identifies the critical data that the receiver needs to prioritize monitoring through the critical data indication information, and then embeds the sequence number of the critical data into the data to be transmitted, instructing the receiver to prioritize monitoring that critical data. Identifying critical data through critical data indication information lays the groundwork for subsequently instructing the receiver to prioritize monitoring of critical data.

[0008] In one possible implementation, the transmitting end includes a Packet Data Convergence Protocol (PDCP) entity, a Radio Link Layer Control (RLC) entity, and a Media Access Control (MAC) entity; and transmits first data to the receiving end, including:

[0009] The RLC entity receives second data to be processed from the PDCP entity and assigns a second sequence number corresponding to the RLC layer to the second data to be processed. The second data to be processed includes key data indication information, which is used to indicate that the second data to be processed is key data. Based on the first data to be processed received from the PDCP entity and the second sequence number, the RLC entity generates first data. The first data includes a first sequence number field and a second sequence number field. The first sequence number field is filled with the first sequence number, and the second sequence number field is filled with the sequence number corresponding to the second data. The RLC entity sends the first data to the MAC entity, which is used to send the first data to the receiving end.

[0010] In this scheme, the PDCP layer adds key data indication information to the key data packets, and the RLC layer identifies the key data through the key data indication information. It further pre-embeds the sequence number of the newly received key data in the data packets currently being transmitted to the receiving end, notifying the receiving end in advance to prioritize the monitoring of key data and promptly providing feedback on the reception status of key data.

[0011] In one possible implementation, the second data includes key data indication information, which indicates that the second data is key data. Thus, if the first data transmission with the pre-embedded key data sequence number fails, the receiving end can use the key data indication information carried in the key data packet itself to identify that the data is key data, and promptly report the reception status of the data to the sending end, improving the success rate of the receiving end in obtaining key data, and thereby improving the timeliness of key data status feedback.

[0012] Secondly, this application also provides a wireless communication method executed by a receiving end. The method includes: receiving first data from a transmitting end, the first data including a first sequence number corresponding to the first data and a second sequence number of second data to be transmitted, the second sequence number being used to instruct the receiving end to monitor the second data in a specific direction; if data with a sequence number greater than or equal to the second sequence number is received, starting a first timer, the timing duration of the first timer being less than the timing duration of a reassembly timer; if complete second data is not received before the first timer expires, sending a first status report to the transmitting end, the first status report being used to indicate that the second data reception has failed, including a negative status and the second sequence number.

[0013] As can be seen, in this scheme, the receiving end obtains the sequence number of the key data that needs to be monitored in advance by parsing the currently received data packets, thus avoiding monitoring delays for key data. Furthermore, when the transmission of the key data is detected to have started, a first timer with a timing duration shorter than the reassembly timer is started. If the key data is not fully received before the first timer expires, a negative reception status is immediately fed back to the sending end without waiting for the t-Reassembly timer to expire, enabling the sending end to quickly detect the loss of key data and promptly trigger the retransmission process of the key data.

[0014] In one possible implementation, the method further includes: if the received second data contains key data indication information, starting a first timer, the timing duration of the first timer being less than the timing duration of the reassembly timer; if the complete second data is not received before the first timer expires, sending a first status report to the sending end, the first status report indicating that the second data reception has failed, including a negative status and a second sequence number of the second data.

[0015] This scheme is suitable for scenarios involving segmented data transmission. If the receiving end fails to know the sequence number of the critical data in advance, it can use the critical data indication information carried by the critical data packet itself to identify that the data is critical and promptly report the reception status of the data to the sending end, thereby improving the success rate of the receiving end in obtaining the critical data and thus improving the timeliness of the critical data status feedback.

[0016] Thirdly, this application also provides a communication device including at least one processor coupled to a memory storing a program or instructions, wherein the processor executes the program or instructions to cause the device to perform a method as described in either the first or second aspect.

[0017] Fourthly, this application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed, cause a computer to perform the method as described in either the first or second aspect.

[0018] Fifthly, this application also provides a communication system, including the communication device as described in the third aspect.

[0019] Sixthly, this application also provides a chip system including one or more processors, the one or more processors being configured to call and execute instructions stored in memory, such that the methods of either the first or second aspect are performed. Attached Figure Description

[0020] Figure 1 A schematic diagram of a communication system provided in an embodiment of this application;

[0021] Figure 2 A schematic diagram of a layered protocol stack used in an NR air interface, provided for an embodiment of this application;

[0022] Figure 3 This application provides a schematic diagram of data transmission in an RLC layer according to an embodiment of the present application.

[0023] Figure 4 A flowchart illustrating a wireless communication method provided in an embodiment of this application;

[0024] Figure 5 A schematic diagram of the header data format of PDCP PDU and RLC PDU provided for embodiments of this application;

[0025] Figure 6 A flowchart illustrating an example of a wireless communication method provided in an embodiment of this application;

[0026] Figure 7 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0027] Figure 8 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0028] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation 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" refers to 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.

[0029] 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.

[0030] The "multiple" mentioned in the embodiments of this application refers to two or more. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order.

[0031] 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.

[0032] Figure 1 This is an example of a communication system applicable to embodiments of this application. The communication system includes at least one network device and at least one terminal device. Figure 1 The example uses a network device and multiple terminal devices. These terminal devices can be cellular phones, smartphones, laptops, handheld communication devices, handheld computing devices, satellite radio devices, GPS devices, personal digital assistants (PDAs), and / or any other suitable devices for communication over a wireless communication system, all of which can connect to the network device. These terminal devices can all communicate with the network device; in addition, they can also communicate with each other. Figure 1 The number of terminal devices and network devices mentioned is just an example; there could be fewer or more.

[0033] 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 macro base stations, micro base stations or indoor stations, relay nodes or donor nodes, or wireless controllers in cloud radioaccess network (CRAN) scenarios. Optionally, access network equipment can also be servers, wearable devices, 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] Access network equipment and / or terminal equipment 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 equipment and terminal equipment. They can be deployed in the same or different scenarios; for example, both can be deployed on land simultaneously; or the access network equipment can be deployed on land while the terminal equipment is deployed on water, etc., and so on.

[0038] In another possible scenario, multiple network devices collaborate to assist the terminal in achieving wireless access, with each network device performing a portion of the base station's functions. For example, these network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs). CUs and DUs can be separate entities 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).

[0039] 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.

[0040] In this embodiment, the form of the network device is not limited. The device used to implement the function of the network device can be the network device itself, or it can be a device that supports the network device in implementing the function, such as a chip system. The device can be installed in the network device or used in conjunction with the network device.

[0041] Please see Figure 2 This diagram illustrates a layered protocol stack used in an NR air interface according to an embodiment of this application.

[0042] The NR user plane protocol stack may include the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and the physical layer. Among them:

[0043] The main function of the SDAP layer is to map the Quality of Service (QoS) flow to the data radio bearer (DRB).

[0044] The PDCP layer is located between the SDAP layer and the RLC layer, providing message forwarding functions for the user plane / control plane, security functions (encryption / integrity protection), header compression / data compression, timed discarding, reordering, and in-order delivery.

[0045] The RLC layer, located between the PDCP and MAC layers, provides functions such as data transmission, segmentation / reassembly, automatic repeat request (ARQ), and duplicate detection. The RLC layer supports three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and AM Mode.

[0046] (1) TM mode is used to transmit data of signaling radio bearer 0 (SRB0), paging data, and broadcast system messages. These messages cannot be segmented. The data is transparently transmitted through the RLC protocol layer. Among them, SRB0 is used to transmit radio resource control (RRC) messages carried by the CCCH (common control channel) logical channel.

[0047] (2) UM mode is suitable for real-time services with high latency requirements and tolerance for errors. Once a data packet is transmitted through the UM RLC entity, the transmission is considered to be complete. Even if the data packet is lost during air interface transmission, the RLC layer will not retransmit it.

[0048] (3) AM mode is suitable for non-real-time services with high reliability requirements, such as web browsing, file transfer protocol (FTP) file download, signaling transmission, etc. Such services need to avoid data loss as much as possible. The AM RLC entity uses the ARQ mechanism to ensure lossless data transmission. The basic idea of ​​ARQ is that the receiving end RLC entity can feed back the sending end an RLC status report, indicating which data packets were successfully received and which data packets failed to be received. The sending end RLC entity can retransmit the failed data packets based on the RLC status report.

[0049] The main functions of the MAC layer are to provide radio resource selection, scheduling information reporting, MAC layer service data unit (SDU) multiplexing and demultiplexing, and hybrid automatic repeat request (HARQ) transmission of data packets.

[0050] Please see Figure 3 This diagram illustrates the data transmission process at the RLC layer.

[0051] A protocol data unit (PDU) is the output of a layer, while an SDU is the input of a layer. The input data of the RLC layer is the RLC SDU, and the output data is the RLC PDU.

[0052] like Figure 3 As shown, the RLC entity at the sending end receives data PDCP PDU (i.e., RLC SDU) transmitted from the upper layer protocol (such as PDCP). It assigns a unique sequence number, SN, to each RLC SDU. This sequence number is used by the receiving end for sorting and acknowledgment. It also adds header information (including the sequence number, etc.) to the RLC SDU and encapsulates it into an RLC PDU, which is then sent to the receiving end through the MAC layer and the physical layer.

[0053] The number of RLC PDUs transmitted is related to the size of the MAC layer's transport block (TB). If the MAC TB size is insufficient to transmit a complete RLC PDU, the RLC will segment the RLC PDU. Figure 3 As shown, the MAC TB is not large enough to transmit three RLC PDUs. SDU3 can be divided into two segments, such as SDU3-1 and SDU3-2. SDU1, SDU2, and SDU3-1 can be transmitted through the same MAC TB, with SDU3-1 transmitted together with the subsequent SDUs.

[0054] Using the traditional ARQ mechanism to transmit critical data has the following problems:

[0055] (1) Accumulated delay in key data feedback.

[0056] In segmented transmission scenarios, to ensure all RLC PDUs are correctly received and to avoid data loss, a reassembly timer (e.g., t-Reassembly) is used. When the receiver detects a lost PDU (e.g., an intermediate PDU is not received), it starts the t-Reassembly timer. During the timer's operation, the receiver continuously checks whether the PDU has been received. After the t-Reassembly timer expires, a status report is triggered, reporting the range of received PDUs and the range of lost PDUs. When the RLC entity at the receiver receives an RLC PDU, it checks its sequence number (SN). If the current highest received sequence number (RX_Next_Highest) is greater than the next expected sequence number (RX_Next), it indicates a gap, and the t-Reassembly timer is started or restarted. Conversely, if the sequence is continuous (RX_Next_Highest = RX_Next), the t-Reassembly timer is stopped. It is evident that retransmission requires waiting for the t-Reassembly timer to time out. However, for low-latency critical data such as industrial control commands and XR interactive data, waiting for the t-Reassembly timer to time out may exceed the latency threshold requirement of the service, thereby causing the related functions to fail.

[0057] (2) The sending window is stagnant and resources are wasted.

[0058] The update of the lower limit of the sending window (TxNextAck) of an RLC AM entity depends on the receiver's status report. The lower limit of the sending window is the sequence number (ACK_SN) of the last data packet that the sender has received an acknowledgment from the receiver. Upon receiving the SN carried in the receiver's acknowledgment report, the sender automatically updates the lower limit of the sending window, moving it up one sequence number. If the data status report is lost, the sender cannot confirm the range of received PDUs, causing the sending window to stall. This stalling results in new data having SNs outside the sending window range, preventing transmission and thus hindering the transmission of critical new data. Furthermore, since the PDUs that the RLC entity needs to send are initially buffered in the sending buffer until the receiver successfully receives them, the buffer resources occupied by the PDU are not released until the status report is lost. Data that has already been transmitted but for which no status report has been received still occupies buffer resources, affecting subsequent data transmission.

[0059] (3) There is currently no targeted monitoring of key data.

[0060] Currently, critical data is treated the same as ordinary data. Its status reporting triggers depend on polling, reassembly timers (e.g., t-Reassembly), or discard timers (t-RxDiscard) timeouts. As a result, the status feedback of critical data may lag behind that of ordinary data, leading to a decrease in the reliability of critical data.

[0061] To address the aforementioned issues, this application provides a wireless communication method in which the transmitting end pre-embeds the sequence number of key data to be transmitted when generating the currently transmitted data packet. The receiving end can obtain the sequence number of the key data in advance by parsing the current data packet and prioritizes monitoring the reception status of data packets with that sequence number. If the key data is not received or is received incompletely, a status report of the key data is immediately returned to the transmitting end, thus reducing the latency of key data status feedback. This triggers the transmitting end to retransmit the key data in a timely manner, improving the retransmission response of key data. Furthermore, after the key data is successfully retransmitted, the occupied buffer resources can be released in a timely manner, improving resource utilization.

[0062] Please see Figure 4 The diagram shows a flowchart of a wireless communication method provided in an embodiment of this application.

[0063] Understandable. Figure 4 The sending end can be a terminal device or a network device, and the receiving end is the device peering from the sending end. For example, if the sending end is a terminal device, then the receiving end is a network device; conversely, if the sending end is a network device, then the receiving end can be a terminal device. The terminal device can refer to a component within the terminal device (such as a processor, chip, or chip system). The network device can be... Figure 1 Any access network device, or a device within an access network device (such as a processor, chip, or chip system).

[0064] like Figure 4 As shown, the method may include the following steps:

[0065] S101, the sending end transmits first data. The first data includes the first sequence number (SN) of the first data and the second SN of the second data to be transmitted. Correspondingly, the receiving end receives the first data.

[0066] The second data in this embodiment is the key data that the receiving end needs to monitor first, such as key instructions or key business data.

[0067] The RLC entity receives PDCP PDUs from the upper protocol layer, generates RLC layer SNs for the data in the order of receipt, and adds header information to the received data to encapsulate it into an RLC PDU.

[0068] In one possible implementation, such as Figure 5 As shown in (1), the upper protocol layer (PDCP layer) can add a critical data indication field (such as the C field) to the header of the PDCPPDU to indicate whether the data is critical data that the receiver needs to monitor first. After receiving the data, the RLC entity identifies whether the data is critical data by the value of the C field. For example, the critical data indication field occupies 1 bit. When C=1, it indicates that the SDU is critical data; when C=0, it indicates that the SDU is not critical data.

[0069] Among them, D / C (Data / Control): is used to indicate whether it is a data PDU or a control PDU, occupying 1 bit, 0 indicates a control PDU, and 1 indicates a data PDU;

[0070] C: Used to indicate whether it is critical data, occupying 1 bit, 0 indicates that it is not critical data, and 1 indicates that it is critical data;

[0071] SN (sequence number): Represents the PDU's sequence number, occupying 12 bits or 18 bits;

[0072] MAC-I is a 32-bit verification code for data integrity protection.

[0073] In one possible implementation, such as Figure 5 As shown in (2), a critical serial number indicator field (critical SN) is added to the header of the RLC PDU to indicate the serial number of critical data that needs to be monitored first.

[0074] in, Figure 5 The other header information of the RLC PDU shown in (2) is as follows:

[0075] D / C (Data / Control): Used to indicate whether it is a data PDU or a control PDU, occupying 1 bit, 0 indicates a control PDU, 1 indicates a data PDU;

[0076] P (polling bit): Used to indicate whether the receiver needs to report a status report. It occupies 1 bit. 0 means no status report is needed and 1 means a status report is needed. When the number of unpolled PDUs or bytes accumulated by the sender reaches the configured threshold (such as pollPDU or pollByte), polling will be triggered, that is, the P bit will be set to 1.

[0077] SI (Segmentation Info): Used to identify the segmentation location, indicating whether the RLC PDU contains a complete SDU or a segmented SDU. It occupies 2 bits: 00 indicates the PDU contains all bytes of the SDU; 01 indicates the PDU contains the first segment of the SDU; 10 indicates the PDU's data field contains the last segment of the SDU; 11 indicates the PDU's data field contains an intermediate segment of the SDU.

[0078] SN (sequence number): The SDU sequence number, responsible for data sorting and preventing retransmission, occupies 12 bits or 18 bits; the RLC entity assigns ascending sequence numbers to each RLC SDU according to the SN in ascending order. In the scenario of segmented transmission of an RLC SDU, the SNs in all PDU segments corresponding to that RLC SDU are the same. If an RLC SDU with SN=3 is divided into two segments for transmission, then the sequence numbers of the two RLC PDUs corresponding to the RLC SDU with SN=3 are both SN=3.

[0079] SO (segment offset): Occupies 16 bits and is used to indicate the byte position of the segment packet in the original SDU, that is, the position of the first byte of the SDU segment in the original SDU. The first byte of the original SDU has a value of all 0. When there is a segment, and the segment is not the first segment, the SO field is included.

[0080] Critical SN: An extended field used to indicate the sequence number of critical data that the receiver needs to monitor first, occupying 12 bits or 18 bits.

[0081] Optionally, the header of the RLC PDU may also include a critical data indicator field, namely the C field, which is used to indicate whether the RLC PDU is critical data; it occupies 1 bit, where 1 indicates that the RLC PDU is critical data and 0 indicates that the RLC PDU is not critical data.

[0082] In particular, the critical SN field and C field in the RLC PDU header are both reserved bits in the PDU.

[0083] If the RLC entity at the transmitting end receives an RLC SDU with C=1, it determines that the data is critical data that the receiving end needs to monitor first, and fills the critical SN field of the critical data with the sequence number of the critical data.

[0084] For example, if a new RLC SDU with SN=5 is received from the upper protocol layer, denoted as RLC SDU5, and the critical data indicator field C=1 is parsed from RLC SDU5, then RLC SDU5 is determined to be critical data, and 5 is filled into the critical SN field of the RLC PDU currently being transmitted to the receiving end (e.g., RLC PDU3). In this way, when the receiving end receives RLC PDU3, it can simultaneously know the sequence number SN=5 of the critical data that needs to be monitored first, avoiding monitoring delays for this critical data. The sending end's RLC entity transmits RLC PDU3 to the receiving end through the MAC layer and physical layer.

[0085] S102, the receiving end successfully received the first data and extracted the second SN.

[0086] The receiver successfully received RLC PDU3 and parsed the critical SN field in the header to obtain the second SN, that is, to know the SN of the key data that needs to be monitored first.

[0087] S103, the receiving end sends the first status report to the sending end.

[0088] The first status report contains the serial number (SN) of the first data. The report content is encapsulated in the form of a STATUSPDU, which includes ACK_SN (the range of consecutive sequence numbers acknowledged as received) and NACK_SN (the sequence numbers or ranges that were not received). For example, when the receiver detects that the RLC PDU with SN=2 is lost, it will report NACK_SN=2 via STATUSPDU, instructing the sender to retransmit the PDU.

[0089] If the receiving end successfully receives the first data, it sends a status report confirming receipt to the sending end. This status report includes the SN of the first data, i.e., ACK_SN.

[0090] If the receiving end does not receive the first data (i.e., the first data is lost), or does not receive the first data completely (e.g., the first data is transmitted in segments and all segments of the first data are not successfully received), the t-Reassembly timer is started. If the first data is not received within the time set by the timer (0-200ms), a status report is triggered, that is, a non-received status report, NACK_SN, is sent to the sending end, so as to promptly notify the sending end that the reception of the first data has failed, so that the sending end can trigger the retransmission of the first data as soon as possible.

[0091] S104, the transmitting end transmits the second data in the transmitting window to the receiving end in ascending order of SN.

[0092] For example, at a certain time t, the data in the transmission window consists of RLC PDUs with SN=1 to SN=10. After the transmitter finishes sending the RLC PDU with SN=1, it continues to send the RLC PDU with SN=2, and so on.

[0093] S105, the receiving end determines whether the SN of the currently received data is greater than or equal to the second SN; if so, it executes S106; otherwise, it receives the next data and continues to execute S105.

[0094] After the receiving end parses the first data to obtain the SN (i.e., the second SN) of the priority monitoring data, it determines whether the SN of the data is greater than or equal to the second SN each time a new RLC PDU is received. If the SN of the currently received RLC PDU is equal to the second SN, it indicates that the currently received RLC PDU is the second data that needs to be monitored first.

[0095] If the SN of the currently received RLC PDU is greater than the second SN, and no RLCPDU with a SN equal to the second SN has been received previously, it indicates that the second data may be lost.

[0096] S106, the receiving end starts the first timer.

[0097] When the receiving end detects that the SN of the currently received data is greater than or equal to the SN of the critical data, it starts the first timer and continuously monitors whether the critical data has been received completely.

[0098] The timing duration of the first timer (which can be called the t-early-trigger timer) is shorter than that of the reassembly timer (t-Reassembly timer).

[0099] In one possible implementation, the timing duration T of the t-early-trigger timer... early-trigger =A×T Reassembly Where 0 < A < 1, and can be dynamically adjusted according to the needs of key data. For example, T Reassembly =20ms, A=0.65, then T early-trigger =13ms.

[0100] In this way, when the receiving end times out the t-early-trigger timer and has not received the critical data completely, it can promptly send a status report of the critical data to the sending end without waiting for the t-Reassembly timer to time out. This allows the sending end to quickly detect the loss of critical data and promptly trigger the retransmission process of the critical data.

[0101] In one possible scenario, the receiving end may not have fully received the data pre-embedded with the key data sequence number, even though the key data has already begun transmission. In this case, the receiving end may not be able to know the sequence number of the key data in advance, and therefore cannot monitor the reception status of the key data. If the receiving end parses the key data indicator field in the currently received data and finds that it is the first value (C=1), it determines that the currently received data is key data, immediately starts the first timer, and continuously monitors whether the data has arrived completely.

[0102] S107, the receiving end determines whether the second data has arrived completely before the first timer expires.

[0103] If the second data arrives completely before the first timer expires, that is, the receiving end receives the complete second data (such as a complete PDU, or all segments of the second data PDU) before the first timer expires, then execute S108; if the complete second data is not received before the first timer expires (such as the second data not arriving or some segments arriving), then execute S109.

[0104] In RLC SDU segmented transmission scenarios, the receiver determines whether all segments of the RLC SDU have been received completely using the segment identifier (SI) and segment offset (SO). The receiver identifies the first, middle, and last segments of the RLC SDU based on the SI field of the RLC PDU. Furthermore, it maps the RLCPDU to the byte positions of the RLC SDU based on the SO fields of all non-first segments. If all byte positions of the RLC SDU are covered without overlap or gaps, the RLC SDU is considered to have arrived completely; otherwise, it is considered that the RLC SDU has not arrived completely.

[0105] S108, the receiving end sends a second status report to the sending end. Correspondingly, the sending end receives the second status report.

[0106] If the receiving end does not receive the complete second data before the first timer expires, it immediately triggers the critical data feedback mechanism, that is, it immediately sends a status report to the sending end. The NACK_SN in this status report is the SN of the second data, used to notify the sending end that the data reception corresponding to the second SN has failed. In addition, the status report includes the offset (SO) of the missing segment, so that the sending end can retransmit the missing segment in the critical data.

[0107] Status reports, as a type of control PDU, have a higher priority than all other types of data PDUs. Therefore, the receiving end sends status reports of critical data to the sending end through the priority scheduling of air interface resources pre-configured by RRC, ensuring that the sending end receives the status reports in a timely manner.

[0108] S109, the sending end responds to the second status report and triggers the retransmission of the second data.

[0109] After the sending end receives the second status report and parses it to obtain NACK_SN=second SN, it triggers the process of retransmitting the second data.

[0110] S110, the receiving end turns off the first timer and resets it.

[0111] If the receiving end receives complete second data before the first timer expires, it shuts down the first timer and resets the timing duration of the first timer to its initial value. If the first timer is a countdown timer, it is reset to the set timing duration; if the first timer is a positive timer, it is reset to 0.

[0112] S111, the receiving end sends a third status report to the sending end. Correspondingly, the sending end receives the third status report.

[0113] In this embodiment of the application, when the receiving end successfully receives the key data, it will immediately send a status report to the sending end indicating that the key data has been successfully received. That is, the third status report includes ACK_SN as the second SN.

[0114] After receiving the status report, the sending end confirms that the second data has been successfully received by the receiving end, updates the lower limit of the sending window, and continues to transmit other data to be sent within the sending window.

[0115] The wireless communication method provided in this embodiment allows the transmitting end to pre-embed the sequence number of the key data in the generated data packet after receiving key data from the upper-layer protocol. This allows the receiving end to obtain the pre-embedded key data sequence number by parsing the current data packet, thus knowing the sequence number of the key data that needs to be monitored in advance and avoiding monitoring delays for key data. The receiving end determines whether the key data has started transmission or has been lost based on the key data sequence number and starts a first timer. The duration of the first timer is shorter than the duration of the reassembly timer. If the key data is not fully received before the first timer expires, a status report is immediately returned to the transmitting end without waiting for the reassembly timer to expire, thereby reducing the latency of key data status feedback and shortening the latency for the transmitting end to perceive the key data status. This allows for timely triggering of key data retransmission and improves the retransmission response. Furthermore, after successful retransmission of the key data, the occupied buffer resources can be released promptly, improving resource utilization.

[0116] The following example illustrates the flow of the wireless communication method provided in this application. This embodiment uses the example of XR glasses sending data to a cloud server. The sending end is the XR glasses, and the receiving end is the cloud server.

[0117] like Figure 6 As shown, the method may include the following steps:

[0118] S201, the sending end receives data from the upper layer protocol, the key data indicator field C=1, and the SN=7 of the corresponding RLC PDU.

[0119] The sensors of XR glasses capture the user's hand gestures when grasping virtual objects. The delay in the gestures will cause the user to feel a delay in operation. Therefore, the gestures are critical data with high latency requirements. The PDCP layer sets a critical data indicator field C=1 in the header of the data to indicate that the data is critical data.

[0120] After receiving data with a critical data indication field of 1, the RLC layer confirms that the data is critical data and assigns a sequence number SN=7 to the gesture command in sequence.

[0121] S202, when generating the RLC PDU for the current transmission, embed critical SN=7 into the PDU.

[0122] After the RLC layer identifies the newly received data as critical data, it pre-fills the SN of the critical data into the RLC PDU with SN=3 to be transmitted (i.e., RLC PDU3), which is used to indicate that the receiver should prioritize monitoring the PDU with SN=7. In addition, the header of the RLCPDU also includes a critical data indication field C. In this example, RLC PDU3 is ordinary frame data, so C=0, which is used to indicate that the PDU is not critical data, but ordinary data.

[0123] As can be seen, RLC PDU3 includes the data content and sequence number SN=3 corresponding to this data, as well as the sequence number of the critical data that needs to be monitored first, namely critical SN=7, and C=0.

[0124] S203, the receiver parses RLC PDU3 to obtain critical SN=7.

[0125] Upon receiving RLC PDU3, the receiving end (cloud rendering server) parses the pre-embedded CriticalSN=7 through the protocol stack and immediately adds SN=7 to the priority monitoring list. Simultaneously, based on C=0, RLC PDU3 is determined to be ordinary data and processed according to the standard mechanism.

[0126] S204, the receiver sends a status report containing ACK_SN=3 to the sender.

[0127] S205, the sending end sequentially sends the subsequent RLC PDUs, that is, RLC PDUs with SN=4~6.

[0128] S206, the sending end sends RLC PDU7. RLC PDU7 has SN=7 and C=1.

[0129] S207, the sending end sends RLC PDU8. The SN of RLC PDU8 is 8.

[0130] S208, if the receiving end determines that the SN of the currently received data is greater than or equal to 7, then the first timer is started.

[0131] In one scenario, the RLC SDU with SN=7 is transmitted to the receiving end in the same MAC TB PDU. In this scenario, the receiving end does not receive the PDU with SN=7, but directly receives the PDU with SN=8. That is, when it detects that the data with SN>7 has arrived, it determines that the PDU with SN=7 has been lost and immediately starts the first timer.

[0132] In another scenario, the RLC SDU with SN=7 is transmitted in segments, meaning the data is divided into multiple segments and transmitted to the receiving end via different MAC TBPDUs. In this scenario, when the receiving end receives the PDU segment with SN=7, it determines that the key data has started to be transmitted, that is, it enters the key data transmission window and immediately starts the first timer.

[0133] S209, the receiving end checks whether the PDU with SN=7 has arrived completely before the first timer expires; if not, it executes S210, and if so, it executes S212.

[0134] The timing duration of the first timer (t-early-trigger timer) is shorter than that of the t-Reassembly timer, and this can be configured via RRC configuration signaling. For example, in this example, T... early-trigger =13ms, T Reassembly =20ms.

[0135] S210, the receiver sends a negative status report to the sender. This status report includes NACK, SN=7, and missing segment information.

[0136] If the RLC PDU7 fails to arrive completely by the timer expires at the receiver (t-early-trigger), the receiver triggers a forced feedback status report mechanism, immediately sending a negative status report to the sender. This report includes NACK, SN=7, and information about the missing segment. This status report can be encapsulated and sent within 1ms, ensuring the sender quickly detects the loss of critical data.

[0137] S211, the sending end triggers retransmission of RLC PDU7.

[0138] After receiving the NACK status report, the sending end immediately triggers the retransmission mechanism, namely retransmitting RLC PDU7, where C=1 in the PDU header to ensure that the receiving end continues to focus on monitoring the PDU.

[0139] Data can be retransmitted to the cloud server within 5ms. After the cloud server completes the rendering, it retransmits the image frame data. The overall latency can be controlled within 18ms, which is less than the 20ms that the human eye can perceive, thus avoiding user dizziness.

[0140] S212, the receiving end turns off the first timer and resets it.

[0141] If the receiver receives all segments of RLC PDU7 and successfully reassembles them before the t-early-trigger timer expires, the t-early-trigger timer is immediately turned off and reset.

[0142] S213, the receiving end sends a status report to the sending end. This status report includes ACK and SN=7.

[0143] In this example, after the cloud server confirms that the gesture command with SN=7 has been fully received, it calls the GPU-accelerated rendering module and returns it to the XR glasses via the downlink. The user's perspective is updated synchronously, with no sense of operation delay.

[0144] It should be understood that Figures 1 to 6 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 6 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0145] The above text combined Figures 1 to 6 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figures 7 to 8 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0146] In the embodiments described above, the sending end may execute some or all of the steps in each embodiment; the receiving end may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and other operations or variations thereof may also be performed in the embodiments of this application. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step 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.

[0147] Figure 7 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 7 As shown, the communication device may include a communication module 102. The communication module 102 can implement corresponding communication functions, which can be internal communication functions of the communication device or communication functions between the communication device and other devices. Optionally, the communication module 102 may also be referred to as a communication interface or transceiver module. Optionally, the communication device further includes a processing module 101. The processing module 101 can implement corresponding processing functions.

[0148] Optionally, the communication device further includes a storage module, which can be used to store instructions and / or data; the processing module 101 can read the instructions and / or data in the storage module so that the communication device can implement the aforementioned method embodiments.

[0149] In one possible design, the communication device may correspond to the transmitting end in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the transmitting end. The communication device can be used to perform the steps or processes executed by the transmitting end in any of the above method embodiments.

[0150] For example, the communication module 102 is used to send first data to the receiving end. The first data includes a first sequence number corresponding to the first data and a second sequence number of the second data to be transmitted. The second sequence number is used to instruct the receiving end to monitor the second data in a specific direction. The second data includes the second sequence number. The receiving end receives a first status report from the receiving end. The first status report includes a negative status and a second sequence number. The report is generated by the receiving end when it detects that the second data has not arrived completely before the first timer expires. The first timer is started when the receiving end detects that data with a sequence number greater than or equal to the second sequence number has arrived. The timing duration of the first timer is less than the timing duration of the reassembly timer.

[0151] The processing module 101 is used to trigger the communication module 102 to retransmit the second data to the receiving end in response to the first status report.

[0152] In one possible implementation, when the communication module 102 sends the first data to the receiving end, it is specifically used for:

[0153] The system receives second data to be processed from the upper protocol layer, assigns a second sequence number corresponding to the current protocol layer to the second data to be processed, and the second data to be processed includes key data indication information, which is used to indicate that the second data to be processed is key data; and, when generating the first data, the second sequence number is embedded in the first data, and the first data is sent to the receiving end; the first data includes a first sequence number field and a second sequence number field, the first sequence number field is filled with the sequence number of the first data, and the second sequence number field is filled with the sequence number corresponding to the second data.

[0154] In one possible implementation, the sending end includes a PDCP entity, an RLC entity, and a MAC entity; when the communication module 102 sends the first data to the receiving end, it is specifically used for:

[0155] The RLC entity receives the second data to be processed from the PDCP entity and assigns a second sequence number corresponding to the RLC layer to the second data to be processed. The second data to be processed includes key data indication information, which is used to indicate that the second data to be processed is key data.

[0156] The RLC entity generates first data based on the first data to be processed and the second sequence number received from the PDCP entity. The first data includes a first sequence number field and a second sequence number field. The first sequence number field is filled with the first sequence number, and the second sequence number field is filled with the sequence number corresponding to the second data.

[0157] The RLC entity sends the first data to the MAC entity, which then sends the first data to the receiving end.

[0158] In one possible implementation, the second data includes key data indication information, which is used to indicate that the second data is key data.

[0159] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0160] In one possible design, the communication device may correspond to the network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the network device. The communication device can be used to perform the steps or processes executed by the network device in any of the above method embodiments.

[0161] For example, the communication module 102 is used to receive first data from the sending end. The first data includes a first sequence number corresponding to the first data and a second sequence number of second data to be transmitted. The second sequence number is used to instruct the receiving end to monitor the second data in a directional manner.

[0162] The processing module 101 is used to start a first timer if it receives data with a sequence number greater than or equal to the second sequence number. The duration of the first timer is less than the duration of the reassembly timer. If the second data is not received before the first timer expires, the communication module 102 is triggered to send a first status report to the sending end. The first status report is used to indicate that the second data reception has failed, including a negative status and the second sequence number.

[0163] In one possible implementation, the processing module 101 is further configured to: if the received second data contains key data indication information, start a first timer, the timing duration of the first timer being less than the timing duration of the reassembly timer; if the complete second data is not received before the first timer expires, trigger the communication module to send a first status report to the sending end, the first status report indicating that the second data reception has failed, including a negative status and the second sequence number of the second data.

[0164] In one possible implementation, the processing module 101 is further configured to: if complete second data is received before the first timer expires, shut down the first timer and reset it.

[0165] In one possible implementation, the communication module 102 is further configured to: if complete second data is received before the first timer expires, send a second status report to the sending end, the second status report including an acknowledgment status and a second sequence number, to indicate that the second data has been completely received.

[0166] In one possible implementation, the timing duration of the first timer is n times the timing duration of the recombinant timer, where 0 < n < 1.

[0167] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0168] Figure 8 This is another schematic block diagram of the communication device provided in the embodiments of this application. The communication device may be a chip, chip system, or processor, etc., in a terminal device or network device that implements the above-described methods. This communication device can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0169] like Figure 8As shown, the communication device may include one or more processors 201, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 201 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device (e.g., base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0170] In an alternative design, the processor 201 may also store instructions and / or data that can be executed by the processor 201 to cause the communication device to perform the methods described in the above method embodiments.

[0171] In another alternative design, the communication device may include a communication interface 202 for implementing receiving and transmitting functions. For example, the communication interface 202 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0172] Optionally, the communication device may include one or more memories 203, which may store instructions that can be executed on the processor 201, causing the communication device to perform the methods described in the above method embodiments. Optionally, the memories 203 may also store data. Optionally, the processor 201 may also store instructions and / or data. The processor 201 and the memories 203 may be provided separately or integrated together.

[0173] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0174] In one implementation, the communication device may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 201 may be used to execute instructions stored in the memory 203, and when the processor 201 executes the instructions stored in the memory, the processor 201 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0175] In another implementation, the communication device may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 201 may be used to execute instructions stored in the memory 203, and when the processor 201 executes the instructions stored in the memory, the processor 201 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0176] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device 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 microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0177] 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.

[0178] 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.

[0179] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0180] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device and terminal device.

[0181] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0182] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0183] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0184] 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.

[0185] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in 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.

[0186] 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.

[0187] 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.

[0188] 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 wireless communication method, characterized in that, The method, executed by the sending end, includes: Send first data to the receiving end. The first data includes a first sequence number corresponding to the first data and a second sequence number of the second data to be transmitted. The second sequence number is used to instruct the receiving end to monitor the second data in a specific direction. The second data is sent in ascending order of the sequence number in the sending window, and the second data includes the second sequence number. The receiver receives a first status report, which includes a negative status and a second sequence number. The first status report is generated by the receiver when it detects that the second data has not arrived completely before the first timer expires. The first timer is started when the receiver detects that data with a sequence number greater than or equal to the second sequence number has arrived. The timing duration of the first timer is less than the timing duration of the reassembly timer. The second data is retransmitted in response to the first status report.

2. The method according to claim 1, characterized in that, Sending the first data to the receiving end includes: The second data to be processed received from the upper protocol layer is assigned a second sequence number corresponding to the current protocol layer. The second data to be processed includes key data indication information, which is used to indicate that the second data to be processed is key data. When generating the first data, the second sequence number is embedded in the first data, and the first data is sent to the receiving end. The first data includes a first sequence number field and a second sequence number field. The first sequence number field is filled with the sequence number of the first data, and the second sequence number field is filled with the sequence number corresponding to the second data.

3. The method according to claim 1, characterized in that, The transmitting end includes a Packet Data Convergence Protocol (PDCP) entity, a Radio Link Layer Control Protocol (RLC) entity, and a Media Access Control Protocol (MAC) entity. Sending the first data to the receiving end includes: The RLC entity receives the second data to be processed from the PDCP entity and assigns a second sequence number corresponding to the RLC layer to the second data to be processed. The second data to be processed includes key data indication information, which is used to indicate that the second data to be processed is key data. The RLC entity generates first data based on the first data to be processed received from the PDCP entity and the second sequence number. The first data includes a first sequence number field and a second sequence number field. The first sequence number field is filled with the first sequence number, and the second sequence number field is filled with the sequence number corresponding to the second data. The RLC entity sends the first data to the MAC entity, which then sends the first data to the receiving end.

4. The method according to claim 2 or 3, characterized in that, The second data includes key data indication information, which is used to indicate that the second data is key data.

5. The method according to claim 4, characterized in that, The first timer is started when the receiving end detects that the received data contains the key data indication information.

6. A wireless communication method, characterized in that, The method, executed by the receiving end, includes: The receiver receives first data from the sender, the first data including a first sequence number corresponding to the first data and a second sequence number of second data to be transmitted, the second sequence number being used to instruct the receiver to monitor the second data in a directional manner. If data with a sequence number greater than or equal to the second sequence number is received, the first timer is started, and the timing duration of the first timer is less than the timing duration of the reassembly timer. If the second data is not received by the time the first timer expires, a first status report is sent to the sending end. The first status report is used to indicate that the second data reception has failed, including a negative status and the second sequence number.

7. The method according to claim 6, characterized in that, The method further includes: If the received second data is parsed to contain key data indication information, start the first timer. The timing duration of the first timer is less than the timing duration of the reassembly timer. If the second data is not received by the time the first timer expires, a first status report is sent to the sending end. The first status report indicates that the second data reception has failed, including a negative status and the second sequence number of the second data.

8. The method according to claim 6 or 7, characterized in that, The method further includes: If the complete second data is received before the first timer times out, the first timer is turned off and reset.

9. The method according to claim 8, characterized in that, The method further includes: If the complete second data is received before the first timer expires, a second status report is sent to the sending end. The second status report includes an acknowledgment status and the second sequence number, which indicates that the second data has been completely received.

10. The method according to claim 6 or 7, characterized in that, The timing duration of the first timer is less than the timing duration of the reassembly timer, including: The timing duration of the first timer is n times the timing duration of the recombinant timer, where 0 < n < 1.

11. A communication device, characterized in that, The device includes at least one processor coupled to a memory storing a program or instructions, the processor executing the program or instructions to cause the device to perform the method as described in any one of claims 1 to 10.

12. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1 to 10.

13. A communication system, characterized in that, Includes the communication device as described in claim 11.

14. A chip system comprising one or more processors, the one or more processors being configured to retrieve and execute instructions stored in memory, such that the method of any one of claims 1 to 10 is performed.

Images