CN111132098A - Communicator, central communication device and blue tooth communication system - Google Patents
Communicator, central communication device and blue tooth communication system Download PDFInfo
- Publication number
- CN111132098A CN111132098A CN201811283433.7A CN201811283433A CN111132098A CN 111132098 A CN111132098 A CN 111132098A CN 201811283433 A CN201811283433 A CN 201811283433A CN 111132098 A CN111132098 A CN 111132098A
- Authority
- CN
- China
- Prior art keywords
- communicator
- communication device
- sdp
- 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.)
- Granted
Links
- 238000004891 communication Methods 0.000 title claims abstract description 179
- 238000000034 method Methods 0.000 description 21
- 230000005540 biological transmission Effects 0.000 description 3
- 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
- 230000000670 limiting effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
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 conflicts between Bluetooth devices. The communicator of the present invention is provided in a central communication apparatus and is capable of performing bluetooth communication with a terminal communication apparatus, and is characterized in that the communicator receives a first SDP request based on a service discovery protocol SDP from the terminal communication apparatus and transmits a first SDP answer corresponding to the first SDP request to the terminal communication apparatus in a state where pairing with the terminal communication apparatus is completed and an asynchronous link is connected, and in a case where the central communication apparatus supports a service related to the first SDP request, the communicator waits for a predetermined period after transmitting the first SDP answer to the terminal communication apparatus and then determines whether or not to transmit a connection request of the service to the terminal communication apparatus.
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, a wireless communication standard for short-distance data exchange technology
Communication is widely used in the fields of computers, mobile internet, vehicle-mounted devices, and the like. A device having a bluetooth communication function (hereinafter referred to as a "bluetooth device") can utilize various services based on bluetooth communication, such as a service of connecting a computer main body with an input device such as a mouse or a keyboard, a service of connecting a smartphone with an in-vehicle device, and the like.
When a connection for a certain service is established between two bluetooth devices, a connection failure may occur due to the physical state of the respective channels, the timing of the mutual connection between the two bluetooth devices, and the like. Regarding the timing of mutual connection, in the process of establishing a connection of a certain service between two bluetooth devices, if two bluetooth devices send connection requests at the same time, the two bluetooth devices may wait for the response of the other bluetooth device at the same time, which may eventually result in a connection failure. Here, "simultaneously" refers to a case where the interval between the connection requests issued by the respective bluetooth devices is small to some extent (for example, less than 50 milliseconds).
In other words, when both bluetooth devices receive a connection request from the other party immediately after transmitting the connection request at the same time, since both bluetooth devices are in a state of waiting for the response of the other party at this time, the received connection request from the other party is temporarily put on hold, and as a result, both bluetooth devices are in a state of not being able to transmit a response to the other party and waiting for the response of the other party. Such a state in which the connection requests of both parties collide is also referred to as a deadlock (deadlock) state. Then, when the deadlock state continues for a certain time (for example, a time longer than 1 second), the two bluetooth devices respectively obtain the results of connection failure.
The above-mentioned connection failure may occur even when the physical channels of the two bluetooth devices are sufficient, and when the connection failure occurs, the user may need to wait for a certain time and may need to perform connection again automatically or manually, which complicates the operation and deteriorates user experience.
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 central communication apparatus, and a bluetooth communication system that can reduce the occurrence of connection collisions between bluetooth apparatuses.
A communicator according to claim 1 of the present invention is a communicator provided in a central communication apparatus and capable of performing bluetooth communication with a terminal communication apparatus, wherein the communicator receives a first SDP request based on a Service Discovery Protocol (SDP) (service discovery protocol) from the terminal communication apparatus in a state where pairing with the terminal communication apparatus is completed and an asynchronous link is connected, and transmits a first SDP answer corresponding to the first SDP request to the terminal communication apparatus, and when the central communication apparatus supports a service related to the first SDP request, the communicator waits for a predetermined period after transmitting the first SDP answer to the terminal communication apparatus, and then determines whether to transmit a connection request for the service to the terminal communication apparatus.
According to the above communicator, the central communication apparatus side (in-vehicle apparatus side) is caused to wait for a predetermined period, and the possibility that both the central communication apparatus side (in-vehicle apparatus side) and the terminal communication apparatus side (smartphone side) simultaneously request connection for any one of the plurality of bluetooth services becomes low, so that deadlock in the control plane which may occur when the terminal communication apparatus side performs automatic connection after SDP is avoided, and connection failure between bluetooth devices is suppressed.
A communicator according to claim 2 of the present invention is characterized in that the communicator does not transmit a connection request for the service to the terminal communication device when the communicator receives the connection request for the service from the terminal communication device during the predetermined period, and transmits the connection request for the service to the terminal communication device when the communicator does not receive the connection request for the service from the terminal communication device during the predetermined period.
According to the communicator, the communicator transmits the connection request of the service to the terminal communication device only in the case where the communicator does not receive the connection request of the service from the terminal communication device, thereby avoiding the situation where the communicator transmits an unnecessary connection request, improving the communication efficiency, and reducing the possibility of occurrence of connection failure.
The 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 answer 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 timing at which the communicator transmits the connection request can be distinguished from the timing at which the terminal communication apparatus side transmits the connection request, and thus connection failure due to connection collision can be reliably avoided.
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, the communicator has a section for automatically establishing a connection related to the first SDP request, and the communicator waits for a predetermined period after transmitting a first SDP answer to the terminal communication apparatus based on the section, and then determines whether or not to transmit a connection request for the service to the terminal communication apparatus.
According to the above communicator, based on the control of the profile relating to the service, the communicator waits for a predetermined period after transmitting the first SDP answer to the terminal communication device, and then determines whether or not to transmit a connection request for the service to the terminal communication device.
The communicator according to claim 5 of the present invention is characterized in that, while the terminal communication device transmits the first SDP request to the communicator and receives the first SDP answer from the communicator, the communicator 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.
When both the communicator side and the terminal communication apparatus side transmit SDP requests to each other, the timings of transmitting the SDPs to each other are substantially the same, and therefore, compared to the case of the solution 1, both the sides have a higher possibility of connection failure due to simultaneous requests for connection after the respective SDPs end. In this case, the possibility of connection failure is greatly reduced by causing the central communication apparatus side to wait for a predetermined period.
The communicator according to claim 6 of the present invention is characterized in that the terminal communication device is a smartphone.
In a normal smart phone, when the smart phone and other bluetooth devices are in a state of being paired and the asynchronous link is connected, the smart phone automatically sends out a connection request after sending out an SDP request. In contrast, in the present invention, the communicator side does not automatically issue a connection request but waits for a predetermined period of time, and therefore, connection failure due to connection conflict with the smartphone is avoided.
The 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.
The communicator according to claim 8 of the present invention is characterized in that 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 more.
In general, in a state where an asynchronous link is connected between a terminal communication device such as a smartphone and a communicator, an SDP request is made for a plurality of services (for example, a bluetooth handsfree service based on HFP protocol (hand-Free Profile, bluetooth handsfree protocol), a bluetooth Audio transmission service based on A2DP protocol (bluetooth Audio transmission protocol), a specific application service based on SPP protocol (Serial Port Profile, Serial Port protocol, etc.)), and connection of each service is made after all the plurality of services are subjected to the SDP request. Since the time required for all of the services to make SDP requests does not usually exceed 1 second, the communicator of the present invention waits for 2 seconds or more, and thus can reliably shift the timing at which the terminal communication device requests a connection to the communicator even if the terminal communication device makes SDP requests for all of the services.
A central communication apparatus according to claim 10 of the present invention is a central communication apparatus capable of performing bluetooth communication with a terminal communication apparatus, wherein the central communication apparatus receives a first SDP request based on a service discovery protocol SDP from the terminal communication apparatus in a state where pairing with the terminal communication apparatus is completed and an asynchronous link is connected, and transmits a first SDP answer corresponding to the first SDP request to the terminal communication apparatus, and when the central communication apparatus supports a service related to the first SDP request, the central communication apparatus waits for a predetermined period after transmitting the first SDP answer to the terminal communication apparatus, and then determines whether to transmit a connection request of the service to the terminal communication apparatus.
According to the above-described central communication apparatus, the central communication apparatus side (the in-vehicle apparatus side) is caused to wait for a predetermined period, and the possibility that both the central communication apparatus side (the in-vehicle apparatus side) and the terminal communication apparatus side (the smartphone side) simultaneously request connection for any one of the plurality of bluetooth services is reduced, whereby deadlock in the control plane which may occur when the terminal communication apparatus side performs automatic connection after SDP is avoided, and connection failure between bluetooth devices is suppressed.
A bluetooth communication system according to claim 11 of the present invention includes a central communication apparatus and a terminal communication apparatus capable of performing bluetooth communication with the central communication apparatus, wherein the central communication apparatus receives a first SDP request based on a service discovery protocol SDP from the terminal communication apparatus in a state where pairing with the terminal communication apparatus is completed and an asynchronous link is connected, and transmits a first SDP answer corresponding to the first SDP request to the terminal communication apparatus, and when the central communication apparatus supports a service related to the first SDP request, the central communication apparatus waits for a predetermined period after transmitting the first SDP answer to the terminal communication apparatus, and then determines whether to transmit a connection request for the service to the terminal communication apparatus.
According to the bluetooth communication system, the central communication apparatus side (the in-vehicle apparatus side) waits for a predetermined period, and the possibility that both the central communication apparatus side (the in-vehicle apparatus side) and the terminal communication apparatus side (the smartphone side) simultaneously request connection to any one of the plurality of bluetooth services is low, whereby deadlock in the control plane that may occur when the terminal communication apparatus side performs automatic connection after SDP is avoided, and connection failure between bluetooth devices is suppressed.
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 a connection process of the central communication apparatus according to the HFP protocol in the first embodiment.
Fig. 3 is a flowchart showing a connection process of the terminal communication apparatus according to the HFP protocol in the first embodiment.
Fig. 4 is a flowchart showing a connection process of the central communication apparatus according to the HFP protocol in the second embodiment.
Fig. 5 is a flowchart showing a connection process of the terminal communication apparatus according to the second embodiment based on the HFP protocol.
Fig. 6 is a flowchart showing a connection process of the central communication apparatus according to the HFP protocol in another modification.
Description of the symbols
1 Bluetooth communication system
10 Central communication device (vehicle device)
20 terminal communication device (Intelligent mobile phone)
T1 predetermined period
Detailed Description
(first embodiment)
A Bluetooth communication system of the present invention includes a central communication device and a terminal communication device capable of performing Bluetooth communication with the central communication device. In the first embodiment shown in fig. 1, a case where the center communication device is an in-vehicle device to which a plurality of terminal communication devices can be simultaneously connected and the terminal communication devices are smartphones to which the in-vehicle device can be connected will be described as an example.
Of course, the central communication device or the terminal communication device in the present invention is not limited to this, for example, the central communication device may also be a bluetooth device such as a computer, a tablet computer, and a smart phone, and the terminal communication device may also be a bluetooth device such as an in-vehicle device, a computer, a tablet computer, a smart watch, a smart band, and 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 smartphone 20.
The in-vehicle device 10 is generally installed near a center console of an automobile as an audio device, and has a plurality of functions such as a radio function, a navigation function, and a multimedia playback function. The in-vehicle device 10 further includes a communicator 11 as a bluetooth communication unit, and is capable of establishing connection with one or more terminal communication devices including the smartphone 20 and transmitting and receiving various types of data.
The smartphone 20 also has a bluetooth communication unit (not shown) and is capable of establishing various bluetooth connections with the in-vehicle device 10. For example, connection is established with the in-vehicle device 10 based on the HFP protocol, thereby using a hands-free call service. Alternatively, a connection is established with the in-vehicle device 10 based on the A2DP protocol, so that the music data in the smartphone 20 is played by the in-vehicle device 10. Alternatively, an 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 process based on the HFP protocol performed by the in-vehicle device 10 according to the first embodiment.
In the bluetooth communication system 1 according to the present embodiment, before the connection processing shown in fig. 2 is executed (i.e., before step S110 is executed), the communicator 11 of the in-vehicle apparatus 10 and the smartphone 20 are in a state in which pairing is completed and ACL (Asynchronous Link) is connected, but a bluetooth connection on a service level is not established between the communicator 11 of the in-vehicle apparatus 10 and the smartphone 20 (for example, the smartphone 20 is in a state of approaching an automobile or just entering the automobile).
As shown in fig. 2, in step S110, the communicator 11 receives an SDP (service discovery Protocol) request (hereinafter referred to as "first SDP request") from the smartphone 20. The SDP request from smartphone 20 contains information about the service desired to be requested (hereinafter referred to as "service information"). In the present embodiment, the description is given taking as an example that the service desired to be requested is the bluetooth handsfree service based on the HFP protocol, and therefore the first SDP request in step S110 is an SDP request that is desired to request the 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 it supports the HFP service. 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 waits for a predetermined period T1 without immediately transmitting a connection request of the HFP service to the smartphone 20 after transmitting the first SDP answer to the smartphone 20 (step S140), and then determines whether or not to transmit the connection request of the HFP service to the smartphone 20 in the subsequent step. The predetermined period T1 is set to be longer than the time required for the smartphone 20 to perform SDP on all services supported by the smartphone, and is preferably set to 2 seconds or longer.
More specifically, in a case where the in-vehicle device 10 supports the HFP service related to the first SDP request, an HFP profile (also referred to as a "profile") for automatically establishing HFP connection related to the first SDP request exists in the communicator 11. The communicator 11 waits for a predetermined period T1 after transmitting the first SDP answer to the smartphone 20 based on the HFP profile, and then determines whether or not to transmit a connection request of the HFP service to the smartphone 20.
After waiting for a 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 determining that the connection request of the HFP service is received (yes in step S150), the communicator 11 performs the connection process of the HFP service with the smartphone 20 without transmitting the connection request of the HFP service to the smartphone 20, and transmits a notification of successful connection to the smartphone 20 after the completion of the connection process (step S160), and the process ends.
On the other hand, if 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 smartphone 20 (step S170).
Next, in step S180, communicator 11 receives the notification of the connection success from smartphone 20, and the process ends.
Fig. 3 is a flowchart showing the connection process by the HFP protocol performed by the smartphone 20 according to the first embodiment.
As shown in fig. 3, in step S210, smartphone 20 sends a first SDP request to communicator 11 (i.e., the first SDP request that communicator 11 received in step S110). In the present embodiment, the smartphone 20 is a device that supports the HFP service.
Next, in step S220, the smartphone 20 receives the first SDP answer corresponding to the first SDP request from the communicator 11 (i.e., the first SDP answer transmitted by the communicator 11 in step S120).
Next, in step S230, the smartphone 20 determines whether the partner in-vehicle device 10 supports the HFP service, based on the content of the first SDP answer. If it is determined that the in-vehicle device 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 device 10 supports the HFP service (yes in step S230), it is further determined whether the smartphone 20 has received a connection request of the HFP service from the communicator 11 (step S240).
When it is determined that the smartphone 20 has received the connection request of the HFP service from the communicator 11 (yes in step S240), the smartphone 20 performs the connection processing of the HFP service with the communicator 11 without transmitting the connection request of the HFP service to the communicator 11, and transmits a notification of connection success to the communicator 11 after the completion of the connection processing (step S250), and the processing ends.
On the other hand, when it is determined that the smartphone 20 has not received the connection request of the HFP service from the communicator 11 (step S240: no), the smartphone 20 transmits the connection request of the HFP service to the communicator 11 (step S260).
Next, in step S270, the smartphone 20 receives the notification of the connection success from the 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 of the in-vehicle device 10 of the first embodiment, by causing the in-vehicle device 10 side to wait for the predetermined period T1, the possibility that both the in-vehicle device 10 side and the smartphone 20 side simultaneously request connection to any one of the plurality of bluetooth services (for example, HFP service) is low, and deadlock in the control plane that may occur when the smartphone 20 side performs automatic connection 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, only in the case where the communicator 11 does not receive the connection request of the HFP service from the smartphone 20, the communicator 11 transmits the connection request of the HFP service to the smartphone 20, thereby avoiding the case where the communicator 11 transmits a redundant connection request, improving both the communication efficiency and reducing the possibility of occurrence of a connection failure.
Further, since the smartphone 20 transmits the connection request immediately after receiving the first SDP answer from the communicator 11, as in most bluetooth devices, the timing at which the communicator 11 transmits the connection request can be distinguished from the timing at which the smartphone 20 side transmits the connection request, and thus 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 predetermined period T1 after transmitting the first SDP answer to the smartphone 20, and then determines whether or not to transmit the connection request of the HFP service to the smartphone 20.
In addition, as for a normal smart phone, when the smart phone is in a state where pairing with other bluetooth devices is completed and an asynchronous link is connected, the smart phone automatically sends a connection request after sending an SDP request. In contrast, in the present invention, the communicator 11 side does not automatically issue a connection request but waits for the predetermined period T1, and therefore, a connection failure due to a connection collision with the smartphone 20 is avoided.
In general, in a state where an asynchronous link is connected between the smartphone 20 and the communicator 11, SDP requests are made for a plurality of services (for example, a bluetooth handsfree service based on the HFP protocol, a bluetooth audio transmission service based on the A2DP protocol, a specific application service based on the SPP protocol, and the like), and connection of each service is made after SDP requests are made for all of the plurality of services. Since the time required for all of the services to make SDP requests does not usually exceed 1 second, communicator 11 of the present invention waits for 2 seconds or more, and thus can reliably shift the timing at which smartphone 20 requests a connection to communicator 11, even if smartphone 20 makes an SDP request for all of the services.
(second embodiment)
In the first embodiment, smartphone 20 has sent a first SDP request to communicator 11, and communicator 11 has then sent a first SDP answer to smartphone 20. In the second embodiment shown in fig. 4 and 5, in addition to the above-described operations, 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 the second SDP request to the smartphone 20 and receives the 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 the bluetooth handsfree service (HFP service), and the second SDP answer issued by the smartphone 20 is also an SDP answer for the HFP service, and contains information indicating that the HFP service is supported or not supported.
Fig. 4 is a flowchart showing the connection process based on the HFP protocol performed by the in-vehicle device 10 according to the second embodiment.
Steps S110, S120, S140 to S180 in fig. 4 are the same as those in the first embodiment, and only different steps S310, S320 and S330 will be described below.
In step S310 and step S320, in parallel 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 sequence of step S110, step S120, step S310, and step S320 in fig. 4 is merely an example, and it is understood that these four steps are performed substantially simultaneously, and the sequence of these steps may be appropriately changed. For example, the sequence of step S110, step S310, step S120, and step S320 may be performed, or the sequence of step S310, step S110, step S120, and step S320 may be performed.
Next, in step S330, the communicator 11 determines whether both the communicator 11 and the smartphone 20 support the HFP service. Determining whether both the communicator 11 and the smartphone 20 support the HFP service may be determined by acquiring information indicating whether the HFP service is supported, which is included in the first SDP answer and the second SDP answer, respectively.
Further, the determination of whether both the communicator 11 and the smartphone 20 support the HFP service may be determined by confirming that both the communicator 11 and the smartphone 20 have issued SDP requests, in other words, it may be determined that both the communicator 11 and the smartphone 20 have issued SDP requests.
In addition, step S330 may perform the same operation as step S130 in the first embodiment.
Fig. 5 is a flowchart showing the connection process by the HFP protocol performed by the smartphone 20 according to the second embodiment.
Steps S210, S220, S240 to S270 in fig. 5 are the same as those in the first embodiment, and only different steps S410, S420 and S430 will be described below.
In steps S410 and S420, the smartphone 20 also receives the second SDP request from the communicator 11 and transmits a second SDP answer corresponding to the second SDP request to the communicator 11, simultaneously with steps S210 and S220.
Here, the sequence of step S210, step S220, step S410, and step S420 in fig. 5 is merely an example, and it is understood that these four steps are performed substantially simultaneously, and the sequence of these steps may be appropriately changed. For example, the sequence of step S210, step S410, step S220, and step S420 may be performed, or the sequence of step S410, step S210, step S220, and step S420 may be performed.
Next, in step S430, the smartphone 20 determines whether both the communicator 11 and the smartphone 20 support the HFP service. Determining whether both the communicator 11 and the smartphone 20 support the HFP service may be determined by acquiring information indicating whether the HFP service is supported, which is included in the first SDP answer and the second SDP answer, respectively.
Further, the determination of whether both the communicator 11 and the smartphone 20 support the HFP service may be determined by confirming that both the communicator 11 and the smartphone 20 have issued SDP requests, in other words, it may be determined that both the communicator 11 and the smartphone 20 have issued SDP requests.
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, the timings of transmitting the SDPs to each other are substantially the same, and therefore, there is a higher possibility that both the communicators request connection at the same time after the respective SDPs are finished, and connection failure occurs. In this case, by causing the communicator 11 to wait for the predetermined period T1, the possibility of connection failure is greatly reduced.
(other modification example)
The first and second embodiments are merely examples, and are not intended to limit the scope of the invention. The present invention may be implemented in other various forms, and various omissions, substitutions, and changes may be made without departing from the spirit of the present invention. These embodiments and modifications are also included in the scope of the present invention and equivalents thereof.
The processes executed 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 collection 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 actually "central" and "terminal" are merely a relative concept and have no specific limiting effect. For example, the central communication device and the terminal communication device in the present invention may respectively correspond to two in-vehicle devices of the same model or different models, and may also respectively correspond to two smart phones, etc.
Further, as shown in fig. 6, the position of step S140 in the first embodiment may be moved to before step S170 (i.e., between step S150 and step S170). Thus, in the bluetooth communication system in which the communicator 11 can quickly receive the connection request of the HFP service from the smartphone 20, the connection process can be performed without performing the wait in step S140 in addition to the technical effect obtained in the first embodiment, and the time required for the connection success in this case can be shortened. Of course, the second embodiment may be similarly modified.
In addition, the order of the steps S240 and S260 in fig. 3 may be adjusted as appropriate, and for example, the steps S240 and S260 may be performed simultaneously. Of course, the second embodiment may be similarly modified.
In the first and second embodiments, the connection procedure of the HFP service is described, and the present invention is also applicable to the connection procedure of another bluetooth service such as A2 DP.
Claims (11)
1. A communicator, which is provided in a central communication device and is capable of performing Bluetooth communication with a terminal communication device,
the communicator receives a first SDP request based on a service discovery protocol SDP from the terminal communication apparatus in a state where pairing with the terminal communication apparatus is completed and an asynchronous link is connected, and transmits a first SDP response corresponding to the first SDP request to the terminal communication apparatus,
when the central communication device supports the service related to the first SDP request, the communicator waits for a predetermined period of time after transmitting the first SDP answer 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,
when the communicator receives a connection request for the service from the terminal communication apparatus during the predetermined period, the communicator does not transmit the connection request for the service to the terminal communication apparatus,
the communicator transmits a connection request for the service to the terminal communication apparatus when the communicator does not receive the connection request for the service from the terminal communication apparatus during the predetermined period.
3. The communicator of claim 1,
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,
when the central communication device supports a service related to the first SDP request, the communicator has a profile for automatically establishing a connection related to the first SDP request, and the communicator waits for a predetermined period of time after transmitting a first SDP answer to the terminal communication device based on the profile, and then determines whether to transmit a connection request for the service to the terminal communication device.
5. The communicator of claim 1,
the terminal communication device transmits the first SDP request to the communicator and receives the first SDP answer from the communicator, and the communicator 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.
6. The communicator according to any one of claims 1 to 5,
the terminal communication device is a smart phone.
7. The communicator according to any one of claims 1 to 5,
the service related to the first SDP request described above is a bluetooth handsfree service.
8. The communicator according to any one of claims 1 to 5,
the central communication device is an audio device that can be mounted on a center console of an automobile.
9. The communicator according to any one of claims 1 to 5,
the predetermined period is 2 seconds or more.
10. A central communication device capable of performing Bluetooth communication with a terminal communication device,
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, and transmits a first SDP response corresponding to the first SDP request to the terminal communication device,
when the central communication device supports a service related to the first SDP request, the central communication device waits for a predetermined period of time after transmitting a first SDP answer 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 performing Bluetooth communication with the central communication device,
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, and transmits a first SDP response corresponding to the first SDP request to the terminal communication device,
when the central communication device supports a service related to the first SDP request, the central communication device waits for a predetermined period of time after transmitting a first SDP answer 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 true CN111132098A (en) | 2020-05-08 |
| CN111132098B 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) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022127171A1 (en) * | 2020-12-14 | 2022-06-23 | 深圳Tcl新技术有限公司 | Bluetooth connection method and system, intelligent terminal and computer storage medium |
Citations (9)
| 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 |
| US20120311273A1 (en) * | 2011-06-03 | 2012-12-06 | Marathe Virendra J | System and Method for Synchronization Between Concurrent Transactions Using Transaction Condition Variables |
| 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 |
-
2018
- 2018-10-31 CN CN201811283433.7A patent/CN111132098B/en active Active
Patent Citations (9)
| 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 |
| US20120311273A1 (en) * | 2011-06-03 | 2012-12-06 | Marathe Virendra J | System and Method for Synchronization Between Concurrent Transactions Using Transaction Condition Variables |
| 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 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022127171A1 (en) * | 2020-12-14 | 2022-06-23 | 深圳Tcl新技术有限公司 | Bluetooth connection method and system, intelligent terminal and computer storage medium |
| GB2617297A (en) * | 2020-12-14 | 2023-10-04 | Shenzhen Tcl New Tech Co Ltd | Bluetooth connection method and system, intelligent terminal and computer storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111132098B (en) | 2023-11-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106658359B (en) | Bluetooth connection method, device and communication system | |
| US10154384B2 (en) | Systems and methods for back channel communication | |
| US8285341B2 (en) | Process for transmitting phone book data from a mobile telephone to an external device and an external device | |
| JP2006262468A (en) | Method for link connection between communication terminals having bluetooth wireless device | |
| US20160286337A1 (en) | Systems and methods for audio streaming | |
| US11991612B2 (en) | Bluetooth data transmission method and apparatus, terminal and storage medium | |
| US8503998B2 (en) | Wireless communication terminal and wireless communication method | |
| CN110784846B (en) | Vehicle-mounted Bluetooth equipment identification method and device, electronic equipment and storage medium | |
| EP3869722B1 (en) | Signalling multiple resources for transmitting a/n in an uplink unlicensed channel | |
| CN110177357B (en) | Bluetooth management method, mobile terminal and computer storage medium | |
| CN105530355B (en) | Hands-free device for vehicle and method of controlling the hands-free device | |
| KR101907075B1 (en) | Method and apparatus for data communication using bluetooth low energy | |
| CN103391640A (en) | Dual-card dual-standby terminal and method for achieving concurrent data service | |
| US7817594B2 (en) | Method for operating a device in a radio access network of a radio communication system as well as radio access network and device | |
| US9942729B2 (en) | Method and apparatus for establishing communication between terminals | |
| JP2001345893A (en) | Storage device for storing performance data, and method for updating the storage device | |
| CN111132098B (en) | Communicator, central communication device and Bluetooth communication system | |
| CN110602683A (en) | Bluetooth control method, device, mobile terminal and storage medium | |
| CN110300393B (en) | Bluetooth communication device, Bluetooth communication system, and Bluetooth communication method | |
| US20050113149A1 (en) | Method for controlling a hands-free system, radio apparatus, and hands free apparatus | |
| KR100703489B1 (en) | Method for using mobile terminal in telematics system | |
| CN111918250B (en) | Bluetooth communicator and Bluetooth communication method | |
| CN106470414B (en) | Method and device for accessing SIM card | |
| CN113810887A (en) | Bluetooth protocol connection method, device, storage medium and related equipment | |
| US11672030B2 (en) | Control method, on-vehicle device, and storage medium |
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 |