Virtual SIM for vehicles

Abstract

To provide a method.SOLUTION: A method includes: identifying a user; acquiring a user profile matched with the identification of the user, the user profile including SIM data associated with a carrier plan; assigning the SIM data associated with the carrier plan of the acquired user profile to a data communication module to virtually replicate the SIM data of the user; and returning carrier settings of the data communication module to original settings based on the user no longer being identifiable.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] FIELD OF THE INVENTION The present disclosure relates generally to methods and systems for mobile twinning, and more particularly to methods and systems for mobile twinning vehicles with a user's carrier settings based on the user's profile. [Background technology]

[0002] Currently, users of shared vehicles (e.g., customers of ride-sharing or car-sharing services) must pair their device (e.g., a mobile device, smartphone, smart pad, etc.) with the vehicle using Bluetooth® connectivity in a multi-step process to make and receive phone calls using Bluetooth® Hands-Free Protocol (“HFP”). While connected over Bluetooth® HFP, calls made in the vehicle (e.g., using the vehicle's hands-free system) and associated data must be routed to and from the device through Bluetooth® pairing. This separate pairing is required in every vehicle in which the user desires to send or receive cellular data using the vehicle. However, individually pairing a user's cell phone with each vehicle the user may have access to can be cumbersome and potentially exposes the user's data unnecessarily. Therefore, a new architecture for accessing and using a customer's cellular data while located in a shared vehicle may be needed. Summary of the Invention [Means for solving the problem]

[0003] In one embodiment, a method includes identifying a user; obtaining a user profile matching the user's identification, the user profile including SIM data associated with a carrier plan; assigning the SIM data associated with the carrier plan of the obtained user profile to a data communication module to virtually replicate the user's SIM data; and restoring carrier settings of the data communication module to original settings based on the user no longer being identifiable.

[0004] In another embodiment, a vehicle includes a data communications module and a controller, the controller configured to identify a user of the vehicle, obtain a user profile matching the user's identification, the user profile including a carrier plan and associated SIM data, assign the carrier plan and associated SIM data of the obtained user profile to a data communications module of the vehicle to virtually replicate the user's SIM data, and restore carrier settings of the data communications module to original settings based on the user no longer being identifiable by the vehicle.

[0005] In yet another embodiment, a vehicle includes a data communications module and a controller, wherein the controller is configured to assign SIM data associated with an original equipment manufacturer's carrier plan to the data communications module, identify a user of the vehicle, obtain a user profile matching the user's identification, the user profile including the SIM data associated with the carrier plan, assign the SIM data associated with the carrier plan of the obtained user profile to the vehicle's data communications module to virtually replicate the user's SIM data, and restore the carrier settings of the data communications module based on the user being no longer identifiable by the vehicle.

[0006] These and additional features provided by the embodiments described herein will be more fully understood in view of the following detailed description taken in conjunction with the drawings.

[0007] The embodiments described in the drawings are exemplary and illustrative in nature and are not intended to limit the subject matter defined by the claims. The following detailed description of exemplary embodiments can be understood when read in conjunction with the following drawings, in which like structure is indicated with like reference numerals and in which: [Brief explanation of the drawings]

[0008] [Figure 1] 1 illustrates a system for virtually cloning a user's SIM according to one or more embodiments shown and described herein; [Figure 2] 1 illustrates a method for virtually cloning a user's SIM according to one or more embodiments shown and described herein. [Figure 3] 1 illustrates a method for virtually cloning a user's SIM according to one or more embodiments shown and described herein. [Figure 4] 1 depicts a scenario in which the system of FIG. 1 is used to virtually clone a user's SIM in accordance with one or more embodiments shown and described herein. DETAILED DESCRIPTION OF THE INVENTION

[0009] Currently, users (e.g., customers of ride-sharing or car-sharing services) must pair a device (e.g., a mobile device, smartphone, smart pad, etc.) with a vehicle using Bluetooth® connectivity in a multi-step process to make and receive phone calls using Bluetooth® Hands-Free Protocol (“HFP”). Once connected over Bluetooth® HFP, calls and associated data made in the vehicle (e.g., using the vehicle's hands-free system) must be routed to and from the device through Bluetooth® pairing. This separate pairing is required in every vehicle in which the user wishes to use the vehicle to send or receive cellular data. For example, due to concerns about leaving paired phone information (e.g., contact lists, call history, text message logs, etc.) behind when using a vehicle other than the user's, not all users want to pair their phone in vehicles other than their own. Additionally, vehicle ownership models may continue to shift from models based primarily on individual ownership of one vehicle to sharing models where users may have driving capabilities or access to multiple vehicles. Given the general customer desire for privacy and convenience to remain unchanged, new architectures may be needed for accessing and using customer cellular data while in a shared vehicle.

[0010] Current-generation vehicles are equipped with data communications modules (DCMs) and advanced antenna arrays that can support inbound and outbound calls. The DCMs also support data connections for vehicle services. In current vehicles, the use of this equipment may depend on the vehicle's own unique data plan. For example, an original equipment manufacturer (OEM) may have a preferred carrier and place a subscriber identity module (SIM) card capable of transmitting and receiving data on the preferred carrier's network within the vehicle to connect the vehicle to the carrier's network. These SIM cards can transmit and receive data related to the vehicle's use that is useful to the OEM (e.g., diagnostic data from the vehicle's CAN bus). In addition, some vehicles may be equipped with a second slot for the vehicle's user's SIM. The user can insert a SIM card associated with their carrier account or another account and use the vehicle to transmit and receive data through the additional SIM card. In some cases, the plan associated with this SIM card may be separate from the user's cellular data plan, or in some cases may require a separate carrier.

[0011] Car-sharing services are becoming increasingly popular as users seek greater flexibility in their vehicle usage. Car-sharing services provide users with a pool of accessible vehicles that they can access and use as needed, thereby eliminating the need for potentially underutilized individual vehicles. Users may find it impractical to insert and remove their own individual SIM cards when using one or more vehicles of a car-sharing or vehicle rental service because doing so would require the user to carry and insert the SIM card associated with their account each time they rent or otherwise operate a new vehicle. Additionally, while users currently have the option to pair their phone with a shared vehicle, doing so can be cumbersome and can result in the unnecessary retention of their own data. That is, contact lists, call logs, and other data from the user's phone may remain in one or more on-board or otherwise connected storage locations. Therefore, what is needed is a system and method for detecting a user and assigning the user's telephone number and data plan details to a vehicle DCM so that the user can make inbound and outbound calls and utilize data services with the vehicle DCM, thereby returning the DCM to a default state upon termination of the user's use of the vehicle.

[0012] 1 , a system 100 for accessing and transferring data using a user's mobile data plan through an onboard system is shown. The system 100 includes a server 102 and a plurality of vehicles 104. In some embodiments, the system 100 includes a device 106. The server 102, the plurality of vehicles 104, and the device 106 may be communicatively coupled by a communication path 108. The communication path 108 may communicatively couple the server 102, the plurality of vehicles 104, and the device 106 to a network, such as, for example, a cloud network 110.

[0013] The server 102 may include one or more processors 114, one or more memory modules 116, network interface hardware 118, and a user profile identification module 112. Each of the plurality of vehicles 104 may include a user identification module 120, an interactive display 122, and network interface hardware 124. The user identification module 120 may be communicatively coupled to an image capture device 121 or other device for identifying a user. In some embodiments, the network interface hardware 124 may be a data communications module. The device 106 may include an interactive display 126 and the network interface hardware 128. In some embodiments, the device 106 may include a user identification module 130, which may be communicatively coupled to the image capture device 121 or other device for identifying a user. Each of the user profile identification module 112, the user identification module 120, and the user identification module 130 may be a program module in the form of an operating system, application program module, or other program module stored within the server 102, the device 106, or one or more vehicles 104. Such program modules may include, without limitation, routines, subroutines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular data types, as described below.

[0014] The server 102 may include, for example, one or more processors 114 and one or more memory modules 116 that store one or more machine-readable instructions. The one or more processors 114 may include any device capable of executing machine-readable instructions. Accordingly, the one or more processors 114 may be a controller, an integrated circuit, a microchip, a computer, or any other computing device. The one or more processors and the one or more memory modules 116 may be communicatively coupled to other components of the system 100 by the communication path 108. The server 102 may be a remote server, a local server, an edge device, and the like.

[0015] The user profile identification module 112 can look up a user profile associated with a particular user or the user's device 106. For example, the user profile identification module 112 can receive input from a user identification module 120 of each of the multiple vehicles 104 or from a device 106 that includes identifying information (e.g., a photograph, biometrics, or other identifying data) and associate the identifying information with a user profile. If a user profile is established for the detected user, the user profile can be stored in a data storage component of the vehicle or server 102, and the user profile identification module 112 can access the user profile. Alternatively, if a user profile does not exist, the user profile identification module 112 can create a user profile for the detected user. The user profile identification module 112 can also maintain a profile log with the user profiles pre-loaded by each of the multiple vehicles 104. The log can include a timestamp of when each user profile was loaded. The log can be updated each time a user profile is loaded.

[0016] In some embodiments, when the user profile identification module 112 determines that a user profile does not exist for the user, a guest profile can be created for the user. The guest profile can have default settings for one or more components of the vehicle that can be loaded when a person operating the vehicle has not established a user profile. The guest profile can be stored in one or more data storage components of the server 102. In some examples, a user can adjust the default vehicle settings associated with the guest profile. In some embodiments, the guest profile can be required to implement at least a minimum required set of instructions for a particular vehicle, which can be based on particular aspects of the vehicle.

[0017] In some embodiments, the user profile identification module 112 can include information related to the user's carrier account (i.e., subscriber information) and can link the network interface hardware 124 with the information related to the user's carrier account to simulate use of a SIM card associated with the user's carrier account, as described in further detail herein. For example, the user profile identification module 112 can identify a user and cause the network interface hardware 124 of each of the plurality of vehicles 104 to simulate the user's SIM card.

[0018] In some embodiments, a user can use an application on a smart device (e.g., device 106) to link their cellular data / phone plan to their profile. The in-application interface can provide the user with an option to add an existing cellular plan to the user's profile, for example, so that the vehicle 104 can make and receive calls from hardware installed within the vehicle, as described in more detail herein. In some embodiments, the vehicle 104 can be a vehicle in a fleet of vehicles, such that once a cellular plan is associated with the user's device (e.g., device 106), any of the vehicles in the fleet will be compatible with the user's cellular plan.

[0019] Network interface hardware 118 can communicatively couple server 102 to communication path 108. Network interface hardware 118 can be any device capable of transmitting and / or receiving data to and from an external vehicle or server, either directly or over a network, such as network 110. Thus, network interface hardware 118 can include a communications transceiver for transmitting and / or receiving any wired or wireless communications. For example, network interface hardware 118 can include an antenna, a modem, a LAN port, a Wi-Fi card, a WiMax card, mobile communications hardware, near-field communications hardware, satellite communications hardware, and / or any wired or wireless hardware for communicating with other networks and / or devices. In an embodiment, network interface hardware 118 can include hardware configured to operate according to the Bluetooth® wireless communications protocol and can include a Bluetooth® transmit / receive module for transmitting and receiving Bluetooth® communications.

[0020] Each of the plurality of vehicles 104 may generally be a vehicle in a pool of vehicles offered for use to customers (“users”) of a car rental service (e.g., a car sharing service), for example. The plurality of vehicles 104 may include vehicles of any class, make, model, size, or type. A user of the car sharing or car rental service may have access to one or more of the plurality of vehicles 104, and in some embodiments, each of the plurality of vehicles 104 may be configured with the necessary systems, equipment, software, and / or modules needed to identify a user and virtually load the user's SIM data into the vehicle's DCM, as will be described in further detail herein.

[0021] Each of the multiple vehicles 104 may include a vehicle 104 controller 119. The controller 119 may include, for example, one or more processors and one or more memory modules that store one or more machine-readable instructions. The one or more processors may include any device capable of executing machine-readable instructions. Thus, the one or more processors may be a controller, an integrated circuit, a microchip, a computer, or any other computing device. The controller 119 may be communicatively coupled to other components of the system 100 by communication paths 108.

[0022] The user identification module 120 may include one or more devices for identifying a user. The devices may include, for example, one or more imaging devices (e.g., one or more on-board cameras) that capture images, retinal scanners, fingerprint or other biometric identifiers, voice recognition modules, etc. The user identification module 120 may identify a user using, for example, a login or username and password combination. In some embodiments, the user identification module 120 may utilize a two-factor authentication method. In some embodiments, the user identification module may identify a user based on the proximity of a particular device, such as the user's device 106 or another device, such as a key fob, that has a separate digital signature. In some embodiments, the user identification module 120 includes an imaging device 121 (e.g., one or more on-board cameras). The imaging device 121 may capture one or more images of the user and compare them to images in a database to identify the user. The imaging device 121 may be, for example, a camera or other imaging device (thermal type, etc.) within the cabin of the vehicle or otherwise communicatively coupled to one or more of the vehicle and the server 102. A database of images may be located, for example, within the server 102 or may otherwise be accessible via the network 110.

[0023] Interactive display 122 may comprise any known or yet to be developed display, such as an LCD, LED, plasma, OLED, CRT, projection, holographic, e-paper, or any other type of suitable output display. In some embodiments, interactive display 122 is positioned in a center console or other location on each of the plurality of vehicles 104. In some embodiments, interactive display 122 may be a head-up display (HUD). In some embodiments, interactive display 122 may be a tactile display, and in such embodiments, interactive display 122 may be any device capable of providing tactile output in the form of refreshable tactile messages. In some embodiments, one or more of the plurality of vehicles 104 does not include a display.

[0024] Network interface hardware 124 can communicatively couple each of the plurality of vehicles 104 to communication path 108. Network interface hardware 124 can be any device capable of transmitting and / or receiving data to and from an external vehicle or server, either directly or over a network, such as network 110. Thus, network interface hardware 124 can include any communications transceiver that transmits and / or receives wired or wireless communications. For example, network interface hardware 124 can include an antenna, a modem, a LAN port, a Wi-Fi card, a WiMax card, mobile communications hardware, near-field communications hardware, satellite communications hardware, and / or any wired or wireless hardware for communicating with other networks and / or devices. In an embodiment, network interface hardware 124 can include hardware configured to operate according to the Bluetooth® wireless communications protocol and can include a Bluetooth® transmit / receive module that transmits and receives Bluetooth® communications.

[0025] The network interface hardware 124 may be a data communications module (e.g., in a vehicle). The data communications module may be any device capable of transmitting and / or receiving data over a wireless network. Thus, the data communications module may include a communications transceiver that transmits and / or receives data according to any wireless communications standard. For example, the data communications module may include a chipset (e.g., an antenna, a processor, machine-readable instructions, etc.) to communicate over a wireless computer network using various communications protocols, such as TCP, UDP, NTTP, Wireless Fidelity (Wi-Fi), WiMax, Bluetooth, IrDA, Wireless USB, Z-Wave, ZigBee, or the like. In some embodiments, the data communications module includes a Bluetooth transceiver that enables the exchange of information with the network 110 via Bluetooth communications. In some embodiments, the data communications module is configured to identify an appropriate communications protocol for one or more signals that may be transmitted and / or received by each of the plurality of vehicles 104. In some embodiments, the data communications module may be capable of emulating a SIM. For example, the data communications module may receive account details for a carrier plan associated with a user and may emulate the account such that the data communications module can make and receive calls and use mobile data associated with the user's carrier account as described in more detail herein.

[0026] Device 106 may be, for example, a portable input / output device (e.g., a smartphone, smart pad, or other device) that includes an interactive display 126 (e.g., a touchscreen or tactile display). Interactive display 126 can have any known or yet to be developed display, such as an LCD, LED, plasma, OLED, CRT, projection, holographic, e-paper, or any other type of suitable output display. When provided as a tactile display, interactive display 126 may be any device capable of providing tactile output in the form of refreshable tactile messages. In some embodiments, device 106 does not include a display, for example, in embodiments where device 106 is a display-less key fob capable of sending and receiving signals.

[0027] Network interface hardware 128 can communicatively couple device 106 to communication path 108. Network interface hardware 128 can be any device capable of transmitting and / or receiving data to and from an external vehicle or server, either directly or over a network, such as network 110. Accordingly, network interface hardware 128 can include any communications transceiver that transmits and / or receives wired or wireless communications. For example, network interface hardware 128 can include an antenna, a modem, a LAN port, a Wi-Fi card, a WiMax card, mobile communications hardware, near-field communications hardware, satellite communications hardware, and / or any wired or wireless hardware that communicates with other networks and / or devices. In an embodiment, network interface hardware 128 can include hardware configured to operate according to the Bluetooth® wireless communications protocol and can include a Bluetooth transmit / receive module that transmits and receives Bluetooth® communications.

[0028] The user identification module 130 may include one or more devices (e.g., one or more user identification devices) that identify a user. The devices may include, for example, one or more imaging devices (e.g., one or more device cameras), a retinal scanner, a fingerprint or other biometric identifier, a voice recognition module, etc. The user identification module 130 may identify a user using, for example, a login or username and password combination. In some embodiments, the user identification module 130 may utilize a two-factor authentication method. In some embodiments, the user identification module 130 includes an imaging device 131 (e.g., one or more device cameras). The imaging device 131 may capture one or more images of the user and compare them to images in a database to identify the user. The imaging device 131 may be, for example, a camera communicatively coupled to one or more of the device 106 and the server 102. The database of images may be located, for example, in the server 102 or may otherwise be accessible via the network 110. In some embodiments, device 106 may verify the user's identity such that the data communication module may emulate the user's SIM card and may transmit a signal (e.g., a digital signature) associated with one or more of device 106 and / or the user that may include data associated with the user's SIM card.

[0029] The communication path 108 can be formed of any medium capable of transmitting a signal, such as, for example, a conductive wire, a conductive trace, an optical waveguide, or the like. In some embodiments, the communication path 108 can facilitate the transmission of wireless signals, such as WiFi, Bluetooth, near field communication (NFC), and the like. Furthermore, the communication path 108 can be formed of a combination of media capable of transmitting a signal. In one embodiment, the communication path 108 includes a combination of conductive traces, conductive wires, connectors, and buses that cooperate to allow the transmission of electrical data signals to components such as processors, memories, sensors, input devices, output devices, and communication devices. Thus, the communication path 108 can include, for example, a vehicle bus, such as a LIN bus, a CAN bus, a VAN bus, and the like. Additionally, it should be noted that the term “signal” refers to a waveform (e.g., electrical, optical, magnetic, mechanical, or electromagnetic) capable of traveling through a medium, such as DC, AC, sine wave, triangle wave, square wave, vibration, and the like.

[0030] The network 110 may include, for example, one or more computer networks (e.g., personal area networks, local area networks, grid computing networks, wide area networks, etc.), cellular networks, satellite networks, and / or global positioning systems, as well as combinations thereof. Accordingly, the server 102, the devices 106, and the plurality of vehicles 104 may be communicatively coupled to the network 110 and / or to each other via wires, wide area networks, local area networks, personal area networks, cellular networks, satellite networks, or the like. Suitable local area networks may include wired Ethernet and / or wireless technologies such as, for example, Wireless Fidelity (Wi-Fi). Suitable personal area networks may include wireless technologies such as, for example, IrDA, Bluetooth, Wireless USB, Z-Wave, ZigBee, and / or other short-range communication protocols. Similarly, suitable personal area networks may include wired computer buses such as, for example, USB and FireWire. Suitable cellular networks include, without limitation, technologies such as LTE, WiMAX, UMTS, CDMA, and GSM.

[0031] 1 and 2, a method 200 for assigning carrier settings for data communication modules of one or more of a plurality of vehicles 104 based on an identifier of a user of the one or more vehicles is shown.

[0032] In step 202, a user is identified. The user may be identified using, for example, the vehicle's user identification module 120 or the device 106's user identification module 130. The user may be a user of the vehicle. In some embodiments, the user may be identified using one or more biometric identifiers. For example, the user may be identified using a fingerprint or voice recognition. The device 106 and / or the vehicle may be configured with a fingerprint reader and / or the vehicle may use an onboard sound system including a speaker and one or more microphones to record and identify the user's voice. The recorded biometric data may be compared to biometric data in a database. In some embodiments, the system 100 may capture one or more images of the user and send the image data to the server 102 to compare the captured image data with the image data in the database. In other embodiments, the user may be identified based on the identification of the device 106. For example, the server 102 may receive location data from the device 106 and use such data to determine that the user is located in or near the vehicle. In some embodiments, one or more of the plurality of vehicles 104 may be configured to detect the proximity of device 106 or another personal identification device of the user and may identify the user based on the proximity of the device.

[0033] In step 204, a user profile matching the user's identification is obtained in step 202. The user profile may be stored in server 102 and / or another storage location communicatively coupled to network 110. In some embodiments, the user profile may include information about the user, such as the user's identification, carrier settings associated with the user's carrier plan, user location history, carrier setting history, and other information about the user. The user's carrier settings may include the user's one or more SIMs and may be used to update a data communication module to simulate the user's carrier settings.

[0034] In step 206, SIM data associated with the retrieved user profile's carrier plan is assigned to a data communications module to virtually replicate the user's SIM data. In some embodiments, the data communications module may be a vehicle data communications module. Assigning the SIM data associated with the user's carrier plan to the data communications module may allow the data communications module to simulate the user's cell phone or other device connecting to one or more of various cellular and data services via the user's carrier plan. As a result, the user may make and receive calls and transfer data using the vehicle to access the user's unique carrier plan through the data communications module. In embodiments, the vehicle may be equipped with a hands-free system, for example, to make calls and / or send text messages or other digital communications.

[0035] In step 208, the carrier settings of the data communication module are reverted to the original settings based on the user no longer being identifiable. For example, the user may leave the vehicle and may no longer be identifiable by one or more biometric identification devices of the vehicle, or may no longer be visible by one or more cameras of the vehicle. In some embodiments, the user may leave the vehicle or may leave a predetermined radius of the vehicle, and the user's device 106 may no longer be detectable by the vehicle.

[0036] In some embodiments, the original settings of the data communications module may refer to the data communications module being configured such that carrier settings associated with the original equipment manufacturer's carrier plan are loaded into the data communications module. For example, if the original equipment manufacturer has a carrier plan with, for example, a 5G carrier, the data communications module may be reconfigured such that the data communications module has the capability to send and receive calls and data over a 5G network. In some embodiments, the data communications module is configured to simultaneously carry the original equipment manufacturer's and one or more user's carrier settings. In such embodiments, the original equipment manufacturer's carrier settings may remain as configured on the data communications module throughout the vehicle's association with the user. Thus, when the settings are reverted to the original settings, the original equipment manufacturer's carrier settings may simply remain as configured on the data communications module.

[0037] In step 210, a second user may be identified. The second user may be identified (e.g., by vehicle) in a similar manner to the first user (referred to above as “user”). For example, one or more biometric identifiers (e.g., voice, fingerprint, etc.) or imaging devices may be used to capture user-specific data of the second user, and the user-specific data may be compared to user-specific data associated with a user profile of the second user (“second user profile”), which may be stored in a storage location accessible via server 102 or network 110.

[0038] In step 212, a second user profile matching the second user's identity is obtained. The second user profile includes SIM data associated with the second user's carrier plan. In some embodiments, the second user profile can include information about the user, such as the user's identity, carrier settings associated with the second user's carrier plan, the second user's user location history, carrier setting history, and other information about the second user. The second user's carrier settings can include one or more SIM profiles for the user and can be used to update the data communications module to simulate the second user's carrier settings.

[0039] In some embodiments, matching a user profile may include capturing images of the user using one or more on-board or device cameras. For example, a user may enter a vehicle, which may include one or more passenger-facing cameras (e.g., imaging device 121). The one or more passenger-facing cameras may capture one or more images of the user and transmit the corresponding image data to server 102 over network 110. In some embodiments, device 106 may include a device camera (e.g., imaging device 131) that may be used to match the user's user profile to their carrier settings. For example, a user may enter a vehicle and determine that they wish to receive and transmit calls and data through the vehicle using their own carrier plan. Thus, the user may capture one or more images using a camera on device 106, and the images may be uploaded to server 102 or another location connected to network 110, where they can be used to match the user to their associated carrier plan details.

[0040] In step 214, the server 102 may cause SIM data associated with the second user carrier plan of the retrieved second user profile to be assigned to the data communications module to simultaneously virtually replicate the SIM data of the first user and the SIM data of the second user. Thus, when the SIM data associated with the first user and the second user are assigned to a vehicle, the vehicle can send and receive calls and data through the two virtually replicated SIMs of the first and second users. The first and second virtually simulated SIM data may be configured to operate on different carrier networks. For example, the first SIM data may be configured to operate with AT&T, and the second SIM data may be configured to operate with Verizon.

[0041] In step 216, the server 102 can configure the carrier settings of the data communications module so that the data communications module does not virtually replicate the first user's SIM data based on the user no longer being identifiable. For example, if the first user leaves the vehicle and is no longer detectable or identifiable by the vehicle, the server 102 can cause the data communications module to stop virtually replicating the user's SIM data. Thus, the user's carrier plan can no longer be used to send and receive calls and data within the vehicle. In some embodiments, the data communications module can stop virtually replicating the user's SIM data after a certain amount of time without the server 102 recognizing the user (e.g., using biometric data, image data, etc.). For example, if a user ceases use of one or more of the multiple vehicles 104 and, for example, leaves the vehicle, the user will no longer be recognized by a camera within the vehicle. The server 102 can receive a signal from the vehicle that the user is no longer recognized and can adjust the settings of the data communication module so that it no longer virtually duplicates the user's SIM and therefore the vehicle can no longer access the user's data and can no longer send and receive calls and / or data.

[0042] In step 218, the server 102 can configure the carrier settings of the data communications module so that the data communications module does not virtually replicate the second user's SIM data based on the second user no longer being identifiable. For example, if the second user leaves the vehicle and is no longer detectable by the vehicle, the server 102 can cause the data communications module to stop virtually replicating the second user's SIM data. Thus, the second user's carrier plan can no longer be used to send and receive calls and data within the vehicle. For example, if the second user leaves the vehicle and is no longer detectable by the vehicle, the server 102 can cause the data communications module to stop virtually replicating the second user's SIM data. Thus, the second user's carrier plan can no longer be used to send and receive calls and data within the vehicle. In some embodiments, the data communications module can stop virtually replicating the second user's SIM data after a specified amount of time without the server 102 recognizing the second user (e.g., using biometric data, image data, etc.). For example, if the second user ceases their use of one or more of the plurality of vehicles 104 and, for example, leaves the vehicle, the user will no longer be recognized by the cameras in the vehicle. The server 102 can receive a signal from the vehicle that the second user is no longer recognized and can adjust the settings of the data communication module so that it no longer virtually replicates the second user's SIM data and, therefore, the vehicle no longer has access to the user's data and can no longer send and receive calls and / or data.

[0043] In some embodiments, one or more users may be provided with a choice as to whether they wish to virtually assign their carrier plan details to the vehicle's data communication module. Such a choice may be presented to the user each time the user comes within proximity of the vehicle's identification sensor, or may be presented to the user on a one-time or periodic basis. For example, the user may be asked to periodically provide permission to the vehicle to automatically set their carrier settings in the data communication module based on the user's identity, such as weekly, monthly, yearly, etc. This may, for example, give the user a choice to control when their vehicle clones the SIM of their device. This may, for example, help with data overages and give the user greater control over what is sent and received using the user's carrier cellular / data plan, and may generally improve user privacy. This choice may be presented to the user using, for example, the vehicle's interactive display 122 or the device's 106's interactive display 126. The server 102 may then receive a user selection indicating whether to set the carrier settings to clone the user's SIM data. If the user indicates that they want the data communication module to virtually clone their SIM data, the server 102 can cause the data communication module to clone the user's carrier settings. If the user does not select or choose to clone their carrier settings, the vehicle will not clone the user's SIM data.

[0044] 1 and 3, a method 300 for setting a user's carrier settings in a data communication module of any of a plurality of vehicles 104 is shown. In step 302, the vehicle's controller 119 or server 102 can assign SIM data associated with an original equipment manufacturer's carrier plan to the data communication module. The original equipment manufacturer may, for example, have preferred carriers with which the original equipment manufacturer has contracted to provide cellular phone and data capabilities to one or more vehicles, such as a fleet of vehicles. The cellular phone and data capabilities provided to the original equipment manufacturer can be used, for example, to transmit diagnostic data, usage data, and other information about the vehicle (e.g., vehicle system status updates, system configuration, user data, odometer readings, location updates, etc.). The original equipment manufacturer may have one or more databases communicatively coupled to the vehicles via network 110 to store and analyze such data, for example, to predict maintenance patterns, usage patterns, etc.

[0045] Additionally, the data communication module can be configured to virtually replicate multiple SIM data at once, and in step 304, the controller 119 of the vehicle 104 can identify the user of the vehicle to replicate that particular user's SIM data. The vehicle controller 119 can identify the user using, for example, the vehicle's user identification module 120 or the device 106's user identification module 130. In some embodiments, the user can be identified using one or more biometric identifiers. For example, the user can be identified using fingerprint or voice recognition. The device 106 and / or the vehicle can be configured with a fingerprint reader and / or the vehicle can use an onboard sound system including a speaker and one or more microphones to record and identify the user's voice. The recorded biometric data can be compared to biometric data in a database. In some embodiments, the system 100 can capture one or more images of the user and transmit the image data to the server 102 to compare the captured image data with image data in the database. In other embodiments, the user can be identified based on the identification of the device 106. For example, the controller 119 of the vehicle 104 can receive location data from the device 106 and use such data to determine that a user is located in or near the vehicle. In some embodiments, one or more of the plurality of vehicles 104 can be configured to detect the proximity of the device 106 or another personal identification device of the user and can identify the user based on the proximity of the device.

[0046] In step 306, the controller 119 of the vehicle 104 may retrieve a user profile matching the user's identification, where the user profile includes SIM data associated with the user's carrier plan. In embodiments, the controller 119 of the vehicle 104 may retrieve the user profile from the server 102. The user profile may be stored in the server 102 and / or another storage location (e.g., the device 106) communicatively coupled to the network 110. In some embodiments, the user profile may include information about the user, such as, for example, carrier settings associated with the user's carrier plan, user location history, carrier setting history, and other information about the user. The user's carrier settings may include one or more SIM profiles for the user and may be used to update the data communication module to simulate the user's carrier settings.

[0047] In step 308, the controller 119 or server 102 of the vehicle 104 may assign SIM data associated with a carrier plan to the vehicle's data communications module to virtually replicate the user's SIM based on the matched user profile. Assigning SIM data associated with the user's carrier plan to the data communications module may allow the data communications module to simulate the user's cell phone or other device that will connect to one or more of various cellular and data services via the user's carrier plan. The user may then make or receive calls and transfer data using the vehicle to access the user's unique carrier plan through the data communications module. In an embodiment, the vehicle may be equipped with a hands-free system, for example, to make calls and / or send text messages or other digital communications.

[0048] In step 310, the controller 119 of the vehicle 104 may restore the carrier settings of the data communication module to the original settings based on the user no longer being identifiable by the vehicle. For example, the user may leave the vehicle and may no longer be identifiable by one or more biometric identification devices or may no longer be visible by one or more cameras of the vehicle. In some embodiments, the user may leave the vehicle or may leave a predetermined radius of the vehicle and the user's device 106 may no longer be detectable by the vehicle.

[0049] In step 312, the controller 119 of the vehicle 104 may identify a second user of the vehicle. The second user may be identified similarly to the first user (referred to above as the “user”). For example, one or more biometric identifiers (e.g., voice, fingerprint, etc.) or an imaging device may be used to capture user-specific data of the second user, and the user-specific data may be compared to user-specific data associated with a user profile of the second user (“second user profile”), which may be stored in a storage location accessible via the server 102 or the network 110.

[0050] A second user profile can be matched to the second user based on the second identifier. The second user profile includes SIM data associated with the second user's carrier plan. In some embodiments, the second user profile can include information about the user, such as carrier settings associated with the second user's carrier plan, the second user's user location history, carrier setting history, and other information about the second user. The second user's carrier settings can include one or more SIM profiles for the user and can be used to update the data communication module to simulate the second user's carrier settings.

[0051] In some embodiments, matching a user profile may include capturing images of the user using one or more on-board or device cameras. For example, a user may enter a vehicle, which may include one or more passenger-facing cameras (e.g., imaging device 121). The one or more passenger-facing cameras may capture one or more images of the user and transmit the corresponding image data to server 102 over network 110. In some embodiments, device 106 may include a device camera (e.g., imaging device 131) that may be used to match the user's user profile to their carrier settings. For example, a user may enter a vehicle and determine that they wish to receive and transmit calls and data using their own carrier plan through the vehicle. Thus, the user may capture one or more images using a camera on device 106, and the images may be uploaded to server 102 or other location connected to network 110, where they can be used to match the user to their relevant carrier plan details.

[0052] In step 316, the controller 119 or server 102 of the vehicle 104 can assign SIM data associated with the second user's carrier plan to the vehicle's data communication module to simultaneously virtually replicate the user's SIM data and the second user's SIM data based on the matched user profile and the matched second user profile, respectively. Thus, the vehicle can send and receive calls and data through the two virtually replicated SIM data of the user and the second user. The first and second virtually simulated SIM data can be configured to operate on different carrier networks. For example, the first SIM data can be configured to operate with AT&T, and the second SIM data can be configured to operate with Verizon.

[0053] In step 318, the controller 119 or server 102 of the vehicle 104 can configure the carrier settings of the data communications module so that the data communications module does not virtually replicate the first user's SIM data based on the user no longer being identifiable. For example, if the first user leaves the vehicle and is no longer detectable or identifiable by the vehicle, the controller 119 or server 102 of the vehicle 104 can cause the data communications module to stop virtually replicating the user's SIM data. Thus, the user's carrier plan can no longer be used to send and receive calls and data within the vehicle. In some embodiments, the data communications module can stop virtually replicating the user's SIM data after a certain amount of time without recognition of the user (e.g., using biometric data, image data, etc.) by the controller 119 or server 102 of the vehicle 104. For example, if a user ceases use of one or more of the multiple vehicles 104 and, for example, leaves the vehicle, the user will no longer be recognized by a camera within the vehicle. The server 102 can receive a signal from the vehicle that the user is no longer recognized and can adjust the settings of the data communication module so that it no longer virtually replicates the user's SIM data and therefore the vehicle no longer has access to the user's data and can no longer send and receive calls and / or data.

[0054] In step 320, the controller 119 or server 102 of the vehicle 104 can configure the carrier settings of the data communications module so that the data communications module does not virtually duplicate the second user's SIM based on the second user no longer being identifiable. For example, if the second user leaves the vehicle and is no longer detectable by the vehicle, the controller 119 or server 102 of the vehicle 104 can cause the data communications module to stop virtually duplicating the second user's SIM. Thus, the second user's carrier plan can no longer be used to send and receive calls and data within the vehicle. For example, if the second user leaves the vehicle and is no longer detectable by the vehicle, the controller 119 or server 102 of the vehicle 104 can cause the data communications module to stop virtually duplicating the second user's SIM. Thus, the second user's carrier plan can no longer be used to send and receive calls and data within the vehicle. In some embodiments, the data communications module can stop virtually duplicating the second user's SIM data after a certain amount of time without the second user being recognized by the server 102 (e.g., using biometric data, image data, etc.). For example, if the second user stops using one or more of the plurality of vehicles 104 and, for example, leaves the vehicle, the user will no longer be recognized by a camera in the vehicle. The controller 119 or server 102 of the vehicle 104 can receive a signal from the vehicle that the second user is no longer recognized and can adjust the settings of the data communications module to no longer virtually duplicate the second user's SIM data and, therefore, the vehicle will no longer have access to the user's data and will no longer be able to send and receive calls and / or data.

[0055] 1 and 4, an exemplary scenario using system 100 for identifying one or more users and assigning carrier plan details of one or more users to a vehicle's data communication module is shown. FIG. 4 illustrates three vehicles: a first vehicle 104a, a second vehicle 104b, and a third vehicle 104c. First vehicle 104a, second vehicle 104b, and third vehicle 104c may be substantially identical and may be vehicles available for sharing in a car sharing or car rental service. Each vehicle may include network interface hardware 124 (which may be configurable as or include a data communication module), a user identification module 120 (including an image capture device 121), and an interactive display 122. First vehicle 104a, second vehicle 104b, and third vehicle 104c may each have a data communication module that includes original equipment manufacturer SIM data. This SIM data may be in the form of an actual SIM card, or may be virtually replicated based on SIM data stored locally, for example, in server 102 and / or in a storage location on the vehicle. The original equipment manufacturer's SIM data may allow the vehicle to connect to network 110 using the original equipment manufacturer's cellular plan so that the vehicle may transmit data related to the use of the vehicle (e.g., diagnostic and other data described herein).

[0056] FIG. 4 illustrates a first user 105 and a second user 107 in a first vehicle 104a. Referring to FIGS. 1 and 4, the server 102 can identify the first user 105 and the second user 107 using one or more on-board systems (e.g., one or more user identification devices). For example, the first user 105 and the second user 107 can be identified using an imaging device 121. The imaging device 121 can be, for example, a camera mounted in the rearview mirror 109 of the first vehicle 104a. In some embodiments, the first vehicle 104a can include other user identification devices for identifying one or more users, such as, for example, a voice recognition system, a fingerprint recognition system, one or more device detection systems configured to detect a user's device (e.g., device 106), etc. The identification device, in this case, the imaging device 121, is used to capture identification data about the one or more users and provide such identification data to the server 102 (e.g., via the network 110). In some embodiments, the user's device can be used to identify the user. For example, image capture device 131 of user identification module 130 of device 106 can be used to capture an image of the user, and this image data can be used to identify the user.

[0057] The server 102 may receive user identification data from the vehicle and may retrieve a user profile matched to the user (e.g., using the user profile identification module 112) and identify a carrier configuration or carrier plan associated with the user. The carrier configuration may be associated with a cellular voice and / or data plan and may be associated with the user's SIM, i.e., the user's personal cellular voice and / or data plan.

[0058] This SIM data can be virtually replicated using the data communications module of the first vehicle 104a. The virtual replication of the user's SIM data cannot affect the original equipment manufacturer's SIM data, which may also be used to send and receive calls and data. Thus, both the user and the original equipment manufacturer can simultaneously send and receive cellular phone calls and data via the data communications module. Similarly, the second user can be identified by the controller of the first vehicle 104a using one or more identification devices, and the SIM data associated with the user's carrier plan can be virtually replicated on the data communications module so that the original equipment manufacturer, the first user, and the second user can each send and receive calls and data using the data communications module. Thus, neither the first user nor the second user needs to pair their cellular device with a phone using, for example, Bluetooth® pairing. The system simply recognizes the first and second users and virtually assigns their SIMs to the data communications module.

[0059] In some embodiments, the controller of the first vehicle 104a can require an affirmative response from the user before cloning the user's SIM data using the data communication module. For example, the controller of the first vehicle 104a can cause an acknowledgement or other information to be provided to the first user 105 and the second user 107, and can require receipt of information from the first user 105 and / or the second user 107 before assigning the user's carrier details to the data communication module. The request for information can be presented to the user using, for example, the interactive display 122, such as a question like, "Do you want to assign your SIM data to the data communication module to send and receive cellular calls and data using your vehicle? Yes or No." The controller of the first vehicle 104a can virtually clone the user's SIM based on the response.

[0060] It should be understood that a user of a car sharing or car rental service may be identified by the vehicle, and their unique carrier plan may be used to send and receive cellular calls and data by virtually replicating the user's SIM data using the vehicle's data communications module. Thus, the user need not go through the effort of pairing their phone with the vehicle via Bluetooth or other connection, and need not even have their phone with them in the vehicle. Furthermore, such virtual replication may be optional for the user, thereby allowing the user to protect their privacy as appropriate. Thus, the use of car sharing and car rental services can grow upon the implementation of such systems, and there is a need for such systems.

[0061] It should be noted that the terms "substantially" and "about" may be used herein to express the inherent degree of uncertainty that can be attributed to any quantitative comparison, value, measurement, or other expression. These terms are also used herein to express the degree to which a quantitative expression may vary from the stated standard without resulting in a change in the basic functionality of the subject matter.

[0062] While particular embodiments have been illustrated and described herein, it should be understood that various other changes and modifications can be made without departing from the spirit and scope of the claimed subject matter. Moreover, although various aspects of the claimed subject matter have been described herein, such aspects need not necessarily be used in combination. Accordingly, the appended claims should be construed to cover all such changes and modifications that are within the scope of the claimed subject matter.

[0063] Example 1. A method comprising: Identifying the user; obtaining a user profile matching the identification of the user, the user profile including SIM data associated with a carrier plan; assigning the SIM data associated with the carrier plan of the retrieved user profile to a data communications module to virtually replicate the SIM data of the user; restoring the carrier settings of the data communication module to original settings based on the user no longer being identifiable; A method having the following. Example 2. The method of example 1, wherein the data communication module is a vehicle data communication module. Example 3. The method of example 1, wherein the user is identified using one or more of biometrics, voice recognition, and image recognition. Example 4. The method of example 1, wherein SIM data associated with an original equipment manufacturer is uploaded to the data communication module when the original configuration is applied to the data communication module. Example 5. The method of Example 4, wherein the SIM data associated with the original equipment manufacturer is assigned to the data communication module to virtually replicate the SIM data of the original equipment manufacturer. Example 6. The method of Example 1, wherein the SIM data associated with the carrier plan and the SIM data associated with the original equipment manufacturer of the retrieved user profile are simultaneously assigned to the data communications module. Example 7. Identifying a second user; obtaining a second user profile matching the identification of the second user, the second user profile including SIM data associated with a second user carrier plan; assigning the SIM data associated with the second user carrier plan of the retrieved second user profile to the data communication module to simultaneously virtually replicate the SIM data of the user and the SIM data of the second user; configuring the carrier settings of the data communication module such that the data communication module does not virtually clone the SIM data of the user based on the user being no longer identifiable; configuring the carrier settings of the data communication module such that the data communication module does not virtually clone the SIM data of the second user based on the second user being no longer identifiable; The method of Example 1, further comprising: Example 8. Identifying the user capturing an image of the user using one or more of an on-board camera and a device camera; comparing the image of the user with one or more images stored in a database; The method of Example 1 having Example 9. Presenting an option to configure the carrier settings of the data communication module to replicate the SIM data of the user based on the carrier plan associated with the retrieved user profile; receiving a user selection indicating whether to configure the carrier settings to replicate the SIM data of the user; configuring the carrier settings to replicate the SIM data for the user based on the received user selection; The method of Example 1, further comprising: Example 10. The method of Example 9, wherein the options for setting the carrier settings are presented to the user using a display on the user's portable device. Example 11. A vehicle, Data communication module and A controller; and the controller comprises: Identifying a user of the vehicle; obtaining a user profile matching the identification of the user, the user profile including carrier plans and associated SIM data; assigning the SIM data associated with the carrier plan of the retrieved user profile to the data communication module of the vehicle to virtually replicate the SIM data of the user; and restoring the carrier settings of the data communication module to original settings based on the user no longer being identifiable by the vehicle. A vehicle configured as follows: Example 12. The system of Example 11, wherein SIM data associated with an original equipment manufacturer is uploaded to the data communication module when the original configuration is applied to the data communication module. Example 13. The system of Example 12, wherein the SIM data associated with the original equipment manufacturer is assigned to the data communications module to virtually replicate the SIM data of the original equipment manufacturer. Example 14. The system of Example 11, wherein the SIM data associated with the carrier plan and the SIM data associated with the original equipment manufacturer of the retrieved user profile are simultaneously assigned to the data communications module. Example 15. The controller: identifying a second user of the vehicle; obtaining a second user profile matching the identification of the second user, the second user profile including SIM data associated with a second user carrier plan; assigning the SIM data associated with the second user carrier plan of the retrieved second user profile to the data communication module of the vehicle to simultaneously virtually replicate the SIM data of the user and the SIM data of the second user; configuring the carrier settings of the data communication module such that the data communication module does not virtually clone the SIM data of the user based on the user being no longer identifiable; and configuring the carrier settings of the data communication module such that the data communication module does not virtually clone the SIM data of the second user based on the second user being no longer identifiable. 12. The system of example 11, further configured as follows: Example 16. The system of example 11, wherein the user is identified using one or more of biometrics, voice recognition, and image recognition. Example 17. The system of example 11, wherein the user profile is stored in a cloud server. Example 18. A vehicle, a data communication module; A controller; and the controller comprises: assigning SIM data associated with an original equipment manufacturer's carrier plan to said data communications module; Identifying a user of the vehicle; obtaining a user profile matching the identification of the user, the user profile including carrier plans and associated SIM data; assigning the SIM data associated with the carrier plan of the retrieved user profile to the data communication module of the vehicle to virtually replicate the SIM data of the user; and restoring the carrier setting of the data communication module based on the user no longer being identifiable by the vehicle; A vehicle configured as follows: Example 19. The controller: identifying a second user of the vehicle; obtaining a second user profile matching the identity of the second user, the second user profile including SIM data associated with a second user carrier plan; and assigning the SIM data associated with the second user carrier plan to the data communication module of the vehicle to simultaneously virtually replicate the SIM data of the first user and the SIM data of the second user; 19. The system of example 18, further configured as follows: Example 20. The controller: configuring the carrier settings of the data communication module such that the data communication module does not virtually clone the SIM data of the user based on the user being no longer identifiable; and configuring the carrier settings of the data communication module such that the data communication module does not virtually clone the SIM data of the second user based on the second user being no longer identifiable. 20. The system of example 19, further configured as follows:

Claims

1. A method performed by a controller, comprising: Identifying a user using one or more of biometrics, voice recognition, and image recognition; transmitting the user's identity to a server; obtaining a user profile of the user from the server, the user profile being associated with the identity of the user, the user profile including SIM data associated with a carrier plan; assigning the SIM data associated with the carrier plan of the retrieved user profile to a data communications module to virtually replicate the SIM data of the user; restoring the carrier settings of the data communication module to original settings based on the user no longer being identifiable; A method comprising:

2. The method of claim 1 , wherein the data communication module is a vehicle data communication module.

3. when the original configuration is applied to the data communication module, SIM data associated with an original equipment manufacturer is uploaded to the data communication module; 10. The method of claim 1, wherein the SIM data associated with the original equipment manufacturer is assigned to the data communication module to virtually replicate the SIM data of the original equipment manufacturer.

4. The method of claim 1 , wherein the SIM data associated with the carrier plan and the SIM data associated with an original equipment manufacturer of the retrieved user profile are simultaneously assigned to the data communications module.

5. Identifying a second user; obtaining a second user profile matching the second user's identity, the second user profile including SIM data associated with a second user carrier plan; assigning the SIM data associated with the second user carrier plan of the retrieved second user profile to the data communication module to simultaneously virtually duplicate the SIM data of the user and the SIM data of the second user; configuring the carrier settings of the data communication module such that the data communication module does not virtually clone the SIM data of the user based on the user being no longer identifiable; configuring the carrier settings of the data communication module such that the data communication module does not virtually duplicate the SIM data of the second user based on the second user being no longer identifiable; The method of claim 1 further comprising:

6. Identifying the user includes: capturing an image of the user using one or more of an on-board camera and a device camera; comparing the image of the user with one or more images stored in a database; 2. The method of claim 1, comprising:

7. presenting an option to configure carrier settings of the data communication module to replicate the SIM data of the user based on the carrier plan associated with the retrieved user profile; receiving a user selection indicating whether to configure the carrier settings to replicate the SIM data of the user; configuring the carrier settings to replicate the SIM data of the user based on the received user selection; and The method of claim 1 , wherein the options for setting the carrier settings are presented to the user using a display on the user's portable device.

8. 1. A system comprising: Data communication module and A controller; and the controller comprises: Identifying a user of the vehicle using one or more of biometrics, voice recognition, and image recognition; transmitting the user's identity to a server; obtaining a user profile for the user from the server, the user profile being associated with the identity of the user, the user profile including SIM data associated with a carrier plan; assigning the SIM data associated with the carrier plan of the retrieved user profile to the data communication module of the vehicle to virtually replicate the SIM data of the user; and restoring the carrier settings of the data communication module to original settings based on the user no longer being identifiable by the vehicle. The system is configured as follows:

9. A vehicle, a data communication module; A controller; and the controller comprises: assigning SIM data associated with an original equipment manufacturer's carrier plan to said data communications module; identifying a user of the vehicle using one or more of biometrics, voice recognition, and image recognition; transmitting the user's identity to a server; obtaining a user profile for the user from the server, the user profile being associated with the identity of the user, the user profile including SIM data associated with a carrier plan; assigning the SIM data associated with the carrier plan of the retrieved user profile to the data communication module of the vehicle to virtually replicate the SIM data of the user; and restoring the carrier setting of the data communication module based on the user no longer being identifiable by the vehicle; A vehicle configured as follows:

Images