Method and system for securing in-vehicle communication with a portable device using NFC

A method for securing wireless communication between an in-vehicle system and multiple portable devices brought into a vehicle. The method can include receiving a communication request from a portable device, and determining whether a primary device has authorized wireless communication between the in-vehicle system and the portable device requesting communication, where such authorization can be provided via near field communication (NFC). The method can further include establishing wireless communication between the in-vehicle system and the portable device requesting communication when the portable device requesting communication is the primary device, and when the portable device requesting communication is a secondary device and the primary device has authorized wireless communication via NFC.

FIELD

The present disclosure relates to a method and a system for securing in-vehicle communication with a portable device using near field communication (NFC).

BACKGROUND

This section provides background information related to the present disclosure which is not necessarily prior art. Vehicles often include a system for wirelessly communicating with portable devices, such as smartphones, which are brought into the vehicle. Such systems may wirelessly communicate with a portable device by way of a Bluetooth communication link. Conventional protocols for establishing a communication link via Bluetooth may first pair the system with the portable device by using a pin code to authenticate the portable device requesting the wireless connection. Once the pin code is authenticated and a media access control (MAC) address is saved by both the system and the portable device, pairing is complete and the system and the portable device can automatically establish wireless communication when the two are within communication range (i.e., the portable device is brought into the vehicle).

Once a Bluetooth communication link is established, the portable device can access the system and perform a variety of functions via various Bluetooth profiles. For example, a hands free function allows an occupant to place or receive calls via the portable device by using a microphone and a speaker disposed in the vehicle. Also, the occupant can wirelessly stream and listen to audio files provided by the portable device through a vehicle audio system.

Portable devices brought into the vehicle by, for example, a guest, who may not be the primary user of the vehicle, may also wirelessly communicate with the system. Thus, allowing the guest to access the system to, for example, play music or even download information. As a result, once paired with the system, the portable device belonging to the guest may now automatically establish wireless communication with the system without the knowledge of the primary user.

SUMMARY

The present disclosure provides for a method for securing wireless communication between an in-vehicle system and multiple portable devices brought into a vehicle. The method includes receiving a communication request from a portable device (i.e., a requesting portable device), and determining whether a primary device has authorized wireless communication between the in-vehicle system and the portable device requesting communication. The primary device can be a portable device that is registered in a primary device registry as the primary device, whereas a portable device not registered in the primary device registry can be a secondary device.

The method can further include establishing wireless communication between the in-vehicle system and the portable device requesting communication when the portable device requesting communication is the primary device, and when the portable device requesting communication is the secondary device and the primary device has authorized wireless communication.

The authorization from the primary device can be received using near field communication (NFC) via a NFC sensor. For instance, the method can include receiving a device ID unique to the portable device from the NFC sensor, and comparing the device ID received from the NFC sensor to device IDs provided in the primary device registry, which has device IDs of the portable devices registered as the primary device. The method determining the primary device has authorized wireless communication when the device ID received from the NFC sensor is registered in the primary device registry. Thus, the method establishes wireless communication between the in-vehicle system and the secondary device when the primary device authorizes the wireless communication via NFC.

DETAILED DESCRIPTION

Example embodiments will now be described more fully with reference to the accompanying drawings. With reference toFIGS. 1 and 2, an in-vehicle system2can communicably couple to one or more portable devices4brought inside a passenger cabin6of a vehicle via wireless communication. Wireless communication can be performed using various techniques such as Bluetooth and near field communication (NFC).

The passenger cabin6having a center console8is depicted inFIG. 2. The center console8includes a communication pad10and a display12. The communication pad10can be disposed in a storage area11, defined by the center console8. Though the storage area11is depicted below the display12, it can be disposed in various suitable areas within the passenger cabin6.

The communication pad10is configured to wirelessly communicate with the portable device4disposed thereon. For instance, the communication pad10can be a near field communication (NFC) pad10A having NFC sensors10B disposed therein for performing wireless communication with the portable device4. As the communication pad10, the NFC pad10A is configured to read a device ID or a tag of the portable device4, which is unique to the portable device4. When the portable device4is placed on the NFC pad10A, the device ID unique to the portable device is read by the NFC pad10A and provided to the in-vehicle system2.

The communication pad10can also be configured as a charging pad having NFC sensors10B disposed therein, such that the charging pad charges the battery of the portable device4disposed thereon and the NFC sensors10B communicates with the portable device4positioned in close proximity to the NFC sensors10B. Though the communication pad10is depicted within the storage area11. The communication pad10can be arranged in various suitable areas within the passenger cabin6, such as next to a gear shift, and can also be configured in various shapes and sizes suitable for wirelessly communicating with the portable device4.

The display12displays information, such as text and images, to occupants of the vehicle. The display12may be an LCD display, or any other device suitable for displaying information, and may include a touch screen surface for receiving input from an occupant. The display12can also be used to access certain vehicular systems, such as climate control, navigation, and sound system. In addition, the display12can provide access to various functionalities supported by various subsystems of the in-vehicle system2, such as hands-free communication, audio streaming, and internet access.

The portable device4can be any electronic device capable of wirelessly coupling with the in-vehicle system2by way of, for example, Bluetooth communication and/or NFC. For example, the portable device4can be a smartphone, a tablet computer, or a laptop. The portable device4can also be capable of wirelessly transmitting data to the in-vehicle system2. Such data can include, for example, audio data, phonebook data, internet data, and navigation data.

The in-vehicle system2can include a control unit13having a CPU, a RAM, and a ROM for storing and executing various processes. Though the control unit13is depicted as being positioned behind the dashboard of the passenger cabin6inFIG. 2, the control unit13can be disposed in various suitable positions within the vehicle. The in-vehicle system2can include various sub-systems, such as a Bluetooth subsystem14and a NFC subsystem16.

The Bluetooth subsystem14allows the in-vehicle system2to wirelessly communicate with other Bluetooth devices, such as the portable device4, through, for example, a Bluetooth transceiver. To establish wireless communication, the Bluetooth subsystem14and the portable device4use standard Bluetooth protocol to form a bond that allows the two to automatically establish a communication link (i.e., a Bluetooth communication link) for wireless communication. Per standard Bluetooth protocol, in order to create a bond, the portable device4and Bluetooth subsystem14are first paired. For instance, the first time the portable device4is brought into communication range of the Bluetooth subsystem14of the in-vehicle system2, the portable device4may send a Bluetooth communication request to the Bluetooth subsystem14. Using standard Bluetooth protocol, a pin code is generated to authenticate the portable device4. Once, the portable device has been authenticated, a MAC address is then stored by the portable device4and the Bluetooth subsystem14, thereby allowing the two to identify each other once within communication range. Once pairing is complete, a bond if formed between the portable device4and the Bluetooth subsystem14, thereby allowing the two to communicate with each other in the future without performing pairing. Various methods suitable for pairing the portable device4and the Bluetooth subsystem14can be used.

The NFC subsystem16can be configured to include the NFC sensors10B provided in the NFC pad10A or provided in other suitable areas in the passenger cabin6. As part of the NFC subsystem16, the NFC pad10A communicates with the portable device4disposed thereon and detects the device ID unique to the portable device4, which is provided to the in-vehicle system2.

Various functions provided by the in-vehicle system2can be accessed by the portable device4once a communication link is established with the Bluetooth subsystem14. For instance, a hands-free communication function can allow an occupant to operate the portable device through audio speakers and a microphone mounted within the passenger cabin6. An audio streaming function plays audio files from the portable device4through the sound system of the vehicle. The audio files can be stored on the portable device4or, can even be files being streamed by the portable device4by way of an application (i.e., an App). An internet connection function can allow the occupant to access the Internet by way of the portable device4. For instance, websites and data can be displayed on the display12of the vehicle, and the occupant may access the data or websites by way of the display12or any other suitable method, such as voice command.

Any portable device4brought into the vehicle can access the various functions of the in-vehicle system2, once a bond is created between the portable device4and the Bluetooth subsystem14. As a result, the in-vehicle system2distinguishes the portable devices4brought into the vehicle as either a primary device4A or a secondary device4B. The primary device4A can be the portable device4of a primary user of the vehicle, such as an owner of the vehicle, whereas the secondary device4B can be the portable device4of a guest, such as a friend or a colleague of the owner.

To identify the primary device4A, the in-vehicle system2can include a device registry18for listing the device ID of the portable device4that are registered as the primary device4A, as shown inFIGS. 1 and 3. Various methods can be used to register the portable device4as the primary device4A. For example, under a setting option of the in-vehicle system2, the occupant may access the device registry18and input the device ID of the portable device4using, for example, the display12or a website. For instance, inFIG. 3, the occupant may add or delete the entries in the device registry18by using operation buttons19A,19B. As another example, the occupant may also place the portable device4onto the NFC pad10A or close to the NFC sensor10B to provide the device registry18with the device ID. It should be understood that more than one portable device4can be registered as the primary device4A. For example, the primary user can register a smartphone and a tablet computer as the primary device4A. As another example, the primary user may include two individuals each having their own portable device4registered as the primary device4A.

As portable devices4are brought into the vehicle, the in-vehicle system2, via the control unit13, performs a communication authorization process100provided inFIG. 4once a communication request is received from the portable device4. At102the in-vehicle system2determines whether the portable device4was previously paired with the Bluetooth subsystem14. One way to determine this is by checking the MAC address that was saved by the portable device4and the Bluetooth subsystem14. If the MAC address matches, the in-vehicle system2determines that the portable device4has been previously paired.

If the portable device4was previously paired, the in-vehicle system2then determines, at104, whether the portable device4requesting communication is the primary device4A. For instance, the in-vehicle system may compare the device ID stored in the device registry18with the device ID of the portable device4provided within the communication request. If the device registry18includes the device ID of the portable device4, then the in-vehicle system2, at106, identifies the portable device4as the primary device4A, and, at108, permits wireless communication with the primary device4A via the Bluetooth subsystem14. If the device registry18does not include the device ID of the portable device4, then the in-vehicle system2identifies the portable device4as the secondary device4B, at110.

To permit wireless communication via a communication link established by the Bluetooth subsystem14, the in-vehicle system2determines whether the system2is authorized to communicate with the portable device4that has never been paired, as determined in102, or with the secondary device4B, as identified at110. Such authorization can be provided by the primary device4A via NFC.

The in-vehicle system2can use the NFC subsystem16to determine if the primary device4A authorizes Bluetooth communication at112by performing a primary device authorization process200ofFIG. 5. For example, at202, the in-vehicle system2determines whether the NFC subsystem16has received a device ID or tag. As provided above, the NFC subsystem16detects the portable device4and receives the device ID that is unique to the portable device4when the portable device4is disposed on the NFC pad10A and/or is in close proximity to the NFC sensor10B. Conversely, when the portable device4is not detected (i.e., not on the NFC pad10A nor in close proximity to the NFC sensor10B), no device ID is provided to the NFC subsystem16.

Accordingly, when the NFC subsystem16receives a device ID, the in-vehicle system2, at204, determines whether the device ID received by the NFC subsystem16is listed in the device registry18as a primary device4A. If the device ID is listed, the in-vehicle system2, at206, determines that the primary device4A authorizes wireless communication via the Bluetooth subsystem14with the portable device4requesting communication, and returns to the communication authorization process100ofFIG. 4. On the other hand, if the device ID is not listed in the device registry18, the in-vehicle system2, at208, determines that the primary device4A does not authorize the wireless communication and returns to the communication authorization process100. In addition, if the NFC subsystem16did not receive a device ID, as determined at202, the in-vehicle system2, at208, determines that the primary device4A does not authorize the wireless communication, and returns to the communication authorization process100.

Returning to the communication authorization process100ofFIG. 4at112, in the event the primary device4A has not authorized the wireless communication, as determined by process200ofFIG. 5, the in-vehicle system2, at114, prohibits the Bluetooth subsystem14from establishing wireless communication with the portable device4requesting the wireless communication. Accordingly, the Bluetooth subsystem14and the portable device4may not be paired if pairing was not previously performed, and no communication link would be established.

When the primary device4A does authorize wireless communication, the in-vehicle system2, at116, determines whether the portable device4requesting the wireless communication has been previously paired with the Bluetooth subsystem14. If the portable device4was not previously paired, the in-vehicle system2, at118, permits the Bluetooth subsystem14to pair with the portable device4and to establish a communication link for wireless communication. When the portable device4has already been paired, the in-vehicle system2, at120, permits the Bluetooth subsystem14to establish a communication link for wireless communication with the portable device4.

According to the present disclosure, the in-vehicle system2allows the primary user to authorize wireless communication between the in-vehicle system2and the secondary device4B. In particular, the in-vehicle system2utilizes NFC as a medium for the primary user to provide authorization. As known, NFC can be established when two devices are in close proximity to each other. As a result, the primary user can consciously provide consent by positioning the primary device4A in close proximity to the NFC sensor10B by, for example, placing the primary device4A onto the NFC pad10A. Accordingly, in-vehicle system2authenticates the authorization by way of the NFC subsystem16. Therefore, even if the secondary device4B was previously paired with the Bluetooth subsystem14, the secondary device4B cannot automatically establish wireless communication with the Bluetooth subsystem14, unless such communication is authorized by primary device4A via the NFC subsystem16.

The communication authorization process100performed by the in-vehicle system2can further be understood by the illustrative examples shown inFIGS. 6-8. With reference toFIG. 6, the in-vehicle system2and the portable device4are depicted. The in-vehicle system2includes the Bluetooth subsystem14, the NFC subsystem16, the NFC pad10A having the NFC sensors10B, and the device registry18. The portable device4requests wireless communication with the Bluetooth subsystem14, as indicated by an arrow. Based on the process100, the in-vehicle system2would permit communication if the portable device4is the primary device4A, as determined by the device ID of the portable device4and the device registry18. However, if the portable device4is the secondary device4B, the in-vehicle system2would prohibit communication since wireless communication has not been authorized, as illustrated by the absence of the primary device4A.

With reference toFIG. 7, which is similar toFIG. 6accept multiple portable devices4are depicted, the in-vehicle system2would permit wireless communication with the primary device4A via the Bluetooth subsystem14as indicated by the wavy lines. However, the in-vehicle system2would prohibit wireless communication with the secondary devices, as indicated by the no symbol, since authorization was not provided. In particular, though the primary device4A is present, it has not been authenticated by the NFC subsystem16, as illustrated by the primary device4A not being positioned on the NFC pad10A. Therefore, only the primary device4A may wirelessly communicate with the in-vehicle system2.

With reference toFIG. 8, the in-vehicle system2would permit wireless communication with all the portable devices4via the Bluetooth subsystem14, including the secondary devices4B, as indicated by the wave lines. Since the primary device4A is present and is authenticated by the NFC subsystem16, as illustrated by the primary device4A being positioned on the NFC pad10A, wireless communication between the in-vehicle system2and the secondary devices4B has been authorized by the primary device4A.

The NFC subsystem16utilizes the NFC pad10A for receiving the communication authorization from the primary device4A. Alternatively, the NFC subsystem16may also utilize a NFC sensor20arranged in proximity to the display12, as shown inFIG. 9. The NFC sensor20performs in the same manner as the NFC sensors10B of the NFC pad10A, in that once the portable device4is placed over and/or in close proximity to the NFC sensor20, the sensor20detects the portable device4and receives the device ID unique to the portable device4. Accordingly, to authorize wireless communication between the secondary device4B and the in-vehicle system2, the primary device4A would be held in close proximity to the NFC sensor20. Though the NFC sensor20is depicted close to the display12, the NFC sensor20can be positioned at various suitable positions easily accessible by an occupant within the passenger cabin6.

In a second embodiment of the present disclosure, an in-vehicle system50, illustrated inFIG. 10, can be customized by the primary user to permit guests to access certain wireless communication features. In other words, wireless communication maybe established between the secondary device4B and the in-vehicle system2, without the authorization of the primary device4A, but such wireless communication would be limited to selected Bluetooth profiles.

The in-vehicle system50stores a list of Bluetooth profiles that have been identified as a public profile that can be accessible without the authorization of the primary device4A. Such a list can be provided as a Bluetooth profile registry21that can be stored by the in-vehicle system50. An example of the Bluetooth profile registry21is depicted inFIG. 11where Bluetooth profiles are provide as either a public profile or a secured profile. A secured profile requires the authorization of the primary device4A in order for communication to be established. In the example ofFIG. 11, public profiles include hands free profile (HFP) and advanced audio distribution profile (A2DP). Whereas, secured profiles include serial port profile (SPP), personal area networking profile (PAN), and dial up network (DUN). It should be understood that various Bluetooth profiles can be registered in the Bluetooth profile registry21, and are not limited to the ones shown inFIG. 11.

Various methods can be used to set selected Bluetooth profiles as either public or secured in the Bluetooth profile registry21. For example, the occupant may access the Bluetooth profile registry21via a setting option of the in-vehicle system50. Using the display12, the user can select the Bluetooth profile, such as “SPP” inFIG. 11, and then operate a left arrow button22A or a right arrow button22B to move the Bluetooth profile to the appropriate column (i.e., “Public Profile” or “Secured Profile”). Such modification can also be made via a website. The Bluetooth profile registry21can also be a predetermined registry provided by the manufacturer.

As portable devices4are brought into the vehicle, the portable device4may send a wireless communication request to the in-vehicle system50for establishing a certain Bluetooth profile. When such a request is received the in-vehicle system50performs a communication authorization process300ofFIG. 12. The communication authorization process300is similar to the communication authorization process100of the first embodiment, where similar steps having similar reference numbers perform in the same manner as in the first embodiment.

When a request is received by the in-vehicle system50, the system50, at302, determines whether the Bluetooth profile being requested is a public profile. In particular, the system50determines whether the profile requested is listed as “Public Profile” in the Bluetooth profile registry21. If the profile is not listed as public, it is a secured profile that requires the authorization of the primary device4A. Thus, the in-vehicle system50continues by performing the remaining process from104to120, which is similar to the communication authorization process100of the first embodiment.

On the other hand if the profile is listed as a public profile, the system50, at304, then determines if the portable device4requesting the Bluetooth profile connection is the primary device4A by determining whether the device ID received with the communication request is provided in the device registry18, as described above. If the primary device4A is requesting the connection, then the in-vehicle system50, at306, permits unrestricted wireless communication via the Bluetooth subsystem14(i.e., any profile, public and/or private, is assessable). When the portable device4is not the primary device4A, the in-vehicle system50, at308, permits wireless communication according to the requested Bluetooth profile, which is a public profile.

The in-vehicle system50of the second embodiment allows secondary devices4B to access certain functions supported by public Bluetooth profiles without requiring the authorization of the primary device4A. The in-vehicle system50becomes customizable to permit limited access, free access, or no access by way of the Bluetooth profile registry, which can be set by the primary user. Thus, the in-vehicle system50can still be utilized by guests while providing the security benefits of the first embodiments for communication requests that are deemed to be restricted unless authorized by the primary device4A via the NFC sub-system16.