Patent Grant
9591482
None.
Not applicable.
Not applicable.
Companies may want potential subscribers to subscribe to their services as simply as possible. Telematics units may provide in-vehicle telematics services. Telematics units are computers within vehicles that receive sensor information from sensor computers associated with the vehicle. Telematics units may need to be registered for telematics services to activate telematics services.
In an embodiment, a method of registering a vehicle telematics unit for telematics services is disclosed. The method comprises contacting a mobile network operator to register a telematics unit of a vehicle for telematics services by a mobile communication device of a subscriber. The method further comprises providing a vehicle identification number (VIN) of the vehicle that the telematics unit is associated with by the mobile communication device. The method further comprises looking up an unpublished phone number of the telematics unit based on the VIN of the vehicle by the mobile network operator from a computer. The method further comprises sending an electronic message via a data communication link to the telematics unit to remove incoming voice call blocking of the phone number of the telematics unit by a mobile communication network from a computer, wherein voice call blocking prevents incoming voice calls from being completed to the telematics unit. The method further comprises placing a voice call to the unpublished phone number of the telematics unit by the mobile network operator. The method further comprises validating the subscriber by the mobile network operator, wherein validation is implied by a powered-on state of the telematics unit. The method further comprises engaging in a voice dialog with the subscriber associated with the vehicle by the mobile network operator via the telematics unit, wherein the subscriber registers for telematics services. The method further comprises after completing the voice dialog with the subscriber that registers for the telematics services, sending an electronic message via a data communication link to the telematics unit to reestablish voice call blocking of the telematics unit of the vehicle by the mobile communication network.
In an embodiment, a method of registering a vehicle telematics unit for telematics services is disclosed. The method comprises contacting a mobile network operator to register a telematics unit of a vehicle for telematics services by an email message from a subscriber, wherein the email message provides a vehicle identification number (VIN) for the vehicle that is associated with the telematics unit, wherein the email is sent from a computer. The method further comprises looking up an unpublished phone number of the telematics unit based on the VIN of the vehicle by the mobile network operator from a computer. The method further comprises sending an electronic message to the telematics unit via a data communication link to remove incoming voice call blocking of the vehicle telematics unit by the mobile communication network, wherein voice call blocking prevents incoming voice calls from being completed to the telematics unit. The method further comprises placing a voice call to the unpublished phone number of the telematics unit by the mobile network operator. The method further comprises validating the subscriber by the mobile network operator, wherein validation is implied by a powered-on state of the vehicle telematics unit. The method further comprises engaging in a dialog with the subscriber associated with the vehicle by the mobile network operator via the telematics unit, wherein the subscriber registers for telematics services. The method further comprises after completing the voice dialog with the subscriber that registers for the telematics services, sending an electronic message via a data communication link to the telematics unit to reestablish voice call blocking of the telematics unit of the vehicle by the mobile communication network.
In an embodiment, a method of registering a vehicle telematics unit for telematics services is disclosed. The method comprises contacting a mobile network operator to register a telematics unit for mobile communication services by a mobile communication device of a subscriber. The method further comprises providing a vehicle identification number (VIN) of a vehicle associated with the telematics unit of the subscriber by the mobile communication device. The method further comprises looking up an unpublished phone number of the telematics unit based on the VIN of the vehicle by the mobile network operator from a workstation computer. The method further comprises sending an electronic message to the telematics unit via a data communication link to remove incoming voice call blocking of the phone number of the telematics unit by a mobile communication network, wherein voice call blocking prevents incoming voice calls from being completed to the telematics unit, wherein the telematics unit controls voice call blocking of the vehicle. The method further comprises placing a voice call to the unpublished phone number of the telematics unit by the mobile network operator. The method further comprises validating the subscriber by the mobile network operator, wherein validation is implied with a powered-on state of the telematics unit. The method further comprises engaging in a voice dialog with the subscriber associated with the vehicle by the mobile network operator, wherein the subscriber registers the telematics unit for telematics services. The method further comprises after completing the voice dialog with the subscriber, sending an electronic message to the vehicle telematics unit to reestablish voice call blocking of the telematics unit by the mobile network operator.
These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.
For a more complete understanding of the present disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.
It should be understood at the outset that although illustrative implementations of one or more embodiments are illustrated below, the disclosed systems and methods may be implemented using any number of techniques, whether currently known or not yet in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, but may be modified within the scope of the appended claims along with their full scope of equivalents.
The present disclosure teaches a plurality of methods that promote registering a vehicle telematics unit for telematics services. Telecommunications service providers may provide in-vehicle telematics services that they want subscribers to register for. Telematics services may comprise one or more of remote vehicle lock/unlock, and/or start service; wireless voice communication service; wireless data communication service; remote diagnostic service; remote maintenance service; and other services supported by wireless communication links. These telematics services may be available for use in the vehicle after user registration. A common scenario may be that a new car buyer may be offered an initial period of free telematics services, and the registration may be completed by the user at the car dealer's venue or shortly after purchase of the vehicle, for example at home parked in the driveway. In the past, registration for such telematics services may have been tedious for subscribers and may have resulted in frustration for the subscriber or in the subscriber not registering for telematics services at all. Telecommunications service providers may wish to improve the rate at which subscribers register for in-vehicle telematics services, for example to expand their subscriber base or to increase their revenues. The method of registration disclosed herein may allow for simplified registration of an in-vehicle telematics unit for telematics services that are provided by a telecommunication service provider.
In an embodiment, a subscriber contacts a mobile network operator to register a telematics unit of a vehicle for telematics services using a mobile communication device. The services for which the telematics unit and/or the subscriber is registering, comprises one or more of remote door unlock and global positioning services. In an embodiment, the mobile network operator is associated with a telecommunication service provider. The subscriber provides the mobile network operator a vehicle identification number (VIN) of the vehicle that the telematics unit is associated with. The mobile network operator then searches for an unpublished phone number of the telematics unit based on the VIN of the vehicle. In an embodiment, the unpublished phone number is located in an unpublished phone number data store. The mobile network operator then sends an electronic message to a mobile communication network to remove incoming voice call blocking of the phone number of the telematics unit via the mobile communication network. Voice call blocking prevents incoming voice calls from being completed to the telematics unit. In an embodiment, voice call blocking functionality may be located in the mobile communication network that is accessed by the mobile network operator (e.g., the network detects an attempt to originate a voice call to the telematics unit and prevents that origination attempt from propagating to the telematics unit).
Alternatively, voice call blocking may instead be provided by the telematics unit (e.g., the voice call origination attempt propagates to the telematics unit, but the telematics unit itself then blocks further call processing of the voice call origination attempt, the driver experiences no ringing of an incoming call and the call is not completed). In this alternative, the mobile network operator may send an electronic message to the subject telematics unit to remove incoming voice call blocking by the telematics unit (temporarily suspend incoming voice call blocking). After registration for telematics services has been completed, the mobile network operator may send a subsequence electronic message to the telematics unit to restore incoming voice call blocking by the telematics unit.
The mobile network operator then places a voice call to the unpublished phone number of the telematics unit. In an embodiment, the subscriber may email the mobile network operator to initiate the registration process. If the subscriber emails the mobile network operator, there is an about 2 minute delay that is provided between the contact that the subscriber sends to initiate the call and the time that the mobile network operator calls the unpublished number of the telematics unit. The mobile network operator then validates the subscriber, wherein validation is implied by a powered-on state of the telematics unit. The mobile network operator directs the call to the telematics unit where the telematics unit rings. In response to the telematics unit ringing, the voice call is answered by someone in the vehicle. The telematics unit will not ring unless the vehicle is in a powered-on state (e.g., with a key present and the vehicle turned on). It is assumed by the mobile network operator that a person in the vehicle with the key present and the telematics unit in a powered-on state is authorized. In an embodiment, it is useful for the call blocking of the telematics unit to be turned back on after the completion of a call in order to promote safety for the owner of the vehicle so as to remove possible distractions while driving. For example, unexpected voice calls placed to the telematics unit may distract the driver while driving the vehicle, increasing the chances that the driver may be involved in an accident. The present disclosure teaches temporarily removing that call blocking when initializing or registering for telematics services and then restoring call blocking after registration for telematics services has been completed. It is thought that the temporary suspension of call blocking for the telematics unit, under these circumstances (the vehicle is probably stationary), and the restoration of call blocking after registration for telematics services is complete may have a negligible effect on safety.
The mobile network operator then engages in a voice dialog with the subscriber associated with the vehicle, where the subscriber registers the telematics unit of the vehicle for telematics services. The mobile network operator may ask the subscriber questions to facilitate the completion of a profile. Some of the profile information may comprise name, age, residence, marital status, or other profile information. After completing the voice dialog with the subscriber that registers for the telematics services, the mobile network operator sends an electronic message to reestablish voice call blocking of the telematics unit of the vehicle via the mobile communication network. In an embodiment, the telematics unit is activated when the subscriber registers for telematics services. Activation of the telematics unit may comprise network provisioning and updating a hardware configuration of the telematics unit.
In an embodiment, the subscriber may send an email to the mobile network operator to initiate registration. In the email, the subscriber may provide the VIN of the vehicle so that the mobile network operator may look up the unpublished phone number of the telematics unit that is associated with the vehicle. In an embodiment, the subscriber may be able to call the mobile network operator directly from the vehicle via the telematics unit.
With the provided registration methods, telecommunications service providers may be able to register more subscribers to telematics services. The provided registration methods simplify the process of registration and activation for subscribers so that they may register for telematics services.
Turning now to
In an embodiment, the mobile communication device 102 is associated with a subscriber that is associated with the vehicle 113. The subscriber may use the mobile communication device 102 to register the telematics unit 112 of the vehicle 113 for and to activate telematics services by contacting the mobile network operator 116. The mobile network operator 116 may be a call center employee that operates via the network 114. The subscriber gives the vehicle identification number (VIN) of the vehicle 113 to the mobile network operator 116 who accesses the unpublished phone number data store 118 to locate the unpublished phone number of the telematics unit 112. For example, the mobile network operator 116 uses a work station or computer to command a database management tool to look up the unpublished phone number of the telematics unit 112 using the VIN as a key. In an embodiment, the unpublished phone number is associated with the VIN of the vehicle 113. In an embodiment, the mobile network operator 116 and the unpublished phone number data store 118 are associated with a telecommunication service provider. In an embodiment, the telematics unit 112 receives sensor data from a plurality of vehicle systems. The vehicle systems that send sensor data to the telematics unit 112 may comprise one or more of an oxygen sensor, an air pressure sensor, an air temperature sensor, an engine temperature sensor, a throttle position sensor, a knock sensor, and other sensors.
After locating the unpublished phone number in the phone number data store 118, the mobile network operator 116 sends an electronic message to remove incoming voice call blocking of the phone number of the telematics unit 112 via the network 114. In an embodiment, voice call blocking prevents incoming voice calls from being completed to the telematics unit 112. The call blocking functionality may be located either in the network 114 or in the telematics unit 112 itself. The suspension of the voice call blocking functionality is done over a data channel between the network 114 and the telematics unit 112; the data channel is not blocked. The mobile network operator 116 places a voice call to the unpublished phone number of the telematics unit 112. Once the subscriber has answered, the mobile network operator 116 validates the subscriber, wherein validation is implied by a powered-on state of the telematics unit 112. With the subscriber validated, the mobile network operator 116 engages in a voice dialog with the subscriber associated with the vehicle 113. During the dialog, the subscriber registers the telematics unit 112 for telematics services. In an embodiment, the telematics services that the subscriber may register for may comprise one or more of remote door unlock, global positioning system (GPS) services, and other telematics services.
After the voice dialog is completed with the subscriber, the mobile network operator 116 sends an electronic message to reestablish voice call blocking of the telematics unit 112 of the vehicle 113 via the network 114. In an embodiment, the base transceiver stations 120 and/or 122 may provide a wireless communication link to the mobile communication device 102 to the network 114. In an embodiment, the base transceiver stations 120, 122 may provide a wireless communication link to the communication device 102 according to one of a code division multiple access (CDMA) wireless protocol, a global system for mobile communications (GSM) wireless protocol, a long term evolution (LTE) wireless protocol, a worldwide interoperability for microwave access (WiMAX) wireless protocol, or another well-known wireless communication protocol. While one mobile communication device 102 and two base transceiver stations 120, 122 are illustrated in
In an embodiment, a subscriber's mobile communication device 102 contacts a mobile network operator 116 to register the telematics unit 112 of the vehicle 113 for telematics services. In an embodiment, the telematics services, for which the telematics unit 112 is registering for, may comprise one or more of remote door unlock, global positioning system (GPS) services, remote diagnosis, wherein remote diagnosis allows a user to check what aspects of a vehicle have been previously worked on or other telematics services. The telematics unit 112 may be activated when the subscriber registers for the telematics services, wherein activation of the telematics unit 112 comprises network provisioning and updating hardware configuration of the telematics unit 112.
In an embodiment the mobile network operator 116 and the telematics services are associated with a telecommunications service provider. The subscriber then provides a vehicle identification number (VIN) of the vehicle 113 that the telematics unit 112 is associated with via the mobile communication device 102. After receiving the VIN from the subscriber, the mobile network operator 116 looks up an unpublished phone number of the telematics unit based on the VIN of the vehicle 113. In an embodiment, the unpublished phone number of the telematics unit 112 is located in the unpublished phone number data store 118. The unpublished phone number is associated with the VIN of the vehicle 113.
The mobile network operator 116 then sends an electronic message to remove incoming voice call blocking of the phone number of the telematics unit 112 via the network 114. Voice call blocking prevents incoming voice calls from being completed to the telematics unit 112. In an embodiment, the voice call blocking functionality is located in the network 114, the telematics unit 112, or another location that may control voice call blocking functionality of the telematics unit 112. The mobile network operator 116 then places a voice call to the unpublished phone number of the telematics unit 112. In an embodiment, the subscriber may email the mobile network operator 116 to initiate the registration process and may include the VIN of the vehicle 113 in the email. If the subscriber emails the mobile network operator 116, the system 100 may provide a delay of about 2 minutes between the time the email is received by the mobile network operator 116 and the time that the voice call is placed to the telematics unit 112, thereby giving the user or subscriber time to find the key to the car, walk to the car, unlock the car, enter the car, and turn the engine on or engage the accessories switch. If the subscriber does not respond to the call to the telematics unit 112, the mobile network operator 116 may call in an additional 2 minutes.
The mobile network operator 116 validates the subscriber associated with the vehicle 113, wherein validation is implied with a powered-on state of the telematics unit 112. The mobile network operator 116 engages in a voice dialog with the subscriber associated with the vehicle 113. While the vehicle 113 may be associated with a particular subscriber, it is possible for people close to the subscriber to register for the telematics services, e.g., a father or mother registering for a child that received a new vehicle such as the vehicle 113. During the voice dialog, the subscriber registers the telematics unit 112 for telematics services. After completing the voice dialog with the subscriber, the mobile network operator 116 sends an electronic message to reestablish voice call blocking of the telematics unit 112 of the vehicle 113 via the network 114.
In
In
It is understood that by programming and/or loading executable instructions onto the computer system 380, at least one of the CPU 382, the RAM 388, and the ROM 386 are changed, transforming the computer system 380 in part into a particular machine or apparatus having the novel functionality taught by the present disclosure. It is fundamental to the electrical engineering and software engineering arts that functionality that can be implemented by loading executable software into a computer can be converted to a hardware implementation by well-known design rules. Decisions between implementing a concept in software versus hardware typically hinge on considerations of stability of the design and numbers of units to be produced rather than any issues involved in translating from the software domain to the hardware domain. Generally, a design that is still subject to frequent change may be preferred to be implemented in software, because re-spinning a hardware implementation is more expensive than re-spinning a software design. Generally, a design that is stable that will be produced in large volume may be preferred to be implemented in hardware, for example in an application specific integrated circuit (ASIC), because for large production runs the hardware implementation may be less expensive than the software implementation. Often a design may be developed and tested in a software form and later transformed, by well-known design rules, to an equivalent hardware implementation in an application specific integrated circuit that hardwires the instructions of the software. In the same manner as a machine controlled by a new ASIC is a particular machine or apparatus, likewise a computer that has been programmed and/or loaded with executable instructions may be viewed as a particular machine or apparatus.
Additionally, after the system 380 is turned on or booted, the CPU 382 may execute a computer program or application. For example, the CPU 382 may execute software or firmware stored in the ROM 386 or stored in the RAM 388. In some cases, on boot and/or when the application is initiated, the CPU 382 may copy the application or portions of the application from the secondary storage 384 to the RAM 388 or to memory space within the CPU 382 itself, and the CPU 382 may then execute instructions that the application is comprised of. In some cases, the CPU 382 may copy the application or portions of the application from memory accessed via the network connectivity devices 392 or via the I/O devices 390 to the RAM 388 or to memory space within the CPU 382, and the CPU 382 may then execute instructions that the application is comprised of. During execution, an application may load instructions into the CPU 382, for example load some of the instructions of the application into a cache of the CPU 382. In some contexts, an application that is executed may be said to configure the CPU 382 to do something, e.g., to configure the CPU 382 to perform the function or functions promoted by the subject application. When the CPU 382 is configured in this way by the application, the CPU 382 becomes a specific purpose computer or a specific purpose machine.
The secondary storage 384 is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if RAM 388 is not large enough to hold all working data. Secondary storage 384 may be used to store programs which are loaded into RAM 388 when such programs are selected for execution. The ROM 386 is used to store instructions and perhaps data which are read during program execution. ROM 386 is a non-volatile memory device which typically has a small memory capacity relative to the larger memory capacity of secondary storage 384. The RAM 388 is used to store volatile data and perhaps to store instructions. Access to both ROM 386 and RAM 388 is typically faster than to secondary storage 384. The secondary storage 384, the RAM 388, and/or the ROM 386 may be referred to in some contexts as computer readable storage media and/or non-transitory computer readable media.
I/O devices 390 may include printers, video monitors, liquid crystal displays (LCDs), touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, or other well-known input devices.
The network connectivity devices 392 may take the form of modems, modem banks, Ethernet cards, universal serial bus (USB) interface cards, serial interfaces, token ring cards, fiber distributed data interface (FDDI) cards, wireless local area network (WLAN) cards, radio transceiver cards that promote radio communications using protocols such as code division multiple access (CDMA), global system for mobile communications (GSM), long-term evolution (LTE), worldwide interoperability for microwave access (WiMAX), near field communications (NFC), radio frequency identity (RFID), and/or other air interface protocol radio transceiver cards, and other well-known network devices. These network connectivity devices 392 may enable the processor 382 to communicate with the Internet or one or more intranets. With such a network connection, it is contemplated that the processor 382 might receive information from the network, or might output information to the network in the course of performing the above-described method steps. Such information, which is often represented as a sequence of instructions to be executed using processor 382, may be received from and outputted to the network, for example, in the form of a computer data signal embodied in a carrier wave.
Such information, which may include data or instructions to be executed using processor 382 for example, may be received from and outputted to the network, for example, in the form of a computer data baseband signal or signal embodied in a carrier wave. The baseband signal or signal embedded in the carrier wave, or other types of signals currently used or hereafter developed, may be generated according to several methods well-known to one skilled in the art. The baseband signal and/or signal embedded in the carrier wave may be referred to in some contexts as a transitory signal.
The processor 382 executes instructions, codes, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk (these various disk based systems may all be considered secondary storage 384), flash drive, ROM 386, RAM 388, or the network connectivity devices 392. While only one processor 382 is shown, multiple processors may be present. Thus, while instructions may be discussed as executed by a processor, the instructions may be executed simultaneously, serially, or otherwise executed by one or multiple processors. Instructions, codes, computer programs, scripts, and/or data that may be accessed from the secondary storage 384, for example, hard drives, floppy disks, optical disks, and/or other device, the ROM 386, and/or the RAM 388 may be referred to in some contexts as non-transitory instructions and/or non-transitory information.
In an embodiment, the computer system 380 may comprise two or more computers in communication with each other that collaborate to perform a task. For example, but not by way of limitation, an application may be partitioned in such a way as to permit concurrent and/or parallel processing of the instructions of the application. Alternatively, the data processed by the application may be partitioned in such a way as to permit concurrent and/or parallel processing of different portions of a data set by the two or more computers. In an embodiment, virtualization software may be employed by the computer system 380 to provide the functionality of a number of servers that is not directly bound to the number of computers in the computer system 380. For example, virtualization software may provide twenty virtual servers on four physical computers. In an embodiment, the functionality disclosed above may be provided by executing the application and/or applications in a cloud computing environment. Cloud computing may comprise providing computing services via a network connection using dynamically scalable computing resources. Cloud computing may be supported, at least in part, by virtualization software. A cloud computing environment may be established by an enterprise and/or may be hired on an as-needed basis from a third party provider. Some cloud computing environments may comprise cloud computing resources owned and operated by the enterprise as well as cloud computing resources hired and/or leased from a third party provider.
In an embodiment, some or all of the functionality disclosed above may be provided as a computer program product. The computer program product may comprise one or more computer readable storage medium having computer usable program code embodied therein to implement the functionality disclosed above. The computer program product may comprise data structures, executable instructions, and other computer usable program code. The computer program product may be embodied in removable computer storage media and/or non-removable computer storage media. The removable computer readable storage medium may comprise, without limitation, a paper tape, a magnetic tape, magnetic disk, an optical disk, a solid state memory chip, for example analog magnetic tape, compact disk read only memory (CD-ROM) disks, floppy disks, jump drives, digital cards, multimedia cards, and others. The computer program product may be suitable for loading, by the computer system 380, at least portions of the contents of the computer program product to the secondary storage 384, to the ROM 386, to the RAM 388, and/or to other non-volatile memory and volatile memory of the computer system 380. The processor 382 may process the executable instructions and/or data structures in part by directly accessing the computer program product, for example by reading from a CD-ROM disk inserted into a disk drive peripheral of the computer system 380. Alternatively, the processor 382 may process the executable instructions and/or data structures by remotely accessing the computer program product, for example by downloading the executable instructions and/or data structures from a remote server through the network connectivity devices 392. The computer program product may comprise instructions that promote the loading and/or copying of data, data structures, files, and/or executable instructions to the secondary storage 384, to the ROM 386, to the RAM 388, and/or to other non-volatile memory and volatile memory of the computer system 380.
In some contexts, the secondary storage 384, the ROM 386, and the RAM 388 may be referred to as a non-transitory computer readable medium or a computer readable storage media. A dynamic RAM embodiment of the RAM 388, likewise, may be referred to as a non-transitory computer readable medium in that while the dynamic RAM receives electrical power and is operated in accordance with its design, for example during a period of time during which the computer system 380 is turned on and operational, the dynamic RAM stores information that is written to it. Similarly, the processor 382 may comprise an internal RAM, an internal ROM, a cache memory, and/or other internal non-transitory storage blocks, sections, or components that may be referred to in some contexts as non-transitory computer readable media or computer readable storage media.
While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted or not implemented.
Also, techniques, systems, subsystems, and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5892900 | Ginter et al. | Apr 1999 | A |
| 6622083 | Knockeart et al. | Sep 2003 | B1 |
| 7209964 | Dugan et al. | Apr 2007 | B2 |
| 7366892 | Spaur et al. | Apr 2008 | B2 |
| 7376392 | Myojo | May 2008 | B2 |
| 7454473 | Suzuki | Nov 2008 | B2 |
| 7912224 | Lee et al. | Mar 2011 | B2 |
| 7949375 | Kortge | May 2011 | B2 |
| 7966111 | Moinzadeh et al. | Jun 2011 | B2 |
| 8271050 | Weiss | Sep 2012 | B2 |
| 8417823 | Luna et al. | Apr 2013 | B2 |
| 8457686 | Przybylski | Jun 2013 | B2 |
| 8484707 | Bertz et al. | Jul 2013 | B1 |
| 8527164 | Staudinger et al. | Sep 2013 | B2 |
| 8548532 | Ng | Oct 2013 | B1 |
| 8606335 | Ozaki | Dec 2013 | B2 |
| 8626152 | Farrell et al. | Jan 2014 | B2 |
| 8630747 | Burcham et al. | Jan 2014 | B2 |
| 8676199 | Madhavan et al. | Mar 2014 | B2 |
| 8750942 | Ng | Jun 2014 | B1 |
| 8787949 | Sumcad et al. | Jul 2014 | B2 |
| 8918244 | Brzezinski et al. | Dec 2014 | B2 |
| 8994591 | Dupray et al. | Mar 2015 | B2 |
| 9002574 | Garrett et al. | Apr 2015 | B2 |
| 9031498 | Bertz et al. | May 2015 | B1 |
| 9032547 | Hohler et al. | May 2015 | B1 |
| 9110774 | Bonn et al. | Aug 2015 | B1 |
| 9173238 | Bloomcamp et al. | Oct 2015 | B1 |
| 9252951 | Katzer et al. | Feb 2016 | B1 |
| 9398454 | Burcham et al. | Jul 2016 | B1 |
| 9439240 | Shipley et al. | Sep 2016 | B1 |
| 9444892 | Amireddy et al. | Sep 2016 | B1 |
| 20010042107 | Palm | Nov 2001 | A1 |
| 20030066884 | Reddy et al. | Apr 2003 | A1 |
| 20030096641 | Odinak | May 2003 | A1 |
| 20030120601 | Ouye et al. | Jun 2003 | A1 |
| 20030224840 | Frank et al. | Dec 2003 | A1 |
| 20040044585 | Franco | Mar 2004 | A1 |
| 20040083041 | Skeen et al. | Apr 2004 | A1 |
| 20040125957 | Rauber et al. | Jul 2004 | A1 |
| 20040157650 | Wissinger et al. | Aug 2004 | A1 |
| 20050021744 | Haitsuka et al. | Jan 2005 | A1 |
| 20050065779 | Odinak | Mar 2005 | A1 |
| 20050113102 | Kwon et al. | May 2005 | A1 |
| 20060059480 | Kimoto | Mar 2006 | A1 |
| 20060087971 | Kim et al. | Apr 2006 | A1 |
| 20060143463 | Ikeda et al. | Jun 2006 | A1 |
| 20060154659 | Roter et al. | Jul 2006 | A1 |
| 20060168578 | Vorlicek | Jul 2006 | A1 |
| 20070028220 | Miller et al. | Feb 2007 | A1 |
| 20070047466 | Todokoro | Mar 2007 | A1 |
| 20070086579 | Lorello et al. | Apr 2007 | A1 |
| 20070113269 | Zhang | May 2007 | A1 |
| 20070124043 | Ayoub et al. | May 2007 | A1 |
| 20070124045 | Ayoub et al. | May 2007 | A1 |
| 20070124046 | Ayoub et al. | May 2007 | A1 |
| 20070160199 | Sekiguchi et al. | Jul 2007 | A1 |
| 20070288423 | Kimoto | Dec 2007 | A1 |
| 20080021633 | Naito et al. | Jan 2008 | A1 |
| 20080034126 | Baker | Feb 2008 | A1 |
| 20080072047 | Sarikaya et al. | Mar 2008 | A1 |
| 20080148374 | Spaur et al. | Jun 2008 | A1 |
| 20080162676 | Magnusson | Jul 2008 | A1 |
| 20080289018 | Kawaguchi | Nov 2008 | A1 |
| 20080289044 | Choi | Nov 2008 | A1 |
| 20080307086 | Brooks et al. | Dec 2008 | A1 |
| 20090028082 | Wynn et al. | Jan 2009 | A1 |
| 20090049119 | Marcinkiewicz et al. | Feb 2009 | A1 |
| 20090109941 | Carter | Apr 2009 | A1 |
| 20090217036 | Irwin et al. | Aug 2009 | A1 |
| 20090265278 | Wang et al. | Oct 2009 | A1 |
| 20090287499 | Link, II | Nov 2009 | A1 |
| 20100054219 | Humblet et al. | Mar 2010 | A1 |
| 20100097239 | Campbell et al. | Apr 2010 | A1 |
| 20100136944 | Taylor et al. | Jun 2010 | A1 |
| 20100197362 | Saitoh et al. | Aug 2010 | A1 |
| 20100220250 | Vanderwall et al. | Sep 2010 | A1 |
| 20100234071 | Shabtay et al. | Sep 2010 | A1 |
| 20100235285 | Hoffberg | Sep 2010 | A1 |
| 20100245122 | Haralson | Sep 2010 | A1 |
| 20100260350 | Chutorash et al. | Oct 2010 | A1 |
| 20100285787 | Matsuda | Nov 2010 | A1 |
| 20110009107 | Guba et al. | Jan 2011 | A1 |
| 20110086668 | Patel | Apr 2011 | A1 |
| 20110090908 | Jacobson et al. | Apr 2011 | A1 |
| 20110098044 | Aoyagi | Apr 2011 | A1 |
| 20110099316 | Tseng et al. | Apr 2011 | A1 |
| 20110111728 | Ferguson | May 2011 | A1 |
| 20110252415 | Ricci | Oct 2011 | A1 |
| 20110257973 | Chutorash et al. | Oct 2011 | A1 |
| 20110263293 | Blake et al. | Oct 2011 | A1 |
| 20110295444 | Westra et al. | Dec 2011 | A1 |
| 20110310731 | Park et al. | Dec 2011 | A1 |
| 20120028597 | Chmielewski | Feb 2012 | A1 |
| 20120028607 | Tengler et al. | Feb 2012 | A1 |
| 20120028656 | Yi | Feb 2012 | A1 |
| 20120109406 | Yousefi et al. | May 2012 | A1 |
| 20120127139 | Hayami et al. | May 2012 | A1 |
| 20120134497 | Roitshtein et al. | May 2012 | A1 |
| 20120142367 | Przybylski | Jun 2012 | A1 |
| 20120159638 | McDade, Sr. | Jun 2012 | A1 |
| 20120167071 | Paek | Jun 2012 | A1 |
| 20120183221 | Alasry et al. | Jul 2012 | A1 |
| 20120203557 | Odinak | Aug 2012 | A1 |
| 20120282895 | Bai et al. | Nov 2012 | A1 |
| 20120324046 | Park | Dec 2012 | A1 |
| 20130082820 | Tieman | Apr 2013 | A1 |
| 20130205026 | Ricci | Aug 2013 | A1 |
| 20130218400 | Knoop et al. | Aug 2013 | A1 |
| 20130226391 | Nordbruch et al. | Aug 2013 | A1 |
| 20130297456 | Annan et al. | Nov 2013 | A1 |
| 20130304281 | Burcham et al. | Nov 2013 | A1 |
| 20140053261 | Gupta et al. | Feb 2014 | A1 |
| 20140068010 | Nicholson et al. | Mar 2014 | A1 |
| 20140087760 | Bennett | Mar 2014 | A1 |
| 20140128047 | Edwards | May 2014 | A1 |
| 20140130036 | Gurikar et al. | May 2014 | A1 |
| 20140143354 | Tiernan | May 2014 | A1 |
| 20140222298 | Gurin | Aug 2014 | A1 |
| 20140222910 | Petersen et al. | Aug 2014 | A1 |
| 20140336919 | Li et al. | Nov 2014 | A1 |
| 20150288636 | Yalavarty et al. | Oct 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 102011112546 | Apr 2014 | DE |
| 20062441 | Sep 2006 | JP |
| WO2013166418 | Nov 2013 | WO |
| WO2013173331 | Nov 2013 | WO |
| Entry |
|---|
| Foreign Communication From a Related Counterpart Application, International Preliminary Report on Patentability dated Nov. 13, 2014, PCT/US13/39514 filed on May 3, 2013. |
| Foreign Communication From a Related Counterpart Application, International Preliminary Report on Patentability dated Nov. 27, 2014, PCT/US13/40940 filed on May 14, 2013. |
| Notice of Allowance dated Dec. 3, 2014, U.S. Appl. No. 13/094,494, filed Apr. 26, 2011. |
| First Action Interview Pre-Communication dated Dec. 1, 2014, U.S. Appl. No. 13/844,226, filed Mar. 15, 2013. |
| Notice of Allowance dated Jan. 6, 2015, U.S. Appl. No. 13/661,536, filed Oct. 26, 2012. |
| Supplemental Notice of Allowance dated Jan. 30, 2015, U.S. Appl. No. 13/661,536, filed Oct. 26, 2012. |
| Restriction Requirement dated Mar. 19, 2015, U.S. Appl. No. 13/463,799, filed May 3, 2012. |
| Final Office Action dated Mar. 17, 2015, U.S. Appl. No. 13/769,268, filed Feb. 15, 2013. |
| Notice of Allowance dated Mar. 12, 2015, U.S. Appl. No. 13/844,226, filed Mar. 15, 2013. |
| Amireddy, Sridhar Reddy, et al., Patent Application entitled, “Vehicle Remote Operations Control,” filed Apr. 28, 2015, U.S. Appl. No. 14/698,522. |
| Notice of Allowance dated Jun. 12, 2015, U.S. Appl. No. 13/769,268, filed Feb. 15, 2013. |
| First Action Interview Pre-Communication dated Jul. 9, 2015, U.S. Appl. No. 14/034,475, filed Sep. 23, 2013. |
| Restriction Requirement dated Feb. 24, 2015, U.S. Appl. No. 14/304,861, filed Jun. 13, 2014. |
| Office Action dated Jun. 30, 2015, U.S. Appl. No. 14/304,861, filed Jun. 13, 2014. |
| Restriction Requirement dated Sep. 4, 2015, U.S. Appl. No. 13/455,121, filed Apr. 24, 2012. |
| Katzer, Robin D., “Vehicle Key Function Control From a Mobile Phone Based on Radio Frequency Link From Phone to Vehicle,” filed Jun. 13, 2014, U.S. Appl. No. 14/304,861. |
| Office Action dated Sep. 9, 2015, U.S. Appl. No. 13/463,799, filed May 3, 2012. |
| Notice of Allowance dated Sep. 18, 2015, U.S. Appl. No. 14/304,861, filed Jun. 13, 2014. |
| Belkin, Wireless Network Access Point User Manual, published by Belkin Corporation, 2003, pp. 1-36. |
| Office Action dated Jan. 13, 2016, U.S. Appl. No. 13/218,503, filed Aug. 26, 2011. |
| Final Office Action dated Mar. 10, 2016, U.S. Appl. No. 13/463,799, filed May 3, 2012. |
| First Action Interview Pre-Communication dated Jan. 29, 2016, U.S. Appl. No. 13/455,121, filed Apr. 24, 2012. |
| Notice of Allowance dated Mar. 11, 2016, U.S. Appl. No. 13/455,121, filed Apr. 24, 2012. |
| Final Office Action dated Mar. 8, 2016, U.S. Appl. No. 14/034,475, filed Sep. 23, 2013. |
| Restriction Requirement dated Jan. 29, 2016, U.S. Appl. No. 14/703,997, filed May 5, 2015. |
| Amireddy, Sridhar Reddy, et al., Patent Application entitled, “Network Event Management Support for Vehicle Wireless Communication,” filed May 5, 2015, U.S. Appl. No. 14/703,997. |
| Amireddy, Sridhar Reddy, et al., Patent Application entitled, “Vehicle Telematics Unit Communication Authorization and Authentication and Communication Service Provisioning,” filed Aug. 8, 2015, U.S. Appl. No. 14/819,425. |
| Aboda, B., et al., “Exentsible Authentication Protocol (EAP)”, Network Working Group, RFC 3748, Standards Track, Jun. 2004. |
| Foreign Communication From a Related Counterpart Application, International Search Report and Written Opinion dated Jun. 13, 2013, International Application No. PCT/US13/40940 filed on May 14, 2013. |
| Foreign Communication From a Related Counterpart Application, International Search Report and Written Opinion dated Dec. 23, 2013, International Application No. PCT/US13/39514 filed on May 3, 2013. |
| First Action Interview Office Action dated Jan. 3, 2013, U.S. Appl. No. 13/218,503, filed Aug. 26, 2011. |
| Final Office Action dated May 7, 2013, U.S. Appl. No. 13/218,503, filed Aug. 26, 2011. |
| Advisory Action dated Aug. 1, 2013, U.S. Appl. No. 13/218,503, filed Aug. 26, 2011. |
| Office Action dated Feb. 5, 2014, U.S. Appl. No. 13/218,503, filed Aug. 26, 2011. |
| Final Office Action dated Jun. 16, 2014, U.S. Appl. No. 13/218,503, filed Aug. 26, 2011. |
| Advisory Action dated Sep. 26, 2014, U.S. Appl. No. 13/218,503, filed Aug. 26, 2011. |
| Office Action-Restriction Requirement dated May 7, 2014, U.S. Appl. No. 13/094,494, filed Apr. 26, 2011. |
| Office Action dated Aug. 28, 2014, U.S. Appl. No. 13/094,494, filed Apr. 26, 2011. |
| First Action Interview Pre-Interview Communication dated Oct. 26, 2012, U.S. Appl. No. 13/156,438, filed Jun. 9, 2011. |
| Notice of Allowance dated Feb. 26, 2013, U.S. Appl. No. 13/156,438, filed Jun. 9, 2011. |
| First Action Interview Pre-Communication dated Jan. 31, 2012, U.S. Appl. No. 13/246,554, filed Sep. 27, 2011. |
| FAIPP Office Action dated May 21, 2012, U.S. Appl. No. 13/246,554, filed Sep. 27, 2011. |
| Final Office Action dated Sep. 5, 2012, U.S. Appl. No. 13/246,554, filed Sep. 27, 2011. |
| Advisory Action dated Nov. 2, 2012, U.S. Appl. No. 13/246,554, filed Sep. 27, 2011. |
| Office Action dated Dec. 5, 2012, U.S. Appl. No. 13/246,554, filed Sep. 27, 2011. |
| Notice of Allowance dated May 20, 2013, U.S. Appl. No. 13/246,554, filed Sep. 27, 2011. |
| First Action Interview Pre-Communication dated Nov. 15, 2013, U.S. Appl. No. 13/791,658, filed Aug. 20, 2013. |
| Notice of Allowance dated Jan. 30, 2014, U.S. Appl. No. 13/791,658, filed Aug. 20, 2013. |
| Office Action dated Mar. 13, 2013, U.S. Appl. No. 13/471,107, filed May 14, 2012. |
| Notice of Allowance dated Aug. 26, 2013, U.S. Appl. No. 13/471,107, filed May 14, 2012. |
| Office Action dated Aug. 12, 2014, U.S. Appl. No. 13/769,268, filed Feb. 15, 2013. |
| Office Action dated Jul. 14, 2014, U.S. Appl. No. 13/661,536, filed Oct. 26, 2012. |
| Shipley, Trevor D., et al. Patent Application entitled “Mobile Communication System Identity Pairing,” filed Aug. 26, 2011, U.S. Appl. No. 13/218,503. |
| Bertz, Lyle T., et al. Patent Application entitled “Automotive Multi-Generation Connectivity,” filed Apr. 26, 2011, U.S. Appl. No. 13/094,494. |
| Burcham, Robert H., et al. Patent Application entitled “In-car Head unit Wireless Communication Service Subscription Initialization,” filed Apr. 24, 2012, U.S. Appl. No. 13/455,121. |
| Bloomcamp, Eric Michael, et al. Patent Application entitled “Dual Path In-Vehicle Communication,” filed Feb. 15, 2013, U.S. Appl. No. 13/769,268. |
| Bonn, Michael J., et al. Patent Application entitled “System and Method of Utilizing Driving Profiles via a Mobile Device,” filed Mar. 15, 2012, U.S. Appl. No. 13/844,226. |
| Hohler, Rick A., et al., Patent Application entitled “Provisioning Vehicle based Digital Rights Management for Media Delivered via Phone,” filed Oct. 26, 2012, U.S. Appl. No. 13/662,536. |
| Bloomcamp, Eric M., et al., Patent Application entitled “Authenticating Mobile Device for on Board Diagnostic System Access,” filed Sep. 23, 2013, U.S. Appl. No. 14/034,475. |
| Notice of Allowance dated Apr. 28, 2016, U.S. Appl. No. 13/218,503, filed Aug. 26, 2011. |
| Advisory Action dated May 20, 2016, U.S. Appl. No. 13/463,799, filed May 3, 2012. |
| Advisory Action dated Jun. 1, 2016, U.S. Appl. No. 14/034,475, filed Sep. 23, 2013. |
| Notice of Allowance dated May 16, 2016, U.S. Appl. No. 14/703,997, filed May 5, 2015. |
| Service Platform for the Connected Traveler, Sep. 9, 2008, Seventh Fromwork Programme, vol. 1, 28, 43, 71, 87. |
| Office Action dated Sep. 26, 2016, U.S. Appl. No. 13/463,799, filed on May 3, 2012. |
| Office Action dated Oct. 4, 2016, U.S. Appl. No. 14/034,475, filed on Sep. 23, 2013. |
| First Action Interview Pre-Communication dated Sep. 9, 2016, U.S. Appl. No. 14/698,522, filed on Apr. 28, 2015. |
