CN111132098B - Communicator, central communication device and Bluetooth communication system - Google Patents
Communicator, central communication device and Bluetooth communication system Download PDFInfo
- Publication number
- CN111132098B CN111132098B CN201811283433.7A CN201811283433A CN111132098B CN 111132098 B CN111132098 B CN 111132098B CN 201811283433 A CN201811283433 A CN 201811283433A CN 111132098 B CN111132098 B CN 111132098B
- Authority
- CN
- China
- Prior art keywords
- communication device
- sdp
- communicator
- terminal communication
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000004891 communication Methods 0.000 title claims abstract description 187
- 238000000034 method Methods 0.000 description 11
- 230000005540 biological transmission Effects 0.000 description 5
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/14—Direct-mode setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A communicator, a central communication device and a Bluetooth communication system capable of reducing connection collision between Bluetooth devices. The communication device of the present invention is provided in a central communication device, and is capable of bluetooth communication with a terminal communication device, and is characterized in that the communication device receives a first SDP request based on a service discovery protocol SDP from the terminal communication device and transmits a first SDP response corresponding to the first SDP request to the terminal communication device in a state in which pairing with the terminal communication device is completed and an asynchronous link is connected, and when the central communication device supports a service related to the first SDP request, the communication device waits for a predetermined period after transmitting the first SDP response to the terminal communication device, and then determines whether to transmit a connection request for the service to the terminal communication device.
Description
Technical Field
The present invention relates to a communicator capable of bluetooth communication, a central communication device incorporating the communicator, and a bluetooth communication system including the central communication device and a terminal communication device.
Background
In recent years, bluetooth has been used as a wireless communication standard for short-range data exchange technologyCommunication is widely used in the fields of computers, mobile internet, vehicle-mounted devices and the like. Devices having a bluetooth communication function (hereinafter referred to as "bluetooth devices") can utilize various services based on bluetooth communication, for example, a service of connecting a host computer to an input device such as a mouse or a keyboard, a service of connecting a smart phone to an in-vehicle device, and the like.
When a connection of a certain service is established between two bluetooth devices, a connection failure may occur based on the physical state of the respective channels, the timing of the interconnection between the two bluetooth devices, and the like. Regarding the timing of the interconnection, in the process of establishing a connection of a certain service between two bluetooth devices, if both bluetooth devices simultaneously send a connection request, there may be a case where the two bluetooth devices wait for the response of each other at the same time, and finally, the connection fails. "simultaneously" here refers to a case where the interval between the respective bluetooth devices issuing connection requests is small to some extent (for example, less than 50 milliseconds).
In other words, when a connection request from a counterpart is received immediately after both bluetooth devices simultaneously transmit the connection request, since both bluetooth devices are in a state of waiting for the counterpart to answer at this time, the received connection request from the counterpart is put aside temporarily, and as a result, both bluetooth devices are in a state of failing to send an answer to the counterpart and waiting for the counterpart to answer. Such a state in which connection requests of both sides collide is also referred to as a deadlock (dead lock) state. Then, after the dead lock state is continued for a certain period of time (for example, more than 1 second), the two bluetooth devices may respectively obtain the connection failure result.
The above connection failure occurs even when the physical channels of the two bluetooth devices are sufficient, and when the connection failure occurs, the user needs to wait for a certain time, and may need to connect again automatically or manually, which complicates the operation and makes the user experience poor.
Disclosure of Invention
The present invention has been made in view of the above circumstances, and an object thereof is to provide a communicator, a center communication device, and a bluetooth communication system capable of reducing occurrence of connection collision between bluetooth devices.
A communicator according to claim 1 of the present invention is a communicator provided in a central communication device and capable of bluetooth communication with a terminal communication device, wherein the communicator receives a first SDP request based on a service discovery protocol SDP (Service Discovery Protocol) from the terminal communication device and transmits a first SDP response corresponding to the first SDP request to the terminal communication device in a state in which pairing with the terminal communication device is completed and an asynchronous link is connected, and when the central communication device supports a service related to the first SDP request, the communicator waits for a predetermined period after transmitting the first SDP response to the terminal communication device, and then determines whether to transmit a connection request for the service to the terminal communication device.
According to the above-described communicator, by waiting the central communicator side (in-vehicle device side) for a predetermined period, the possibility that both the central communicator side (in-vehicle device side) and the terminal communicator side (smart phone side) simultaneously request connection for any one of the plurality of bluetooth services becomes low, and deadlock on the control plane which may occur when the terminal communicator side automatically connects after SDP is avoided, thereby suppressing connection failure between bluetooth devices.
A communicator according to claim 2 of the present invention is the communicator according to the third aspect of the present invention, wherein the communicator does not transmit the connection request of the service to the terminal communication device when the communicator receives the connection request of the service from the terminal communication device in the predetermined period, and the communicator transmits the connection request of the service to the terminal communication device when the communicator does not receive the connection request of the service from the terminal communication device in the predetermined period.
According to the communicator, the communicator transmits the connection request of the service to the terminal communication device only when the communicator does not receive the connection request of the service from the terminal communication device, thereby avoiding the situation that the communicator transmits redundant connection requests, improving the communication efficiency and reducing the possibility of connection failure.
A communicator according to claim 3 of the present invention is characterized in that the terminal communication device transmits a connection request of the service to the communicator immediately after receiving the first SDP response from the communicator.
Since the terminal communication apparatus transmits the connection request immediately after receiving the first SDP answer, as in most bluetooth devices, the above-described communicator of the present invention can distinguish the connection request transmission timing from the connection request transmission timing at the terminal communication apparatus side, and thus can reliably avoid connection failure due to connection collision.
A communicator according to claim 4 of the present invention is characterized in that, when the central communication apparatus supports a service related to the first SDP request, a section for automatically establishing a connection related to the first SDP request exists in the communicator, and the communicator waits for a predetermined period after transmitting a first SDP response to the terminal communication apparatus based on the section, and then determines whether to transmit a connection request for the service to the terminal communication apparatus.
According to the above-described communicator, based on the control of the profile related to the service, the communicator waits for a predetermined period after transmitting the first SDP answer to the terminal communication device, and then decides whether to transmit the connection request of the service to the terminal communication device.
A communicator according to claim 5 of the present invention is characterized in that the terminal communication device transmits the first SDP request to the communicator and receives the first SDP response from the communicator, and the communicator transmits a second SDP request to the terminal communication device and receives a second SDP response corresponding to the second SDP request from the terminal communication device.
When both the communicator side and the terminal communication apparatus side mutually transmit SDP requests, since the timings of mutually transmitting SDP are substantially the same, there is a higher possibility that both sides simultaneously request connection after the end of their respective SDP and cause connection failure, as compared with claim 1. In this case, the possibility of connection failure is greatly reduced by having the central communication apparatus side wait for a prescribed period.
The communicator of claim 6 of the present invention is characterized in that the terminal communication device is a smart phone.
In a typical smart phone, the smart phone will automatically issue a connection request after issuing an SDP request in a state where the smart phone is paired with other bluetooth devices and the asynchronous link is connected. In contrast, in the present invention, since the communicator side does not automatically issue a connection request but waits for a predetermined period, connection failure due to connection collision with the smart phone is avoided.
A communicator according to claim 7 of the present invention is characterized in that the service related to the first SDP request is a bluetooth handsfree service.
In the communicator according to claim 8 of the present invention, the central communication device is an audio device which can be mounted on a center console of an automobile.
A communicator according to claim 9 of the present invention is characterized in that the predetermined period is 2 seconds or longer.
In general, in a state where a terminal communication device such as a smart phone and a communicator are connected in an asynchronous link, SDP requests are made for a plurality of services (for example, bluetooth handsfree service based on HFP protocol (handles-Free Profile), bluetooth audio transmission service based on A2DP protocol (Advanced Audio Distribution Profile, bluetooth audio transmission protocol), specific application service based on SPP protocol (Serial Port Profile: serial port protocol), etc.), and connection of each service is made after SDP requests are made for all of the plurality of services. Since the time required for making SDP requests for all of the plurality of services does not normally exceed 1 second, the communicator of the present invention can reliably shift the timing of the terminal communication device requesting connection to the communicator by waiting for 2 seconds or more even if the terminal communication device makes SDP requests for all of the plurality of services.
In the center communication device according to claim 10 of the present invention, bluetooth communication is performed between the center communication device and the terminal communication device, and when the center communication device receives a first SDP request based on a service discovery protocol SDP from the terminal communication device and transmits a first SDP response corresponding to the first SDP request to the terminal communication device in a state in which pairing with the terminal communication device is completed and an asynchronous link is connected, the center communication device waits for a predetermined period after transmitting the first SDP response to the terminal communication device, and then determines whether to transmit a connection request for the service to the terminal communication device.
According to the above-described center communication device, by waiting for a predetermined period on the center communication device side (in-vehicle device side), the possibility that both the center communication device side (in-vehicle device side) and the terminal communication device side (smart phone side) simultaneously request connection for any one of the plurality of bluetooth services becomes low, and deadlock on the control plane that may occur when the terminal communication device side automatically connects after SDP is avoided, thereby suppressing connection failure between bluetooth devices.
A bluetooth communication system according to claim 11 of the present invention includes a central communication device and a terminal communication device capable of bluetooth communication with the central communication device, wherein the central communication device receives a first SDP request based on a service discovery protocol SDP from the terminal communication device in a state where pairing with the terminal communication device is completed and an asynchronous link is connected, transmits a first SDP response corresponding to the first SDP request to the terminal communication device, and when the central communication device supports a service related to the first SDP request, the central communication device waits for a predetermined period after transmitting the first SDP response to the terminal communication device, and then determines whether to transmit a connection request for the service to the terminal communication device.
According to the above bluetooth communication system, by waiting for a predetermined period on the central communication device side (in-vehicle device side), the possibility that both the central communication device side (in-vehicle device side) and the terminal communication device side (smart phone side) simultaneously request connection for any one of the plurality of bluetooth services becomes low, and deadlock on the control plane that may occur when the terminal communication device side automatically connects after SDP is avoided, thereby suppressing connection failure between bluetooth devices.
Drawings
Fig. 1 is a diagram showing a configuration of a bluetooth communication system according to a first embodiment.
Fig. 2 is a flowchart showing connection processing by the HFP protocol by the center communication apparatus according to the first embodiment.
Fig. 3 is a flowchart showing connection processing by the HFP protocol by the terminal communication apparatus according to the first embodiment.
Fig. 4 is a flowchart showing connection processing by the HFP protocol by the center communication apparatus according to the second embodiment.
Fig. 5 is a flowchart showing connection processing by the HFP protocol by the terminal communication apparatus according to the second embodiment.
Fig. 6 is a flowchart showing a connection process by the HFP protocol performed by the center communication apparatus according to another modification.
Symbol description
1. Bluetooth communication system
10. Central communication equipment (vehicle-mounted device)
20. Terminal communication device (Intelligent mobile phone)
T1 for a predetermined period of time
Detailed Description
(first embodiment)
The Bluetooth communication system of the present invention includes a central communication device and a terminal communication device capable of Bluetooth communication with the central communication device. In the first embodiment shown in fig. 1, description will be made taking, as an example, a case where the center communication device is an in-vehicle device capable of simultaneously connecting a plurality of terminal communication devices, and the terminal communication device is a smart phone capable of being connected to the in-vehicle device.
Of course, the center communication device or the terminal communication device in the present invention is not limited to this, and for example, the center communication device may be a bluetooth device such as a computer, a tablet computer, or a smart phone, and the terminal communication device may be a bluetooth device such as a car-mounted device, a computer, a tablet computer, a smart watch, a smart bracelet, or a bluetooth headset.
Fig. 1 is a diagram showing a configuration of a bluetooth communication system 1 according to a first embodiment. As shown in fig. 1, the bluetooth communication system 1 includes an in-vehicle apparatus 10 and a smart phone 20.
The in-vehicle device 10 is usually mounted near a center console of an automobile as an audio apparatus, and has various functions such as a radio function, a navigation function, and a multimedia play function. The in-vehicle device 10 further includes a communicator 11 as bluetooth communication means, and is capable of establishing connection with one or more terminal communication devices including the smartphone 20 and transmitting and receiving various data.
The smart phone 20 also has a bluetooth communication unit (not shown) capable of establishing various bluetooth connections with the in-vehicle device 10. For example, a connection is established with the in-vehicle apparatus 10 based on the HFP protocol, thereby using a hands-free call-making service. Alternatively, a connection is established with the in-vehicle apparatus 10 based on the A2DP protocol, so that music data in the smartphone 20 is played through the in-vehicle apparatus 10. Alternatively, a certain application in the smartphone 20 establishes a connection with the in-vehicle device 10 based on the SPP protocol, thereby using a specific service provided by the application.
Fig. 2 is a flowchart showing the connection processing by the HFP protocol performed by the in-vehicle apparatus 10 according to the first embodiment.
In the bluetooth communication system 1 of the present embodiment, before the connection process shown in fig. 2 is performed (i.e., before step S110 is performed), the communicator 11 of the in-vehicle device 10 and the smartphone 20 are in a state where pairing is completed and the ACL (Asynchronous Connectionless Link, asynchronous link) is connected, but no bluetooth connection on the service level is established between the communicator 11 of the in-vehicle device 10 and the smartphone 20 (for example, the smartphone 20 is in a state of approaching an automobile or just entering an inside of an automobile).
As shown in fig. 2, in step S110, the communicator 11 receives an SDP (Service Discovery Protocol ) request (hereinafter referred to as a "first SDP request") from the smartphone 20. The SDP request from smartphone 20 includes information about the service desired to be requested (hereinafter referred to as "service information"). In the present embodiment, description will be made taking an example in which the service desired to be requested is a bluetooth handsfree service based on HFP protocol, and thus the first SDP request in step S110 is an SDP request desired to request a bluetooth handsfree service (HFP service).
Next, in step S120, the communicator 11 transmits a first SDP answer corresponding to the first SDP request to the smartphone 20 according to whether or not HFP service is supported by itself. When the in-vehicle device 10 supports the HFP service, the first SDP answer contains at least information indicating that the HFP service is supported; when the in-vehicle device 10 does not support the HFP service, the first SDP answer contains at least information indicating that the HFP service is not supported.
Next, when the in-vehicle device 10 supports the HFP service (yes in step S130), the communicator 11 does not immediately transmit the connection request of the HFP service to the smartphone 20 after transmitting the first SDP response to the smartphone 20, but waits for the predetermined period T1 itself (step S140), and then decides whether to transmit the connection request of the HFP service to the smartphone 20 in the subsequent step. The predetermined period T1 is preferably set to 2 seconds or longer than the time required for the smartphone 20 to SDP all services supported by itself.
In more detail, in the case where the in-vehicle device 10 supports the HFP service related to the first SDP request, there is an HFP profile (also referred to as "profile") in the communicator 11 for automatically establishing the HFP connection related to the first SDP request. Based on the HFP profile, the communicator 11 waits for the predetermined period T1 after transmitting the first SDP answer to the smartphone 20, and then determines whether to transmit the connection request of the HFP service to the smartphone 20.
After waiting for the predetermined period T1 in step S140, the process proceeds to step S150.
In step S150, the communicator 11 determines whether a connection request of the HFP service is received from the smartphone 20. When it is determined that the connection request for the HFP service is received (yes in step S150), the communicator 11 performs the connection process with the HFP service of the smartphone 20 without transmitting the connection request for the HFP service to the smartphone 20, and transmits a notification of success of the connection to the smartphone 20 after the connection process is completed (step S160).
On the other hand, when it is determined that the connection request of the HFP service is not received (no in step S150), the communicator 11 transmits the connection request of the HFP service to the smart phone 20 (step S170).
Next, in step S180, communicator 11 receives a notification of successful connection from smartphone 20, and the process ends.
Fig. 3 is a flowchart showing connection processing by the HFP protocol by the smartphone 20 according to the first embodiment.
As shown in fig. 3, in step S210, smartphone 20 transmits a first SDP request to communicator 11 (i.e., the first SDP request received by communicator 11 in step S110). In the present embodiment, the smartphone 20 is a device supporting HFP services.
Next, in step S220, smartphone 20 receives a first SDP answer corresponding to the first SDP request described above (i.e., the first SDP answer transmitted by communicator 11 in step S120) from communicator 11.
Next, in step S230, the smartphone 20 determines whether the vehicle-mounted device 10 of the other party supports the HFP service, based on the content of the first SDP answer. If it is determined that the in-vehicle apparatus 10 does not support the HFP service (no in step S230), the process ends. On the other hand, when it is determined that the in-vehicle apparatus 10 supports the HFP service (yes in step S230), it is further determined whether the smartphone 20 has received a connection request for the HFP service from the communicator 11 (step S240).
When it is determined that the smartphone 20 has received the connection request for the HFP service from the communicator 11 (yes in step S240), the smartphone 20 does not transmit the connection request for the HFP service to the communicator 11, but performs connection processing with the HFP service of the communicator 11, and transmits a notification of connection success to the communicator 11 after the connection processing is completed (step S250), and the processing ends.
On the other hand, when it is determined that smartphone 20 has not received the connection request for the HFP service from communicator 11 (step S240: no), smartphone 20 transmits the connection request for the HFP service to communicator 11 (step S260).
Next, in step S270, smartphone 20 receives a notification of successful connection from communicator 11, and the process ends.
Next, the technical effects obtained by the first embodiment of the present invention will be described.
According to the communicator 11 in the in-vehicle device 10 of the first embodiment, by waiting the in-vehicle device 10 side for the predetermined period T1, the possibility of both the in-vehicle device 10 side and the smartphone 20 side simultaneously requesting connection for any one of the plurality of bluetooth services (for example, HFP service) becomes low, and deadlock on the control plane that may occur when the smartphone 20 side automatically connects after SDP is avoided, thereby suppressing connection failure between bluetooth devices.
Further, according to the communicator 11 in the in-vehicle device 10 of the first embodiment, the communicator 11 transmits the connection request of the HFP service to the smartphone 20 only in the case where the communicator 11 does not receive the connection request of the HFP service from the smartphone 20, thereby avoiding a case where the communicator 11 transmits an unnecessary connection request, both improving the communication efficiency and reducing the possibility of occurrence of connection failure.
Further, since the timing of transmitting the connection request is transmitted immediately after receiving the first SDP answer from the communicator 11, like most bluetooth devices, the timing of transmitting the connection request by the communicator 11 of the present invention can be distinguished from the timing of transmitting the connection request by the side of the smartphone 20, so that connection failure due to connection collision can be reliably avoided.
According to the communicator 11 in the in-vehicle device 10 of the first embodiment, based on the control of the profile related to the HFP service, the communicator 11 waits for the prescribed period T1 after transmitting the first SDP answer to the smartphone 20, and then decides whether to transmit the connection request of the HFP service to the smartphone 20.
In addition, with a typical smart phone, in a state where pairing of the smart phone with other bluetooth devices is completed and an asynchronous link is connected, the smart phone automatically issues a connection request after issuing an SDP request. In contrast, in the present invention, since the communicator 11 side does not automatically issue the connection request but waits for the predetermined period T1, connection failure due to connection collision with the smartphone 20 is avoided.
In general, in a state where the asynchronous link between the smartphone 20 and the communicator 11 is connected, SDP requests are made for a plurality of services (for example, a bluetooth handsfree service based on HFP protocol, a bluetooth audio transmission service based on A2DP protocol, a specific application service based on SPP protocol, etc.), and connection of each service is made after all SDP requests are made for the plurality of services. Since the time required for SDP request for all of the plurality of services does not normally exceed 1 second, the communicator 11 of the present invention can reliably shift the timing of connection request from the communicator 11 by the smartphone 20 even if the smartphone 20 makes SDP request for all of the plurality of services by waiting for 2 seconds or more.
(second embodiment)
In the first embodiment, smartphone 20 has sent a first SDP request to communicator 11, and communicator 11 then sends a first SDP answer to smartphone 20. In the second embodiment shown in fig. 4 and 5, in addition to the above-described operation, the smartphone 20 transmits the above-described first SDP request to the communicator 11 and receives the above-described first SDP answer from the communicator 11, and the communicator 11 also transmits a second SDP request to the smartphone 20 and receives a second SDP answer corresponding to the second SDP request from the smartphone 20.
In the second embodiment, the second SDP request issued by the communicator 11 is also an SDP request for requesting a bluetooth handsfree service (HFP service), and the second SDP response issued by the smartphone 20 is also an SDP response for the HFP service and includes at least information indicating that the HFP service is supported or not supported.
Fig. 4 is a flowchart showing the connection processing by the HFP protocol performed by the in-vehicle apparatus 10 according to the second embodiment.
Step S110, step S120, and steps S140 to S180 in fig. 4 are the same as those in the first embodiment, and only the differences in step S310, step S320, and step S330 will be described below.
In step S310 and step S320, simultaneously with step S110 and step S120, communicator 11 also transmits a second SDP request to smartphone 20 and receives a second SDP answer corresponding to the second SDP request from smartphone 20.
Here, the order of steps S110, S120, S310, and S320 in fig. 4 is merely an example, and it is understood that the four steps are performed substantially simultaneously, and the order of each other may be changed appropriately. For example, the steps S110, S310, S120, and S320 may be performed in the order of steps S310, S110, S120, and S320.
Next, in step S330, the communicator 11 determines whether both the communicator 11 and the smartphone 20 support HFP service. The determination of whether or not both the communicator 11 and the smartphone 20 support the HFP service can be determined by acquiring information indicating whether or not the HFP service is supported, which is contained in the first SDP answer and the second SDP answer, respectively.
In addition, determining whether both communicator 11 and smartphone 20 support HFP service may be determined by confirming that both communicator 11 and smartphone 20 have issued SDP requests, in other words, determining that both communicators 11 and smartphones 20 support HFP service based on the fact that both communicators 11 and smartphones 20 have issued SDP requests.
In addition, step S330 may perform the same operation as step 130 in the first embodiment.
Fig. 5 is a flowchart showing connection processing by the HFP protocol by the smartphone 20 according to the second embodiment.
Step S210, step S220, and steps S240 to S270 in fig. 5 are the same as those in the first embodiment, and only the differences in step S410, step S420, and step S430 will be described below.
In step S410 and step S420, simultaneously with step S210 and step S220, smartphone 20 also receives a second SDP request from communicator 11 and transmits a second SDP answer corresponding to the second SDP request to communicator 11.
Here, the sequence of steps S210, S220, S410, and S420 in fig. 5 is merely an example, and it is understood that the four steps are performed substantially simultaneously, and the sequence of each other may be changed appropriately. For example, the steps S210, S410, S220, and S420 may be performed in the order of steps S410, S210, S220, and S420.
Next, in step S430, smartphone 20 determines whether both communicator 11 and smartphone 20 support HFP services. The determination of whether or not both the communicator 11 and the smartphone 20 support the HFP service can be determined by acquiring information indicating whether or not the HFP service is supported, which is contained in the first SDP answer and the second SDP answer, respectively.
In addition, determining whether both communicator 11 and smartphone 20 support HFP service may be determined by confirming that both communicator 11 and smartphone 20 have issued SDP requests, in other words, determining that both communicators 11 and smartphones 20 support HFP service based on the fact that both communicators 11 and smartphones 20 have issued SDP requests.
In addition, step S430 may perform the same operation as step S230 in the first embodiment.
According to the communicator 11 in the in-vehicle device 10 of the second embodiment, when both the communicator 11 and the smartphone 20 transmit SDP requests to each other, since the timings of transmitting SDP to each other are substantially the same, both requests connection at the same time after the end of the SDP, and the possibility of connection failure increases. In this case, the possibility of connection failure is greatly reduced by causing the communicator 11 to wait for the prescribed period T1.
(other modifications)
The first and second embodiments are merely examples, and are not intended to limit the scope of the invention. The present invention can be implemented in various other modes, and various omissions, substitutions, and changes can be made without departing from the scope of the present invention. These embodiments and modifications are also included in the scope of the present invention and their equivalents.
The processing performed in fig. 2 to 6 may be stored in a storage medium in the bluetooth device, or may be implemented by a functional circuit or a set of functional circuits in the bluetooth device.
The bluetooth communication system of the present invention includes a central communication device and a terminal communication device, and in fact, "central" and "terminal" are merely a relative concept, and are not particularly limited. For example, the center communication device and the terminal communication device in the present invention may correspond to two in-vehicle devices of the same model or different models, respectively, or may correspond to two smart phones, respectively, or the like.
Further, as shown in fig. 6, the position of step S140 in the first embodiment may be moved before step S170 (i.e., between step S150 and step S170). Thus, in addition to the technical effects obtained in the first embodiment, the bluetooth communication system in which the communicator 11 can quickly receive the connection request of the HFP service from the smartphone 20 can perform the connection processing without waiting in step S140, and the time required for connection success in this case can be shortened. Of course, the second embodiment may be modified in the same manner.
The order of step S240 and step S260 in fig. 3 may be appropriately adjusted, and for example, step S240 and step S260 may be performed simultaneously. Of course, the second embodiment may be modified in the same manner.
In addition, the connection procedure of the HFP service is described in both the first and second embodiments, and the present invention is also applicable to connection procedures of other bluetooth services such as A2 DP.
Claims (11)
1. A communicator provided in a central communication device and capable of Bluetooth communication with a terminal communication device, characterized in that,
the communicator receives a first SDP request based on a service discovery protocol SDP from the terminal communication device in a state that pairing with the terminal communication device is completed and an asynchronous link is connected, and transmits a first SDP response corresponding to the first SDP request to the terminal communication device,
when the center communication device supports a service related to the first SDP request, the communication device waits for a predetermined period after transmitting the first SDP response to the terminal communication device, and then determines whether to transmit a connection request for the service to the terminal communication device.
2. The communicator of claim 1, wherein the communication device comprises a plurality of communication devices,
when the communicator receives the connection request of the service from the terminal communication device in the prescribed period, the communicator does not transmit the connection request of the service to the terminal communication device,
when the communicator does not receive the connection request of the service from the terminal communication device during the predetermined period, the communicator transmits the connection request of the service to the terminal communication device.
3. The communicator of claim 1, wherein the communication device comprises a plurality of communication devices,
the terminal communication device transmits a connection request of the service to the communicator immediately after receiving the first SDP answer from the communicator.
4. The communicator of claim 1, wherein the communication device comprises a plurality of communication devices,
in the case where the central communication apparatus supports a service related to the first SDP request, a configuration file for automatically establishing a connection related to the first SDP request is present in the communicator, and the communicator waits for a predetermined period after transmitting a first SDP response to the terminal communication apparatus based on the configuration file and then decides whether to transmit a connection request for the service to the terminal communication apparatus.
5. The communicator of claim 1, wherein the communication device comprises a plurality of communication devices,
the terminal communication device transmits a second SDP request to the terminal communication device and receives a second SDP answer corresponding to the second SDP request from the terminal communication device, while the terminal communication device transmits the first SDP request to the communicator and receives the first SDP answer from the communicator.
6. The communicator of any one of claims 1 to 5,
the terminal communication device is a smart phone.
7. The communicator of any one of claims 1 to 5,
the service related to said first SDP request is a bluetooth hands-free service.
8. The communicator of any one of claims 1 to 5,
the center communication device is an audio device that can be mounted on a center console of an automobile.
9. The communicator of any one of claims 1 to 5,
the predetermined period is 2 seconds or longer.
10. A central communication device capable of Bluetooth communication with a terminal communication device, characterized in that,
the central communication device receives a first SDP request based on a service discovery protocol SDP from the terminal communication device in a state that pairing with the terminal communication device is completed and an asynchronous link is connected, and transmits a first SDP response corresponding to the first SDP request to the terminal communication device,
when the center communication device supports a service related to the first SDP request, the center communication device waits for a predetermined period after transmitting the first SDP response to the terminal communication device, and then determines whether to transmit a connection request for the service to the terminal communication device.
11. A Bluetooth communication system comprising a central communication device and a terminal communication device capable of Bluetooth communication with the central communication device, characterized in that,
the central communication device receives a first SDP request based on a service discovery protocol SDP from the terminal communication device in a state that pairing with the terminal communication device is completed and an asynchronous link is connected, and transmits a first SDP response corresponding to the first SDP request to the terminal communication device,
when the center communication device supports a service related to the first SDP request, the center communication device waits for a predetermined period after transmitting the first SDP response to the terminal communication device, and then determines whether to transmit a connection request for the service to the terminal communication device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811283433.7A CN111132098B (en) | 2018-10-31 | 2018-10-31 | Communicator, central communication device and Bluetooth communication system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811283433.7A CN111132098B (en) | 2018-10-31 | 2018-10-31 | Communicator, central communication device and Bluetooth communication system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111132098A CN111132098A (en) | 2020-05-08 |
| CN111132098B true CN111132098B (en) | 2023-11-28 |
Family
ID=70485107
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811283433.7A Active CN111132098B (en) | 2018-10-31 | 2018-10-31 | Communicator, central communication device and Bluetooth communication system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111132098B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114630303A (en) * | 2020-12-14 | 2022-06-14 | 深圳Tcl新技术有限公司 | Bluetooth connection method, system, intelligent terminal and computer storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1533656A (en) * | 2001-07-26 | 2004-09-29 | �ʼҷ����ֵ�������˾ | Method for reliable and effective support of congestion control in nack-based protoclos |
| CN101064695A (en) * | 2007-05-16 | 2007-10-31 | 杭州看吧科技有限公司 | P2P(Peer to Peer) safe connection method |
| CN102331727A (en) * | 2011-08-24 | 2012-01-25 | 华为软件技术有限公司 | Bluetooth media play controlling method and relevant device |
| CN102342174A (en) * | 2009-08-06 | 2012-02-01 | 株式会社电装 | In-vehicle terminal apparatus and radio connection program for in-vehicle terminal apparatus |
| JP2014017790A (en) * | 2012-07-11 | 2014-01-30 | Ntt Docomo Inc | Application server, communication control method, and communication control program |
| CN103733661A (en) * | 2011-07-25 | 2014-04-16 | 摩托罗拉移动有限责任公司 | Methods and apparatuses for providing profile information in a bluetooth communication system |
| CN105792386A (en) * | 2016-04-20 | 2016-07-20 | 上海斐讯数据通信技术有限公司 | Frequency range connecting method of wireless equipment and wireless equipment |
| CN107454563A (en) * | 2017-09-08 | 2017-12-08 | 歌尔科技有限公司 | A kind of Bluetooth communication method, device and bluetooth equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9430275B2 (en) * | 2011-06-03 | 2016-08-30 | Oracle International Corporation | Synchronization between concurrent notifier and waiter transactions using transaction condition variables |
-
2018
- 2018-10-31 CN CN201811283433.7A patent/CN111132098B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1533656A (en) * | 2001-07-26 | 2004-09-29 | �ʼҷ����ֵ�������˾ | Method for reliable and effective support of congestion control in nack-based protoclos |
| CN101064695A (en) * | 2007-05-16 | 2007-10-31 | 杭州看吧科技有限公司 | P2P(Peer to Peer) safe connection method |
| CN102342174A (en) * | 2009-08-06 | 2012-02-01 | 株式会社电装 | In-vehicle terminal apparatus and radio connection program for in-vehicle terminal apparatus |
| CN103733661A (en) * | 2011-07-25 | 2014-04-16 | 摩托罗拉移动有限责任公司 | Methods and apparatuses for providing profile information in a bluetooth communication system |
| CN102331727A (en) * | 2011-08-24 | 2012-01-25 | 华为软件技术有限公司 | Bluetooth media play controlling method and relevant device |
| JP2014017790A (en) * | 2012-07-11 | 2014-01-30 | Ntt Docomo Inc | Application server, communication control method, and communication control program |
| CN105792386A (en) * | 2016-04-20 | 2016-07-20 | 上海斐讯数据通信技术有限公司 | Frequency range connecting method of wireless equipment and wireless equipment |
| CN107454563A (en) * | 2017-09-08 | 2017-12-08 | 歌尔科技有限公司 | A kind of Bluetooth communication method, device and bluetooth equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111132098A (en) | 2020-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106658359B (en) | Bluetooth connection method, device and communication system | |
| US8850031B2 (en) | Pairing system, pairing management device, pairing method, and program | |
| US10764898B2 (en) | Media access control (MAC) address identification | |
| US9521238B1 (en) | Establishing multiple short range wireless links between a vehicle and a mobile device | |
| JP2002261686A (en) | Method for link connection between communication terminals having bluetooth wireless device | |
| US11930542B2 (en) | Source device switching method and device through Bluetooth connection information sharing | |
| CN113498622A (en) | Electronic device for requesting NSSAI in wireless communication network and method thereof | |
| KR20200110086A (en) | Method for establishing wireless communication link and electronic device supporting the same | |
| CN111132098B (en) | Communicator, central communication device and Bluetooth communication system | |
| US9942729B2 (en) | Method and apparatus for establishing communication between terminals | |
| KR101907075B1 (en) | Method and apparatus for data communication using bluetooth low energy | |
| JP2001345893A (en) | Storage device for storing performance data, and method for updating the storage device | |
| CN110177357B (en) | Bluetooth management method, mobile terminal and computer storage medium | |
| JP6062293B2 (en) | Hands-free communication device and computer program | |
| CN110300393B (en) | Bluetooth communication device, Bluetooth communication system, and Bluetooth communication method | |
| US9300778B2 (en) | Bluetooth headset for mobile phone | |
| KR100703489B1 (en) | Method for using mobile terminal in telematics system | |
| US20230041033A1 (en) | ELECTRONIC DEVICE AND METHOD FOR INSTALLING eSIM PROFILE IN ELECTRONIC DEVICE | |
| CN111918250B (en) | Bluetooth communicator and Bluetooth communication method | |
| CN113810887A (en) | Bluetooth protocol connection method, device, storage medium and related equipment | |
| US20230337302A1 (en) | Electronic device that carries out communication and operation method therefor | |
| US11672030B2 (en) | Control method, on-vehicle device, and storage medium | |
| CN106470414B (en) | Method and device for accessing SIM card | |
| CN110737456B (en) | Online upgrading method of wireless earphone and earphone equipment | |
| US20220038216A1 (en) | Electronic device for transmitting eir packet in bluetooth network environment, and method related thereto |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |