Wireless connecting method, computer, and non-transitory computer-readable storage medium

Abstract

A wireless connecting method is disclosed. The wireless connecting method includes the following operations: connecting a device to a computer by BLUETOOTH; determining the computer is a host or a accessory for the device; operating the computer as the host for the device by a Microsoft BLUETOOTH stack if the computer is the host for the device; and operating the computer as the accessory for the device by an application if the computer is the accessory for the device. The computer is operated as the host and the accessory at the same time.

Description

FIELD OF INVENTION

The invention relates to a wireless connecting method, a computer, and a non-transitory computer-readable storage medium. More particularly, the invention relates to a wireless connecting method, a computer, and a non-transitory computer-readable storage medium for wireless connection by BLUETOOTH between a computer and other devices.

BACKGROUND

BLUETOOTH is a wireless technology standard for exchanging data over short distances (using short-wavelength UHF radio waves in the ISM band from 2.4 to 2.485 GHz) from fixed and mobile devices and building personal area networks (PANs). It can connect several devices, overcoming problems of synchronization.

According to the BLUETOOTH specification, when a personal computer (PC), such as a desktop or a laptop computer, is connected with one or more external devices through BLUETOOTH, the PC generally serves as a BLUETOOTH host device and the external devices serve as BLUETOOTH accessory devices. In other words, a PC itself cannot be a Bluetooth accessory of other Bluetooth device. A way to solve the problem is to implement a BLUETOOTH application so that the PC may work as a host and an accessory of the connected device at the same time.

However, the Microsoft system has the Microsoft Bluetooth stack which may operate the PC as a host for a device connected to the PC by Bluetooth originally, and it may be convenience if the BLUETOOTH application implemented can co-exist with the Microsoft Bluetooth stack.

SUMMARY

An embodiment of this disclosure is to provide a wireless connecting method includes the following operations: connecting a device to a computer by BLUETOOTH; determining the computer is a host or accessory for the device; operating the computer as the host for the device by a Microsoft BLUETOOTH stack if the computer is the host for the device; and operating the computer as the accessory for the device by an application if the computer is the accessory for the device. The computer is operated as the host and accessory at the same time.

An embodiment of this disclosure is to provide a computer includes a memory and a processor. The memory includes an application to handle a device connected to the computer by BLUETOOTH. The processor is configured to run the application to determine whether the computer is a host or a accessory for the device. The processor operates the computer as the host for the device by a Microsoft BLUETOOTH stack if the computer is the host for the device, and the processor operates the computer as the accessory for the device by an application if the computer is the accessory for the device. The computer is operated as the host and the accessory at the same time.

The embodiment of the present disclosure is to provide a non-transitory computer-readable storage medium storing a computer program performing a wireless connecting method. The wireless connecting method includes the following operations: connecting a device to a computer by BLUETOOTH; determining the computer is a host or a accessory for the device; operating the computer as the host for the device by a Microsoft BLUETOOTH stack if the computer is the host for the device; and operating the computer as the accessory for the device by an application if the computer is the accessory for the device. The computer is operated as the host and the accessory at the same time.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the following detailed description when read with the accompanying figures. It is noted that, in accordance with the standard practice in the industry, various features are not drawn to scale. In fact, the dimensions of the various features may be arbitrarily increased or reduced for clarity of discussion.

FIG. 1 is a schematic diagram illustrating a computer according to some embodiments of the present disclosure.

FIG. 2 is a schematic diagram illustrating a driving system according to some embodiments of the present disclosure.

FIG. 3 is a flow chart illustrating a driving system according to some other embodiments of the present disclosure.

FIG. 4 is a flow chart illustrating a driving system according to some other embodiments of the present disclosure.

FIG. 5 is a flow chart illustrating a wireless connecting method according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

The following disclosure provides many different embodiments, or examples, for implementing different features of the invention. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting. In addition, the present disclosure may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed.

The terms used in this specification generally have their ordinary meanings in the art, within the context of the invention, and in the specific context where each term is used. Certain terms that are used to describe the invention are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the invention.

Reference is made to FIG. 1. FIG. 1 is a schematic diagram illustrating a computer 100 according to some embodiments of the present disclosure. As illustrated in FIG. 1, the computer 100 includes a memory 110, a processor 130, and several communication interfaces 150. The computer 100 may be connected to the device 900A, 900B through connection 170 and the communication interfaces 150. In some embodiments, the connection 170 may be wire connection or wireless connection. In some embodiments, the device 900A and the device 900B may be smartphones, music players, mouse, keyboards, speakers, or any other devices with similar functions. The computer 100 shown in FIG. 1 is for illustrative purposes only and the present disclosure is not limited thereto.

In some embodiments, the memory 110 includes an application. The application is configured to handle the device 900 which is connected to the computer 100 by BLUETOOTH connection 170. The processor 130 is configured to run the application to determine whether the computer 100 is an accessory or a host for the device 900A or the device 900B when the device 900A or the device 900B is connected to the computer 100 by BLUETOOTH connection 170.

In some embodiments, for example, if the processor 130 determines the computer 100 to run as the accessory and the device 900A to run as the host when the device 900A is connected to the computer 100 by BLUETOOTH connection 170, the processor 130 operates the computer 100 as the accessory for the device 900A by the application. In some embodiments, if the processor 130 determines the computer 100 to run as the host and the device 900A to run as the accessory when the device 900A is connected to the computer 100 by BLUETOOTH connection 170, the processor 130 operates the computer 100 as the host for the device 900A by the Microsoft BLUETOOTH stack. When the device 900A works as the host, the computer 100 and the device 900B all become peripheral devices (accessories) of the device 900A.

Furthermore, in the present disclosure, the computer 100 may operate as the host and the accessory at the same time. For example, the device 900A and the device 900B may connect to the computer 100 by the BLUETOOTH connection 170 at the same time. The device 900A is the accessory and the computer 100 is the master; meanwhile, the device 900B is the host and the computer 100 is the slave. The computer 100 operates as the host for the device 900A by the Microsoft BLUETOOTH stack. The computer 100 operates as the accessory for the device 900B by the application.

Reference is made to FIG. 2. FIG. 2 is a schematic diagram illustrating a driver system 200 according to some embodiments of the present disclosure. For convenience of explanation and understanding, reference is made to both FIG. 1 and FIG. 2.

As illustrated in FIG. 2, the application 230 runs in the user space of the computer 100. The application 230 includes a BLUETOOTH event arbiter module 234 and a communication link module 232. A filter driver 210 is implemented in the kernel space of the computer 100 by the processor 130. A Microsoft BLUETOOTH stack 250 is implemented in the kernel space of the computer 100.

When the device 900A is connected to the computer 100 through the BLUETOOTH connection 170 (as illustrated in FIG. 1), the application 230 determines whether the computer 100 is a host or an accessory for the device 900A. If the computer 100 is determined to operate as a host for the device 900A, the computer 100 operates as the host for the device 900A through the Microsoft BLUETOOTH stack 250. The information transmits between the Microsoft BLUETOOTH stack 250 and the device 900A may be intercepted by the filter driver 210. The filter driver 210 sends the information intercepted to the application 230. The application 230 then sends the information intercepted to the device 900A through the filter driver 210 and the driver 270.

On the other hand, if the computer 100 is determined to operate as an accessory for the device 900A, the computer 100 operates as the accessory for the device 900A through a customized BLUETOOTH stack. The customized BLUETOOTH stack is implemented by the application 230 at the communication link module 232, which may make the computer 100 work as the accessory for the device 900A. The information transmits between the customized BLUETOOTH stack and the device 900A may be transmitted through the filter driver 210.

If the computer 100 works as a host and an accessory at the same time when connected to several devices 900A and 900B, the BLUETOOTH event arbiter module 234 may handle the conflict between the Microsoft BLUETOOTH stack 250 and the customized BLUETOOTH stack. Methods of handling the conflict between the Microsoft BLUETOOTH stack 250 and the customized BLUETOOTH stack includes sequencing the information and/or the packets transmitting from the Microsoft BLUETOOTH stack 250 and the customized BLUETOOTH stack. However, the present disclosure is not limited to the method mentioning above.

In some embodiments, when the device 900A or the device 900B is not connected to the computer 100, the processor 130 detaches the device 900A or the device 900B from the computer 100 by the application 230.

Reference is made to FIG. 3. FIG. 3 is a schematic diagram illustrating a driver system 300 according to some embodiments of the present disclosure. For convenience of explanation and understanding, reference is made to both FIG. 1 and FIG. 3.

As illustrated in FIG. 3, a filter driver 310 is implemented in the kernel space of the computer 100 by the processor 130. The application 330 runs in the filter driver 310. The application 330 includes a BLUETOOTH event arbiter module 334 and a communication link module 332. A Microsoft BLUETOOTH stack 250 is implemented in the kernel space of the computer 100.

When the device 900A is connected to the computer 100 through the BLUETOOTH connection 170 (as illustrated in FIG. 1), the application 330 determines whether the computer 100 is a host or an accessory for the device 900A. If the computer 100 is determined to operate as a host for the device 900A, the computer 100 operates as a host for the device 900A through the Microsoft BLUETOOTH stack 250. The information transmits between the Microsoft BLUETOOTH stack 250 and the device 900A may be intercepted by the filter driver 310. The filter driver 310 sends the information intercepted to the application 330. The application 330 then sends the information intercepted to the device 900A through the filter driver 310 and the driver 270.

On the other hand, if the computer 100 is determined to operate as an accessory for the device 900A, the computer 100 operates as an accessory for the device 900A through a customized BLUETOOTH stack. The customized BLUETOOTH stack is implemented by the application 330 at the communication link module 332, which may make the computer 100 work as the accessory for the device 900A.

If the computer 100 works as a host and an accessory at the same time when connected to several devices 900A and 900B, the BLUETOOTH event arbiter module 334 may handle the conflict between the Microsoft BLUETOOTH stack 250 and the customized BLUETOOTH stack. Methods of handling the conflict between the Microsoft BLUETOOTH stack 250 and the customized BLUETOOTH stack includes sequencing the information and/or the packets transmitting from the Microsoft BLUETOOTH stack 250 and the customized BLUETOOTH stack. However, the present disclosure is not limited to the method mentioning above.

In some embodiments, when the device 900A or the device 900B is not connected to the computer 100, the processor 130 detaches the device 900A or the device 900B from the computer 100 by the application 330.

It is to be noted that in some embodiments, the device 900A and the device 900B may be driven by the same driver 270. In some other embodiments, the device 900A and the device 900B may be driven by different driver 270.

Reference is made to FIG. 4. FIG. 4 is a schematic diagram illustrating a driver system 400 according to some embodiments of the present disclosure. For convenience of explanation and understanding, reference is made to both FIG. 1 and FIG. 4.

As illustrated in FIG. 4, the application 430 runs in the user space of the computer 100. The application 430 includes a BLUETOOTH event arbiter module 434 and a communication link module 432. A filter driver 410 is implemented in the kernel space of the computer 100 by the processor 130. A Microsoft BLUETOOTH stack 250 is implemented in the kernel space of the computer 100 by the processor 130.

When the device 900A is connected to the computer 100 through the BLUETOOTH connection 170 (as illustrated in FIG. 1), the application 430 determines whether the computer 100 is a host or an accessory for the device 900A. If the computer 100 is determined to operate as a host for the device 900A, the computer 100 operates as the host for the device 900A through the Microsoft BLUETOOTH stack 250. The information transmits between the Microsoft BLUETOOTH stack 250 and the device 900A may be intercepted by the filter driver 410, and the filter driver 410 sends the information intercepted to the application 430. For example, the filter driver 410 intercepts the BLUETOOTH events from the Microsoft BLUETOOTH stack 250 and forwards the BLUETOOTH events to the BLUETOOTH event arbiter module 434. The information intercepted by the filter driver 410 comprises isochronous packets. That is, the filter driver 410 may focus on the data of USB isochronous packets.

On the other hand, if the computer 100 is determined to operate as an accessory for the device 900A, the computer 100 operates as the accessory for the device 900A through a customized BLUETOOTH stack. The customized BLUETOOTH stack is implemented by the application 430 at the communication link module 432, which may make the computer 100 work as the accessory for the device 900A.

The processor 130 (as illustrated in FIG. 1) is further configured to implement a USB emulated device (UDE) 420 in the kernel space, as illustrated in FIG. 4. USB stands for Universal Serial Bus. The USB emulated device 420 supports in the Windows operating system, for developing an emulated Universal Serial Bus (USB) host controller driver and a connected virtual USB device.

In some embodiments, the USB emulated device 420 is configured to emulate a BLUETOOTH adapter 422 and a BLUETOOTH driver 424. The USB emulated device 420 is a virtual software device configured to run the Microsoft BLUETOOTH stack 250. Moreover, the USB emulated device 420 forwards the USB traffic to the application 430. The USB traffic includes bulk packets, interrupt packets, and control packets. In some embodiments, the information is sent between the filter driver 410 and the USB emulated device 420 through the driver 270.

The processor 130 (as illustrated in FIG. 1) is further configured to implement a USBDK driver (USB development kit driver) 460. The USBDK driver 460 is configured to make the device 900A or 900B be accessed by the application 430 only. The USBDK driver 460 is a modified driver of an open source project. It is used by application 430 to hide the physical BLUETOOTH adapter (e.g. device 900A or 900B) from Windows operating system (OS) or Microsoft system, so that Windows OS may only see the USB emulated device 420 to load the Microsoft BLUETOOTH stack 250. That is, only the application 430 may access the physical BLUETOOTH adapter (e.g. device 900A or 900B).

If the computer 100 works as a host and an accessory at the same time when connected to several devices 900A and 900B, the BLUETOOTH event arbiter module 434 may handle the conflict between the Microsoft BLUETOOTH stack 250 and the customized BLUETOOTH stack.

The Microsoft BLUETOOTH stack 250 (as illustrated in FIG. 2 to FIG. 4) includes a BLUETOOTH USB 252, a BLUETOOTH Port 254, a BLUETOOTH low energy ENUM 256, and a BLUETOOTH ENUM 258. The BLUETOOTH USB 252 is a miniport that abstracts the bus interface from the BLUETOOTH Port 254. The BLUETOOTH Port 254 is a mini-driver that is loaded by the BLUETOOTH USB 252. The BLUETOOTH Port 254 includes four components: the HCl component, the SCO component, the L2CAP and the SDP. The HCl component communicates to the local Bluetooth-enabled radio through the Host Controller Interface (HCl) defined in the Bluetooth specification. The SCO component implements the Synchronous Connection-Oriented (SCO) protocol. This protocol supports creating point-to-point connections to a remote device. L2CAP implements the Bluetooth logical link control and adaptation protocol. This protocol supports creating a lossless channel to a remote device. SDP implements the Bluetooth Service Discovery Protocol.

Reference is made to FIG. 5. FIG. 5 is a flow chart illustrating a wireless connecting method 500 according to some embodiments of the present disclosure. The wireless connecting method 500 includes operations S510-S570.

For convenience of explanation and understanding reference is made to FIG. 1 and FIG. 5.

In operation S510, connecting a device to a computer by BLUETOOTH. In some embodiments, operation S510 may be performed by the processor 130, as illustrated in FIG. 1. For example, the processor 130 may connect the device 900A or 900B to the connection interface 150 of the computer 100 through BLUETOOTH connection 170.

In operation S530, determining whether the computer is a host or an accessory for the device. In some embodiments, operation S530 may be performed by the processor 130, as illustrated in FIG. 1. For example, the processor 130 may determine the computer 100 as an accessory or a host for the device 900A or 900B.

Reference is made to FIG. 1 to FIG. 5. In some other embodiments, operation S530 may be performed by the application 230, 330, or 430. In some embodiments, when the device 900A or the device 900B is connected to the computer 100, a descriptor information corresponding to the device 900A or 900B is sent to the application 230, 330, or 430. In some embodiments, the operation S530 is performed according to the descriptor. That is, in some embodiments, the computer 100 is classified as an accessory or a host for the device 900A or 900B according to the descriptor.

As illustrated in FIG. 5, if it is determined that the computer 100 is an accessory for the device 900A or 900B, operation S550 is performed. If it is determined that the computer 100 is a host for the device 900A or 900B, operation S570 is performed.

In operation S550, operating the computer as the accessory for the device by an application. Reference is made to FIG. 2 to FIG. 4, for example, when the device 900A is connected to the computer 100, the application 230, 330, or 430 may operate the computer 100 as the accessory for the device 900A. In some embodiments, the application 230, 330, or 430 may implement a customized BLUETOOTH stack at the communication link module 232, 332, or 432 to communicate with the device 900A, so as to operate the computer 100 as the accessory for the device 900A.

In operation S570, operating the computer as the host for the device by a Microsoft BLUETOOTH stack. Reference is made to FIG. 2 to FIG. 4, for example, when the device 900A is connected to the computer 100, the Microsoft BLUETOOTH stack 250 may communicate with the device 900A, so as to operate the computer 100 as the host for the device 900A. The filter driver 210, 310, or 410 intercepts the information between the Microsoft BLUETOOTH stack 250 and the device 900A, and the filter driver 210, 310, or 410 sends the information intercepted to the application 230, 330, or 430. The application 230, 330, or 430 then sends the information to the device 900A or the Microsoft BLUETOOTH stack 250.

Reference is made to FIG. 2 to FIG. 5. In some embodiments, if the computer 100 works as a host and an accessory at the same time when connected to several devices 900A and 900B, the BLUETOOTH event arbiter module 234, 334, or 434 may handle the conflict between the Microsoft BLUETOOTH stack 250 and the customized BLUETOOTH stack.

Another embodiment of the disclosure is a non-transitory computer-readable storage medium. The non-transitory computer readable storage medium stores instructions for performing the method 500 in aforesaid embodiment shown in FIG. 5.

The kernel space is strictly reserved for running a privileged operating system kernel, kernel extensions, and most device drivers. The user space is the memory area where application software and some drivers execute. The concept of the kernel space and the user space are known to one of ordinary skill in the art, and may not be addressed in details.

According to the embodiment of the present disclosure, it is understood that the embodiment of the present disclosure is to provide a wireless connecting method, a computer, and a non-transitory computer-readable storage medium, in order to operate the computer as the accessory and the host at the same time when the computer is connecting to devices by BLUETOOTH. Furthermore, the implemented application that makes the computer work as an accessory for the connected device may co-exist with the Microsoft BLUETOOTH stack.

In this document, the term “coupled” may also be termed as “electrically coupled”, and the term “connected” may be termed as “electrically connected”. “Coupled” and “connected” may also be used to indicate that two or more elements cooperate or interact with each other. It will be understood that, although the terms “first,” “second,” etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.

In addition, the above illustrations comprise sequential demonstration operations, but the operations need not be performed in the order shown. The execution of the operations in a different order is within the scope of this disclosure. In the spirit and scope of the embodiments of the present disclosure, the operations may be increased, substituted, changed and/or omitted as the case may be.

The foregoing outlines features of several embodiments so that those skilled in the art may better understand the aspects of the present disclosure. Those skilled in the art should appreciate that they may readily use the present disclosure as a basis for designing or modifying other processes and structures for carrying out the same purposes and/or achieving the same advantages of the embodiments introduced herein. Those skilled in the art should also realize that such equivalent constructions do not depart from the spirit and scope of the present disclosure, and that they may make various changes, substitutions, and alterations herein without departing from the spirit and scope of the present disclosure.

Claims

1. A wireless connecting method, comprising: connecting a device to a computer by BLUETOOTH;determining the computer is an accessory or a host for the device;operating the computer as the host for the device by a Microsoft BLUETOOTH stack if the computer is the host for the device; andoperating the computer as the accessory for the device by an application if the computer is the accessory for the device;wherein the computer is operated as the accessory and the host at the same time.

2. The wireless connecting method of claim 1, further comprising: intercepting information between the Microsoft BLUETOOTH stack and the device by a filter driver; andsending the information intercepted by the filter driver to the application.

3. The wireless connecting method of claim 2, wherein the filter driver is implemented in a kernel space and the application runs in a user space.

4. The wireless connecting method of claim 2, wherein the filter driver is implemented in a kernel space and the application runs in the filter driver.

5. The wireless connecting method of claim 1, further comprising: implementing a customized BLUETOOTH stack by the application for the computer to operate as the accessory for the device.

6. The wireless connecting method of claim 5, further comprising: handling a plurality of conflict between the Microsoft BLUETOOTH stack and the customized BLUETOOTH stack by the application when the computer is operated as the host and the accessory at the same time.

7. The wireless connecting method of claim 1, further comprising: implementing a USB emulated device (UDE) in the kernel space;wherein the USB emulated device is configured to emulate a BLUETOOTH adapter, to run the Microsoft BLUETOOTH stack, and to forward USB traffic to the application.

8. The wireless connecting method of claim 1, further comprising: implementing a USBDK driver (USB development kit driver);wherein the USBDK driver is configured to make the device be accessed by the application only.

9. The wireless connecting method of claim 1, wherein connecting the device to the computer comprises: sending a descriptor information corresponding to the device to the application for the application to determine whether the computer is the accessory or the host for the device.

10. A computer, comprising: a memory, wherein the memory comprises an application to handle a device connected to the computer by BLUETOOTH; anda processor configured to run the application to determine whether the computer is a accessory or a host for the device;wherein the processor operates the computer as the host for the device by a Microsoft BLUETOOTH stack if the computer is the host for the device, and the processor operates the computer as the accessory for the device by an application if the computer is the accessory for the device;wherein the computer is operated as the host and the accessory at the same time.

11. The computer of claim 10, wherein the processor is further configured to implement a filter driver, and the filter driver is configured to intercept information between the Microsoft BLUETOOTH stack and the device and to send the information intercepted by the filter driver to the application.

12. The computer of claim 11, wherein the filter driver is implemented in a kernel space and the application runs in a user space.

13. The computer of claim 11, wherein the filter driver is implemented in a kernel space and the application runs in the filter driver.

14. The computer of claim 10, wherein the application comprises a communication link module, wherein the processor is further configured to implement a customized BLUETOOTH stack at the communication link module for the computer to operate as the accessory for the device.

15. The computer of claim 10, wherein the application further comprises a BLUETOOTH event arbiter module, and the BLUETOOTH event arbiter module is configured to handle a plurality of conflict between the Microsoft BLUETOOTH stack and the customized BLUETOOTH stack by the BLUETOOTH event arbiter module when the computer is operated as the host and the accessory at the same time.

16. The computer of claim 11, wherein the processor is further configured to implement a USB emulated device (UDE) in the kernel space, and the USB emulated device is configured to emulate a BLUETOOTH adapter, to run the Microsoft BLUETOOTH stack, and to forward USB traffic to the application.

17. The computer of claim 12, wherein the information intercepted by the filter driver comprises isochronous packets.

18. The computer of claim 11, wherein the processor is further configured to implement a USBDK driver (USB development kit driver), and the USBDK driver is configured to make the device be accessed by the application only.

19. A non-transitory computer-readable storage medium storing a computer program performing a wireless connecting method, wherein the wireless connecting method comprises: connecting a device to a computer by BLUETOOTH;determining the computer is a host or an accessory for the device;operating the computer as the host for the device by a Microsoft BLUETOOTH stack if the computer is the host for the device; andoperating the computer as the accessory for the device by an application according to the program code if the computer is the accessory for the device;wherein the computer is operated as the host and the accessory at the same time.

20. The non-transitory computer-readable storage medium of claim 19, wherein the wireless connecting method further comprises: intercepting information between the Microsoft BLUETOOTH stack and the device by a filter driver; andsending the information intercepted by the filter driver to the application.