Gateway control protocol: Resource management packages
|Publication Date:||1 March 2009|
This Recommendation contains packages that allow a media gateway controller (MGC) and a media gateway (MG) to work together to allow the MG to manage its resources in the most efficient manner possible. Three approaches are defined: rules-based, configuration, and abstract.
In the rules-based approach, the MG expects the MGC to behave in a particular manner in order to manage resources. For example, the MG may expect that, for optimal resource allocation, once a stream is assigned to a particular media (e.g., audio), it will not change it to another media (e.g., video).
In the configuration approach, the MGC indicates the expected characteristics of the Context in terms of the actual resources required. This could be a number of a particular type of Termination. For example, the MGC could indicate that for a particular Context, it may have up to five receive-only Terminations.
An "abstract" approach is also provided, whereby the MGC indicates a specific resource management requirement via a single codepoint which then relates directly to a particular H.248 configuration. For example, the MGC could indicate "conference listener" and this would then map directly to a send-only Termination configuration and to a particular type of audio codec.
The description of MG internal resource structures is out of scope of this Recommendation.
This Recommendation assumes that the MGC is responsible for
determining for how long the resources are reserved, and thus is
responsible for requesting and clearing the resources. This is in
keeping with the H.248 LocalControl descriptor