US20180095456A1 - Remote vehicle engine immobilization - Google Patents
Remote vehicle engine immobilization Download PDFInfo
- Publication number
- US20180095456A1 US20180095456A1 US15/282,572 US201615282572A US2018095456A1 US 20180095456 A1 US20180095456 A1 US 20180095456A1 US 201615282572 A US201615282572 A US 201615282572A US 2018095456 A1 US2018095456 A1 US 2018095456A1
- Authority
- US
- United States
- Prior art keywords
- vehicle
- immobilization
- communication
- additional
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course or altitude of land, water, air, or space vehicles, e.g. automatic pilot
- G05D1/0011—Control of position, course or altitude of land, water, air, or space vehicles, e.g. automatic pilot associated with a remote control arrangement
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C9/00571—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by interacting with a central unit
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R2325/00—Indexing scheme relating to vehicle anti-theft devices
- B60R2325/10—Communication protocols, communication systems of vehicle anti-theft devices
- B60R2325/101—Bluetooth
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R2325/00—Indexing scheme relating to vehicle anti-theft devices
- B60R2325/10—Communication protocols, communication systems of vehicle anti-theft devices
- B60R2325/103—Near field communication [NFC]
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R2325/00—Indexing scheme relating to vehicle anti-theft devices
- B60R2325/10—Communication protocols, communication systems of vehicle anti-theft devices
- B60R2325/105—Radio frequency identification data [RFID]
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R25/00—Fittings or systems for preventing or indicating unauthorised use or theft of vehicles
- B60R25/20—Means to switch the anti-theft system on or off
- B60R25/24—Means to switch the anti-theft system on or off using electronic identifiers containing a code not memorised by the user
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D2201/00—Application
- G05D2201/02—Control of position of land vehicles
- G05D2201/0213—Road vehicle, e.g. car or truck
Definitions
- Modern vehicles are equipped with built-in communication devices that enable the vehicles to remotely communicate with different service providers.
- the communication devices may include subscriber identity module (SIM)-equipped network devices that enable the vehicles to use a cellular communication network to communicate with the service providers.
- SIM subscriber identity module
- the built-in communication devices may enable other devices in the vehicle to provide a multitude of services. These services may include in-vehicle security, trouble diagnostics, concierge, emergency assistance, and/or global positioning system (GPS) navigation capabilities.
- GPS global positioning system
- FIG. 1 illustrates an example environment for performing remote vehicle engine immobilization.
- FIG. 2 is a block diagram showing various components of a master control device and a vehicle communication device.
- FIG. 3 is a block diagram showing various components of an immobilizer device that performs remote vehicle engine immobilization via peer-to-peer communication.
- FIG. 4 is a flow diagram of an example process for a master control device to initiate a cellular network assisted vehicle immobilization of a vehicle.
- FIG. 5 is a flow diagram of an example process for a cellular communication carrier to initiate the broadcast of an immobilization command to a vehicle in response to the initiation of immobilization from the master control device.
- FIG. 6 is a flow diagram of an example process for a master control device to initiate a peer-to-peer vehicle immobilization of a vehicle.
- FIG. 7 is a flow diagram of an example process for a vehicle communication device on a vehicle to determine whether to disable the vehicle based on a received immobilization command.
- FIG. 8 is a flow diagram of an example process for automatically initiating remote vehicle immobilization of a vehicle using an immobilizer device.
- This disclosure is directed to techniques for using a master control device on a particular vehicle to initiate remote immobilization of an additional vehicle.
- the particular vehicle that is equipped with the master control device may be a law enforcement vehicle.
- the master control device on the particular vehicle may remotely immobilize the additional vehicle by using proximity communication to directly send an immobilization command to the additional vehicle in a peer-to-peer manner.
- the immobilization command may be received by a vehicle communication device on the additional vehicle.
- the vehicle communication device may be a subscriber identity module (SIM)-equipped communication device that is fitted with both a cellular communication radio and a wireless proximity communication transceiver.
- SIM subscriber identity module
- the vehicle communication device may trigger an engine disabler on the additional vehicle to immobilize the vehicle.
- the master control device on the initial vehicle may trigger a wireless communication carrier to use cellular communication to send an immobilization command to the additional vehicle.
- the immobilization command for the additional vehicle may be sent by an immobilizer device via proximity communication with the vehicle communication device of the additional vehicle.
- the immobilizer device may be a stationary immobilizer device or a movable immobilizer device. The immobilizer device may send the immobilization command following the immobilizer device detecting a device identifier of the vehicle communication device, and receiving a vehicle immobilization request from a law enforcement server for the device identifier.
- the immobilization of the additional vehicle may involve the immediate disablement of an engine of the vehicle, a gradual diminishment of the power outputted by the engine of the vehicle until the engine is in a stopped state, or a configuration that blocks an engine restart once the engine is manually switched off by a user.
- the engine may also be further configured to block an engine restart after the engine is in a stopped state.
- a device may remotely immobilize a vehicle via peer-to-peer device communication or network assisted communication.
- a request inputted by a user to initiate vehicle immobilization of a vehicle may be received at a master control device.
- the master control device may send an information query command to the vehicle communication device of the vehicle via proximity communication.
- the master control device may receive a device identifier from the vehicle communication device via the proximity communication.
- a vehicle immobilization request that includes the device identifier may be sent from the master control device to a wireless communication carrier.
- the request may prompt the wireless communication carrier to broadcast an immobilization command via a cellular communication network to the vehicle communication device of the vehicle that is identified by the device identifier.
- the master control device may directly send the immobilization command to the vehicle communication device.
- the techniques may enable a mobile device or an immobilizer device to remotely immobilize a vehicle via peer-to-peer device communication with a vehicle communication device of the vehicle.
- the remote immobilization may be achieved by the user triggering a cellular communication carrier to send an immobilization command to the vehicle communication device via a cellular communication connection.
- the peer-to-peer communication may be initiated by a master control device in a law enforcement vehicle. The remote immobilization of a vehicle may enable the vehicle to be safely brought to a stop without endangering the occupants of the vehicle or bystanders who are in the vicinity of the vehicle.
- the remote immobilization of the vehicle may provide law enforcement officers with an opportunity to detain the occupants without dangerous vehicle pursuits that can jeopardize public safety.
- Example implementations are provided below with reference to the following figures.
- FIG. 1 illustrates an example environment 100 for performing remote vehicle engine immobilization.
- the environment 100 may include multiple vehicles, such as the vehicles 102 - 106 .
- the vehicles 102 and 104 may be respectively equipped with vehicle communication devices 108 and 110 .
- Each vehicle communication device may enable a corresponding vehicle to remotely communicate with different service providers.
- a vehicle communication device may be a subscriber identity module (SIM)-equipped communication device that is fitted with both a cellular communication radio and a wireless proximity communication transceiver.
- SIM subscriber identity module
- the cellular communication radio may enable the vehicle communication device to obtain cellular communication services from a cellular communication network 112 of a cellular communication carrier that is identified in the SIM.
- the cellular communication network 112 may provide telecommunication and data communication in accordance with one or more technical standards, such as such as Enhanced Data Rates for GSM Evolution (EDGE), Wideband Code Division Multiple Access (W-CDMA), High Speed Packed Access (HSPA), Long Term Evolution (LTE), CDMA-2000 (Code Division Multiple Access 2000), and/or so forth.
- EDGE Enhanced Data Rates for GSM Evolution
- W-CDMA Wideband Code Division Multiple Access
- HSPA High Speed Packed Access
- LTE Long Term Evolution
- CDMA-2000 Code Division Multiple Access 2000
- the wireless proximity communication transceiver may enable the vehicle communication device to engage in short-range peer-to-peer communication with another device.
- the wireless proximity communication transceiver may be a Near Field Communication (NFC) transceiver, a Bluetooth transceiver, Radio-frequency identification (RFID), and/or so forth.
- NFC Near Field Communication
- RFID Radio-frequency identification
- the vehicle communication device of each vehicle may be equipped with a unique device identifier.
- each vehicle communication device may be capable of sending an immobilization signal to an engine immobilization device on each vehicle.
- the engine immobilization device of a vehicle that receives the immobilization signal may disable the vehicle.
- the vehicle 106 may be equipped with a master control device 116 that is used to immobilize other vehicles, such as the vehicles 102 and 104 .
- the master control device 116 may be equipped with a wireless proximity communication transceiver that interfaces with the wireless proximity communication transceivers of the vehicle communication devices 108 and 110 . In this way, the master control device 116 may obtain the device identifiers of the vehicles communication devices 108 and 110 , as well as broadcast immobilization commands to the vehicle communication devices 108 and 110 .
- the master control device 116 may be further equipped with a cellular communication radio that enables the master control device 116 to use the cellular communication network 112 .
- the master control device 116 may be connected to an image sensor 118 .
- the image sensor 118 may enable the master control device 116 to capture images of license plates, such as the license plate 120 of the vehicle 104 .
- the master control device 116 may receive a request from a user, such as a law enforcement officer 122 , to remotely immobilize a vehicle.
- the master control device 116 may establish proximity communication with the vehicle communication device of the vehicle to obtain a device identifier of the vehicle communication device.
- the master control device 116 may send a vehicle immobilization request that includes the device identifier to one or more servers 124 of the wireless communication carrier 114 .
- the servers 124 may execute software that cause the cellular communication network 112 to broadcast an immobilization command that includes the device identifier.
- the vehicle communication device of the vehicle may receive the immobilization command via the cellular communication network 112 and verify the device identifier in the command. Following verification of the device identifier, the vehicle communication device may command an engine immobilization device of the vehicle to immobilize the vehicle.
- the master control device 116 may fail to establish proximity communication with the vehicle communication device of the vehicle.
- the failure may be due to signal interference or the vehicle being out of signal range.
- the master control device 116 may be unable obtain a device identifier of the vehicle communication device within a predetermined amount of time.
- the master control device 116 may automatically activate the image sensor 118 to capture a license plate number of the vehicle.
- the master control device 116 may use the cellular communication network 112 to send the license plate number to one or more servers 126 of a government agency 128 .
- the servers 126 may execute software that queries a vehicle database 130 for a vehicle identifier that matches the license plate.
- the vehicle identifier of a vehicle may be a vehicle identification number (VIN), a chassis number, or another identifier that uniquely identifies the vehicle.
- the government agency 128 may be the Department of Motor Vehicles (DMV) or Department of Licensing (DOL) that administers the registration of motor vehicles in the jurisdiction.
- the vehicle database 130 may be a database that correlates license plate numbers of vehicles with vehicle identifiers of the vehicles.
- the servers 126 may return a vehicle identifier of the vehicle to the master control device 116 via the cellular communication network 112 .
- the master control device 116 may send a vehicle immobilization request that includes the vehicle identifier to one or more servers 124 of the wireless communication carrier 114 .
- the servers 124 may execute software that queries a carrier database 132 for a device identifier that matches the vehicle identifier.
- the carrier database 132 may be a database that correlates vehicle identifiers of vehicles with device identifiers of vehicle communication devices that are installed on the vehicles.
- the software on the servers 124 may cause the cellular communication network 112 to broadcast an immobilization command to the vehicle communication device that is associated with the device identifier.
- the master control device 116 may receive a request from a user, such as a law enforcement officer 122 , to remotely immobilize a vehicle. In turn, the master control device 116 may establish proximity communications with the vehicle communication device of the vehicle to obtain a device identifier of the vehicle communication device. At this point, instead of sending a vehicle immobilization request to the wireless communication carrier 114 , the master control device 116 may directly broadcast an immobilization command that includes the device identifier to the vehicle via proximity communication. In some embodiments, the master control device 116 may initiate peer-to-peer immobilization in the event that access to the cellular communication network 112 is unavailable.
- the master control device 116 may be unable obtain a device identifier of the vehicle communication device within a predetermined amount of time. In such an event, the master control device 116 may once again automatically activate the image sensor 118 to capture a license plate number of the vehicle. Subsequently, the master control device 116 may use the license plate number to obtain a corresponding vehicle identifier from the vehicle database 130 of the government agency 128 . The vehicle identifier is further sent by the master control device 116 to the wireless communication carrier 114 for querying against the carrier database 132 , such that the master control device 116 may obtain a corresponding device identifier of the vehicle communication device in the vehicle.
- the master control device may use the cellular communication network 112 to obtain access to the vehicle database 130 and the carrier database 132 . Subsequently, the master control device 116 may directly broadcast an immobilization command that includes the device identifier to the vehicle via proximity communication.
- immobilizer devices 134 ( 1 )- 134 (N) may be deployed at multiple locations in a geographical area.
- the immobilizer devices 134 ( 1 )- 134 (N) may be configured to continuously scan for the device identifiers of vehicle communication device-equipped vehicles traveling in the geographical area in order to detect vehicles that are of interest to a law enforcement agency. For example, a vehicle may be subject to a stolen vehicle report, an all-points bulletin (APB), an Amber alert, and/or another type of emergency broadcast alert.
- Each of the immobilizer devices 134 ( 1 )- 134 (N) may be linked to the wireless communication carrier 114 via a network 136 .
- the network 136 may include a local area network (“LAN”), a larger network such as a wide area network (“WAN”), or a collection of networks, such as the Internet. Further, the network 136 may include wired and/or wireless link components.
- an immobilizer device may be equipped with a cellular communication radio that enables the immobilizer device to communicate via the cellular communication network 112 , a wired network transceiver, and a wireless proximity communication transceiver that enables the immobilizer device to engage in communication with vehicle communication devices.
- the immobilizer devices 134 ( 1 )- 134 (N) may include immobilizer devices that are deployed as standalone fixtures, fixtures on existing structures, or movable fixtures.
- the existing structures may include toll booths, gas stations, traffic lights, light poles, traffic signs, and/or so forth.
- the immobilizer devices 134 ( 1 )- 134 (N) may include immobilizer devices that are mounted on wheeled dollies or trailers that can be moved and positioned at different locations.
- an immobilizer device may periodically broadcast information query commands.
- the immobilizer device may broadcast an information query command when an image sensor of the device detects a vehicle approaching within a predetermined distance of the device.
- the information query commands may result in a vehicle communication device of a vehicle responding with a vehicle identifier.
- the immobilizer device may receive a vehicle identifier from the vehicle communication device 108 of the vehicle 102 .
- the immobilizer device may use the cellular communication network 112 or the network 136 to send the device identifier to the servers 124 of the wireless communication carrier 114 .
- the one or more servers 124 may execute software that queries the carrier database 132 for a vehicle identifier that matches the device identifier.
- the vehicle identifier may be sent by the wireless communication carrier 114 to the servers of a law enforcement agency.
- the servers of the law enforcement agency may respond with a vehicle immobilization request if the law enforcement agency determines that the vehicle is subject to immobilization.
- the servers of the law enforcement agency may include software that consult the vehicle database 130 to determine a license plate number that corresponds to the vehicle identifier. The software may further check whether the license plate number matches a flagged license plate number targeted for immobilization. Accordingly, if the immobilizer device receives a vehicle immobilization request for the vehicle, the immobilizer device may directly broadcast an immobilization command that includes the device identifier to the vehicle via proximity communication.
- FIG. 2 is a block diagram showing various components of a master control device and a vehicle communication device.
- the master control device 116 may include a communication interface 202 , one or more processors 204 , memory 206 , and device hardware 208 .
- the communication interface 202 may include wireless and/or wired communication components that enable the master control device 116 to transmit and receive data with other networked devices.
- the communication interface 202 may include a network transceiver and proximity communication transceiver.
- the device hardware 208 may include additional hardware that performs user interface, data display, data communication, data storage, and/or other server functions.
- the device hardware 208 may include a data output device (e.g., visual display, audio speakers), and one or more data input devices.
- the data input devices may include, but are not limited to, combinations of one or more of keypads, keyboards, mouse devices, touch screens that accept gestures, microphones, voice or speech recognition devices, and any other suitable devices or other electronic/software selection methods.
- the memory 206 may be implemented using computer-readable media, such as computer storage media.
- Computer-readable media includes, at least, two types of computer-readable media, namely computer storage media and communications media.
- Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device.
- communication media may embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism.
- the processors 204 and the memory 206 of the master control device 116 may implement an operating system 210 .
- the operating system 210 may include components that enable the master control device 116 to receive and transmit data via various interfaces (e.g., user controls, communication interface, and/or memory input/output devices), as well as process data using the processors 204 to generate output.
- the operating system 210 may include a presentation component that presents the output (e.g., display the data on an electronic display, store the data in memory, transmit the data to another electronic device, etc.). Additionally, the operating system 210 may include other components that perform various additional functions generally associated with an operating system.
- the operating system 210 may be used to implement an authentication module 212 , an immobilization module 214 , an encryption module 216 , and a user interface module 218 .
- These modules may include routines, program instructions, objects, and/or data structures that perform particular tasks or implement particular abstract data types.
- the authentication module 212 may authenticate a user so that the user may create or log into a user account on the master control device 116 .
- the authentication module 212 may prompt a user to enter an authentication credential for a corresponding user account.
- the authentication credential may include one or more of a user name, a password, an electronic identifier, a digital certificate, biometric characteristics, and/or the like.
- the authentication credential may include a user identifier in the form of an officer identifier that is assigned to the law enforcement officer.
- the authentication module 212 may compare the inputted authentication credential to a list of authorize authentication credentials for user accounts stored on the master control device 116 .
- the authentication module 212 may send the authentication credential to an authentication server for authentication.
- the authentication server may be operated by a law enforcement agency and stores authentication credentials of officers that are authorized to perform remote vehicle immobilization. Accordingly, the authentication module 212 may permit the user access to the functionalities of the master control device 116 when the inputted authentication credential is found within a list of authorized authentication credentials or deemed by an authentication server as authorized.
- the immobilization module 214 may initiate the vehicle immobilization of a vehicle in the proximity of the master control device 116 based on a request inputted by a user. In response to the request, the immobilization module 214 may use a proximity communication transceiver to send an information query command to a vehicle communication device of the vehicle. Subsequently, the immobilization module 214 may determine whether a device identifier and a vehicle description of the vehicle is received from the vehicle communication device within a predetermined amount of time.
- the vehicle description of the vehicle may include a make, a model, a vehicle color, a vehicle type, a model year, and/or other pertinent information that enables the user to identify the vehicle.
- the immobilization module 214 may display the vehicle description of the vehicle on a display of the master control device 116 with a request that the user confirm the vehicle description.
- the user may confirm the vehicle description by providing a specific user input to the immobilization module 214 .
- the confirmation prompt may serve to ensure that the correct vehicle will be immobilized, as there may be multiple vehicles that are within proximity communication range of the master control device 116 .
- the immobilization module 214 may initiate a peer-to-peer immobilization or a cellular network assisted immobilization of the vehicle.
- the immobilization module 214 may initiate peer-to-peer immobilization based on a user configuration setting, based on the vehicle being within proximity communication range, and/or based on the lack of an adequate cellular communication network signal (e.g., signal strength below a strength threshold).
- the immobilization module 214 may initiate peer-to-peer immobilization by broadcasting an immobilization command that includes the device identifier of the vehicle via proximity communication.
- the immobilization module 214 may initiate cellular network assisted immobilization when proximity communication is unreliable or when configured based on a user inputted configuration setting. For example, proximity communication with the vehicle communication device of the vehicle may be unreliable due to signal interference or the vehicle being out of proximity communication range. As a consequence, the immobilization module 214 may be unable to receive the device identifier and the vehicle description of the vehicle in the predetermined amount of time. In such a scenario, the immobilization module 214 may activate the image sensor 118 to capture a license plate number of the vehicle.
- the immobilization module 214 may include a software algorithm for recognizing alphanumeric text from graphical images.
- the license plate number may then be used by the immobilization module 214 to obtain a corresponding vehicle identifier from the vehicle database 130 . Subsequently, the immobilization module 214 may send a vehicle immobilization request that includes the vehicle identifier to the wireless communication carrier 114 . In turn, the vehicle immobilization request may trigger the wireless communication carrier 114 to broadcast a corresponding immobilization command to the vehicle using the cellular communication network 112 .
- the proximity communication between the immobilization module 214 and the vehicle communication device of the vehicle may become disrupted after the immobilization module 214 has obtained the device identifier, resulting in the peer-to-peer broadcast of the immobilization request becoming ineffective.
- the immobilization module 214 may send a vehicle immobilization request that includes the device identifier to the wireless communication carrier 114 .
- the vehicle immobilization request may trigger the wireless communication carrier 114 to broadcast a corresponding immobilization command to the vehicle using the cellular communication network 112 .
- the vehicle immobilization request may further include the user identifier of the user that initiated the vehicle immobilization request.
- the servers 124 of the wireless communication carrier 114 may execute a verification algorithm to ensure that the user identifier belongs to a user that is authorized to initiate vehicle immobilization.
- the verification algorithm may send the user identifier to a verification application at the law enforcement agency to verify that the corresponding law enforcement officer is authorized to initiate immobilization of vehicles.
- the verification algorithm may check the user identifier against an internal database of users who are authorized to initiate vehicle immobilizations.
- the internal database may be periodically updated based on authorization data from various government agencies, such as law enforcement agencies.
- the immobilization module 214 may also receive notifications either directly from a vehicle communication device of a vehicle via proximity communication or from the wireless communication carrier 114 via the cellular communication network 112 .
- the notifications may include a notification that the immobilization of a vehicle is in progress once a corresponding vehicle communication device has verified and implemented the immobilization command.
- the notifications may further include a notification that the vehicle is immobilized once the vehicle communication device receives an immobilization notification from an engine disabler of the vehicle.
- the encryption module 216 may work with the encryption modules that are on the vehicle communication devices, the servers 124 of the wireless communication carrier 114 , and the servers 126 of the government agency 128 to ensure that the data exchanged between the different entities are encrypted.
- the encryption module 216 may encrypt outgoing data and decrypted incoming data using various encryption schemes.
- the encryption may be implemented using various asymmetric and symmetric encryption techniques such as public key infrastructure (PKI) key negotiation and encryption, Diffie-Hellman key exchange, and/or so forth.
- the encryption module 216 may also implement hash-based techniques to specify and verify the authenticity of the data that are exchanged between the entities.
- the hash-based techniques may include the use of MD 5 hashing, SHA- 1 hashing, and/or so forth, to generate keyed-hash message authentication codes (HMAC).
- the user interface module 218 may provide interface options for the user to configure the functionalities of the master control device 116 .
- a configuration menu provided by the user interface module 218 may enable the user to configure the immobilization module 214 to initially default to either peer-to-peer vehicle immobilization or cellular network assisted immobilization.
- Another configuration menu provided by the user interface module 218 may enable the user to customize the amount of time the immobilization module 214 waits before activating the image sensor 118 to scan for a license plate number.
- the vehicle communication device 108 may include a communication interface 220 , one or more processors 222 , device hardware 224 , and memory 226 .
- the vehicle communication device 108 may correspond to vehicle communication device 110 .
- the communication interface 220 may include wireless and/or wired communication components that enable the vehicle communication device to transmit data to and receive data from other networked devices.
- the communication interface 220 may include a network transceiver and proximity communication transceiver.
- the device hardware 224 may include additional hardware that performs user interface, data display, data communication, data storage, and/or other server functions.
- the device hardware 224 may include a data output device (e.g., visual display, audio speakers), and one or more data input devices.
- the data input devices may include, but are not limited to, combinations of one or more of keypads, keyboards, mouse devices, touch screens that accept gestures, microphones, voice or speech recognition devices, and any other suitable devices or other electronic/software selection methods.
- the device hardware 224 may further include signal converters, antennas, modems, hardware decoders and encoders, graphic processors, a SIM card slot, and/or the like that enable the vehicle communication device 108 to execute applications and provide telecommunication and data communication functions.
- a SIM card may be inserted into the SIM card slot of the vehicle communication device 108 . Accordingly, the SIM card may enable the vehicle communication device 108 to obtain telecommunication and/or data communication services from the wireless communication carrier 114 or another carrier.
- the memory 226 may be implemented using computer-readable media, such as computer storage media.
- Computer-readable media includes, at least, two types of computer-readable media, namely computer storage media and communications media.
- Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device.
- communication media may embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism.
- the processors 222 and the memory 226 of the vehicle communication device may implement an operating system 228 .
- the operating system 228 may include components that enable the master control device 116 to receive and transmit data via various interfaces (e.g., user controls, communication interface, and/or memory input/output devices), as well as process data using the processors 222 to generate output.
- the operating system 228 may include a presentation component that presents the output (e.g., display the data on an electronic display, store the data in memory, transmit the data to another electronic device, etc.). Additionally, the operating system 228 may include other components that perform various additional functions generally associated with an operating system.
- the operating system 228 may implement applications 230 .
- the applications 230 may include software that enable other software on the device to exchange data with service providers.
- the applications 230 may include data collection applications, vehicle diagnostic applications, navigation applications, autopilot applications, security applications, and/or so forth.
- the operating system 228 may be used to implement a control interface module 232 , an encryption module 234 , and trigger module 236 .
- These modules may include routines, program instructions, objects, and/or data structures that perform particular tasks or implement particular abstract data types.
- the control interface module 232 may continuously listen for information query commands and immobilization commands from another device.
- the information query commands may be received via proximity communication.
- the control interface module 232 may respond with a device identifier of the vehicle communication device as well as the vehicle description of the corresponding vehicle that is stored in the memory 226 .
- the control interface module 232 may receive immobilization commands via proximity communication or cellular communication.
- the encryption module 234 may work with the encryption modules on other devices to ensure that the exchange of data with the other devices are encrypted.
- the encryption module 234 may also verify the authenticity of the requests and commands that are received by the vehicle communication device.
- the encryption module 234 may use asymmetric or symmetric encryption to secure the data that is exchanged with the other devices.
- the encryption module 234 may generate and use HMACs to guarantee that the requests and commands are authentic.
- the control interface module 232 may respond to information query commands that are authenticated by the encryption module 234 .
- the trigger module 236 may trigger an engine disabler to immobilize the vehicle based on an immobilization command.
- the immobilization command may be verified by the encryption module 234 .
- the trigger module 236 may extract a device identifier from the immobilization command.
- the extracted device identifier may be compared to an embedded device identifier of the vehicle communication device 108 . Accordingly, if the extracted device identifier matches the embedded the device identifier, the trigger module 236 may send a signal to the engine disabler of the vehicle to immobilize the vehicle.
- the engine disabler of the vehicle may include software and/or hardware components that are configured to disable the engine the vehicle. Further, the trigger module 236 may generate a notification that the immobilization that the immobilization of the vehicle is in progress.
- the trigger module 236 may generate a notification of vehicle immobilization.
- the trigger module 236 may send the notification back to the master control device 116 via one of the proximity communication or the cellular communication network 112 .
- FIG. 3 is a block diagram showing various components of an immobilizer device 300 that performs remote vehicle engine immobilization via peer-to-peer communication.
- the immobilizer device 300 may include a communication interface 302 , one or more processors 304 , memory 306 , and device hardware 308 .
- the communication interface 302 may include wireless and/or wired communication components that enable the immobilizer device to transmit data to and receive data from other networked devices.
- the communication interface 302 may include a proximity communication transceiver, as well as network transceivers that enable the immobilizer device 300 to communicate with the wireless communication carrier 114 and the government agency 128 via the network 136 .
- the network transceivers may include a wired transceiver and a wireless transceiver.
- the device hardware 308 may include additional hardware that performs user interface, data display, data communication, data storage, and/or other server functions.
- the device hardware 308 may include a data output device (e.g., visual display, audio speakers), and one or more data input devices.
- the data input devices may include, but are not limited to, combinations of one or more of keypads, keyboards, mouse devices, touch screens that accept gestures, microphones, voice or speech recognition devices, and any other suitable devices or other electronic/software selection methods.
- the memory 306 may be implemented using computer-readable media, such as computer storage media.
- Computer-readable media includes, at least, two types of computer-readable media, namely computer storage media and communications media.
- Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device.
- communication media may embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism.
- the processors 304 and the memory 306 of the immobilizer device 300 may implement an operating system 310 .
- the operating system 310 may include components that enable the immobilizer device 300 to receive and transmit data via various interfaces (e.g., user controls, communication interface, and/or memory input/output devices), as well as process data using the processors 304 to generate output.
- the operating system 310 may include a presentation component that presents the output (e.g., display the data on an electronic display, store the data in memory, transmit the data to another electronic device, etc.). Additionally, the operating system 310 may include other components that perform various additional functions generally associated with an operating system.
- the operating system 310 may be used to implement a monitoring module 312 , a disablement module 314 , and an encryption module 316 . These modules may include routines, program instructions, objects, and/or data structures that perform particular tasks or implement particular abstract data types.
- the monitoring module 312 may send information query commands to vehicles that are in the vicinity of the immobilizer device 300 .
- the information query commands may be sent on a periodic basis (e.g., every second, every minute, etc.).
- vehicle communication devices of the vehicles that are in the vicinity of the immobilizer device 300 may respond by transmitting their device identifiers.
- the immobilizer device 300 may be equipped with an image sensor.
- the monitoring module 312 may use an image analysis algorithm to detect the arrival of new vehicles in the vicinity of the immobilizer device 300 . Accordingly, the monitoring module 312 may send an information query command when a new vehicle arrives in the vicinity of the immobilizer device 300 .
- the disablement module 314 may use the network 136 to send a device identifier to the servers 124 of the wireless communication carrier 114 to obtain a corresponding vehicle identifier from the carrier database 132 . Following the receipt of the device identifier, the disablement module 314 may send the vehicle identifier to the servers 126 at the government agency 128 via the network 136 .
- the servers 126 may execute an application to determine whether the vehicle that is identified by the vehicle identifier is subject to immobilization. For example, the vehicle may be subject to immobilization if it is the object of an outstanding APB, an Amber alert, a stolen vehicle report, and/or so forth. The servers 126 may make the determination using a vehicle immobilization request database.
- the vehicle immobilization request database may be a repository of pending vehicle immobilization requests that contains lawful requests inputted by authorized law enforcement officers of one or more law enforcement agencies.
- the servers 126 may use the vehicle database 130 to determine a license plate number of the vehicle for the purpose of checking with the vehicle immobilization request database.
- the disablement module 314 may broadcast an immobilization command that includes the device identifier of the vehicle via proximity communication for reception by the vehicle.
- the disablement module 314 may use an image sensor to capture the license plate number of a vehicle, rather than obtaining a device identifier of a vehicle communication device in the vehicle. In such instances, the disablement module 314 may send the license plate number to the servers 126 of the government agency 128 . In turn, the servers 126 may execute an application to check the license plate number against the immobilization request database.
- the encryption module 234 may work with the encryption modules of the other devices to ensure that the exchange of data with other devices are encrypted, and to verify the authenticity of the requests and commands that are received by the vehicle communication device. For example, the encryption module 234 may use asymmetric or symmetric encryption to secure the data that is exchanged with the other devices. Further, encryption module 234 may generate and use HMACs to guarantee that the requests and commands are authentic.
- FIGS. 4-8 present illustrative processes 400 - 800 for performing remote vehicle engine immobilization.
- Each of the processes 400 - 800 is illustrated as a collection of blocks in a logical flow chart, which represents a sequence of operations that can be implemented in hardware, software, or a combination thereof.
- the blocks represent computer-executable instructions that, when executed by one or more processors, perform the recited operations.
- computer-executable instructions may include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types.
- the order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks can be combined in any order and/or in parallel to implement the process.
- the processes 400 - 800 are described with reference to the environment 100 of FIG. 1 .
- FIG. 4 is a flow diagram of an example process 400 for a master control device 116 to initiate a cellular network assisted vehicle immobilization of a vehicle.
- the master control device 116 may receive a request inputted by a user to initiate vehicle immobilization of a vehicle at the master control device 116 .
- the master control device 116 may be installed on a law enforcement vehicle, such as the vehicle 106 .
- the user may be a law enforcement officer that is operating the vehicle 106 .
- the master control device 116 may send an information query command to the vehicle via proximity communication.
- the proximity communication may be in the form of NFC communication, Bluetooth communication, RFID communication, and/or so forth.
- the information query command may be received by a vehicle communication device of the vehicle.
- the master control device 116 may determine whether a device identifier and vehicle description of the vehicle is received from the vehicle communication device of the vehicle in a predetermined amount of time.
- the vehicle identifier of a vehicle may be a VIN, a chassis number, or another identifier that uniquely identifies the vehicle.
- the vehicle description of the vehicle may include a make, a model, a vehicle color, a vehicle type, a model year, and/or other pertinent information that enables the user to identify the vehicle.
- the process 400 may proceed to block 410 .
- the master control device 116 may prompt the user to confirm the vehicle description of the vehicle.
- the master control device 116 may display the vehicle description of the vehicle on a display with a request that the user confirm the vehicle description.
- the user may confirm the vehicle description by providing a specific user input to the master control device 116 .
- the process 400 may proceed to block 414 .
- the master control device 116 may send a vehicle immobilization request that includes the device identifier and a user identifier of the user to the wireless communication carrier 114 .
- the user identifier may be an officer identifier of a law enforcement officer.
- the process 400 may proceed to block 416 .
- the master control device 116 may resend the information query command unless a cancellation request is inputted by the user. The user may decline to confirm the vehicle description if the device identifier acquired by the master control device 116 does not belong to the vehicle of interest.
- the user may send such an indication to the master control device 116 via a user input.
- the resending of the information query command may enable the master control device 116 to acquire the device identifier from a vehicle communication device of another vehicle.
- the process 400 may proceed to block 418 .
- the master control device 116 may obtain a license plate number of the vehicle via an image sensor, such as the image sensor 118 .
- the master control device 116 may include a software algorithm for recognizing alphanumeric text from graphical images.
- the master control device 116 may use a cellular communication connection to obtain a vehicle identifier from a vehicle database that correlates the license plate numbers with vehicle identifiers.
- the vehicle database may be the vehicle database 130 that is operated by the government agency 128 .
- the master control device 116 may send a vehicle immobilization request that includes the vehicle identifier and the user identifier of the user to the wireless communication carrier.
- FIG. 5 is a flow diagram of an example process 500 for a cellular communication carrier to initiate the broadcast of an immobilization command to a vehicle in response to the initiation of immobilization from the master control device.
- a server application executing on the servers 124 of the wireless communication carrier 114 may receive a vehicle immobilization request to remotely immobilize a vehicle. The request may originate from a master control device, such as the master control device 116 that is on the vehicle 106 .
- the server application may extract a user identifier and one of a vehicle identifier or a device identifier of the vehicle communication device from the vehicle immobilization request.
- the user identifier may be an office identifier of a law enforcement officer.
- the server application may determine whether the user identified by the user identifier is authorized to initiate the vehicle immobilization request. In some instances, the server application may verify the user identifier with a database of authorized users at a law enforcement agency. In other instances, the server application may verify the user identifier with a database of authorized users that reside on the servers 124 of the wireless communication carrier 114 .
- the process 500 may proceed to decision block 510 .
- the server application may determine whether a device identifier or a vehicle identifier is extracted from the vehicle immobilization request. Accordingly, if the vehicle identifier is extracted from the vehicle immobilization request, the process 500 may proceed to block 512 .
- the server application may obtain the device identifier of the corresponding vehicle communication device from a database that correlates vehicle identifiers with device identifiers.
- the database may be the carrier database 132 of the wireless communication carrier 114 .
- the server application may broadcast an immobilization command that includes the device identifier via a cellular communication network 112 of the wireless communication carrier 114 .
- the server application may send a notification to the master control device (e.g., the master control device 116 ) via the cellular communication network 112 .
- the notification may indicate that the immobilization of the vehicle is initiated.
- the process 500 may proceed directly to block 514 .
- the server application determines that the user identifier is not authorized, the process 500 may proceed to block 518 .
- the server application may send a notification to the master control device (e.g., the master control device 116 ) via the cellular communication network 112 .
- the notification may indicate that the user is not authorized to initiate immobilization.
- FIG. 6 is a flow diagram of an example process 600 for a master control device to initiate a peer-to-peer vehicle immobilization of a vehicle.
- the master control device 116 may receive a request inputted by a user to initiate vehicle immobilization of a vehicle at the master control device 116 .
- the master control device 116 may be installed on a law enforcement vehicle, such as the vehicle 106 .
- the user may be a law enforcement officer that is operating the vehicle 106 .
- the master control device 116 may send an information query command to the vehicle via proximity communication.
- the proximity communication may be in the form of NFC communication, Bluetooth communication, RFID communication, and/or so forth.
- the information query command may be received by a vehicle communication device of the vehicle.
- the master control device 116 may determine whether a device identifier and vehicle description of the vehicle is received from the vehicle communication device of the vehicle in a predetermined amount of time.
- the vehicle identifier of a vehicle may be a VIN, a chassis number, or another identifier that uniquely identifies the vehicle.
- the vehicle description of the vehicle may include a make, a model, a vehicle color, a vehicle type, a model year, and/or other pertinent information that enables the user to identify the vehicle.
- the process 600 may proceed to block 610 .
- the master control device 116 may prompt the law enforcement vehicle to confirm the vehicle description of the vehicle.
- the master control device 116 may display the vehicle description of the vehicle on a display with a request that the user confirm the vehicle description.
- the user may confirm the vehicle description by providing a specific user input to the master control device 116 .
- the master control device 116 may broadcast an immobilization command that includes the device identifier to the vehicle via proximity communication.
- the process 600 may proceed to block 616 .
- the master control device 116 may resend the information query command unless a cancellation request is inputted by the user.
- the user may decline to confirm the vehicle description if the device identifier acquired by the master control device 116 does not belong to the vehicle of interest. In such a case, the user may send such an indication to the master control device 116 via a user input. Subsequently, the resending of the information query command may enable the master control device 116 to acquire the device identifier from a vehicle communication device of another vehicle.
- the process 600 may proceed to block 618 .
- the master control device 116 may obtain a license plate number of the vehicle via an image sensor, such as the image sensor 118 .
- the master control device 116 may include a software algorithm for recognizing alphanumeric text from graphical images.
- the master control device 116 may use a cellular communication connection to obtain a vehicle identifier from a vehicle database that correlates license plate numbers with vehicle identifiers.
- the vehicle database may be the vehicle database 130 that is operated by the government agency 128 .
- master control device 116 may obtain the device identifier of the vehicle communication device from a carrier database that correlates vehicle identifiers to device identifiers.
- the carrier database may be the carrier database 132 of the wireless communication carrier 114 .
- the master control device 116 may access the carrier database 132 by communicating with the servers 124 via the cellular communication network 112 . Subsequently, the process 600 may loop back to block 614 , such that the master control device 116 may broadcast an immobilization command that includes the device identifier to the vehicle via proximity communication.
- FIG. 7 is a flow diagram of an example process 700 for a vehicle communication device on a vehicle to determine whether to disable the vehicle based on a received immobilization command.
- a vehicle communication device of a vehicle may receive an immobilization command that includes a device identifier.
- the vehicle communication device may receive the immobilization command via proximity communication or a cellular communication connection that is provided by the cellular communication network 112 .
- an application on the vehicle communication device may extract the device identifier from the immobilization command.
- the application may compare the extracted device identifier to an embedded device identifier of the vehicle communication device.
- the embedded device identifier may be stored in a protected memory space of the vehicle communication device.
- the application may determine whether the extracted device identifier matches the embedded device identifier of the vehicle communication device. Accordingly, if the application determines that the identifiers match, the process 700 may proceed to block 710 .
- the application may send a signal from the vehicle communication device to an engine disabler of the vehicle to immobilize the vehicle.
- the application may send a notification indicating that the immobilization of the vehicle is in progress.
- the application may cause the vehicle communication device to send the notification back to the wireless communication carrier 114 via the cellular communication network 112 .
- the wireless communication carrier 114 may route the notification to a master control device that originated the immobilization command via the cellular communication network 112 .
- the application may cause the vehicle communication device to send the notification directly to the master control device via proximity communication.
- the application may send a notification indicating that the vehicle is immobilized following receipt of an immobilized status from the engine disabler.
- the engine disabler may provide the immobilized status to the application when an engine check by the engine disabler indicates that the engine of the vehicle is stopped or switched off.
- the application may route the notification either directly to a master control device that originated the immobilization command or to a wireless communication carrier 114 that forwards the notification to the master control device.
- the process 700 may proceed to block 716 .
- the application may ignore the immobilization command.
- FIG. 8 is a flow diagram of an example process 800 for automatically initiating remote vehicle immobilization of a vehicle using an immobilizer device.
- the immobilizer device may send an information query command to the vehicle via proximity communication.
- the proximity communication may be in the form of NFC communication, Bluetooth communication, RFID communication, and/or so forth.
- the information query command may be received by a vehicle communication device of the vehicle.
- the immobilizer device may receive a device identifier from a vehicle communication device of the vehicle via proximity communication.
- the device identifier may be one of multiple identifiers that are received by the immobilizer device.
- the immobilizer device may hold one or more of the device identifiers in a buffer until all of the device identifiers are processed.
- the immobilizer device may send the vehicle identifier to a database of a wireless communication carrier that correlates vehicle identifiers to device identifiers of vehicle communication devices.
- the database may be the carrier database 132 of the wireless communication carrier 114 .
- the vehicle identifier may be sent via a network communication connection.
- the network communication connection may be a connection that is provided by the cellular communication network 112 and/or the network 136 .
- the immobilizer device may receive a corresponding vehicle identifier for the device identifier from the wireless communication carrier via the network communication connection.
- the immobilizer device may use the network communication connection provided by the cellular communication network 112 to send the vehicle identifier to a server at a government agency.
- the server may execute an application to determine whether the vehicle that is identified by the vehicle identifier is subject to immobilization. For example, the vehicle may be subject to immobilization if it is the target of an outstanding APB, an Amber alert, a stolen vehicle report, and/or so forth.
- the immobilizer device may determine whether a vehicle immobilization request for the vehicle identifier is received from the server at the government agency via the network communication connection. Accordingly, at decision block 814 , if the immobilizer device determines that the vehicle immobilization request is received, the process 800 may proceed to block 816 . At block 816 , the immobilizer device may broadcast an immobilization command that includes the device identifier to the vehicle via proximate communication. However, if the immobilizer device determines that no vehicle immobilization request is received, the process 800 may loop back to block 802 .
- the techniques may enable a mobile device or an immobilizer device to remotely immobilize a vehicle via peer-to-peer device communication with a vehicle communication device of the vehicle.
- the remote immobilization may be achieved by the user triggering a cellular communication carrier to send an immobilization command to the vehicle communication device via a cellular communication connection.
- the peer-to-peer communication may be initiated by a master control device in a law enforcement vehicle.
- the remote immobilization of a vehicle may enable the vehicle to be safely brought to a stop without endangering the occupants of the vehicle or bystanders who are in the vicinity of the vehicle.
- the remote immobilization of the vehicle may provide law enforcement officers with an opportunity to detain the occupants without dangerous vehicle pursuits that can jeopardize public safety.
Abstract
Description
- Modern vehicles are equipped with built-in communication devices that enable the vehicles to remotely communicate with different service providers. The communication devices may include subscriber identity module (SIM)-equipped network devices that enable the vehicles to use a cellular communication network to communicate with the service providers. Accordingly, the built-in communication devices may enable other devices in the vehicle to provide a multitude of services. These services may include in-vehicle security, trouble diagnostics, concierge, emergency assistance, and/or global positioning system (GPS) navigation capabilities.
- The detailed description is described with reference to the accompanying figures, in which the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items.
-
FIG. 1 illustrates an example environment for performing remote vehicle engine immobilization. -
FIG. 2 is a block diagram showing various components of a master control device and a vehicle communication device. -
FIG. 3 is a block diagram showing various components of an immobilizer device that performs remote vehicle engine immobilization via peer-to-peer communication. -
FIG. 4 is a flow diagram of an example process for a master control device to initiate a cellular network assisted vehicle immobilization of a vehicle. -
FIG. 5 is a flow diagram of an example process for a cellular communication carrier to initiate the broadcast of an immobilization command to a vehicle in response to the initiation of immobilization from the master control device. -
FIG. 6 is a flow diagram of an example process for a master control device to initiate a peer-to-peer vehicle immobilization of a vehicle. -
FIG. 7 is a flow diagram of an example process for a vehicle communication device on a vehicle to determine whether to disable the vehicle based on a received immobilization command. -
FIG. 8 is a flow diagram of an example process for automatically initiating remote vehicle immobilization of a vehicle using an immobilizer device. - This disclosure is directed to techniques for using a master control device on a particular vehicle to initiate remote immobilization of an additional vehicle. In various embodiments, the particular vehicle that is equipped with the master control device may be a law enforcement vehicle. In some instances, the master control device on the particular vehicle may remotely immobilize the additional vehicle by using proximity communication to directly send an immobilization command to the additional vehicle in a peer-to-peer manner. The immobilization command may be received by a vehicle communication device on the additional vehicle. The vehicle communication device may be a subscriber identity module (SIM)-equipped communication device that is fitted with both a cellular communication radio and a wireless proximity communication transceiver. In turn, the vehicle communication device may trigger an engine disabler on the additional vehicle to immobilize the vehicle.
- In other instances, the master control device on the initial vehicle may trigger a wireless communication carrier to use cellular communication to send an immobilization command to the additional vehicle. In further instances, the immobilization command for the additional vehicle may be sent by an immobilizer device via proximity communication with the vehicle communication device of the additional vehicle. In various embodiments, the immobilizer device may be a stationary immobilizer device or a movable immobilizer device. The immobilizer device may send the immobilization command following the immobilizer device detecting a device identifier of the vehicle communication device, and receiving a vehicle immobilization request from a law enforcement server for the device identifier.
- The immobilization of the additional vehicle may involve the immediate disablement of an engine of the vehicle, a gradual diminishment of the power outputted by the engine of the vehicle until the engine is in a stopped state, or a configuration that blocks an engine restart once the engine is manually switched off by a user. In the case of the gradual power diminishment, the engine may also be further configured to block an engine restart after the engine is in a stopped state.
- In at least one embodiment, a device may remotely immobilize a vehicle via peer-to-peer device communication or network assisted communication. Initially, a request inputted by a user to initiate vehicle immobilization of a vehicle may be received at a master control device. The master control device may send an information query command to the vehicle communication device of the vehicle via proximity communication. Subsequently, the master control device may receive a device identifier from the vehicle communication device via the proximity communication. A vehicle immobilization request that includes the device identifier may be sent from the master control device to a wireless communication carrier. The request may prompt the wireless communication carrier to broadcast an immobilization command via a cellular communication network to the vehicle communication device of the vehicle that is identified by the device identifier. Alternatively, the master control device may directly send the immobilization command to the vehicle communication device.
- The techniques may enable a mobile device or an immobilizer device to remotely immobilize a vehicle via peer-to-peer device communication with a vehicle communication device of the vehicle. Alternatively, the remote immobilization may be achieved by the user triggering a cellular communication carrier to send an immobilization command to the vehicle communication device via a cellular communication connection. In some instances, the peer-to-peer communication may be initiated by a master control device in a law enforcement vehicle. The remote immobilization of a vehicle may enable the vehicle to be safely brought to a stop without endangering the occupants of the vehicle or bystanders who are in the vicinity of the vehicle. In instances in which the occupants of the vehicle are fleeing suspects or felons, the remote immobilization of the vehicle may provide law enforcement officers with an opportunity to detain the occupants without dangerous vehicle pursuits that can jeopardize public safety. Example implementations are provided below with reference to the following figures.
-
FIG. 1 illustrates anexample environment 100 for performing remote vehicle engine immobilization. Theenvironment 100 may include multiple vehicles, such as the vehicles 102-106. Thevehicles vehicle communication devices cellular communication network 112 of a cellular communication carrier that is identified in the SIM. Thecellular communication network 112 may provide telecommunication and data communication in accordance with one or more technical standards, such as such as Enhanced Data Rates for GSM Evolution (EDGE), Wideband Code Division Multiple Access (W-CDMA), High Speed Packed Access (HSPA), Long Term Evolution (LTE), CDMA-2000 (Code Division Multiple Access 2000), and/or so forth. Thecellular communication network 112 may be operated by thewireless communication carrier 114 or another carrier that has a network interoperability agreement with thewireless communication carrier 114. - The wireless proximity communication transceiver may enable the vehicle communication device to engage in short-range peer-to-peer communication with another device. For example, the wireless proximity communication transceiver may be a Near Field Communication (NFC) transceiver, a Bluetooth transceiver, Radio-frequency identification (RFID), and/or so forth. The vehicle communication device of each vehicle may be equipped with a unique device identifier. Additionally, each vehicle communication device may be capable of sending an immobilization signal to an engine immobilization device on each vehicle. In turn, the engine immobilization device of a vehicle that receives the immobilization signal may disable the vehicle.
- The
vehicle 106 may be equipped with amaster control device 116 that is used to immobilize other vehicles, such as thevehicles master control device 116 may be equipped with a wireless proximity communication transceiver that interfaces with the wireless proximity communication transceivers of thevehicle communication devices master control device 116 may obtain the device identifiers of thevehicles communication devices vehicle communication devices master control device 116 may be further equipped with a cellular communication radio that enables themaster control device 116 to use thecellular communication network 112. Themaster control device 116 may be connected to animage sensor 118. Theimage sensor 118 may enable themaster control device 116 to capture images of license plates, such as thelicense plate 120 of thevehicle 104. - During cellular network assisted immobilization, the
master control device 116 may receive a request from a user, such as alaw enforcement officer 122, to remotely immobilize a vehicle. In turn, themaster control device 116 may establish proximity communication with the vehicle communication device of the vehicle to obtain a device identifier of the vehicle communication device. Subsequently, themaster control device 116 may send a vehicle immobilization request that includes the device identifier to one ormore servers 124 of thewireless communication carrier 114. In turn, theservers 124 may execute software that cause thecellular communication network 112 to broadcast an immobilization command that includes the device identifier. The vehicle communication device of the vehicle may receive the immobilization command via thecellular communication network 112 and verify the device identifier in the command. Following verification of the device identifier, the vehicle communication device may command an engine immobilization device of the vehicle to immobilize the vehicle. - In an alternative scenario of the cellular network assisted immobilization, the
master control device 116 may fail to establish proximity communication with the vehicle communication device of the vehicle. For example, the failure may be due to signal interference or the vehicle being out of signal range. As a result, themaster control device 116 may be unable obtain a device identifier of the vehicle communication device within a predetermined amount of time. In such an event, themaster control device 116 may automatically activate theimage sensor 118 to capture a license plate number of the vehicle. Subsequently, themaster control device 116 may use thecellular communication network 112 to send the license plate number to one ormore servers 126 of agovernment agency 128. In turn, theservers 126 may execute software that queries avehicle database 130 for a vehicle identifier that matches the license plate. The vehicle identifier of a vehicle may be a vehicle identification number (VIN), a chassis number, or another identifier that uniquely identifies the vehicle. For example, thegovernment agency 128 may be the Department of Motor Vehicles (DMV) or Department of Licensing (DOL) that administers the registration of motor vehicles in the jurisdiction. Accordingly, thevehicle database 130 may be a database that correlates license plate numbers of vehicles with vehicle identifiers of the vehicles. Theservers 126 may return a vehicle identifier of the vehicle to themaster control device 116 via thecellular communication network 112. - Subsequently, the
master control device 116 may send a vehicle immobilization request that includes the vehicle identifier to one ormore servers 124 of thewireless communication carrier 114. In turn, theservers 124 may execute software that queries acarrier database 132 for a device identifier that matches the vehicle identifier. Thecarrier database 132 may be a database that correlates vehicle identifiers of vehicles with device identifiers of vehicle communication devices that are installed on the vehicles. Upon obtaining a device identifier, the software on theservers 124 may cause thecellular communication network 112 to broadcast an immobilization command to the vehicle communication device that is associated with the device identifier. - However, in peer-to-peer immobilization, the
master control device 116 may receive a request from a user, such as alaw enforcement officer 122, to remotely immobilize a vehicle. In turn, themaster control device 116 may establish proximity communications with the vehicle communication device of the vehicle to obtain a device identifier of the vehicle communication device. At this point, instead of sending a vehicle immobilization request to thewireless communication carrier 114, themaster control device 116 may directly broadcast an immobilization command that includes the device identifier to the vehicle via proximity communication. In some embodiments, themaster control device 116 may initiate peer-to-peer immobilization in the event that access to thecellular communication network 112 is unavailable. - In an alternative scenario of the peer-to-peer immobilization, the
master control device 116 may be unable obtain a device identifier of the vehicle communication device within a predetermined amount of time. In such an event, themaster control device 116 may once again automatically activate theimage sensor 118 to capture a license plate number of the vehicle. Subsequently, themaster control device 116 may use the license plate number to obtain a corresponding vehicle identifier from thevehicle database 130 of thegovernment agency 128. The vehicle identifier is further sent by themaster control device 116 to thewireless communication carrier 114 for querying against thecarrier database 132, such that themaster control device 116 may obtain a corresponding device identifier of the vehicle communication device in the vehicle. In such instances, the master control device may use thecellular communication network 112 to obtain access to thevehicle database 130 and thecarrier database 132. Subsequently, themaster control device 116 may directly broadcast an immobilization command that includes the device identifier to the vehicle via proximity communication. - In other embodiments, immobilizer devices 134(1)-134(N) may be deployed at multiple locations in a geographical area. The immobilizer devices 134(1)-134(N) may be configured to continuously scan for the device identifiers of vehicle communication device-equipped vehicles traveling in the geographical area in order to detect vehicles that are of interest to a law enforcement agency. For example, a vehicle may be subject to a stolen vehicle report, an all-points bulletin (APB), an Amber alert, and/or another type of emergency broadcast alert. Each of the immobilizer devices 134(1)-134(N) may be linked to the
wireless communication carrier 114 via anetwork 136. Thenetwork 136 may include a local area network (“LAN”), a larger network such as a wide area network (“WAN”), or a collection of networks, such as the Internet. Further, thenetwork 136 may include wired and/or wireless link components. In various embodiments, an immobilizer device may be equipped with a cellular communication radio that enables the immobilizer device to communicate via thecellular communication network 112, a wired network transceiver, and a wireless proximity communication transceiver that enables the immobilizer device to engage in communication with vehicle communication devices. In some instances, the immobilizer devices 134(1)-134(N) may include immobilizer devices that are deployed as standalone fixtures, fixtures on existing structures, or movable fixtures. For example, the existing structures may include toll booths, gas stations, traffic lights, light poles, traffic signs, and/or so forth. In another example, the immobilizer devices 134(1)-134(N) may include immobilizer devices that are mounted on wheeled dollies or trailers that can be moved and positioned at different locations. - In operation, an immobilizer device may periodically broadcast information query commands. Alternatively, the immobilizer device may broadcast an information query command when an image sensor of the device detects a vehicle approaching within a predetermined distance of the device. The information query commands may result in a vehicle communication device of a vehicle responding with a vehicle identifier. For example, the immobilizer device may receive a vehicle identifier from the
vehicle communication device 108 of thevehicle 102. Subsequently, the immobilizer device may use thecellular communication network 112 or thenetwork 136 to send the device identifier to theservers 124 of thewireless communication carrier 114. In turn, the one ormore servers 124 may execute software that queries thecarrier database 132 for a vehicle identifier that matches the device identifier. The vehicle identifier may be sent by thewireless communication carrier 114 to the servers of a law enforcement agency. In response, the servers of the law enforcement agency may respond with a vehicle immobilization request if the law enforcement agency determines that the vehicle is subject to immobilization. For example, the servers of the law enforcement agency may include software that consult thevehicle database 130 to determine a license plate number that corresponds to the vehicle identifier. The software may further check whether the license plate number matches a flagged license plate number targeted for immobilization. Accordingly, if the immobilizer device receives a vehicle immobilization request for the vehicle, the immobilizer device may directly broadcast an immobilization command that includes the device identifier to the vehicle via proximity communication. -
FIG. 2 is a block diagram showing various components of a master control device and a vehicle communication device. Themaster control device 116 may include acommunication interface 202, one ormore processors 204,memory 206, anddevice hardware 208. Thecommunication interface 202 may include wireless and/or wired communication components that enable themaster control device 116 to transmit and receive data with other networked devices. In various embodiments, thecommunication interface 202 may include a network transceiver and proximity communication transceiver. Thedevice hardware 208 may include additional hardware that performs user interface, data display, data communication, data storage, and/or other server functions. In at least one embodiment, thedevice hardware 208 may include a data output device (e.g., visual display, audio speakers), and one or more data input devices. The data input devices may include, but are not limited to, combinations of one or more of keypads, keyboards, mouse devices, touch screens that accept gestures, microphones, voice or speech recognition devices, and any other suitable devices or other electronic/software selection methods. - The
memory 206 may be implemented using computer-readable media, such as computer storage media. Computer-readable media includes, at least, two types of computer-readable media, namely computer storage media and communications media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device. In contrast, communication media may embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism. - The
processors 204 and thememory 206 of themaster control device 116 may implement anoperating system 210. Theoperating system 210 may include components that enable themaster control device 116 to receive and transmit data via various interfaces (e.g., user controls, communication interface, and/or memory input/output devices), as well as process data using theprocessors 204 to generate output. Theoperating system 210 may include a presentation component that presents the output (e.g., display the data on an electronic display, store the data in memory, transmit the data to another electronic device, etc.). Additionally, theoperating system 210 may include other components that perform various additional functions generally associated with an operating system. Theoperating system 210 may be used to implement anauthentication module 212, animmobilization module 214, anencryption module 216, and auser interface module 218. These modules may include routines, program instructions, objects, and/or data structures that perform particular tasks or implement particular abstract data types. - The
authentication module 212 may authenticate a user so that the user may create or log into a user account on themaster control device 116. In various embodiments, theauthentication module 212 may prompt a user to enter an authentication credential for a corresponding user account. The authentication credential may include one or more of a user name, a password, an electronic identifier, a digital certificate, biometric characteristics, and/or the like. In instances in which the user is a law enforcement officer, the authentication credential may include a user identifier in the form of an officer identifier that is assigned to the law enforcement officer. - The
authentication module 212 may compare the inputted authentication credential to a list of authorize authentication credentials for user accounts stored on themaster control device 116. Alternatively, theauthentication module 212 may send the authentication credential to an authentication server for authentication. For example, the authentication server may be operated by a law enforcement agency and stores authentication credentials of officers that are authorized to perform remote vehicle immobilization. Accordingly, theauthentication module 212 may permit the user access to the functionalities of themaster control device 116 when the inputted authentication credential is found within a list of authorized authentication credentials or deemed by an authentication server as authorized. - The
immobilization module 214 may initiate the vehicle immobilization of a vehicle in the proximity of themaster control device 116 based on a request inputted by a user. In response to the request, theimmobilization module 214 may use a proximity communication transceiver to send an information query command to a vehicle communication device of the vehicle. Subsequently, theimmobilization module 214 may determine whether a device identifier and a vehicle description of the vehicle is received from the vehicle communication device within a predetermined amount of time. The vehicle description of the vehicle may include a make, a model, a vehicle color, a vehicle type, a model year, and/or other pertinent information that enables the user to identify the vehicle. - The
immobilization module 214 may display the vehicle description of the vehicle on a display of themaster control device 116 with a request that the user confirm the vehicle description. The user may confirm the vehicle description by providing a specific user input to theimmobilization module 214. The confirmation prompt may serve to ensure that the correct vehicle will be immobilized, as there may be multiple vehicles that are within proximity communication range of themaster control device 116. Following the confirmation of the vehicle description, theimmobilization module 214 may initiate a peer-to-peer immobilization or a cellular network assisted immobilization of the vehicle. Theimmobilization module 214 may initiate peer-to-peer immobilization based on a user configuration setting, based on the vehicle being within proximity communication range, and/or based on the lack of an adequate cellular communication network signal (e.g., signal strength below a strength threshold). Theimmobilization module 214 may initiate peer-to-peer immobilization by broadcasting an immobilization command that includes the device identifier of the vehicle via proximity communication. - On the other hand, the
immobilization module 214 may initiate cellular network assisted immobilization when proximity communication is unreliable or when configured based on a user inputted configuration setting. For example, proximity communication with the vehicle communication device of the vehicle may be unreliable due to signal interference or the vehicle being out of proximity communication range. As a consequence, theimmobilization module 214 may be unable to receive the device identifier and the vehicle description of the vehicle in the predetermined amount of time. In such a scenario, theimmobilization module 214 may activate theimage sensor 118 to capture a license plate number of the vehicle. Theimmobilization module 214 may include a software algorithm for recognizing alphanumeric text from graphical images. The license plate number may then be used by theimmobilization module 214 to obtain a corresponding vehicle identifier from thevehicle database 130. Subsequently, theimmobilization module 214 may send a vehicle immobilization request that includes the vehicle identifier to thewireless communication carrier 114. In turn, the vehicle immobilization request may trigger thewireless communication carrier 114 to broadcast a corresponding immobilization command to the vehicle using thecellular communication network 112. - Alternatively, the proximity communication between the
immobilization module 214 and the vehicle communication device of the vehicle may become disrupted after theimmobilization module 214 has obtained the device identifier, resulting in the peer-to-peer broadcast of the immobilization request becoming ineffective. In such an instance, theimmobilization module 214 may send a vehicle immobilization request that includes the device identifier to thewireless communication carrier 114. In turn, the vehicle immobilization request may trigger thewireless communication carrier 114 to broadcast a corresponding immobilization command to the vehicle using thecellular communication network 112. In some embodiments, the vehicle immobilization request may further include the user identifier of the user that initiated the vehicle immobilization request. Accordingly, theservers 124 of thewireless communication carrier 114 may execute a verification algorithm to ensure that the user identifier belongs to a user that is authorized to initiate vehicle immobilization. In an example in which the user identifier is an officer identifier, the verification algorithm may send the user identifier to a verification application at the law enforcement agency to verify that the corresponding law enforcement officer is authorized to initiate immobilization of vehicles. In another example, the verification algorithm may check the user identifier against an internal database of users who are authorized to initiate vehicle immobilizations. In at least one embodiment, the internal database may be periodically updated based on authorization data from various government agencies, such as law enforcement agencies. - Following the broadcast of an immobilization command, the
immobilization module 214 may also receive notifications either directly from a vehicle communication device of a vehicle via proximity communication or from thewireless communication carrier 114 via thecellular communication network 112. The notifications may include a notification that the immobilization of a vehicle is in progress once a corresponding vehicle communication device has verified and implemented the immobilization command. The notifications may further include a notification that the vehicle is immobilized once the vehicle communication device receives an immobilization notification from an engine disabler of the vehicle. - The
encryption module 216 may work with the encryption modules that are on the vehicle communication devices, theservers 124 of thewireless communication carrier 114, and theservers 126 of thegovernment agency 128 to ensure that the data exchanged between the different entities are encrypted. In various embodiments, theencryption module 216 may encrypt outgoing data and decrypted incoming data using various encryption schemes. For example, the encryption may be implemented using various asymmetric and symmetric encryption techniques such as public key infrastructure (PKI) key negotiation and encryption, Diffie-Hellman key exchange, and/or so forth. In some instances, theencryption module 216 may also implement hash-based techniques to specify and verify the authenticity of the data that are exchanged between the entities. For example, the hash-based techniques may include the use of MD5 hashing, SHA-1 hashing, and/or so forth, to generate keyed-hash message authentication codes (HMAC). - The
user interface module 218 may provide interface options for the user to configure the functionalities of themaster control device 116. For instance, a configuration menu provided by theuser interface module 218 may enable the user to configure theimmobilization module 214 to initially default to either peer-to-peer vehicle immobilization or cellular network assisted immobilization. Another configuration menu provided by theuser interface module 218 may enable the user to customize the amount of time theimmobilization module 214 waits before activating theimage sensor 118 to scan for a license plate number. - The
vehicle communication device 108 may include acommunication interface 220, one ormore processors 222,device hardware 224, andmemory 226. As an example, thevehicle communication device 108 may correspond tovehicle communication device 110. Thecommunication interface 220 may include wireless and/or wired communication components that enable the vehicle communication device to transmit data to and receive data from other networked devices. In various embodiments, thecommunication interface 220 may include a network transceiver and proximity communication transceiver. Thedevice hardware 224 may include additional hardware that performs user interface, data display, data communication, data storage, and/or other server functions. In at least one embodiment, thedevice hardware 224 may include a data output device (e.g., visual display, audio speakers), and one or more data input devices. The data input devices may include, but are not limited to, combinations of one or more of keypads, keyboards, mouse devices, touch screens that accept gestures, microphones, voice or speech recognition devices, and any other suitable devices or other electronic/software selection methods. For example, thedevice hardware 224 may further include signal converters, antennas, modems, hardware decoders and encoders, graphic processors, a SIM card slot, and/or the like that enable thevehicle communication device 108 to execute applications and provide telecommunication and data communication functions. A SIM card may be inserted into the SIM card slot of thevehicle communication device 108. Accordingly, the SIM card may enable thevehicle communication device 108 to obtain telecommunication and/or data communication services from thewireless communication carrier 114 or another carrier. - The
memory 226 may be implemented using computer-readable media, such as computer storage media. Computer-readable media includes, at least, two types of computer-readable media, namely computer storage media and communications media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device. In contrast, communication media may embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism. - The
processors 222 and thememory 226 of the vehicle communication device may implement anoperating system 228. Theoperating system 228 may include components that enable themaster control device 116 to receive and transmit data via various interfaces (e.g., user controls, communication interface, and/or memory input/output devices), as well as process data using theprocessors 222 to generate output. Theoperating system 228 may include a presentation component that presents the output (e.g., display the data on an electronic display, store the data in memory, transmit the data to another electronic device, etc.). Additionally, theoperating system 228 may include other components that perform various additional functions generally associated with an operating system. Theoperating system 228 may implementapplications 230. Theapplications 230 may include software that enable other software on the device to exchange data with service providers. For example, theapplications 230 may include data collection applications, vehicle diagnostic applications, navigation applications, autopilot applications, security applications, and/or so forth. Theoperating system 228 may be used to implement acontrol interface module 232, an encryption module 234, andtrigger module 236. These modules may include routines, program instructions, objects, and/or data structures that perform particular tasks or implement particular abstract data types. - The
control interface module 232 may continuously listen for information query commands and immobilization commands from another device. The information query commands may be received via proximity communication. In response to a query command, thecontrol interface module 232 may respond with a device identifier of the vehicle communication device as well as the vehicle description of the corresponding vehicle that is stored in thememory 226. Thecontrol interface module 232 may receive immobilization commands via proximity communication or cellular communication. - The encryption module 234 may work with the encryption modules on other devices to ensure that the exchange of data with the other devices are encrypted. The encryption module 234 may also verify the authenticity of the requests and commands that are received by the vehicle communication device. For example, the encryption module 234 may use asymmetric or symmetric encryption to secure the data that is exchanged with the other devices. Further, the encryption module 234 may generate and use HMACs to guarantee that the requests and commands are authentic. Thus, the
control interface module 232 may respond to information query commands that are authenticated by the encryption module 234. - The
trigger module 236 may trigger an engine disabler to immobilize the vehicle based on an immobilization command. The immobilization command may be verified by the encryption module 234. In various embodiments, thetrigger module 236 may extract a device identifier from the immobilization command. The extracted device identifier may be compared to an embedded device identifier of thevehicle communication device 108. Accordingly, if the extracted device identifier matches the embedded the device identifier, thetrigger module 236 may send a signal to the engine disabler of the vehicle to immobilize the vehicle. The engine disabler of the vehicle may include software and/or hardware components that are configured to disable the engine the vehicle. Further, thetrigger module 236 may generate a notification that the immobilization that the immobilization of the vehicle is in progress. Subsequently, when the engine disabler of the vehicle indicates to thetrigger module 236 that the vehicle is immobilized, thetrigger module 236 may generate a notification of vehicle immobilization. Thetrigger module 236 may send the notification back to themaster control device 116 via one of the proximity communication or thecellular communication network 112. -
FIG. 3 is a block diagram showing various components of animmobilizer device 300 that performs remote vehicle engine immobilization via peer-to-peer communication. Theimmobilizer device 300 may include acommunication interface 302, one ormore processors 304,memory 306, anddevice hardware 308. Thecommunication interface 302 may include wireless and/or wired communication components that enable the immobilizer device to transmit data to and receive data from other networked devices. In various embodiments, thecommunication interface 302 may include a proximity communication transceiver, as well as network transceivers that enable theimmobilizer device 300 to communicate with thewireless communication carrier 114 and thegovernment agency 128 via thenetwork 136. The network transceivers may include a wired transceiver and a wireless transceiver. Thedevice hardware 308 may include additional hardware that performs user interface, data display, data communication, data storage, and/or other server functions. In at least one embodiment, thedevice hardware 308 may include a data output device (e.g., visual display, audio speakers), and one or more data input devices. The data input devices may include, but are not limited to, combinations of one or more of keypads, keyboards, mouse devices, touch screens that accept gestures, microphones, voice or speech recognition devices, and any other suitable devices or other electronic/software selection methods. - The
memory 306 may be implemented using computer-readable media, such as computer storage media. Computer-readable media includes, at least, two types of computer-readable media, namely computer storage media and communications media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device. In contrast, communication media may embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism. - The
processors 304 and thememory 306 of theimmobilizer device 300 may implement anoperating system 310. Theoperating system 310 may include components that enable theimmobilizer device 300 to receive and transmit data via various interfaces (e.g., user controls, communication interface, and/or memory input/output devices), as well as process data using theprocessors 304 to generate output. Theoperating system 310 may include a presentation component that presents the output (e.g., display the data on an electronic display, store the data in memory, transmit the data to another electronic device, etc.). Additionally, theoperating system 310 may include other components that perform various additional functions generally associated with an operating system. Theoperating system 310 may be used to implement amonitoring module 312, adisablement module 314, and anencryption module 316. These modules may include routines, program instructions, objects, and/or data structures that perform particular tasks or implement particular abstract data types. - The
monitoring module 312 may send information query commands to vehicles that are in the vicinity of theimmobilizer device 300. In some embodiments, the information query commands may be sent on a periodic basis (e.g., every second, every minute, etc.). In turn, vehicle communication devices of the vehicles that are in the vicinity of theimmobilizer device 300 may respond by transmitting their device identifiers. In other embodiments, theimmobilizer device 300 may be equipped with an image sensor. In such embodiments, themonitoring module 312 may use an image analysis algorithm to detect the arrival of new vehicles in the vicinity of theimmobilizer device 300. Accordingly, themonitoring module 312 may send an information query command when a new vehicle arrives in the vicinity of theimmobilizer device 300. - The
disablement module 314 may use thenetwork 136 to send a device identifier to theservers 124 of thewireless communication carrier 114 to obtain a corresponding vehicle identifier from thecarrier database 132. Following the receipt of the device identifier, thedisablement module 314 may send the vehicle identifier to theservers 126 at thegovernment agency 128 via thenetwork 136. Theservers 126 may execute an application to determine whether the vehicle that is identified by the vehicle identifier is subject to immobilization. For example, the vehicle may be subject to immobilization if it is the object of an outstanding APB, an Amber alert, a stolen vehicle report, and/or so forth. Theservers 126 may make the determination using a vehicle immobilization request database. The vehicle immobilization request database may be a repository of pending vehicle immobilization requests that contains lawful requests inputted by authorized law enforcement officers of one or more law enforcement agencies. In some instances, theservers 126 may use thevehicle database 130 to determine a license plate number of the vehicle for the purpose of checking with the vehicle immobilization request database. Thus, if thedisablement module 314 receives a vehicle immobilization request for a vehicle from thegovernment agency 128, thedisablement module 314 may broadcast an immobilization command that includes the device identifier of the vehicle via proximity communication for reception by the vehicle. - In some instances, the
disablement module 314 may use an image sensor to capture the license plate number of a vehicle, rather than obtaining a device identifier of a vehicle communication device in the vehicle. In such instances, thedisablement module 314 may send the license plate number to theservers 126 of thegovernment agency 128. In turn, theservers 126 may execute an application to check the license plate number against the immobilization request database. - The encryption module 234 may work with the encryption modules of the other devices to ensure that the exchange of data with other devices are encrypted, and to verify the authenticity of the requests and commands that are received by the vehicle communication device. For example, the encryption module 234 may use asymmetric or symmetric encryption to secure the data that is exchanged with the other devices. Further, encryption module 234 may generate and use HMACs to guarantee that the requests and commands are authentic.
-
FIGS. 4-8 present illustrative processes 400-800 for performing remote vehicle engine immobilization. Each of the processes 400-800 is illustrated as a collection of blocks in a logical flow chart, which represents a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the blocks represent computer-executable instructions that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions may include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks can be combined in any order and/or in parallel to implement the process. For discussion purposes, the processes 400-800 are described with reference to theenvironment 100 ofFIG. 1 . -
FIG. 4 is a flow diagram of anexample process 400 for amaster control device 116 to initiate a cellular network assisted vehicle immobilization of a vehicle. Atblock 402, themaster control device 116 may receive a request inputted by a user to initiate vehicle immobilization of a vehicle at themaster control device 116. Themaster control device 116 may be installed on a law enforcement vehicle, such as thevehicle 106. In some instances, the user may be a law enforcement officer that is operating thevehicle 106. - At
block 404, themaster control device 116 may send an information query command to the vehicle via proximity communication. In various embodiments, the proximity communication may be in the form of NFC communication, Bluetooth communication, RFID communication, and/or so forth. The information query command may be received by a vehicle communication device of the vehicle. - At
block 406, themaster control device 116 may determine whether a device identifier and vehicle description of the vehicle is received from the vehicle communication device of the vehicle in a predetermined amount of time. The vehicle identifier of a vehicle may be a VIN, a chassis number, or another identifier that uniquely identifies the vehicle. The vehicle description of the vehicle may include a make, a model, a vehicle color, a vehicle type, a model year, and/or other pertinent information that enables the user to identify the vehicle. - Thus, at
decision block 408, if themaster control device 116 determines that device identifier and the vehicle description are received at themaster control device 116 within the predetermined amount of time, theprocess 400 may proceed to block 410. Atblock 410, themaster control device 116 may prompt the user to confirm the vehicle description of the vehicle. In various embodiments, themaster control device 116 may display the vehicle description of the vehicle on a display with a request that the user confirm the vehicle description. In turn, the user may confirm the vehicle description by providing a specific user input to themaster control device 116. Accordingly, atdecision block 412, if themaster control device 116 determines that a confirmation is received, theprocess 400 may proceed to block 414. - At
block 414, themaster control device 116 may send a vehicle immobilization request that includes the device identifier and a user identifier of the user to thewireless communication carrier 114. In some instances, the user identifier may be an officer identifier of a law enforcement officer. Returning to decision block 412, if themaster control device 116 determines that no confirmation is received, theprocess 400 may proceed to block 416. Atblock 416, themaster control device 116 may resend the information query command unless a cancellation request is inputted by the user. The user may decline to confirm the vehicle description if the device identifier acquired by themaster control device 116 does not belong to the vehicle of interest. In such a case, the user may send such an indication to themaster control device 116 via a user input. Subsequently, the resending of the information query command may enable themaster control device 116 to acquire the device identifier from a vehicle communication device of another vehicle. - Returning to decision block 408, if the
master control device 116 determines that device identifier and the vehicle description are not received within the predetermined amount of time, theprocess 400 may proceed to block 418. Atblock 418, themaster control device 116 may obtain a license plate number of the vehicle via an image sensor, such as theimage sensor 118. In various embodiments, themaster control device 116 may include a software algorithm for recognizing alphanumeric text from graphical images. - At
block 420, themaster control device 116 may use a cellular communication connection to obtain a vehicle identifier from a vehicle database that correlates the license plate numbers with vehicle identifiers. In various embodiments, the vehicle database may be thevehicle database 130 that is operated by thegovernment agency 128. Atblock 422, themaster control device 116 may send a vehicle immobilization request that includes the vehicle identifier and the user identifier of the user to the wireless communication carrier. -
FIG. 5 is a flow diagram of anexample process 500 for a cellular communication carrier to initiate the broadcast of an immobilization command to a vehicle in response to the initiation of immobilization from the master control device. Atblock 502, a server application executing on theservers 124 of thewireless communication carrier 114 may receive a vehicle immobilization request to remotely immobilize a vehicle. The request may originate from a master control device, such as themaster control device 116 that is on thevehicle 106. Atblock 504, the server application may extract a user identifier and one of a vehicle identifier or a device identifier of the vehicle communication device from the vehicle immobilization request. In some instances, the user identifier may be an office identifier of a law enforcement officer. - At
block 506, the server application may determine whether the user identified by the user identifier is authorized to initiate the vehicle immobilization request. In some instances, the server application may verify the user identifier with a database of authorized users at a law enforcement agency. In other instances, the server application may verify the user identifier with a database of authorized users that reside on theservers 124 of thewireless communication carrier 114. - Accordingly, at
decision block 508, if the server application determines that the user identifier is authorized, theprocess 500 may proceed todecision block 510. Atdecision block 510, the server application may determine whether a device identifier or a vehicle identifier is extracted from the vehicle immobilization request. Accordingly, if the vehicle identifier is extracted from the vehicle immobilization request, theprocess 500 may proceed to block 512. Atblock 512, the server application may obtain the device identifier of the corresponding vehicle communication device from a database that correlates vehicle identifiers with device identifiers. In various embodiments, the database may be thecarrier database 132 of thewireless communication carrier 114. Atblock 512, the server application may broadcast an immobilization command that includes the device identifier via acellular communication network 112 of thewireless communication carrier 114. Atblock 514, the server application may send a notification to the master control device (e.g., the master control device 116) via thecellular communication network 112. The notification may indicate that the immobilization of the vehicle is initiated. - Returning to the
decision block 510, if the device identifier is extracted from the vehicle immobilization request, theprocess 500 may proceed directly to block 514. Returning to decision block 508, if the server application determines that the user identifier is not authorized, theprocess 500 may proceed to block 518. Atblock 518, the server application may send a notification to the master control device (e.g., the master control device 116) via thecellular communication network 112. The notification may indicate that the user is not authorized to initiate immobilization. -
FIG. 6 is a flow diagram of anexample process 600 for a master control device to initiate a peer-to-peer vehicle immobilization of a vehicle. Atblock 602, themaster control device 116 may receive a request inputted by a user to initiate vehicle immobilization of a vehicle at themaster control device 116. Themaster control device 116 may be installed on a law enforcement vehicle, such as thevehicle 106. In some instances, the user may be a law enforcement officer that is operating thevehicle 106. - At
block 604, themaster control device 116 may send an information query command to the vehicle via proximity communication. In various embodiments, the proximity communication may be in the form of NFC communication, Bluetooth communication, RFID communication, and/or so forth. The information query command may be received by a vehicle communication device of the vehicle. - At
block 606, themaster control device 116 may determine whether a device identifier and vehicle description of the vehicle is received from the vehicle communication device of the vehicle in a predetermined amount of time. The vehicle identifier of a vehicle may be a VIN, a chassis number, or another identifier that uniquely identifies the vehicle. The vehicle description of the vehicle may include a make, a model, a vehicle color, a vehicle type, a model year, and/or other pertinent information that enables the user to identify the vehicle. - Thus, at
decision block 608, if themaster control device 116 determines that device identifier and the vehicle description are received at themaster control device 116 within the predetermined amount of time, theprocess 600 may proceed to block 610. Atblock 610, themaster control device 116 may prompt the law enforcement vehicle to confirm the vehicle description of the vehicle. In various embodiments, themaster control device 116 may display the vehicle description of the vehicle on a display with a request that the user confirm the vehicle description. In turn, the user may confirm the vehicle description by providing a specific user input to themaster control device 116. Accordingly, atdecision block 612, if themaster control device 116 determines that a confirmation is received, theprocess 600 may proceed to block 614. Atblock 614, themaster control device 116 may broadcast an immobilization command that includes the device identifier to the vehicle via proximity communication. - Returning to decision block 612, if the
master control device 116 determines that no confirmation is received, theprocess 600 may proceed to block 616. Atblock 416, themaster control device 116 may resend the information query command unless a cancellation request is inputted by the user. The user may decline to confirm the vehicle description if the device identifier acquired by themaster control device 116 does not belong to the vehicle of interest. In such a case, the user may send such an indication to themaster control device 116 via a user input. Subsequently, the resending of the information query command may enable themaster control device 116 to acquire the device identifier from a vehicle communication device of another vehicle. Returning to decision block 608, if themaster control device 116 determines that device identifier and the vehicle description are not received within the predetermined amount of time, theprocess 600 may proceed to block 618. - At
block 618, themaster control device 116 may obtain a license plate number of the vehicle via an image sensor, such as theimage sensor 118. In various embodiments, themaster control device 116 may include a software algorithm for recognizing alphanumeric text from graphical images. Atblock 620, themaster control device 116 may use a cellular communication connection to obtain a vehicle identifier from a vehicle database that correlates license plate numbers with vehicle identifiers. In various embodiments, the vehicle database may be thevehicle database 130 that is operated by thegovernment agency 128. Atblock 622,master control device 116 may obtain the device identifier of the vehicle communication device from a carrier database that correlates vehicle identifiers to device identifiers. In various embodiments, the carrier database may be thecarrier database 132 of thewireless communication carrier 114. Themaster control device 116 may access thecarrier database 132 by communicating with theservers 124 via thecellular communication network 112. Subsequently, theprocess 600 may loop back to block 614, such that themaster control device 116 may broadcast an immobilization command that includes the device identifier to the vehicle via proximity communication. -
FIG. 7 is a flow diagram of anexample process 700 for a vehicle communication device on a vehicle to determine whether to disable the vehicle based on a received immobilization command. Atblock 702, a vehicle communication device of a vehicle may receive an immobilization command that includes a device identifier. In various embodiments, the vehicle communication device may receive the immobilization command via proximity communication or a cellular communication connection that is provided by thecellular communication network 112. - At
block 704, an application on the vehicle communication device may extract the device identifier from the immobilization command. Atblock 706, the application may compare the extracted device identifier to an embedded device identifier of the vehicle communication device. In some instances, the embedded device identifier may be stored in a protected memory space of the vehicle communication device. Atdecision block 708, the application may determine whether the extracted device identifier matches the embedded device identifier of the vehicle communication device. Accordingly, if the application determines that the identifiers match, theprocess 700 may proceed to block 710. Atblock 710, the application may send a signal from the vehicle communication device to an engine disabler of the vehicle to immobilize the vehicle. - At
block 712, the application may send a notification indicating that the immobilization of the vehicle is in progress. In instances in which the immobilization command is received from thewireless communication carrier 114, the application may cause the vehicle communication device to send the notification back to thewireless communication carrier 114 via thecellular communication network 112. In turn, thewireless communication carrier 114 may route the notification to a master control device that originated the immobilization command via thecellular communication network 112. However, in instances in which the immobilization command is directly received from a master control device, the application may cause the vehicle communication device to send the notification directly to the master control device via proximity communication. - At
block 714, the application may send a notification indicating that the vehicle is immobilized following receipt of an immobilized status from the engine disabler. The engine disabler may provide the immobilized status to the application when an engine check by the engine disabler indicates that the engine of the vehicle is stopped or switched off. In turn, the application may route the notification either directly to a master control device that originated the immobilization command or to awireless communication carrier 114 that forwards the notification to the master control device. Returning to decision block 708, if the application determines that the extracted device identifier does not match the embedded device identifier, theprocess 700 may proceed to block 716. Atblock 716, the application may ignore the immobilization command. -
FIG. 8 is a flow diagram of anexample process 800 for automatically initiating remote vehicle immobilization of a vehicle using an immobilizer device. Atblock 802, the immobilizer device may send an information query command to the vehicle via proximity communication. In various embodiments, the proximity communication may be in the form of NFC communication, Bluetooth communication, RFID communication, and/or so forth. The information query command may be received by a vehicle communication device of the vehicle. - At
block 804, the immobilizer device may receive a device identifier from a vehicle communication device of the vehicle via proximity communication. In some instances, the device identifier may be one of multiple identifiers that are received by the immobilizer device. In such instances, the immobilizer device may hold one or more of the device identifiers in a buffer until all of the device identifiers are processed. Atblock 806, the immobilizer device may send the vehicle identifier to a database of a wireless communication carrier that correlates vehicle identifiers to device identifiers of vehicle communication devices. In various embodiments, the database may be thecarrier database 132 of thewireless communication carrier 114. In such embodiments, the vehicle identifier may be sent via a network communication connection. The network communication connection may be a connection that is provided by thecellular communication network 112 and/or thenetwork 136. Atblock 808, the immobilizer device may receive a corresponding vehicle identifier for the device identifier from the wireless communication carrier via the network communication connection. - At
block 810, the immobilizer device may use the network communication connection provided by thecellular communication network 112 to send the vehicle identifier to a server at a government agency. In various embodiments, the server may execute an application to determine whether the vehicle that is identified by the vehicle identifier is subject to immobilization. For example, the vehicle may be subject to immobilization if it is the target of an outstanding APB, an Amber alert, a stolen vehicle report, and/or so forth. - At
block 812, the immobilizer device may determine whether a vehicle immobilization request for the vehicle identifier is received from the server at the government agency via the network communication connection. Accordingly, atdecision block 814, if the immobilizer device determines that the vehicle immobilization request is received, theprocess 800 may proceed to block 816. Atblock 816, the immobilizer device may broadcast an immobilization command that includes the device identifier to the vehicle via proximate communication. However, if the immobilizer device determines that no vehicle immobilization request is received, theprocess 800 may loop back to block 802. - The techniques may enable a mobile device or an immobilizer device to remotely immobilize a vehicle via peer-to-peer device communication with a vehicle communication device of the vehicle. Alternatively, the remote immobilization may be achieved by the user triggering a cellular communication carrier to send an immobilization command to the vehicle communication device via a cellular communication connection. In some instances, the peer-to-peer communication may be initiated by a master control device in a law enforcement vehicle. The remote immobilization of a vehicle may enable the vehicle to be safely brought to a stop without endangering the occupants of the vehicle or bystanders who are in the vicinity of the vehicle. In instances in which the occupants of the vehicle are fleeing suspects or felons, the remote immobilization of the vehicle may provide law enforcement officers with an opportunity to detain the occupants without dangerous vehicle pursuits that can jeopardize public safety.
- Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims.
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/282,572 US9939809B1 (en) | 2016-09-30 | 2016-09-30 | Remote vehicle engine immobilization |
PCT/US2017/054198 WO2018064430A1 (en) | 2016-09-30 | 2017-09-29 | Remote vehicle engine immobilization |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/282,572 US9939809B1 (en) | 2016-09-30 | 2016-09-30 | Remote vehicle engine immobilization |
Publications (2)
Publication Number | Publication Date |
---|---|
US20180095456A1 true US20180095456A1 (en) | 2018-04-05 |
US9939809B1 US9939809B1 (en) | 2018-04-10 |
Family
ID=61757086
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/282,572 Active US9939809B1 (en) | 2016-09-30 | 2016-09-30 | Remote vehicle engine immobilization |
Country Status (2)
Country | Link |
---|---|
US (1) | US9939809B1 (en) |
WO (1) | WO2018064430A1 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10339739B2 (en) * | 2017-01-26 | 2019-07-02 | SmartBox Technology, LLC | Vehicle key programming system and method |
US10356620B1 (en) * | 2018-05-07 | 2019-07-16 | T-Mobile Usa, Inc. | Enhanced security for electronic devices |
CN110943965A (en) * | 2018-09-21 | 2020-03-31 | 上海擎感智能科技有限公司 | Method, system, medium and device for sending/forwarding/processing distress request |
US10657812B2 (en) * | 2017-11-28 | 2020-05-19 | Toyota Jidosha Kabushiki Kaisha | Notification system, notification device, and notification method |
US20220078886A1 (en) * | 2017-03-31 | 2022-03-10 | T-Mobile Usa, Inc. | Managing communications for connected vehicles using a cellular network |
US11409278B2 (en) * | 2019-07-26 | 2022-08-09 | Zoox, Inc. | System and method for providing a teleoperation instruction to an autonomous vehicle |
US20230119247A1 (en) * | 2021-10-19 | 2023-04-20 | Lenovo (United States) Inc. | Wireless communication order session generation |
FR3135177A1 (en) * | 2022-04-29 | 2023-11-03 | Psa Automobiles Sa | Immobilization of a suspicious vehicle using V2X communication |
US11892835B2 (en) | 2019-07-26 | 2024-02-06 | Zoox, Inc. | System and method for controlling an autonomous vehicle |
US11922740B2 (en) * | 2017-08-10 | 2024-03-05 | Zoox, Inc. | Vehicle self-diagnostics |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9406086B2 (en) * | 2010-11-03 | 2016-08-02 | Endeavoring, Llc | System and method for violation enforcement utilizing vehicle immobilization |
US11440505B2 (en) | 2017-08-11 | 2022-09-13 | Aeris Communications, Inc. | Auto-immobilization of machines capable of moving |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070168104A1 (en) * | 2006-01-19 | 2007-07-19 | Honda Motor Co., Ltd. | Method and system for remote immobilization of vehicles |
US20100214084A1 (en) * | 2007-09-05 | 2010-08-26 | Haste Iii Thomas E | Vehicle immobilizer |
US8487740B2 (en) * | 2008-06-12 | 2013-07-16 | Kabushiki Kaisha Tokai Rika Denki Seisakusho | Vehicle function restriction system |
US8744412B1 (en) * | 2010-06-25 | 2014-06-03 | Cellco Partnership | Law enforcement vehicle information authorization system |
US20170186257A1 (en) * | 2015-12-23 | 2017-06-29 | Volkswagen Ag | Apparatus, method and computer program for controlling functions of a vehicle |
US20170294114A1 (en) * | 2013-03-14 | 2017-10-12 | The Crawford Group, Inc. | Smart Key Emulation for Vehicles |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE69918330T2 (en) | 1998-12-12 | 2005-05-12 | Howells, Donald Glanmor, Rushden | vehicle immobilizer |
US7119716B2 (en) | 2003-05-28 | 2006-10-10 | Legalview Assets, Limited | Response systems and methods for notification systems for modifying future notifications |
EP1781504A2 (en) * | 2004-08-25 | 2007-05-09 | The Marenco Group | Anti-carjacking apparatus, systems, and methods for hi-speed pursuit avoidance and occupant safety |
US7825782B2 (en) | 2007-03-20 | 2010-11-02 | Ford Global Technologies, Llc | Device and method for wireless vehicle communication |
US9406086B2 (en) * | 2010-11-03 | 2016-08-02 | Endeavoring, Llc | System and method for violation enforcement utilizing vehicle immobilization |
-
2016
- 2016-09-30 US US15/282,572 patent/US9939809B1/en active Active
-
2017
- 2017-09-29 WO PCT/US2017/054198 patent/WO2018064430A1/en active Application Filing
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070168104A1 (en) * | 2006-01-19 | 2007-07-19 | Honda Motor Co., Ltd. | Method and system for remote immobilization of vehicles |
US20100214084A1 (en) * | 2007-09-05 | 2010-08-26 | Haste Iii Thomas E | Vehicle immobilizer |
US8487740B2 (en) * | 2008-06-12 | 2013-07-16 | Kabushiki Kaisha Tokai Rika Denki Seisakusho | Vehicle function restriction system |
US8744412B1 (en) * | 2010-06-25 | 2014-06-03 | Cellco Partnership | Law enforcement vehicle information authorization system |
US20170294114A1 (en) * | 2013-03-14 | 2017-10-12 | The Crawford Group, Inc. | Smart Key Emulation for Vehicles |
US20170186257A1 (en) * | 2015-12-23 | 2017-06-29 | Volkswagen Ag | Apparatus, method and computer program for controlling functions of a vehicle |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20190266823A1 (en) * | 2017-01-26 | 2019-08-29 | SmartBox Technology, LLC | Vehicle key programming system and method |
US10339739B2 (en) * | 2017-01-26 | 2019-07-02 | SmartBox Technology, LLC | Vehicle key programming system and method |
US11195356B2 (en) * | 2017-01-26 | 2021-12-07 | SmartBox Technology, LLC | Vehicle key programming system and method |
US11690133B2 (en) * | 2017-03-31 | 2023-06-27 | T-Mobile Usa, Inc. | Managing communications for connected vehicles using a cellular network |
US20220078886A1 (en) * | 2017-03-31 | 2022-03-10 | T-Mobile Usa, Inc. | Managing communications for connected vehicles using a cellular network |
US11922740B2 (en) * | 2017-08-10 | 2024-03-05 | Zoox, Inc. | Vehicle self-diagnostics |
US10657812B2 (en) * | 2017-11-28 | 2020-05-19 | Toyota Jidosha Kabushiki Kaisha | Notification system, notification device, and notification method |
US11335198B2 (en) | 2017-11-28 | 2022-05-17 | Toyota Jidosha Kabushiki Kaisha | Notification system, notification device, and notification method |
US10356620B1 (en) * | 2018-05-07 | 2019-07-16 | T-Mobile Usa, Inc. | Enhanced security for electronic devices |
US10588018B2 (en) | 2018-05-07 | 2020-03-10 | T-Mobile Usa, Inc. | Enhanced security for electronic devices |
CN110943965A (en) * | 2018-09-21 | 2020-03-31 | 上海擎感智能科技有限公司 | Method, system, medium and device for sending/forwarding/processing distress request |
US11892835B2 (en) | 2019-07-26 | 2024-02-06 | Zoox, Inc. | System and method for controlling an autonomous vehicle |
US11409278B2 (en) * | 2019-07-26 | 2022-08-09 | Zoox, Inc. | System and method for providing a teleoperation instruction to an autonomous vehicle |
US20230119247A1 (en) * | 2021-10-19 | 2023-04-20 | Lenovo (United States) Inc. | Wireless communication order session generation |
US11861588B2 (en) * | 2021-10-19 | 2024-01-02 | Lenovo (United States) Inc. | Wireless communication order session generation |
FR3135177A1 (en) * | 2022-04-29 | 2023-11-03 | Psa Automobiles Sa | Immobilization of a suspicious vehicle using V2X communication |
Also Published As
Publication number | Publication date |
---|---|
US9939809B1 (en) | 2018-04-10 |
WO2018064430A1 (en) | 2018-04-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9939809B1 (en) | Remote vehicle engine immobilization | |
US10569739B2 (en) | Virtual keyfob for vehicle sharing | |
US10595352B2 (en) | Establishing a secure short-range wireless communications connection at a vehicle | |
US10538220B1 (en) | User activated/deactivated short-range wireless communications (SRWC) auxiliary key fob | |
US10019621B2 (en) | Identifying a vehicle using a mobile device | |
US9821767B2 (en) | Key module | |
US10654447B2 (en) | Vehicle sharing accessory module and system | |
US10231123B2 (en) | Bluetooth low energy (BLE) communication between a mobile device and a vehicle | |
US20180326947A1 (en) | Operating a key fob in a car sharing system | |
JP5803724B2 (en) | Authentication system and authentication device | |
US10377346B2 (en) | Anticipatory vehicle state management | |
KR20190038550A (en) | Communication Flow during Identification and Identification Inspection | |
RU2017135020A (en) | A mobile device for authenticating vehicle communications, a method and system for authenticating a mobile device for communicating with a vehicle | |
CN112822630B (en) | Data processing method of device and computer-readable storage medium | |
US9813399B2 (en) | Secure remote user device unlock for carrier locked user devices | |
US20140343755A1 (en) | Start system for a motor vehicle | |
US10919497B1 (en) | Systems and methods for starting a vehicle using a secure password entry system | |
EP3286945B1 (en) | Method and system for authentication of collaborative mobile devices | |
JP2015072244A (en) | Radio communication system and radio communication system ranging method | |
US9867050B1 (en) | Ultrasonic audio transmission of wireless LAN information | |
US20190193677A1 (en) | Distribution device, rescue system, method of controlling distribution device, and recording medium | |
JP2016211157A (en) | Information processing apparatus and unlocking control method | |
WO2014173015A1 (en) | Method, device and system for acquiring information about illegal driver | |
CN108737090B (en) | Method and apparatus for dynamic vehicle key generation and processing | |
US10306341B2 (en) | Method and apparatus for determining sensor data reliability at an incident scene for real-time and post-incident processing |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: T-MOBILE U.S.A, INC., WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:OBAIDI, AHMAD ARASH;REEL/FRAME:039913/0309 Effective date: 20160928 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNORS:T-MOBILE USA, INC.;ISBV LLC;T-MOBILE CENTRAL LLC;AND OTHERS;REEL/FRAME:053182/0001 Effective date: 20200401 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: SPRINT SPECTRUM LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINT INTERNATIONAL INCORPORATED, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINTCOM LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: CLEARWIRE IP HOLDINGS LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: CLEARWIRE COMMUNICATIONS LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: BOOST WORLDWIDE, LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: ASSURANCE WIRELESS USA, L.P., KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: T-MOBILE USA, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: T-MOBILE CENTRAL LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: PUSHSPRING, LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: LAYER3 TV, LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: IBSV LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 |