OEM Safe Aftermarket Gateway

• US 20130317668A1
• Filed: 08/02/2013
• Published: 11/28/2013
• Est. Priority Date: 01/03/2012
• Status: Abandoned Application

• Current Assignee: Stephan A. Tarnutzer
• Original Assignee: Stephan A. Tarnutzer
• Inventors: Tarnutzer, Stephan A.
• Application Number:
  US13/957,682
• Publication Number:
  US 20130317668A1
• Time in Patent Office: Days
• US Class Current: 701/2
• CPC Class Codes: G06F 13/38 Information transfer, e.g. on bus G06F13/14 takes precedence
• CPC Class Codes: H04L 12/40006 Architecture of a communication node current supply arrangements H04L12/10; intermediate storage or scheduling H04L49/90
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge

Abstract

The OEM safe aftermarket gateway is used to enable aftermarket devices and systems that the OEM did not design or specify to be connected to the OEM vehicles without negatively affecting the electronics system of the vehicle. The OEM safe aftermarket gateway protects the OEM vehicle communication bus from aftermarket devices and systems, yet still enables aftermarket devices and systems to function as intended. The OEM safe aftermarket gateway enables the ‘bridging’ between the OEM vehicle communication bus and the aftermarket suppliers requiring access to the communication bus. The OEM safe aftermarket gateway is similar to what a firewall and router do for the Internet industry. The OEM safe aftermarket gateway protects the proprietary information of each party and yet still enables an aftermarket supplier to access the OEM vehicle communication bus through a safe and reliable system.

Claims

1. An OEM safe aftermarket gateway having a processor, said gateway enabling access to OEM vehicle communication bus software that includes proprietary data;

and an aftermarket application in communication with an aftermarket device or system, said OEM safe aftermarket gateway providing said aftermarket device or system with vehicle connectivity that is OEM approved, one digital connection of said OEM safe aftermarket gateway is via said OEM control module vehicle communication bus software, and another digital connection of said OEM safe aftermarket gateway communicates is via said aftermarket device or system, said aftermarket device or system being unable to communicate directly or interfere with said OEM control module vehicle communication bus software, but through said gateway providing an aftermarket device or system with standard interface to OEM vehicle communication bus for data exchange, said interface comprising;

a) an OEM control module vehicle communication bus software;

b) an OEM safe aftermarket gateway, the gateway being wired or wireless with software Application Programming Interface; and

c) an aftermarket application device or system;

whereby said OEM safe aftermarket gateway enables an unlimited number of aftermarket devices or systems to be safely connected to the OEM vehicle without the need to test each aftermarket device or system independently that needs to be used with a particular vehicle.

2. The OEM safe aftermarket gateway of claim 1, wherein the OEM safe aftermarket gateway, in use, communicates on one side with the OEM vehicle communication bus directly and on the other side with the aftermarket device or system on a different type of communication bus using a standard the Application programming interface so that the aftermarket device or system cannot interfere with the OEM vehicle communication bus.

3. The OEM safe aftermarket gateway of claim 1, wherein said OEM safe aftermarket gateway provides said aftermarket supplier with vehicle connectivity that is OEM approved.

4. An OEM control module for use with an OEM vehicle, said OEM control module comprising:

a) OEM control module vehicle communication bus software which includes OEM proprietary data embodied in a set of OEM approved messages used in information exchange; and

b) an OEM safe aftermarket gateway linked to said OEM control module vehicle communication bus software; and

c) an aftermarket application in communication with an aftermarket device or system, said OEM safe aftermarket gateway providing said aftermarket with vehicle connectivity that is OEM approved; and

whereby, one digital connection of said OEM safe aftermarket gateway is via said OEM control module vehicle communication bus software, and another digital connection of said OEM safe aftermarket gateway communicates is via said aftermarket device or system so said aftermarket device or system is unable to communicate directly or interfere with said OEM control module vehicle communication bus software; and

whereby said OEM safe aftermarket gateway provides an aftermarket device or system with standard interface to OEM vehicle communication bus for data exchange through a standard OEM approved API, said API as an integral part of a OEM safe aftermarket gateway, or as a standalone software module as part of an existing OEM module.

5. The OEM control module of claim 4, wherein said OEM safe aftermarket gateway creates connectivity to said OEM vehicle that protects and addresses the proprietary data concerns of said OEM.

6. The OEM safe aftermarket gateway of claim 4, wherein said OEM safe aftermarket gateway isolates said aftermarket device or system from said OEM vehicle communication bus software enabling an OEM sign-off and OEM vehicle warranty applying to said aftermarket device or system.

7. An OEM control module for use with an OEM vehicle, said OEM control module comprising:

a) an OEM control module vehicle communication bus software which includes OEM proprietary data embodied in a set of OEM approved messages used in information exchange;

b) an OEM safe aftermarket gateway linked to said OEM control module vehicle communication bus software residing in protected memory region linked to said OEM control module vehicle communication bus software via a sandbox; and

c) an aftermarket application in communication with an aftermarket device or system, said OEM safe aftermarket gateway isolating said aftermarket device or system from said OEM control module vehicle communication bus software to maintain network integrity, said OEM safe aftermarket gateway providing said aftermarket with vehicle connectivity that is OEM approved;

whereby said sandbox acts as a gateway protecting the operation of the OEM vehicle while providing access via defined software Application Processor Interfaces for aftermarket software to interact with said OEM vehicle bus communication software; and

whereby, said gateway protects the operation of the OEM vehicle while providing access to aftermarket software to interact with said OEM via defined, software Application programming interface; and

whereby, said aftermarket device or system uses said OEM safe aftermarket gateway to acquire and process vehicle data required for the operation of said aftermarket device or system or to control specific OEM vehicle features and functions, said aftermarket device or system being interfaced with said OEM safe aftermarket gateway receiving or requesting vehicle data that said OEM vehicle bus communication software provides.

8. The OEM control module of claim 7, wherein the OEM aftermarket gateway software component comprising the standard OEM safe aftermarket API is in a partitioned-off and secured, non-volatile memory space of said OEM control module.

9. The OEM control module of claim 7, wherein said OEM safe aftermarket gateway creates connectivity to said OEM vehicle that protects and addresses the proprietary data concerns of said OEM.

10. The OEM control module of claim 7, wherein said OEM safe aftermarket gateway provides said aftermarket supplier with vehicle connectivity that is OEM approved.

11. The OEM control module of claim 7, wherein the sandbox is a partitioned-off and secured, non-volatile memory space of said OEM control module.

12. The OEM control module of claim 7, wherein said application processor interfaces enable a controlled method for said aftermarket device or system to control certain pre-defined features of said OEM vehicle through said sandbox.

13. The OEM control module of claim 7, wherein secured non-volatile memory region provides a safe space for aftermarket software to reside inside said OEM control module without the ability for said aftermarket software to be able to negatively affect operation of said OEM control module.

14. An OEM control module for use with an OEM vehicle, said OEM control module comprising:

a) an OEM control module vehicle communication bus software which includes OEM proprietary data embodied in a set of OEM approved messages used in information exchange;

b) an OEM safe aftermarket gateway linked to said OEM control module vehicle communication bus software; and

c) an aftermarket application in communication with an aftermarket device or system, said OEM safe aftermarket gateway providing said aftermarket with vehicle connectivity that is OEM approved;

whereby said OEM safe aftermarket gateway acts as said OEM control module to perform specific vehicle control and data acquisition functions via communication of properly formatted commands sent periodically or on-demand by said OEM control module, said OEM safe aftermarket gateway is granted the control of the feature or function normally controlled by said OEM control module; and

whereby one digital connection of said OEM safe aftermarket gateway is via said OEM control module vehicle communication bus software, and another digital connection of said OEM safe aftermarket gateway communicates is via said aftermarket device or system so that said aftermarket device or system is prevented from direct communication with said OEM control module vehicle communication bus software, but only by said OEM safe aftermarket gateway as approved by said OEM.

15. The OEM control module of claim 14, wherein collision detection is used to determine if the same or similar message or signal is being sent concurrently by the OEM control module and OEM safe aftermarket gateway, ensuring no information will be lost.

16. The OEM control module of claim 14, wherein said OEM safe aftermarket gateway isolates said aftermarket device or system from the OEM system and the network to maintain the network integrity and the vehicle safety.

17. The OEM control module of claim 14, wherein a vehicle control system capable of facilitating the transfer of data from vehicle hardware modules to remote sources and for remote sources to be able to control existing OEM features.