ZL50110/11/12/14
Data Sheet
63
Zarlink Semiconductor Inc.
shows the packet format for structured TDM data, where the payload is split into frames, and each frame
concatenated to form the packet.
5.4.1.1
Structured Payload Order
Packets are assembled sequentially, with each channel placed into the packet as it arrives at the TDM Access
Interface. A fixed order of channels is maintained (see
Figure 16), with channel 0 placed before channel 1,
which is placed before channel 2. It is this order that allows the packet to be correctly disassembled at the far
end. A context must contain only unique channel numbers. As such a context that contains the same channel
from different streams, for example channel 1 from stream 2 and channel 1 from stream 5, would not be
permitted.
Figure 16 - Channel Order for Packet Formation
Each packet contains one or more frames of TDM data, in sequential order. This groups the selected channels
for the first frame, followed by the same set of channels for the subsequent frame, and so on.
5.4.2
Unstructured Payload Operation
In unstructured mode, the payload is not split by defined frames or timeslots, so the packet consists of a continuous
stream of data. Each packet contains a programmable number of octets, as shown in
Figure 17. The number of
octets in a packet need not be an integer number of frames. A typical value for N may be 192, as defined in the
IETF PWE3 RFC. For example, consider mapping the unstructured data of a 25 timeslot DS0 stream. The data for
each T1 frame would normally consist of 193 bits, 192 data bits and 1 framing bit. If the payload consists of 24
octets it will be 1 bit short of a complete frames worth of data, if the payload consists of 25 octets it will be 7 bits over
a complete frames worth of data. NOTE: No alignment of the octets with the T1 framing structure can be assumed.
Figure 17 - ZL50110/11/12/14 Packet Format - Unstructured Mode
C h an nel 0
C h an nel 1
C han ne l 2
C h a n nel 31
Stre a m 0
C h an nel 0
C h an nel 1
C han ne l 2
C h a n nel 31
Stre am 3 1
C h an nel 0
C h an nel 1
C han ne l 2
C h a n nel 31
Stre a m 1
C h an nel 0
C h an nel 1
C han ne l 2
C h a n nel 31
Stre a m 2
C han ne l A s s e m b ly O rder
Header
N octets of data from unstructured stream
NOTE: No frame or channel alignment
may include VLAN tagging
e.g. IPv4, IPv6, MPLS
e.g. UDP, L2TP, RTP,
CESoPSN, SAToP
TDM Payload
(constructed by Payload Assembler)
46 to 1500 bytes
may also be placed in the
packet header
Octet 1
Octet 2
Octet N
Ethernet Header
Network Layers
(added by Packet Transmit)
Upper layers
(added by Protocol Engine)
Ethernet FCS
Static Padding
(if required to meet minimum payload size)