CN1319330C - Fault information transmitting method - Google Patents
Fault information transmitting method Download PDFInfo
- Publication number
- CN1319330C CN1319330C CNB031552072A CN03155207A CN1319330C CN 1319330 C CN1319330 C CN 1319330C CN B031552072 A CNB031552072 A CN B031552072A CN 03155207 A CN03155207 A CN 03155207A CN 1319330 C CN1319330 C CN 1319330C
- Authority
- CN
- China
- Prior art keywords
- message
- error message
- flow process
- error
- monitoring flow
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Communication Control (AREA)
- Computer And Data Communications (AREA)
Abstract
The present invention provides a fault information transmitting method which comprises the following steps: after a first entity receives a message packet transmitted by a second entity, the message packet is processed according to the message constitution rule, which generates an error message corresponding to an IUA or M2UA rule protocol; the error message is sent into a monitoring flow path and is monitored by the monitoring flow path, and the type of the error message is judged; the first entity transmits the type of the error message to the second entity abutted with the first entity. The present invention provides a reasonable method for monitoring and transmitting an error, an error generating end can rapidly judge the type of the error, the error message which can embody the type of the current error among a plurality of error messages which are simultaneously generated is firstly transmitted to a message transmitting end, and therefore, the error can be rapidly eliminated.
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 ISDN Q921 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 that whether this error message is " invalid version number ", " unsupported message kind ", " unsupported News Category " successively, if not then continuing, otherwise stop this monitoring flow process;
B2, judge whether to be " unexpected message " error message, if not then continuing, otherwise stop this monitoring flow process;
B3, judge whether to be " invalid traffic identifier ", " refusal that is caused is blocked in management " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B4, judge whether to be " needed application server process sign ", " invalid application server process sign " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B5, judge whether to be " unsupported service processing mode " error message, if not then continuing, otherwise stop this monitoring flow process;
B6, judge whether to be " unsupported interface identifier classification ", " invalid interface identifier ", " the application server process state that has carried interface identifier is for activating " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B7, judge whether to be " unappropriated terminal node sign ", " Unidentified Service Access Point Indicator ", " invalid terminal node sign and Service Access Point Indicator combination " error message successively, if not then continuation, 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 number ", " unsupported message kind ", " unsupported News Category " successively, if not then continuing, otherwise stop this monitoring flow process;
B2 ', judge whether to be " unexpected message " error message, if not then continuing, otherwise stop this monitoring flow process;
B3 ', judge whether to be " invalid traffic identifier ", " management is blocked and caused refusal " error message, otherwise to stop this monitoring flow process successively if not then continuation;
B4 ', judge whether to be " parameter field mistake " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B5 ', judge whether to be " needed application server process sign ", " invalid application server process sign " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B6 ', judge whether to be " unsupported service processing mode " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B7 ', judge whether to be " unsupported interface identifier classification ", " invalid interface identifier ", " the application server process state that has carried interface identifier is for activating " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B8 ', judge whether to be " invalid parameter values ", " unexpected parameter ", " parameter omission " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B9 ', judge whether to be " protocol error " error message, stop this monitoring flow process then.
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 (Message Type) 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 number (InvalidVersion) ", " unsupported message kind (Unsupported Message Class) ", " unsupported News Category (Unsupported Message Type) " successively, if not then continuation, otherwise stop this monitoring flow process; These error messages are corresponding to universal information head field.
(2) judge whether it is " unexpected message (Unexpected Message) " error message,, otherwise stop this monitoring flow process if not then continuation; This error message is corresponding to " News Category (Message the 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 traffic identifier (Invalid Stream Identifier) ", " refusal (Refused-Management Blocking) that is caused is blocked in management " error message successively, if not then continuation, otherwise stop this monitoring flow process; After the detection of universal information head field is errorless, just can carry out remaining judgement according to " message kind (Message Class) " and " News Category (Message Type) ".
(4) judge whether it is " needed application server process sign (ASPIdentifier Required) ", " invalid application server process sign (Invalid ASPIdentifier) " error message successively, if not then continuation, otherwise stop this monitoring flow process;
(5) judge whether it is " unsupported service processing mode (Unsupported TrafficHandling Mode) " error message,, otherwise stop this monitoring flow process if not then continuation;
(6) judge whether it is " unsupported interface identifier classification (UnsupportedInterface Identifier Type) " and " invalid interface identifier (Invalid InterfaceIdentifier) ", " the application server process state that has carried interface identifier is for activating (ASPActive for Interface Identifier (s)) " error message successively, if not then continuation, otherwise stop this monitoring flow process;
(7) judge whether it is " unappropriated terminal node sign (UnassignedTEI) ", " Unidentified Service Access Point Indicator (Unrecognized SAPI) ", " invalid terminal node sign and Service Access Point Indicator combination (Invalid TEI; SAPIcombination) " error message successively, if not then continuation, otherwise stop this monitoring flow process; Because in the message bag of ISDN Q.921-User Adaptation Layer, TEI and SAPI field are positioned at last, when " interface identifier (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 (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 InterfaceIdentifier " (invalid interface identifier) in this message, 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 after ASP Active message is received in the expectation of SG side, the state of ASP could receive MAUP message after becoming Active by Inactive.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 interface identifier (Invalid Interface Identifier) " and " unexpected message (Unexpected Message) ", so after the monitoring and judgement via above-mentioned error message monitoring flow process, at first detect " unexpected message (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 number (InvalidVersion) ", " unsupported message kind (Unsupported Message Class) ", " unsupported News Category (Unsupported Message Type) " successively, if not then continuation, otherwise stop this monitoring flow process;
(2) judge whether it is " unexpected message (Unexpected Message) " error message,, otherwise stop this monitoring flow process if not then continuation;
(3) judge whether it is " invalid traffic identifier (Invalid Stream Identifier) ", " refusal (Refused-Management Blocking) that is caused is blocked in management " error message successively, if not then continuation, otherwise stop this monitoring flow process;
(4) judge whether it is " parameter field mistake (Parameter Field Error) " error message successively,, otherwise stop this monitoring flow process if not then continuation;
(5) judge whether it is " needed application server process sign (ASPIdentifier Required) ", " invalid application server process sign (Invalid ASPIdentifier) " error message successively, if not then continuation, otherwise stop this monitoring flow process;
(6) judge whether it is " unsupported service processing mode (UnsupportedTraffic Handling Mode) " error message successively,, otherwise stop this monitoring flow process if not then continuation;
(7) judge whether it is " unsupported interface identifier classification (UnsupportedInterface Identifier Type) " and " invalid interface identifier (Invalid InterfaceIdentifier) ", " the application server process state that has carried interface identifier is for activating (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 values (Invalid ParameterValue) ", " unexpected parameter (Unexpected Parameter) ", " parameter is omitted (Missing Parameter) " error message successively, if not then continuation, otherwise stop this monitoring flow process;
(9) judge whether it is " protocol error (Protocol Error) " error message, stop this monitoring flow process then.
Entity SG monitors " Invalid Stream Identifier " (invalid traffic identifier) and " Protocol Error " (protocol error) error message simultaneously, according to above-mentioned error message monitoring flow process, obviously " invalid traffic identifier (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 modern transmission of the letter of two butt joints entity 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 that whether this error message is " invalid version number ", " unsupported message kind ", " unsupported News Category " successively, if not then continuing, otherwise stop this monitoring flow process;
B2, judge whether to be " unexpected message " error message, if not then continuing, otherwise stop this monitoring flow process;
B3, judge whether to be " invalid traffic identifier ", " refusal that is caused is blocked in management " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B4, judge whether to be " needed application server process sign ", " invalid application server process sign " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B5, judge whether to be " unsupported service processing mode " error message, if not then continuing, otherwise stop this monitoring flow process;
B6, judge whether to be " unsupported interface identifier classification ", " invalid interface identifier ", " the application server process state that has carried interface identifier is for activating " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B7, judge whether to be " unappropriated terminal node sign ", " Unidentified Service Access Point Indicator ", " invalid terminal node sign and Service Access Point Indicator combination " error message successively, if not then continuation, 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 number ", " unsupported message kind ", " unsupported News Category " successively, if not then continuing, otherwise stop this monitoring flow process;
B2 ', judge whether to be " unexpected message " error message, if not then continuing, otherwise stop this monitoring flow process;
B3 ', judge whether to be " invalid traffic identifier ", " management is blocked and caused refusal " error message, otherwise to stop this monitoring flow process successively if not then continuation;
B4 ', judge whether to be " parameter field mistake " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B5 ', judge whether to be " needed application server process sign ", " invalid application server process sign " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B6 ', judge whether to be " unsupported service processing mode " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B7 ', judge whether to be " unsupported interface identifier classification ", " invalid interface identifier ", " the application server process state that has carried interface identifier is for activating " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B8 ', judge whether to be " invalid parameter values ", " unexpected parameter ", " parameter omission " error message successively, if not then continuing, otherwise stop this monitoring flow process;
B9 ', judge whether to be " protocol error " error message, stop this monitoring flow process then.
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 CN1585351A (en) | 2005-02-23 |
| CN1319330C true 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) |
Families Citing this family (4)
| 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 |
| CN101115055B (en) | 2006-07-24 | 2010-05-12 | 上海贝尔阿尔卡特股份有限公司 | Device and method for reporting all-level error in tunnel data package of communication network |
| CN107784052A (en) * | 2016-12-28 | 2018-03-09 | 平安科技（深圳）有限公司 | A kind of prompt statement generation method and device |
| CN109995557B (en) * | 2017-12-29 | 2022-05-13 | 中国移动通信集团陕西有限公司 | Communication method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2001086970A2 (en) * | 2000-05-09 | 2001-11-15 | Ss8 Networks, Inc. | System and method for providing ip-based services |
| EP1246477A2 (en) * | 2001-03-28 | 2002-10-02 | Nec Corporation | Gateway system and fault management method |
| CN1380777A (en) * | 2001-04-11 | 2002-11-20 | 日本电气株式会社 | Gateway system and total management method |
| CN1114863C (en) * | 1996-12-20 | 2003-07-16 | 日本电气株式会社 | Error information reporting system for error monitoring system |
-
2003
- 2003-08-19 CN CNB031552072A patent/CN1319330C/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1114863C (en) * | 1996-12-20 | 2003-07-16 | 日本电气株式会社 | Error information reporting system for error monitoring system |
| WO2001086970A2 (en) * | 2000-05-09 | 2001-11-15 | Ss8 Networks, Inc. | System and method for providing ip-based services |
| EP1246477A2 (en) * | 2001-03-28 | 2002-10-02 | Nec Corporation | Gateway system and fault management method |
| CN1380777A (en) * | 2001-04-11 | 2002-11-20 | 日本电气株式会社 | Gateway system and total management method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1585351A (en) | 2005-02-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101316197B (en) | Detection method and apparatus for Ethernet port loop of MSTP equipment | |
| US8626883B2 (en) | Injecting addresses to enable OAM functions | |
| CN108964943B (en) | Method and device for realizing IOAM packaging | |
| US6813634B1 (en) | Network fault alerting system and method | |
| US8243608B2 (en) | Metro Ethernet connectivity fault management acceleration | |
| EP1969743B1 (en) | Methods, systems, and computer program products for detecting and mitigating fraudulent message service message traffic | |
| CN100387003C (en) | Chain-circuit time delay detecting method | |
| US20080101241A1 (en) | Ethernet OAM at intermediate nodes in a PBT network | |
| US7965625B2 (en) | Communication device and logical link abnormality detection method | |
| CN101924659B (en) | Network equipment and method for detecting links of physical ports of same | |
| CA2633720A1 (en) | A method and system for obtaining path maximum transfer unit in network | |
| CN107370636B (en) | Link state determination method and device | |
| CN103404100A (en) | Relay device, relay device control method, and network system | |
| CN1319330C (en) | Fault information transmitting method | |
| CN103078791A (en) | Method, device and system for processing operation, administration and maintenance (OAM) message | |
| WO2008025283A1 (en) | A method and system for ethernet oam failure detection | |
| EP2129042A1 (en) | A multicast network system, node and a method for detecting a fault of a multicast network link | |
| CN113824574A (en) | Detection configuration, processing method, system, control device, communication device and storage medium | |
| JP2014007501A (en) | Communication device | |
| JP2007537617A (en) | How to speed up execution file transit time via checkpoint | |
| CN101321094A (en) | Connectivity fault positioning device and method | |
| JP4351368B2 (en) | Data transfer method and communication apparatus using the same | |
| CN116057911A (en) | Load balancing and OAM in service function chains using multiprotocol label switching | |
| EP1557981B1 (en) | Testing telecommunications networks | |
| CN103609066A (en) | Method and node for querying operation administration maintenance configuration information |
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 |
Granted publication date: 20070530 Termination date: 20170819 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |