WEBSERVICE ARCHITECTURE FOR VEHICLE HEALTH MAINTENANCE
First Claim
1. A webservice architecture for vehicle health maintenance, comprising:
- a core module in communication with a webservice provider, a webservice consumer, and a webservice registry over an internet protocol (IP) backbone, the core module adapted for;
registering and discovering the webservice provider using a universal description, discovery, and integration (UDDI) communications open standard,receiving a request from the webservice provider using a simple object access protocol (SOAP), the webservice provider accepting the request from the webservice consumer, andextracting a data structure based on the webservice request in a format according to the webservice registry using a web services description language (WSDL).
1 Assignment
0 Petitions
Accused Products
Abstract
A webservice architecture for vehicle health maintenance is provided. A core module is in communication with a webservice provider, a webservice consumer, and a webservice registry over an internet protocol (IP) backbone. The core module is adapted for registering and discovering the webservice provider using a universal description, discovery, and integration (UDDI) communications open standard, receiving a request from the webservice provider using a simple object access protocol (SOAP), the webservice provider accepting the request from the webservice consumer, and extracting a data structure based on the webservice request in a format according to the webservice registry using a web services description language (WDSL).
-
Citations
21 Claims
-
1. A webservice architecture for vehicle health maintenance, comprising:
a core module in communication with a webservice provider, a webservice consumer, and a webservice registry over an internet protocol (IP) backbone, the core module adapted for; registering and discovering the webservice provider using a universal description, discovery, and integration (UDDI) communications open standard, receiving a request from the webservice provider using a simple object access protocol (SOAP), the webservice provider accepting the request from the webservice consumer, and extracting a data structure based on the webservice request in a format according to the webservice registry using a web services description language (WSDL). - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
10. A method for communication over a webservice architecture for providing health maintenance for a vehicle, the webservice architecture including a core module in communication with a webservice provider, a webservice consumer, and a webservice registry over an internet protocol (IP) backbone, comprising:
-
registering and discovering the webservice provider using a universal description, discovery, and integration (UDDI) communications open standard; receiving a request from the webservice provider using a simple object access protocol (SOAP), the webservice provider accepting the request from the webservice consumer; and extracting a data structure based on the webservice request in a format according to the webservice registry using a web services description language (WDSL). - View Dependent Claims (11, 12, 13, 14, 15, 16, 17)
-
-
18. A computer program product for communication over a webservice architecture for providing health maintenance for a vehicle, the webservice architecture including a core module in communication with a webservice provider, a webservice consumer, and a webservice registry over an internet protocol (IP) backbone, the computer program product comprising a computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:
-
a first executable portion for registering and discovering the webservice provider using a universal description, discovery, and integration (UDDI) communications open standard; a second executable portion for receiving a request from the webservice provider using a simple object access protocol (SOAP), the webservice provider accepting the request from the webservice consumer; and a third executable portion for extracting a data structure based on the webservice request in a format according to the webservice registry using a web services description language (WDSL). - View Dependent Claims (19, 20, 21)
-
Specification