+

WO1995034158A1 - Connexions de maintenance scindees et de surveillance - Google Patents

Connexions de maintenance scindees et de surveillance Download PDF

Info

Publication number
WO1995034158A1
WO1995034158A1 PCT/CA1995/000330 CA9500330W WO9534158A1 WO 1995034158 A1 WO1995034158 A1 WO 1995034158A1 CA 9500330 W CA9500330 W CA 9500330W WO 9534158 A1 WO9534158 A1 WO 9534158A1
Authority
WO
WIPO (PCT)
Prior art keywords
maintenance
connection
circuits
circuit
path
Prior art date
Application number
PCT/CA1995/000330
Other languages
English (en)
Inventor
Lynne Martin
Chuong Ngo
Erica Liu
Arun Chandrasekaran
Original Assignee
Newbridge Networks Corporation
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Newbridge Networks Corporation filed Critical Newbridge Networks Corporation
Priority to AU25589/95A priority Critical patent/AU2558995A/en
Publication of WO1995034158A1 publication Critical patent/WO1995034158A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H04M3/26—Arrangements for supervision, monitoring or testing with means for applying test signals or for measuring
    • H04M3/28—Automatic routine testing ; Fault testing; Installation testing; Test methods, test equipment or test arrangements therefor
    • H04M3/32—Automatic routine testing ; Fault testing; Installation testing; Test methods, test equipment or test arrangements therefor for lines between exchanges
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H04M3/2254—Arrangements for supervision, monitoring or testing in networks

Definitions

  • This invention relates to a method and arrangement for monitoring the status of a network, and more particularly to a split and monitor maintenance connection.
  • the pomt-and-click paradigm used m the applicant's 4602 Network Management System for the set-up of connections (called paths) in a network is unique.
  • the path set-up feature is based on the end-user selecting the two endpoints and using a "connect" request.
  • the connect request causes the 4602 to optimally route the path through the network.
  • An object of the present invention is to alleviate the aforementioned problem.
  • a method of monitoring a network having a plurality of nodes, wherein a path is set up to carry traffic between two points on said network comprising the steps of providing a test device at a common test site for the network; setting up cross-connections with a network manager at a single location between said test device and said nodes on said path; and monitoring said path through said cross-connections with the aid of said test device.
  • a split maintenance connection splits a connection such that each end of the connection is routed to a test device.
  • a monitor maintenance connection allows listen- only maintenance on a live traffic path. Monitor connection maintenance allows the maintenance circuits to act as additional destination circuits for the data being carried by the target connection. The data carried between the target circuits is not disrupted in any way.
  • the split and monitor maintenance connections provided by the invention offer a means of advanced path diagnostics to initiate maintenance on a connected path to test connections and path integrity.
  • a point-and-click paradigm is preferably employed to perform the above maintenance connections from the single location.
  • the user can select the circuit and the test circuits on which maintenance has to be performed and invoke a split or monitor connection.
  • the concept also provides the ability to "undo" a maintenance connection and restore the circuit under test to the original connected state.
  • the system inherently checks for the access privileges of the operator before proceeding with the maintenance operation request. This system can save network operators much time and money because the entire network can be monitored from the network manager using common test equipment that can be maintained at one common location.
  • a maintenance connection allows access to a target connection such it can be tested for integrity.
  • Each maintenance connection requires a target connection and two maintenance circuits.
  • a monitor maintenance connection is a non-intrusive maintenance action.
  • the target circuits of the monitored connection are each routed to a maintenance circuit where a test can be performed without affecting service.
  • a split-back maintenance connection is an intrusive maintenance action which splits a target connection such that each end of the connection is routed to its respective maintenance circuit.
  • a split-through maintenance connection is an intrusive maintenance action which inserts the maintenance circuits in the data and signaling path between the target circuits.
  • a target circuit is either one of the two circuits involved in a network manager or NMTI connection that is to be maintained. It is located on the path-under-test; it is also referred to as a pathpoint.
  • a target connection is the connection to the network manager that the user wishes to apply a maintenance connection on. Once the maintenance connection is established the target connection can be tested.
  • Terminate and leave maintenance provides the ability to apply trunk conditioning at the output of a target circuit without removing the target connection.
  • Test equipment includes devices such as BERTs (Bit Error Rate Tester) which are used to test maintained connections.
  • BERTs Bit Error Rate Tester
  • Figure 1 shows a typical network with centralized test equipment
  • Figure 2 shows a typical network under maintenance
  • Figure 3 shows a split-through subrate channel from composite HCM DSO
  • Figure 4 shows a split-back subrate channel from DDS DSOA
  • Figures 5a to 5c show split-back maintenance on a preferred connection
  • Figures 6a and 6b show split-back maintenance on a protection connection
  • Figure 7 shows a network path with protection
  • Figure 8 shows maintenance on an alternate path while the primary path is active,-
  • Figure 9 shows Maintenance on primary path while alternate path is active
  • Figures 10 and 11 are state diagrams giving the transitions for target and maintenance circuit statuses
  • Figure 12 is a state Diagram for Target Connection Status .
  • An example of the usage of connection maintenance for wil now be described with reference to Figure 1.
  • Tl network is setup as shown in Figure 1.
  • Two PBX's (Private Branch Exchanges) 1, 2 have respective Tl interfaces in San Francisco, attached to link SFO A8-A, and New York, attached to link NYC A5-B.
  • a Tl test set 3 with DSO test capability is attached to Dallas link B3-A.
  • a path between the two PBX's is set up, using the following cross-connections under the control of a Newbridge Networks Corporation 4602 network manager:
  • the craftsperson first establishes connections between the link to the coommon test set 3 and links to the nodes to be tested. The following cross-connections are established:
  • DNV (Denver) Bl -B- 23 to Bl -A- 23 DNV Bl -B-24 to Bl -A-24 A customer using centralized test equipment would reserves specific bandwidth to connect that test equipment to the rest of the network.
  • the maintenance then begins as shown in Figure 2.
  • the SFO A8—A-l to A3-A-1 connection is monitored by A3-B- 24 and A3-B-23, to ensure that the connection is not currently carrying an active call. If the connection is currently idle, then T&L maintenance is applied to trunk condition SFO A8-A-1 and NYC A5-B-1; this ensures that the PBX's will not receive the test patterns, and, if "seize" fault signaling has been configured, that the
  • PBX's will not attempt to place calls over those circuits during the test.
  • the test set 3 is configured to inject a test pattern into circuits 1 and 7.
  • the SFO A8-A-1 to A3-A-l connection is split-back by A3-B-24 and A3-B-23; this means that the test set's test pattern on circuit 1 is transmitted to SFO A3-A-l, and that the test set receives on circuit 1 whatever SFO A3-A-l is receiving from the line.
  • the NYC B7-B-14 to A5-B-1 connection is split-back by A5-A-23 and A5-A-24; this means that the test set's test pattern on circuit 7 is transmitted to NYC B7-B-14, and that the test set 3 receives on circuit 7 whatever NYC B7-B-14 is receiving from the line. It turns out that the test reports that circuit 1 is receiving error-free data, but that circuit 7 is receiving errored data. Therefore, the path is clean in the NYC to SFO direction, but there are problems in the SFO to NYC direction.
  • the KC Al-A-1 to A2-A-6 connection is monitored by A2-B-23 and A2-B-24; A2-B-23 is monitoring the SFO to NYC direction, and the test set's circuit 3 will receive this data.
  • the CGO A4-B-6 to A3-A-14 connection is monitored by A7-B-23 and A7-B-24; A7-B-23 is monitoring the SFO to NYC direction, and the test set's circuit 5 will receive this data.
  • the network's connections and maintenance are as shown in Figure 2.
  • the test set reports that circuit 3 is error-free, but that circuit 5 is receiving errors.
  • the problem must be between the C and CGO connection matrices: either in the line output of KC A2-A-6, the Tl between KC and CGO, or the line input of CGO A4-B-6.
  • the craftsperson applies T&L maintenance to trunk condition CGO A3-A-14; this will prevent the propagation of the noise received at CGO A4-B-6. Finally, all connection maintenance, except for this last T&L, is removed.
  • connection maintenance can only operate on the central switching matrices, this problem cannot be further isolated using only connection maintenance.
  • any primary rate, data or voice circuit in the system can act as a maintenance circuit, as long as that circuit is not involved in a target connection.
  • maintenance circuits may require some configuration to permit them to be used with a particular target connection. Specifically:
  • Maintenance circuits are always bi ⁇ directional, even if the target connection is unidirectional. This is particularly important for maintenance on a unidirectional superrate connection: the maintenance circuit must be configured as a bi-directional superrate of the same speed.
  • Tandem primary rate target connections are those connections which are exclusively between El, Tl, V.35 PRI, X.21 PRI or 64 kb/s co-directional circuits, and whose signaling type is either bypass with signaling ("xx_Sig” in NMTI) or bypass without signaling ("xx_NoSig” in NMTI) .
  • primary rate circuits, DCC circuits, DNIC circuits, OCU-DP circuits, DSO-DP, SRS DSO circuits, SRM outputs, packet stream circuits, DCP-like CPSS circuits and test card DSO-TM circuits can act as maintenance circuits for 64 kb/s tandem primary rate target connections.
  • Primary rate circuits, DCC circuits and packet stream circuits can act as maintenance circuits for superrate tandem primary rate target connections.
  • 56 kb/s and 64 kb/s OCU-DP or DSO-DP circuits with error correction, as well as 56 kb/s DSO-TM circuits with error correction can act as maintenance circuits for 128 kb/s tandem primary rate superrate connections.
  • DCC circuits, DNIC circuits, OCU-DP circuits, DSO-DP circuits, SRS DSO circuits, SRM outputs or packet stream circuits should be used as maintenance circuits only if the tandem primary rate target connection is known to be carrying subrate data. However, this cannot be enforced by the node, since the node has no way of determining the content of a tandem primary rate connection.
  • Connection maintenance is always specified for the master circuit of a primary rate superrate, and always affects all circuits in the superrate group identically. It is not possible to apply connection maintenance to a single superrate slave.
  • the trunk conditioning pattern applied as a result of T&L maintenance is that which would normally be applied if the circuit was physically disconnected.
  • T&L maintenance and normal physical disconnections may behave differently for certain fault signaling configurations. Specifically:
  • the seized signaling pattern will be transmitted as soon as T&L maintenance is applied. With trunk conditioning resulting from a normal physical disconnect, 2.5 seconds of idle signaling pattern is transmitted before the seized signaling pattern is transmitted.
  • signaling code 2 pattern will be transmitted as soon as T&L maintenance is applied. With trunk conditioning resulting from a normal physical disconnect, 2.5 seconds of signaling code 1 pattern is transmitted before the signaling code 2 pattern is transmitted.
  • Circuits configured for idle, OOS-A or OOS-B fault signaling will trunk condition in the same fashion, regardless of whether the trunk conditioning is as a result of T&L maintenance or a normal physical disconnect.
  • Data target connections are those connections involving RS-232 (V.24) DCC, X.21 DCC, V.35 DCC, RS-422 DCC, DNIC, OCU-DP, DSO-DP, DSO-TM, 4-wire TO, SRM (HCM, transparent, DDS or X.50), SRS DSO, DCP CPSS (including FRS or FRE CPSS) , ITB token stream, FRS stream, or FRE stream circuits. Connections involving VCB or PCM multidrop SRM's are treated as voice. Tandem primary rate connections which are known to be carrying subrate data can be treated as subrate data connections for the purposes of connection maintenance.
  • primary rate circuits, DCC circuits, DNIC circuits, OCU-DP circuits, DSO-DP circuits, SRS DSO circuits, SRM outputs, packet stream circuits, DCP-like CPSS circuits and test card DSO-TM circuits can act as maintenance circuits for subrate data target connections .
  • Primary rate circuits, DCC circuits and packet stream circuits can act as maintenance circuits for superrate data target connections. (56 kb/s and 64 kb/s OCU-DP, DSO-DP or DSO-TM circuits with error correction can act as maintenance circuits for similar target circuits.)
  • Maintenance ports have some external physical interface which allows the user access to the data.
  • Maintenance ports may be primary rate, DCC, DNIC, etc. circuits.
  • the maintenance circuits are the circuits specified when the maintenance is being applied to the target connection.
  • the maintenance circuits may be the same as the maintenance ports, or the maintenance circuits may be SRM outputs or SRS DSO's; the latter have no external physical interface.
  • SRM inputs can never act as maintenance circuits.
  • Non-composite subrate data connections involve DSO's which carry only one subrate data channel .
  • DCC and DNIC maintenance ports can be used directly as maintenance circuits for DSO connections carrying non- composite subrate data for all subrate multiplexing methods except DDS.
  • Figure 3 shows an example of split-back maintenance on a DSO carrying non-composite HCM subrate data.
  • the target connection is from a 9.6 kb/s DNIC circuit Bl-l-A to Tl circuit A2-1; the DNIC circuit is configured for HCM subrate multiplexing.
  • 9.6 kb/s V.35 DCC circuits B8-1 and B8-2 are the intended maintenance ports. It is sufficient to simply configure the subrate multiplexing on the V.35 maintenance ports to match the DNIC circuit, then perform the split-back maintenance using the V.35 maintenance ports as the maintenance circuits.
  • the maintenance circuit must be a DDS DSOA SRM output.
  • SRM output can be connected to an HCM_DDS DCC maintenance port .
  • FIG. 4 shows an example of split-back maintenance on a DSO carrying a DDS DSOA.
  • Bl-l-A is a 9.6 kb/s DNIC circuit, configured for HCM_DDS, which is connected to DDS DSOA SRM input Bl-l-Bl on a DPM2 on the DNIC card.
  • the DDS DSOA SRM output Bl-l-Ml is connected to Tl circuit A2-1.
  • 9.6 kb/s V.35 DCC circuits B8-1 and B8-2 are to be used as split-back maintenance ports. Since the connection from Bl-l-A to Bl-l-Bl is an on-card connection, no maintenance is possible on this connection; maintenance must be performed on the SRM output to Tl connection.
  • An additional DDS SRM resource, B7-1 must be used to perform conversion from DDS DSOA to DDS_HCM.
  • the maintenance ports B8-1 and B8-2 are configured for DDS_HCM.
  • B8-1 is connected to B7-1-M1 via input B7-1-B1
  • B8-2 is connected to B7-1-M2 via input B7-1-B2; these are normal (non-maintenance) connections.
  • Split-through maintenance is then applied on the connection between Bl-l-Ml and A2-1, using B7-1-M1 and B7-1-M2 as maintenance circuits. Note that exactly the same approach could be taken for monitor or split-through maintenance.
  • Figures 5a - 5c show maintence applied to a circuit with protection.
  • Figure 5a shows all circuits ready, both preferred split-back connections physically connected
  • Figure 5b shows splitting circuit SI not ready: split- back connection between A and SI physically disconnected, but no protection switch; split-back connection between B and S2 remains physically connected
  • Figure 5c shows target circuit B not ready: Switch to protection connection occurs .
  • connection between A and B is split-back by circuits SI and S2 :
  • Figure 6a shows all circuits ready: preferred connection physically connected; split-back connection between C and S2 also physically connected; and Figure 6b shows target circuit B not ready: switch to protection connection occurs; split-back connection between A and SI physically connected; split-back connection between C and S2 not disturbed.
  • the first point in the above paragraph is significant : it allows split-back maintenance to be physically connected on a protecting circuit (C) while the protected circuit (A) is physically connected at the preferred level .
  • connection For split-through maintenance, if any of the target or maintenance circuits in the connection are not ready, the connection cannot be physically connected.
  • connections made on any intermediate nodes are preferred connections, regardless of whether the intermediate nodes are on the primary or alternate paths. Also, all circuits in the preferred path are configured for OOS signaling; circuits in the alternate path are configured for idle signaling. Assume that, initially, there are no failures on the network; therefore, the primary path will be active. However, the circuits on the DNV and DAL nodes will also be physically connected, since their connections are programmed at the preferred level. For simplicity, assume that the user's MOP's reserve link B8-B as a TAD for all nodes, and that test equipment is co-located with each node.
  • DNV Bl-A-7 connected to Bl-B-16; DAL B2-A-16 connected to B2-B-4.
  • split-back maintenance is applied to the protection connection at the endpoint nodes :
  • SFO A8-A-1 and NYC A5-B-1 are already physically connected at the preferred level; split-back maintenance at the protection level will not physically affect these circuits.
  • SFO A3-B-7 and NYC A5-A-4 are not physically connected; therefore, they can be physically connected to their respective splitting-back circuits. This allows the test sets at SFO and NYC to exchange data along the alternate path. Test patterns transmitted into SFO B8-B-2 should be received at NYC B8-B-2, and vice- versa: the alternate path is tested without disturbing the preferred path (See Figure 8) .
  • connection maintenance used to test alternate paths be released as soon as the test is completed.
  • T&L maintenance could be applied to trunk condition the tail circuits at the protected level for the duration of the tests . This T&L maintenance will have no effect if no switch occurs to the alternate path occurs.
  • KC will begin transmitting OOS signaling towards SFO; CGO will begin transmitting OOS signaling towards NYC.
  • SFO and NYC will declare circuits A3-A-1 and B7-B-14, respectively, out of service, and perform a switch to the protecting connection.
  • Connection maintenance can be used at this point to ensure that network does not automatically switch back to the primary path when the link between KC and CGO is restored.
  • Two instances of one-way T&L maintenance are applied, such that KC is trunk conditioning towards SFO, and CGO is trunk conditioning towards NYC. Of course, this T&L maintenance is redundant while the link between KC and CGO is broken; that trunk conditioning would have been applied anyway.
  • KC Al-A-l (already connected to A2-A-6) split back by B8-B-1 and B8- B-2;
  • test patterns sent into KC B8-B-2 should be received by CGO B8-B-1, and vice-versa. Once the craftsperson has been convinced that service is in fact restored between KC and CGO, the split-back maintenance can be removed.
  • T&L maintenance can be difficult.
  • the preferred circuits at SFO and NYC should come back into service nearly simultaneously. This is to prevent some period where one endpoint has the preferred connection active while the other endpoint still has the protection connection active, and therefore neither path properly active. Such a period is probably unavoidable there is an attempt to manually release T&L maintenance at both the KC and CGO nodes simultaneously.
  • the proper procedure is to apply two-way T&L maintenance at either KC or CGO, and to release the T&L maintenance at the other intermediate node.
  • One node will then be transmitting the OOS signaling in both directions.
  • the two-way T&L maintenance at that node is removed; this will result in the near-simultaneous cancellation of OOS transmission in both directions, and SFO and NYC should switch back to their preferred connections at about the same time.
  • connection maintenance is useless.
  • the same T&L maintenance as above could be used to prevent a switch back to the primary path when the link between KC and SFO is restored.
  • this same T&L maintenance would keep the circuit KC A3-A-l out of service. Since it is out of service, it can't be physically connected. Since it can't be physically connected, connection maintenance involving that circuit cannot be physically connected. Therefore, connection maintenance cannot be used to test the restored link between SFO and KC.
  • Non-revertive switching means that if the protection connection is physically connected, then a switch to the preferred connection will not occur as soon as all of the circuits in the preferred connection are ready,- instead, such a switch from the protection connection to the preferred connection must be manually initiated by the craftsperson. Such a switch would typically not be made until the craftsperson had verified the integrity of the primary path using connection maintenance.
  • the routine calculate_circuit_status handles the state transitions for both the target and maintenance circuits as described above.
  • the parameter that currently indicates whether the circuit is being connected or disconnected will have another value to indicate when a circuit is being maintained (MAINTENANCE_FLAG) .
  • MAINTENANCE_FLAG the target circuit is considered to be maintained
  • CONNECT_FLAG CONNECT_FLAG
  • the target and maintenance circuits' maintenance fields will also be updated. This will be done within the routine db_update__conn_circuit () (formerly called db_update_conn_circ_ ⁇ tatus () ) .
  • the constants used for the maintenance field have bitwise values.
  • the constants used for the target circuits include level information as well. This allows for identifying when maintenance is being applied at both levels of a branch target connection. For example, if the branch of a RAPID path has slit-thru maintenance on the primary level and monitor maintenance on the alternate level, then the branch target circuit's maitenance field will have the value 0x101.
  • a routine db_update_intruded_count_for_loopback() updates the intruded field in the call_att record associated with the circuit when a loopback is added or removed. This routine will be called by db_update_circ_conn_info () and by db_update_circ_po ⁇ t_save_default () .
  • a target circuit When a target circuit is pasted into the Diagnostics window, the mate target circuit must be determined and the Test Equipment A and Test Equipment B fields must be automatically filled in with the maintenance circuit ids.
  • the routine db_get_mate__target_circ_id() will be called to determine the mate target circuit while db_get_maintenance_circ_ids () will be called to retrieve the maintenance circuit ids .
  • a routine db_list_all_circ_looped_and_maintained() lists all circuits that currently have loopbacks or maintenance connections .
  • Maintenance connections are always saved as conn records in the database. The number of conn records added depends on the maintenance type. For a monitor maintenance connection, a total of 2 conn records are added, one for each target and maintenance circuit pair. For a split-through maintenance connection a total of 4 conn records are added, one for each target and maintenance circuit combination (i.e. target circuit 1 - maintenance circuit 1, target circuit 1 - maintenance circuit 2, target circuit 2 - maintenance circuit 1, and target circuit 2 - maintenance circuit 2) .
  • these conns are added for each target circuit in the superrate bundle; for example, a monitor maintenance connection applied on a 3 DSO superrate bundle will add 6 conns in the database. These connections are given a status according to the type of maintenance being applied and the level.
  • one conn record will be added in the database with DB_UNIDIRECTIONAL_PRI/ALT_CONN status.
  • the order of the circuits in the conn id will indicate the source and destination of the undirectional connection, ie: the first circuit is the source and the second circuit is the destination.
  • the conn records saved in the database have a pair of circuit ids as their ids.
  • the circuit ids used in the maintenance conn id will be ordered such that the target circuit is always first and the maintenance circuit second. This ordering is required for BWA.
  • the first circuit is that of the source circuit and the second is the destination circuit, as mentioned above.
  • the routine db_order_conn_id() will NOT be used to handle the circuit ordering for maintenance, unidirectional, and broadcast conn records.
  • the ids are ordered when the conn records are saved in the database and when they are handled. For example, db_get_conn() will be modified to be able to handle retrieving these new types of conn records .
  • db_add_maintenance_conn() when a maintenance connection is added from the network manager, the routine db_add_maintenance_conn() is called. This routine calls db_nci_add_conn() for each maintenance connection component. db_add_maintenance_conn() includes the target and maintenance circuit ids and the maintenance type as parameters.
  • db_nci_add_conn() When a maintenance connection is added, db_nci_add_conn() first checks whether the connection exists in the database. If not, the conn record is added. If it is the first component of a maintenance connection, the status of the target connection is updated accordingly. The new target connection's status is based on the state diagram shown in Figure 12.
  • PRI type states can be interchanged for "ALT” type states. For example, downloading a DB_4602_ALT_CONN conn will change its status to DB_NMTI_ALT_CONN.
  • the routine db_GetConnLevel () called from db_nci_add_conn() , returns a connection's level (primary or alternate) based on its status. It handles the new conn statuses that are being added.
  • the routine db_update_conn_circuit () which is called to update the circuits of the conn record is modified to handle the target and maintenance circuits. This includes updating the maintenance field in the circuit record.
  • CHG_notif calls the routine db_remove_conns_for_circ () for any type of disconnection done from the node. If it is a maintenance connection, db_remove_conns_for_circ() calls db remove maintenance connection() which will remove the maintenance connection by calling db_nci_del_conn() for each component of the connection. When a maintenance connection is removed, db_remove__maintenance_connection() is called as well. db_nci_del_conn() will change the target connection's status when the connection being deleted is a maintenance connection.
  • the target connection is part of a path, its call_att maint_pri/alt_count and intruded fields will be updated as well . All components of the maintenance connection will be removed when the delete notification is received for the first maintenance circuit. Subsequent notifications will not cause any additional updates .
  • the invention thus allows a network to be monitored in a particularly conveninent manner from a single location using common test equipment for all the nodes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

On décrit un procédé pour surveiller un réseau ayant une pluralité de noeuds et dans lequel un itinéraire est établi pour assurer le trafic entre deux points dudit réseau. On met en place un dispositif d'essai à un emplacement d'essai, on établit des connexions transversales entre l'emplacement d'essai et les noeuds de l'itinéraire et on surveille l'itinéraire par les connexions transversales
PCT/CA1995/000330 1994-06-07 1995-06-07 Connexions de maintenance scindees et de surveillance WO1995034158A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU25589/95A AU2558995A (en) 1994-06-07 1995-06-07 Split and monitor maintenance connections

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB9411360.2 1994-06-07
GB9411360A GB9411360D0 (en) 1994-06-07 1994-06-07 Method of monitoring a network

Publications (1)

Publication Number Publication Date
WO1995034158A1 true WO1995034158A1 (fr) 1995-12-14

Family

ID=10756308

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA1995/000330 WO1995034158A1 (fr) 1994-06-07 1995-06-07 Connexions de maintenance scindees et de surveillance

Country Status (3)

Country Link
AU (1) AU2558995A (fr)
GB (1) GB9411360D0 (fr)
WO (1) WO1995034158A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1996021982A2 (fr) * 1995-01-09 1996-07-18 Cabletron Systems, Inc. Utilisation de services de connexion multipoint pour etablir des points d'ecoute d'appels dans un reseau commute
WO1998033303A1 (fr) * 1997-01-29 1998-07-30 Cabletron Systems, Inc. Procede et appareil d'etablissement d'un point de derivation dans un reseau commute
US6041042A (en) * 1997-05-27 2000-03-21 Cabletron Systems, Inc. Remote port mirroring system and method thereof
WO2004056043A1 (fr) * 2002-12-17 2004-07-01 Xyratex Technology Limited Module prise de reseau
US8239960B2 (en) 2004-03-10 2012-08-07 Enterasys Networks, Inc. Method for network traffic mirroring with data privacy
US8819213B2 (en) 2004-08-20 2014-08-26 Extreme Networks, Inc. System, method and apparatus for traffic mirror setup, service and security in communication networks

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4001559A (en) * 1974-12-16 1977-01-04 Northern Telecom, Inc. Programmable measuring
DE3110633A1 (de) * 1981-03-19 1982-09-30 Vierling, Oskar, Prof. Dr.Phil.Habil., 8553 Ebermannstadt Anordnung und verfahren zum abschnittweisen messen von fest geschalteten uebertragungswegen der fernmeldetechnik

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4001559A (en) * 1974-12-16 1977-01-04 Northern Telecom, Inc. Programmable measuring
DE3110633A1 (de) * 1981-03-19 1982-09-30 Vierling, Oskar, Prof. Dr.Phil.Habil., 8553 Ebermannstadt Anordnung und verfahren zum abschnittweisen messen von fest geschalteten uebertragungswegen der fernmeldetechnik

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
GEORG GLUNDER ET AL: "FUNDAMENTALS OF CENTRAL SUPERVISION FACILITIES FOR LONG-HAUL COMMUNICATION NETWORKS", SIEMENS REVIEW XLI-SPECIAL ISSUE: COMMUNICATIONS ENGINEERING, MUNCHEN(DE), pages 283 - 289 *
J.F.MARSHALL ET AL: "AUTOMATIC CROSSCONNECTION EQUIPMENT IN BRITISH TELECOMS KILOSTREAM NETWORK", IEEE GLOBAL TELECOMMUNICATIONS CONFERENCE, vol. 2, 1 December 1986 (1986-12-01) - 4 December 1986 (1986-12-04), HOUSTON(US), pages 1179 - 1184 *
K.E.CRAWFORD ET AL: "4A TOLL CROSSBAR APPLICATION", BELL SYSTEM TECHNICAL JOURNAL, vol. 57, no. 2, NEW YORK US, pages 283 - 323 *
MYRANDA A. JOHNSON ET AL: "NEW SERVICE TESTING FUNCTIONS FOR ADVANCED INTELLIGENT NETWORKS", IEEE 1992-NETWORK OPERATIONS AND MANAGEMENT SYMPOSIUM, vol. 3, 6 April 1992 (1992-04-06) - 9 April 1992 (1992-04-09), MEMPHIS(US), pages 709 - 720 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1996021982A2 (fr) * 1995-01-09 1996-07-18 Cabletron Systems, Inc. Utilisation de services de connexion multipoint pour etablir des points d'ecoute d'appels dans un reseau commute
WO1996021982A3 (fr) * 1995-01-09 1996-10-03 Cabletron Systems Inc Utilisation de services de connexion multipoint pour etablir des points d'ecoute d'appels dans un reseau commute
US5627819A (en) * 1995-01-09 1997-05-06 Cabletron Systems, Inc. Use of multipoint connection services to establish call-tapping points in a switched network
US5754532A (en) * 1995-01-09 1998-05-19 Cabletron Systems, Inc. Use of multipoint connection services to establish call-tapping points in a switched network
WO1998033303A1 (fr) * 1997-01-29 1998-07-30 Cabletron Systems, Inc. Procede et appareil d'etablissement d'un point de derivation dans un reseau commute
US5940376A (en) * 1997-01-29 1999-08-17 Cabletron Systems, Inc. Method and apparatus to establish a tap-point in a switched network using self-configuring switches having distributed configuration capabilities
AU716013B2 (en) * 1997-01-29 2000-02-17 Extreme Networks, Inc. Method and apparatus to establish a tap-point in a switched network using self-configuring switches having distributed configuration capabilities
US6041042A (en) * 1997-05-27 2000-03-21 Cabletron Systems, Inc. Remote port mirroring system and method thereof
WO2004056043A1 (fr) * 2002-12-17 2004-07-01 Xyratex Technology Limited Module prise de reseau
US8239960B2 (en) 2004-03-10 2012-08-07 Enterasys Networks, Inc. Method for network traffic mirroring with data privacy
US8819213B2 (en) 2004-08-20 2014-08-26 Extreme Networks, Inc. System, method and apparatus for traffic mirror setup, service and security in communication networks

Also Published As

Publication number Publication date
AU2558995A (en) 1996-01-04
GB9411360D0 (en) 1994-07-27

Similar Documents

Publication Publication Date Title
JP3126604B2 (ja) 通信システム
US5862125A (en) Automated restoration of unrestored link and nodal failures
US5233600A (en) Method and apparatus for identifying a failed span in a network of span interconnected nodes
US6853641B2 (en) Method of protecting traffic in a mesh network
KR960007668B1 (ko) 통신 회로망용 서비스 복구 시스템 및 통신 회로망의 대체 트래픽 경로 설정 방법
US5517489A (en) Synchronous digital hierarchy 2-fiber ring having a selective protection function
JPH07202924A (ja) 通信システム
JPH07112203B2 (ja) リング相互接続保を提供するデュアル・ハブ装置
US6496476B1 (en) System and method for restricted reuse of intact portions of failed paths
WO2007082450A1 (fr) Méthode destinée à traiter une dépendance de défaillance de surveillance de connexion en tandem de différents niveaux, et équipement associé
US20040078483A1 (en) System and method for implementing virtual loopbacks in ethernet switching elements
JPH11507487A (ja) 予備容量の実質的に同時の両方向リクエストを解決するためのシステム及び方法
EP0632667A2 (fr) Méthode de libération des liaisons superflues d'une connection téléphonique
WO1995034158A1 (fr) Connexions de maintenance scindees et de surveillance
US6337846B1 (en) Quantification of the quality of spare links in a telecommunications network
US8983052B2 (en) Method and apparatus for communication having critically assured services
JP3226773B2 (ja) 複数のリングノードのうちの所定のリングノードに用いる方法とリングノード伝送システムにおいて通信回路を確定的にスケルチする方法
US20040136520A1 (en) Next generation gateway
US6907035B1 (en) Master controller for a flexible switching system
US7518981B1 (en) Method and system for a graceful reroute of connections on a link
US5951701A (en) Detection of loop-back conditions on faulty digital trunks
JP2970801B2 (ja) Ｉｓｄｎ交換機及び回線の試験システム及び試験方法
US7602701B1 (en) WideBand cross-connect system and protection method utilizing SONET add/drop multiplexers
EP0980189A2 (fr) Procédé et appareil d'acheminement de données pour éviter un commutateur défectueux
CN1327716C (zh) 用于中间接口,例如v5.2接口的起动方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AM AT AU BB BG BR BY CA CH CN CZ DE DK EE ES FI GB GE HU JP KE KG KP KR KZ LK LR LT LU LV MD MG MN MW MX NO NZ PL PT RO RU SD SE SI SK TJ TT UA US UZ VN

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): KE MW SD SZ UG AT BE CH DE DK ES FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

NENP Non-entry into the national phase

Ref country code: CA

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载