Communication method and communication device

By treating unreceived data packets as received in RLC confirmation mode, the problem of large packet transmission delay is solved, and the effect of reducing delay and saving resources is achieved, and high reliability and low delay are met. data business requirements.

CN119096589APending Publication Date: 2024-12-06QUECTEL WIRELESS SOLUTIONS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480001402.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-06-21
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In the existing RLC acknowledgement mode, the data packet transmission delay is large and cannot meet the data service requirements of high reliability and low latency.

Method used

When a specific condition is met, the first device treats unreceived data packets as received, thereby avoiding unnecessary retransmission, reducing delay and saving transmission resources. This condition is determined based on the received second data packet, by sending information to determine whether or not the unreceived first data packet is considered to have been received.

Benefits of technology

It effectively reduces delay, saves transmission resources, avoids unnecessary retransmission, and improves the reliability and efficiency of data services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096589A_ABST
    Figure CN119096589A_ABST
Patent Text Reader

Abstract

Provided are a communication method and a communication device, the communication method comprising: when a first condition is satisfied, a first device regards that a first data packet that is not received is received, the first condition being determined based on a second data packet received by the first device, the first data packet and the second data packet are data packets transmitted in a radio link control (RLC) acknowledgement mode. In the embodiment of the invention, the first device determines whether the unreceived data packet is considered to be received, and avoids triggering unnecessary retransmission by considering the unreceived data packet is considered to be received, thereby being beneficial to reducing time delay and saving transmission resources.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art

[0002] The radio link control (RLC) layer includes three working modes, namely transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM). In the AM mode, when the receiving end does not receive the data packets sent by the sending end, it can instruct the sending end to retransmit these data packets through the RLC status report. However, the data packet transmission delay of the current retransmission mechanism is relatively large. In particular, for some data services with high reliability and low latency requirements, the existing AM mode cannot meet their needs. Summary of the invention

[0003] The present application provides a communication method and a communication device. The following introduces various aspects involved in the present application.

[0004] In a first aspect, a communication method is provided, including: when a first condition is met, a first device regards a first data packet that has not been received as received, and the first condition is determined based on a second data packet received by the first device, and the first data packet and the second data packet are data packets transmitted in a radio link control RLC confirmation mode.

[0005] In a second aspect, a communication method is provided, including: a second device sends first information to a first device, the first information is used to determine whether to regard a first data packet that has not been received as received, the first information is associated with a second data packet received by the first device, and the first data packet and the second data packet are data packets transmitted in an RLC confirmation mode.

[0006] According to a third aspect, a communication device is provided, comprising: a processing unit, for determining whether to regard a first data packet that has not been received as received based on first information, wherein the first information is associated with a second data packet received by the first device, and the first data packet and the second data packet are data packets transmitted in an RLC confirmation mode.

[0007] In a fourth aspect, a communication device is provided, comprising: a sending unit, used to send first information to a first device, the first information being used to determine whether to regard an unreceived first data packet as received, the first information being associated with a second data packet received by the first device, the first data packet and the second data packet being data packets transmitted in an RLC confirmation mode.

[0008] In a fifth aspect, a communication device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the communication device executes part or all of the steps in the method of the first aspect.

[0009] In a sixth aspect, a communication device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the communication device executes part or all of the steps in the method of the second aspect.

[0010] In a seventh aspect, an embodiment of the present application provides a communication system, wherein the communication system includes the above-mentioned communication device, such as a first device and a second device. In some implementations, the communication system also includes other devices that interact with the communication device.

[0011] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a communication device, such as a first device and a second device, to perform part or all of the steps in the methods of the above aspects.

[0012] In a ninth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable a communication device, such as a first device and a second device, to perform some or all of the steps in the above-mentioned various aspects of the method. In some implementations, the computer program product may be a software installation package.

[0013] In the tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0014] In an embodiment of the present application, the first device determines whether to regard an unreceived data packet as received, and by regarding an unreceived data packet as received, avoids triggering unnecessary retransmission, which is beneficial to reducing latency and saving transmission resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a schematic diagram of a wireless communication system that may be applied in an embodiment of the present application.

[0016] Figure 2 It is a schematic diagram of possible protocol layers of an embodiment of the present application.

[0017] Figure 3 It is a schematic diagram of data packet retransmission in AM mode.

[0018] Figures 4 to 7 It is a schematic diagram of the changes in the state parameters of the receiving end.

[0019] Figure 8 It is a schematic diagram of an embodiment of the present application in which a transmitting end instructs a receiving end that it no longer retransmits a data packet.

[0020] Fig. 9 It is a schematic flow chart of a communication method according to an embodiment of the present application.

[0021] Fig.10 It is a schematic flow chart of a communication method according to another embodiment of the present application.

[0022] Fig.11 It is a schematic block diagram of a communication device according to an embodiment of the present application.

[0023] Fig.12 It is a schematic block diagram of a communication device according to an embodiment of the present application.

[0024] Fig.13 It is a schematic block diagram of a device for communication according to an embodiment of the present application. DETAILED DESCRIPTION

[0025] The technical solution in this application will be described below in conjunction with the accompanying drawings. Figures 1 to 4 Introduce the communication terms and communication processes that may be involved in the embodiments of the present application.

[0026] Communication System

[0027] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as the fifth generation (5th generation, 5G) system or the new radio (new radio, NR) system, the long term evolution (long term evolution, LTE) system, the LTE frequency division duplex (frequency division duplex, FDD) system, the LTE time division duplex (time division duplex, TDD) system, etc. The technical solutions of the embodiments of the present application can also be applied to future communication systems, such as the sixth generation (6th generation, 6G) mobile communication system, satellite communication system, etc.

[0028] Figure 1The wireless communication system 100 used in the embodiment of the present application may include a network device 110 and a terminal device 120. The network device 110 may provide communication coverage for a specific geographical area and may communicate with the terminal device 120 located in the coverage area.

[0029] For example, Figure 1 One network device 110 and two terminal devices 120 are shown. Optionally, the wireless communication system 100 may include multiple network devices 100, and each network device 100 may include other number of terminal devices 110 within its coverage area. In addition, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity.

[0030] In the embodiments of the present application, the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal device, wireless communication device, user agent or user device. The terminal device may be, for example, a device that provides voice and / or data connectivity to a user, and may be used to connect people, objects and machines, such as household appliances, sensors, and electronic tags with wireless connection functions. The terminal device may also be a wireless terminal in a smart home, a wireless terminal in an IWSN, a wireless terminal in smart logistics and smart warehousing, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, and the like.

[0031] The network device may be a device for communicating with the terminal device. The network device may also be an access network device or a radio access network device, for example, the network device may be a base station. The network device in the embodiment of the present application may refer to a radio access network (RAN) node or device that connects the terminal device to the wireless network. A base station may broadly cover various names as follows, or may be replaced with the following names, for example: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station (MeNB), secondary station (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), centralized unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. The base station may also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station may also be a mobile switching center and a device to device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication device that performs the base station function, a network side device in a 6G network, and a device that performs the base station function in a future communication system. The base station may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network equipment.

[0032] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0033] In some deployments, the network device may refer to a CU or a DU; or, the network device includes a CU and a DU. Optionally, the gNB may include an AAU.

[0034] The network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air. The embodiments of the present application do not limit the scenarios in which the network equipment and terminal equipment are located.

[0035] Working mode of RLC layer

[0036] In order to realize data transmission over the air interface, the wireless cellular network sets up corresponding protocol layers in the network equipment and terminal equipment to complete different functions. Figure 2 As shown in the figure, the network equipment and terminal equipment may include the packet data convergence protocol (PDCP) layer, RLC layer, media access control (MAC) layer, physical layer (PHY) and other protocol layers. Among them, the PDCP layer is responsible for security, integrity protection, in-order transmission, etc.; the RLC layer is responsible for data forwarding, segmentation, retransmission, discarding and RLC reconstruction, etc.; the MAC layer is responsible for allocating transmission opportunities to each data radio bearer (DRB) and organizing transmission blocks for transmission; the PHY layer is responsible for transmitting data on the wireless interface.

[0037] The technical solution of the embodiment of the present application mainly relates to the RLC layer. The RLC layer is located between the PDCP layer and the MAC layer. It communicates with the PDCP layer through the RLC channel (RLC channel) and communicates with the MAC layer through the logical channel (logical channel, LCH). The functions of the RLC layer are implemented by the RLC entity, and the RLC entity is created when the RLC bearer is established and deleted when the RLC bearer is released. Each RLC entity can be configured by the radio resource control (RRC) layer and includes 3 working modes: transparent mode TM, unconfirmed mode UM, and confirmed mode AM, to meet different business needs.

[0038] Among them, the TM mode is also called transparent transmission mode, which is mainly used for information transmission such as paging and broadcasting. For the RLC entity using the TM mode, the data is transparent, and the RLC entity will not make any modifications to the data, such as not segmenting the RLC service data unit (SDU) and not adding any header information. The TM entity consists of a transmission buffer that stores RLC SDUs, and its function is to cache forwarding data. When the MAC layer notifies the TM entity that there is a transmission opportunity, the TM entity sends the RLC SDU in the transmission buffer directly to the MAC layer without making any modifications.

[0039] The UM mode provides an unreliable service and cannot guarantee 100% successful data transmission. For the RLC entity using the UM mode, after receiving the data from the upper layer, an unacknowledged mode data (UMD) protocol data unit (PDU) will be generated for each RLC SDU, which includes the header information, and the generated UMD PDU will be cached in the transmission buffer. When the MAC layer notifies it to send the RLC PDU, if necessary, some RLC SDUs will be segmented, and the RLC header and RLC PDU will be regenerated so that the total size of the RLC PDU finally sent is equal to the total size indicated by the MAC layer. In the UM mode, the sender is only responsible for sending the data and does not care whether the other end successfully receives the data; after receiving the data, the receiver will not send the sender a confirmation message whether it has received the data correctly. Therefore, in the UM mode, data can be delivered to the other end RLC entity in sequence with the shortest delay. The UM mode is mainly suitable for services that are sensitive to latency but allow a certain packet loss rate, such as NR voice calls (voice over newradio, VoNR) and other services.

[0040] The AM mode provides a reliable service, which is mainly suitable for services that are not sensitive to delays but are sensitive to errors, such as file transfer protocol (FTP) services. In order to ensure that each data can be transmitted successfully, the AM mode is configured with an automatic repeat request (ARQ) error correction function. After sending the data, the sender needs to wait for the receiver to reply with confirmation information on whether the data has been received correctly, and resend the data that the receiver failed to receive in the case of a negative confirmation. Therefore, the AM mode can provide reliable data transmission for the upper layer and ensure that the data is delivered to the other end in the correct order. In the AM mode, multiple retransmissions can be performed when data transmission is unsuccessful, and when the number of retransmissions reaches the maximum number of retransmissions, it is considered that the quality of the wireless interface is too poor, and RRC re-establishment is initiated. Therefore, the data transmission delay in the AM mode is relatively large.

[0041] Status parameters in AM mode

[0042] The basic design idea of ​​the AM mode is to ensure that each data packet is successfully transmitted through retransmission, and the retransmission process is triggered by the RLC status report sent by the receiving end. The receiving end maintains the relevant status parameters, continuously updates the status parameters according to the RLC sequence number (SN) carried in the header of the received data packet, and sends an RLC status report to the sending end when certain conditions are met to urge the sending end to retransmit the data packet. It should be noted that the sequence number of the data sent by the sending end is gradually increased in sequence, but due to the hybrid automatic repeat-request acknowledgement (HARQ) retransmission of the MAC layer, the sequence number of the data packet received by the receiving end may not be monotonically increasing, so the receiving end designs the status parameters to trigger the RLC status report.

[0043] For example, Figure 3 The flowchart of triggering retransmission in AM mode is shown in FIG. 1 . The first device is a receiving end and the second device is a transmitting end. For example, the first device is Figure 1 The terminal device 120 shown in FIG. 1 is a second device. Figure 1 The network device 110 shown in FIG. 1 ; or the second device is Figure 1 The network device 110 shown in FIG. 1 is a first device. Figure 1 The terminal device 120 shown in FIG.

[0044] like Figure 3 As shown, in step 111, the second device sends a data packet to the first device.

[0045] If the first device is a terminal device and the second device is a network device, the data packet is a downlink data packet; if the second device is a network device and the first device is a terminal device, the data packet is an uplink data packet.

[0046] In step 112, the first device determines whether to send an RLC status report according to current status parameters.

[0047] Wherein, when it is determined to send the RLC status report, step 113 and step 114 are executed.

[0048] In step 113, the first device sends an RLC status report to the second device.

[0049] In step 114, the second device retransmits the data packet based on the RLC status report.

[0050] In AM mode, the receiving end needs to maintain the following status parameters, where RX represents the receiving end:

[0051] The first parameter (denoted as RX_Next) is used to indicate the next sequence number after the last completely correctly received data packet, and can be used as the lower edge of the receive window. The receive window is [RX_Next, RX_Next + AM_Window_Size], where AM_Window_Size is the length of the receive window, for example, it can usually be selected as 2 SN / 2, assuming that the length of SN is 12 bits, the length of the receiving window can be 2 12 / The length corresponding to 2 data packets;

[0052] The second parameter (denoted as RX_Highest_Status) is used to indicate the sequence number updated when the reassembly timer (t-Reasembly Timer) times out, which corresponds to ACK_SN when the RLC status report is triggered, or the maximum value that ACK_SN can be set to in the RLC status report;

[0053] The third parameter (denoted as RX_Next_Highest) is used to indicate the next sequence number after the sequence number of the data packet with the highest sequence number is received;

[0054] The fourth parameter (denoted as RX_Next_Status_Trigger) is used to indicate the sequence number of the next incorrectly received data packet after the sequence number of the data packet that triggered the reassembly timer.

[0055] At the RLC layer, explicit confirmation is not performed for each data packet. The receiving end usually sends RLC status reports for multiple data packets to reduce overhead. The conditions for triggering the RLC status report may include, for example, one or more of the following: the receiving end receives polling information sent by the sending end; the reassembly timer times out; the status prohibition timer (t-StatusProhibit) times out.

[0056] The reassembly timer is used to detect packet loss in the underlying transmission. When a hole appears in the receiving window of the RLC entity at the receiving end, that is, when the SN of the received data packet is discontinuous, the reassembly timer is started; when the hole between the sequence numbers indicated by RX_Next and RX_Next_status_trigger is filled, the reassembly timer is stopped and cleared; when the reassembly timer times out, the RLC entity at the receiving end triggers an RLC status report and sends the RLC status report to the RLC entity at the sending end.

[0057] The following, combined Figures 4 to 7 Here, it is assumed that the size of the receiving window (AM_Window_Size) is 10.

[0058] In the initial state, RX_Next, RX_Highest_Status, RX_Next_Highest, and RX_Next_Status_Trigger are all set to 0.

[0059] In the case of receiving in order, such as Figure 4 As shown, RX_Next, RX_Highest_Status, and RX_Next_Highest are updated in sequence; RX_Next_Status_Trigger remains unchanged and the reassembly timer is not started.

[0060] Specifically, Figure 4As shown, after receiving the data packet with SN=0, RX_Next_Status_Trigger remains at the initial value, i.e., SN=0, and RX_Next, RX_Highest_Status, and RX_Next_Highest are all updated to SN=1; after receiving the data packet with SN=1, RX_Next_Status_Trigger remains at the initial value, i.e., SN=0, and RX_Next, RX_Highest_Status, and RX_Next_Highest are all updated to SN=2; after receiving the data packet with SN=2, RX_Next_Status_Trigger remains at the initial value, i.e., SN=0, and RX_Next, RX_Highest_Status, and RX_Next_Highest are all updated to SN=3. If the RLC status report is assembled at this time, ACK_SN=3 is filled in the RLC status report.

[0061] In non-ideal situations, such as Figure 4 As shown, assuming that the receiving end receives data packets with SN=0, SN=5, and SN=8 in sequence, when receiving the data packet with SN=5, since the transmitting end sends data packets in the order of increasing SN, the receiving end can determine that the transmitting end has sent data packets with SN=1, SN=2, SN=3, and SN=4, but these 4 data packets have undergone HARQ retransmission and have not been received yet. Therefore, the receiving end starts the reassembly timer to wait for these 4 data packets.

[0062] Specifically, Figure 4 As shown, when receiving the data packet of SN=5, RX_Highest_Status remains at SN=0, RX_Next is updated to SN=1, RX_Next_Status_Trigger and RX_Next_Highest are updated to SN=6; when receiving the data packet of SN=8, RX_Highest_Status remains at SN=0, RX_Next is updated to SN=1, RX_Next_Status_Trigger remains at SN=6, and RX_Next_Highest is updated to SN=9. Here, when receiving the data packet of SN=8, the previously started reassembly timer has not timed out, so the data packet that triggers the start of the reassembly timer is still the data packet of SN=5, so RX_Next_Status_Trigger is still SN=6 after SN=5. Of course, if the previously started reassembly timer has timed out before receiving the data packet of SN=8, the start of the reassembly timer can be triggered again when receiving the data packet of SN=8, and at this time, RX_Next_Status_Trigger is updated to SN=9.

[0063] based on Figure 4 In the case shown in FIG. 1 , if the receiving end receives packets with SN=1, SN=2, SN=3, and SN=4 during the operation of the reassembly timer, that is, before the reassembly timer times out, then based on Figure 5 Update the corresponding status parameters.

[0064] Specifically, Figure 5 As shown, after receiving the data packet with SN=4, RX_Next is updated to SN=6. It is determined that RX_Next_Status_Trigger=RX_Next, the reassembly timer is stopped, and then it is determined that RX_Next_Highest>RX_Next+1, and the reassembly timer is started again to wait for the data packets with SN=6 and SN=7, and RX_Next_Status_Trigger is set to SN=9. Here, the RLC status report is not triggered when the reassembly timer is stopped, and the RLC status report may be triggered only when the reassembly timer times out. If the RLC status report is assembled at this time, ACK_SN=6 is filled in the RLC status report, and the physical layer HARQ retransmission is reserved during the operation of the reassembly timer.

[0065] based on Figure 5 In the case shown in FIG. 1 , if the receiving end does not wait for the data packets of SN=1, SN=2, SN=3 and SN=4 during the operation of the reassembly timer, an RLC status report is sent to the sending end when the reassembly timer times out to instruct the sending end to perform retransmission. Figure 7 Update the corresponding status parameters.

[0066] Specifically, Figure 7 As shown, the reassembly timer times out, RX_Highest_Status is updated to SN = 6, and RX_Next_Highest>RX_Highest_Status+1 is judged, the reassembly timer is started again, and RX_Next_Status_Trigger is set to SN = 9. If the RLC status report is assembled at this time, ACK_SN = 0 and NACK_SN = 1, 2, 3, 4 are filled in the RLC status report, and it is considered that the physical layer will no longer report the data packets of SN = 1, SN = 2, SN = 3 and SN = 4.

[0067] Based on the above description, due to the large data transmission delay of the AM mode, for some data services with high reliability and low latency requirements, such as extended reality (XR) services, in order to ensure the reliability of data transmission, it is necessary to use the AM mode for data transmission. In addition, due to the burst characteristics of XR services, that is, service data arrives at the access layer in the form of data packet clusters, and the transmission delay budget is short, if the delay budget expires and the transmission is not successful, even if the transmission is successful later, it is meaningless to the receiving end and will waste transmission resources.

[0068] To this end, in an embodiment of the present application, the transmitting end may send a notification to the receiving end to inform the receiving end which data packets will no longer be transmitted. Figure 8 As shown, the first device is still taken as the receiving end and the second device is taken as the sending end as an example.

[0069] like Figure 8 As shown, in step 121, the second device sends a data packet cluster 1 to the first device.

[0070] The data packet cluster 1 includes a plurality of data packets with consecutive sequence numbers, for example, SN=0 to SN=49, a total of 50 data packets.

[0071] In step 122, the first device sends an RLC status report to the second device.

[0072] During the initial transmission process, some data packets are successfully transmitted, while some data packets are not successfully transmitted. The first device can notify the second device which data packets are successfully transmitted and which data packets are not successfully transmitted through the RLC status report. Assuming that the first data packet in the data packet cluster is not successfully transmitted, the data packets that are not successfully transmitted in the RLC status report include the first data packet.

[0073] In step 123, the second device retransmits the first data packet based on the RLC status report.

[0074] Wherein, during the retransmission process, if the PDCP discard timer maintained by the PDCP layer of the second device times out, the PDCP layer notifies the RLC layer that the discard timer of the first data packet has timed out. Generally, if the RLC layer has started to retransmit the first data packet, it does not delete the first data packet, but continues to transmit the first data packet.

[0075] In recent discussions, the behavior of the sender has been changed. Even if the first data packet has started transmission at the RLC layer, the second device still deletes the first data packet and does not send the first data packet to the first device. Although the PDCP layer of the second device notifies the RLC layer that the first data packet that has not been successfully transmitted does not need to be transmitted, the first device is unaware of this and triggers an RLC status report due to the reassembly timer expiration, but the second device does not trigger retransmission for this RLC status report.

[0076] To this end, step 124 may be performed.

[0077] In step 124, the second device sends a notification to the first device to indicate that the first data packet will not be retransmitted.

[0078] That is, after the second device deletes the first data packet, the first device may know that the second device will no longer retransmit the first data packet, and the first device may modify the status parameters by itself and no longer trigger the RLC status report.

[0079] In step 125, the second device sends a packet cluster 2 to the first device.

[0080] Data packet cluster 2 may include a plurality of data packets with consecutive sequence numbers, for example, 50 data packets from SN=50 to SN=999.

[0081] As described above, if the second device notifies the first device of the data packet that is no longer to be transmitted, it is necessary to increase the signaling overhead and occupy additional air interface transmission resources.

[0082] In view of this, an embodiment of the present application provides a data transmission scheme under AM mode, in which the first device determines whether to regard an unreceived data packet as received, and regards an unreceived data packet as received to avoid triggering unnecessary retransmission, which is beneficial to reducing latency and saving transmission resources.

[0083] The data packets described in the embodiments of the present application include, for example, SDUs and / or SDU fragments, or include PDUs and / or PDU fragments. Taking SDUs and SDU fragments as an example, each SDU has a sequence number. The sequence numbers of multiple fragments of an SDU are the same, and the sequence numbers of the SDUs to which they belong are used. The RLC status report generated by the first device can specifically indicate which SDUs or which fragments of the SDU are transmitted successfully or unsuccessfully.

[0084] Fig. 9 A flow chart of a communication method according to an embodiment of the present application is shown. Fig. 9The method 200 shown may be performed by a first device, the first device may be a receiving end, the opposite end device may be a second device, and the second device may be a transmitting end. As an example, the first device is a terminal device and the second device is a network device, or the first device is a network device and the second device is a terminal device. Fig. 9 As shown, method 200 may include some or all of the following steps.

[0085] In step 210, if the first condition is met, the first device regards the unreceived first data packet as received. The first condition is determined based on the second data packet received by the first device, and the first data packet and the second data packet are data packets transmitted in RLC confirmation mode, i.e., RLC AM mode.

[0086] Here, the first device does not actually receive the first data packet, but the first device can determine whether to regard the first data packet as received according to the first condition. For example, if the unreceived first data packet meets the first condition, the first data packet is regarded as received; and / or, if the unreceived first data packet does not meet the first condition, the first data packet is not regarded as received.

[0087] Optionally, in the case where the first data packet is deemed to have been received, the first device may not trigger an RLC status report; or, the first device triggers an RLC status report but the RLC status report does not indicate that the first data packet has not been received.

[0088] Specifically, before the first data packet is deemed to have been received, the reassembly timer associated with the first data packet has not timed out. Thus, when the first data packet is deemed to have been received, the reassembly timer is stopped, and therefore, an RLC status report is not triggered due to the timeout of the reassembly timer. When the first data packet is deemed to have been received, if an RLC status report is triggered for other reasons, since the first data packet has been deemed to have been received, the RLC status report will not indicate that the first data packet has not been received.

[0089] In addition, there is another situation that before the first data packet is deemed to have been received, if the RLC status report is triggered due to the timeout of the reassembly timer or due to other reasons, and the RLC status report includes information indicating that the first data packet has not been received, the first device can cancel the RLC status report and re-trigger the RLC status report according to the updated status parameter, and the re-triggered RLC status report does not indicate that the first data packet has not been received. Here, triggering the RLC status report does not indicate that the RLC status report has been sent to the second device. Therefore, before the RLC status report is sent to the second device, the first device can cancel the RLC status report and regenerate the RLC status report.

[0090] Optionally, if the first device has triggered an RLC status report and has sent an RLC status report, and the RLC status report that has been sent indicates that the first data packet has not been received, in this case, the first device may trigger an RLC status report again after considering the first data packet to have been received, so as to indicate to the second device that the first data packet has been received. The second sent RLC status report shall prevail.

[0091] In the above-mentioned situations, the second device will not receive the indication sent by the first device that the first data packet was not successfully transmitted, and therefore will not trigger the retransmission of the first data packet, which is beneficial to reducing latency and saving transmission resources, and the first device will not initiate uplink scheduling requests (scheduling request, SR), buffer status reports (buffer status report, BSR) and other operations for the RLC status report, thereby simplifying the process of the first device.

[0092] In some implementations, the first condition is determined based on first information, and the first information is associated with the second data packet. For example, the first information includes time-related information and / or sequence number information of the second data packet.

[0093] Optionally, the time-related information of the second data packet may include one or more of the following: the receiving time of the second data packet; the sending time of the second data packet; and the timestamp in the real-time transport protocol (RTP) header of the second data packet.

[0094] Among them, the reception time of the second data packet is the time when the first device receives the second data packet; the timestamp in the RTP header of the second data packet may refer to the sampling time or generation time of the second data packet, and the RTP layer is a higher protocol layer located above the RRC layer and the IP layer; the sending time of the second data packet is the time when the second device sends the second data packet.

[0095] Since the air interface transmission of the data packet requires time, the sending time of the second data packet is different from the receiving time of the second data packet, and the sending time of the second data packet and the receiving time of the second data packet may differ by at least the air interface transmission duration. For example, the first device may determine the sending time of the second data packet according to the sending time of the second data packet and the air interface transmission duration, and the second device may also determine the receiving time of the second data packet according to the sending time of the second data packet and the air interface transmission duration.

[0096] The present application does not limit the type of time-related information of the second data packet. For example, the type of time-related information of the second data packet may include one or more of the following: absolute time; system frame number (SFN) of the current cell; time slot number; symbol.

[0097] The first device may determine which unreceived data packets are to be regarded as received based on the time-related information of the second data packet. For example, the time-related information of the second data packet is used to determine the waiting time of the first data packet, and if the first data packet is still not received after the waiting time, the first data packet is regarded as received. In other words, the first condition includes that the data packet is still not received after the waiting time, or is not received before the waiting time.

[0098] The first device may also determine which unreceived data packets are considered received based on the sequence number of the second data packet. For example, if the difference between the sequence number of the first data packet and the sequence number of the second data packet is less than a preset value, the first data packet is considered received. In other words, the first condition includes that the difference between the sequence number of the data packet and the sequence number of the second data packet is less than the preset value.

[0099] The embodiment of the present application does not limit the method for obtaining the first information. For example, the first information may be obtained through one or more of the following methods: pre-agreed; determined by the first device; sent by the second device.

[0100] If the first information is sent through the second device, optionally, the first information can be carried in one or more of the following: PDCP packet header; RLC packet header; MAC packet header; PDCP control signaling (PDCP control PDU); RLC control signaling (RLCcontrol PDU); MAC CE.

[0101] In combination with Embodiment 1 and Embodiment 2, the following describes in detail how the first device determines, using the first information, whether to regard a first data packet that has not been received as received.

[0102] Example 1

[0103] In embodiment 1, the second data packet and the first data packet are located in the same receiving window.

[0104] In some implementations, the second data packet may include one or more of the following: the data packet with the highest sequence number among the data packets received in the receiving window; the last received data packet among the data packets received in the receiving window; the data packet with the lowest sequence number among the data packets received in the receiving window; and the earliest received data packet among the data packets received in the receiving window.

[0105] In some implementations, the first information includes time-related information of the second data packet, and the time-related information of the second data packet is used to determine the first moment. If the first data packet is not received after the first moment, or if the first data packet is not received before the first moment, the first data packet is deemed to have been received. That is, the first condition includes not being received before the first moment or not being received after the first moment.

[0106] The first device may determine the first time based on the time-related information of the second data packet, and further determine which unreceived data packets can be regarded as received according to the first time. For example, if the current time is already the first time and the first device still has not received the first data packet, it will give up waiting for the first data packet and regard the first data packet as received.

[0107] In some implementations, the first moment may be a first preset time length after the moment indicated by the time-related information of the second data packet. For example, if the time-related information of the second data packet includes the time of receiving the second data packet or a timestamp in the RTP header, the first moment may be a first preset time length after the time of receiving the second data packet or the timestamp. The first preset time length may be pre-agreed or sent by the second device.

[0108] In some implementations, the first data packet is deemed to have been received if the difference between the sequence number of the first data packet and the sequence number of the second data packet is less than a first preset value. The first preset value may be pre-agreed or sent by the second device. The first preset value is, for example, a positive integer. That is, the first condition includes that the difference between the sequence number of the data packet and the sequence number of the second data packet is less than the first preset value.

[0109] The following describes possible positions at the first moment by way of example.

[0110] For example, among the data packets received in the current receiving window, the data packet with the highest sequence number is the second data packet, then the first device can determine whether it needs to wait for data packets that have not been received before the second data packet, such as the first data packet, based on the reception time of the second data packet. Specifically, if the reception time of the second data packet is T1, and the first preset time length is assumed to be T1', then when the current time reaches T1+T1', the first device determines that it does not need to wait for the first data packet anymore, and regards the first data packet as having been received.

[0111] For another example, among the data packets received in the current receiving window, the data packet with the highest sequence number is the second data packet, then the first device can determine whether it needs to wait for a data packet that has not been received before the second data packet, such as the first data packet, based on the timestamp in the RTP header of the second data packet. Specifically, if the timestamp in the RTP header of the second data packet is T2, and the first preset duration is assumed to be T2', then when the current time reaches T2+T2', the first device determines that it does not need to wait for the first data packet any longer, and regards the first data packet as having been received.

[0112] For another example, among the data packets received in the current receiving window, the last received data packet is the second data packet, then the first device can determine whether it needs to wait for data packets that have not been received before the second data packet, such as the first data packet, based on the reception time of the second data packet. Specifically, if the reception time of the second data packet is T3, and the first preset time length is assumed to be T3', then when the current time reaches T3+T3', the first device determines that it does not need to wait for the first data packet any longer, and regards the first data packet as having been received.

[0113] For another example, among the data packets received in the current receiving window, the last received data packet is the second data packet, then the first device can determine whether it needs to wait for data packets that have not been received before the second data packet, such as the first data packet, based on the timestamp in the RTP header of the second data packet. Specifically, if the timestamp in the RTP header of the second data packet is T4, and the first preset duration is assumed to be T4', then when the current time reaches T4+T4', the first device determines that it does not need to wait for the first data packet any longer, and regards the first data packet as having been received.

[0114] It should be noted that the data packet with the highest sequence number may be different from the last received data packet. The data packets sent by the second device in sequence may be received by the first device in a different order due to HARQ retransmission or other reasons. Figure 7 For example, a data packet with sequence number SN=5 may be received before a data packet with sequence number SN=1.

[0115] For another example, among the data packets received in the current receiving window, the data packet with the lowest sequence number is the second data packet, then the first device can determine whether it needs to wait for other data packets that have not been received in the current receiving window, such as all or part of the data packets in the receiving window, including the first data packet, based on the receiving time of the second data packet. Specifically, if the receiving time of the second data packet is T5, and the first preset time length is assumed to be T5', then when the current time reaches T5+T5', the first device determines that it does not need to wait for all the data packets in the receiving window, or determines that it does not need to wait for the data packets that have not been received within the range of [T5, T5+T5'] from T5 to T5+T5' in the receiving window, and regards these data packets as received.

[0116] For another example, among the data packets received in the current receiving window, the data packet with the lowest sequence number is the second data packet, then the first device can determine whether it needs to wait for other data packets that have not been received in the current receiving window, such as all or part of the data packets in the receiving window, including the first data packet, based on the timestamp in the RTP header of the second data packet. Specifically, if the timestamp in the RTP header of the second data packet is T6, and the first preset duration is assumed to be T6', then when the current moment reaches T6+T6', the first device determines that it does not need to wait for all the data packets in the receiving window, or determines that it does not need to wait for the data packets that have not been received within the range of [T6, T6+T6'] in the receiving window, and regards these data packets as received.

[0117] For another example, among the data packets received in the current receiving window, the earliest received data packet is the second data packet, then the first device can determine whether it needs to wait for other data packets that have not been received in the current receiving window, such as all or part of the data packets in the receiving window, including the first data packet, based on the receiving time of the second data packet. Specifically, if the receiving time of the second data packet is T7, and the first preset time length is assumed to be T7', then when the current time reaches T7+T7', the first device determines that it does not need to wait for all the data packets in the receiving window, or determines that it does not need to wait for the data packets that have not been received within the range of [T7, T7+T7'] in the receiving window, and regards these data packets as received.

[0118] For another example, among the data packets received in the current receiving window, the earliest received data packet is the second data packet, then the first device can determine whether it needs to wait for other data packets that have not been received in the current receiving window, such as all or part of the data packets in the receiving window, including the first data packet, based on the timestamp in the RTP header of the second data packet. Specifically, if the timestamp in the RTP header of the second data packet is T8, and the first preset duration is assumed to be T8', then when the current moment reaches T8+T8', the first device determines that it does not need to wait for all the data packets in the receiving window, or determines that it does not need to wait for the data packets that have not been received within the range of [T8, T8+T8'] in the receiving window, and regards these data packets as received.

[0119] Similarly, the data packet with the lowest sequence number may be different from the earliest received data packet. The data packets sent by the second device in sequence may be received by the first device in a different order due to HARQ retransmission or other reasons. For example, the data packet with sequence number SN=0 may be received after the data packet with sequence number SN=1.

[0120] It can be understood that the first data packet and the second data packet are located in the same receiving window; or, the first data packet and the second data packet are located in a predetermined time period of the same receiving window, the starting time of the predetermined time period is determined based on the time-related information of the second data packet, for example, it can be the receiving time of the second data packet or the time corresponding to the timestamp in the RTP packet header, and the end time of the predetermined time period can be the above-mentioned first time. For example, the predetermined time period can be the above-mentioned [T5, T5+T5'], [T6, T6+T6'], [T7, T7+T7'] or [T8, T8+T8'].

[0121] As another example, if the second data packet is the earliest received data packet or the data packet with the smallest sequence number in the current receiving window, the first device may also consider that it is not necessary to wait for data packets with M1 sequence numbers after the sequence number of the second data packet; or, if the second data packet is the latest received data packet or the data packet with the largest sequence number in the current receiving window, the first device may also consider that it is not necessary to wait for data packets with M2 sequence numbers before the sequence number of the second data packet. Among them, M1 and M2 may be pre-agreed or sent by the second device.

[0122] Example 2

[0123] In embodiment 2, the first data packet and the second data packet belong to the same data packet cluster. For example, the second data packet is the first data packet in the data packet cluster.

[0124] The first data packet in the data packet cluster may be determined by the first device or indicated by the second device. For example, the sequence number of the second data packet may be the data packet with the smallest sequence number in the data packet cluster received by the first device; or, the sequence number of the second data packet may be indicated by the second device.

[0125] Specifically, if the first data packet in the data packet cluster is determined by the first device, the first device can use the data packet with the smallest sequence number in the current data packet cluster it receives as the first data packet cluster it receives, but the data packet is not necessarily the first data packet in the data packet cluster sent by the second device. As an example, the data packet cluster includes 50 data packets from SN=0 to SN=49, and the first data packet in the data packet cluster is a data packet with SN=0. Assuming that the smallest sequence number among the data packets received by the first device is SN=1, and the data packet with SN=0 has not been received due to HARQ and other reasons, the first device will use the data packet with SN=1 as the first data packet in the current data packet cluster. For the first device, the data packet cluster includes 50 data packets from SN=1 to SN=50. However, since the RLC retransmission of the second device is enhanced in the Release 19 version of NR, the sender will retransmit the data packet faster, so the probability of this happening is low.

[0126] If the information of the first data packet in the data packet cluster is sent by the second device, the second device can send the sequence number of the first data packet in the data packet cluster to the first device. As an example, the data packet cluster includes 50 data packets from SN=0 to SN=49, then the second device can send SN=0 of the first data packet in the data packet cluster to the first device, and even if the first device first receives the data packet with sequence number SN=1, it will treat the data packet with SN=0 as the first data packet in the data packet cluster when it receives the data packet with SN=0.

[0127] In some implementations, the first information includes time-related information of the second data packet, and the time-related information of the second data packet is used to determine the second moment. If the first data packet is still not received after the second moment, or if the first data packet is not received before the first moment, the first data packet is deemed to have been received. That is, the first condition includes not being received before the second moment or not being received after the first moment.

[0128] The first device may determine the second time based on the time-related information of the second data packet, and further determine which unreceived data packets can be regarded as received according to the second time. For example, if the current time is the second time and the first device still has not received the first data packet, it will give up waiting for the first data packet and regard the first data packet as received.

[0129] In some implementations, the second moment may be a second preset time length after the moment indicated by the time-related information of the second data packet. For example, if the time-related information of the second data packet includes the receiving moment or sending moment of the second data packet, the second moment may be a second preset time length after the receiving moment or sending moment of the second data packet.

[0130] Several methods for determining the second preset duration are provided below.

[0131] Method 1

[0132] In some implementations, the first information further includes time-related information of the data packet cluster, and the second preset duration can be determined based on the time-related information of the data packet cluster.

[0133] Optionally, the time-related information of the data packet cluster includes one or more of the following: an air interface transmission delay budget of the data packet cluster; timeout information of the data packet cluster; and a clearing time of the data packet cluster indicated by the second device.

[0134] The air interface transmission delay budget of the data packet cluster is related to the time when the data packet cluster arrives at the second device. The time when the data packet cluster arrives at the air interface of the second device may have clock jitter. If the data packet cluster arrives at the air interface of the second device late, the air interface transmission delay budget is short. If the data packet cluster arrives at the air interface of the second device early, the air interface transmission delay budget is long.

[0135] The timeout information of a data packet cluster may, for example, include one or more of the following: the timeout moment of the data packet cluster; the timeout moment of the first data packet in the data packet cluster; the timeout moment of the last data packet in the data packet cluster; the timeout moment of the earliest timed-out data packet in the data packet cluster; the timeout moment of the latest timed-out data packet in the data packet cluster.

[0136] Usually, the timeout moments of each data packet in a data packet cluster may be different, because the importance of each data packet in the data packet cluster is different, and the corresponding transmission delay budget may be different. The transmission delay budget of the data packet with high importance is large, and the transmission delay budget of the data packet with low importance is small, so the timeout moment of each data packet is not necessarily always increasing. If it is assumed that the arrival time of each data packet in the data packet is the same, for example, the arrival time of each data packet is forced to be aligned, then the timeout moment of each data packet is the same, that is, the timeout moment of the above-mentioned data packet cluster.

[0137] The clearing time of the data packet cluster indicated by the second device may be a time determined by the second device that does not need to continue waiting for the first data packet. If the current time has reached the clearing time and the first device has not received the first data packet, the first device does not need to continue waiting for the first data packet and regards the first data packet as received.

[0138] The embodiment of the present application does not limit the type of time-related information of the data packet cluster. For example, the type of time-related information of the data packet cluster includes one or more of the following: absolute time; SFN of the current cell; time slot number; symbol.

[0139] In some implementations, the second preset duration can be recorded by a timer of the first device, and the start time of the timer is the time indicated by the time-related information of the second data packet, such as the reception time or the transmission time of the second data packet. Here, the reception time or the transmission time of the second data packet, that is, the reception time or the transmission time of the first data packet in the current data packet cluster, can be the reception time or the transmission time of the data packet with the smallest sequence number in the data packet cluster. As described above, the data packet with the smallest sequence number in the data packet cluster can be determined by the first device or sent by the second device.

[0140] For example, the first data packet in the data packet cluster is the second data packet, and the first information sent by the second device to the first device includes time-related information of the data packet cluster, such as the air interface transmission delay budget of the data packet cluster, the timeout information of the data packet cluster, and the clearing time of the data packet cluster. If the receiving time or sending time of the second data packet is T9, and the air interface transmission delay budget, the timeout time of the data packet cluster, or the clearing time of the data packet cluster is equal to the second preset duration T9', then when the current time reaches T9+T9', the first device determines that it does not need to wait for all or part of the data packets that have not been received in the data packet cluster, including the first data packet, and regards these data packets as received. The partial data packets mentioned here may be, for example, data packets with a lower level of importance.

[0141] For another example, the first data packet in the data packet cluster is the second data packet, and the terminal device starts the timer when receiving the second data packet. If the receiving time or sending time of the second data packet is T10, and the second preset duration is T10', the first device starts the timer at T10, and when the time recorded by the timer reaches the second preset duration, the first device has not received the first data packet, then there is no need to wait for all or part of the data packets that have not been received in the data packet cluster, including the first data packet, and these data packets are regarded as received. The partial data packets mentioned here can be, for example, data packets with a lower level of importance.

[0142] Furthermore, in some implementations, the first information may also include the number of data packets in the data packet cluster and / or the amount of data in the data packet cluster, and the number of data packets in the data packet cluster and the amount of data in the data packet cluster are used to determine the data packets belonging to the data packet cluster, that is, to determine which data packets belong to the data packet cluster. For example, the first device may determine which data packets are included in the data packet cluster based on the sequence number of the first data packet in the data packet cluster, i.e., the second data packet, and the number of data packets in the data packet cluster. Assuming that the sequence number of the second data packet is SN=0, and there are 50 data packets in the data packet cluster, then the data packet cluster includes data packets from SN=0 to SN=49. In this way, when the current moment reaches the second moment, the unreceived data packets, such as the first data packet, belonging to the same data packet cluster as the second data packet may no longer be waited for and may be deemed to have been received.

[0143] Method 2

[0144] In some implementations, the first information also includes the number of data packets in the data packet cluster, and the second preset time length is the time length that the first device takes to receive data packets of the same number from the second data packet. For example, if the sequence number of the second data packet is SN=0, and there are 50 data packets in the data packet cluster, then the second preset time length is the time length that the second device takes to receive data packets from SN=0 to SN=49.

[0145] The first device can determine the second time based on the reception time or transmission time of the second data packet and the number of data packets in the data packet cluster. Then determine which unreceived data packets can be regarded as received according to the second time. For example, the second time is the time when the first device receives the data packets with the number of data packets since receiving the second data packet. If the current time reaches the second time, and the first device still has not received the first data packet in the data packet cluster, it will give up waiting for the first data packet and regard the first data packet as received.

[0146] In some implementations, the number of data packets carried in the first information can be recorded by a counter of the first device, and the start time of the counter is the reception time or the sending time of the second data packet. Here, the reception time or the sending time of the second data packet, that is, the reception time or the sending time of the first data packet in the current data packet cluster, can be the reception time or the sending time of the data packet with the smallest sequence number in the data packet cluster. As described above, the data packet with the smallest sequence number in the data packet cluster can be determined by the first device or sent by the second device.

[0147] For example, the first data packet in the data packet cluster is the second data packet, and the first information sent by the second device to the first device includes the number of data packets in the data packet cluster. If the receiving time or sending time of the second data packet is T11, the number of data packets in the data packet cluster is N, and the time when the first device receives N data packets from time T11 is T11', then when the current time reaches T11+T11', the first device determines that it does not need to wait for all or part of the data packets that have not been received in the data packet cluster, including the first data packet, and regards these data packets as received. The partial data packets mentioned here can be, for example, data packets with a lower level of importance.

[0148] For another example, the first data packet in the data packet cluster is the second data packet, and the terminal device starts the counter when receiving the second data packet. If the receiving time or sending time of the second data packet is T12, the first device starts the timer at T12, the number of data packets in the data packet cluster is N, and the time when the value recorded by the counter reaches N is T12', then when the current time reaches T12+T12', the first device has not received the first data packet, and there is no need to wait for all or part of the data packets that have not been received in the data packet cluster, including the first data packet, and these data packets are regarded as received. The partial data packets mentioned here can be, for example, data packets with a lower importance level.

[0149] In Embodiment 2, in other implementations, the first information includes information of a sequence number of the second data packet, wherein the difference between the sequence number of the first data packet and the sequence number of the second data packet is less than a second preset value, and the first data packet is deemed to have been received. The second preset value may be agreed in advance or sent by the second device. The second preset value is, for example, a positive integer.

[0150] That is, the first condition includes that the difference between the sequence number of the data packet and the sequence number of the second data packet is less than a second preset value. The first device may regard the unreceived data packets among the data packets corresponding to the sequence numbers whose difference between the sequence number of the data packet and the sequence number of the second data packet is less than the second preset value as received.

[0151] The above describes how the first device determines whether to regard an unreceived data packet as received. The following describes how the first device determines whether to perform this operation.

[0152] In some implementations, the communication method of the embodiment of the present application may also include, the first device determining whether to perform a first operation based on the second information, the first operation for example including the aforementioned determination whether to regard an unreceived data packet as received.

[0153] Optionally, the second information may include indication information for indicating whether to perform the first operation, that is, the second information is used to indicate whether the first device performs the first operation; or, the second information may include information associated with the first operation.

[0154] The first operation may be associated with one or more of the following, for example: a logical channel (logic channel, LCH), a logical channel group (logic channel group, LCG), a service type, and information of a terminal device.

[0155] If the second information indicates a specific logical channel, the first device only performs the first operation on the data packets transmitted on the logical channel; if the second information indicates a specific logical channel group, the first device only performs the first operation on the data packets transmitted on the logical channel group; if the second information indicates a specific service type such as XR service, the first device only performs the first operation on the data packets of the service type such as XR service; if the second information indicates certain terminal devices or a certain type of terminal devices, then if the first device is the terminal device indicated by the second information, it performs the first operation.

[0156] Here, the information of the terminal device may include, for example, one or more of the following: a protocol version supported by the terminal device; device information of the terminal device. Taking the protocol version supported by the terminal device as an example, a terminal device with a higher version, such as a terminal device with a version of Release 19 or higher, may perform the first operation, while a terminal device with a lower version, such as a terminal device with a version of Release 18 or lower, may not perform the first operation.

[0157] The second information may include one or more information associated with the first operation. For example, if the second information includes a logical channel group and a service type such as an XR service, the first device may perform the first operation on a data packet on a logical channel in the logical channel group used to transmit the XR service; for another example, if the second information includes information about a terminal device and information about a logical channel, then when the first device is the terminal device indicated by the second information, the first device performs the first operation on a data packet on the logical channel indicated by the second information.

[0158] Further, optionally, the second information may also indicate the method used to perform the first operation, that is, which of the aforementioned methods is used by the first device to determine whether to regard the unreceived data packet as received. Of course, the first device may also select one of the methods to determine whether to regard the unreceived data packet as received.

[0159] Optionally, the second information may be obtained in one or more of the following ways: pre-agreed; determined by the first device; sent by the second device.

[0160] If the second information is sent through the second device, the second information may be carried by one or more of the following, for example: RRC signaling; RLC control signaling.

[0161] In some implementations, the first device may also send third information to the second device, and the third information is used to indicate whether the first device has the ability to perform the first operation. The capability may be associated with one or more of the following information: frequency range (FR), logical channel, logical channel group, and terminal device information. Optionally, the third information may also be provided by other devices. For example, if the first device is a terminal device and the second device is a network device, the third information may also be provided by the core network to the second device.

[0162] Based on the above description, if the first device determines to regard the unreceived first data packet as received, the first device needs to update the status parameters it maintains, such as the aforementioned first parameter (RX_Next), second parameter (RX_Highest_Status), third parameter (RX_Next_Highest), and fourth parameter (RX_Next_Status_Trigger).

[0163] In some implementations, when the unreceived first data packet is deemed to have been received, the state parameter maintained by the first device is updated based on the state of receiving data packets with the second sequence number and sequence numbers before the second sequence number.

[0164] The second sequence number may be defined in the following two ways: when the first data packet is deemed to have been received, the second sequence number is the sequence number of the first data packet; or, when multiple data packets that have not been received are deemed to have been received, the second sequence number is the sequence number of the last data packet in the multiple data packets, the multiple data packets including the first data packet. In other implementations, the second sequence number may also be indicated by the second device.

[0165] In some implementations, the state parameters may be updated in one or more of the following ways: the first parameter is updated to the sequence number of the next unreceived data packet after the second sequence number; the second parameter is updated to the sequence number of the next unreceived data packet after the next received data packet after the first parameter; the sequence number indicated by the third parameter is updated to the sequence number indicated by the third parameter plus 1 if it is before the second sequence number, or remains unchanged if it is after the second sequence number; the fourth parameter is updated to the sequence number of the next segment of unreceived data packets after the second sequence number. The next segment of unreceived data packets refers to one or more data packets with consecutive sequence numbers that are not received, for example Figure 5The data packets of SN=6 and SN=7 shown in can be called a segment of data packets that have not been received, and the data packets of SN=1, SN=2, SN=3 and SN=4 can be called a segment of data packets that have not been received.

[0166] based on Figure 5 In the case shown, if during the operation of the reassembly timer, the first device does not wait for the data packets of SN=1, SN=2, SN=3 and SN=4, and the first device determines that it does not need to wait for the data packets of SN=1, SN=2, SN=3 and SN=4, the second sequence number is SN=4. The first device regards the data packets of SN=1, SN=2, SN=3 and SN=4 as received. At this time, the data packets of SN=1, SN=2, SN=3 and SN=4 are regarded as received, and RX_Next is updated to SN=6. RX_Next_Highest is SN=9, which is located after the second sequence number SN=4 and therefore remains unchanged. It is determined that RX_Next_Status_Trigger=RX_Next, and the reassembly timer is stopped. It is determined that RX_Next_Highest>RX_Next+1, and the reassembly timer is started again to wait for the data packets of SN=6 and SN=7, and RX_Next_Status_Trigger is set to SN=9. If the first device determines that it does not need to wait for the data packets of SN=6 and SN=7, RX_Highest_Status is updated to SN=9; if the first device still needs to wait for the data packets of SN=6 and SN=7, RX_Highest_Status is updated to SN=6.

[0167] Optionally, when the first device updates the state parameter maintained by the receiving end, the first device may send fourth information to the second device, and the fourth information is used for the second device to update the state parameter maintained by the sending end. For example, the fourth information may indicate whether the first device has updated the state parameter, or the fourth information includes one or more of the updated state parameters.

[0168] Fig.10 A flow chart of a communication method according to another embodiment of the present application is shown. Fig.10 The method 300 shown may be performed by a second device, the second device may be a receiving end, the opposite device may be a first device, and the first device may be a receiving end. As an example, the first device is a terminal device and the second device is a network device, or the first device is a network device and the second device is a terminal device. Fig.10 As shown, method 300 may include some or all of the following steps.

[0169] In step 310, the second device sends first information to the first device, wherein the first information is used to determine whether to regard a first data packet that has not been received as received, and the first information is associated with a second data packet received by the first device, and the first data packet and the second data packet are data packets transmitted in RLC confirmation mode.

[0170] It can be understood that the content included in the first information described in method 300 may be all the content that can be provided by the second device among the content that may be included in the first information described in method 200.

[0171] In some implementations, the first data packet is deemed to have been received, wherein the first device does not trigger an RLC status report; or, the first device triggers an RLC status report and the RLC status report does not indicate that the first data packet was not received.

[0172] In some implementations, the first data packet and the second data packet belong to the same data packet cluster.

[0173] In some implementations, the second data packet is the first data packet in the data packet cluster.

[0174] In some implementations, the second data packet is a data packet with the smallest sequence number in a data packet cluster received by the first device; or, the sequence number of the second data packet is indicated by the second device.

[0175] In some implementations, the first information is used to determine a second time instant, wherein if the first data packet is still not received after the second time instant, the first data packet is deemed to have been received.

[0176] In some implementations, the first information is used to determine a second preset duration, and the second moment is the second preset duration after a moment of receiving or sending the second data packet.

[0177] In some implementations, the first information includes time-related information of the data packet cluster, and the time-related information of the data packet cluster is used to determine the second preset duration.

[0178] In some implementations, the time-related information of the data packet cluster includes one or more of the following: air interface transmission delay budget of the data packet cluster; timeout information of the data packet cluster; and clearing time of the data packet cluster.

[0179] In some implementations, the timeout information of a data packet cluster includes one or more of the following: the timeout moment of the data packet cluster; the timeout moment of the first data packet in the data packet cluster; the timeout moment of the last data packet in the data packet cluster; the timeout moment of the earliest timed-out data packet in the data packet cluster; the timeout moment of the latest timed-out data packet in the data packet cluster.

[0180] In some implementations, the second preset duration is recorded by a timer of the first device, and the start time of the timer is the reception time or the sending time of the second data packet.

[0181] In some implementations, the type of time-related information of the data packet cluster includes one or more of the following: absolute time; system frame number; time slot number; symbol.

[0182] In some implementations, the first information also includes the number of data packets in the data packet cluster and / or the amount of data in the data packet cluster, and the number of data packets in the data packet cluster or the amount of data in the data packet cluster is used to determine the data packets belonging to the data packet cluster.

[0183] In some implementations, the first information includes the number of data packets in the data packet cluster, and the second preset time duration is the time duration for the first device to receive data packets having the same number of data packets from the second data packet.

[0184] In some implementations, the number of data packets is recorded by a counter of the first device, and the counter is started at the time when the second data packet is received or sent.

[0185] In some implementations, the first information includes information about the sequence number of the second data packet, and if a difference between the sequence number of the first data packet and the sequence number of the second data packet is less than a second preset value, the first data packet is deemed to have been received.

[0186] In some implementations, the first information is carried in one or more of the following: PDCP packet header; RLC packet header; MAC packet header; PDCP control signaling; RLC control signaling; MAC CE.

[0187] In some implementations, the second device sends second information to the first device, where the second information is used to determine whether to perform a first operation, where the first operation includes determining whether to regard an unreceived data packet as received.

[0188] In some implementations, the second information includes indication information for indicating whether to perform the first operation; or, the second information includes information associated with the first operation.

[0189] In some implementations, the first operation is associated with one or more of the following: a logical channel, a logical channel group, a service type, and information of a terminal device.

[0190] In some implementations, the information of the terminal device includes one or more of the following: a protocol version supported by the terminal device; and device information of the terminal device.

[0191] In some implementations, the second information is carried in one or more of the following: RRC signaling; RLC control signaling.

[0192] In some implementations, the method 300 may further include the second device receiving third information sent by the first device, where the third information is used to indicate whether the first device has the ability to perform the first operation.

[0193] In some implementations, the capability is associated with one or more of the following information: frequency band, logical channel, logical channel group, and terminal device information.

[0194] In some implementations, when the first data packet is deemed to have been received, the state parameter of the data packet maintained by the first device is updated based on the state of the data packets received with the second sequence number and the sequence numbers before it.

[0195] In some implementations, when a first data packet is deemed to have been received, the second sequence number is the sequence number of the first data packet; or, when multiple data packets that have not been received are deemed to have been received, the second sequence number is the sequence number of the last data packet in the multiple data packets, and the multiple data packets include the first data packet.

[0196] In some implementations, the status parameter includes one or more of the following: a first parameter, used to indicate the next sequence number after the last completely correctly received data packet; a second parameter, used to indicate the sequence number updated when the reassembly timer times out; a third parameter, used to indicate the next sequence number after the sequence number of the received data packet with the highest sequence number; a fourth parameter, used to indicate the sequence number of the next incorrectly received data packet after the sequence number of the data packet that triggered the reassembly timer.

[0197] In some implementations, the first parameter is updated to the sequence number of the next unreceived data packet after the second sequence number; the second parameter is updated to the sequence number of the next unreceived data packet after the next received data packet after the first parameter; the sequence number indicated by the third parameter is updated to the sequence number indicated by the third parameter plus 1 if it is before the second sequence number, or remains unchanged if it is after the second sequence number; the fourth parameter is updated to the sequence number of the next unreceived data packet after the second sequence number.

[0198] In some implementations, the method 300 may further include: the second device receiving an RLC status report sent by the first device, where the RLC status report is an RLC status report triggered by the first device based on an updated status parameter.

[0199] In some implementations, the first data packet includes an SDU and / or a fragment of an SDU.

[0200] Understandably, Fig.10For specific details of various implementations of the method 300 shown, reference may be made to the related descriptions of the method 200 described above. For the sake of brevity, they will not be described in detail here.

[0201] Combined with the above Figures 1 to 10 , describes the method embodiment of the present application in detail, and the following is combined with Figures 11 to 13 , describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0202] Fig.11 It is a schematic diagram of a communication device according to an embodiment of the present application. Fig.11 The communication device 400 shown may be the first device described above, and the communication device 400 includes a processing unit 410. Optionally, the communication device 400 also includes a transceiver unit 420. The processing unit 410 is used to determine whether to regard an unreceived first data packet as received based on first information, wherein the first information is associated with a second data packet received by the first device, and the first data packet and the second data packet are data packets transmitted in an RLC confirmation mode.

[0203] In some implementations, the first data packet is deemed to have been received, wherein the first device does not trigger an RLC status report; or, the first device triggers the RLC status report and the RLC status report does not indicate that the first data packet has not been received.

[0204] In some implementations, the first information includes time-related information and / or sequence number information of the second data packet.

[0205] In some implementations, the time-related information of the second data packet includes one or more of the following: the time when the second data packet is received; the time when the second data packet is sent; and the timestamp in the RTP header of the second data packet.

[0206] In some implementations, the difference between the time when the second data packet is sent and the time when the second data packet is received is the air interface transmission duration.

[0207] In some implementations, the type of time-related information of the second data packet includes one or more of the following: absolute time; system frame number; time slot number; symbol.

[0208] In some implementations, the first data packet and the second data packet are located in the same receiving window.

[0209] In some implementations, the second data packet includes one or more of the following: the data packet with the highest sequence number among the data packets received in the receiving window; the last received data packet among the data packets received in the receiving window; the data packet with the lowest sequence number among the data packets received in the receiving window; and the earliest received data packet among the data packets received in the receiving window.

[0210] In some implementations, the first information includes time-related information of the second data packet, and the time-related information of the second data packet is used to determine a first moment, wherein if the first data packet is still not received after the first moment, the first data packet is deemed to have been received.

[0211] In some implementations, the time-related information of the second data packet includes the reception time of the second data packet or a timestamp in the RTP packet header, wherein the first time is a first preset time length after the reception time of the second data packet or the timestamp.

[0212] In some implementations, the first information includes information of a sequence number of the second data packet, wherein if a difference between the sequence number of the first data packet and the sequence number of the second data packet is less than a first preset value, the first data packet is deemed to have been received.

[0213] In some implementations, the first data packet and the second data packet belong to the same data packet cluster.

[0214] In some implementations, the second data packet is the first data packet in the data packet cluster.

[0215] In some implementations, the second data packet is a data packet with a smallest sequence number in the data packet cluster received by the first device; or, the sequence number of the second data packet is indicated by the second device.

[0216] In some implementations, the first information includes time-related information of the second data packet, and the time-related information of the second data packet is used to determine a second moment, wherein if the first data packet is still not received after the second moment, the first data packet is deemed to have been received.

[0217] In some implementations, the time-related information of the second data packet includes a receiving time or a sending time of the second data packet, and the second time is a second preset time length after the receiving time or the sending time of the second data packet.

[0218] In some implementations, the first information also includes time-related information of the data packet cluster, and the second preset duration is determined based on the time-related information of the data packet cluster.

[0219] In some implementations, the time-related information of the data packet cluster includes one or more of the following: an air interface transmission delay budget of the data packet cluster; timeout information of the data packet cluster; and a clearing time of the data packet cluster.

[0220] In some implementations, the timeout information of the data packet cluster includes one or more of the following: the timeout moment of the data packet cluster; the timeout moment of the first data packet in the data packet cluster; the timeout moment of the last data packet in the data packet cluster; the timeout moment of the earliest timed-out data packet in the data packet cluster; the timeout moment of the latest timed-out data packet in the data packet cluster.

[0221] In some implementations, the type of time-related information of the data packet cluster includes one or more of the following: absolute time; system frame number; time slot number; symbol.

[0222] In some implementations, the second preset duration is recorded by a timer of the first device, and the start time of the timer is the reception time or the sending time of the second data packet.

[0223] In some implementations, the first information also includes the number of data packets in the data packet cluster and / or the amount of data in the data packet cluster, and the number of data packets in the data packet cluster and the amount of data in the data packet cluster are used to determine the data packets belonging to the data packet cluster.

[0224] In some implementations, the first information also includes the number of data packets in the data packet cluster, and the second preset time duration is the time duration for the first device to receive data packets of the number of data packets starting from the second data packet.

[0225] In some implementations, the number of data packets is recorded by a counter of the first device, and a start time of the counter is a reception time or a sending time of the second data packet.

[0226] In some implementations, the first information includes information about the sequence number of the second data packet, and if a difference between the sequence number of the first data packet and the sequence number of the second data packet is less than a second preset value, the first data packet is deemed to have been received.

[0227] In some implementations, the first information is obtained through one or more of the following methods: pre-agreed; determined by the first device; sent by the second device.

[0228] In some implementations, the first information is carried in one or more of the following: PDCP packet header; RLC packet header; MAC packet header; PDCP control signaling; RLC control signaling; MAC CE.

[0229] In some implementations, the processing unit 410 is further configured to: determine whether to perform a first operation based on the second information, wherein the first operation includes determining whether to regard an unreceived data packet as received.

[0230] In some implementations, the second information includes indication information for indicating whether to perform the first operation; or, the second information includes information associated with the first operation.

[0231] In some implementations, the first operation is associated with one or more of the following: a logical channel, a logical channel group, a service type, and information of a terminal device.

[0232] In some implementations, the information of the terminal device includes one or more of the following: a protocol version supported by the terminal device; and device information of the terminal device.

[0233] In some implementations, the second information is obtained by one or more of the following methods: pre-agreed; determined by the first device; sent by the second device.

[0234] In some implementations, the second information is carried by one or more of the following: RRC signaling; RLC control signaling.

[0235] In some implementations, the transceiver unit 420 is used to send third information to the second device, where the third information is used to indicate whether the first device has the ability to perform the first operation.

[0236] In some implementations, the capability is associated with one or more of the following information: frequency band, logical channel, logical channel group, and terminal device information.

[0237] In some implementations, when the first data packet is deemed to have been received, the state parameter of the data packet maintained by the first device is updated based on the state of the data packets received with the second sequence number and the sequence numbers before it.

[0238] In some implementations, when the first data packet is deemed to have been received, the second sequence number is the sequence number of the first data packet; or, when multiple data packets that have not been received are deemed to have been received, the second sequence number is the sequence number of the last data packet among the multiple data packets, and the multiple data packets include the first data packet.

[0239] In some implementations, the status parameters include one or more of the following: a first parameter, used to indicate the next sequence number after the last completely correctly received data packet; a second parameter, used to indicate the sequence number updated when the reassembly timer times out; a third parameter, used to indicate the next sequence number after the sequence number of the data packet with the highest sequence number received; a fourth parameter, used to indicate the next incorrectly received sequence number after the sequence number of the data packet that triggered the reassembly timer.

[0240] In some implementations, the first parameter is updated to the sequence number of the next unreceived data packet after the second sequence number; the second parameter is updated to the sequence number of the next unreceived data packet after the next received data packet after the first parameter; the sequence number indicated by the third parameter is updated to the sequence number indicated by the third parameter plus 1 if it is before the second sequence number, or remains unchanged if it is after the second sequence number; the fourth parameter is updated to the sequence number of the next unreceived data packet after the second sequence number.

[0241] In some implementations, the processing unit 410 is further used to: when the RLC status report has been triggered and the RLC status report indicates that the first data packet has not been received, cancel the RLC status report and re-trigger the RLC status report based on the updated status parameters.

[0242] In some implementations, the first data packet includes an SDU and / or a fragment of an SDU.

[0243] In some implementations, the first device is a terminal device or a network device.

[0244] It can be understood that the processing unit 410 may be, for example, a processor 610, and the transceiver unit 420 may be, for example, a transceiver 630. In addition, the communication device 400 may further include a memory 620, for details, see Fig.13 .

[0245] Fig.12 It is a schematic diagram of a communication device according to another embodiment of the present application. Fig.12 The communication device 500 shown may be the second device described above, and includes a transceiver unit 510. The transceiver unit 510 is used to send first information to the first device, the first information being used to determine whether to regard an unreceived first data packet as received, the first information being associated with a second data packet received by the first device, and the first data packet and the second data packet being data packets transmitted in an RLC confirmation mode.

[0246] In some implementations, the first data packet is deemed to have been received, wherein the first device does not trigger an RLC status report; or, the first device triggers the RLC status report and the RLC status report does not indicate that the first data packet has not been received.

[0247] In some implementations, the first data packet and the second data packet belong to the same data packet cluster.

[0248] In some implementations, the second data packet is the first data packet in the data packet cluster.

[0249] In some implementations, the second data packet is a data packet with a smallest sequence number in the data packet cluster received by the first device; or, the sequence number of the second data packet is indicated by the second device.

[0250] In some implementations, the first information is used to determine a second time instant, wherein if the first data packet is still not received after the second time instant, the first data packet is deemed to have been received.

[0251] In some implementations, the first information is used to determine a second preset duration, and the second moment is the second preset duration after a moment of receiving or sending the second data packet.

[0252] In some implementations, the first information includes time-related information of the data packet cluster, and the time-related information of the data packet cluster is used to determine the second preset duration.

[0253] In some implementations, the time-related information of the data packet cluster includes one or more of the following: an air interface transmission delay budget of the data packet cluster; timeout information of the data packet cluster; and a clearing time of the data packet cluster.

[0254] In some implementations, the timeout information of the data packet cluster includes one or more of the following: the timeout moment of the data packet cluster; the timeout moment of the first data packet in the data packet cluster; the timeout moment of the last data packet in the data packet cluster; the timeout moment of the earliest timed-out data packet in the data packet cluster; the timeout moment of the latest timed-out data packet in the data packet cluster.

[0255] In some implementations, the second preset duration is recorded by a timer of the first device, and the start time of the timer is the reception time or the sending time of the second data packet.

[0256] In some implementations, the type of time-related information of the data packet cluster includes one or more of the following: absolute time; system frame number; time slot number; symbol.

[0257] In some implementations, the first information also includes the number of packets in the packet cluster and / or the amount of data in the packet cluster, and the number of packets in the packet cluster or the amount of data in the packet cluster is used to determine the packets belonging to the packet cluster.

[0258] In some implementations, the first information includes the number of data packets in the data packet cluster, and the second preset time duration is the time duration for the first device to receive data packets of the number of data packets starting from the second data packet.

[0259] In some implementations, the number of data packets is recorded by a counter of the first device, and a start time of the counter is a reception time or a sending time of the second data packet.

[0260] In some implementations, the first information includes information about the sequence number of the second data packet, and if a difference between the sequence number of the first data packet and the sequence number of the second data packet is less than a second preset value, the first data packet is deemed to have been received.

[0261] In some implementations, the first information is carried in one or more of the following: PDCP packet header; RLC packet header; MAC packet header; PDCP control signaling; RLC control signaling; MAC CE.

[0262] In some implementations, the transceiver unit 510 is further used to: send second information to the first device, the second information is used to determine whether to perform a first operation, the first operation including determining whether to regard an unreceived data packet as received.

[0263] In some implementations, the second information includes indication information for indicating whether to perform the first operation; or, the second information includes information associated with the first operation.

[0264] In some implementations, the first operation is associated with one or more of the following: a logical channel, a logical channel group, a service type, and information of a terminal device.

[0265] In some implementations, the information of the terminal device includes one or more of the following: a protocol version supported by the terminal device; and device information of the terminal device.

[0266] In some implementations, the second information is carried in one or more of the following: radio resource control RRC signaling; RLC control signaling.

[0267] In some implementations, the transceiver unit 510 is further used to: receive third information sent by the first device, where the third information is used to indicate whether the first device has the ability to perform the first operation.

[0268] In some implementations, the capability is associated with one or more of the following information: frequency band, logical channel, logical channel group, and terminal device information.

[0269] In some implementations, when the first data packet is deemed to have been received, the state parameter of the data packet maintained by the first device is updated based on the state of the data packets received with the second sequence number and the sequence numbers before it.

[0270] In some implementations, when the first data packet is deemed to have been received, the second sequence number is the sequence number of the first data packet; or, when multiple data packets that have not been received are deemed to have been received, the second sequence number is the sequence number of the last data packet among the multiple data packets, and the multiple data packets include the first data packet.

[0271] In some implementations, the status parameters include one or more of the following: a first parameter, used to indicate the next sequence number after the last completely correctly received data packet; a second parameter, used to indicate the sequence number updated when the reassembly timer times out; a third parameter, used to indicate the next sequence number after the sequence number of the data packet with the highest sequence number received; a fourth parameter, used to indicate the next incorrectly received sequence number after the sequence number of the data packet that triggered the reassembly timer.

[0272] In some implementations, the first parameter is updated to the sequence number of the next unreceived data packet after the second sequence number; the second parameter is updated to the sequence number of the next unreceived data packet after the next received data packet after the first parameter; the sequence number indicated by the third parameter is updated to the sequence number indicated by the third parameter plus 1 if it is before the second sequence number, or remains unchanged if it is after the second sequence number; the fourth parameter is updated to the sequence number of the next unreceived data packet after the second sequence number.

[0273] In some implementations, the transceiver unit 510 is further used to: receive an RLC status report sent by the first device, where the RLC status report is an RLC status report triggered by the first device based on the updated status parameter.

[0274] In some implementations, the first data packet includes an SDU and / or a fragment of an SDU.

[0275] In some implementations, the second device is a terminal device or a network device.

[0276] It can be understood that the transceiver unit 510 can be, for example, a transceiver 630. In addition, optionally, the communication device 500 can also include a processor 610 and a memory 620, for details, see Fig.13 .

[0277] Fig.13 It is a schematic structural diagram of a device for communication according to an embodiment of the present application. Fig.13 The dotted line in the figure indicates that the unit or module is optional. The device can be used to implement the method described in the above method embodiment. The device is, for example, a chip, a terminal device or a network device.

[0278] like Fig.13 As shown, the device 600 may include one or more processors 610. The processor 610 may support the device 600 to implement the method described in the above method embodiment. The processor 610 may be a general-purpose processor or a special-purpose processor. For example, the processor 610 may be a central processing unit (CPU). Alternatively, the processor 610 may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0279] The apparatus 600 may further include one or more memories 620. The memory 620 stores a program, which can be executed by the processor 610, so that the processor 610 executes the method described in the foregoing method embodiment. The memory 620 may be independent of the processor 610 or integrated in the processor 610.

[0280] The apparatus 600 may further include a transceiver 630. The processor 610 may communicate with other devices or chips through the transceiver 630. For example, the processor 610 may transmit and receive data with other devices or chips through the transceiver 630.

[0281] The embodiment of the present application also provides a communication system. The system includes the above-mentioned first device and second device. In some implementations, the system also includes other devices that interact with the first device or the second device.

[0282] The embodiment of the present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the embodiment of the present application, such as the first device or the second device, and the program enables the computer to execute the method performed by the first device or the second device in each embodiment of the present application.

[0283] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in the embodiment of the present application, such as the first device or the second device, and the program enables the computer to execute the method performed by the first device or the second device in each embodiment of the present application.

[0284] The embodiment of the present application also provides a computer program. The computer program can be applied to the communication device provided in the embodiment of the present application, such as the first device or the second device, and the computer program enables the computer to execute the method performed by the first device or the second device in each embodiment of the present application.

[0285] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions.

[0286] In the embodiments of the present application, the "indication" mentioned can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0287] In the embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0288] In the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship of indication and being indicated, configuration and being configured, etc.

[0289] In the embodiments of the present application, "pre-definition" or "pre-configuration" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device, such as a terminal device or a network device, and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0290] In the embodiments of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0291] In the embodiments of the present application, the term "include" may refer to direct inclusion or indirect inclusion. Optionally, the term "include" mentioned in the embodiments of the present application may be replaced with "indicate" or "used to determine". For example, "A includes B" may be replaced with "A indicates B" or "A is used to determine B".

[0292] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean 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 the present application.

[0293] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0294] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0295] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0296] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless such as infrared, wireless, microwave, etc., to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium such as a floppy disk, a hard disk, a magnetic tape, etc., or an optical medium such as a digital versatile disk (DVD) or a semiconductor medium such as a solid state disk (SSD), etc.

[0297] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, It is characterized in that include: When a first condition is met, the first device regards a first data packet that has not been received as received, and the first condition is determined based on a second data packet received by the first device, and the first data packet and the second data packet are data packets transmitted in a radio link control RLC confirmation mode.

2. The communication method according to claim 1, It is characterized in that The first data packet is deemed to have been received, wherein the first device does not trigger an RLC status report; or, the first device triggers the RLC status report and the RLC status report does not indicate that the first data packet is not received.

3. The communication method according to claim 1 or 2, It is characterized in that The first condition is determined based on first information, where the first information includes time-related information and / or sequence number information of the second data packet.

4. The communication method according to claim 3, It is characterized in that The time related information of the second data packet includes one or more of the following: a time at which the second data packet is received; The sending time of the second data packet; The timestamp in the Real-time Transport Protocol (RTP) packet header of the second data packet.

5. The communication method according to claim 4, It is characterized in that The difference between the sending time of the second data packet and the receiving time of the second data packet is the air interface transmission time length.

6. The communication method according to claim 4 or 5, It is characterized in that The type of the time-related information of the second data packet includes one or more of the following: absolute time; system frame number; time slot number; symbol.

7. The communication method according to any one of claims 3 to 6, It is characterized in that The first data packet and the second data packet are located in the same receiving window.

8. The communication method according to claim 7, It is characterized in that The second data packet includes one or more of the following: The data packet with the highest sequence number among the data packets received in the receiving window; The last received data packet among the data packets received in the receiving window; The data packet with the lowest sequence number among the data packets received in the receiving window; The earliest received data packet among the data packets received in the receiving window.

9. The communication method according to claim 7 or 8, It is characterized in that The first information includes time-related information of the second data packet, and the time-related information of the second data packet is used to determine a first moment, wherein if the first data packet is still not received after the first moment, the first data packet is deemed to have been received.

10. The communication method according to claim 9, It is characterized in that The time-related information of the second data packet includes the receiving time of the second data packet or the timestamp in the RTP packet header, wherein the first time is located at the first preset time length after the receiving time of the second data packet or the timestamp.

11. The communication method according to claim 7 or 8, It is characterized in that The first information includes information of the sequence number of the second data packet, wherein if a difference between the sequence number of the first data packet and the sequence number of the second data packet is less than a first preset value, the first data packet is deemed to have been received.

12. The communication method according to any one of claims 3 to 6, It is characterized in that The first data packet and the second data packet belong to the same data packet cluster.

13. The communication method according to claim 12, It is characterized in that The second data packet is the first data packet in the data packet cluster.

14. The communication method according to claim 13, It is characterized in that The second data packet is a data packet with the smallest sequence number in the data packet cluster received by the first device; or, the sequence number of the second data packet is sent by the second device.

15. The communication method according to any one of claims 12 to 14, It is characterized in that The first information includes time-related information of the second data packet, and the time-related information of the second data packet is used to determine a second moment, wherein if the first data packet is still not received after the second moment, the first data packet is deemed to have been received.

16. The communication method according to claim 15, It is characterized in that The time-related information of the second data packet includes a receiving time or a sending time of the second data packet, and the second time is located at a second preset time length after the receiving time or the sending time of the second data packet.

17. The communication method according to claim 16, It is characterized in that The first information also includes time-related information of the data packet cluster, and the second preset duration is determined based on the time-related information of the data packet cluster.

18. The communication method according to claim 17, It is characterized in that The time-related information of the data packet cluster includes one or more of the following: An air interface transmission delay budget of the data packet cluster; Timeout information of the data packet cluster; The clearing time of the packet cluster.

19. The communication method according to claim 18, It is characterized in that The timeout information of the data packet cluster includes one or more of the following: The timeout moment of the data packet cluster; The timeout moment of the first data packet in the data packet cluster; The timeout moment of the last data packet in the data packet cluster; The timeout time of the earliest timed-out data packet in the data packet cluster; The timeout moment of the latest timed-out data packet in the data packet cluster.

20. The communication method according to any one of claims 17 to 19, It is characterized in that The types of time-related information of the data packet cluster include one or more of the following: absolute time; system frame number; time slot number; symbol.

21. The communication method according to any one of claims 17 to 20, It is characterized in that The second preset duration is recorded by a timer of the first device, and the start time of the timer is the reception time or the sending time of the second data packet.

22. The communication method according to any one of claims 17 to 21, It is characterized in that The first information also includes the number of data packets in the data packet cluster and / or the data volume of the data packet cluster, and the number of data packets in the data packet cluster and the data volume of the data packet cluster are used to determine the data packets belonging to the data packet cluster.

23. The communication method according to claim 16, It is characterized in that The first information also includes the number of data packets in the data packet cluster, and the second preset time duration is the time duration for the first device to receive data packets of the number of data packets starting from the second data packet.

24. The communication method according to claim 23, It is characterized in that The number of data packets is recorded by a counter of the first device, and a start time of the counter is a reception time or a sending time of the second data packet.

25. The communication method according to any one of claims 12 to 14, It is characterized in that The first information includes information about the sequence number of the second data packet. If a difference between the sequence number of the first data packet and the sequence number of the second data packet is smaller than a second preset value, the first data packet is deemed to have been received.

26. The communication method according to any one of claims 1 to 25, It is characterized in that The first information is obtained in one or more of the following ways: pre-agreed; determined by the first device; sent by the second device.

27. The communication method according to any one of claims 1 to 26, It is characterized in that The first information is carried in one or more of the following: a packet data convergence protocol PDCP packet header; an RLC packet header; a medium access control MAC packet header; a PDCP control signaling; an RLC control signaling; a medium access control element MAC CE.

28. The communication method according to any one of claims 1 to 27, It is characterized in that Also includes: The first device determines whether to perform a first operation according to the second information, where the first operation includes determining whether to regard an unreceived data packet as received.

29. The communication method according to claim 28, It is characterized in that The second information includes indication information for indicating whether to execute the first operation; or the second information includes information associated with the first operation.

30. The communication method according to claim 29, It is characterized in that The first operation is associated with one or more of the following: a logical channel, a logical channel group, a service type, and information of a terminal device.

31. The communication method according to claim 30, It is characterized in that The information of the terminal device includes one or more of the following: the protocol version supported by the terminal device; and the device information of the terminal device.

32. The communication method according to any one of claims 27 to 31, It is characterized in that The second information is obtained in one or more of the following ways: pre-agreed; determined by the first device; sent by the second device.

33. The communication method according to claim 32, It is characterized in that The second information is carried in one or more of the following: radio resource control RRC signaling; RLC control signaling.

34. The communication method according to any one of claims 28 to 33, It is characterized in that Also includes: The first device sends third information to the second device, where the third information is used to indicate whether the first device has the ability to perform the first operation.

35. The communication method according to claim 34, It is characterized in that The capability is associated with one or more of the following information: frequency band, logical channel, logical channel group, and terminal device information.

36. The communication method according to any one of claims 1 to 35, It is characterized in that In a case where the first data packet is deemed to have been received, the state parameter of the data packet maintained by the first device is updated based on the state of the received data packets having the second sequence number and sequence numbers before the second sequence number.

37. The communication method according to claim 35, It is characterized in that In the case where the first data packet is deemed to have been received, the second sequence number is the sequence number of the first data packet; or, In a case where multiple unreceived data packets are regarded as received, the second sequence number is a sequence number of a last data packet among the multiple data packets, the multiple data packets including the first data packet.

38. The communication method according to claim 36 or 37, It is characterized in that The state parameters include one or more of the following: The first parameter is used to indicate the next sequence number after the last completely correctly received data packet; The second parameter is used to indicate the sequence number updated when the reassembly timer times out; A third parameter is used to indicate the next sequence number after the sequence number of the data packet with the highest sequence number is received; The fourth parameter is used to indicate the next incorrectly received sequence number after the sequence number of the data packet that triggers the reassembly timer.

39. The communication method according to claim 38, It is characterized in that The first parameter is updated to the sequence number of the next unreceived data packet after the second sequence number; The second parameter is updated to the sequence number of the next unreceived data packet after the next received data packet after the first parameter; The sequence number indicated by the third parameter is updated to the sequence number indicated by the third parameter plus 1 if it is before the second sequence number, or remains unchanged if it is after the second sequence number; The fourth parameter is updated to the sequence number of the next segment of unreceived data packets after the second sequence number.

40. The communication method according to any one of claims 36 to 39, It is characterized in that Also includes: In a case where the RLC status report has been triggered and the RLC status report indicates that the first data packet has not been received, the RLC status report is canceled, and the RLC status report is re-triggered based on the updated status parameter.

41. The communication method according to any one of claims 1 to 40, It is characterized in that The first data packet includes a service data unit SDU and / or a fragment of the SDU.

42. The communication method according to any one of claims 1 to 41, It is characterized in that The first device is a terminal device or a network device.

43. A communication method, It is characterized in that include: The second device sends first information to the first device, where the first information is used to determine whether to regard a first data packet that has not been received as received, and the first information is associated with a second data packet received by the first device, and the first data packet and the second data packet are data packets transmitted in a radio link control RLC confirmation mode.

44. The communication method according to claim 43, It is characterized in that The first data packet is deemed to have been received, wherein the first device does not trigger an RLC status report; or, the first device triggers the RLC status report and the RLC status report does not indicate that the first data packet is not received.

45. The communication method according to claim 43 or 44, It is characterized in that The first data packet and the second data packet belong to the same data packet cluster.

46. ​​The communication method according to claim 45, It is characterized in that The second data packet is the first data packet in the data packet cluster.

47. The communication method according to claim 46, It is characterized in that The second data packet is a data packet with the smallest sequence number in the data packet cluster received by the first device; or, the sequence number of the second data packet is indicated by the second device.

48. A communication method according to any one of claims 45 to 47, It is characterized in that The first information is used to determine a second time instant, wherein if the first data packet is still not received after the second time instant, the first data packet is deemed to have been received.

49. The communication method according to claim 48, It is characterized in that The first information is used to determine a second preset duration, and the second moment is located at the second preset duration after a receiving moment or a sending moment of the second data packet.

50. The communication method according to claim 48, It is characterized in that The first information includes time-related information of the data packet cluster, and the time-related information of the data packet cluster is used to determine the second preset duration.

51. The communication method according to claim 50, It is characterized in that The time-related information of the data packet cluster includes one or more of the following: An air interface transmission delay budget of the data packet cluster; Timeout information of the data packet cluster; The clearing time of the packet cluster.

52. The communication method according to claim 51, It is characterized in that The timeout information of the data packet cluster includes one or more of the following: The timeout moment of the data packet cluster; The timeout moment of the first data packet in the data packet cluster; The timeout moment of the last data packet in the data packet cluster; The timeout time of the earliest timed-out data packet in the data packet cluster; The timeout moment of the latest timed-out data packet in the data packet cluster.

53. The communication method according to any one of claims 50 to 52, It is characterized in that The second preset duration is recorded by a timer of the first device, and the start time of the timer is the reception time or the sending time of the second data packet.

54. A communication method according to any one of claims 50 to 53, It is characterized in that The types of time-related information of the data packet cluster include one or more of the following: absolute time; system frame number; time slot number; symbol.

55. The communication method according to any one of claims 50 to 54, It is characterized in that The first information also includes the number of data packets in the data packet cluster and / or the data volume of the data packet cluster, and the number of data packets in the data packet cluster or the data volume of the data packet cluster is used to determine the data packets belonging to the data packet cluster.

56. The communication method according to claim 49, It is characterized in that The first information includes the number of data packets in the data packet cluster, and the second preset time duration is the time duration for the first device to receive data packets of the number of data packets starting from the second data packet.

57. The communication method according to claim 56, It is characterized in that The number of data packets is recorded by a counter of the first device, and a start time of the counter is a reception time or a sending time of the second data packet.

58. A communication method according to any one of claims 45 to 47, It is characterized in that The first information includes information about the sequence number of the second data packet. If a difference between the sequence number of the first data packet and the sequence number of the second data packet is smaller than a second preset value, the first data packet is deemed to have been received.

59. A communication method according to any one of claims 43 to 57, It is characterized in that The first information is carried in one or more of the following: a packet data convergence protocol PDCP packet header; an RLC packet header; a medium access control MAC packet header; a PDCP control signaling; an RLC control signaling; a medium access control element MAC CE.

60. The communication method according to any one of claims 43 to 58, It is characterized in that Also includes: The second device sends second information to the first device, where the second information is used to determine whether to perform a first operation, where the first operation includes determining whether to regard an unreceived data packet as received.

61. The communication method according to claim 60, It is characterized in that The second information includes indication information for indicating whether to execute the first operation; or the second information includes information associated with the first operation.

62. The communication method according to claim 61, It is characterized in that The first operation is associated with one or more of the following: a logical channel, a logical channel group, a service type, and information of a terminal device.

63. The communication method according to claim 62, It is characterized in that The information of the terminal device includes one or more of the following: the protocol version supported by the terminal device; and the device information of the terminal device.

64. The communication method according to any one of claims 60 to 63, It is characterized in that The second information is carried in one or more of the following: radio resource control RRC signaling; RLC control signaling.

65. The communication method according to any one of claims 60 to 64, It is characterized in that Also includes: The second device receives third information sent by the first device, where the third information is used to indicate whether the first device has the ability to perform the first operation.

66. The communication method according to claim 65, It is characterized in that The capability is associated with one or more of the following information: frequency band, logical channel, logical channel group, and terminal device information.

67. A communication method according to any one of claims 43 to 66, It is characterized in that In a case where the first data packet is deemed to have been received, the state parameter of the data packet maintained by the first device is updated based on the state of the received data packets having the second sequence number and sequence numbers before the second sequence number.

68. The communication method according to claim 67, It is characterized in that In the case where the first data packet is deemed to have been received, the second sequence number is the sequence number of the first data packet; or, In a case where multiple unreceived data packets are regarded as received, the second sequence number is a sequence number of a last data packet among the multiple data packets, the multiple data packets including the first data packet.

69. The communication method according to claim 67 or 68, It is characterized in that The state parameters include one or more of the following: The first parameter is used to indicate the next sequence number after the last completely correctly received data packet; The second parameter is used to indicate the sequence number updated when the reassembly timer times out; A third parameter is used to indicate the next sequence number after the sequence number of the data packet with the highest sequence number is received; The fourth parameter is used to indicate the next incorrectly received sequence number after the sequence number of the data packet that triggers the reassembly timer.

70. The communication method according to claim 69, It is characterized in that The first parameter is updated to the sequence number of the next unreceived data packet after the second sequence number; The second parameter is updated to the sequence number of the next unreceived data packet after the next received data packet after the first parameter; The sequence number indicated by the third parameter is updated to the sequence number indicated by the third parameter plus 1 if it is before the second sequence number, or remains unchanged if it is after the second sequence number; The fourth parameter is updated to the sequence number of the next segment of unreceived data packets after the second sequence number.

71. A communication method according to any one of claims 67 to 70, It is characterized in that Also includes: The second device receives the RLC status report sent by the first device, where the RLC status report is an RLC status report triggered by the first device based on the updated status parameter.

72. A communication method according to any one of claims 43 to 71, It is characterized in that The first data packet includes a service data unit SDU and / or a fragment of the SDU.

73. A communication method according to any one of claims 43 to 72, It is characterized in that The second device is a terminal device or a network device.

74. A communication device, It is characterized in that The communication device is a first device, comprising: A processing unit is used to regard a first data packet that has not been received as received when a first condition is met, and the first condition is determined based on a second data packet received by the first device, and the first data packet and the second data packet are data packets transmitted in a radio link control RLC confirmation mode.

75. The communication device according to claim 74, It is characterized in that The first data packet is deemed to have been received, wherein the first device does not trigger an RLC status report; or, the first device triggers the RLC status report and the RLC status report does not indicate that the first data packet is not received.

76. The communication device according to claim 74 or 75, It is characterized in that The first condition is determined based on first information, where the first information includes time-related information and / or sequence number information of the second data packet.

77. The communication device according to claim 76, It is characterized in that The time related information of the second data packet includes one or more of the following: a time at which the second data packet is received; The sending time of the second data packet; The timestamp in the Real-time Transport Protocol (RTP) packet header of the second data packet.

78. The communication device according to claim 77, It is characterized in that The difference between the sending time of the second data packet and the receiving time of the second data packet is the air interface transmission time length.

79. The communication device according to claim 77 or 78, It is characterized in that The type of the time-related information of the second data packet includes one or more of the following: absolute time; system frame number; time slot number; symbol.

80. The communication device according to any one of claims 76 to 79, It is characterized in that The first data packet and the second data packet are located in the same receiving window.

81. The communication device according to claim 77, It is characterized in that The second data packet includes one or more of the following: The data packet with the highest sequence number among the data packets received in the receiving window; The last received data packet among the data packets received in the receiving window; The data packet with the lowest sequence number among the data packets received in the receiving window; The earliest received data packet among the data packets received in the receiving window.

82. The communication device according to claim 80 or 81, It is characterized in that The first information includes time-related information of the second data packet, and the time-related information of the second data packet is used to determine a first moment, wherein if the first data packet is still not received after the first moment, the first data packet is deemed to have been received.

83. The communication device according to claim 82, It is characterized in that The time-related information of the second data packet includes the receiving time of the second data packet or the timestamp in the RTP packet header, wherein the first time is located at the first preset time length after the receiving time of the second data packet or the timestamp.

84. The communication device according to claim 80 or 81, It is characterized in that The first information includes information of the sequence number of the second data packet, wherein if a difference between the sequence number of the first data packet and the sequence number of the second data packet is less than a first preset value, the first data packet is deemed to have been received.

85. A communication device according to any one of claims 76 to 79, It is characterized in that The first data packet and the second data packet belong to the same data packet cluster.

86. The communication device according to claim 85, It is characterized in that The second data packet is the first data packet in the data packet cluster.

87. The communication device according to claim 86, It is characterized in that The second data packet is a data packet with the smallest sequence number in the data packet cluster received by the first device; or, the sequence number of the second data packet is indicated by the second device.

88. A communication device according to any one of claims 85 to 87, It is characterized in that The first information includes time-related information of the second data packet, and the time-related information of the second data packet is used to determine a second moment, wherein if the first data packet is still not received after the second moment, the first data packet is deemed to have been received.

89. The communication device according to claim 88, It is characterized in that The time-related information of the second data packet includes a receiving time or a sending time of the second data packet, and the second time is located at a second preset time length after the receiving time or the sending time of the second data packet.

90. The communication device according to claim 89, It is characterized in that The first information also includes time-related information of the data packet cluster, and the second preset duration is determined based on the time-related information of the data packet cluster.

91. The communication device according to claim 90, It is characterized in that The time-related information of the data packet cluster includes one or more of the following: An air interface transmission delay budget of the data packet cluster; Timeout information of the data packet cluster; The clearing time of the packet cluster.

92. The communication device according to claim 91, It is characterized in that The timeout information of the data packet cluster includes one or more of the following: The timeout moment of the data packet cluster; The timeout moment of the first data packet in the data packet cluster; The timeout moment of the last data packet in the data packet cluster; The timeout time of the earliest timed-out data packet in the data packet cluster; The timeout moment of the latest timed-out data packet in the data packet cluster.

93. The communication device according to any one of claims 90 to 92, It is characterized in that The types of time-related information of the data packet cluster include one or more of the following: absolute time; system frame number; time slot number; symbol.

94. The communication device according to any one of claims 90 to 93, It is characterized in that The second preset duration is recorded by a timer of the first device, and the start time of the timer is the reception time or the sending time of the second data packet.

95. The communication device according to any one of claims 90 to 94, It is characterized in that The first information also includes the number of data packets in the data packet cluster and / or the data volume of the data packet cluster, and the number of data packets in the data packet cluster and the data volume of the data packet cluster are used to determine the data packets belonging to the data packet cluster.

96. The communication device according to claim 89, It is characterized in that The first information also includes the number of data packets in the data packet cluster, and the second preset time duration is the time duration for the first device to receive data packets of the number of data packets starting from the second data packet.

97. The communication device according to claim 96, It is characterized in that The number of data packets is recorded by a counter of the first device, and a start time of the counter is a reception time or a sending time of the second data packet.

98. The communication device according to any one of claims 85 to 87, It is characterized in that The first information includes information of the sequence number of the second data packet, wherein if the difference between the sequence number of the first data packet and the sequence number of the second data packet is less than a second preset value, the first data packet is deemed to have been received.

99. The communication device according to any one of claims 85 to 98, It is characterized in that The first information is obtained in one or more of the following ways: pre-agreed; determined by the first device; sent by the second device.

100. The communication device according to any one of claims 85 to 99, It is characterized in that The first information is carried in one or more of the following: a packet data convergence protocol PDCP packet header; an RLC packet header; a medium access control MAC packet header; a PDCP control signaling; an RLC control signaling; a medium access control element MAC CE.

101. The communication device according to any one of claims 85 to 100, It is characterized in that The processing unit is also used for: Determine whether to perform a first operation according to the second information, wherein the first operation includes determining whether to regard an unreceived data packet as received.

102. The communication device according to claim 101, It is characterized in that The second information includes indication information for indicating whether to execute the first operation; or the second information includes information associated with the first operation.

103. The communication device according to claim 102, It is characterized in that The first operation is associated with one or more of the following: a logical channel, a logical channel group, a service type, and information of a terminal device.

104. The communication device according to claim 103, It is characterized in that The information of the terminal device includes one or more of the following: the protocol version supported by the terminal device; and the device information of the terminal device.

105. The communication device according to any one of claims 101 to 104, It is characterized in that The second information is obtained in one or more of the following ways: pre-agreed; determined by the first device; sent by the second device.

106. The communication device according to claim 105, It is characterized in that The second information is carried in one or more of the following: radio resource control RRC signaling; RLC control signaling.

107. The communication device according to any one of claims 101 to 105, It is characterized in that Also includes a transceiver unit for: Sending third information to the second device, where the third information is used to indicate whether the first device has the ability to perform the first operation.

108. The communication device according to claim 107, It is characterized in that The capability is associated with one or more of the following information: frequency band, logical channel, logical channel group, and terminal device information.

109. The communication device according to any one of claims 85 to 108, It is characterized in that In a case where the first data packet is deemed to have been received, the state parameter of the data packet maintained by the first device is updated based on the state of the received data packets having the second sequence number and sequence numbers before the second sequence number.

110. The communication device according to claim 109, It is characterized in that In the case where the first data packet is deemed to have been received, the second sequence number is the sequence number of the first data packet; or, In a case where multiple unreceived data packets are regarded as received, the second sequence number is a sequence number of a last data packet among the multiple data packets, the multiple data packets including the first data packet.

111. The communication device according to claim 109 or 110, It is characterized in that The state parameters include one or more of the following: The first parameter is used to indicate the next sequence number after the last completely correctly received data packet; The second parameter is used to indicate the sequence number updated when the reassembly timer times out; A third parameter is used to indicate the next sequence number after the sequence number of the data packet with the highest sequence number is received; The fourth parameter is used to indicate the next incorrectly received sequence number after the sequence number of the data packet that triggers the reassembly timer.

112. The communication device according to claim 111, It is characterized in that The first parameter is updated to the sequence number of the next unreceived data packet after the second sequence number; The second parameter is updated to the sequence number of the next unreceived data packet after the next received data packet after the first parameter; The sequence number indicated by the third parameter is updated to the sequence number indicated by the third parameter plus 1 if it is before the second sequence number, or remains unchanged if it is after the second sequence number; The fourth parameter is updated to the sequence number of the next segment of unreceived data packets after the second sequence number.

113. The communication device according to any one of claims 109 to 112, It is characterized in that The processing unit is also used for: In a case where the RLC status report has been triggered and the RLC status report indicates that the first data packet has not been received, the RLC status report is canceled, and the RLC status report is re-triggered based on the updated status parameter.

114. A communication device according to any one of claims 85 to 113, It is characterized in that The first data packet includes a service data unit SDU and / or a fragment of the SDU.

115. The communication device according to any one of claims 85 to 114, It is characterized in that The first device is a terminal device or a network device.

116. A communication device, It is characterized in that The communication device is a second device, comprising: A transceiver unit is used to send first information to a first device, where the first information is used to determine whether to regard a first data packet that has not been received as received, and the first information is associated with a second data packet received by the first device, and the first data packet and the second data packet are data packets transmitted in a radio link control RLC confirmation mode.

117. The communication device according to claim 116, It is characterized in that The first data packet is deemed to have been received, wherein the first device does not trigger an RLC status report; or, the first device triggers the RLC status report and the RLC status report does not indicate that the first data packet is not received.

118. The communication device according to claim 116 or 117, It is characterized in that The first data packet and the second data packet belong to the same data packet cluster.

119. The communication device according to claim 118, It is characterized in that The second data packet is the first data packet in the data packet cluster.

120. The communication device according to claim 119, It is characterized in that The second data packet is a data packet with the smallest sequence number in the data packet cluster received by the first device; or, the sequence number of the second data packet is indicated by the second device.

121. A communication device according to any one of claims 118 to 120, It is characterized in that The first information is used to determine a second time instant, wherein if the first data packet is still not received after the second time instant, the first data packet is deemed to have been received.

122. The communication device according to claim 121, It is characterized in that The first information is used to determine a second preset duration, and the second moment is located at the second preset duration after a receiving moment or a sending moment of the second data packet.

123. The communication device according to claim 122, It is characterized in that The first information includes time-related information of the data packet cluster, and the time-related information of the data packet cluster is used to determine the second preset duration.

124. The communication device according to claim 123, It is characterized in that The time-related information of the data packet cluster includes one or more of the following: An air interface transmission delay budget of the data packet cluster; Timeout information of the data packet cluster; The clearing time of the packet cluster.

125. The communication device according to claim 124, It is characterized in that The timeout information of the data packet cluster includes one or more of the following: The timeout moment of the data packet cluster; The timeout moment of the first data packet in the data packet cluster; The timeout moment of the last data packet in the data packet cluster; The timeout time of the earliest timed-out data packet in the data packet cluster; The timeout moment of the latest timed-out data packet in the data packet cluster.

126. The communication device according to any one of claims 123 to 125, It is characterized in that The second preset duration is recorded by a timer of the first device, and the start time of the timer is the reception time or the sending time of the second data packet.

127. The communication device according to any one of claims 123 to 126, It is characterized in that The types of time-related information of the data packet cluster include one or more of the following: absolute time; system frame number; time slot number; symbol.

128. The communication device according to any one of claims 123 to 127, It is characterized in that The first information also includes the number of data packets in the data packet cluster and / or the data volume of the data packet cluster, and the number of data packets in the data packet cluster or the data volume of the data packet cluster is used to determine the data packets belonging to the data packet cluster.

129. The communication device according to claim 122, It is characterized in that The first information includes the number of data packets in the data packet cluster, and the second preset time duration is the time duration for the first device to receive data packets of the number of data packets starting from the second data packet.

130. The communication device according to claim 129, It is characterized in that The number of data packets is recorded by a counter of the first device, and a start time of the counter is a reception time or a sending time of the second data packet.

131. A communication device according to any one of claims 118 to 120, It is characterized in that The first information includes information about the sequence number of the second data packet. If a difference between the sequence number of the first data packet and the sequence number of the second data packet is smaller than a second preset value, the first data packet is deemed to have been received.

132. A communication device according to any one of claims 116 to 130, It is characterized in that The first information is carried in one or more of the following: a packet data convergence protocol PDCP packet header; an RLC packet header; a medium access control MAC packet header; a PDCP control signaling; an RLC control signaling; a medium access control element MAC CE.

133. A communication device according to any one of claims 116 to 131, It is characterized in that The transceiver unit is also used for: Sending second information to the first device, where the second information is used to determine whether to perform a first operation, where the first operation includes determining whether to regard an unreceived data packet as received.

134. The communication device according to claim 133, It is characterized in that The second information includes indication information for indicating whether to execute the first operation; or the second information includes information associated with the first operation.

135. The communication device according to claim 134, It is characterized in that The first operation is associated with one or more of the following: a logical channel, a logical channel group, a service type, and information of a terminal device.

136. The communication device according to claim 135, It is characterized in that The information of the terminal device includes one or more of the following: the protocol version supported by the terminal device; and the device information of the terminal device.

137. A communication device according to any one of claims 133 to 136, It is characterized in that The second information is carried in one or more of the following: radio resource control RRC signaling; RLC control signaling.

138. A communication device according to any one of claims 133 to 137, It is characterized in that The transceiver unit is also used for: Receive third information sent by the first device, where the third information is used to indicate whether the first device has the ability to perform the first operation.

139. The communication device according to claim 138, It is characterized in that The capability is associated with one or more of the following information: frequency band, logical channel, logical channel group, and terminal device information.

140. The communication device according to any one of claims 116 to 139, It is characterized in that In a case where the first data packet is deemed to have been received, the state parameter of the data packet maintained by the first device is updated based on the state of the received data packets having the second sequence number and sequence numbers before the second sequence number.

141. The communication device according to claim 140, It is characterized in that In the case where the first data packet is deemed to have been received, the second sequence number is the sequence number of the first data packet; or, In a case where multiple unreceived data packets are regarded as received, the second sequence number is a sequence number of a last data packet among the multiple data packets, the multiple data packets including the first data packet.

142. The communication device according to claim 140 or 141, It is characterized in that The state parameters include one or more of the following: The first parameter is used to indicate the next sequence number after the last completely correctly received data packet; The second parameter is used to indicate the sequence number updated when the reassembly timer times out; A third parameter is used to indicate the next sequence number after the sequence number of the data packet with the highest sequence number is received; The fourth parameter is used to indicate the next incorrectly received sequence number after the sequence number of the data packet that triggers the reassembly timer.

143. The communication device according to claim 142, It is characterized in that The first parameter is updated to the sequence number of the next unreceived data packet after the second sequence number; The second parameter is updated to the sequence number of the next unreceived data packet after the next received data packet after the first parameter; The sequence number indicated by the third parameter is updated to the sequence number indicated by the third parameter plus 1 if it is before the second sequence number, or remains unchanged if it is after the second sequence number; The fourth parameter is updated to the sequence number of the next segment of unreceived data packets after the second sequence number.

144. A communication device according to any one of claims 140 to 143, It is characterized in that The transceiver unit is also used for: An RLC status report sent by the first device is received, where the RLC status report is an RLC status report triggered by the first device based on the updated status parameter.

145. A communication device according to any one of claims 116 to 144, It is characterized in that The first data packet includes a service data unit SDU and / or a fragment of the SDU.

146. A communication device according to any one of claims 116 to 145, It is characterized in that The second device is a terminal device or a network device.

147. A communication device, It is characterized in that It comprises a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the communication device executes the method according to any one of claims 1 to 42.

148. A communication device, It is characterized in that It includes a transceiver, a memory and a processor, the memory is used to store programs, the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the communication device executes the method according to any one of claims 43 to 73.

149. A device, It is characterized in that It comprises a processor, configured to call a program from a memory so that the apparatus executes the method according to any one of claims 1 to 42, or the method according to any one of claims 43 to 73.

150. A chip, It is characterized in that It comprises a processor for calling a program from a memory so that the chip executes a method according to any one of claims 1 to 42, or a method according to any one of claims 43 to 73.

151. A computer-readable storage medium, It is characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 42, or the method according to any one of claims 43 to 73.

152. A computer program product, It is characterized in that Comprising a program causing a computer to execute the method according to any one of claims 1 to 42, or the method according to any one of claims 43 to 73.

153. A computer program, It is characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 42, or the method according to any one of claims 43 to 73.