Terminal device and communication method thereof, and related device

Abstract

A terminal device and a communication method thereof, and a related device. The communication method of the terminal device comprises: when detecting that a target channel is in an idle state, performing availability probing on the target channel; and when probing that the target channel is available, using the target channel to communicate with a peer device. The technical solution of the present invention can improve the communication quality of an HB BLE terminal device.

Description

Terminal device and communication method thereof, and related device TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of communication, and in particular to a terminal device and a communication method thereof, and a related device. BACKGROUND

[0002] Bluetooth Low Energy (BLE) communication adopts a Gauss Frequency Shift Keying (GFSK) modulation mode and works in an Industrial Scientific Medical (ISM) frequency band of 2.4 GHz, with a frequency range of 2.400-2.4835 GHz. The ISM frequency band is divided into 40 channels (f = 2402 + k * 2MHz, k = 0, 1, …, 39), with a 2MHz interval between adjacent channels. BLE devices can also operate in higher bands (HB), such as unlicensed frequency bands of 5 GHz and 6 GHz. Accordingly, a BLE device operating in a higher band is referred to as an HB BLE device.

[0003] The HB BLE device accesses a channel using a Frame Based-Listen Before Talk (FB-LBT) mechanism. Specifically, before transmitting data using a target channel, the HB BLE device needs to listen to the target channel, and when the listening result indicates that the target channel is in an idle state, the HB BLE device can use the channel for transmission.

[0004] However, the communication quality of the current HB BLE device still needs to be improved. TECHNICAL PROBLEM

[0005] The problem solved by embodiments of the present application is to provide a terminal device and a communication method thereof, and a related device, to improve the communication quality of the HB BLE terminal device. TECHNICAL SOLUTION

[0006] To solve the above problems, embodiments of the present application provide a communication method of a terminal device, comprising:

[0007] When it is detected that a target channel is in an idle state, performing availability detection on the target channel;

[0008] When it is detected that the target channel is available, using the target channel to communicate with a peer device.

[0009] Optionally, the availability detection of the target channel comprises:

[0010] sending a probe data packet to the peer device using the target channel;

[0011] determining that the target channel is available when a reply to the probe data packet is received from the peer device.

[0012] Optionally, the probe data packet comprises any one of a null data packet and a blank data packet.

[0013] Optionally, the communication with the peer device using the target channel comprises communicating with the peer device in connection events.

[0014] Optionally, in the process of communicating with the peer device in connection events, the communication method of the terminal device further comprises:

[0015] sending a dynamic connection event unavailability notification to the peer device, so that the peer device refrains from sending data to the terminal device using an affected time period in a connection event;

[0016] or, receiving a dynamic connection event unavailability notification sent by the peer device, and refraining from communicating with the peer device using an affected time period in a connection event according to the dynamic connection event unavailability notification.

[0017] Optionally, the dynamic connection event unavailability notification comprises at least one of:

[0018] information of an early end time of a current connection event;

[0019] available information of a subsequent connection event;

[0020] information of a receiving capability and / or a sending capability of the current connection event;

[0021] information of a receiving capability and / or a sending capability of the subsequent connection event.

[0022] Optionally, the refraining from sending data to the peer device using an affected time period in a connection event according to the dynamic connection event unavailability notification comprises:

[0023] not sending data to the peer device using an affected time period in a connection event;

[0024] adjusting a parameter of an encapsulated data packet to be sent, so that a sending time of the encapsulated data packet does not use an affected time period in a connection event.

[0025] Optionally, the adjusting the parameter of the encapsulated data packet to be sent comprises any one of the following:

[0026] adjusting a physical transmission rate of the encapsulated data packet;

[0027] adjusting a payload length of the encapsulated data packet to be sent at a logical link layer or an isochronous adaptation layer;

[0028] generating the encapsulated data packet in an HDT Format1 format using a link layer, the encapsulated data packet in the HDT Format1 format comprising a plurality of blocks of the same payload data.

[0029] Optionally, in the process of communicating with the peer device in units of connection events, the terminal device and the peer device communicate in a master-slave mode; wherein the connection initiator in the terminal device and the peer device is a central device, and the connected device is a peripheral device.

[0030] Optionally, if the terminal device is a peripheral device and the sending capability of the terminal device is limited, the communicating with the peer device in units of connection events comprises:

[0031] sending display delay confirmation notification information to the peer device, the display delay confirmation notification information being used to indicate a connection event in which the terminal device only has a receiving capability and a data packet received in the connection event in which the terminal device only has the receiving capability will be delayed to a subsequent connection event in which the terminal device has a sending capability for reply;

[0032] receiving the encapsulated data packet sent by the peer device in the connection event in which the terminal device only has the receiving capability;

[0033] replying, in the subsequent connection event in which the terminal device has the sending capability, to the encapsulated data packet sent by the peer device in the connection event in which the terminal device only has the receiving capability.

[0034] Optionally, if the peer device is a peripheral device and the sending capability of the peer device is limited, the communicating with the peer device in units of connection events comprises:

[0035] receiving display delay confirmation notification information sent by the peer device, the display delay confirmation notification information being used to indicate a connection event in which the peer device only has a receiving capability and a data packet received in the connection event in which the peer device only has the receiving capability will be delayed to a subsequent connection event in which the peer device has a sending capability for reply;

[0036] continuously sending a plurality of encapsulated data packets in an HDT format to the peer device in the connection event in which the peer device only has the receiving capability.

[0037] after continuously sending a plurality of encapsulation data packets in HDT format to the peer device in a connection event in which the peer device only has receiving capability, receiving acknowledgement information that the plurality of encapsulation data packets in HDT format are received from the peer device in a subsequent connection event in which the peer device has transmitting capability.

[0038] Optionally, the plurality of encapsulation data packets in HDT format include a plurality of encapsulation data packets in HDT Format0 format and / or a plurality of encapsulation data packets in HDT Format1 format.

[0039] Optionally, the connection event includes a BLE event, and the terminal device and the peer device are respectively HB BLE devices.

[0040] Correspondingly, the embodiment of the present application further provides a terminal device, comprising:

[0041] a detection module adapted to detect a target channel in an idle state and perform availability detection on the target channel;

[0042] a communication module adapted to perform communication with the peer device using the target channel when it is detected that the target channel is available.

[0043] Correspondingly, the embodiment of the present application further provides a computer program product comprising computer programs / instructions for implementing the communication method of the terminal device according to any one of the above embodiments when executed by a processor.

[0044] Correspondingly, the embodiment of the present application further provides a device comprising at least one memory and at least one processor, wherein the memory stores one or more computer instructions, and the one or more computer instructions are executed by the processor to implement the communication method of the terminal device according to any one of the above embodiments.

[0045] Correspondingly, the embodiment of the present application further provides a storage medium storing one or more computer instructions for implementing the communication method of the terminal device according to any one of the above embodiments. Advantages

[0046] The communication method of the terminal device provided by the embodiment of the present application comprises: detecting a target channel in an idle state and performing availability detection on the target channel; and performing communication with a peer device using the target channel when it is detected that the target channel is available.

[0047] The communication method of the terminal device provided in the embodiment of the present application can improve the accuracy of channel detection when the target channel is detected to be in an idle state, and then the target channel is used to communicate with the opposite terminal device, so that the interference caused by other devices using the target channel for communication is avoided, and the communication quality of the terminal device is improved. BRIEF DESCRIPTION OF DRAWINGS

[0048] Fig. 1 is a flowchart of an embodiment of the communication method of the terminal device provided in the present application;

[0049] Fig. 2 is a schematic diagram of a position distribution relationship among terminal devices 1 to 3;

[0050] Figs. 3 to 5 are schematic diagrams of BLE communication between a BLE central device and a BLE peripheral device using dynamic BLE event unavailable notification;

[0051] Fig. 6 is a schematic diagram of the composition structure of an encapsulated data packet in HDT format;

[0052] Fig. 7 is a schematic diagram of BLE communication between a BLE central device and a BLE peripheral device using display delay confirmation notification;

[0053] Fig. 8 is a schematic diagram of an embodiment of the terminal device provided in the present application;

[0054] Fig. 9 is a schematic diagram of an optional hardware structure of the device provided in the present application. Embodiments of the present application

[0055] As known from the background, the communication quality of the current HB BLE device still needs to be improved.

[0056] To solve the technical problem, the communication method of the terminal device provided in the embodiment of the present application comprises: when a target channel is detected to be in an idle state, the availability of the target channel is detected; and when the target channel is detected to be available, the target channel is used to communicate with the opposite terminal device.

[0057] The communication method of the terminal device provided in the embodiment of the present application can improve the accuracy of channel detection when the target channel is detected to be in an idle state, and then the target channel is used to communicate with the opposite terminal device, so that the interference caused by other devices using the target channel for communication is avoided, and the communication quality of the terminal device is improved.

[0058] In order to make the above objectives, characteristics and advantages of the present application more apparent, more comprehensible, specific embodiments of the present application are described in detail below with reference to the drawings.

[0059] Fig. 1 shows a flow diagram of an embodiment of the communication method of the terminal device provided by the present application. Referring to Fig. 1, the communication method of the terminal device can specifically include the following steps:

[0060] Step S110: When it is detected that the target channel is in an idle state, performing availability detection on the target channel.

[0061] Step S120: When it is detected that the target channel is available, using the target channel to communicate with the peer device.

[0062] Please continue to refer to Fig. 1, and perform step S110: When it is detected that the target channel is in an idle state, performing availability detection on the target channel.

[0063] When it is detected that the target channel is in an idle state, performing availability detection on the target channel, which provides a basis for subsequent use of the target channel to communicate with the peer device when it is detected that the target channel is available.

[0064] In this embodiment, the terminal device is a terminal device that communicates using the HB BLE communication protocol. Specifically, the terminal device includes an HB BLE module. It can be understood that the terminal device can also communicate using other communication protocols, which is not limited herein.

[0065] In this embodiment, the terminal device uses a Frame-Based Listen Before Talk mechanism for channel access. Specifically, before the terminal device sends valid data to the peer device, it first uses a Clear Channel Assessment (CCA) technology to detect the target channel to determine whether the target channel is in an idle state or a busy state. When it is detected that the target channel is in a busy state, the terminal device cannot use the target channel to communicate with the peer device using HB BLE; when it is detected that the target channel is in an idle state, the terminal device can use the target channel to communicate with the peer device using HB BLE.

[0066] However, the BLE signal coverage of the terminal device is limited, resulting in limited CCA detection range. Even if the CCA technology detects that the target channel is in an idle state, there may still be other devices outside the BLE signal coverage of the terminal device that are using the target channel for communication.

[0067] Please refer to FIG. 2. The terminal device 2 and the terminal device 1 have established a BLE connection, and the terminal device 3 is also present around the terminal device 1. The distance between the terminal device 2 and the terminal device 3 is far, so that the BLE signal coverage of the terminal device 2 and the BLE signal coverage of the terminal device 3 only have a small part of overlap, resulting in that the terminal device 2 and the terminal device 3 cannot detect the presence of each other. Therefore, even if the terminal device 3 is using the target communication channel for communication, the terminal device 2 cannot detect that the terminal device 3 is using the target channel for communication, so that the channel detection result of the terminal device 2 is still idle.

[0068] When detecting that the target channel is in an idle state, the terminal device 2 sends data to the terminal device 1, resulting in that the data sent by the terminal device 2 to the terminal device 1 is interfered by the terminal device 3, so that the terminal device 1 cannot correctly receive the data sent by the terminal device 2, affecting the communication quality between the terminal device 2 and the terminal device 1.

[0069] Therefore, after detecting that the target channel is in an idle state, the terminal device can detect whether there is other device outside the detection range thereof that is using the target channel for communication by performing availability detection on the target channel, so as to determine whether the target channel is truly in an idle state, that is, to determine whether the target channel is available.

[0070] In this embodiment, the step of performing availability detection on the target channel by the terminal device includes: sending a probe data packet to the opposite terminal device using the target channel; and determining that the target channel is available when receiving a reply of the opposite terminal device to the probe data packet.

[0071] When there is no other terminal device within the detection range of the opposite terminal device that is using the target channel for communication outside the detection range of the terminal device, the probe data packet sent by the terminal device to the opposite terminal device using the target channel will not be interfered by other devices using the target channel for communication, so that the opposite terminal device can correctly receive the probe data packet and can reply to the probe data packet. Therefore, when receiving the reply of the opposite terminal device to the probe data packet, the terminal device can determine that the target channel is available.

[0072] When there is another terminal device outside the listening range of the terminal device and within the listening range of the peer terminal device, and the other terminal device is using the target channel to communicate, the probe data packet sent by the terminal device to the peer terminal device using the target channel will be interfered by the communication of the other terminal device using the target channel, so that the peer terminal device cannot correctly receive the probe data packet, and cannot reply to the probe data packet. Accordingly, when the reply of the peer terminal device to the probe data packet is not received, the terminal device can determine that the target channel is unavailable.

[0073] Therefore, when the terminal device detects that the target channel is in an idle state, the availability of the target channel is probed again, which not only can confirm that the devices within the listening range of the terminal device do not use the target channel to communicate, but also can confirm that the devices outside the listening range of the terminal device and within the listening range of the peer terminal device also do not use the communication channel to communicate, thereby improving the accuracy of channel detection.

[0074] It should be noted that the above example takes the terminal device 3 as an example to illustrate the terminal device outside the listening range of the terminal device 2 and within the listening range of the terminal device 1. It can be understood that the number of terminal devices outside the listening range of the terminal device 2 can also be multiple.

[0075] In this embodiment, the probe data packet is a packet without valid data. For example, the probe data packet is an empty data PDU or a NULL data PDU.

[0076] The probe data packet is a packet without valid data, so that the packet size of the probe data packet is small, which is beneficial to improve the efficiency of availability detection of the target channel.

[0077] In other embodiments, the probe data packet can also be other types of data packets, which are not limited herein.

[0078] Please continue to refer to FIG. 1, and perform step S120. When it is detected that the target channel is available, the target channel is used to communicate with the peer terminal device.

[0079] When it is detected that the target channel is available, the target channel is used to communicate with the peer terminal device, so that the data interaction between the terminal device and the peer terminal device using the target channel will not be interfered by the communication of other devices using the target channel, thereby facilitating to improve the communication quality of the terminal device.

[0080] In this embodiment, the step of communicating with the peer device using the target channel comprises: communicating with the peer device in units of connection events.

[0081] In this embodiment, the terminal device is an HB BLE device. Accordingly, the terminal device communicates with the peer device in units of BLE events.

[0082] The target channel is divided into time units, referred to as BLE events, at the BLE link layer (LL) of the HB BLE device. The starting time and the closing time of each BLE event are determined in advance by negotiation between the terminal device and the peer device.

[0083] It should be noted that, in the process of the terminal device communicating with the peer device in units of BLE events, other devices can use the target channel for communication, which interferes with the HB BLE communication between the terminal device and the peer device.

[0084] Accordingly, in the process of the terminal device communicating with the peer device in units of BLE events, when the communication between the terminal device and the peer device is interfered, the communication method of the terminal device further comprises: sending a dynamic BLE event unavailable notification to the peer device, so that the peer device avoids sending data to the terminal device in the affected time period in the connection event; or receiving a dynamic BLE event unavailable notification sent by the peer device, and avoiding sending data to the peer device in the affected time period in the connection event according to the dynamic BLE event unavailable notification.

[0085] After the BLE connection is established between the terminal device and the peer device, the BLE communication between the terminal device and the peer device will adopt a master-slave mode. Among them, the initiator of the BLE connection between the terminal device and the peer device is referred to as a BLE central device (BLE Central), and the connected one among the terminal device and the peer device is referred to as a BLE peripheral device (BLE Peripheral).

[0086] When the terminal device and the peer device communicate with each other in units of BLE events, the terminal device can be the connection initiator of the BLE connection, or can be the connected one of the BLE connection. Therefore, the terminal device can communicate with the peer device in units of BLE events as a BLE central device and a BLE peripheral device, and can also communicate with the peer device in units of BLE events as a BLE peripheral device and a BLE central device.

[0087] The dynamic BLE event unavailable notification can be sent by a BLE central device to a BLE peripheral device, or sent by a BLE peripheral device to a BLE central device. Correspondingly, the terminal device can send the dynamic BLE event unavailable notification to the peer terminal device as a BLE peripheral device to the peer terminal device as a BLE central device, or receive the dynamic BLE event unavailable notification sent by the peer terminal device as a BLE peripheral device to the peer terminal device as a BLE central device. The terminal device can also send the dynamic BLE event unavailable notification to the peer terminal device as a BLE central device to the peer terminal device as a BLE peripheral device, or receive the dynamic BLE event unavailable notification sent by the peer terminal device as a BLE central device to the peer terminal device as a BLE peripheral device.

[0088] The dynamic BLE event unavailable notification can include any one of the following: information of an early end time of a current BLE event, information of a subsequent BLE event, information of a receiving capability and / or a sending capability of the current BLE event, and information of a receiving capability and / or a sending capability of the subsequent BLE event.

[0089] In a case where the dynamic BLE event unavailable notification includes the information of the early end time of the current BLE event, the dynamic BLE event unavailable notification is used to make the terminal device or the peer terminal device as a receiver of the dynamic BLE event unavailable notification maintain BLE communication with the peer terminal device or the terminal device as a sender of the dynamic BLE event unavailable notification before the early end time of the current BLE event, and stop sending data to the peer terminal device or the terminal device as the sender of the dynamic BLE event unavailable notification after the early end time of the current BLE event.

[0090] In the embodiment, the information of the subsequent BLE event includes information of a subsequent available BLE event and a subsequent unavailable BLE event.

[0091] Correspondingly, in a case that the dynamic BLE event unavailable notification comprises available information of a subsequent BLE event, the dynamic BLE event unavailable notification is used to instruct the peer device or the terminal device as a receiver of the dynamic BLE event unavailable notification to maintain BLE communication between the peer device or the terminal device and the terminal device or the peer device as a sender of the dynamic BLE event unavailable notification before an end time of the current BLE event, and is further used to instruct the peer device or the terminal device as a receiver of the dynamic BLE event unavailable notification to skip a subsequent unavailable BLE event after the end of the current BLE event, and continue BLE communication with the terminal device or the peer device as a sender of the dynamic BLE event unavailable notification using a subsequent available BLE event.

[0092] The receiving capability of the current BLE event refers to whether the sender of the dynamic BLE event unavailable notification can receive data in the current BLE event. The sending capability of the current BLE event refers to whether the sender of the dynamic BLE event unavailable notification can send data in the current BLE event.

[0093] In a case that the dynamic BLE event unavailable notification comprises information of the receiving capability and / or the sending capability of the current BLE event, the dynamic BLE event unavailable notification is used to instruct the peer device or the terminal device as a receiver of the dynamic BLE event unavailable notification whether to be able to send data to the terminal device as a sender of the dynamic BLE event unavailable notification using the current BLE event and / or receive data sent by the terminal device, and is further used to instruct the terminal device or the peer device as a sender of the dynamic BLE event unavailable notification to no longer perform BLE communication between the peer device or the terminal device as a receiver of the dynamic BLE event unavailable notification after the end of the current BLE event.

[0094] The receiving capability of the subsequent BLE event refers to whether the sender of the dynamic BLE event unavailable notification can receive data in other BLE events after the current BLE event. The sending capability of the subsequent BLE event refers to whether the sender of the dynamic BLE event unavailable notification can send data in other BLE events after the current BLE event.

[0095] In a case where the dynamic BLE event unavailable notification includes information of receiving capability and / or sending capability of the subsequent BLE event, the dynamic BLE event unavailable notification is used to instruct the peer device or the terminal device as the receiver of the dynamic BLE event unavailable notification to send data to the terminal device or the peer device as the sender of the dynamic BLE event unavailable notification and / or receive data sent by the terminal device or the peer device as the sender of the dynamic BLE event unavailable notification using the current BLE event, and to instruct the peer device or the terminal device as the receiver of the dynamic BLE event unavailable notification to skip the subsequent unavailable BLE event after the current BLE event ends and continue to send data to the terminal device or the peer device as the sender of the dynamic BLE event unavailable notification and / or receive data sent by the peer device or the terminal device as the receiver of the dynamic BLE event unavailable notification using the subsequent available BLE event.

[0096] Please refer to FIG. 3, in the duration of the current BLE event, the BLE central device transmits two data packets P301 and P302 to the BLE peripheral device on the target channel, and the BLE peripheral device transmits two data packets P311 and P312 to the BLE central device on the target channel. Among them, the BLE peripheral device carries a dynamic BLE event unavailable notification in the data packet P311, and carries information of the early end time T31 of the current BLE event in the dynamic BLE event unavailable notification.

[0097] Correspondingly, after the BLE central device receives the dynamic BLE event unavailable notification transmitted by the BLE peripheral device on the target channel and obtains the early end time T31 of the current BLE event from the dynamic BLE event unavailable notification, the BLE central device adjusts the parameters of the transmitted data packet P302 so that the end time of the data packet P302 is located before the early end time T31 of the current BLE event, so that the unavailable time T31-T32 in the current BLE event will not be used.

[0098] Please refer to FIG. 4, in the duration of the current BLE event, the BLE central device transmits two data packets P401 and P402 to the BLE peripheral device on the target channel, and the BLE peripheral device transmits two data packets P411 and P412 to the BLE central device on the target channel. Among them, the BLE central device carries a dynamic BLE event unavailable notification sent to the BLE peripheral device in the data packet P401, and carries information of the early end time T41 of the current BLE event in the dynamic BLE event unavailable notification.

[0099] Correspondingly, the BLE peripheral device receives the dynamic BLE event unavailability notification transmitted by the BLE central device in the current BLE event, and obtains the early end time T41 of the current BLE event therefrom, and then adjusts the parameter of the transmitted data packet P412 so that the end time of the data packet P412 is located before the early end time T41 of the BLE event 1, thereby not using the unavailable time T41-T42 in the current BLE event.

[0100] Please refer to FIG. 5, in the duration of the BLE event 1, the BLE central device transmits two data packets P501 and P502 to the BLE peripheral device on the target channel, and the BLE peripheral device transmits two data packets P511 and P512 to the BLE central device on the target channel. Among them, the dynamic BLE event unavailability notification transmitted by the BLE peripheral device to the BLE central device is carried in the data packets P511 and P512, and the unavailability time of the BLE event 2 and the information that the BLE event 3 is available are carried in the dynamic BLE event unavailability notification.

[0101] Correspondingly, the BLE central device receives the dynamic BLE event unavailability notification transmitted by the BLE peripheral device in the BLE event 1, and obtains the information that the BLE event 2 is unavailable and the BLE event 3 is available therefrom, and then the BLE central device performs normal BLE communication with the BLE peripheral device in the BLE event 1, skips the BLE event 2 after the BLE event 1 ends, and continues to attempt to transmit the data packet P503 to the BLE peripheral device in the BLE event 3, and receives the data packet P513 transmitted by the BLE peripheral device.

[0102] In the embodiment, the step of adjusting the parameter of the encapsulated data packet to be transmitted by the terminal device comprises: adjusting the physical transmission rate of the encapsulated data packet, or adjusting the load length of the encapsulated data packet in the logical link and adaptation layer (L2CAP) or isochronous adaptation layer (ISOAL), or using the link layer to generate an encapsulated data packet in the high data throughput (HDT) Format1 format.

[0103] In the case where the dynamic BLE event unavailability notification comprises the information of the early end time of the current BLE event, by adjusting the physical rate of the encapsulated data packet, or adjusting the load length of the encapsulated data packet in the logical link and adaptation layer or isochronous adaptation layer, the terminal device can transmit the data packet to be transmitted to the opposite device before the early end time of the current BLE event.

[0104] Please refer to Fig. 6(b), in this embodiment, the encapsulation data packet in HDT Format1 format includes a Preamble field, a Control field, a Protocol Data Unit (PDU) Header field and a Payload field. The PDU Header field carries a sequence number identification field, and the byte length of the sequence number identification field is longer than the byte length of the sequence number field in the conventional BLE encapsulation data packet, such as 3 bits. Accordingly, the link layer is used to generate the encapsulation data packet in HDT Format1 format, so that the terminal device can send multiple payload PDUs that have not been confirmed by the peer device to the peer device.

[0105] Meanwhile, the payload PDUs with different sequence number identifications in the encapsulation data packet in HDT Format1 format can be further divided into multiple blocks and each block can be independently sent. Please refer to Fig. 6, the encapsulation data packet in HDT Format1 format includes two blocks of payload protocol data unit 1, Payload1 Block, and two blocks of payload protocol data unit 2, Payload2 Block.

[0106] Accordingly, in the case that the dynamic BLE event unavailable notification includes subsequent available BLE event information, by using the link layer to generate the encapsulation data packet in HDT Format1 format, the same payload protocol data unit with the same sequence number identification can be divided into blocks, so that the terminal device can send part of the blocks of the encapsulation data packet in HDT Format1 format before the current BLE event ends, skip the subsequent unavailable BLE event after the current BLE event ends, and continue to send the remaining blocks of the encapsulation data packet in HDT Format1 format to the peer device in the subsequent available BLE event, so that the communication between the terminal device and the peer device does not use the affected BLE event.

[0107] By interacting the dynamic BLE event unavailable notification between the terminal device and the peer device, the terminal device and the peer device do not communicate using the affected BLE event, so that the interaction between the terminal device and the peer device is not disturbed by other devices, and thus the communication quality between the terminal device and the peer device is improved.

[0108] It can be understood that in the process of communicating with the peer device as a BLE central device, the terminal device cannot send data to the peer device as a BLE central device using BLE events due to limited sending capability, but can still receive data from the peer device as a BLE central device using BLE events.

[0109] Correspondingly, when the sending capability of the terminal device as a BLE peripheral device is limited, the step of the terminal device communicating with the peer device in units of BLE events further includes: sending display delay confirmation notification information to the peer device, the display delay confirmation notification information being used to indicate that the terminal device only has a BLE event with receiving capability and a data packet received in the BLE event with only receiving capability will be delayed to a subsequent BLE event with sending capability for reply; receiving the data packet sent by the peer device in the BLE event with only receiving capability; and after receiving the data packet sent by the peer device in the BLE event with only receiving capability, replying to the data packet sent by the peer device in the BLE event with only receiving capability of the terminal device in the subsequent BLE event with sending capability.

[0110] Similarly, in the process of communicating with the peer device as a BLE central device, the peer device cannot send data to the terminal device as a BLE central device using BLE events due to limited sending capability, but can still receive data from the terminal device as a BLE central device using BLE events.

[0111] Correspondingly, when the sending capability of the terminal device as a BLE peripheral device is limited, the step of the terminal device communicating with the peer device in units of BLE events further includes: receiving display delay confirmation notification information sent by the peer device, the display delay confirmation notification information being used to indicate that the peer device only has a BLE event with receiving capability and a data packet received in the BLE event with only receiving capability will be delayed to a subsequent BLE event with sending capability for reply; continuously sending a plurality of encapsulated data packets in HDT format to the peer device in the BLE event with only receiving capability of the peer device; and after continuously sending the plurality of encapsulated data packets in HDT format to the peer device in the BLE event with only receiving capability of the peer device, receiving information sent by the peer device in the subsequent BLE event with sending capability of the peer device to reply to the plurality of encapsulated data packets in HDT format.

[0112] When receiving the display delay confirmation notification, the terminal device or the peer device as the BLE central device can continuously send a plurality of encapsulation data packets in HDT format to the peer device or the terminal device as the BLE peripheral device, and will not expect to receive a reply of the plurality of encapsulation data packets in HDT format from the terminal device or the peer device as the BLE peripheral device in the BLE event of sending the plurality of encapsulation data packets in HDT format, but wait to receive the reply of the plurality of encapsulation data packets in HDT format from the terminal device or the peer device as the BLE peripheral device in the subsequent BLE event indicated in the display delay confirmation notification.

[0113] In a specific implementation, the terminal device or the peer device as the BLE central device can continuously send a plurality of encapsulation data packets in HDT Format0 format or HDT Format1 format to the peer device or the terminal device as the BLE peripheral device.

[0114] For the encapsulation data packet in HDT Format1 format, please refer to the foregoing description for implementation, which will not be repeated. Please continue to refer to FIG. 6(a), in this embodiment, the encapsulation data packet in HDT Format0 format includes a preamble field, a control field, a payload PDU header field and a payload field. Among them, the sequence number identification field is carried in the payload PDU header field, and the byte length of the sequence number identification field is longer than the byte length of the sequence number field in the conventional BLE encapsulation data packet, such as 3 bits. Accordingly, the link layer is used to generate the encapsulation data packet in HDT Format0 format, so that the terminal device or the peer device as the BLE central device can send a plurality of unacknowledged received payload PDUs to the peer device or the terminal device as the BLE peripheral device.

[0115] Please refer to FIG. 7, in the duration of BLE event 1, the BLE central device transmits two data packets P701 and P702 to the BLE peripheral device on the target channel, and the BLE peripheral device transmits two data packets P711 and P712 to the BLE central device on the target channel. Among them, the display delay confirmation notification sent by the BLE peripheral device to the BLE central device is carried in the data packet P701, and the display delay confirmation notification indicates that the BLE peripheral device only has receiving capability in BLE event 2, and also indicates the information that the reply to the received data packet in BLE event 2 will be delayed to BLE event 3 in which the BLE peripheral device has transmitting capability.

[0116] Correspondingly, when receiving the display delay confirmation notification sent by the BLE peripheral device in the BLE event 1, the BLE central device can continuously send two HDT Format1 format data packets to the BLE peripheral device in the BLE event 2, such as the block SN1 / Block1 of the payload PDU1 identified by the sequence number 1 and the block SN2 / Block2 of the payload PDU2 identified by the sequence number 2. In the BLE event 3, after receiving the data packet 703 sent by the BLE central device, the BLE peripheral device uses the data packet 713 to reply to the block SN1 / Block1 of the payload PDU1 identified by the sequence number 1 and the block SN2 / Block2 of the payload PDU2 identified by the sequence number 2 sent by the BLE central device.

[0117] The BLE peripheral device sends the display delay confirmation notification to the BLE central device when the sending capability of the BLE peripheral device is limited, so that the BLE central device can continuously send multiple HDT format encapsulated data packets to the BLE peripheral device in the event that the BLE peripheral device only has receiving capability after receiving the display delay confirmation notification, thereby facilitating to improve the system throughput.

[0118] The communication method of the terminal device provided by the embodiment of the application is described above by taking the terminal device as an example. It can be understood by those skilled in the art that the terminal device can also be a terminal device using other suitable communication protocols, which is not limited herein.

[0119] Correspondingly, the embodiment of the application further provides a terminal device, comprising:

[0120] FIG. 8 shows a structural schematic diagram of an embodiment of the terminal device provided by the technical scheme of the application. In combination with reference to FIG. 8, a terminal device 80 can comprise: a detection module 801 adapted to detect the availability of a target channel when detecting that the target channel is in an idle state; and a communication module 802 adapted to communicate with the peer device using the target channel when detecting that the target channel is available.

[0121] The terminal device in the embodiment of the application can be used to execute the communication method of the terminal device described above, or other functional modules can also be used to execute the communication method of the terminal device described above. For the communication method of the terminal device, please refer to the detailed description in the foregoing part, which will not be described herein.

[0122] Correspondingly, the embodiment of the application further provides a device, which can load the communication method of the terminal device described above in the form of a program to implement the communication method of the terminal device provided by the embodiment of the application.

[0123] Referring to FIG. 9, an optional hardware structure diagram of the device provided by an embodiment of the present application is shown. The device in the embodiment of the present application comprises at least one processor 01, at least one communication interface 02, at least one memory 03 and at least one communication bus 04.

[0124] In the embodiment, the number of the processor 01, the communication interface 02, the memory 03 and the communication bus 04 is at least one respectively, and the processor 01, the communication interface 02 and the memory 03 complete the communication with each other through the communication bus 04.

[0125] The communication interface 02 can be the interface of the communication module for network communication, for example, the interface of the GSM module.

[0126] The processor 01 can be a central processing unit CPU, or an application specific integrated circuit ASIC, or one or more integrated circuits configured to implement the communication method of the terminal device of the embodiment.

[0127] The memory 03 can contain a high-speed RAM memory, and can also include a non-volatile memory, for example, at least one disk memory. The memory 03 stores one or more computer instructions, and the one or more computer instructions are executed by the processor 01 to implement the communication method of the terminal device provided by the foregoing embodiment.

[0128] It should be noted that the above-mentioned electronic device can also include other devices (not shown) which can not be necessary for the disclosure of the embodiment of the present application; since these other devices can not be necessary for understanding the disclosure of the embodiment of the present application, the embodiment of the present application does not introduce them one by one.

[0129] Correspondingly, the embodiment of the present application also provides a computer program product comprising computer programs / instructions, which are executed by a processor to implement the communication method of the terminal device provided by the embodiment of the present application.

[0130] The embodiment of the present application also provides a storage medium, which stores one or more computer instructions, and the one or more computer instructions are used to implement the communication method of the terminal device provided by the foregoing embodiment.

[0131] The above-described embodiments of the application are combinations of elements and features of the applications. The elements or features can be applied to one another only in combinations, unless otherwise indicated. Each individual element or feature can be replaced by alternative elements or features serving the same, equivalent or similar purpose, unless otherwise stated. The numerous individual features or elements can be combined or integrated in other combinations or arrangements, unless otherwise indicated. Other combinations and modifications of the application will occur to those skilled in the art upon reading this description.

[0132] The embodiments of the present application can be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In a hardware configuration, the method according to the exemplary embodiments of the present application can be implemented by 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), processors, controllers, micro-controllers, microprocessors, etc.

[0133] In a firmware or software configuration, the embodiments of the present application can be implemented in the form of modules, procedures, functions, and so on. Software code can be stored in a memory unit and executed by a processor. The memory unit is located at the interior or exterior of the processor and can deliver data to and receive data from the processor via various known means.

[0134] The above description of disclosed embodiments is merely intended to illustrate the general principles of the application. Various modifications in form and details can be made to the described embodiments without departing from the spirit of the application. Accordingly, the scope of the application should be determined not by the embodiments illustrated, but by the claims and their equivalents.

[0135] While the application has been disclosed in connection with the embodiments presented, it should be understood that modifications and / or additions can be made thereto without departing from the spirit and scope of the application. Accordingly, this application is intended to be governed solely by the spirit and scope of the claims, including all equivalents thereof.

Claims

1. A communication method of a terminal device, characterized by, The method comprises: detecting that a target channel is idle; when the target channel is detected to be available, performing availability detection on the target channel; 2. The communication method of the terminal device according to claim 1, characterized by, when the target channel is detected to be available, using the target channel to communicate with a peer device. The availability detection on the target channel comprises: sending a probe data packet to the peer device using the target channel; 3. The communication method of the terminal device according to claim 2, wherein when a reply to the probe data packet is received from the peer device, determining that the target channel is available.

4. The communication method of the terminal device according to claim 1, characterized by, The probe data packet comprises any one of a no-load packet and a null packet.

5. The communication method of the terminal device according to claim 4, characterized by, The using the target channel to communicate with the peer device comprises communicating with the peer device in connection events. In the process of communicating with the peer device in connection events, when communication between the terminal device and the peer device is interfered, the method further comprises: sending a dynamic connection event unavailability notification to the peer device, so that the peer device avoids sending data to the terminal device in a time period affected in a connection event; 6. The communication method of the terminal device according to claim 5, wherein or, receiving a dynamic connection event unavailability notification sent by the peer device, and avoiding sending data to the peer device in a time period affected in a connection event according to the dynamic connection event unavailability notification. The dynamic connection event unavailability notification comprises at least one of: information of an early end time of a current connection event; availability information of a subsequent connection event; information of reception capability and / or transmission capability of the current connection event; 7. The communication method of a terminal device according to Claim 5, characterized by, information of reception capability and / or transmission capability of the subsequent connection event. The avoiding sending data to the peer device in a time period affected in a connection event according to the dynamic connection event unavailability notification comprises:

8. The communication method of the terminal device according to Claim 7, characterized by, not sending data to the peer device in the time period affected in the connection event; or adjusting a parameter of a to-be-sent encapsulated data packet, so that a sending time of the encapsulated data packet does not use the time period affected in the connection event. The adjusting the parameter of the to-be-sent encapsulated data packet comprises any one of: adjusting a physical transmission rate of the encapsulated data packet; adjusting a payload length of the to-be-sent encapsulated data packet at a logical link and an adaptation layer or an isochronous adaptation layer; 9. The communication method of the terminal device according to claim 4, characterized by, generating, using a link layer, an encapsulated data packet in an HDT Format1 format, the encapsulated data packet in the HDT Format1 format comprising multiple subblocks of the same payload data.

10. The communication method of the terminal device according to Claim 9, characterized by, In the process of communicating with the peer device in connection events, the terminal device and the peer device communicate in a master-slave mode; wherein a connection initiator in the terminal device and the peer device is a central device, and a connected device is a peripheral device. If the terminal device is a peripheral device and transmission capability of the terminal device is limited, the communicating with the peer device in connection events comprises: sending display delay confirmation notification information to the peer device, the display delay confirmation notification information being used to indicate information that the terminal device only has a connection event with reception capability and a data packet received in the connection event with only reception capability will be delayed to a subsequent connection event with transmission capability for reply; Receiving the encapsulated data packet sent by the peer device in the connection event with only receiving capability; After receiving the encapsulated data packet sent by the peer device in the connection event with only receiving capability, replying to the encapsulated data packet sent by the peer device in the connection event with only receiving capability in the subsequent connection event with sending capability.

11. The communication method of the terminal device according to Claim 9, characterized by, If the peer device is a peripheral device and the sending capability of the peer device is limited, the communication with the peer device is performed in connection events, and the method further comprises: Receiving display delay confirmation notification information sent by the peer device, the display delay confirmation notification information being used to indicate that the connection event with only receiving capability of the peer device and the data packet received in the connection event with only receiving capability will be delayed to be replied in the subsequent connection event with sending capability; Continuously sending a plurality of encapsulated data packets in HDT format to the peer device in the connection event with only receiving capability of the peer device; After continuously sending a plurality of encapsulated data packets in HDT format to the peer device in the connection event with only receiving capability of the peer device, receiving confirmation information sent by the peer device in the subsequent connection event with sending capability of the peer device, the confirmation information being used to indicate that the plurality of encapsulated data packets in HDT format have been received.

12. The communication method of the terminal device according to Claim 11, characterized by, The plurality of encapsulated data packets in HDT format comprise a plurality of encapsulated data packets in HDT Format0 format and / or a plurality of encapsulated data packets in HDT Format1 format.

13. The communication method of the terminal device according to any one of claims 4 to 12, characterized by, The connection event comprises a BLE event, and the terminal device and the peer device are HB BLE devices.

14. A terminal device, comprising: The method comprises: a detection module adapted to detect that a target channel is in an idle state, and perform availability detection on the target channel; a communication module adapted to perform communication with the peer device using the target channel when it is detected that the target channel is available.

15. A computer program product comprising computer programs / instructions, characterized in that, The computer program / instruction is executed by a processor to implement the communication method of the terminal device according to any one of claims 1-13.

16. An apparatus, comprising: The computer program / instruction is executed by a processor to implement the communication method of the terminal device according to any one of claims 1-13.

17. A storage medium, characterized by The computer program / instruction is executed by a processor to implement the communication method of the terminal device according to any one of claims 1-13. The computer program / instruction is executed by a processor to implement the communication method of the terminal device according to any one of claims 1-13.

Images