WO2021233401A1

WO2021233401A1 - Data transmission method and device

Info

Publication number: WO2021233401A1
Application number: PCT/CN2021/095007
Authority: WO
Inventors: 张艳霞
Original assignee: 维沃移动通信有限公司
Priority date: 2020-05-22
Filing date: 2021-05-21
Publication date: 2021-11-25
Also published as: CN113708889A

Abstract

Disclosed in the embodiments of the present application are a data transmission method and device. The method comprises: when the send timeout of N continuous first data packets is determined, a sending end device adjusting a data transmission strategy, N being an integer greater than 1.

Description

Data transmission method and equipment

Cross-references to related applications

This application claims the priority of Chinese Patent Application No. 202010444358.9 filed in China on May 22, 2020, the entire content of which is incorporated herein by reference.

Technical field

The embodiments of the present application relate to the field of communications, and in particular, to a data transmission method and device.

Background technique

The availability of communication services is an important service performance requirement indicator for many automated functional applications, especially for applications with deterministic business flows. In an industrial environment, many automation function applications have high demand for communication service availability. For example, mobile control has a high demand for communication service availability as high as 99.999999%.

In the actual application process, when the receiving end device does not correctly receive the data packet sent by the sending end device within a specific time (such as survival time), it will cause the (automation function) application of the receiving end device to be unavailable. Use state.

However, for the sending end device, it does not know whether the relevant application of the receiving end device is about to enter an unavailable state, and thus cannot provide an effective strategy to ensure that the data packet reaches the receiving end device within the survival time as much as possible.

Summary of the invention

The purpose of the embodiments of this application is to provide a data transmission method and device to solve the problem that the sender device cannot determine whether the relevant application of the receiver device is about to enter an unavailable state, and thus cannot provide an effective strategy to ensure the survival time of the data packet as much as possible. Problems reaching the receiving end device within.

In a first aspect, a data transmission method is provided, the method is executed by a sending end device, and the method includes: adjusting a data transmission strategy when it is determined that the sending of N consecutive first data packets is timed out, where N is greater than An integer of 1.

In a second aspect, a data transmission method is provided, the method is executed by a network device, and the method includes at least one of the following: sending first configuration information, where the first configuration information is used to indicate N consecutive sending timeouts The logical channel configuration of the radio bearer corresponding to the first data packet; sending the uplink grant; sending the second configuration information, the second configuration information is used to reconfigure the radio bearer corresponding to the first data packet whose transmission timed out. Logical channel configuration.

In a third aspect, a sender device is provided, including: an adjustment module, configured to adjust a data transmission strategy when it is determined that the sending of N consecutive first data packets timeout, where N is an integer greater than 1.

In a fourth aspect, a network device is provided. The network device includes a sending module, configured to send at least one of the following: first configuration information, where the first configuration information is used to indicate N consecutive sending timeout first data The logical channel configuration of the radio bearer corresponding to the packet; sending the uplink grant; sending the second configuration information, the second configuration information being used to reconfigure the logical channel configuration of the radio bearer corresponding to the first data packet whose transmission times out.

In a fifth aspect, a sender device is provided. The sender device includes a processor, a memory, and instructions or programs that are stored on the memory and run on the processor. The instructions or programs are The processor implements the steps of the data transmission method as described in the first aspect when executed.

In a sixth aspect, a network device is provided. The network device includes a processor, a memory, and instructions or programs that are stored on the memory and that can run on the processor. The instructions or programs are executed by the processor. When executed, the data transmission method as described in any one of the first aspect and the second aspect is realized.

In a seventh aspect, a readable storage medium is provided. The readable storage medium stores an instruction or a program. When the instruction or program is executed by a processor, the implementation is as described in any one of the first aspect and the second aspect. Data transfer method.

In an eighth aspect, an embodiment of the present application provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used to run a program or an instruction to implement the chip as in the first aspect And the data transmission method described in any one of the second aspects.

In the embodiment of the present application, when it is determined that the sending of N consecutive first data packets has timed out, the sending end device thinks that the relevant application of the receiving end device is about to enter an unavailable state, and then adjusts the data transmission strategy, for example, increasing the first The priority of the logical channel corresponding to the data packet; receiving the uplink authorization specially used for transmitting the first data packet, etc., to ensure that the data packet reaches the receiving end device within the survival time as much as possible to improve the effectiveness of communication.

Description of the drawings

Fig. 1 is a schematic flowchart of a data transmission method according to an embodiment of the present application;

Fig. 2 is a schematic diagram of the initial state of a sliding window according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a state after a sliding window is moved according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a state in which a sliding window does not need to be moved according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a state after a sliding window is moved according to another embodiment of the present application;

Fig. 6 is a schematic diagram of timer start/stop according to an embodiment of the present application;

FIG. 7 is a schematic flowchart of a data transmission method according to another embodiment of the present application;

Fig. 8 is a schematic structural diagram of a sending end device according to an embodiment of the present application;

Fig. 9 is a schematic structural diagram of a network device according to an embodiment of the present application;

Fig. 10 is a schematic structural diagram of a terminal device according to an embodiment of the present application;

Fig. 11 is a schematic structural diagram of a network device according to another embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be described clearly and completely in conjunction with specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The terms "first" and "second" in the specification and claims of this application are used to distinguish similar objects, but not to describe a specific sequence or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in a sequence other than those illustrated or described herein. In addition, "and/or" in the specification and claims means at least one of the connected objects, and the character "/" generally means that the associated objects before and after are in an "or" relationship.

It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex ( Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS) or Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5G system, or New Radio (NR) System, or the subsequent evolution of the communication system.

In the embodiments of this application, terminal equipment may include, but is not limited to, a mobile station (Mobile Station, MS), a mobile terminal (Mobile Terminal), a mobile phone (Mobile Telephone), a user equipment (User Equipment, UE), and a mobile phone (handset) And portable equipment (portable equipment), vehicles (vehicle), etc., the terminal equipment can communicate with one or more core networks through a radio access network (Radio Access Network, RAN), for example, the terminal equipment can be a mobile phone (or It is called a "cellular" phone), a computer with wireless communication function, etc. The terminal device can also be a portable, pocket-sized, handheld, built-in computer or a mobile device in a vehicle.

In the embodiments of the present application, a network device is a device deployed in a wireless access network to provide wireless communication functions for terminal devices. The network device may be a base station, and the base station may include various forms of macro base stations, micro base stations, relay stations, and access points. In systems using different wireless access technologies, the names of devices with base station functions may be different. For example, in an LTE network, it is called an evolved NodeB (evolved NodeB, eNB or eNodeB), in a third generation (3rd Generation, 3G) network, it is called a Node B (NodeB), and in a 5G system, it is called a lower node. Generation Node B (gNB), or network equipment in subsequent evolved communication systems, etc., however, the terminology does not constitute a restriction.

As shown in FIG. 1, an embodiment of the present application provides a data transmission method 100. The method 100 can be executed by a sending end device. In other words, the method 100 can be executed by software or hardware installed on the sending end device. The method includes the following steps.

S102: When it is determined that the sending of N consecutive first data packets is timed out, adjust the data transmission strategy, where N is an integer greater than 1.

The sending end device mentioned in each embodiment of the present application may be a terminal device (such as a UE) or a network device (such as a gNB). When the sending end device is a terminal device, N can be configured by the network device or agreed upon by a protocol; when the sending end device is a network device, N can be independently determined by the network device or agreed upon by the protocol.

In this embodiment, each first data packet may correspond to a timer, which is used to determine whether the transmission of the first data packet has timed out, and the timer may be in the data packet (including the first data packet mentioned above, It can also be started at the time when other data packets arrive, or it can be started after a predetermined time has passed after the data packet arrives. Wherein, the "data packet arrival" can be understood as the data packet arriving from the upper layer to the protocol layer maintaining the timer, and it can also be understood as the protocol layer maintaining the timer receiving the data packet from the upper layer. In one example, the Packet Data Convergence Protocol (PDCP) layer of the sender device maintains the above timer, which is started when the first data packet reaches the PDCP layer from the upper layer (such as the SDAP layer or the application layer) The timer. In another example, the Packet Data Convergence Protocol (PDCP) layer of the sender device maintains the above timer, and the PDCP layer starts when the first data packet is received from the upper layer (such as the SDAP layer or the application layer) The timer.

In this embodiment, the N consecutive first data packets may be N consecutive first data packets; it may also be N consecutive first data packets with arrival times (for example, the time to reach a certain protocol layer); It can also be N first data packets with consecutive numbers and consecutive arrival times.

For the above-mentioned number, for example, when the packet data convergence protocol (PDCP) layer of the sender device maintains the above-mentioned timer, the number can be the PDCP count value (that is, COUNT), the PDCP sequence Number (Sequence Number, SN), etc. In another example, when the radio link control (RLC) layer of the transmitting end device maintains the above timer, the number may be an RLC sequence number (Sequence Number, SN), etc.

Optionally, the adjustment of the data transmission strategy mentioned in this embodiment includes at least one of the following:

1) Adjust the logical channel configuration of the radio bearer corresponding to the first data packet. For example, the priority of the logical channel of the radio bearer corresponding to the first data packet is increased to facilitate the timely transmission of the first data packet, to prevent the application of the receiving end device from entering an unavailable state, and to improve the effectiveness of communication.

Optionally, before adjusting the data transmission strategy, the method 100 further includes: receiving first configuration information, where the first configuration information is used to indicate the radio bearer corresponding to the first data packet whose transmission timed out for N consecutive transmissions. The logical channel configuration. For example, a network device provides two sets of

logical channel configurations

1 and 2 for a dedicated radio bearer (DRB). If there are N consecutive first data packets sent overtime in the DRB, the terminal device automatically adjusts logical channel configuration 1 to logical channel configuration 2, where the logical channel priority of logical channel configuration 2 can be higher than that of logical channel configuration 1. The priority of the logical channel.

2) Receive uplink authorization.

The uplink authorization can be used to transmit a specific type of data packet. The specific type of data packet includes sending timeout (for example, the first data packet mentioned above) or sending a data packet that is about to time out, so as to prevent the application of the receiving device from entering unavailability. Status to improve the effectiveness of communication.

Optionally, when the sending end device is a terminal device, the aforementioned adjusting data transmission strategy includes at least one of the following:

1) Send a scheduling request to the network device. Optionally, the scheduling request carries first indication information, and the first indication information carries at least one of the amount of data to be sent and the remaining time. For example, the scheduling request (Scheduling Request, SR) resource for sending the scheduling request corresponds to the logical channel, and the sending end device detects that the sending of multiple consecutive first data packets is timed out. The SR resource corresponding to the channel sends a scheduling request. The network device side can determine which or which logical channel corresponds to the data packet whose transmission timeout occurs through the SR resource. Exemplarily, the scheduling request may also carry data volume and remaining time information, and the remaining time may indicate the remaining time until the timer expires (the remaining time may be an absolute time value or The range value of the remaining time, for example, 1ms～2ms corresponds to the range value 1, 2ms～3ms corresponds to the range value 2.), the amount of data can indicate the amount of data corresponding to the remaining time. For example, the data amount corresponding to the range value 1 of the remaining time is 100 bytes, and the data amount corresponding to the range value 2 of the remaining time is 200 bytes. The scheduling request carrying the first indication information may also be triggered under normal conditions, that is to say, it is not sent when the UE detects that the sending of N consecutive first data packets has timed out. The normal condition may be high priority. When the data arrives, but the BSR cannot be sent.

2) Send a cache status report to the network device. Optionally, the buffer status report carries second indication information, and the second indication information carries at least one of the amount of buffered data and the remaining time. Exemplarily, the buffer status report may also carry data amount and remaining time information, and the remaining time may indicate the remaining time before the aforementioned timer expires (the remaining time may be an absolute time value or Is the range value of the remaining time, for example, 1ms～2ms corresponds to the range value 1, 2ms～3ms corresponds to the range value 2.), the data amount can indicate the data amount corresponding to the remaining time. For example, the data amount corresponding to the range value 1 of the remaining time is 100 bytes, and the data amount corresponding to the range value 2 of the remaining time is 200 bytes. The buffer status report carrying the first indication information can also be triggered under normal conditions, that is to say, it is not sent when the UE detects that the sending of N consecutive first data packets has timed out. The normal condition may be high. In the case of priority data arrival.

3) Send Media Access Control (MAC) layer signaling (such as MAC CE) to the network device. Optionally, the MAC layer signaling may carry a logical channel identifier, which is used to indicate that the logical channel corresponding to the logical channel identifier has a data packet that has timed out. Additionally, the MAC layer signaling can trigger SR. For example, if the sending end detects that the sending of N consecutive first data packets has timed out, it needs to send MAC layer signaling (such as MAC CE) to the network device side, but there is no resource for sending the MAC layer signaling (such as PUSCH resource), then The sending end device can trigger the SR.

In this embodiment, by executing one or a combination of the above three implementation manners, the network device can allocate an uplink grant to the terminal device. The uplink grant can be used to transmit data packets that are timed out or are about to time out, so as to avoid The application of the receiving end device enters an unavailable state, which improves the effectiveness of communication.

Optionally, the uplink authorization mentioned in the above multiple examples may carry third indication information, and the third indication information is used to indicate that the uplink authorization is used for a specific type of data packet, wherein the specific type of data Packets include sending timeouts or sending data packets that are about to time out.

In this embodiment, by executing one or a combination of the above three implementation manners, the network device may also send second configuration information, which is used to reconfigure the logic corresponding to the first data packet Channel configuration. For example, the priority of the logical channel of the radio bearer corresponding to the first data packet is increased to facilitate the timely transmission of the first data packet, to prevent the application of the receiving end device from entering an unavailable state, and to improve the effectiveness of communication.

In the data transmission method provided by the embodiment of the present application, when it is determined that the sending of N consecutive first data packets is timed out, the sending end device considers that the relevant application of the receiving end device is about to enter an unavailable state, and then adjusts the data transmission strategy, for example, Increase the priority of the logical channel corresponding to the first data packet; receive the uplink authorization dedicated to the transmission of the first data packet, etc., so as to ensure that the data packet reaches the receiving end device within the survival time and improve the effectiveness of communication.

In order to explain in detail the data transmission method provided by the above-mentioned embodiments of the present application, the following will describe in combination with two specific embodiments.

Example one

In this embodiment 1, on the basis of embodiment 100, a sliding window can also be used to determine whether consecutive N first data packet transmission timeouts occur, and the window length of the sliding window is equal to N.

In this embodiment, if the first timers corresponding to the N first data packets in the sliding window are all timed out, it is determined that the sending of the N consecutive first data packets has timed out, where each first data packet may correspond to A first timer.

In this embodiment, the sender device, for example, the PDCP layer or the Radio Link Control (RLC) layer of the sender device can maintain a sliding window, and the window length N of the sliding window can be configured by the network device. It can also be an agreement. In an example, the sending end device is a terminal device, and the window length of the sliding window configured by the network device is N, corresponding to N data packets.

In an example, when M consecutive data packets on the Uu port do not reach the receiving device as required (such as not in accordance with the configured QoS requirements), the communication service or application will enter an unavailable state. At this time, the access network can be configured with N It is an integer value less than M, for example, N=M-1.

The above sliding window includes an initial state. In one example, the sliding window includes an initial lower boundary and an initial upper boundary; wherein, the initial lower boundary is located at the position of the number of the initially transmitted data packet, and the initial upper boundary is Numbered positions of N data packets from the initial lower boundary. In another example, the sliding window includes an initial lower boundary and an initial upper boundary; wherein, the initial lower boundary is located at a position numbered 0 of the data packet, and the initial upper boundary is N distances from the initial lower boundary. The numbered position of the data packet.

In the example shown in Figure 2, the initial lower boundary of the sliding window is located at the position of the number (number 1) of the initially sent data packet, and the initial upper boundary is 4 (N=4) data packets away from the initial lower boundary. The numbered position, that is, the initial upper boundary is located at the position numbered 4 of the data packet.

In this embodiment, the sending end device can move the sliding window through one or more of the following three conditions, or maintain the position of the sliding window unchanged, and determine that the N first data packets in the sliding window correspond to Whether all the first timers have timed out.

Situation 1:

When it is determined that the second data packet is successfully sent and the difference between the number of the second data packet and the lower boundary of the sliding window is less than the length of the window, the lower boundary of the sliding window is moved to the first The numbered position of the first third data packet that was not successfully sent after the second data packet.

Exemplarily, the “difference between the number of the second data packet and the lower boundary of the sliding window” may be understood as the difference between the number of the second data packet and the data packet number corresponding to the lower boundary of the sliding window Value, or the absolute value of the difference between the number of the second data packet and the data packet number corresponding to the lower boundary of the sliding window, or the data packet of the data packet interval corresponding to the second data packet and the lower boundary of the sliding window Quantity value.

Case 1: As shown in Figures 2 and 3, the initial lower boundary of the sliding window is at PDCP COUNT=1, and the initial upper boundary of the sliding window is at PDCP COUNT=4, which is the position shown in Fig. 2. When receiving the indication that the data packet of PDCP COUNT=3 (corresponding to the above-mentioned second data packet) was successfully received, move the sliding window to the lower boundary of the sliding window at PDCP COUNT=4 (corresponding to the above-mentioned first data packet) Three data packets). At this time, the upper boundary of the sliding window is at PDCP COUNT=7, that is, the position shown in FIG. 3. In addition, Fig. 3 shows that the data packet with PDCP COUNT=1 has timed out; the data packet with PDCP COUNT=3 is successfully received.

Situation two

When it is determined that the second data packet is successfully sent and the difference between the number of the second data packet and the lower boundary of the sliding window is greater than or equal to the length of the window, the position of the sliding window is kept unchanged.

Exemplarily, the meaning of the "difference between the number of the second data packet and the lower boundary of the sliding window" is as described above, and will not be repeated here.

Case 2 is shown in Figures 3 and 4. In Figure 3, the lower boundary of the sliding window is at PDCP COUNT=4, and the upper boundary of the sliding window is at PDCP COUNT=7. When receiving the indication that the data packet with PDCP COUNT=9 (corresponding to the above-mentioned second data packet) was successfully received, the difference between PDCP COUNT=9 and the lower boundary of the sliding window PDCP COUNT=4 is 5, which is larger than the window The length is 4, so the position of the sliding window is maintained without moving, see Figure 4 for details. In addition, Figure 4 shows that the data packet with PDCP COUNT=1 has timed out; the data packets with PDCP COUNT=3 and 9 are successfully received.

Situation three

When it is determined that the second data packet is successfully sent and the difference between the number of the second data packet and the lower boundary of the sliding window is less than the length of the window, the lower boundary of the sliding window is moved to the first The position of the number (see PDCP COUNT=10 in FIG. 5) of the first third data packet that was not successfully sent after the second data packet; where the number of the third data packet and the distance after the third data packet The difference between the number of the first successfully sent data packet (PDCP COUNT=14 in FIG. 5) is greater than or equal to the window length.

Optionally, in case three, in the process of moving the sliding window, if there is a successfully sent data packet in the sliding window, it is determined that the fourth data packet with the highest number is successfully sent, and the lower boundary of the sliding window is moved. To the numbered position of the first unsuccessfully sent data packet after the fourth data packet.

Similarly, the "difference between the number of the third data packet and the number of the first successfully transmitted data packet after the third data packet" has the same meaning as the above-mentioned " The meaning of "the difference between the number of the second data packet and the lower boundary of the sliding window" will not be repeated here.

Case 3 is shown in Figures 3 and 5. In Figure 3, the lower boundary of the sliding window is at PDCP COUNT=4, and the upper boundary of the sliding window is at PDCP COUNT=7. When receiving the indication that the data packet with PDCP COUNT=7 (corresponding to the above-mentioned second data packet) was successfully received, first, move (temporarily move) the sliding window to the lower boundary of the sliding window at PDCP COUNT= At this time, the upper boundary of the sliding window is at PDCP COUNT=11, because there are successfully sent data packets in the sliding window, that is, the data packet with PDCP COUNT=9 (corresponding to the fourth data packet above), continue to move The lower boundary from the sliding window to the sliding window is at PDCP COUNT=10. At this time, the upper boundary of the sliding window is at PDCP COUNT=13. There is no successfully sent data packet in the sliding window, see Figure 5 Show.

In Figure 5, it is shown that the data packet with PDCP COUNT=1 has timed out; the data packet with PDCP COUNT=3, 7, 9, and 14 are successfully received.

In other examples, it can be understood that if there are successfully sent data packets in the sliding window, that is, PDCP COUNT=10 and PDCP COUNT=13, you can continue to move the sliding window backward according to the aforementioned rules until it is in the sliding window. There is no data packet successfully sent.

Optionally, the successful transmission of the second data packet mentioned in the foregoing case 1 to case 3 includes at least one of the following:

1) The second data packet is successfully sent.

2) The opposite end entity (receiving end device) indicates that the second data packet is successfully received.

3) The underlying entity indicates that the second data packet is successfully received.

Exemplarily, the successful transmission of the second data packet may be for a protocol entity (such as a PDCP entity) maintaining the first timer to deliver the second data packet to the bottom layer (such as an RLC entity). It may also be that the second data packet is sent from the sending end device (for example, sent from the air interface).

The indication by the opposite-end entity that the second data packet is successfully received may be indicated through a status report. For example, the first timer is maintained at the PDCP layer, and the opposite PDCP entity is indicated by the PDCP status report, or the first timer is maintained at the RLC layer, and the corresponding RLC entity is indicated by the RLC status report.

The bottom layer entity indicating that the second data packet is successfully received may be through bottom layer HARQ feedback and/or bottom layer RLC feedback.

Through the sliding window introduced in the previous section, if the sending end device determines that the first timers corresponding to the N first data packets in the sliding window are all timed out, it determines that the sending of N consecutive first data packets has timed out, and can execute At least one of the following method one and method two:

method one

Adjust the logical priority configuration of the RB (such as DRB) corresponding to the data packet (which may include the aforementioned first data packet). This example is applicable to the case where the sending end device is a terminal device, and it is also applicable to the case where the sending end device is a network device.

In addition, in the case that the sending end device is a terminal device, the network device side may also implicitly or explicitly indicate the logical channel configuration to be used when the sending of N consecutive first data packets time out. For example, a network device provides two sets of

logical channel configurations

1 and 2 for a dedicated radio bearer (DRB). If there are N consecutive first data packets sent overtime in the DRB, the terminal device automatically adjusts logical channel configuration 1 to logical channel configuration 2, where the logical channel priority of logical channel configuration 2 can be higher than that of logical channel configuration 1. The priority of the logical channel. Exemplarily, after the sending end device sends a data packet corresponding to the timeout of the first timer (including the first data packet), the sending end device may also automatically adjust the logical channel configuration 2 back to the previous logical channel configuration 1.

In addition, when the sending end device is a terminal device, the sending end device may also receive the logical channel configuration sent by the network side after sending the instruction information to the network side. Exemplarily, the logical channel configuration 1 used by the sending end device before sending the instruction, and the logical channel configuration sent by the network side is adjusted to logical channel configuration 2.

Method Two

Send instructions to the network side. This example is suitable for the case where the sending end device is a terminal device, and the method for the terminal device to send instruction information to the network device side can be any of the following:

1) Send a scheduling request to the network device side. The indication information may be the scheduling request. Optionally, the scheduling request carries additional indication information, such as the amount of data and/or the remaining time. Optionally, the terminal device may send the scheduling request through a dedicated scheduling request (Scheduling Request, SR) resource, where the dedicated SR resource is configured on the network device side to provide a specific type of data packet (such as the first A data packet whose timer expires, or a data packet configured with the first timer) applies for a dedicated SR resource for uplink authorization. For a detailed introduction of the scheduling request, reference may be made to the related description in Embodiment 100.

2) Send a cache status report to the network device side. The indication information may be the cache status report. Optionally, the buffer status report carries additional indication information, such as the amount of data and/or the remaining time. For a detailed introduction of the cache status report, reference may be made to the related description in Embodiment 100.

3) Sending MAC layer signaling to the network device, such as a MAC control element (CE), the MAC CE may carry a logical channel identifier, which is used to indicate that the logical channel corresponding to the logical channel identifier has a first timer timeout Packets. The MAC-side signaling may also carry additional information, such as the amount of data and/or the remaining time, for example, the total data amount of the data packets in the logical channel 1 whose first timer has expired. Or, for example, the total data volume of the data packet with the remaining time of 0 in the logical channel 1 is 100 bytes, and the total data volume of the data packet with the remaining time of 0.5 ms in the logical channel 2 is 200 bytes. For a detailed introduction of the MAC layer signaling, reference may be made to the related description in Embodiment 100.

For the first timer mentioned in the first embodiment, the start timing of the first timer includes: after the data packet arrives; or, after a predetermined time after the data packet arrives.

The stop timing of the first timer includes at least one of the following:

1) The data packet corresponding to the first timer is successfully sent. For details, please refer to the foregoing introduction.

2) The peer entity indicates that the data packet corresponding to the first timer is successfully received.

3) The underlying entity indicates that the data packet corresponding to the first timer is successfully received.

Optionally, the first timer and the duration of the first timer are configured by the network device side. Additionally, the configuration granularity of the first timer may be each DRB or each Quality of Service (QoS) flow.

Exemplarily, the duration of the first timer may be configured as the Uu maximum transmission delay corresponding to DRB or QoS flow (such as packet delay budget, Packet Delay Budget, PDB). For the first timer, the terminal device may have the following behaviors:

1) When a data packet is received from the upper layer, the first timer corresponding to the data packet is started.

2) When the data packet is successfully sent, stop the first timer corresponding to the data packet; wherein, the successful data packet transmission may mean that the data packet is successfully received, and the sending end device determines the data The successful reception of the packet may be based on the indication of the underlying entity (such as RLC or HARQ) or based on the indication of the opposite entity (such as the PDCP status report).

In the second method above, the network device side receives the instruction information sent by the terminal device, and may also perform one or more of the following actions:

1) The network equipment side allocates the uplink authorization to the terminal equipment.

In addition, the uplink authorization carries indication information, and the indication information is used to indicate that the uplink authorization is suitable for use of a specific type of data packet, such as a data packet whose first timer expires, or a data packet configured with the first timer. Timer data packet.

2) Reconfiguration of logical channel priority configuration. For example, the logical channel priority configuration 1 corresponding to the DRB for which the consecutive N first data packets are sent overtime is adjusted to the logical channel priority configuration 2.

Example two

In the second embodiment, on the basis of the embodiment 100, it is also possible to determine whether consecutive N first data packet transmission timeouts occur through the running status of the timer.

The timer mentioned in the second embodiment includes a second timer and a third timer. Wherein, each data packet may correspond to a second timer, and the start timing of the second timer may include: after the data packet arrives; or, after a predetermined time after the data packet arrives. The start timing of the third timer includes: any one of the second timers expires. For a detailed introduction of "data packet arrival", reference may be made to the related description in Embodiment 100.

Optionally, in the case that the second timer expires and the third timer is running, the sending end device may also perform at least one of the following: not start the new third timer; do not restart all The third timer; keep the running third timer continuing to run.

Optionally, the stop timing of the second timer includes at least one of the following:

1) The data packet corresponding to the second timer is successfully sent;

2) The peer entity indicates that the data packet corresponding to the second timer is successfully received;

3) The underlying entity indicates that the data packet corresponding to the second timer is successfully received.

Exemplarily, the successful transmission of the data packet corresponding to the second timer may be for the protocol entity (such as the PDCP entity) maintaining the second timer to deliver the data packet to the bottom layer (such as the RLC entity). It can also be that the data packet is sent from the sending end device (for example, sent from the air interface).

The opposite entity indicates that the data packet corresponding to the second timer may be indicated by a status report. For example, the second timer is maintained at the PDCP layer, and the opposite PDCP entity is indicated by the PDCP status report, or the second timer is maintained at the RLC layer, and the corresponding RLC entity is indicated by the RLC status report.

The bottom layer entity indicating that the data packet corresponding to the second timer is successfully received may be through bottom layer HARQ feedback and/or bottom layer RLC feedback.

In an example, in a case where it is determined that the fifth data packet is successfully sent, the second timer corresponding to the fifth data packet is stopped.

The second embodiment determines whether consecutive N first data packets are sent overtime based on the running condition of the timer, including: if the third timer expires, determining that N consecutive first data packets are sent When the timeout expires, the adjustment data transmission strategy described in the foregoing embodiment 100 or the first embodiment can be executed subsequently.

During the running of the third timer, if it is determined that the fifth data packet is successfully sent, the third timer is stopped. Optionally, the second timer corresponding to the fifth data packet does not expire.

Exemplarily, during the operation of the third timer, if the receiving end reports that the fifth data packet has been successfully received, but at the sending end device, the second timer corresponding to the fifth data packet has expired, Then the third timer is not stopped. Conversely, if the receiving end reports that the fifth data packet has been successfully received, but at the sending end, the second timer corresponding to the fifth data packet does not expire, then the third timer is stopped.

The successful transmission of the fifth data packet mentioned above includes at least one of the following:

1) The fifth data packet is successfully sent;

2) The opposite entity indicates that the fifth data packet is successfully received;

3) The underlying entity indicates that the fifth data packet is to be received.

Exemplarily, the successful transmission of the fifth data packet may be for a protocol entity (such as a PDCP entity) that maintains the second timer and/or the third timer to submit the fifth data packet to the bottom layer (such as an RLC entity) . It may also be that the fifth data packet is sent from the sending end device (for example, sent from the air interface).

The indication by the opposite-end entity that the fifth data packet is successfully received may be indicated through a status report. For example, the second timer and/or third timer is maintained at the PDCP layer, and the opposite PDCP entity indicates through the PDCP status report, or the second timer and/or third timer is maintained at the RLC layer, and the corresponding RLC entity passes RLC status report indication.

The bottom layer entity indicating that the fifth data packet is successfully received may be through bottom layer HARQ feedback and/or bottom layer RLC feedback.

In order to describe the second embodiment in detail, the following will be described in conjunction with the embodiment shown in FIG. 6.

In this example, the sender device (such as the PDCP layer or the RLC layer) maintains two timers, which are the second timer and the third timer, respectively. The two timers and the timer duration can be configured by the network device side. Additionally, the configuration granularity of the two timers may be per DRB or per QoS flow.

Exemplarily, the duration of the second timer may be configured as the Uu maximum transmission delay corresponding to DRB or QoS flow; the duration of the third timer may be configured as the Uu port survival time corresponding to DRB or QoS flow. The Uu port survival time may be obtained by the mapping process of the survival time maintained by the application at the receiving end, and may be sent by the core network node to the access network node.

Exemplarily, suppose that when the Uu port does not receive the required (such as not in accordance with the configured QoS requirements) within the time period T and arrives at the receiving end device, the communication service will enter the unavailable state. At this time, the RAN can configure the third timer Time length T3<T, exemplary T3=T-maximum Uu port delay.

Among them, corresponding to the second timer, the sending end device (such as UE) behaves as follows:

1) The second timer is started when a data packet is received from the upper layer, or a predefined time after the data packet is received from the upper layer. For example, the PDCP layer of the UE maintains the second timer, and when the PDCP layer receives a data packet from the upper layer (such as the SDAP layer or the application layer), the second timer is started. Alternatively, the PDCP layer of the UE maintains the second timer, and when the PDCP layer receives the data packet from the upper layer (such as the SDAP layer or the application layer) for a preset period of time, it starts the second timer corresponding to the data packet (such as The data packet belongs to QoS flow 1, and the second timer corresponding to QoS flow 1 is started).

Refer to Figure 6 for details. In Figure 6, after the data packet corresponding to PDCP SN = 1 arrives, the corresponding second timer (timer2 in Figure 6) is started; after a certain transmission interval, PDCP SN = 2 corresponds to After the data packet arrives, the corresponding second timer is started; after a certain transmission interval, PDCP SN=3 and the corresponding data packet arrives, the corresponding second timer is started; after a certain transmission interval, PDCP SN = 4 After the corresponding data packet arrives, the corresponding second timer is started.

In Fig. 6, the second timers corresponding to PDCP SN=1, PDCP SN=3, and PDCP SN=4 all time out; the second timer corresponding to PDCP SN=2 does not time out.

2) When receiving an indication that the data packet is successfully received, stop the second timer corresponding to the data packet. For example, the PDCP layer of the UE maintains the second timer. When receiving the indication that the data packet corresponding to PDCP SN=2 was successfully received by the receiving end (such as the underlying RLC indication or the PDCP status report indication), the PDCP layer stops PDCP SN=2 The second timer corresponding to the corresponding data packet.

3) When the second timer expires, the third timer is started.

Referring to Fig. 6, for example, the PDCP layer of the UE maintains the second timer. When the second timer (timer2 in Fig. 6) of the data packet corresponding to PDCP SN=1 expires, the PDCP layer starts the third timer (in Fig. 6). Timer3). Or, for example, the RLC layer of the UE maintains the second timer, and when the second timer of the data packet corresponding to RLC SN=1 expires, the RLC layer starts the third timer.

Corresponding to the third timer, the behavior of the sending end device (such as UE) is at least one of the following:

1) When the second timer expires, start or restart the third timer.

For example, if the second timer of the data packet corresponding to PDCP SN=1 expires, the third timer is started. During the running of the third timer, the data packet corresponding to PDCP SN=1 is successfully received, and the PDCP layer stops. After the third timer, the second timer corresponding to the data packet corresponding to PDCP SN=3 times out, and the PDCP layer restarts the third timer. The "restart the third timer" indicates that the third timer starts to run from an initial value (such as 0).

2) During the operation of the third timer, if an indication that the data packet is successfully received is received, stop the third timer, wherein the second timer corresponding to the successfully received data packet does not expire.

For example, in Fig. 6, during the operation of the third timer, when receiving the indication that the data packet corresponding to PDCP SN=2 was successfully received by the receiving end (such as the underlying RLC indication or the PDCP status report indication), the PDCP layer stops the first Three timers, where the second timer corresponding to the data packet corresponding to PDCP SN=2 does not expire.

In each of the above examples, if the third timer expires, the sending end device can perform one or more of the following:

method one

Adjust the logical priority configuration of the RB (such as DRB) corresponding to the data packet. This example is applicable to the case where the sending end device is a terminal device, and it is also applicable to the case where the sending end device is a network device.

In addition, when the sending end device is a terminal device, the network device side may also implicitly or explicitly indicate the logical channel configuration used when the third timer expires. For example, a network device provides two sets of

logical channel configurations

1 and 2 for a dedicated radio bearer (DRB). If the third timer in the DRB expires, the terminal device automatically adjusts logical channel configuration 1 to logical channel configuration 2, where the logical channel priority of logical channel configuration 2 may be higher than the logical channel priority of logical channel configuration 1. Exemplarily, after the sending end device sends a data packet corresponding to the timeout of the third timer, the sending end device may also automatically adjust the logical channel configuration 2 back to the previous logical channel configuration 1.

Method Two

1) Send a scheduling request to the network device side. The indication information may be the scheduling request. Optionally, the scheduling request carries additional indication information, such as the amount of data and/or the remaining time. Optionally, the terminal device may send the scheduling request through a dedicated SR resource, where the dedicated SR resource is configured on the network device side to provide data packets of a specific type (such as the second timer or the third timer). Timeout data packets, or data packets configured with the second timer and third timer) apply for dedicated SR resources for uplink authorization. For a detailed introduction of the scheduling request, reference may be made to the related description in Embodiment 100.

2) Send a cache status report to the network device side. The indication information may be a buffer status report (such as short BSR, long BSR, etc.). The buffer status report may be different from the traditional buffer status report, for example, it can be distinguished by a logical channel ID. Optionally, the buffer status report carries additional indication information, such as the amount of data and/or the remaining time. For a detailed introduction of the cache status report, reference may be made to the related description in Embodiment 100.

3) Sending MAC layer signaling to the network device, such as a MAC control element (CE), the MAC CE may carry a logical channel identifier, which is used to indicate that the logical channel corresponding to the logical channel identifier has a third timer timeout Packets. The MAC-side signaling may also carry additional information, such as the amount of data and or the remaining time, for example, the total data amount of the data packets in the logical channel 1 whose second timer has expired. Or, for example, the total data volume of the data packet with the remaining time of 0 in the logical channel 1 is 100 bytes, and the total data volume of the data packet with the remaining time of 0.5 ms in the logical channel 2 is 200 bytes. Additionally, the MAC layer signaling can trigger SR. For a detailed introduction of the MAC layer signaling, reference may be made to the related description in Embodiment 100.

In addition, the uplink authorization carries indication information, and the indication information is used to indicate that the uplink authorization is applicable to a specific type of data packet use (such as a data packet whose second timer or third timer expires, or configuration There are data packets of the second timer and the third timer).

2) Reconfiguration of logical channel priority configuration. For example, the logical channel priority configuration 1 corresponding to the DRB where the third timer expires is adjusted to the logical channel priority configuration 2.

The data transmission method according to the embodiment of the present application is described in detail above with reference to FIG. 1 and FIG. 6. The data transmission method according to another embodiment of the present application will be described in detail below with reference to FIG. 7. The description from the network device side can refer to the description on the sending end device side above. To avoid repetition, the related description is appropriately omitted.

FIG. 7 is a schematic diagram of the implementation process of the data transmission method according to the embodiment of the present application, which can be applied to the network device side. As shown in FIG. 7, the method 700 includes at least one of the steps introduced in S702:

S702: Send first configuration information, where the first configuration information is used to indicate a logical channel configuration of a radio bearer corresponding to N consecutive first data packets whose sending has timed out;

Send uplink authorization;

The second configuration information is sent, and the second configuration information is used to reconfigure the logical channel configuration of the radio bearer corresponding to the N consecutive first data packets whose sending has timed out.

In the embodiment of the present application, the network device may send uplink authorization or send configuration information to ensure that the data packets of the sending end device (such as UE) reach the receiving end device within the survival time and improve the effectiveness of communication.

Optionally, as an embodiment, the method 700 further includes: receiving a first message, the first message being sent by the terminal device when it is determined that the sending of the N consecutive first data packets has timed out, so The first message includes at least one of the following:

Scheduling request

Cache status report;

MAC layer signaling.

Optionally, as an embodiment,

In a case where the first message includes the scheduling request, the scheduling request carries first indication information, and the first indication information carries at least one of a data amount and a remaining time;

In a case where the first message includes the buffer status report, the buffer status report carries second indication information, and the second indication information carries at least one of a data amount and a remaining time.

Optionally, as an embodiment, the uplink authorization carries third indication information, and the third indication information is used to indicate that the uplink authorization is used for a specific type of data packet, where the specific type of data packet includes Sending timeout or sending a packet that is about to time out.

The data transmission method according to the embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 7. The sender device according to the embodiment of the present application will be described in detail below with reference to FIG. 8.

Fig. 8 is a schematic structural diagram of a sending end device according to an embodiment of the present application. The sending end device may be a terminal device or a network device. As shown in FIG. 8, the sending end device 800 includes:

The adjustment module 802 may be used to adjust the data transmission strategy when it is determined that the sending of N consecutive first data packets is timed out, where N is an integer greater than 1.

Optionally, as an embodiment, in a case where the sending end device is a terminal device, the N is configured by a network device.

Optionally, as an embodiment,

The N consecutive first data packets are N consecutive first data packets; and/or

The N consecutive first data packets are N first data packets with consecutive arrival times.

Optionally, as an embodiment, the sending end device 800 further includes a determining module, which may be used to determine whether there are N consecutive sending timeouts of the first data packet through a sliding window, and the window length of the sliding window is equal to all the first data packets.述N.

Optionally, as an embodiment, the determining module determines, through a sliding window, whether N consecutive transmission timeouts of the first data packets occur, including: if the N first data packets in the sliding window correspond to If the first timers are all timed out, it is determined that the sending of the N consecutive first data packets is timed out.

Optionally, as an embodiment, the start timing of the first timer includes:

After the data packet arrives; or,

After a predetermined time after the data packet arrives.

Optionally, as an embodiment, the stop timing of the first timer includes at least one of the following:

The data packet corresponding to the first timer is successfully sent;

The opposite entity indicates that the data packet corresponding to the first timer is successfully received;

The underlying entity indicates that the data packet corresponding to the first timer is successfully received.

Optionally, as an embodiment, the sending end device 800 further includes a mobile module, which can be used to determine that the second data packet is successfully sent and the difference between the number of the second data packet and the lower boundary of the sliding window If it is less than the length of the window, move the lower boundary of the sliding window to the numbered position of the first unsuccessful third data packet after the second data packet.

Optionally, as an embodiment, the successful sending of the second data packet includes at least one of the following:

The second data packet is successfully sent;

The opposite entity indicates that the second data packet is successfully received;

The underlying entity indicates that the second data packet is successfully received.

Optionally, as an embodiment, the sending end device 800 further includes a mobile module, which can be used to determine that the second data packet is successfully sent and the difference between the number of the second data packet and the lower boundary of the sliding window If it is greater than or equal to the length of the window, keep the position of the sliding window unchanged.

Optionally, as an embodiment, the sending end device 800 further includes a mobile module, which can be used to determine that the second data packet is successfully sent and the difference between the number of the second data packet and the lower boundary of the sliding window If the length is less than the window length, move the lower boundary of the sliding window to the position of the numbered position of the first third data packet that was not successfully sent after the second data packet;

Wherein, the difference between the number of the third data packet and the number of the first successfully transmitted data packet after the third data packet is greater than or equal to the window length.

Optionally, as an embodiment, in the process of moving the sliding window, if there is a successfully sent data packet in the sliding window, it is determined that the fourth data packet that is successfully sent and the largest number is sent, and the sliding window is moved From the lower boundary of to the numbered position of the first unsuccessfully sent data packet after the fourth data packet.

Optionally, as an embodiment, the sliding window includes an initial lower boundary and an initial upper boundary; wherein, the initial lower boundary is located at the position of the number of the initially transmitted data packet, and the initial upper boundary is a distance from the initial The numbered position of the lower boundary N data packets.

Optionally, as an embodiment, the sliding window includes an initial lower boundary and an initial upper boundary; wherein, the initial lower boundary is located at a position numbered 0 of the data packet, and the initial upper boundary is a distance from the initial lower boundary. The numbered position of the N data packets on the boundary.

Optionally, as an embodiment, the sending end device 800 further includes a determining module, which may be used to determine whether consecutive N first data packets are sent overtime based on the running status of a timer.

Optionally, as an embodiment, the timer includes a second timer and a third timer.

Optionally, as an embodiment, the start timing of the second timer includes:

After the data packet arrives; or,

After a predetermined time after the data packet arrives.

Optionally, as an embodiment, the start timing of the third timer includes: the second timer expires.

Optionally, as an embodiment, when the second timer expires and the third timer is running, the sending end device 800 further includes a timer control module, which can be used to:

Do not start the new said third timer; or,

The third timer is not restarted.

Optionally, as an embodiment, the stop timing of the second timer includes at least one of the following:

The data packet corresponding to the second timer is successfully sent;

The opposite entity indicates that the data packet corresponding to the second timer is successfully received;

The underlying entity indicates that the data packet corresponding to the second timer is successfully received.

Optionally, as an embodiment, the determining whether consecutive N first data packet transmission timeouts occur through the running condition of a timer includes: if the third timer times out, determining consecutive N first data packets The sending of the first data packet times out.

Optionally, as an embodiment, the sending end device 800 further includes a timer control module, which may be used to stop the second timing corresponding to the fifth data packet in a case where it is determined that the fifth data packet is successfully sent. Device.

Optionally, as an embodiment, the sender device 800 further includes a timer control module, which may be used to: during the running of the third timer, if it is determined that the fifth data packet is successfully sent, stop the third timing Device.

Optionally, as an embodiment, the successful transmission of the fifth data packet includes at least one of the following:

The fifth data packet is successfully sent;

The opposite entity indicates that the fifth data packet is successfully received;

The underlying entity indicates that the fifth data packet is to be received.

Optionally, as an embodiment, the second timer corresponding to the fifth data packet does not expire.

Optionally, as an embodiment, the adjustment module 802 adjusting the data transmission strategy includes at least one of the following:

Adjusting the logical channel configuration of the radio bearer corresponding to the first data packet;

Receive uplink authorization.

Optionally, as an embodiment, the sending end device 800 further includes a receiving module, which may be used to receive first configuration information, where the first configuration information is used to indicate that N consecutive sending timeouts correspond to the first data packet The logical channel configuration of the radio bearer.

Optionally, as an embodiment, in a case where the sending end device is a terminal device, the adjusting the data transmission strategy includes at least one of the following:

Send a scheduling request to the network device;

Send a cache status report to the network device;

Send media access control MAC layer signaling to the network device.

Optionally, as an embodiment,

In the case of sending a scheduling request to the network device, the scheduling request carries first indication information, and the first indication information carries at least one of a data amount and a remaining time;

In the case of sending a cache status report to a network device, the cache status report carries second indication information, and the second indication information carries at least one of a data amount and a remaining time.

Optionally, as an embodiment, the sending end device 800 further includes a receiving module, which may be used for at least one of the following:

Receive uplink authorization;

Receiving second configuration information, where the second configuration information is used to reconfigure the logical channel configuration corresponding to the first data packet.

Optionally, as an embodiment, the uplink authorization mentioned in each of the foregoing examples carries third indication information, and the third indication information is used to indicate that the uplink authorization is used for a specific type of data packet, where the specific Types of data packets include sending timeout or sending data packets that are about to time out.

The sender device 800 according to the embodiment of the present application may refer to the flow of the method 100 in the embodiment of the present application, and each unit/module in the sender device 800 and the other operations and/or functions mentioned above are used to implement the method 100 Corresponding process, and can achieve the same or equivalent technical effect, for the sake of brevity, it will not be repeated here.

Fig. 9 is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in FIG. 9, the network device 900 includes: a sending module 902, which can be used for at least one of the following:

Sending first configuration information, where the first configuration information is used to indicate a logical channel configuration of a radio bearer corresponding to N consecutive first data packets whose sending has timed out;

Send uplink authorization;

Sending second configuration information, where the second configuration information is used to reconfigure the logical channel configuration of the radio bearer corresponding to the N consecutive first data packets whose sending has timed out.

Optionally, as an embodiment, the network device 900 further includes a receiving module, which may be configured to receive a first message, where the first message is when the terminal device determines that the sending of N consecutive first data packets has timed out Sent, the first message includes at least one of the following:

Scheduling request

Cache status report;

MAC layer signaling.

Optionally, as an embodiment,

In a case where the first message includes the cache status report, the cache status report carries second indication information, and the second indication information carries at least one of a data amount and a remaining time.

The network device 900 according to the embodiment of the present application can refer to the process of the method 700 corresponding to the embodiment of the present application, and each unit/module in the network device 900 and the other operations and/or functions described above are used to implement the corresponding methods in the method 700. The process, and can achieve the same or equivalent technical effect, for the sake of brevity, it will not be repeated here.

The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.

When an indefinite or definite article is used when referring to a feature or noun (for example, "一", "这"), the article used does not limit the number of the feature or noun, that is, unless otherwise In addition to specifically stating that the feature or noun is one, it does not exclude the fact that the feature or noun includes more than one.

In addition, the terms "first", "second", and "third" are used in the description and claims to distinguish between similar data packets or timers, and these terms do not necessarily describe the order or time sequence. It should be understood that the terms so used are interchangeable under appropriate circumstances, and the embodiments of the application described herein can be operated in other orders than those described or illustrated herein.

Fig. 10 is a block diagram of a terminal device according to another embodiment of the present application. The terminal device 1000 shown in FIG. 10 includes: at least one processor 1001, a memory 1002, at least one network interface 1004, and a user interface 1003. The various components in the terminal device 1000 are coupled together through the bus system 1005. It can be understood that the bus system 1005 is used to implement connection and communication between these components. In addition to the data bus, the bus system 1005 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear description, various buses are marked as the bus system 1005 in FIG. 10.

Wherein, the user interface 1003 may include a display, a keyboard, a pointing device (for example, a mouse, a trackball), a touch panel or a touch screen, etc.

It can be understood that the memory 1002 in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate SDRAM, DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), Synchronous Link Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) And Direct Rambus RAM (DRRAM). The memory 1002 of the system and method described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

In some embodiments, the memory 1002 stores the following elements, executable modules or data structures, or a subset of them, or an extended set of them: operating system 10021 and application programs 10022.

Among them, the operating system 10021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks. The application program 10022 includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services. The program for implementing the method of the embodiment of the present application may be included in the application program 10022.

In the embodiment of the present application, the terminal device 1000 further includes: instructions or programs that are stored in the memory 1002 and run on the processor 1001. The instructions or programs are executed by the processor 1001 to implement the steps of the method embodiment 100 as follows.

The methods disclosed in the foregoing embodiments of the present application may be applied to the processor 1001 or implemented by the processor 1001. The processor 1001 may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the foregoing method can be completed by an integrated logic circuit of hardware in the processor 1001 or instructions in the form of software. The aforementioned processor 1001 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature readable storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The readable storage medium is located in the memory 1002, and the processor 1001 reads the information in the memory 1002, and completes the steps of the foregoing method in combination with its hardware. Specifically, instructions or programs are stored on the readable storage medium, and when the instructions or programs are executed by the processor 1001, the steps of the above-mentioned method embodiment 100 are implemented.

It can be understood that the embodiments described in the embodiments of the present application may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application specific integrated circuits (ASIC), digital signal processor (Digital Signal Processing, DSP), digital signal processing equipment (DSP Device, DSPD), programmable Logic device (Programmable Logic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, and others for performing the functions described in this application Electronic unit or its combination.

For software implementation, the technology described in the embodiments of the present application can be implemented by modules (for example, procedures, functions, etc.) that execute the functions described in the embodiments of the present application. The software codes can be stored in the memory and executed by the processor. The memory can be implemented in the processor or external to the processor.

The terminal device 1000 can implement each process implemented by the sending end device in the foregoing embodiment, and can achieve the same or equivalent technical effects. To avoid repetition, details are not described herein again.

Please refer to FIG. 11. FIG. 11 is a structural diagram of a network device applied in an embodiment of the present application, which can implement the details of the

method embodiments

100 and 700 and achieve the same effect. As shown in Figure 11, the network device 1100 includes: a processor 1101, a transceiver 1102, a memory 1103, and a bus interface, where:

In the embodiment of the present application, the network device 1100 further includes: instructions or programs that are stored in the memory 1103 and can be run on the processor 1101. The instructions or programs are executed by the processor 1101 to implement the steps of the

method embodiments

100 and 700. .

In FIG. 11, the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 1101 and various circuits of the memory represented by the memory 1103 are linked together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further descriptions are provided herein. The bus interface provides the interface. The transceiver 1102 may be a plurality of elements, including a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium.

The processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 can store data used by the processor 1101 when performing operations.

The embodiment of the present application also provides a readable storage medium, the readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, it implements any one of the above method embodiment 100 and method embodiment 700. Each process of the embodiment can achieve the same technical effect, and in order to avoid repetition, it will not be repeated here.

Wherein, the processor is the processor in the electronic device described in the foregoing embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk.

An embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or an instruction to implement the above method embodiment 100 and method Each process of any method embodiment in the embodiment 700 can achieve the same technical effect. In order to avoid repetition, it will not be repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-level chips, system-on-chips, system-on-chips, or system-on-chips.

It should be noted that in this article, the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, It also includes other elements that are not explicitly listed, or elements inherent to the process, method, article, or device. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, article, or device that includes the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. The functions are performed, for example, the described method may be performed in a different order from the described order, and various steps may also be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the description of the above implementation manners, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present application.

The embodiments of the application are described above with reference to the accompanying drawings, but the application is not limited to the above-mentioned specific embodiments. The above-mentioned specific embodiments are only illustrative and not restrictive. Those of ordinary skill in the art are Under the enlightenment of this application, many forms can be made without departing from the purpose of this application and the scope of protection of the claims, all of which fall within the protection of this application.

Claims

A data transmission method, the method includes:

In the case where it is determined that the sending of N consecutive first data packets has timed out, the sending end device adjusts the data transmission strategy, and N is an integer greater than 1.
The method according to claim 1, wherein, in a case where the sending end device is a terminal device, the N is configured by a network device.
The method of claim 1, wherein:

The N consecutive first data packets are N consecutive first data packets; and/or,

The N consecutive first data packets are N first data packets with consecutive arrival times.
The method according to claim 1, wherein the method further comprises:

The sending end device determines whether there are N consecutive sending timeouts of the first data packet through a sliding window, and the window length of the sliding window is equal to the N.
The method according to claim 4, wherein the sending end device determines whether there are N consecutive sending timeouts of the first data packet through a sliding window, comprising:

If the first timers corresponding to the N first data packets in the sliding window all time out, the sending end device determines that the sending of the N consecutive first data packets has timed out.
The method according to claim 5, wherein the starting timing of the first timer comprises:

After the data packet arrives; or,

After a predetermined time after the data packet arrives.
The method according to claim 5, wherein the stop timing of the first timer includes at least one of the following:

The data packet corresponding to the first timer is successfully sent;

The opposite entity indicates that the data packet corresponding to the first timer is successfully received;

The underlying entity indicates that the data packet corresponding to the first timer is successfully received.
The method according to claim 4 or 5, wherein the method further comprises:

In the case where it is determined that the second data packet is sent successfully and the difference between the number of the second data packet and the lower boundary of the sliding window is less than the length of the window, the sending end device moves the lower boundary of the sliding window. From the boundary to the numbered position of the first unsuccessful third data packet after the second data packet.
The method according to claim 8, wherein the successful transmission of the second data packet comprises at least one of the following:

The second data packet is successfully sent;

The opposite entity indicates that the second data packet is successfully received;

The underlying entity indicates that the second data packet is successfully received.
The method according to claim 4 or 5, wherein the method further comprises:

In a case where it is determined that the second data packet is successfully sent and the difference between the number of the second data packet and the lower boundary of the sliding window is greater than or equal to the length of the window, the sending end device maintains the sliding window The position does not move.
The method according to claim 4 or 5, wherein the method further comprises:

In the case where it is determined that the second data packet is sent successfully and the difference between the number of the second data packet and the lower boundary of the sliding window is less than the length of the window, the sending end device moves the lower boundary of the sliding window. From the boundary to the numbered position of the first unsuccessful third data packet after the second data packet;

Wherein, the difference between the number of the third data packet and the number of the first successfully transmitted data packet after the third data packet is greater than or equal to the window length.
The method according to claim 11, wherein:

In the process of moving the sliding window, if there is a successfully sent data packet in the sliding window, the sending end device determines that the fourth data packet with the highest number is successfully sent, and moves the lower boundary of the sliding window to The numbered position of the first unsuccessfully sent data packet after the fourth data packet.
The method according to claim 4, wherein the sliding window includes an initial lower boundary and an initial upper boundary; wherein the initial lower boundary is located at the position of the number of the initially transmitted data packet, and the initial upper boundary is the distance Describe the numbered positions of the N data packets at the initial lower boundary.
The method according to claim 4, wherein the sliding window includes an initial lower boundary and an initial upper boundary; wherein the initial lower boundary is located at a position numbered 0 of the data packet, and the initial upper boundary is a distance from the The numbered position of the initial lower boundary N data packets.
The method according to claim 1, wherein the method further comprises:

Based on the running status of the timer, the sending end device determines whether there are N consecutive sending timeouts of the first data packet.
The method according to claim 15, wherein the timer includes a second timer and a third timer.
The method according to claim 16, wherein the start timing of the second timer comprises:

After the data packet arrives; or,

After a predetermined time after the data packet arrives.
The method according to claim 16, wherein the start timing of the third timer comprises:

The second timer expires.
The method according to claim 18, wherein, when the second timer expires and the third timer is running, the method further comprises:

The sending end device does not start the new third timer; or,

The sending end device does not restart the third timer.
The method according to claim 16, wherein the stop timing of the second timer includes at least one of the following:

The data packet corresponding to the second timer is successfully sent;

The opposite entity indicates that the data packet corresponding to the second timer is successfully received;

The underlying entity indicates that the data packet corresponding to the second timer is successfully received.
The method according to claim 18, wherein the determining by the sending end device whether there are N consecutive sending timeouts of the first data packet through the running condition of the timer comprises:

If the third timer times out, the sending end device determines that N consecutive sending of the first data packet times out.
The method according to claim 16, wherein the method further comprises:

In a case where it is determined that the fifth data packet is successfully sent, the sending end device stops the second timer corresponding to the fifth data packet.
The method according to claim 18, wherein the method further comprises:

During the running of the third timer, if it is determined that the fifth data packet is successfully sent, the sending end device stops the third timer.
The method according to claim 22 or 23, wherein the successful transmission of the fifth data packet includes at least one of the following:

The fifth data packet is successfully sent;

The opposite entity indicates that the fifth data packet is successfully received;

The underlying entity indicates that the fifth data packet is to be received.
The method according to claim 23, wherein the second timer corresponding to the fifth data packet does not expire.
The method according to claim 1, wherein said adjusting a data transmission strategy comprises at least one of the following:

Adjusting the logical channel configuration of the radio bearer corresponding to the first data packet;

Receive uplink authorization.
The method according to claim 26, wherein, before the sending end device adjusts the data transmission strategy, the method further comprises:

The transmitting end device receives first configuration information, where the first configuration information is used to indicate a logical channel configuration of a radio bearer corresponding to the first data packet whose transmission times out in a row.
The method according to claim 1, wherein, when the sending end device is a terminal device, adjusting the data transmission strategy by the sending end device comprises at least one of the following:

The sending end device sends a scheduling request to the network device;

The sending end device sends a buffer status report to the network device;

The sending end device sends media access control MAC layer signaling to the network device.
The method of claim 28, wherein:

In the case of sending a scheduling request to the network device, the scheduling request carries first indication information, and the first indication information carries at least one of a data amount and a remaining time;

In the case of sending a cache status report to a network device, the cache status report carries second indication information, and the second indication information carries at least one of a data amount and a remaining time.
The method according to claim 28, wherein the method further comprises at least one of the following:

The sending end device receives the uplink authorization;

The sending end device receives second configuration information, where the second configuration information is used to reconfigure the logical channel configuration corresponding to the first data packet.
The method according to claim 26 or 30, wherein the uplink authorization carries third indication information, and the third indication information is used to indicate that the uplink authorization is used for a specific type of data packet, wherein the specific type The data packets include sending timeout or sending data packets that are about to time out.
A data transmission method, the method includes at least one of the following:

The network device sends first configuration information, where the first configuration information is used to indicate a logical channel configuration of a radio bearer corresponding to N consecutive first data packets whose sending timeouts;

The network device sends an uplink authorization;

The network device sends second configuration information, where the second configuration information is used to reconfigure the logical channel configuration of the radio bearer corresponding to the N consecutive first data packets whose sending has timed out.
The method according to claim 32, wherein the method further comprises:

The network device receives a first message, the first message being sent by the terminal device when it is determined that the sending of N consecutive first data packets has timed out, and the first message includes at least one of the following:

Scheduling request

Cache status report;

MAC layer signaling.
The method of claim 33, wherein:

In a case where the first message includes the scheduling request, the scheduling request carries first indication information, and the first indication information carries at least one of a data amount and a remaining time;

In a case where the first message includes the cache status report, the cache status report carries second indication information, and the second indication information carries at least one of a data amount and a remaining time.
The method according to claim 32, wherein the uplink authorization carries third indication information, and the third indication information is used to indicate that the uplink authorization is used for a specific type of data packet, wherein the specific type of data Packets include sending timeouts or sending data packets that are about to time out.
A sender device, including:

The adjustment module is used to adjust the data transmission strategy when it is determined that the sending of N consecutive first data packets is timed out, where N is an integer greater than 1.
A network device, including a sending module, used for at least one of the following:

Sending first configuration information, where the first configuration information is used to indicate a logical channel configuration of a radio bearer corresponding to N consecutive first data packets whose sending has timed out;

Send uplink authorization;

Sending second configuration information, where the second configuration information is used to reconfigure the logical channel configuration of the radio bearer corresponding to the N consecutive first data packets whose sending has timed out.
A communication device, comprising: a memory, a processor, and instructions or programs stored on the memory and capable of running on the processor, and the instructions or programs are executed by the processor to implement as claimed in claims 1 to 35. The data transmission method described in any one of 35.
A readable storage medium on which instructions or programs are stored, and when the instructions or programs are executed by a processor, the data transmission method according to any one of claims 1 to 35 is realized.
A chip comprising a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used to run a program or an instruction to implement the one described in any one of the first aspect and the second aspect Data transfer method.
A computer program product that is executed by at least one processor to implement the data transmission method according to any one of claims 1 to 31, or to implement the data transmission method according to any one of claims 32 to 35 Data transmission method.
A sender device, comprising the sender device configured to execute the data transmission method according to any one of claims 1 to 31.
A network device, comprising the network device configured to execute the data transmission method according to any one of claims 32 to 25.