Virtual SIM for vehicles

Abstract

This application relates to a virtual SIM for vehicles. One method includes: identifying a user; obtaining a user profile matching the user's identifier, wherein the user profile includes SIM data associated with an operator plan; assigning the SIM data associated with the operator plan of the obtained user profile to a data communication module to virtually replicate the user's SIM data; and restoring the operator settings of the data communication module to their original settings based on the user no longer being identifiable.

Description

Technical Field

[0001] This specification generally relates to methods and systems for twinning, and more specifically, to methods and systems for twinning vehicles based on a user's profile and the user's operator settings. Background Technology

[0002] Currently, users of shared vehicles (e.g., customers of carpooling or car-sharing services) must use Bluetooth connectivity in a multi-step process to pair their devices (e.g., mobile devices, smartphones, tablets, etc.) with the vehicle to make and receive phone calls using the Bluetooth Hands-Free Protocol (“HFP”). When connecting via Bluetooth HFP, data associated with calls made in the vehicle (e.g., using the vehicle's hands-free system) must be routed to and from the device via Bluetooth pairing. This individual pairing is required for each vehicle in which the user wants to send or receive cellular data. However, pairing a user's cellular phone individually with each vehicle the user might access can be cumbersome and unnecessarily exposes the user's data excessively. Accordingly, a new architecture may be needed for accessing and using a customer's cellular data while in a shared vehicle. Summary of the Invention

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

[0004] In another embodiment, a vehicle includes a data communication module and a controller configured to: identify a user of the vehicle; obtain a user profile matching the user's identifier, wherein the user profile includes SIM data associated with an operator plan; assign the SIM data associated with the operator plan of the obtained user profile to the vehicle's data communication module to virtually replicate the user's SIM data; and restore the operator settings of the data communication module to their original settings based on the user no longer being identifiable by the vehicle.

[0005] In yet another embodiment, a vehicle includes a data communication module and a controller configured to: allocate SIM data associated with an original equipment manufacturer (OEM) operator plan to the data communication module; identify a user of the vehicle; obtain a user profile matching the user's identifier, wherein the user profile includes SIM data associated with the operator plan; allocate SIM data associated with the operator plan of the obtained user profile to the vehicle's data communication module to virtually replicate the user's SIM data; and restore the operator settings of the data communication module based on the user no longer being identifiable by the vehicle.

[0006] These and additional features provided by the embodiments described herein will be more fully understood in light of the following detailed description and in conjunction with the accompanying drawings. Attached Figure Description

[0007] The embodiments illustrated in the accompanying drawings are illustrative and exemplary in nature and are not intended to limit the subject matter defined by the claims. The following detailed description of the illustrative embodiments will be understood when read in conjunction with the following drawings, in which the same structures are indicated by the same reference numerals and wherein:

[0008] Figure 1 A system for virtually replicating a user's SIM card, according to one or more embodiments shown and described herein, is illustrated schematically.

[0009] Figure 2 A method for virtually replicating a user's SIM is described according to one or more embodiments shown and described herein;

[0010] Figure 3 A method for virtually replicating a user's SIM is described according to one or more embodiments shown and described herein; and

[0011] Figure 4 The use of one or more embodiments shown and described herein is depicted. Figure 1 The system is used to virtually replicate the user's SIM card scenario. Detailed Implementation

[0012] Currently, users (e.g., customers of carpooling or car-sharing services) must use a Bluetooth connection in a multi-step process to pair their devices (e.g., mobile devices, smartphones, tablets, etc.) with vehicles to make and receive phone calls using the Bluetooth Hands-Free Protocol (“HFP”). When connecting via Bluetooth HFP, data associated with calls made in the vehicle (e.g., using the vehicle's hands-free system) must be routed to and from the device via Bluetooth pairing. This separate pairing is required for each vehicle in which the user wants to send or receive cellular data. Not all users are willing to pair their phones in vehicles that don't belong to them, for example, due to concerns about leaving paired phone information (e.g., contact lists, call history, SMS logs, etc.) while using vehicles that don't belong to them. Furthermore, vehicle ownership models are likely to continue shifting from a model primarily based on individual ownership of a single vehicle to a shared arrangement where users can access or operate multiple vehicles. Assuming that general customer expectations for privacy and convenience remain unchanged, a new architecture may be needed for accessing and using customers' cellular data while in shared vehicles.

[0013] Current-generation vehicles are equipped with a Data Communication Module (DCM) and a complex antenna array that supports both incoming and outgoing calls. The DCM also supports data connectivity for vehicle services. In current vehicles, the use of this equipment can depend on the vehicle's unique data plan. For example, an Original Equipment Manufacturer (OEM) may have a preferred carrier and may place a Subscriber Identity Module (SIM) card in the vehicle, capable of sending and receiving data on that preferred carrier's network, to connect the vehicle to the carrier's network. These SIM cards can send and receive data useful to the OEM in relation to the vehicle's use (e.g., diagnostic data from the vehicle's CAN bus). Additionally, some vehicles may be equipped with a second SIM slot for the vehicle's user. The user can insert a SIM card associated with his or her carrier account or other accounts and can use the vehicle to send and receive data via the additional SIM card. In some cases, the plan associated with this SIM card may differ from the user's cellular data plan and may even require a different carrier.

[0014] Car-sharing services are gaining popularity as users seek greater flexibility in vehicle usage. These services provide users with an accessible pool of vehicles, which they can access and use as needed, eliminating the need for potentially underutilized individual vehicles. Users using one or more vehicles through car-sharing or car rental services may find inserting and removing their own personal SIM cards impractical, as this could require them to carry and insert the SIM card associated with their account each time they rent or otherwise operate a new vehicle. Furthermore, while users currently have the option to pair their phones with shared vehicles, this can be cumbersome and may result in the unnecessary retention of their own data. Specifically, contact lists, call logs, and other data from a user's phone may be stored in one or more onboard or otherwise connected storage locations. Accordingly, systems and methods are needed to detect users and assign their phone numbers and data plan details to the vehicle's DCM (Data Management Center), enabling users to make inbound and outbound calls and utilize the vehicle's DCM data services, and then reverting the DCM to its default state based on the user's termination of vehicle use.

[0015] Now for reference Figure 1 A system 100 for accessing and transmitting data via an in-vehicle system using a user's mobile data plan is illustrated. System 100 includes a server 102 and multiple vehicles 104. In some embodiments, system 100 includes a device 106. The server 102, multiple vehicles 104, and device 106 can be communicatively coupled via a communication path 108. The communication path 108 can communicatively couple the server 102, multiple vehicles 104, and device 106 to a network such as a cloud network 110.

[0016] Server 102 may include one or more processors 114, one or more memory modules 116, network interface hardware 118, and user profile identification module 112. Each of the plurality of vehicles 104 may include user identification module 120, interactive display 122, and network interface hardware 124. User identification module 120 may be communicatively coupled to imaging device 121 or other devices for identifying users. In some embodiments, network interface hardware 124 may be a data communication module. Device 106 may include interactive display 126 and network interface hardware 128. In some embodiments, device 106 may include user identification module 130, which may be communicatively coupled to imaging device 121 or other devices for identifying users. Each of user profile identification module 112, user identification module 120, and user identification module 130 may be a program module in the form of an operating system, application module, and other program modules stored in server 102, device 106, or the plurality of vehicles 104. Such program modules may include, but are not limited to, routines, subroutines, programs, objects, components, data structures, etc., for performing specific tasks or performing specific data types, as described below.

[0017] Server 102 may include, for example, one or more processors 114 and one or more memory modules 116 storing 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, integrated circuit, microchip, 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 system 100 via communication path 108. Server 102 may be a remote server, a local server, an edge device, etc.

[0018] User profile identification module 112 can locate a user profile associated with a specific user or a user's device 106. For example, user profile identification module 112 can receive input including identification information (e.g., a photograph, biometric data, or other identification data) from user identification modules 120 in each of the multiple vehicles 104 or from device 106, and can associate the identification information with a user profile. If a user profile has already been created for the detected user, it can be stored in a data storage component of the vehicle or server 102, and the user profile identification module 112 can access it. Alternatively, if no user profile exists, the user profile identification module 112 can create one for the detected user. User profile identification module 112 can also maintain a profile log, which includes previously loaded user profiles from 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.

[0019] In some embodiments, when the user profile identification module 112 determines that a user does not have a user profile, a visitor profile can be created for that user. The visitor profile may include default settings for one or more components of the vehicle, which can be loaded when the individual driving the vehicle has not created a user profile. The visitor profile may be stored in one or more data storage components of the server 102. In some examples, the user can adjust the default vehicle settings associated with the visitor profile. In some embodiments, the visitor profile may be required to execute at least a minimum required set of instructions for a particular vehicle, which may be based on specific aspects of the vehicle.

[0020] In some embodiments, the user profile identification module 112 may include information related to the user's operator account (i.e., subscriber information) and may link the network interface hardware 124 and the information related to the user's operator account to simulate the use of a SIM card associated with the user's operator account, as will be explained in more detail herein. For example, the user profile identification module 112 may identify a user and may enable the network interface hardware 124 of each of the plurality of vehicles 104 to simulate the user's SIM card.

[0021] In some embodiments, a user may use an app on a smart device (e.g., device 106) to link his or her cellular data / phone plan to his or her profile. The in-app interface may provide the user with options, such as adding an existing cellular plan to the user's profile, enabling vehicle 104 to make and receive calls from hardware installed in the vehicle, as described in more detail herein. In some embodiments, vehicle 104 may be a vehicle in a fleet, such that once a cellular plan is associated with the user's device (e.g., device 106), any vehicle in the fleet is compatible with the user's cellular plan.

[0022] 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 directly or via a network (such as network 110) to an external vehicle or server. Accordingly, network interface hardware 118 may include a transceiver for transmitting and / or receiving any wired or wireless communication. For example, network interface hardware 118 may include an antenna, modem, LAN port, Wi-Fi card, WiMax card, mobile communication hardware, near-field communication hardware, satellite communication hardware, and / or any wired or wireless hardware for communicating with other networks and / or devices. In embodiments, network interface hardware 118 may include hardware configured to operate according to the Bluetooth wireless communication protocol and may include a Bluetooth transmit / receive module for transmitting and receiving Bluetooth communications.

[0023] Each of the multiple vehicles 104 may be a vehicle from a pool of vehicles typically provided to customers (“users”) of services such as car rental (e.g., car-sharing services). The multiple vehicles 104 may include vehicles of any category, brand, model, size, or type. Users of the car-sharing or car rental service can access one or more of the multiple vehicles 104, and in some embodiments, each of the multiple vehicles 104 may be configured with the necessary systems, equipment, software, and / or modules required to identify the user and virtually load the user’s SIM data into the vehicle’s DCM, as will be explained in more detail herein.

[0024] Each of the plurality of vehicles 104 may include a controller 119 for vehicle 104. Controller 119 may include, for example, one or more processors and one or more memory modules storing one or more machine-readable instructions. The one or more processors may include any device capable of executing machine-readable instructions. Accordingly, the one or more processors may be a controller, integrated circuit, microchip, computer, or any other computing device. Controller 119 may be communicatively coupled to other components of system 100 via communication path 108.

[0025] User identification module 120 may include one or more devices for identifying a user. Devices may include, for example, imaging devices for capturing images (e.g., one or more in-vehicle cameras), retinal scanners, fingerprints or other biometric identifiers, voice recognition modules, etc. User identification module 120 may identify a user, for example, using a login name or a combination of username and password. In some embodiments, user identification module 120 may utilize a two-factor authentication method. In some embodiments, user identification module 120 may identify a user based on proximity to a specific device (such as the user's device 106 or another device, such as, for example, a key fob with a different digital signature). In some embodiments, user identification module 120 includes imaging device 121 (e.g., one or more in-vehicle cameras). Imaging device 121 may capture one or more images of the user and compare them with images in a database to identify the user. Imaging device 121 may be, for example, a camera or other imaging device (thermal, etc.) in the driver's cab of a vehicle, or one or more otherwise communicatively coupled to the vehicle and server 102. The image database may reside, for example, on server 102 or may be otherwise accessed via network 110.

[0026] Interactive display 122 may include any known or under-development display, such as LCD, LED, plasma, OLED, CRT, projection, holographic, electronic paper, or any other suitable type of output display. In some embodiments, interactive display 122 is positioned in the center console or other location of 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 haptic display, and in such embodiments, interactive display 122 may be any device capable of providing haptic output in the form of refreshable haptic messages. In some embodiments, one or more of the plurality of vehicles 104 do not include a display.

[0027] 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 directly or via a network (e.g., network 110) to external vehicles or servers. Therefore, network interface hardware 124 may include a communication transceiver for transmitting and / or receiving any wired or wireless communication. For example, network interface hardware 124 may include an antenna, modem, LAN port, Wi-Fi card, WiMax card, mobile communication hardware, near-field communication hardware, satellite communication hardware, and / or any wired or wireless hardware for communicating with other networks and / or devices. In embodiments, network interface hardware 124 may include hardware configured to operate according to the Bluetooth wireless communication protocol and may include a Bluetooth transmit / receive module for transmitting and receiving Bluetooth communications.

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

[0029] Device 106 may be a portable input / output device (e.g., a smartphone, smartboard, or other device) including, for example, an interactive display 126 (e.g., a touchscreen or haptic display). The interactive display 126 may include any known or under-development display, such as LCD, LED, plasma, OLED, CRT, projection, holographic, electronic paper, or any other suitable type of output display. If provided as a haptic display, the interactive display 126 may be any device capable of providing haptic output in the form of refreshable haptic messages. In some embodiments, device 106 may not include a display, for example, in an embodiment where device 106 is a displayless keychain capable of transmitting and receiving signals.

[0030] 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 directly or via a network (e.g., network 110) to an external vehicle or server. Accordingly, network interface hardware 128 may include a transceiver for transmitting and / or receiving any wired or wireless communications. For example, network interface hardware 128 may include an antenna, modem, LAN port, Wi-Fi card, WiMax card, mobile communication hardware, near-field communication hardware, satellite communication hardware, and / or any wired or wireless hardware for communicating with other networks and / or devices. In embodiments, network interface hardware 128 may include hardware configured to operate according to the Bluetooth wireless communication protocol and may include a Bluetooth transmit / receive module for transmitting and receiving Bluetooth communications.

[0031] User identification module 130 may include one or more devices for identifying a user (e.g., one or more user identification devices). Devices may include one or more of, for example, imaging devices (e.g., one or more device cameras), retinal scanners, fingerprints or other biometric identifiers, voice recognition modules, etc. User identification module 130 may identify a user, for example, using a login name or a combination of username and password. In some embodiments, user identification module 130 may utilize a two-factor authentication method. In some embodiments, user identification module 130 includes imaging device 131 (e.g., one or more device cameras). Imaging device 131 may capture one or more images of the user and compare them with images in a database to identify the user. Imaging device 131 may be, for example, a camera communicatively coupled to one or more of device 106 and server 102. The image database may reside, for example, on server 102 or may be otherwise accessed via network 110. In some embodiments, device 106 may verify the user's identity and may send signals associated with device 106 and / or one or more of the user, including data associated with the user's SIM card (e.g., digital signature), such that a data communication module can emulate the user's SIM card.

[0032] The communication path 108 can be formed of any medium capable of transmitting signals, such as, for example, a conductive line, a conductive trace, an optical waveguide, etc. In some embodiments, the communication path 108 can facilitate communication such as WiFi, The communication path 108 can be formed by a combination of media capable of transmitting signals, such as near field communication (NFC). In one embodiment, the communication path 108 includes a combination of conductive traces, conductive lines, connectors, and buses that cooperate to allow the transmission of electrical data signals to components such as processors, memory, sensors, input devices, output devices, and communication devices. Accordingly, the communication path 108 may include vehicle buses, such as, for example, LIN buses, CAN buses, VAN buses, etc. Furthermore, it should be noted that the term "signal" refers to a waveform (e.g., electrical, optical, magnetic, mechanical, or electromagnetic) capable of passing through a medium, such as DC, AC, sine waves, triangle waves, square waves, vibrations, etc.

[0033] 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 and combinations thereof. Accordingly, server 102, device 106, and multiple vehicles 104 may be communicatively coupled to network 110 and / or another network via wired, wide area network, local area network, personal area network, cellular network, satellite network, etc. Suitable local area networks may include wired Ethernet and / or wireless technologies such as, for example, Wi-Fi. Suitable personal area networks may include wireless technologies such as, for example, IrDA, Bluetooth, wireless USB, Z-Wave, ZigBee, and / or other near-field communication protocols. Suitable personal area networks may similarly include wired computer buses such as, for example, USB and FireWire. Suitable cellular networks include, but are not limited to, technologies such as LTE, WiMAX, UMTS, CDMA, and GSM.

[0034] Now for reference Figure 1 and Figure 2 This paper illustrates a method 200 for assigning operator settings for one or more data communication modules in multiple vehicles 104 based on the identity of a user in one or more vehicles 104.

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

[0036] At step 204, a user profile matching the user's identifier is obtained in step 202. The user profile may be stored on server 102 and / or in another storage location communicatively coupled to network 110. In some embodiments, the user profile may include information about the user, such as, for example, the user's identifier, 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 of the user and may be used to update the data communication module to simulate the user's carrier settings.

[0037] At step 206, SIM data associated with the carrier plan in the obtained user profile is assigned to the data communication module to virtually replicate the user's SIM data. In some embodiments, the data communication module may be a vehicle data communication module. Assigning SIM data associated with the user's carrier plan to the data communication module allows the data communication module to simulate a user's cellular 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 can then use the vehicle to make and receive calls and transmit data to access their own carrier plan through the data communication module. In embodiments, the vehicle may be equipped with a hands-free system, for example, for making phone calls and / or sending text messages or other digital communications.

[0038] At step 208, based on the user no longer being identifiable, the operator settings of the data communication module are restored to their original settings. For example, the user may have left the vehicle and may no longer be identifiable by one or more biometric identification devices of the vehicle or may no longer be visible to one or more cameras of the vehicle. In some embodiments, the user may have left the vehicle or may have left a predetermined radius of the vehicle and the user's device 106 may no longer be detected by the vehicle.

[0039] In some embodiments, the original settings of the data communication module may refer to the data communication module being configured such that the carrier settings associated with the original equipment manufacturer's (OEM) carrier plan are loaded onto the data communication module. For example, if the OEM has a carrier plan, for example, with a 5G operator, the data communication module can be restored to its original settings, enabling it to send and receive calls and data on a 5G network. In some embodiments, the data communication module is configured to carry both the OEM's and one or more users' carrier settings simultaneously. In such embodiments, the OEM's carrier settings can remain configured on the data communication module throughout the vehicle-user association process, after the OEM's carrier settings have been configured. Accordingly, when the settings are restored to the original settings, the OEM's carrier settings can simply remain configured on the data communication module.

[0040] At step 210, a second user can be identified. The second user can be identified in a manner similar to that of the first user (hereinafter referred to as the "user") (e.g., via a vehicle). For example, one or more biometric identifiers (e.g., voice, fingerprint, etc.) or imaging devices can be used to capture user-specific data of the second user, and the user-specific data can be compared with user-specific data associated with a user profile ("second user profile") of the second user that can be stored on server 102 or in a storage location accessible via network 110.

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

[0042] In some embodiments, matching a user profile may include capturing images of the user using one or more of an in-vehicle camera and a device camera. For example, a user may enter a vehicle that 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 the corresponding image data may be sent to server 102 via network 110. In some embodiments, device 106 may include a device camera (e.g., imaging device 131) that may be used to match a user's profile with his or her carrier settings. For example, a user may enter a vehicle and determine that he or she wants to use his or her own carrier plan to receive and send calls and data through the vehicle. Accordingly, he or she may use the camera on device 106 to capture one or more images and may upload the images to server 102 or other locations connected to network 110, where these images may be used to match the user with his or her associated carrier plan details.

[0043] At step 214, server 102 may allocate SIM data associated with the second user's carrier plan obtained from the second user profile to the data communication module to simultaneously and virtually replicate the SIM data of the first user and the second user. Accordingly, with the SIM data associated with the first and second users allocated to the vehicle, the vehicle can send and receive calls and data via the two virtually replicated SIMs of the user and the second user. The first and second virtual SIM data can be configured to operate on different carrier networks. For example, the first SIM data can be configured to operate on AT&T and the second SIM data can be configured to operate on Verizon.

[0044] At step 216, server 102 can configure the carrier settings of the data communication module such that the data communication module does not virtually copy 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 detected or identified by the vehicle, server 102 can cause the data communication module to stop virtually copying the user's SIM data. Accordingly, the user's carrier plan may no longer be used to send and receive calls and data within the vehicle. In some embodiments, the data communication module can stop virtually copying the user's SIM data after a certain period of time without server 102 identifying the user (e.g., using biometric data, image data, etc.). For example, if a user stops using one or more of the multiple vehicles 104 and, for example, leaves the vehicle, then he or she will no longer be identified by the cameras in the vehicle. Server 102 can receive a signal from the vehicle that the user is no longer identifiable and can adjust the settings of the data communication module so that it no longer virtually copies the user's SIM, and therefore the vehicle may no longer be able to access the user's data and may no longer send and receive calls and / or data.

[0045] At step 218, server 102 can configure the carrier settings of the data communication module such that the data communication module does not virtually copy the second user's SIM data if the second user is no longer identifiable. For example, if the second user leaves the vehicle and is no longer detected by the vehicle, server 102 can cause the data communication module to stop virtually copying the second user's SIM data. Accordingly, the second user's carrier plan may no longer be used to send and receive calls and data within the vehicle. In some embodiments, the data communication module can stop virtually copying the second user's SIM data after a certain period of time if server 102 does not recognize the second user (e.g., using biometric data, image data, etc.). For example, if the second user stops using one or more of the multiple vehicles 104 and, for example, leaves the vehicle, he or she will no longer be recognized by the cameras in the vehicle. Server 102 can receive a signal from the vehicle that it no longer recognizes the second user and can adjust the settings of the data communication module so that it no longer virtually copies the second user's SIM data, and therefore the vehicle may no longer be able to access the user's data and may no longer send and receive calls and / or data.

[0046] In some embodiments, one or more users may be presented with the option of whether he or she wishes to have their carrier plan details virtually assigned to the vehicle's data communication module. Such an option may be presented to the user each time they approach the vehicle's identification sensors, or it may be presented to the user once or periodically. For example, the user may be required to periodically grant permission to the vehicle to automatically set his or her carrier settings to the data communication module based on weekly, monthly, yearly, etc., user identification. This can provide the user with, for example, the option to control when his or her vehicle copies his or her device's SIM. This can help, for example, prevent data overages and give the user more control over what they send and receive using their carrier's cellular / data plan, and generally improve user privacy. The option may be presented to the user using, for example, the vehicle's interactive display 122 or the device 106's interactive display 126. The server 102 may then receive the user's selection indicating whether to set carrier settings to copy the user's SIM data. If the user indicates that he or she wishes the data communication module to virtually copy his or her SIM data, then the server 102 may cause the data communication module to copy the user's carrier settings. If the user does not make a selection or chooses not to copy his or her carrier settings, the vehicle will not copy the user's SIM data.

[0047] Now for reference Figure 1 and Figure 3 This illustrates a method 300 for setting a user's operator settings to the data communication module of any one of multiple vehicles 104. At step 302, the vehicle's controller 119 or server 102 may assign SIM data associated with the original equipment manufacturer's (OEM) operator plan to the data communication module. For example, the OEM may have a preferred operator with whom it has a contract to provide cellular and data capabilities to one or more vehicles (e.g., a fleet). The cellular and data capabilities provided to the OEM can be used to transmit, for example, diagnostic data, usage data, and other information about the vehicles (e.g., vehicle system status updates, system configurations, user data, odometer readings, location updates, etc.). The OEM has 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.

[0048] Furthermore, the data communication module can be configured to virtually copy more than one SIM data at a time, and at step 304, the controller 119 of vehicle 104 can identify the user of the vehicle in order to copy the SIM data of that specific user. The vehicle controller 119 can identify the user, for example, using the user identification module 120 of the vehicle or the user identification module 130 of device 106. In some embodiments, one or more biometric identifiers can be used to identify the user. For example, fingerprint or voice recognition can be used to identify the user. Device 106 and / or the vehicle can be configured with a fingerprint reader and / or the vehicle can use an in-vehicle audio system including a speaker and one or more microphones to record and identify the user's voice. The recorded biometric data can be compared with biometric data in a database. In some embodiments, system 100 can capture one or more images of the user and can send the image data to server 102 to compare the captured image data with image data in a database. In other embodiments, the user can be identified based on the identifier of device 106. For example, the controller 119 of vehicle 104 can receive location data from device 106 and can use such data to determine that the user is 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 to identify the user based on the proximity of that device.

[0049] At step 306, the controller 119 of vehicle 104 can obtain a user profile matching the user's identifier, wherein the user profile includes SIM data associated with the user's carrier plan. In an embodiment, the controller 119 of vehicle 104 can obtain the user profile from server 102. The user profile may be stored in server 102 and / or another storage location communicatively coupled to network 110 (e.g., device 106). 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 of the user and may be used to update the data communication module to simulate the user's carrier settings.

[0050] At step 308, the controller 119 or server 102 of vehicle 104 can assign SIM data associated with a carrier plan to the vehicle's data communication module to virtually replicate the user's SIM based on a matching user profile. Assigning SIM data associated with the user's carrier plan to the data communication module allows the data communication module to simulate a user's cellular 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 can then use the vehicle to make and receive calls and transmit data to access their own carrier plan through the data communication module. In embodiments, the vehicle may be equipped with a hands-free system, for example, for making phone calls and / or sending text messages or other digital communications.

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

[0052] At step 312, the controller 119 of vehicle 104 can identify a second user of the vehicle. The second user can be identified in a similar manner to the first user (hereinafter referred to as the "user"). For example, one or more biometric identifiers (e.g., voice, fingerprint, etc.) or imaging devices can be used to capture user-specific data of the second user, and the user-specific data can be compared with user-specific data associated with a user profile ("second user profile") of the second user that can be stored on server 102 or in a storage location accessible via network 110.

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

[0054] In some embodiments, matching a user profile may include capturing images of the user using one or more of an in-vehicle camera and a device camera. For example, a user may enter a vehicle that 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 the corresponding image data may be sent to server 102 via network 110. In some embodiments, device 106 may include a device camera (e.g., imaging device 131) that may be used to match a user's profile with his or her carrier settings. For example, a user may enter a vehicle and determine that he or she wants to use his or her own carrier plan to receive and send calls and data through the vehicle. Accordingly, he or she may use the camera on device 106 to capture one or more images and may upload the images to server 102 or other locations connected to network 110, where these images may be used to match the user with his or her associated carrier plan details.

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

[0056] At step 318, the controller 119 or server 102 of vehicle 104 can configure the data communication module's operator settings such that the data communication module does not virtually copy 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 detected or identified by the vehicle, the controller 119 or server 102 of vehicle 104 can cause the data communication module to stop virtually copying the user's SIM data. Accordingly, the user's operator plan may no longer be used to send and receive calls and data within the vehicle. In some embodiments, the data communication module may stop virtually copying the user's SIM data after a certain period of time if the controller 119 or server 102 of vehicle 104 does not identify the user (e.g., using biometric data, image data, etc.). For example, if the user stops using one or more of the multiple vehicles 104 and, for example, leaves the vehicle, then he or she will no longer be identified by the cameras in the vehicle. The server 102 can receive a signal from the vehicle that the user is no longer identifiable and can adjust the settings of the data communication module so that it no longer virtually copies the user's SIM data, and therefore the vehicle may no longer be able to access the user's data and may no longer send and receive calls and / or data.

[0057] At step 320, the controller 119 or server 102 of vehicle 104 can configure the carrier settings of the data communication module such that the data communication module does not virtually copy the second user's SIM based on the second user being no longer identifiable. For example, if the second user leaves the vehicle and is no longer detected by the vehicle, the controller 119 or server 102 of vehicle 104 can cause the data communication module to stop virtually copying the second user's SIM. Accordingly, the second user's carrier plan may no longer be used to send and receive calls and data within the vehicle. In some embodiments, the data communication module may stop virtually copying the second user's SIM data after a certain period of time if the server 102 does not recognize the second user (e.g., using biometric data, image data, etc.). For example, if the second user stops using one or more of the multiple vehicles 104 and, for example, leaves the vehicle, then he or she will no longer be recognized by the cameras in the vehicle. The controller 119 or server 102 of 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 communication module so that it no longer virtually copies the second user's SIM data, and therefore the vehicle may no longer be able to access the user's data and may no longer send and receive calls and / or data.

[0058] Now for reference Figure 1 and Figure 4 This illustrates an exemplary scenario where system 100 is used to identify one or more users and assign the operator plan details of those one or more users to the vehicle's data communication module. Figure 4 Three vehicles are shown: a first vehicle 104a, a second vehicle 104b, and a third vehicle 104c. The first vehicle 104a, the second vehicle 104b, and the third vehicle 104c may be substantially similar and may be vehicles available for use in car-sharing or car rental services. Each vehicle may include network interface hardware 124 (which may be configured to or may include a data communication module), a user identification module 120 (which includes an imaging device 121), and an interactive display 122. Each of the first vehicle 104a, the second vehicle 104b, and the third vehicle 104c may have a data communication module that includes SIM data from the original equipment manufacturer (OEM). This SIM data may be in the form of an actual SIM card or may be virtually copied based on SIM data stored, for example, in a storage location on server 102 and / or locally stored on the vehicle. The OEM SIM data may allow the vehicle to connect to network 110 using the OEM's cellular plan, enabling the vehicle to send data related to vehicle use (e.g., diagnostic and other data discussed herein).

[0059] Figure 4 The first user 105 and the second user 107 in the first vehicle 104a are shown. (Reference) Figure 1 and Figure 4 Server 102 can use one or more in-vehicle systems (e.g., one or more user identification devices) to identify the first user 105 and the second user 107. For example, imaging device 121 can be used to identify the first user 105 and the second user 107. For example, imaging device 121 can be a camera mounted in the rearview mirror 109 of the first vehicle 104a. In some embodiments, the first vehicle 104a may 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 users (e.g., device 106), etc. The identification device, in this case, is imaging device 121, for capturing identification data about one or more users and providing such identification data to server 102 (e.g., via network 110). In some embodiments, a user's device can be used to identify the user. For example, imaging device 131 of the user identification module 130 of device 106 can be used to capture an image of the user and that image data can be used to identify the user.

[0060] Server 102 can receive user identification data from the vehicle and retrieve a user profile matching the user (e.g., using user profile identification module 112), and can identify the carrier settings or carrier plan associated with the user. Carrier settings may be associated with a cellular voice and / or data plan and with the user's SIM card; that is, the user's personal cellular voice and / or data plan.

[0061] The SIM data can be virtually copied using the data communication module of the first vehicle 104a. This virtual copying of the user's SIM data may not affect the original equipment manufacturer's (OEM) SIM data, which can also be used to send and receive calls and data. Accordingly, both the user and the OEM can simultaneously send and receive cellular calls and data via the data communication module. Similarly, a second user can be identified by the controller of the first vehicle 104a using one or more identification devices, and their SIM data associated with their carrier plan can be virtually copied on the data communication module, allowing the OEM, the first user, and the second user to each use the data communication module to send and receive calls and data. Consequently, neither the first user nor the second user needs to pair their cellular device with the phone using, for example, Bluetooth pairing. The system simply identifies the first user and the second user and virtually assigns their SIMs to the data communication module.

[0062] In some embodiments, the controller of the first vehicle 104a may require an affirmative response from the user before copying the user's SIM data using the data communication module. For example, the controller of the first vehicle 104a may provide confirmation or other information to the first user 105 and the second user 107 and may need to receive information from the first user 105 and / or the second user 107 before assigning his or her carrier details to the data communication module. For example, an interactive display 122 may be used to present the user with a request for information. For example, a question such as: "Do you wish to assign your SIM data to the data communication module in order to send and receive cellular calls and data using the vehicle? Yes or No." The controller of the first vehicle 104a may virtually copy the user's SIM based on the response.

[0063] It should now be understood that users of car-sharing or car rental services can be identified by the vehicle, and their own carrier plans can be used to virtually replicate the user's SIM data to send and receive cellular calls and data using the vehicle's data communication module. Accordingly, users do not need to bother pairing their phones with the vehicle via Bluetooth or other connections, or even carry their phones into the vehicle. Furthermore, this virtual replication can be optional for the user, allowing them to protect their privacy when needed. Consequently, the use of car-sharing and car rental services may surge when one or more such systems are implemented.

[0064] It should be noted that the terms “substantially” and “approximately” are used herein to indicate the inherent degree of uncertainty attributable to any quantitative comparison, value, measurement, or other representation. These terms are also used herein to indicate the extent to which a quantitative representation may differ from the reference stated therein without altering the fundamental function of the subject matter.

[0065] While specific embodiments have been illustrated and described herein, it should be understood that various other changes and modifications may be made without departing from the spirit and scope of the claimed subject matter. Furthermore, although various aspects of the claimed subject matter have been described herein, these aspects need not be used in combination. Therefore, the appended claims are intended to cover all such changes and modifications within the scope of the claimed subject matter.

Claims

1. A method for virtually replicating a user's SIM, comprising: Use one or more of biometrics, speech recognition, and image recognition to identify the first user; Send the first user's identifier to the server; Obtain a first user profile of the first user from the server. The first user profile is associated with the identifier of the first user. The first user profile includes SIM data associated with the operator's plan. The SIM data associated with the operator plan from the obtained first user profile is allocated to the data communication module to virtually replicate the first user's SIM data; as well as Since the first user is no longer identifiable, the operator settings of the data communication module are restored to their original settings.

2. The method as described in claim 1, wherein the data communication module is a vehicle data communication module.

3. The method of claim 1, wherein when the original settings are applied to the data communication module, SIM data associated with the original equipment manufacturer (OEM) is uploaded to the data communication module, wherein the SIM data associated with the OEM is assigned to the data communication module to virtually replicate the OEM's SIM data.

4. The method of claim 1, wherein the SIM data associated with the operator plan and the SIM data associated with the original equipment manufacturer of the obtained first user profile are simultaneously allocated to the data communication module.

5. The method of claim 1, further comprising: Identify the second user; Obtain a second user profile that matches the identifier of the second user, wherein the second user profile includes SIM data associated with the second user's operator plan; The SIM data associated with the second user's operator plan from the obtained second user profile is allocated to the data communication module to simultaneously and virtually replicate the SIM data of the first user and the SIM data of the second user. Configure the operator settings of the data communication module so that the data communication module does not virtually copy the SIM data of the first user when the first user is no longer identifiable; as well as Configure the data communication module's operator settings so that, based on the fact that the second user is no longer identifiable, the data communication module does not virtually copy the second user's SIM data.

6. The method of claim 1, wherein identifying the first user comprises: The image of the first user is captured using one or more of the vehicle-mounted camera and the device camera; as well as The image of the first user is compared with one or more images stored in the database.

7. The method of claim 1, further comprising: The system presents options for setting up the carrier settings of the data communication module to copy the first user's SIM data based on the carrier plan associated with the obtained first user profile; The first user selects whether to set operator settings to copy the first user's SIM data; as well as Based on the received first user's selection of carrier settings, the first user's SIM data is copied. The display of the first user's portable device presents the first user with options to set carrier settings.

8. A system for virtually replicating a user's SIM, comprising: Data communication module, and The controller is configured to: Use one or more of biometrics, voice recognition, and image recognition to identify the first user of the vehicle; Send the first user's identifier to the server; Obtain a first user profile of the first user from the server. The first user profile is associated with the identifier of the first user. The first user profile includes SIM data associated with the operator's plan. The SIM data associated with the operator plan from the obtained first user profile is assigned to the vehicle's data communication module to virtually replicate the first user's SIM data; as well as Since the first user is no longer recognizable by the vehicle, the operator settings of the data communication module are restored to their original settings.

9. A vehicle comprising: Data communication module, and The controller is configured to: Assign SIM data associated with the original equipment manufacturer's operator plan to the data communication module; Use one or more of biometrics, voice recognition, and image recognition to identify the first user of the vehicle; Send the first user's identifier to the server; Obtain a first user profile of the first user from the server. The first user profile is associated with the identifier of the first user. The first user profile includes SIM data associated with the operator's plan. The SIM data associated with the operator's plan from the obtained first user profile is allocated to the vehicle's data communication module to virtually replicate the first user's SIM data; as well as Since the first user is no longer identifiable by the vehicle, the operator settings of the data communication module are restored.

Images