CN113708889A

CN113708889A - Data transmission method and device

Info

Publication number: CN113708889A
Application number: CN202010444358.9A
Authority: CN
Inventors: 张艳霞
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-05-22
Filing date: 2020-05-22
Publication date: 2021-11-26
Also published as: WO2021233401A1

Abstract

The embodiment of the application discloses a data transmission method and equipment, which are used for solving the problem that a sending terminal device cannot determine whether related applications of a receiving terminal device are about to enter an unavailable state or not, and further cannot provide an effective strategy to ensure that a data packet reaches the receiving terminal device within the survival time as far as possible. The method may be performed by a sending end device, and includes: and under the condition that the sending time-out of N continuous first data packets is determined, adjusting a data transmission strategy, wherein N is an integer larger than 1.

Description

Data transmission method and device

Technical Field

The embodiment of the application relates to the field of communication, in particular to a data transmission method and device.

Background

The availability of communication services is an important service performance requirement indicator for many automation function applications, especially for applications with deterministic traffic flow. In an industrial environment, many automation function applications have high communication service availability requirements, such as mobile control, which is 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 (e.g., a survival time), the (automation function) application of the receiving end device will enter an unavailable state.

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

Disclosure of Invention

An object of the embodiments of the present application is to provide a data transmission method and device, so as to solve a problem that a sending end device cannot determine whether a relevant application of a receiving end device is about to enter an unavailable state, and further cannot provide an effective policy to ensure that a data packet reaches the receiving end device within a survival time as much as possible.

In a first aspect, a data transmission method is provided, where the method is performed by a sending end device, and the method includes: and under the condition that the sending time-out of N continuous first data packets is determined, adjusting a data transmission strategy, wherein N is an integer larger than 1.

In a second aspect, a data transmission method is provided, where the method is performed by a network device, and the method includes at least one of: sending first configuration information, wherein the first configuration information is used for indicating the logical channel configuration of the radio bearer corresponding to the continuous N first data packets which are sent overtime; sending an uplink authorization; and sending second configuration information, wherein the second configuration information is used for reconfiguring the logical channel configuration of the radio bearer corresponding to the continuous N first data packets which are sent overtime.

In a third aspect, a sending end device is provided, which includes: and the adjusting module is used for adjusting the data transmission strategy under the condition of determining that the sending of the continuous N first data packets is overtime, wherein N is an integer larger than 1.

In a fourth aspect, a network device is provided, where the network device includes a sending module configured to at least one of: sending first configuration information, wherein the first configuration information is used for indicating the logical channel configuration of the radio bearer corresponding to the continuous N first data packets which are sent overtime; sending an uplink authorization; and sending second configuration information, wherein the second configuration information is used for reconfiguring the logical channel configuration of the radio bearer corresponding to the continuous N first data packets which are sent overtime.

In a fifth aspect, a sending end device is provided, where the sending end device includes a processor, a memory, and instructions or programs stored on the memory and executable on the processor, and the instructions or programs, when executed by the processor, implement the steps of the data transmission method according to the first aspect.

A sixth aspect provides a network device comprising a processor, a memory, and instructions or programs stored on the memory and executable on the processor, the instructions or programs, when executed by the processor, implementing the data transmission method according to any one of the first and second aspects.

In a seventh aspect, a readable storage medium is provided, on which instructions or a program are stored, which when executed by a processor implement the data transmission method according to any one of the first and second aspects.

In an eighth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the data transmission method according to any one of the first aspect and the second aspect.

In this embodiment of the present application, when it is determined that N consecutive first data packets are overtime, the sending end device considers that a related application of the receiving end device is about to enter an unavailable state, and further adjusts a data transmission policy, for example, to improve a priority of a logical channel corresponding to the first data packet; and receiving uplink authorization and the like specially used for transmitting the first data packet so as to ensure that the data packet reaches the receiving terminal equipment within the survival time as much as possible and improve the communication effectiveness.

Drawings

FIG. 1 is a schematic flow chart diagram of a data transmission method according to one embodiment of the present application;

FIG. 2 is a schematic view of a sliding window initial state according to one embodiment of the present application;

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

FIG. 4 is a schematic view of a sliding window without moving, according to an embodiment of the present application;

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

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

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

fig. 8 is a schematic structural diagram of a transmitting-end device according to an embodiment of the present application;

FIG. 9 is a block diagram of a network device according to one embodiment of the present application;

FIG. 10 is a block diagram of a terminal device according to one 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 Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

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

In the embodiment of the present application, the Terminal device may include, but is not limited to, a Mobile Station (MS), a Mobile Terminal (Mobile Terminal), a Mobile phone (Mobile Telephone), a User Equipment (UE), a handset (handset), a portable device (portable Equipment), a vehicle (vehicle), and the like, and the Terminal device may communicate with one or more core networks through a Radio Access Network (RAN), for example, the Terminal device may be a Mobile phone (or referred to as a "cellular" phone), a computer with a wireless communication function, and the Terminal device may also be a portable, pocket, handheld, computer-embedded, or vehicle-mounted Mobile apparatus.

In the embodiment of the present application, a network device is an apparatus deployed in a radio access network to provide a wireless communication function for a terminal device. The network device may be a base station, and the base station may include various macro base stations, micro base stations, relay stations, access points, and the like. In systems employing different radio access technologies, the names of devices having a base station function may differ. For example, in an LTE network, referred to as an Evolved node B (eNB or eNodeB), in a third Generation (3rd Generation, 3G) network, referred to as a node B (node B), in a 5G system, referred to as a next Generation node B (gnb), or a network device in a later Evolved communication system, etc., the terms are not limited.

As shown in fig. 1, an embodiment of the present application provides a data transmission method 100, where the method 100 may be executed by a sending-end device, in other words, the method 100 may be executed by software or hardware installed on the sending-end device, and the method includes the following steps.

S102: and under the condition that the sending time-out of N continuous first data packets is determined, adjusting a data transmission strategy, wherein N is an integer larger than 1.

The sending end device mentioned in the embodiments of the present application may be a terminal device (e.g., UE) or a network device (e.g., gNB). Under the condition that the sending terminal device is the terminal device, N can be configured by the network device or agreed by a protocol; in the case that the sending end device is a network device, N may be autonomously determined by the network device or agreed by a protocol.

In this embodiment, each first packet may correspond to a timer, and the timer is configured to determine whether the first packet is sent out for a time-out, where the timer is started at the time when the packet (including the aforementioned first packet, and other packets, etc.) arrives, or after a predetermined time elapses after the packet arrives. The "packet arrival" may be understood as a packet arriving from an upper layer to a protocol layer maintaining the timer, or may be understood as a packet received from an upper layer by a protocol layer maintaining the timer. In one example, a Packet Data Convergence Protocol (PDCP) layer of the sending end device maintains the timer, and the timer is started when the first Packet arrives at the PDCP layer from an upper layer (e.g., an SDAP layer or an application layer). In another example, a Packet Data Convergence Protocol (PDCP) layer of the sending end device maintains the timer, and the PDCP layer starts the timer when receiving a first Packet from an upper layer (e.g., an SDAP layer or an application layer).

In this embodiment, the consecutive N first packets may be N numbered consecutive first packets; or a first packet in which N arrival times (e.g., arrival times at a certain protocol layer) are consecutive; it is also possible to have N first packets with consecutive numbers and consecutive arrival times.

For the above-mentioned numbering, for example, when the Packet Data Convergence Protocol (PDCP) layer of the sending end device maintains the above timer, the numbering may be a PDCP COUNT value (i.e., COUNT), a PDCP Sequence Number (SN), or the like. In another example, when the Radio Link Control (RLC) layer of the sending end device maintains the timer, the Number may be an RLC Sequence Number (SN) or the like.

Optionally, the adjusting the data transmission policy mentioned in this embodiment includes at least one of:

1) and adjusting 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, so that the first data packet is sent in time, the application of the receiving end device is prevented from entering an unavailable state, and the communication effectiveness is improved.

Optionally, before adjusting the data transmission policy, the method 100 further includes: and receiving first configuration information, where the first configuration information is used to indicate logical channel configurations of radio bearers corresponding to the consecutive N sending overtime first data packets. For example, the 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 with transmission time-out in the DRB, the terminal device automatically adjusts the logical channel configuration 1 to the logical channel configuration 2, where the logical channel priority of the logical channel configuration 2 may be higher than the logical channel priority of the logical channel configuration 1.

2) And receiving an uplink authorization.

The uplink grant may be used to transmit a specific type of data packet, where the specific type of data packet includes a data packet that is sent out for a timeout (e.g., the first data packet mentioned above) or is to be sent out for a timeout, so as to prevent an application of the receiving end device from entering an unavailable state, and improve the communication efficiency.

Optionally, in a case that the sending end device is a terminal device, the adjusting data transmission policy includes at least one of the following:

1) a scheduling request is sent to the network device. Optionally, the scheduling request carries first indication information, where the first indication information carries at least one of a data amount to be sent and a remaining time. For example, Scheduling Request (SR) resources for transmitting a Scheduling Request and a logical channel are corresponding, and the transmitting-end device detects that a plurality of consecutive first data packets are transmitted overtime, and may transmit the Scheduling Request through the SR resources corresponding to the logical channel of the plurality of consecutive first data packets. The network device side can judge which or which logical channel corresponds to the data packet with the transmission timeout through the SR resource. For example, the scheduling request may further carry information of a data amount and a remaining time, where the remaining time may indicate a remaining time that is a time-out time of the timer (the remaining time may be an absolute time value, or a range value of the remaining time, such as a range value 1 corresponding to 1ms to 2ms, and a range value 2 corresponding to 2ms to 3 ms), and the data amount may indicate a 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 scheduling request carrying the first indication information may also be triggered in a normal case, that is, not sent when the UE detects that the sending of the consecutive N first data packets is overtime, where the normal case may be a case where high-priority data arrives but BSR cannot be sent.

2) And sending the buffer status report to the network equipment. Optionally, the buffer status report carries second indication information, where the second indication information carries at least one of the buffered data amount and the remaining time. For example, the buffer status report may further carry information of a data amount and a remaining time, where the remaining time may indicate a remaining time that is a time-out time of the timer (the remaining time may be an absolute time value, or a range value of the remaining time, such as a range value 1 corresponding to 1ms to 2ms, and a range value 2 corresponding to 2ms to 3 ms), and the data amount may indicate a 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 may also be triggered in a normal case, that is, the buffer status report is not sent when the UE detects that the sending of the consecutive N first data packets is overtime, where the normal case may be when high-priority data arrives.

3) Media Access Control (MAC) layer signaling (e.g., MAC CE) is sent to the network device. Optionally, the MAC layer signaling may carry a logical channel identifier, which is used to indicate that a logical channel corresponding to the logical channel identifier has a data packet with a timeout. Additionally, the MAC layer signaling may trigger SR. For example, when the sending end detects that N consecutive first data packets are overtime, it needs to send an MAC layer signaling (e.g., MAC CE) to the network device side, but there is no resource (e.g., PUSCH resource) for sending the MAC layer signaling, and then the sending end device may trigger the SR.

In this embodiment, by implementing a combination of one or more of the three embodiments, the network device may allocate an uplink grant to the terminal device, where the uplink grant may be used to transmit a data packet that is sent overtime or is about to be overtime, so as to prevent the application of the receiving end device from entering an unavailable state, and improve the communication effectiveness.

Optionally, the uplink grant mentioned in the above multiple examples may carry third indication information, where the third indication information is used to indicate that the uplink grant is used for a specific type of data packet, where the specific type of data packet includes a data packet that is sent overtime or is about to be overtime.

In this embodiment, by implementing a combination of one or more of the above three embodiments, the network device may further send second configuration information, where the second configuration information is used to reconfigure a logical channel configuration 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, so that the first data packet is sent in time, the application of the receiving end device is prevented from entering an unavailable state, and the communication effectiveness is improved.

In the data transmission method provided in the embodiment of the present application, when it is determined that N consecutive first data packets are overtime, the sending end device considers that a relevant application of the receiving end device is about to enter an unavailable state, and further adjusts a data transmission policy, for example, improves a priority of a logical channel corresponding to the first data packet; and receiving uplink authorization and the like specially used for transmitting the first data packet so as to ensure that the data packet reaches the receiving terminal equipment within the survival time as much as possible and improve the communication effectiveness.

To describe the data transmission method provided in the above embodiments of the present application in detail, the following description will be made with reference to two specific embodiments.

Example one

The first embodiment may further determine whether consecutive N first data packet transmission time-outs occur through a sliding window based on the first embodiment 100, where the window length of the sliding window is equal to N.

In this embodiment, if the first timers corresponding to the N first packets in the sliding window all time out, it is determined that the consecutive N first packets are timed out to be sent, where each first packet may correspond to one first timer.

In this embodiment, a sending end device, for example, a PDCP layer or a Radio Link Control (RLC) layer of the sending end device, may maintain a sliding window, where a window length N of the sliding window may be configured by a network device, and may also be a protocol convention. In one example, the sending end device is a terminal device, and the network device configures a sliding window with a window length of N, which corresponds to N data packets.

In one example, when M consecutive packets of the Uu port do not arrive at the receiving device as required (e.g., do not meet the configured QoS requirement), the communication service or application enters an unavailable state, and the access network may configure N to be an integer value smaller than M, for example, N ═ M-1.

The sliding window includes an initial state, and in one example, the sliding window includes an initial lower boundary and an initial upper boundary; 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 position of the number of the data packets which are N times away from the initial lower boundary. In another example, the sliding window includes an initial lower boundary and an initial upper boundary; the initial lower boundary is located at the position of the data packet with the number of 0, and the initial upper boundary is the number position of the data packets which are N times away from the initial lower boundary.

In the example shown in fig. 2, the initial lower boundary of the sliding window is located at the position of the number (number 1) of the initially transmitted packet, and the initial upper boundary is located at the position of the number of 4 packets away from the initial lower boundary (N ═ 4), that is, the initial upper boundary is located at the position of the number 4 of the packet.

In this embodiment, the sending end device may move the sliding window through one or more of the following three conditions, or maintain the position of the sliding window unchanged, and determine whether all the first timers corresponding to the N first packets in the sliding window are overtime.

The first condition is as follows:

and under the condition that the second data packet is successfully transmitted and the difference value between the number of the second data packet and the lower boundary of the sliding window is smaller than the window length, moving the lower boundary of the sliding window to the number position of a first third data packet which is not successfully transmitted and follows the second data packet.

For example, the "difference between the number of the second packet and the lower boundary of the sliding window" may be understood as a difference between the number of the second packet and the number of the packet corresponding to the lower boundary of the sliding window, or an absolute value of the difference between the number of the second packet and the number of the packet corresponding to the lower boundary of the sliding window, or a value of the number of packets between the second packet and the packet corresponding to the lower boundary of the sliding window.

In the case shown in fig. 2 and 3, the initial lower boundary of the sliding window is at PDCP COUNT of 1, and the initial upper boundary of the sliding window is at PDCP COUNT of 4, that is, the position shown in fig. 2. When receiving the indication that the packet (corresponding to the second packet) with PDCP COUNT of 3 is successfully received, the sliding window is moved to a position where the lower boundary of the sliding window is at PDCP COUNT of 4 (corresponding to the third packet), and at this time, the upper boundary of the sliding window is at PDCP COUNT of 7, that is, the position shown in fig. 3. In addition, a packet transmission timeout of PDCP COUNT 1 is shown in fig. 3; the PDCP COUNT-3 packet is successfully received.

Situation two

And keeping the position of the sliding window not to move under the condition that the second data packet is determined to be successfully sent and the difference value of the number of the second data packet and the lower boundary of the sliding window is larger than or equal to the window length.

For example, the meaning of the "difference between the number of the second packet and the lower boundary of the sliding window" is as described above, and is not described herein again.

Case two as shown in fig. 3 and 4, in fig. 3, the lower boundary of the sliding window is at PDCP COUNT of 4, and the upper boundary of the sliding window is at PDCP COUNT of 7. When receiving the indication information that the packet with PDCP COUNT 9 (corresponding to the second packet) is successfully received, since the difference between PDCP COUNT 9 and the lower boundary PDCP COUNT 4 of the sliding window is 5, which is greater than the window length 4, the position of the sliding window is not moved, which is specifically shown in fig. 4. In addition, a packet transmission timeout of PDCP COUNT 1 is shown in fig. 4; the

PDCP COUNT

3 and 9 packets are successfully received.

Situation three

In the case that it is determined that a second packet is successfully transmitted and the difference between the number of the second packet and the lower boundary of the sliding window is smaller than the window length, moving the lower boundary of the sliding window to the number (see PDCP COUNT of 10 in fig. 5) position of a first third packet after the second packet which is not successfully transmitted; wherein a difference between the number of the third packet and a number of a packet which is a first packet after the third packet and is successfully transmitted (PDCP COUNT of fig. 5 is 14) is greater than or equal to the window length.

Optionally, in a third case, in the process of moving the sliding window, if a successfully-sent data packet exists in the sliding window, determining that a fourth data packet with a largest number is successfully sent, and moving a lower boundary of the sliding window to a number position of a first unsuccessfully-sent data packet after the fourth data packet.

Similarly, the meaning of the "difference between the number of the third data packet and the number of the data packet that is located at the first position after the third data packet and is successfully transmitted" is the same as the meaning of the "difference between the number of the second data packet and the lower boundary of the sliding window" described above, and is not described herein again.

Case three as shown in fig. 3 and 5, in fig. 3, the lower boundary of the sliding window is at PDCP COUNT of 4, and the upper boundary of the sliding window is at PDCP COUNT of 7. When receiving the indication that the PDCP COUNT-7 packet (corresponding to the second packet) is successfully received, first, the sliding window is moved (temporarily moved) to the lower boundary of the sliding window at PDCP COUNT-8, at which the upper boundary of the sliding window is at PDCP COUNT-11, and because there is a packet (corresponding to the fourth packet) with a successful transmission rate in the sliding window, the sliding window is continuously moved to the lower boundary of the sliding window at PDCP COUNT-10, at which the upper boundary of the sliding window is at PDCP COUNT-13 and there is no packet with a successful transmission rate in the sliding window, as shown in fig. 5.

The packet transmission timeout of PDCP COUNT 1 is shown in fig. 5; the PDCP COUNT of 3, 7, 9 and 14 packets is successfully received.

In other examples, it can be understood that if there are successfully transmitted packets within the sliding window, i.e. PDCP COUNT 10 and PDCP COUNT 13, the sliding window may be moved backward according to the aforementioned rule until there are no successfully transmitted packets within the sliding window.

Optionally, the successful transmission of the second data packet mentioned in the above cases one to three includes at least one of:

1) the second data packet is successfully transmitted.

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

3) The lower layer entity indicates that the second data packet was successfully received.

Illustratively, the successful sending of the second data packet may be the delivery of the second data packet to an underlying layer (e.g., RLC entity) for a protocol entity (e.g., PDCP entity) that maintains the first timer. Or the second data packet may be sent from the sending end device (e.g., sent over the air interface).

The peer entity indicating successful receipt of the second data packet may be indicated by a status report. For example, the first timer is maintained in the PDCP layer and the opposite PDCP entity indicates the PDCP status report, or the first timer is maintained in the RLC layer and the corresponding RLC entity indicates the RLC status report.

The lower layer entity indicating successful receipt of the second data packet may be through lower layer HARQ feedback and/or lower layer RLC feedback.

Through the sliding window described above, when the sending-end device determines that the first timers corresponding to the N first data packets in the sliding window all time out, it determines that the sending of the consecutive N first data packets is time out, and may execute at least one of the following first method and second method:

method 1

And adjusting the logic priority configuration of the RB (such as DRB) corresponding to the data packet (which can comprise the first data packet). This example is applicable to the case where the sending-end device is a terminal device, and also to the case where the sending-end device is a network device.

Additionally, in the case that the sending-end device is a terminal device, the network device side may also implicitly or explicitly indicate a logical channel configuration used in the case that consecutive N first data packets are sent out overtime. For example, the 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 with transmission time-out in the DRB, the terminal device automatically adjusts the logical channel configuration 1 to the logical channel configuration 2, where the logical channel priority of the logical channel configuration 2 may be higher than the logical channel priority of the logical channel configuration 1. For example, after the sending end device sends a data packet (including the first data packet) corresponding to the timeout of the first timer, the sending end device may further 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 further receive the logical channel configuration sent by the network side after sending the indication information to the network side. Illustratively, the logical channel configuration 1 used by the sending end device before sending the indication is adjusted to the logical channel configuration 2 by the logical channel configuration sent by the network side.

Method two

And sending the indication information to the network side. This example is applicable to the case where the sending-end device is a terminal device, and the manner in which the terminal device sends the indication information to the network device side may be any of the following:

1) and sending a scheduling request to the network equipment side. The indication information may be the scheduling request. Optionally, the scheduling request carries additional indication information, such as data volume and/or remaining time. Optionally, the terminal device may send the Scheduling Request through a dedicated Scheduling Request (SR) resource, where the dedicated SR resource is a dedicated SR resource configured by the network device side and used for applying for uplink authorization for a specific type of data packet (e.g., a data packet with a timeout first timer, or a data packet with the timeout first timer). For a detailed description of the scheduling request, reference may be made to the related description in embodiment 100.

2) And sending a buffer status report to the network equipment side. The indication information may be the buffer status report. Optionally, the buffer status report carries additional indication information, such as data volume and/or remaining time. For a detailed description of the buffer status report, reference may be made to the related description in embodiment 100.

3) And sending an MAC layer signaling, such as an MAC Control Element (CE), to a network device, where the MAC CE may carry a logical channel identifier and is configured to indicate that a logical channel corresponding to the logical channel identifier has a data packet with a first timer being overtime. The MAC side signaling may also carry additional information, such as data volume and/or remaining time, for example, total data volume of data packets that have timed out by the first timer in logical channel 1. Alternatively, for example, the total data amount of the data packets with the remaining time of 0 in logical channel 1 is 100 bytes, and the total data amount of the data packets with the remaining time of 0.5ms in logical channel 2 is 200 bytes. For a detailed description 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 arrival of the data packet.

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

1) the data packet corresponding to the first timer is successfully transmitted, which is specifically referred to the foregoing description.

2) And the opposite terminal entity indicates that the data packet corresponding to the first timer is successfully received.

3) And the bottom 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 configured granularity of the first timer may be per DRB or per Quality of Service (QoS) flow.

For example, the duration of the first timer may be configured as the Uu maximum transmission Delay corresponding to the DRB or the QoS flow (e.g., Packet Delay Budget, PDB). For the first timer, the terminal device may have the following behavior:

1) and starting a first timer corresponding to the data packet when the data packet is received from an upper layer.

2) Stopping a first timer corresponding to the data packet after the data packet is successfully sent; wherein the successful transmission of the data packet may refer to the successful reception of the data packet, and the determination of the successful reception of the data packet by the sending end device may be based on an indication of an underlying entity (e.g., RLC or HARQ) or based on an indication of a peer entity (e.g., PDCP status report).

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

1) and the network equipment side distributes uplink authorization to the terminal equipment.

Additionally, the uplink grant carries indication information, where the indication information is used to indicate that the uplink grant is applicable to a specific type of data packet, such as a data packet with the first timer expired or a data packet with the first timer configured.

2) Reconfiguring a logical channel priority configuration. For example, the logical channel priority configuration 1 corresponding to the DRB with the consecutive N first packet transmission timeouts is adjusted to the logical channel priority configuration 2.

Example two

In the second embodiment, on the basis of the embodiment 100, it may also be determined whether consecutive N first data packets are timed out by running the timer.

The timer mentioned in the second embodiment includes a second timer and a third timer. 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 arrival of the data packet. The start timing of the third timer includes: any one of the second timers times out. For a detailed description of "packet arrival", reference may be made to the description of embodiment 100.

Optionally, in a case that the second timer is expired and the third timer is running, the sending end device may further perform at least one of the following: not starting a new said third timer; not restarting the third timer; the third timer that remains running continues to run.

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

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

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

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

For example, the successful transmission of the data packet corresponding to the second timer may be the delivery of the data packet to the lower layer (e.g., RLC entity) for the protocol entity (e.g., PDCP entity) maintaining the second timer. Or the data packet may be sent from the sending end device (e.g., over the air interface).

The peer 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 in the PDCP layer and the opposite PDCP entity indicates the PDCP status report, or the second timer is maintained in the RLC layer and the corresponding RLC entity indicates the RLC status report.

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

In one example, the second timer corresponding to the fifth data packet is stopped when it is determined that the fifth data packet is successfully transmitted.

The embodiment determines whether the sending time-out of the consecutive N first data packets occurs through the running condition of the timer, and includes: if the third timer is over time, it is determined that N consecutive first data packets are over time, and then the adjustment of the data transmission policy described in the foregoing embodiment 100 or the first embodiment may be performed.

Stopping the third timer if it is determined that the fifth packet transmission is successful during the operation of the third timer. Optionally, the second timer corresponding to the fifth data packet does not time out.

Illustratively, during the running of the third timer, if the receiving end feedback has successfully received the fifth data packet, but at the sending end device, the second timer corresponding to the fifth data packet has timed out, the third timer is not stopped. On the contrary, if the receiving end has fed back that the fifth data packet has been successfully received, but the second timer corresponding to the fifth data packet is not overtime at the transmitting end, the third timer is stopped.

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

1) the fifth data packet is successfully transmitted;

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

3) the bottom entity indicates that the fifth packet is ready for reception.

Illustratively, the successful sending of the fifth data packet may be a delivery of the fifth data packet to an underlying layer (e.g., RLC entity) for a protocol entity (e.g., PDCP entity) that maintains the second timer and/or the third timer. Or the fifth data packet may be sent from the sending end device (e.g., sent over the air interface).

The peer entity indicating successful receipt of the fifth data packet may be indicated by a status report. For example, the second timer and/or the third timer is maintained in the PDCP layer and the peer PDCP entity indicates the PDCP status report, or the second timer and/or the third timer is maintained in the RLC layer and the corresponding RLC entity indicates the RLC status report.

The lower layer entity indicating successful reception of the fifth data packet may be through lower layer HARQ feedback and/or lower layer RLC feedback.

To describe the second embodiment in detail, the following description will be made with reference to the embodiment shown in fig. 6.

In this example, the sending end device (e.g., PDCP layer or RLC layer) maintains two timers, namely, a second timer and a third timer, and the two timers and the time duration of the timers can be configured by the network device side. Additionally, the configuration granularity of the two timers may be per DRB or per QoS flow.

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

For example, assuming that the Uu port does not reach the receiving device on demand (e.g., does not meet the configured QoS requirement) within the time duration T, the communication service will enter an unavailable state, and the RAN may configure the time duration T3< T of the third timer, which is exemplary T3 ═ T — maximum Uu port latency.

Corresponding to the second timer, the behavior of the sending end device (e.g., UE) is 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 a second timer, which is started when the PDCP layer receives a packet from an upper layer (e.g., the SDAP layer or the application layer). Or, the PDCP layer of the UE maintains the second timer, and starts the second timer corresponding to the data packet after the PDCP layer receives the data packet from an upper layer (e.g., the SDAP layer, or the application layer) for a preset duration (e.g., the second timer corresponding to the QoS flow 1 is started if the data packet belongs to the QoS flow 1).

Referring to fig. 6 in detail, in fig. 6, after the packet corresponding to the PDCP SN of 1 arrives, the corresponding second timer (timer 2 in fig. 6) is started; after a certain transmission interval, starting a corresponding second timer after the data packet corresponding to the PDCP SN 2 arrives; after a certain transmission interval, starting a corresponding second timer after the data packet corresponding to the PDCP SN (3 SN) arrives; after a certain transmission interval, starting a corresponding second timer after the data packet corresponding to the PDCP SN-4 arrives.

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 is not expired.

2) And when the indication that the data packet is successfully received is received, stopping the second timer corresponding to the data packet. For example, the PDCP layer of the UE maintains the second timer, and when receiving the indication information (e.g., the bottom RLC indication or the PDCP status report indication) that the data packet corresponding to the PDCP SN of 2 is successfully received by the receiving end, the PDCP layer stops the second timer corresponding to the data packet corresponding to the PDCP SN of 2.

3) And when the second timer is overtime, starting a third timer.

Referring to fig. 6, for example, the PDCP layer of the UE maintains a second timer, and starts a third timer (timer 3 in fig. 6) when the second timer (timer 2 in fig. 6) of the packet corresponding to the PDCP SN of 1 expires. Or, for example, the RLC layer of the UE maintains the second timer, and starts the third timer when the second timer of the packet corresponding to the RLC SN of 1 expires.

Corresponding to the third timer, the sending end device (e.g., UE) behaves as at least one of:

1) when the second timer times out, a third timer is started or restarted.

For example, if the second timer of the packet corresponding to PDCP SN 1 times out, the third timer is started, and during the running period of the third timer, the packet corresponding to PDCP SN 1 is successfully received, the PDCP layer stops the third timer, and after that, if the second timer corresponding to the packet corresponding to PDCP SN 3 times out, the PDCP layer restarts the third timer. The "restart of the third timer" indicates that the third timer is started from an initial value (e.g., 0).

2) And stopping the third timer if an indication that the data packet is successfully received is received during the running period of the third timer, wherein the second timer corresponding to the successfully received data packet is not overtime.

For example, in fig. 6, during the operation of the third timer, when receiving indication information (such as an RLC indication or a PDCP status report indication) that a data packet corresponding to PDCP SN 2 is successfully received by the receiving end, the PDCP layer stops the third timer, wherein the second timer corresponding to the data packet corresponding to PDCP SN 2 does not time out.

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

method 1

And adjusting the logic 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 also to the case where the sending-end device is a network device.

Additionally, in the case that the sending-end device is a terminal device, the network device side may also implicitly or explicitly indicate a logical channel configuration used in the case that the third timer times out. For example, the 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 is overtime, the terminal device automatically adjusts the logical channel configuration 1 to the logical channel configuration 2, wherein the logical channel priority of the logical channel configuration 2 may be higher than the logical channel priority of the logical channel configuration 1. For example, after the sending end device sends the data packet corresponding to the timeout of the third timer, the sending end device may further automatically adjust the logical channel configuration 2 back to the previous logical channel configuration 1.

Method two

1) and sending a scheduling request to the network equipment side. The indication information may be the scheduling request. Optionally, the scheduling request carries additional indication information, such as data volume and/or remaining time. Optionally, the terminal device may send the scheduling request through a dedicated SR resource, where the dedicated SR resource is a dedicated SR resource configured on the network device side and used for applying for uplink authorization for a specific type of data packet (for example, a data packet in which the second timer or the third timer expires, or a data packet in which the second timer and the third timer are configured). For a detailed description of the scheduling request, reference may be made to the related description in embodiment 100.

2) And sending a buffer status report to the network equipment side. The indication information may be a buffer status report (e.g., short BSR, long BSR, etc.). The buffer status report may be different from a conventional buffer status report, e.g. distinguished by a logical channel ID. Optionally, the buffer status report carries additional indication information, such as data volume and/or remaining time. For a detailed description of the buffer status report, reference may be made to the related description in embodiment 100.

3) And sending an MAC layer signaling, such as a MAC Control Element (CE), to a network device, where the MAC CE may carry a logical channel identifier, and is configured to indicate that a logical channel corresponding to the logical channel identifier has a data packet with a timeout third timer. The MAC side signaling may also carry additional information, such as the amount of data and/or the remaining time, e.g., the total amount of data of the data packets that have expired by the second timer in logical channel 1. Alternatively, for example, the total data amount of the data packets with the remaining time of 0 in logical channel 1 is 100 bytes, and the total data amount of the data packets with the remaining time of 0.5ms in logical channel 2 is 200 bytes. Additionally, the MAC layer signaling may trigger SR. For a detailed description of the MAC layer signaling, reference may be made to the related description in embodiment 100.

Additionally, the uplink grant carries indication information, where the indication information is used to indicate that the uplink grant is suitable for a specific type of packet (e.g., a packet that the second timer or the third timer expires, or a packet that is configured with the second timer and the third timer).

2) Reconfiguring a logical channel priority configuration. For example, the logical channel priority configuration 1 corresponding to the DRB with the timeout of the third timer 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 to fig. 6. A data transmission method according to another embodiment of the present application will be described in detail below with reference to fig. 7. The description of the slave network device side can be referred to the same description of the sender device side as above, and the related description is appropriately omitted to avoid redundancy.

Fig. 7 is a schematic diagram of an implementation flow of a data transmission method according to an embodiment of the present application, which may be applied to a network device side. As shown in fig. 7, the method 700 includes at least one of the following introduced in S702:

s702: sending first configuration information, wherein the first configuration information is used for indicating the logical channel configuration of the radio bearer corresponding to the continuous N first data packets which are sent overtime;

sending an uplink authorization;

and sending second configuration information, wherein the second configuration information is used for reconfiguring the logical channel configuration of the radio bearer corresponding to the continuous N first data packets which are sent overtime.

In this embodiment, the network device may adopt a mode of sending the uplink grant or sending the configuration information, so as to ensure that the data packet of the sending end device (e.g., UE) reaches the receiving end device within the survival time as much as possible, thereby improving the communication effectiveness.

Optionally, as an embodiment, the method 700 further includes: receiving a first message, wherein the first message is sent by a terminal device under the condition that the sending of N continuous first data packets is determined to be overtime, and the first message comprises at least one of the following:

scheduling requests;

caching a status report;

and MAC layer signaling.

Alternatively, the processor may, as an embodiment,

under the condition that the first message comprises the scheduling request, the scheduling request carries first indication information, and the first indication information carries at least one of data volume and remaining time;

and under the condition that the first message comprises the cache state report, the cache state report carries second indication information, and the second indication information carries at least one of data volume and remaining time.

Optionally, as an embodiment, the uplink grant carries third indication information, where the third indication information is used to indicate that the uplink grant is used for a data packet of a specific type, where the data packet of the specific type includes a data packet that is sent overtime or is about to be overtime.

The data transmission method according to the embodiment of the present application is described in detail above with reference to fig. 1 to 7. A transmitting end device according to an 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, where the sending end device may be a terminal device or a network device. As shown in fig. 8, the transmitting-end device 800 includes:

the adjusting module 802 may be configured to adjust the data transmission policy when it is determined that consecutive N first data packets are sent out overtime, where N is an integer greater than 1.

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

Alternatively, the processor may, as an embodiment,

the N continuous first data packets are N first data packets with continuous numbers; and/or

The N continuous first data packets are N first data packets with continuous arrival time.

Optionally, as an embodiment, the sending-end device 800 further includes a determining module, configured to determine whether consecutive N first data packets are sent out overtime through a sliding window, where a window length of the sliding window is equal to N.

Optionally, as an embodiment, the determining module determines whether consecutive N first data packet transmission time-outs occur through a sliding window, including: and if the first timers corresponding to the N first data packets in the sliding window are overtime, determining that the sending of the N continuous first data packets is overtime.

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

after the data packet arrives; or the like, or, alternatively,

after a predetermined time after the arrival of the data packet.

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

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

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

and the bottom 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 moving module, and configured to, when it is determined that the second data packet is successfully sent and a difference between the number of the second data packet and the lower boundary of the sliding window is smaller than the window length, move the lower boundary of the sliding window to a number position of a first third data packet that is not successfully sent after the second data packet.

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

the second data packet is successfully sent;

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

the lower layer entity indicates that the second data packet was successfully received.

Optionally, as an embodiment, the sending-end device 800 further includes a moving module, and configured to keep the position of the sliding window not moving when it is determined that the second data packet is successfully sent and a difference between the number of the second data packet and the lower boundary of the sliding window is greater than or equal to the window length.

Optionally, as an embodiment, the sending-end device 800 further includes a moving module, configured to, when it is determined that the second data packet is successfully sent and a difference between the number of the second data packet and the lower boundary of the sliding window is smaller than the window length, move the lower boundary of the sliding window to a number position of a first third data packet that is not successfully sent after the second data packet;

and the difference value between the number of the third data packet and the number of the first successfully-sent 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 a successfully-sent data packet exists in the sliding window, a fourth data packet with a largest number and a successful sending is determined, and the lower boundary of the sliding window is moved to a number position of a 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; 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 position of the number of the data packets which are N times away from the initial lower boundary.

Optionally, as an embodiment, the sliding window includes an initial lower boundary and an initial upper boundary; the initial lower boundary is located at the position of the data packet with the number of 0, and the initial upper boundary is the number position of the data packets which are N times away from the initial lower boundary.

Optionally, as an embodiment, the sending-end device 800 further includes a determining module, which is configured to determine whether consecutive N times of sending the first data packets are expired according to a running condition of a timer.

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

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

after the data packet arrives; or the like, or, alternatively,

after a predetermined time after the arrival of the data packet.

Optionally, as an embodiment, the starting timing of the third timer includes: the second timer times out.

Optionally, as an embodiment, in a case that the second timer is expired and the third timer is running, the sending-end device 800 further includes a timer control module, and may be configured to:

not starting a new said third timer; or the like, or, alternatively,

the third timer is not restarted.

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

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

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

and the bottom entity indicates that the data packet corresponding to the second timer is successfully received.

Optionally, as an embodiment, the determining, by using a running condition of a timer, whether consecutive N first data packet transmission time-outs occur includes: and if the third timer is overtime, determining that the sending of the N continuous first data packets is overtime.

Optionally, as an embodiment, the sending-end device 800 further includes a timer control module, and may be configured to: and stopping the second timer corresponding to the fifth data packet under the condition that the fifth data packet is determined to be successfully sent.

Optionally, as an embodiment, the sending-end device 800 further includes a timer control module, and may be configured to: stopping the third timer if it is determined that the fifth packet transmission is successful during the operation of the third timer.

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

the fifth data packet is successfully transmitted;

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

the bottom entity indicates that the fifth packet is ready for reception.

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

Optionally, as an embodiment, the adjusting module 802 adjusts the data transmission policy and includes at least one of:

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

and receiving an uplink authorization.

Optionally, as an embodiment, the sending-end device 800 further includes a receiving module, which is configured to receive first configuration information, where the first configuration information is used to indicate logical channel configurations of radio bearers corresponding to the consecutive N sending timeout first data packets.

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

sending a scheduling request to the network equipment;

sending a buffer status report to the network equipment;

and sending Media Access Control (MAC) layer signaling to the network equipment.

Alternatively, the processor may, as an embodiment,

under the condition of sending a scheduling request to the network equipment, the scheduling request carries first indication information, and the first indication information carries at least one of data volume and remaining time;

and under the condition of sending a cache state report to the network equipment, the cache state report carries second indication information, and the second indication information carries at least one of data volume and remaining time.

Optionally, as an embodiment, the sending-end device 800 further includes a receiving module, and may be configured to at least one of the following:

receiving an uplink grant;

and receiving second configuration information, wherein the second configuration information is used for reconfiguring the logical channel configuration corresponding to the first data packet.

Optionally, as an embodiment, the uplink grant mentioned in each of the above examples carries third indication information, where the third indication information is used to indicate that the uplink grant is used for a specific type of data packet, where the specific type of data packet includes a data packet that is sent overtime or is about to be overtime.

The sending-end 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 and the other operations and/or functions in the sending-end device 800 are respectively for implementing the corresponding flow in the method 100 and can achieve the same or equivalent technical effects, and for brevity, no further description is provided 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, configured to at least one of:

sending first configuration information, wherein the first configuration information is used for indicating the logical channel configuration of the radio bearer corresponding to the continuous N first data packets which are sent overtime;

sending an uplink authorization;

Optionally, as an embodiment, the network device 900 further includes a receiving module, which is configured to receive a first message, where the first message is sent by the terminal device when it is determined that consecutive N first data packets are sent overtime, and the first message includes at least one of:

scheduling requests;

caching a status report;

and MAC layer signaling.

Alternatively, the processor may, as an embodiment,

The network device 900 according to the embodiment of the present application may refer to the flow corresponding to the method 700 of the embodiment of the present application, and each unit/module and the other operations and/or functions in the network device 900 are respectively for implementing the corresponding flow in the method 700 and achieving the same or equivalent technical effects, and for brevity, no further description is provided here.

The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts in the embodiments are referred to each other. For the apparatus embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.

Where an indefinite or definite article is used when referring to a feature or noun, e.g. "a" or "an", "the", the article "a" or "an" does not exclude the presence of a plurality of such features or nouns, e.g. where one is specifically stated otherwise.

Furthermore, the terms "first," "second," and "third," etc. are used in the description and claims to distinguish between similar packets or timers, and do not necessarily describe a sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances and that the embodiments of the application described herein are capable of operation in other sequences than 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, memory 1002, at least one network interface 1004, and a user interface 1003. The various components in terminal device 1000 are coupled together by a bus system 1005. It is understood that bus system 1005 is used to enable communications among the components connected. The bus system 1005 includes a power bus, a control bus, and a status signal bus, in addition to a data bus. But for the sake of clarity the various busses are labeled in figure 10 as the bus system 1005.

The user interface 1003 may include, among other things, a display, a keyboard, a pointing device (e.g., a mouse, trackball), a touch pad, or a touch screen.

It is to be appreciated that the memory 1002 in the subject embodiment can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (ddr Data Rate SDRAM, ddr SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 1002 of the systems and methods described in connection with the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

In some embodiments, memory 1002 stores the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof: an operating system 10021 and applications 10022.

The operating system 10021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks. The application 10022 includes various applications, such as a Media Player (Media Player), a Browser (Browser), and the like, for implementing 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 this embodiment of the present application, the terminal device 1000 further includes: instructions or programs stored on the memory 1002 and executable on the processor 1001, which when executed by the processor 1001 implement the steps of the method embodiment 100 as follows.

The method disclosed in the embodiments of the present application may be applied to the processor 1001, or may be implemented by the processor 1001. The processor 1001 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 1001. The Processor 1001 may be a general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, or other readable storage medium known in the art. The readable storage medium is located in the memory 1002, and the processor 1001 reads the information in the memory 1002 and performs the steps of the method in combination with the hardware. In particular, the readable storage medium has stored thereon instructions or a program which, when executed by the processor 1001, implements the steps of the method embodiment 100 as described above.

It is to be understood that the embodiments described in connection with the embodiments disclosed herein may be implemented by hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the Processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units configured to perform the functions described herein, or a combination thereof.

For a software implementation, the techniques described in this application may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described in this application. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.

The terminal device 1000 can implement each process implemented by the sending-end device in the foregoing embodiments, and can achieve the same or equivalent technical effects, and for avoiding repetition, details are not described here.

Referring to fig. 11, fig. 11 is a structural diagram of a network device applied in the embodiment of the present application, which can implement details of

method embodiments

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

in this embodiment, the network device 1100 further includes: instructions or programs stored on the memory 1103 and executable on the processor 1101, which when executed by the processor 1101, 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, with one or more processors, represented by processor 1101, and various circuits, represented by memory 1103, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1102 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.

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

An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of any one of the

method embodiments

100 and 700, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to execute a program or an instruction to implement each process of any one of

method embodiments

100 and 700, and the same technical effect can be achieved, and details are not repeated here to avoid repetition.

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

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A data transmission method, wherein the method is performed by a sending end device, and the method comprises:

and under the condition that the sending time-out of N continuous first data packets is determined, adjusting a data transmission strategy, wherein N is an integer larger than 1.

2. The method of claim 1, wherein the N is configured by a network device in a case that the sender device is a terminal device.

3. The method of claim 1,

4. The method of claim 1, further comprising:

and determining whether continuous N first data packet sending time-outs occur or not through a sliding window, wherein the window length of the sliding window is equal to N.

5. The method of claim 4, wherein said determining whether consecutive N of said first packet transmission timeouts occur via a sliding window comprises:

and if the first timers corresponding to the N first data packets in the sliding window are overtime, determining that the sending of the N continuous first data packets is overtime.

6. The method of claim 5, wherein the starting timing of the first timer comprises:

after the data packet arrives; or the like, or, alternatively,

after a predetermined time after the arrival of the data packet.

7. The method of claim 5, wherein the stop timing of the first timer comprises at least one of:

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

8. The method according to claim 4 or 5, characterized in that the method further comprises:

9. The method of claim 8, wherein the successful transmission of the second data packet comprises at least one of:

the second data packet is successfully sent;

10. The method according to claim 4 or 5, characterized in that the method further comprises:

11. The method according to claim 4 or 5, characterized in that the method further comprises:

under the condition that it is determined that a second data packet is successfully transmitted and the difference value between the number of the second data packet and the lower boundary of the sliding window is smaller than the window length, moving the lower boundary of the sliding window to the number position of a first third data packet which is not successfully transmitted and follows the second data packet;

12. The method of claim 11,

in the process of moving the sliding window, if a successfully-sent data packet exists in the sliding window, determining a fourth data packet which is successfully sent and has the largest number, and moving the lower boundary of the sliding window to the number position of a first unsuccessfully-sent data packet after the fourth data packet.

13. The method of claim 4, wherein the sliding window comprises an initial lower boundary and an initial upper boundary; 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 position of the number of the data packets which are N times away from the initial lower boundary.

14. The method of claim 4, wherein the sliding window comprises an initial lower boundary and an initial upper boundary; the initial lower boundary is located at the position of the data packet with the number of 0, and the initial upper boundary is the number position of the data packets which are N times away from the initial lower boundary.

15. The method of claim 1, further comprising:

and determining whether continuous N first data packet transmission time-outs occur according to the running condition of the timer.

16. The method of claim 15, wherein the timer comprises a second timer and a third timer.

17. The method of claim 16, wherein the start timing of the second timer comprises:

after the data packet arrives; or the like, or, alternatively,

after a predetermined time after the arrival of the data packet.

18. The method of claim 16, wherein the start timing of the third timer comprises:

the second timer times out.

19. The method of claim 18, wherein if the second timer expires and the third timer is running, the method further comprises:

not starting a new said third timer; or the like, or, alternatively,

the third timer is not restarted.

20. The method of claim 16, wherein the stop timing of the second timer comprises at least one of:

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

21. The method of claim 18, wherein said determining whether N consecutive first packet transmission time-outs occur through running of a timer comprises:

and if the third timer is overtime, determining that the sending of the N continuous first data packets is overtime.

22. The method of claim 16, further comprising:

and stopping the second timer corresponding to the fifth data packet under the condition that the fifth data packet is determined to be successfully sent.

23. The method of claim 18, further comprising:

stopping the third timer if it is determined that the fifth packet transmission is successful during the operation of the third timer.

24. The method according to claim 22 or 23, wherein the successful transmission of the fifth data packet comprises at least one of:

the fifth data packet is successfully transmitted;

the bottom entity indicates that the fifth packet is ready for reception.

25. The method of claim 23, wherein the second timer for the fifth packet does not time out.

26. The method of claim 1, wherein the adjusting the data transmission policy comprises at least one of:

and receiving an uplink authorization.

27. The method of claim 26, wherein prior to adjusting the data transmission policy, the method further comprises:

and receiving first configuration information, where the first configuration information is used to indicate logical channel configurations of radio bearers corresponding to the consecutive N sending overtime first data packets.

28. The method according to claim 1, wherein in a case that the sending end device is a terminal device, the adjusting the data transmission policy includes at least one of:

sending a scheduling request to the network equipment;

sending a buffer status report to the network equipment;

29. The method of claim 28,

30. The method of claim 28, further comprising at least one of:

receiving an uplink grant;

31. The method according to claim 26 or 30, wherein the uplink grant carries third indication information, and the third indication information is used to indicate that the uplink grant is used for a specific type of data packet, and wherein the specific type of data packet includes a data packet that is timed out or is about to be timed out.

32. A data transmission method, the method being performed by a network device, the method comprising at least one of:

sending an uplink authorization;

33. The method of claim 32, further comprising: receiving a first message, wherein the first message is sent by a terminal device under the condition that the sending of N continuous first data packets is determined to be overtime, and the first message comprises at least one of the following:

scheduling requests;

caching a status report;

and MAC layer signaling.

34. The method of claim 33,

35. The method of claim 32, wherein the uplink grant carries third indication information, and wherein the third indication information is used to indicate that the uplink grant is used for a specific type of packet, and wherein the specific type of packet includes a packet that is timed out or is about to be timed out.

36. A transmitting-end device, comprising:

and the adjusting module is used for adjusting the data transmission strategy under the condition of determining that the sending of the continuous N first data packets is overtime, wherein N is an integer larger than 1.

37. A network device, comprising a sending module configured to at least one of:

sending an uplink authorization;

38. A communication device, comprising: memory, a processor and instructions or programs stored on the memory and executable on the processor, which when executed by the processor implement a data transmission method as claimed in any one of claims 1 to 35.

39. A readable storage medium, characterized in that it has stored thereon instructions or a program which, when executed by a processor, implements the data transmission method according to any one of claims 1 to 35.