Method for providing access to services on a vehicle computing system

Abstract

Computer-activated procedure, including: Receiving an initial identifier associated with a wireless device to connect a vehicle computer system to a remote network; Receiving a second identifier associated with a vehicle that contains a vehicle computing system; Determine a service scope that is associated with at least the first or the second identifier; Providing access to services that correspond to the identified scope of services; Identifying a user, at least partially based on the first identifier; Determining the vehicle containing the vehicle computer system, at least partially based on the second identifier; Determine whether the user has a specific affiliation with the vehicle; Determine whether the user has a similar affiliation with a second vehicle, where the second vehicle has a different service scope than the first vehicle containing the vehicle computing system; and Providing access to services that correspond to the determined scope of services for the second vehicle.

Description

BACKGROUND 1. Technical field

[0001] The illustrative embodiments generally relate to a network for providing services. More specifically, the illustrative embodiments relate to a network for providing a variety of services and a variety of features for a vehicle communication system that is connected to the network via a mobile device or other device capable of wireless connectivity.

[0002] Specifically, the invention relates to a method for providing access to services on a vehicle computer system according to claim 1. 2. State of the art

[0003] Using a mobile phone while driving, particularly for texting, is demonstrably more deadly than driving under the influence of alcohol, according to a recent study by the Transport Research Laboratory in the UK. With the advent of GPS systems, drivers can potentially endanger themselves in another way by engaging in dialogue with a personal navigation device while driving. In addition to the potential dangers of texting and GPS dialogue, drivers may also have access to the mobile internet on a PDA or similar device and check their emails or sports scores while driving.

[0004] While none of these activities (PDA dialogue, GPS dialogue, text messages, retrieving news, weather reports, sports results, etc.) are dangerous in themselves, they become a significant hazard when performed by a driver.

[0005] Even with a passenger present, the driver can still perform all the aforementioned actions, thereby endangering all passengers in the vehicle as well as other drivers. While some existing systems offer these capabilities via voice control, the driver often has to manually activate the voice function. Furthermore, if multiple voice-controlled devices are active simultaneously, commands directed at one device can be unintentionally received and processed by a second. This can lead to confusion and further distraction.

[0006] Since the driver may also try to prevent this confusion by switching devices or their voice command mode on and off, distraction can occur even if all available devices are voice-controlled.

[0007] DE 10 2007 049 018 A1 relates to a method and a device for transmitting emergency data and audio signals in a motor vehicle, wherein an emergency data set is transmitted via conventional GSM transmission channels and according to GSM standards (CSD, Circuit Switched Data) when necessary and then switched to an audio connection.

[0008] DE 10 2004 061 356 A1 describes a telecommunications system in which a connection is to be made using pseudonyms without disclosing the subscriber data.

[0009] DE 102 25 786 A1 describes a method for transmitting vehicle information between the vehicle and a remote server, whereby the transmission takes place via a standardized WAP network protocol, among other things using a login process provided in the standard.

[0010] DE 103 23 384 A1 describes a remote diagnostic system for a vehicle, whereby the identification of the vehicle to the remote diagnostic system is carried out via a vehicle identification number.

[0011] US 2008 / 0102854A1 describes a vehicle telematics system in which the telematics unit can contain various data, such as "subscriber authentication information" or "vehicle identifiers".

[0012] US 2004 / 0203634A1 describes a vehicle telematics system in which authentication for access to a voice menu system is carried out via a user account number, on the basis of which certain services can also be enabled. SUMMARY

[0013] One object of the invention is to provide a method for providing access to services on a vehicle computer system in which the problems described above are eliminated.

[0014] This problem is solved by a method having the features of claim 1.

[0015] Advantageous embodiments of the invention are explained in the dependent patent claims.

[0016] In an illustrative embodiment, the service provisioning network includes at least one automatic call distribution (ACD) system for routing incoming calls. The ACD can route calls to at least one agent terminal, at least one IVR system, and / or at least one modem for extracting data embedded in a voice signal.

[0017] The network can also include at least one Call Control Gateway (CCG) for managing ACD resources and at least one System Administration Manager (SAM) for ensuring network security. The SAM can also determine a Vehicle Identification Number (VIN) associated with an incoming call and offer services to that caller based, at least partially, on the determined VIN. The SAM can further store call records, including the VINs associated with each call.

[0018] In a second illustrative embodiment, a service delivery system comprises a service delivery network and a vehicle communication system.

[0019] The service delivery network includes at least one automatic call distribution (ACD) system to route incoming calls, at least one call control gateway (CCG) to manage ACD resources, and at least one system administration manager (SAM) to ensure network security.

[0020] The vehicle communication system includes a computer processor that communicates with persistent and non-persistent memory. The communication system also includes a transmitter / receiver capable of communicating with a wireless device and which communicates with the processor.

[0021] In this illustrative embodiment, the processor can automatically establish a connection to the service provisioning network via the wireless device. Furthermore, the SAM can automatically scan an incoming call from the processor for information associated with the call.

[0022] In another illustrative embodiment, a computer-activated method (executed, for example, by a server) includes receiving a first identifier associated with the wireless device, which connects a vehicle computer system to a remote network.

[0023] The procedure also includes receiving a second identifier associated with a vehicle containing a vehicle computer system and determining a service scope associated with at least the first or the second identifier.

[0024] Finally, the procedure includes providing access to services that correspond to the identified scope of services.

[0025] In another illustrative embodiment, a service access method activated by a vehicle computing system includes the delivery of an initial identifier to a remote network, which is connected to a wireless device capable of communicating with a vehicle computing system and the remote network.

[0026] The procedure also includes the delivery of a second identifier, associated with a vehicle containing the vehicle computing system, to the remote network.

[0027] The procedure further includes access to one or more services, whereby the services were made accessible at least in part by virtue of both the first and the second identifier. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Further aspects and features of the illustrative embodiments will become apparent from the following detailed description of exemplary embodiments with reference to the accompanying drawings, wherein: Fig. 1 shows an illustrative example of a vehicle communication and entertainment system capable of establishing a network connection; Fig. 2 shows an illustrative example of a service delivery network; and Fig. Figure 3 shows an illustrative example of a Data-over-Voice (DOV) connection to a network resource providing DOV functionality. DETAILED DESCRIPTION

[0029] The present invention is described here in connection with certain exemplary, illustrative embodiments. However, it should be apparent to those with a normal level of expertise that the disclosed exemplary, illustrative embodiments can be produced without departing from the true scope and spirit of the invention. In short, the following descriptions are given merely as examples, and the present invention is not limited to any of the illustrative embodiments disclosed herein.

[0030] Fig. Figure 1 illustrates an exemplary block topology for a vehicle-based computing system (VCS) 1 for a vehicle 31. An example of such a vehicle-based computing system 1 is the SYNC system manufactured by THE FORD MOTOR COMPANY. A vehicle equipped with a vehicle-based computing system may include a visual front interface 4 located in the vehicle. The user may also be able to interact with the interface, for example, if it is equipped with a touchscreen. In another illustrative embodiment, the interaction takes place through keystrokes, audible speech, and speech synthesis.

[0031] At the in Fig. In the illustrative embodiment 1 shown, a processor 3 controls at least part of the operation of the vehicle-based computing system. Installed in the vehicle, the processor allows the processing of instructions and utility programs on board. Furthermore, the processor is connected to both a non-permanent memory 5 and a permanent memory 7. In this illustrative embodiment, the non-permanent memory is RAM and the permanent memory is a hard disk drive (HDD) or flash memory.

[0032] The processor is also equipped with a number of different inputs through which the user and processor can interface. In this illustrative embodiment, a microphone 29, an auxiliary input 25 (for input 33), a USB input 23, a GPS input 24, and a BLUETOOTH input 15 are provided. An input selector switch 51 is also provided so that the user can switch between different inputs. Both the inputs via the microphone and the auxiliary input are converted from analog signals to digital signals by a converter 27 before being forwarded to the processor.

[0033] Output options for the system include a display device 4 and a speaker 13, or a stereo system output. The speaker is connected to an amplifier 11 and receives its signal from the processor 3 via a digital-to-analog converter 9. Output can also be made via the bidirectional data streams designated 19 and 21 to a remote Bluetooth device such as a PND 54 or a USB device such as a vehicle navigation system 60.

[0034] In one illustrative embodiment, the system 1 uses the BLUETOOTH transmitter / receiver 15 to communicate 17 with a user's mobile device 53 (e.g., mobile phone, smartphone, PDA, or other device with a wireless connection to a remote network). The mobile device can then be used to communicate 59 with a network 61 outside the vehicle 31, for example, by communicating 55 with a cell tower 57. In some embodiments, the tower 57 may be a WiFi access point.

[0035] Example communication between the mobile device and the BLUETOOTH transmitter / receiver is represented by signal 14.

[0036] Connecting a mobile device 53 to the BLUETOOTH transmitter / receiver 15 can be initiated via a button 52 or a similar input. The CPU is then informed that the onboard BLUETOOTH transmitter / receiver is being connected to a BLUETOOTH transmitter / receiver in a mobile device.

[0037] Data can be exchanged between the CPU 3 and the network 61, for example, using a data plan assigned to the mobile device 53, the data-over-voice mode, or via dual-frequency dialing. Alternatively, it may be desirable to include an onboard modem 63 with an antenna 18 to transmit data between the CPU 3 and the network 61 over the voice band 16. The mobile device 53 can then be used to communicate 59 with a network 61 outside the vehicle 31, for example, by communicating 55 with a mobile phone tower 57. In some embodiments, the modem 63 can establish a connection 20 with the tower 57 for communication with the network 61. As a non-restrictive example, the modem 63 can be a USB mobile modem and the connection 20 a mobile phone connection.

[0038] In one illustrative embodiment, the processor is equipped with an operating system including an API for communication with the modem application software. The modem application software can access an integrated module or firmware on the Bluetooth transmitter / receiver to establish wireless communication with a remote Bluetooth transmitter / receiver (such as that found in a mobile device).

[0039] In another embodiment, the mobile device 53 includes a modem for voice band or broadband data communication. In a data-over-voice embodiment, a technique known as frequency division multiplexing may be implemented if the owner of the mobile device can also speak through the device during data transmission. At other times, when the owner is not using the device, data transmission can take place over the entire bandwidth (in one example, 300 Hz to 3.4 kHz).

[0040] If the user has a data plan associated with the mobile device, it is possible that the data plan permits broadband transmission and the system can utilize a much wider bandwidth (which speeds up data transmission). In another embodiment, the mobile device 53 is replaced by a mobile communication device (not shown) attached to the vehicle 31. In yet another embodiment, the ND 53 can be a wireless LAN network device capable of communicating via, for example (but not exclusively), an 802.11g network (i.e., WiFi) or a WiMAX network.

[0041] In one embodiment, incoming data can be routed via a data-over-voice or data plan through the mobile device, then through the Bluetooth transmitter / receiver, and into the vehicle's internal processor 3. In the case of certain temporary data, the data can be stored, for example, on the hard drive or another storage medium 7 until it is no longer needed.

[0042] Other sources that can interface with the vehicle include a personal navigation device 54, which may, for example, have a USB port 56 and / or an antenna 58; or a vehicle navigation device 60 with a USB port 62 or other port, an on-board GPS device 24 or a remote navigation system (not shown) connected to a network 61.

[0043] Furthermore, the CPU could communicate with a variety of other auxiliary devices 65. These devices could be connected via a wireless connection 67 or a wired connection 69. The CPU could also, or alternatively, be connected to a vehicle-based router 73, which, for example, uses a WiFi transmitter / receiver 71. This could allow the CPU to connect to remote networks within range of the local router 73. Auxiliary devices 65 could include, among other things, personal media players, wireless medical devices, portable computers, and the like.

[0044] Fig. Figure 2 shows an illustrative example of a Service Delivery Network (SDN) 200. For example, a vehicle communication system establishes a connection to the service delivery network via a mobile network 61. The vehicle communication system can also establish a connection via a variety of other networks, such as a local area network if it is connected to a router.

[0045] In one or more illustrative embodiments, a connection arriving at the SDN can be routed by an Automated Call Distributor (ACD). In this illustrative embodiment, the ACD is a device that can direct or distribute incoming calls, for example, to a specific group of terminals used by agents, to interactive voice response (IVR) systems, modem pools for extracting electronic data, and so on. An exemplary, non-restrictive ACD could consist of hardware for terminals and exchanges, telephone lines, software for a routing strategy, and so forth.

[0046] A routing strategy can be a rule based on a set of instructions that directs the ACD (Automatic Call Distribution) regarding the handling of calls in the SDN (Software Definition Network). This routing determines the best available resource for an incoming call / connection. Additional information attached to incoming connections can be used to determine the reason for a particular call or connection. This information can include, among other things, the caller's phone number or automatic number identification (ANI). If the system can "guess" the reason for a call, it facilitates call routing.

[0047] The ACD can perform a variety of different functions. For example, the ACD can support voice and data traffic between switching centers, monitor the activity of queues and agents for the effective allocation of appropriate resources, and perform telephone service functions.

[0048] The ACD can also exchange data between callers and applications in real time. Since the ACD can be equipped with the ability to "guess" the reason for a call, it can function as an intelligent answering system. The ACD can also archive calls and call logs if desired. For example, the ACD can maintain a call log for each call, recording information such as the call's wait time in the ACD queue, how long the call was on hold, how many times the call was transferred, and caller-specific information from the closure data of an agent or IVR system when the call is closed or the service is no longer in use. Each call can also be assigned a unique identifier.

[0049] Another aspect of ACD's "intelligence" lies in its ability to intelligently balance loads based on the day of the week, time of day, and other predefined parameters. Furthermore, intelligent routing is possible by leveraging customer data previously stored in a database. For example, if a particular caller calls daily at 5:00 PM for a stock market update, the system can, based on past performance, assume that a call arriving from that same caller at 5:03 PM is also for securities verification and allocate the appropriate resources accordingly. If the call is intended for a different purpose, the resources can be reassigned as needed.

[0050] In addition to the ACD, a Call Control Gateway (CCG) can be used to manage ACD resources and assist in allocating resources to incoming calls / connections. Naturally, other resources may also be allocated to the network, which are likewise managed by a CCG.

[0051] For example, in one illustrative implementation, the CCG creates a unique session identifier and uses this number to route a call to different resources, for example depending on the caller's needs in the SDN.

[0052] In an illustrative embodiment, calls that need to be moved between different elements of the SDN are assigned, monitored, and handled via a CCG.

[0053] Among other things, a sample CCG can create rules and tables for routing, forwarding, and managing calls in the ACD. The ACD can access these rules and tables and determine how to handle an incoming call. The CCG can interact with telephone and internet services simultaneously, provided an interface for both exists.

[0054] Additionally, a CCG can be designed to be scalable, allowing it to scale up (or down) as network demand increases. Finally, the CCG can monitor the health and well-being of the SDN.

[0055] A System Administration Manager (SAM) 207 may also be assigned to the SDN. Among other things, the SAM may be responsible for the security and certification of users, callers, applications, and services on the SDN. The SAM may have direct access to a customer database and, for example, be responsible for granting or denying services to callers based on criteria attributable to individual caller accounts.

[0056] The SAM can also be used to retrieve reports, documentation, usage patterns (both local and remote), and more. The SAM can also store and update individual user records. These records can be used in a variety of ways, including for intelligent call routing by the ACD and billing for chargeable services.

[0057] The documents and corresponding reports can be stored and retrieved based on a number of criteria. A non-exhaustive list includes, for example: individual users, individual services, individual applications, time of day, day of the week, telephone numbers, and vehicle identification numbers (VINs) associated with calls from a vehicle-based communication system.

[0058] The SAM can monitor and ensure security for the SDN, for example, by assigning login IDs and passwords to users. Because the SAM can store and retrieve reports, it is also well-positioned to identify patterns of unauthorized access. The SAM can also provide certification for applications, including third-party applications.

[0059] One of the applications to which a call can be routed is the IVR System 215. The IVR System is an automated telephone information system that speaks to a caller using a combination of predefined voice menus and data retrieved in real time from a database. For example, the system can greet the caller with the predefined word "Hello" followed by the username "Susan," which is dynamically retrieved from a database.

[0060] The caller can respond to questions or menus presented by the IVR by speaking or pressing keys with an answer key. Additionally, a command spoken by the caller can be processed by the vehicle communication system and transmitted as DTMF tones for a specific key. The caller may also be able to speak short phrases that the IVR can understand.

[0061] The IVR is useful for a variety of applications, including telephone banking, booking flights, ordering products and services, etc. Since the user can handle all necessary commands and inputs via the vehicle communication system, the driving experience becomes safer than if the user had to manually enter all the information, for example, into a PDA with internet access.

[0062] Voice portals, systems with upstream speech recognition software, can be designed and integrated into an IVR to help the user obtain the desired information.

[0063] The IVR can be capable of phonetically recognizing a very large vocabulary, independent of the speaker. It can also be capable of recognizing natural language (such as spoken sentences) and numbers. Continuous alphanumeric recognition can be offered, allowing the user to speak a string of alphanumeric characters. The IVR can also be interruptible, allowing the user to call out a command or phrase if they already know which option is desired. It may also be desirable to equip the IVR with multilingual functionality.

[0064] Another service to which calls can be routed is a Data-over-Voice (DOV) provider. The DOV provider offers a mechanism for sending and receiving data over a voice channel. This is referred to in Fig. 3 described.

[0065] In addition to the listed network components, an SDN can be connected to a network provider backend 225. This backend can provide essential system services and can also be used by the network provider for direct access to the system.

[0066] Also connected to the SDN in this illustrative embodiment are information services 221, which provide callers with the requested information; a POI database 223, which directs drivers to points of interest; a route engine 209, which assists with navigation to destinations; a traffic database 211 for real-time traffic information; and telephone service operators 217, who assist callers. The SDN can connect to some or all of these additional services via WANs 213, 227, as some of these services are provided by other vendors. However, all of them contribute to the SDN's capabilities in this illustrative embodiment via the WAN connection.

[0067] Fig. Figure 3 shows an illustrative example of a data-over-voice (DOV) connection to a network resource providing DOV functionality. On the connection side of the vehicle communication system, a media gateway module (MGM) 301 is provided to establish the DOV connection. Through an interface with one or more client APIs 303, which provide DOV-specific APIs 305, the MGM can connect to a mobile device, such as a mobile phone, for DOV transmission. The DOV client implementation 307 handles the connection to the mobile device and the connection to the network. In an illustrative embodiment, the network 309 is a public switched telephone network (PSTN), although any suitable network can provide the connection between the client and server.

[0068] At the backend, a switching center 311 is used as part of the SDN to route incoming DOV calls to a server 317, which runs a DOV server implementation 313. The DOV server implementation 313 has access to one or more DOV APls 321, 323, which are designated as server applications 315, 319.

[0069] The DOV APIs at both ends enable seamless data transmission over voice signal carrier lines and allow clients and servers to send information as DOV. The DOV connection can be initiated from either end, either as a call from the server to the client or as a call from the client to the server.

[0070] In an illustrative implementation, the DOV server automatically restarts without human intervention in the event of a failure. This allows for virtually continuous service. The DOV server can also log all SNMP connection attempts and the IP address of an SNMP manager.

[0071] Given the variety of services available to the user on an SDN, a differentiation of various services may be desirable, e.g., automatic, free, upgrade services, etc. Of course, any classifications and chapter numbering can be used.

[0072] Similarly, certain services can be used in a vehicle, online, from a mobile device, etc. Again, all plausible service methods are considered.

[0073] Since it is possible that a user may be in a vehicle that does not belong to the user, certain services may be disabled unless the user's phone is the primary phone for the vehicle in which the user is driving or ownership of the vehicle is otherwise detected.

[0074] Finally, it may be possible for a user to own more than one vehicle, so documentation can be kept on the user's personal "vehicle fleet" to ensure that the options available to the owner are accessible in all vehicles.

[0075] Given the wide variety of possible service offerings and locations where a service can be provided, it may require more than a simple CIN (mobile phone ID) to verify a user's authorization to use a service.

[0076] In one example scenario, there are four service levels. This illustrative, non-restrictive example includes automatic services offered with the vehicle, which are initially included and activated. These services include, for example, maintenance and recall alerts, as well as emergency services.

[0077] A second service tier consists of free services that users can download and / or activate, for example, using a mobile device or via a website. These services include, among others, music players, email readers, etc.

[0078] A third service tier, referred to as upgrade services, encompasses services that may be standard equipment in some higher-end vehicles or offered as promotional features, which later become paid services upon use. These could include premium OEM and third-party applications.

[0079] A fourth service classification could include vehicle- and / or fleet-specific services. This classification can be combined with other classifications to define a service that is only available in a specific group of vehicles or to a specific vehicle belonging to the owner.

[0080] If the SDN uses only a CIN for user identification, the SDN knows nothing about the user except the information associated with the CIN. This may or may not be sufficient for accessing certain services. For example, the VINs of a user's vehicle(s) may contain relevant information, so a CIN is sufficient to grant basic access rights.

[0081] However, if permissions are restricted to a specific vehicle, the SDN does not know whether the user is in that vehicle or in any vehicle at all.

[0082] Similarly, SDN may not be able to determine whether a particular user is authorized to use a particular service if the mobile device only transmits the VIN corresponding to the vehicle the user is driving.

[0083] In this illustrative example, there are four types of services for use in specific environments (these examples are for illustrative purposes only and are not intended to be limiting). These services include user-specific services, vehicle-specific services, vehicle-user-specific services, and fleet-user-specific services.

[0084] Based on the identification achieved through a combination of VIN and CIN, and cross-references to information stored on the SDN, the SDN can determine whether a specific user can access a particular service when that service is requested. Similarly, when a service list is requested, the SDN can use these identifiers to determine which services to list.

[0085] Although there are numerous ways to classify a user, SDN receives this information in this case. Fig.4. In the illustrative embodiment shown, an incoming request for the use of network 401.

[0086] This request is made using a CIN and a VIN (or a null string indicating that the mobile device is not currently connected to the vehicle). In this example, the system first checks the CIN to see if the user is associated with CIN 403.

[0087] For example, a user might have an account where the CIN is the primary number or account identifier, or the CIN might be associated with one or more vehicles as a primary or secondary number. It's also conceivable that in an environment where devices can be addressed, instead of owning a CIN, the device's address or another identifier could be used. However, in this example, a CIN is used because the connection originates directly from a device with a CIN.

[0088] The check can be performed using a database, reference table, etc. If the user is associated with the CIN, the system "sets up" the user 413 and grants access to the services to which that user belongs 415 (e.g., subscription-based services that are not restricted by vehicle).

[0089] If the user is not associated with the CIN, the system checks whether services are associated with the VIN (405). For example, if a new user connects a phone to a rental or loan vehicle, but that user does not have an account or connection to the remote network, it may still be desirable to provide certain services that are based within the vehicle itself. This allows access to services without a user account or membership. Any services available with that vehicle will be offered to the user as accessible (417) if the check is successful.

[0090] Next, the system checks whether services are associated with the user in this vehicle (407). That is, the system checks whether the user is in the vehicle with which the user is associated and whether the user-vehicle combination entitles the user to services associated with that combination. If there are services that a particular user is entitled to use in a particular vehicle, these services are then provided (419).

[0091] Finally, in this illustrative example, this process may include a check to see if the user associated with this CIN is registered with the remote network as the owner of the vehicle 409.

[0092] If the user is the owner, the system can further check whether the user owns other vehicles registered in the system (411). Ownership of multiple vehicles may entitle the user to transfer services as if the user were driving the other vehicle.

[0093] For example, the purchase of a luxury vehicle may entitle the user of that vehicle to use service X for a predetermined or unlimited period while driving any vehicle owned by the owner. This is a "fleet-transferable" premium service for the user's personal vehicle fleet.

[0094] Therefore, if the user drives a second vehicle and owns that vehicle, the user is entitled to use the service that came with the first vehicle because they own both vehicles. The user thus receives all fleet-accessible services 421.

[0095] Once all checks are complete and the access levels have been determined, the system disconnects from connection 423. Of course, this is just one example of how service levels are determined. For instance, the determination can also be based on service requests and limited to a specific request (as opposed to pre-authorization by the user). Other suitable identification methods are possible and are being considered.

Claims

[1] Computer-activated procedure, comprising: Receiving an initial identifier associated with a wireless device to connect a vehicle computer system to a remote network; Receiving a second identifier associated with a vehicle that contains a vehicle computing system; Determine a service scope that is associated with at least the first or the second identifier; Providing access to services that correspond to the identified scope of services; Identifying a user, at least partially based on the first identifier; Determining the vehicle containing the vehicle computer system, at least partially based on the second identifier; Determine whether the user has a specific affiliation with the vehicle; Determine whether the user has a similar affiliation with a second vehicle, where the second vehicle has a different service scope than the first vehicle containing the vehicle computing system; and Providing access to services that correspond to the determined scope of services for the second vehicle. [2] Method according to claim 1, wherein determining the service scope includes determining the service scope associated with both the first and the second identifier. [3] Method according to claim 1, characterized by , that the first identifier is a wireless phone number associated with a wireless phone. [4] Method according to claim 1, wherein the second identifier is a vehicle identification number. [5] Method according to claim 1, further comprising: Determining a first user, based at least partially on the first identifier; Determining the vehicle containing the vehicle computer system, at least partially based on the second identifier; Determination of whether the first user has a specific affiliation with the vehicle; Determine whether a second user with a similar vehicle affiliation has a different service scope than the first user; and Providing access to services that correspond to the identified service scope for the second user. [6] Method according to claim 1, wherein the belonging to the vehicle is that of an owner. [7] Method according to claim 1, wherein the belonging to the vehicle is that of a non-owner. [8] Method according to claim 5, wherein the belonging to the vehicle is that of an owner. [9] Method according to claim 5, wherein the belonging to the vehicle is that of a non-owner.

Images