Process for automatic conversion for porting telecommunications applications from the TCP/IP network to the OSI-CO network, and module used in this process

• US 5,568,487 A
• Filed: 11/28/1994
• Issued: 10/22/1996
• Est. Priority Date: 11/30/1993
• Status: Expired due to Fees

• Current Assignee: Bull Sas (Atos SE)
• Original Assignee: Bull Sas (Atos SE)
• Inventors: Katrantzis, Bernard, Bassier, Jean-Francois, Sitbon, Gerard
• Primary Examiner(s): Olms, Douglas W.
• Assistant Examiner(s): TON, DANG T
• Application Number:
  US08/348,860
• Time in Patent Office: 694 Days
• Field of Search: 370/94.1, 370/94.2, 370/94.3, 370/60, 370/60.1, 370/85.13, 370/79, 370/100.1, 370/110.1, 370/94.3, 370/80, 395/200, 395/600, 395/650, 395/400, 395/425, 395/325, 395/800, 395/200.01, 395/727, 395/728, 395/410, 395/427, 340/825.03
• US Class Current: 370/466
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The invention relates to an address conversion process for porting a telecommunications application APP from the TCP/IP network to the OSI/CO network, and to an address conversion module used in this process. In a known manner, access to the networks is authorized by way of a "socket" interface (SOC) for the TCP/IP network, and an "XTI" interface for the OSI/CO network. In a notable manner, the "socket" interface calls (SC), like a plurality of system cells (SY), are in a first time period oriented, at the moment of the link editing phase prior to obtaining the executable, to a module (W) for automatic address conversion of the library type. This module (W) then performs the conversion of the addresses specific to the TCP/IP network into addresses of the OSI/CO network and enables the passage from the TCP/IP protocol to the OSI/CO protocol. After conversion, the calls are transmitted to the "XTI" interface and can be used directly in the OSI/CO network. Only the calls intended for the TCP/IP network are processed; all other calls (NT) are returned to the system.

Claims

1. A process of address conversion for porting telecommunications applications from a TCP/IP network to an OSI-CO network, access to these networks being authorized by way of a socket interface for the TCP/IP network, and an XTI interface for the OSI-CO network, said process comprising:

trapping socket interface calls, and a plurality of system calls of a read, write, close type, in a first time period, at a moment of a link editing phase prior to obtaining an executable, in an automatic address conversion module of a library type;

converting, by said conversion module, addresses pertaining to the TCP/IP network into addresses of the OSI-CO network so as to enable passage from a TCP/IP protocol to an OSI-CO protocol;

transmitting the system calls to the XTI interface after conversion to be directly used in the OSI-CO network, wherein only the calls intended for the TCP/IP network are processed, and all other calls are returned to the networks.

2. The address conversion process of claim 1, wherein when the call of the socket interface is for the TCP/IP network, a specific resource is first created in a memory in order to preserve a trace of a connection, and the XTI interface is called for opening said connection, said connection being managed by means of a binary searching tree.

3. An address conversion module used in a process of address conversion for porting telecommunications applications from a TCP/IP network to an OSI-CO network wherein said module comprises:

a first submodule forming a main library and containing a mapping table between TCP/IP communication functions and conversion functions included in an input interface of a wrapper;

a second service Submodule for converting IP and OSI addresses;

a third submodule for recording connection information and managing said connection information by means of a binary searching tree; and

a fourth service submodule for processing a specific set of extensions to the networks.

4. The address conversion module of claim 3, wherein the mapping table included in the first submodule furnishes a bijective correspondence, wherein, for any TCP/IP communication function authorized by a socket interface, there is one and only one function in the interface that executes the service demanded by the applications;

and names of calls, a number of parameter arguments of a call, semantics, and chaining together of calls are preserved exactly.

5. The address conversion module of claim 4, wherein the second service submodule for converting addresses also forms a library and performs the conversion between addresses including the network address of a given machine and a port relating to a service accessed, and OSI addresses including a network service access point and a transport selector, said conversion being capable of being done in both directions, either IP addresses to OSI addresses, or OSI addresses to IP addresses.

6. The address conversion module of claim 5, wherein the third submodule for recording connection information managed by the binary searching tree provides an independent service comprising a library enabling optimal recording, sorting, searching and deletion of all significant information elements relating to a given connection.

7. The address conversion modeule of claim 6, wherein the fourth service submodule enables processing of a specific set of extensions to the networks for returning calls that are not intended for the TCP/IP network and accordingly are not converted by the conversion module, to a standard library in the socket interface.