Bluetooth pairing method, device, communication system, and storage medium

Abstract

A Bluetooth pairing method, a device, a communication system, and a storage medium. The method comprises: a first device sending a first data packet to a second device, wherein the first data packet is a data packet based on a transmission control protocol / Internet protocol (TCP / IP), the first data packet comprises first out-of-band (OOB) data, and the first OOB data is used for Bluetooth pairing between the first device and the second device. When Bluetooth devices needing to be paired do not have an NFC function, the Bluetooth devices can still implement reliable Bluetooth pairing on the basis of OOB, thereby effectively reducing the cost of the Bluetooth devices.

Description

Bluetooth pairing method, device, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a Bluetooth pairing method, device, communication system, and storage medium. Background Art

[0002] Bluetooth communication features low cost, low complexity, and low power consumption. It has been widely deployed and commercialized in various scenarios, including audio transmission, human-computer interaction, smart homes, wearable devices, and indoor positioning. In Bluetooth communication, Bluetooth devices can be paired using out-of-band (OOB) transmission.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a Bluetooth pairing method, device, communication system, and storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, a Bluetooth pairing method is proposed, the method comprising:

[0006] A first device sends a first data packet to a second device. The first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol. The first data packet includes first out-of-band transmission OOB data. The first OOB data is used for Bluetooth pairing between the first device and the second device.

[0007] According to a second aspect of an embodiment of the present disclosure, a Bluetooth pairing method is proposed, the method comprising:

[0008] The second device receives a first data packet sent by the first device, where the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, and the first data packet includes first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

[0009] According to a third aspect of an embodiment of the present disclosure, a first device is provided, the first device including:

[0010] The transceiver module is used to send a first data packet to the second device, where the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, and the first data packet includes first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

[0011] According to a fourth aspect of an embodiment of the present disclosure, a second device is provided, the second device including:

[0012] The transceiver module is used to receive a first data packet sent by a first device, where the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, and the first data packet includes first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

[0013] According to a fifth aspect of the embodiments of the present disclosure, a first device is provided, including:

[0014] one or more processors;

[0015] A memory coupled to the one or more processors, the memory comprising executable instructions, which, when executed by the one or more processors, causes the first device to execute the Bluetooth pairing method described in the first aspect.

[0016] According to a sixth aspect of the embodiments of the present disclosure, a second device is provided, including:

[0017] one or more processors;

[0018] A memory coupled to the one or more processors, the memory comprising executable instructions, which, when executed by the one or more processors, causes the second device to execute the Bluetooth pairing method described in the second aspect.

[0019] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a first device and a second device, wherein the first device is configured to implement the Bluetooth pairing method described in the first aspect, and the second device is configured to implement the Bluetooth pairing method described in the second aspect.

[0020] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the Bluetooth pairing method as described in the first aspect or the second aspect.

[0021] In the above embodiment, the first device can send a first data packet carrying first OOB data to the second device based on the TCP / IP protocol, and then initiate Bluetooth pairing based on online OOB, providing a secure out-of-band transmission channel other than NFC. When the Bluetooth device to be paired does not have NFC function, reliable Bluetooth pairing can still be achieved based on OOB, effectively reducing the cost of Bluetooth devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0023] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0024] FIG2 is an exemplary interaction diagram of a Bluetooth pairing method provided according to an embodiment of the present disclosure.

[0025] FIG3A is a schematic diagram of an exemplary flow chart of a Bluetooth pairing method provided according to an embodiment of the present disclosure.

[0026] FIG3B is a schematic diagram of an exemplary flow chart of a Bluetooth pairing method provided according to an embodiment of the present disclosure.

[0027] FIG3C is a schematic diagram of an exemplary flow chart of a Bluetooth pairing method provided according to an embodiment of the present disclosure.

[0028] FIG3D is a schematic diagram of an exemplary flow chart of a Bluetooth pairing method provided according to an embodiment of the present disclosure.

[0029] FIG4A is a schematic diagram of an exemplary flow chart of a Bluetooth pairing method provided according to an embodiment of the present disclosure.

[0030] FIG4B is a schematic diagram of an exemplary flow chart of a Bluetooth pairing method provided according to an embodiment of the present disclosure.

[0031] FIG4C is a schematic diagram of an exemplary flow chart of a Bluetooth pairing method provided according to an embodiment of the present disclosure.

[0032] FIG4D is a schematic diagram of an exemplary flow chart of a Bluetooth pairing method provided according to an embodiment of the present disclosure.

[0033] FIG5 is an exemplary interaction diagram of a Bluetooth pairing method provided according to an embodiment of the present disclosure.

[0034] [Corrected 09.05.2024 according to Rule 91] Figure 6 is an exemplary flow chart of the Bluetooth pairing method provided according to an embodiment of the present disclosure.

[0035] [Corrected 09.05.2024 in accordance with Article 91] [Deleted]

[0036] FIG7A is a schematic diagram of an exemplary structure of a terminal provided according to an embodiment of the present disclosure.

[0037] FIG7B is a schematic diagram of an exemplary structure of a network device provided according to an embodiment of the present disclosure.

[0038] FIG8A is a schematic diagram of an exemplary structure of a communication device provided according to an embodiment of the present disclosure.

[0039] FIG8B is a schematic diagram of an exemplary structure of a communication device provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0040] The embodiments of the present disclosure provide a Bluetooth communication method, device, communication system, and storage medium.

[0041] In a first aspect, an embodiment of the present disclosure provides a Bluetooth pairing method, the method comprising:

[0042] A first device sends a first data packet to a second device, where the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol (TCP / IP) protocol, and the first data packet includes first out-of-band (OOB) data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

[0043] In the above embodiment, the first device can send a first data packet carrying first OOB data to the second device based on the TCP / IP protocol, and then initiate Bluetooth pairing based on online OOB, providing a secure out-of-band transmission channel other than Near Field Communication (NFC). When the Bluetooth device to be paired does not have NFC function, reliable Bluetooth pairing can still be achieved based on OOB, effectively reducing the cost of Bluetooth devices.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the first OOB data includes at least one of the following fields:

[0045] A first field is used to indicate the length of the first OOB data;

[0046] The second field is used to indicate the device address and address type of the first device;

[0047] The third field is used to indicate the role and capabilities of the first device;

[0048] The fourth field is used to indicate the security connection confirmation value;

[0049] The fifth field is used to indicate a random value for a secure connection.

[0050] In the above embodiment, the first OOB data can carry information such as the security connection confirmation value and the security connection random number, so that the responder of the Bluetooth pairing (i.e., the second device) can reliably authenticate the initiator of the Bluetooth pairing (i.e., the first device) based on the first OOB data, thereby ensuring the security and reliability of the Bluetooth pairing based on online OOB.

[0051] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0052] The first device and the second device exchange capability information, where the capability information is used to indicate whether OOB and / or TCP / IP protocols are supported; the first device determines whether to send the first data packet based on the capability information.

[0053] In the above embodiment, two Bluetooth devices that need to be paired can exchange capability information before sending the first data packet, and determine whether to send corresponding OOB data to initiate Bluetooth pairing based on the capability information. When the Bluetooth device does not support the online OOB pairing method, the online OOB-based Bluetooth pairing will not be initiated, which effectively reduces resource overhead and device power consumption.

[0054] In conjunction with some embodiments of the first aspect, in some embodiments, the first device determines, based on the capability information, whether to send the first data packet, including:

[0055] The first device determines that the first device and / or the second device supports OOB, and both the first device and the second device support TCP / IP protocol, and sends the first data packet to the second device.

[0056] In the above embodiment, when both Bluetooth devices to be paired support TCP / IP protocol communication, one-way OOB data transmission or two-way OOB data transmission can be implemented based on the Bluetooth device's support for online OOB, effectively improving the flexibility of online OOB pairing.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the first device sending a first data packet to the second device includes:

[0058] The first device establishes a wireless local area network (WLAN) point-to-point connection with the second device;

[0059] The first device sends the first data packet to the second device through the point-to-point connection.

[0060] In the above embodiment, the first device and the second device can realize the transmission of OOB data based on WLAN point-to-point connection, and can still realize Bluetooth pairing based on online OOB when the Bluetooth device is not connected to the wide area network, which effectively improves the versatility of online OOB.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0062] The first device receives a second data packet sent by the second device, where the second data packet is a data packet based on the TCP / IP protocol and includes second OOB data. The second OOB data packet is used for Bluetooth pairing between the first device and the second device.

[0063] In the above embodiment, the first device can not only send the first OOB data to the second device, but also receive the second OOB data sent by the second device and authenticate the second device based on the second OOB data, thereby effectively improving the security and reliability of online OOB pairing.

[0064] In a second aspect, an embodiment of the present disclosure provides a Bluetooth pairing method, the method comprising:

[0065] The second device receives a first data packet sent by the first device, where the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, and the first data packet includes first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

[0066] In conjunction with some embodiments of the second aspect, in some embodiments, the first OOB data includes at least one of the following fields:

[0067] A first field is used to indicate the length of the first OOB data;

[0068] The second field is used to indicate the device address and address type of the first device;

[0069] The third field is used to indicate the role and capabilities of the first device;

[0070] The fourth field is used to indicate the security connection confirmation value;

[0071] The fifth field is used to indicate a random value for a secure connection.

[0072] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0073] The first device and the second device exchange capability information, and the capability information is used by the first device to determine whether to send the first data packet.

[0074] In combination with some embodiments of the second aspect, in some embodiments, the first data packet is sent to the second device when the first device determines that the first device and / or the second device supports OOB, and both the first device and the second device support the TCP / IP protocol.

[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the second device receiving a first data packet sent by the first device includes:

[0076] The second device establishes a wireless local area network WLAN point-to-point connection with the first device;

[0077] The second device receives the first data packet sent by the first device through the point-to-point connection.

[0078] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0079] The second device sends a second data packet to the first device, where the second data packet is a data packet based on the TCP / IP protocol and includes second OOB data. The second OOB data packet is used for Bluetooth pairing between the first device and the second device.

[0080] In a third aspect, an embodiment of the present disclosure provides a first device, the first device including:

[0081] The transceiver module is used to send a first data packet to the second device, where the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, and the first data packet includes first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

[0082] In a fourth aspect, an embodiment of the present disclosure provides a second device, the second device including:

[0083] The transceiver module is used to receive a first data packet sent by a first device, where the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, and the first data packet includes first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

[0084] In a fifth aspect, an embodiment of the present disclosure proposes a first device comprising: one or more processors; a memory coupled to the one or more processors, the memory comprising executable instructions, which, when executed by the one or more processors, enables the first device to execute the Bluetooth communication method in the first aspect.

[0085] In the sixth aspect, an embodiment of the present disclosure proposes a second device, comprising: one or more processors; a memory coupled to the one or more processors, the memory comprising executable instructions, which, when executed by the one or more processors, enables the second device to execute the Bluetooth communication method in the second aspect.

[0086] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, which includes: a first device and a second device; wherein the first device is configured to execute the method described in the optional implementation manner of the first aspect, and the second device is configured to execute the method described in the optional implementation manner of the second aspect.

[0087] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium, wherein the storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0088] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0089] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first and second aspects.

[0090] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0091] It is understandable that the first device, the second device, the communication system, the storage medium, the program product, the computer program, the chip, or the chip system described above are all used to perform the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0092] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0093] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0094] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0095] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0096] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0097] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0098] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0099] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0100] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0101] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0102] In some embodiments, terms such as "time / frequency" and "time / frequency domain" refer to the time domain and / or the frequency domain.

[0103] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0104] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0105] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0106] In some embodiments, "network" can be interpreted as devices included in the network (for example, a first device, a second device, an access network device, a core network device, etc.).

[0107] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0108] In some embodiments, the terms "first device", "second device", "terminal", "terminal device", "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0109] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0110] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0111] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0112] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0113] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0114] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 includes a first device 101 and a second device 102. In some embodiments, the first device 101 and the second device 102 can both be devices capable of Bluetooth communication. In some embodiments, the first device 101 and the second device 102 can also support TCP / IP communication.

[0115] In some embodiments, the second device 102 may be provided as a central device in Bluetooth communication, and the first device 101 may be provided as a peripheral device in Bluetooth communication. Alternatively, the first device 101 may serve as a central device, and the second device 102 may serve as a peripheral device, which is not limited in the present disclosure.

[0116] In some embodiments, after establishing a Bluetooth connection, the first device 101 and the second device 102 may enter a pairing phase, during which the first device 101 and the second device 102 may generate a shared key, which may be used for encryption and address resolution of subsequent connections.

[0117] In some embodiments, the pairing of Bluetooth devices may include three stages. In the first stage, two devices (such as the first device 101 and the second device 102) exchange authentication capabilities and input and output (IO) capabilities with each other, so that the Bluetooth devices determine which pairing method to use in the second stage; in the second stage, the Bluetooth devices are paired according to the pairing method determined in the first stage, where the pairing method may include but is not limited to: just works, numeric comparison, passkey entry, OOB based on Near Field Communication (NFC), and online OOB; in the third stage, the paired devices can use the key generated in the second stage to encrypt the link transmission.

[0118] In some cases, NFC-based OOB requires both parties to support NFC near-field communication. In some scenarios, a phone can pair with a Bluetooth headset by scanning it with NFC, or with a tablet by scanning it with NFC. NFC communication is OOB communication that doesn't require the devices to be online, meaning they don't need to be connected to the internet.

[0119] However, since NFC-based OOB requires both parties to support NFC, the cost of Bluetooth devices is relatively high. In some embodiments, based on online OOB, the first device 101 and the second device 102 can perform OOB communication without relying on NFC, and can also achieve device authentication to complete pairing.

[0120] In some embodiments, the second device 102 and the first device 101 can each be any one of a terminal, an access network device, and a core network device. For example, the second device 102 can be a computer, which can be connected to a medical sensor, a light bulb, a socket, a switch, or the like via Bluetooth. The first device 101 can be any of these devices. After the second device 102 and the first device 101 establish a connection, the two parties can realize the transmission of audio data or other types of data, such as querying and reading sensor status values, adjusting device modes, or other setting parameters.

[0121] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0122] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0123] The embodiments of the present disclosure may be applied to Bluetooth (registered trademark)), Star Flash system, Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of Bluetooth, Starlink, LTE, LTE-A, and 5G).

[0124] FIG2 is an interactive diagram of a Bluetooth pairing method according to an embodiment of the present disclosure. As shown in FIG2 , the embodiment of the present disclosure relates to a Bluetooth pairing method, which includes:

[0125] Step S2101: The first device and the second device exchange capability information.

[0126] In some embodiments, the capability information is used to indicate whether OOB and / or TCP / IP protocols are supported. Optionally, the first device and the second device each determine whether the other device supports OOB and / or TCP / IP protocols based on the capability information obtained through interaction.

[0127] It can be understood that when the first device or the second device supports the TCP / IP protocol, it can be said that the first device and / or the second device has the ability to send and receive wireless signals based on the TCP / IP protocol. For example, if the first device supports the TCP / IP protocol, the first device can access the wireless network through Wireless Fidelity (WiFi) and compile or parse data packets based on the TCP / IP protocol to send data packets based on the TCP / IP protocol to other devices (such as the second device) in the local area network or wide area network, or receive data packets based on the TCP / IP protocol sent by other devices.

[0128] In some embodiments, the capability information may include at least one of authentication capability and input / output (I / O) capability.

[0129] In some embodiments, the capability information is used by the first device and the second device to determine whether to use an online OOB method for Bluetooth pairing. When the first device and the second device use an online OOB method for pairing, the steps performed by the first device and the second device may include at least one of steps S2102, S2103, S2104, and S2105.

[0130] It is understood that the online OOB method can be an OOB method based on the TCP / IP protocol. Bluetooth devices can transmit OOB data through OOB based on the TCP / IP protocol, thereby achieving Bluetooth pairing. Possible implementations of OOB data transmission in the online OOB method will be described in detail later and are not detailed here.

[0131] In some embodiments, the capability information is used by the first device to determine whether to send a first data packet to the second device, for example, to determine whether to execute step S2102 and / or step S2103. Alternatively, the capability information is used by the second device to determine whether to send a second data packet to the second device, for example, to determine whether to execute step S2102 and / or step S2104.

[0132] In some embodiments, the capability information is used by the first device and the second device to determine a pairing method. Optionally, the pairing method may include at least one of the following: a just works method, a numeric comparison method, a passkey entry method, an OOB method based on Near Field Communication (NFC), and an online OOB method.

[0133] In some embodiments, the capability information may include first capability information and second capability information. Optionally, the first device and the second device exchanging capability information may include the first device sending the first capability information to the second device, and the second device sending the second capability information to the first device, wherein the first capability information may be used to indicate whether the first device supports OOB and / or TCP / IP protocols, and the second capability information is used to indicate whether the second device supports OOB and / or TCP / IP protocols.

[0134] In some embodiments, a first device receives second capability information sent by a second device. Optionally, the first device determines whether the second device supports OOB and / or TCP / IP protocols based on the second capability information. Optionally, the first device determines whether to perform Bluetooth pairing using online OOB based on its own first capability information and the received second capability information, for example, determining whether to execute step S2103 or to execute steps S2102 and S2103.

[0135] In some embodiments, the second device receives the first capability information sent by the first device. Optionally, the second device determines whether the first device supports OOB and / or TCP / IP protocols based on the first capability information. Optionally, the second device determines whether to use online OOB Bluetooth pairing based on its own second capability information and the received first capability information, for example, determining whether to execute step S2104 or execute steps S2102 and S2104.

[0136] Step S2102: The first device establishes a WLAN point-to-point connection with the second device.

[0137] In some embodiments, the WLAN point-to-point connection may also be referred to as WiFi direct connection or WLAN direct connection. Optionally, based on the WLAN point-to-point connection, communication between the first device and the second device may be achieved without the participation of other devices.

[0138] Optionally, the WLAN point-to-point connection can be, for example, a connection established based on WiFi point-to-point (point to point or peer to peer, P2P) technology, or a connection established based on soft access point (SoftAP) technology, which is not limited in the present embodiment. If the WiFi P2P technology is used to establish the WLAN point-to-point connection, when the first device initiates the establishment of the WLAN point-to-point connection, the first device can act as the P2P Group Owner, and the second device can act as the P2P Client.

[0139] In some embodiments, after a first device establishes a WLAN point-to-point connection with a second device, the first device can directly send TCP / IP-based data packets to the second device, or receive TCP / IP-based data packets sent by the second device, without the need for transit through other devices. For example, the first device can directly send data packets to the second device without sending the data packets to an access network device such as a router, base station, or satellite.

[0140] In some embodiments, if the Bluetooth pairing is initiated by the first device, the first device may enable a WiFi hotspot, and the second device may establish a WLAN point-to-point connection with the first device through the WiFi hotspot.

[0141] In some embodiments, step S2102 may be omitted. For example, if the first device or the second device does not support a WiFi hotspot function or does not support a WLAN point-to-point connection, step S2102 may not be performed, and the first device or the second device may send the first data packet or the second data packet to the other device via a router, base station, or other device.

[0142] Step S2103: The first device sends a first data packet to the second device.

[0143] In some embodiments, the first data packet is a data packet based on the TCP / IP protocol. Optionally, the first data packet can be transmitted at the network layer, or at the data link layer, or at the application layer. For example, the first data packet can be an IP data packet, or an Ethernet data packet, or an HTTP data packet, etc., which is not limited in the present disclosure.

[0144] In some embodiments, the first data packet includes first OOB data. Optionally, the first OOB data is used for Bluetooth pairing between the first device and the second device.

[0145] In some embodiments, the first OOB data includes at least one of the following fields: a first field for indicating the length of the first OOB data; a second field for indicating the device address and address type of the first device; a third field for indicating the role and capabilities of the first device; a fourth field for indicating a secure connection confirmation value; and a fifth field for indicating a secure connection random value.

[0146] Optionally, the first field may be an Online OOB Data Length field, and the first field may be 2 bytes.

[0147] Optionally, the second field may be a Low Energy (LE) Bluetooth Device Address and Address Type field, the Assigned Numbers thereof may be 0x1B, and the second field may be 7 bytes. Optionally, the device address in the second field may be 6 bytes, and the address type may be 1 byte. Optionally, the address type of the Bluetooth device may include two address types: a public device address and a random device address.

[0148] Optionally, the third field may be a Low Energy Role (LE Role) field, the assigned number of which may be 0x1C, and the third field may be 1 byte. Optionally, the roles of a Bluetooth device may include a central device role and a peripheral device role. For example, when the first device can only function as a peripheral device, a corresponding LE Role field may be generated, and OOB data including the field may be sent to the second device. The second device may then determine, based on the OOB data, that the role of the first device is a peripheral device role.

[0149] Optionally, the fourth field may be a low-power secure connection confirmation value (LE Secure Connections Confirmation Value) field, the assigned number of which may be 0x22, and the fourth field may be 16 bytes, i.e., 128 bits. Optionally, the secure connection confirmation value may be generated based on a first preset function. Optionally, the first preset function may be function f4 (function f4) in the related art, which may be used to generate a confirmation value during the pairing process, such as the low-power secure connection confirmation value described above. Optionally, the secure connection confirmation value may be determined based on the secure connection random value indicated by the fifth field and the shared key.

[0150] Optionally, the fifth field may be a Low Energy Secure Connections Random Value (LE Secure Connections Random Value) field, the assigned number of which may be 0x23, and the fifth field may be 16 bytes, i.e., 128 bits. Optionally, the first device may use a different secure connection random value when sending different OOB data, or the access rights of the first device may be restricted.

[0151] In some embodiments, the first device may encrypt the first OOB data and send the encrypted first OOB data to the second device. Alternatively, the first device may encrypt the first OOB data using an elliptic curve encryption algorithm.

[0152] In some embodiments, at least one of the first to fifth fields in the first OOB data is used by the second device to determine whether to pair with the first device.

[0153] In some embodiments, the first device may send the first data packet directly to the second device, for example, by sending the first data packet to the second device via a WLAN point-to-point connection. Alternatively, the first device may send the first data packet to the second device through forwarding by another device. For example, the first device may send the first data packet to a router, and the router may forward the first data packet to the second device based on the IP address of the target device in the first data packet. This is not limited in the presently disclosed embodiments.

[0154] Step S2104: The second device sends a second data packet to the first device.

[0155] In some embodiments, the second data packet is a data packet based on the TCP / IP protocol. Optionally, the second data packet can be transmitted at the network layer, or at the data link layer, or at the application layer. For example, the second data packet can be an IP data packet, or an Ethernet data packet, or an HTTP data packet, etc., which is not limited in the present disclosure.

[0156] In some embodiments, the second data packet includes second OOB data, and the second OOB data is used for Bluetooth pairing between the first device and the second device.

[0157] In some embodiments, the second OOB data includes at least one of the following: a first field for indicating the length of the second OOB data; a second field for indicating the device address and address type of the second device; a third field for indicating the role and capabilities of the second device; a fourth field for indicating a secure connection confirmation value; and a fifth field for indicating a secure connection random value.

[0158] It is understood that the second OOB data and the first OOB data are both OOB data, and their formats and functions can be exactly the same. The only difference between the two is the sender and the receiver. The OOB data includes information such as the sender's device address, address type, role, role capabilities, etc. For example, the fourth and fifth fields in the first OOB data can be generated by the first device, while the fourth and fifth fields in the second OOB data can be generated by the second device.

[0159] The optional implementation of the second data packet can refer to the optional implementation of the first data packet in step S2103, which is not described here in detail.

[0160] In some embodiments, when both the first device and the second device support OOB and TCP / IP protocols, the first device and the second device can each perform a Bluetooth pairing process based on the received OOB data. In some embodiments, the order of executing steps S2103 and S2104 can be swapped. Optionally, if the Bluetooth pairing is initiated by the first device, step S2103 can be executed first, followed by step S2104. If the Bluetooth pairing is initiated by the second device, step S2104 can be executed first, followed by step S2103.

[0161] In some embodiments, step S2103 or step S2104 can be omitted. For example, if both the first device and the second device support the TCP / IP protocol, and the first device does not support OOB, such as when the first device is OOB not set, and the second device supports OOB, such as when the second device is OOB ready (OOB SET), OOB data can be transmitted unidirectionally, such as when the second device can unidirectionally send a second data packet to the first device to initiate Bluetooth pairing.

[0162] Step S2105: The first device and the second device perform Bluetooth pairing.

[0163] In some embodiments, the first device determines whether to pair with the second device based on the second data packet. Optionally, the first device determines whether to pair with the second device based on a secure connection random value and a secure connection confirmation value generated by the second device in the second data packet.

[0164] In some embodiments, the second device determines whether to pair with the first device based on the first data packet. Alternatively, the second device determines whether to pair with the first device based on a secure connection random value and a secure connection confirmation value generated by the first device in the first data packet.

[0165] In some embodiments, the second device verifies the first OOB data sent by the first device according to the fourth field and the fifth field in the first OOB data to determine whether to pair with the first device.

[0166] For example, the second device determines the first key corresponding to the first OOB data based on the received security connection random value and security connection confirmation value, and determines whether the first key matches the shared key pre-stored by the second device; or the second device performs a security connection confirmation value calculation based on the received security connection random value to obtain a first security connection confirmation value generated by the second device, and determines whether the first security connection random value matches the security connection random value received by the second device. If they match, the second device can pair with the first device. For example, the second device can receive the short-term key (STK) calculated and sent by the first device to encrypt subsequently transmitted Bluetooth data. If they match, the second device can not pair with the first device. For example, the second device can send a pairing failure instruction to the first device, such as a confirm value faild instruction.

[0167] In some embodiments, the second device verifies the first OOB data sent by the first device according to the fourth field and the fifth field in the first OOB data to determine whether to pair with the first device.

[0168] In some embodiments, after the first device successfully verifies the second OOB data and the second device successfully verifies the first OOB data, the first device and the second device perform Bluetooth pairing.

[0169] It is worth noting that in the embodiment of the present disclosure, the first device and the second device can be any two Bluetooth devices, and both the first device and the second device can serve as initiators of pairing. For example, when the first device is preparing to pair with the second device, it can send corresponding OOB data to the second device and receive the corresponding OOB data sent by the second device. Alternatively, the second device can first send corresponding OOB data to the first device and receive the OOB data sent by the first device.

[0170] In some embodiments, the first device and the second device are interchangeable.

[0171] In some embodiments, terms such as "data packet", "data frame", "message", "frame", "packet", "protocol data unit (PDU)" and the like can be used interchangeably.

[0172] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "message", "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "bit", and "data" can be used interchangeably.

[0173] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0174] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0175] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0176] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0177] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "some", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, some A, any A, or first A, etc., but not limited to this.

[0178] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0179] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0180] The Bluetooth pairing method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2105. For example, step S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2104 can be implemented as an independent embodiment, step S2101+step S2102+step S2103 can be implemented as an independent embodiment, step S2101+step S2102+step S2104 can be implemented as an independent embodiment, and step S2103+step S2104 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0181] In some embodiments, step S2103 and step S2104 may be executed in an interchangeable order or simultaneously.

[0182] In some embodiments, steps S2101 to S2102 and steps S2104 to S2105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0183] In some embodiments, steps S2101 to S2103 and step S2105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0184] In some embodiments, step S2101, step S2103, and step S2105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0185] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0186] FIG3A is a flow chart of a Bluetooth pairing method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a Bluetooth pairing method (on the first device side), the method comprising:

[0187] Step S3101: Exchange capability information with the second device.

[0188] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0189] Step S3102: Establish a WLAN point-to-point connection with the second device.

[0190] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0191] Step S3103: Send the first data packet.

[0192] The optional implementation of step S3103 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0193] In some embodiments, the first device sends the first data packet to the second device, but is not limited thereto and the first data packet may also be sent to other entities.

[0194] Step S3104, receiving a second data packet.

[0195] The optional implementation of step S3104 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0196] In some embodiments, the first device receives the second data packet sent by the second device, but is not limited thereto and may also receive the second data packet sent by other entities.

[0197] In some embodiments, step S3101 is omitted, and the terminal 101 autonomously implements the function indicated by the first information, or the above function is default or by default.

[0198] Step S3105: Bluetooth pairing with the second device.

[0199] The optional implementation of step S3105 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0200] The Bluetooth pairing method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3105. For example, step S3102 can be implemented as an independent embodiment, step S3103 can be implemented as an independent embodiment, step S3104 can be implemented as an independent embodiment, step S3101+step S3102+step S3103 can be implemented as an independent embodiment, step S3101+step S3102+step S3104 can be implemented as an independent embodiment, and step S3103+step S3104 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0201] In some embodiments, step S3103 and step S3104 may be executed in an interchangeable order or simultaneously.

[0202] In some embodiments, steps S3101 to S3102 and steps S3104 to S3105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0203] In some embodiments, steps S3101 to S3103 and step S3105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0204] In some embodiments, step S3101, step S3103, and step S3105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0205] FIG3B is a flow chart of a Bluetooth pairing method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a Bluetooth pairing method (on the first device side), the method comprising:

[0206] Step S3201, sending a first data packet.

[0207] Optional implementations of step S3201 can be found in step S2103 of FIG. 2 , optional implementations of step S3103 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0208] Step S3202: Bluetooth pairing with the second device.

[0209] Optional implementations of step S3202 can be found in step S2105 of FIG. 2 , optional implementations of step S3105 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0210] In some embodiments, step S3202 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0211] In some embodiments, step S3201 and / or step S3202 may also be combined with step S3101 and / or step S3102 in Figure 3 A. For example, in step S3201, the first device sends a first data packet to the second device via a WLAN point-to-point connection.

[0212] In some embodiments, step S3201 and step S3202 may also be combined with step S3104 in Figure 3 A. For example, the first device and the second device each send their generated OOB data to the other device to achieve Bluetooth pairing.

[0213] FIG3C is a flow chart of a Bluetooth pairing method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a Bluetooth pairing method (on the first device side), which includes:

[0214] Step S3301, receiving a second data packet.

[0215] The optional implementation of step S3301 can be found in step S2104 of FIG. 2 , the optional implementation of step S3104 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 , FIG. 3A , and FIG. 3B , which will not be described in detail here.

[0216] Step S3302: Bluetooth pairing with the second device.

[0217] The optional implementation of step S3302 can be found in step S2105 of FIG. 2 , the optional implementation of step S3105 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 , FIG. 3A , and FIG. 3B , which will not be described in detail here.

[0218] In some embodiments, step S3302 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0219] In some embodiments, step S3301 and / or step S3302 may also be combined with step S3101 and / or step S3102 in Figure 3 A. For example, in step S3301, the first device receives the second data packet sent by the second device via a WLAN point-to-point connection.

[0220] FIG3D is a flow chart of a Bluetooth pairing method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a Bluetooth pairing method (on the first device side), the method comprising:

[0221] Step S3401, sending a first data packet.

[0222] In some embodiments, the first device sends a first data packet to the second device, the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, the first data packet includes first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

[0223] In some embodiments, the first OOB data includes at least one of the following fields:

[0224] The first field is used to indicate the length of the first OOB data;

[0225] The second field is used to indicate the device address and address type of the first device;

[0226] The third field is used to indicate the role and capabilities of the first device;

[0227] The fourth field is used to indicate the security connection confirmation value;

[0228] The fifth field is used to indicate a random value for a secure connection.

[0229] In some embodiments, the method comprises:

[0230] The first device and the second device exchange capability information, where the capability information is used to indicate whether OOB and / or TCP / IP protocols are supported;

[0231] The first device determines whether to send the first data packet according to the capability information.

[0232] In some embodiments, the first device determines whether to send the first data packet based on the capability information, including:

[0233] The first device determines that the first device and / or the second device supports OOB, and both the first device and the second device support the TCP / IP protocol, and sends a first data packet to the second device.

[0234] In some embodiments, the first device sends a first data packet to the second device, including:

[0235] The first device establishes a wireless local area network WLAN point-to-point connection with the second device;

[0236] The first device sends a first data packet to the second device through a point-to-point connection.

[0237] In some embodiments, the method comprises:

[0238] The first device receives a second data packet sent by the second device, where the second data packet is a data packet based on the TCP / IP protocol and includes second OOB data. The second OOB data packet is used for Bluetooth pairing between the first device and the second device.

[0239] FIG4A is a flow chart of a Bluetooth pairing method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a Bluetooth pairing method (on the second device side), which includes:

[0240] Step S4101: Exchange capability information with the first device.

[0241] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0242] Step S4102: Establish a WLAN point-to-point connection with the first device.

[0243] The optional implementation of step S4102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0244] Step S4103, receiving the first data packet.

[0245] The optional implementation of step S4103 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0246] Step S4104, sending a second data packet.

[0247] The optional implementation of step S4104 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0248] Step S4105: Bluetooth pairing with the first device.

[0249] The optional implementation of step S4105 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0250] The Bluetooth pairing method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4105. For example, step S4102 can be implemented as an independent embodiment, step S4103 can be implemented as an independent embodiment, step S4104 can be implemented as an independent embodiment, step S4101+step S4102+step S4103 can be implemented as an independent embodiment, step S4101+step S4102+step S4104 can be implemented as an independent embodiment, and step S4103+step S4104 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0251] In some embodiments, step S4103 and step S4104 may be executed in an interchangeable order or simultaneously.

[0252] In some embodiments, steps S4101 to S4102 and steps S4104 to S4105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0253] In some embodiments, steps S4101 to S4103 and step S4105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0254] In some embodiments, step S4101, step S4103, and step S4105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0255] FIG4B is a flow chart of a Bluetooth pairing method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a Bluetooth pairing method (on the second device side), the method comprising:

[0256] Step S4201, receiving a first data packet.

[0257] Optional implementations of step S4201 can be found in step S2103 of FIG. 2 , optional implementations of step S4103 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0258] Step S4202: Bluetooth pairing with the first device.

[0259] The optional implementation of step S4202 can refer to step S2105 in Figure 2, the optional implementation of step S4105 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0260] In some embodiments, step S4202 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0261] In some embodiments, step S4201 and / or step S4202 may also be combined with step S4101 and / or step S4102 in Figure 4A. For example, in step S4201, the second device receives the first data packet sent by the second device through a WLAN point-to-point connection.

[0262] In some embodiments, step S4201 and step S4202 may also be combined with step S4104 in Figure 4A. For example, the first device and the second device each send their generated OOB data to the other device to achieve Bluetooth pairing.

[0263] FIG4C is a flow chart of a Bluetooth pairing method according to an embodiment of the present disclosure. As shown in FIG4C , the embodiment of the present disclosure relates to a Bluetooth pairing method (on the second device side), which includes:

[0264] Step S4301, sending a second data packet.

[0265] The optional implementation of step S4301 can be found in step S2104 of FIG. 2 , the optional implementation of step S4104 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2 , FIG. 4A , and FIG. 4B , which will not be described in detail here.

[0266] Step S4302: Bluetooth pairing with the first device.

[0267] The optional implementation of step S4302 can be found in step S2105 of FIG. 2 , the optional implementation of step S4105 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2 , FIG. 4A , and FIG. 4B , which will not be described in detail here.

[0268] In some embodiments, step S4302 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0269] In some embodiments, step S4301 and / or step S4201 may also be combined with step S4101 and / or step S4102 in Figure 4A. For example, in step S4301, the second device sends a second data packet to the first device via a WLAN point-to-point connection.

[0270] FIG4D is a flow chart of a Bluetooth pairing method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a Bluetooth pairing method (on the second device side), the method comprising:

[0271] Step S4401, receiving a first data packet.

[0272] In some embodiments, the second device receives a first data packet sent by the first device, the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, the first data packet includes first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

[0273] In some embodiments, the first OOB data includes at least one of the following fields:

[0274] The first field is used to indicate the length of the first OOB data;

[0275] The second field is used to indicate the device address and address type of the first device;

[0276] The third field is used to indicate the role and capabilities of the first device;

[0277] The fourth field is used to indicate the security connection confirmation value;

[0278] The fifth field is used to indicate a random value for a secure connection.

[0279] In some embodiments, the method comprises:

[0280] The first device and the second device exchange capability information, and the capability information is used by the first device to determine whether to send the first data packet.

[0281] In some embodiments, the first data packet is sent by the first device to the second device when the first device determines that the first device and / or the second device supports OOB, and both the first device and the second device support TCP / IP protocol.

[0282] In some embodiments, the second device receives a first data packet sent by the first device, including:

[0283] The second device establishes a wireless local area network WLAN point-to-point connection with the first device;

[0284] The second device receives the first data packet sent by the first device through a point-to-point connection.

[0285] In some embodiments, the method comprises:

[0286] The second device sends a second data packet to the first device. The second data packet is a data packet based on the TCP / IP protocol. The second data packet includes second OOB data. The second OOB data packet is used for Bluetooth pairing between the first device and the second device.

[0287] FIG5 is a flow chart illustrating the interaction of a Bluetooth pairing method according to an embodiment of the present disclosure. As shown in FIG4B , an embodiment of the present disclosure relates to a Bluetooth pairing method, which includes:

[0288] Step S5101: The first device sends a first data packet to the second device.

[0289] For the optional implementation of step S5101, please refer to the optional implementation of step S2103 in Figure 2, step S3103 in Figure 3A, step S3101 in Figure 3B, step S4103 in Figure 4A, step S4401 in Figure 4B, and other related parts in the embodiments involved in Figures 2, 3A, 3B, 3C, 4A, 4B, and 4C, which will not be repeated here.

[0290] FIG6 is a flow chart of a Bluetooth pairing method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a Bluetooth pairing method, which includes:

[0291] Step S6101: The initiator sends online OOB data to the responder.

[0292] In some embodiments, the initiator may be the first device in the above embodiment, and the responder may be the second device in the above embodiment. Alternatively, the initiator may be the second device in the above embodiment, and the responder may be the first device in the above embodiment. This disclosure is not limited to this.

[0293] In some embodiments, the online OOB data may be the first OOB data or the second OOB data in the above embodiment.

[0294] In some embodiments, the online OOB data may be sent based on the TCP / IP protocol. Alternatively, the online OOB data may be carried by an IP data packet.

[0295] In some embodiments, the format of online OOB data may be as shown in Table 1 below:

[0296] Table 1

[0297] In some embodiments, as shown in Table 1, online OOB data may be used as a payload of an IP data packet between two online Bluetooth devices (e.g., a first device and a second device) that need to be paired, and may include the following fields:

[0298] Online OOB Data Length (2 bytes): identifies the length of the Online OOB Data.

[0299] LE Bluetooth Device Address and Address Type (7 bytes), identifies the address and address type of the Bluetooth device.

[0300] LE Role (1 byte), identifies the role and capabilities of the Bluetooth device.

[0301] LE Secure Connections Confirmation Value (16 bytes), the result of the OOB communication function.

[0302] LE Secure Connections Random Value (16 bytes), a random number transmitted for OOB communication.

[0303] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0304] In some embodiments, online OOB data may be transmitted in a point-to-point manner via WLAN. For example, the initiator may enable the responder to connect to the initiator by enabling the WiFi hotspot function. The initiator may then send online OOB data to the responder and / or receive online OOB data from the responder via the connection.

[0305] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, a first device, a second device, a network device, etc.) in any of the above methods.

[0306] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0307] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0308] Figure 7A is a structural diagram of the first device proposed in an embodiment of the present disclosure. As shown in Figure 7A, the first device 7100 may include: at least one of a transceiver module 7101, a processing module 7102, etc. In some embodiments, the above-mentioned transceiver module 7101 is used to send a first data packet to the second device, and the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, and the first data packet includes a first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device. Optionally, the above-mentioned transceiver module 7101 is used to execute at least one of the communication steps such as sending and / or receiving performed by the first device in any of the above methods, which will not be repeated here. Optionally, the above-mentioned processing module 7102 is used to execute at least one of the other steps performed by the first device in any of the above methods, which will not be repeated here.

[0309] Figure 7B is a structural diagram of the second device proposed in an embodiment of the present disclosure. As shown in Figure 7B, the second device 7200 may include: at least one of a transceiver module 7201, a processing module 7202, etc. In some embodiments, the above-mentioned transceiver module 7201 is used to receive a first data packet sent by the first device, and the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, and the first data packet includes a first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device. Optionally, the above-mentioned transceiver module 7201 is used to execute at least one of the communication steps such as sending and / or receiving performed by the second device in any of the above methods, which will not be repeated here. Optionally, the above-mentioned processing module 7202 is used to execute at least one of the other steps performed by the second device in any of the above methods, which will not be repeated here.

[0310] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0311] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0312] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., a first device, a second device, an access network device, a core network device, etc.), or a terminal (e.g., a first device, a second device, a user device, etc.), or a chip, a chip system, or a processor that supports a network device in implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal in implementing any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0313] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a Bluetooth device, a Bluetooth chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 8100 is used to perform any of the above methods. Optionally, one or more processors 8101 are used to call instructions to enable the communication device 8100 to perform any of the above methods.

[0314] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceiver 8102 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method, and the processor 8101 performs at least one of the other steps. In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0315] In some embodiments, the communication device 8100 further includes one or more memories 8103 for storing data. Alternatively, all or part of the memories 8103 may be located outside the communication device 8100. In alternative embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuits 8104 are connected to the memories 8103 and may be configured to receive data from the memories 8103 or other devices, or to send data to the memories 8103 or other devices. For example, the interface circuits 8104 may read data stored in the memories 8103 and send the data to the processor 8101.

[0316] The communication device 8100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0317] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0318] The chip 8200 includes one or more processors 8201. The chip 8200 is configured to execute any of the above methods.

[0319] In some embodiments, chip 8200 further includes one or more interface circuits 8202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 8200 further includes one or more memories 8203 for storing data. Alternatively, all or part of memory 8203 may be located external to chip 8200. Optionally, interface circuit 8202 is connected to memory 8203 and may be used to receive data from memory 8203 or other devices, or may be used to send data to memory 8203 or other devices. For example, interface circuit 8202 may read data stored in memory 8203 and send the data to processor 8201.

[0320] In some embodiments, the interface circuit 8202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 8202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 8202 performs data exchange between the processor 8201, the chip 8200, the memory 8203, or the transceiver device. In some embodiments, the processor 8201 performs at least one of the other steps.

[0321] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0322] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto, and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and may also be a temporary storage medium.

[0323] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0324] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A Bluetooth pairing method, characterized in that: The method comprises: A first device sends a first data packet to a second device. The first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol. The first data packet includes first out-of-band transmission OOB data. The first OOB data is used for Bluetooth pairing between the first device and the second device.

2. The method according to claim 1, characterized in that The first OOB data includes at least one of the following fields: A first field is used to indicate the length of the first OOB data; The second field is used to indicate the device address and address type of the first device; The third field is used to indicate the role and capabilities of the first device; The fourth field is used to indicate the security connection confirmation value; The fifth field is used to indicate a random value for a secure connection.

3. The method according to claim 1 or 2, characterized in that The method comprises: The first device and the second device exchange capability information, where the capability information is used to indicate whether OOB and / or TCP / IP protocols are supported; The first device determines whether to send the first data packet according to the capability information.

4. The method according to claim 3, characterized in that The first device determining, according to the capability information, whether to send the first data packet includes: The first device determines that the first device and / or the second device supports OOB, and both the first device and the second device support TCP / IP protocol, and sends the first data packet to the second device.

5. The method according to any one of claims 1 to 4, characterized in that The first device sending a first data packet to the second device includes: The first device establishes a wireless local area network WLAN point-to-point connection with the second device; The first device sends the first data packet to the second device through the point-to-point connection.

6. The method according to any one of claims 1 to 5, characterized in that The method comprises: The first device receives a second data packet sent by the second device, where the second data packet is a data packet based on the TCP / IP protocol and includes second OOB data. The second OOB data packet is used for Bluetooth pairing between the first device and the second device.

7. A Bluetooth pairing method, characterized in that: The method comprises: The second device receives a first data packet sent by the first device, where the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, and the first data packet includes first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

8. The method according to claim 7, characterized in that The first OOB data includes at least one of the following fields: A first field is used to indicate the length of the first OOB data; The second field is used to indicate the device address and address type of the first device; The third field is used to indicate the role and capabilities of the first device; The fourth field is used to indicate the security connection confirmation value; The fifth field is used to indicate a random value for a secure connection.

9. The method according to claim 7 or 8, characterized in that The method comprises: The first device and the second device exchange capability information, and the capability information is used by the first device to determine whether to send the first data packet.

10. The method according to claim 9, characterized in that The first data packet is sent by the first device to the second device when the first device determines that the first device and / or the second device supports OOB, and both the first device and the second device support TCP / IP protocol.

11. The method according to any one of claims 7 to 10, characterized in that: The second device receiving a first data packet sent by the first device includes: The second device establishes a wireless local area network WLAN point-to-point connection with the first device; The second device receives the first data packet sent by the first device through the point-to-point connection.

12. The method according to any one of claims 7 to 11, characterized in that: The method comprises: The second device sends a second data packet to the first device, where the second data packet is a data packet based on the TCP / IP protocol and includes second OOB data. The second OOB data packet is used for Bluetooth pairing between the first device and the second device.

13. A first device, characterized in that: The first device includes: The transceiver module is used to send a first data packet to the second device, where the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, and the first data packet includes first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

14. A second device, characterized in that: The second device includes: The transceiver module is used to receive a first data packet sent by a first device, where the first data packet is a data packet based on the Transmission Control Protocol / Internet Protocol TCP / IP protocol, and the first data packet includes first out-of-band transmission OOB data, and the first OOB data is used for Bluetooth pairing between the first device and the second device.

15. A first device, characterized in that: include: one or more processors; A memory coupled to the one or more processors, the memory comprising executable instructions, which, when executed by the one or more processors, causes the first device to execute the Bluetooth pairing method according to any one of claims 1 to 6.

16. A second device, characterized in that: include: one or more processors; A memory coupled to the one or more processors, the memory comprising executable instructions, which, when executed by the one or more processors, causes the second device to execute the Bluetooth pairing method according to any one of claims 7 to 12.

17. A communication system, characterized in that: The method comprises a first device and a second device, wherein the first device is configured to implement the Bluetooth pairing method according to any one of claims 1 to 6, and the second device is configured to implement the Bluetooth pairing method according to any one of claims 7 to 12.

18. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device is enabled to perform the Bluetooth pairing method according to any one of claims 1 to 6 or claims 7 to 12.

Images