WO2011145314A1 - 近距離無線通信装置 - Google Patents
近距離無線通信装置 Download PDFInfo
- Publication number
- WO2011145314A1 WO2011145314A1 PCT/JP2011/002692 JP2011002692W WO2011145314A1 WO 2011145314 A1 WO2011145314 A1 WO 2011145314A1 JP 2011002692 W JP2011002692 W JP 2011002692W WO 2011145314 A1 WO2011145314 A1 WO 2011145314A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- short
- wireless communication
- range wireless
- communication device
- profile
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/60—Substation equipment, e.g. for use by subscribers including speech amplifiers
- H04M1/6033—Substation equipment, e.g. for use by subscribers including speech amplifiers for providing handsfree use or a loudspeaker mode in telephone sets
- H04M1/6041—Portable telephones adapted for handsfree use
- H04M1/6075—Portable telephones adapted for handsfree use adapted for handsfree use in a vehicle
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2250/00—Details of telephonic subscriber devices
- H04M2250/02—Details of telephonic subscriber devices including a Bluetooth interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
Definitions
- 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.
- a BT communication device having a Bluetooth (registered trademark, hereinafter abbreviated as BT) communication function As a near field communication device, a BT communication device having a Bluetooth (registered trademark, hereinafter abbreviated as BT) communication function is known.
- BT Bluetooth
- 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.
- a BT communication device to which A2DP or the like is to be connected is referred to as a first BT communication device
- 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.
- problem operation such disconnection of the profile (HFP) is referred to as “problem operation”.
- the first BT communication apparatus that performs the problem operation transmits an A2DP connection request to the second BT communication apparatus.
- 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.
- 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,
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- the 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.
- 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.
- 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.
- BT Bluetooth
- 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.
- the BT-compatible mobile phone 200 corresponds to “another short-range wireless communication device”.
- 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.
- CPU Central Processing Unit
- RAM Random Access
- ROM Read-only Memory
- I / O Input / Output
- 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).
- 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.
- 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.
- 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.
- 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.
- the audio processing unit 103 has a function of accumulating streaming data and a function of reproducing the streaming data.
- 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.
- the received voice data or music streaming data is amplified and the speaker is amplified.
- 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.
- 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.
- 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.
- 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.
- 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.
- the mobile phone 200 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).
- 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.
- 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.
- 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.
- 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.
- the mobile phone 200 transmits an A2DP connection request to the in-vehicle device 100 as a process of subsequent step S106.
- 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).
- 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.
- HFP disconnection response Acceptepted
- in-vehicle device 100 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.
- 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.
- 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).
- 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.
- the processing of steps S110 to S112 of the control unit 101 corresponds to communication reconnection means (communication reconnection unit).
- 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.
- the mobile phone 200 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.
- 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.
- 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,
- the request is accepted.
- step S116 the mobile phone 200 responds to the A2DP connection response.
- Send (Accepted).
- 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.
- the process of step S116 of the control unit 101 corresponds to a communication reconnection unit (communication reconnection unit).
- 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.
- 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).
- the vehicle-mounted apparatus 100 connects only the profile requested
- 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.
- the request is accepted (S116).
- 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. .
- 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.
- BT Bluetooth
- 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.
- 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.
- 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.
- the control unit 301 reproduces the streaming data stored in the storage unit 303 and outputs it from the speaker 306.
- the mobile phone 200 performs the “problem operation” as in the first 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.
- the in-vehicle device 100 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.
- a profile rejection response (Not accepted) is transmitted to the mobile phone 200 or the mobile device 300.
- step S201 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).
- 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.
- 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.
- the mobile phone 200 transmits an A2DP connection request to the in-vehicle device 100 as the process of subsequent step S207.
- step S208 an A2DP rejection response (NotDPaccepted) is transmitted to the mobile phone 200.
- 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).
- 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.
- in-vehicle device 100 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.
- 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.
- a predetermined time for example, “100 [milliseconds]”
- control unit 101 transmits an A2DP disconnection request to the portable device 300 as the process of subsequent step S212.
- 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.
- the processing in step S212 of the control unit 101 corresponds to communication reconnection means (communication reconnection unit).
- 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.
- the processing in steps S214 to S216 of the control unit 101 corresponds to communication reconnection means (communication reconnection unit).
- 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.
- the mobile phone 200 transmits an A2DP connection request to the in-vehicle device 100 as a process of subsequent step S219.
- the in-vehicle device 100 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.
- the in-vehicle device 100 gives priority to connecting the HFP over connecting the A2DP to the mobile phone 200 or the mobile device 300.
- 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-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.
- 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.
- BT Bluetooth (registered trademark)
- the cellular phone 200 performs “problem operation” as in the first 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.
- 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.
- the in-vehicle device 100 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.
- step S301 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).
- 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.
- 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.
- the mobile phone 200 transmits an A2DP connection request to the in-vehicle device 100 as a process of subsequent step S307.
- 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.
- 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).
- 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.
- the HFP connection between the in-vehicle device 100 and the mobile phone 200 is disconnected for a short time.
- 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.
- 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).
- 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.
- 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.
- 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.
- the in-vehicle device 100 enters the HFP and A2DP connection state with the mobile phone 200 as the subsequent processing of step 312.
- the processing of steps S309 to S311 of the control unit 101 corresponds to connection request receiving means (connection request receiving unit).
- priority is given to connecting the HFP over connecting the A2DP to the mobile phone 200 or the mobile device 300.
- the in-vehicle device 100 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.
- 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.
- 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.
- the predetermined profile is reconnected by the communication reconnection unit.
- 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.
- 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.
- 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.
- 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.
- 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.
- the short-range wireless communication device 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.
- 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.
- 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.
- 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.
- the 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.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
Abstract
Description
マルチプロファイル接続可能なBT通信装置の中には、接続相手のBT通信装置との間で例えばHFP(Hands-Free Profile)等を接続すると、さらに例えばA2DP(Advanced
Audio Distribution Profile)等を接続しようとするBT通信装置がある。以下、A2DP等を接続しようとするBT通信装置を第1BT通信装置と呼び、この第1BT通信装置と接続されるBT通信装置を第2BT通信装置と呼ぶ。
本発明の第1の観点によると、接続相手である他の近距離無線通信装置との間で複数のプロファイルを同時に接続可能な近距離無線通信装置であって、通信切断検出部と、通信再接続部とを備える近距離無線通信装置が提供される。前記通信切断検出部は、当該近距離無線通信装置が前記他の近距離無線通信装置との間で所定のプロファイルを接続している間に前記他の近距離無線通信装置から要求された別のプロファイルの接続要求を当該近距離無線通信装置が受け入れなかったことに起因して前記所定のプロファイルの接続が切断されたか否かを検出する。前記通信再接続部は、前記通信切断検出部によって前記所定のプロファイルの接続が切断されたことが検出されたことに基づいて、前記他の近距離無線通信装置との間で前記所定のプロファイルを再接続する。
近距離無線通信装置としての上記構成では、当該近距離無線通信装置が他の近距離無線通信装置との間で所定のプロファイルを接続している間に他の近距離無線通信装置から当該近距離無線通信装置に対し要求された別のプロファイルの接続要求を受け入れなかったことに起因して所定のプロファイルの接続が切断されたか否か(すなわち、接続されていた所定のプロファイルの接続がユーザの意思によらず切断されたか否か)が通信切断検出部によって検出される。そして、通信切断検出部によって所定のプロファイルの接続が切断されたことが検出されたことに基づいて、通信再接続部によって所定のプロファイルが再接続される。これにより、接続されていたプロファイルの接続がユーザの意思によらず切断された場合に、切断されたままの状態が維持されることを防止することができるようになる。
本発明の第2の観点によると、接続相手である他の近距離無線通信装置との間で複数のプロファイルを同時に接続可能な近距離無線通信装置であって、接続要求保留部と接続要求受入部とを備える近距離無線通信装置が提供される。前記接続要求受入部は、前記他の近距離無線通信装置との間で所定のプロファイルを接続している間に要求された別のプロファイルの接続要求を当該近距離無線通信装置が受け入れない場合には前記所定のプロファイルの接続を切断する前記他の近距離無線通信装置から前記別のプロファイルの接続を要求されたことに基づいて、一旦、前記別のプロファイルの接続要求を受け入れることを保留する。前記接続要求受入部は、前記接続要求保留部が前記別のプロファイルの接続要求を受け入れることを保留している間に前記別のプロファイルを接続するに当たり必要なリソースを確保した後、前記別のプロファイルの接続要求を受け入れる。
近距離無線通信装置としての上記構成では、当該近距離無線通信装置は、他の近距離無線通信装置から別のプロファイルの接続要求を受けた場合に、その別のプロファイルの接続要求を受け入れないのではなく、一旦、別のプロファイルの接続要求を受け入れることを保留する。そのため、上記他の近距離無線通信装置は、その保留中、当該近距離無線通信装置との間で接続していた所定のプロファイルを切断しない。そして、当該近距離無線通信装置は、別のプロファイルの接続要求を受け入れることを保留している間に、換言すれば、所定のプロファイルが接続されている間に、別のプロファイルを接続するに必要なリソースを確保し、そのリソースを確保した後に、別のプロファイルの接続要求を受け入れる。したがって、所定のプロファイルの接続が切断されることなく、別のプロファイルが接続されることになる。このようにして、接続されていたプロファイルの接続がユーザの意思によらず切断されることを防止することができるようになる。したがって、上記構成によれば、接続されていたプロファイルの接続がユーザの意思によらず切断されることがなくなるため、切断されたままの状態が維持されることを防止することができるようになる。
第1の実施の形態に係る近距離無線通信装置について、図1及び図2を参照して説明する。なお、本実施の形態では、近距離無線通信装置は、Bluetooth(登録商標)(以下、BTと略記する)通信機能を有するBT対応の車載装置100として具体化されており、当該車載装置100が搭載されている図示しない車両の車室内に、BT通信機能を有するBT対応の携帯電話機200が持ち込まれ、これら車載装置100及び携帯電話機200がBT通信可能な状態にある場合を説明する。なお、BT対応の携帯電話機200が「他の近距離無線通信装置」に相当する。
Memory)、ROM (Read-only Memory)及びI/O(Input/Output)バス等を有し、車載装置100の通信動作やデータ管理動作等の動作全般を制御する。
Audio
Distribution Profile)等を同時に接続可能(いわゆるマルチプロファイル接続
可能)である。なお、これらHFPやA2DPは、機能毎に定義された通信プロトコルを意味する。なお、HFPが「所定のプロファイル」に相当し、A2DPが「別のプロファイル」に相当する。
次に、第2の実施の形態に係る近距離無線通信装置について、図3及び図4を参照して説明する。
次に、第3の実施の形態に係る近距離無線通信装置について、図5を参照して説明する。
けではないため、車載装置100との間で接続していたHFPを切断することなく、A2DPの接続に係る処理の進行を一旦停止する。なお、制御部101のステップS308の処理が接続要求保留手段(接続要求保留部)に相当する。
車載装置100のリソースが確保されると、車載装置100は、先のステップS30
7の処理において受信し受け入れることを保留していたA2DPの接続要求を受け入れ、続くステップS311の処理として、携帯電話機200に対しA2DPの接続応答(Accepted)を送信する。そして、車載装置100は、続くステップ312の処理として、携帯電話機200との間でHFP及びA2DPの接続状態となる。なお、制御部101のステップS309~S311の処理が接続要求受入手段(接続要求受入部)に相当する。
携帯電話機200は、車載装置100からA2DPの拒絶応答を受信したわけではないため、車載装置100との間で接続していたHFPを切断することなく、A2DPの接続に係る処理の進行を一旦停止(保留)するだけである。したがって、上記構成によれば、接続されていたHFPの接続がユーザの意思によらず切断されることがないため、HFPが切断されたままの状態が維持されることを防止することができるようになる。
本開示の第1の例によると、接続相手である他の近距離無線通信装置との間で複数のプロファイルを同時に接続可能な近距離無線通信装置であって、通信切断検出部と通信再接続部とを備える近距離無線通信装置が提供できる。前記通信切断検出部は、当該近距離無線通信装置が前記他の近距離無線通信装置との間で所定のプロファイルを接続している間に前記他の近距離無線通信装置から要求された別のプロファイルの接続要求を当該近距離無線通信装置が受け入れなかったことに起因して前記所定のプロファイルの接続が切断されたか否かを検出する。前記通信再接続部は、前記通信切断検出部によって前記所定のプロファイルの接続が切断されたことが検出されたことに基づいて、前記他の近距離無線通信装置との間で前記所定のプロファイルを再接続する。
近距離無線通信装置としての上記構成では、当該近距離無線通信装置が他の近距離無線通信装置との間で所定のプロファイルを接続している間に他の近距離無線通信装置から当該近距離無線通信装置に対し要求された別のプロファイルの接続要求を受け入れなかったことに起因して所定のプロファイルの接続が切断されたか否か(すなわち、接続されていた所定のプロファイルの接続がユーザの意思によらず切断されたか否か)が通信切断検出部によって検出される。そして、通信切断検出部によって所定のプロファイルの接続が切断されたことが検出されたことに基づいて、通信再接続部によって所定のプロファイルが再接続される。これにより、接続されていたプロファイルの接続がユーザの意思によらず切断された場合に、切断されたままの状態が維持されることを防止することができるようになる。
すなわち、通信再接続部によって他の近距離無線通信装置との間で所定のプロファイルが再接続されると、他の近距離無線通信装置から別のプロファイルの接続要求が再度要求される。当該近距離無線通信装置が上記仕様に起因してこの接続要求を受け入れないと、再接続した所定のプロファイルの接続が他の近距離無線通信装置によって再度切断されてしまう。その結果、接続されていたプロファイルのユーザの意思によらない切断とその切断されたプロファイルの再接続とが繰り返されてしまう。
そこで、上記の構成において、当該近距離無線通信装置が上記仕様を有する場合には、通信再接続部は、通信切断検出部によって所定のプロファイルの接続が切断されたことが検出されたことに基づいて、別のプロファイルを接続するに当たり、別のプロファイルの既接続を切断することにより、必要なリソースを確保した上で、別のプロファイルを再接続するように構成されてもよい。これにより、再接続した所定のプロファイルの接続が他の近距離無線通信装置によって再度切断されることがなくなるため、接続されていたプロファイルのユーザの意思によらない切断とその切断されたプロファイルの再接続とは繰り返されなくなる。
Claims (7)
- 接続相手である他の近距離無線通信装置(200)との間で複数のプロファイルを同時に接続可能な近距離無線通信装置において、
当該近距離無線通信装置が前記他の近距離無線通信装置(200)との間で所定のプロファイルを接続している間に前記他の近距離無線通信装置(200)から要求された別のプロファイルの接続要求を当該近距離無線通信装置が受け入れなかったことに起因して前記所定のプロファイルの接続が切断されたか否かを検出する通信切断検出部(101)と、
前記通信切断検出部(101)によって前記所定のプロファイルの接続が切断されたことが検出されたことに基づいて、前記他の近距離無線通信装置(200)との間で前記所定のプロファイルを再接続する通信再接続部(101)とを備える近距離無線通信装置。 - 請求項1に記載の近距離無線通信装置において、
前記通信切断検出部(101)は、前記他の近距離無線通信装置(200)との間で所定のプロファイルを接続している間に前記他の近距離無線通信装置(200)から要求された別のプロファイルの接続要求を当該近距離無線通信装置が受け入れなかった時点を基準として経過時間を計時開始し、その経過時間が所定時間経過する前に前記所定のプロファイルの接続が切断されたことをもって、前記所定のプロファイルの接続が切断されたことを検出する近距離無線通信装置。 - 請求項1または2に記載の近距離無線通信装置において、
当該近距離無線通信装置は、他の近距離無線通信装置(200)に対し要求したプロファイルを接続し、他の近距離無線通信装置(200)から当該近距離無線通信装置に対し要求されたプロファイルの接続要求を受け入れない仕様を有しており、
前記通信再接続部(101)は、前記所定のプロファイルを再接続した後、前記他の近距離無線通信装置(200)から別のプロファイルの接続要求が再度要求された場合には、その要求を受け入れる近距離無線通信装置。 - 請求項1または2に記載の近距離無線通信装置において、
当該近距離無線通信装置は、リソースが不足している場合には、前記他の近距離無線通信装置(200)から要求されたプロファイルの接続を受け入れず、
前記通信再接続部(101)は、前記通信切断検出部(101)によって前記所定のプロファイルの接続が切断されたことが検出されたことに基づいて、前記別のプロファイルを接続するに当たり必要なリソースを確保した上で、別のプロファイルを再接続する近距離無線通信装置。 - 接続相手である他の近距離無線通信装置(200)との間で複数のプロファイルを同時に接続可能な近距離無線通信装置において、
前記他の近距離無線通信装置(200)との間で所定のプロファイルを接続している間に要求された別のプロファイルの接続要求を当該近距離無線通信装置が受け入れない場合には前記所定のプロファイルの接続を切断する前記他の近距離無線通信装置(200)から前記別のプロファイルの接続を要求されたことに基づいて、一旦、前記別のプロファイルの接続要求を受け入れることを保留する接続要求保留部(101)と、
前記接続要求保留部(101)が前記別のプロファイルの接続要求を受け入れることを保留している間に前記別のプロファイルを接続するに当たり必要なリソースを確保した後、前記別のプロファイルの接続要求を受け入れる接続要求受入部(101)と、
を備える近距離無線通信装置。 - 請求項5に記載の近距離無線通信装置において、
前記接続要求保留部(101)は、前記別のプロファイルの接続要求を受け入れることを保留する旨を示す保留応答を前記別の近距離無線通信装置に対し送信する近距離無線通信装置。 - 請求項5または6に記載の近距離無線通信装置において、
前記接続要求受入部(101)は、前記所定のプロファイル以外に接続しているプロファイルを切断することにより、前記必要なリソースを確保する近距離無線通信装置。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/640,534 US8849204B2 (en) | 2010-05-17 | 2011-05-16 | Short-range wireless communication apparatus |
DE112011101669T DE112011101669T5 (de) | 2010-05-17 | 2011-05-16 | Drahtlose Nahbereichskommunikationsvorrichtung |
CN201180024492.2A CN102948250B (zh) | 2010-05-17 | 2011-05-16 | 短程无线通信装置 |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2010113196 | 2010-05-17 | ||
JP2010-113196 | 2010-05-17 | ||
JP2010210304A JP5472002B2 (ja) | 2010-05-17 | 2010-09-20 | 近距離無線通信装置 |
JP2010-210304 | 2010-09-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011145314A1 true WO2011145314A1 (ja) | 2011-11-24 |
Family
ID=44991432
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2011/002692 WO2011145314A1 (ja) | 2010-05-17 | 2011-05-16 | 近距離無線通信装置 |
Country Status (5)
Country | Link |
---|---|
US (1) | US8849204B2 (ja) |
JP (1) | JP5472002B2 (ja) |
CN (1) | CN102948250B (ja) |
DE (1) | DE112011101669T5 (ja) |
WO (1) | WO2011145314A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015125362A1 (ja) * | 2014-02-21 | 2015-08-27 | ソニー株式会社 | ウェアラブル装置、および通信制御方法 |
US9241363B2 (en) | 2011-06-22 | 2016-01-19 | Denso Corporation | Short-range wireless communication apparatus and system |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5558988B2 (ja) | 2010-09-21 | 2014-07-23 | 株式会社デンソー | 車載機 |
IL243356A0 (en) * | 2015-12-27 | 2016-04-21 | Elbit Systems Ltd | Biodegradable polymer sheet |
JP2013251613A (ja) * | 2012-05-30 | 2013-12-12 | Denso Corp | 通信システム及び出力装置 |
KR101982243B1 (ko) * | 2012-09-28 | 2019-05-24 | 삼성전자주식회사 | 사용자 단말 장치, 전자 장치 및 그 제어 방법 |
US9641963B2 (en) * | 2013-06-20 | 2017-05-02 | Lg Electronics Inc. | Method and apparatus for reproducing multimedia contents using bluetooth in wireless communication system |
US9668294B2 (en) * | 2014-01-14 | 2017-05-30 | Qualcomm Incorporated | Method and apparatus for bluetooth low energy suspend and resume |
JP6319722B2 (ja) * | 2014-02-19 | 2018-05-09 | アルプス電気株式会社 | ハンズフリー機器 |
CN104867320A (zh) * | 2014-02-26 | 2015-08-26 | 王志强 | 出租车招车系统的车载终端及快捷响应控制方法 |
KR101583925B1 (ko) | 2014-05-09 | 2016-01-08 | 현대자동차주식회사 | 블루투스 연결 제어 방법 |
WO2015190194A1 (ja) * | 2014-06-09 | 2015-12-17 | 株式会社Nttドコモ | 通信装置及び通信制御方法 |
CN111263467B (zh) * | 2014-06-17 | 2023-03-31 | 华为技术有限公司 | 无线连接的切换方法,无线终端及其系统 |
CN105407476A (zh) * | 2014-08-25 | 2016-03-16 | 中兴通讯股份有限公司 | 一种通话中控制拆线的方法及终端 |
KR20160042569A (ko) * | 2014-10-10 | 2016-04-20 | 삼성전자주식회사 | 다중 연결 방법 및 이를 지원하는 전자 장치 |
CN110351690B (zh) * | 2018-04-04 | 2022-04-15 | 炬芯科技股份有限公司 | 一种智能语音系统及其语音处理方法 |
US11570625B2 (en) * | 2019-03-25 | 2023-01-31 | Micron Technology, Inc. | Secure vehicle communications architecture for improved blind spot and driving distance detection |
US11979513B2 (en) * | 2021-03-24 | 2024-05-07 | Panasonic Automotive Systems Co., Ltd. | Hands-free apparatus, hands-free system, and data transfer method |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007281652A (ja) * | 2006-04-04 | 2007-10-25 | Nissan Motor Co Ltd | 無線通信装置および無線通信装置におけるプロファイル検出方法 |
JP2010109929A (ja) * | 2008-10-31 | 2010-05-13 | Toshiba Corp | 無線通信端末 |
WO2011004576A1 (ja) * | 2009-07-07 | 2011-01-13 | 株式会社デンソー | 近距離無線通信装置 |
Family Cites Families (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003319062A (ja) * | 2002-04-23 | 2003-11-07 | Nec Corp | ハンズフリー携帯電話機およびハンズフリー切替プログラム |
JP2004180244A (ja) | 2002-11-29 | 2004-06-24 | Alps Electric Co Ltd | 回線接続復旧方法および回線接続復旧プログラム |
US7050834B2 (en) * | 2003-12-30 | 2006-05-23 | Lear Corporation | Vehicular, hands-free telephone system |
CN100420184C (zh) * | 2004-11-26 | 2008-09-17 | 腾讯科技(深圳)有限公司 | 一种网络电台编码器重连流媒体服务器的实现方法及系统 |
JP4578392B2 (ja) | 2005-11-28 | 2010-11-10 | 富士通テン株式会社 | 無線通信接続装置 |
JP4424303B2 (ja) | 2005-12-05 | 2010-03-03 | 株式会社デンソー | 車載ハンズフリー装置及び車載ハンズフリーシステム |
JP4715492B2 (ja) | 2005-12-12 | 2011-07-06 | 株式会社デンソー | 車載ハンズフリー装置及び車載ハンズフリーシステム |
KR100754612B1 (ko) * | 2006-01-26 | 2007-09-05 | 삼성전자주식회사 | 서로 다른 이동 통신 방식 간에 패킷 호 재접속 지연시간을 최소화하기 위한 핸드오버 방법 및 이를 위한멀티모드 단말기 |
JP4513789B2 (ja) | 2006-08-22 | 2010-07-28 | 株式会社デンソー | 車載ハンズフリー装置 |
US20080091814A1 (en) * | 2006-10-16 | 2008-04-17 | Tao Xie | Network Connection Fast Recovery |
US8116223B2 (en) * | 2006-11-09 | 2012-02-14 | Ivt Technology Inc. | System and method for supporting automatic establishing and disconnecting several wireless connections |
JP2008273370A (ja) * | 2007-04-27 | 2008-11-13 | Toyota Motor Corp | 車両用オーディオビジュアル装置、車両用オーディオビジュアルシステム、装置識別方法、プログラム、記憶媒体 |
JP4459253B2 (ja) * | 2007-05-29 | 2010-04-28 | 株式会社東芝 | 通信端末 |
US8295766B2 (en) * | 2007-08-31 | 2012-10-23 | Motorola Mobility Llc | Methods and devices for automatic multiple pairing of Bluetooth devices |
JP2009124243A (ja) * | 2007-11-12 | 2009-06-04 | Toshiba Corp | 情報処理装置 |
US7973657B2 (en) * | 2008-02-20 | 2011-07-05 | Mourad Ben Ayed | Systems for monitoring proximity to prevent loss or to assist recovery |
JP4973580B2 (ja) * | 2008-04-04 | 2012-07-11 | 株式会社デンソー | 車載ハンズフリー装置 |
DE102009015997B4 (de) * | 2008-04-04 | 2018-02-01 | Denso Corporation | Fahrzeug-Freisprecheinrichtung |
JP4645709B2 (ja) * | 2008-09-12 | 2011-03-09 | 株式会社デンソー | 近距離無線通信機能付きストリーミングデータ再生装置 |
JP4220575B1 (ja) * | 2008-09-12 | 2009-02-04 | 株式会社東芝 | 情報処理装置 |
JP2010113196A (ja) | 2008-11-07 | 2010-05-20 | Canon Inc | 画像表示装置 |
JP4687795B2 (ja) | 2009-02-13 | 2011-05-25 | 株式会社デンソー | ハンズフリー機能付き車載装置 |
JP2010199716A (ja) * | 2009-02-23 | 2010-09-09 | Fujitsu Ten Ltd | 車載装置及び通信制御方法 |
JP2010210304A (ja) | 2009-03-09 | 2010-09-24 | Clarion Co Ltd | 車載情報処理装置、及び、車載情報処理装置の制御方法 |
US8265557B2 (en) * | 2009-10-06 | 2012-09-11 | Lg Electronics Inc. | Mobile terminal capable of being connected to audio output device using short-range communication and method of controlling the operation of the mobile terminal |
-
2010
- 2010-09-20 JP JP2010210304A patent/JP5472002B2/ja not_active Expired - Fee Related
-
2011
- 2011-05-16 WO PCT/JP2011/002692 patent/WO2011145314A1/ja active Application Filing
- 2011-05-16 DE DE112011101669T patent/DE112011101669T5/de not_active Withdrawn
- 2011-05-16 CN CN201180024492.2A patent/CN102948250B/zh not_active Expired - Fee Related
- 2011-05-16 US US13/640,534 patent/US8849204B2/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007281652A (ja) * | 2006-04-04 | 2007-10-25 | Nissan Motor Co Ltd | 無線通信装置および無線通信装置におけるプロファイル検出方法 |
JP2010109929A (ja) * | 2008-10-31 | 2010-05-13 | Toshiba Corp | 無線通信端末 |
WO2011004576A1 (ja) * | 2009-07-07 | 2011-01-13 | 株式会社デンソー | 近距離無線通信装置 |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9241363B2 (en) | 2011-06-22 | 2016-01-19 | Denso Corporation | Short-range wireless communication apparatus and system |
WO2015125362A1 (ja) * | 2014-02-21 | 2015-08-27 | ソニー株式会社 | ウェアラブル装置、および通信制御方法 |
CN106031135A (zh) * | 2014-02-21 | 2016-10-12 | 索尼公司 | 可穿戴设备和通信控制方法 |
JPWO2015125362A1 (ja) * | 2014-02-21 | 2017-03-30 | ソニー株式会社 | ウェアラブル装置、および通信制御方法 |
Also Published As
Publication number | Publication date |
---|---|
JP2012005098A (ja) | 2012-01-05 |
CN102948250B (zh) | 2015-11-25 |
JP5472002B2 (ja) | 2014-04-16 |
DE112011101669T5 (de) | 2013-05-29 |
US8849204B2 (en) | 2014-09-30 |
US20130029604A1 (en) | 2013-01-31 |
CN102948250A (zh) | 2013-02-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5472002B2 (ja) | 近距離無線通信装置 | |
US10742247B2 (en) | Short-range wireless communication apparatus | |
JP5275928B2 (ja) | 近距離無線通信装置 | |
JP5273215B2 (ja) | 近距離無線通信装置 | |
US7890147B2 (en) | Portable terminal device | |
US8391792B2 (en) | System and method for initiating ad-hoc communication between mobile headsets | |
JP5278506B2 (ja) | 近距離無線通信装置 | |
US8452348B2 (en) | Hands-free apparatus | |
WO2012142794A1 (zh) | 蓝牙配件配对蓝牙设备的方法及蓝牙配件 | |
JP5988900B2 (ja) | 車載電子装置、車載システム、ハンズフリー通話プログラムおよびハンズフリー通話方法 | |
JP5168371B2 (ja) | 近距離通信装置 | |
JP2009253602A (ja) | 車載ハンズフリー装置 | |
JP2013034178A (ja) | 近距離無線通信装置 | |
JP2014140248A (ja) | 近距離無線通信装置 | |
JP5459428B2 (ja) | 近距離無線通信装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201180024492.2 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11783251 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13640534 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1120111016697 Country of ref document: DE Ref document number: 112011101669 Country of ref document: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11783251 Country of ref document: EP Kind code of ref document: A1 |