CN100493070C

CN100493070C - Media gateway command serial method

Info

Publication number: CN100493070C
Application number: CNB2004100629984A
Authority: CN
Inventors: 林扬波
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2004-06-27
Filing date: 2004-06-27
Publication date: 2009-05-27
Anticipated expiration: 2024-06-27
Also published as: CN1713634A

Abstract

The media gateway previously creates a queue used in buffer for each terminal. When the terminal detects an event, if the descriptor of event enabled by the terminal is locked, or is not locked, but the previous command is not completed, then decides if the terminal is physical terminal. If yes, then makes selectable abandon or buffer for all non reported event in the terminal, otherwise directly buffers detected event.

Description

Media gateway command serial method

Technical field

The present invention relates to the communications field, particularly the media gateway in the next generation network.

Background technology

Development of telecom technology will cause the next generation network large-scale application of (Next Generation Network is called for short ＂ NGN ＂).And based on the starting point of protecting original communication network investment; NGN must support seamlessly transitting existing telecommunication service network; so NGN must keep the compatibility to original communication network in considerable time; the gateway device that different business, distinct interface, difference in functionality conversion can be provided must be arranged between the so different networks; and; along with technical development; deepening continuously of problem understanding; proposed the thought of gateway function separation again, be about to gateway function and be decomposed into high-rise control and underlying resource management/medium processing two parts called out.Those of ordinary skill in the art will be appreciated that, by the critical piece after the above-mentioned thought decomposition is Media Gateway Controller (Media Gateway Controller, be called for short ＂ MGC ＂) and media gateway (Media Gateway is called for short ＂ MG ＂), they are two key members among the NGN.MGC is responsible for CCF, and it is grasping the availability of each resource.MG is responsible for the service bearer function, i.e. the hardware operation that the exchange of Media Stream and processing need in the media gateway.Each performs its own functions works in coordination again for two parts, realize by this calling out separating of control plane and service bearer plane, thereby abundant shared network resource, simplified apparatus upgrading and professional expansion, reduce development and maintenance cost greatly, the bottleneck that function is too concentrated becomes network can not occur, become outside open agreement between MGC and MG yet, make things convenient for the intercommunication between the product of different vendor by original internal agreement.As shown in Figure 1:

In Fig. 1, protocol network 1 is the network that institute's protocols having transmits, Media Gateway Controller 10 and media gateway 11 are got in touch by MGCP 110, Media Gateway Controller 10 and media gateway 12 are got in touch by MGCP 120, and MGCP 110 can be different agreements with MGCP 120.MGCP is the main agreement of communicating by letter between MG and the MGC, present widely used H.248 (the MediaGateway Control/H.248 of MGCP that has, be called for short H.248/MeGaCo ＂ of ＂) and two kinds of agreements of MGCP MGCP (Media Gateway Control Protocol is called for short ＂ MGCP ＂).Wherein, the MGCP agreement is by internet engineering task group (Internet Engineering Task Force, be called for short ＂ IETF ＂) work out and revise in October, 1999 in January, 2003, H.248/MeGaCo agreement is revised in common formulation of in November, 2000 and in June, 2003 by IETF and International Telecommunications Union's (International Telecommunication Union is called for short ＂ ITU ＂).

Among Fig. 1, media gateway 11, media gateway 12 connect by RTP 140 under Media Gateway Controller 10 controls.Iso-ip Internetworking protocol ISO-IP 130 carrying media gateway control protocols 110, MGCP 120 and RTP 140 transmit in protocol network 1.

Among Fig. 1, user terminal 13 is by media gateway 11 access protocol networks 1, and user terminal 14 is by media gateway 12 access protocol networks 1.To realize by the agreement of various device in the protocol network 1 and equipment room alternately of 14 of user terminal 13 and user terminals.

Among Fig. 1, the various resources on media gateway 11, the media gateway 12 are the H.248 terminal (Termination) in the agreement or the end points (Endpoint) in the MGCP agreement by abstract representation.Terminal is divided into physical terminal and ephemeral terminations again, on behalf of some, the former have the physical entity of semipermanent existence, time division multiplexing (Time Division Multiplex for example, be called for short ＂ TDM ＂) passage etc., the public resource that on behalf of some provisional application, the latter discharge with the back, RTP (Real-time TransportProtocol is called for short ＂ RTP ＂) stream etc. for example.

Combination between terminal or the end points is the H.248 context (Context) in the agreement or the connection (Connection) in the MGCP agreement by abstract representation.Context can comprise a plurality of terminals, thereby describes the correlation of terminal room with topology (Topology).Connect and only comprise two end points, thereby directly just reflected its correlation.

Based on the abstract model of these two kinds of agreements, in fact continuing of calling be exactly to terminal and context or end points and the operation that is connected.

Media Gateway Controller 10 and media gateway 11, undertaken alternately by protocol command (Command) between the media gateway 12, order entrained parameter to be divided into signal (Signal), incident classifications such as (Event), wherein signal is used to refer to media gateway 11 by Media Gateway Controller 10 or media gateway 12 is carried out the operation of resource, for example put dialing tone to the user, ring-back tone, busy tone etc., incident is used to refer to media gateway 11 by Media Gateway Controller 10 or media gateway 12 is carried out the monitoring of state, for example the monitor user ' off-hook, on-hook, dialing, hooking etc.

The various control details of call proceeding and resource operation are being represented in order, and therefore the execution of order needs strict assurance order.Even but IP bearer network unreliable causes order is order when sending, still might be out of order when receiving even lose, so must take certain mechanism to guarantee to order orderly being transmitted and carrying out.

H.248 the agreement defined order can be combined into affairs (Transaction) and transmits and carry out, and the correlation of order is limited range with affairs, also be that the order in the same affairs is carried out by its sequencing, and the order in the different affairs can executed in parallel.Different with the form of the H.248 many orders of the single affairs of agreement, the MGCP agreement is the form of single affairs single command, therefore also just meets this requirement naturally.

For the execution sequence of ordering in the different affairs following some rule is arranged:

● for agreement H.248, at the order of the different terminals transmission that can walk abreast.For the MGCP agreement, at the transmission that also can walk abreast of the different orders that connect on different end points or the same end points.

● for agreement H.248,8 basic commands are arranged between MGC and the MG, are respectively:

(1) adds (Add)

(2) revise (Modify)

(3) delete (Subtract)

(4) move (Move)

(5) audit value (AuditValue)

(6) auditability (AuditCapabilities)

(7) circular (Notify)

(8) professional change (ServiceChange)

Should have only a uncompleted interpolation (Add) on the terminal at most, revise (Modify) or move (Move) order, unless these orders in same affairs, but delete that (Subtract) order can at any time send.

For the MGCP agreement, 9 basic commands are arranged between MGC and the MG, be respectively

(1) service request (RQNT);

(2) circular (NTFY);

(3) create connection (CRCX);

(4) revise connection (MDCX);

(5) deletion connects (DLCX);

(6) audit endpoint (AUEP);

(7) audit connects (AUCX);

(8) restart and carry out (RSIP);

(9) endpoint configurations (EPCF).

Should have only the order of a uncompleted service request (RQNT) or endpoint configurations (EPCF) on the end points at most, also should have only a uncompleted establishment to connect (CRCX) in the connection at most or revise to connect (MDCX) order, can at any time send but deletion connects (DLCX) order.

● for the transmission (for example UDP) that does not guarantee that message sequence transmits, should have only the Notify of a uncompleted H.248 agreement to order at most on the terminal, also should have only the NTFY of a uncompleted MGCP agreement to order at most on the end points.Need to prove, these two orders H.248 with MGCP in function class seemingly.

● the H.248 AuditValue of agreement and AuditCapabilities order, the AUEP of MGCP agreement and AUCX order are not subjected to any sequence limit.

● the ServiceChange of agreement H.248, the RSIP order of MGCP agreement, the first order that in restarting process, sends of MG always, other any order or respond and must after this order, be sent out.

Based on above-mentioned rule, the order the recipient with affairs as independent executable unit, if exist a plurality of orders then to carry out by its sequencing, the order in the different affairs then both can be carried out by the serial of reception order in the same affairs, also can ignore the order executed in parallel.Therefore if there is correlation, then Ming Ling transmit leg must effectively ensure its execution sequence the recipient between ordering.

For Media Gateway Controller 10, need to ensure Add, Modify or the Move order of having only a uncompleted H.248 agreement on the terminal at most, perhaps have only the RQNT of a uncompleted MGCP agreement or EPCF to order on an end points, have only the CRCX of a uncompleted MGCP agreement or MDCX to order in the connection.For can the MGC of controlling call process, order as long as after last order is by response, send back one again.

For media gateway 11 and media gateway 12, need to ensure that the Notify that has only a uncompleted H.248 agreement on a terminal or the end points at most orders or the NTFY order of MGCP agreement.Because it is user's operation mostly that media gateway 11 and media gateway 12 report the information of Media Gateway Controller 10, for example off-hook, on-hook, dialing, hooking etc., and user operation is often at random, thus media gateway 11 and media gateway 12 need to set up than Media Gateway Controller 10 complexity the mechanism of Duoing ensures that the order that reports of oneself carried out by serial at Media Gateway Controller 10.

Prior art one is, use the reliable host-host protocol that connects, for example TCP guarantees to order serial, the application layer that is transmit leg only needs the command messages that is ready for sending is consigned to transport layer, utilizes the reliability mechanisms of host-host protocol to guarantee that each bar message sequence arrives at the recipient.Before last order does not meet with a response as yet, subsequent commands will be buffered in the transmit queue of transport layer like this, and the mechanism that sends by the message serial has also just reached the purpose that the order serial is carried out naturally.

Prior art two is: use the incident of the incident buffer memory (EventBuffer) of agreement H.248 or MGCP agreement to isolate (EventQuarantine) mechanism and guarantee to order serial, promptly when occurring reporting events on certain terminal or the end points and not meeting with a response as yet, subsequent detection to incident based on certain screening conditions elder generation's temporary cache or isolate in the fifo queue of setting up for this terminal or end points, need to prove that this formation exists among the MG.From this formation, choose reporting events based on certain condition again Deng after the response that receives last reporting events, and the incident that does not meet alternative condition will be dropped.

H.248 agreement uses the Events descriptor that the report condition of incident is set; Use the EventBuffer descriptor that the buffer memory condition of incident is set; Using the EventBufferControl attribute that incident buffer memory fifo queue is set is to close (Off), also is based on the set condition of Events descriptor therefrom single pick and reported event (LockStep).

The MGCP agreement uses the RequestedEvents tabulation that the report condition of incident is set; Use DetectEvents and RequestedEvents tabulation that the buffer memory condition of incident is set; Using the QuarantineHandling parameter that incident is set, to isolate this fifo queue be that processed (Process) still is dropped (Discard), and tabulating based on RequestedEvents that set condition therefrom chooses with reported event is only to allow single (Step) or repeatedly (Loop).

Summary of the invention

In view of this, main purpose of the present invention is to provide a kind of media gateway command serial method, makes media gateway can simply and efficiently realize the order serial.

For achieving the above object, the invention provides a kind of media gateway command serial method, comprise following steps:

The described media gateway of A is that each terminal of being managed is respectively created a formation that is used for buffer memory;

When B detected an incident when described terminal, described media gateway judged whether that the event descriptor of the current activation of this terminal is locked, if then enter step C; Otherwise, judge in the event descriptor of the current activation of this terminal whether comprise detected described incident, if then enter step B3, otherwise abandon this incident;

B3 judges whether previous circular order is not also finished, if then enter step C, otherwise reports detected described incident;

C is cached to detected described incident in the formation of this terminal.

Wherein, described step B also further comprises following substep:

When B1 detected an incident when described terminal, described media gateway judged whether the event descriptor of the current activation of this terminal is locked, if then enter step C, otherwise enters step B2;

B2 judges in the event descriptor of the current activation of this terminal whether comprise detected described incident, if then enter step B3, otherwise abandons this incident;

B3 judges whether previous order is not also finished, if then enter step C, otherwise reports detected described incident.Described step C also further comprises following substep:

C1 judges that whether described terminal is physical terminal, if then enter step C2, otherwise enters step C3;

C2 is according to described detected incident and nearest reported event, in the formation of this detected incident and this terminal all as yet not reported event abandon selectively or buffer memory based on real-time effectiveness;

C3 is cached to described detected incident in the formation of this terminal.

Described step C2 also further comprises following substep:

C21 judges that whether described detected incident is a kind of of off-hook, on-hook, hooking, during dialing, if then according to this detected incident and nearest reported event, to in the formation of this detected incident and this terminal all as yet not reported event abandon selectively or buffer memory based on real-time effectiveness, otherwise this detected incident is cached in the formation of this terminal.

When described nearest reported event was off-hook, described step C21 also further comprised following substep:

C211 judges whether described detected incident is off-hook, if then empty existing incident in the formation of described terminal, and abandons described detected incident;

C212 judges whether described detected incident is on-hook or hooking, if then empty existing incident in the formation of described terminal, and described detected incident is cached to the end of this formation;

C213 judges whether described detected incident is dialing, if then recall nearest off-hook or hookflash event forward from the formation end of described terminal,

If what find earlier is nearest off-hook event, then empty incident and this nearest off-hook event itself more Zao in this formation than this nearest off-hook event, more described detected incident is cached to the end of this formation,

If what find is nearest hookflash event, then empty incident more Zao in this formation than this nearest hookflash event, more described detected incident is cached to the end of this formation,

If do not find nearest off-hook or hookflash event, then described detected incident is cached to the end of this formation.

When described nearest reported event was on-hook, described step C21 also further comprised following substep:

C214 judges whether described detected incident is off-hook, if then empty existing incident in the formation of described terminal, more described detected incident is cached to the end of this formation;

C215 judges whether described detected incident is on-hook, if then empty existing incident in the formation of described terminal, and abandons described detected incident;

C216 judges whether described detected incident is hooking or dialing, if then recall nearest off-hook event forward from the formation end of described terminal,

If can find nearest off-hook event, then empty incident more Zao and more late in this formation than this nearest off-hook event, more described detected incident is cached to the end of this formation;

If do not have to find nearest off-hook event, then empty existing incident in this formation, and abandon described detected incident, start terminal abnormal and handle.

When described nearest reported event was hooking or dialing, described step C21 also further comprised following substep:

C217 judges whether described detected incident is off-hook, if then recall nearest onhook event forward from the formation end of described terminal,

If can find nearest onhook event, then empty existing incident more Zao in this formation than this nearest onhook event, more described detected incident is cached to the end of this formation,

If do not have to find nearest onhook event, then empty existing incident in this formation, and abandon described detected incident, start terminal abnormal and handle;

C218 judges whether described detected incident is on-hook or hooking, if then empty existing incident in the formation of described terminal, more described detected incident is cached to the end of this formation;

C219 judges whether described detected incident is dialing, if then described detected incident is cached to the formation end of described terminal.

When described terminal obtains new event descriptor, comprise following steps:

D judges that whether the formation of described terminal is empty, if not then getting in this formation first incident and entering step e;

E judges whether new described event descriptor comprises this incident, if enter step F, otherwise removes this incident and enter step D from this formation;

F judges whether previous circular order is not also finished, if not then reporting this incident and remove this incident from this formation.

When described terminal obtains the response of previous circular order, comprise following steps:

H judges whether the event descriptor of the current activation of described terminal is locked, if not then entering step I;

I judges that whether the formation of described terminal is empty, if not then getting in this formation first incident and entering step J;

J judges whether the event descriptor of the current activation of described terminal comprises this incident, if then report this incident and remove this incident from this formation, otherwise removes this incident and enter step I from this formation.

By relatively finding, technical scheme difference with the prior art of the present invention is, media gateway is that each terminal of being managed is respectively created a formation (prior art is just to carry out the foundation of formation later at the related command of receiving Media Gateway Controller) that is used for buffer memory in advance, when terminal detects an incident, if the event descriptor of the current activation of this terminal is locked, though or not locked but previous order is not also finished, judge then whether this terminal is physical terminal, if then to this terminal all as yet not reported event abandon selectively based on real-time effectiveness or buffer memory (prior art not to as yet not reported event abandon selectively based on real-time effectiveness or the mechanism of buffer memory), otherwise the direct detected incident of buffer memory.

Difference on this technical scheme, brought comparatively significantly beneficial effect, promptly because each terminal has been pre-created the formation that is used for buffer memory, and after the response of receiving the previous command, just report incident on the queue heads, therefore can guarantee the serial of ordering according to first in first out.Because formation is pre-created, thus can be so that command string is capable independently to be realized by media gateway, and do not rely on Media Gateway Controller, implementation is more simple.Select to abandon by operated physical terminal being carried out having of incident, can significantly reduce reporting of invalid event, improve the efficient of order serial.This in addition technical scheme goes for any host-host protocol.Especially unreliable host-host protocol has also avoided simultaneously using the decline of the interactive efficiency that reliable transport protocol brings.

Description of drawings

Fig. 1 is MG and a MGC networking schematic diagram among the NGN;

Fig. 2 is that the real-time validity event of MG buffer memory is realized order serial schematic diagram;

Fig. 3 is an event detection handling process schematic diagram;

Fig. 4 abandons based on current validity or the regular flow chart of buffer memory selectively to all incidents that do not report as yet;

Fig. 5 is that off-hook event is handled the sub-rule flow chart;

Fig. 6 is that onhook event is handled the sub-rule flow chart;

Fig. 7 is that hooking or dialer event are handled the sub-rule flow chart;

Fig. 8 is the event descriptor process chart;

Fig. 9 is a circular response process chart.

Embodiment

For making the purpose, technical solutions and advantages of the present invention clearer, the present invention is described in further detail below in conjunction with accompanying drawing.

Describe below according to principle of the present invention, describe the solution simply efficiently that the serial for media gateway realization Notify order provides in detail.And emphasis is set forth core content of the present invention: media gateway is initiatively created First Input First Output, and the real-time validity event of buffer memory guarantees the serial transmission and the execution of order.

As shown in Figure 2, media gateway 20 is exactly the media gateway 11 among Fig. 1, and Media Gateway Controller 21 is exactly the Media Gateway Controller 10 among Fig. 1.Fig. 2 illustrates the real-time validity event realization of MG buffer memory order serial with these two equipment room signaling flow schematic forms.Media gateway MG initiatively is that each terminal is respectively enabled first-in first-out (First In First Out is called for short a ＂ FIFO ＂) formation that is initialized as sky as the incident buffer memory.Need to prove that this formation is present on the media gateway 20, for better explanation in logic, incident buffer memory 22 and separately expression of media gateway 20, the two will be in a physical equipment in the reality among Fig. 2.Below each step among Fig. 2 is described in detail.

Step 201, Media Gateway Controller 21 sends request command to media gateway 20, has carried the event descriptor that comprises incident 1 in this request command, also promptly requires to detect this incident.

Step 202, media gateway 20 sends response command to Media Gateway Controller 21, confirm to have received the request command in the step 201, the event descriptor of carrying in this request command becomes the event descriptor of current activation, its incident that comprises 1 will be detected with report.

Step 203, media gateway 20 detects the generation of incident 1.Because the event descriptor of current activation is not locked, then can directly determine whether report according to the event descriptor content.

It is the incident that comprises in the event descriptor of current activation that step 204, media gateway 20 are examined incident 1, and therefore decision reports incident of detecting 1 and lock event descriptor.

Step 205, media gateway 20 sends request command to Media Gateway Controller 21, and circular incident 1 has been detected.

Step 206, media gateway 20 detects the generation of incident 2, because the event descriptor of current activation is locked, therefore needs to consider its buffer memory.The result event of judging based on real-time effectiveness 2 is current effective, therefore is appended in the incident buffer memory.

Step 207, Media Gateway Controller 21 sends response command to media gateway 20, and the affirmation step has been received the request command in 205.

Step 208, media gateway 20 detects the generation of incident 3, because the event descriptor of current activation is locked, therefore needs to consider its buffer memory.The result event of judging based on real-time effectiveness 3 is current effective, therefore is appended in the incident buffer memory.

Step 209, Media Gateway Controller 21 sends request command to media gateway 20, has carried the event descriptor that comprises incident 3 in this request command, also promptly requires to detect this incident.

Step 210, media gateway 20 sends response command to Media Gateway Controller 21, confirm to have received the request command in the step 209, the event descriptor of carrying in this request command becomes the event descriptor of current activation, its incident that comprises 3 will be detected with report.

Step 211, media gateway 20 begins to scan the incident of buffer memory according to the new event descriptor that activates from incident buffer memory head.The incident 2 of finding first buffer memory is not the incident that comprises in the event descriptor of current activation, therefore determines removing incident 2.The incident 3 of finding the back buffer memory again is the incidents that comprise in the event descriptor of current activation, therefore determines reported event 3 and lock event descriptor.

Step 212, media gateway 20 sends request command to Media Gateway Controller 21, and circular incident 3 has been detected.

Step 213, media gateway 20 detects the generation of incident 4, because the event descriptor of current activation is locked, therefore needs to consider its buffer memory.The result event of judging based on real-time effectiveness 4 is current effective, therefore is appended in the incident buffer memory.

Step 214, Media Gateway Controller 21 sends response command to media gateway 20, and the affirmation step has been received the request command in 212.

Step 215, media gateway 20 detects the generation of incident 5, because the event descriptor of current activation is locked, therefore needs to consider its buffer memory.The result event of judging based on real-time effectiveness 5 is current effective, therefore is appended in the incident buffer memory.

Step 216, media gateway 20 detects the generation of incident 8, because the event descriptor of current activation is locked, therefore needs to consider its buffer memory.The incident 4,5 of buffer memory etc. is current invalid before this for the result who judges based on real-time effectiveness, therefore is eliminated the outgoing event buffer memory, and incident 8 is current effectively, therefore is appended to the incident buffer memory.

Step 217, Media Gateway Controller 21 sends request command to media gateway 20, has carried the event descriptor that comprises incident 8 in this request command, also promptly requires to detect this incident.

Step 218, media gateway 20 sends response command to Media Gateway Controller 21, confirm to have received the request command in the step 217, the event descriptor of carrying in this request command becomes the event descriptor of current activation, its incident that comprises 8 will be detected with report.

Step 219, media gateway 20 begins to scan the incident of buffer memory according to the new event descriptor that activates from incident buffer memory head.The incident 8 of finding buffer memory is the incidents that comprise in the event descriptor of current activation, therefore determines reported event 8 and lock event descriptor.

Step 220, media gateway 20 sends request command to Media Gateway Controller 21, and circular incident 8 has been detected.

Step 221, Media Gateway Controller 21 sends response command to media gateway 20, and the affirmation step has been received the request command in 220.

Need to prove, media gateway 20 replaces former event descriptor and unlocks except receiving new event descriptor and allows again the reporting events, can also replace former event descriptor and unlock and allow reporting events again by activating embedded event descriptor mode, embedded event descriptor is in order to reduce the mutual amount of message, by Media Gateway Controller 21 when sending new event descriptor, two new events descriptors are merged into together in an order send, second event descriptor is embedded in first event descriptor, locking back second in first event descriptor activates automatically, but after activating, the definition that not to be subsequent detection satisfied event descriptor to incident just is sent out, and can send next incident after the circular request that must wait until previous incident has had corresponding response at once.

Above describe, in general terms the real-time validity event of media gateway buffer memory realize the order serial, and and Media Gateway Controller between the signaling flow situation, specifically describe event detection, event descriptor on the media gateway below in conjunction with flow chart, the flow processing situation of circular response.

Shown in Figure 3 is a situation according to this programme, i.e. handling process when certain terminal on the MG detects any incident.

As shown in the figure, at first, in step 3000, MG detects new incident will trigger following flow process.

In step 3100, detect the event descriptor lock condition.If event descriptor is locked, i.e. existing incident was reported in the event descriptor of current activation, then entered step 3200.Otherwise enter step 3110.

In step 3110,, therefore detect the situation that whether contains this incident in the event descriptor in this step owing in step 3100, judge the event descriptor non-locking.If this incident does not occur, just enter step 3111 in the event descriptor of current activation.Otherwise enter step 3120.

In step 3111, owing in step 3110, do not contain this incident in the judgement event descriptor, therefore abandon this incident in this step, finish then.

In step 3120,, therefore detect the performance of circular (Notify) request on this terminal in this step owing in step 3110, contain this incident in the judgement event descriptor.Do not have uncompleted circular request if this terminal is current, then enter step 3130 immediately.Otherwise, enter step 3200.

In step 3130, do not have uncompleted circular request because this terminal of judgement is current in step 3120, so report MGC by the circular request in this step subsequently, finish then.

Then in step 3200, because in step 3100, detect that existing incident was reported in the event descriptor of current activation, promptly event descriptor is locked, enters this step.Perhaps because in step 3120, detect that terminal is current a uncompleted circular signaling, also enter this step.Therefore sense terminals situation in this step if physical terminal then enters step 3210, otherwise enters step 3300.

In step 3210, owing to judge that in step 3200 this terminal is a physical terminal, therefore in this step according to incident that has reported recently and the firm recently incident that detects, all incidents that do not report are as yet abandoned or buffer memory selectively based on its current validity.Finish then.

In step 3300, owing to judge that in step 3200 this terminal is a for example rtp streaming of ephemeral terminations, and event is less so do not need to optimize direct end of adding this incident to the incident buffer memory on the ephemeral terminations, also be the end of fifo queue, finish then.

In this example, because in the incident that physical terminal for example may be detected on the TDM passage, off-hook, on-hook, hooking, dialing are the most frequent and bigger to the call proceeding influence, for the incident of buffer memory being done cleaning, reducing unnecessary incident sends to raise the efficiency, therefore also need according to incident that has reported recently and the firm recently incident that detects as above-mentioned, all incidents that do not report are as yet abandoned or buffer memory selectively based on its current validity, following rule is followed in its processing, and promptly the step 3210 among Fig. 3 needs to handle step by step in more detail.Be described in detail below in conjunction with Fig. 4, Fig. 5, Fig. 6, Fig. 7.

As shown in Figure 4:

In explanation rule, the judgment processing of nearest reported event promptly appears carrying out after the new detection incident in explanation system convention flow process earlier, according to concrete event type its treatment step is described again after having judged the reported event type, i.e. each sub-rule at once.

At first, step 4000 detects new this flow process of Event triggered.

Next in step 4100, judge whether nearest detection incident is the frequent incident of off-hook, on-hook, hooking, dialing and so on.If detection incident recently is not frequent incident, then enters step 4110, otherwise enter step 4200.

In step 4110, owing to judge that in step 4100 nearest detection incident is not frequent incident, therefore direct in this step end of adding this incident to the incident buffer memory, the i.e. end of fifo queue.

In step 4200,, therefore judge in this step whether the incident that has reported recently is off-hook, if off-hook event then enters step 4210 owing to judge that in step 4100 nearest detection incident is frequent incident.Otherwise enter step 4300.

In step 4210, owing to judge that in step 4200 incident that has reported recently is an off-hook event, therefore handle the incident that has just detected recently based on this condition in this step, the back illustrates in conjunction with Fig. 5.

In step 4300,, therefore judge in this step whether the incident that has reported recently is on-hook, if onhook event then enters step 4310, otherwise enters step 4400 owing to judge that in step 4200 incident that has reported recently is not an off-hook event.

In step 4310, owing to judge that in step 4300 incident that has reported recently is an onhook event, therefore handle the incident that has just detected recently based on this condition in this step, the back illustrates in conjunction with Fig. 6.

In step 4400, owing to judge that in step 4300 incident that has reported recently is not an onhook event, therefore judge in this step whether the incident that has reported recently is hooking or dialing, if hooking or dialer event then enter step 4410, otherwise finish.

In step 4410, owing to judge that in step 4400 incident that has reported recently is hooking or dialing, therefore handle the incident that has just detected recently based on this condition in this step, the back illustrates in conjunction with Fig. 7.

Illustrate recently that below in conjunction with Fig. 5 reported event is the handling process of firm detected incident under the off-hook condition.

As shown in Figure 5: at first carry out step 5000, the incident that has reported recently is an off-hook.

Then enter step 5100, judge whether the incident that detects recently is off-hook event,, then enter step 5110, otherwise enter step 5200 if the incident that detects is an off-hook event recently.

In step 5110, owing to judge that in step 5100 incident that detects recently is an off-hook event, therefore empty existing incident in the incident buffer memory in this step, abandon this off-hook event simultaneously, then process ends.

In step 5200,, therefore judge in this step whether the incident that detects recently is on-hook or hookflash event, if then enter step 5210, otherwise enters step 5300 owing in step 5100, judge the non-off-hook event of incident that detects recently.

In step 5210, owing to judge that in step 5200 incident that detects recently is on-hook or hookflash event, therefore empty existing incident in the incident buffer memory in this step, again the end of adding this on-hook or hookflash event to the incident buffer memory, process ends then.

In step 5300,, therefore judge in this step whether the incident that detects recently is dialer event, if not dialer event, so with regard to process ends owing in step 5200, judge non-on-hook of incident or the hookflash event that detects recently.If dialer event need be recalled nearest off-hook or hookflash event forward from incident buffer memory end, enter step 5310 and further handle.

In step 5310, begin to recall from incident buffer memory end, if also have incident not to be examined, enter step 5320 so, if all incidents were examined, enter step 5350 so.

In step 5320, get first also not checked incident forward from incident buffer memory end, enter step 5330.

In step 5330, whether the incident of getting is off-hook event in the determining step 5320, is then to enter step 5331, otherwise enters step 5340.

In step 5331, owing in step 5330, judge and find nearest off-hook event earlier, therefore empty existing incident and this off-hook event itself more Zao in the incident buffer memory, the end of again this dialer event being added to the incident buffer memory, process ends then in this step than this off-hook event.

In step 5340, whether the incident of getting is hookflash event in the determining step 5320, is then to enter step 5341 to handle, otherwise returns step 5310.

In step 5341,, therefore empty existing incident more Zao in the incident buffer memory, the end of again this dialer event being added to the incident buffer memory, process ends then in this step than this hookflash event because nearest hookflash event is found in judgement earlier in step 5340.

In step 5350, owing to all do not have in the incident buffer memory, to find nearest off-hook or hookflash event through above-mentioned steps, therefore direct end of adding this dialer event to the incident buffer memory, process ends then.

Illustrate recently that below in conjunction with Fig. 6 reported event is the handling process of firm detected incident under the receiver-on-hook condition.

As shown in Figure 6: at first carry out step 6000, the incident that has reported recently is on-hook.

Then enter step 6100, judge that whether nearest detection incident is off-hook event, if detection incident recently is an off-hook event, then enters step 6110.Otherwise enter step 6200.

In step 6110, owing to judge that in step 6100 incident that has just detected recently is an off-hook event, therefore empty existing incident in the incident buffer memory in this step, again this off-hook event is added to incident buffer memory end, process ends then.

In step 6200,, judge therefore whether the incident that has just detected recently is onhook event, if then enter step 6210, otherwise enters step 6300 owing to judge that in step 6100 incident that has just detected recently is not an off-hook event.

In step 6210, owing to judge that in step 6200 incident that has just detected recently is an onhook event, therefore empty existing incident in the incident buffer memory in this step, abandon this onhook event simultaneously, then process ends.

In step 6300,, judge therefore whether the incident that has just detected recently is hooking or dialer event, if not hooking or dialer event, so with regard to process ends owing to judge that in step 6200 incident that has just detected recently is not an onhook event.Otherwise, need recall nearest off-hook event forward from incident buffer memory end, enter step 6310 and further handle.

In step 6310, begin to recall from incident buffer memory end, if also have incident not to be examined, enter step 6320 so, if all incidents were examined, enter step 6340 so.

In step 6320, get first also not checked incident forward from incident buffer memory end, enter step 6330.

In step 6330, whether determining step 6320 incident of getting is off-hook event, is then to enter step 6331, otherwise returns step 6310.

In step 6331, owing in step 6330, judge and find nearest off-hook event, therefore empty existing incident more Zao and more late in the incident buffer memory, the end of again this hookflash event being added to the incident buffer memory, process ends then in this step than this off-hook event.

In step 6340, owing to all not have to find nearest off-hook event in the incident buffer memory through above-mentioned steps, so this step empties the existing incident in the incident buffer memory, abandons this hooking or dialer event simultaneously, starts the terminal abnormal processing, then process ends.Need to prove, for example this terminal is withdrawed from service and uploaded state and lose and just belong to a kind of terminal abnormal processing mode.

Illustrate recently that below in conjunction with Fig. 7 reported event is the handling process of firm detected incident under hooking or the dialing situation.

As shown in Figure 7: at first carry out step 7000, the incident that has reported recently is hooking or dialing.

Then enter step 7100, judge whether nearest detection incident is off-hook, if, need so to recall nearest onhook event forward from incident buffer memory end, enter step 7110 and further handle, otherwise enter step 7200.

In step 7110, begin to recall from incident buffer memory end, if also have incident not to be examined, enter step 7120 so, if all incidents were examined, enter step 7140 so.

In step 7120, get first also not checked incident forward from incident buffer memory end, enter step 7130.

In step 7130, whether determining step 7120 incident of getting is nearest onhook event.Be then to enter step 7131, otherwise return step 7110.

In step 7131, owing to find nearest onhook event in step 7130 judgement, therefore empty existing incident more Zao in the incident buffer memory in this step, again the end of adding this nearest detected off-hook event to the incident buffer memory, process ends then than this onhook event.

In step 7140, owing to all do not have to find nearest onhook event in the incident buffer memory through above-mentioned steps, so this step empties the existing incident in the incident buffer memory, abandons this nearest detected off-hook event simultaneously, start terminal abnormal and handle, then process ends.Need to prove, for example this terminal is withdrawed from service and uploaded state and lose and just belong to a kind of terminal abnormal processing mode.

In step 7200, owing to judge that in step 7100 nearest detection incident is not an off-hook, so this step judges whether nearest detection incident is on-hook or hooking.If detection incident recently is on-hook or hookflash event, then enters step 7210, otherwise enter step 7300.

In step 7210, owing to judge that in step 7200 nearest detection incident is on-hook or hookflash event, therefore empty existing incident in the incident buffer memory, again the end of adding this nearest detected on-hook or hookflash event to the incident buffer memory in this step.

In step 7300, owing to judge that in step 7200 nearest detection incident is not on-hook or hookflash event, therefore judge in this step whether nearest detection incident is dialing, if dialer event just enters step 7310, otherwise with regard to process ends.

In step 7310, owing to judge that in step 7300 nearest detection incident is a dialer event, therefore from the end that this step is added this dialer event to the incident buffer memory, process ends then.

Need to prove, go up certain physical terminal as if MG in the above-mentioned rule, lose as TDM passage uploaded state, then will start the exception handling of terminal, concrete processing procedure is: MG is by sending the signaling that uploaded state is lost to MGC, trigger MGC and issue the audit order with the synchronous state of this terminal on MG and MGC, MG feeds back the actual off-hook or the hook state of this terminal, and empties incident buffer memory and the locking that reports that starts event descriptor.

Shown in Figure 8 is another situation according to this programme, promptly certain terminal on MG obtains the new events descriptor, this new events descriptor may be the new events descriptor that MGC sends, and when perhaps former embedded event descriptor is activated, MG will scan the handling process of the incident buffer memory of this terminal.

As shown in the figure, at first, in step 8000, MG obtains new event descriptor will trigger following flow process.

In step 8100, the situation of decision event buffer memory, if the incident buffer memory is empty, MG will wait for that based on the new events descriptor new incident is detected, process ends so.If be not empty, then enter step 8200, continue to handle.

In step 8200, MG promptly comes the top incident of incident buffer memory by the FIFO order from the first incident of initial extraction of incident buffer queue, carries out the judgement of step 8300.

In step 8300, this incident is compared with the new events descriptor, see whether the new events descriptor contains this incident.If this incident does not appear in the new events descriptor, carry out step 8310 so, otherwise enter step 8400.

In step 8310, owing to judge that in step 8300 this incident does not appear in the new events descriptor, therefore in this step, MG removes this incident and restarts the scan event buffer memory.

In step 8400, owing to judge that in step 8300 this incident appears in the new events descriptor, judge whether to exist uncompleted circular (Notify) request, promptly request does not meet with a response as yet yet.Exist uncompleted Notify to ask if this terminal is current, MG will continue to wait for Notify request responding, process ends so.If there is no uncompleted Notify request continues the processing of later step 8500 so.

In step 8500, MG reports this incident by the Notify request, enters step 8600.

In step 8600, MG removes this incident from the incident buffer memory, process ends.

Need to prove that reporting the timestamp of Notify request is the actual time that is detected of this incident.The event descriptor of current activation is locked on this terminal then, and MG waits for the new events descriptor, during any on this terminal the incident of being detected will be placed into this incident buffer memory.

Shown in Figure 9 is last situation according to this programme, and promptly certain terminal on MG obtains the handling process of circular (Notify) response.

As shown in the figure, at first, in step 9000, MG obtains circular (Notify) response and triggers following flow process.

In step 9100, carry out the judgement whether event descriptor locks.If event descriptor is locked, the incident that promptly has in the event descriptor of current activation on this terminal was reported, MG will wait for the new events descriptor so, during any on this terminal the incident of being detected will be placed into the incident buffer memory of this this terminal, process ends.Need to prove that must wait for the new events descriptor this moment, and obtain can not sending next Notify request before the new events descriptor, because an event descriptor only allows to report once just locked then.If event descriptor does not have lockedly on this terminal, enter step 9200 so.

In step 9200, MG will scan the incident buffer memory of this terminal.If the scan event buffer memory is empty, MG will continue to wait for that terminal detects new incident, process ends based on the current event descriptor so.If scan this terminal affair buffer memory not for empty, then enter step 9300.

In step 9300, MG promptly comes the top incident of incident buffer memory by the FIFO order from the first incident of initial extraction of incident buffer queue, carries out the judgement of step 9400.

In step 9400, this incident is compared with the new events descriptor, see whether the new events descriptor contains this incident.If this incident does not appear in the new events descriptor, enter step 9410 so, otherwise enter step 9500.

In step 9410, owing to judge that in step 9400 this incident does not appear in the new events descriptor, therefore in this step, MG removes this incident and restarts the scan event buffer memory.

In step 9500, owing to judge that in step 9400 this incident appears in the new events descriptor, so MG just asks to report this incident by Notify, enters step 9600.

In step 9600, MG removes this incident from the incident buffer memory, process ends.

Except the above-mentioned technical scheme of mentioning, can also other alternate embodiments.

On MG terminal distribution incident buffer memory fifo queue, can be in different ways:

First kind of mode can be the fifo queue of all allocating what a fixed length for each terminal in advance, and realizing simple relatively like this but take resource may be more, that is to say the fifo queue method of salary distribution that the above-mentioned technical scheme of mentioning adopts;

The second way can be to reserve a public buffer area, when each terminal has demand just from applying for that wherein a memory cell and serial connection become oneself a fifo queue, obviously, realize relative complex like this, need each terminal shared resource under the coordination of MG, but resource utilization can be higher.

On MG,, all incidents that do not report are as yet abandoned selectively based on its current validity or buffer memory also can adopt different rules flexibly according to incident that has reported recently and the incident that detects recently just:

First kind can be as noted above technical scheme with off-hook, on-hook, hooking, dialer event as the combination Rule of judgment.Judge that like this flow process is more clear and complexity is also more moderate.

Second kind, also can be reduced to and have only off-hook and onhook event, judge that like this flow process greatly reduces but the control dynamics is also thicker relatively.

The third can also expand more incident as the combination Rule of judgment, and the dynamics of controlling like this is higher relatively but the judgement flow process is complicated more.

Though by reference some preferred embodiment of the present invention, the present invention is illustrated and describes, but the personage who sets foot in this area should be understood that, can do various changes to it in the form and details, and the spirit and scope of the present invention that do not depart from appended claims and limited.

Claims

1. a media gateway command serial method is characterized in that, comprises following steps:

C is cached to detected described incident in the formation of this terminal.

2. media gateway command serial method according to claim 1 is characterized in that, described step C also further comprises following substep:

C3 is cached to described detected incident in the formation of this terminal.

3. media gateway command serial method according to claim 2 is characterized in that, described step C2 also further comprises following substep:

4. media gateway command serial method according to claim 3 is characterized in that, when described nearest reported event was off-hook, described step C21 also further comprised following substep:

5. media gateway command serial method according to claim 3 is characterized in that, when described nearest reported event was on-hook, described step C21 also further comprised following substep:

6. media gateway command serial method according to claim 3 is characterized in that, when described nearest reported event was hooking or dialing, described step C21 also further comprised following substep:

7. media gateway command serial method according to claim 1 is characterized in that, when described terminal obtains new event descriptor, comprises following steps:

8. media gateway command serial method according to claim 1 is characterized in that, when described terminal obtains the response of previous circular order, comprises following steps: