Apparatus and method to handle dynamic payloads in a heterogeneous network

• US 8,687,624 B2
• Filed: 02/13/2008
• Issued: 04/01/2014
• Est. Priority Date: 02/13/2008
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Kumarasamy, Parameswaran, Parameswaran, Kavithadevi
• Primary Examiner(s): Nawaz, Asad
• Assistant Examiner(s): PATEL, PARTHKUMAR
• Application Number:
  US12/030,759
• Publication Number:
  US 20090201910A1
• Time in Patent Office: 2,239 Days
• Field of Search: 370/352, 370/401, 370/235, 370/248, 370/252, 370/392, 370/389, 379/219, 455/450, 709/227
• US Class Current: 370/352
• CPC Class Codes: H04L 65/102 Gateways arrangements for connecting between networks having differing types of switching systems, e.g. gateways, H04L12/66
• CPC Class Codes: H04L 65/1033 Signalling gateways
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

Various embodiments provide an apparatus and method for handling dynamic payloads in a heterogeneous network. An example embodiment includes a first node interface to receive a first request for data communication from a first node, the first request being coded in a first protocol and including information identifying a first payload type. The example embodiment includes a second node interface to receive a second request for data communication from a second node, the second request being coded in a second protocol and including information identifying a second payload type. The first node interface of the example embodiment configures a message coded in the first protocol to include the information identifying the second payload type and to send the message to the first node.

Claims

1. A method comprising:

receiving a first request for data communication from a first node, the first request being coded in a first protocol, the first request being modified to include information identifying a first payload type;

receiving a second request for data communication from a second node, the second request being coded in a second protocol, the second request being modified to include information identifying a second payload type;

configuring a first message coded in the first protocol to include the information identifying the second payload type, the first message being an Open Logical Channel (OLC) message;

sending the first message to the first node to ascertain a capability of the first node to process the second payload type; and

receiving a first response to the first message from the first node, the first response being sent by the first node as a response to receiving the first message and including information indicative of whether the first node can process a payload of the second payload type.

2. The method as claimed in claim 1 wherein the first protocol is H.323 protocol.

3. The method as claimed in claim 1 wherein the first protocol is Session Initiation Protocol (SIP) protocol.

4. An apparatus comprising:

means for receiving a first request for data communication from a first node, the first request being coded in a first protocol, the first request being modified to include information identifying a first payload type;

means for receiving a second request for data communication from a second node, the second request being coded in a second protocol, the second request being modified to include information identifying a second payload type;

means for configuring a first message coded in the first protocol to include the information identifying the second payload type, the first message being an Open Logical Channel (OLC) message;

means for sending the first message to the first node to ascertain a capability of the first node to process the second payload type; and

means for receiving a first response to the first message from the first node, the first response being sent by the first node as a response to receiving the first message and including information indicative of whether the first node can process a payload of the second payload type.

5. The apparatus as claimed in claim 4 wherein the first protocol is H.323 protocol.

6. The apparatus as claimed in claim 4 wherein the first protocol is Session Initiation Protocol (SIP) protocol.

7. An intermediate gateway apparatus comprising:

a first node interface to receive a first request for data communication from a first node, the first request being coded in a first protocol, the first request being modified to include information identifying a first payload type;

a second node interface to receive a second request for data communication from a second node, the second request being coded in a second protocol, the second request being modified to include information identifying a second payload type; and

the first node interface to configure a first message coded in the first protocol to include the information identifying the second payload type, the first message being an Open Logical Channel (OLC) message, to send the first message to the first node to ascertain a capability of the first node to process the second payload type, and to receive a first response to the first message from the first node, the first response being sent by the first node as a response to receiving the first message and including information indicative of whether the first node can process a payload of the second payload type.

8. The apparatus as claimed in claim 7 wherein the first protocol is H.323 protocol.

9. The apparatus as claimed in claim 7 wherein the first protocol is Session Initiation Protocol (SIP) protocol.

10. A system comprising a plurality of network elements including an originating endpoint, an intermediate gateway and a target endpoint, the intermediate gateway including:

a first node interface to receive a first request for data communication from a first node, the first request being coded in a first protocol, the first request being modified to include information identifying a first payload type;

a second node interface to receive a second request for data communication from a second node, the second request being coded in a second protocol, the second request being modified to include information identifying a second payload type; and

the first node interface to configure a first message coded in the first protocol to include the information identifying the second payload type, the first message being an Open Logical Channel (OLC) message, to send the first message to the first node to ascertain a capability of the first node to process the second payload type, and to receive a first response to the first message from the first node, the first response being sent by the first node as a response to receiving the first message and including information indicative of whether the first node can process a payload of the second payload type.

11. The system as claimed in claim 10 wherein the first protocol is H.323 protocol.

12. The system as claimed in claim 10 wherein the first protocol is Session Initiation Protocol (SIP) protocol.