CN116634548A

CN116634548A - Synchronous link data transmission method, communication device, and storage medium

Info

Publication number: CN116634548A
Application number: CN202310486418.7A
Authority: CN
Inventors: 刘治文
Original assignee: Chongqing Xiwei Technology Co ltd
Current assignee: Chongqing Xiwei Technology Co ltd
Priority date: 2023-05-04
Filing date: 2023-05-04
Publication date: 2023-08-22

Abstract

The application discloses a synchronous link data transmission method, communication equipment and a storage medium. The method is used for data transmission of a synchronous link between a first device and a second device, the synchronous link is provided with a reserved transmission window which is arranged according to a preset interval, the first device generates a first service data block which corresponds to the reserved transmission window in time sequence, the method is executed by the first device, and the method comprises the following steps: judging whether the current transmission window has enough residual time or not in response to the completion of the data transmission associated with the last first service data block in the current transmission window; and in response to the current transmission window having sufficient time remaining, performing data transmission associated with the first service data block to be currently transmitted with the second device. The application can optimize the synchronous links of the pre-allocated time slices, improve the fragmentation problem of the time slices which can be used for other links, reduce the switching frequency of the links and improve the scheduling efficiency.

Description

Synchronous link data transmission method, communication device, and storage medium

Technical Field

The present application relates to the field of wireless communications technologies, and in particular, to a synchronous link data transmission method, a communication device, and a storage medium.

Background

Synchronous link data transmission is a data transmission method associated with a system clock, and is generally implemented by reserving certain physical resources, that is, reserving time slices for a link between two devices participating in communication at fixed intervals, for the two devices to perform link data transmission. The link between the two devices may be a bi-directional data transmission link. The data stream generated by each of the two devices may be divided sequentially into data blocks, which are transmitted sequentially at reserved time slices. The transmission mode can ensure a certain transmission bandwidth and is mostly used in some services with higher real-time performance, such as voice, video or other data streams with higher priority.

When there is a synchronization link with reserved time slices, other services can only transmit in the unused time slices of the synchronization link, so that the fragmentation degree of the time slices which can be used by other services is high, and the link/service switching frequency is high, thereby directly affecting the scheduling efficiency and scheduling difficulty of multi-link multi-service concurrency.

Disclosure of Invention

In order to solve the technical problems, the invention aims to provide a synchronous link data transmission method, which optimizes a synchronous link data transmission mode of a pre-allocated time slice so as to improve the fragmentation problem of the time slices available for other links, thereby reducing the link switching frequency, reducing the multi-link multi-service concurrent scheduling difficulty and improving the scheduling efficiency.

In one aspect of the present application, there is provided a synchronous link data transmission method for data transmission of a synchronous link between a first device and a second device, the synchronous link having reserved transmission windows set at preset intervals, the first device generating first traffic data blocks each corresponding to the reserved transmission windows in chronological order, the method being performed by the first device, the method comprising: step S1: judging whether the current transmission window has enough residual time or not in response to the completion of data transmission associated with the last first service data block in the current transmission window; step S2: and in response to the current transmission window having enough remaining time, performing data transmission associated with the first service data block to be transmitted currently with the second device.

In some embodiments, the method further comprises: and repeatedly executing the step S1 and the step S2 until the current window does not have enough residual time.

In some embodiments, the method further comprises: and responding to the fact that the current transmission window does not have enough residual time, taking a reserved transmission window corresponding to the first service data block to be transmitted currently as a new transmission window, and carrying out data transmission associated with the first service data block to be transmitted currently in the new transmission window and the second equipment.

In some embodiments, the method further comprises: and responding to the completion of the data transmission associated with the first service data block to be transmitted currently, taking a reserved transmission window corresponding to a new first service data block to be transmitted as a new transmission window, and carrying out the data transmission associated with the new first service data block to be transmitted on the new transmission window and the second equipment.

In some embodiments, the preset interval of the link is determined by the first device and the second device negotiating when establishing the link.

In some embodiments, the current transmission window includes a first interval for the first device to transmit packets to the second device and a second interval for the second device to transmit packets to the first device, which are alternately distributed in time order.

In some embodiments, transmitting data associated with the first traffic data block currently to be transmitted with the second device includes: transmitting a first packet including the first service data block currently to be transmitted to the second device; and receiving a second packet sent by the second device.

In this embodiment, the synchronization link is a bluetooth SCO link.

In this embodiment, the first packet is an HV2 packet or an HV3 packet.

In some embodiments, transmitting data associated with the first traffic data block currently to be transmitted with the second device includes: the following steps are sequentially executed until the transmission of the first service data block to be transmitted is completed: transmitting a first packet including the first service data block currently to be transmitted to the second device; receiving feedback information sent by the second device, wherein the feedback information indicates whether the second device successfully receives a last first packet sent by the first device; and judging whether the transmission of the first service data block to be transmitted is completed or not.

In this embodiment, determining whether the transmission of the first service data block to be currently transmitted is completed includes: and if the feedback information of the last first packet sent by the first device is received in the current transmission window, the second device feedback indicates that the second device has successfully received the feedback information of the last first packet sent by the first device, and the transmission of the first service data block to be transmitted currently is confirmed to be completed.

In some embodiments, determining whether the transmission of the first service data block to be currently transmitted is completed further includes: and if the current transmission window is finished, confirming that the transmission of the first service data block to be transmitted currently is finished.

In other embodiments, determining whether the transmission of the first service data block to be currently transmitted is completed further includes: and if the current transmission window is over but feedback information indicating that the second equipment has successfully received the last first packet sent by the first equipment is not received by the second equipment, confirming that the transmission of the first service data block to be transmitted currently is not completed.

In some embodiments, receiving feedback information sent by the second device indicating whether the second device successfully received a last first packet sent by the first device includes: and receiving a second packet sent by the second device, wherein the second packet comprises feedback information indicating whether the second device successfully receives a last first packet sent by the first device.

In other embodiments, receiving feedback information sent by the second device indicating whether the second device successfully received a last first packet sent by the first device includes: and receiving a second packet sent by the second device, wherein the second packet comprises feedback information indicating whether the second device successfully receives a last first packet sent by the first device, and further comprises a second service data block generated by the second device.

In some embodiments, the first packet further includes feedback information indicating whether the first device successfully received a last second packet sent by the second device.

In some embodiments, the synchronization link is a bluetooth eSCO link.

In another aspect of the present application, a communication device is provided that includes a processor and a non-transitory storage medium storing computer-executable instructions executable by the processor to perform the steps of the above-described synchronous link data transmission method.

In a third aspect of the present application, there is provided a non-transitory computer readable storage medium storing computer executable instructions which, when executed by a computer, perform the steps of the above-described synchronous link data transmission method.

By the synchronous link data transmission method, the communication equipment and the storage medium, the link of the pre-allocated time slice can be optimized, and the subsequent service data blocks are transmitted in advance under the condition that the transmission of the service data block corresponding to the current reserved transmission window is completed and enough residual time exists, so that the reserved transmission window corresponding to the subsequent service data block is released for the data transmission of other links, the problem of time slice fragmentation of other links is solved, the link switching frequency is reduced, the scheduling difficulty of multi-link multi-service concurrency is reduced, and the scheduling efficiency is improved.

Drawings

Fig. 1 shows a schematic diagram of a bluetooth eSCO link transmission window;

fig. 2 shows a schematic diagram of eSCO link data transmission between a central device and a peripheral device as specified in the existing bluetooth protocol;

fig. 3 illustrates a flow chart of a method 100 of synchronous link data transmission in accordance with an embodiment of the present disclosure;

fig. 4 shows a time division diagram of a transmission window;

FIG. 5 illustrates one embodiment of a method 100 using the present disclosure;

fig. 6 illustrates another embodiment of a method 100 using the present disclosure, in which a first traffic data block B is pre-transmitted and the transmission is unsuccessful;

fig. 7 illustrates another embodiment of a method 100 using the present disclosure, in which a first traffic data block B is pre-transmitted and the transmission is unsuccessful, continuing the transmission in its corresponding reserved transmission window;

fig. 8 illustrates another embodiment of a method 100 using the present disclosure, in which both first traffic data blocks B and C are pre-transmitted and the transmission is successful;

fig. 9 shows a flowchart of a method 400 of synchronous link data transmission in accordance with yet another embodiment of the present disclosure;

fig. 10 illustrates an embodiment of a method 400 using the present disclosure, in which a first traffic data block B remains for a time after a pre-transmission of a current transmission window is successful.

Detailed Description

In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, like reference numerals generally refer to like elements unless the context indicates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the inventive subject matter. It will be readily understood that the aspects of the present disclosure, as generally described and illustrated in the figures herein, could be arranged, substituted, and combined in a wide variety of different configurations, all of which are explicitly contemplated as part of this disclosure.

For the convenience of those skilled in the art to understand the present disclosure, the following description will be made with respect to a synchronous link data transmission procedure by taking bluetooth technology as an example.

Bluetooth Basic Rate (BR) and Enhanced Data Rate (EDR) modes support connection-Oriented Synchronization (SCO) logical transport (logicaltransport) and extended connection-Oriented synchronization (Extended SynchronousConnection-Oriented, eSCO) logical transport between a Central device (Central) or Master and a Peripheral device (Peripheral) or Slave (Slave).

SCO/eSCO supports data transmission requiring a fixed bandwidth by reserving a fixed interval transmission window (SCO/eSCOwindow) and can therefore be considered a circuit switched connection between a central device and a peripheral device. Each reserved transmission window comprises a number of time slots, and the starting point of the transmission window is called SCO/eSCO time instant (SCO/eSCOinstant). The data stream generated by the central device or the peripheral device is divided into data blocks in sequence, and each data block is transmitted in a reserved transmission window in sequence. The data block is transmitted in the payload of a Packet (Packet) and may be retransmitted if the Packet is not transmitted successfully. The central device sends a packet to the peripheral device at the SCO/eSCO instant, and the peripheral device sends a packet to the central device after the end of the packet sent by the central device.

Fig. 1 shows an eSCO link transmission window schematic. In fig. 1, a packet transmitted by the central device is denoted by C, and a packet transmitted by the peripheral device is denoted by P. The eSCO transmission window comprises a reserved time slot and a retransmission window, wherein the reserved time slot comprises a time interval for the central device to transmit packets at eSCO time and the peripheral device to transmit packets, and the retransmission window is located after the reserved time slot.

The central equipment determines the using mode of the retransmission window, and the peripheral equipment performs corresponding transmission in the retransmission window according to the behavior of the central equipment. In general, when packet transmission fails in either direction, the central device may start a retransmission window to retransmit data, and the number of retransmissions is not limited, so long as the retransmission window has enough slots. If the central device does not need to retransmit the data, the retransmission window can also be used for transmitting the data of other services. The main difference between SCO and eSCO is that SCO does not support retransmissions, so the transmission window of SCO does not include a retransmission window. But after completion of the SCO link data block transmission, if there is a remaining time slot before the next transmission window, the remaining time slot may be used for data transmission of other traffic.

Fig. 2 shows a schematic diagram of eSCO link data transmission between a central device and peripheral devices as specified in the existing bluetooth protocol. The service data stream generated by the central device is divided into service data blocks in chronological order, each service data block corresponding to a reserved transmission window in chronological order. Three consecutive traffic data blocks A, B, C generated by the central device are exemplarily shown in fig. 2, wherein traffic data block a corresponds to a reserved transmission window 240, traffic data block B corresponds to a reserved transmission window 241, traffic data block C corresponds to a reserved transmission window 242, and each traffic data block is transmitted in turn in the corresponding reserved transmission window. Similarly, the traffic data stream generated by the peripheral device is divided into traffic data blocks in sequence, as three consecutive traffic data blocks 1, 2, 3 are shown in fig. 2. As shown in fig. 2, the central device transmits a packet containing service data block a to the peripheral device after the start of the reserved transmission window 240, and the peripheral device transmits the packet to the central device after receiving. The packet sent by the peripheral device contains a block of traffic data 1 and feedback information indicating whether the peripheral device successfully received the packet sent by the central device. The first transmitted data block by the central device or peripheral device is referred to as the initial version of the data block. After receiving the packet sent by the peripheral device, if it is determined that the service data block a fails to be sent successfully, the central device resends the packet containing the service data block a in the reserved transmission window 240. Similarly, if the peripheral device determines that service data block 1 fails to be transmitted successfully, the packet containing service data block 1 is retransmitted in reserved transmission window 240. The data block retransmitted by the central device or the peripheral device is called a retransmission version. In the example of fig. 2, the service data block a and the service data block 1 are each successfully transmitted after 1 retransmission, so that no transmission is performed. If the transmission is not successful, retransmission continues until there is no time remaining in the reserved transmission window 240. After the service data block a is successfully transmitted or after the reserved transmission window 240 is finished, if there is an idle time before the next reserved transmission window 241, other link data may be transmitted using the idle time slot before the next reserved transmission window 241. In the reserved transmission window 241, the service data block B is successfully transmitted after being retransmitted once, and the data block 2 is successfully transmitted once, so that the peripheral device transmits a NULL packet (indicated by "NULL" in fig. 2) which does not include the service data block to the central device when transmitting for the second time. The reserved transmission window 242 and the reserved transmission window 240 are similar, and thus are not described in detail.

Bluetooth devices typically have multiple concurrent links in operation. Since the SCO/eSCO link needs to reserve a fixed transmission window, data of other traffic or links can only be transmitted in the time slices occupied by the non-SCO/eSCO link between two SCO/eSCO transmission moments. Therefore, when the SCO/eSCO-like pre-allocated time slice links exist, the fragmentation degree of the time slices which can be used by other links or services is high, and the link/service switching frequency is high, so that the concurrent scheduling efficiency and scheduling difficulty of multiple links and multiple services are directly affected.

Aiming at the problem of time slice fragmentation in the synchronous link data transmission of the reserved time slices, the disclosure provides a synchronous link data transmission method, and when the reserved transmission window has residual time, the residual time is used for transmitting the data block corresponding to the next reserved transmission window.

The synchronous link data transmission method of the present disclosure is described below with reference to the accompanying drawings.

Fig. 3 illustrates a flow chart of a method 100 of synchronous link data transmission in accordance with an embodiment of the present disclosure. The method 100 is performed by a first device for synchronous link data transmission between the first device and a second device. The synchronization link has reserved transmission windows set at preset intervals. The preset interval refers to an interval of a start time of the reserved transmission window, and the preset interval and the length of the reserved transmission window can be determined by negotiation of the first device and the second device when the link is established. The preset interval may be greater than or equal to the length of the reserved transmission window. The first device generates first traffic data blocks, each corresponding to a reserved transmission window in time sequence. The method 100 comprises the steps of:

In step 110, it is determined whether the current transmission window has sufficient time remaining in response to the data transmission associated with the last first traffic data block within the current transmission window having been completed.

The first device transmits the first traffic data blocks to the second device in chronological order. If the second device also has service data to be sent to the first device, the second device also generates second service data blocks in time sequence and transmits the second service data blocks to the first device in time sequence.

The first device and the second device may perform link data transmission through a packet, where the packet includes a Header (Header) and a Payload (Payload), and the data block generated by the transmitting device is carried through the Payload (Payload) portion of the packet. The packets sent by the first device to the second device are referred to as first packets, and the packets sent by the second device to the first device are referred to as second packets.

The data transmission of a service data block, referred to in this disclosure, refers to a transmission device transmitting a packet containing the service data block one or more times until a specific condition is satisfied. When the specific condition is satisfied, the transmission of the service data block is considered to be completed. The specific condition may be set as required, for example, the receiving device may successfully receive the service data block, the number of times of transmission of the service data block reaches a preset number of times, the time of transmission of the service data block reaches a preset time, or a combination of the above several conditions, and so on.

The transmission of one service data block related to the sending device in this disclosure refers to that the packet sent by the sending device to the receiving device contains the service data block, but the content of the packet sent by the receiving device to the sending device is not limited.

The first device and the second device perform synchronous link data transmission through a reserved transmission window, and the reserved transmission window which is currently used is the current transmission window. Each reserved transmission window may be sequentially divided into first and second intervals alternately distributed in time sequence as shown in fig. 4. The first interval is for the first device to send packets to the second device and the second interval is for the second device to send packets to the first device. The lengths of the first section and the second section may be the same or different.

The specific condition of whether or not transmission of one first service data block associated with the first device is completed may be set as needed.

In some embodiments, the transmission of one first traffic data block associated with the first device may take the form of no retransmission. When the retransmission is not adopted, the first device sends the packet containing the first service data block to the second device, and then receives a packet sent by the second device in the second interval, and then considers that the transmission associated with the first service data block is completed.

In other embodiments, the transmission of one first traffic data block associated with the first device may employ retransmission without crossing the transmission window. In this way, after the first device sends the packet containing the first service data block to the second device, the feedback information containing the last packet sent by the first device is received, wherein the feedback information indicates whether the last packet is successfully received by the second device; if the second device does not successfully receive the first service data block, retransmitting the packet containing the first service data block, and then receiving the packet containing the feedback information transmitted by the second device. This process continues until the second device feeds back that it has successfully received a packet containing the first traffic data block, or the current transmission window ends, and the transmission associated with the first traffic data block is deemed complete. Since the transmitting device and the receiving device alternately transmit packets in time order, what is referred to as a "last packet" in this disclosure is a last packet with respect to a packet currently transmitted by the receiving device, that is, a most recent packet transmitted by the transmitting device before a current packet transmitted by the receiving device.

In other embodiments, retransmission schemes that can span transmission windows may be employed. In this way, if the first device does not receive feedback information that the second device has successfully received the packet including the first service data block sent by the first device until the current transmission window ends, the first device considers that the transmission of the first service data block is not completed, and continues to transmit in the reserved transmission window corresponding to the first service data block until the second device feeds back that the second device has successfully received the packet including the first service data block, or the reserved transmission window corresponding to the service data block ends. It can be seen that the retransmission scheme that can cross the transmission window differs from the retransmission scheme that does not cross the transmission window in that the former can continue to transmit the same service data block across the transmission window.

For the retransmission method in the above two embodiments, a check code may be added to the packet sent by the first device, where the check code includes check information of the first service data block, and the second device determines whether to successfully receive the packet sent by the first device by calculating whether the check code is correct.

In some embodiments, the data links of the first device and the second device are bi-directional links, i.e. both the first device and the second device have traffic data to send to the other party. In this embodiment, the second device sends the second service data block it generated to the first device via the second packet. In some embodiments, the second packet may further include feedback information indicating whether the second device successfully received the last first packet sent by the first device. Accordingly, the first device, after receiving the second packet transmitted by the second device, may include feedback information indicating whether it successfully received the last second packet transmitted by the second device in the first packet transmitted subsequently thereto.

In some embodiments, the digitally controlled links of the first device and the second device are unidirectional links, i.e. the second device has no traffic data to send to the first device. In this embodiment, the second packet may include feedback information indicating whether the second device successfully received the last first packet transmitted by the first device, but does not include a traffic data block.

In the present disclosure, determining whether there is enough remaining time in the current transmission window refers to whether there is enough one transmission of the first service data block associated with the first device in the remaining time of the current transmission window after the data transmission associated with the last first service data block is completed. I.e. whether the remaining time is sufficient for the first device to send a packet of the first traffic data block associated with the first device to the second device and to receive a packet from the second device.

Since the length of the first traffic data block is typically fixed, the length of time the first device sends a packet containing the first traffic data block to the second device is fixed, e.g. may be equal to the length of the first interval. The time required for the second device to transmit the packet may be varied as appropriate and may be shorter than the length of the second section but must not exceed the length of the second section. For example, when the second device needs to transmit a packet of a fixed length, the time required for the second device to transmit the packet may be equal to the length of the second section. When the second device does not have a service data block to send to the first device, the packet sent by the second device may not contain a payload, but simply send feedback information to the first device indicating whether the second device successfully received the packet sent by the first device. The first device may determine whether there is sufficient remaining time in the current transmission window according to the above. When the first device cannot determine whether the second device has a service data block to send to the first device, the time required for the second device to send the packet may be set to the time required for including the service data block.

In step 120, in response to the current transmission window having sufficient time remaining, data transmission associated with the first traffic data block currently to be transmitted is performed with the second device at the time remaining.

When the transmission of one service data block associated with the transmitting device has been completed, the next service data block to be transmitted by the transmitting device is taken as the current service data block to be transmitted. It will be appreciated that since each service data block corresponds to a reserved transmission window, the start time of the reserved transmission window corresponding to the currently to be transmitted service data block is later than the current transmission window.

In this step, if the first device confirms that there is enough time remaining for the current transmission window, the remaining time is continued for data transmission associated with the first traffic data block to be transmitted. In this way, the first service data block corresponding to the next reserved transmission window is sent in advance to the current transmission window, so that the resources of the reserved transmission window can be fully utilized, and if the first service data block corresponding to the next reserved transmission window is successfully transmitted in the current transmission window, the next reserved transmission window can be used for sending other links or service data.

In the present disclosure, a manner in which a first service data block corresponding to a future reserved transmission window is transmitted before a start time of the future reserved transmission window arrives is referred to as pre-transmission of the first service data block.

In some embodiments, after the step 120 is performed, the step 110 may be continued until the current transmission window does not have enough time remaining. If there is not enough time remaining in the current transmission window, step 130 is performed.

In step 130, in response to the current transmission window not having enough remaining time, taking the reserved transmission window corresponding to the first service data block to be transmitted currently as a new transmission window, and performing data transmission associated with the first service data block to be transmitted currently with the second device in the new transmission window.

The first service data block to be transmitted may be a new service data block that the first device has not sent to the second device, or may be a service data block that the first device has pre-transmitted to the second device in a previous transmission window, but has not yet transmitted to the second device.

As can be seen from the above steps, compared with the prior art, the method 100 of the present disclosure uses the pre-transmission mechanism, so that the reserved transmission window corresponding to the service data block that is transmitted through the pre-transmission mechanism is no longer used for the transmission of the current data link, thereby freeing more continuous time slices for the data transmission of other links, reducing the fragmentation degree of the time slices, reducing the link switching frequency, and thus reducing the scheduling difficulty under the circumstance of multi-link multi-service concurrency.

It should be noted that, since the bluetooth SCO link does not retransmit, the embodiment of the method 100 regarding the transmission manner of the service data block without retransmission may be applied to the bluetooth SCO link. Since the transmission interval of HV2 packets in the bluetooth SCO link specified by the protocol is 4 slots, and the transmission interval of HV3 packets is 6 slots, but the slot lengths required for HV2 and HV3 packet transmission are both 1 slot, there is a remaining time after the first device and the second device perform one packet interaction until the next reserved transmission window. Thus, the method 100 of the present disclosure may be applied to a bluetooth SCO link, and the type of packet sent by the first device or the second device may be HV2 or HV3.

Since the bluetooth eSCO link supports retransmissions, the embodiment of the method 100 regarding the manner of transmission of the retransmitted traffic data blocks can be applied to bluetooth eSCO links. And the transmission mode associated with the first service data block can be a mode without crossing transmission windows or a mode with crossing transmission windows.

To facilitate an understanding of the present disclosure by those skilled in the art, fig. 5-8 illustrate the method 100 of the present disclosure further by way of different embodiments, respectively. In fig. 5-7, three consecutive reserved transmission windows 240, 241, and 242 are exemplarily shown, and the first device generates three consecutive first traffic data blocks A, B, C corresponding to reserved transmission windows 240, 241, and 242, respectively. The second device generates three consecutive second traffic data blocks 1, 2, 3. A, B or C in the figure indicates that the first packet sent by the first device contains a first service data block A, B or C, and 1, 2 or 3 indicates that the second packet sent by the second device contains a second service data block 1, 2 or 3. The "ACK" indicates feedback information generated by the second device indicating that it successfully received the last first packet transmitted by the first device, and the "NAK" indicates feedback information generated by the second device indicating that it did not successfully receive the last first packet transmitted by the first device.

Fig. 5 illustrates one embodiment of using the method 100 of the present disclosure in which a first traffic data block B is pre-transmitted and transmitted successfully.

As shown in fig. 5, the first device starts at the start time of the reserved transmission window 240 corresponding to the first service data block a, and performs data transmission associated with the first service data block a, so the reserved transmission window 240 is used as the current transmission window. The first device transmits a first packet containing a in a first interval 2401 at the beginning and receives a second packet transmitted by the second device in a second interval 2402 immediately following, the second packet including a second traffic data block 1 and an "ACK" for the first packet. After receiving the "ACK", the first device confirms that the data transmission associated with the first service data block a is completed, and the first service data block to be transmitted currently is B. The first device determines whether there is sufficient remaining time for the current transmission window 240 (step 110), and after confirming that there is sufficient remaining time, performs data transmission associated with the first service data block B for the remaining time (step 120). The first device first sends a new first packet to the second device, wherein the new first packet comprises a first service data block B and feedback information 'NAK' for the second packet, and the second device retransmits the second service data block 1 after receiving the NAK. After the first device sends the data twice, the data transmission associated with the first service data block B is completed, and the first service data block to be transmitted currently is C. And if the first device determines that the current transmission window does not have enough residual time, the first device uses the reserved transmission window 242 corresponding to the first service data block C as a new transmission window, and performs data transmission associated with the first service data block C with the second device.

As can be seen from this embodiment, after the pre-transmission of the first service data block B is completed, the corresponding reserved transmission window 241 is vacated, and may be used for transmission of other links or service data. Such that the continuous time slice from the end of transmission window 240 to the start of transmission window 242 is available for other link or traffic data transmissions.

Fig. 6 illustrates another embodiment of a method 100 using the present disclosure, in which a first traffic data block B is pre-transmitted but the transmission is unsuccessful.

The difference between this embodiment and the embodiment shown in fig. 5 is that in this embodiment, although the pre-transmission is unsuccessful for the first service data block B of the pre-transmission, since the current window 240 ends, the transmission of B is no longer performed in the pre-transmission window 241 corresponding to the first service data block B. The implementation mode is characterized in that after the first service data block is pre-transmitted, a reserved transmission window corresponding to the pre-transmitted first service data block can be always set aside for transmission of other links or service data. This implementation is essentially through the partial tolerance to packet loss in exchange for a reduction in the degree of time slice fragmentation.

Fig. 7 illustrates another embodiment of a method 100 using the present disclosure, in which a first traffic data block B is pre-transmitted and the transmission is unsuccessful, continuing the transmission in its corresponding reserved transmission window.

The difference between this embodiment and the embodiment shown in fig. 6 is that in this embodiment, for the first traffic data block B that is pre-transmitted, the first traffic data block to be currently transmitted is still B if the transmission was not successful before the end of the current window 240. Therefore, the reserved transmission window 241 corresponding to the first service data block B is used as a new transmission window, and after the start time of the new transmission window is reached, the new transmission window becomes the current transmission window, and the transmission of the first service data block B is continued in the current transmission window 241 (step 130). In addition, after the transmission of the first service data block B is successful, the first device determines whether the current transmission window 241 has enough remaining time (step 110), and after confirming that the transmission window 241 has enough remaining time, performs data transmission associated with the first service data block C at the remaining time (step 120).

For this embodiment, since the pre-transmitted first service data block may be retransmitted across the transmission window, the first service data block has more transmission opportunities, so that the probability of successful transmission of the first service data block may be improved.

Fig. 8 illustrates another embodiment of using the method 100 of the present disclosure, in which both first traffic data blocks B and C are pre-transmitted and the transmission is successful.

In this embodiment, the first device determines whether there is enough remaining time in the current transmission window after the first service data block a transmitted in the current transmission window is successfully transmitted (step 110). After confirming that there is sufficient remaining time, data transmission associated with the first traffic data block B is performed for the remaining time (step 120). After the first service data block B is successfully transmitted, it is determined whether there is enough remaining time in the current transmission window (step 110). After confirming that there is sufficient remaining time, data transmission associated with the first traffic data block C is performed for the remaining time (step 120).

In this embodiment, since the transmission of the first service data blocks B and C is completed in the reserved transmission window corresponding to the data block a, the reserved transmission windows corresponding to the first service data blocks B and C can be used for the transmission of other links or service data.

Fig. 9 shows a flowchart of a method 400 of synchronous link data transmission in accordance with yet another embodiment of the present disclosure. Similar to method 100, method 400 is performed by a first device for synchronous link data transmission between the first device and a second device. The method 400 includes the steps of:

in step 410, it is determined whether the current transmission window has sufficient time remaining in response to the data transmission associated with the last first traffic data block within the current transmission window having been completed.

This step may refer to step 110 of the method 100 and will not be described in detail herein.

In step 420, in response to the current transmission window having sufficient time remaining for data transmission associated with the first traffic data block currently to be transmitted with the second device.

This step may refer to step 120 of method 100 and is not described in detail herein.

In step 430, in response to the data transmission associated with the first service data block to be currently transmitted being completed, taking the reserved transmission window corresponding to the new first service data block to be transmitted as a new transmission window, and performing data transmission associated with the new first service data block to be transmitted with the second device in the new transmission window.

In this step, after the first device confirms that the data transmission associated with the first service data block to be currently transmitted is completed, it means that the first service data block has been pre-transmitted in the current transmission window, and the reserved transmission window corresponding to the first service data block may be used for data transmission of other links or other services. Therefore, in this step, no matter whether the current transmission window has the remaining time, the pre-transmission is not continued on the new first service data block to be transmitted in the current transmission window, but the transmission is performed until the start of the reserved transmission window corresponding to the new first service data block to be transmitted, and then the new first service data block to be transmitted is transmitted.

As shown in fig. 10, the first device starts data transmission associated with the first service data block a at the start time of the reserved transmission window 240 corresponding to the first service data block a, and after confirming that data transmission associated with the first service data block a is completed, the first service data block to be currently transmitted is B. The first device determines whether there is sufficient remaining time for the current transmission window 240 (step 410) and, after confirming that there is sufficient remaining time, performs data transmission associated with the first traffic data block B for the remaining time (step 420). After the data transmission associated with the first service data block B is completed, the first service data block to be transmitted currently is C. At this time, although the current transmission window still has enough remaining time for transmitting the first service data block C, the first device does not continue to transmit the first service data block C for the remaining time, but uses the reserved transmission window 242 corresponding to the first service data block C as a new transmission window, and performs data transmission associated with the first service data block C with the second device in the new transmission window (step 430).

As can be seen from this embodiment, after one pre-transmission in the remaining time of the current transmission window, the first device does not use the remaining time for transmission of the new first service data block, but performs transmission in the pre-transmission window corresponding to the new first service data block, although the remaining time remains in the current transmission window. Therefore, for the method 400, the time advance between the transmission time of the first service data block participating in the pre-transmission and the start time of the reserved transmission window of the first service data block is smaller than the preset interval, so that the time jitter (jitter) of the first service data block received by the second device is smaller, and the method is suitable for the occasion with strict requirements on the time delay jitter. The method 400 is effectively a trade-off between the degree of improvement in time slice fragmentation and the time jitter of the traffic data blocks.

The present disclosure also provides a communication device comprising a processor and a non-transitory storage medium storing computer-executable instructions. The computer-executable instructions may be executed by a processor to perform the functions or steps of the various embodiments of the synchronous link data transmission method 100 or 400 described above.

The present disclosure also provides a non-transitory computer-readable storage medium storing computer-executable instructions which, when executed by a computer, may perform the functions or steps of the various embodiments of the methods 100 or 400.

Other variations to the disclosed embodiments can be understood and effected by those skilled in the art from a reading of the specification, the disclosure, and the drawings, and the appended claims, in which the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. In the practice of the application, a single component may perform the functions of several of the features recited in the claims. Any reference signs in the claims shall not be construed as limiting the scope.

Claims

1. A synchronous link data transmission method for data transmission of a synchronous link between a first device and a second device, the synchronous link having reserved transmission windows set at preset intervals, the first device generating first traffic data blocks each corresponding to a time sequence of the reserved transmission windows, the method being performed by the first device, the method comprising:

step S1: judging whether the current transmission window has enough residual time or not in response to the completion of data transmission associated with the last first service data block in the current transmission window;

Step S2: and in response to the current transmission window having enough remaining time, performing data transmission associated with the first service data block to be transmitted currently with the second device.

2. The method of claim 1, wherein the method further comprises:

and repeatedly executing the step S1 and the step S2 until the current window does not have enough residual time.

3. The method of claim 1, wherein the method further comprises:

and responding to the fact that the current transmission window does not have enough residual time, taking a reserved transmission window corresponding to the first service data block to be transmitted currently as a new transmission window, and carrying out data transmission associated with the first service data block to be transmitted currently in the new transmission window and the second equipment.

4. The method of claim 1, wherein the method further comprises:

and responding to the completion of the data transmission associated with the first service data block to be transmitted currently, taking a reserved transmission window corresponding to a new first service data block to be transmitted as a new transmission window, and carrying out the data transmission associated with the new first service data block to be transmitted on the new transmission window and the second equipment.

5. The method of claim 1, wherein the preset interval of the link is determined by negotiations by the first device and the second device when establishing the link.

6. The method of claim 1, wherein the current transmission window comprises first intervals and second intervals that are alternately distributed in time order, the first intervals for the first device to send packets to the second device, the second intervals for the second device to send packets to the first device.

7. The method of claim 1, wherein transmitting data associated with the first traffic data block currently to be transmitted with the second device comprises:

transmitting a first packet including the first service data block currently to be transmitted to the second device;

and receiving a second packet sent by the second device.

8. The method of claim 7, wherein the synchronization link is a bluetooth SCO link.

9. The method of claim 8, wherein the first packet is a HV2 packet or a HV3 packet.

10. The method of claim 1, wherein transmitting data associated with the first traffic data block currently to be transmitted with the second device comprises:

The following steps are sequentially executed until the transmission of the first service data block to be transmitted is completed:

receiving feedback information sent by the second device, wherein the feedback information indicates whether the second device successfully receives a last first packet sent by the first device; and

and judging whether the transmission of the first service data block to be transmitted is completed or not.

11. The method of claim 10, wherein determining whether transmission of the first block of traffic data currently to be transmitted is complete comprises:

and if the feedback information of the last first packet sent by the first device is received in the current transmission window, the second device feedback indicates that the second device has successfully received the feedback information of the last first packet sent by the first device, and the transmission of the first service data block to be transmitted currently is confirmed to be completed.

12. The method of claim 11, wherein determining whether transmission of the first block of traffic data currently to be transmitted is complete further comprises:

and if the current transmission window is finished, confirming that the transmission of the first service data block to be transmitted currently is finished.

13. The method of claim 11, wherein determining whether transmission of the first block of traffic data currently to be transmitted is complete further comprises:

and if the current transmission window is over but feedback information indicating that the second equipment has successfully received the last first packet sent by the first equipment is not received by the second equipment, confirming that the transmission of the first service data block to be transmitted currently is not completed.

14. The method of claim 10, wherein receiving feedback information sent by the second device indicating whether the second device successfully received a last first packet sent by the first device comprises:

and receiving a second packet sent by the second device, wherein the second packet comprises feedback information indicating whether the second device successfully receives a last first packet sent by the first device.

15. The method of claim 10, wherein receiving feedback information sent by the second device indicating whether the second device successfully received a last first packet sent by the first device comprises:

and receiving a second packet sent by the second device, wherein the second packet comprises feedback information indicating whether the second device successfully receives a last first packet sent by the first device, and further comprises a second service data block generated by the second device.

16. The method of claim 15, wherein the first packet further comprises feedback information indicating whether the first device successfully received a last second packet sent by the second device.

17. The method of claim 10, wherein the synchronization link is a bluetooth eSCO link.

18. A communication device comprising a processor and a non-transitory storage medium storing computer-executable instructions executable by the processor to perform the method of any one of claims 1-17.

19. A non-transitory computer readable storage medium storing computer executable instructions which, when executed by a computer, perform the method of any one of claims 1-17.