Subscription-based services

• US 8,285,669 B2
• Filed: 04/30/2009
• Issued: 10/09/2012
• Est. Priority Date: 12/12/1994
• Status: Expired due to Fees

• Current Assignee: Cappelle Networking DE LLC (Intellectual Ventures LLC)
• Original Assignee: Cappelle Networking DE LLC (Intellectual Ventures LLC)
• Inventors: Northrup, Charles J.
• Primary Examiner(s): JUNG, DAVID YIUK
• Application Number:
  US12/433,528
• Publication Number:
  US 20090300192A1
• Time in Patent Office: 1,258 Days
• Field of Search: 709/228
• US Class Current: 707/608
• CPC Class Codes: G06F 9/44552 Conflict resolution, i.e. enabling coexistence of conflicting executables
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/922 Communications
• CPC Class Codes: Y10S 707/966 Distributed
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

The present invention provides a virtual network, sitting “above” the physical connectivity and thereby providing the administrative controls necessary to link various communication devices via an Access-Method-Independent Exchange. In this sense, the Access-Method-Independent Exchange can be viewed as providing the logical connectivity required. In accordance with the present invention, connectivity is provided by a series of communication primitives designed to work with each of the specific communication devices in use. As new communication devices are developed, primitives can be added to the Access-Method-Independent Exchange to support these new devices without changing the application source code. A Thread Communication Service is provided, along with a Binding Service to link Communication Points. A Thread Directory Service is available, as well as a Broker Service and a Thread Communication Switching Service. Intraprocess, as well as Interprocess, services are available. Dynamic Configuration Management and a Configurable Application Program Service provide software which can be commoditized, as well as upgraded while in operation.

Claims

1. A method comprising:

receiving, at a service provider computer, a request communication comprising a request to perform at least one operation, the at least one operation including one or more of (i) registering an application service, wherein the request communication comprises required registration information, (ii) registering an application service, wherein the request communication comprises required registration information and one or more optional registration information, (iii) querying for an application service, wherein the request communication comprises one or more criteria for selecting the application service, and (iv) selecting and connecting to an accessible application service, wherein the request communication comprises one or more criteria for selecting the application service;

interacting, by the service provider computer, with a directory service of registered application services to satisfy the request; and

in response thereto, sending a response communication from the service provider computer to the end-user application process.

2. The method of claim 1, wherein the criteria is at least one of a textual description of a type of the application service, a sending communication primitive and a receiving communication primitive, a communication mechanism used in establishing the application service, a location of the application service, an input type understood by the application service, an output type generated by the application service, a keyword search list, a token indicating whether execution of the application service can be started, a token describing a data representation in communication with the application service, a token describing if execution of the application service must have previously been started, a token indicating whether a thread communication identifier is listed, a token indicating whether a public connection to the application service can be used, a token indicating whether a private connection to the application service can be used, a token indicating whether a public connection is mandatory, a token indicating whether a private connection is mandatory, a token indicating whether the application service is a component of a larger application service, a shell action to execute in initializing the application service, a maximum number of concurrent communications, licensing information, general user information, a link to additional services required for using the application service, status information components, information components used for future enhancements, a thread communication identifier, a secondary thread service directory, a usage fee, and a directory service fee.

3. A non-transitory computer-readable medium having instructions stored thereon, the instructions comprising:

instructions to receive a request comprising at least one unique identifier assigned to an end-user application process, and in response thereto validate the at least one unique identifier;

instructions to select one or more accessible application services from a set of registered application services; and

instructions to communicate the results thereof to the end-user application process.

4. The system of claim 3, wherein the criteria is at least one of a textual description of a type of the application service, a sending communication primitive and a receiving communication primitive, a communication mechanism used in establishing the application service, a location of the application service, an input type understood by the application service, an output type generated by the application service, a keyword search list, a token indicating whether execution of the application service can be started, a token describing a data representation in communication with the application service, a token describing if execution of the application service must have previously been started, a token indicating whether a thread communication identifier is listed, a token indicating whether a public connection to the application service can be used, a token indicating whether a private connection to the application service can be used, a token indicating whether a public connection is mandatory, a token indicating whether a private connection is mandatory, a token indicating whether the application service is a component of a larger application service, a shell action to execute in initializing the application service, a maximum number of concurrent communications, licensing information, general user information, a link to additional services required for using the application service, status information components, information components used for future enhancements, a thread communication identifier, a secondary thread service directory, a usage fee, and a directory service fee.

5. A method comprising:

a service provider initializing a communication link over the Internet in response to receiving a connection request to establish a connection with an end-user application process,

wherein the service provider executes on a service provider computer;

the service provider receiving a query request via the communication link, the query request including one or more criteria for selecting at least one application service satisfying the criteria;

the service provider locating a registered application service satisfying the criteria;

the service provider sending a response communication to the end-user application process, the response including information representative of the registered information describing the application service satisfying the request; and

the service provider disconnecting the communication link.

6. The method of claim 5, wherein the criteria is at least one of a textual description of a type of the application service, a sending communication primitive and a receiving communication primitive, a communication mechanism used in establishing the application service, a location of the application service, an input type understood by the application service, an output type generated by the application service, a keyword search list, a token indicating whether execution of the application service can be started, a token describing a data representation in communication with the application service, a token describing if execution of the application service must have previously been started, a token indicating whether a thread communication identifier is listed, a token indicating whether a public connection to the application service can be used, a token indicating whether a private connection to the application service can be used, a token indicating whether a public connection is mandatory, a token indicating whether a private connection is mandatory, a token indicating whether the application service is a component of a larger application service, a shell action to execute in initializing the application service, a maximum number of concurrent communications, licensing information, general user information, a link to additional services required for using the application service, status information components, information components used for future enhancements, a thread communication identifier, a secondary thread service directory, a usage fee, and a directory service fee.

7. A method comprising:

a service provider initializing a communication link in response to receiving a connection request to establish a connection with an end-user application process, wherein the service provider executes on a service provider computer;

the service provider receiving a query request via the communication link, the query request including one or more criteria for selecting a desired application service;

the service provider interacting with a directory service process comprising one or more registered application services to select an application service satisfying the criteria; and

the service provider connecting the end user application process to the selected application service.

8. The method of claim 7, wherein the criteria is at least one of a textual description of a type of the application service, a sending communication primitive and a receiving communication primitive, a communication mechanism used in establishing the application service, a location of the application service, an input type understood by the application service, an output type generated by the application service, a keyword search list, a token indicating whether execution of the application service can be started, a token describing a data representation in communication with the application service, a token describing if execution of the application service must have previously been started, a token indicating whether a thread communication identifier is listed, a token indicating whether a public connection to the application service can be used, a token indicating whether a private connection to the application service can be used, a token indicating whether a public connection is mandatory, a token indicating whether a private connection is mandatory, a token indicating whether the application service is a component of a larger application service, a shell action to execute in initializing the application service, a maximum number of concurrent communications, licensing information, general user information, a link to additional services required for using the application service, status information components, information components used for future enhancements, a thread communication identifier, a secondary thread service directory, a usage fee, and a directory service fee.

9. A method comprising:

a service provider application process receiving a communication comprising a request to provide an application service, wherein the service provider application process executes on a service provider computer;

the service provider application process interacting with the received communication to dynamically configure an application service to satisfy the request; and

the service provider application process executing the dynamically configured application service to satisfy the request.

10. A method comprising:

a service provider application process receiving a communication comprising a unique identifier assigned to an end-user application process during a subscription process and criteria for selecting a registered communication point, wherein the service provider application process executes on a service provider computer;

in response thereto, the service provider application process validating the end-user application process;

the service provider application process selecting a registered communication point satisfying the criteria; and

the service provider application process redirecting communication from the selected communication point to the end-user application process.

11. The method of claim 10, wherein the criteria is at least one of a textual description of a type of the registered communication point, a sending communication primitive and a receiving communication primitive, a communication mechanism used in establishing the registered communication point, a location of the registered communication point, an input type understood by the registered communication point, an output type generated by the registered communication point, a keyword search list, a token indicating whether execution of the registered communication point can be started, a token describing a data representation in communication with the registered communication point, a token describing if execution of the registered communication point must have previously been started, a token indicating whether a thread communication identifier is listed, a token indicating whether a public connection to the registered communication point can be used, a token indicating whether a private connection to the registered communication point can be used, a token indicating whether a public connection is mandatory, a token indicating whether a private connection is mandatory, a shell action to execute in initializing the registered communication point, a maximum number of concurrent communications, licensing information, general user information, a link to additional communication points required for using the registered communication point, status information components, information components used for future enhancements, a thread communication identifier, a secondary thread service directory, a usage fee, and a directory service fee.

12. A computer including a data storage having instructions stored thereon that, if executed by the computer, cause the computer to execute an application process, the application process comprising at least a first minor service, wherein the application process is configured to perform operations comprising:

selecting a second minor service based at least in part on one or more criteria;

replacing the first minor service with the second minor service by at least;

suspending the first minor service, and

loading the second minor service; and

connecting the application process to the second minor service,

wherein the first minor service comprises a process or a thread, and wherein the second minor service comprises a process or a thread.

13. The computer of claim 12, wherein the second minor service is configured to execute within an address space of the application process.

14. The computer of claim 12, wherein the second minor service is configured to execute within a different address space than the application process.

15. The computer of claim 12, wherein selecting the second minor service based on the one or more criteria comprises sending the one or more criteria to a directory service of registered minor services.

16. The computer of claim 15, wherein selecting the second minor service based on the one or more criteria further comprises receiving a listing of minor services matching the one or more criteria.

17. The computer of claim 16, wherein the listing of minor services comprises respective locations for individual minor services.

18. The computer of claim 12, wherein connecting the application process to the second minor service comprises connecting the application process to the second minor service when the application process requires interaction with the second minor service.

19. The computer of claim 12, wherein loading the second minor service comprises loading the second minor service into an address space of the application process.

20. The computer of claim 12, wherein the criteria is at least one of a textual description of a type of a minor service, a sending communication primitive and a receiving communication primitive, a communication mechanism used in establishing the minor service, a location of the minor service, an input type understood by the minor service, an output type generated by the minor service, a keyword search list, a token indicating whether execution of the minor service can be started, a token describing a data representation in communication with the minor service, a token describing if execution of the minor service must have previously been started, a token indicating whether a thread communication identifier is listed, a token indicating whether a public connection to the minor service can be used, a token indicating whether a private connection to the minor service can be used, a token indicating whether a public connection is mandatory, a token indicating whether a private connection is mandatory, a token indicating whether the minor service is a component of a larger application service, a shell action to execute in initializing the minor service, a maximum number of concurrent communications, licensing information, general user information, a link to additional services required for using the minor service, status information components, information components used for future enhancements, a thread communication identifier, a secondary thread service directory, a usage fee, and a directory service fee.

21. A method comprising:

a computer selecting a second minor service based at least in part on one or more criteria;

the computer replacing a first minor service with the second minor service by at least;

suspending the first minor service, and

loading the second minor service; and

the computer connecting an application process to the second minor service;

wherein the first minor service comprises a process or a thread, and wherein the second minor service comprises a process or a thread.

22. The method of claim 21, wherein the second minor service is configured to execute within an address space of the application process.

23. The method of claim 21, wherein the second minor service is configured to execute within a different address space than the application process.

24. The method of claim 21, wherein selecting the second minor service based on the one or more criteria comprises sending the one or more criteria to a directory service of registered minor services.

25. The method of claim 24, wherein selecting the second minor service based on the one or more criteria further comprises receiving a listing of minor services matching the one or more criteria.

26. The method of claim 25, wherein the listing of minor services comprises respective locations for individual minor services.

27. The method of claim 21, wherein connecting the application process to the second minor service comprises connecting the application process to the second minor service when the application process requires interaction with the second minor service.

28. The method of claim 21, wherein loading the second minor service comprises loading the second minor service into an address space of the application process.

29. The method of claim 21, wherein the criteria is at least one of a textual description of a type of a minor service, a sending communication primitive and a receiving communication primitive, a communication mechanism used in establishing the minor service, a location of the minor service, an input type understood by the minor service, an output type generated by the minor service, a keyword search list, a token indicating whether execution of the minor service can be started, a token describing a data representation in communication with the minor service, a token describing if execution of the minor service must have previously been started, a token indicating whether a thread communication identifier is listed, a token indicating whether a public connection to the minor service can be used, a token indicating whether a private connection to the minor service can be used, a token indicating whether a public connection is mandatory, a token indicating whether a private connection is mandatory, a token indicating whether the minor service is a component of a larger application service, a shell action to execute in initializing the minor service, a maximum number of concurrent communications, licensing information, general user information, a link to additional services required for using the minor service, status information components, information components used for future enhancements, a thread communication identifier, a secondary thread service directory, a usage fee, and a directory service fee.

30. A method comprising:

a computer performing a first minor service of an application process;

the computer replacing the first minor service of the application process with a second minor service by at least;

suspending the first minor service, and

loading the second minor service;

wherein the first minor service comprises a process or a thread, and wherein the second minor service comprises a process or a thread.

31. The method of claim 30, wherein the second minor service is configured to execute within an address space of the application process.

32. The method of claim 30, wherein the second minor service is configured to execute within a different address space than the application process.

33. The method of claim 30, further comprising:

sending one or more criteria to a directory service of registered minor services.

34. The method of claim 33, further comprising:

receiving a listing of minor services matching the one or more criteria.

35. The method of claim 34, wherein the listing of minor services comprises respective locations for individual minor services.

36. The method of claim 30, further comprising:

connecting the application process to the second minor service when the application process requires interaction with the second minor service.

37. The method of claim 30, wherein loading the second minor service comprises loading the second minor service into an address space of the application process.

38. The method of claim 30, wherein the criteria is at least one of a textual description of a type of a minor service, a sending communication primitive and a receiving communication primitive, a communication mechanism used in establishing the minor service, a location of the minor service, an input type understood by the minor service, an output type generated by the minor service, a keyword search list, a token indicating whether execution of the minor service can be started, a token describing a data representation in communication with the minor service, a token describing if execution of the minor service must have previously been started, a token indicating whether a thread communication identifier is listed, a token indicating whether a public connection to the minor service can be used, a token indicating whether a private connection to the minor service can be used, a token indicating whether a public connection is mandatory, a token indicating whether a private connection is mandatory, a token indicating whether the minor service is a component of a larger application service, a shell action to execute in initializing the minor service, a maximum number of concurrent communications, licensing information, general user information, a link to additional services required for using the minor service, status information components, information components used for future enhancements, a thread communication identifier, a secondary thread service directory, a usage fee, and a directory service fee.