Flexible mechanism for implementing the middleware of a data distribution system over multiple transport networks

• US 8,671,135 B1
• Filed: 04/24/2006
• Issued: 03/11/2014
• Est. Priority Date: 04/24/2006
• Status: Active Grant

• Current Assignee: Real-Time Innovations, Inc.
• Original Assignee: Real-Time Innovations, Inc.
• Inventors: Joshi, Rajive, Pardo-Castellote, Gerardo, Thiebaut, Stefaan Sonck, Choi, Henry
• Primary Examiner(s): Zele, Krista M.
• Assistant Examiner(s): Vostal, Ondrej
• Application Number:
  US11/410,511
• Time in Patent Office: 2,878 Days
• Field of Search: 709/202
• US Class Current: 709/202
• CPC Class Codes: H04L 2101/30 Types of network names
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers

Abstract

A method of providing transports for a data distribution middleware over a plurality of transport networks is provided. A data distribution middleware with a pluggable transport layer is provided. A plurality of transport plugins in the transport layer are provided. Aliases are assigned to each of the transport plugins of the plurality of transport plugins, wherein at least one of the transport plugins of the plurality of transport plugins has a plurality of aliases.

Claims

1. A method of providing transports for an Object Management Group'"'"'s (OMG) Data Distribution Service middleware implementation operating over a plurality of transports in a data distribution system, the method comprising:

creating a domain participant in a peer to peer network of computer systems in the OMG Data Distribution Service middleware on the data distribution system;

creating a transport plugin for the domain participant in the OMG Data Distribution Service middleware on the data distribution system;

using an application programming interface (API) to register the transport plugin to be used by the Data Distribution Service middleware and the domain participant;

using the API provided by the transport plugin from the Data-Distribution Service middleware to configure the transport and the resources used by the transport to communicate on a specific transport network;

using the API provided by the transport plugin from the Data-Distribution Service middleware to send data via the transport; and

using the API provided by the transport plugin from the Data-Distribution Service middleware to receive data via the transport.

2. The method, as recited in claim 1, further comprising:

providing an OMG Data Distribution Service middleware implementation with a pluggable transport layer; and

providing a plurality of transport plugins in the transport layer, wherein each transport plugin with unicast support uses a locator comprising a transport class id, a subnet identifier, transport address, and port number, wherein the subnet identifier is transport independent and the transport address is transport specific and meaningful only with in the transport network.

3. The method as recited in claim 2, further comprising providing a plurality of transport plugins in the transport layer, wherein each transport plugin with multicast support uses a locator comprising a transport class id, and a multicast address, and port number wherein the multicast address is transport independent.

4. The method, as recited in claim 3, wherein the plurality of transport networks comprises shared memory, IPv6 networks, and IPv4 networks.

5. The method, as recited in claim 4, wherein the plurality of transport networks further comprises serial interconnect networks and bus-based networks.

6. The method, as recited in claim 1, further comprising:

using the API provided by the transport plugin to send commands from the OMG Data Distribution Service middleware to the plurality of transport plugins to create send resources and receive resources;

using the API provided by the transport plugin to create the send resources and receive resources before the resources are needed;

keeping and managing the send resources and receive resources in the data distribution middleware core; and

using the API provided by the transport plugin to send requests from the OMG Data Distribution Service middleware to the plurality of transport plugins to share the send resources and receive resources.

7. The method, as recited in claim 6, further comprising sharing the send resources and receive resources for multiple addresses and port numbers, wherein each transport plugin independently decides whether or not to share a send resource or a receive resource for a given address and port number.

8. The method, as recited in claim 7, wherein the transport plugin can decide whether to copy a received message into a buffer provided by the middleware core or whether to loan an internal buffer provided by the transport plugin.

9. The method, as recited in claim 6, wherein a transport plugin determines the interfaces on which it can receive messages.

10. The method, as recited in claim 9, further comprising allowing a user to direct a transport plugin to not report specified interfaces.

11. The method, as recited in claim 6, further comprising allowing a transport plugin decide resources needed to send and receive messages.

12. The method, as recited in claim 1, further comprising:

providing a sending routing table to specify the address ranges served by a transport plugin for outgoing messages; and

providing a receiving routing table to specify the address ranges served by a transport plugin for incoming messages.

13. The method, as recited in claim 12, wherein the sending routing table links address ranges with the transport plugins by specifying the address ranges served by a transport plugin for outgoing messages.

14. The method, as recited in claim 13, further comprising providing encryption in the plurality of transport plugins.

15. The method, as recited in claim 1, further comprising assigning aliases to each of the transport plugins of the plurality of transport plugins.

16. The method, as recited in claim 15, wherein at least one of the transport plugins of the plurality of transport plugins has a plurality of aliases.

17. The method, as recited in claim 16, wherein at least one of the aliases is assigned to a plurality of transport plugins of the plurality of transport plugins.

18. The method, as recited in claim 1, further comprising:

providing a string based addressing, wherein the string based addressing comprises a transport independent substring and a transport dependent substring; and

translating the string based addressing to a numeric address representation using an address mapping method provided by the transport plugin.

19. The method, as recited in claim 1, further comprising:

providing built in transport plugins that are automatically registered on the Domain Participant; and

generating default network addresses for the built in transport plugins.

20. The method, as recited in claim 1, wherein the registration involves specifying network address and aliases.

21. The method, as recited in claim 20, wherein the network address is chosen so that the unicast address of an interface (including the network address, transport address) is unique in the data distribution domain.

22. The method, as recited in claim 20, further comprising allowing a user to direct a transport plugin to not report specified interfaces.

23. A method of providing transports for an Object Management Group'"'"'s (OMG) Data Distribution Service middleware operating over a plurality of transports in a data distribution system, the method comprising:

providing an OMG Data Distribution Service middleware with a pluggable transport layer in the data distribution system in a peer to peer network of computer systems;

providing a plurality of transport plugins in the transport layer in the data distribution system wherein each individual transport plug-in is configured to communicate on a specific transport network; and

assigning aliases to each of the transport plugins of the plurality of transport plugins, wherein at least one of the transport plugins of the plurality of transport plugins has a plurality of aliases.

24. The method, as recited in claim 23, wherein at least one alias refers to plurality of transport plugins.

25. The method, as recited in claim 23, wherein at least one of the aliases is assigned to a plurality of transport plugins of the plurality of transport plugins.

26. The method, as recited in claim 23, further comprising:

creating a plurality of OMG Data Distribution Service entities, such as domain participants, publishers, subscribers, data writers and data readers; and

associating the Transport Qos Policies with the OMG Data Distribution Service entities, wherein Transport QosPolicies use aliases to refer to a plurality of transport plugins.

27. A method of providing transports for a data distribution middleware over a plurality of transport networks in an OMG Data Distribution Service in a data distribution system, the method comprising:

providing an OMG Data Distribution Service middleware with a pluggable transport layer in the data distribution system in a peer to peer network of computer systems;

providing a plurality of transport plugins in the data distribution system wherein each individual transport plug-in is configured to communicate on a specific transport network;

providing a plurality of domain participants; and

associating the plurality of transport plugins with the plurality of domain participants.

28. The method, as recited in claim 27 further comprising:

providing routing of messages to the plurality of transport plugins in the plurality of domain participants; and

providing encryption using a plurality of transport plugins in the plurality of domain participants.

29. A method for creating transport plugins in an Object Management Group'"'"'s (OMG) Data Distribution Service middleware, comprising:

using an application programming interface (API) to send commands from the OMG Data Distribution Service middleware on a data distribution system in a peer to peer network of computer systems to a plurality of transport plugins to create send resources and receive resources wherein each individual transport plug-in is configured to communicate on a specific transport network;

creating the send resources and receive resources before the resources are needed;

keeping and managing the send resources and receive resources in the data distribution middleware core; and

using the API to send requests from the data distribution middleware to the plurality of transport plugins to share the send resources and receive resources.

30. The method, as recited in claim 29, further comprising sharing the send resources and receive resources for multiple addresses and port numbers, wherein each transport plugin independently decides whether or not to share a send resource or a receive resource for a given address and port number.

31. The method, as recited in claim 29, wherein a transport plugin determines the interfaces on which it can receive messages.

32. The method, as recited in claim 29, further comprising allowing a transport plugin decide the resources needed to send and receive messages.

33. Non-transitory computer readable media for providing transports for an OMG Data Distribution Service middleware implementation over a plurality of transport networks, comprising:

computer readable code for creating a domain participant in a peer to peer network of computer systems;

computer readable code for creating a transport plugin for the domain participant;

computer readable code with application programming interfaces (APIs) for registering the transport plugin with the domain participant;

computer readable code with APIs provided by the transport plugin from the Data-Distribution Service middleware to configure the transport and the resources used by the transport to communicate on a specific transport network;

computer readable code with APIs provided by the transport plugin from the Data-Distribution Service middleware to send data via the transport; and

computer readable code with APIs provided by the transport plugin from the Data-Distribution Service middleware to receive data via the transport.

34. The non-transitory computer readable media, as recited in claim 33, further comprising:

computer readable code for providing an OMG Data Distribution Service middleware implementation with a pluggable transport layer; and

computer readable code providing a plurality of transport plugins in the transport layer, wherein each transport plugin with unicast support uses a locator comprising a transport class id, a subnet identifier, transport address, and port number, wherein the subnet identifier is transport independent and the transport address is transport specific and meaningful only with in the transport network.

35. The computer readable media as recited in claim 34, further comprising computer readable code for providing a plurality of transport plugins in the transport layer, wherein each transport plugin with multicast support uses a locator comprising a transport class id, and a multicast address, and port number wherein the multicast address is transport independent.

36. The computer readable media, as recited in claim 35, wherein the plurality of transport networks comprises shared memory, IPv6 networks, and IPv4 networks.

37. Non-transitory computer-readable media comprising readable code for providing transports for an OMG Data Distribution Service middleware over a plurality of transport networks, comprising:

computer readable code for providing an OMG Data Distribution Service middleware with a pluggable transport layer in a peer to peer network of computer systems;

computer readable code for providing a plurality of transport plugins in the transport layer wherein each individual transport plug-in is configured to communicate on a specific transport network; and

computer readable code for assigning aliases to each of the transport plugins of the plurality of transport plugins, wherein at least one of the transport plugins of the plurality of transport plugins has a plurality of aliases.

38. The non-transitory computer readable media, as recited in claim 37, wherein at least one alias refers to plurality of transport plugins.

39. The non-transitory computer readable media, as recited in claim 37 wherein at least one of the aliases is assigned to a plurality of transport plugins of the plurality of transport plugins.

40. The non-transitory computer readable media, as recited in claim 37, further comprising:

computer readable code for creating a plurality of OMG Data Distribution Service entities, such as domain participants, publishers, subscribers, data writers and data readers; and

computer readable code for associating the Transport Qos Policies with the OMG Data Distribution Service entities, wherein Transport QosPolicies use aliases to refer to a plurality of transport plugins.

41. Non-transitory computer readable media for providing transports for an OMG Data Distribution Service middleware over a plurality of transport networks, comprising:

computer readable code for providing a data distribution middleware with a pluggable transport layer in a peer to peer network of computer systems;

computer readable code for providing a plurality of transport plugins wherein each individual transport plug-in is configured to communicate on a specific transport network;

computer readable code for providing a plurality of domain participants; and

computer readable code for associating the plurality of transport plugins with the plurality of domain participants.

42. The non-transitory computer readable media, as recited in claim 41, further comprising:

computer readable code for providing routing of messages to the plurality of transport plugins in the plurality of domain participants; and

computer readable codes for providing encryption using a plurality of transport plugins in the plurality of domain participants.

43. Non-transitory computer readable media for creating transport plugins, comprising:

computer readable code containing an application programming interface (API) used to send commands from an OMG Data Distribution Service middleware to a plurality of transport plugins to create send resources and receive resources in a peer to peer network of computer systems wherein each individual transport plug-in is configured to communicate on a specific transport network;

computer readable code containing an API to a transport plugin for creating the send resources and receive resources before the resources are needed;

computer readable code for a transport plugin for keeping and managing the send resources and receive resources in the OMG Data Distribution Service middleware; and

computer readable code containing an API for sending requests from the data distribution middleware to the plurality of transport plugins to share the send resources and receive resources.

44. The non-transitory computer readable media, as recited in claim 43, further comprising computer readable code for sharing the send resources and receive resources for multiple addresses and port numbers, wherein each transport plugin independently decides whether or not to share a send resource or a receive resource for a given address and port number.