H.248 Bearer Path Setup via Event Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current H.248 protocol does not support the setup or teardown of a bearer path when a Media Gateway (MG) and a Media Gateway Controller (MGC) serve as data receivers, limiting their ability to implement sessions with guaranteed resources.
Innovation Solution
The method involves extending the H.248 protocol to enable MG and MGC to report events and receive resource reservation decisions, allowing them to process bearer paths and initiate RSVP requests for setup and teardown, using new events and signals such as Path Request (PR), Resource Reservation Indication (RI), Path Error Indication (PEI), Reservation Error (RE), Reservation Confirm (RC), and Reservation Tear Indication (RTI) to manage bearer paths efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If H.248 protocol is used for MG and MGC communication, then call control and service bearing are separated effectively, but bearer path setup and teardown are not supported when MG and MGC serve as data receivers
Solution Approach 1:
The patent segments the H.248 protocol into two functional parts: the original call control mechanisms remain unchanged, while a new bearer path management subsystem is added. This subsystem includes separate event types (Path Request, Path Error, Reservation Confirm, Reservation Tear) and signal types (Resource Reservation Indication, Reservation Tear Indication) that operate independently alongside existing H.248 operations, allowing bearer path setup without disrupting established call control functionality.
Solution Approach 2:
The patent introduces event reports as intermediary messages between MG and MGC for bearer path management. When an MG receives a path setup request, it reports a Path Request event to the MGC, which then processes resource allocation and responds with appropriate signals. This intermediary event mechanism enables bearer path setup while maintaining the existing H.248 command-response framework.
2Reliability
If H.248 protocol is extended to support bearer path setup, then MG and MGC can implement sessions with guaranteed resources, but the protocol structure becomes more complex
Solution Approach 1:
The patent extracts bearer path management functionality from the general H.248 protocol flow by creating dedicated event types and signal types. The Path Request event, Path Error event, Reservation Confirm event, and Reservation Tear event are extracted as separate notification mechanisms, while Resource Reservation Indication and Reservation Tear Indication signals are extracted as separate command types. This extraction allows resource guarantee capabilities to be added without integrating bearer path setup into every H.248 operation.
Solution Approach 2:
The patent creates a universal event reporting mechanism that serves multiple purposes: existing H.248 events continue to handle call control notifications, while new event types (Path Request, Path Error, Reservation Confirm, Reservation Tear) handle bearer path management. Similarly, the command structure supports both traditional H.248 operations and new resource reservation functions through the Resource Reservation Indication and Reservation Tear Indication signals, making the protocol multi-functional without requiring separate protocol stacks.
3Adaptability or versatility
If new events and signals are added to H.248 protocol, then bearer path management is enabled, but implementation and maintenance difficulty increases
Solution Approach 1:
The patent implements dynamic event reporting where the MG determines which events to report based on its operational state and received requests. The event types (Path Request, Path Error, Reservation Confirm, Reservation Tear) are dynamically activated only when bearer path operations are needed, rather than being constantly processed. This dynamic approach allows session implementation capability to be added without requiring continuous processing of all event types, reducing implementation complexity.
Data Source
AI summary
A method and apparatus for implementing a bearer path are disclosed. The method includes the following steps: a Media Gateway (MG) reports a preset Path Request (PR) event to a Media Gateway Controller (MGC) according to a received request message related to a bearer path, requesting the MGC to deliver a resource reservation decision; the MG receives the resource reservation decision sent by the MGC; and the MG processes the bearer path according to the resource reservation decision. The present disclosure is applicable to setup of a bearer path.