Data transmission system

Abstract

The invention relates to a data transmission system and a method, in general, and to a data transmission system and a method for frame-oriented digital data, in particular.

Description

CROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims priority of European Application No. 01302929.3 filed on Mar. 28, 2001.

FIELD OF THE INVENTION

[0002] The invention relates to a data transmission system, a method, and a device in general, and to a data transmission system, a method and a device for frame-oriented digital data, in particular.

BACKGROUND OF THE INVENTION

[0003] The importance of digital data transmission for the information society of the 21st Century is increasing strongly. Important applications for this are, for example, voice and data transmission in telecommunication networks and via the Internet. A major part of digital data transmission is presently accomplished by means of optical signals via optically conducting fibres, since transmission via an optical channel (OCh) generally permits higher data rates than transmission of electric signals via metallic conductors. The invention is preferably applied, but not restricted to optical transmission.

[0004] Standards are defined by the International Telecommunication Union (ITU) in order to ensure compatibility of the data formats between different users in a network. Frequently used standards are the ITU-T G.813, ITU-T G.958, ITU-T G.825, ITU-T G.707 and ITU-T G.975 standards. Hereby, said standards and documents are incorporated as subject matter of the present disclosure by reference.

[0005] A flexible data format is achieved by virtue of the fact that the data are embedded in frames which typically contain an overhead and payload data sections (payload envelopes). The payload data to be transmitted are embedded in these payload sections or payload areas. The overhead serves in this case, inter alia, for transmitting control information. Regarding the processing of overheads of optical channels in the case of frame-oriented data transmission via optical channels, reference may also be made to Ballintine, J. E. “Data Format and Generic Processing for OCh-OH”, wave star, volume 420.200.11, issue 1.0. Hereby, said document is incorporated as subject matter of the present disclosure by reference.

[0006] In order to transmit a plurality of client signals or clients via the same physical channel, the client signals are typically multiplexed. For example, four client signals or secondary streams with data rates of respectively 2.488 gigabits per second (Gbit/s) (≈2.5 Gbit/s) are mapped into a server signal or server of approximately 9.953 Gbit/s using time-division multiplex operation. Known data hierarchies typically used for this purpose are the synchronous digital hierarchy (SDH) and the synchronous optical network (SONET).

[0007] In these known transmission systems in accordance with SDH or SONET, data are typically transmitted by means of synchronous transport modules (STM). A synchronous transport module contains a dedicated STM section overhead (STM-SOH) and a payload data section or payload envelope in which virtual containers with payload data are embedded.

[0008] A central problem in digital data transmission is the handling of different data rates between the client signals and the server signal. For example, if the rate of the client signal is higher than the rate of the server signal, excess data must be stored as stuff bytes in stuff locations (negative stuff opportunities) in order to achieve rate adaptation. For this purpose, each synchronous transport module in the section overhead contains three stuff bytes for rate adaptation or matching. In order to locate the start of the virtual container, which start can be displaced by the stuffing, there is, moreover, located in the section overhead of each synchronous transport module a pointer which points as start value to the first byte of the virtual container and is decremented or incremented during stuffing. In the transmission of the synchronous transport modules in accordance with SDH or SONET standards stuff locations are therefore reserved inside each STM section overhead.

[0009] However, using known frame structures and so-called STM-N/OC-M multiplexers which operate according to the ITU-T G. 707 standard, the section overhead (SOH) is always terminated. Those hierarchies are therefore data transparent and timing transparent only with reference to the administrative data units (AU-x data units) of the synchronous digital hierarchy, and with reference to the equivalent data units of the synchronous optical network and to the payload data. The original timing and the STM section overhead are not transmitted or propagated.

[0010] Consequently, the synchronous digital hierarchy and the synchronous optical network are not data transparent and not timing transparent or more precisely are not completely data transparent and not completely timing transparent. That is to say bit-by-bit data preservation is not ensured during transmission.

[0011] This method proves, however, to be disadvantageous, as, inter alia, the outlay on hardware and software is increased, as it may be necessary to is generate a new overhead in the receiver. Therefore those aforementioned frame structures or multiplexing techniques require a high and cost intensive outlay on hardware and software.

SUMMARY OF THE INVENTION

[0012] Therefore, it is an object of the invention to provide a digital data transmission system, a method and a device which avoid or at least reduce the disadvantages of the prior art.

[0013] A further object of the invention is to provide a transmission system and a method which enable improved rate adaptation between a client signal or client signals and a server signal.

[0014] Still a further object of the invention is to provide a transmission system and a method which cause a lesser degree of complexity and a lower outlay on costs.

[0015] Still a further object of the invention is to provide a transmission system and a method which enable reliable data transmission at a low bit error rate.

[0016] These objects are achieved in a surprisingly simple manner by the transmission system, the method and the device which are defined by claims 1, 30 and 34.

[0017] The transmission system according to the present invention provides a frame-oriented transmission of digital data, comprising a server signal and at least a first client signal. Said server signal comprises a server frame structure and data of said first client signal are embedded in said server frame structure. First data for rate adaptation between the server signal and the first client signal are provided and said transmission is data transparent.

[0018] Such data transparency is highly advantageous as the data are preserved bit-by-bit, thereby simplifying hardware and software and, consequently, reducing complexity and costs. In other words, the data stream is transmitted, multiplexed and/or de-multiplexed bit-by-bit.

[0019] Furthermore it is advantageous that the data rate of the generated data stream keeps constant during transmission, multiplexing and/or de-multiplexing, in particular the data rate is neither increased nor reduced.

[0020] Preferably the whole first client signal or at least essentially the whole first client signal is transmitted data transparent. Data transparency of the whole data stream is advantageous as it can be applied for signals with known and unknown data structure. Therefore the system is future proof. Furthermore the signal is bit-by-bit restored when received or after de-multiplexing as it is transmitted or multiplexed.

[0021] Furthermore, transmission is preferably timing transparent with respect to the data of the first client signal, i.e. the timing related to the data of the first client signal is preserved during the transmission.

[0022] Timing transparency of the datastream is advantageous as the signal can be used for synchronization purposes after reception or de-multiplexing.

[0023] Preferably, said first client signal is a frame-oriented signal, e.g. according to SDH or SONET standards. However, the transmission system is suitable for non-frame-oriented client signals, e.g. in accordance with the Ethernet standard or the Internet Protocol (IP). Advantageously, the present transmission system is, therefore, very flexible.

[0024] Preferably, said first client signal comprises a client frame structure, e.g. according to the STM-N G.707 standard of the ITU-T or according to OC-M standard. Such frame structure comprises a data portion reserved for overhead data, the so-called section overhead (SOH). Preferably, the overhead also comprises a data portion for administrative unit pointers. Furthermore, said client frame structure comprises a portion for embedding payload data, e.g. an STM-N or OC-M payload envelope. The actual data to be transmitted with the first client signal are embedded in that payload envelope.

[0025] Advantageously, not only the payload data, but also at least a portion of the overhead data, e.g. at least a portion of the section overhead, in particular at least a portion of the regenerator section overhead RSOH and/or at least a portion of the multiplexing section overhead MSOH of the first client signal, is or are transmitted data transparent. Preferably a multiplexer or multiplexing device for time division multiplexing is used. Beneficially, the requirements for terminating the overhead, in particular the section overhead, of SDH/SONET signals for hardware and software is lower than in current systems. Therefore, a faster time-to-market can be achieved due to less effort and more cost effectiveness.

[0026] In a preferred embodiment said payload data and at least a portion of said overhead data, in particular at least a portion of the regenerator section overhead RSOH, are embedded in said server frame structure of said server signal. With respect to the server frame structure said portion of the overhead data are processed like payload data.

[0027] In a further preferred embodiment said section overhead comprises at least a first data sequence having predetermined values, e.g. A1 and A2 bytes of the STM-N-SOH or OC-M-SOH. Said predetermined or known values preferably form a frame alignment word or are at least a portion of said client frame structure. Said data having predetermined values or a predetermined number of bytes of said frame alignment word are replaced by said first data for rate adaptation, e.g. when the first client signal is multiplexed to the server signal. Heretofore said first data sequence or said predetermined bytes of the frame alignment word are terminated, e.g. with multiplexing and are later reinserted, e.g. with de-multiplexing.

[0028] At this point it should be noted, that this procedure could also be termed “pseudo data transparent”, as said first data sequence is not directly transmitted, but is terminated and later the same values are reinserted. Therefore, the received data are bit-by-bit the same as if data would have been transmitted bit-by-bit. Consequently, for a receiver of the data after de-multiplexing it at least appears as a bit-by-bit transmission. Therefore, in this disclosure terminology “data transparent” should be understood comprising the previously so-called “pseudo data transparency”. In other words, according to this disclosure, data transparent means that the same bit stream or byte stream is received as it is transmitted, even though some bits or bytes are terminated and reinserted intermediately.

[0029] Preferably, said first data sequence is replaced by said first data for rate adaptation with multiplexing prior to transmission and said first data for rate adaptation are replaced with de-multiplexing by the same predetermined or known values as they had before the multiplexing.

[0030] In a preferred embodiment, data of predetermined data positions in said client frame structure, e.g. some of the A1 and A2 bytes are put into predetermined data positions or bytes in said server frame structure, e.g. at the beginning of the server frame section overhead.

[0031] Preferably, said first data sequence of the section overhead of the frame server structure which is replaced by said first data for rate adaptation is a portion or a predetermined number of said frame alignment word.

[0032] As the frame alignment word is preferably significantly longer than said first data for rate adaptation, said first data sequence can have different positions in said frame alignment word, such that the position of said first data sequence in the frame alignment word is programmable, e.g. by hardware or software, or is fixed.

[0033] Preferably, said first data for rate adaptation comprise a predetermined number of data units or bytes. The inventors have found that 13 bytes are sufficient for proper rate adaptation including error protection for multiplexing four OC48 client signals into an OC-192 server signal. However, any other number of rate adaptation bytes, e.g. 10, 11, 12, 14, 15, 16 or more bytes is also suitable, wherein better error protection or higher order multiplexing can be provided with a higher number of rate adaptation bytes.

[0034] Said first data for rate adaptation or rate adaptation bytes which are inserted in the section overhead of the server signal instead of the predetermined bytes of the frame alignment word comprise stuffing opportunities or stuff bytes and/or a pointer addressing a predetermined byte of the data of said first client signal and/or stuff control data and/or parity compensation data and/or signalling data. In a most preferred embodiment said pointer comprises 2, 3, 4, 5 or more bytes, most preferred 3 bytes. Preferably said pointer addresses the J0-byte of an STM-N or OC-M frame structure of the first client signal.

[0035] Most preferably, said first data for rate adaptation, in particular said 3-byte-pointer and said stuff control data are error protected by a Hamming Code.

[0036] As aforementioned, essentially embedding a first client signal in a server signal is described. However, advantages of the invention become even more important when a plurality of client signals is multiplexed to a server signal by a multiplexing device or a multiplexer. Exemplarily, multiplexing of 4 OC48 clients to a OC-192 server or 16 OC-12 clients to a OC-192 server is provided. However, the invention is suitable also for nearly any other signal rate.

[0037] It remains to be mentioned that unless expressly denoted, wordings first and second do not fix a temporal sequence but is used for distinguishing purposes.

[0038] The invention is explained in more detail below by means of exemplary embodiments and with reference to the drawings.

BRIEF DESCRIPTION OF THE FIGURES

[0039] It is shown in

[0040] FIG. 1 a schematic diagram of an OC-M frame structure,

[0041] FIG. 2 a schematic diagram of an OC48 section overhead,

[0042] FIG. 3 a schematic diagram of an OC48 frame alignment word,

[0043] FIG. 4 the meaning of bytes used for rate adaptation,

[0044] FIG. 5 a schematic description of a control byte,

[0045] FIG. 6 an assignment of client signal numbers to 2 bits in the control byte of FIG. 5,

[0046] FIG. 7 two subsequent OC48* frames as defined according to the present invention,

[0047] FIG. 8 a description of the pointer values of FIG. 4,

[0048] FIG. 9 a composition of a HC(7, 4, 3) hamming code word referring bit #i and

[0049] FIG. 10 a schematic diagram of the composition of byte Z, used for signalling.

DETAILED DESCRIPTION

[0050] In the following, the system and method is described exemplarily for OC48 signals. Multiplexing of four OC48 signals to a 10G-server signal is described, but it is clear to those skilled in the art that the invention can also be applied to OC-M signals with any other rate, i.e. for any value of M. Furthermore, it should be noted that the invention can also be used for any STM-N signal, as STM-N signals are nearly equivalent to OC-M signals, wherein it is M=3×N.

[0051] The transmission system according to this preferred embodiment of the invention uses certain overhead bytes of the signals which are previously not used. By this, data and timing transparency or data and timing transparent multiplexing is enabled.

[0052] Referring to FIG. 1 an OC-M frame structure 10 comprising a payload section 12 and an overhead OH is shown. The OC-M frame structure 10 comprises 270×N columns or bytes, wherein the overhead OH comprises 9×N bytes and the payload section 12 comprises 261×N bytes, wherein N M/3. The frame structure 10 further comprises 9 rows, wherein rows 1 to 3 and 5 to 9 are reserved for a section overhead SOH and row 4 is reserved for administrative unit pointers.

[0053] Referring now to FIG. 2 the OC-M overhead OH of the frame structure shown in FIG. 1 is described in more detail for M=48 or N=12, respectively. The overhead OH comprises or consists of 144 columns times 9 rows. As can be seen further in FIG. 2 the first 96 bytes of the first row comprise A1 bytes followed by A2 bytes. Said A1 and A2 bytes serve as frame alignment word FAW. The first byte after the A1 and A2 bytes is the so-called J0 byte. Said frame alignment word reserves a portion of a regenerator section overhead RSOH which is located in rows 1 to 3, whereas in rows 5 to 9 a multiplexing section overhead MSOH is located.

[0054] The frame alignment word FAW is s portion of the section overhead SOH, more precisely of the regenerator overhead RSOH of the synchronous digital hierarchy SDH frame or of the synchronous optical network SONET frame. In the exemplary OC48/STM-16 signals the frame alignment word FAW comprises 48 bytes “A1” and 48 bytes “A2”, such that the number of FAW bytes NFAW is NFAW=96.

[0055] The FAW bytes have according to the ITU-T G.707 standard always the fixed values A1=F6h and A2=28h (hexadecimal notation).

[0056] In transmission systems only a small number of the FAW bytes, typically about 5 to 8 bytes, are used for framing and framing supervision purposes. That means a large number of the bytes are unused. Some of those previously unused bytes are used for rate adaptation purposes according to the present invention.

[0057] The values of the FAW bytes are fixed or known and can therefore easily be replaced and recovered later.

[0058] Those OC-M structures shown in FIG. 1 and FIG. 2 are generally known to those skilled in the art and are described in more detail e.g. in ITU-T G.707 standard.

[0059] 10G—OC48 Multiplexing with Rate Adaptation

[0060] In the following, a system, a method and a multiplexer for mapping four independent OC48 data streams or client signals into one OC-192* server signal is described. The OC48 signals pass through unchanged and the system behaves as a SONET/SDH repeater. Timing transparency is provided.

[0061] A rate adaptation algorithm is provided using a number of NRA bytes of the frame alignment word FAW for rate adaptation. The inventors found that NRA=13 bytes are sufficient for this exemplary embodiment. In this exemplary embodiment 13 of the A2 bytes are used. However it is clear to those skilled in the art that other predetermined or known bytes, e.g. some of the A1 bytes and/or using more than 13 bytes, in particular for higher order multiplexing is also appropriate.

[0062] However, it is possible that a client of the network already uses some of the overhead bytes which should actually be unused. If the location of the “mis-used” FAW bytes is known, the locations of the FAW bytes which are used for the system according to this invention are kept programmable by hardware or software, i.e. are flexible. In general the invention provides of carrying G.707 standard conform STM-N/OC-N data signals. To keep the approach flexible, the location of the used FAW bytes, i.e. the specific ones of the A1 or A2 bytes to be replaced can be chosen or programmed by the user.

[0063] At this point the definition of the term data transparent becomes more clear. The frame alignment word FAW {A1, A2} is terminated and reinserted. In fact the complete RSOH is terminated in each SONET/SDH network element, i.e. including the frame alignment word FAW. So the method introduced here is a kind of repeater preserving all of the SONET/SDH frame except the frame alignment word FAW whose values are well defined. The transmit frequency is not increased using this method. Furthermore, the client signals as transmitted and the client signals as received are bit-by-bit equivalent.

[0064] Moreover, as described in section “B1 Parity Compensation” below, bit errors may appear in the data, i.e. also in the frame alignment word FAW, at some point between the transmitter and the receiver. Such bit errors in the frame alignment word are preferably corrected by the system according to the invention. In this case a bit-by-bit identity is still at least provided of the first client signal as transmitted by the transmitter and as received by the receiver, even though, a bit-by-bit identity of the data stream might not be existing at all times or all locations in the network between the transmitter and the receiver. Preferably, this also applies for all further client signals, if a plurality of those is multiplexed. Therefore, the transmission is called data transparent.

[0065] By performing the rate adaptation according to the invention the regular OC48 frame is transposed to a new OC48* frame. This new OC-48* frame according to the invention comprises or consists of the same number of rows and columns, i.e. number of bytes, as the regular OC48 frame. The byte locations of the frame alignment word FAW are identical to that of the regular OC48 frame. For rate adaptation purposes the actual payload, i.e. the whole OC48 frame without frame alignment word FAW, floats within the OC48* frame referred by a pointer. More precisely, a pointer V addresses the J0-byte of the OC-M section overhead. Furthermore, a certain number of bytes of the frame alignment word FAW is used for stuffing, control and signalling purposes.

[0066] Utilization of the OC48 Frame Alignment Word

[0067] As the clients or tributaries are only OC48 signals, portions of the frame alignment word FAW can be used for stuffing purposes. FIG. 3 schematically shows the structure of a OC48 frame alignment word FAW. The A1_.. and A2_.. bytes represent each a sequence of the respective bytes which are not shown. The FAW comprises 48×A1 (A1_1, . . . , A1_48) followed by 48×A2 (A2_1, . . . , A2_48), where the bytes have fixed values A1=F6h and A2=28h according to ITU G.707.

[0068] In some equipment, e.g. by Lucent Technologies Inc. only five bytes, i.e. A1_46, A1_47, A1_48, A2_1 and A2_2 are actually used for framing purposes. The remaining framing bytes still have fixed values and are preliminary unused.

[0069] Structure of the Data for Adaptation

[0070] As mentioned in the previous section the framing bytes A1_1, A1_45 and A2_3, . . . , A2_48 are typically not used. Therefore a number NRA of the FAW bytes are used for rate adaptation, i.e. stuffing, control and administration purposes. Most preferably, the last 13 bytes of the frame alignment word, i.e. bytes A2_36 to A2_48 are used. The structure of the sequence of 13 rate adaptation bytes is shown in FIG. 4 and is as follows:

[0071] NS=4 stuff bytes (S0, S1, S2, S3) are used for negative stuffing, i.e. due to a higher client or tributary frequency some bytes have to be stuffed and transported here;

[0072] NC=1 stuff control byte (C) steers the rate adaptation procedure;

[0073] NB1=1 byte (B) is used for B1 parity compensation;

[0074] NV=3 bytes (V0, V1, V2) are used for a pointer to address the location of the J0-byte of an OC48 SONET frame. As an OC48 frame comprises NOC48=38880 bytes a 2 bytes=16 bits pointer providing 216=65536 possible values is generally sufficient to address the J0-byte. However, to be tolerant of future enhancements the pointer value (V0, V1, V2) is stored in NV3 bytes (24 bits, 16777216=224 possible values);

[0075] The control information, i.e. the three pointer bytes and the one control byte are protected by a single error protecting Hamming code HC(7, 4, 3). An interleaved structure is applied to enhance burst error capabilities. The number of additional protection bytes, therefore, is NP=3.

[0076] NZ=1 byte (Z) is used for signalling e.g. Forward Defect Indication FDI, Backward Defect Indication BDI and/or Open Connection Indication OCI (i.e. Uneq);

[0077] All unused/reserved bits in the bytes used for rate adaptation are set to a fixed value, e.g. to “0”.

[0078] Stuff Bytes

[0079] NS=4 stuff bytes (S0, S1, S2, S3) are reserved for negative stuffing. Preferably, full bytes or multiples of bytes are stuffed.

[0080] Providing four stuff bytes, a jitter or frequency deviation Δf0 up to Δf0=±100 ppm or even more can be compensated by the stuffing. This calculates as follows:

NOC48 = 38880                   (Number of bytes in an OC-48 frame)
NS = 4                          (number of stuff bytes used for
                                negative stuffing)
NA1 = 48                        (number of A1 bytes)
NA2 = 48                        (number of A2 bytes)
NFAW = NA1 + NA2 = 96           (number of FAW bytes)
Δf0 per Byte = 1/NOC48 = 25 ppm (frequency deviation that can be
                                buffered by using a single byte for
                                negative stuffing)

[0081] The frequency deviation that can be processed is basicly limited by the number of used or respectively available stuff bytes NS. So generally the achievable frequency deviation of Δf0 can be expressed as 1$\begin{array}{c}\Delta f_0=N_S/\mathrm{NOC48}\\ =N_S*\Delta f_{0\mathrm{per}\mathrm{Byte}}\end{array}$

[0082] As for this exemplary embodiment four bytes are used for negative stuffing a frequency deviation of at least

Δf 0 =4/NOC48=100 ppm

[0083] can be compensated.

[0084] Stuff Control Byte

[0085] NC=1 stuff control byte is used for stuff control purposes. The structure of the stuff control byte C is shown in detail in FIG. 5. A counter reflecting the number of stuffed bytes (±0 . . . 4→4 bits; total range [−8, . . . , +7]) is implemented. This counter is defined by four bits C0, C1, C2 and C3. Two Bits C4 and C5 are not used and are reserved for future use.

[0086] Two protected bits C7, C6 of the control byte are used as a client signal or tributary channel identifier TCI. Referring to FIG. 8, a certain 2-bits value is assigned to each client signal. These bits, or respectively this feature, is used for the so-called “roll control”.

[0087] Pointer Value

[0088] NV=3 bytes (V0, V1, V2, V3) are used for representing the pointer value. It refers to the J0 byte which is floating in the OC-48* frame as shown in FIG. 7. A client signal frame #j, represented by the hatched area, is distributed over two server frames #i and #(i+1). Therein the client signal frame #j start at the J0-byte of the server frame #i and ends at the J0-byte of the following server frame #(i+1).

[0089] Each server frame starts with a portion of the original frame alignment word FAW, represented by A1* and A2* bytes and the data for rate adaptation, represented by the pointer, the control bytes C and the stuff bytes S in this FIG. 7.

[0090] With a 24 bits or 3 bytes pointer a range of 16777216 bytes can be addressed. An OC48 client signal comprises 38880 bytes, an OC-192 client signal comprises 155520 and an OC-768 client signal comprises 622080 bytes. Consequently, the pointer is prepared for further significant enhancements in the future. A pointer value description is shown in FIG. 8.

[0091] Error Protection

[0092] The NV=3 pointer bytes and the NC=1 control byte are protected by a single error correcting HC(7, 4, 3) Hamming code. Therefore NP=3 additional bytes for error control coding are provided within the data or 13 bytes for rate adaptation. The error correction mechanism is applied interleaved so that the protected bytes are robust against burst errors.

[0093] The composition of a 7 bits long Hamming HC(7, 4, 3) code word (systematic encoding) is shown in detail in FIG. 9.

[0094] As there are four bytes, i.e. three pointer bytes and one control byte, to be protected and 8 bits per byte, 8 coders are interleaved. In other words, the interleave factor is 8. That means 8 subsequent errors, i.e. a burst of 8 errors, can be corrected.

[0095] B1 Parity Compensation

[0096] A mechanism or method is provided to compensate the B1 parity value as parity errors are located in the frame alignment word FAW can appear. Therewith, errors in the frame alignment word FAW which are excluded with the reinsertion of the frame alignment word FAW are detected.

[0097] The suggested solution is to calculate the differential BIP-8 parity B over the complete actual frame alignment word FAW comprising the A1 and A2 bytes and the default frame alignment word FAW before creating a new OC48* frame according to the invention.

[0098] NB1=1 byte is reserved for this purpose and is shown and denoted B in FIG. 4. This processing makes the received B1 neutral to the rate adaptation processing although the mechanism is not completely neutral concerning defective values of the A1's and A2's. The parity compensation byte B is calculated as follows: 2$B_{\mathrm{A1}}=\sum _{i=0}^{N_{\mathrm{A1}}}\left({\mathrm{A1}}_{\mathrm{act},i}\oplus {\mathrm{A1}}_{\mathrm{def}}\right)$$B_{\mathrm{A2}}=\sum _{i=0}^{N_{\mathrm{A2}}}\left({\mathrm{A2}}_{\mathrm{act},i}\oplus {\mathrm{A2}}_{\mathrm{def}}\right)$$B=B_{\mathrm{A1}}\oplus B_{\mathrm{A2}}$

[0099] This compensation info or byte is transported in a designated location of the bytes used for rate adaptation as shown in FIG. 4. After adding (EXOR) the compensation value B to a certain byte of the frame alignment word FAW (e.g. A2_48) towards the OC48 transmit interface, the whole error information is concentrated in one FAW byte. Due to that fact, the frame alignment word FAW includes less or equal errors than before. That behaviour can be interpreted as a kind of error correction capability since all A1 and A2 values have a well defined value. Theses “corrected” FAW bytes advantageously lead to a reduced probability of out of frame incidents.

[0100] Signalling

[0101] NZ=1 byte is used to carry signalling information as shown in detail in FIG. 10.

[0102] The specific bits can have the following values: 3$\begin{array}{ccc}\mathrm{Signal}\mathrm{label}& =00& \left(\mathrm{unequipped}\right)\\ & =01& \left(\mathrm{equipped}\mathrm{non}\mathrm{specific}\right)\\ & =10,11& \left(\mathrm{reserved}\mathrm{for}\mathrm{future}\mathrm{use}\right)\\ \mathrm{BDI}& =0& \left(\mathrm{no}\mathrm{BDI};\mathrm{default}\mathrm{value}\right)\\ & =1& \left(\mathrm{BDI}\right)\\ \mathrm{FDI}& =0& \left(\mathrm{no}\mathrm{FDI};\mathrm{default}\mathrm{value}\right)\\ & =1& \left(\mathrm{FDI}\right)\end{array}$

[0103] Summarising, the total number of bytes used for realising the rate adaptation according to the invention in a single OC48 client or tributary data stream is 4$N_{\mathrm{RA}}=N_S+N_C+N_{\mathrm{B1}}+N_Z+N_V+N_P⩵4+1+1+3+1+3=13$

[0104] This number of bytes is reserved in the OC48* frame alignment word.

[0105] Jitter Requirements and Capabilities

[0106] The system should be capable of tolerating frequency deviations as requested by SDH/SONET standards of

1.	ΔfTrib <±20 ppm	(maximal deviation of client or
		tributary, i.e. OC-48 datarate)
2.	ΔfOCh <±50 ppm	(maximal deviation of transmit, (i.e.
		OCh-10G datarate)

[0107] The jitter should, furthermore, fulfill the following requirements:

1.	Jitter generation JG
	a.	JG <0.01 UIrms	(ITU G.958, p.13, section 5.3.1)
	b.	JG <0.1 UIpp	(ITU G.813, section 7.3, option 2,
			bandpass [12 kHz. . .2 MHz])
2.	Network limits for jitter JNEL
	a.	JNEL <0.15 UIrms	(ITU G.825, tab.1, section 3.1,
			[f3. . .f4] = [1 MHz. . .20 MHz])
	b.	JNEL <1.5 UIpp	(ITU G.825, tab.1, section 3.1,
			[f1. . .f4] = [5 kHz. . .20 MHz])

[0108] The jitter requirements as described above are substantially all fulfilled or can even be surpassed using the system, method or device according to the invention.

[0109] Wander Requirements

[0110] At the moment no wander requirements to be fulfilled are known.

[0111] It will be appreciated that the above-described embodiment of the system, method and device according to the present invention has been set forth solely by way of example and illustration of the principles thereof and that further modifications and alterations may be made therein without thereby departing from the spirit and scope of the invention.

Claims

1. A transmission system for frame-oriented transmission of digital data, comprising a server signal and at least a first client signal, wherein said server signal comprises a server frame structure, data of said first client signal are embedded in said server frame structure, first data for rate adaptation between the server signal and the first client signal are provided and said transmission is data transparent.

2. The transmission system according to claim 1, wherein essentially the whole first client signal is transmitted data transparent.

3. The transmission system according to claim 1, wherein said first client signal is a frame-oriented signal.

4. The transmission system according to claim 1, wherein said first client signal comprises a client frame structure, wherein payload data and overhead data of said first client signal are embedded in said client frame structure.

5. The transmission system according to claim 4, wherein at least a portion of said overhead data is transmitted data transparent.

6. The transmission system according to claim 4, wherein said payload data and at least a portion of said overhead data are embedded in said server frame structure of said server signal.

7. The transmission system according to claim 4, wherein at least a first data sequence of said overhead data having predetermined or known values and are replaced by said first data for rate adaptation.

8. The transmission system according to claim 7, wherein said first data sequence is terminated and later reinserted.

9. The transmission system according to claim 7, wherein said replacing of said first data sequence by said first data for rate adaptation is provided prior to transmission and said first data for rate adaptation are replaced by the same values as those of said first data sequence after transmission.

10. The transmission system according to claim 1, wherein said first client signal comprises a client frame structure and first data of predetermined data positions in said client frame structure are put into predetermined data positions in said server frame structure.

11. The transmission system according to claim 10, wherein said first data comprise at least a portion of a frame alignment word.

12. The transmission system according to claim 10, wherein said first data comprise at least a portion of a frame alignment word of said client frame structure.

13. The transmission system according to claim 11, wherein the position of said first data sequence within said frame alignment word is programmable or fixed.

14. The transmission system according to claim 11, wherein said first data sequence is a portion of said frame alignment word.

15. The transmission system according to claim 1, wherein said first client signal is a signal according to synchronous digital hierarchy (SDH) standard or according to synchronous optical network (SONET) standard.

16. The transmission system according to claim 1, wherein said first client signal comprises OC-M frame structures or STM-N frame structures, preferably according to the ITU-T G.707 standard.

17. The transmission system according to claim 1, wherein said first data for rate adaptation comprise a predetermined number of data units.

18. The transmission system according to claim 1, wherein said first data for rate adaptation between the server signal and first client signal comprise stuffing opportunities.

19. The transmission system according to claim 1, wherein said first data for rate adaptation comprise a pointer addressing a predetermined byte of the data of said first client signal.

20. The transmission system according to claim 19, wherein said pointer comprises three bytes.

21. The transmission system according to claim 19, wherein said predetermined byte is the J0-byte of an STM-N-frame structure or OC-M-frame structure.

22. The transmission system according to claim 1, wherein said first data for rate adaptation comprise stuff control data.

23. The transmission system according to claim 1, wherein said first data for rate adaptation comprise parity compensation data.

24. The transmission system according to claim 1, wherein said first data for rate adaptation comprise signalling data.

25. The transmission system according to claim 1, wherein said first data for rate adaptation are error protected, preferably by a hamming code.

26. The transmission system according to claim 1, wherein data of a second client signal are embedded in said server frame structure and second data for rate adaptation between the server signal and the second client signal are provided in said server frame structure.

27. The transmission system according to claim 26, wherein said first client signal is multiplexed with a second client signal, data of a second client signal are embedded in said server frame structure, said second data for rate adaptation are provided in said server frame structure.

28. The transmission system according to claim 1, wherein a plurality of client signals is multiplexed, data of each of the plurality of client signals are embedded in said server frame structure, data for rate adaptation between the server signal and each of the client signals are provided in said server frame structure.

29. The transmission system according to claim 28, wherein said plurality of client signals comprises a number of client signals which is an integer power of two.

30. A method for frame-oriented transmission of digital data, comprising: providing a server signal comprising a server frame structure, providing at least a frame-oriented first client signal, embedding data of said first client signal in said server frame structure, providing data for rate adaptation between the server signal and the first client signal, embedding said data for rate adaptation in said server frame structure.

31. The method of claim 30, wherein overhead and payload data of said first client signal are embedded in said server frame structure for transparent transmission.

32. The method of claim 30, wherein a pointer addressing a predetermined byte of the data of said first client signal is provided.

33. The method of claim 30, wherein a plurality of frame-oriented client signals is multiplexed and embedded in the server signal and each a pointer is assigned to each of said client signals of said plurality of frame-oriented client signals and each of said pointers of the server signal is addressing a predetermined byte of the data of the respective client signal.

34. A device for embedding at least a digital first client signal into a digital server signal wherein said server signal comprises a server frame structure with an overhead and a payload section, said device comprising: means for embedding data of said first client signal in said server frame structure, means for providing first data for rate adaptation between the server signal and the first client signal and means for replacing a plurality of predetermined bytes of said overhead of the server frame structure by said first data for rate adaptation.