EP3119645A1 - Système de services automobiles - Google Patents

Système de services automobiles

Info

Publication number
EP3119645A1
EP3119645A1 EP15765431.0A EP15765431A EP3119645A1 EP 3119645 A1 EP3119645 A1 EP 3119645A1 EP 15765431 A EP15765431 A EP 15765431A EP 3119645 A1 EP3119645 A1 EP 3119645A1
Authority
EP
European Patent Office
Prior art keywords
vehicle
obd
threshold
user
server
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.)
Withdrawn
Application number
EP15765431.0A
Other languages
German (de)
English (en)
Other versions
EP3119645A4 (fr
Inventor
Jeremy Zeev GELBART
Steven Wolf
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Autobrain LLC
Original Assignee
Autobrain LLC
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Autobrain LLC filed Critical Autobrain LLC
Publication of EP3119645A1 publication Critical patent/EP3119645A1/fr
Publication of EP3119645A4 publication Critical patent/EP3119645A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
    • B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
    • B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
    • B60R16/0231—Circuits relating to the driving or the functioning of the vehicle
    • B60R16/0232—Circuits relating to the driving or the functioning of the vehicle for measuring vehicle parameters and indicating critical, abnormal or dangerous conditions
    • B60R16/0234—Circuits relating to the driving or the functioning of the vehicle for measuring vehicle parameters and indicating critical, abnormal or dangerous conditions related to maintenance or repairing of vehicles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00—Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • 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
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0816—Indicating performance data, e.g. occurrence of a malfunction
    • G07C5/0825—Indicating performance data, e.g. occurrence of a malfunction using optical means
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
    • G08G1/0108—Measuring and analyzing of parameters relative to traffic conditions based on the source of data
    • G08G1/0112—Measuring and analyzing of parameters relative to traffic conditions based on the source of data from the vehicle, e.g. floating car data [FCD]
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/052—Detecting movement of traffic to be counted or controlled with provision for determining speed or overspeed
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096708—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control
    • G08G1/096716—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control where the received information does not generate an automatic action on the vehicle control
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096733—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place
    • G08G1/096741—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place where the source of the transmitted information selects which information to transmit to each vehicle
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096766—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission
    • G08G1/096775—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission where the origin of the information is a central station
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/20—Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles
    • G08G1/207—Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles with respect to certain areas, e.g. forbidden or allowed areas with possible alerting when inside or outside boundaries
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
    • G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
    • G01C21/20—Instruments for performing navigational calculations
    • 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
    • G07C2205/00—Indexing scheme relating to group G07C5/00
    • G07C2205/02—Indexing scheme relating to group G07C5/00 using a vehicle scan tool
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Definitions

  • the present invention relates to monitoring of a vehicle performance using an On Board Diagnostic (OBD) device, and providing the results to a user.
  • OBD On Board Diagnostic
  • an apparatus that allows a user to set thresholds for one or more vehicle performance levels, and monitor the performance of the vehicle remotely. Additionally provided is an apparatus, system and method for allowing a user to monitor the state of their vehicle remotely via a connection with the OBD device, which can be configured to monitor the vehicle computer for one or more occurrences.
  • a system for providing monitoring of vehicle conditions may include a measurement device.
  • the measurement device may be removably connected to a vehicle.
  • the system may include a computer.
  • the computer may be located within the vehicle.
  • the measurement device may include a connection with the computer.
  • the system may include a receiver. The receiver may be configured to receive, from the measurement device:
  • the system may include a processor.
  • the processor may be configured to determine if the threshold
  • FIG. 1 depicts an illustrative computer system and network in accordance with the principles of the invention
  • FIGS. 2A-2C show an illustrative apparatus in accordance with the principles of the invention
  • FIG. 3A, 3B, 4A and 4B show illustrative processes in accordance with the principles of the invention.
  • FIGS. 5-12 show illustrative information in accordance with the principles of the invention.
  • the present invention relates generally to automobile services and, more particularly, to a system and apparatus for providing additional automobile services to a user.
  • the present invention includes providing a full suite of vehicle-related services by communicating vehicle-related information to users.
  • the present invention includes a device that plugs into the On-Board Diagnostics ("OBD") - II port of any car sold after 1996 that will be used to deliver a full suite of vehicle-related services.
  • the device reads information from a vehicle's computer.
  • the device may also include an Accelerometer, GPS, Wireless
  • GSM Global System for Mobile communications
  • CDMA Code Division Multiple Access
  • Near Field Communication e.g., Bluetooth
  • WiFi Wireless Fidelity
  • On-Board diagnostics is an automotive term referring to a vehicle's self-diagnostic and reporting capability.
  • OBD systems provide the vehicle owner or repair technician access to the status of the various vehicle systems and sub-systems. Currently, the OBD is not being utilized to its fullest extent.
  • the invention may be described as part of a system.
  • the OBD device may be described as being part of the system.
  • the system may include one or more of the features of the apparatus that are shown or described herein.
  • the system may include one or more OBD devices (hereinafter referred to as "OBD device” or the “device"), one or more servers, and one or more computing devices, such as a mobile device or computer. It should be noted that the system is not limited to these devices, and may include additional devices as well.
  • Embodiments of the present invention may include the device in combination with specialized software.
  • a user can trigger a set of functions to monitor information from the device and issue alerts to the user if certain thresholds are exceeded or reached. This can be accomplished with one click or toggle.
  • the selection of one or more operating modes with one click establishes, for example, a pre-determined set of thresholds and provides alerts for any thresholds that are exceeded or reached or reached.
  • the invention may include a device.
  • the device may be an OBD device.
  • the OBD device may adhere to, and include software and hardware that adhere to, the
  • the device may include a connection, and may be releasably connected to a vehicle.
  • the device may be connected to the vehicle via the data port.
  • the connection may be a plug-in connection, USB port connection, serial port connection, pin connection, or any other suitable connection.
  • the connection may also be wireless using protocols such as WiFi or Bluetooth.
  • the device may interact or communicate with a computer.
  • the computer may be an onboard computer located within the vehicle (also referred to as the "vehicle computer").
  • vehicle computer may be configured to measure one or more data points or parameters from the vehicle.
  • the invention is contemplated with the OBD device as separate device that plugs into, or otherwise connects with the vehicle, as well as with the OBD device being built into the vehicle.
  • the OBD device may be connected to the vehicle computer, integral to the vehicle, or may be built into the vehicle computer itself.
  • the OBD device may be any suitable diagnostic device for use in a vehicle.
  • the device may be a measurement device.
  • the invention is operable with a standard OBD device, as well as with an OBD device including the unique features discussed in this application.
  • the OBD device may include one or more processors, transmitters, receivers, transceivers and any additional suitable components.
  • the OBD device may include one or more communication systems configured to operate over various communication protocols.
  • the OBD device may be configured to operate using a GSM or GPRS network.
  • the OBD device may be configured to operate using 2G, 3G, 4G, LTE or any other suitable connectivity technology.
  • the OBD device may include one or more cellular or GPS antennas.
  • the OBD device may include short-range wireless communication hardware, such as Bluetooth and Wi-Fi chipsets.
  • the OBD device may include an internal battery supply.
  • the OBD device may draw power from external sources, such as solar power, or via connectivity to a car port.
  • the OBD device may be configured to draw power from multiple sources.
  • the OBD device may be configured to support TCP, UDP and FTP protocols.
  • the OBD device may include SMS connectivity, and may be configured to receive and send SMS messages.
  • the OBD device may be configured and updated via any suitable communication protocols, such as those already described.
  • the OBD device may include firmware.
  • the firmware may be configured to operate using predetermined communication protocols.
  • the device may be configured to receive one or more commands.
  • the commands may be altered to vary the information collected, received and/or transmitted by the device.
  • the OBD device may receive, via the connection port with the vehicle computer, a command or instruction to collect information related to the speed of the vehicle.
  • the OBD device may be instructed to collect data related to the acceleration and location of the vehicle, and to transmit the information at predetermined intervals.
  • the OBD device data usage may be optimized to limit the quantity of data sent and received by the device. Therefore, in accordance with the invention, the OBD device may be instructed to transmit information to the server only in response to a specified occurrence or event. For example, the OBD device may normally receive continuous data reports from the vehicle computer.
  • event based reporting may be used. Rather than have the device send ail information to the server at particular interval (i.e., 30 seconds), use of events allows the device to automatically notify the server when the event occurds. For example, to know the precise route that a driver took, GPS coordinates may not be used every 10 seconds. Instead, reports may be provided every time the vehicle changes heading, which will reduce the amount of data sent. It should be noted that event-based reporting may be used in conjunction with normal data transmission.
  • the system may include a server, such as the server already described.
  • the server may include one or more processors, transmitters, receivers, transceivers, and any additional suitable components.
  • the OBD device may be in contact with the server.
  • the server may set controls for the OBD device.
  • the OBD device may be instructed by the server to only send an alert to the server when the data received and/or processed by the OBD device indicates that a threshold has been exceeded or reached (i.e., speed threshold), a limit has been violated (i.e., geofence) or an event has occurred (movement detected in the vehicle by an onboard OBD gyroscope or accelerometer).
  • the OBD may be instructed to send an alert only when multiple events have occurred, such as both the speed threshold limit has been exceeded or reached and the geofence has been breached/violated.
  • Additional examples of data usage optimization of the OBD device may include instructing the OBD to only transmit a message that a threshold has been violated, and the type of threshold that has been violated, or transmitting a message containing additional data such as the particular data of the threshold violation, such as location, duration, etc.
  • the OBD device data may be transmitted from the OBD device to a server or plurality of servers and/or computers over cellular networks, wireless networks, USB, infrared, NFC or any other suitable transmission protocols.
  • the OBD device may transmit data to the servers using any other suitable protocols, such as UDP, UDP-C, TCP/IP, TU and SMS.
  • Vehicle data retrieved from the vehicle computer by the OBD device may be processed at one or more locations.
  • Various configurations as to where and how to process the vehicle data may be selected, programmed or input by a user, or by the company or entity responsible for managing the OBD device and its service.
  • a user may program, or transmit an instruction to, the OBD device to process the data using the OBD device's processor.
  • the user may transmit, using a telephone, mobile device, smartphone, computing device, such as a mobile device, laptop, desktop or server, application, or any other suitable program or device, a series of instructions to the OBD device on how to process data received from the vehicle computer.
  • the OBD may be instructed to only send speed information of the vehicle when the vehicle exceeds a programmed speed threshold, such as 50 MPH.
  • the OBD device may be instructed to monitor vehicle computer data to determine if a driver in the vehicle has engaged the hard brake.
  • the OBD device may be programmed, via firmware, software, initial instructions, updated instructions, or in any suitable way, to transmit certain information to the server.
  • the instructions may include an instruction for the OBD device not to process the data, and to send the data to the OBD device to be processed.
  • the device may receive an instruction to transmit all acceleration data to the server.
  • the device may further receive an instruction to transmit the acceleration data (or any other suitable data) at predetermined intervals. That is, the OBD may be instructed to transmit all deceleration data to the server at 30-second intervals.
  • the OBD may be further customized to transmit all data related to a particular parameter, such as deceleration data, while only transmitting predetermined/preset threshold violations for another parameter, such as
  • deceleration data (or any other parameter that may be processed by the OBD) may be transmitted at a periodic rate of 60 Hz, 30 Hz, 20 Hz, 5 Hz, 2 Hz irrespective of whether there is a change in the deceleration parameter.
  • the deceleration data may also be transmitted only upon a change in such parameter.
  • the deceleration data may also be transmitted at the next scheduled
  • transmission time only if there is a change. That is, if parameters in general or a particular parameter, may be transmitted at 30 Hz, and there is a change in a parameter between possible transmissions, the transmissions would not take place immediately after a change in the parameter, but would only be transmitted at the next scheduled transmission.
  • the OBD device may transmit unprocessed or processed data to the server.
  • the server may initially instruct the OBD device which parameters to monitor, what data to send, and at what intervals to send the data.
  • the server may process data received from the OBD.
  • the server may determine whether a threshold for a parameter has been exceeded or reached.
  • the server may instruct the OBD to determine, using the OBD processor, whether a threshold for a parameter has been exceeded or reached (or fall below a threshold). If the OBD processor determines that a threshold for a parameter has been exceeded or reached, the OBD may be further instructed, either previously or at that point, to send a message to the server of the exceeding of the threshold.
  • the OBD device may be initialized.
  • the initialization of the device may be performed prior to the first use of the OBD by a user.
  • An exemplary initialization device sequence may include (1) Input OBD device phone number (and/or other identifying OBD information such as IMEI, IP address, and the like) into server; (2) Send Initial Command to Device via, for example, SMS; and (3) Set Port, IP address, Username, Password, APN, SMS number, Communication Protocol of the device with which the OBD is to communicate.
  • the OBD device may be assigned a unique telephone number. The telephone number may allow the OBD device to communicate using standard telephonic features, such as using voice calls, SMS or MMS messaging, or transmitting or receiving data, using any suitable communication protocols.
  • the device phone number associated with the OBD may be saved and associated with the program server.
  • the program server may be one device, or a series of interconnected devices or servers, that manages the OBD devices in multiple vehicles.
  • the server may transmit an initial command.
  • the initial command may be transmitted to the OBD device.
  • the OBD device may receive an SMS from the server.
  • the initial command notifies the OBD device of the server's IP address and Port, so that the OBD devuce may communicate with the server.
  • the initial command may also notify the OBD device of a username and/or password to the server such that the OBD device may logon to the server.
  • the password may be optionally required.
  • the user may access a Graphical User Interface ("GUI") that displays or utilizes information received from the OBD device.
  • the GUI may be located on a user device, such as a telephone or computing device.
  • the user device may be in contact with the server and/or the OBD device, and any other suitable devices.
  • the server may set the Port, IP address, username, password, APN, SMS number and/or communication protocol for communicating with the device.
  • the OBD device may be plugged into a portal.
  • the portal may be used to initially communicate initial information to the OBD device, communicate with the device, and set the information as outlined in steps 1-3.
  • the portal may be a docking station, and the docking station may include a powering unit to charge the OBD device.
  • the docking station may be powered using any suitable powering system.
  • the OBD device may receive a Subscriber Identity Model (“SIM”) card.
  • SIM Subscriber Identity Model
  • the SIM card may be programmed via the docking station, which may send a command to the OBD device.
  • the OBD device may be programmed by the server.
  • the subsequent programming sequence may include (1) receiving a response from the OBD device to the initial command; (2) sending a command to the device to query device firmware and model;
  • the OBD may indicate to the server that the initial command has been received.
  • the OBD device may validate the commands.
  • the query may commence a test sequence.
  • the device table may include a lookup table or any other suitable table stored in memory, may initialize such table and may store initial values in such table.
  • the table may be associated with the OBD device.
  • Each OBD device may be associated with a unique lookup table.
  • the lookup table may be located in the server.
  • Each device may be stored with a model type associated with it.
  • the thresholds may be setup using default parameters.
  • the default parameters may include default thresholds based on one or more modes.
  • the default parameters may be modified.
  • the thresholds may also be customized thresholds, input by the user.
  • the user may input the thresholds via an application on a smartphone or computer associated with, and in direct or indirect communication with, the OBD device.
  • the OBD device status may be set to onboarded, which can indicate that the device is running properly.
  • the user may receive a notification via any suitable method that the device is onboarded.
  • the server may send an instruction to the OBD to determine GPS coordinates of the vehicle, using the OBD internal GPS antenna, the GPS antenna of the vehicle, or any other suitable method.
  • the OBD device may include a memory module, power supply, microprocessor, firmware, and one or more communication hardware chips (e.g., a CatlO LTE Modem, Intel's 7360 LTE modem, or Qualcomm's MDM9625 LTE Modem).
  • the OBD may be
  • the OBD may be connected to the OBD port in the vehicle using any suitable connection, such as a pin connection.
  • the OBD device may be programmed with data collection parameters.
  • the OBD may be configured to be operable with various modes. The modes may operate sequentially, or multiple modes may be utilized by the OBD at the same time.
  • the OBD may be utilized for vehicle pick up or drop off.
  • a vehicle owner or operator hereinafter, "owner,” but used to reference operator non-owners as well
  • owner may desire to leave their vehicle under the care of another individual or company for a temporary period of time.
  • the vehicle owner may desire to monitor the vehicle, or prevent the occurrence of certain events.
  • valet mode a mode, known herein as valet mode, to monitor the vehicle when under the care and/or custody of another person or entity. It should be noted that valet mode is merely a reference name, and is not intended to limit the scope of the invention.
  • the owner may input a number of parameters to be monitored.
  • the parameters may have been input by the owner prior to leaving the vehicle with a parking attendant.
  • the parameters may be input at the time of the handoff event to leave the vehicle to, for example, the valet or another party.
  • the parameters may be default parameters input by the manager of the OBD system, or default parameters input by the owner.
  • the parameters may include a maximum speed threshold, maximum acceleration threshold, geofence coordinates, and/or odometer thresholds.
  • the geofence coordinates may include a radius of permissible locations for the vehicle while valet mode is enabled. For example, once valet mode is activated a geofence including points on the circumference of a circle of a particular radius around the point at which valet mode was activated. That radius, may be for example, 1 mile, 0.5 miles, 1 km, 0.5 km, and the like. The radius may also be larger or smaller depending on the nature of the valet. For example, if the valet has a parking lot within a certain radius of the dropoff location, the radius may be smaller and closely surround the parking lot.
  • the geofence coordinates may also, or alternatively, include a radius of
  • the geofence coordinates may also include certain areas, such as a specified street, where the vehicle is not allowed, even when within an otherwise permissible geofence area.
  • the prohibited areas may include, for example, areas with a level of crime higher a certain threshold or crimes related to vehicles (e.g., carjacking, vehicle theft, and the like).
  • the server and/or the OBD device may determine whether any part of the geofenced area includes areas with crime rates higher than 20% (or another percentage) more than other portions of the geofenced area (or the national average, city average, state average, or other threshold) and may then exclude that area from the geofenced area.
  • Variables such as number of car accidents, demographic information including census data, may also be used separately or in conjunction with with crime rates
  • the owner may initiate the valet mode.
  • the valet mode may be initiated by toggling a switch or pressing a button, such as one on a smartphone application, to initiate the valet mode.
  • the OBD monitors the vehicle for violation of one or more thresholds.
  • the OBD may transmit a message to the server with data including one or more of the type of threshold violation (i.e. geofence violation), duration of violation, frequency of violation, current location of the vehicle, and any other suitable information.
  • the server may then transmit an alert to the owner if there is a violation.
  • the owner may receive an alert from the user with information about the threshold violation.
  • the owner may instruct the server to transmit threshold violation alerts at each occurrence, in real-time.
  • the owner may instruct the server to transmit threshold violation alerts in batches, such as when there are a certain number of alerts (i.e. 5 alerts), or in batches at predetermined time intervals (e.g., every hour, minute, and the like).
  • the OBD device may additionally be operable to provide a system for facilitating retrieval of a valeted or parked vehicle.
  • the retrieval steps may include (1) a customer instruction to retrieve the vehicle; (2) identification of the valet company or parking company responsible for the vehicle, which is determined by prior input by the user or valet company, or by determining the GPS location of the vehicle.
  • the OBD device may be operable to provide a system for facilitating the drop off of a vehicle to be parked.
  • the steps may include (1) leaving the vehicle at a location; (2) initiating an application to request pickup at a specified location; (3) searching or identifying a valet or parking company to park the vehicle; (4) transferring the possession of the vehicle; (5) optionally initiating valet mode; and (5) optionally alerting the user that the vehicle has been parked.
  • the OBD device may be used to facilitate user pickup of a parked vehicle.
  • a system may facilitate the process for retrieving a valeted vehicle using the following steps: (a) initiating a vehicle retrieval application and/or feature within an application, such as one on a phone or computer; (b) requesting retrieval of the vehicle and preparation of the vehicle for pickup; (c) identifying the valet company/valet attendant where the vehicle is parked; and (d) transmitting a message to the company/attendant to prepare the vehicle for pickup.
  • an application may include functionality to interface with an OBD device.
  • the application may be configured to retrieve the GPS of the vehicle using the GPS receiver located within the OBD device or within the vehicle itself (which would be provided to the application via the OBD).
  • the application may also have previously stored the GPS coordinates of the vehicle when in the vehicle, such as when the owner drops off the vehicle at the parking facility. Further, the owner can manually enter the parking area or facility address and location within the application. The owner can also input the name of the parking facility or nearby businesses/sites and select the name on the business and/or a point on a map.
  • the application may be configured to harness communication systems of a telephone or computer to transmit a message.
  • the application may receive an input from a user to retrieve the vehicle.
  • the application may then determine the location of the vehicle, and initiate step (c).
  • the application may determine the valet company associated with the parked vehicle. For example, using GPS coordinates of the parked vehicle, the application may utilize a database to determine what entity owns or operates the parking facility at that location. In another example, the application may access, via public records or mapping software, the owner of the facility.
  • the application may also determine the contact information of the operator of the location, and at step (d), contact the parking facility.
  • the contact at step (d) may include phone call, a text message or an email, which includes pre-programmed details of the vehicle, and/or a vehicle ID/parking ticket.
  • the application may remotely activate the OBD device.
  • the OBD device may be instructed to begin actively tracking the location of the vehicle, as well as when the ignition is activated. This feature allows the owner of the to determine the estimated time at which the vehicle will be ready for pickup. For example, once the OBD device determines that the ignition has been activated, the OBD device may transmit a message to the server, which then transmits an alert to the owner. The owner may then know that the vehicle will be ready for pickup in a few minutes.
  • the server and/or the OBD may estimate the amount of time necessary to drive the vehicle from its current location to the pickup location and notify the user of such time. Even prior to the ignition being turned on, the server may use data as to how long it generally takes a particular valet company to turn the ignition on from the time a car is requested and provide a time estimate based on such data.
  • a sequence for tracking the vehicle using the OBD device may include: (1) the driver of a vehicle transfers their vehicle to a valet/parking attendant; (2) when the vehicle is transferred, the driver activates a vehicle monitoring mode using an application, in order to monitor the location, speed and various additional attributes of the vehicle (It should be noted that these attributes can be monitored, remotely, via the application, in real time.
  • a server receives initiation of the mode; (4) the server queries the OBD device for the current location of the device/vehicle; (5) the server receives the location of the vehicle; (6) the server creates a geofence with a radius around the current location and/or planned location (e.g., the location of the valet parking lot) of the vehicle; (7) the server converts the radius of the geofence into a plurality of GPS coordinates, and populates and connects those coordinates on a map within the application; (8) the server creates a speed threshold for the vehicle (the speed threshold may be based on, for example, the speed limit on particular roads); (9) the server creates acceleration and/or deceleration thresholds for the vehicle; (10) the server instructs the OBD to transmit an alert to transmit a
  • the creation of the geofence may be performed using prepopulated parameters for the geofence.
  • the OBD device may be
  • the preprogramming may be done at the device level, or at the server level. In another example, a user may input a customized geofence radius.
  • the speed threshold may be predetermined, or customized by the driver.
  • point one is at 60 degress, point two is at 120 degrees, etc.; (3) for each point, the coordinates are calculated by [r * cos(degrees), r * sin(degrees)], with "r” standing for radius or inradius, which gives the coordinates in miles; and (4) the coordinates are then converted to latitude and longitude coordinates.
  • Exemplary formulas and code for converting the radius into geofence coordinates may include:
  • latitude Iatitude_coordinate / one_latitude_in_miies + latitude of midpoint
  • longitude longitude_coordinate / one_longitude_in_miles + longitude of midpoint
  • an embodiment of the present invention provides a system for providing vehicle related services comprising: an On Board Diagnostic device (OBD) comprising wireless communication, wherein the on board diagnostic device is connected with an automobile's computer; a program product comprising machine-readable program code for causing, when executed, the device to perform the following process steps: compiling data from the OOB Diagnostic device (OBD)
  • OBD On Board Diagnostic device
  • program product comprising machine-readable program code for causing, when executed, the device to perform the following process steps: compiling data from the
  • the OBD device may continuously monitor the vehicle computer data.
  • Data points (or parameters/variables) measured by the vehicle computer may include, but are not limited to: fuel level, engine coolant temperature, battery level, fuel pressure, engine RPM, vehicle speed, intake air temperature, oxygen sensor information, barometric pressure, throttle position information, ambient air temperature, fuel type or air flow information, or any other suitable information. It should be noted that the OBD-II standard is used to govern which OBD parameters are to be monitored by the vehicle computer, and all OBD Parameter ID's are contemplated in this invention.
  • the OBD device may include a receiver.
  • the receiver may receive information.
  • the information may be received from a server.
  • the OBD device may receive information from the computer, such as data measured or monitored by the vehicle computer.
  • the OBD device may also receive information and/or instructions from the server.
  • the server may be located in a separate location from the device.
  • the server may transmit information and/or instructions to the device.
  • information/instructions may include one or more variables, parameters and/or thresholds.
  • a user of the invention may monitor the state of repair of a vehicle, its location, speed, acceleration, deceleration and other vehicle-related information, using the OBD device.
  • the OBD device may be plugged into the vehicle, and may contain software, a GPS antenna, an accelerometer, a cellular antenna to communicate data between the device and a server which could then communicate with a user.
  • the server may communicate with the user by activation warnings and delivering information to users via a plurality of communication methods, including, but not limited to telephone calls, text messages, email, ftp, etc.
  • the software of the present invention may allow users to use a one-click feature to set various modes, thereby allowing the user to get alerts and information about the vehicle based on parameters that can be predetermined by mode.
  • the present invention allows the user to easily receive and use vehicle-related information such as warnings, reports, and other information.
  • the present invention may include an OBD device plugged into a motor vehicle.
  • the OBD device gathers information from the vehicle's on-board computer; and independently collects information such as vehicle speed, location, acceleration, deceleration (in three dimensions) and communicates that information to server via a wireless connection, such as a cellular connection. Further, the present invention may receive requests to gather and report on specific information that the OBD device is programmed to report.
  • the user interface of the present invention may include a Website, Mobile App, SMS message, Phone (and other methods of communication), which allows users to select various modes using one click with each mode designed to deliver specific feedback to the users or to others.
  • the intermediary server provides a method for communicating between the user and the OBD device.
  • the software transmits and receives information to and from the OBD device, analyzes it and facilitates communication between the user and the website, mobile application, email, text messages or person.
  • a method of using the present invention may include the following; (1) Insert OBD device in vehicle port; (2) Subscribe to the OBD device monitoring service; (3) Use website, mobile application, SMS or Voice communication to initiate programming sequence and calibration of device.
  • Valet mode A vehicle owner or driver may establish an alerts system for when a valet attendant or parking garage is mishandling the vehicle.
  • the driver transfers their vehicle to the valet attendant, they can initiate valet mode through an application.
  • thresholds for, for example, speeding, acceleration, deceleration, geofence, and odometer are automatically configured.
  • the thresholds may be preconfigured, or may be input by the user. If the thresholds are violated, the user receives an alert. For example, a speed limit of 30mph, a circular geofence of one mile, and certain acceleration thresholds.
  • [0080] Family safety mode A user may establish several safe driving thresholds. This may be established by toggling on, or selecting a one-click feature, to activate the mode.
  • the mode may activate predetermined or preconfigured safety thresholds, including, for example, speed, hard acceleration, hard deceleration and preset geofences.
  • the application relays the activation to a server, which transmits an instruction to the OBD device to begin monitoring the vehicle computer for the threshold violations.
  • the OBD device may be further instructed to alert the server when any of the thresholds are exceeded or reached. Once the server receives an alert that the threshold is exceeded or reached, the server may choose to send an alert to the user, based on the user's predetermined threshold configurations.
  • Certain embodiments of the present invention may also include more than one "Profile" that may be activated and each Profile may have different pre-determined thresholds, i.e., for user A, 55 MPH and certain geofence parameters as well as certain accelerometer readings OR 65 MPH.
  • Profile may also include more than one "Profile” that may be activated and each Profile may have different pre-determined thresholds, i.e., for user A, 55 MPH and certain geofence parameters as well as certain accelerometer readings OR 65 MPH.
  • Towing Alerts The user may enable monitoring of the vehicle remotely to determine if the vehicle is being towed or moved.
  • the user may activate towing monitoring. When this mode is activated, the vehicle ignition may be off. It should be noted that towing monitoring may also be activated when the ignition is on, such as when the OBD device detects upward movement of the vehicle.
  • the OBD device may then be instructed, via the server, to monitor the vehicle. It should be noted that in all modes, and in the towing mode, the OBD may utilize vehicle computer data, as well as data determined by the OBD device hardware and software. For towing mode, the OBD device may monitor for one or more conditions when the vehicle is ignition is off, and not switched on.
  • the OBD device may monitor if: (a) the accelerometer and/or GPS antenna/system and/or gyroscope reports the vehicle is being tilted and/or lifted (for example, if a change in the altitude parameter in the GPS is detected, or if the accelerometer and/or gyroscope detect a change); (b) the vehicle is moving or (c) there is a sudden acceleration.
  • the accelerometer or gyroscope may be located within the vehicle itself, or may be built into the OBD device. Thus, the OBD device may determine, when the ignition is off, that the vehicle is moving or there is an acceleration, based on data retrieved from the vehicle computer.
  • the OBD device may determine that the vehicle is moving or there is an acceleration based on the accelerometer and/or gyroscope and/or GPS antenna/system within the OBD device.
  • the OBD device may send a message to the server that movement has been detected when the ignition is off.
  • the OBD device may send the message only when sufficient movement has been detected.
  • the threshold for movement may include determining that the movement has occurred for a sufficient duration, such as continuous movement for more than 30 seconds (or 20 seconds, or 15 seconds, or 10 seconds, or 5 seconds, or 3 seconds, or 1 second), and/or sufficient acceleration (for example, 3 m/s A 2 or 4 m/s A 2).
  • the user may enable monitoring of a vehicle associated with the OBD device.
  • the attendance mode or school attendance mode, may be used to monitor work, school, medical or other repeat appointments or time commitments. Thus, whenever an individual must drive to a specified place, the attendance mode allows monitoring to ensure that the user is attending. Additionally, it provides functionality to ensure that the user is attending for the right amount of time.
  • the attendance mode may be enabled by a first user, who may be the administrator of the device.
  • the school attendance mode may be enabled on a per-use basis, such as every time a child uses the vehicle, the administrator enables school attendance mode. Alternatively, school attendance mode may be enabled for extended periods of time, such as weeks, months or years.
  • the monitoring of the vehicle by the administrator of the OBD device may allow monitoring of a student or child's vehicle.
  • the administrator may establish permissible routes for the vehicle.
  • the permissible routes may be established by the administrator by using a user interface.
  • the user interface may provide the administrator with a map, and the administrator may select a route (or a plurality of routes) and designate the route as permissible.
  • the administrator may also select one or more allowable deviations, such as selecting a parallel avenue or block (in the case of traffic, for example).
  • the system may include a threshold for allowable deviations, such as if traffic is detected, allowing a deviation of a block (or 2 blocks or 3 blocks or 4 blocks), or mileage radius (such as 0.5 miles or 1 mile or 1.5 miles).
  • Traffic may be detected by receiving such traffic from a third party provider or by analysis performed by the OBD device or the server.
  • the server may receive information as to the speed and location of the vehicle. Based on the location and/or speed of the vehicle as compared to the speed limit of the road on which the car is driving and/or the speed of the vehicle on previous trips on the road as previously related by the OBD to the server or as stored in the OBD.
  • the server may take into account the time of day in determining whether the vehicle is in traffic, warranting deviation from the permissible route. That is, while 30 MPH may be normal for 2 p.m. on a weekday, 15 MPH may be normal for 5 p.m. on a weekday.
  • the server may have a threshold to warrant deviation such as 50% (or 25% or 75%) of the normal speed based on at least one of the following factors: location, date, time, weather, whether the day is a holiday, current driver, gender of the driver, age of the driver, and the like.
  • the administrator may establish permissible routes to/from the student's school, and may provide monitoring and reporting of any divergence from the permissible routes.
  • the monitoring and reporting of divergence from the routes may include receiving information from the OBD device, which may be programmed to detect stoppage of the vehicle. Further, in one
  • the OBD device may analyze traffic, either from publicly available traffic resources such as news sites, smartphone traffic applications, or any other suitable traffic provider. The OBD device may then determine that, if the vehicle stops when there is no detected traffic, an impermissible stop has occurred. The OBD may also use its onboard accelerometer to determine sudden stops and delays. Thus, the device may detect stops along the way and delays of more than a predetermined amount of time (such as, for example, 1 minute, 2 minutes, 3 minutes, 4 minutes or 5 minutes). The predetermined number of minutes for stops may be preconfigured by the system, or may be input the user.
  • a predetermined amount of time such as, for example, 1 minute, 2 minutes, 3 minutes, 4 minutes or 5 minutes.
  • the predetermined number of minutes for stops may be preconfigured by the system, or may be input the user.
  • the number of minutes for stops may be based on the maximum amount of time a red light may stay red and may take into account the distance the car is from the light (since it may take time for the cars in front of the relevant car to move).
  • the OBD device may warn an administrator if the vehicle leaves the school location, or travels outside an authorized route, at unauthorized times.
  • Carpool Mode and School Bus Mode A user may input, via any suitable method, such as on a website or application on a smartphone, one or more participants in a carpool or bus.
  • the carpool may be one or more individuals sharing a vehicle.
  • Carpool mode may monitor drop/off and pickup locations of one or more individuals within the carpool, set permissible routes and deviations for carpool, set an order of pick up/drop off for carpool participants, monitor vehicle progress along carpool route, and report any changes to a route to authorized carpool
  • the bus mode may monitor, for each user, the progress of one child on a school bus.
  • the server may receive, from a user input into a user interface, a carpool order for pickup and/or drop off.
  • the order for pickup may differ from the drop off order.
  • the server may determine the order for pickup and order for drop off. The user may then adjust the order.
  • the server may transmit the order to the OBD device, and instruct the device to monitor the stopping points (e.g., drop offs and pickups) of the vehicle.
  • the OBD device may be instructed to monitor the location of drop offs and pickups, as well as the order in which they occur.
  • the OBD device may be further instructed to transmit a message to the server if the order and/or duration of the drop off and pickups is different than the prepopulated list.
  • the OBD device may also transmit, using its onboard GPS antenna, the location of the vehicle to the server.
  • the OBD device may transmit its location in real time, or at predetermined intervals, such as every 30 seconds, or 1 minute, or 2 minutes, or 3 minutes, or 4 minutes, or 5 minutes.
  • the server may then transmit the information to one or more users, who may monitor the progress of the vehicle along the route, and receive any changes or deviations from the route.
  • the OBD device may also calculate estimated times until each stop, and at predetermined intervals, or in real time, transmit the estimated times to the server.
  • the server may then transmit an alert to the user.
  • a user may transmit a query to determine the location of a child on a school bus.
  • the location may be returned from the OBD device of the school bus.
  • the location may be received from the child's cell phone.
  • the location may be crowdsourced based on the GPS location of all or some of the children's phones on the bus.
  • the system may be configured to allow multiple users to follow each other in their vehicles to a predetermined or non-predetermined location, and/or along a predetermined route or a non pre-determined route by creating a Follow Mode event.
  • Each of the users may enable the follow mode, which transmits an instruction to the OBD device in their vehicle to transmit location signals using a GPS antenna.
  • follow mode Once a user selects follow mode, they will be prompted to enter identifying information for one or more other users.
  • the leader may generate a unique code that can be shared with potential followers. When the followers enter this code, they may see the location of the leader.
  • the system will alert the other user(s) of the request for them to participate in a follow mode event, and each user may separately and proactively accept the invitation before their location is revealed to other participants.
  • each user's OBD device may transmit its location using the onboard GPS antenna, or through the GPS antenna of a telephone, to the server.
  • the server may then aggregate the locations of all participants, and display them on a map.
  • One of the users may designate themselves as the Leader (similar to the leader on a conference call).
  • All participants in the Follow Mode event can display a map showing the location of each participant in the Follow Mode event, or just the location of the Leader. The location may be determined based on the GPS coordinates received from the OBD device for each participant, or based on the GPS coordinates retrieved from a participant's phone.
  • the route to that location may be displayed on a Graphical User Interface (GUI) to participants, along with the location of the Leader and/or the pre-determined location, and/or along with all other participants' vehicles as waypoints on a map. If the event is not to a predetermined location, the location of the Leader and the individual user, or the location of the leader and all participants, may be displayed on a map.
  • GUI Graphical User Interface
  • Driving Safety When this mode is activated by a user, the system monitors to determine when the ignition is on and the speed of a vehicle exceeds a pre-determined threshold.
  • the ignition status is determined via the OBD device, which receives ignition information from the vehicle computer.
  • the speed of the vehicle may be determined using the device accelerometer, or analysis by the OBD of the vehicle computer information (including, for example, GPS coordinates). If the ignition is active and a pre-determined threshold is exceeded or reached, functions associated with a driver's email, text messaging, and/or voice calling will be disabled and/or modified on the cellular phone of a person associated with that particular vehicle.
  • the OBD device is additionally operable to detect potholes.
  • the OBD contains a gyrometer and accelerometer, which detect changes in speed and movement to determine the presence of potholes. Information about the location of the potholes is compiled and sent to the server, where it is stored in a database. The pothole information is then aggregated and provided to other users.
  • Safe Baby Mode The user may activate the mode by toggling a switch or clicking a selection. This mode may be activated for extended period of time. For example, SBM may be activated when a user brings a baby home from a hospital, and remain active for a number of years.
  • SBM When active, SBM assists a user in monitoring their vehicle for children. Thus, when a user exits the vehicle, checks are performed to make sure that no baby, infant, or child is left inside the vehicle.
  • the OBD device may send a notification to the server, which transmits an alert to a driver or the person who activated SBM.
  • the notification may alert the driver that the vehicle has been turned off, and may be presented as a pop-up alert, either within a smartphone application or on a phone, as an email, or SMS message, and the like.
  • the system may activate a microphone within the OBD device in order to listen in on the vehicle. If the OBD device detects a noise level above a predetermined threshold, indicating the presence of a child, or noise for an extended period of time that is determined, by the system, to be human generated noise, the system may initiate a call to first responders. If the OBD device determines that a human may be in the vehicle, the OBD device may connect with a call center, which may allow a human operator to determine whether a baby is in the vehicle, based on sound, or video.
  • a predetermined period of time such as, for example, 10 minutes
  • the OBD may also determine when the the human is a child by analyzing the pitch, breathing patterns, determine the words used via voice recognition, and the like. Thus, if for example, the OBD and/or the server determines that a person is speaking (e.g., on a phone) such that the voice recognition can determine the words being used, it is determined that that person is not a baby or an infant. Once voice recognition software determined the words being used, the OBD and/or the server may use the Flesch Reading Ease scale and/or the Flesch-Kincaid Grade-Level scale to determine the age of the person speaking. Thus, for example, using the scale it may be determines that the speaker is 5 years old and, thus, a child is still in the vehicle.
  • the OBD device may also include a temperature sensor.
  • the system may contact emergency responders.
  • the OBD device can be instructed to, and then trigger, turning on the vehicle's heating system.
  • the OBD device may be instructed to turn on the vehicle's air conditioning system.
  • the air conditioning or heating systems may be turned on by the OBD device.
  • the OBD device may further include a motion sensor, which can be used concurrently with the temperature sensor and/or microphone to detect the presence of a child, or afterward. Additional features may include a pressure sensor, such as one installed under the child seat, which is in communication (e.g., Bluetooth or WiFi) with the OBD device, and is configured to instruct the OBD device that a child is present or absent from the seat.
  • a motion sensor such as one installed under the child seat, which is in communication (e.g., Bluetooth or WiFi) with the OBD device, and is configured to instruct the OBD device that a child is present or absent from the seat.
  • SBM may be operable, therefore, to prevent unintentional leaving of a child or baby in a vehicle. Toggling on the SBM mode instructs the system to begin checking for a child in the vehicle.
  • the server receives an instruction from a user device to initiate SBM.
  • the system is then configured to receive, when in SBM, an alert that the vehicle ignition is turned off.
  • the OBD device transmits a notification of such to the server.
  • the server transmits an instruction to the OBD device, or alternatively, at the time when SBM is activated, the OBD device receives an instruction, to determine that a driver or individual has vacated the vehicle.
  • the OBD may determine, once the ignition has been turned off, whether a Bluetooth connection between the vehicle and a mobile device has been terminated.
  • seat sensors may be in communication with the OBD device and/or the server, and may indicate whether anyone is remaining in the vehicle.
  • the SBM may utilize motion sensors, video cameras, such as a video camera mounted in the vehicle or on the OBD device, infrared sensors located within the OBD device or the vehicle, a microphone to detect a child voice or sounds, or any distress sounds, and a pressure sensor in the child car seat.
  • motion sensors video cameras, such as a video camera mounted in the vehicle or on the OBD device, infrared sensors located within the OBD device or the vehicle, a microphone to detect a child voice or sounds, or any distress sounds, and a pressure sensor in the child car seat.
  • the notification sequence notifies the driver, as well as one or more emergency contacts input by the user and stored within the OBD and/or server.
  • the system may notify emergency authorities. The notifications may occur via SMS or telephone call.
  • emergency services may only be notified when dangerous conditions are detected within the car.
  • the OBD may then determine the temperature, the recent drop or rise in temperature, air quality within the vehicle, and other suitable conditions. If the conditions are all suitable, emergency services may not be notified. Instead, additional attempts may be made to contact the driver or owner. Only then may emergency services be notified, after, for example, five attempts or twenty minutes, or any other suitable number. In the event of a sudden temperature change, emergency services may be contacted immediately.
  • some or all of the following sequence may occur, in no particular order: (1) determine the local Public Safety Answering Point (PSAP) based on the GPS coordinates of the vehicle; and (2) notify the appropriate PSAP that there is a child in the car and needs assistance. Notification of the local PSAP may occur with the OBD device
  • the server may transmit an instruction to the OBD device to remotely control some functions within the vehicle in order to increase the baby's safety while waiting for the driver, parent, or authorities.
  • the OBD may communicate with the vehicle's computer and instruct the computer to turn on the air conditioning or heating system, open or close windows, turn on or off lights, and lock or unlock the doors.
  • the present invention may also be operable to predict when the car battery will fail, project traffic based on driving patterns, monitor fuel usage and efficiency, and display the different costs/savings of adopting different driving strategies.
  • Exemplary threshold calculations for the various modes may be as follows, with the following speed thresholds in miles per hour, and acceleration thresholds and deceleration thresholds in miles per hour per second:
  • the computer-based data processing system and method described above is for purposes of example only, and may be implemented in any type of computer system or programming or processing environment, or in a computer program, alone or in conjunction with hardware.
  • the present invention may also be implemented in software stored on a computer-readable medium and executed as a computer program on a general purpose or special purpose computer. For clarity, only those aspects of the system germane to the invention are described, and product details well known in the art are omitted. For the same reason, the computer hardware is not described in further detail. It should thus be understood that the invention is not limited to any specific computer language, program, or computer.
  • the present invention may be run on a stand-alone computer system, or may be run from a server computer system that can be accessed by a plurality of client computer systems interconnected over an intranet network, or that is accessible to clients over the Internet.
  • many embodiments of the present invention have application to a wide range of industries.
  • the present application discloses a system, the method implemented by that system, as well as software stored on a computer-readable medium and executed as a computer program to perform the method on a general purpose or special purpose computer, are within the scope of the present invention.
  • a system of apparatuses configured to implement the method are within the scope of the present invention.
  • a system for monitoring valet and/or parking facility usage of a vehicle is therefore provided.
  • the system may include an apparatus or method.
  • the system may include a server.
  • the server may receive information from a user.
  • the user may transmit the information using a computer, web application, website, smartphone, application, or any other suitable device.
  • the user may transmit an instruction to the server to initiate a valet mode.
  • the initiation of the valet may be selected by the user on a graphical user interface.
  • the user may instruct the server to initiate a valet restriction function.
  • the server may transmit a message to the OBD device for the associated vehicle to monitor the vehicle usage, via data received from the onboard vehicle computer, for violation of one or more predetermined thresholds, such as speed, acceleration, deceleration, and geofence violation.
  • the user may form a geofence around the location of the vehicle.
  • the user may know that he or she desires to leave the vehicle at the parking facility for two days.
  • the user may be concerned about "joyriding" or the use of the vehicle by one or more valet attendants.
  • the user may therefore transmit a request to the server to form a geofence.
  • the settings of valet mode may be preconfigured or customized to form a default geofence whenever the mode is initiated.
  • the geofence may include outer boundaries for the vehicle.
  • the geofence may be formed with a mileage radius, which may be a default radius or customized by the user.
  • the server may instruct the OBD to monitor the vehicle to determine if it travels more than 0.5 miles outside the radius of the geofence, with the centerpoint being the current location of the vehicle or any point within a parking facility. If the OBD determines that the mileage radius has been exceeded or reached, the OBD may transmit a message to the server, which may transmit an alert to the user that radius has been exceeded or reached.
  • the user may then transmit a message, or select an option, to retrieve the vehicle.
  • the server may transmit a query to the OBD device.
  • the query may be a location query to determine the current location of the vehicle.
  • the query may include a request to retrieve the vehicle.
  • the location query may further include (1) querying the GPS location of the vehicle; (2) determining the GPS coordinates of the vehicle from the GPS antenna located within the OBD device and/or the vehicle; and (3) transmitting the GPS coordinates of the vehicle to the server.
  • the location query may include (1) querying the GPS location of the user; (2) determining the GPS location of the user from GPS information determined by the GPS antenna located within the user's mobile device; and (3) transmitting the GPS coordinates of the user and/or vehicle to the server.
  • the server may receive the location of the vehicle.
  • the response may be sent by the valet/parking facility.
  • the server may query the location, and the OBD device may respond with the GPS coordinates of the OBD/vehicle.
  • the server may form a geofence, using a mileage radius.
  • the mileage radius may then be converted into a plurality of GPS coordinates on a map.
  • the mileage radius may be predetermined, or may be input by a user.
  • the system may transmit, from the server to the OBD device coupled to the vehicle, one or more geofence parameters.
  • the geofence parameters may include a permissible area within the geofence, an impermissible area outside the geofence, areas that are permissible or impermissible at specified times, or any other suitable parameters.
  • the system may transmit, from the server to the OBD device, an instruction to monitor the vehicle.
  • the monitoring may include monitoring the vehicle for one or more violations.
  • the violations may be geofence violations.
  • the OBD device may be further instructed to transmit an alert to the server when one or more of the geofence parameters are violated.
  • the system may receive one or more parameter restriction thresholds for a vehicle.
  • the parameters may include speed, acceleration, deceleration, geofencing, time of day, duration, or any other suitable parameter.
  • the threshold may be a threshold for a restriction, such as speed above 60 MPH is restricted.
  • the parameter restriction thresholds may include one or more values.
  • the values may be predetermined, or may be input by a user.
  • the user may input parameter restriction threshold values by (1) transmitting, to the server, a parameter; (2) transmitting, to the server, a restriction for the parameter, the restriction including a threshold value; and (3) transmitting an instruction to the OBD device to monitor the parameter to determine if the threshold level is exceeded or reached.
  • the system may receive an instruction from a user.
  • the user may input the instruction into an application or any other suitable medium, via a user interface.
  • the instruction may then be transmitted to a server.
  • the instruction may be an instruction to activate parameter restriction thresholds.
  • the activation of the restriction thresholds may be requested when the user utilizes a valet or parking facility.
  • the valet restriction function may cause the server to instruct the OBD device to monitor the vehicle for violation of one or more parameter restriction thresholds.
  • the system may transmit, from the server to the OBD device coupled to the vehicle, a speed query for the vehicle.
  • the speed query may request the speed of the vehicle at multiple points in time, to determine if the vehicle is speeding and has violated one or more parameter restriction thresholds.
  • the speed query may include a first point in time and a second point in time, and an instruction, from the server to the OBD device, to analyze speed information between the first point in time and the second point in time, to determine if the speed threshold has been exceeded or reached at any point between the two points in time.
  • the server may receive from the OBD device a determination.
  • the determination may include a speed determination if the speed threshold has or has not been exceeded or reached.
  • the OBD device may transmit a message to the server with information about the speed violation. If the OBD device determines that the speed threshold has not been exceeded or reached between the first point in time and the second point, the OBD may refrain from transmitting data about the speed threshold from the OBD device to the server. Alternatively, if a query is transmitted to the OBD to determine if the speed threshold has been violated, the OBD device may transmit a message that no violation has occurred.
  • the system may transmit an alert.
  • the alert may be transmitted from the user server to the user.
  • the alert may inform the user that the speed threshold has been exceeded or reached.
  • the system may (1) receive one or more parameter restriction thresholds for a vehicle; (2) receive an instruction from a user to enable a valet restriction function, the valet restriction function corresponding to monitoring the vehicle for violating one or more parameter restriction thresholds; (3) transmit, from the server to an OBD device coupled to the vehicle, an acceleration query for the vehicle, the acceleration query comprising a query to determine if the vehicle has violated the one or more parameter restriction thresholds, the acceleration query comprising: (4) a first point in time and a second point in time; and (5) an instruction to the OBD device to analyze the rate of speed acceleration between the first point in time and the second point in time to determine if the acceleration rate threshold has been exceeded or reached; and (6) receive, from the OBD device, the determination, wherein: (7) if the OBD determines that an acceleration rate threshold has been exceeded or reached between the first and second point in time, transmitting a message from the OBD to the server; and (8) if the OBD determines that an acceleration rate threshold has not been exceeded
  • the acceleration and/or deceleration may be calculated using one or more well-known algorithms or formulas for acceleration and/or deceleration.
  • a system for monitoring valet attendants and parking facility usage of a vehicle is provided.
  • the system may include an apparatus and method, and may provide monitoring of vehicle conditions when the vehicle is valeted.
  • the system may include receiving an instruction from a user.
  • the user instruction may request to initiate a specified mode, such as a valet monitoring mode.
  • the mode may include a vehicle retrieval mode, to be used in requesting retrieval of a vehicle.
  • the system may receive a request from the user.
  • the request may be a request to retrieve the vehicle.
  • the request may be received by a server.
  • the system may identify the valet or parking company associated with the of the vehicle.
  • the location may be the location of the vehicle at the time the user requests to retrieve the vehicle, or at the time the user initiates valet mode.
  • the valet or parking company may be determined by determining a GPS location.
  • the GPS location may be the GPS location of the vehicle, or the GPS location of the user's mobile device when the valet mode was activated.
  • the system may determine the entity associated with the location of the vehicle, and determine contact information for the entity.
  • the system may transmit, from the server to the entity, a request to retrieve the vehicle.
  • the request may include an instruction to the valet attendant to prepare the vehicle for pickup by the user.
  • the request may further include an instruction to the valet attendant to bring the vehicle to a specified location, such as GPS coordinates input by the user. For example, the user may instruct a valet to retrieve the vehicle from one location, and bring the vehicle to a completely separate location.
  • the system may receive, from the entity, an estimated time when the vehicle will be available for pickup, as well as the location where the vehicle be available for pickup.
  • the system may provide, to the user, status monitoring the vehicle.
  • the status monitoring may include GPS coordinates of the vehicle, ignition status of the vehicle, and movement of the vehicle. Movement of the vehicle may include whether the vehicle is in motion, whether it has been in motion within a recent period of time (i.e., the last 10 minutes), and real-time tracking of the vehicle movements.
  • a system for providing monitoring of vehicle conditions when the vehicle is valeted may also include a measurement device.
  • the measurement device may be removably connected to a vehicle.
  • the system may also include a computer.
  • the computer may include a connection to the measurement device.
  • the computer may be located within the vehicle.
  • the computer may be an onboard vehicle computer.
  • the system may further include a receiver.
  • the receiver may be configured to receive, from the user, a request to retrieve the vehicle.
  • the vehicle may be parked in a location managed by a valeting entity.
  • the system may further include a processor.
  • the processor may be configured to identify the entity responsible for the valeting location.
  • the processor may be configured to identify the entity based on GPS coordinates.
  • the entity may be identified from the GPS coordinates based on the system retrieving, using the GPS coordinates, a business at those coordinates. This may be accomplished using mapping software.
  • the GPS coordinates of the entity may be retrieved from the vehicle itself, from the GPS antenna within the OBD device, from the user's mobile device when the user activates the valet mode, or when the user manually enters the GPS location of the vehicle.
  • the system may further include a transmitter.
  • the transmitter may be configured to transmit, to the entity, an instruction to an attendant to retrieve the vehicle.
  • the transmitter may be further configured to transmit, to the entity, GPS coordinates for the vehicle.
  • the transmitter and receiver may be a transceiver.
  • the receiver may be further configured to receive, from the entity, an estimated time when the vehicle will be ready for pickup.
  • the transmitter may be further configured to transmit, to the user, the estimated location of the vehicle and the estimated time when the vehicle will be ready for pickup.
  • the system may further receive tracking information for the location of the vehicle in real-time, or at predetermined intervals.
  • the system may also receive a message form the entity that the vehicle is ready for pickup.
  • a system for providing monitoring of vehicle conditions may include: (1) a
  • the measurement device removably connected to a vehicle; (2) the measurement device comprising a connection with a computer, the computer located within the vehicle; (3) a receiver configured to receive, from the measurement device, measurement of data corresponding to an attribute of the vehicle; (5) a transmitter configured to transmit, to the measurement device, a threshold measurement corresponding to a desired data measurement level for the vehicle attribute; and (6) a processor located within the measurement device configured to: determine if the threshold measurement is exceeded or reached by the data measurement; and instruct a transmitter to transmit, to a user, an alert that the data measurement for the vehicle attribute has been exceeded or reached.
  • the system may perform the following steps: (1) receiving a vehicle attribute; (2) receiving a threshold range for the measurement of the vehicle attribute, the threshold range comprising an upper threshold measurement and a lower threshold measurement of the vehicle attribute; (3) receiving a measurement of the vehicle attribute; (4) if the vehicle attribute measurement exceeds the upper threshold measurement or falls below the lower threshold measurement, transmitting, to a user, an alert comprising: (5) the vehicle attribute; (6) the measurement of the vehicle attribute; and (7) information corresponding to the measurement of the vehicle attribute.
  • a system for setting and monitoring vehicle usage thresholds may include (1) a measurement device removably connected to a vehicle; (2) the measurement device comprising a connection with a computer, the computer located within the vehicle; (3) wherein upon connection of the measurement device to the computer, the measurement device receives vehicle information from the computer; (4) a user device configured to: (5) transmit one or more instructions to the measurement device; (6) receive information; and (7) display information; (8) a server comprising: a receiver configured to receive: (9) a plurality of thresholds, each of the plurality of thresholds corresponding to an allowable limit of a vehicle attribute; (10) data from the measurement device; and (1 1) instructions to monitor data received from the measurement device, the data corresponding to one or more vehicle attributes; (12) a transmitter configured to: (13) transmit the plurality of thresholds to the measurement device; (14) instruct the
  • measurement device to: (15) compare the data received from the vehicle computer to the threshold level; and (16) if the data exceeds the threshold level, transmit a message to the server of a threshold violation.
  • the transmitter may be further configured to transmit an alert of the threshold violation to the user.
  • certain information such as a threshold for an attribute, may be received from a user, via the user's mobile device, and transmitted to the server.
  • certain information such as another threshold for the same or different attribute, may be programmed into the server via software.
  • measurement of data corresponding to an attribute of the vehicle is provided.
  • the measurement may include (1) a threshold measurement corresponding to a desired data measurement level for the vehicle attribute; and (2) a processor configured to:
  • a system and method for infant monitoring of a vehicle using an OBD device may include one or more of the following steps: (1) receiving a selection from a user to enable infant monitoring mode; (2) receiving an alert from the OBD that the ignition has been switched off; (3) transmitting a message to the user comprising: (4) an alert that the ignition has been switched off; and (5) a query if the user has removed all children from the vehicle; (6) if the user does not respond to the query within a predetermined period of time, transmitting an instruction to the OBD to activate a microphone; (7) if the microphone does not indicate that any noise over a predetermined threshold is present, and there is still no response from the user, transmitting an instruction to activate a temperature sensor; (8) if the temperature sensor indicates a temperature reading above a predetermined threshold or below a predetermined threshold, transmitting an instruction to the OBD device to activate heat or air conditioning systems, and (9) contacting emergency first responders.
  • the system may further include transmitting location information to emergency first responders.
  • the system may receive an alert that the ignition is on, but the car is idle for an extended period of time.
  • the system may, in response, transmit a message to the user to determine if there is an unattended child in the vehicle. If there is no response, the system may activate some or all of the steps discussed.
  • the system may receive a response from the user to the query. In response to the query if the user has removed all children from the vehicle, the system may receive an affirmative response from the user. In that case, the alert sequence may end, and no further action, such as activating sensors or contacting emergency authorities, is necessitated.
  • the system may prioritize resources based on a determination of the urgency of each particular situation. For example, if there are two SBM alerts that require an emergency operator to contact the local PSAP, and only one operator is available, the system may prioritize one situation if the device temperature monitor detects rapidly rising or falling temperatures in one vehicle. This is just an example of one way to prioritize.
  • a prioritization system is essential for handling emergency situations. In another example, if one PSAP has the ability to receive information on emergencies via the internet or email, but another PSAP does not have that ability, the PSAP without online capabilities may be contacted first. It should be noted that the priority may be changed based on time, child age, and many other factors.
  • Carpool mode may provide the ability to coordinate and organize carpool trips.
  • the system may include providing a (for example, weekly) template schedule which is used by the system to produce a, for example, weekly schedule, which can be manipulated by the carpool participants.
  • the carpool participants may create a week-based template schedule for a week and this template creates the schedule for the current week.
  • the current week may be editable. Subsequent weeks may not be editable, because they have not yet been created based on the template schedule.
  • the template schedule is a week long, because carpool is usually a weekly function. For example, one family is responsible for Monday and Wednesday, and another family is responsible for Tuesday, Thursday, and Friday.
  • This concept of using a template to create a weekly schedule applies to any scheduling system, and the unit of time may change based on the particular activity. For example, the week may start on a specific day, which means that the template will refresh a weekly schedule on a specific day, or the week may be a rolling week, and will display 7 days from current day.
  • a carpool may provide a plurality of waypoints, with responsibilities assigned to one or more participants.
  • Provided is a system for managing coordination of waypoints and integration of carpool waypoints with other transportation systems.
  • the carpool system provides drivers the option to change the order or quantity of carpool stops on a web application, with the order of the waypoints saved as a template.
  • the existing template for the driver may be used for the order of stops for that driver. If no member of the driver's household is going to be a part of a specified carpool run, the household is deleted from the waypoint. If the address for a member of the carpool changes, the waypoint/address for that member changes.
  • the system may detect a change in the waypoint, even if the driver does not notify the system of changes based on the driver's route.
  • the notification may include sending a notification to users associated with a waypoint.
  • the notification may include
  • ETA Estimated Time of Arrival
  • An exemplary detection may include, determining that there are five waypoints and two routes to each waypoint. If, based on the driver's route, all eight routes that go to four of the waypoints are eliminated, the driver must be going to the fifth waypoint. If all 10 routes are eliminated, it is known that the dri ver is not going to any of the waypoints.
  • the system starts with the most likely or best route, using any suitable determination method, such as Waze or Google Maps data. The system may then create rectangular geofences ail the way from point A to point B.
  • the system may wait a certain amount of time, such as any suitable time period, such as two minutes, and then check the route from current location to point B, using mapping software, and determines a change in ETA. If the ETA has decreased down by the elapsed amount of time + a certain threshold, the user is still considered on the route.
  • a certain amount of time such as any suitable time period, such as two minutes
  • the driver is determined to be off the route.
  • the carpool system may be integrated with other modes of transportation. For example, if two passengers take the same train and live near one another, they can carpool to the train station. Integrating the carpool system with the monitoring of the location of the other transport vehicles, allows for the creation of a hub and spoke system.
  • GPS accuracy and arrival time can be utilized to project or coordinate transfers in hub and spoke system.
  • an alert is sent to other parents and/or the school.
  • the alert may be sent at a predetermined time threshold or distance threshold, such as when the deviation is greater than five minutes or more than 0.5 miles.
  • the alert may further include a statement that the carpool will be late to school, and may include a revised estimated time of arrival.
  • each of the above steps will comprise computer-implemented aspects, performed by one or more of the computer components described herein.
  • communications and calculations of thresholds may be performed electronically.
  • Determination of threshold violations, monitoring parameters, and communicating the threshold violations may be performed electronically.
  • all steps may be performed electronically - either by general or special purpose processors implemented in one or more computer systems such as those described herein.
  • Embodiments of the present system described herein are generally implemented as a special purpose or general-purpose computer including various computer hardware as discussed in greater detail below.
  • Embodiments within the scope of the present invention also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon.
  • Such computer-readable media can be any available media which can be accessed by a general purpose or special purpose computer, or downloadable through communication networks.
  • such computer-readable media can comprise physical storage media such as RAM, ROM, flash memory, EEPROM, CD-ROM, DVD, or other optical disk storage, magnetic disk storage or other magnetic storage devices, any type of removable non- volatile memories such as secure digital (SD), flash memory, memory stick etc., or any other medium which can be used to carry or store computer program code in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer, or a mobile device.
  • physical storage media such as RAM, ROM, flash memory, EEPROM, CD-ROM, DVD, or other optical disk storage, magnetic disk storage or other magnetic storage devices, any type of removable non- volatile memories such as secure digital (SD), flash memory, memory stick etc.
  • SD secure digital
  • Computer- executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device such as a mobile device processor to perform one specific function or a group of functions.
  • the invention may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, networked PCs, minicomputers, mainframe computers, and the like.
  • the invention is practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network.
  • program modules may be located in both local and remote memory storage devices.
  • An exemplary system for implementing the inventions includes a general purpose computing device in the form of a conventional computer, including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit.
  • the computer will typically include one or more magnetic hard disk drives (also called “data stores” or “data storage” or other names) for reading from and writing to.
  • the drives and their associated computer-readable media provide nonvolatile storage of computer-executable instructions, data structures, program modules, and other data for the computer.
  • exemplary environment described herein employs a magnetic hard disk, a removable magnetic disk, removable optical disks, other types of computer readable media for storing data can be used, including magnetic cassettes, flash memory cards, digital video disks (DVDs), Bernoulli cartridges, RAMs, ROMs, and the like.
  • Computer program code that implements most of the functionality described herein typically comprises one or more program modules may be stored on the hard disk or other storage medium.
  • This program code usually includes an operating system, one or more application programs, other program modules, and program data.
  • a user may enter commands and information into the computer through keyboard, pointing device, a script containing computer program code written in a scripting language or other input devices (not shown), such as a microphone, etc.
  • input devices are often connected to the processing unit through known electrical, optical, or wireless connections.
  • the main computer that effects many aspects of the inventions will typically operate in a networked environment using logical connections to one or more remote computers or data sources, which are described further below.
  • Remote computers may be another personal computer, a server, a router, a network PC, a mobile device, such as a smartphone, tablet or laptop, a peer device or other common network node, and typically include many or all of the elements described above relative to the main computer system in which the inventions are embodied.
  • the logical connections between computers include a local area network (LAN), a wide area network (WAN), and wireless LANs (WLAN) that are presented here by way of example and not limitation.
  • LAN local area network
  • WAN wide area network
  • WLAN wireless LANs
  • the main computer system implementing aspects of the invention is connected to the local network through a network interface or adapter.
  • the computer may include a modem, a wireless link, or other means for establishing communications over the wide area network, such as the Internet.
  • program modules depicted relative to the computer, or portions thereof may be stored in a remote memory storage device. It will be appreciated that the network connections described or shown are exemplary and other means of establishing communications over wide area networks or the Internet may be used.
  • Computers 100 communicate via network 110 with a server 130.
  • a plurality of sources of data 120-121 also communicate via network 110 with a server 130, processor 150, and/or other components operable to calculate and/or transmit information.
  • Server(s) 130 may be coupled to one or more storage devices 140, one or more processors 150, and software 160.
  • Server 130 may facilitate communication of data from a storage device 140 to and from processor(s) 150, and communications to computers 100.
  • Processor 150 may optionally include or communicate with local or networked storage (not shown) which may be used to store temporary or other information.
  • Software 160 can be installed locally at a computer 100, processor 150 and/or centrally supported for facilitating calculations and applications.
  • FIG. 2A illustrates a top view of an OBD device 205 that may be used in accordance with the invention.
  • OBD device 205 may include a plurality of electrical connectors, or pins 201. Pins 201 may be configured to communicate with an OBD port of a vehicle. OBD device 205 may be configured to receive diagnostic information from the vehicle's OBD system.
  • FIG. 2B illustrates a perspective top and side view of OBD device 205.
  • FIG. 2C illustrates a side view of the OBD device.
  • FIG. 3 A illustrates an exemplary process 301 for providing vehicle monitoring in accordance with principles of the invention.
  • an OBD device may be provided.
  • a vehicle attribute may be received via server.
  • the server may receive a measurement of the vehicle attribute from the OBD device.
  • a threshold range for the measurement of the vehicle attribute may be received by the server and/or OBD device.
  • an alert is transmitted to a user.
  • FIG. 3B illustrates exemplary process 313 for transmitting alerts in accordance with the principles of the invention.
  • Process 313 provides the information that is transmitted in an alert.
  • the alert may contain vehicle attribute 315, measurement of the vehicle attribute 317, and information corresponding to the measurement of the vehicle attribute 319.
  • FIG. 4A illustrates exemplary process 401 for activating a threshold monitoring and alert system in accordance with the principles of the invention.
  • the system may receive an instruction from a user to enable a restriction function. The instruction may be received via a server.
  • the system may receive, via the server, one or more vehicle attributes.
  • the system may receive, via the server, an instruction to monitor one or more of the vehicle attributes.
  • the system may transmit the instruction from the server to an OBD device.
  • the system may receive one or more acceptable threshold levels for the vehicle attributes via the server.
  • the system may receive one or more unacceptable threshold levels for the vehicle attributes via the server.
  • FIG. 4B illustrates exemplary process 415 for receiving alerts from the OBD device in accordance with principles of the invention.
  • the OBD device may monitor the vehicle computer for one or more vehicle attributes. The vehicle attributes may be programmed into the OBD device.
  • the OBD device may determine if the vehicle attribute threshold levels are unacceptable, such as if a threshold level has been exceeded.
  • the OBD device may transmit a message to the server if the threshold levels are reached or are unacceptable.
  • the an alert about the threshold level may be transmitted from the server to a user device.
  • FIG. 5 shows illustrative display 501 in accordance with the invention.
  • Display 501 may be an alert displayed to a user in response to a threshold violation.
  • 503 shows an area violation, such as a geofence violation, has occurred, within the setting 'Family Mode.' The user has the option to select the violation and view on map 505.
  • 507 is a background display showing other violations.
  • FIG. 6 shows illustrative information 601 monitored by the OBD device.
  • 601 is a user display.
  • 603 shows that the information is fuel consumption since the last refuel
  • 605 is the user score provided for driving since last refuel.
  • 605 shows ' 100' as a perfect score for driving, based on an algorithm.
  • the details of the driving for calculating the score are show in in 607, 609, 611, and 613.
  • FIG. 7 shows illustrative settings display 701 in accordance with the invention.
  • the user has enabled various features, which may be toggled on or off. Enabling of these features allows the user to receive alerts.
  • the user has enabled diagnostics 703, maintenance notifications 705, low battery alerts 707, tow alerts 709, and low fuel level 711. Thus, when any of these thresholds or scenarios are triggered, the user may receive notifications or alerts.
  • FIG. 8 shows illustrative dashboard 801 in accordance with the invention. Shown is fuel level 811, battery level 809, and speed 807. This information may be provided in real time. That is, an administrator of a vehicle and/or OBD device may monitor the speed and other levels of the vehicle at any given time. Also provided is car find 813, which, when selected, shows the location of the vehicle. Alert selector 815 displays one or more notifications and alerts, while trip info 817 displays different information about a trip. Customer service selector 819 allows a user to contact customer service within the application, and transmits information about the user's vehicle with the call. Safe Teen 803 and Safe Family 805 are two modes that are toggled on, with monitoring of various thresholds enabled.
  • FIG. 9 is the result when car finder 813 is selected, showing map 901. 905 is the location of the vehicle with the OBD device, 903 is additional map information, and 907 includes particulars such as date and time.
  • FIG. 10 shows additional alerts in accordance with the invention.
  • FIG. 11 displays alert 1101, with information 1103 including detailed information about the violation, such as the speed detected.
  • FIG. 12 displays another exemplary alert 1201, including particular information about the threshold violation detection in display 1203. It should be noted that the approximate violation may be calculated in advance. Thus, in this case, traffic patterns may dictate that, though a user has left ten minutes before an appointment, using traffic data, it may be estimated that the user will arrive three minutes late.
  • steps of various processes may be shown and described as being in a preferred sequence or temporal order, the steps of any such processes are not limited to being carried out in any particular sequence or order, absent a specific indication of such to achieve a particular intended result. In most cases, the steps of such processes may be carried out in a variety of different sequences and orders, while still falling within the scope of the present inventions. In addition, some steps may be carried out simultaneously.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Automation & Control Theory (AREA)
  • Mechanical Engineering (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Atmospheric Sciences (AREA)
  • Chemical & Material Sciences (AREA)
  • Transportation (AREA)
  • Combustion & Propulsion (AREA)
  • Analytical Chemistry (AREA)
  • Traffic Control Systems (AREA)
  • Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)
  • Burglar Alarm Systems (AREA)
  • Emergency Alarm Devices (AREA)

Abstract

L'invention concerne un système permettant de surveiller des conditions de véhicule. Le système peut comprendre un dispositif de mesure. Le dispositif de mesure peut être relié de façon amovible à un véhicule. Le système peut comprendre un ordinateur. L'ordinateur peut être situé dans le véhicule. Le dispositif de mesure peut comprendre une connexion avec l'ordinateur. Le système peut comprendre un récepteur. Le récepteur peut être conçu pour recevoir, en provenance du dispositif de mesure : des mesures de données correspondant à un attribut du véhicule, et une mesure seuil correspondant à un niveau de mesure de données souhaité pour l'attribut de véhicule. Le système peut comprendre un processeur. Le processeur peut être conçu pour déterminer si la mesure seuil est dépassée par la mesure de données, et donner l'instruction à un émetteur de transmettre, à un utilisateur, une alerte indiquant que la mesure de données pour l'attribut de véhicule a été dépassée.
EP15765431.0A 2014-03-19 2015-03-19 Système de services automobiles Withdrawn EP3119645A4 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201461955469P 2014-03-19 2014-03-19
US201562107091P 2015-01-23 2015-01-23
US201562108335P 2015-01-27 2015-01-27
PCT/US2015/021463 WO2015143153A1 (fr) 2014-03-19 2015-03-19 Système de services automobiles

Publications (2)

Publication Number Publication Date
EP3119645A1 true EP3119645A1 (fr) 2017-01-25
EP3119645A4 EP3119645A4 (fr) 2018-01-17

Family

ID=54145312

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15765431.0A Withdrawn EP3119645A4 (fr) 2014-03-19 2015-03-19 Système de services automobiles

Country Status (6)

Country Link
EP (1) EP3119645A4 (fr)
JP (1) JP2017512712A (fr)
KR (1) KR20160135264A (fr)
AU (1) AU2015231207A1 (fr)
CA (1) CA2941873A1 (fr)
WO (1) WO2015143153A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102015121113A1 (de) * 2015-12-04 2017-06-08 Valeo Schalter Und Sensoren Gmbh Verfahren zum autonomen Einparken eines Kraftfahrzeugs mit Innenraumsüberwachung, Fahrerassistenzsystem sowie Kraftfahrzeug
CN105704660A (zh) * 2016-01-06 2016-06-22 上海德科电子仪表有限公司 一种车联网终端
EP3445602A4 (fr) * 2016-04-19 2020-06-10 Magtec Products, Inc. Système et procédé de commande de papillon
JP2019127132A (ja) * 2018-01-24 2019-08-01 株式会社Ｓｕｂａｒｕ 駐車装置
KR102246932B1 (ko) * 2019-10-22 2021-04-30 주식회사 쓰리세컨즈 모터스포츠 주행 데이터 분석 서버 및 처리 시스템
KR102111010B1 (ko) * 2019-11-21 2020-05-14 주식회사 크래블 Obd 단말 기반 농기계 고장 진단 시스템
US20210293969A1 (en) * 2020-03-17 2021-09-23 Anirudha Surabhi Venkata Jagannadha Rao System and method for measuring event parameters to detect anomalies in real-time
CN111988374A (zh) * 2020-08-03 2020-11-24 支付宝(杭州)信息技术有限公司 一种通知车主挪车的方法及系统
US12067816B2 (en) 2021-10-25 2024-08-20 Woven By Toyota, Inc. Method and system for providing driving information to non-driver user

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2001235001A1 (en) * 2000-02-11 2001-08-20 Richard A. Geving Device and method for transmitting vehicle position
US6924750B2 (en) * 2000-05-17 2005-08-02 Omega Patents, L.L.C. Vehicle tracking unit for controlling operable vehicle devices using a vehicle data bus and related methods
US7346439B2 (en) * 2002-11-07 2008-03-18 International Business Machines Corporation Location-based intelligent remote vehicle function control
US9014160B2 (en) * 2006-05-16 2015-04-21 Autoner Mobile, Inc. Method for providing a valet mode in a vehicle
WO2008019339A2 (fr) * 2006-08-04 2008-02-14 Micah Paul Anderson Système de sécurité et procédé utilisant une technologie de téléphone mobile
AT507032B1 (de) * 2008-06-05 2011-07-15 Efkon Ag Verfahren und system zur erstellung von kraftfahrzeug-ferndiagnosen
KR101333128B1 (ko) * 2012-04-18 2013-11-26 주식회사 티모넷 앱의 백그라운드 실행 기능을 이용한 usim정보 변경내역 안내 시스템
US8768565B2 (en) * 2012-05-23 2014-07-01 Enterprise Holdings, Inc. Rental/car-share vehicle access and management system and method
CN102795175B (zh) * 2012-09-01 2014-08-06 北京车网互联科技有限公司 一种车灯开闭提醒方法及系统

Also Published As

Publication number Publication date
JP2017512712A (ja) 2017-05-25
AU2015231207A1 (en) 2016-09-22
KR20160135264A (ko) 2016-11-25
CA2941873A1 (fr) 2015-09-24
WO2015143153A9 (fr) 2016-10-20
EP3119645A4 (fr) 2018-01-17
WO2015143153A1 (fr) 2015-09-24

Similar Documents

Publication Publication Date Title
US20170039784A1 (en) Automobile diagnostic device using dynamic telematic data parsing
WO2015143153A1 (fr) Système de services automobiles
US11161519B2 (en) Method and system for impaired driving detection, monitoring and accident prevention with driving habits
US10394253B1 (en) Caravan management
US11132849B1 (en) Vehicle telematics and account management
US10375174B2 (en) Cloud integrated vehicle platform
US8924240B2 (en) System for monitoring vehicle and operator behavior
US10567935B1 (en) Connected services configuration for connecting a mobile device to applications to perform tasks
US10507845B2 (en) Method and apparatus for changing vehicle behavior based on current vehicle location and zone definitions created by a remote user
US8212691B2 (en) Controlling location-based services using a portable privacy key
US8390474B2 (en) Method for collecting data and system for accomplishing the same
US8532921B1 (en) Systems and methods for determining available providers
US20110196571A1 (en) System And Method For The Collection And Monitoring Of Vehicle Data
US8880133B2 (en) Vehicle communication device
CN103093586B (zh) 车辆状态上报和监控方法，车载终端和服务中心
CN110857073B (zh) 提供遗忘通知的系统和方法
US9349290B2 (en) Self-reported tracking methods including a trip plan with an expected duration or expected return
WO2013130201A1 (fr) Systèmes et procédés pour communiquer avec un utilisateur de véhicule
US20180285846A1 (en) System and method for parking violation risk management
CN108875986A (zh) 用于车辆预订可靠性预测的系统和方法
JP2009193141A (ja) 車両セキュリティシステム
US11623655B1 (en) Systems and methods for restricting the use of a vehicle operator's electronic device
CN117912188A (zh) 车内孩童安全监测与紧急响应方法与装置

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20160913

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20171220

RIC1 Information provided on ipc code assigned before grant

Ipc: B60R 16/02 20060101ALI20171214BHEP

Ipc: G08G 1/123 20060101ALI20171214BHEP

Ipc: G08G 1/00 20060101ALI20171214BHEP

Ipc: G07C 5/00 20060101AFI20171214BHEP

Ipc: G08G 1/01 20060101ALI20171214BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20180719