Technical data

TraverseEdge 2020 Applications and Engineering Guide, Chapter 3: System Applications
Page 3-72 Turin Networks Release 5.0.x
The TE-2020 supports transparent Section DCC as well as transparent K1 and K2 byte passthrough.
Although these can be used in conjunction, it is not a required operation. Furthermore, the overhead trans-
parency does not need to be tied to a user traffic connection. This connection type is specific to transparent
overhead passthrough and is made independently of traffic connections.
Transparent Overhead Connection Creation
The transparent overhead connections can be made by the user to send proprietary management messages
through the TE-2020 system which functions as a pipe that blindly sends the information to the other end.
No interpretation or reaction to the transparent data is attempted or supported. Transparent overhead con-
nections can only be performed on a per STS basis. The connection is always bi-directional.
The user is able to select any STS from the first 48 STSs in a facility for transparent overhead passthrough
to be used for the transparent overhead connection. These connections can only be made on the TE-2020
Main Shelf. If the user needs to use multiple STSs on the same facility for transparent overhead
passthrough, separate connections will need to be made for each STS. Note that the first STS of each ring
interface is reserer for Turin Networks product use.
K1/K2 Switching Bytes
The number of transparent K1/K2 byte connections per PLM type is 32 max. The number of transparent
K1/K2 byte connections per facility type is defined in Table 3-25 . The TE-2020 Main Shelf supports up to
40 transparent DCC connections and 40 K1/K2 transparent connections.
Table 3-25 Transparent K1/K2 per Facility
The TE-2020 supports Add/Drop, Through, and Hairpin transparent overhead connections. The parameters
for making the transparent overhead connection will be similar to those used for user traffic connections.
Only explicit connections are supported in this release, routed connections may be supported in a future
release. A connection identifier will allow the user to uniquely identify each transparent overhead connec-
tion in their network. The user will need to supply the following parameters for a transparent overhead
connection:
• Ingress/Egress (receive/transmit) facility
• Ingress/Egress (receive/transmit) timeslot
• Overhead selection
• Final Service State: OOS-MA or IS
• Connection Identifier of no more than 20 characters
The user can edit the following fields in a transparent overhead connection:
Facility Type Number of Transparent DCC Connections
OC-192 32
OC48 16
OC-12 4
OC-3 1