WO1995019082A1 - Synchronous transmission systems - Google Patents

Synchronous transmission systems Download PDF

Info

Publication number
WO1995019082A1
WO1995019082A1 PCT/GB1995/000014 GB9500014W WO9519082A1 WO 1995019082 A1 WO1995019082 A1 WO 1995019082A1 GB 9500014 W GB9500014 W GB 9500014W WO 9519082 A1 WO9519082 A1 WO 9519082A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
package
path
admux
byte
Prior art date
Application number
PCT/GB1995/000014
Other languages
French (fr)
Inventor
Andrew James Barker
Original Assignee
Gpt Limited
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 Gpt Limited filed Critical Gpt Limited
Priority to DE69532882T priority Critical patent/DE69532882T2/en
Priority to EP95904648A priority patent/EP0738444B1/en
Priority to AT95904648T priority patent/ATE264588T1/en
Priority to US08/666,482 priority patent/US5905731A/en
Priority to AU13242/95A priority patent/AU686718B2/en
Priority to JP7518365A priority patent/JPH09507357A/en
Publication of WO1995019082A1 publication Critical patent/WO1995019082A1/en
Priority to FI962752A priority patent/FI962752A/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/04Selecting arrangements for multiplex systems for time-division multiplexing
    • H04Q11/0428Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
    • H04Q11/0478Provisions for broadband connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/02Details
    • H04J3/08Intermediate station arrangements, e.g. for branching, for tapping-off
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/24Time-division multiplex systems in which the allocation is indicated by an address the different channels being transmitted sequentially
    • H04J3/247ATM or packet multiplexing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J2203/00Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0051Network Node Interface, e.g. tandem connections, transit switching
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J2203/00Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0057Operations, administration and maintenance [OAM]
    • H04J2203/006Fault tolerance and recovery
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S370/00Multiplex communications
    • Y10S370/916Multiplexer/demultiplexer

Definitions

  • the present invention relates to telecommunication systems and more particularly to
  • SDH digital hierarchy systems
  • the data is sent in the form of two packages or so-called virtual containers which essentially are made up of two sections, one being the actual data which is transmitted, i.e. the so-called payload, and the other being data which is concerned with the integrity of the data, referred to hereinafter as overhead or ancillary data.
  • One of the requirements for a system of the kind outlined above is that there must be some means for checking whether the package is correctly switched (or routed) at each individual station along the overall path of the data. Essentially this is achieved by use of the ancillary or overhead data area at each station in order to include an identity, and other monitoring information, to ensure correct switching.
  • the present invention is concerned with overcoming this problem.
  • data packages carry identification data which is unique to the package within a station, and does not depend on channel or card numbers.
  • V4 byte is one which calls for data whose purpose is to provide monitoring of the actual data. This is only valid between stations, allowing it separate use within a station. In addition some data packages (or payloads) do not have such an overhead that may be used, in which case a part of the Section Overhead of the traffic is used in its place. For clarity only the V4 byte is
  • identification data is substituted for the so-called V4 byte to ensure the correct routing of the data package whilst at the same time not creating an increase in the overhead or ancillary data contained in the data package. In other words the inclusion of such identification data does not result in a requirement for increased bandwidth.
  • ADMUX add-drop multiplexer
  • the package identification data may have the characteristics referred to in our co- pending application number 9301575 or the characteristics referred to above in connection with the present invention.
  • Figure 1 is a diagrammatic representation of a typical transmission loop connected to a main transmission path
  • FIG 2 shows diagrammatically and in more detail one of the ADMUX shown in Figure 1.
  • a transmission loop 2 is connected to a main transmission path 1 through a switch in ADMUX 3. There is included in the transmission loop 2 ADMUX switches 4, 5 and 6 each of which serves tributaries 7, 8 and 9 respectively.
  • Data destined for tributary 9 can reach the ADMUX 6 either through the path 3,4 or through the path 3,5. Data is sent on both paths, with the terminating ADMUX (ADMUX 6) selecting which to use. This provides protection against failure of either path.
  • ADMUX 6 terminating ADMUX
  • the present invention is concerned with ensuring that this is the case in arrangements where the so-called path protection is provided, i.e. the data can reach its destination by one of at least two routes.
  • the ADMUX 6 (shown in dotted lines) consists essentially of four cards 10, 11, 12 and 13. Card 11 is the switch itself. Cards 10 and 12 are so-called synchronous transport modules (STM) which can be designed to multiplex at different levels e.g. 1, 4 or 16 which equate to bit rates of 155.52 Mbit/s, 622.08 Mbit/s and 2488.32 Mbit/s respectively would thus be designated STM1, STM4 or STM16 tributary card.
  • STM synchronous transport modules
  • Data packages entering the ADMUX 6 at A and B will have inserted into the ancillary or overhead data in place of the V4 byte, data which uniquely identifies that data
  • ADMUX entry point into the ADMUX, for example by means of its channel number and card
  • This identity is distinct from the other data which forms the overhead and which is designed to enable various checks to be made in order to monitor the integrity of the data being transmitted.
  • the first two- of the above involve the monitoring of diagnostic messages inserted by
  • a path is first set up, and a controller is arranged to generate a 16 bit number which uniquely identifies that path, this number is inserted at each sender port into the diagnostic message for that channel, a separate number being used for each unidirectional path (i.e. a bidirectional path utilises 2 numbers). It will be appreciated that the 16 bit number generated, allows up to 65536 unique path numbers the ADMX4 being capable of having up to 1008 bi-directional or 2016 unidirectional cross connections.
  • the path identity number of each channel, inserted by the sender port, is arranged to be compared with the expected address (downloaded from the Mux Controller configuration-data).
  • the address check is arranged to be carried out on traffic from both Switch units simultaneously, to detect failures of either switch. This method of failure detection is
  • Parity bits are calculated at the sender port and inserted into the diagnostic
  • parity checks are carried out on traffic from the working switch and the standby switch simultaneously. This method of failure detection is subject to a persistence check and protection switching is in accordance with the allocated priorities.
  • V4 bytes occur every fourth frame (i.e. every multiframe) and a complete V4 diagnostic message requires four such bytes.
  • Each parity bit for a channel is relevant to all bits from that channel within the previous multiframe (four frames), including the V4 byte.
  • the four parity bits of the V4 message are therefore completely independent of each other and are related to the data of the previous four frames only.
  • AU-3 and AU-4 signals only eight parity bits are contained within the diagnostic message within the Signal path overhead (SOH). Since a complete diagnostic message is transmitted every frame, these are used to indicate the parity of the data within the previous frame.
  • SOH Signal path overhead
  • Each peripheral card incorporates transition-loss detectors which the internal clock signals from each switch. A failure of the (38.88 MHz) clock shall be defined as a loss- of clock transitions for a period exceeding a nominal threshold of 125-500nS. There need not be persistency check on clock failures.
  • a check is necessary to identify any alignment failure. If the alignment bits contained within the diagnostic messages are incorrect, the detecting destination port is arranged to generate a loss-of-frame alarm. This check is subject to a persistence check as described later.
  • a request to switch is arranged to be issued to all destination ports on receipt of a switch- failure indication by the Mux. controller.
  • a manual request may also be issued when demanded by an operator via the NMI. These requests are treated as switch-failure conditions and acted upon in accordance with prescribed routines. No persistence check is carried out on such conditions.
  • a persistence check is performed to prevent spurious switching during transient conditions (e.g. MSP switching).
  • This check takes the form of a threshold on the number of permissible consecutive mismatches of the diagnostic messages, with the messages being partially updated and compared every multiframe.
  • a hardware persistence check is therefore applied to the channel identification number and the parity check independently. This persistence is programmable from between 1 and 256 successive failures of the check. The enabling and disabling of protection is carried out according to the following
  • V4-bvte diagnostic message format is as shown in the following table.
  • Section Overhead diagnostic message configurations are treated as follows: TU-3 and AU-3
  • the diagnostic message is contained in the first three columns of the first three rows of the SOH, as follows. Section Overhead Bytes
  • CMN D15 D14 D13 D12 Dl l D10 D9 D8
  • the diagnostic message is contained in the first column of the first three rows of the SOH.
  • the three bytes 'A', 'B' and 'C have the same format as bytes 'AMN', 'BMN' and 'CMN' for TU-3 and AU-3 signals.
  • Comparison messages sent from the mux. controller and stored in an ASIC at the destination ports have the following format:
  • the system described above gives an effective protection arrangement for ADMX switch plane protection without any need for disabling a card when protection is applied to a traffic path.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Time-Division Multiplex Systems (AREA)
  • Input Circuits Of Receivers And Coupling Of Receivers And Audio Equipment (AREA)
  • Emergency Protection Circuit Devices (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)
  • Near-Field Transmission Systems (AREA)
  • Exchange Systems With Centralized Control (AREA)

Abstract

In a digital telecommunication system having data packages carrying identification data, the identification data is characterised in that it is unique to the package within a station and does not depend on the identity of the originating station.

Description

SYNCHRONOUS TRANSMISSION SYSTEMS
The present invention relates to telecommunication systems and more particularly to
digital hierarchy systems (SDH). In such systems data is switched within an individual
station to the appropriate output port. Also alternate routes are provided between
stations by which data can be transmitted from an originating stations port to a receiver
stations port so that failure of one route, e.g. due to accidental damage, will not prevent the data from reaching the receiver stations port via the other route.
The data is sent in the form of two packages or so-called virtual containers which essentially are made up of two sections, one being the actual data which is transmitted, i.e. the so-called payload, and the other being data which is concerned with the integrity of the data, referred to hereinafter as overhead or ancillary data.
One of the requirements for a system of the kind outlined above is that there must be some means for checking whether the package is correctly switched (or routed) at each individual station along the overall path of the data. Essentially this is achieved by use of the ancillary or overhead data area at each station in order to include an identity, and other monitoring information, to ensure correct switching.
In our co-pending application no. 9301575 we disclose an arrangement where the package is identified in terms of the channel number of the data, and the receiving stations card number. However there is a potential problem with such an arrangement in situations where the package travels by the alternative route referred to earlier. In the event of failure of the first route the package will acquire a new channel and card number. This means that the destination port of the station will not recognise the package because it will be looking for a package which has an identification which is characteristic of the first route. This problem is a direct result of the use of the alternate route protection identified earlier.
The present invention is concerned with overcoming this problem.
According to the present invention in a digital telecommunications system of the kind referred to, data packages carry identification data which is unique to the package within a station, and does not depend on channel or card numbers.
In designing systems of the kind referred to there is always the conflicting requirement of on the one hand making maximum use of the transmission capacity to transmit payload data and on the other hand ensuring the correct transmission of that payload data. In other words in each data package a balance has to be struck between the ratio of payload capacity and overhead or ancillary capacity.
Further design constraints are the internationally agreed standards and protocols which
are necessary to ensure that the various national telecommunications systems can communicate with one another, e.g. the so-called CCITT standards and protocols.
Included in the ITU (formally CCITT) standards concerning the above mentioned overhead or ancillary data is one which calls for data whose purpose is to provide monitoring of the actual data, referred to as the V4 byte. This is only valid between stations, allowing it separate use within a station. In addition some data packages (or payloads) do not have such an overhead that may be used, in which case a part of the Section Overhead of the traffic is used in its place. For clarity only the V4 byte is
described below, but the same principle applies to the Section Overhead.
According to one aspect of the present invention overhead or ancillary data characteristic
of the identification of a data package is substituted for the so-called V4 byte to ensure the correct routing of the data package whilst at the same time not creating an increase in the overhead or ancillary data contained in the data package. In other words the inclusion of such identification data does not result in a requirement for increased bandwidth.
More specifically where an add-drop multiplexer (ADMUX) is employed to switch data from a data transmission channel into a so-called tributary channel the package identification data is substituted for the V4 byte as the package enters the ADMUX and is re-substituted as the package leaves the ADMUX.
The package identification data may have the characteristics referred to in our co- pending application number 9301575 or the characteristics referred to above in connection with the present invention.
How the invention may be carried out will now be described by way of example only and with reference to the accompanying drawings in which: Figure 1 is a diagrammatic representation of a typical transmission loop connected to a main transmission path; and
Figure 2 shows diagrammatically and in more detail one of the ADMUX shown in Figure 1.
A transmission loop 2 is connected to a main transmission path 1 through a switch in ADMUX 3. There is included in the transmission loop 2 ADMUX switches 4, 5 and 6 each of which serves tributaries 7, 8 and 9 respectively.
Data destined for tributary 9 can reach the ADMUX 6 either through the path 3,4 or through the path 3,5. Data is sent on both paths, with the terminating ADMUX (ADMUX 6) selecting which to use. This provides protection against failure of either path. When the packet of data reaches its destination at 9, there must be means to check that the correct packet of data has been switched down to it by the switch in ADMUX 6. The present invention is concerned with ensuring that this is the case in arrangements where the so-called path protection is provided, i.e. the data can reach its destination by one of at least two routes.
Referring to Figure 2, the ADMUX 6 (shown in dotted lines) consists essentially of four cards 10, 11, 12 and 13. Card 11 is the switch itself. Cards 10 and 12 are so-called synchronous transport modules (STM) which can be designed to multiplex at different levels e.g. 1, 4 or 16 which equate to bit rates of 155.52 Mbit/s, 622.08 Mbit/s and 2488.32 Mbit/s respectively would thus be designated STM1, STM4 or STM16 tributary card.
Data packages entering the ADMUX 6 at A and B will have inserted into the ancillary or overhead data in place of the V4 byte, data which uniquely identifies that data
package within that ADMUX. This contrasts with the arrangement disclosed in our co-
pending application no. 9301575 where the data package is identified in terms of its
entry point into the ADMUX, for example by means of its channel number and card
number. This would result in the packages at A and B having different identifications.
This identity is distinct from the other data which forms the overhead and which is designed to enable various checks to be made in order to monitor the integrity of the data being transmitted.
Having described the inventive concept illustrated in broad terms in relation to the accompanying drawings there will now be given a more detailed description of the embodiment of the present invention.
It is necessary to ensure that switch protection takes place automatically a failure condition at a destination port is detected or alternatively on demand from the ADMUX controller.
There are a number of conditions which can be used to initiate switching and these are: - mismatch on path identification number - failure of parity checks
- failure of alignment
- loss-of system-clock transitions
The first two- of the above involve the monitoring of diagnostic messages inserted by
sender ports which are compared with data which is downloaded from a Mux Controller as a 'comparison message' or which is calculated internally (parity errors). For TU-1 and TU-2 SDH signals, where the diagnostic messages are contained in the V4 bytes and are completely updated only every 16 frames (4 V4 bytes), the comparison is carried out every four frames on a partial V4 message. For TU-3, AU-3 and AU-4 signals, the diagnostic message is fully updated every frame.
According to the invention a path is first set up, and a controller is arranged to generate a 16 bit number which uniquely identifies that path, this number is inserted at each sender port into the diagnostic message for that channel, a separate number being used for each unidirectional path (i.e. a bidirectional path utilises 2 numbers). It will be appreciated that the 16 bit number generated, allows up to 65536 unique path numbers the ADMX4 being capable of having up to 1008 bi-directional or 2016 unidirectional cross connections.
At each destination port, the path identity number of each channel, inserted by the sender port, is arranged to be compared with the expected address (downloaded from the Mux Controller configuration-data). The address check is arranged to be carried out on traffic from both Switch units simultaneously, to detect failures of either switch. This method of failure detection is
preferably subject to a persistence check and protection switching is in accordance with
established priorities.
In carrying the invention to effect parity checks are carried-out on the data of each channel. Parity bits are calculated at the sender port and inserted into the diagnostic
messages such that even parity is maintained in each channel. At the destination port, the parity of each channel is again calculated and any parity errors generate an alarm signal. As with the source address checks, the parity checks are carried out on traffic from the working switch and the standby switch simultaneously. This method of failure detection is subject to a persistence check and protection switching is in accordance with the allocated priorities.
For TU- 1 or TU-2 signals, V4 bytes occur every fourth frame (i.e. every multiframe) and a complete V4 diagnostic message requires four such bytes. Each parity bit for a channel is relevant to all bits from that channel within the previous multiframe (four frames), including the V4 byte. The four parity bits of the V4 message are therefore completely independent of each other and are related to the data of the previous four frames only.
For TU-3, AU-3 and AU-4 signals only eight parity bits are contained within the diagnostic message within the Signal path overhead (SOH). Since a complete diagnostic message is transmitted every frame, these are used to indicate the parity of the data within the previous frame. Each peripheral card incorporates transition-loss detectors which the internal clock signals from each switch. A failure of the (38.88 MHz) clock shall be defined as a loss- of clock transitions for a period exceeding a nominal threshold of 125-500nS. There need not be persistency check on clock failures.
A check is necessary to identify any alignment failure. If the alignment bits contained within the diagnostic messages are incorrect, the detecting destination port is arranged to generate a loss-of-frame alarm. This check is subject to a persistence check as described later.
A request to switch is arranged to be issued to all destination ports on receipt of a switch- failure indication by the Mux. controller. A manual request may also be issued when demanded by an operator via the NMI. These requests are treated as switch-failure conditions and acted upon in accordance with prescribed routines. No persistence check is carried out on such conditions.
In cases of diagnostic message failure, a persistence check is performed to prevent spurious switching during transient conditions (e.g. MSP switching). This check takes the form of a threshold on the number of permissible consecutive mismatches of the diagnostic messages, with the messages being partially updated and compared every multiframe. A hardware persistence check is therefore applied to the channel identification number and the parity check independently. This persistence is programmable from between 1 and 256 successive failures of the check. The enabling and disabling of protection is carried out according to the following
cπtena: a. Unconnected - no checks performed b. Connected - all checks performed c. - Protected - all checks performed
The V4-bvte diagnostic message format is as shown in the following table.
MSB LSB
Parity Alignment bits bits.
V4 byte 1 PI 0 Al 0 D3 D2 Dl DO
V4 byte 2 P2 0 A2 0 D7 D6 D5 D4
V4byte 3 P3 0 A3 0 Dll D10 D9 D8
V4 byte 4 P4 0 A4 0 D15 D14 D13 D12
These bits are defined as follows :- Data Parity
PI P2 P3 P4
Alignment Bits
Al A2 A3 A4
Path Identification Number
DO to D15
The various Section Overhead diagnostic message configurations are treated as follows: TU-3 and AU-3 The diagnostic message is contained in the first three columns of the first three rows of the SOH, as follows. Section Overhead Bytes
Row Column
1 2 3
1 AMI AM2 AM3
2 BM1 BM2 BM3
3 CM1 CM2 CM3
Where the bytes shown have the format:
MSB LSB
AMN = PI P2 P3 P4 P5 P6 P7 P8
BMN = D7 D6 D5 D4 D3 D2 Dl DO
CMN = D15 D14 D13 D12 Dl l D10 D9 D8
(where N = 1 to 3)
AU-4
The diagnostic message is contained in the first column of the first three rows of the SOH.
The three bytes 'A', 'B' and 'C have the same format as bytes 'AMN', 'BMN' and 'CMN' for TU-3 and AU-3 signals.
Comparison messages sent from the mux. controller and stored in an ASIC at the destination ports have the following format:
MSB LSB
Byte l = D7 D6 D5 D4 D3 D2 Dl DO Byte 2 = • D15 D14 D13 D12 Dll D10 D9 D8
The system described above gives an effective protection arrangement for ADMX switch plane protection without any need for disabling a card when protection is applied to a traffic path.

Claims

1. In a digital telecommunication system having data packages carrying identification data, the identification data is characterised in that it is unique to the package within a station and does not depend on the identity of the originating station.
2. A system as claimed in Claim 1 which comprises:
a) means to set up a uni-directional route or path through the switch;
b) a controller to generate an identification number which uniquely identifies that route or path;
c) means to insert that identification number at each sender port into a diagnostic message for that channel ; and
d) means at each of a plurality of destination ports to compare the actual identification number received with that expected.
3. A system as claimed in Claim 2 in which the unique identification number is applied to the data package as it enters an ADMUX, in place of the V4 byte normally carried by the data package, and is replaced by the V4 byte as the data package leaves the ADMUX.
4. A system substantially as hereinbefore described with reference to and as shown in the accompanying drawings.
PCT/GB1995/000014 1994-01-05 1995-01-05 Synchronous transmission systems WO1995019082A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
DE69532882T DE69532882T2 (en) 1994-01-05 1995-01-05 SYNCHRONOUS TRANSMISSION SYSTEMS
EP95904648A EP0738444B1 (en) 1994-01-05 1995-01-05 Synchronous transmission systems
AT95904648T ATE264588T1 (en) 1994-01-05 1995-01-05 SYNCHRONOUS TRANSMISSION SYSTEMS
US08/666,482 US5905731A (en) 1994-01-05 1995-01-05 Synchronous telecommunications system with unique indentification of paths
AU13242/95A AU686718B2 (en) 1994-01-05 1995-01-05 Synchronous transmission systems
JP7518365A JPH09507357A (en) 1994-01-05 1995-01-05 Telecommunications system
FI962752A FI962752A (en) 1994-01-05 1996-07-04 Synchronous data transmission system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB9400057A GB9400057D0 (en) 1994-01-05 1994-01-05 Telecommunications system
GB9400057.7 1994-01-05

Publications (1)

Publication Number Publication Date
WO1995019082A1 true WO1995019082A1 (en) 1995-07-13

Family

ID=10748389

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB1995/000014 WO1995019082A1 (en) 1994-01-05 1995-01-05 Synchronous transmission systems

Country Status (12)

Country Link
US (1) US5905731A (en)
EP (1) EP0738444B1 (en)
JP (1) JPH09507357A (en)
CN (1) CN1080505C (en)
AT (1) ATE264588T1 (en)
AU (1) AU686718B2 (en)
CA (1) CA2180550A1 (en)
DE (1) DE69532882T2 (en)
FI (1) FI962752A (en)
GB (2) GB9400057D0 (en)
WO (1) WO1995019082A1 (en)
ZA (1) ZA9565B (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6298038B1 (en) * 1997-04-24 2001-10-02 Nortel Networks Limited Transparent transport
JP2000049898A (en) 1998-07-31 2000-02-18 Sony Computer Entertainment Inc Information reception device and method, information reception system, information transmission device and method and information transmission/reception system
US6348985B1 (en) 2000-12-08 2002-02-19 Seneca Networks Bidirectional WDM optical communication network with data bridging plural optical channels between bidirectional optical waveguides
US6411412B1 (en) 2000-12-08 2002-06-25 Seneca Networks WDM optical communication network with data bridging plural optical channels between optical waveguides
JP2012044574A (en) * 2010-08-23 2012-03-01 Nec Corp Transmission system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1990006660A1 (en) * 1988-12-09 1990-06-14 Transwitch Corporation Virtual tributary cross connect switch and switch network utilizing the same
US4999829A (en) * 1989-11-06 1991-03-12 At&T Bell Laboratories Automatic fault recovery in a packet network
EP0437197A2 (en) * 1990-01-09 1991-07-17 Fujitsu Limited Digital cross connection apparatus

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4742511A (en) * 1985-06-13 1988-05-03 Texas Instruments Incorporated Method and apparatus for routing packets in a multinode computer interconnect network
US4964095A (en) * 1989-05-12 1990-10-16 Alcatel Na, Inc. Data communication bypass apparatus and method
US5189410A (en) * 1989-12-28 1993-02-23 Fujitsu Limited Digital cross connect system
EP0529649B1 (en) * 1991-08-30 1998-12-02 Nec Corporation Virtual tributary path idle insertion using timeslot interchange
US5365518A (en) * 1992-03-02 1994-11-15 Alcatel Network Systems, Inc. Sonet overhead server
US5315594A (en) * 1992-03-02 1994-05-24 Alcatel Network Systems, Inc. Inter-network transport element of sonet overhead
JPH0774749A (en) * 1993-09-01 1995-03-17 Hitachi Ltd Switching system
FR2711466B1 (en) * 1993-10-20 1996-01-26 Tremel Jean Yves ATM type telecommunication network test and ATM connection performance measurement.
US5493565A (en) * 1994-08-10 1996-02-20 Dsc Communications Corporation Grooming device for streamlining a plurality of input signal lines into a grouped set of output signals

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1990006660A1 (en) * 1988-12-09 1990-06-14 Transwitch Corporation Virtual tributary cross connect switch and switch network utilizing the same
US4999829A (en) * 1989-11-06 1991-03-12 At&T Bell Laboratories Automatic fault recovery in a packet network
EP0437197A2 (en) * 1990-01-09 1991-07-17 Fujitsu Limited Digital cross connection apparatus

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
J. GRUBER, ICC93, vol. 3, CH, pages 1308 - 1314, XP000448355 *
M. HAMMER ET AL, PHILIPS TELECOM REVIEW, vol. 51, no. 1, NL, pages 43 - 50, XP000426373 *

Also Published As

Publication number Publication date
DE69532882T2 (en) 2004-08-19
CN1141704A (en) 1997-01-29
CN1080505C (en) 2002-03-06
GB2285554B (en) 1998-11-25
GB9400057D0 (en) 1994-03-02
ATE264588T1 (en) 2004-04-15
GB9500141D0 (en) 1995-03-01
AU1324295A (en) 1995-08-01
CA2180550A1 (en) 1995-07-13
FI962752A (en) 1996-08-15
AU686718B2 (en) 1998-02-12
JPH09507357A (en) 1997-07-22
GB2285554A (en) 1995-07-12
US5905731A (en) 1999-05-18
ZA9565B (en) 1996-02-08
FI962752A0 (en) 1996-07-04
EP0738444B1 (en) 2004-04-14
EP0738444A1 (en) 1996-10-23
DE69532882D1 (en) 2004-05-19

Similar Documents

Publication Publication Date Title
JP3195465B2 (en) Bidirectional multiplex section switching ring transmission system and communication signal transfer method
US6553034B2 (en) Virtual path ring protection method and apparatus
CN1211964C (en) Method and apparatus for multiplex transmission
US6147968A (en) Method and apparatus for data transmission in synchronous optical networks
EP1411663B1 (en) Traffic handling in a protected synchronous communication network
US4964112A (en) Method for monitoring the quality of a digital signal in sections of a data transmission circuit
US6735171B2 (en) SDH transmission system, SDH transmission equipment and line switching control method in SDH transmission system
EP1083690B1 (en) Enhanced multiframe alignment for tandem connection trails
GB2338370A (en) Identifying undeliverable traffic in a SDH system
US5905731A (en) Synchronous telecommunications system with unique indentification of paths
US7526197B2 (en) Utilizing the protecting bandwidth in a SONET network
JP4244150B2 (en) Bidirectional track switching ring network
US4964122A (en) TDM data transmission system
US6456596B2 (en) Synchronous transmission systems
US20030142678A1 (en) Virtual path ring protection method and apparatus
US5710759A (en) Switch protection arrangement
FI98771C (en) A method for examining the operation of a network element of a data transmission network
US6987759B1 (en) Method for using a pre-configured TDM switch and traffic discard to facilitate UPSR selection
EP1598969A1 (en) Optimized link capacity adjustment scheme

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 95191754.4

Country of ref document: CN

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 NL 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 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

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 1995904648

Country of ref document: EP

Ref document number: 277856

Country of ref document: NZ

WWE Wipo information: entry into national phase

Ref document number: 2180550

Country of ref document: CA

Ref document number: 962752

Country of ref document: FI

WWE Wipo information: entry into national phase

Ref document number: 08666482

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 1995904648

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWG Wipo information: grant in national office

Ref document number: 1995904648

Country of ref document: EP