Bluetooth device network connection method, apparatus, and device

Abstract

The embodiments of this specification disclose a method, apparatus, and device for networking Bluetooth devices. By receiving a service request from a Bluetooth device that employs a client standard protocol, obtaining first device information of the Bluetooth device, determining a communication link that employs the client standard protocol based on the first device information, and transmitting the service request to a server via the communication link, a broad adaptation to different types of Bluetooth devices is achieved, enabling different types of Bluetooth devices to acquire network connectivity capabilities through this method and thus broadening adaptability.

Description

Technical Field

[0001] This specification relates to the technical field of the Internet, and particularly to a method, apparatus, and device for network connection of Bluetooth devices.

Background Art

[0002] With the development of the Internet of Things, the types of Bluetooth devices are also diversifying. Considering cost and power consumption, some smart wearable watches do not have a network connection function, that is, the ability to request a network from a remote server regularly or almost in real time. To overcome this drawback, some device manufacturers provide network connection solutions for Bluetooth devices via mobile phones or manufacturer apps, but these are generally closed and it is difficult to simultaneously meet the network connection needs of increasingly diverse Bluetooth devices, lacking adaptability.

[0003] Based on this, a more adaptable network connection solution for Bluetooth devices is required.

Summary of the Invention

[0004] Embodiments of this specification provide a method, apparatus, device, and storage medium for network connection of Bluetooth devices, aiming to solve the technical problem of the need for a more adaptable network connection solution for Bluetooth devices.

[0005] To solve the above technical problems, one or more embodiments of this specification are implemented as follows. In the first embodiment, an embodiment of this specification provides a method for networking a Bluetooth device applied to a client, the method comprising: receiving a service request transmitted from the Bluetooth device that employs a client standard protocol; obtaining first device information of the Bluetooth device; determining a communication link that employs the client standard protocol based on the first device information; and transmitting the service request to a server via the communication link.

[0006] In a second aspect, embodiments of this specification provide a method for networking another Bluetooth device applicable to a Bluetooth device, the method comprising: generating a service request and determining the protocol type of the service request; translating the protocol type of the service request into a client standard protocol; and sending a service request to a client that employs the client standard protocol so that the client determines a communication link and transmits the service request to a server based on the communication link.

[0007] In a third aspect, corresponding to the first aspect, an embodiment of this specification provides a network connection device for a Bluetooth device applied to a client, the device including a receiving module that receives a service request from a Bluetooth device employing a client standard protocol, an acquisition module that acquires first device information of the Bluetooth device, a determination module that determines a communication link employing the client standard protocol based on the first device information, and a transmission module that transmits the service request to a backend server via the communication link.

[0008] In a fourth aspect, corresponding to the second aspect, an embodiment of the Specified herein provides a Bluetooth device network connection device applicable to a Bluetooth device, the device including a generating module that generates a service request and determines the protocol type of the service request; a conversion module that converts the protocol type of the service request to a client standard protocol; and a transmitting module that transmits a service request to a client employing the client standard protocol so that the client determines a communication link and transmits the service request to a server based on the communication link.

[0009] In a fifth aspect, one or more embodiments of this specification provide an electronic device comprising at least one processor and a memory communicably connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the at least one processor can perform the method according to the first or second aspect by executing the instructions by the at least one processor.

[0010] In a sixth aspect, embodiments of this specification provide a non-volatile computer storage medium in which computer-executable instructions are stored, and when a computer reads a computer-executable instruction from the storage medium, the instruction causes one or more processors to perform the method described in the first aspect.

[0011] At least one of the above technical solutions employed by one or more embodiments of this specification can achieve the following beneficial effects: By receiving a service request from a Bluetooth device employing a client standard protocol, obtaining first device information of the Bluetooth device, determining a communication link employing the client standard protocol based on the first device information, and transmitting the service request to a server via the communication link, it enables broad adaptation to different types of Bluetooth devices, allowing different types of Bluetooth devices to acquire network connectivity capabilities through the method and thus broadening adaptability.

[0012] To more clearly illustrate the technical solutions in the embodiments described herein, the following briefly introduces the drawings necessary for describing the embodiments. Naturally, the drawings in the following description represent only a selection of embodiments described herein, and those skilled in the art can obtain other drawings based on these without requiring any creative effort. [Brief explanation of the drawing]

[0013] [Figure 1] This is a flowchart of the network connection method for a Bluetooth device provided by the embodiments of this specification. [Figure 2] This is a schematic diagram of the Bluetooth device SDK architecture provided by the embodiments of this specification. [Figure 3] This is a schematic diagram of link aggregation provided by the embodiments of this application. [Figure 4] This is a schematic diagram of the system architecture of a device where a client is located, as provided by the embodiments of this application. [Figure 5] This is a flowchart of a network connection method for another Bluetooth device provided by the embodiments of this specification. [Figure 6]This is a schematic diagram of the structure of a network connection device for a Bluetooth device provided by the embodiments of this specification. [Figure 7] This is a schematic diagram of the structure of a network connectivity device for another Bluetooth device provided by the embodiments of this specification. [Figure 8] This is a schematic diagram of the structure of an electronic device provided by the embodiments of this specification. [Modes for carrying out the invention]

[0014] The embodiments described herein provide a method, apparatus, device, and storage medium for networking Bluetooth devices.

[0015] To enable those skilled in the art to easily understand the technical solutions of this specification, the following will clearly and completely describe the technical solutions in the embodiments of this specification with reference to the drawings in the embodiments of this specification. Naturally, the embodiments described are only a part of the embodiments of this application, not all of them. All other embodiments that can be obtained by those skilled in the art without creative effort based on the embodiments of this specification are within the scope of protection of this application.

[0016] Current Bluetooth devices, especially wearable smart Bluetooth devices, generally lack network connectivity due to cost and power consumption considerations. In this context, network connectivity refers to the ability of a Bluetooth device to autonomously interact with a remote server.

[0017] However, in practical applications, some functions of these devices may require network connectivity. For example, if a Bluetooth watch has a QR code payment service, it needs to obtain deposit QR codes and payment QR codes from a server. Here, the deposit QR code may not need to change within a week (the Bluetooth watch may need to interact with the server once a week to update the deposit QR code, i.e., it may require periodic network connectivity), but the payment QR code may expire within a minute (the Bluetooth watch may need to interact with the server once a minute to update the payment QR code when a payment is made, i.e., it may require near real-time network connectivity).

[0018] To achieve this functionality, current Bluetooth device manufacturers offer several solutions. The first solution, for manufacturers capable of producing both mobile phones and Bluetooth devices, is to establish a device communication link between the Bluetooth device and the mobile phone based on the operating systems built into the mobile phones and Bluetooth devices they produce. However, this link is relatively closed and generally cannot be ported to other Bluetooth devices.

[0019] As a second countermeasure, in the case of a manufacturer that can only produce Bluetooth devices, generally, for Android and IOS systems, a corresponding manufacturer application is developed, and a communication link with its own Bluetooth device is established through the manufacturer application. Such a method is also relatively closed in the same way. On the one hand, the manufacturer application is generally only provided for connection with its own Bluetooth device, the connection is unstable, and background operations are also easily restricted. On the other hand, for users, such a method means that every time a new manufacturer's Bluetooth device is used, it is necessary to download and install a new manufacturer application, and the user experience is very poor. Based on this, the embodiments of this specification provide a network connection solution for Bluetooth devices to adapt to a wider range of Bluetooth devices. The embodiments of this specification include two aspects: the client and the Bluetooth device.

[0020] In the first aspect, as shown in FIG. 1, which is a flowchart of the network connection method for Bluetooth devices provided by the embodiments of this specification and is applied to the client, the flow in FIG. 1 may include steps S101 to S107.

[0021] In S101, a service request adopting the client standard protocol transmitted from the Bluetooth device is received.

[0022] In a Bluetooth device, due to the device type adopted by the manufacturer, the chip type installed in the device, and the services provided, there are significant differences in the adoptable internal protocols.

[0023] For example, some of the functions provided by Bluetooth devices only require the adoption of the BLE standard protocol. However, for some other Bluetooth devices, in order to provide manufacturer-specific functions, they may adopt the manufacturer's private protocol. To achieve adaptation to a wide range of Bluetooth devices, in the development process, a Software Development Kit (SDK) for the corresponding Bluetooth device is also provided. As shown in Figure 2, Figure 2 is an architectural schematic diagram of the Bluetooth device SDK side provided by the embodiments of this specification.

[0024] Based on this architecture, in the development process, different types of protocols can be selected according to actual needs, and through protocol adaptation, a series of client standard protocols are provided in the protocol aggregation layer. As a result, any protocol adopted by the Bluetooth device can be converted into a client standard protocol, enabling communication with the external world.

[0025] In this development process, the client provides the corresponding platform, and the manufacturer adapts and aggregates the private protocol on this platform, and finally transplant the generated corresponding code to its own Bluetooth device. In other words, this process is not complicated for the manufacturer of the Bluetooth device, and the manufacturer only needs to provide the corresponding private protocol and conform to the client standard protocol. The code that needs to be transplanted finally does not include other irrelevant protocol types. By this method, the Bluetooth device can realize the interaction based on the standard BLE protocol, and at the same time, realize the bridge and compatibility with the manufacturer's private protocol, making the best use of the existing link function.

[0026] The service requests may include, for example, connection establishment, binding, device wake-up, data transfer, proxy requests to network services, and business request services. The service requests require network connectivity, i.e., communication between the Bluetooth device and a remote server.

[0027] In S103, the first device information of the Bluetooth device is obtained.

[0028] The first device information includes the model, chip model, and manufacturer of the Bluetooth device. A Bluetooth device can carry this first device information during the process of transmitting a service request. A client can also obtain the first device information of Bluetooth devices in its surrounding environment by scanning.

[0029] For example, the client can obtain the type of Bluetooth device, "Mi Smart Band 6," through the Bluetooth scanning function provided by the device it is located on, thereby determining the type of smart band it corresponds to, and further obtaining the device model, chip model, and manufacturer corresponding to that smart band type.

[0030] In S105, based on the first device information, the communication link that adopts the client standard protocol is determined.

[0031] After the client obtains the first device information of the Bluetooth device, it needs to determine the corresponding communication link from the Bluetooth device to the server in order to fulfill a service request that requires network connectivity. Since the client has a pre-aggregated set of different communication links, it can perform a corresponding matching based on the first device information (i.e., the Bluetooth device model, chip model, and manufacturer, etc.) to determine and obtain the communication link. When transmitting information on the obtained communication link, the aforementioned client standard protocol is adopted.

[0032] In one embodiment, to determine a communication link based on the first device information, the communication link can be determined based on the first device information and the service request type, or the second device information of the device where the client is located can be obtained, and the communication link can be determined based on the first device information and the second device information.

[0033] The pre-configured device set includes device information of Bluetooth devices that have undergone corresponding protocol aggregation via the aforementioned SDK, or the pre-configured device set includes device information of Bluetooth devices that have been pre-approved by the client (i.e., the Bluetooth device is authorized by the client to provide related custom services via the client).

[0034] In other words, Bluetooth devices included in a pre-configured device set are typically Bluetooth devices that use a private protocol, and these Bluetooth devices provide corresponding custom services via that private protocol. For this type of Bluetooth device, the user usually needs to pre-install the corresponding manufacturer application on their local device in order to fulfill custom service requests that are only possible with that Bluetooth device.

[0035] The type of service request referred to here may specifically include whether or not it matches the client type. That is, whether or not the client can provide the functional support corresponding to the service request. For example, if the type of service request is "acquisition of a QR code for payment" and the client type is "payment," then it can be determined that the two are a match. Alternatively, this correspondence between the type of service request and the client type can be established in advance and stored on the client, allowing the client to query whether the corresponding type of service request matches the client type based on the locally stored correspondence. If a match is confirmed, a communication link can be established between the Bluetooth device and the client without going through the manufacturer's application.

[0036] As mentioned above, Bluetooth devices employ client standard protocols during communication. Client standard protocols refer to protocols that clients can identify and analyze, as well as protocols used for internal client communication or communication between the client and its corresponding server. Therefore, a communication link can be established between the client and the Bluetooth device without interference, and the client can establish a network connection with the remote server. Based on this communication link, communication between the Bluetooth device and the remote server can be realized.

[0037] In this embodiment, if it is confirmed that the first device information belongs to a pre-configured device set and the service request type does not match the client, it is understood that the client service cannot provide the functionality to respond to the Bluetooth device's service request. In other words, a custom service by the manufacturer's application corresponding to the Bluetooth device is required to fulfill the service request. In this case, the client can determine the manufacturer's application corresponding to the first device information (usually this can be pre-configured by the client), thereby allowing the client to launch the manufacturer's application, establish a communication link between the Bluetooth device and the manufacturer's application, and establish a network connection with a remote server via the manufacturer's application.

[0038] In one embodiment, when establishing a communication link based on the first device information and the second device information, the first device information and the second device information are matched, and if the first device information matches the second device information, the device communication link provided by the device where the client is located is determined, and a communication link is established between the Bluetooth device, the device communication link and the client.

[0039] The matching conditions for the first and second device information may include, for example, that the manufacturers are the same or that the device models are the same. If the Bluetooth device and the device where the client is located are manufactured by the same manufacturer, the Bluetooth device may also be a peripheral device of the device where the client is located. In this case, the manufacturer typically designs a dedicated device communication link between its devices based on the chip capabilities and development engine of Bluetooth, WiFi, NFC, etc. Subsequently, communication between the Bluetooth device and the device where the client is located is realized based on this device communication link, including proxying and forwarding network requests from the Bluetooth device. Because the entire device communication link, including the chip, system, and device, is managed by the manufacturer itself, the stability of the link is usually relatively high.

[0040] In one embodiment, if the first device information does not belong to the pre-configured device set (i.e., the Bluetooth device is not a device from a predetermined manufacturer), the client needs to adopt a standard communication link provided by the operating system of the device on which it is located and establish a communication link between the Bluetooth device and the standard communication link. In this operation, the general-purpose Bluetooth function provided by the operating system is used to establish a link for communication with the Bluetooth device.

[0041] Furthermore, it should be explained that if the Bluetooth device itself has 4G / 5G network connectivity, for example, certain Bluetooth devices can communicate with remote servers via cellular networks (CAT1 / CAT4), and in this case, the solution of this application is compatible with such Bluetooth devices. If the 4G / 5G network connectivity of the Bluetooth device becomes unavailable, the solution of this application can be used to establish a network connection. As shown in Figure 3, Figure 3 is a schematic diagram of link aggregation provided by an embodiment of this application. As can be seen from this schematic diagram, a complete communication link should include the complete link from service initiation to the server, for example, for one custom service, its corresponding communication link is custom service initiation → request transmission → manufacturer application → gateway → server, and the data backflow portion is omitted in this schematic diagram. Generally, the communication link used by data backflow is the same link, only the direction of data flow is reversed.

[0042] In S107, the service request is transmitted to the server via the communication link.

[0043] In an established communication link, service requests are forwarded to the server via a gateway based on the different communication links, thereby enabling the network connectivity function of the Bluetooth device. As shown in Figure 4, Figure 4 is a schematic diagram of the system architecture of a device where a client resides, provided by an embodiment of this application. This architecture allows the client to adapt to different operating systems, platforms, and a wide range of communication protocols, thereby enabling a unified Bluetooth service for diverse Bluetooth devices.

[0044] By receiving a service request using a client standard protocol transmitted from a Bluetooth device, acquiring first device information of the Bluetooth device, determining a communication link using the client standard protocol based on the first device information, and transmitting the service request to a server via the communication link, broad compatibility with different types of Bluetooth devices is achieved, enabling different types of Bluetooth devices to acquire network connectivity capabilities through this method and thus broadening adaptability.

[0045] In one embodiment, when determining a communication link based on the first device information, particularly when a client and the Bluetooth device establish a communication connection for the first time, the client can scan for surrounding Bluetooth devices based on a Bluetooth device scanning function provided by the device at hand, obtain a Universally Unique Identifier (UUID) included in the first device information of the Bluetooth device, and establish a communication link with the client based on the UUID.

[0046] Specifically, the client scans for surrounding devices, scans for a bluetoothDevice to obtain a bluetoothSocket(UUID), and then connects to the surrounding Bluetooth device using bluetoothSocket.connect(UUID), where the UUID is the UUID specified by the Bluetooth device.

[0047] A Bluetooth device obtains a generic identifier, BluetoothServerSocket(Name, UUID), via a Bluetooth adapter. Both Name and UUID are specified by the Bluetooth device (the smart device in question). The client connects to the Bluetooth device via this UUID, establishing communication between the two. This method establishes a communication link between the two by creating a listening service port with a name and a unique identifier.

[0048] It should be noted that the communication link established at this point is merely a communication link between the Bluetooth device and the client; in other words, the communication link established at this point does not yet require, and may not even have, network connectivity functionality.

[0049] In one embodiment, if multiple Bluetooth devices are present around a client, a self-organizing Bluetooth network can be configured among the multiple Bluetooth devices. Each Bluetooth device in the Bluetooth network can communicate with each other using a publish / subscribe messaging system. Any device in the Bluetooth network can act as a relay device, retransmitting messages received from other devices, and a single message can be received by all devices within range through multiple relays.

[0050] Based on this, when establishing an initial connection, if the client scans for multiple Bluetooth devices, it can communicate with any device in the Bluetooth network composed of the Bluetooth devices, receive a general-purpose identifier included in the first device information of the Bluetooth device broadcast by the Bluetooth network, and then establish communication with the Bluetooth device based on the general-purpose identifier to determine the subsequent communication link.

[0051] In a second embodiment, the method is applied to a Bluetooth device as shown in Figure 5, which is a flowchart of a network connection method for another Bluetooth device provided by an embodiment of this specification, the method comprising: S501 generating a service request and determining the protocol type of the service request; S503 converting the protocol type of the service request to a client standard protocol; and S505 sending a service request to a client that adopts the client standard protocol so that the client determines a communication link and transmits the service request to the server based on the communication link.

[0052] Service requests may include, for example, connection establishment, binding, device wake-up, data transfer, proxy requests to network services, and business request services (e.g., payments, rides, and utilities).

[0053] As shown in Figure 2 above, compared to conventional Bluetooth devices, this Bluetooth device provides a protocol aggregation layer that performs protocol adaptation and conversion during the development process, thereby enabling adaptation to various types of Bluetooth devices and providing network connectivity functionality.

[0054] To further clarify the solutions of the examples described herein, specific examples are given below.

[0055] The client first scans for Bluetooth devices and obtains the first device information of nearby Bluetooth devices. When establishing the initial connection, it establishes a listening service port based on the generic identifier UUID provided by the Bluetooth device, and then establishes a connection with the Bluetooth device based on that listening service port. This connection usually does not require a network connection to a remote server.

[0056] After the connection is established, the Bluetooth device sends a corresponding service request (e.g., payment service or custom service), and upon receiving the service request, the client determines the communication link based on the first device information.

[0057] Because Bluetooth devices have protocol conformance and aggregation pre-integrated, service requests initiated by Bluetooth devices can adopt client standard protocols, and even in established communication links, information is transmitted using at least partially the said client standard protocols.

[0058] For example, if the Bluetooth device is an approved manufacturer's product and the service request is a payment service supported by the client (including obtaining a payment QR code, obtaining a deposit QR code, and checking payment details), a communication link is established between the Bluetooth device and the client. Based on the aforementioned communication link, the client forwards the service request to the remote server, and the payment service is completed through forwarding by the client's proxy. For example, a request to obtain a deposit QR code is forwarded to the server, the deposit QR code is received from the server, and the deposit QR code is transmitted to the Bluetooth device based on the aforementioned communication link.

[0059] As another example, if the matching results in a match between the first device information and the second device information, meaning that the Bluetooth device and the device where the client is located are manufactured by the same manufacturer and their device models or chip functions match (for example, both are WearEngine-based devices), and the manufacturer has previously provided device communication links between its various devices, then for the service request, the device communication link provided by the manufacturer will be adopted to establish a communication link between the Bluetooth device, the device communication link, and the client, thereby realizing a 4G / 5G network connection and achieving more stable communication.

[0060] As another example, if it is determined that the Bluetooth device does not belong to a pre-configured set of devices, that is, that the relevant functions of the Bluetooth device have not been approved by the client, the client can adopt a standard communication link provided by the operating system of the device on which it is located, establish a communication link between the Bluetooth device and the standard communication link, thereby enabling a 4G / 5G network connection.

[0061] As can be seen from the examples described above, the embodiments of this application are widely adaptable to different types of Bluetooth devices and can enable network connectivity of Bluetooth devices. Furthermore, even for different service requests on the same Bluetooth device, it is possible to select the appropriate communication link based on the device type and the type of service request.

[0062] Based on the same concept, as shown in Figures 6 and 7, one or more embodiments of this specification further provide apparatus and devices corresponding to the methods described above.

[0063] In a third aspect, corresponding to the first aspect, the embodiments of this specification further provide a network connection device for a Bluetooth device applied to a client, as shown in Figure 6, a schematic diagram of the structure of the network connection device for a Bluetooth device provided by the embodiments of this specification, the device includes: a receiving module 601 that receives a service request employing a client standard protocol transmitted from a Bluetooth device; an acquisition module 603 that acquires first device information of the Bluetooth device; a determination module 605 that determines a communication link employing the client standard protocol based on the first device information; and a transmission module 607 that transmits the service request to a backend server via the communication link.

[0064] Selectively, the decision module 605 determines a communication link based on the first device information and the service request type, or obtains second device information of the device on which the client is located, and determines a communication link based on the first device information and the second device information.

[0065] Selectively, the determination module 605 determines a manufacturer application corresponding to the first device information and establishes a communication link between the Bluetooth device and the manufacturer application if the first device information belongs to a preset device set and the service request type does not match the client, or establishes a communication link between the Bluetooth device and the client if the first device information belongs to a preset device set and the service request type matches the client.

[0066] Selectively, the determination module 605 determines the device communication link provided by the device where the client is located if the first device information matches the second device information, and establishes a communication link between the Bluetooth device, the device communication link, and the client.

[0067] Selectively, if the first device information does not belong to the preset device set, the determination module 605 determines a standard communication link provided by the operating system of the device where the client is located and establishes a communication link between the Bluetooth device and the standard communication link.

[0068] Selectively, the decision module 605 scans for surrounding Bluetooth devices, obtains a generic identifier included in the first device information of the Bluetooth device, and establishes a communication link with the client based on the generic identifier.

[0069] Selectively, the determination module 605 determines a Bluetooth network composed of the plurality of Bluetooth devices and receives a general-purpose identifier included in the first device information of the Bluetooth device, which is broadcast by the Bluetooth network.

[0070] In a fourth aspect, corresponding to the second aspect, the embodiments of this specification further provide another Bluetooth device network connection device applicable to a Bluetooth device, as shown in Figure 7, a schematic structural diagram of another Bluetooth device network connection device provided by the embodiments of this specification, the device includes a generating module 701 that generates a service request and determines the protocol type of the service request; a converting module 703 that converts the protocol type of the service request to a client standard protocol; and a transmitting module 705 that transmits a service request to a client adopting the client standard protocol so that the client determines a communication link and transmits the service request to a server based on the communication link.

[0071] In the fifth aspect, as shown in Figure 8, a schematic diagram of the structure of an electronic device provided by an embodiment of this specification, the device comprises at least one processor and a memory communicably connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the at least one processor can perform the method of the first or second aspect by executing the instructions by the at least one processor.

[0072] In a sixth aspect, based on the same concept, embodiments of this specification further provide a non-volatile computer storage medium corresponding to the above method, wherein computer-executable instructions are stored therein, and when a computer reads a computer-executable instruction from the storage medium, the instruction causes one or more processors to execute the method of the first or second aspect.

[0073] In the 1990s, it was possible to clearly distinguish between improvements to a technology that were hardware improvements (e.g., improvements to circuit structures such as diodes, transistors, and switches) and software improvements (improvements to method flows). However, with technological advancements, many method flow improvements can now be considered direct improvements to hardware circuit structures. Most designers acquire the corresponding hardware circuit structures by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that method flow improvements cannot be realized by physical hardware modules. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is an integrated circuit whose logic function is determined by programming the device by the user. By programming themselves, designers can "integrate" a single digital system onto a single PLD, eliminating the need to request the design and manufacture of dedicated integrated circuit chips from chip manufacturers.Furthermore, instead of manually manufacturing integrated circuit chips, such programming is now often achieved using "logic compiler" software. This is similar to the software compilers used during program development and writing, and the source code to be compiled must also be written in a specific programming language, known as a Hardware Description Language (HDL). There is not just one HDL; many exist, including ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most widely used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. As those skilled in the art will understand, by performing some logic programming on a method flow using one of the aforementioned hardware description languages ​​and then programming that into an integrated circuit, a hardware circuit that realizes that logic method flow can be easily obtained.

[0074] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor, a computer-readable medium for storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, or embedded microcontrollers. Examples of controllers include, but are not limited to, the ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320 microcontrollers. Furthermore, the memory controller can be implemented as part of the memory control logic. As those skilled in the art will see, in addition to the implementation method of the controller using pure computer-readable program code, the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, embedded microcontrollers, etc., and achieve the same functionality by logic programming method steps. Therefore, such a controller can be considered a hardware component, and the devices contained within it that realize various functions can also be considered structures within the hardware component. Alternatively, the devices that realize various functions can be considered both as software modules that realize methods and as structures within the hardware component.

[0075] The systems, devices, modules, or units described in the embodiments above may be implemented by computer chips or physical entities, or by products having some function. A typical implementing device is a computer. Specifically, a computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal data assistant (PDA), a media player, a navigation device, an e-mail device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0076] For the sake of clarity, the above devices have been described by dividing them into various units according to their function. Naturally, in implementing this specification, it is also possible to implement the functions of each unit using one or more identical software and / or hardware components.

[0077] It will be obvious to those skilled in the art that the embodiments described herein may be provided as methods, systems, or computer program products. Accordingly, the embodiments described herein may take the form of complete hardware embodiments, complete software embodiments, or embodiments combining software and hardware. Furthermore, the embodiments described herein may take the form of computer program products implemented on one or more computer-readable storage media (including, but not limited to, disk memory, CD-ROM, optical memory, etc.) containing computer-readable program code.

[0078] This specification will be described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments herein. As can be understood, each flow and / or block in a flowchart and / or block diagram, and combinations of flows and / or blocks in a flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate equipment, which can be generated by instructions executed by the processor of the computer or other programmable data processing equipment to implement one or more flows in a flowchart and / or one or more blocks in a block diagram.

[0079] These computer program instructions may be stored in computer-readable memory that can operate a computer or other programmable data processing equipment in a particular way, thereby generating a product including an instruction unit, which implements a function specified in one or more flows of a flowchart and / or one or more blocks of a block diagram.

[0080] These computer program instructions may be loaded into a computer or other programmable data processing equipment, thereby executing a series of operational steps on the computer or other programmable equipment, enabling the processing implemented on the computer, and furthermore, the instructions executed on the computer or other programmable equipment provide steps to realize the functions specified in one or more flows of a flowchart and / or one or more blocks of a block diagram.

[0081] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0082] Memory can take the form of non-persistent storage, random-access memory (RAM), and / or non-volatile memory in a computer-readable medium, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0083] Computer-readable media include persistent and non-persistent, removable and non-removable media, and are capable of storing information by any means or technique. Information may be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), other types of random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, or other memory technologies, portable compact disc read-only memory (CD-ROM), digital purpose discs (DVDs), other optical storage, magnetic cassette tapes, magnetic tape / disk storage, other magnetic storage devices, or any other non-transmission media, all of which can be used to store information accessible by computing devices. As defined herein, computer-readable media do not include transient media such as modulated data signals and carrier waves.

[0084] Furthermore, since “includes,” “equips,” and other variations are intended to be non-exclusive, a process, method, product, or equipment that includes a set of elements includes not only those elements but also other elements not explicitly listed, or elements specific to that process, method, product, or equipment. Unless further limited, an element limited by the statement “includes one…” does not preclude the presence of another identical element in a process, method, product, or equipment that includes the said element.

[0085] This specification is written in the general context of computer executable instructions, such as program modules, that are executed by computers. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. It is also possible to implement this specification in a distributed computing environment, in which tasks are executed by remote processing devices connected via a communication network. In a distributed computing environment, program modules may reside on local and remote computer storage media, including memory devices.

[0086] Each example in this specification is described in a progressive manner, and parts that are identical or similar between examples should be cross-referenced. Each example focuses on explaining the differences from other examples. In particular, the examples of apparatus, devices, and non-volatile computer storage media are basically similar to the examples of methods, so their descriptions are relatively simple, and relevant parts should be referred to the corresponding descriptions in the examples of methods.

[0087] The above describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the operations or steps described in the claims may be performed in a different order than those described in the embodiments to obtain the desired results. Furthermore, the processes depicted in the appended drawings do not necessarily require the specific order or sequence shown to obtain the desired results. In some embodiments, multitasking or parallel processing may be possible or advantageous.

[0088] The above are one or more embodiments of this specification, but they are not limiting to this specification. Those skilled in the art can make various changes and modifications to one or more embodiments of this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of one or more embodiments of this specification should all be included in the claims of this specification.

Claims

1. A method for connecting a Bluetooth device to a network, which is applied to a client, The steps include receiving a service request from a Bluetooth device that employs a client standard protocol, The steps include: obtaining first device information of the Bluetooth device; The steps include determining a communication link that adopts the client standard protocol based on the first device information, The steps include transmitting the service request to the server via the aforementioned communication link, and Methods that include...

2. The step of determining a communication link based on the first device information is: Determining the communication link based on the first device information and service request type, or The process involves obtaining second device information of the device where the client is located, and determining a communication link based on the first device information and the second device information. The method according to claim 1, including the method described in claim 1.

3. Determining the communication link based on the first device information and service request type means If the first device information belongs to a pre-configured device set and the service request type does not match the client, the manufacturer application corresponding to the first device information is determined, and a communication link is established between the Bluetooth device and the manufacturer application, or If the first device information belongs to a pre-configured device set and the service request type matches the client, a communication link is established between the Bluetooth device and the client. The method according to claim 2, including the method described in claim 2.

4. Determining a communication link based on the first device information and the second device information means If the first device information matches the second device information, the device communication link provided by the device where the client is located is determined, To establish a communication link between the Bluetooth device, the device communication link, and the client. The method according to claim 2, including the method described in claim 2.

5. The step of determining a communication link based on the first device information is: The method according to claim 3, further comprising determining a standard communication link provided by the operating system of the device on which the client is located, and establishing a communication link between the Bluetooth device and the standard communication link, if the first device information does not belong to the pre-configured device set.

6. The step of determining a communication link based on the first device information is: Scanning surrounding Bluetooth devices and obtaining a general-purpose identifier included in the first device information of the Bluetooth device, To establish a communication link with the client based on the aforementioned general identifier. The method according to claim 1, including the method described in claim 1.

7. If there are multiple Bluetooth devices in the vicinity, obtaining the general-purpose identifier included in the first device information of the Bluetooth device is: The method according to claim 6, comprising determining a Bluetooth network composed of the plurality of Bluetooth devices, and receiving a general-purpose identifier included in the first device information of the Bluetooth device that is broadcast by the Bluetooth network.

8. A method for connecting a Bluetooth device to a network, applicable to a Bluetooth device, The steps include generating a service request and determining the protocol type of the service request, The steps include converting the protocol type of the service request to the client standard protocol, A step of sending a service request to a client that employs the client standard protocol so that the client determines the communication link and transmits the service request to the server based on the communication link. Methods that include...

9. A network connection device for a Bluetooth device applied to a client, A receiving module that receives service requests using the client standard protocol sent from a Bluetooth device, An acquisition module for acquiring first device information of the Bluetooth device, A decision module that determines a communication link that adopts the client standard protocol based on the first device information, A transmission module that transmits the service request to the backend server via the aforementioned communication link. A device including a device.

10. A Bluetooth device network connection device applicable to a Bluetooth device, A generation module that generates a service request and determines the protocol type of the service request, A conversion module that converts the protocol type of the service request to the client standard protocol, A transmission module that sends a service request to the client using the client standard protocol, so that the client determines the communication link and transmits the service request to the server based on the communication link. A device including a device.

11. It is an electronic device, At least one processor, A memory that is communicably connected to at least one of the processors and Equipped with, An electronic device in which the memory stores instructions that can be executed by the at least one processor, and the at least one processor can perform the method according to any one of claims 1 to 8 by executing the instructions by the at least one processor.

Images