System and method for establishing communication protocols between application programs

• US 5,546,584 A
• Filed: 04/13/1995
• Issued: 08/13/1996
• Est. Priority Date: 07/01/1992
• Status: Expired due to Term

• Current Assignee: Kenneth Lundin, Lars-Erik Wiman, Mats Svensson
• Original Assignee: Kenneth Lundin, Lars-Erik Wiman, Mats Svensson
• Inventors: Svensson, Mats, Lundin, Kenneth, Wiman, Lars-Erik
• Primary Examiner(s): Coleman, Eric
• Assistant Examiner(s): SHAH, ALPESH
• Application Number:
  US08/422,625
• Time in Patent Office: 488 Days
• Field of Search: 395/700, 395/650, 395/600, 395/500, 395/200, 364/188, 364/191, 364/194
• US Class Current: 719/315
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method and system for implementing a common protocol for communication of data between a first application program and a second application program. The method and system uses a high level interface specification that is created in a computer program language-independent fashion using an object oriented paradigm. The high level interface specification is used to define the common protocol, and to generate first and second protocol interfaces. Either of the generated first and second protocol interfaces is capable of performing the services of a client or server, and are inserted into the first and second application programs respectively. The first and second protocol interfaces are executed by the first and second application programs for communication of data between them using the common protocol.

Claims

1. A method for generating and monitoring the interaction of a plurality of a dynamically varying set of software modules, in a computing system having one or more processors, wherein each of said software modules is capable of interactively creating and manipulating objects belonging to one or more object classes, each of said object class being automatically generated from an interface specification, said method comprising the steps

defining a computer-language-independent interface specification to govern the interaction of said plurality of software modules across one or more processors by the steps of;

providing a unique name for said interface specification;

providing a list of one or more in instance variables which define the characteristics of a class of objects;

providing zero or more interaction variables specifying the public or private interaction of a group of said objects; and

specifying constraints if any, on the interaction of said software modules;

converting said computer-language-independent interface specification into a computer-language-specific interface implementation for a specific computing system using at least the following information;

a name of a communications protocol to be used for the interchange of data between said software modules;

an identification of the software modules that need to exchange data to interactively create and manipulate objects;

an operational command set for each such software module; and

the constraints, if any, on the interaction of said software modules;

creating a plurality of functional software modules that are capable of interacting or communicating with each other using said computer-language-specific interface implementation;

regulating the interaction of said software modules such that any of said plurality of software modules is permitted to initiate or respond to communications from any other software module; and

executing said plurality of software modules on said computing system using said computer-language-specific interface implementation for communicating data between said software modules.

2. The method of claim 1 wherein the definition of said computer-language-independent interface specification governing the interaction of said plurality of software modules across one or more processors further comprises:

providing the name of a parent specification whenever said interface specification is based upon said parent specification.

3. The method of claim 1 wherein said step of converting said computer-language-independent interface specification into said computer-language-specific interface implementation performed using a stub-code generation tool, regardless of whether said software modules are linked statically or dynamically.

4. The method of claim 1 wherein said step of defining a computer-language-independent interface specification further comprises the steps of:

grouping the operations of said interface specification into a plurality of two-party communications protocols, each of said two-party communications protocols specifying the communication between a pair of software modules that are parties to a communications contract; and

specifying the constraints, if any, on the interaction of each of the pairs of software modules that are the parties to said communications contract.

5. The method of claim 4 wherein the specification of each of said two-party communications protocols further includes:

a name of said two-party communications protocol;

a name of a first software module;

an operational command set for said first software module;

a name of a second software module;

an operational command set for said second software module; and

the constraints, if any, on the interaction of the two software modules that are the parties to said communications contract.

6. The method of claim 1 wherein the functional software modules created from said interface specification further comprises an interface agent.

7. The method of claim 6 wherein said interface agent additionally comprises a despatcher that receives a signal from a communication party, parses said signal into an address and a message, strips said address from said signal and distributes said message of said signal based upon said address to a recipient software module.

8. The method of claim 1 wherein the functional software modules created from said interface specification additionally includes a protocol supervisor operating as a state machine that supervises obedience to protocol rules predefined in said interface specification.

9. The method of claim 1 wherein information about all interfaces that have been implemented for software modules within said computing system is stored centrally in a trader module that is part of the kernel of the operating system of said computing system.

10. A system for generating and monitoring the interaction of a plurality of a dynamically varying set of software modules in a computing system having one or more processors, wherein each of said software modules is capable of interactively creating and manipulating objects belonging to one or more object classes, each of said object class being automatically generated from an interface specification, said system comprising:

means for defining a computer-language-independent interface specification to govern the interaction of said plurality of software modules across one or more processors by the steps

providing a unique name for said interface specification;

providing a list of one or more instance variables which define the characteristics of a class of objects;

providing zero or more interaction variables specifying the public or private interaction of a group of said objects; and

specifying constraints, if any, on the interaction of said software modules;

means for converting said computer-language-independent interface specification into a computer-language-specific interface implementation for a specific computing system using at least the following information;

a name of a communications protocol to be used for the interchange of data between said software modules;

an identification of the software modules that need to exchange data to interactively create and manipulate objects;

an operational command set for each such software module; and

the constraints, if any, on the interaction of said software modules;

means for creating a plurality of functional software modules that are capable of interacting or communicating with each other using said computer-language-specific interface implementation;

means for regulating the interaction of said software modules such that any of said plurality of software modules is permitted to initiate or respond to communications from any other software module; and

means for executing said plurality of software modules on said computing system using said computer-language-specific interface implementation for communicating data between said software modules.

11. The system of claim 10 wherein said means for defining computer-language-independent interface specification to govern the interaction of said plurality of software modules across one or more processors further comprises:

means for providing the name of a parent specification whenever said interface specification is based upon said parent specification.

12. The system of claim 10 wherein said means for converting said computer-language-independent interface specification into said computer-language-specific interface implementation comprises a stub-code generation tool, regardless of whether said software modules are linked statically or dynamically.

13. The system of claim 10 wherein said means for defining a computer-language-independent interface specification further comprises:

means for grouping the operations of said interface specification into a plurality of two-party communications protocols, each of said two-party communications protocols specifying the communication between a pair of software modules that are parties to a communications contract; and

means for specifying the constraints, if any, on the interaction of each of the pairs of software modules that are the parties to said communications contract.

14. The system of claim 13 wherein the means for specifying each of said two-party communications protocols further comprises:

means for providing a name for said two-party communications protocol;

means for providing a name of a first software module;

means for providing an operational command set for said first software module;

means for providing a name of a second software module;

means for providing an operational command set for said second software module; and

means for specifying the constraints, if any, on the interaction of the two software modules that are the parties to said communications contract.

15. The system of claim 10 wherein said means for creating functional software modules from said interface specification further comprises an interface agent.

16. The system of claim 15 wherein said interface agent additionally comprises a despatcher that receives a signal from a communication party, parses said signal into an address and a message, strips said address from said signal and distributes said message of said signal based upon said address to a recipient software module.

17. The system of claim 10 wherein said means for creating functional software modules from said interface specification additionally includes a protocol supervisor operating as a state machine that supervises obedience to protocol rules predefined in said interface specification.

18. The system of claim 10 further comprising central storage means within a trader module that is part of the kernel of the operating system of said computing system for storing information about all interfaces that have been implemented for software modules within said computing system.

19. The system of claim 10 wherein said computing system is a distributed or modular computing system of the type commonly used in telecommunications environments.

20. A method for generating and monitoring the interaction of a plurality of a dynamically varying set of software modules in a computing system having one or more processors, wherein each of said software modules is capable of interactively creating and manipulating objects belonging to one or more object classes, each of said object class being automatically generated from an interface specification, said method comprising the steps of:

defining a computer-language-independent interface specification to govern the interaction of said plurality of software modules across one or more processors by the steps of;

providing a unique name for said interface specification;

providing a list of one or more instance variables which define the characteristics of a class of objects;

providing zero or more interaction variables specifying the public or private interaction of a group of said objects; and

specifying constraints, if any, on the interaction of said software modules;

converting said computer-language-independent interface specification into a computer-language-specific interface implementation for a specific computing system using at least the following information;

a name of a communications protocol to be used for the interchange of data between said software modules;

an identification of the software modules that need to exchange data to interactively create and manipulate objects;

an operational command set for each such software module; and

the constraints, if any, on the interaction of said software modules;

creating a plurality of functional software modules that arc capable of interacting or communicating with each other using said computer-language-specific interface implementation;

regulating the interaction of said software modules such that only one of each pair of software modules is permitted to initiate communication with the other, and the other software module of said pair is only permitted to respond to queries of said initiating software module; and

executing said plurality of software modules on said computing system using said computer-language-specific interface implementation for communicating data between said software modules.

21. The method of claim 20 wherein the definition of said computer-language-independent interface specification governing the interaction of said plurality of software modules across one or more processors further comprises:

providing the name of a parent specification whenever said interface specification is based upon said parent specification.

22. The method of claim 20 wherein said step of converting said computer-language-independent interface specification into said computer-language-specific interface implementation is performed using a stub-code generation tool, regardless of whether said software modules are linked statically or dynamically.

23. The method of claim 20 wherein the functional software modules created from said interface specification further comprises an interface agent.

24. The method of claim 23 wherein said interface agent additionally comprises a despatcher that receives a signal from a communication party, parses said signal into an address and a message, strips said address from said signal and distributes said message of said signal based upon said address to a recipient software module.

25. The method of claim 20 wherein the functional software modules created from said interface specification additionally includes a protocol supervisor operating as a state machine that supervises obedience to protocol rules predefined in said interface specification.

26. The method of claim 20 wherein information about all interfaces that have been implemented for software modules within said computing system is stored centrally in a trader module that is part of the kernel of the operating system of said computing system.

27. A system for generating and monitoring the interaction of a plurality or a dynamically varying set of software modules in a computing system having one or more processors, wherein each of said software modules is capable of interactively creating and manipulating objects belonging to one or more object classes, each of said object class being automatically generated from an interface specification, said system comprising:

means for defining a computer-language-independent interface specification to govern the interaction of said plurality of software modules across one or more processors by the steps of;

providing a unique name for said interface specification;

providing a list of one or more instance variables which define the characteristics of a class of objects;

providing zero or more interaction variables specifying the public or private interaction of a group of said objects; and

specifying constraints, if any, on the interaction of said software modules;

means for converting said computer-language-independent interface specification into a computer-language-specific interface implementation for a specific computing system using at least the following information;

a name of a communications protocol to be used for the interchange of data between said software modules;

an identification of the software modules that need to exchange data to interactively create and manipulate objects;

an operational command set for each such software module; and

the constraints, if any, on the interaction of said software modules;

means for creating a plurality of functional software modules that are capable of interacting or communicating with each other using said computer-language-specific interface implementation;

means for regulating the interaction of said software modules such that only one of each pair of software modules is permitted to initiate communication with the other, and the other software module of said pair is only permitted to respond to queries of said initiating software module; and

means for executing said plurality of software modules on said computing system using said computer-language-specific interface implementation for communicating data between said software modules.

28. The system of claim 27 wherein said means for defining said computer-language-independent interface specification to govern the interaction of said plurality of software modules across one or more processors further comprises:

means for providing the name of a parent specification whenever said interface specification is based upon said parent specification.

29. The system of claim 27 wherein said means for converting said computer-language-independent interface specification into said computer-language-specific interface implementation comprises a stub-code generation tool, regardless of whether said software modules are linked statically or dynamically.

30. The system of claim 27 wherein said means for creating functional software modules from said interface specification further comprises an interface agent.

31. The system of claim 30 wherein said interface agent additionally comprises a despatcher that receives a signal from a communication party, parses said signal into an address and a message, strips said address from said signal and distributes said message of said signal based upon said address to a recipient software module.

32. The system of claim 27 wherein said means for creating functional software modules from said interface specification additionally includes a protocol supervisor operating as a state machine that supervises obedience to protocol rules predefined in said interface specification.

33. The system of claim 27 further comprising central storage means within a trader module that is part of the kernel of the operating system of said computing system for storing information about all interfaces that have been implemented for software modules within said computing system.

34. The system of claim 27 wherein said computing system is a distributed or modular computing system of the type commonly used in telecommunications environments.