zl50118gag2 Zarlink Semiconductor, zl50118gag2 Datasheet - Page 53

• Manufacturer Part Number: zl50118gag2
• Description: 32 Channel 1 T1/e1 Cesop Processor With Single Ethernet Interface
• Manufacturer: Zarlink Semiconductor

Contexts in the TDM to PKT direction are placed in the UPDATE state when they are opened, pending the local
clock source generation. If there is no local clock source to generate packets, the context will remain in the
UPDATE state and cannot be closed. ZLAN-202 describes the procedure to close transmit contexts in the UPDATE
state.
When the payload has been assembled it is written into the centrally managed memory, and a task message is
passed to the Task Manager.
6.5.1
In structured mode a context may contain any number of 64 kbps channels. These channels need not be
contiguous and they may be selected from any input stream.
Channels may be added or deleted dynamically from a context. This feature can be used to optimize bandwidth
utilisation. Modifications to the context are synchronised with the start of a new packet.
The fixed header at the start of each packet is added by the Packet Transmit block. This consists of up to 64 bytes,
containing the Ethernet header, any upper layer protocol headers, and the two byte context descriptor field (see
section below). The header is entirely user programmable, enabling the use of any protocol.
The payload header and size must be chosen so that the overall packet size is not less than 64 bytes, the Ethernet
standard minimum packet size. Where this is likely to be the case, the header or data must be padded (as shown in
Figure 17 and Figure 19) to ensure the packet is large enough. This padding is added by the ZL5011x for most
applications.
Structured Payload Operation
Data for TDM Frame 1
Data for TDM Frame 2
Data for TDM Frame n
Figure 17 - ZL50115/16/17/18/19/20 Packet Format - Structured Mode
Header
ZL50115/16/17/18/19/20
(if required to meet minimum payload size)
Zarlink Semiconductor Inc.
(added by Packet Transmit)
(added by Protocol Engine)
Ethernet Header
Network Layers
Static Padding
Ethernet FCS
Upper layers
Channel 1
Channel 2
Channel 1
Channel 2
Channel 1
Channel 2
Channel x
Channel x
Channel x
53
may include VLAN tagging
e.g. IPv4, IPv6, MPLS
e.g. UDP, L2TP, RTP,
TDM Payload
(constructed by Payload Assembler)
may also be placed in the
packet header
CESoPSN, SAToP
Data Sheet