Digital music consumption (e.g., the acquisition of selected audio tracks for personal listening enjoyment) continues to increase with advances in digital music products such as on-line music services and devices for digital music storage and playback. In particular, portable media players and personal digital assistants such as the iPod available from Apple, Inc. and personal communication devices (e.g., mobile terminals or cellular telephones) such as the iPhone also available from Apple Inc., which have additional applications such as music download and playback applications, are becoming increasingly popular.
Existing download sources are not as comprehensive as, for example, the music library of a satellite digital audio radio service (SDARS) such as, for example, that of Sirius XM Radio Inc. For example, some download sources only provide users access to recordings of one or more particular recording companies. Furthermore, one of the primary drivers for consumption of new music and other media is exposure to new content through spontaneous programmed broadcast content such as FM radio, television, and satellite radio. In particular, exposure to a rich variety of content provided by a broadcast programmer can be a powerful motivator to gain interest in, investigate and ultimately acquire new music and other media.
The Docking Unit Application, referenced above, addresses just such a need by describing various embodiments of a novel and simple device that can interface digital media players such as the iPod, iPhone, smartphones, tablets, Android based machines, and the like with a SDARS or similar programming service. As disclosed in the Docking Unit Application, this can optimally be accomplished in a vehicle using an existing vehicle FM radio system. The Docking Unit Application also discloses an application program that can be downloaded to a digital media player, personal electronic device or smartphone to facilitate the selection, storage and playback, and optionally, the acquisition, of content from a SDARS or similar programming service, using the digital device's user interface.
Telematics generally refers to solutions that are based on information flowing to and/or from a vehicle. For example, vehicle telematics can refer to automobile systems that combine Global Positioning System (GPS) tracking and other wireless communications for automatic roadside assistance and remote diagnostics. When implemented, telematics have the potential to increase operational efficiency and improve driver safety in a number of ways. For example, GPS technology can be used to track a vehicle's location, mileage, and speed. Communications technology promotes connectivity between drivers and other parties such as service dispatchers (e.g., public safety answering point or PSAP, traffic data aggregator, commercial telematics service providers or call centers such as Onstar Corporation, and the like). Sensors monitor vehicle operations and conditions which can then be used to streamline vehicle maintenance, or facilitate seeking assistance for the vehicle occupants. For example, accelerometers measure changes in speed and direction, and cameras can monitor road conditions, and drivers' actions.
In addition to interfacing media players with a vehicle's SDARS receiver and head unit, there also exists a need in-vehicle for interfacing various telematics functionalities with existing in-vehicle resources, such as, for example, an SDARS head unit, a communications device or interface, such as an in-vehicle modem or cellular telephone, or, for example, a smart phone, tablet or other portable device with the ability to store and run various telematics applications or telematics control applications such as emergency assistance, and traffic monitoring, data aggregation and reporting.
In exemplary embodiments of the present invention, a portable sensing and telematics device can sense one or more conditions with respect to a vehicle and/or its occupant(s), and can communicate information about, or in response to, the sensed condition to a remote entity, such as emergency responders, law enforcement agencies, or various monitoring services and systems that track or monitor vehicle occupants or their activities. For example, the portable sensing and telematics device can be connected to, or integrated in, a cigarette lighter adapter (CLA) configured to be connected to a vehicle cigarette lighter socket or auxiliary power socket. The CLA can convert DC power from the vehicle to supply its components as well as other device(s) connected to the CLA. The portable sensing and telematics device can be connected to a tethered smartphone or other personal electronic device, can interface with an in-vehicle modem or cellular phone, or can itself incorporate smartphone or similar functionalities within it. Other small footprint form factors are possible. An exemplary device can be used in a wide variety of emergency sensing and response applications, as well as various monitoring applications and scenarios.
The above and other aspects, features, and advantages of certain embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:
It is noted that throughout the figures, the same drawing reference numerals will be understood to refer to the same elements, features, and structures;
Next described are various exemplary portable telematics systems and devices that can be provided in a vehicle. Some of these exemplary devices are based on the CLA device described in the Docking Unit Application, others can have different form factors, but similar low footprint in-vehicle access. Exemplary systems can stand alone, or, for example, can interoperate with a smartphone, and/or be integrated with an existing SDARS receiver and head unit already in the vehicle.
Thus, in exemplary embodiments of the present invention, a low footprint portable telematics device can be provided in a vehicle. Such a device can provide easy access to a user with no or minimal disruption of his or her field of view or range of motion within the vehicle cabin. The device can include, for example, (i) one or more sensors for detecting one or more conditions of a vehicle and/or its occupant(s), and (ii) a communications interface for communicating with a remote monitoring system and/or responder in response to any detected condition(s). For example, such a portable device can be provided in a Cigarette Lighter Adaptor (CLA), as described in the Docking Unit Application, and can be coupled with a smartphone or other suitable mobile terminal so as to enable crash detection. Exemplary mobile terminals can include, for example, an iPad™, iPhone, Android based device, smartphone, tablet, etc. The CLA can comprise a crash detection accelerometer or other sensors, and can include either a wired connection USB charger or, for example, a wireless link, such as, for example, Bluetooth™ (“BT”) 802.11, or the like, to the smartphone or other mobile terminal. Upon sensing a crash, an exemplary software application running on the mobile terminal can initiate a request for emergency help through a telematics response service. In various exemplary embodiments of the present invention, either the CLA, smartphone or other in-vehicle device can provide position sensing, and the smartphone or other coupled device can, for example, (i) transmit the vehicle's location, and (ii) initiate a conversation between a response service and the vehicle's occupants.
It is highly noteworthy that in exemplary embodiments of the present invention at least one accelerometer is provided in the portable telematics device. The accelerometer, preferably an XYZ or 3-axis accelerometer, can be used for crash and other significant event detection. Three axis is preferred because the orientation of the accelerometer will change from car to car as the cigarette lighter sockets are mounted differently. Containing the accelerometer within the CLA increases the reliability of the crash detection, as opposed to trying to leverage an accelerometer provided in a tethered smartphone. In exemplary embodiments of the present invention the accelerometer in the CLA can be a 3-axis (XYZ) accelerometer capable of measuring G forces up to a range of, for example, 15 G or higher, or in other exemplary embodiments, up to 25 G or higher, to insure that the accelerometer reading does not clip during a crash. This is required in order to obtain an accurate delta velocity (ΔV) reading. In addition, when the accelerometer is mounted securely in a Cigarette Lighter socket, the accelerometer can more accurately capture G forces transmitted through the body of the vehicle. In general a smartphone is not guaranteed to be secured to the vehicle, and thus cannot be relied upon to accurately capture the G forces transmitted through the body of the vehicle. Another option, for example, is to use a 2-axis (XY) accelerometer capable of measuring G forces in the range of 15 G or higher, or in the range of 25 G or higher, which is aligned or calibrated based on the installation orientation to measure lateral forces on the vehicle. The calibration is an extra step but it allows the use of a 2-axis accelerometer.
Thus, with reference to
Continuing with reference to
Portable device 110 can further include a cell phone module or the like with which to perform telematics communications functions such as (i) initiating a call to a responder, (ii) remote monitoring in response to a detected condition of the vehicle and/or occupant(s), and (iii) session management. It is understood that other wireless communications protocols and links can be employed, of various available types, and that an exemplary telematics responder service can be IP based. Further, portable device 110 can include, for example, a Bluetooth™ or other wireless link 120 for communicating with smartphone 130 or interfacing with a vehicle head unit and speaker system to allow for hands-free operation. Thus, device 110 can be configured, for example, as a portable CLA that can wirelessly communicate with different types of smartphones, portable computers, personal data assistants, thereby essentially providing a universal interface. Finally, smartphone 130 can have a resident telematics/crash sensor application, which takes sensor inputs from CLA device 110, sent across one or both of wireless link 120 or direct link 115, and processes them to take various telematics actions.
With reference to
Additionally, portable device 220 can be physically wired to mobile terminal 250 via a USB cable 240. Such a cable can also be used for charging mobile terminal 250, as described above. Additionally, for example, another serial link can be provided.
Mobile terminal 250 can be wirelessly coupled to automotive infotainment head unit 270, or for example, it could be hard wired to it via a docking mechanism, as is known. Preferably, so as not to require a user to bother with a docking unit for, for example, a smartphone, the link can be Bluetooth hands-free profile (“HFP”), for example, used to transmit telephone and telematics audio to the vehicle speakers and from a vehicle built-in microphone. Additionally, there can be another Bluetooth link between mobile terminal 250 and automotive infotainment head unit 270, this one to transfer entertainment audio, such as for example, IP and MP3 data, this second Bluetooth link being A2DP. As is known, multiple Bluetooth links using different protocols can be simultaneously established.
Finally,
It is noted that
Given the examples of
In exemplary embodiments of the present invention, speakerphone Bluetooth™ link 260 can be arranged to have priority over content being played back via the vehicle speaker system. It is to be understood, however, that portable device 220 can, in various exemplary embodiments, operate independently of vehicle head unit 270. As noted above, portable device 220 can, for example, be arranged to convert vehicle power so as both to power its components and provide power to other devices. This can be done, for example, via USB charging link 240.
In exemplary embodiments of the present invention, portable device 220 can be configured to sense conditions such as, for example, speed, distance, range from a selected location, use of texting via, or call operations on, a connected smartphone, vehicle crash conditions, and daylight or time conditions, amongst others. Speed can be sensed, for example, using an accelerometer to translate acceleration and deceleration forces in to a change in velocity of the vehicle, as is known in the art. This can be done, for example, using a 3-axis accelerometer in device 220, with a range of 15 G or higher, or, alternatively with a range of 25 G or higher, so as to insure that the accelerometer reading does not clip during a crash. Making sure that the accelerometer reading does not clip during a crash is critical to obtaining an accurate ΔV reading. Alternatively, as noted above, a XY accelerometer capable of measuring G forces in the range of 15 G or higher, or alternatively in the range of 25 G or higher, and which is aligned or calibrated based on the installation orientation to measure lateral forces on the vehicle, can be used. The calibration is an extra step but it allows the use of a 2-axis accelerometer.
In exemplary embodiments of the present invention, in addition to providing emergency response to a detected crash via telematics, an exemplary portable device can be used for various other purposes, such as, for example, monitoring. Such monitoring can include, for example, (i) monitoring drivers on probation due to criminal or traffic violations, (ii) monitoring drivers having restricted licenses due to age, inexperience or disability, and (iii) monitoring of driver behaviors such as drifting or erratic speeds due to inattentiveness (e.g., driver is falling asleep at the wheel, is distracted by texting or other communications activity, etc.).
Thus, in exemplary embodiments of the present invention, an exemplary portable telematics device, with or without a smartphone, can institute two-way communications with a monitoring center or responder. In addition, it can, for example, collect data for use by one or more monitoring entities, such as, for example, a driver's legal guardian, law enforcement, insurance companies, automobile manufacturers, etc.
In exemplary embodiments of the present invention, processor 306 can also send and receive both instructions and data to device interface 312, which can be, for example, a serial bus, a parallel bus, USB™, Firewire™, etc., that can, for example, communicate via known protocols to internal and external devices. Device interface 312 can be configured to send and receive information from mobile terminal 302. For example, processor 306 can transmit a GPS based vehicle location to mobile terminal 302 for security purposes.
Exemplary CLA 300 can also communicate with other wireless communication services (e.g., 3GPP, 802.11(n) wireless networks, Bluetooth™, etc.) via transceiver 307. For example, transceiver 307 can communicate with mobile terminal 302 via an ad-hoc Bluetooth™ network. Alternatively, for example, transceiver 307 can be connected to device interface 312. As noted above, processor 306 can employ a TCU application to operate in conjunction with transceiver 307, GPS receiver 314, Sensors 316 as well as other devices to implement various telematics and telematics related processes, as described herein.
In exemplary embodiments of the present invention, CLA 300 can optionally include a SDARS or other programming receiver 320 to receive either an SDARS broadcast stream or other content stream(s). Such received content streams can then be frequency modulated and retransmitted via FM transmitter 322 to head unit 304, as described above, or provided via a Bluetooth™ link or other interface. CLA 300 can also include DC converter 324 for receiving a DC voltage from vehicle power 326 and convert the received DC to a suitable DC voltage for use by CLA 300, as well as mobile terminal 302 or other devices. As described above, FM transmitter 322 can provide an FM audio stream to head unit 304 via the DC power line associated with vehicle power 326. Finally, CLA 300 can be provided with a microphone 318, via which a user can issue voice commands as well as communicate through the various provided communications links, e.g., cellular.
In the example of
As noted, device 300 can have its own three button user interface, with, for example, buttons for each of (i) phone—to make regular telephone calls through the automobile's speakers, (ii) agent—to contact a telematics service provider agent, and (iii) emergency—for contacting 911 or similar emergency responder dispatchers. It is noted that the buttons that correspond to emergency dialing, agent assistance, and hands-free functionality are preferably operational, even when the vehicle's ignition is off.
In addition, in some exemplary embodiments, a portable device can have an embedded or connected speaker, and a volume control, to facilitate interaction with the cellular modem, as shown in stand alone portable device embodiments such as that illustrated in
A primary use for an exemplary portable telematics device can be crash notification and emergency dialing, so the overall design of the device and the associated cables can, for example, be optimized for this use case. A HMI (Human Machine Interface) for the product can be simple, consisting of as few buttons as possible to achieve necessary functionality, as described above in connection with
Use Cases
Next described are various use cases illustrating the utility as well as versatility of a portable telematics device, in one or more of the exemplary embodiments described above. The use cases address functionalities available even on a stand alone portable device, such as that depicted in
Use Case 1—Automatic Crash Notification
When a vehicle encounters a collision, sensors and electronics in the CLA can, for example, detect the incident and automatically gather information (e.g., device identification number, covered vehicle GPS coordinates, call type, and other available data) from the CLA or vehicle bus and output this information, via an embedded cellular connection to an Emergency Response Center. An Emergency Response Center agent can then validate the subscriber's status, merge this information with other subscriber and vehicle data, and attempt to open a dialog with the vehicle to determine casualty condition and contact an appropriate emergency responder, such as the relevant Public Safety Answering Point (“PSAP”), for appropriate deployment of emergency service. If the Emergency Response Center agent is unable to establish verbal communication with the vehicle occupant(s), the agent can then deploy emergency services to the vehicle based upon the last known GPS coordinates. When contacting the PSAP, police or another emergency response provider, the Emergency Response Center agent can, for example, provide them with the covered vehicle and/or subscriber information (e.g., vehicle position, direction, color, cellular phone number), to the extent provided by the Crusader1 and the telematics service database. Should the vehicle lose power during the crash, a rechargeable back-up battery can ensure that all available data is sent to the agent. Such a backup battery can be, for example, a 3 Volt small footprint battery.
Use Case 2—Emergency Dialing/Crisis Assist
When a driver encounters an emergency and presses an emergency button on the portable device, an agent can be available to assist with (i) collecting any critical information related to the emergency and (ii) contacting the correct emergency service provider based upon the vehicle's location. The agent can remain on the line until the driver and vehicle receive assistance. In the event that the driver has witnessed an emergency, the incident can be reported to the agent, and the agent can relay the information to the appropriate authorities for assistance.
When a user presses the emergency button on the portable device, it can, for example, connect to an Emergency Response Center. The device can automatically gather information (e.g. device identification number, covered vehicle GPS coordinates, call type and other available data) from the vehicle bus and output this information via an embedded cellular connection through a telematics service database to the Emergency Response Center. Details on emergency response centers are provided in the PCT/US2012/068318 application which was cited above and incorporated herein by reference. An Emergency Response Center agent can validate the subscriber's status, merge this information with other subscriber data, and attempt to speak to the driver to understand the emergency situation. If the agent cannot speak with the driver, the agent can ask the occupant(s) to honk the horn, tap the steering wheel or console, or generally “make some type of noise” so that the agent knows that the occupants(s) are in the vehicle. If the foregoing attempts are unsuccessful in establishing some type of contact with the vehicle occupant(s) then the following procedure can, for example, be used: (i) If the location of the vehicle was received, the agent will pass an “unconfirmed” emergency to the PSAP; and (ii) If the location of the vehicle was not received, the agent will stay on the line with the vehicle for additional time and continue to query for some type of response and if unsuccessful will disconnect the call and note the service request accordingly.
Additionally, the portable device and/or tethered smartphone can be connected to a medical condition sensor, or other occupant condition sensor, to receive an output from the occupant condition sensor when a selected parameter falls outside a designated range or above or below a designated value, such as is defined using the subscriber portal, for example, and automatically initiate communication with a response provider.
As noted above, when contacting a PSAP, police or another emergency response provider, the Emergency Response Center agent can provide them with the covered vehicle and/or subscriber information (e.g., vehicle position, direction, registration plate and color, cellular phone number), to the extent provided by the portable telematics device (e.g., device 110 or 220 in
Use Case 3—Roadside Assistance
Roadside assistance can, for example, include events such as a flat tire, dead battery, keys locked in the vehicle, no fuel, and tow truck assistance. When a user presses the Agent button on the keypad of the portable device, an operator can be available to direct assistance to the vehicle's location. In addition, the Agent can provide information regarding the location of nearest service facility, and can, for example, even contact that facility to schedule an appointment.
In exemplary embodiments of the present invention, a roadside assistance feature can also be enabled when a user engages the roadside assistance service via the vehicle's voice menu feature, or remotely through a cell phone or smart phone app. This call can be taken by an Interactive Voice Response (IVR) system that can, for example, route the call to a roadside assistance company. The subscriber can request assistance to connect to the appropriate authority for advice and/or to request assistance or repair service. At the subscriber's request, a roadside assistance provider can connect the user to a client-authorized service center. The telematics service database will provide all necessary data (e.g., device identification number, covered vehicle GPS coordinates, call type and other available data) from the portable device to the roadside assistance company.
Use Case 4—Smart Phone Notifications
In exemplary embodiments of the present invention, the following alerts/notifications can, for example, be sent from a portable device to a mobile telephone:
Crash Alert—this notification can be automatically generated when a vehicle sensors register that a crash has occurred. This notification can be posted to a Subscriber Portal And Mobile Application in addition to a Public Safety Answering Point (“PSAP”) (the functioning of a PSAP and the interaction of a telematics device with a PSAP are described in detail in PCT/US2012/068318. Communication to the subscriber of this vehicle condition can be, for example, via text, SMS message, or email, as may be determined by the subscriber preference input via the Subscriber Portal. This alert can, for example, be sent to up to five destinations that have been pre-determined by the vehicle owner.
Remote Alarm Notification—once enabled by a subscriber, a client authorized service center can support an alarm notification feature which causes a notification to be sent to the vehicle owner communicating that their covered vehicle's alarm system has been triggered. This notification can be posted to the Subscriber Portal and Mobile Application. Communication to the subscriber of this vehicle condition can be via text, SMS message, or email, as determined by the subscriber preference input via the Subscriber Portal. This alert can be sent up to five destinations that have been pre-determined by the vehicle owner.
Speed Alert—this service allows a subscriber to monitor a covered vehicle when it exceeds speed limits set by a subscriber. Subscribers can, for example, specify speed limits via the mobile application or the subscriber portal. This limit can be transmitted to the portable device, which can than monitor the vehicle's speed, via, for example, information from one or more of the vehicle bus or integrated sensor. When the vehicle's speed exceeds the set limit for more than a defined time interval, for example 10 seconds, the portable device can send a message to the client authorized service center, which can then notify the subscriber via the subscriber's preferred communication link. The subscriber can also set preferences via the Subscriber Portal so that the vehicle displays a speed alert notification to the driver.
Geo-fencing—This service that allows a subscriber to set geographic parameters for a covered vehicles usage, such as, for example, a designated geographic area or co-ordinates defining one or more geographic areas. If the vehicle is driven outside those constraints, and remains outside of those constraints for a period of a defined time interval, say, for example, more than 60 seconds, the subscriber can be notified. In exemplary embodiments of the present invention, subscribers can activate this feature, and specify the geographic driving range limit, via the Subscriber Portal or Mobile Application. These limits can, for example, be transmitted to the portable device, which can than monitor the vehicle's location. When the vehicle is operated inside an exclusion (non-permitted) zone or outside an inclusion (permitted) zone, a message can be sent to the operations center which will notify the subscriber of the violation via the subscriber's designated communication link. The subscriber can also set a preference to turn on or off a geo-fencing notification alarm or pop up to be received in the vehicle.
Valet Alert—Valet Alert is a subset of the geo-fencing service, where geo-fencing can be armed quickly by a driver, so that an alert can be generated if the covered vehicle is moved outside of a short distance from its present location once armed. This is useful when parking a car via a valet service at an event, affair or restaurant, for example, so as to ensure that the parking attendants do not “joy ride” with the vehicle. The range of distance before an alert is triggered can be dependent upon the condition preferences set at the Subscriber Portal or Mobile Application. If a vehicle is driven outside the set area, a subscriber can be notified, for example, via email and/or SMS.
Tow Alert—this notification can be triggered if the vehicle sensors register vehicle tilt. To register a vehicle lift event, the portable device can use an XYZ accelerometer, for example, to detect a change in orientation of the plane of the vehicle. For example, a threshold can be set for, for example, a 3 degree lift angle, and any angular change in orientation meeting or exceeding that threshold is interpreted as a vehicle lift.
Impact while Parked Alert—If the vehicle is parked and an impact occurs, the portable device's sensor can automatically send data to notify an agent of the occurrence. In addition, a crash alert notification can be sent to the destinations set by the subscriber via the Subscriber Portal or Mobile Application/recipients.
Low Battery Alert—as noted above, a re-chargeable back-up battery can be included in the portable device so that an emergency call can be made if the vehicle loses power during a collision. When the re-chargeable back-up battery in the device is running low and requires replacement, an indication can be communicated via the subscriber portal and mobile application. In addition, the portable device can give an audible and visible indication. Once this notification is received, the end user can receive information regarding battery replacement via the mobile application, subscriber portal, or directly from an agent.
Use Case 5—Hands-Free Calling
In exemplary embodiments of the present invention, Bluetooth capability built in to the portable device can allow a driver to pair his mobile device so that at the touch of the Phone Button, communication can occur via a speaker provided on the portable device. To use this feature a user would initiate the call from his mobile device. A volume control dial on the portable device allows a user to adjust the volume level during a call.
In exemplary embodiments of the present invention, a portable device's Bluetooth system can accept pairing from up to five mobile devices that also have Bluetooth capability. Only one paired device can be connected at a time. If multiple paired mobile devices are within range, the portable device can, for example, connect to devices in the order that they were paired. To pair a device, a user can press and hold the phone button on the device for a given number of seconds, for example. The phone button can, for example, flash blue or give some other indication. Following the prompts on the mobile device, a PIN and a device can be entered. Once the connection is made, the phone button will no longer flash, but can, for example, remain solid blue. An audible alert can also signal that successful paring has occurred. This process can be repeated to pair additional devices. If a connection is desired with another paired device, the phone button can again be pressed and held for a defined time interval for the next device in queue to be connected.
Alternatively, the portable device can support voice-activated hands-free calling with a prepaid minutes' package. For this option, a user must purchase minutes, which can be done directly from the vehicle by pressing the Agent button or by pressing the Phone button. If the latter option is used, a series of voice prompts can, for example, guide the user through purchasing minutes. In one example, in the event that minutes are used up during a call, the call will be terminated. This will trigger an immediate connection with an Agent so that minutes can be quickly added.
Alternatively, an “over minute protection” arrangement can be arranged, where a certain average of minutes is allowed and automatically arranged. In exemplary embodiments of the present invention, outgoing calls placed, and incoming calls received, can be deducted from a prepaid minutes balance. Emergency calls and Agent assistance calls would not count against the minutes balance.
To check the balance of minutes, a user can press the Phone button and a series of voice prompts can guide the user through acquiring this information. Minutes balance can also be accessed via the Subscriber Portal.
Use Case 6—Stolen Vehicle Location
In exemplary embodiments of the present invention, when a vehicle tracking request is received from a subscriber, a telematics service provider or other agent can, for example, confirm the location of the vehicle and provide the location to the police to assist their recovery of the lost vehicle. The service provider's operations center can request that the subscriber contact their local police department to obtain a police report. Once this report is obtained the subscriber can provide it to the service provider. The service provider's operations center can have the ability (provided the device and vehicle connections have been provisioned by the device designer to allow such command and control) to control the vehicle immobilizer function to incapacitate the engine from further restarting in a remote manner and within the guidelines of state law and in agreement with local police authorities. During the entire time the service is active, service provider can use reasonable efforts to attempt to block all other services via remote voice call, subscriber portal, and smart phone application and a notification of this state can be displayed on the Subscriber Portal and mobile app. A notification of feature activation can be sent to the customer using their preference settings (email, text, etc.). As remote access and functionality is subject to differing state laws and liability, deployment of these features can be determined by the Telematics Service Provider. Police can contact the subscriber to inform that the vehicle has been located and/or recovered. In exemplary embodiments, a Telematics Service Provider will not disclose the vehicle location data to the subscriber.
The components of the illustrative devices, systems and methods employed in accordance with the illustrated embodiments of the present invention can be implemented, at least in part, in digital electronic circuitry, analog electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. These components can be implemented, for example, as a computer program product such as a computer program, program code or computer instructions tangibly embodied in an information carrier, in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus such as a programmable processor, a computer, or multiple computers. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
Method steps associated with various exemplary embodiments of the present invention can be performed, for example, by one or more programmable processors executing a computer program, code or instructions to perform functions (e.g., by operating on input data and/or generating an output). Method steps can also be performed by, and apparatus of the invention can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example, semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in special purpose logic circuitry.
The foregoing disclosure of the exemplary embodiments of the present invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many variations and modifications of the embodiments described herein will be obvious to one of ordinary skill in the art in light of the above disclosure. The scope of the invention is to be defined only by the claims appended hereto, and by their equivalents.
This application claims the benefit of U.S. Provisional Patent Application No. 61/602,557, entitled SYSTEM AND METHOD OF PORTABLE VEHICLE OCCUPANT CONDITION SENSING AND TELEMATICS COMMUNICATIONS, filed on Feb. 23, 2012, and PCT/US2012/068318, filed on Dec. 6, 2012, the disclosure of each of which is hereby fully incorporated by reference. Related subject matter is disclosed and claimed in commonly owned US 2011/0045794, entitled DOCKING UNIT AND VEHICLE POWER ADAPTER WITH FREQUENCY MODULATED AUDIO SIGNAL INJECTION FOR CONNECTING PORTABLE MEDIA PLAYER AND/OR COMMUNICATIONS DEVICE TO VEHICLE FM RADIO AND AUDIO SYSTEM FOR PLAYBACK OF DIGITAL AUDIO BROADCAST STREAM (the “Docking Unit Application”), the entire contents of which is also hereby incorporated by reference.
Number | Date | Country | |
---|---|---|---|
61602557 | Feb 2012 | US |