Automatic transport detection by attempting to establish communication session using list of possible transports and corresponding media dependent modules

• US 5,754,765 A
• Filed: 06/06/1995
• Issued: 05/19/1998
• Est. Priority Date: 11/24/1993
• Status: Expired due to Term

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Prasad, Rama, Danneels, Gunner, Gates, Gregory
• Primary Examiner(s): DINH, DUNG C
• Application Number:
  US08/467,279
• Time in Patent Office: 1,078 Days
• Field of Search: 395/200.12, 395/200.2, 395/650, 395/700, 395/500, 395/682, 395/200.1, 395/200.04, 370/261, 370/402, 370/260, 370/265, 370/254
• US Class Current: 709/222
• CPC Class Codes: G06T 1/00 General purpose image data processing
• CPC Class Codes: G06T 2200/16 involving adaptation to the client's capabilities
• CPC Class Codes: H04L 12/1813 for computer conferences, e.g. chat rooms instant messaging H04L51/04; protocols for multimedia communication H04L65/1101; arrangements for multi-party communication H04L65/403; telephonic conference arrangements H04M3/56; television conference systems H04N7/15
• CPC Class Codes: H04M 3/567 Multimedia conference systems
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04N 21/643 Communication protocols network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP], H04L65/65
• CPC Class Codes: H04N 7/15 Conference systems

Abstract

The transports available in a local computer system for communicating with a remote computer system are automatically determined at either install time or run time. At install time, a list of transports supported by the local computer system is used to determine which supported transports are actually installed in the local computer system and the media dependent modules (MDMs) that correspond to those installed transports. At run time, a list of the installed transports and corresponding MDMs is used to determine which installed transports (and corresponding MDMs) can actually be used for an impending communications session with the remote computer system.

Claims

1. A computer-implemented process for transport detection, comprising the steps of

(a) providing a list of possible transports over which a local computer system communicates with at least one remote computer system;

and

(b) automatically identifying, at run time, a subset of the list of possible transports that are available for communications with the remote computer system, wherein;

the list of possible transports corresponds to transports installed in the local computer system and corresponding MDMs;

the subset of the list of possible transports corresponds to transports that can be used by the local computer system for an impending communications session with the remote computer system; and

for each installed transport, step (b) comprises the steps of;

(1) attempting, by a network independent layer of the local computer system, to begin the communications session using a specified transport by calling a begin-session function into a network dependent layer of the local computer system;

(2) attempting, by the network dependent layer, to begin the communications session using the list of installed transports and corresponding MDMs, by loading an MDM corresponding to the specified transport and instructing the MDM to attempt to communicate with a corresponding network stack;

(3) if the MDM'"'"'s attempt to communicate with the corresponding network stack is successful, then identifying the specified transport as one of the transports that can be used by the local computer system for the impending communications session with the remote computer system; and

(4) if the MDM'"'"'s attempt to communicate with the corresponding network stack is unsuccessful, then rejecting the specified transport as one of the transports that can be used by the local computer system for the impending communications session with the remote computer system.

2. The process of claim 1, wherein:

step (b)(1) comprises the steps of;

(A) calling, by an application of the local computer system, into a conference manager of the local computer system to begin the communications session using the specified transport;

(B) calling, by the conference manager, into a conferencing application programming interface (API) of the local computer system to begin the communications session using the specified transport;

(C) calling, by the conferencing API, into a communications API of the local computer system to begin the communications session using the specified transport;

(D) causing, by the communications API, a data ink manager corresponding to the specified transport to be loaded; and

(E) calling, by the communications API, into the data link manager to begin the communications session;

step (b)(2) comprises the steps of;

(A) causing, by the data link manager, the MDM to be loaded using the list of installed transports and corresponding MDMs;

(B) calling, by the data link manager, into the MDM to begin the communications session; and

(C) attempting, by the MDM, to communicate with the corresponding network stack;

step (b)(3) comprises the step of passing a success message from the MDM to the data link manager to the communications API to the conferencing API to the conference manager to the application; and

step (b)(4) comprises the steps of;

(A) passing a failure message from the MDM to the data link manager to the communications API to the conferencing API to the conference manager to the application;

(B) causing, by the data link manager, the MDM to be unloaded; and

(C) causing, by the communications API, the data link manager to be unloaded.

3. The process of claim 1, further comprising the step of displaying, by the application, a list of callee addresses for the impending communications session, wherein each callee address corresponds to one of the transports that can be used for the impending communications session as identified in step (b).

4. The process of claim 1, wherein the installed transports and corresponding MDMs are identified in an initialization file.

5. The process of claim 1, wherein:

the installed transports comprise at least one of an ISDN transport and a LAN transport;

the installed transports comprise one or more LAN transports conforming to one or more LAN-transport standards; and

the one or more LAN transports comprise two or more LAN products conforming to a single LAN-transport standard.

6. An apparatus for transport detection, comprising:

(a) a list of possible transports over which a local computer system communicates with at least one remote computer system; and

(b) a network independent layer and a network dependent layer of the local computer system, adapted to automatically identify, at run time, a subset of the list of possible transports that are available for communications with the remote computer system, wherein;

the list of possible transports corresponds to transports installed in the local computer system and corresponding MDMs;

the subset of the list of possible transports corresponds to transports that can be used by the local computer system for an impending communications session with the remote computer system; and

for each installed transport;

the network independent layer attempts to begin the communications session using a specified transport by calling a begin-session function into the network dependent layer;

the network dependent layer attempts to begin the communications session using the list of installed transports and corresponding MDMs, by loading an MDM corresponding to the specified transport and instructing the MDM to attempt to communicate with a corresponding network stack;

if the MDM'"'"'s attempt to communicate with the corresponding network stack is successful, then the network independent layer identifies the specified transport as one of the transports that can be used by the local computer system for the impending communications session with the remote computer system; and

if the MDM'"'"'s attempt to communicate with the corresponding network stack is unsuccessful, then the network independent layer rejects the specified transport as one of the transports that can be used by the local computer system for the impending communications session with the remote computer system.

7. The apparatus of claim 6, wherein:

the network independent layer comprises an application, a conference manager, a conferencing application programming interface (API), and a communications API;

the network dependent layer comprises a data link manager, the MDM, and the corresponding network stack;

for each installed transport;

the application calls into the conference manager to begin the communications session using the specified transport;

the conference manager calls into the conferencing API to begin the communications session using the specified transport;

the conferencing API calls into the communications API to begin the communications session using the specified transport;

the communications API causes the data link manager to be loaded; and

the communications API calls into the data link manager to begin the communications session;

the data ink manager causes the MDM to be loaded using the list of installed transports and corresponding MDMs;

the data link manager calls into the MDM to begin the communications session; and

the MDM attempts to communicate with the corresponding network stack;

if the MDM'"'"'s attempt to communicate with the corresponding network stack is successful, then a success message is passed from the MDM to the data link manager to the communications API to the conferencing API to the conference manager to the application; and

if the MDM'"'"'s attempt to communicate with the corresponding network stack is unsuccessful, then;

a failure message is passed from the MDM to the data link manager to the communications API to the conferencing API to the conference manager to the application;

the data link manager causes the MDM to be unloaded; and

the communications API causes the data link manager to be unloaded.

8. The apparatus of claim 6, wherein the application displays a list of callee addresses for the impending communications session, wherein each callee address corresponds to one of the transports that can be used for the impending communications session.

9. The apparatus of claim 6, wherein the installed transports and corresponding MDMs are identified in an initialization file.

10. The apparatus of claim 6, wherein:

the installed transports comprise at least one of an ISDN transport and a LAN transport;

the installed transports comprise one or more LAN transports conforming to one or more LAN-transport standards; and

the one or more LAN transports comprise two or more LAN products conforming to a single LAN-transport standard.

11. A computer program embodied in a tangible medium, wherein, when the computer program is loaded into and executed by a local computer system:

the local computer system provides a list of possible transports over which the local computer system communicates with at least one remote computer system; and

the local computer system automatically identifies, at run time, a subset of the list of possible transports that are available for communications with the remote computer system, wherein;

the list of possible transports corresponds to transports installed in the local computer system and corresponding MDMs;

the subset of the list of possible transports corresponds to transports that can be used by the local computer system for an impending communications session with the remote computer system; and

the local computer system comprises a network independent layer of the local computer system and a network dependent layer of the local computer system; and

for each installed transport;

the network independent layer attempts to begin the communications session using a specified transport by calling a begin-session function into the network dependent layer;

the network dependent layer attempts to begin the communications session using the list of installed transports and corresponding MDMs, by loading an MDM corresponding to the specified transport and instructing the MDM to attempt to communicate with a corresponding network stack;

if the MDM'"'"'s attempt to communicate with the corresponding network stack is successful, then the local computer system identifies the specified transport as one of the transports that can be used by the local computer system for the impending communications session with the remote computer system; and

if the MDM'"'"'s attempt to communicate with the corresponding network stack is unsuccessful, then the local computer system rejects the specified transport as one of the transports that can be used by the local computer system for the impending communications session with the remote computer system.

12. The computer program of claim 11, wherein:

the network independent layer comprises an application, a conference manager, a conferencing application programming interface (API), and a communications API;

the network dependent layer comprises a data link manager, the MDM, and the corresponding network stack;

for each installed transport;

the application calls into the conference manager to begin the communications session using the specified transport;

the conference manager calls into the conferencing API to begin the communications session using the specified transport;

the conferencing API calls into the communications API to begin the communications session using the specified transport;

the communications API causes the data link manager to be loaded; and

the communications API calls into the data link manager to begin the communications session;

the data link manager causes the MDM to be loaded using the list of installed transports and corresponding MDMs;

the data link manager calls into the MDM to begin the communications session; and

the MDM attempts to communicate with the corresponding network stack;

if the MDM'"'"'s attempt to communicate with the corresponding network stack is successful, then a success message is passed from the MDM to the data link manager to the communications API to the conferencing API to the conference manager to the application; and

if the MDM'"'"'s attempt to communicate with the corresponding network stack is unsuccessful, then;

a failure message is passed from the MDM to the data link manager to the communications API to the conferencing API to the conference manager to the application;

the data link manager causes the MDM to be unloaded; and

the communications API causes the data link manager to be unloaded.

13. The computer program of claim 11, wherein the application displays a list of callee addresses for the impending communications session, wherein each callee address corresponds to one of the transports that can be used for the impending communications session.

14. The computer program of claim 11, wherein the installed transports and corresponding MDMs are identified in an initialization file.

15. The computer program of claim 11, wherein:

the installed transports comprise at least one of an ISDN transport and a LAN transport;

the installed transports comprise one or more LAN transports conforming to one or more LAN-transport standards; and

the one or more LAN transports comprise two or more LAN products conforming to a single LAN-transport standard.

16. A computer-implemented process for transport detection, comprising the steps of:

(a) providing a list of possible transports over which a local computer system communicates with at least one remote computer system; and

(b) automatically identifying, at install time, a subset of the list of possible transports that are available for communications with the remote computer system, wherein;

the list of possible transports corresponds to transports supported by the local computer system;

the subset of the list of possible transports corresponds to transports installed in the local computer system; and

for each supported transport, step (b) comprises the steps of;

(1) loading a media dependent module (MDM) corresponding to the supported transport;

(2) attempting to initialize a network transport stack corresponding to the MDM;

(3) if the attempt to initialize is successful, then identifying the supported transport as one of the installed transports and identifying the MDM as corresponding to the installed transport;

(4) if the attempt to initialize is unsuccessful, then determining if there is another MDM for the supported transport;

(5) if there is another MDM for the supported transport, then repeating steps (1)-(4) for the another MDM; and

(6) if there is not another MDM for the supported transport, then determining that the supported transport is not one of the installed transports.

17. The process of claim 16, wherein step (b) comprises the step of saving the installed transports and corresponding MDMs in an initialization file.

18. The process of claim 16, wherein:

the supported transports comprise at least one of an ISDN transport and a LAN transport;

the supported transports comprise one or more LAN transports conforming to one or more LAN-transport standards; and

the one or more LAN transports comprise two or more LAN products conforming to a single LAN-transport standard.

19. An apparatus for transport detection, comprising:

(a) a list of possible transports over which a local computer system communicates with at least one remote computer system; and

(b) a network independent layer adapted to automatically identify, at install time, a subset of the list of possible transports that are available for communications with the remote computer system, wherein;

the list of possible transports corresponds to transports supported by the local computer system;

the subset of the list of possible transports corresponds to transports installed in the local computer system; and

for each supported transport, the network independent layer;

(1) loads a media dependent module (MDM) corresponding to the supported transport;

(2) attempts to initialize a network transport stack corresponding to the MDM;

(3) identifies the supported transport as one of the installed transports and identifying the MDM as corresponding to the installed transport, if the attempt to initialize is successful;

(4) determines if there is another MDM for the supported transport, if the attempt to initialize is unsuccessful;

(5) repeats (1)-(4) for the another MDM, if there is another MDM for the supported transport; and

(6) determines that the supported transport is not one of the installed transports, if there is not another MDM for the supported transport.

20. The apparatus of claim 19, wherein the network independent layer saves the installed transports and corresponding MDMs in an initialization file.

21. The apparatus of claim 19, wherein:

the supported transports comprise at least one of an ISDN transport and a LAN transport;

the supported transports comprise one or more LAN transports conforming to one or more LAN-transport standards; and

the one or more LAN transports comprise two or more LAN products conforming to a single LAN-transport standard.

22. A computer program embodied in a tangible medium, wherein, when the computer program is loaded into and executed by a local computer system:

the local computer system provides a list of possible transports over which the local computer system communicates with at least one remote computer system; and

the local computer system automatically identifies, at install time, a subset of the list of possible transports that are available for communications with the remote computer system, wherein;

the list of possible transports corresponds to transports supported by the local computer system;

the subset of the list of possible transports corresponds to transports installed in the local computer system; and

for each supported transport, the local computer system;

(1) loads a media dependent module (MDM) corresponding to the supported transport;

(2) attempts to initialize a network transport stack corresponding to the MDM;

(3) identifies the supported transport as one of the installed transports and identifying the MDM as corresponding to the installed transport, if the attempt to initialize is successful;

(4) determines if there is another MDM for the supported transport, if the attempt to initialize is unsuccessful;

(5) repeats (1)-(4) for the another MDM, if there is another MDM for the supported transport; and

(6) determines that the supported transport is not one of the installed transports, if there is not another MDM for the supported transport.

23. The computer program of claim 22, wherein the local computer system saves the installed transports and corresponding MDMs in an initialization file.

24. The computer program of claim 22, wherein:

the supported transports comprise at least one of an ISDN transport and a LAN transport;

the supported transports comprise one or more LAN transports conforming to one or more LAN-transport standards; and

the one or more LAN transports comprise two or more LAN products conforming to a single LAN-transport standard.