CN1722672A - Method for carrying out concentrated bandwidth management by server in voice network - Google Patents
Method for carrying out concentrated bandwidth management by server in voice network Download PDFInfo
- Publication number
- CN1722672A CN1722672A CN 200410068940 CN200410068940A CN1722672A CN 1722672 A CN1722672 A CN 1722672A CN 200410068940 CN200410068940 CN 200410068940 CN 200410068940 A CN200410068940 A CN 200410068940A CN 1722672 A CN1722672 A CN 1722672A
- Authority
- CN
- China
- Prior art keywords
- bandwidth
- gateway
- bmg
- called
- calling
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000006855 networking Effects 0.000 claims description 12
- 238000007726 management method Methods 0.000 description 47
- 230000008569 process Effects 0.000 description 10
- 230000008859 change Effects 0.000 description 6
- 238000012790 confirmation Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Abstract
This invention discloses a method for centralized bandwidth managing the sever in voice network, characterized in that it combines the gateways with same bandwidth feature to a gateway bandwidth management group BMG; the sever uses the BMG inner total bandwidth, BMG output total bandwidth, the whole or part total bandwidth between any two BMG to manage collectively. Said invention can realize the flexible management without expanding the protocol, and it is fit for several kinds of network topology.
Description
Technical field
The present invention relates to a kind of bandwidth management method, server is concentrated the method for Bandwidth Management in particularly a kind of speech network.
Background technology
Along with the development of IP technology, IP phone/facsimile art becomes a big focus.IP phone/facsimile network generally is made of gatekeeper, gateway (GW), terminal (Terminal), the IP network that supports IP phone/facsimile transmission and corresponding webmaster, charging and business system.IP phone gatekeeper is the key equipment of entire I P telephone system, the routing management of being responsible for making up IP telephony network and finishing IP telephony network, the butt joint of safety management and other networks.Gateway and terminal provide real-time, two-way voice, video (optional), data (optional) service.In network H.323, the set of entities such as the gateway under gatekeeper and its administration, terminal is called territory (Zone).In a territory, there is and has only a gatekeeper; General structure-irrelevant can be opened up with network in the territory, can the cross-domain a plurality of network segments that connected by router or miscellaneous equipment such as a territory.
Gatekeeper's a critical function is the Bandwidth Management of calling out.H.323 protocol description according to ITU_T, have this in the access request message (ARQ) of gateway and call out to estimate the bandwidth that to use, it should be noted that the bandwidth here is to need the bandwidth used in the bi-directional call, for example, the calling of a 128kbit/s should be marked as 256kbit/s; The gatekeeper calls out this to available maximum bandwidth information band and gives gateway in access grant message (ACF), this value may be less than the bandwidth of gateway application; After calling out beginning, gateway dedicated bandwidth request message (BRQ) application change bandwidth; Reply bandwidth if the gatekeeper agrees change and allow message (BCF), otherwise reply bandwidth reject message (BRJ); When end of calling, gateway notifies gatekeeper's bandwidth to discharge.
H.323 agreement has just provided several operations that are used for Bandwidth Management, and how managing bandwidth does not provide suggestion to the gatekeeper.For example: bandwidth is that gateway is linked into available bandwidth between total bandwidth on the INTERNET or two gateways, gatekeeper's bandwidth application (ARQ, BRQ) to gateway under which kind of situation adds their confirmation (ACF, BCF), when refuses (ARJ, BRJ) again ...
The common treating method of existing gatekeeper's equipment is: the total bandwidth that gateway is linked on the Internet manages.That is: on the gatekeeper for each gateway of its management is provided with a total bandwidth, when per call is set up, from total bandwidth, deduct respective value; During bandwidth change, discharge former bandwidth, take new bandwidth; Call out when discharging, discharge the bandwidth that this calling takies.
This mode will run into following problem in actual applications: relevant with the general structure of opening up of network as the bandwidth between Fig. 1 gateway, for example: certain company in Beijing, there is branch in Shenzhen, Shanghai, in each place some gateways are set, Pekinese's gateway uses the 100M Ethernet card to be connected on the internal network of company, Beijing is 10M with the bandwidth between the Shanghai, and Beijing is 20M with the bandwidth between Shenzhen.If simply Pekinese's gateway total bandwidth is defined as 10M or less than 10M, Beijing can't be fully utilized with the network bandwidth between Shenzhen; If be defined as 20M or more than the 20M, the call volume between Beijing and the Shanghai is big, when utilized bandwidth surpassed 10M, the gatekeeper can't refuse calling when the bandwidth application, the Network Packet Loss between Beijing and the Shanghai as a result, and voice quality descends, even can't normal talking.Therefore, this is a kind of rough Bandwidth Management mode.
For realizing comprehensive Bandwidth Management, also can pass through proprietary protocol, and increase off-gauge network entity realization Bandwidth Management.This scheme requires gateway to support proprietary protocol, can go wrong with other vendor equipment intercommunication the time.For user's upgrade expanding brings difficulty.
Summary of the invention
The purpose of this invention is to provide the method that server is concentrated Bandwidth Management in a kind of speech network, under not to the situation that H.323 agreement is expanded, on the gatekeeper, realize a kind of perfect Bandwidth Management.
According to an aspect of the present invention, the method that server is managed concentratedly in the speech network that is provided may further comprise the steps:
The networking that bandwidth characteristic is identical is closed and is formed gateway Bandwidth Management group BMG;
The all or part of of total bandwidth managed concentratedly bandwidth between the interior total bandwidth of server by utilizing BMG, BMG outlet total bandwidth, any two BMG.
According to another aspect of the present invention, the method that server is managed concentratedly in the speech network that is provided may further comprise the steps:
The networking that bandwidth characteristic is identical is closed and is formed gateway Bandwidth Management group BMG;
The caller gateway is called out the called gateway that is positioned at same BMG by server;
Server judges according to the information of calling and called gateway relevant bandwidth in calling procedure whether caller gateway and called gateway outlet total bandwidth is all enough, judges then whether the inner total bandwidth of BMG of caller gateway is enough;
If described any one bandwidth does not satisfy, then the server refusal is called out, otherwise allows to call out.
According to a further aspect of the invention, the method that server is managed concentratedly in the speech network that is provided may further comprise the steps:
The networking that bandwidth characteristic is identical is closed and is formed gateway Bandwidth Management group BMG;
The caller gateway is called out the called gateway that is positioned at different B MG by server;
Server is according to the information of calling and called gateway relevant bandwidth in calling procedure, whether the outlet total bandwidth of judging caller gateway and called gateway is all enough, whether the inside total bandwidth of BMG of judging caller gateway and called gateway is all enough, judges then whether the BMG bandwidth between caller gateway and called gateway is enough;
If described any one bandwidth does not satisfy, then the server refusal is called out, otherwise allows to call out.
Wherein, behind end of calling, recover to call out the bandwidth that takies.
Wherein, the calling that contains among the server by utilizing ARQ needs the information of occupied bandwidth, judge whether caller gateway and called gateway outlet total bandwidth is all enough, export total bandwidth less than caller gateway and called gateway respectively, judge that then described outlet total bandwidth is enough if call out the bandwidth that need take.
Wherein, the calling that contains among the server by utilizing ARQ needs the information of occupied bandwidth, whether the inner total bandwidth of BMG of judging the caller gateway is enough, if the bandwidth that calling need take, judges then that the inner total bandwidth of described BGM is enough less than the inner total bandwidth of the BMG of caller gateway.
Wherein, the calling that contains among the server by utilizing ARQ needs the information of occupied bandwidth, whether the inner total bandwidth of BMG of judging called gateway is enough, if the bandwidth that calling need take, judges then that the inner total bandwidth of described BGM is enough less than the inner total bandwidth of the BMG of called gateway.
Wherein, the calling that contains among the server by utilizing ARQ needs the information of occupied bandwidth, judge whether the inner total bandwidth of BMG between caller gateway and called gateway is enough, if it is wide enough that the bandwidth that calling need take, is then judged the BGM between described caller gateway and called gateway less than the BMG bandwidth between caller gateway and called gateway.
Although The present invention be directed to protocol frame H.323 this Bandwidth Management scheme is set forth, this thought is not limited to H.323 network, be suitable for too for NGN networks such as SIP, MGCP.
In conjunction with the accompanying drawings with the explanation of instantiation, can make above and other objects of the present invention, advantage and characteristics become clearer by following.
Description of drawings
Fig. 1 has shown the same topology of networks of bandwidth between the gateway of prior art;
Fig. 2 has shown the same topology of networks of the bandwidth between the gateway of the present invention;
Another flow process of routing call during H.323 Fig. 3 has shown;
Fig. 4 has shown the flow process that SIP calls out.
Embodiment
Abbreviation relevant and Key Term definition with the present invention
VOIP:Voice over IP is based on the voice of IP technology
H.323:ITU-T the VOIP agreement of Zhi Dinging
GK:GateKeeper is the network entity in the agreement H.323, and major function is registration management, call manager, address resolution, Bandwidth Management.It should be noted that in NGN networks such as SIP, MGCP and realize similar functions, therefore in this article, GK is kept in the pass be considered as a kind of server by server.
NGN:Next Generation Network next generation network.
The GW:Gateway gateway refers in particular to the VOIP gateway herein.
IP:Internet Protocol, Internet protocol
Gateway IP: the internet protocol address of gateway
ARQ:Address Request is the access request message in the agreement H.323
ACF:Address Confirm is the access confirmation message in the agreement H.323, to the affirmation message of ARQ message
ARJ:Address Reject is the access confirmation message in the agreement H.323, to the refuse information of ARQ message
BRQ:Bandwith Request is the change of the bandwidth in agreement request message H.323
BCF:Bandwith Confirm is the change of the bandwidth in agreement acknowledge message H.323, to the affirmation message of BRQ message
BRJ:Bandwith Request is the change of the bandwidth in agreement refuse information H.323, to the refuse information of BRQ message
BMG: Bandwidth Management group (Bandwidth Management Group) is opened up in the general structure chart at network, and the networking that bandwidth characteristic is identical is closed and formed a Bandwidth Management group.
The BMG notion
Introducing new ideas earlier---gateway Bandwidth Management group BMG (Bandwidth ManagementGroup): open up in the general structure chart at network, the networking that bandwidth characteristic is identical is closed and is formed BMG.In the superincumbent example, all have just formed a BMG at Pekinese's gateway, and all gateways in Shanghai belong to another BMG.
Divide BMG
At Guan Shoushang, gateway is classified as several BMG; When some gateway need not to carry out Bandwidth Management, maybe can't carry out Bandwidth Management (such as overseas gateway), they can be classified as a special BMG, also can give tacit consent to the gateway that will not belong to any one BMG and all belong to this special BMG.
Relevant parameter
The BMG notion has been arranged, and Bandwidth Management can relate to 4 parameters: the gateway access bandwidth, and the BMG internal bandwidth, BMG exports total bandwidth, bandwidth between BMG.
● the gateway access bandwidth: during gateway of predefine, be the attribute of its setting on the gatekeeper, the gateway that in general uses Fast Ethernet is 100M, and using the gateway of gigabit Ethernet is 1000M.
● the BMG internal bandwidth: be each BMG configuration internal bandwidth total amount, this is a parameter of maximum available bandwidths between the gateway of describing in the BMG.To need not to carry out the BMG of internal bandwidth management, can be set to infinity.
● BMG exports total bandwidth: be each BMG configuration outlet total bandwidth, this is to describe a converse parameter of maximum available bandwidths of inside and outside all gateways of BMG.When need not BMG outlet total bandwidth managed, can be set to infinity.
● bandwidth between BMG: can define total bandwidth between BMG between any two BMG, this is a parameter of describing between two BMG by maximum available bandwidths.When need not bandwidth between certain two BMG managed, can be set to infinity.
BMG and outside BMG in the territory
The BMG of the last configuration of GK or inside, or outside.If the gateway among the BMG all is under this GK administration, Here it is an inner BMG; If the gateway among the BMG is not that this is an outside BMG under this GK administration.When outside GW number very for a long time, safeguard that a plurality of outside BMG can be very complicated, can simplify configuration: if gateway does not belong to BMG that any one is determined, then it belongs to the BMG of " other " by name.
Inner BMG, the gateway that can manage among the BMG inserts total bandwidth, inner total bandwidth, outlet total bandwidth, this BMG with the bandwidth between other BMG.For the BMG of outside, can only manage it with the bandwidth between the inner BMG.
In general, the caller gateway call comprises calls out the called gateway that is positioned at same BMG and calls out the two kinds of situations of called gateway that are positioned at different B MG, and therefore the method that server is managed concentratedly in the speech network of the present invention comprises following two kinds of methods:
The method of first kind of centralized management may further comprise the steps:
The networking that bandwidth characteristic is identical is closed and is formed gateway Bandwidth Management group BMG;
The caller gateway is called out the called gateway that is positioned at same BMG by server;
Server judges according to the information of calling and called gateway relevant bandwidth in calling procedure whether caller gateway and called gateway outlet total bandwidth is all enough, judges then whether the inner total bandwidth of BMG of caller gateway is enough;
If described any one bandwidth does not satisfy, then the server refusal is called out, otherwise allows to call out.
The method of second kind of centralized management may further comprise the steps:
The networking that bandwidth characteristic is identical is closed and is formed gateway Bandwidth Management group BMG;
The caller gateway is called out the called gateway that is positioned at different B MG by server;
Server is according to the information of calling and called gateway relevant bandwidth in calling procedure, whether the outlet total bandwidth of judging caller gateway and called gateway is all enough, whether the inside total bandwidth of BMG of judging caller gateway and called gateway is all enough, judges then whether the BMG bandwidth between caller gateway and called gateway is enough;
If described any one bandwidth does not satisfy, then the server refusal is called out, otherwise allows to call out.
Below by the method for how carrying out comprehensive Bandwidth Management by several examples explanation servers by this Several Parameters.
As shown in Figure 2, each gateway of Pekinese is connected in the local area network (LAN) by Fast Ethernet, and the access bandwidth of each gateway all is 100M; Each gateway of Pekinese in same local area network (LAN), its internal bandwidth 100M, (if local area network (LAN) is a switching network of all being made up of switch, can inner total bandwidth be set to infinity); Pekinese's outlet total bandwidth is 50M, so the outlet bandwidth of Beijing BMG is 50M; Beijing is 20M to the maximum bandwidth in Shanghai, is 40M to the maximum bandwidth in Shenzhen, and then Beijing BMG is 20M with the bandwidth of Shanghai BMG, and Beijing BMG is 40M with the bandwidth of Shenzhen BMG.
If calling another one port from certain port of GW1 to GW1 does not use the network bandwidth in the calling procedure, do not influence each Bandwidth Management parameter on the GK in call setup, the dispose procedure.
If a calling is called out GW2 from GW1.GK receives the caller ARQ of GW1, learns that through resolving calling to GW2, judges at first whether the outlet total bandwidth of GW1 and GW2 is all enough, judges then whether the inside total bandwidth of Beijing BMG is enough.Wherein any one bandwidth does not satisfy, and then refusal is called out, otherwise allows to call out.After calling out permission, the total bandwidth of GW1, GW2 and Beijing BMG will be reduced, and behind the end of calling, recover the bandwidth that takies.
If the GW3 of Shanghai BMG is called out in a calling from the GW1 of Beijing BMG.GK receives the caller ARQ of GW1, (that is, called number is arranged among the ARQ, the mapping table of number to gateway IP arranged on the GK through resolving, can learn that by tabling look-up which gateway supports this number) learn and call out to GW3, judge that at first whether enough the outlet total bandwidth of GW1 and GW3 (promptly.The bandwidth that has current calling to take among the ARQ, just can know by the network egress total bandwidth of judging GW1 and GW3 and can support this road calling), whether the inside total bandwidth of judging Beijing BMG then is enough (promptly, the bandwidth that has current calling to take among the ARQ, known that call setup is between GW1 and GW3, just know that also call setup is between Shanghai BMG and Beijing BMG, to take the inside total bandwidth of two BMG respectively, by judge the inner total bandwidths of two BMG whether greater than current call out the bandwidth that needs just can know can support current calling), whether the internal bandwidth of judging Shanghai BMG is enough, judge that whether enough the BMG bandwidth between Beijing and Shanghai (promptly, whether judge the current bandwidth that takies of calling out greater than bandwidth between Beijing BMG and Shanghai BMG, just can know that can current calling set up).Wherein any one bandwidth does not satisfy, and then refusal is called out, otherwise allows to call out.After call out allowing, GW1, GW3,, the total bandwidth of Beijing BMG, the total bandwidth of Shanghai BMG, Beijing and Shanghai BMG bandwidth will be reduced, and behind the end of calling, recover the bandwidth that takies.
The process of above-mentioned judgement can reduce: server is being received ARQ, learn called gateway by called number, just know also call setup is between which two gateway, judge that respectively the current bandwidth that takies of calling out is whether less than the outlet total bandwidth of each gateway, no matter calling out at same BMG still is between two BMG, all to take the bandwidth of calling and called place BMG, therefore need to judge this parameter; If calling out is between two BMG, judge whether bandwidth satisfies between BMG.
Above-named is the call flow of Direct Call H.323.Also have other several calling control flow in addition, for Bandwidth Management, just Server will be according to calling out used bandwidth on the different tactful acquisition gateway.
1, the another kind of routing call in H.323:
As shown in Figure 3, clearly do not indicate this road in the signaling in this flow process between GW1 and GK and call out how many bandwidth of use, but GK can obtain calling out the code/decode type of use from message H.225 or H.245, can calculate this road according to code/decode type and call out the bandwidth that needs take.
Idiographic flow is as follows:
Caller gateway (GW1) makes a call (Setup) to GK, is opening soon under the mode, comprises the encoding and decoding tabulation that caller is supported in the current calling.CallProceeding is the affirmation to SETUP message.
GK sends to Setup called, and called answer CallProceeding message authentication has been received the Setup called terminal ringing, and called gateway GW2 replys Alerting to GK, represents called ring, and GK is transmitted to caller gateway GW1 with Alerting; Behind the called off-hook, called gateway GW2 sends Connect to GK, represents called off-hook, is opening soon under the mode, comprising the current code/decode type (the highest according to priority of selection in the encoding and decoding tabulation of GW2 from Setup) that uses of calling out.GK can calculate the employed bandwidth of current calling by the encoding and decoding among the Connect, judges whether to accept current calling according to bandwidth.
Deterministic process is with above similar substantially: if GW1 and GW2 are same gateways, allow to call out, do not influence any parameter; If GW1 and GW2 are in same BMG, judge whether the outlet total bandwidth of GW1 and GW2 is all enough, judge then whether the inside total bandwidth of they place BMG is enough.Wherein any one bandwidth does not satisfy, and then refusal is called out, otherwise allows to call out.After calling out permission, the total bandwidth of GW1, GW2 and Beijing BMG will be reduced, and behind the end of calling, recover the bandwidth that takies; If GW1 and GW3 are in different BMG, whether the outlet total bandwidth of at first judging GW1 and GW2 is enough, whether the inside total bandwidth of judging GW1 place BMG then is enough, judges whether the internal bandwidth of GW2 place BMG is enough, judges whether bandwidth is enough between GW1 place BMG and the GW2 place BMG.Wherein any one bandwidth does not satisfy, and then refusal is called out, otherwise allows to call out.After calling out permission, bandwidth between the total bandwidth of GW1, GW2, GW1 place BMG, the total bandwidth of GW2 place BMG, GW1 place BMG and the GW2 place BMG behind the end of calling, is recovered the bandwidth that takies.
If bandwidth allows, GK transmits Connect message to caller gateway GW1, otherwise call release.
Open in the flow process soon non-, there is not the negotiation of encoding and decoding among Setup and the Connect, this will finish by follow-up H.245 process, basic process is: GW1 sends to GK with the code/decode type of its support, GK is forwarded to GW2, and GW2 selects priority the highest, sends to GK, after GK knows code/decode type, can calculate institute's dedicated bandwidth.Use method mentioned above to judge whether to allow to call out by this bandwidth,, transmit message and give GW1 if allow, otherwise, call release.(determination methods is: if GW1 and GW2 are same gateways, allow to call out, do not influence any parameter; If GW1 and GW2 are in same BMG, judge whether the outlet total bandwidth of GW1 and GW2 is all enough, judge then whether the inside total bandwidth of they place BMG is enough.Wherein any one bandwidth does not satisfy, and then refusal is called out, otherwise allows to call out.After calling out permission, the total bandwidth of GW1, GW2 and Beijing BMG will be reduced, and behind the end of calling, recover the bandwidth that takies; If GW1 and GW3 are in different BMG, whether the outlet total bandwidth of at first judging GW1 and GW2 is enough, whether the inside total bandwidth of judging GW1 place BMG then is enough, judges whether the internal bandwidth of GW2 place BMG is enough, judges whether bandwidth is enough between GW1 place BMG and the GW2 place BMG.Wherein any one bandwidth does not satisfy, and then refusal is called out, otherwise allows to call out.After calling out permission, bandwidth between the total bandwidth of GW1, GW2, GW1 place BMG, the total bandwidth of GW2 place BMG, GW1 place BMG and the GW2 place BMG behind the end of calling, is recovered the bandwidth that takies.)
After GK collects bandwidth, utilize Several Parameters mentioned above that the bandwidth of VOIP network is managed equally.
2, SIP calls out
Fig. 4 has shown the flow process that SIP calls out.With H.323 routing call is similar, signaling between GW and the SIP Server does not have bandwidth parameter yet, but in INVITE, 200, ACK, there is this road of SDP information description to call out the encoding and decoding of using, SIP Server can calculate this road according to encoding and decoding and call out the bandwidth that needs take, after SIP Server collects bandwidth, utilize Several Parameters mentioned above that the bandwidth of VOIP network is managed equally.
Idiographic flow is as follows:
Caller gateway (GW1) makes a call (INVITE) to SIP SERVER, comprises the encoding and decoding tabulation that caller is supported in the current calling.100Trying is the affirmation to INVITE.
SIP Server sends to INVITE called, and called answer 100Trying message authentication has been received INVITE
Called terminal ringing, called gateway GW2 reply 180Ringing for SIP SERVER, represent called ring, and SIP SERVER is transmitted to caller gateway GW1 with 180Ringin
Behind the called off-hook, called gateway GW2 gives SIP SERVER transmission 200, represents called off-hook, comprising the current code/decode type (the highest according to priority of selection in the encoding and decoding tabulation of GW2 from INVITE) that uses of calling out.SIP SERVER can calculate the employed bandwidth of current calling by the encoding and decoding in 200, judges whether to accept current calling according to bandwidth.
Deterministic process is with above similar substantially: if GW1 and GW2 are same gateways, allow to call out, do not influence any parameter; If GW1 and GW2 are in same BMG, judge whether the outlet total bandwidth of GW1 and GW2 is all enough, judge then whether the inside total bandwidth of they place BMG is enough.Wherein any one bandwidth does not satisfy, and then refusal is called out, otherwise allows to call out.After calling out permission, the total bandwidth of GW1, GW2 and Beijing BMG will be reduced, and behind the end of calling, recover the bandwidth that takies; If GW1 and GW3 are in different BMG, whether the outlet total bandwidth of at first judging GW1 and GW2 is enough, whether the inside total bandwidth of judging GW1 place BMG then is enough, judges whether the internal bandwidth of GW2 place BMG is enough, judges whether bandwidth is enough between GW1 place BMG and the GW2 place BMG.Wherein any one bandwidth does not satisfy, and then refusal is called out, otherwise allows to call out.After calling out permission, bandwidth between the total bandwidth of GW1, GW2, GW1 place BMG, the total bandwidth of GW2 place BMG, GW1 place BMG and the GW2 place BMG behind the end of calling, is recovered the bandwidth that takies.
If bandwidth allows, SIP SERVER transmits 200 message to caller gateway GW1, otherwise call release.
ACK message is the affirmation to 200 message.
SIP carries out coding/decoding negotiation by INVITE-200 (or 180 or 183 message)-ACK three-way handshake when setting up calling, top example is to carry out coding/decoding negotiation by INVITE and 200, also can hold consultation by INVITE and 180 (or 183), can also by 200 and ACK to carry out coding/decoding negotiation (be not have coding/decoding information among the INVITE, called elder generation sends to caller to the encoding and decoding tabulation of oneself supporting by 200, and it is called that caller selects the back to reply to by ACK).Which kind of mode no matter, message is all wanted SIP Server, and SIP Server can adopt to use the same method and carry out Bandwidth Management.Here just do not describe in detail one by one.
During 3MGCP called out, the SDP information calculations that MGCP Server (MGC) reports by gateway equally went out this road and calls out the bandwidth that takies, and carries out Bandwidth Management.
The gateway interoperability
Because agreement is not carried out any privately owned expansion, the gatekeeper with bandwidth management capability of mentioning herein can be with any gateway networking, and does not influence the enforcement of Bandwidth Management.
With the interoperability between the gatekeeper who does not have bandwidth management capability
The problem that the management method of this BMG does not exist many gatekeepers to cooperate, the gatekeeper with bandwidth management capability of mentioning herein can be with any other gatekeeper's networking, and no matter being that processing domain is interior calls out or inter-domain call, does not influence the enforcement of Bandwidth Management.
Has the interoperability between the gatekeeper of different bandwidth management strategy
If two gatekeepers have the management function of this BMG, but has different band-width tacticses, such as total bandwidth between two BMG has been defined different numerical value.Because therefore the problem that the management method of this BMG does not exist many gatekeepers to cooperate does not influence the enforcement of Bandwidth Management.
In sum, can learn that the present invention realizes flexile Bandwidth Management under the prerequisite of agreement not being expanded, the adaptation diverse network is opened up general, and does not introduce inter-communicating problem.
Claims (11)
1, the method that server is managed concentratedly in a kind of speech network may further comprise the steps:
The networking that bandwidth characteristic is identical is closed and is formed gateway Bandwidth Management group BMG;
The all or part of of total bandwidth managed concentratedly bandwidth between the interior total bandwidth of server by utilizing BMG, BMG outlet total bandwidth, any two BMG.
2, the method that server is managed concentratedly in a kind of speech network may further comprise the steps:
The networking that bandwidth characteristic is identical is closed and is formed gateway Bandwidth Management group BMG;
The caller gateway is called out the called gateway that is positioned at same BMG by server;
Server judges according to the information of calling and called gateway relevant bandwidth in calling procedure whether caller gateway and called gateway outlet total bandwidth is all enough, judges then whether the inner total bandwidth of BMG of caller gateway is enough;
If described any one bandwidth does not satisfy, then the server refusal is called out, otherwise allows to call out.
3, method according to claim 2 wherein, behind end of calling, recovers to call out the bandwidth that takies.
4, method according to claim 2, wherein the calling that contains among the server by utilizing ARQ needs the information of occupied bandwidth, judge whether caller gateway and called gateway outlet total bandwidth is all enough, export total bandwidth less than caller gateway and called gateway respectively if call out the bandwidth that need take, judge that then described outlet total bandwidth is enough.
5, method according to claim 2, wherein the calling that contains among the server by utilizing ARQ needs the information of occupied bandwidth, whether the inner total bandwidth of BMG of judging the caller gateway is enough, if the bandwidth that calling need take, judges then that the inner total bandwidth of described BGM is enough less than the inner total bandwidth of caller gateway BMG.
6, the method that server is managed concentratedly in a kind of speech network may further comprise the steps:
The networking that bandwidth characteristic is identical is closed and is formed gateway Bandwidth Management group BMG;
The caller gateway is called out the called gateway that is positioned at different B MG by server;
Server is according to the information of calling and called gateway relevant bandwidth in calling procedure, whether the outlet total bandwidth of judging caller gateway and called gateway is all enough, whether the inside total bandwidth of BMG of judging caller gateway and called gateway is all enough, judges then whether the BMG bandwidth between caller gateway and called gateway is enough;
If described any one bandwidth does not satisfy, then the server refusal is called out, otherwise allows to call out.
7, method according to claim 6 wherein, behind end of calling, recovers to call out the bandwidth that takies.
8, method according to claim 6, wherein the calling that contains among the server by utilizing ARQ needs the information of occupied bandwidth, judge whether caller gateway and called gateway outlet total bandwidth is all enough, export total bandwidth less than caller gateway and called gateway respectively if call out the bandwidth that need take, judge that then described outlet total bandwidth is enough.
9, method according to claim 6, wherein the calling that contains among the server by utilizing ARQ needs the information of occupied bandwidth, whether the inner total bandwidth of BMG of judging caller gateway and called gateway is all enough, if the bandwidth that calling need take respectively less than the inner total bandwidth of the BMG of caller gateway and called gateway, judges that then the inner total bandwidth of described BGM is enough.
10, method according to claim 6, wherein the calling that contains among the server by utilizing ARQ needs the information of occupied bandwidth, judge whether the inner total bandwidth of BMG between caller gateway and called gateway is enough, if it is wide enough that the bandwidth that calling need take, is then judged the BGM between described caller gateway and called gateway less than the BMG bandwidth between caller gateway and called gateway.
11, method according to claim 6, wherein, server obtains calling out employed bandwidth information by the encoding and decoding of calling and called gateway.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100689400A CN100385857C (en) | 2004-07-14 | 2004-07-14 | Method for carrying out concentrated bandwidth management by server in voice network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100689400A CN100385857C (en) | 2004-07-14 | 2004-07-14 | Method for carrying out concentrated bandwidth management by server in voice network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1722672A true CN1722672A (en) | 2006-01-18 |
| CN100385857C CN100385857C (en) | 2008-04-30 |
Family
ID=35912648
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100689400A Expired - Fee Related CN100385857C (en) | 2004-07-14 | 2004-07-14 | Method for carrying out concentrated bandwidth management by server in voice network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100385857C (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102075411A (en) * | 2009-11-25 | 2011-05-25 | 杭州华三通信技术有限公司 | Call admission control method of Internet protocol voice and call processor |
| CN104468536A (en) * | 2014-11-25 | 2015-03-25 | 中国电子科技集团公司第三十研究所 | QoS guarantee method and system based on one-time connection establishment process in wireless VoIP environment |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1999004547A1 (en) * | 1997-07-15 | 1999-01-28 | British Telecommunications Public Limited Company | Multimedia call handling |
| JP3346234B2 (en) * | 1997-08-12 | 2002-11-18 | ケイディーディーアイ株式会社 | Inter-route control communication system between circuit switching network and Internet network. |
| GB0106918D0 (en) * | 2001-03-20 | 2001-05-09 | Marconi Comm Ltd | VoIP SYSTEMS |
| CN1199458C (en) * | 2002-04-18 | 2005-04-27 | 华为技术有限公司 | All-process backup video communication system |
-
2004
- 2004-07-14 CN CNB2004100689400A patent/CN100385857C/en not_active Expired - Fee Related
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102075411A (en) * | 2009-11-25 | 2011-05-25 | 杭州华三通信技术有限公司 | Call admission control method of Internet protocol voice and call processor |
| CN104468536A (en) * | 2014-11-25 | 2015-03-25 | 中国电子科技集团公司第三十研究所 | QoS guarantee method and system based on one-time connection establishment process in wireless VoIP environment |
| CN104468536B (en) * | 2014-11-25 | 2017-10-31 | 中国电子科技集团公司第三十研究所 | QoS assurance and system based on a link setup process under a kind of Wireless VoIP environment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100385857C (en) | 2008-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103634490B (en) | The gateway that a kind of enterprise network being provided for use SIP can be survived | |
| CN1941753A (en) | IP interconnected gateway in next-generation Internet and method for interconnecting IP domain | |
| CN1361994A (en) | Capability negotiation in a telecommunications network | |
| CN1913472A (en) | Voice over IP network architecture | |
| CN1633102A (en) | Method for implementing NAT traversing and system thereof | |
| CN1879357A (en) | Serverless and switchless internet protocol telephony system and method | |
| CN1925450A (en) | Communication method preventing circumbendibus of media-flow | |
| CN1652561A (en) | Call processing system and method in a voice and data integrated switching system | |
| CN1968327A (en) | System and method of proxy independent hunt group function in a packet based network | |
| CN1445967A (en) | Method for receiving call | |
| CN1870691A (en) | Method for listening dailed signal sound at dail line terminal when network communicating | |
| CN101056418A (en) | A bandwidth control method and terminal device | |
| CN101079807A (en) | A mesh relaying method and IP communication system for controlling media transmission path | |
| CN1882116A (en) | Mobile switching centre built in video gateway and method for realizing multimedia interconnection | |
| CN1497906A (en) | System and method for generating ringbace tone | |
| CN1819565A (en) | System and method for realizing bridging in IP multi-media subsystem | |
| CN1553676A (en) | Method for holding common audio-video meeting via various protocol terminals | |
| CN1878173A (en) | IP multimedia subsystem domain user access controlling method and its system | |
| CN1855931A (en) | Method for processing upload event of media gateway in network of the latter generation | |
| CN1645861A (en) | Flexible exchanging network method for passing fire wall | |
| CN1838616A (en) | Media stream shunting system and method | |
| CN1610340A (en) | A multimedia communication safe proxy gateway and safety proxy method | |
| CN100417153C (en) | Network system and method for processing VOIP business based on media net-link control protocol | |
| CN1719788A (en) | Method for call controlling and service monitoring of soft exchange monitoring | |
| CN1722672A (en) | Method for carrying out concentrated bandwidth management by server in voice network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: HANGZHOU HUASANTONG TECHNOLOGY CO.,LTD. Free format text: FORMER OWNER: HANGZHOU HUAWEI 3COM TECHNOLOGY CO., LTD. Effective date: 20070720 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20070720 Address after: 310053 HUAWEI Hangzhou production base, No. 310 Liuhe Road, Hangzhou hi tech Industrial Development Zone, Zhejiang Applicant after: Hangzhou Huawei-3Com Technology Co., Ltd. Address before: 310053, Hangzhou hi tech Industrial Development Zone, Zhejiang hi tech Industrial Park, Liuhe Road, Donghua, Hangzhou production base Applicant before: Huawei Sankang Technology Co., Ltd., Hangzhou |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CI01 | Correction of invention patent gazette |
Correction item: Patentee Correct: Huasan Communication Technology Co., Ltd. False: Hangzhou Huawei-3Com Technology Co., Ltd. Number: 18 Volume: 24 |
|
| CI03 | Correction of invention patent |
Correction item: Patentee Correct: Huasan Communication Technology Co., Ltd. False: Hangzhou Huawei-3Com Technology Co., Ltd. Number: 18 Page: The title page Volume: 24 |
|
| ERR | Gazette correction |
Free format text: CORRECT: PATENTEE; FROM: HANGZHOU H3C TECHNOLOGY CO., LTD. TO: HUASAN COMMUNICATION TECHNOLOGY CO., LTD. |
|
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080430 Termination date: 20200714 |