WO2011145314A1 - Short-range wireless communication apparatus - Google Patents

Abstract

Disclosed is a short-range wireless communication apparatus (100) that can establish simultaneous connections of a plurality of profiles between the apparatus (100) and another short-range wireless communication apparatus (200) that is the other end of connection. The short-range wireless communication apparatus (100) comprises: a communication disconnection detecting unit (101) for detecting whether or not a given profile has been disconnected because, while the short-range wireless communication apparatus (100) performs a connection of the given profile between the apparatus (100) and the other short-range wireless communication apparatus (200), the short-range wireless communication apparatus (100) has rejected the connection request of another profile made by the other short-range wireless communication apparatus (200); and a communication re-connecting unit (101) for establishing a re-connection of the given profile between the apparatus (100) and the other short-range wireless communication apparatus (200) on the basis of the fact that the communication disconnection detecting unit (101) has detected that the given profile has been disconnected.

Description

Near field communication device Cross-reference of related applications

This application claims priority based on Japanese Patent Application No. 2010-113196 filed on May 17, 2010 and Japanese Patent Application No. 2010-210304 filed on September 20, 2010. The description is cited by reference.

The present invention relates to a short-range wireless communication apparatus that can simultaneously connect a plurality of profiles to another short-range wireless communication apparatus that is a connection partner.

As a near field communication device, a BT communication device having a Bluetooth (registered trademark, hereinafter abbreviated as BT) communication function is known. For example, as in the techniques described in Patent Documents 1 to 3, a plurality of profiles defined in the BT communication standard can be connected simultaneously to another BT communication apparatus that is a connection partner (so-called multi-profile connection is possible). A BT communication apparatus is known. The profile means a communication protocol defined for each function.

Japanese Published Patent Publication No. 2007-281852 Japanese published patent publication 2007-158670 (corresponding to US published patent publication 200701129116) Japanese Published Patent Publication No. 2008-53805 (corresponding to US Published Patent Publication No. 20080051156)

The present inventor has found the following regarding the short-range wireless communication device.
If, for example, an HFP (Hands-Free Profile) or the like is connected to a BT communication device of a connection partner among the BT communication devices capable of multi-profile connection, for example, A2DP (Advanced
There is a BT communication apparatus that is trying to connect an Audio Distribution Profile) or the like. Hereinafter, a BT communication device to which A2DP or the like is to be connected is referred to as a first BT communication device, and a BT communication device connected to the first BT communication device is referred to as a second BT communication device.

The first BT communication device transmits an A2DP connection request while the HFP is connected to the second BT communication device of the connection partner, and if the A2DP connection request is not accepted by the second BT communication device, The connected HFP is disconnected. Hereinafter, such disconnection of the profile (HFP) is referred to as “problem operation”.

This “problem behavior” will be explained in detail. When the second BT communication apparatus connects the HFP to the first BT communication apparatus that performs the problem operation, the first BT communication apparatus that performs the problem operation transmits an A2DP connection request to the second BT communication apparatus. Here, if the second BT communication apparatus does not accept the A2DP connection request due to its specifications, or cannot accept the A2DP connection request due to lack of resources, the first BT performs the above problem operation. The communication apparatus disconnects the HFP that was connected before transmitting the A2DP connection request regardless of the user's intention, and the state in which the HFP connection remains disconnected is maintained.

The present invention has been made in view of the above circumstances, and its purpose is to prevent the connection of the connected profile from being disconnected regardless of the user's intention and maintaining the disconnected state. An object of the present invention is to provide a short-range wireless communication device capable of performing the above.
According to a first aspect of the present invention, there is provided a short-range wireless communication apparatus capable of simultaneously connecting a plurality of profiles with another short-range wireless communication apparatus that is a connection partner, the communication disconnection detecting unit, Provided is a short-range wireless communication device including a connection unit. The communication disconnection detection unit may receive another request from the other short-range wireless communication device while the short-range wireless communication device is connecting a predetermined profile with the other short-range wireless communication device. It is detected whether or not the connection of the predetermined profile is disconnected due to the fact that the short-range wireless communication apparatus has not accepted the profile connection request. The communication reconnection unit transmits the predetermined profile with the other short-range wireless communication device based on the fact that the connection of the predetermined profile is detected by the communication disconnection detection unit. Reconnect.
In the above-described configuration as the short-range wireless communication device, the short-range wireless communication device is connected to the short-range wireless communication device from the other short-range wireless communication device while the predetermined profile is connected to the other short-range wireless communication device. Whether or not the connection of the predetermined profile has been disconnected because the connection request of another profile requested to the wireless communication apparatus has not been accepted (that is, the connection of the predetermined profile connected by the user Whether or not the communication is disconnected is detected by the communication disconnection detection unit. Then, based on the fact that the connection disconnection of the predetermined profile is detected by the communication disconnection detection unit, the predetermined profile is reconnected by the communication reconnection unit. As a result, it is possible to prevent the disconnected state from being maintained when the connection of the connected profile is disconnected regardless of the intention of the user.
According to a second aspect of the present invention, a short-range wireless communication device capable of simultaneously connecting a plurality of profiles with another short-range wireless communication device that is a connection partner, the connection request holding unit and connection request acceptance A short-range wireless communication device comprising a unit is provided. The connection request receiving unit is configured when the short-range wireless communication apparatus does not accept a connection request for another profile requested while a predetermined profile is connected to the other short-range wireless communication apparatus. Suspends accepting the connection request of the other profile once based on the request for the connection of the other profile from the other short-range wireless communication device that disconnects the connection of the predetermined profile. The connection request accepting unit secures resources necessary for connecting the another profile while the connection request holding unit holds the connection request of the another profile pending, and then receives the other profile. Accept the connection request.
In the above configuration as a short-range wireless communication device, when the short-range wireless communication device receives a connection request for another profile from another short-range wireless communication device, the short-range wireless communication device does not accept the connection request for the other profile. Rather, it suspends accepting another profile connection request. Therefore, the other short-range wireless communication device does not disconnect the predetermined profile connected to the short-range wireless communication device during the suspension. The short-range wireless communication device is required to connect another profile while holding a connection request for another profile, in other words, while a predetermined profile is connected. Secure resources and accept the connection request of another profile after securing the resources. Therefore, another profile is connected without disconnecting the predetermined profile. In this way, it is possible to prevent the connection of the connected profile from being disconnected regardless of the user's intention. Therefore, according to the above configuration, since the connection of the connected profile is not disconnected regardless of the user's intention, it is possible to prevent the disconnected state from being maintained. .

The above and other objects, configurations, and advantages of the present invention will become more apparent from the following detailed description with reference to the accompanying drawings. In the drawing
FIG. 1 is a block diagram showing a configuration of an in-vehicle device and a configuration of a mobile phone in the short-range wireless communication device according to the first embodiment. FIG. 2 is a sequence diagram illustrating an example of operations of the in-vehicle device and the mobile phone according to the first embodiment. FIG. 3 is a block diagram illustrating a configuration of a portable device in the short-range wireless communication device according to the second embodiment. FIG. 4 is a sequence diagram illustrating an example of operations of the in-vehicle device and the mobile phone according to the second embodiment. FIG. 5 is a sequence diagram illustrating an example of operations of the in-vehicle device and the mobile phone according to the third embodiment.

(First embodiment)
A short-range wireless communication apparatus according to the first embodiment will be described with reference to FIGS. 1 and 2. In the present embodiment, the short-range wireless communication device is embodied as a BT-compatible in-vehicle device 100 having a Bluetooth (registered trademark) (hereinafter abbreviated as BT) communication function. A case will be described in which a BT-compatible mobile phone 200 having a BT communication function is brought into a vehicle interior of a vehicle (not shown) that is mounted, and the in-vehicle device 100 and the mobile phone 200 are in a state capable of BT communication. Note that the BT-compatible mobile phone 200 corresponds to “another short-range wireless communication device”.

As shown in FIG. 1, the in-vehicle device 100 includes a control unit 101, a BT communication unit 102, an audio processing unit 103, a microphone 104, an audio amplifier 105, speakers 106 and 107, a tuner deck 108, The storage unit 109, the display control unit 110, the display device 111, the touch operation input unit 112, and the touch operation input device 113 are configured.

The control unit 101 includes a CPU (Central Processing Unit), a RAM (Random Access), and a known microcomputer.
Memory), ROM (Read-only Memory), I / O (Input / Output) bus, and the like, and controls overall operations such as communication operation and data management operation of the in-vehicle device 100.

The BT communication unit 102 is connected to the control unit 101 and is controlled by the control unit 101 to perform BT communication with the mobile phone 200. The BT communication unit 102 is an HFP (Hands Free Profile) that defines a hands-free call as a plurality of profiles defined in the BT communication standard, and an A2DP (Advanced) that defines packet transfer of music streaming data.
Audio
Distribution Profile) can be connected at the same time (so-called multi-profile connection is possible). Note that these HFP and A2DP mean communication protocols defined for each function. HFP corresponds to “predetermined profile”, and A2DP corresponds to “another profile”.

The audio processing unit 103 is connected to the microphone 104 and the audio amplifier 105. Among these, the microphone 104 is composed of a well-known microphone, and is disposed in a part of the vehicle interior where it is easy to collect voices uttered by the user, such as in the vicinity of the steering wheel. The audio amplifier 105 includes two speakers 106 and 107 that are publicly known speakers.

In addition, the voice processing unit 103 is connected to the control unit 101 and the BT communication unit 102, and while the BT communication unit 102 connects the HFP with the mobile phone 200, the voice uttered by the user is the microphone 104. Is input as transmission voice data, the input transmission voice data is subjected to voice processing and output to the BT communication unit 102, while when reception voice data is input from the BT communication unit 102, the input is performed. The received voice data is output to the audio amplifier 105.

Also, the audio processing unit 103 has a function of accumulating streaming data and a function of reproducing the streaming data. When the audio processing unit 103 receives streaming data transmitted from the mobile phone 200 while the BT communication unit 102 connects the A2DP to the mobile phone 200, the audio processing unit 103 stores the received streaming data and stores the stored streaming data. Data is reproduced and output to the audio amplifier 105.

The audio amplifier 105 is connected to the audio processing unit 103. When received voice data or music streaming data is input from the audio processing unit 103, the received received voice data or music streaming data is amplified and the speaker is amplified. Output from 106 and 107. The audio amplifier 105 is also connected to the tuner deck 108. For example, when a music sound reproduced from a recording medium for music or a radio program received from a radio broadcasting station is input from the tuner deck 108, these inputs are input. The music sound and radio program that have been played are amplified and output from the speakers 106 and 107.

The storage unit 109 is configured to be able to store various types of data. For example, telephone book data indicating correspondence between a telephone number and a registered name, an outgoing operation from the in-vehicle device 100, or an HFP connected to the in-vehicle device 100 Call history data indicating the correspondence between the call origination time associated with the call origination operation from the mobile phone 200 that is being operated and the call origination phone number, the call arrival time associated with the call termination operation of the mobile phone 200 connected to the in-vehicle device 100 Incoming call history data indicating the correspondence between the call number and the incoming phone number can be stored. The storage unit 109 is connected to the control unit 101, and the control unit 101 reads and writes the various data as appropriate.

The display control unit 110 is connected to the control unit 101 and a display device 111 that displays various images on the screen. When a display command notification is input from the control unit 101, the display control unit 110 displays based on the input display command notification. The display operation of the device 111 is controlled.

The touch operation input unit 112 is connected to the control unit 101 and the touch operation input device 113 that forms a touch switch on the screen, and touch operation input according to the user operating the touch switch formed on the screen. When an operation detection notification is input from the device 113, the input operation detection notification is output to the control unit 101, and the control unit 101 analyzes the operation detection notification input from the touch operation input unit 112.

As shown in FIG. 1, the mobile phone 200 includes a control unit 201, a telephone communication unit 202, a BT communication unit 203, a key input unit 204, a storage unit 205, a display unit 206, a microphone 207, And a speaker 208.

The control unit 201 includes a CPU, a RAM, a ROM, an I / O bus, and the like that are well-known microcomputers, and controls the overall operation of the mobile phone 200.

The telephone communication unit 202 is connected to the control unit 201 and is controlled by the control unit 201 to perform telephone communication with a communication network (not shown). This communication network includes facilities for providing a well-known mobile phone communication service such as a mobile phone base station and a base station control device.

The BT communication unit 203 is connected to the control unit 201, and is controlled by the control unit 201 to perform BT communication with the in-vehicle device 100. Similarly to the BT communication unit 102, the BT communication unit 203 can simultaneously connect HFP, A2DP, and the like as a plurality of profiles defined by the BT communication standard (so-called multi-profile connection is possible).

The key input unit 204 is connected to the control unit 201 and includes various keys operated by the user. When various keys are operated by the user, the key input unit 204 outputs a signal corresponding to the operated key to the control unit 201.

The storage unit 205 is configured to be able to store various types of data, and stores various types of data such as telephone book data indicating correspondence between telephone numbers and registered names, and streaming data received from the communication network by the telephone communication unit 202, for example. . The storage unit 205 is connected to the control unit 201, and various data is appropriately read or written by the control unit 201.

The display unit 206 is connected to the control unit 201. When a display command notification is input from the control unit 201, the display unit 206 displays various images based on the input display command notification.

The microphone 207 includes a known microphone and is connected to the control unit 201. The speaker 208 is a known speaker and is connected to the control unit 201. The control unit 201 transmits streaming data stored in the storage unit 205 to the in-vehicle device 100 while the BT communication unit 203 connects the A2DP to the in-vehicle device 100.

By the way, when the mobile phone 200 is connected to the in-vehicle device 100 that is the connection partner, there is a mobile phone 200 that further attempts to connect the A2DP (in other words, the mobile phone 200 includes the in-vehicle device that is the connection partner. If it is possible to connect a profile with the device 100, there is one that tries to connect all the profiles that can be connected). In addition, the mobile phone 200 transmits an A2DP connection request while the HFP is connected to the in-vehicle device 100, and if the A2DP connection request is not accepted, the mobile phone 200 establishes the connection of the previously connected HFP. Some will cut. The operation of disconnecting the HFP connection has already been described as “problem operation” in the problem column.

Further, in the present embodiment, the in-vehicle device 100 connects only the profile requested to the other short-range wireless communication device, and the connection of the profile requested from the other short-range wireless communication device to the in-vehicle device 100. Has a specification that does not accept the request. Specifically, when the in-vehicle device 100 transmits a profile connection request from the in-vehicle device 100 to the mobile phone 200 and receives a profile connection response from the mobile phone 200, the in-vehicle device 100 performs a profile with the mobile phone 200. Connect. However, when receiving the profile connection request from the mobile phone 200, the in-vehicle device 100 rejects the received profile connection request without accepting the received profile connection request and transmits a profile rejection response to the mobile phone 200. Do not connect the profile with.

When the in-vehicle apparatus 100 according to the present embodiment having such specifications connects the HFP with the mobile phone 200 that performs the above-described problem, the following situation may occur. Hereinafter, a description will be given with reference to FIG.

As shown in FIG. 2, the in-vehicle device 100 first transmits an HFP connection request to the mobile phone 200 as the process of step S <b> 101. The mobile phone 200 that has received the HFP connection request accepts the HFP connection request without rejecting it, and transmits an HFP connection response (Accepted) to the in-vehicle device 100 as the processing of the subsequent step S102. The in-vehicle device 100 that has received the HFP connection response enters the HFP connection state with the mobile phone 200 as the process of subsequent step S103.

Here, when the mobile phone 200 connects the HFP to the in-vehicle device 100, it further tries to connect the A2DP. Therefore, the cellular phone 200 transmits a service inquiry for confirming whether or not the A2DP service is supported to the in-vehicle device 100 as the process of step S104. Since the in-vehicle device 100 supports the A2DP service, when a service inquiry is received from the mobile phone 200, a service inquiry response indicating that the A2DP service is present is transmitted to the mobile phone 200 as processing of the subsequent step S 105. To do. Then, when the mobile phone 200 receives a service inquiry response indicating that the A2DP service is present from the in-vehicle device 100, the mobile phone 200 transmits an A2DP connection request to the in-vehicle device 100 as a process of subsequent step S106.

However, since the in-vehicle device 100 has the above specifications, the in-vehicle device 100 rejects the A2DP connection request received from the mobile phone 200 without accepting it, and in the subsequent step S107, the mobile phone 200 rejects the A2DP rejection response (Not に 対 し accepted). Send. Then, since the cellular phone 200 receives the A2DP rejection response from the in-vehicle device 100 (that is, the A2DP connection request has not been accepted), the mobile phone 200 requests the in-vehicle device 100 to disconnect the HFP as the process of step S108. Send (problem behavior).

As a result, the in-vehicle device 100 transmits an HFP disconnection response (Accepted) to the mobile phone 200 as the processing of the subsequent step S109, and the mobile phone 200 makes the connection of the HFP that has been connected to the user's intention. Therefore, the HFP is disconnected and the state where the HFP connection is disconnected is maintained. Incidentally, in the prior art, the processing up to step S109 above the broken line shown in FIG.

Therefore, in the present embodiment, in-vehicle device 100 (specifically, control unit 101) did not accept the A2DP connection request transmitted from mobile phone 200 while HFP was connected to mobile phone 200. Therefore, it is detected whether or not the HFP connection is disconnected regardless of the user's intention, and when it is detected that the HFP is disconnected, the HFP is reconnected to the mobile phone 200; did.

Specifically, the control unit 101 detects that the in-vehicle device 100 does not accept the A2DP connection request transmitted from the mobile phone 200, that is, the in-vehicle device 100 sends an A2DP rejection response (Not The elapsed time is started from the point of time when “accepted” is transmitted, and the HFP is disconnected from the mobile phone 200 before the elapsed time elapses for a predetermined time (eg, “100 [milliseconds]”). In other words, when the in-vehicle device 100 transmits an HFP disconnection response to the mobile phone 200 as the process of step S109, the HFP is reconnected to the mobile phone 200. Note that the timing process of the control unit 101 and the processes of steps S107 and 109 correspond to communication disconnection detection means (communication disconnection detection unit).

In this way, when it is detected that the HFP connection has been disconnected regardless of the user's intention, the in-vehicle device 100 transmits an HFP connection request to the mobile phone 200 as the processing of the subsequent step S110. The mobile phone 200 that has received the HFP connection request accepts the HFP connection request without rejecting it, and transmits an HFP connection response (Accepted) to the in-vehicle device 100 as the processing of the subsequent step S111. The in-vehicle device 100 that has received the HFP connection response enters the HFP connection state with the mobile phone 200 as the process of subsequent step S112. Note that the processing of steps S110 to S112 of the control unit 101 corresponds to communication reconnection means (communication reconnection unit).

As described above, when the mobile phone 200 reconnects the HFP to the in-vehicle device 100, it further tries to connect the A2DP. Therefore, the cellular phone 200 transmits a service inquiry for confirming whether or not the A2DP service is supported to the in-vehicle device 100 as the process of step S113. Since the in-vehicle device 100 supports the A2DP service, when a service inquiry is received from the mobile phone 200, a service inquiry response indicating that the A2DP service is present is transmitted to the mobile phone 200 as the processing of the subsequent step S114. To do. When the mobile phone 200 receives a service inquiry response indicating that the A2DP service is present from the in-vehicle device 100, the mobile phone 200 transmits an A2DP connection request to the in-vehicle device 100 as a process in subsequent step S115.

Here, if the in-vehicle device 100 does not accept the A2DP connection request due to the above specifications, the reconnected HFP connection is disconnected again by the mobile phone 200 regardless of the user's intention. As a result, disconnection that is not made by the user's intention to connect the HFP that has been connected and reconnection of the disconnected HFP are repeated.

Therefore, in the present embodiment, the in-vehicle device 100 (specifically, the control unit 101), after reconnecting the HFP with the mobile phone 200, with respect to the mobile phone 200 that executes the “problem operation” described above, When an A2DP connection request is requested again from the telephone 200, the request is accepted.

Specifically, when the in-vehicle device 100 receives an A2DP connection request from the mobile phone 200, the in-vehicle device 100 accepts the A2DP connection request without rejecting it, and in the subsequent step S116, the mobile phone 200 responds to the A2DP connection response. Send (Accepted). And the vehicle equipment 100 will be in the connection state of HF and A2DP between the mobile telephones 200 as a process of following step S117. Note that the process of step S116 of the control unit 101 corresponds to a communication reconnection unit (communication reconnection unit).

In the first embodiment described above, the in-vehicle device 100 starts measuring the elapsed time with reference to the time point when the A2DP rejection response is transmitted to the mobile phone 200 (S107), and the elapsed time passes a predetermined time. When an HFP disconnection response is transmitted to the mobile phone 200 before (S109), the HFP is reconnected to the mobile phone 200 (S110 to S112). Thereby, it becomes possible to detect disconnection that does not depend on the user's intention of connecting the HFP that has been connected with a simple configuration that only measures the time, and the connection of the HFP that has been connected can be detected by the user's intention. When it is cut without any problems, it is possible to prevent the state of being cut off from being maintained.

Moreover, in 1st Embodiment, the vehicle-mounted apparatus 100 connects only the profile requested | required with respect to the other near field communication apparatus, and the profile requested | required with respect to the said vehicle apparatus 100 from the other near field communication device However, the mobile phone 200 that performs the “problem operation” is connected to the A2DP from the mobile phone 200 after reconnecting the HFP to the mobile phone 200. When the request is requested again, the request is accepted (S116). As a result, the reconnected HFP connection is not disconnected again by the mobile phone 200, so that the disconnection of the connected HFP connection not intended by the user and the reconnection of the disconnected HFP are not repeated. .

(Second Embodiment)
Next, a short-range wireless communication apparatus according to the second embodiment will be described with reference to FIGS.

In the present embodiment, as in the first embodiment, the short-range wireless communication device is a BT-compatible in-vehicle device 100 having a Bluetooth (registered trademark) (hereinafter abbreviated as BT) communication function. The BT-compatible mobile phone 200 having the BT communication function and the BT-compatible portable device 300 having the BT communication function are brought into the vehicle interior of the vehicle (not shown) on which the in-vehicle device 100 is mounted. A case where the in-vehicle device 100, the mobile phone 200, and the mobile device 300 are in a state where BT communication is possible will be described.

Further, in the present embodiment, the in-vehicle device 100 connects only the profile requested to the other short-range wireless communication device, and the connection of the profile requested from the other short-range wireless communication device to the in-vehicle device 100. If the specification does not accept the request but the resource is insufficient, the connection of the profile requested from another short-range wireless communication device is not accepted.

Hereinafter, detailed description will be made mainly on parts different from the first embodiment. As illustrated in FIG. 3, the portable device 300 includes a control unit 301, a BT communication unit 302, a storage unit 303, a display unit 304, an operation unit 305, and a speaker 306.

The control unit 301 includes a CPU, a RAM, a ROM, an I / O bus, and the like that are well-known microcomputers, and controls the overall operation of the portable device 300.

The BT communication unit 302 is connected to the control unit 301, and is controlled by the control unit 301 to perform BT communication with the in-vehicle device 100. The BT communication unit 302 can connect A2DP or the like as a plurality of profiles defined by the BT communication standard.

The storage unit 303 is configured to be able to store various data such as streaming data, for example. The storage unit 303 is connected to the control unit 301, and various data are appropriately read out by the control unit 301.

The display unit 304 is connected to the control unit 301, and when a display command notification is input from the control unit 301, displays various images based on the input display command notification.

The operation unit 305 is connected to the control unit 301 and includes, for example, a push button operated by the user. When the push button is operated by the user, the operation unit 305 outputs a signal corresponding to the operated push button to the control unit 301.

The speaker 306 is composed of a known speaker and is connected to the control unit 301.

The control unit 301 transmits streaming data stored in the storage unit 303 to the in-vehicle device 100 while the BT communication unit 302 connects the A2DP to the in-vehicle device 100. In addition, when the BT communication unit 302 is not connected to the in-vehicle device 100 with the A2DP, the control unit 301 reproduces the streaming data stored in the storage unit 303 and outputs it from the speaker 306.

By the way, the mobile phone 200 performs the “problem operation” as in the first embodiment. Further, in the present embodiment, the in-vehicle device 100 connects only the profile requested to the other short-range wireless communication device, and the connection of the profile requested from the other short-range wireless communication device to the in-vehicle device 100. If the specification does not accept the request but the resource is insufficient, the connection of the profile requested from another short-range wireless communication device is not accepted. Specifically, when the in-vehicle device 100 receives a profile connection request from the mobile phone 200 or the portable device 300, the in-vehicle device 100 checks the remaining amount of resources of the in-vehicle device 100, and if the resource is insufficient, If there is no resource for connecting the requested profile, a profile rejection response (Not accepted) is transmitted to the mobile phone 200 or the mobile device 300.

When the in-vehicle device 100 according to the present embodiment makes an HFP connection with the mobile phone 200 that performs the above-described operation, the following situation may occur. Hereinafter, a description will be given with reference to FIG.

As shown in FIG. 4, it is assumed that the in-vehicle device 100 is already in an A2DP connection state with the mobile device 300 (processing in step S201), and in this state, the in-vehicle device 100 is connected to the mobile phone 200. It is assumed that an HFP connection request has been transmitted (processing in step S202).

At this time, the mobile phone 200 that has received the HFP connection request accepts the HFP connection request without rejecting it, and transmits an HFP connection response (Accepted) to the in-vehicle device 100 as the processing of the subsequent step S203. The in-vehicle device 100 that has received the HFP connection response enters the HFP connection state with the mobile phone 200 as the process of subsequent step S204.

Here, when the mobile phone 200 connects the HFP to the in-vehicle device 100, it further tries to connect the A2DP. Therefore, the cellular phone 200 transmits a service inquiry for confirming whether or not the A2DP service is supported to the in-vehicle device 100 as the process of step S205. Since the in-vehicle device 100 supports the A2DP service, when a service inquiry is received from the mobile phone 200, a service inquiry response indicating that the A2DP service is present is transmitted to the mobile phone 200 as processing of the next step S206. To do. Then, when the mobile phone 200 receives a service inquiry response indicating that the A2DP service is present from the in-vehicle device 100, the mobile phone 200 transmits an A2DP connection request to the in-vehicle device 100 as the process of subsequent step S207.

However, since the in-vehicle device 100 has already connected the portable device 300 to the A2DP and there is no resource for newly connecting the A2DP, the in-vehicle device 100 cannot accept the A2DP connection request received from the mobile phone 200 and rejects it. In step S208, an A2DP rejection response (NotＤＰaccepted) is transmitted to the mobile phone 200. Then, since the cellular phone 200 receives the A2DP rejection response from the in-vehicle device 100 (that is, the A2DP connection request has not been accepted), the mobile phone 200 requests the in-vehicle device 100 to disconnect the HFP as the process of step S209. (Problem behavior).

As a result, the in-vehicle device 100 transmits an HFP disconnection response (Accepted) to the mobile phone 200 as the processing of the subsequent step S210, and the mobile phone 200 makes the connection of the HFP that has been connected to the user's intention. Therefore, the HFP is disconnected and the state where the HFP connection is disconnected is maintained. Further, the in-vehicle device 100 remains in the A2DP connection state with the portable device 300 (processing in step S211). Incidentally, in the prior art, the processing up to step S211 above the broken line shown in FIG.

Therefore, in the present embodiment, in-vehicle device 100 (specifically, control unit 101) did not accept the A2DP connection request transmitted from mobile phone 200 while HFP was connected to mobile phone 200. Therefore, it is detected whether or not the HFP connection is disconnected regardless of the user's intention, and when it is detected that the disconnection is detected, after securing resources necessary for connecting the A2DP, The HFP is reconnected to the mobile phone 200.

Specifically, the control unit 101 detects that the in-vehicle device 100 does not accept the A2DP connection request transmitted from the mobile phone 200, that is, the in-vehicle device 100 sends an A2DP rejection response (Not Elapsed time starts based on the time when (accepted) is transmitted. If the HFP connection with the mobile phone 200 is disconnected before a predetermined time (for example, “100 [milliseconds]”) elapses, that is, the in-vehicle device 100 performs the process of step S210 as a mobile phone. When an HFP disconnection response is transmitted to the mobile phone 200, resources necessary for connecting the A2DP to the mobile phone 200 are secured by disconnecting the A2DP connection that was connected to the mobile device 300. After that, the HFP is reconnected to the mobile phone 200.

Specifically, the control unit 101 transmits an A2DP disconnection request to the portable device 300 as the process of subsequent step S212. As a result, the portable device 300 that has received the A2DP connection request accepts the A2DP disconnection request without rejecting it, and transmits an A2DP disconnection response (Accepted) to the in-vehicle device 100 as the processing of the subsequent step S213. The A2DP connection between the in-vehicle device 100 and the portable device 300 is disconnected, and the resources of the in-vehicle device 100 are secured. Note that the processing in step S212 of the control unit 101 corresponds to communication reconnection means (communication reconnection unit).

When the resources of the in-vehicle device 100 are ensured in this way, the in-vehicle device 100 transmits an HFP connection request to the mobile phone 200 as the process of subsequent step S214. The mobile phone 200 that has received the HFP connection request accepts the HFP connection request without rejecting it, and transmits an HFP connection response (Accepted) to the in-vehicle device 100 as the processing of the next step S215. The in-vehicle device 100 that has received the HFP connection response enters the HFP connection state with the mobile phone 200 as the process of subsequent step S216. Note that the processing in steps S214 to S216 of the control unit 101 corresponds to communication reconnection means (communication reconnection unit).

As described above, when the mobile phone 200 reconnects the HFP to the in-vehicle device 100, it further tries to connect the A2DP. Therefore, the cellular phone 200 transmits a service inquiry for confirming whether or not the A2DP service is supported to the in-vehicle device 100 as the process of step S217. Since the in-vehicle device 100 supports the A2DP service, when a service inquiry is received from the mobile phone 200, a service inquiry response indicating that the A2DP service is present is transmitted to the mobile phone 200 as the processing of subsequent step S218. To do. Then, when the mobile phone 200 receives a service inquiry response indicating that the A2DP service is present from the in-vehicle device 100, the mobile phone 200 transmits an A2DP connection request to the in-vehicle device 100 as a process of subsequent step S219.

When the in-vehicle device 100 receives the A2DP connection request from the mobile phone 200, the resources necessary for connecting the A2DP to the mobile phone 200 are secured, so that the A2DP connection request is not rejected. Acceptance, and in the subsequent step S220, an A2DP connection response (Accepted) is transmitted to the mobile phone 200. And the vehicle-mounted apparatus 100 will be in the connection state of HFP and A2DP between the mobile telephones 200 as a process of subsequent step S221.

Note that the in-vehicle device 100 according to the present embodiment gives priority to connecting the HFP over connecting the A2DP to the mobile phone 200 or the mobile device 300.

In the second embodiment described above, as in the first embodiment, the in-vehicle device 100 sets the elapsed time with reference to the time point when the A2DP rejection response is transmitted to the mobile phone 200 (S208). If the HFP disconnection response is transmitted to the mobile phone 200 before the time has elapsed and the predetermined time has elapsed (S210), the HFP is reconnected to the mobile phone 200 ( S214 to S216). Thereby, it becomes possible to detect disconnection that is not the intention of the user of the connected HFP with a simple configuration that only measures time, and the connection of the connected HFP is disconnected not by the intention of the user. In this case, it is possible to prevent the disconnected state from being maintained.

In the second embodiment, in-vehicle device 100 does not accept connection of a profile requested from another short-range wireless communication device when resources are insufficient, and connects A2DP. The HFP is reconnected to the mobile phone 200 after securing necessary resources. If the HFP is reconnected without securing the resources necessary to connect the A2DP with the mobile phone 200, disconnection that is not the intention of the connected HFP user and reconnection of the disconnected HFP are repeated. However, since the HFP is reconnected with the mobile phone 200 after securing the resources necessary to connect the A2DP, the reconnection of the HFP is not disconnected again by the mobile phone 200. The disconnection not based on the intention of the connected HFP user and the reconnection of the disconnected HFP are not repeated.

(Third embodiment)
Next, a short-range wireless communication apparatus according to the third embodiment will be described with reference to FIG.

In this embodiment, as in the first and second embodiments, the short-range wireless communication device has a Bluetooth (registered trademark) (hereinafter abbreviated as BT) communication function. It is embodied as a BT-compatible in-vehicle device 100 having a BT-compatible mobile phone 200 having a BT communication function and a BT-compatible function having a BT communication function in a vehicle interior of a vehicle (not shown) on which the in-vehicle device 100 is mounted. A case will be described in which the mobile device 300 is brought in and the in-vehicle device 100, the mobile phone 200, and the mobile device 300 are in a state capable of BT communication.

In the present embodiment, the cellular phone 200 performs “problem operation” as in the first embodiment.

In the present embodiment, as in the second embodiment, the in-vehicle device 100 connects only the requested profile to another short-range wireless communication device, and the other short-range wireless communication device The in-vehicle device 100 does not have a specification that does not accept a connection request for the requested profile. However, unlike the second embodiment, in-vehicle device 100 suspends accepting connection requests for profiles requested from other short-range wireless communication devices when resources are insufficient. After securing the resources during the hold, the connection request for the profile requested from another short-range wireless communication device is accepted. Specifically, when the in-vehicle device 100 receives a profile connection request from the mobile phone 200 or the portable device 300, the in-vehicle device 100 checks the remaining amount of resources of the in-vehicle device 100, and if the resource is insufficient, When there is no resource for connecting the requested profile, a pending response (Pending) for holding the acceptance of the profile is transmitted to the mobile phone 200 or the mobile device 300.

Hereinafter, description will be given with reference to FIG. As shown in FIG. 5, it is assumed that the in-vehicle device 100 is already in an A2DP connection state with the portable device 300 (processing in step S301). It is assumed that an HFP connection request has been transmitted (processing in step S302).

At this time, the mobile phone 200 that has received the HFP connection request accepts the HFP connection request without rejecting it, and transmits an HFP connection response (Accepted) to the in-vehicle device 100 as the processing of the subsequent step S303. The in-vehicle device 100 that has received the HFP connection response enters the HFP connection state with the mobile phone 200 as the process of subsequent step S304.

Here, when the mobile phone 200 connects the HFP to the in-vehicle device 100, it further tries to connect the A2DP. Therefore, the cellular phone 200 transmits a service inquiry for confirming whether or not the A2DP service is supported to the in-vehicle device 100 as the process of step S305. Since the in-vehicle device 100 supports the A2DP service, when a service inquiry is received from the mobile phone 200, a service inquiry response indicating that the A2DP service is present is transmitted to the mobile phone 200 as processing of the next step S306. To do. Then, when the mobile phone 200 receives a service inquiry response indicating that the A2DP service is present from the in-vehicle device 100, the mobile phone 200 transmits an A2DP connection request to the in-vehicle device 100 as a process of subsequent step S307.

In the second embodiment shown in FIG. 4, the in-vehicle device 100 has already connected the portable device 300 to the A2DP, and there is no resource for newly connecting the A2DP. The connection request of A2DP received from 200 cannot be accepted and rejected, and as a process of subsequent step S208, an A2DP rejection response (Not accepted) is transmitted to the mobile phone 200. Then, since the cellular phone 200 receives the A2DP rejection response from the in-vehicle device 100 (that is, the A2DP connection request has not been accepted), the mobile phone 200 requests the in-vehicle device 100 to disconnect the HFP as the process of step S209. Was sent (problem behavior).

As a result, the in-vehicle device 100 transmits an HFP disconnection response (Accepted) to the mobile phone 200 as the processing of the subsequent step S210, and the mobile phone 200 makes the connection of the HFP that has been connected to the user's intention. Cut regardless. Thus, in the second embodiment, the HFP connection between the in-vehicle device 100 and the mobile phone 200 is disconnected for a short time.

Therefore, in the present embodiment, the in-vehicle device 100 (specifically, the control unit 101) accepts an A2DP connection request transmitted from the mobile phone 200 while the HFP is connected to the mobile phone 200. After holding, after securing the resources necessary to connect the A2DP with the mobile phone 200 by disconnecting the A2DP already connected with the mobile device 300 during the hold, The A2DP connection request transmitted from the mobile phone 200 is accepted. Note that the A2DP connected to the portable device 300 corresponds to a profile connected to other than a predetermined profile.

Specifically, when the control unit 101 receives the A2DP connection request transmitted from the mobile phone 200, the control unit 101 checks the remaining amount of the resource of the in-vehicle device 100, that is, if the resource is insufficient, that is, is requested. If there is no resource to connect the received profile, the acceptance of the A2DP connection request is suspended, and a pending response (Pending) indicating suspension is transmitted to the mobile phone 200 as processing of step S308. The mobile phone 200 that has received the A2DP pending response (Pending) does not receive the A2DP rejection response (Not Accepted). The processing related to the connection is temporarily stopped. Note that the processing in step S308 of the control unit 101 corresponds to a connection request holding unit (connection request holding unit).

While holding the acceptance of the A2DP connection request in this manner, the control unit 101 transmits an A2DP disconnect request to the portable device 300 as the process of subsequent step S309. The portable device 300 accepts this A2DP disconnection request without rejecting it, and transmits an A2DP disconnection response (Accepted) to the in-vehicle device 100 as the processing of the subsequent step S310. As a result, the A2DP connection between the in-vehicle device 100 and the portable device 300 is disconnected, and the resources of the in-vehicle device 100 are secured.
When the resources of the in-vehicle device 100 are secured, the in-vehicle device 100 performs the previous step S30.
The A2DP connection request that has been received and accepted in the process 7 is accepted, and an A2DP connection response (Accepted) is transmitted to the mobile phone 200 as the process of step S311. Then, the in-vehicle device 100 enters the HFP and A2DP connection state with the mobile phone 200 as the subsequent processing of step 312. Note that the processing of steps S309 to S311 of the control unit 101 corresponds to connection request receiving means (connection request receiving unit).

In the in-vehicle device 100 of the present embodiment, priority is given to connecting the HFP over connecting the A2DP to the mobile phone 200 or the mobile device 300.

In the third embodiment described above, when the in-vehicle device 100 receives an A2DP connection request from the mobile phone 200 while the HFP is connected to the mobile phone 200, the in-vehicle device 100 temporarily connects the A2DP. Defer accepting requests. While holding, the A2DP that is already connected to the mobile device 300 is disconnected to secure resources necessary for connecting the A2DP to the mobile phone 200, and then the mobile phone 200 The A2DP connection request transmitted from the server is accepted.
Since the mobile phone 200 does not receive the rejection response of A2DP from the in-vehicle device 100, the progress of the process related to the connection of A2DP is temporarily stopped without disconnecting the HFP connected to the in-vehicle device 100. Just hold it. Therefore, according to the above configuration, since the connected HFP is not disconnected regardless of the user's intention, it is possible to prevent the HFP from being kept disconnected. become.

(Mode)
According to the first example of the present disclosure, a short-range wireless communication apparatus capable of simultaneously connecting a plurality of profiles with another short-range wireless communication apparatus that is a connection partner, and a communication reconnection detecting unit and a communication reconnection A short-range wireless communication device comprising a unit. The communication disconnection detection unit may receive another request from the other short-range wireless communication device while the short-range wireless communication device is connecting a predetermined profile with the other short-range wireless communication device. It is detected whether or not the connection of the predetermined profile is disconnected due to the fact that the short-range wireless communication apparatus has not accepted the profile connection request. The communication reconnection unit transmits the predetermined profile with the other short-range wireless communication device based on the fact that the connection of the predetermined profile is detected by the communication disconnection detection unit. Reconnect.
In the above-described configuration as the short-range wireless communication device, the short-range wireless communication device is connected to the short-range wireless communication device from the other short-range wireless communication device while the predetermined profile is connected to the other short-range wireless communication device. Whether or not the connection of the predetermined profile has been disconnected because the connection request of another profile requested to the wireless communication apparatus has not been accepted (that is, the connection of the predetermined profile connected by the user Whether or not the communication is disconnected is detected by the communication disconnection detection unit. Then, based on the fact that the connection disconnection of the predetermined profile is detected by the communication disconnection detection unit, the predetermined profile is reconnected by the communication reconnection unit. As a result, it is possible to prevent the disconnected state from being maintained when the connection of the connected profile is disconnected regardless of the intention of the user.

The short-range wireless communication device may be configured as follows. The communication disconnection detection unit sends a connection request for another profile requested from another short-range wireless communication device while a predetermined profile is connected to the other short-range wireless communication device. The elapsed time starts with the time when the communication device does not accept as a reference, and the connection of the predetermined profile is disconnected when the predetermined profile is disconnected before the predetermined time elapses. To detect. As a result, it becomes possible to detect disconnection of the profile that does not depend on the user's intention, with a simple configuration, for example, including a time counter.

By the way, the short-range wireless communication device connects the requested profile to the other short-range wireless communication device, and the connection request for the profile requested from the other short-range wireless communication device to the short-range wireless communication device is made. In some cases, the specification may not be accepted. If the specification is included, the following situation may occur.
That is, when a predetermined profile is reconnected to another short-range wireless communication device by the communication reconnection unit, another connection request for another profile is requested again from the other short-range wireless communication device. If the short-range wireless communication device does not accept this connection request due to the above specifications, the connection of the reconnected predetermined profile will be disconnected again by another short-range wireless communication device. As a result, disconnection of the connected profile not depending on the user's intention and reconnection of the disconnected profile are repeated.

Therefore, in the above configuration, when the short-range wireless communication device has the above specifications, the communication reconnection unit reconnects a predetermined profile and then connects another profile from another short-range wireless communication device. If the request is requested again, it may be configured to accept the request. As a result, the connection of the re-established profile is not disconnected again by another short-range wireless communication device, so that the disconnection of the connected profile without intention of the user and the re-connection of the disconnected profile are prevented. Connection is no longer repeated.

In addition, the short-range wireless communication device may not accept the connection of the profile requested from another short-range wireless communication device when the resource is insufficient, and if the connection is not accepted, Such a situation may occur.

That is, when a predetermined profile is reconnected to another short-range wireless communication device by the communication reconnection unit, another connection request for another profile is requested again from the other short-range wireless communication device. When the short-range wireless communication device has already connected another profile with another short-range wireless communication device, the short-range wireless communication device may have another short-range wireless communication device due to lack of resources. Unable to accept another profile connection requested by. As described above, if the short-range wireless communication device does not accept a connection request from another short-range wireless communication device due to a shortage of resources, the connection of the reconnected predetermined profile becomes another It is disconnected again by the short-range wireless communication device. As a result, disconnection of the connected profile not depending on the user's intention and reconnection of the disconnected profile are repeated.
Therefore, in the above configuration, when the short-range wireless communication apparatus has the above specifications, the communication reconnection unit is based on the fact that the connection disconnection of the predetermined profile is detected by the communication disconnection detection unit. Then, when connecting another profile, it may be configured to reconnect another profile after securing necessary resources by disconnecting the already connected connection of another profile. As a result, the connection of the re-established profile is not disconnected again by another short-range wireless communication device, so that the disconnection of the connected profile without intention of the user and the re-connection of the disconnected profile are prevented. Connection is no longer repeated.

In addition, according to the second example of the present disclosure, a short-range wireless communication device capable of simultaneously connecting a plurality of profiles with another short-range wireless communication device that is a connection partner, which is connected to the connection request holding unit A short-range wireless communication device including a request receiving unit can be provided. The connection request receiving unit is configured when the short-range wireless communication apparatus does not accept a connection request for another profile requested while a predetermined profile is connected to the other short-range wireless communication apparatus. Suspends accepting the connection request of the other profile once based on the request for the connection of the other profile from the other short-range wireless communication device that disconnects the connection of the predetermined profile. The connection request accepting unit secures resources necessary for connecting the another profile while the connection request holding unit holds the connection request of the another profile pending, and then receives the other profile. Accept the connection request.

In the above configuration as a short-range wireless communication device, when the short-range wireless communication device receives a connection request for another profile from another short-range wireless communication device, the short-range wireless communication device does not accept the connection request for the other profile. Rather, it suspends accepting another profile connection request. Therefore, the other short-range wireless communication device does not disconnect the predetermined profile connected to the short-range wireless communication device during the suspension. The short-range wireless communication device is required to connect another profile while holding a connection request for another profile, in other words, while a predetermined profile is connected. Secure resources and accept the connection request of another profile after securing the resources. Therefore, another profile is connected without disconnecting the predetermined profile. In this way, it is possible to prevent the connection of the connected profile from being disconnected regardless of the user's intention. Therefore, according to the above configuration, since the connection of the connected profile is not disconnected regardless of the user's intention, it is possible to prevent the disconnected state from being maintained. .

In the above configuration, it is desirable to transmit a hold response indicating that a connection request of another profile is to be held to another short-range wireless communication device.

In the above configuration, necessary resources may be secured by disconnecting profiles other than the predetermined profile.

Note that the embodiments, configurations, modes, and the like according to the present invention are not limited to the above-described embodiments, configurations, modes, and the like. Embodiments, configurations, aspects, and the like obtained by appropriately combining technical parts disclosed in different embodiments, configurations, aspects, etc. are also included in the technical scope of the embodiments, structures, aspects, etc. according to the present invention.

Claims (7)

1. In a short-range wireless communication device that can simultaneously connect a plurality of profiles with another short-range wireless communication device (200) that is a connection partner,
   Another profile requested from the other short-range wireless communication device (200) while the short-range wireless communication device is connecting a predetermined profile to the other short-range wireless communication device (200) A communication disconnection detection unit (101) for detecting whether or not the connection of the predetermined profile has been disconnected due to the fact that the short-range wireless communication device has not accepted the connection request;
   Based on the fact that the connection disconnection of the predetermined profile is detected by the communication disconnection detection unit (101), the predetermined profile is re-established with the other short-range wireless communication device (200). A short-range wireless communication device comprising a communication reconnection unit (101) for connection.
2. The short-range wireless communication device according to claim 1,
   The communication disconnection detection unit (101) is requested from the other short-range wireless communication device (200) while a predetermined profile is connected to the other short-range wireless communication device (200). The elapsed time is started from the time point when the short-range wireless communication device does not accept another profile connection request, and the connection of the predetermined profile is disconnected before the elapsed time elapses. A short-range wireless communication device that detects that the connection of the predetermined profile has been disconnected.
3. The short-range wireless communication device according to claim 1 or 2,
   The short-range wireless communication device connects the profile requested to the other short-range wireless communication device (200), and the profile requested from the other short-range wireless communication device (200) to the short-range wireless communication device. Has a specification that does not accept the connection request of
   After the reconnection of the predetermined profile, the communication reconnection unit (101), when a connection request for another profile is requested again from the other short-range wireless communication device (200), Accepting short-range wireless communication device.
4. The short-range wireless communication device according to claim 1 or 2,
   The short-range wireless communication device does not accept connection of the profile requested from the other short-range wireless communication device (200) when the resource is insufficient,
   The communication reconnection unit (101) is a resource necessary for connecting the other profile based on the fact that the connection disconnection of the predetermined profile is detected by the communication disconnection detection unit (101). A short-range wireless communication device that reconnects another profile while ensuring
5. In a short-range wireless communication device that can simultaneously connect a plurality of profiles with another short-range wireless communication device (200) that is a connection partner,
   If the short-range wireless communication apparatus does not accept a connection request for another profile requested while a predetermined profile is connected to the other short-range wireless communication apparatus (200), A connection request for temporarily suspending acceptance of a connection request for another profile based on a request for connection of the other profile from the other short-range wireless communication apparatus (200) that disconnects the profile. A holding section (101);
   The connection request holding unit (101) secures resources necessary for connecting the another profile while holding the connection request of the different profile, and then requests the connection request of the different profile. An incoming connection request accepting unit (101);
   A near field communication device.
6. The short-range wireless communication device according to claim 5,
   The connection request holding unit (101) is a short-range wireless communication device that transmits a hold response indicating that the connection request of the another profile is held to the other short-range wireless communication device.
7. The short-range wireless communication device according to claim 5 or 6,
   The connection request receiving unit (101) is a short-range wireless communication apparatus that secures the necessary resources by disconnecting a profile connected to other than the predetermined profile.
   
   
   
   
   

Images