Internetworking Gateway Dynamic Payload Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The interoperability issues between SIP and H.323/H.320/H.324 VoIP protocols arise due to mismatched payload handling directions, leading to interoperability problems in internetworking, particularly in devices like TDM gateways and session border controllers.

Innovation Solution

An apparatus and method that handle dynamic payloads by configuring messages to include information about the payload type from one protocol to another, allowing for seamless communication between nodes using different protocols, such as H.323 and SIP, through an internetworking gateway that specifies and enforces payload types in capabilities and media establishment messages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional SIP and H.323/H.320/H.324 protocols are used for internetworking, then basic connections can be established, but payload handling mismatch causes interoperability problems

Engineering Contradiction:
ImproveinteroperabilityVSAvoidpayload handling compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an internetworking gateway that acts as an intermediary between SIP and H.323/H.320/H.324 protocols. The gateway receives requests from one protocol, extracts payload type information, configures appropriate messages in the target protocol, and forwards them. This mediator resolves the payload handling mismatch by translating between SIP's receiving-direction specification and H.323's transmitting-direction specification, enabling reliable interoperability while supporting diverse payload types.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If dynamic payloads with new audio and video codecs are supported, then system versatility improves, but payload handling complexity increases

Engineering Contradiction:
Improvecodec supportVSAvoidpayload handling mechanism
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent handles dynamic payloads by extracting and mapping payload type parameters between protocols. The gateway identifies payload type information in incoming requests, transforms the parameter representation to match the target protocol's expectations, and includes it in outgoing messages. This parameter transformation approach enables support for diverse audio and video codecs without requiring complex protocol-specific processing for each codec type, thereby maintaining relatively simple device architecture while achieving high versatility.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If payload type information is mapped between protocols, then interoperability improves, but call setup delay may increase due to additional processing

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidcall setup delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs payload type information mapping during the initial message exchange phase of call setup. The gateway extracts payload type information from incoming requests and configures the corresponding target protocol messages in advance before forwarding them. By completing the payload type reconciliation during the earliest possible stage of interaction, the system avoids repeated processing delays later in the call setup sequence, thereby minimizing overall call setup delay while ensuring protocol compatibility.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8687624B2Apparatus and method to handle dynamic payloads in a heterogeneous network
Publication Date: 2014.04.01 CISCO TECHNOLOGY INC
  • US8687624B2 patent drawing
  • US8687624B2 patent drawing
  • US8687624B2 patent drawing

AI summary

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.