WO2009121249A1 - 一种包公布与应用的控制方法和装置 - Google Patents

一种包公布与应用的控制方法和装置 Download PDF

Info

Publication number
WO2009121249A1
WO2009121249A1 PCT/CN2009/070453 CN2009070453W WO2009121249A1 WO 2009121249 A1 WO2009121249 A1 WO 2009121249A1 CN 2009070453 W CN2009070453 W CN 2009070453W WO 2009121249 A1 WO2009121249 A1 WO 2009121249A1
Authority
WO
WIPO (PCT)
Prior art keywords
package
media gateway
command
mgc
supported
Prior art date
Application number
PCT/CN2009/070453
Other languages
English (en)
French (fr)
Inventor
林扬波
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP09729137.1A priority Critical patent/EP2271034B1/en
Publication of WO2009121249A1 publication Critical patent/WO2009121249A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers

Definitions

  • the present invention relates to the field of communication technologies, and more particularly to a method and apparatus for controlling the publication and application of a package. Background technique
  • the Media Gateway Controller (hereinafter referred to as: MGC) and the Media Gateway (hereinafter referred to as MG) are two key components of the packet network under the service and bearer separation architecture.
  • the MGC is responsible for the service control function.
  • the MG is responsible for the media bearer function, thereby separating the service control plane and the media bearer plane, thereby fully sharing network resources, upgrading equipment and service expansion, and reducing development and maintenance costs.
  • (Media) Gateway Control Protocol is the main protocol for communication between MG and MGC.
  • H.248/MeGaCo Media Gateway Control Protocol
  • MGCP Media Gateway Control Protocol
  • Agreement two protocols.
  • the interaction between the MGC and the MG is done through the Request (Request) and Response (Reply) of the Command in the (Media) Gateway Control Protocol.
  • the parameters of the command also known as descriptors (Descriptor ), are classified into Property, Signal, Event, Statistic, and so on. For convenience, logically related parameters are logically aggregated into packages.
  • a package represents a feature or combination of features for a particular business. As the business evolves, the corresponding functionality will be enhanced or expanded, requiring the package to be enhanced or expanded.
  • a new package can be derived on the basis of the original package, and the original package is also called As a base package, a new package is also called an Extended Package.
  • the MG In order to facilitate MGC's control of the MG, the MG needs to announce its own supported packages to the MGC. Only when the MG announces a packet to the MGC can the MGC apply it to its own control interface with the MG.
  • the above existing mechanism does not involve whether the MG can apply the packet to its control interface with the MGC. If the MG can apply the packet, when the MGC does not support the application due to the MG not being published or not implemented by itself, the message from the MG to which the packet is applied cannot be processed normally.
  • the embodiment of the invention provides a method and a device for controlling the publication and application of a package, which solves the contradiction between the advertisement and the application on the control interface between the media gateway controller and the media gateway under the existing mechanism.
  • the embodiment of the present invention provides a packet advertisement and application control method, including: the media gateway MG receives a first audit command request sent by the media gateway controller MGC, and the first audit command request carries a packet descriptor, indicating that the audit is performed. a package supported by the MG;
  • a first audit command response to the MGC where the first audit command response includes an identifier of a package supported by the MG;
  • the MG selects an application from the identification of the package published by the MG.
  • the embodiment of the invention further provides a media gateway controller, including:
  • a sending unit configured to send a first command request to the media gateway, where the first command request carries a packet descriptor, where the media gateway is required to announce that the media gateway supports Package
  • the receiving unit is configured to receive a first command response that is returned by the media gateway and that is related to the first command request, where the first command response carries an identifier of a packet supported by the media gateway.
  • the embodiment of the invention further provides a media gateway, including:
  • a receiving unit configured to receive a first command request sent by the media gateway controller, where the first command request carries a packet descriptor, where the media gateway is required to advertise the packet supported by the media gateway;
  • a processing unit configured to include, in a first command response returned to the media gateway controller, an identifier of a packet supported by the media gateway, and subsequently in an identifier of a package supported by the published media gateway Select an application;
  • a sending unit configured to send, to the media gateway controller, the first command response corresponding to the first command request, where the first command response includes an identifier of a packet supported by the media gateway.
  • the MG selects an application from the identifiers of the packets that are published by the MG, which prevents the MG from using the unpublished packets and is not supported by the MGC, thereby effectively solving the control interface between the media gateway controller and the media gateway. Announce conflicts with applications. DRAWINGS
  • FIG. 1 is a schematic diagram of networking of an MG and an MGC used in an embodiment of the present invention
  • FIG. 2 is a flowchart of Embodiment 1 of the present invention
  • Embodiment 2 of the present invention is a flow chart of Embodiment 2 of the present invention.
  • FIG. 5 is a flow chart of Embodiment 4 of the present invention.
  • FIG. 6 is a schematic structural diagram of a system according to Embodiment 5 of the present invention. detailed description
  • FIG. 1 is a schematic diagram of networking of an MG and an MGC used in an embodiment of the present invention.
  • the (media) gateway control protocol is the main protocol for communication between the MG and the MGC.
  • the H.248/MeGaCo and MGCP protocols are widely used.
  • Terminations which can be called individual terminals.
  • the terminal is further divided into physical terminals and temporary (Ephemeral) terminals.
  • the former represents some semi-permanent physical entities, such as TDM (Time Division Multiplex) time slots, and the latter represents some temporary applications. Released common resources, such as RTP (Real-time Transport Protocol) streams.
  • the MG as a whole is represented by a special terminal called a root terminal.
  • the association between terminals is abstracted as a context (Context).
  • the context can contain multiple terminals, so the topology is used to describe the interrelationship between the terminals.
  • a null Null
  • Termination and Context the interaction between the service and the bearer is actually the operation of Termination and Context. This is done through the request (Request) and response (Reply) of the command between the MGC and the MG.
  • Command types include Add, Modify, Subtract, Move, AuditValue, AuditCapabilities, Notify, and ServiceChange.
  • Command parameters also known as descriptors (Descriptor ), are classified as Property, Signal, Event, Statistic, and so on. In order to facilitate the logical aggregation of parameters with business relevance into packages.
  • the MGC's control of the MG can be directed to the flow on the terminal or terminal.
  • the terminal state (TerminationState) descriptor is used to include non-stream specific characteristics on the terminal, such as service state (ServiceState), event buffer control (EventBufferControl), and the like.
  • a media-specific feature is included by a media (Media) descriptor, which includes a series of Stream descriptors. Each stream descriptor is for a single stream, and contains local control (LocalControl), local (Local), and remote (Remote) descriptors. Local control The descriptor is used to include flow-related control information such as mode, ReserveGroup, and Reserve Value.
  • the local and remote descriptors are used to include features of the stream received by the local end and the remote end, such as an address and a port, a codec algorithm, and the like, and are in the form of a Session Description Protocol (SDP).
  • SDP Session Description Protocol
  • the package is divided into a base package and an extension package.
  • MG announces its own supported expansion packs to MGC, it can choose whether to publish the corresponding base package.
  • the MGC can apply the base package to its control interface with the MG only if the base package is published by the MG. Otherwise, the MGC can only apply the extension package and cannot apply the base package of the extension package.
  • the network (Network, identified as nt) in H.248 is derived from the base package as a real-time transport protocol (identified as rtp).
  • the length of the nt packet (duration, identified as dur), the number of bytes sent (Octets Sent, identified as os), and the number of received bytes (Octets Received, identified as or) are inherited by the rtp packet, that is, When referenced, rtp/dur, rtp/os, and rtp/or are equivalent to nt/dur, nt/os, and nt/or, respectively.
  • the rtp packet also has its own extended packet number (Packets Sent, identified as ps), the number of received packets (Packets Received, labeled "i is only pr", and the number of lost packets (Package Loss, labeled "i only” Pi ), jitter buffer (Jitter, identified as jit), delay (detailed, identified as delay) statistical parameters, etc., which can only be referenced by rtp/ps, rtp/pr, rtp/pK rtp/jit, rtp/delay.
  • MG publishes nt and rtp packages, Bay 'J rtp/dur, rtp/os, rtp/or and nt/dur, nt/os, nt/or can all be referenced by MGC. If the MG only publishes the rtp package, only rtp/dur, rtp/os, rtp/or can be referenced by the MGC. If the MG cannot apply a base packet because it is not published, the MG can only refer to the base packet of the base packet by replacing the base packet with the corresponding extended package.
  • the MGC does not support the application due to reasons such as not being implemented by itself, When the package is expanded, the message from the MG to which the extension is applied will not be processed normally. Therefore, it is necessary to add an effective mechanism to enable the MGC to control the release and application of the base and extension packages by the MG.
  • Embodiment 1 In order for the MGC to control the application of the MG to the base package and the extension package, it is first necessary to extend the (media) gateway control protocol.
  • the invention will now be described in detail by way of several specific examples.
  • FIG. 2 it is a flowchart of Embodiment 1 of the present invention, which includes the following steps.
  • Step 101 The MG receives an audit command request sent by the MGC, where the MG carries a packet descriptor, which indicates that the MG supports the package.
  • Step 102 The MG includes the identifier of the package supported by itself in the corresponding audit command response returned to the MGC, that is, the package is announced.
  • Step 103 The MGC and the MG apply the identifier of the package published by the MG on the control interface between them.
  • the specific operation may be as follows:
  • the MGC and the MG respectively save the identifiers of the packets published by the MG, and subsequently select applications from the identifiers of the saved packets as needed. It avoids the MG's use of unpublished packets and is not supported by MGC, thus effectively solving the contradiction between the announcement and application of the control interface between the media gateway controller and the media gateway.
  • Embodiment 2 :
  • the packet Since the packet is divided into a base package and an extension package, whether the base package is also announced when the extension package is published will determine whether the control interface between the MGC and the MG must use the identifier of the extension package for the reference of the package element of the base package.
  • This embodiment uses a property (Property) to indicate whether the base package is also published when the extension package is published. This attribute can be defined in an existing package or in a new package, in the format of "package ID/attribute ID".
  • the new package is named "Package Identifier Publishing and Applicatiion (labeled as pipa) package", and the attribute is named “Base Package Publishing” (base package publishing, standard port, bpp),, to " The format of pipa/bpp" is used.
  • This attribute can be used in the TerminationState descriptor for both the root (Root) terminal representing the MG as a whole and the individual terminal application in the MG.
  • the attribute is an Enumeration type, and the value can be "Both”, “Extension” or "Opt", indicating that the base package identifier and the extension package identifier are both announced. Only the extension package identifier is advertised, or whether the base package identifier is published depends on the MG, and the default value (that is, the attribute is not set) is "optional". Because a package is likely to be both a foundation The package is an extension package, so the so-called announcement of its base package identifier is only for its expansion package. For non-extended packages, such as the base package of a standalone (Stand Alone) package or other packages, it does not apply.
  • the MGC When the MGC needs to control whether the MG publishes the extension package or not, the MGC sets the above bpp attribute to the MG.
  • the MGC can transmit the attribute through commands such as Add, Move, Modify, Subtract, etc., and can set the entire MG represented by the root terminal or individual terminals in the MG. Then, when the MGC sends an audit request for the packet descriptor to the MG, the MG, when the corresponding audit response returned to the MGC includes the identifier of the package supported by the MG, determines whether the extended package included therein also corresponds according to the attribute setting.
  • the ground includes its base package.
  • Step 201 The MGC sends a command to the MG to set a basic packet advertisement attribute to the MG for a specific terminal on the MG.
  • the MGC can carry the base packet advertisement attribute to the MG in the TerminationState descriptor for the terminal by using Add, Move, Modify, Subtract, and the like.
  • the terminal may be the terminal of the entire MG or an individual terminal in the MG.
  • the MGC may also send a command to the MG as required to change the value of the attribute.
  • Step 202 The MG receives the command of the MGC, and sets the basic package advertisement attribute parameter.
  • the MGC can send the above-mentioned audit command request to the MG through a command such as AuditValue carrying a packet descriptor.
  • Step 204 In the corresponding audit command response returned to the MGC, the MG publishes the attribute of the package supported by the terminal according to the above-mentioned basic package advertisement attribute parameter, that is, the package is announced.
  • the value of the base package advertisement attribute in the above setting is set to "Both", that is, the MGC requires the MG to publish the package when both the base package and the extension package are announced, then when the MG announces a package, if the package is extended , which should include the package itself and its extension when it is published. From the basic package.
  • the value of the base package advertisement attribute in the above setting is set to "Ext", that is, when the MGC requests the MG to publish the package, only the extension package is announced, then when the MG announces a package, even if the package is extended, it is announced. Only the package itself is included.
  • the value of the base package advertisement attribute in the above setting is set to "Opt", that is, when the MGC allows the MG to publish the package, it may choose whether to include the base package, then when the MG announces a package, if the package is extended , when published, on the basis of including the package itself, whether or not it also includes the base package whose extension is included.
  • the MGC can freely control whether the MG publishes the extension package and also publish its base package, thereby determining whether to use the extension package identifier or the base package identifier when referring to the package element of the base package.
  • Embodiment 3 :
  • the third embodiment of the present invention uses an attribute to indicate the basic and extended correspondence between the packages, and the announcement.
  • This attribute can be defined in an existing package or in a new package, in the format of "Package ID/Attribute ID". For example, reuse the above pipa package, and name the attribute "Package Extension Infomation (labeled as pei)" in the format "pipa/pei”.
  • the publication is not necessary, and an attribute may be used to indicate the basic and extended correspondence between the packages. The following only describes the basic and extended correspondence between packages by an attribute, and the announcement is taken as an example.
  • This attribute can be used in the TerminationState descriptor for both the root (Root) terminal representing the MG as a whole and the individual terminal application in the MG.
  • This attribute is of type Sub-list of String.
  • Each element in the list represents the extension information of a package, including its package name (Package Name), optional extension package name, and optional publication status.
  • the package name is in turn composed of a package identifier (Package Identifier) and an optional version. If the extension package ID name does not appear, it indicates that the package corresponding to the base package name is a separate package.
  • the announcement can be "Both” or "Extension", indicating that the base package and its extension package are both announced; if only the extension package of the base package is publicized Cloth, then does not appear to indicate "both”.
  • the version does not appear to indicate version 1.
  • base package name [: extension package name] [: publication status]
  • base package name [: publication status]
  • base package name and “extension package name” are in the format of "package identification-version”, where "
  • nt:rtp:both means rtp as an extension package, its base package is nt, and rtp and nt are both announced.
  • nt: tdmc:ext means tdmc as an extension package, its base package is nt, and only tdmc is Announced.
  • the MGC audits the above pei attributes to the MG.
  • the MGC can audit the entire MG represented by the root terminal or individual terminals in the MG through the AuditValue command.
  • the MG then includes the corresponding and extended correspondence between the packages supported by the MG in the corresponding audit response returned to the MGC, as well as the announcement. Subsequent MGCs can process the packet identification included in the message from the MG based on this information.
  • Step 301 The MGC sends an audit command request for a specific terminal on the MG to the MG, where the packet extension information attribute is carried, indicating that the audit MG is in the The basic and extended correspondence between the packages supported on the terminal, and the announcement.
  • the MGC can send the above audit command request to the MG by carrying the packet extension information attribute through an instruction such as AuditValue.
  • the terminal may be a root terminal representing the entire MG or an individual terminal in the MG.
  • Step 302 The MG, in response to the corresponding audit command returned to the MGC, includes the basic and extended correspondence between the packets supported by the package, and the announcement by using the value of the packet extension information attribute.
  • the attribute is a string list type.
  • Each element in the list represents extended information of a package, including its base package name, optional extension package name, and optional publication status, where the package name is further identified by the package identifier and optional.
  • Version composition For example, in the format of "base package identifier name [: extension package identifier name] [: publication status]", "base package name” and “extension package name” are in the format of "package identification-version", where "[ ⁇ .]” means optional. If the extension package name does not appear, it means that the package corresponding to the base package name is a separate package. Announcement It can be "Both” or “Ext”, indicating that the base package and its extension package are both announced, and only the extension package of the base package is published, and no "Both” is displayed. The version does not appear to indicate version 1.
  • the MG When the above audit command responds to the relationship between the packages supported by the MG, the corresponding package identifiers are used to represent the packets. Therefore, the MG also announces to the MGC the packages supported by the MG.
  • Step 303 The MGC may, based on the received packet identifier included in the message from the MG, a basic and extended correspondence between the packet corresponding to the packet identifier obtained from the packet extension information and other packets, and an advertisement situation. , carry out the corresponding processing.
  • A is the base package
  • B is the extension package
  • the above MGC can accept that the MG refers to a by B/a even if A only implements B. It is known that the B/a is A/a according to the basic and extended correspondence between the above-mentioned packets and packets.
  • Embodiment 4 is A/a according to the basic and extended correspondence between the above-mentioned packets and packets.
  • the attributes in the foregoing two embodiments are used in combination, for example, when the bpp value is set to "optional" or default by the MGC, that is, the advertisement for a certain extended packet is determined by the MG itself. Whether or not the base package of the extension is also announced at the same time, the MGC can apply the pei attribute to understand the basic and extended correspondence between the packages supported by the MG, and the announcement.
  • Step 401 The MGC sends a command to the MG, and sets a value of the basic packet advertisement attribute to the MG for the specific terminal on the MG, which is "Opt". That is, the MGC allows the MG to select whether or not to include the base package when the package is published.
  • the MGC may carry the basic package advertisement attribute to the MG in the TerminationState descriptor for the terminal by using Add, Move, Modify, Subtract, and the like.
  • the terminal may be the terminal of the entire MG or an individual terminal in the MG.
  • Step 402 The MG receives the command of the MGC, and saves the foregoing settings.
  • Step 403 The MGC sends an audit command request for the terminal to the MG, where the carrying packet descriptor indicates that the packet supported by the MG on the terminal is audited.
  • the MGC can send the above-mentioned audit command request to the MG through a command such as AuditValue carrying a packet descriptor.
  • Step 404 In the corresponding audit command response returned to the MGC, the MG includes the identifier of the package supported by the terminal according to the foregoing setting, that is, the package is announced, and if one of the packages is extended, the advertised Based on the inclusion of the package itself, you can choose whether or not to include the base package from which it is extended.
  • Step 405 The MGC sends an audit command request for the terminal to the MG, where the packet extension information attribute is carried, indicating the basic and extended correspondence between the packets supported by the auditing MG on the terminal, and the publishing situation.
  • the MGC can send the above audit command request to the MG by carrying the packet extension information attribute through an instruction such as AuditValue.
  • Step 406 In the corresponding audit command response returned to the MGC, the MG uses the value of the packet extension information attribute to include the basic and extended correspondence between the packages supported by the MG, and the publishing situation.
  • the attribute is a string list type.
  • Each element in the list represents extended information of a package, including its base package identifier name, optional base extension package identifier name, and optional advertisement status, where the package name is further identified by the package identifier.
  • Optional version composition For example, in the format of "base package identifier name [: base extension package identifier name] [: publication status]", "base package name” and “extension package name” are in the format of "package identification-version", where "[ ...]” means optional.
  • the base package ID name does not appear. The default indicates that the package corresponding to the base package name is a stand-alone package, that is, a non-extension package.
  • the announcement can be "Both” or “Ext”, indicating that the base package and its base extension package are both announced, and only the extension package of the base package itself is published, and "Both” is not displayed.
  • the version does not appear to indicate version 1.
  • Step 407 The MGC may perform, based on the packet identifier included in the received message from the MG, a basic and extended correspondence between the packet corresponding to the packet identifier obtained from the packet extension information and other packets, and an advertisement situation. , carry out the corresponding processing.
  • Embodiment 5
  • Embodiment 5 of the present invention provides a system capable of implementing the above control of the application of the base package and the extension package.
  • the system architecture of the fifth embodiment of the present invention includes: a media gateway controller 60 and a media gateway 61.
  • the media gateway controller 60 further includes a sending unit 601 and a receiving unit 602.
  • the media gateway 61 further includes a receiving unit 611, a processing unit 612, and a sending unit 613.
  • the sending unit 601 of the media gateway controller 60 is configured to send, to the media gateway 61, a command request for instructing the media gateway 61 to set a basic package publishing attribute, where the command may be an add command, a move command, a modify command, or a cut command, and the like, and / or send a command request to the media gateway 61 for the audit package descriptor or the package extension information attribute.
  • the command request may be an audit value command, where the packet descriptor is carried, indicating that the media gateway 61 is required to publish the package it supports; or the packet extension information attribute is carried, indicating that the base and extension between the packets supported by the audit media gateway 61 correspond to relationship.
  • the receiving unit 602 of the media gateway controller 60 is configured to receive the command response corresponding to the command request from the media gateway 61, where the command response for the audit command request carries the identifier of the packet supported by the media gateway 61, or carries the media gateway.
  • the receiving unit 611 of the media gateway 61 is configured to receive the above command request from the media gateway controller 60.
  • the processing unit 612 of the media gateway 61 is configured to set the basic package advertisement attribute parameter according to the command request sent by the media gateway controller 60, and/or include the media gateway 61 in the command response returned to the media gateway controller 60.
  • processing unit 612 is further configured to include, in the command response returned to the media gateway controller 60, the identifier of the packet supported by the media gateway 61 according to the setting of the basic package advertisement attribute.
  • the sending unit 613 of the media gateway 61 is configured to send to the media gateway controller 60 The above command requests the corresponding command response.
  • the media gateway controller controls the media gateway to include the basic package when the package is published, and understands the basic and extended correspondence between the supported packages from the media gateway to effectively solve the basic package and the extended package.
  • the present invention can be implemented by hardware, or can be implemented by means of software plus necessary general hardware platform, and the technical solution of the present invention. It can be embodied in the form of a software product that can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including a number of instructions for making a computer device (may It is a personal computer, a server, or a network device, etc.) that performs the methods described in various embodiments of the present invention.
  • a non-volatile storage medium which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.
  • a computer device may It is a personal computer, a server, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Description

一种包公布与应用的控制方法和装置 本申请要求于 2008 年 4 月 1 日提交中国专利局， 申请号为 200810066435.0,发明名称为 "一种包公布与应用的控制方法、装置" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通讯技术领域，特别是一种包公布与应用的控制方法 和装置。 背景技术
媒体网关控制器（Media Gateway Controller, 以下筒称： MGC ) 和媒体网关（Media Gateway, 以下筒称： MG )是业务与承载分离架 构下的分组网络的两个关键构件。 MGC 负责业务控制功能， MG 负 责媒体承载功能， 藉此实现业务控制平面和媒体承载平面的分离， 从 而充分共享网络资源， 筒化设备升级和业务扩展， 降低开发和维护成 本。
(媒体）网关控制协议是 MG和 MGC之间通信的主要协议， 目 前应用较为广泛的有 H.248/MeGaCo ( Media Gateway Control Protocol , 媒体网关控制协议） 和 MGCP ( Media Gateway Control Protocol, 媒体网关控制协议）两种协议。 MGC和 MG之间的交互操 作通过（媒体 )网关控制协议中的命令 ( Command )的请求（ Request ) 和响应 （Reply )来完成。 命令的参数， 也称为描述符 ( Descriptor ), 被分类为属性（ Property )、信号（ Signal )、事件（ Event )、统计（ Statistic ) 等。 为了方便起见， 将具有业务相关性的参数从逻辑上聚合为包 ( Package )。
包代表了针对特定业务的功能或功能组合。 随着业务的发展， 相 应的功能也会被增强或扩充， 进而要求包也要被增强或扩充。 为此包 扩展机制规定可以在原有包的基础上派生出新的包，其中原有包也称 为基础包 （Base Package ), 派生出的新包也称为扩展包 （Extended Package )。基础包的包元素（ Package Element ), 包括属性 ( Property )、 信号 （Signal ), 事件 （ Event )、 统计 （Statistic ), 以及相应的规程 ( Procedure )等， 都被扩展包所继承。
为了方便 MGC对 MG的控制， MG需要向 MGC公布自身支持 的包。 只有在 MG向 MGC公布了某个包的情况下， MGC才能将其 应用于自身与该 MG之间的控制接口。
在实现本发明的过程中， 发明人发现现有技术至少存在以下问 题：
在 MG未向 MGC公布该包的情况下， 上述现有机制并未涉及 MG是否可以将该包应用于其与该 MGC之间的控制接口。 若 MG可 以应用该包， 则当 MGC由于 MG未公布或自身未实现等原因而不支 持应用该包时， 将无法正常处理来自 MG的应用了该包的消息。 发明内容
本发明实施例提供一种包公布与应用的控制方法和装置，解决了 现有机制下包在媒体网关控制器与媒体网关之间的控制接口上公布 与应用的矛盾。
本发明实施例提供一种包公布与应用的控制方法， 包括： 媒体网关 MG接收媒体网关控制器 MGC下发的第一审计命令请 求，所述第一审计命令请求中携带包描述符，表示审计所述 MG所支 持的包；
所述 MG向所述 MGC返回第一审计命令响应， 所述第一审计命 令响应中包含所述 MG所支持的包的标识；
所述 MG从所述 MG公布的包的标识中选择应用。
本发明实施例还提供一种媒体网关控制器， 包括：
发送单元， 用于向媒体网关发送第一命令请求， 所述第一命令请 求中携带包描述符，表示要求所述媒体网关公布所述媒体网关所支持 的包；
接收单元，用于接收所述媒体网关返回的与所述第一命令请求相 应的第一命令响应，所述第一命令响应中携带所述媒体网关所支持的 包的标识。
本发明实施例还提供一种媒体网关， 包括：
接收单元， 用于接收媒体网关控制器发送的第一命令请求， 所述 第一命令请求中携带包描述符，表示要求所述媒体网关公布所述媒体 网关所支持的包；
处理单元，用于在向所述媒体网关控制器返回的第一命令响应中 包括所述媒体网关所支持的包的标识，并且后续在所述公布的所述媒 体网关所支持的包的标识中选择应用；
发送单元，用于向所述媒体网关控制器发送所述第一命令请求相 应的所述第一命令响应，所述第一命令响应中包含所述媒体网关所支 持的包的标识。
本发明实施例中， MG从自身公布的包的标识中选择应用， 避免 了 MG使用未公布的包而被 MGC所不支持，从而有效解决了包在媒 体网关控制器与媒体网关之间控制接口公布与应用的矛盾问题。 附图说明
图 1是本发明实施例所采用的 MG和 MGC组网示意图； 图 2是本发明实施例一的流程图；
图 3是本发明实施例二的流程图；
图 4是本发明实施例三的流程图；
图 5是本发明实施例四的流程图；
图 6是本发明实施例五的系统结构示意图。 具体实施方式
为使本发明的技术方案更加清楚明白，以下参照附图并列举实施 例， 对本发明进一步详细说明。
如图 1所示，是本发明实施例所采用的 MG与 MGC的组网示意 图。
(媒体）网关控制协议是 MG和 MGC之间通信的主要协议， 应 用较为广泛的有 H.248/MeGaCo和 MGCP两种协议。
以 H.248 为例， MG 上的各种资源被抽象表示为终端 ( Termination ), 可以称之为个别终端。 终端又分为物理（Physical ) 终端和临时 （Ephemeral )终端， 前者代表一些具有半永久存在性的 物理实体， 例如 TDM ( Time Division Multiplex, 时分复用）时隙等， 后者代表一些临时申请用后释放的公共资源， 例如 RTP ( Real-time Transport Protocol, 实时传送协议） 流等。 另以被称为根（Root )终 端的特殊终端来代表 MG整体。终端之间的关联被抽象表示为上下文 ( Context )。 上下文可以包含多个终端， 因而以拓朴（Topology ) 来 描述终端间的相互关系。 对于还未与其他终端发生关联的终端， 由一 个被称为空 （Null )上下文的特殊上下文来包含。
基于上述抽象连接模型， 业务与承载之间的交互实际上就是对 Termination和 Context的操作。 这种操作通过 MGC和 MG之间的命 令（Command ) 的请求（Request )和响应 （Reply )来完成。 命令类 型包括增加 ( Add )、修改 ( Modify )、删减 ( Subtract )、移动 ( Move )、 审计值（ AuditValue )、 审计能力（ AuditCapabilities ), 通报（ Notify )、 服务改变（ ServiceChange )。 命令参数， 也称为描述符 ( Descriptor ), 被分类为属性（ Property )、信号（ Signal )、事件（ Event )、统计（ Statistic ) 等。为了方便将具有业务相关性的参数从逻辑上聚合为包（ Package )。
MGC对 MG的控制可以针对终端或终端上的流。 通过终端状态 ( TerminationState )描述符来包括终端上非流特有的特性， 例如服务 状态 （ ServiceState )、 事件緩沖控制 （ EventBufferControl )等。 通过 媒体 ( Media )描述符来包括终端上流特有的特性， 其包含一系列流 ( Stream ) 描述符。 每个流描述符针对单个流， 又包含本端控制 ( LocalControl )、 本端 （Local ) 和远端 （Remote )描述符。 本端控 制描述符用于包括流相关的控制信息， 例如模式 （Mode )、 预留组 ( ReserveGroup )和预留值（ Reserve Value )等。 本端和远端描述符 分别用于包括本端和远端所接收的流的特征， 例如地址和端口、 编解 码算法等， 采用 SDP ( Session Description Protocol, 会话描述协议） 的形式。
进一步地， 由于包分基础包和扩展包。 MG在向 MGC公布自身 支持的扩展包时，可以选择是否也公布相应的基础包。只有在 MG公 布了该基础包的情况下， MGC才能将该基础包应用于其与该 MG之 间的控制接口。 否则， MGC只能应用该扩展包， 而无法应用该扩展 包的基础包。 例如： H.248 中的网络（Network, 标识为 nt ) 包作为 基础包派生出了作为扩展包的实时传输协议 ( Real-time Transport Protocol,标识为 rtp )包。 nt包所包括的时长（ Duration,标识为 dur )、 发送字节数 ( Octets Sent, 标识为 os ),接收字节数 ( Octets Received, 标识为 or )统计参数等被 rtp包所继承， 即在引用时 rtp/dur、 rtp/os、 rtp/or分别等同于 nt/dur、 nt/os、 nt/or。 在此基础上 rtp包还有自身扩 展的发送分组数（Packets Sent, 标识为 ps )、 接收分组数 ( Packets Received, 标" i只为 pr )、 丟失分组数（ Packet Loss, 标" i只为 pi )、 抖动 緩存 ( Jitter, 标识为 jit )、 延时（Delay, 标识为 delay )统计参数等， 即只能以 rtp/ps、 rtp/pr, rtp/pK rtp/jit、 rtp/delay引用。 若 MG公布了 nt和 rtp包, 贝 'J rtp/dur, rtp/os、 rtp/or与 nt/dur, nt/os、 nt/or均可被 MGC所引用。 若 MG只公布了 rtp包， 则只有 rtp/dur、 rtp/os、 rtp/or 可被 MGC所引用。 如果 MG因为未公布而不可以应用某个基础包， 那么 MG 只能以相应的扩展包代替该基础包来引用该基础包的包元 素时， 若 MGC由于自身未实现等原因而不支持应用该扩展包时， 则 将无法正常处理来自 MG的应用了该扩展包的消息。因此需要新增有 效机制以使 MGC可以控制 MG对基础包与扩展包的发布与应用。
因此， 为了使 MGC控制 MG对基础包与扩展包的应用， 首先需 要对（媒体）网关控制协议进行扩展。 下面通过几个具体的实施例对 本发明进行详细的说明。 实施例一：
如图 2所示， 是本发明实施例一的流程图， 包括如下步骤。
步骤 101 , MG接收 MGC下发的审计命令请求， 其中携带包描 述符， 表示审计 MG所支持的包；
步骤 102, MG在返回给 MGC的相应的审计命令响应中包含自 身所支持的包的标识， 即公布包。
步骤 103, MGC与 MG在它们之间的控制接口上， 应用 MG公 布的包的标识。
具体操作可以采用如下的方法： MGC与 MG分别保存 MG公布 的包的标识， 后续按需从这些保存的包的标识中选择应用。 避免了 MG使用未公布的包而被 MGC所不支持， 从而有效解决了包在媒体 网关控制器与媒体网关之间控制接口公布与应用的矛盾问题。 实施例二：
由于包分基础包和扩展包，因此在公布扩展包时是否也公布其基 础包，将决定在 MGC与 MG之间的控制接口对基础包的包元素的引 用是否必须使用扩展包的标识。 本实施例通过一个属性（Property ) 来表示在公布扩展包时是否也公布其基础包。该属性可以定义在现有 包（Package )或新的包中， 以 "包标识 /属性标识" 的格式使用。 例 如将该新包命名为 "包标识公布与应用 （ Package Identifier Publishing andApplicatiion,标识为 pipa )包"，该属性命名为 "基础包公布（Base Package Publishing, 标口、为 bpp )，，， 以 "pipa/bpp" 的格式使用。
该属性既可以针对代表 MG 整体的根（Root )终端也可以针对 MG 中的个别终端应用， 在 TerminationState描述符中使用。 该属性 为枚举（ Enumeration )类型，取值可以是 "二者（ Both )"、 "扩展（ Ext )" 或 "可选（Opt )" , 分别表示基础包标识与扩展包标识均被公布、 仅 扩展包标识被公布、 或基础包标识是否公布取决于 MG, 缺省 （即该 属性未被设置） 时取值为 "可选"。 因为一个包有可能同时既是基础 包又是扩展包 ,所以这里所谓的是否公布其基础包标识仅针对其作为 扩展包而言， 对于非扩展包， 例如孤立（Stand Alone ) 包或其他包的 基础包不适用。
当 MGC需要控制 MG公布扩展包时是否也公布其基础包时， MGC向 MG设置上述 bpp属性。 MGC可以通过 Add、 Move, Modify, Subtract等命令传送该属性， 既可以对以根终端代表的整个 MG也可 以对 MG中的个别终端进行设置。然后当 MGC向 MG发送针对包描 述符的审计请求， MG在返回给 MGC的相应的审计响应中包含自身 所支持的包的标识时，将根据该属性设置决定对于其中包括的扩展包 是否也相应地包括其基础包。
如图 3所示， 是本发明实施例二的流程图， 包括如下步骤： 步骤 201 , MGC向 MG发送命令，针对 MG上特定的终端向 MG 设置基础包公布属性。
MGC可以通过 Add、 Move, Modify, Subtract等命令将基础包 公布属性携带在针对该终端的 TerminationState描述符中发送给 MG。 该终端可以是整个 MG的 ^终端， 也可以是 MG中的个别终端。
在本发明的另一个实施例中， 在设置完成后， MGC还可根据需 要向 MG发送命令， 要求更改该属性的取值。
步骤 202, MG接收到 MGC的命令， 设置基础包公布属性参数。 步骤 203, MGC向 MG发送针对上述终端的审计命令请求， 其 中携带包描述符， 表示审计在该终端上 MG所支持的包。
MGC可以通过 AuditValue等命令携带包描述符来向 MG发送上 述审计命令请求。
步骤 204, MG在返回给 MGC的相应的审计命令响应中， 根据 上述设置的基础包公布属性参数包含自身在该终端上所支持的包的 标识， 即公布包。
如果上述设置中基础包公布属性的取值设置为 "Both" , 也即 MGC要求 MG公布包时基础包与扩展包均被公布， 那么在 MG公布 某个包时， 若该包是扩展而来的， 则公布时应包含该包自身和其扩展 自的基础包。
如果上述设置中基础包公布属性的取值设置为 "Ext" ,也即 MGC 要求 MG公布包时仅扩展包被公布， 那么在 MG公布某个包时， 即 使该包是扩展而来的， 公布时也只包含该包自身。
如果上述设置中基础包公布属性的取值设置为 "Opt" ,也即 MGC 允许 MG公布包时， 可以选择是否包括基础包， 那么在 MG公布某 个包时， 若该包是扩展而来的， 则公布时在包含该包自身的基础上可 选是否还包含其扩展自的基础包。
MGC通过该基础包公布属性可以自由地控制 MG公布扩展包时 是否也公布其基础包，从而决定引用基础包的包元素时是否既可以使 用扩展包标识也可以使用基础包标识。 实施例三：
本发明实施例三通过一个属性来表示包之间的基础与扩展对应 关系， 以及公布情况。 该属性可以定义在现有包或新的包中， 以 "包 标识 /属性标识" 的格式使用。 例如重用上述 pipa包， 将该属性命名 为 "包扩展信息 ( Package Extension Infomation , 标识为 pei )" , 以 "pipa/pei" 的格式使用。 本发明的另一个实施例中， 公布情况不是 必须的， 可以通过一个属性来表示包之间的基础与扩展对应关系。 下 面仅以通过一个属性来表示包之间的基础与扩展对应关系，以及公布 情况为例进行说明。
该属性既可以针对代表 MG 整体的根（Root )终端也可以针对 MG 中的个别终端应用， 在 TerminationState描述符中使用。 该属性 为字符串列表（Sub-list of String )类型， 列表中每个元素代表一个包 的扩展信息， 包括其基础包名称（Package Name )、 可选的扩展包名 称和可选的公布情况。 其中包名称又由包标识（Package Identifier ) 与可选的版本构成。 扩展包标识名称若不出现， 则表示基础包名称所 对应的包为独立包。公布情况可以是"二者（ Both )"或者 "扩展（ Ext )" , 分别表示该基础包与其扩展包均被公布；若仅该基础包的扩展包被公 布， 则不出现表示 "二者"。 版本不出现表示版本 1。
例如可以采用 "基础包名称 [： 扩展包名称] [： 公布情况]" 的格 式， "基础包名称" 与 "扩展包名称"都采用 "包标识-版本" 的格式， 其中的 "|：…： Γ 表示可选， 则 "nt" 表示 nt包是对立包并且被公布，
"nt:rtp:both" 表示 rtp作为扩展包， 其基础包是 nt, 并且 rtp与 nt均 被公布， "nt: tdmc:ext" 表示 tdmc作为扩展包， 其基础包是 nt, 并且 仅 tdmc被公布。
当 MGC需要了解 MG所支持的包之间的基础与扩展对应关系， 以及公布情况时， MGC向 MG审计上述 pei属性。 MGC可以通过 AuditValue命令对根终端代表的整个 MG或者对 MG中的个别终端进 行审计。 然后 MG在返回给 MGC的相应的审计响应中包含自身所支 持的包之间的基础与扩展对应关系， 以及公布情况。 后续 MGC就可 以根据该信息处理来自 MG的消息中所包括的包标识。
如图 4所示， 为本发明实施例三的流程图， 包括如下步骤： 步骤 301 , MGC向 MG发送针对 MG上特定的终端的审计命令 请求，其中携带包扩展信息属性，表示审计 MG在该终端上所支持的 包之间的基础与扩展对应关系， 以及公布情况。
MGC可以通过 AuditValue等命令携带包扩展信息属性来向 MG 发送上述审计命令请求。该终端可以是代表整个 MG的根终端，也可 以是 MG中的个别终端。
步骤 302, MG在返回给 MGC的相应的审计命令响应中， 通过 上述包扩展信息属性的取值来包含自身所支持的包之间的基础与扩 展对应关系， 以及公布情况。
该属性为字符串列表类型，列表中每个元素代表一个包的扩展信 息， 包括其基础包名称、 可选的扩展包名称和可选的公布情况， 其中 包名称又由包标识与可选的版本构成。 例如采用 "基础包标识名称 [： 扩展包标识名称] [： 公布情况]" 的格式， "基础包名称" 与 "扩展包 名称" 都采用 "包标识-版本" 的格式， 其中的 "[ ··.]" 表示可选。 扩 展包名称不出现， 则表示基础包名称所对应的包为独立包。 公布情况 可以是 "Both"或者 "Ext" , 分别表示该基础包与其扩展包均被公布、 仅该基础包的扩展包被公布， 不出现表示 "Both"。 版本不出现表示 版本 1。
上述审计命令响应公布 MG 所支持的包之间的关系时以相应的 包标识来代表这些包， 因此也相当于 MG向 MGC公布了 MG所支持 的包。
步骤 303, MGC对于接收到的来自 MG的消息中所包括的包标 识，可以基于从上述包扩展信息获得的该包标识所对应的包与其他包 之间的基础与扩展对应关系， 以及公布情况， 进行相应的处理。
例如： 假设 A是基础包， B是扩展包， 对于 A的包元素 a: 若 MG公布了 A与 B, 则 MGC只要实现了 A就可以接受 MG以 A/a 或 B/a来引用 a; 若 MG只公布了 B, 则 MGC只要实现了 A就可以 接受 MG以 B/a来引用 a。 上述 MGC即使只实现 A未实现 B也可以 接受 MG以 B/a来引用 a的原因， 正在于 MGC根据上述包与包之间 的基础与扩展对应关系知道 B/a就是 A/a。 实施例四：
本发明实施例四将上述两个实施例中的属性结合使用， 例如当 bpp取值被 MGC设置为 "可选" 或缺省， 也即对于某个扩展而来的 包的公布由 MG自身决定是否也同时公布其扩展自的基础包时， MGC 可以应用 pei属性来了解 MG所支持的包之间的基础与扩展对应关 系， 以及公布情况。
如图 5所示， 是本发明实施例四的流程图， 包括如下步骤： 步骤 401 , MGC向 MG发送命令，针对 MG上特定的终端向 MG 设置基础包公布属性的取值为 "Opt" , 也即 MGC允许 MG公布包时 可选是否包括基础包。
MGC可以通过 Add、 Move, Modify, Subtract等命令将基础包 公布属性携带在针对该终端的 TerminationState描述符中发送给 MG。 该终端可以是整个 MG的 ^终端， 也可以是 MG中的个别终端。 步骤 402, MG接收到 MGC的命令， 保存上述设置。
步骤 403, MGC向 MG发送针对上述终端的审计命令请求， 其 中携带包描述符表示审计在该终端上 MG所支持的包。
MGC可以通过 AuditValue等命令携带包描述符来向 MG发送上 述审计命令请求。
步骤 404, MG在返回给 MGC的相应的审计命令响应中， 根据 上述设置包含自身在该终端上所支持的包的标识， 即公布包， 若其中 某个包是扩展而来的，则公布时在包含该包自身的基础上可以选择是 否还包含其扩展自的基础包。
步骤 405, MGC向 MG发送针对上述终端的审计命令请求， 其 中携带包扩展信息属性，表示审计 MG在该终端上所支持的包之间的 基础与扩展对应关系， 以及公布情况。
MGC可以通过 AuditValue等命令携带包扩展信息属性来向 MG 发送上述审计命令请求。
步骤 406, MG在返回给 MGC的相应的审计命令响应中， 通过 上述包扩展信息属性的取值包含自身所支持的包之间的基础与扩展 对应关系， 以及公布情况。
该属性为字符串列表类型，列表中每个元素代表一个包的扩展信 息， 包括其基础包标识名称、 可选的基础扩展包标识名称和可选的公 布情况， 其中包名称又由包标识与可选的版本构成。 例如采用 "基础 包标识名称 [： 基础扩展包标识名称] [： 公布情况]" 的格式， "基础包 名称"与 "扩展包名称"都采用 "包标识-版本"的格式，其中的 "[ ...]" 表示可选。基础包标识名称不出现缺省表示基础包名称所对应的该包 为独立包， 即非扩展包。 公布情况可以是 "Both" 或者 "Ext" , 分别 表示该基础包与其基础扩展包均被公布、仅该基础包自身的扩展包被 公布， 不出现表示 "Both"。 版本不出现表示版本 1。
步骤 407 , MGC对于接收到的来自 MG的消息中所包括的包标 识，可以基于从上述包扩展信息获得的该包标识所对应的包与其他包 之间的基础与扩展对应关系， 以及公布情况， 进行相应的处理。 实施例五：
本发明实施例五提供了一种能够实现上述对基础包与扩展包的 应用进行控制的系统。 如图 6所示， 是本发明实施例五的系统结构示 意图， 包括： 媒体网关控制器 60和媒体网关 61。 其中， 媒体网关控 制器 60进一步包括发送单元 601和接收单元 602, 媒体网关 61进一 步包括接收单元 611、 处理单元 612和发送单元 613。
该媒体网关控制器 60的发送单元 601 , 用于向媒体网关 61发送 指示媒体网关 61设置基础包公布属性的命令请求， 该命令可以为添 加命令、 移动命令、 修改命令或删减命令等， 和 /或向媒体网关 61发 送审计包描述符或包扩展信息属性的命令请求。该命令请求可以为审 计值命令， 其中携带包描述符， 表示要求媒体网关 61公布其所支持 的包； 或者携带包扩展信息属性， 表示审计媒体网关 61所支持的包 之间的基础与扩展对应关系。
该媒体网关控制器 60的接收单元 602, 用于从媒体网关 61接收 上述命令请求相应的命令响应，其中对于上述审计命令请求的命令响 应携带媒体网关 61所支持的包的标识，或者携带媒体网关 61所支持 的包之间的基础与扩展对应关系。
该媒体网关 61的接收单元 611 , 用于从媒体网关控制器 60接收 上述命令请求。
该媒体网关 61的处理单元 612, 用于根据媒体网关控制器 60发 送的命令请求， 设置上述基础包公布属性参数， 和 /或在向媒体网关 控制器 60返回的命令响应中包括媒体网关 61所支持的包的标识，或 者媒体网关 61所支持的包之间的基础与扩展对应关系， 并且后续在 公布的媒体网关 61所支持的包的标识中选择应用。
进一步地， 处理单元 612还用于根据上述基础包公布属性的设 置，在向媒体网关控制器 60返回的命令响应中包括媒体网关 61所支 持的包的标识。
该媒体网关 61的发送单元 613, 用于向媒体网关控制器 60发送 上述命令请求相应的命令响应。
本发明实施例通过媒体网关控制器按需控制媒体网关公布包时 是否包括基础包，以及从媒体网关了解其所支持的包之间的基础与扩 展对应关系，来有效解决基础包与扩展包在媒体网关控制器与媒体网 关之间控制接口应用的矛盾问题。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解 到本发明可以通过硬件实现，也可以可借助软件加必要的通用硬件平 台的方式来实现基于这样的理解，本发明的技术方案可以以软件产品 的形式体现出来， 该软件产品可以存储在一个非易失性存储介质（可 以是 CD-ROM, U盘， 移动硬盘等） 中， 包括若干指令用以使得一 台计算机设备（可以是个人计算机， 服务器， 或者网络设备等）执行 本发明各个实施例所述的方法。
总之， 以上所述仅为本发明的较佳实施例而已， 并非用于限定本 发明的保护范围。 凡在本发明的精神和原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权利要求
1、 一种包公布与应用的控制方法， 其特征在于， 包括： 媒体网关 MG接收媒体网关控制器 MGC下发的第一审计命令请 求，所述第一审计命令请求中携带包描述符，表示审计所述 MG所支 持的包；
所述 MG向所述 MGC返回第一审计命令响应，所述第一审计命 令响应中包含所述 MG所支持的包的标识；
所述 MG从所述 MG公布的包的标识中选择应用。
2、如权利要求 1所述的方法， 其特征在于， 所述 MG接收 MGC 下发的第一审计命令请求之前， 还包括：
所述 MG接收来自所述 MGC的命令，所述命令携带基础包公布 属性；
所述 MG根据接收到的来自所述 MGC的命令，设置基础包公布 属性参数；
如果所述基础包公布属性的取值表示所述 MGC要求所述 MG公 布包时基础包与扩展包均被公布， 则所述 MG公布所述扩展包时， 同 时公布所述扩展包和所述扩展包对应的基础包； 或者
如果所述基础包公布属性的取值表示所述 MGC要求所述 MG公 布包时仅所述扩展包被公布， 则所述 MG公布所述扩展包时，仅公布 所述扩展包； 或者
如果所述基础包公布属性的取值表示所述 MGC允许所述 MG公 布包时可选是否包括所述基础包， 则所述 MG公布所述扩展包时，在
3、 如权利要求 2所述的方法， 其特征在于， 所述 MG向 MGC 返回第一审计命令响应， 包括：
所述 MG根据所述设置的基础包公布属性参数，在所述第一审计 命令响应中包含所述 MG所支持的包的标识。
4、 如权利要求 2所述的方法， 其特征在于， 所述基础包公布属 性针对所述 MG上特定的终端， 所述终端是代表整个 MG的根终端， 或者所述 MG中的个别终端。
5、 如权利要求 2或 3所述的方法， 其特征在于， 如果所述基础 括所述基础包， 还包括：
所述 MGC向所述 MG发送第二审计命令请求，所述第二审计命 令请求中携带包扩展信息属性，表示审计所述 MG所支持的包之间的 基础与扩展对应关系；
所述 MG向所述 MGC返回第二审计命令响应，所述第二审计命 令响应中携带所述 MG所支持的包之间的基础与扩展对应关系。
6、 如权利要求 5所述的方法， 其特征在于， 所述包扩展信息属 性针对所述 MG上特定的终端， 所述终端是代表整个 MG的根终端， 或者所述 MG中的个别终端。
7、 如权利要求 5所述的方法， 其特征在于， 所述包扩展信息属 性， 包括：
基础包名称、 可选的扩展包名称、 可选的公布情况。
8、 如权利要求 7所述的方法， 其特征在于， 所述基础包名称和 扩展包名称均由包标识和可选的版本构成。
9、 如权利要求 7所述的方法， 其特征在于， 所述公布情况的取 值表示所述基础包与所述扩展包均被公布， 或者仅所述扩展包被发 布。
10、 一种媒体网关控制器， 其特征在于， 包括：
发送单元， 用于向媒体网关发送第一命令请求， 所述第一命令请 求中携带包描述符，表示要求所述媒体网关公布所述媒体网关所支持 的包；
接收单元，用于接收所述媒体网关返回的与所述第一命令请求相 应的第一命令响应 ,所述第一命令响应中携带所述媒体网关所支持的 包的标识。
11、 如权利要求 10所述的媒体网关控制器， 其特征在于， 所述发送模块，还用于向所述媒体网关发送指示所述媒体网关设 置基础包公布属性的第二命令请求，所述媒体网关根据所述第二命令 请求设置基础包公布属性参数。
12、 如权利要求 11所述的媒体网关控制器， 其特征在于， 所述发送模块， 还用于向所述媒体网关发送第三命令请求， 所述 第三命令请求中携带包扩展信息属性，表示审计所述媒体网关所支持 的包之间的基础与扩展对应关系；
所述接收模块，还用于从所述媒体网关接收所述第三命令请求相 应的第三命令响应 ,所述第三命令响应中携带所述媒体网关所支持的 包之间的基础与扩展对应关系。
13、 一种媒体网关， 其特征在于， 包括：
接收单元， 用于接收媒体网关控制器发送的第一命令请求， 所述 第一命令请求中携带包描述符，表示要求所述媒体网关公布所述媒体 网关所支持的包；
处理单元，用于在向所述媒体网关控制器返回的第一命令响应中 包括所述媒体网关所支持的包的标识，并且后续在所述公布的所述媒 体网关所支持的包的标识中选择应用；
发送单元，用于向所述媒体网关控制器发送所述第一命令请求相 应的所述第一命令响应，所述第一命令响应中包含所述媒体网关所支 持的包的标识。
14、 如权利要求 13所述的媒体网关， 其特征在于，
所述接收单元，还用于接收所述媒体网关控制器发送的指示所述 媒体网关设置基础包公布属性的第二命令请求；
所述处理单元，还用于根据所述媒体网关控制器发送的所述第二 命令请求， 设置基础包公布属性参数。
15、 如权利要求 14所述的媒体网关， 其特征在于，
所述接收单元，还用于接收所述媒体网关控制器发送的第三命令 请求， 所述第三命令请求中携带包扩展信息属性， 表示审计所述媒体 网关所支持的包之间的基础与扩展对应关系； 所述处理单元，还用于在向所述媒体网关控制器返回的第三命令 响应中包括所述媒体网关所支持的包之间的基础与扩展对应关系； 所述发送单元，还用于向所述媒体网关控制器发送所述第三命令 请求相应的所述第三命令响应。
PCT/CN2009/070453 2008-04-01 2009-02-17 一种包公布与应用的控制方法和装置 WO2009121249A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP09729137.1A EP2271034B1 (en) 2008-04-01 2009-02-17 Package publishing and applying control method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2008100664350A CN101552746B (zh) 2008-04-01 2008-04-01 一种包公布与应用的控制方法、装置
CN200810066435.0 2008-04-01

Publications (1)

Publication Number Publication Date
WO2009121249A1 true WO2009121249A1 (zh) 2009-10-08

Family

ID=41134817

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/070453 WO2009121249A1 (zh) 2008-04-01 2009-02-17 一种包公布与应用的控制方法和装置

Country Status (3)

Country Link
EP (1) EP2271034B1 (zh)
CN (1) CN101552746B (zh)
WO (1) WO2009121249A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2549696B1 (en) * 2010-06-29 2017-03-29 Huawei Technologies Co., Ltd. Method, device and system for negotiating multimedia capability
WO2016015783A1 (en) * 2014-08-01 2016-02-04 Telefonaktiebolaget L M Ericsson (Publ) Service availability in mobile communications networks
TWI650978B (zh) * 2018-03-21 2019-02-11 和碩聯合科技股份有限公司 封包辨識方法及封包辨識裝置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070116018A1 (en) * 2005-11-18 2007-05-24 Santera Systems, Inc. Methods, systems, and computer program products for distributed resource allocation among clustered media gateways in a communications network
CN101080091A (zh) * 2006-10-25 2007-11-28 中兴通讯股份有限公司 无线网络控制器获取基站能力的方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070116018A1 (en) * 2005-11-18 2007-05-24 Santera Systems, Inc. Methods, systems, and computer program products for distributed resource allocation among clustered media gateways in a communications network
CN101080091A (zh) * 2006-10-25 2007-11-28 中兴通讯股份有限公司 无线网络控制器获取基站能力的方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ARANGO M. ET AL.: "Media Gateway Control Protocol (MGCP) Version 1.0", RFC2705, October 1999 (1999-10-01) *
FOSTER B. ET AL.: "The Media Gateway Control Protocol (MGCP) Bulk Audit Package", RFC3624, November 2003 (2003-11-01) *

Also Published As

Publication number Publication date
EP2271034A1 (en) 2011-01-05
EP2271034A4 (en) 2011-08-17
EP2271034B1 (en) 2017-05-10
CN101552746B (zh) 2011-06-15
CN101552746A (zh) 2009-10-07

Similar Documents

Publication Publication Date Title
CN107006054B (zh) 用于音频-视频中继的无线对接方法和系统
WO2009121249A1 (zh) 一种包公布与应用的控制方法和装置
WO2008046311A1 (en) A method, system and network entity for negotiating the session description protocol version and obtaining the session description protocol version information
WO2008101429A1 (fr) Procédé, dispositif et système pour réguler le rapport du protocole de transport en temps réel haute résolution
WO2010017725A1 (zh) 媒体播放的控制方法、系统和设备
US8750318B2 (en) Method, apparatus and system for applying relations between package base and extension
US8488454B2 (en) Method for adjusting signal speed, media gateway, and media gateway controller
WO2009129712A1 (zh) 上报会话状态的方法、媒体网关和系统
WO2009092251A1 (zh) 标识媒体资源的方法、媒体网关及媒体网关控制器
RU2474065C2 (ru) Способ, система и устройство для приостановки сигналов
WO2008148347A1 (fr) Procédé de gestion de ressources, dispositif de support et dispositif de commande de support
WO2009092258A1 (zh) 实现获取媒体流信息的方法及装置
US8358581B2 (en) Method for adjusting signal delivery bandwidth, media gateway and media gateway controller
WO2010017758A1 (zh) 信号增益控制方法、系统、媒体网关及媒体网关控制器
WO2008148340A1 (fr) Procédé et dispositif de réservation de ressources
WO2009089737A1 (fr) Procédé d'interaction de la capacité d'expression d'informations de zone et passerelle multimédia et unité de commande de passerelle multimédia associées
WO2009089724A1 (fr) Procédé de fourniture, procédé d'acquisition, système et dispositif d'informations d'expiration de ressources
WO2009121258A1 (zh) 一种匹配结果上报控制方法和装置
WO2009121268A1 (zh) 一种媒体流中拨号信息的处理方法、装置和系统
US20100265961A1 (en) Method, device and system for controlling the packet size for media transmission
WO2008148338A1 (fr) Procédé et dispositif de commande de ressource en service et structure de séparation de support
WO2012000172A1 (zh) 多媒体能力协商方法、装置及系统
WO2008116418A1 (fr) Procédé et système pour transmettre des informations de ressource, passerelle multimédia et contrôleur de passerelle multimédia
WO2009092270A1 (zh) 一种基于范围的媒体控制方法及设备
WO2009121235A1 (zh) 一种媒体流中信号音的处理方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09729137

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2009729137

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2009729137

Country of ref document: EP