System for integrating a plurality of modules using a power/data backbone network
First Claim
1. A Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) support architecture comprising:
- a vehicle layer having;
a module positioned in a vehicle and configured to couple to a device via an input/output (I/O) interface compatible with the device and configured to couple to a controller via a cable adapted to simultaneously carry bi-directional data and uni-directional power to the module, wherein the module has a first processor and a first memory containing a first instruction set executable by the first processor, the first instruction set including instructions for providing a HyperText Transfer Protocol (HTTP) server, and wherein the first memory further contains a documentation set containing a service history of the module and a bill of materials for at least one of the module and the device that is accessible via the HTTP server and both event driven and time series data captured from the device and the module during operation of the vehicle; and
the controller positioned in the vehicle and having a second processor and a second memory containing a second instruction set executable by the second processor, the second instruction set including instructions for receiving data from the module and storing the data in the second memory, wherein the data includes the event driven and time series data; and
a shop layer separate from the vehicle layer having;
a browser configured to communicate with the HTTP server to access the documentation set; and
an analysis tool configured to receive the event driven and time series data from the controller and analyze a performance of the vehicle compared to predefined optimal vehicle parameters using the event driven and time series data.
2 Assignments
0 Petitions
Accused Products
Abstract
A Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) support architecture is provided. In one example, the VEEDIMS support architecture includes a vehicle layer and a shop layer. The vehicle layer has a module and a controller positioned in a vehicle. The module is configured to couple to a device via an input/output (I/O) interface compatible with the device and configured to couple to the controller via a cable adapted to simultaneously carry bi-directional data and uni-directional power to the module. The shop layer is separate from the vehicle layer and has a browser configured to communicate with an HTTP server in the module and an analysis tool configured to receive and analyze event driven and time series data from the controller.
-
Citations
20 Claims
-
1. A Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) support architecture comprising:
-
a vehicle layer having; a module positioned in a vehicle and configured to couple to a device via an input/output (I/O) interface compatible with the device and configured to couple to a controller via a cable adapted to simultaneously carry bi-directional data and uni-directional power to the module, wherein the module has a first processor and a first memory containing a first instruction set executable by the first processor, the first instruction set including instructions for providing a HyperText Transfer Protocol (HTTP) server, and wherein the first memory further contains a documentation set containing a service history of the module and a bill of materials for at least one of the module and the device that is accessible via the HTTP server and both event driven and time series data captured from the device and the module during operation of the vehicle; and the controller positioned in the vehicle and having a second processor and a second memory containing a second instruction set executable by the second processor, the second instruction set including instructions for receiving data from the module and storing the data in the second memory, wherein the data includes the event driven and time series data; and a shop layer separate from the vehicle layer having; a browser configured to communicate with the HTTP server to access the documentation set; and an analysis tool configured to receive the event driven and time series data from the controller and analyze a performance of the vehicle compared to predefined optimal vehicle parameters using the event driven and time series data. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) support architecture comprising:
-
a vehicle layer having; a plurality of modules positioned in a vehicle, wherein each module is configured to couple to at least one device via an input/output (I/O) interface compatible with the device and configured to couple to a controller via a cable adapted to simultaneously carry bi-directional data and uni-directional power to the module, and wherein each module has a first processor and a first memory containing a first instruction set executable by the first processor, the first instruction set including instructions for capturing and storing both event driven and time series data from the module and the device during operation of the vehicle; and the controller positioned in the vehicle and having a second processor and a second memory containing a second instruction set executable by the second processor, the second instruction set including instructions for receiving data from each of the plurality of modules and storing the data in the second memory, wherein the data includes the event driven and time series data; and a shop layer separate from the vehicle layer and having; a communications component configured to obtain the data from at least one of the plurality of modules and the controller; a server configured to store the obtained data; and an analysis tool configured to review and analyze the event driven and time series data to correlate the event driven and time series data to a specific fault event and to view a status of vehicle layer systems during the interval of the specific fault event. - View Dependent Claims (8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20)
-
Specification