Generic Transport layer

• US 20040057464A1
• Filed: 09/23/2002
• Published: 03/25/2004
• Est. Priority Date: 09/23/2002
• Status: Abandoned Application

• Current Assignee: Wind River Systems Incorporated (Aptiv PLC)
• Original Assignee: Wind River Systems Incorporated (Aptiv PLC)
• Inventors: Sanders, Michael
• Application Number:
  US10/252,989
• Publication Number:
  US 20040057464A1
• Time in Patent Office: Days
• US Class Current: 370/469
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 7/1225 Details of core network interconnection arrangements

Abstract

A generic transport layer interface is described, to connect protocol independent communications applications with specific transport layer protocols. An abstraction layer core is provided, where data received from the communications applications is used to generate data that can be sent to the specific transport layer protocols. A protocol independent transport interface connects the abstraction core to the communications applications, and a transport specific interface connects the abstraction core to the transport layer protocols. Transport layer protocols such as UDP, TCP and SCTP are supported.

Claims

1. An abstraction layer to connect a communications application to a computer network, comprising:

a generic transport layer core, having an abstraction element to generate interfaces to transport layer protocols;

a transport specific interface relating the generic transport layer core to transport layer protocol applications; and

a protocol independent transport interface relating the generic transport layer core to the communications application.

2. The abstraction layer according to claim 1, further comprising a primitive exchange interface of the protocol independent transport interface configured to exchange data elements between the generic transport layer core and the communications application.

3. The abstraction layer according to claim 1, further comprising a service binding interface of the protocol independent transport interface configured to provide binding of the communications application with the generic transport layer core.

4. The abstraction layer according to claim 1, further comprising a delivery agent of the protocol independent transport interface, the delivery agent mediating exchange data between the generic transport layer core and applications registered with the delivery agent.

5. The abstraction layer according to claim 4, wherein the delivery agent is configured to receive a signal indicating availability of a service, to receive a signal indicating a request for service of a client, and to form a path for data exchange between the client and the service.

6. The abstraction layer according to claim 1, further comprising a system services interface to a system library of functions to manage operating system services.

7. The abstraction layer according to claim 1, further comprising a management interface to a system management entity configured to manage configuration and initialization tasks.

8. The abstraction layer'"'"'according to claim 1, wherein the generic abstraction layer core is configured to receive protocol independent data from the communications application, to generate transport protocol specific data based at least in part on the protocol independent data, and to send the transport protocol specific data to the transport layer protocol applications.

9. A system of transmitting data over a network, comprising:

a generic transport layer adapted to generate protocol specific data based at least in part on transport independent inputs, and to generate transport independent data based at least in part on protocol specific inputs;

a protocol independent transport interface configured to transmit the transport independent inputs and transport independent data between applications and the generic transport layer; and

a transport specific interface configured to transmit the protocol specific data and protocol specific inputs between the generic transport layer and transport layer protocol applications.

10. The system according to claim 9, further comprising delivery agents configured to mediate exchange of transport independent inputs and data between the applications and the generic transport layer.

11. The system according to claim 9, wherein the transport specific interface is configured to provide the protocol specific data to an internet protocol application.

12. The system according to claim 9, wherein the transport layer protocol applications comprise at least one of a UDP application, TCP application and SCTP application.

13. The system according to claim 9, wherein the applications comprise at least one of MGCP applications, SIP applications and Megaco applications.

14. The system according to claim 10, wherein the delivery agent is further configured to form client-service bindings between the applications and the generic transport layer.

15. The system according to claim 14, further comprising service access points configured to collect information identifying the bindings and provide the information to distinguish between the bindings.

16. The system according to claim 14, wherein the delivery agent is further configured to exchange transport independent inputs from the application to the generic transport layer.

17. A method of transmitting data comprising:

receiving transport independent inputs from applications;

processing the transport independent inputs to generate protocol specific data;

providing the protocol specific data to transport layer protocol applications;

receiving protocol specific inputs from the transport layer protocol applications;

processing the protocol specific inputs to generate transport independent data; and

providing the transport independent data to the applications.