CN1585351A - Fault information transmitting method - Google Patents
Fault information transmitting method Download PDFInfo
- Publication number
- CN1585351A CN1585351A CN 03155207 CN03155207A CN1585351A CN 1585351 A CN1585351 A CN 1585351A CN 03155207 CN03155207 CN 03155207 CN 03155207 A CN03155207 A CN 03155207A CN 1585351 A CN1585351 A CN 1585351A
- Authority
- CN
- China
- Prior art keywords
- error message
- message
- flow process
- monitoring flow
- stop
- 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
Images
Abstract
The method includes following steps: the first entity receives the message packet from second entity, processes it according to constitutive rule and generates an error message corresponding to the IUA or M2UA protocol; the error message is inputted into monitor process, the monitor process monitors the error message and judges its type of error message; the first entity transmits the error message type to the second entity connected with it. The invention can transmit in priority the error message that mostly presents current error state in many errors.
Description
Technical field
The present invention proposes a kind of error message sending method, belong to the signaling transmission technique field, relate to a kind of specifically based on the fault monitoring of IUA and M2UA standard agreement and the method for transmission thereof.
Background technology
In existing signaling transmission (SIGTRAN:Signalling Transfer), the two ends SIGTRAN entity of butt joint, wherein an end after having produced error event, can send error message because receiving the message of not expecting to the other end, informs the type of error of generation.
At present, in SIGTRAN, can send corresponding error message, and provide multiple different error message type respectively for different agreements at concrete error event.In ISDNQ921 user adaptation layer (IUA:ISDN is Adaptation Layer Q.921-User) and MTP2-User Adaptation Layer (M2UA:MTP2 User Adaption Layer) standard agreement, can send the corresponding error type of message at concrete error event.
Yet there is following shortcoming in the method that the error message that provides at IUA and M2UA standard agreement in the prior art sends:
1, only clear and definite sends corresponding error message, and the priority that does not point out faults, thereby make and when multiple mistake produces simultaneously, can't finish the monitoring of error event and the transmission of error message at concrete error event.
2, when having multiple error event produce simultaneously, because the order that does not have clear and definite error message to send, make that the wrong end that produces can not quick wrongheaded form, thereby the quick eliminating of mistake is impacted, and finally influence the stability of system.
Summary of the invention
The present invention proposes a kind of error message sending method, thereby with the transmission that solves the monitoring that can't rationally finish error event that exists in the prior art and error message, the problem that can not quick wrongheaded form the quick eliminating of mistake be impacted.
For addressing the above problem, solution of the present invention is:
A kind of error message sending method, the signaling transmission entity of two butt joints is first entity and second entity, and wherein, second entity sends message bag to the first entity that meets IUA or M2UA standard agreement, and the method includes the steps of:
A, first entity are handled it according to the message composition rule after receiving this message bag, produce and this IUA or the corresponding error message of M2UA standard agreement;
B, this error message is sent into the monitoring flow process, this error message is monitored, and, byte-orders preferential according to message sequence preferentially reaches gross error one or more situations in preferential and come the misjudgment type of message by this monitoring flow process;
C, first entity are sent to second entity of butt joint with it with this error message type.
If error message monitoring flow process among the described step b then specifically comprises following steps based on the IUA standard agreement:
B1, judge whether this error message is " Invalid Version ", " UnsupportedMessage Class ", " Unsupported Message Type " successively, if not then continuing, otherwise stop this monitoring flow process;
B2, judge whether error message, if not then continuing, otherwise stop this monitoring flow process into " Unexpected Message ";
B3, judge whether to be " Invalid Stream Identifier ", " Refused-Management Blocking " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B4, judge whether to be " ASP Identifier Required ", " Invalid ASPIdentifier " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B5, judge whether error message, if not then continuing, otherwise stop this monitoring flow process into " Unsupported Traffic Handling Mode ";
B6, judge whether to be " Unsupported Interface Identifier Type ", " Invalid Interface Identifier ", " ASP Active for Interface Identifier (s) " error message successively, if not then continuation, otherwise stop this monitoring flow process;
B7, judge whether to be " Unassigned TEI ", " Unrecognized SAPI ", " Invalid TEI, SAPI combination " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B8, judge whether it is " Protocol Error " error message, stop this monitoring flow process then.
If error message monitoring flow process among the described step b then specifically comprises following steps based on the M2UA standard agreement:
B1 ', judge whether this error message is " Invalid Version ", " UnsupportedMessage Class ", " Unsupported Message Type " successively, if not then continuing, otherwise stop this monitoring flow process;
B2 ', judge whether error message, if not then continuing, otherwise stop this monitoring flow process into " Unexpected Message ";
B3 ', judge whether to be " Invalid Stream Identifier ", " Refused-Management Blocking " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B4 ', judge whether error message successively, if not then continuing, otherwise stop this monitoring flow process into " Parameter Field Error ";
B5 ', judge whether to be " ASP Identifier Required ", " Invalid ASPIdentifier " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B6 ', judge whether error message successively, if not then continuing, otherwise stop this monitoring flow process into " Unsupported Traffic Handling Mode ";
B7 ', judge whether to be " Unsupported Interface Identifier Type ", " Invalid Interface Identifier ", " ASP Active for Interface Identifier (s) " error message successively, if not then continuation, otherwise stop this monitoring flow process;
B8 ', judge whether to be " Invalid Parameter Value ", " UnexpectedParameter ", " Missing Parameter " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B9 ', judge whether error message, stop this monitoring flow process then into " Protocol Error ".
A kind of error message sending method of the present invention, the mechanism that error event produces and error message sends of a kind of reasonable monitoring IUA and M2UA standard agreement has been proposed, thereby make when multiple mistake takes place, can be according to wherein a kind of mistake of the only preferential transmission of this mechanism, other mistakes can not send.Especially for the situation that has multiple error event to produce simultaneously, the rational method of a kind of fault monitoring and transmission has been proposed, make wrong the generation hold the quick wrongheaded form of energy, the error message that best embodies current error pattern in produced simultaneously a plurality of error messages preferentially is sent to message sending end, thereby has got rid of mistake fast.
Description of drawings
Fig. 1 is the data structure schematic diagram of universal information head;
Fig. 2 is the data structure schematic diagram of elongated parameter;
Fig. 3 is the treatment principle schematic diagram of the described method of the embodiment of the invention;
Fig. 4 is the frame construction drawing of the method for the invention;
Fig. 5 is the specific implementation flow chart of the embodiment of the invention one;
Fig. 6 is the specific implementation flow chart of the embodiment of the invention two.
Embodiment
The embodiment of the invention has been introduced a kind of error message sending method, the mechanism that error event produces and error message sends of a kind of reasonable monitoring IUA and M2UA standard agreement is provided, especially for the situation that has multiple error event to produce simultaneously, provide the rational method of a kind of fault monitoring and transmission.
At first, introduce some background knowledges of IUA and M2UA message bag.
The data structure of IUA and M2UA message bag comprises universal information head and elongated argument structure two major parts.Wherein, different message kind (Message Class) and type of messages (MessageType) have determined elongated argument structure.The data structure of its universal information head and elongated Parameters data structure are respectively as shown in Figure 1, 2.The message Bao Junxu of IUA and all transmissions of M2UA observes this message composition rule, and according to the message bag that this message composition rule monitoring receives, checks whether each field domain value is correct, as the incorrect error message that then sends correspondence.
The error message type that IUA and M2UA provide is distinguished as shown in Table 1 and Table 2:
Table 1
| ?Invalid?Version | ????0x01 |
| ?Invalid?Interface?Identifier | ????0x02 |
| ?Unsupported?Message?Class | ????0x03 |
| ?Unsupported?Message?Type | ????0x04 |
| ?Unsupported?Traffic?Handling?Mode | ????0x05 |
| ?Unexpected?Message | ????0x06 |
| ?Protocol?Error | ????0x07 |
| ?Unsupported?Interface?Identifier?Type | ????0x08 |
| ?Invalid?Stream?Identifier | ????0x09 |
| ?Unassigned?TEI | ????0x0a |
| ?Unrecognized?SAPI | ????0x0b |
| ?Invalid?TEI，SAPI?combination | ????0x0c |
| ?Refused-Management?Blocking | ????0x0d |
| ?ASP?Identifier?Required | ????0x0e |
| ?Invalid?ASP?Identifier | ????0x0f |
Table 2
| ?Invalid?Version | ????0x1 |
| ?Invalid?Interface?Identifier | ????0x2 |
| ?Unsupported?Message?Class | ????0x3 |
| ?Unsupported?Message?Type | ????0x4 |
| ?Unsupported?Traffic?Handling?Mode | ????0x5 |
| ?Unexpected?Message | ????0x6 |
| ?Protocol?Error | ????0x7 |
| ?Unsupported?Interface?Identifier?Type | ????0x8 |
| ?Invalid?Stream?Identifier | ????0x9 |
| ?Not?Used?in?M2UA | ????0xa |
| ?Not?Used?in?M2UA | ????0xb |
| ?Not?Used?in?M2UA | ????0xc |
| ?Refused-Management?Blocking | ????0xd |
| ?ASP?Identifier?Required | ????0xe |
| ?Invalid?ASP?Identifier | ????0xf |
| ?ASP?Active?for?Interface?Identifier(s) | ????0x10 |
| ?Invalid?Parameter?Value | ????0x11 |
| ?Parameter?Field?Error | ????0x12 |
| ?Unexpected?Parameter | ????0x13 |
| ?Not?Used?in?M2UA | ????0x14 |
| ?Not?Used?in?M2UA | ????0x15 |
| ?Missing?Parameter | ????0x16 |
The embodiment of the invention constitutes according to the message of foregoing description, has proposed the monitoring of error message and has sent the Several principles that should follow, and is as shown in Figure 3, specific as follows:
1, message sequence is preferentially monitored principle.
Promptly according to the precedence of the reception of the message bag in the agreement flow process, whether what judge current reception is expection message.If what receive is unexpected message, then send corresponding error message.
2, byte-orders is preferentially monitored principle.
Promptly whether according to the precedence of byte in the message bag that receives, it is correct to detect byte content, total byte length etc.Incorrectly then send corresponding error message.
3, gross error preferentially sends principle.
Though receiving terminal monitors several error messages simultaneously,, then preferentially send this error message if wherein certain type of error can the current error pattern of clearer description.
When multiple mistake took place, according to wherein a kind of mistake of the only preferential transmission of above-described three principles, other mistakes can not send.
Based on above-mentioned three principles, will be described by following two embodiment for the error message monitoring of IUA and M2UA and the specific implementation that sends:
Embodiment one
To the error message monitoring of IUA standard agreement and the specific implementation step that sends, as shown in Figure 4:
One, the signaling of two butt joints transmission entity is entity SG and entity MGC, wherein, the message bag that entity MGC transmission meets the IUA standard agreement is to entity SG, and entity SG handles it according to the message composition rule after receiving this message bag, produces the error message corresponding with this IUA standard agreement.
Two, this error message is sent into the monitoring flow process, this error message is monitored, and, byte-orders preferential according to message sequence preferentially reaches gross error one or more situations in preferential and come the misjudgment type of message by this monitoring flow process.
This monitoring flow process is specifically carried out according to following steps according to the already provided error message type of IUA standard agreement, as shown in Figure 5:
(1) judges in this error message whether be " Invalid Version ", " Unsupported Message Class ", " Unsupported Message Type " successively,, otherwise stop this monitoring flow process if not then continuation; These error messages are corresponding to universal information head field.
(2) judge whether it is " Unexpected Message " error message,, otherwise stop this monitoring flow process if not then continuation; This error message is corresponding to " Message Type " content in the universal information head field, and the type of message of not expecting is received in expression.
(3) judge whether it is " Invalid Stream Identifier ", " Refused-Management Blocking " error message successively,, otherwise stop this monitoring flow process if not then continuation; When universal information head field detect errorless after, just can according to " Message Class,, and " Message Type " carries out remaining judgement.
(4) judge whether it is " ASP Identifier Required ", " Invalid ASPIdentifier " error message successively,, otherwise stop this monitoring flow process if not then continuation;
(5) judge whether it is " Unsupported Traffic Handling Mode " error message,, otherwise stop this monitoring flow process if not then continuation;
(6) judge whether it is " Unsupported Interface Identifier Type " and " Invalid Interface Identifier ", " ASP Active for Interface Identifier (s) " error message successively, if not then continuation, otherwise stop this monitoring flow process;
(7) judge whether it is " Unassigned TEI ", " Unrecognized SAPI ", " Invalid TEI, SAPI combination " error message successively,, otherwise stop this monitoring flow process if not then continuation; Because in the message bag of ISDN Q.921-User Adaptation Layer, TEI and SAPI field are positioned at last, when " Interface Identifier " field test errorless after, and then need judge the field that comprises TEI and SAPI parameter.
(8) judge whether it is " Protocol Error " error message, stop this monitoring flow process then.When receiving the parameter of the correct but non-expectation of any syntactic structure, send this error message.
Entity SG receives MAUP message, comprise " Invalid Interface Identifier " in this message, (invalid interface identifier), because MAUP message only could send when the ASP state is Active (activation), so the SG side should be received MAUP message when the ASP state is Inactive (deexcitation), be that the state of ASP could receive MAUP message after becoming Active by Inactive after ASP Active message was received in the expectation of SG side.And the ASP state when being Inactive the SG side receive MAUP message, then can cause the generation of " Unexpected Message " (message of not expecting) error message.At this moment, in fact simultaneously there are two kinds of mistakes: i.e. " Invalid InterfaceIdentifier " and " Unexpected Message ", so after the monitoring and judgement via above-mentioned error message monitoring flow process, at first detect " Unexpected Message " error message and judge the error message type of this error message type for sending.
Three, entity SG is sent to detected error message type the entity MGC that docks with it.
After detecting the corresponding error type of message by above-mentioned steps two, entity SG should " Unexpected Message " error message type be sent to entity MGC.
By above-mentioned steps, after the message sink termination is received the message bag, the error message type priority that best embodies current error pattern in produced simultaneously a plurality of error messages is sent to former message sending end.
Embodiment two
Similar to specific implementation step and embodiment one that the error message of M2UA standard agreement is monitored and sent, and because the error message type that the M2UA standard agreement is provided is different from the error message type that the IUA standard agreement provides, so the monitoring of the error message in step 2 flow process is then specifically carried out according to following steps, as shown in Figure 6:
(1) judges in this error message whether be " Invalid Version ", " Unsupported Message Class ", " Unsupported Message Type " successively,, otherwise stop this monitoring flow process if not then continuation;
(2) judge whether it is " Unexpected Message " error message,, otherwise stop this monitoring flow process if not then continuation;
(3) judge whether it is " Invalid Stream Identifier ", " Refused-Management Blocking " error message successively,, otherwise stop this monitoring flow process if not then continuation;
(4) judge whether it is " Parameter Field Error " error message successively,, otherwise stop this monitoring flow process if not then continuation;
(5) judge whether it is " ASP Identifier Required ", " Invalid ASPIdentifier " error message successively,, otherwise stop this monitoring flow process if not then continuation;
(6) judge whether it is " Unsupported Traffic Handling Mode " error message successively,, otherwise stop this monitoring flow process if not then continuation;
(7) judge whether it is " Unsupported Interface Identifier Type " and " Invalid Interface Identifier ", " ASP Active for Interface Identifier (s) " error message successively, if not then continuation, otherwise stop this monitoring flow process;
(8) judge whether it is " Invalid Parameter Value ", " UnexpectedParameter ", " Missing Parameter " error message successively,, otherwise stop this monitoring flow process if not then continuation;
(9) judge whether it is " Protocol Error " error message, stop this monitoring flow process then.
Entity SG monitors " Invalid Stream Identifier " (invalid stream number) and " Protocol Error " (protocol error) error message simultaneously, according to above-mentioned error message monitoring flow process, obviously " Invalid Stream Identifier " message can the current error pattern of clearer description, so entity SG preferentially sends it to entity MGC.
In sum, the present invention is respectively by embodiment one and embodiment two, the mechanism that error event produces and error message sends of a kind of reasonable monitoring IUA and M2UA standard agreement has been proposed, thereby make when multiple mistake takes place, can be according to wherein a kind of mistake of the only preferential transmission of this mechanism, other mistakes can not send.Especially for the situation that has multiple error event to produce simultaneously, a kind of method of clear and definite error message order of transmission has been proposed, make wrong the generation hold the quick wrongheaded form of energy, the error message that best embodies current error pattern in produced simultaneously a plurality of error messages preferentially is sent to message sending end, thereby has got rid of mistake fast.
Claims (3)
1, a kind of error message sending method, the signaling transmission entity of two butt joints is first entity and second entity, wherein, second entity sends message bag to the first entity that meets IUA or M2UA standard agreement, it is characterized in that:
The method includes the steps of:
A, first entity are handled it according to the message composition rule after receiving this message bag, produce and this IUA or the corresponding error message of M2UA standard agreement;
B, this error message is sent into the monitoring flow process, this error message is monitored, and, byte-orders preferential according to message sequence preferentially reaches gross error one or more situations in preferential and come the misjudgment type of message by this monitoring flow process;
C, first entity are sent to second entity of butt joint with it with this error message type.
2, a kind of error message sending method as claimed in claim 1 is characterized in that: if the error message monitoring flow process among the described step b then specifically comprises following steps based on the IUA standard agreement:
B1, judge whether this error message is " Invalid Version ", " Unsupported Message Class ", " Unsupported Message Type " successively, if not then continuing, otherwise stop this monitoring flow process;
B2, judge whether error message, if not then continuing, otherwise stop this monitoring flow process into " Unexpected Message ";
B3, judge whether to be " Invalid Stream Identifier ", " Refused-Management Blocking " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B4, judge whether to be " ASP Identifier Required ", " Invalid ASPIdentifier " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B5, judge whether error message, if not then continuing, otherwise stop this monitoring flow process into " Unsupported Traffic Handling Mode ";
B6, judge whether to be " Unsupported Interface Identifier Type ", " Invalid Interface Identifier ", " ASP Active for Interface Identifier (s) " error message successively, if not then continuation, otherwise stop this monitoring flow process;
B7, judge whether to be " Unassigned TEI ", " Unrecognized SAPI ", " Invalid TEI, SAPI combination " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B8, judge whether it is " Protocol Error " error message, stop this monitoring flow process then.
3, a kind of error message sending method as claimed in claim 1 is characterized in that: if the error message monitoring flow process among the described step b then specifically comprises following steps based on the M2UA standard agreement:
B1 ', judge whether this error message is " Invalid Version ", " Unsupported Message Class ", " Unsupported Message Type " successively, if not then continuing, otherwise stop this monitoring flow process;
B2 ', judge whether error message, if not then continuing, otherwise stop this monitoring flow process into " Unexpected Message ";
B3 ', judge whether to be " Invalid Stream Identifier ", " Refused-Management Blocking " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B4 ', judge whether error message successively, if not then continuing, otherwise stop this monitoring flow process into " Parameter Field Error ";
B5 ', judge whether to be " ASP Identifier Required ", " Invalid ASPIdentfifier " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B6 ', judge whether error message successively, if not then continuing, otherwise stop this monitoring flow process into " Unsupported Traffic Handling Mode ";
B7 ', judge whether to be " Unsupported Interface Identifier Type ", " Invalid Interface Identifier ", " ASP Active for InterfaceIdentifier (s) " error message successively, if not then continuation, otherwise stop this monitoring flow process;
B8 ', judge whether to be " Invalid Parameter Value ", " UnexpectedParameter ", " Missing Parameter " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B9 ', judge whether error message, stop this monitoring flow process then into " Protocol Error ".
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031552072A CN1319330C (en) | 2003-08-19 | 2003-08-19 | Fault information transmitting method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031552072A CN1319330C (en) | 2003-08-19 | 2003-08-19 | Fault information transmitting method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1585351A true CN1585351A (en) | 2005-02-23 |
| CN1319330C CN1319330C (en) | 2007-05-30 |
Family
ID=34598067
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB031552072A Expired - Fee Related CN1319330C (en) | 2003-08-19 | 2003-08-19 | Fault information transmitting method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1319330C (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008014666A1 (en) * | 2006-07-24 | 2008-02-07 | Alcatel Lucent | An apparatus and a method for reporting the error of each level of the tunnel data packet in a communication network |
| CN100454851C (en) * | 2006-03-17 | 2009-01-21 | 华为技术有限公司 | Measuring method and device and system for Diameter protocol interface |
| CN107784052A (en) * | 2016-12-28 | 2018-03-09 | 平安科技（深圳）有限公司 | A kind of prompt statement generation method and device |
| CN109995557A (en) * | 2017-12-29 | 2019-07-09 | 中国移动通信集团陕西有限公司 | Communication method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH10187498A (en) * | 1996-12-20 | 1998-07-21 | Nec Corp | Fault information system |
| AU2001264170A1 (en) * | 2000-05-09 | 2001-11-20 | Ss8 Networks, Inc. | System and method for providing ip-based advanced intelligent network services |
| JP2002290551A (en) * | 2001-03-28 | 2002-10-04 | Nec Corp | Gateway system and trouble processing method for use therein |
| JP3678161B2 (en) * | 2001-04-11 | 2005-08-03 | 日本電気株式会社 | Gateway system and management management method used therefor |
-
2003
- 2003-08-19 CN CNB031552072A patent/CN1319330C/en not_active Expired - Fee Related
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100454851C (en) * | 2006-03-17 | 2009-01-21 | 华为技术有限公司 | Measuring method and device and system for Diameter protocol interface |
| WO2008014666A1 (en) * | 2006-07-24 | 2008-02-07 | Alcatel Lucent | An apparatus and a method for reporting the error of each level of the tunnel data packet in a communication network |
| CN101115055B (en) * | 2006-07-24 | 2010-05-12 | 上海贝尔阿尔卡特股份有限公司 | Device and method for reporting all-level error in tunnel data package of communication network |
| US8086908B2 (en) | 2006-07-24 | 2011-12-27 | Alcatel Lucent | Apparatus and a method for reporting the error of each level of the tunnel data packet in a communication network |
| CN107784052A (en) * | 2016-12-28 | 2018-03-09 | 平安科技（深圳）有限公司 | A kind of prompt statement generation method and device |
| CN109995557A (en) * | 2017-12-29 | 2019-07-09 | 中国移动通信集团陕西有限公司 | Communication method and device |
| CN109995557B (en) * | 2017-12-29 | 2022-05-13 | 中国移动通信集团陕西有限公司 | Communication method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1319330C (en) | 2007-05-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101056194A (en) | A SNMP message transfer method and device | |
| CN1863074A (en) | System and method for implementing OAM function of ethernet and multi-protocol tag exchange network | |
| CN1968163A (en) | Method for service channel detection and system for providing the same | |
| CN1655552A (en) | Managing transmission control protocol (TCP) connections | |
| CN1917452A (en) | Method for testing forwarding performance of Ethernet exchange, and method for configuring network | |
| CN1503513A (en) | Syste mand method for detecting lost messages transmitted between modules in a communication device | |
| CN1913457A (en) | Method for fault detection of two-way conversion link | |
| CN1845512A (en) | Method and apparatus for detecting loop | |
| CN1859327A (en) | Method, device and system for transfer news | |
| CN101039224A (en) | Method and equipment for detecting periodically link state | |
| CN1344069A (en) | Prelude restoring device and prelude restoring method | |
| CN1889470A (en) | Chain-circuit time delay detecting method | |
| CN101060485A (en) | Topology changed messages processing method and processing device | |
| CN1585351A (en) | Fault information transmitting method | |
| CN1863141A (en) | Method for transmission processing IP fragment message | |
| CN101043387A (en) | Remote mirror-image realization process, remote monitoring aids and system for realizing remote mirror-image | |
| CN101051957A (en) | Dynamically regulating method and device for link state and bundled link state | |
| CN1929390A (en) | Business flow protection method | |
| US7760655B2 (en) | Method and device for transfer of data over a data connection from a sender to a receiver by means of packets | |
| CN1852183A (en) | Method and apparatus for detecting counter defect indication-path condition | |
| CN1741480A (en) | Method and equipment for detecting signalling or media path fault in next generation method | |
| CN1870558A (en) | Loop detection method and system of intersection ring in elastic group ring | |
| CN1913470A (en) | Information transmitting method and system between Ethernet equipment | |
| CN1842076A (en) | Data transmission method of multi transmission channel | |
| CN1571418A (en) | A method and system for implementing data transmission in flow control transmission protocol |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| 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: 20070530 Termination date: 20170819 |