Patent Application
20200008040
The present disclosure relates to a method and an apparatus for transmitting data of a predetermined capacity or over to a data device using Bluetooth low energy (BLE).
Specifically, the present disclosure relates to a method and an apparatus for transmitting and receiving data in a Bluetooth classic (BT classic: existing Bluetooth) mode by transmitting a media access control (MAC) address to a data device in a BT classic mode of a terminal through a connection in a BLE mode and then by enabling the data device to make a forced connection with the terminal in the BT classic mode through the MAC address of the terminal.
Bluetooth uses IEEE 802.15.1 standards that correspond to industrial standards for personal area networks (PANs) in wireless communication, and it enables various devices to communicate with one another using radio frequencies that can be safely used at low costs throughout the world.
Bluetooth uses 2.45 GHz that is an ISM band, and it has been developed through addition of new functions, such as Version 1.1, 1.2, 2.0+EDR (Enhanced Data Rate), 2.1+EDR, 3.0+HS (High Speed), 4.0, and 4.1. Starting from Bluetooth 4.0, a new protocol stack of Bluetooth low energy (BLE) has been proposed.
A chip that supports only BLE is called a single mode, and it supports only unidirectional transmission. As described above, a product mounted with BLE is called Bluetooth smart. A chip with BT classic is called a dual mode, and it supports bidirectional transmission. A product mounted with BT classic is called Bluetooth smart ready.
In accordance with iOS operating system iAP (iPod Accessory Protocol) rules of Apple Inc., an operation protocol of a peripheral device connected to a device using the iOS operating system is determined. In accordance with the iAP protocol, BLE can have device access, such as connection and disconnection, even on an application installed in a smart phone. However, BLE is unable to have a communication speed that is equal to or higher than a predetermined speed, and thus it has disadvantages that it is not easy to transmit data of a predetermined capacity or over. In contrast, according to the iAP protocol, in the BT classic mode in the iOS, an application installed in a smart phone is unable to have access with respect to a control, such as connection and disconnection, caused by the OS (Operating System) design in consideration of security, but it is able to have access only for system setting. However, because the BT classic has a higher communication speed than the communication speed of BLE, it has advantages that it is easy to perform data transmission of the predetermined capacity or over.
In order for a smart phone using the iOS to quickly transmit data of the predetermined capacity or over through Bluetooth communication, BT classic mode connection is necessary. However, if an iOS user is unable to control a connection with a data device, transmission and reception of necessary data, and quick disconnection through an application, but is able to control a connection and a disconnection in the BT classic mode between the smart phone using the iOS and the data device through one-by-one system setting, it may cause great inconvenience in use.
Accordingly, there is a need for development of a technology capable of controlling a connection and a disconnection in the BT classic mode in order for the application installed in the smart phone to transmit and receive data of a predetermined capacity or over through Bluetooth communication with the data device in spite of the OS design limits in the smart phone using the iOS.
An aspect of the present disclosure is to provide a terminal and a data device supporting both BLE and BT classic, which can perform Bluetooth transmission and reception of data of a predetermined capacity or over that is not easily transmitted through a BLE connection from the terminal to the data device through an iOS application capable of controlling only the BLE connection of the terminal.
Another aspect of the present disclosure is for an iOS application to control a BT classic connection between a terminal and a data device as a result of forcing the data device to make the BT classic connection with the terminal through the BLE connection through the iOS application capable of controlling only the BLE connection of the terminal.
In accordance with an aspect of the present disclosure, a method by a terminal supporting Bluetooth connection of a first profile and a second profile for performing communication with a data device includes transmitting a media access control (MAC) address of the terminal to the data device having established a first connection in the first profile with the terminal; disconnecting the first connection; receiving, from the data device, a request for a second connection in the second profile through the MAC address of the terminal; identifying the data device using pre-registered first information; and establishing the second connection without transmission of an acknowledgment for the second connection.
Preferably, the first profile may be Bluetooth low energy that does not support transmission and reception of data at a predetermined speed or over, and the second profile may be classic Bluetooth that supports the transmission and the reception of the data at the predetermined speed or over.
The method may further include performing the transmission and reception of the data with the data device after establishing the second connection.
The method may further include searching for the data device in the first profile before transmitting the MAC address of the terminal to the data device; transmitting a request for the first connection in the first profile to the data device; and receiving an acknowledgment for the first connection from the data device.
The terminal may be configured to transmit a request or an acknowledgment for a connection between the terminal and the data device only in the first profile through an application stored in a memory of the terminal.
The method may further include searching for the data device in the second profile through setting of an operating system (OS) installed in the terminal before searching for the data device in the first profile; and registering the first information on the data device in the second profile.
In accordance with another aspect of the present disclosure, a method by a data device supporting Bluetooth connection of a first profile and a second profile for performing data communication with a terminal includes receiving a media access control (MAC) address of the terminal from the terminal having established a first connection of the first profile with the data device; disconnecting the first connection; and transmitting a request for a second connection of the second profile to the terminal through the MAC address of the terminal.
Preferably, the first profile may be Bluetooth low energy that does not support transmission and reception of data at a predetermined speed or over, and the second profile may be classic Bluetooth that supports the transmission and the reception of the data at the predetermined speed or over.
The method may further include performing the transmission and reception of the data with the terminal without reception of an acknowledgment for the second connection after transmitting the request for the second connection; and disconnecting the second connection after completing the transmission and reception of the data.
The method may further include receiving a request for the first connection in the first profile from the terminal before receiving the MAC address of the terminal; and transmitting an acknowledgment for the first connection to the terminal.
The method may further include switching the first profile and the second profile at predetermined intervals and waiting before receiving the request for the first connection.
The request for the first connection in the first profile received from the terminal may be received while the data device switches to the first profile and waits.
In accordance with still another aspect of the present disclosure, a data device supporting Bluetooth connection of a first profile and a second profile and performing communication with a terminal includes a transceiver module; and a processor, wherein the processor is configured to control the transceiver module to receive a media access control (MAC) address of the terminal from the terminal having established a first connection of the first profile with the data device, to disconnect the first connection, and to transmit a request for a second connection of the second profile to the terminal through the MAC address of the terminal.
Preferably, the first profile may be Bluetooth low energy that does not support transmission and reception of data at a predetermined speed or over, and the second profile may be classic Bluetooth that supports the transmission and the reception of the data at the predetermined speed or over.
The processor may be further configured to control the transceiver module to perform the transmission and reception of the data with the terminal without reception of an acknowledgment for the second connection after transmitting the request for the second connection, and to disconnect the second connection after completing the transmission and reception of the data.
The data device may further include a memory, wherein the processor may be further configured to control the transceiver module to perform the transmission and reception of the data with the terminal without reception of an acknowledgment for the second connection after transmitting the request for the second connection, and to disconnect the second connection after completing the transmission and reception of the data, and the processor may be further configured to control the memory to store the data therein.
The processor may be further configured to control the transceiver module to switch the first profile and the second profile at predetermined intervals and wait before receiving the request for the first connection.
The request for the first connection in the second profile received from the terminal may be received while the processor controls the transceiver module to switch to the second profile and wait.
In accordance with still another aspect of the present disclosure, an application performs a method according to any one of claims 1 to 4, and it is stored in a memory of a terminal.
In accordance with still another aspect of the present disclosure, a terminal supporting Bluetooth connection of a first profile and a second profile and performing communication with a data device includes a transceiver module; a memory configured to store an application therein; and a processor, wherein the processor is configured to execute the application stored in the memory, and to perform a method according to any one of claims 1 to 4 by controlling the transceiver module and the memory.
According to an embodiment of the present disclosure, the terminal and the data device supporting both BLE and BT classic can perform the Bluetooth transmission and reception of data of a predetermined capacity or over that is not easily transmitted through the BLE connection from the terminal to the data device through the iOS application capable of controlling only the BLE connection of the terminal.
Further, according to an embodiment of the present disclosure, the iOS application can control the BT classic connection between the terminal and the data device as the result of forcing the data device to make the BT classic connection with the terminal through the BLE connection through the iOS application capable of controlling only the BLE connection of the terminal.
Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those of ordinary skill in the art can easily embody the technical idea of the present disclosure. The present disclosure can be implemented in various different forms, and thus it is not limited to the embodiments described herein.
The present disclosure is for the purpose of a connection between a terminal 100 and a data device 200 in a BT classic mode through execution of an application rather than system setting.
The terminal 100 and the data device 200 may support a Bluetooth profile of Bluetooth low energy (BLE) or Bluetooth classic (BT classic).
The iOS operating system of Apple Inc. does not permit Bluetooth connection control in BT classic mode through execution of an application in accordance with the iAP protocol. The iOS operating system permits Bluetooth connection control in BLE mode through execution of the application. However, the communication speed of the BLE mode is considerably lower than the communication speed of the BT classic mode, and thus the BLE mode has the limitations that it is not easy to perform data transmission over a predetermined capacity. Accordingly, in order for a user to smoothly perform data transmission over a predetermined capacity to the extent that the user does not feel any inconvenience, the BT classic mode connection is necessary.
However, other operating systems including Android of other companies including Google excluding the iOS operating system of Apple Inc. do not have such limitations.
Accordingly, in the case where the terminal 100 intends to smoothly perform data communication with the data device 200 over a predetermined capacity, it may initially attempt to connect to the data device 200 in the BT classic mode.
With reference to
If the data device 200 is initially registered in the BT classic mode, it is not required to register the data device 200 again during the BT classic mode connection in the subsequent procedure. Further, if a connection request is received from the data device 200 in the BT classic mode through the information of the registered data device 200, the terminal 100 can directly identify the data device 200.
After the terminal 100 performs registration of the data device 200 in the BT classic mode, the data device 200 performs switching (S120) of Bluetooth (BT) module mode of the BT classic mode and the BLE mode at predetermined intervals, and it waits for the connection of the terminal 100 in each mode (S130). Further, although not illustrated, the data device 200 may initially wait for the connection of the terminal 100 in the BLE mode.
The terminal 100 starts the Bluetooth connection control through the application by executing the application (S140).
Procedures after operation 5140 will be described later with reference to
A procedure that is performed through execution of the application is as follows.
The terminal 100 transmits a request for a first connection to the data device 200 in the BLE mode (S210), and it receives an acknowledgment for the first connection in the BLE mode from the data device 200 (S220).
The terminal 100 transmits a MAC address of the terminal 100 to the data device 200 (S300). The MAC address is data having a size of a predetermined capacity or less capable of being smoothly transmitted to the extent that the user does not feel any inconvenience.
The terminal 100 terminates the first connection after transmitting the MAC address (S400). The iOS operating system permits the BLE mode connection control for the application, and thus the terminal 100 itself can terminate the first connection through the application.
That is, the first connection is a connection of the BLE mode that can be controlled by the application, and thus operations 5200 to 5400 may be performed under the control of the application installed in the terminal 100.
After terminating the first connection (S400), the terminal 100 may receive a request for a second connection in the BT classic mode from the data device 200 through the transmitted MAC address (S500).
Because the terminal 100 has registered information of the data device 200 in advance (S110), it may establish the second connection with the data device without any additional procedure, such as an acknowledgment for the second connection in the BT classic mode based on the registered information (S520).
Because the second connection has been established in the BT classic mode, the terminal 100 may transmit and receive data of a predetermined capacity or over with the data device 200 (S600).
Because the iOS operating system does not permit a control for disconnection of the BT classic mode connection of the application, the terminal 100 is unable to control the termination of the second connection through execution of the application. Accordingly, after the data transmission and reception is completed, the termination of the second connection is performed by the data device (S700).
A procedure that is performed through execution of the application is as follows.
The terminal 100 searches for the data device 200 in the BT classic mode (S800). The terminal 100 transmits a request for a third connection in the BT classic mode to the searched data device 200 (S810), and it receives an acknowledgment for the third connection in the BT classic mode from the data device 200 (S820).
Because the connection in the BT classic mode with the data device 200 has been established, the terminal 100 may directly transmit and receive data of a predetermined size or over with the data device 200.
The other operating system has no limits in controlling the disconnection of the BT classic mode connection of the application. Accordingly, the terminal 100 may control the termination of the third connection through execution of the application. After the data transmission and reception is completed (S900), the termination 100 disconnects the third connection (S1000).
Because the third connection is a connection of the BT classic mode that can be controlled by the application in the other operating system, operations S800 to S1000 may be performed under the control of the application installed in the terminal 100.
The terminal 100 includes a transceiver module 110, a memory 120, and a processor 130. The transceiver module 110 is connected to the processor 130 to transmit and/or receive a radio signal. The memory 120 stores therein applications and/or data. The processor 130 may be configured to implement procedures and/or methods proposed in the present disclosure through execution of the application stored in the memory 120.
The data device 200 includes a transceiver module 210, a memory 220, and a processor 230. The transceiver module 210 is connected to the processor 230 to transmit and/or receive a radio signal. The memory 220 is connected to the processor 230, and it stores therein various pieces of information related to an operation of the processor 230. The processor 230 may be configured to implement procedures and/or methods proposed in the present disclosure.
Although
The processors 130 and 230 of each of the terminal 100 and the data device 200 instruct (e.g., control, adjust, and manage) the operations of the terminal 100 and the data device 200. The respective processors 130 and 230 may be connected to the memories 120 and 220 storing program codes and data. The memories 120 and 220 are connected to the processors 130 and 230, respectively, to store operating systems, applications, and general files.
The processors 130 and 230 according to the present disclosure may be called controllers, microcontrollers, microprocessors, or microcomputers. On the other hand, the processors 130 and 230 may be implemented by hardware or firmware, software, or a combination thereof.
In the case of implementing embodiments of the present disclosure using hardware, application specific integrated circuits (ASICs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), and field programmable gate arrays (FPGAs), which are configured to perform the present disclosure, may be provided in the processors 130 and 230.
According to the above-described embodiments, constituent elements and features of the present disclosure are combined in a specific form. Unless explicitly mentioned, the respective constituent elements and the features should be considered as being selective. The respective constituent elements or the features may be embodied in the form in which they are not combined with other constituent elements and/or features. Further, some constituent elements and/or features may be combined with each other to configure an embodiment of the present disclosure. The order of operations explained in embodiments of the present disclosure may be changed. Partial configurations or features of any one embodiment may be included in another embodiment, or they may be replaced by configurations or features corresponding to another embodiment. It is apparent that an embodiment may be configured by combining claims that are not in an explicitly cited relationship or a new claim may be included by amendment after application.
Embodiments of the present disclosure may be implemented by various means for hardware, firmware, software, or a combination thereof. In the case where embodiments of the present disclosure are implemented by hardware, they may be implemented by at least one application specific integrated circuit (ASIC), digital signal processor (DSP), digital signal processing device (DSPD), programmable logic device (PLD), field programmable gate array (FPGA), processor, controller, microcontroller, or microprocessor.
In the case where embodiments of the present disclosure are implemented by firmware or software, they may be implemented by modules performing functions or operations, procedures, or functions. Software codes may be stored in a memory unit, and then they may be driven by a processor. The memory unit may be located inside or outside the processor to receive data from the processor through the various known means.
It will be apparent to those of ordinary skill in the art to which the present disclosure pertains that the present disclosure can be embodied in different forms without departing from the technical idea and essential features of the present disclosure. Accordingly, the above-described embodiments are not limited, but they should be considered in all exemplary aspects. The scope of the present disclosure should be determined by reasonable interpretations of the appended claims and all possible changes within the equivalent range of the present disclosure.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2017-0039034 | Mar 2017 | KR | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2018/003550 | 3/26/2018 | WO | 00 |
