US2003182361A1PendingUtilityA1

Business-model agnostic service deployment management service

41
Assignee: SUN MICROSYSTEMS INCPriority: Mar 22, 2002Filed: Mar 22, 2002Published: Sep 25, 2003
Est. expiryMar 22, 2022(expired)· nominal 20-yr term from priority
H04L 41/5045H04L 41/082G06Q 30/04H04L 41/5054
41
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

An invention is provided for a business-model agnostic system that provides service deployment management. The business-model agnostic system includes a plurality of service objects, wherein each service object stores information for a particular service. In addition, a plurality of service directories is included, wherein each service directory includes a list of service objects. The business-model agnostic system also includes a plurality of service entry objects, each service entry object defining a relationship between a service object and a service directory. Further included is a plurality of vehicle client objects. Each vehicle client object stores a list of service directories. In this manner, the business-model agnostic system can be queried based on object relationships utilizing the service entry objects.

Claims

exact text as granted — not AI-modified
What is claimed is:  
     
         1 . A system for providing service deployment management, comprising: 
 a plurality of service objects, each service object storing information for a particular service;    a plurality of service directories, each service directory including a list of service objects; and    a plurality of service entry objects, each service entry object defining a relationship between a service object and a service directory.    
     
     
         2 . A system as recited in  claim 1 , wherein each service object stores a list of software components required to utilize a related service.  
     
     
         3 . A system as recited in  claim 2 , wherein each service directory object includes a set related services, the set of related services capable of being deployed on a vehicle client device.  
     
     
         4 . A system as recited in  claim 3 , wherein a service entry object indicates a price of a service.  
     
     
         5 . A system as recited in  claim 1 , further comprising a plurality vehicle client objects, each vehicle client object storing information regarding a vehicle client device.  
     
     
         6 . A system as recited in  claim 5 , wherein each vehicle client object stores a list of service directories.  
     
     
         7 . A system as recited in  claim 6 , further comprising a user object associated with a particular vehicle client object, the user object storing information regarding a particular user.  
     
     
         8 . A system as recited in  claim 7 , further comprising an authorization object, the authorization object storing a relationship between the user object and the particular vehicle client object.  
     
     
         9 . A method for providing service deployment management, comprising the operations of: 
 providing a plurality of service objects, each service object storing information for a particular service;    storing a list of service objects using a service directory object; and    defining a relationship between each listed service object and the service directory using a service entry object.    
     
     
         10 . A method as recited in  claim 9 , wherein each service object stores a list of software components required to utilize a related service.  
     
     
         11 . A method as recited in  claim 10 , wherein each service directory object includes a set related services, the set of related services capable of being deployed on a vehicle client device.  
     
     
         12 . A method as recited in  claim 11 , wherein a service entry object indicates a price of a service.  
     
     
         13 . A method as recited in  claim 9 , further comprising the operation of providing a plurality vehicle client objects, each vehicle client object storing information regarding a vehicle client device.  
     
     
         14 . A method as recited in  claim 13 , wherein each vehicle client object stores a list of service directories.  
     
     
         15 . A method as recited in  claim 14 , further comprising the operation of associating a user object with a particular vehicle client object, the user object storing information regarding a particular user.  
     
     
         16 . A method as recited in  claim 15 , further comprising the operation of providing an authorization object, the authorization object storing a relationship between the user object and the particular vehicle client object.  
     
     
         17 . A business-model agnostic system for providing service deployment management, comprising: 
 a plurality of service objects, each service object storing information for a particular service;    a plurality of service directories, each service directory including a list of service objects;    a plurality of service entry objects, each service entry object defining a relationship between a service object and a service directory; and    a plurality of vehicle client objects, each vehicle client object storing a list of service directories, wherein the business-model agnostic system can be queried based on object relationships utilizing the service entry objects.    
     
     
         18 . A business-model agnostic system as recited in  claim 17 , wherein each service object stores a list of software components required to utilize a related service, and wherein each service directory object includes a set related services, the set of related services capable of being deployed on a vehicle client device.  
     
     
         19 . A business-model agnostic system as recited in  claim 17 , further comprising a user object associated with a particular vehicle client object, the user object storing information regarding a particular user.  
     
     
         20 . A business-model agnostic system as recited in  claim 19 , further comprising an authorization object, the authorization object storing a relationship between the user object and the particular vehicle client object.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.