Patent Application
20100002727
The invention relates to inverse multiplexing within telecommunication, and in particular to a versatile inverse multiplex protocol comprising associated state machines and a method for using this protocol allowing a high speed link to be distributed via an inverse multiplexer into a number of lower speed connections.
An inverse multiplexer accepts a single, high capacity information stream and splits it up into multiple streams with information, each of which is sent over a separate and lower capacity link, the process is reversed at the receiving end. Resynchronization at the receiving end is one of the major problems that have to be dealt with, as each of the four links may impose different levels of propagation delay on the signal due to for example different route lengths.
In a system with many low speed connections the current invention seeks to provide a high speed link by combining the bandwidth of several low speed links by using inverse multiplexing.
Several products with proprietary multiplexing methods exist and a “Multilink whitepaper” mentions three inverse multiplexing methods: Bit based, Multi-link PPP (MLPPP) and Multi-link Frame Relay (MLFR).
The existing products have automatic activation/de-activation of links based on the quality of the link.
Existing solutions supports multiplexing of up to 8xE1 links.
Another known solution is inverse multiplexing with ATM bonding. The ATM inverse multiplexing involves multiplexing and de-multiplexing of ATM cells in a cyclic fashion among multiple links to form a higher bandwidth.
The existing solutions are limited to a maximum of eight E1 links. Further, these solutions employ inefficient protocols i.e. overhead reducing effective bandwidth.
To meet the requirements of low transmission delay, a minimized overhead, an increased working range, a reduced number of repeaters, reduced service and maintenance, an increased reliability and robustness, as well as higher availability for the transmission systems, a new and inventive mechanism of inverse multiplex protocol is disclosed.
There exists no versatile Inverse Multiplex Protocol for transporting or spreading high speed data across several low speed data connections. Hence a versatile solution allowing high speed data on one link to be distributed over a suitable number of lower speed links, where the number of lower speed links can vary over a wide range of connections is a wanted solution today. For example, a protocol supporting connections and disconnections of low speed links where the number of low speed links can be within the range of 2-63 without loss of data, is not supported by any known inverse multiplexing protocol. These and other features will be met by the present invention.
It is an object of the present invention to provide a method and an arrangement avoiding the above described problems.
The features defined in the independent claims enclosed characterize this method and arrangement.
In order to make the invention more readily understandable, the discussion that follows will refer to the accompanying drawing.
The present invention discloses an arrangement and a method for the use of said arrangement, where the arrangement's main feature is its versatility and flexibility within inverse multiplexing and particularly within inverse multiplexing using an inverse multiplexer protocol according to the present invention. In the following a detailed description of the present invention with support in the accompanying drawings is given.
The present invention defines a protocol for inverse multiplexing over G.704 multi frames. The protocol does not introduce overhead to the G.704 and provide means to add and remove links without introducing loss of information.
In the following the wording link is supposed to be read as any communication channel or circuit adapted for transfer of data between two or more nodes.
The protocol also provides delay information for each link in addition to information about link ordering for multiplexing/de-multiplexing.
The protocol defines the behaviour between the local and remote ends of one link and an instance of the protocol applied to one link operates independently of protocol instances applied to other links. However, the implementation that extracts information from a link must correlate the information from all the links and decide which links that are allowed to carry data.
The protocol defines how to identify the remote end so that the implementation can enable inverse multiplexing only for links that are connected to the same remote end. Alien links (which may be due to erroneous configuration of connections) should not be enabled for participation in the multiplexing scheme.
Link quality monitoring is not a part of the inverse mux protocol as this is provided by the G.704 framing.
In the above reference is made to G.704 multi frames and inverse multiplexing, however the solution discussed above can be expanded to cover signal lines with bit transfer rates different from those covered by G.704, wherever the inverse multiplexer technique described with support in table 2 and 3 is applicable, the present invention will be applicable. That is if the lower speed links have enough spare bits (Sa bits or similar) to implement the present protocol it will be applicable.
The present invention will in addition to describing the inverse multiplexing protocol in detail also provide some implementation examples such as state machines to better communicate how the protocol operates.
Note that the concept of the Inverse Multiplex Protocol is broader than the implementation example as shown in the following discussion.
The protocol is applied to the SA bits in a G.704 E1 Multi Frame (refer Table 1). Such a Multi Frame provides a total of 40 SA bits.
The protocol operates with two types of multi frame payload: control frames and data frames.
Until the remote end has been identified the application according to the present invention should treat all incoming frames as control frames regardless of what the protocol fields indicates.
This will avoid that a link carrying random data will be able to disturb the already inverse multiplexed data stream and different protocol versions will be identified before a link can participate in the inverse multiplexing.
The protocol version described in this embodiment of the present invention document uses 20 SA bits, the other 20 SA bits may be used to extend the already defined bit fields or to define new ones.
A Multi Frame is built by collecting timeslot zero from 16 consecutive structured E1 frames as shown in
A G.704 framer or a modified G.704 framer is used for multi frame synchronisation and for extracting/inserting the inverse multiplex protocol information.
The content of the MF header is described in table 1.
To uniquely identify each SA bit for protocol purpose the bits will according to the present invention be assigned subscript numbers from SA00 to SA39. The following table is a subset of Table 1 and it shows only the bits that are defined by the protocol and their protocol naming
The following table defines the protocol fields, their meaning and their assignment to specific SA bits. The bits are listed in most significant to least significant order for multi bit fields. Bits with consecutive bit numbering may be written as SAxx-SAyy, where both SAxx and SAyy are included.
A “Data type MF” (e.g. SA00=“1”) indicates that all of the MF's body content is to be forwarded according to the low level multiplex algorithm.
The multiplexing method works on a set of active links. Active means that transmitter and receiver end are ready for data, however not necessarily in both directions at the same time.
The transmitter distributes the high-speed data on a set of data type MF. All the multi frames have the same major sequence number and the whole MF contains the same type of payload.
The MUX method will distribute the high-speed data on the multi frames in a round robin scheme using one byte fragments. The minor sequence numbers indicate the multi frame sequence order used. This is vital for correct reassembly. The minor sequence numbers does not need to be consecutive, but they must be unique. The round robin scheme start at the multi frame/link with the lowest minor sequence number and the rest of the multi frames/links follows in ascending order. The sequence wraps to the multi frame/link with the lowest minor sequence number after the link with the highest minor sequence number.
When the multi frames are filled up, the sequence is repeated at a new set of multi frames. The new set will have their major sequence number incremented by one. Note that the transmitting end should not buffer a MF but rather have the multiplexed data delivered just in time to be transmitted,
There are five links numbered as follows: 5, 3, 6, 9 and 15. The round robin sequence will then be: 3, 5, 6, 9, 15, 3, 5 and so on.
The receiver has to reassemble the data in the same order to be able to reconstruct the high-speed data.
The receiver has to compensate for transmission delay in order to get a complete set of multi frames. This means that a fast link must buffer some data while a slow link will deliver data just as they arrive.
A “Control type MF” (e.g. SA00=“0”) indicates that the MF's body carries control information and is to be processed by the logic associated with the E1 link the frame is received on.
The currently defined control information fields are listed in the table below. The bits are listed in most significant to least significant order for multi bit fields. Bits with consecutive bit numbering may be written as CFxx-CFyy where both CFxx and CFyy are included.
Multi Frame Header Vs. Multi Frame Body
To minimise the delay introduced, a MF should not be buffered for a longer time than strictly needed. This means that the early bits of a MF may already be forwarded on the high capacity link before the complete MF header has been received. To ensure that all protocol information is received completely before the corresponding MF body is being processed, the MF header contains protocol information for the subsequent MF body.
This is illustrated in
For better understanding of the protocol behaviour according to the present invention the following sections discusses state machines. The state machines could also be realized by using other internal signals in addition to the ones shown here, i.e. in the
The state machine in
The receiver starts disabled, but it tries to synchronise with possible Multi Frames arriving on the interface. When MF synchronisation is established the receiver must identify the remote end to determine if this link is to be incorporated into the inverse multiplexing traffic.
Once the link is accepted for data traffic and the link becomes enabled the data received will be made available to the block that reassembles data from several links into one data stream.
The receiver is only dependant on the enable signal and the received Multi Frames. When the receiver is ready to receive data type Multi Frames this will be reflected in the outgoing MFs (Tx:SA01).
Note that before the local receiver indicates that it is ready for data type MFs it must have used the control type MFs to synchronise the major sequence number with the other active links. The impact of not doing this is easily seen if the new link has an extra transmission delay that is more than the duration of one MF (it will arrive after the reassembling have started).
The state machine in
The transmitter is continuously sending control type MFs while it is waiting for the link to be enabled. Once the link is enabled the transmitter continues to send control type Multi Frames until the local receiver has locked to its incoming stream and the remote signals that it is willing to accept data on this link. The control type Multi Frames sent are in phase with Multi Frames sent on other links and have a major sequence number identical to the other Multi Frames. The minor number must be assigned as if the Multi Frame was carrying data (to better obtain remote synchronisation). The remote receiver will ensure that the data is suppressed from reassembling as long as the Multi Frame is a control type Multi Frame.
The protocol bit indication of whether the local receiver is ready for data type MFs or not (Tx SAO1), is supplied by the local receiver state machine.
The local receiver supplies the bit indicating whether the remote receiver is ready for data type MFs (Rx SA01). Once this bit is activated the link will start to transmit data payload.
While in the foregoing the present invention has been discussed with examples of preferred embodiments, however it should be understood that the principles as shown for the use of a number of E1 links as the lower speed data links also applies to T1 links.
G.704, G.7043, G.8080
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/NO04/00387 | 12/14/2004 | WO | 00 | 9/10/2009 |
