CN100388694C - Loopback testing method - Google Patents
Loopback testing method Download PDFInfo
- Publication number
- CN100388694C CN100388694C CNB2005101156747A CN200510115674A CN100388694C CN 100388694 C CN100388694 C CN 100388694C CN B2005101156747 A CNB2005101156747 A CN B2005101156747A CN 200510115674 A CN200510115674 A CN 200510115674A CN 100388694 C CN100388694 C CN 100388694C
- Authority
- CN
- China
- Prior art keywords
- dte
- oam
- far
- end dte
- oampdu
- 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.)
- Active
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
- Maintenance And Management Of Digital Transmission (AREA)
Abstract
The present invention discloses a loopback testing method which is suitable for establishing near-end data terminal equipment (DTE) and far-end data terminal equipment (DTE) which are connected with OAM. The loopback testing method comprises the steps: A1. the near-end DTE transmits a loopback test to start an OAM protocol message (OAMPDU) in order to inform the far-end DTE to start a loopback test, and the far-end DTE is in a loopback state; A2. the near-end DTE transmits OAM connection to keep the OAMPDU for the far-end DTE, and the OAMPDU is kept for informing the far-end DTE and the near-end DTE to be in the loopback state by recovering the OAM connection which is returned from the far-end DTE; A3. the near-end DTE transmits the data message of the loopback test for the far-end DTE, and the link state is determined by recovering the data message of the loopback test, which is returned from the far-end DTE. The loopback testing method provided by the present invention can realize the remote loopback test of the OAM of the existing DTE equipment.
Description
Technical field
The present invention relates to the loopback test technology, relate in particular to Operations, Administration and Maintenance (OAM, Operations, Administration and Maintenance) remote loop-back method of testing.
Background technology
For improving to management function than complex network, Electrical and Electronic engineering association (IEEE) has proposed the OAM standard in the 802.3ah protocol specification, this standard is a target to solve last mile Network Management problem, and functions such as link performance monitoring, detecting fault and alarm, remote loop-back test and management information base (MIB) variable obtain are provided.As one of major function of OAM, the remote loop-back test can be used for link failure detection and performance test, the remote loop-back test of regularly carrying out can guarantee the unimpeded of existing link, and the remote loop-back of carrying out stage by stage test helps to locate fast the concrete zone of breaking down.
Common, the prerequisite of carrying out the test of OAM remote loop-back between two data terminal equipment (DTE)s is, set up the OAM connection between near-end DTE and the far-end DTE, that is to say, the OAM entity of near-end DTE has had been found that the OAM entity of far-end DTE, and set up stable OAM session with the OAM entity of far-end DTE, this process is commonly referred to the phase I of OAM session connection.Hereinafter the OAM entity with near-end DTE abbreviates near-end OAM solid as, abbreviates the OAM entity of far-end DTE as far end OAM solid.
In the phase I of OAM session connection, near-end OAM solid and far end OAM solid are carried out both sides OAM physical arrangements by OAM protocol massages (OAMPDU), and the exchange of port function parameter and sign, wherein, an end OAM entity can determine that whether set up OAM with opposite end OAM entity is connected according to the opposite end parameter.Specific to OAM remote loop-back test function, if near-end OAM solid requires far end OAM solid to have the remote loop-back test function, promptly require far-end to can be used as the controlled terminal of remote loop-back test, and opposite end OAM entity does not have this function, near-end OAM solid will be refused to set up OAM with far end OAM solid and be connected so, accordingly, only when far end OAM solid has the remote loop-back test function, near-end OAM solid just can be set up OAM with far end OAM solid and be connected, and periodically carries out the remote loop-back test.
OAM connects after the foundation, and near-end OAM solid can periodically send OAM to opposite end OAM entity respectively with far end OAM solid and be connected maintenance message INFO_OAMPDU, so that the OAM information of mutual near-end DTE and far-end DTE.Concrete, near-end DTE disposes OAM with far-end DTE and is connected overtime timer, if an end OAM entity receives that before local terminal OAM connection overtime timer is overtime the OAM that the opposite end sends connects the maintenance message, then an end OAM entity resets local terminal OAM connects overtime timer, and current OAM connects correct; On the contrary, if an end OAM entity does not receive that before local terminal OAM connection overtime timer is overtime the OAM that the opposite end sends connects the maintenance message, then current OAM connects interruption.
Common, for setting up near-end DTE and the far-end DTE that OAM connects, near-end OAM solid can start the remote loop-back test of data link layer between near-end DTE and the far-end DTE by send the mode of remote loop-back test instruction to far end OAM solid.Wherein, the near-end DTE that sends the remote loop-back test instruction often is called the loopback control end, and the far-end DTE of receiving remote loopback test instruction often is called the loopback controlled terminal.
OAM remote loop-back test generally includes three phases: the startup stage of loopback test, loopback test stage and loopback test dwell period, at this three phases, near-end DTE is in different transmit statuss and parse state respectively with far-end DTE.
Before loopback test starts, near-end DTE and far-end DTE are in non-wrapped state, be that transmit status and parse state all are to transmit (FWD) state, transmit status is in FWD and represents not only can send the control message but also can transmit data message, but parse state is in FWD to be represented not only to resolve control message but also resolution data message, and said here control message comprises the OAMPDU message.
Task startup stage of loopback test is to make near-end DTE and far-end DTE enter wrapped state respectively, and just: make near-end DTE enter wrapped state, become the loopback control end in the loopback test, promptly transmit status is FWD, and parse state is for abandoning (DC); Make far-end DTE enter wrapped state, become the loopback controlled terminal in the loopback test, promptly transmit status is DC, and parse state is loopback (LB).Transmit status is in DC to be represented only to send the control message, and abandons data message to be transmitted; Parse state is in DC and represents only to resolve the control message of receiving, and abandons the data message of receiving; Parse state is in LB and represents only to resolve the OAMPDU message, and other messages of receiving are returned according to former road, and said here other messages comprise the control message of data message and non-OAMPDU.
And the task of loopback test dwell period is to make near-end DTE and far-end DTE return to non-wrapped state from wrapped state respectively, that is to say, makes the transmit status of near-end DTE and far-end DTE and parse state all return to FWD.
Fig. 1 is the OAM remote loop-back test flow chart of current agreement regulation, comprising loopback test the startup stage, loopback test stage and loopback test dwell period, when carrying out this three phases successively, near-end OAM solid and far end OAM solid periodically send OAM to opposite end OAM entity respectively and are connected and keep message, so that keep near-end DTE to be connected with OAM between far-end DTE.Wherein, the OAM loopback test startup flow process of current agreement regulation comprises:
Step 101～105: near-end OAM solid stops forwarding data message after receiving the instruction of the outside OAM of startup loopback test, and transmit status and parse state that local terminal DTE is set all are DC; Near-end OAM solid sends loopback test and starts message LB_ON_OAMPDU_L to far end OAM solid; After far end OAM solid was received LB_ON_OAMPDU_L, the transmit status that local terminal DTE is set was DC, and the parse state that local terminal DTE is set is LB; Far end OAM solid sends loopback test and starts response message LB_ON_OAMPDU_R to near-end OAM solid; After near-end OAM solid was received LB_ON_OAMPDU_R, the transmit status that local terminal DTE is set was FWD, enters the loopback test stage.
The OAM loopback test flow process of current agreement regulation comprises:
Step 106～108: near-end OAM solid sends loopback test data message L to far end OAM solid; Far end OAM solid is returned loopback test data message L and is given near-end OAM solid; Near-end OAM solid is determined Link State according to the loopback test data message L that is recovered to.
The OAM loopback test closing flow path of current agreement regulation comprises:
Step 109～113: near-end OAM solid stops forwarding data message after receiving that the instruction of OAM loopback test is closed in the outside, and transmit status and parse state that local terminal DTE is set all are DC; Near-end OAM solid sends loopback test and closes message LB_OFF_OAMPDU_L to far end OAM solid; After far end OAM solid was received LB_OFF_OAMPDU_L, transmit status and parse state that local terminal DTE is set all were FWD; Far end OAM solid sends loopback test and closes response message LB_OFF_OAMPDU_R to near-end OAM solid; After near-end OAM solid was received LB_OFF_OAMPDU_R, transmit status and parse state that local terminal DTE is set all were FWD, process ends.
The startup stage carrying out loopback test successively, in loopback test stage and the loopback test dwell period, near-end OAM solid and far end OAM solid be execution in step a1～b1 and step c1～d1 periodically, only shows step a1～b1 and step c1～d1 in the loopback test stage among Fig. 1.
Step a1～b1: near-end OAM solid periodically sends OAM and connects maintenance message INFO_OAMPDU_L to far end OAM solid; After far end OAM solid was received INFO_OAMPDU_L, the OAM of the local terminal DTE that resets connected overtime timer.
Step c1～d1: far end OAM solid periodically sends OAM and connects maintenance message INFO_OAMPDU_R to near-end OAM solid; After near-end OAM solid was received INFO_OAMPDU_R, the OAM of the local terminal DTE that resets connected overtime timer.
As seen, OAM remote loop-back method of testing according to current agreement regulation, after entering wrapped state, loopback control end and loopback controlled terminal should send and receive the OAMPDU message as usual, simultaneously, the loopback control end sends to other messages except that OAMPDU of loopback controlled terminal, all will be by the intact loopback control end that returns to.
From above analysis as can be known, agreement for the requirement of loopback control end is:
1) enter wrapped state after, can send the control message and transmit data message;
2) enter wrapped state after, can resolve the OAMPDU message of receiving, and abandon other messages except that the OAMPDU message.
Agreement for the requirement of loopback controlled terminal is:
1) enter wrapped state after, can send the OAMPDU message;
2) enter wrapped state after, can resolve the OAMPDU message and return other messages except that the OAMPDU message.
In actual applications, current DTE equipment can reach the loopback control end requirement that agreement is stipulated usually.But be subjected to the restriction of phy chip function, the actual execution situation of current DTE equipment during as the loopback controlled terminal normally: can resolve the OAMPDU message, return all messages that comprise the OAMPDU message simultaneously, but can't send any message.Obviously, existing DTE can't reach the loopback controlled terminal function of agreement regulation.In actual applications, if with existing DTE as the loopback controlled terminal, carry out the test of OAM remote loop-back according to the flow process of agreement regulation and following problem will occur:
1) protocol requirement loopback controlled terminal sends loopback test startup response message by the loopback control end after entering wrapped state, the loopback control end can enter wrapped state according to this message change oneself state, but, after entering wrapped state as the existing DTE equipment of loopback controlled terminal, can't send any message, start response message comprising loopback test, so will make the loopback control end can't enter wrapped state, cause the remote loop-back test crash;
2) the loopback control end is to keep the OAM of the two to be connected with the prerequisite that the loopback controlled terminal can carry out loopback test, just the two periodically sends OAM connection maintenance message to the other side respectively, so that opposite end OAM entity resets local terminal OAM connects overtime timer, but, after entering wrapped state as the existing DTE equipment of loopback controlled terminal, can't send OAM again and connect the maintenance message, so will make the loopback control end not receive OAM for a long time and connect the maintenance message, it is overtime to cause OAM to connect, the remote loop-back test crash.
Summary of the invention
In view of this, the object of the present invention is to provide a kind of loop testing method, can realize the OAM remote loop-back test of existing DTE equipment.
For achieving the above object, the invention provides a kind of loop testing method, be applicable to and set up near-end data terminal equipment DTE and the far-end DTE that OAM connects that described loop testing method comprises step:
A1, near-end DTE send loopback test and start OAM protocol massages OAMPDU notice far-end DTE startup loopback test, and far-end DTE enters wrapped state;
A2, the near-end DTE transmission OAMPDU that connection keeps message as OAM knows that by reclaiming the OAMPDU as OAM connection maintenance message that is returned by far-end DTE far-end DTE enters wrapped state to far-end DTE, and near-end DTE enters wrapped state;
A3, near-end DTE send the loopback test data message to far-end DTE, determine Link State by reclaiming the loopback test data message that is returned by far-end DTE.
Wherein, the wrapped state of described near-end DTE is, sends the control message and transmits data message to far-end DTE, only resolves from the OAMPDU of far-end DTE and abandons other messages from far-end DTE.
Wherein, the wrapped state of described far-end DTE is, do not send message, only resolves from the OAMPDU of near-end DTE and returns from all messages of near-end DTE and give near-end DTE.
Wherein, before described far-end DTE entered wrapped state, the OAM between near-end DTE and the far-end DTE connected the maintenance flow process and comprises:
Near-end DTE periodically send connect to keep message as OAM OAMPDU to far-end DTE, the far-end DTE local terminal OAM that resets connects overtime timer,
Far-end DTE periodically send connect to keep message as OAM OAMPDU to near-end DTE, the near-end DTE local terminal OAM that resets connects overtime timer.
Wherein, after described near-end DTE entered wrapped state, the OAM between near-end DTE and the far-end DTE connected the maintenance flow process and comprises:
B1, near-end DTE periodically send connect to keep message as OAM OAMPDU to far-end DTE, the far-end DTE local terminal OAM that resets connects overtime timer, returns connecting the OAMPDU that keeps message as OAM and giving near-end DTE of receiving;
B2, near-end DTE reclaim by what far-end DTE returned and connect the OAMPDU that keeps message as OAM, and the OAM of the local terminal DTE that resets connects overtime timer.
Wherein, further comprise after the described steps A 3:
A4, near-end DTE send loopback test and close OAMPDU notice far-end DTE end loopback test, and far-end DTE finishes wrapped state;
A5, far-end DTE transmission loopback test is closed and is replied OAMPDU to near-end DTE, and near-end DTE finishes wrapped state.
Wherein, before described far-end DTE finished wrapped state, the OAM between near-end DTE and the far-end DTE connected the maintenance flow process and comprises:
C1, near-end DTE periodically send connect to keep message as OAM OAMPDU to far-end DTE, the far-end DTE local terminal OAM that resets connects overtime timer, and returns connecting the OAMPDU that keeps message as OAM and giving near-end DTE of receiving;
C2, near-end DTE reclaim by what far-end DTE returned and connect the OAMPDU that keeps message as OAM, and the OAM of the local terminal DTE that resets connects overtime timer.
Wherein, after described far-end DTE finished wrapped state, the OAM between near-end DTE and the far-end DTE connected the maintenance flow process and comprises:
Near-end DTE periodically send connect to keep message as OAM OAMPDU to far-end DTE, the far-end DTE local terminal OAM that resets connects overtime timer,
Far-end DTE periodically send connect to keep message as OAM OAMPDU to near-end DTE, the near-end DTE local terminal OAM that resets connects overtime timer.
As seen, OAM remote loop-back method of testing provided by the invention, function according to existing DTE equipment, utilization will be returned this characteristic of all messages after entering wrapped state as the existing DTE equipment of loopback controlled terminal, reclaiming the OAM connection that self sends by the loopback control end keeps message to know whether the other side enters wrapped state, and whether current OAM connection is correct, and this method can be carried out the remote loop-back test to existing DTE equipment.
Description of drawings
Fig. 1 is the OAM remote loop-back test flow chart of current agreement regulation.
Fig. 2 is an OAM remote loop-back test flow chart of the present invention.
Embodiment
Core concept of the present invention is: will return this characteristic of all messages at existing DTE equipment during as the loopback controlled terminal, the loopback control end connects the maintenance message by reclaiming the OAM that self sends, know that the loopback controlled terminal enters wrapped state, and keep self being connected with OAM between the loopback controlled terminal.
For making the purpose, technical solutions and advantages of the present invention clearer, by the following examples, and with reference to accompanying drawing, the present invention is described in more detail.
Fig. 2 is an OAM remote loop-back test flow chart of the present invention, comprising loopback test the startup stage, loopback test stage and loopback test dwell period.Wherein, near-end DTE as the loopback control end satisfies the requirement of agreement for the loopback control end, and the transmit status that enters after the wrapped state as the far-end DTE of loopback controlled terminal is DC ', parse state is LB ', transmit status is that DC ' expression can't send any message, and parse state is that LB ' expression parsing OAMPDU message returns all messages that comprise the OAMPDU message simultaneously.
Loopback test of the present invention starts flow process and comprises:
Step 201～203: near-end OAM solid stops forwarding data message after receiving the instruction of the outside OAM of startup loopback test, and transmit status and parse state that local terminal DTE is set all are DC; Near-end OAM solid sends loopback test and starts message LB_ON_OAMPDU_L to far end OAM solid; After far end OAM solid was received LB_ON_OAMPDU_L, the transmit status that local terminal DTE is set was DC ', and the parse state that local terminal DTE is set is LB ', and far-end DTE enters wrapped state.
In execution in step 201～203, near-end OAM solid periodically sends OAM to opposite end OAM entity respectively with far end OAM solid and is connected the maintenance message, thereby keep the OAM between near-end DTE and the far-end DTE to connect, not shown concrete situation among Fig. 2, detailed step is introduced referring to the step a1 among Fig. 1～b1 and step c1～d1 herein no longer in detail.
Step 204～207: near-end OAM solid sends OAM and connects maintenance message INFO_OAMPDU_L to far end OAM solid; After far end OAM solid was received INFO_OAMPDU_L, the local terminal OAM that resets connected overtime timer; Far end OAM solid is returned INFO_OAMPDU_L and is given near-end OAM solid; After near-end OAM solid reclaimed INFO_OAMPDU_L, the local terminal OAM that resets connected overtime timer, and the parse state that local terminal DTE is set is FWD.
Wherein, near-end OAM solid sends to the OAM connection maintenance message INFO_OAMPDU_L of far end OAM solid in the step 204, be that far-end DTE enters first OAM connection maintenance message of receiving after the wrapped state, according to the current parse state LB ' of far-end DTE equipment, after far end OAM solid receives OAM connection maintenance message, the OAM of local terminal DTE of will resetting connects timer, and returns the OAM that receives and connect and keep message to give near-end OAM solid.
Equally, far-end DTE returns to the OAM connection maintenance message INFO_OAMPDU_L of near-end DTE in the step 206, is that first MAC Address that near-end DTE is recovered to is the OAM connection maintenance message of self.Far-end DTE can know from this message that far-end DTE has entered wrapped state, then far-end DTE receive this OAM connect keep message after, the OAM of the local terminal DTE that can reset connects overtime timer, and the local terminal transmit status is set is FWD, near-end DTE enters wrapped state.
OAM loopback test flow process of the present invention comprises:
Step 207～209: near-end OAM solid sends loopback test data message L to far end OAM solid; Far end OAM solid is returned loopback test data message L and is given near-end OAM solid; Near-end OAM solid is determined Link State according to the loopback test data message L that is recovered to.
OAM loopback test closing flow path of the present invention comprises:
Step 210～214: near-end OAM solid stops forwarding data message after receiving that the instruction of OAM loopback test is closed in the outside, and transmit status and parse state that local terminal DTE is set all are DC; Near-end OAM solid sends loopback test and closes message LB_OFF_OAMPDU_L to far end OAM solid; After far end OAM solid was received LB_OFF_OAMPDU_L, transmit status and parse state that local terminal DTE is set all were FWD; Far end OAM solid sends loopback test and closes response message LB_OFF_OAMPDU_R to near-end OAM solid; After near-end OAM solid was received LB_OFF_OAMPDU_R, transmission and parse state that local terminal DTE is set all were FWD, process ends.
In execution in step 207～212, near-end OAM solid and far end OAM solid be execution in step a2～d2 periodically.
Step a2～d2: near-end OAM solid sends OAM and connects maintenance message INFO_OAMPDU_L to far end OAM solid; After far end OAM solid was received INFO_OAMPDU_L, the OAM of the local terminal DTE that resets connected overtime timer; Far end OAM solid is returned INFO_OAMPDU_L and is given near-end OAM solid; After near-end OAM solid reclaimed INFO_OAMPDU_L, the OAM of the local terminal DTE that resets connected overtime timer.
In execution in step 213～214, near-end OAM solid periodically sends OAM to opposite end OAM entity respectively with far end OAM solid and is connected the maintenance message, thereby keep the OAM between near-end DTE and the far-end DTE to connect, not shown concrete situation among Fig. 2, detailed step is introduced referring to the step a1 among Fig. 1～b1 and step c1～d1 herein no longer in detail.
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.
Claims (8)
1. a loop testing method is applicable to and sets up near-end data terminal equipment DTE and the far-end DTE that OAM connects, and it is characterized in that described loop testing method comprises step:
A1, near-end DTE send loopback test and start OAM protocol massages OAMPDU notice far-end DTE startup loopback test, and far-end DTE enters wrapped state;
A2, the near-end DTE transmission OAMPDU that connection keeps message as OAM knows that by reclaiming the OAMPDU as OAM connection maintenance message that is returned by far-end DTE far-end DTE enters wrapped state to far-end DTE, and near-end DTE enters wrapped state;
A3, near-end DTE send the loopback test data message to far-end DTE, determine Link State by reclaiming the loopback test data message that is returned by far-end DTE.
2. the method for claim 1 is characterized in that, the wrapped state of described near-end DTE is, sends the control message and transmits data message to far-end DTE, only resolves from the OAMPDU of far-end DTE and abandons other messages from far-end DTE.
3. the method for claim 1 is characterized in that, the wrapped state of described far-end DTE is, does not send message, only resolves from the OAMPDU of near-end DTE and returns from all messages of near-end DTE and give near-end DTE.
4. the method for claim 1 is characterized in that, before described far-end DTE entered wrapped state, the OAM between near-end DTE and the far-end DTE connected the maintenance flow process and comprises:
Near-end DTE periodically send connect to keep message as OAM OAMPDU to far-end DTE, the far-end DTE local terminal OAM that resets connects overtime timer,
Far-end DTE periodically send connect to keep message as OAM OAMPDU to near-end DTE, the near-end DTE local terminal OAM that resets connects overtime timer.
5. the method for claim 1 is characterized in that, after described near-end DTE entered wrapped state, the OAM between near-end DTE and the far-end DTE connected the maintenance flow process and comprises:
B1, near-end DTE periodically send connect to keep message as OAM OAMPDU to far-end DTE, the far-end DTE local terminal OAM that resets connects overtime timer, returns connecting the OAMPDU that keeps message as OAM and giving near-end DTE of receiving;
B2, near-end DTE reclaim by what far-end DTE returned and connect the OAMPDU that keeps message as OAM, and the OAM of the local terminal DTE that resets connects overtime timer.
6. the method for claim 1 is characterized in that, further comprises after the described steps A 3:
A4, near-end DTE send loopback test and close OAMPDU notice far-end DTE end loopback test, and far-end DTE finishes wrapped state;
A5, far-end DTE transmission loopback test is closed and is replied OAMPDU to near-end DTE, and near-end DTE finishes wrapped state.
7. method as claimed in claim 6 is characterized in that, before described far-end DTE finished wrapped state, the OAM between near-end DTE and the far-end DTE connected the maintenance flow process and comprises:
C1, near-end DTE periodically send connect to keep message as OAM OAMPDU to far-end DTE, the far-end DTE local terminal OAM that resets connects overtime timer, and returns connecting the OAMPDU that keeps message as OAM and giving near-end DTE of receiving;
C2, near-end DTE reclaim by what far-end DTE returned and connect the OAMPDU that keeps message as OAM, and the OAM of the local terminal DTE that resets connects overtime timer.
8. method as claimed in claim 6 is characterized in that, after described far-end DTE finished wrapped state, the OAM between near-end DTE and the far-end DTE connected the maintenance flow process and comprises:
Near-end DTE periodically send connect to keep message as OAM OAMPDU to far-end DTE, the far-end DTE local terminal OAM that resets connects overtime timer,
Far-end DTE periodically send connect to keep message as OAM OAMPDU to near-end DTE, the near-end DTE local terminal OAM that resets connects overtime timer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101156747A CN100388694C (en) | 2005-11-08 | 2005-11-08 | Loopback testing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101156747A CN100388694C (en) | 2005-11-08 | 2005-11-08 | Loopback testing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1764133A CN1764133A (en) | 2006-04-26 |
| CN100388694C true CN100388694C (en) | 2008-05-14 |
Family
ID=36748095
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005101156747A Active CN100388694C (en) | 2005-11-08 | 2005-11-08 | Loopback testing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100388694C (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101599882B (en) * | 2009-06-17 | 2011-12-07 | 中兴通讯股份有限公司 | Method and device for achieving point-to-point far end loopback of Ethernet |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5659540A (en) * | 1995-12-15 | 1997-08-19 | General Datacomm, Inc. | Apparatus and method for detection of operation administration and management (OAM) cell loopback and physical loopbacks in an asynchronous transfer mode (ATM) network |
| CN1159113A (en) * | 1995-11-29 | 1997-09-10 | 美国电报电话公司 | Out-of-band control for preforming loopback lest for asynchronous transfer mode (ATM) networks |
| WO2004066601A1 (en) * | 2003-01-24 | 2004-08-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and arrangement to perform a link test between end nodes in dsl communication networks, using several separate loop-back tests |
| CN1543033A (en) * | 2003-11-06 | 2004-11-03 | 北京四方继保自动化有限公司 | Far loopback testing technique for circuit longitudinal differential protection |
-
2005
- 2005-11-08 CN CNB2005101156747A patent/CN100388694C/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1159113A (en) * | 1995-11-29 | 1997-09-10 | 美国电报电话公司 | Out-of-band control for preforming loopback lest for asynchronous transfer mode (ATM) networks |
| US5659540A (en) * | 1995-12-15 | 1997-08-19 | General Datacomm, Inc. | Apparatus and method for detection of operation administration and management (OAM) cell loopback and physical loopbacks in an asynchronous transfer mode (ATM) network |
| WO2004066601A1 (en) * | 2003-01-24 | 2004-08-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and arrangement to perform a link test between end nodes in dsl communication networks, using several separate loop-back tests |
| CN1543033A (en) * | 2003-11-06 | 2004-11-03 | 北京四方继保自动化有限公司 | Far loopback testing technique for circuit longitudinal differential protection |
Non-Patent Citations (2)
| Title |
|---|
| Managing ATM-based Broadband Networks. Stephen C. Farkouh.IEEE Communications Magazine. 1993 |
| Managing ATM-based Broadband Networks. Stephen C. Farkouh.IEEE Communications Magazine. 1993 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1764133A (en) | 2006-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8085670B2 (en) | Method and system for originating connectivity fault management (CFM) frames on non-CFM aware switches | |
| CN111660956B (en) | Network management state monitoring method and device and automobile | |
| EP1919138B1 (en) | A method for implementing backup of the uplink | |
| CN101267363A (en) | Loop testing method, system and device | |
| CN100553213C (en) | A kind of method and apparatus of WLAN abnormal quick restoring | |
| JP2006013827A (en) | Packet transfer apparatus | |
| EP1895718B1 (en) | Method and apparatus for checking Maintenance Association integrity and method and apparatus for adding Maintenance End Point | |
| CN110875857B (en) | Method, device and system for reporting disconnected network state | |
| KR20070068462A (en) | Method and devices for matching data between a manager and an agent in a management network | |
| JP2001127761A (en) | Communication data confirmation test method in mpls communication system, and router, exchange and communication system utilizing the method | |
| RU2304849C2 (en) | Method affording transmission of information about communication line condition in network | |
| CN112134775B (en) | Switch loop detection method and device | |
| CN100388694C (en) | Loopback testing method | |
| CN110224916B (en) | Message processing method and device and message packaging method, device and system | |
| CN108282383B (en) | Method and equipment for realizing fault processing | |
| CN107995644B (en) | Method, switch, system and storage medium for automatic recovery of wireless access point | |
| CN114143904B (en) | CPE management method based on 5G fusion network shunt | |
| CN102014054A (en) | Sending method and equipment for keep-alive messages | |
| US7580371B2 (en) | Method for recognizing local management interface type automatically by data terminal equipment | |
| CN100375437C (en) | Network safety equipment synchronizing method under cluster mode | |
| CN101237382A (en) | A method and system and network device for synchronizing user data | |
| CN101247287B (en) | Fault detection method of operation management maintenance mechanism | |
| KR20030047010A (en) | Equipment monitoring system and method in asynchronous transfer mode | |
| CN112788546B (en) | Method and equipment for optimizing control unit indication information in B-trunk system | |
| US20230162298A1 (en) | Method for reconnecting a smart electricity meter and smart electricity meter implementing said method |
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 | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |