01-02 TDMoPSN

Quidway CX200/300 Metro Services Platforms Feature Description - Services
Contents
Contents
2 TDMoPSN ...................................................................................................................................2-1
2.1 TDM Overview .............................................................................................................................................2-2 2.1.1 TDM Technology .................................................................................................................................2-2 2.1.2 Digital Carrier System .........................................................................................................................2-3 2.1.3 Channelization Technology and Unchannelization Technology ..........................................................2-4 2.1.4 Circuit Switching Technology..............................................................................................................2-5 2.1.5 Typical Application of Circuit Switching.............................................................................................2-5 2.2 PSN Overview...............................................................................................................................................2-6 2.2.1 Packet Switching Technology ..............................................................................................................2-6 2.2.2 Virtual Circuit Technology...................................................................................................................2-6 2.2.3 Typical Application of Packet Switching .............................................................................................2-7 2.3 Principle of TDMoPSN.................................................................................................................................2-8 2.3.1 TDMoPSN Circuit Emulation..............................................................................................................2-8 2.3.2 PWE3 Transmission Mechanism .........................................................................................................2-9 2.3.3 Establishement of a PW .....................................................................................................................2-10 2.3.4 Encapsulation and Forwarding of TDM Data Flows .........................................................................2-13 2.3.5 Format of a TDMoPSN Packet ..........................................................................................................2-15 2.3.6 Calculation of TDM Frames and the Bandwidth ...............................................................................2-18 2.4 Clock Synchronization ................................................................................................................................2-23 2.4.1 Concept and Function of Clock Synchronization...............................................................................2-24 2.4.2 Adaptive Clock...................................................................................................................................2-26 2.4.3 Synchronization Ethernet Clock ........................................................................................................2-26 2.5 Characteristics of TDMoPSN Implemented on the CX ..............................................................................2-29 2.5.1 Data Jitter Buffer................................................................................................................................2-29 2.5.2 Analysis on Latency of Data Packet...................................................................................................2-30 2.5.3 OAM Supported by TDM ..................................................................................................................2-30 2.6 Application of TDMoPSN on the CX .........................................................................................................2-31 2.6.1 PSN Bearing GSM Wireless Access Services....................................................................................2-31 2.6.2 PSN Bearing R99/R4 WCDMA Wireless Access Services................................................................2-32 2.6.3 PSN Bearing R5 WCDMA Wireless Access Services .......................................................................2-33 2.6.4 PSN Bearing Traditional Services......................................................................................................2-34 2.6.5 MPLS OAM Supported by TDM.......................................................................................................2-34
Issue 01 (2008-01-15)
Huawei Technologies Proprietary
Contents
2.7 References ...................................................................................................................................................2-35
ii
Issue 01 (2008-01-15)
Figures
Figures
Figure 2-1 Principle of the TDM technology .....................................................................................................2-2 Figure 2-2 Relationship between frames and TSs in TDM ................................................................................2-3 Figure 2-3 TS classification for E1/T1 frames ...................................................................................................2-4 Figure 2-4 Framework of a PWE3 network .....................................................................................................2-10 Figure 2-5 Setting up and maintaining the single-hop PW............................................................................... 2-11 Figure 2-6 Withdrawing a single-hop PW ........................................................................................................2-12 Figure 2-7 Encapsulation position and structure of a PWE3 label ...................................................................2-13 Figure 2-8 Encapsulation and forwarding of 2G/3G wireless services ............................................................2-14 Figure 2-9 Encapsulation and forwarding of traditional data flows .................................................................2-15 Figure 2-10 Format of a CESoPSN packet.......................................................................................................2-16 Figure 2-11 Format of an SAToP packet...........................................................................................................2-17 Figure 2-12 Networking diagram for the conversion of TDM data into frames at the network side................2-18 Figure 2-13 Clock synchronization hierarchy ..................................................................................................2-24 Figure 2-14 Principle of the recovery algorithm of the adaptive clock ............................................................2-26 Figure 2-15 Clock synchronization mechanism ...............................................................................................2-27 Figure 2-16 Clock extraction and selection ......................................................................................................2-28 Figure 2-17 Influence of phase lock on the transmission of the clock signal...................................................2-29 Figure 2-18 PSN bearing GSM wireless access services .................................................................................2-31 Figure 2-19 PSN bearing R99/R4 WCDMA wireless access services .............................................................2-32 Figure 2-20 PSN bearing R5 WCDMA wireless access services .....................................................................2-33 Figure 2-21 PSN bearing traditional services...................................................................................................2-34 Figure 2-22 MPLS OAM supported by TDM ..................................................................................................2-35
Issue 01 (2008-01-15)
iii
2 TDMoPSN
2
About This Chapter
The following table shows the contents of this chapter. Section 2.1 TDM Overview Description
TDMoPSN
This section describes the TDM technology, E1/T1 digital carrier system, channelized technology and unchannelized technology, and circuit switching technology. This section describes the packet switching technology and the virtual circuit technology. This section describes the background of TDMoPSN, basic concepts and network framework of PWE3, encapsulation and forwarding of TDM data flow, and format of a TDMoPSN packet. This section describes the concept and role of clock synchronization, and the principle for the adaptive clock and the synchronization Ethernet clock. This section describes the TDMoPSN features supported by the CX, such as data jitter buffer and analysis for the delay of data packets. This section describes the typical networking for the PSN that bears 2G, 3G, and traditional services. This section lists the references for TDMoPSN.
2.2 PSN Overview 2.3 Principle of TDMoPSN
2.4 Clock Synchronization
2.5 Characteristics of TDMoPSN Implemented on the CX 2.6 Application of TDMoPSN on the CX 2.7 References
Issue 01 (2008-01-15)
2-1
2 TDMoPSN
2.1 TDM Overview

2.1.1 TDM Technology
Introduction to TDM
Multiplexing is a process of combining multiple input signals for transmission on the same link. That is, there are multiple logical channels on a link. Time Division Multiplexing (TDM) is a technology through which different pulses are transmitted on the same link based on preassigned Timeslots (TSs) , as shown in Figure 2-1. Figure 2-1 Principle of the TDM technology
n inputs
1 link, n channels MUX DEMUX
n outputs
channel 1 channel 2 channel 3 channel n
Signals from multiple channels are input into the Multiplexer (MUX) . The MUX allocates TS resources for different input signals and transmits a certain input signal at a specified timeslot. The input signals reach the Demultiplexer (DEMUX) at different times. The DEMUX extracts signals from different TSs and outputs signals into multiple links to transmit more than one multiplexed signal on the same link.
Relationship Between Frames and TSs in TDM

TDM allocates different TSs to different channels. Each TS carries one channel of signals. A number of TSs form a frame. Each frame transmits signals from different channels based on the preassigned TSs, as shown in Figure 2-2.
2-2
Issue 01 (2008-01-15)
2 TDMoPSN
Figure 2-2 Relationship between frames and TSs in TDM

n TSs in one frame 8000 frame/second F1 F2 F3
TS1 TS2 TS3 TS1 TS2 TS3 TS1 TS2 TS3 TSi TSi TSi TSn-1 TSn TSn-1 TSn TSn-1 TSn
F7999 TS1 TS2 TS3 F8000 TS1 TS2 TS3
TSi TSi
TSn-1 TSn TSn-1 TSn
The first timeslot TS1 transmits a signal from the first channel. The second timeslot TS2 transmits a signal from the second channel. The rest may be deduced by analogy. The combination of these signals forms a frame. The next frame transmits signals from different channels also based on the preassigned TSs. Frames are arranged in order so that each channel can transmit signals independently.
2.1.2 Digital Carrier System

Current digital transmission systems adopt Pulse Code Modulation (PCM) . PCM was initially designed to enable more than one voice signal to be transmitted over a trunk between telephone exchanges through the TDM technology. The bandwidth of each voice signal is 64 kbit/s in a traditional telephone system. Such a signal is taken as a timeslot. As for the PCM mechanism, there are two international standards that are not compatible with each other.
E-Carrier
E-carrier is a digital communications system recommended by the International Telecommunication Union-Telecommunication Standardization Sector (ITU-T). This standard starts from E1. As shown in Figure 2-3, E1 provides 30B+D, including 32 TSs from TS0 to TS31. B indicates a circuit channel. D indicates a signaling channel. E1 provides 30 TDM service TSs, one signaling TS, and one frame synchronization TS. TS0 is used to transmit frame synchronization information. TS16 is used to transmit signaling or services. Other TSs are used to transmit services. The E1 works at 2.048 Mbit/s. At present, this standard mainly applies to Europe and China.
T-Carrier
The American National Standards Institute (ANSI) defines the T-carrier system in the T1.107 standard. This standard starts from T1.
Issue 01 (2008-01-15)
2-3
2 TDMoPSN
As shown in Figure 2-3, T1 provides 23B+D, including 24 TSs from TS1 to TS24. T1 provides 23 PCM TSs and one signaling TS. T1 adopts one bit to transmit frame synchronization information. The signaling TS can also be omitted. Other TSs are used to transmit services. The T1 works at 1.544 Mbit/s. At present, this standard mainly applies to North America. The Japanese J1 standard is similar to T1 and can also be classified into the T-carrier hierarchy. Figure 2-3 TS classification for E1/T1 frames
1 frame = 256 bits:125us TS0 E1 TS1 TS2 TS31
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
1 frame = 193 bits:125us TS1 T1 TS2 TS24
F 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
The sampling frequency of PCM is 8000 Hz. Each E1 frame contains 32 TSs. Each T1 frame contains 24 TSs and one bit is used for synchronization. Each TS is encoded in 8 bits. Thus, E1 interface bandwidth = 32 x 8 x 8000 = 2.048 Mbit/s T1 interface bandwidth = (24 x 8 + 1) x 8000 = 1.544 Mbit/s There are many differences on protocols between E-carrier and T-carrier. For example, TS0 in E1 is used for clock synchronization, whereas in T1 only the frame synchronization bit F is used for clock synchronization. The basic features of E-carrier and T-carrier are roughly the same.
2.1.3 Channelization Technology and Unchannelization Technology

There are two operation modes for the E1/T1 interface (referred to as the TDM interface in this document).
Channelization Technology
Channelized operation means that the TDM data flow is transmitted in frames and the MUX and DEMUX devices need to identify, encapsulate and decapsulate TDM frames, and transmit synchronization information in frames. The header of a TDM frame is identified by the frame delimiter. For example, an E1 frame must begin with TS0. TSs are used as the smallest units for resource allocation in channelized mode. This technology identifies available TSs and the idle TSs of an E1/T1 circuit, and encapsulates only the TSs that are being used into PW packets for transmission. The idle TSs are discarded . This saves network bandwidth and improves resource utilization.
2-4
Issue 01 (2008-01-15)
2 TDMoPSN
The channelized or structured mode can improve bandwidth utilization and save network bandwidth. The implementation of channelized TDM is complex because the following information should be identified and processed: Framing sign of the TDM data flow Timeslots of the frames Signaling information carried in certain timeslots
Unchannelization Technology
The unchannelized mode does not require clock synchronization. The data format in the TDM data flow is not identified and TDM data is processed as serial code streams. As for E1 interfaces, a payload unit contains 32 bytes based on the unchannelized protocol. Although the E1 frame structure is not identified, the TDM data flow is divided on the basis of the integral number of times the length of an E1 frame. As for T1 interfaces, a payload unit contains 24 bytes based on the unchannelized protocol. The TDM data flow is divided based on the integral number of times the length of a T1 frame. The unchannelized mode is simple, and the data format of TDM service flow need not be identified. Therefore, the unchannelization technology can be widely used. E1/T1 interfaces function as synchronous serial interfaces in traditional data networks, that is, the format of the frame is ignored.
2.1.4 Circuit Switching Technology

Because the TDM technology utilizes circuit switching for communications, the TDM data flow is continuously transmitted through the switching of TSs. Data need not be stored before being forwarded by each device on the network. Traditionally, communications connections are set up and sufficient resources are pre-reserved before two ends transmit the TDM data flow. The connections break when the communications end and the resources are released. Because sufficient resources are pre-reserved, the circuit switching technology features short delay and low jitter, and is thus applicable to stable transmission. The TDM technology adopts the Synchronous Transfer Mode (STM) to transmit services. In STM, information is transmitted on each link in the format of frames. The frame is generated periodically. Each frame is divided into multiple TSs with a fixed length. When the connection is set up, the Quality of Service (QoS) of this connection is not affected by other users on the network. STM supports only certain data services at specified rates. In addition, channel resources are allocated on the basis of the peak bit ratio to guarantee the bandwidth of connections. Therefore, the TDM service is accessed and borne by leased lines. TS resources are occupied before the break of connections and cannot be used for the transmission of other data flows. The bandwidth is not used to the maximum extent and the cost is high. The transmission rate is fixed for circuit switching, which cannot meet the requirement of traffic bursts.
2.1.5 Typical Application of Circuit Switching

PSTN Telephone Communications
In the Public Switched Telephone Network (PSTN), the Stored Program Control (SPC) switches in local offices, central offices, and toll offices are connected to each other through E1/T1 cables. End-to-end connections are set up between users through circuit switching for voice communications.
Issue 01 (2008-01-15)
2-5
2 TDMoPSN
RAN Wireless Access Communications

The Radio Access Network (RAN) is classified into the Second Generation (2G) access mode and the Third Generation (3G) wireless access mode. wireless
The 2G is the Global System for Mobile Communications (GSM) digital cellular communication system and mainly bears voice services. Circuit connections are set up between the Base Transceiver Station (BTS) and the Base Station Controller (BSC) through E1/T1 cables. The 3G is based on the Code Division Multiple Access (CDMA) technology and bears voice and broadband services. Now, the 3G has three standards, WCDMA, CDMA2000, and TDCDMA. The chapter takes WCDMA as an example to illustrate the 3G technology. WCDMA supports R99, R4, and R5 released versions. R99 is the first complete 3G or Universal Mobile Telecommunications System (UMTS) system. Based on all services and functions of R99, R4 provides an independent service system by separating the service module from the call control and the call control from the bearer. Based on all services and functions of R4, R5 provides the all-IP network and capabilities of IP RAN access and enhanced IP QoS. In R99 and R4, circuit connections are set up between Node B and the Radio Network Controller (RNC) through E1/T1 cables. In R5, circuit connections are set up between Node B and the RNC through FE/GE interfaces.
2.2 PSN Overview

2.2.1 Packet Switching Technology
Packet Switched Networks (PSNs) mainly apply to data communications. Each device divides service flows into packets based on a certain length. This process is called packeting. Each packet has its own addressing information.Devices on the network perform routing for each packet. Packets are segmented and reassembled. This can improve utilization of the link bandwidth. Because the packet switching technology provides the store-and-forward mechanism, it is suitable for the transmission at different input/output rates. At present, the PSN technology is widely applied. However, setting up connections and reserving resources are not required for the PSN technology. Congestions may easily occur to networks. Because routing is performed for each packet and PSNs adopt the store-and-forward mechanism, packet loss and disorder may easily occur during transmission, which greatly affects the reliability of packet transmission.
2.2.2 Virtual Circuit Technology

A Virtual Circuit (VC) is a logical circuit connection between two network devices. VC combines the advantages of circuit switching and packet switching, using the packets to bear TDM services. Connections are set up and resources are reserved before communications to ensure bandwidth and service quality during transmission. Devices on the network divide data flow into several packets and perform routing for each packet before forwarding it. The VC is classified into the following types according to its establishment:
2-6
Issue 01 (2008-01-15)
2 TDMoPSN
Switched Virtual Circuit (SVC): It is a virtual circuit that is automatically created and deleted after triggered by the protocol. When data is transmitted, a connection (that is, VC) is set up between devices through the communications protocol. The VC is disconnected after the communication is over. Permanent Virtual Circuit (PVC) It is a virtual circuit that is manually configured. Within the period defined in the contract, PVCs are manually set up between devices to provide resources for later communications. Before and after actual data transmission, call setup and call disconnect programs are not required. Virtual circuit switching has the following advantages: Possessing multiple logical channels to ensure high circuit utilization of trunks Implementing interworking between terminals of different codes, speeds, and specifications on the PSN Detecting and correcting errors to ensure minimal error codes in circuit transmission
2.2.3 Typical Application of Packet Switching

ATM Communications
Asynchronous Transfer Mode (ATM) uses cells for exchange of information. It is a new connection-oriented technology that features fast packet switching, combining the advantages of packet switching and circuit switching, and utilizing fast switching of fixed-length cells into which the information flow is divided. ATM uses VCs to carry out cell transmission. Each VC is identified by the Virtual Path identifier (VPI) and Virtual Channel Identifier (VCI) . ATM uses statistical TDM to use channel resources dynamically. In this manner, the channel utilization is high. The output channel is occupied so long as the input cell flow continues. The Inverse Multiplexing over ATM (IMA) technology can carry out the ATM services on multiple E1/T1 links to save expensive E3/T3 lines.
FR Communications
Frame Relay (FR) works on the physical layer and the data link layer in the Open Systems Interconnection (OSI) model and adopts the connection-oriented switching technology. FR provides SVC and PVC services through the VC technology. Data is transmitted in the format of frames. FR can set up multiple logical connections on a physical link and carry out the multiplexing and dynamic allocation of bandwidths. FR simplifies the third layer function of X.25. The processing of information is simplified for the nodes on the network, which improves the efficiency of the network. The link protocol carries out statistical multiplexing, transparent transmission of frames, and error detection. This increases the network throughput and reduces the delay of transmission.
MPLS Communications
Multiprotocol Label Switching (MPLS) uses short fixed-length labels to encapsulate IP packets and carry out fast label forwarding on the data plane. On the control plane, MPLS
Issue 01 (2008-01-15)
2-7
2 TDMoPSN
utilizes strong and flexible routing functions of the IP network to meet the requirements of new applications on the network.
2.3 Principle of TDMoPSN

2.3.1 TDMoPSN Circuit Emulation
Background
With the IP orientation of core networks and popularization of the Ethernet technology adopted by access-layer devices, the Ethernet plus IP solution is more appealing to customers than traditional service access and bearing solutions in terms of costs and resource utilization. The existing Plesiochronous Digital Hierarchy (PDH) /Synchronous Digital Hierarchy (SDH) networks that transmit TDM services exist for a long time. This is because they transmit voice services with high quality and synchronous services with high precision. Service Providers (SPs) needs to transmit various types of services to obtain the maximum returns and the minimum operation expenditure. This technology is also called network integration or all-IP solution. Therefore, to benefit both SPs and users, the access and bearing of TDM services need be migrated into packet networks.
TDMoPSN Circuit Emulation Technology

The circuit emulation technology originates from the ATM network. Circuit-switched service data is encapsulated into ATM cells through the technologies such as VC before being transmitted on the ATM network. Circuit emulation is a mechanism that is used to transparently transmit circuit-switched services on the network. A special circuit emulation header is encapsulated for TDM frames. In addition, the clock signal can be transmitted on the PSN through a certain mechanism. The component on the physical layer that implements encapsulation is called a framer or mapper. This component can be directly connected to the existing TDM network. Based on the design of the circuit emulation technology, the TDM over PSN (TDMoPSN) is applied accordingly. TDMoPSN is a technology that uses the TDM circuit emulation technology to bind timeslots (TSs) into packets to transmit TDM services across the PSN. For TDM circuit emulation, the physical transmission mode of TDM is emulated. Identifying services transmitted on E1/T1 links is not required so that services are transparently transmitted. A Pseudo Wire (PW) is set up between two devices in the PSN. The PW is set up over the MPLS tunnel and sends packets from the source Provider Edge (PE) to one or multiple destination PEs. For more information about MPLS, refer to chapter "MPLS LDP" in the Quidway CX200/300 Metro Services Platforms Feature Description - MPLS.
Advantages of TDMoPSN
TDMoPSN has the following advantages: Supports clock synchronization in adaptive clock mode and synchronization Ethernet mode on the Ethernet. Uses the E1/T1 leased line only on the Attachment Circuit (AC). The bearer network is the PSN, and thus greatly reduces the operation cost.
2-8
Issue 01 (2008-01-15)
2 TDMoPSN
Uses the MPLS technology and the Pseudo Wire Emulation Edge-to-Edge (PWE3) technology to transparently transmit and rapidly exchange user datagrams.
2.3.2 PWE3 Transmission Mechanism

PWE3 Overview
With the development of the IP network, expandability, upgradeability, and compatibility of the IP network are very strong. Due to transmission modes and service types, the upgrade, expansion, and interworking of the traditional communication network is low. In addition, the sharing among new networks is low and is not suitable for interworking management. Therefore, during the upgrade and expansion of the traditional communication network, constructing a repeated network or making full use of the existing public network resources should be considered . PWE3 is a solution that combines the traditional communications network with the existing PSN. PWE3 is a Layer 2 service bearing technology. It mainly applies to the PSN to emulate the basic actions and characteristics of TDM circuit, ATM, FR, Ethernet service, Synchronous Optical Network (SONET) service, and SDH service. PWE3 combines the traditional TDM network with the PSN to share resources and expand the network.
Basic Concepts
CE Customer Edge (CE) refers to the device that starts or ends the services. A CE cannot and need not distinguish whether the running services are simulated or local. PE Provider Edge (PE) refers to the device that provides transmission mechanism for PWE3 tunnels. It is usually connected to a CE on a backbone network to access VPN services. During the process, a PE performs the mapping and forwarding of packets from the private network to the public tunnel and then from the public tunnel to the private network. PW PW refers to a mechanism that bears the simulated services between PEs on the PSN. AC Attachment circuit (AC) refers to the physical or virtual circuit that connects a CE and a PE. The ATM VPI/VCI, Ethernet interface, VLAN, and MPLS LSP can function as ACs. Forwarder The forwarder at the local end is a PE sub-system that selects a PW to transmit the payload received from the AC. The forwarder at the peer end receives the payload from the specified PW and transfers the payload to the AC. Tunnels The tunnel technology refers to a mechanism that transparently transmits data on the network. For example, tunnels can be used to bear PW. Therefore, a tunnel is a directlyconnected channel between the local PE and the remote PE, and transparently transmits data between the PEs. One tunnel can bear multiple PWs, which is the MPLS tunnel. Encapsulation
Issue 01 (2008-01-15)
2-9
2 TDMoPSN
Packets transmitted through PWs use the standard PW encapsulation format and encapsulation/decapsulation technology.
Framework of a PWE3 Network

Figure 2-4 shows the transmission components of a PWE3 network. Figure 2-4 Framework of a PWE3 network
AC PW AC
Forwarder
Forwarder
BTS/ NodeB ATM /PSTN /FR Forwarder
MPLS network
BSC/ RNC ATM /PSTN /FR
Forwarder
MPLS tunnel
PW
As shown in Figure 2-4, forwarder nodes function as PEs. The BTS or Node B at the user side functions as a CE to access a PE through the AC. The BTS or Node B at the network side functions as a CE to access a PE through the AC. ACs are usually E1/T1 leased lines. In the MPLS network, the CXs communicate with each other through the MPLS protocol. PWs are set up between forwarders. At the edge of the MPLS network, forwarders transmit TDM data flows to one of the CEs by selecting a PW label.
2.3.3 Establishement of a PW
Classification of a PW
PWE3 is an end-to-end Layer 2 VPN technology. According to the establishment modes of the PW, PWs are classified into static PWs and dynamic PWs. Among them, dynamic PWE3 is the extension of the Martini protocol and the signaling process is the same as the static one. Static PWs The static PWs negotiate parameters without using the signaling protocol. Instead, the command is used to manually specify related information and data is transmitted between PEs through tunnels. Dynamic PWs The dynamic PWs refer to the PWs that are set up through the signaling protocol. The PEs switch VC labels through the Link Distribution Protocol (LDP) and are bound to
2-10
Issue 01 (2008-01-15)
2 TDMoPSN
CEs through VC-IDs. When the tunnel that connects two PEs is set up, and switching and binding of labels are complete, a VC is set up, if the AC of these two PEs is Up. The messages of dynamic PWs contain the following:

Request: used to request the peer for allocating labels. Mapping: used to notify the remote PE of the local labels. It can choose to carry the status field according to the default signaling. By default, the Martini mode does not support the status field. Notification: used to notify and negotiate the PW status and reduce the number of transmitted messages. Withdraw: used to carry the label and status for notifying the peer of withdrawing labels. Release: used to notify the peer that sends withdraw messages of withdrawing labels as the response message of the withdraw message.
PWE3 negotiates the PW status based on the Notification message and withdraws the label based on the Withdraw message. Both ends negotiate to determine the mode when a PW is set up between them. If the Notification message is used, the number of transmitted packets is reduced when the network is unstable.
Setting Up and Maintaining a PW

When using LDP as the signaling protocol, PWs carry the VC information by extending the TLV of standard LDP. In the extended TLV, Types 128 and 129 Forwarding Equivalence Class Type-Length-Values (FEC TLVs) are added. When PWs are set up, the Downstream Unsolicited (DU) label distribution mode and the liberal label retention mode are adopted. LDP sessions need to be created between PEs. If a P exists between PEs, the LDP session is created in remote mode between PEs. If the PEs are directly connected, an ordinary LDP session is created. At present, the CX supports the single-hop PW, that is, there is one PW between PEs and label switching is not required. Figure 2-5 shows how the single-hop PW is set up and maintained. Figure 2-5 Setting up and maintaining the single-hop PW
1.1.1.1/32 MPLS network PE1 mpls l2vc 2.2.2.2 101 Request Mapping Mapping parameter match, VC up Notification AC/Tunnel state changed AC/Tunnel state changed mpls l2vc 1.1.1.1 101 parameter match, VC up PE2 2.2.2.2/32
A VC is configured on PE1 and PE2 is specified as the peer of PE1. A VC is also configured on PE2 and PE1 is specified as the peer of PE2. Dynamic PW labels are allocated at inbound and outbound interfaces.
Issue 01 (2008-01-15)
2-11
2 TDMoPSN
Take Figure 2-5 as an example. The messages are transmitted as follows: 1. 2. 3. If an LDP session is already set up between PE1 and PE2, PE1 sends a Request message to PE2. Otherwise, the LDP session is set up first. PE1 determines the VC label and notifies PE2 through a Mapping message. PE2 receives the Request and Mapping messages sent from PE1. If the PW on PE2 is the same as that on PE1, PE2 sets the VC to UP after processing the message received from PE1 and sends Mapping messages to PE1. After receiving the Mapping message, PE2 checks whether the local end is configured with the same VC. If the VC is configured and the VC ID and VC-Type are the same, it indicates that the VCs on the two PEs belong to one VPN. In addition, if parameters on the interfaces are the same, it indicates that the VC is set up on PE2. 4. PE1 receives the Mapping message of PE2 and sets the VC to Up after the system processing. A dynamic PW between PE1 and PE2 is thus set up. After receiving the Mapping message, PE1 checks the VC ID, VC-Type, and interface parameters in the message. If they are the same on both ends, the VC is also set up on PE1. A PW that consists of two bidirectional VCs is set up between PE1 and PE2. 5. After the PW is set up, PE1 and PE2 send Notification messages to learn the status of each other.
In PWE3 mode, however, a Notification message is sent to notify the peer that packets cannot be forwarded. The PW is not withdrawn. When the AC or the tunnel becomes Up, a Notification message is sent to notify the peer that packets can be forwarded.
Withdrawing a PW
Figure 2-6 shows how the dynamic PW is removed between PE1 and PE2 and how messages are transmitted. Figure 2-6 Withdrawing a single-hop PW
1.1.1.1/32 MPLS network PE1 mpls l2vc 2.2.2.2 101 Session Down Withdraw Release Session Down Release Delete PW Delete PW PE2 mpls l2vc 1.1.1.1 101 2.2.2.2/32
Take Figure 2-6 as an example. The messages are transmitted as follows: 1. 2. 3. When PE1 detects that the AC or the tunnel becomes Down or the VC is deleted, it sets the VC to Down and sends a Withdraw message to PE2. PE1 sends a Release message to PE2. After receiving the Withdraw and Release messages from PE1, PE2 sets the VC to Down and processes the Withdraw message, and then sends a Release message to PE1.
2-12
Issue 01 (2008-01-15)
2 TDMoPSN
4.
The PW between PE1 and PE2 is deleted.
When PE1 does not forward packets sent from PE2, for example, PE2 is not specified as the peer, it sends a Withdraw message to PE2. After PE2 receives the Withdraw message, it withdraws the PW and responds to a Release message. After receiving the Release message, PE1 releases the label and withdraw the PW.
2.3.4 Encapsulation and Forwarding of TDM Data Flows

Encapsulation Position and Structure of the Label
When TDM services are emulated through PWE3, the following should be emulated: Frame format Alarm Signaling Synchronous timing The implementation of emulated services of TDM circuit is to encapsulate the TDM service with a special packet header of the emulated circuit. The encapsulated packet is called the PW packet. The PW packet is then carried to traverse the PSN through MPLS. After reaching the remote end, the PW packet is decapsulated. The TDM flow is reestablished. Figure 2-7 shows the encapsulation position and structure of a PWE3 packet header in a packet. Figure 2-7 Encapsulation position and structure of a PWE3 label
Ethernet header MPLS header PW header TDM Data
0 MPLS Label PW Label
20 EXP EXP
23 S 1 TTL TTL
31
A PWE3 frame header consists of the following fields: PW Label: It refers to the field of label value. It is 20 bits long and is used as the basis of label forwarding. EXP: It is 3 bits long and is used to map the user priority level of QoS scheduling. S: It refers to the mark of stack bottom and is 1 bit long. MPLS supports multiple labels; therefore, the stack bottom should be marked. The value of 1 indicates the bottom label. The S field of PW is 1. TTL: It is the same as Time To Live (TTL) in IP packet and is 8 bits long. For more information about MPLS, refer to the chapter "MPLS LDP" in the Quidway CX200/300 Metro Services Platforms Feature Description - MPLS.
Encapsulation and Forwarding of 2G/3G Wireless Services

Figure 2-8 shows the encapsulation and forwarding of 2G/3G wireless data flows on the TDMoPSN network.
Issue 01 (2008-01-15)
2-13
2 TDMoPSN
Figure 2-8 Encapsulation and forwarding of 2G/3G wireless services
Forwarder E1/T1
MPLS network E1/T1 Forwarder BSC /RNC
BTS /NodeB
TDM
PW
PDU
M'
PW
PDU
TDM
MPLS tunnel
PW
As shown in Figure 2-8, TDM indicates 2G/3G wireless access service frames. Protocol Data Unit (PDU) indicates the initial packets for the emulated TDM service. PW indicates a PWE3 frame header. M and M' indicate MPLS frame headers. ACs are TDM circuits that can be E1 or T1 leased lines. Node B sends the data flow in the TDM format. One frame contains multiple TSs. The local forwarder receives the TDM TSs and binds them into packets. The packets are encapsulated with two-layer labels. The inner label is used to identify PW. The outer label is used to identify the MPLS tunnel. Then, the local forwarder transmits the packets to the next CX in the PSN. After receiving the packets, the transit node forwards the packets based only on the outer label, and does not interpret the inner label. After receiving the packets, the remote forwarder strips off the two-layer labels and decapsulates the packets, reconstructs the TDM flow, and forwards the flow to BSC or RNC.
Encapsulation and Forwarding of Traditional Services

Figure 2-9 shows the encapsulation and forwarding of traditional ATM, PSTN, and FR data flows on the TDMoPSN network.
2-14
Issue 01 (2008-01-15)
2 TDMoPSN
Figure 2-9 Encapsulation and forwarding of traditional data flows
ATM1
Forwarder E1/T1
MPLS network
Forwarder E1/T1
FR2
FR1
E1/T1 Forwarder
E1/T1 Forwarder
ATM2
FR ATM M PW PDU M' PW PDU
FR ATM
MPLS tunnel
PW
As shown in Figure 2-9, ATM indicates ATM service frames. FR indicates FR service frames. PDU indicates the initial packets for the emulated service. PW indicates a PWE3 frame header. M and M' indicate MPLS frame headers. Take the data flow from ATM1 to ATM2 as an example to illustrate the encapsulation and forwarding of traditional services: ACs are TDM circuits that can be E1 or T1 leased lines. The ATM, PSTN and FR network send the data flow in the TDM format. One frame contains multiple TSs. The local forwarder receives the TDM TSs and binds them to packets. The packets are encapsulated with two-layer labels. The outer label is used to identify PW. The inner label is used to identify the MPLS tunnel. Then, the local forwarder forwards the packets to the next node. After receiving the packets, the transit node forwards the packets based only on the outer label, and does not resolute the inner label. After receiving the packets, the remote forwarder strips off the two-layer labels and decapsulates the packets, reconstructs the TDM flow, and forwards the flow to the receiver.
2.3.5 Format of a TDMoPSN Packet

TDMoPSN has two formats of packets for channelized and unchannelized modes.
Format of a CESoPSN Packet

The Circuit Emulation Services over PSN (CESoPSN) standard provides the emulation for the transmission of channelized TDM services, that is, TDM frame structure and signaling in the frame can be identified.
Issue 01 (2008-01-15)
2-15
2 TDMoPSN
At present, the CX supports the construction of CESoPSN packets in MPLS mode. Figure 210 shows the format of a CESoPSN packet. Figure 2-10 Format of a CESoPSN packet
0 MPLS Label PW Label 0 0 0 0 L R RSV FRG LEN 20 EXP EXP 23 S 1 TTL TTL 31
Sequence Number
RTP header
Time slot 1 Time slot 5
Time slot 2
Time slot 3
Time slot 4
Time slot n (Frame 1#) Time slot 2 Time slot 3 Time slot 4
Time slot 1 Time slot 5
Time slot n (Frame 2#)
Time slot n (Frame m#)
A CESoPSN packet contains a 4-byte MPLS frame header and a 4-byte PW frame header, which have been described in "Encapsulation Position and Structure of the Label." The control word of a CESoPSN packet is of 4 bytes and contains the following fields: 0000: It is of 4 bits long and usually set to all 0s. When Virtual Circuit Connectivity Verification (VCCV) is used to monitor the status of the PW based on the Structure Agnostic TDM over PSN (SAToP) protocol, the four bits are used to identify the start of an Associated Channel Header (ACH). L: It indicates whether the TDM data in the packet is invalid. It is 1 bit long. If the value is 1, it indicates that the TDM data in the packet is invalid. That is, the TDM data in the packet is ignored to save bandwidth resources. R: It indicates whether the packets are lost on the CE side of the local end. If the value is 0, it indicates that continuous packets are received and packets are no longer lost. RSV: It is 2 bits long. The bits are reserved. FRG: It indicates the fragmentation status of packets. It is 2 bits long and has four values:

00: It indicates that this packet is encapsulated with the whole TDM data. 01: It indicates that this packet is encapsulated with the first fragment of the TDM data. 10: It indicates that this packet is encapsulated with the last fragment of the TDM data. 11: It indicates that this packet is encapsulated with the middle fragments of the TDM data.
2-16
Issue 01 (2008-01-15)
2 TDMoPSN
LEN: It indicates the length of a whole CESoPSN packet (including the CESoPSN packet header and TDM data). When the packet length is less than 64 bytes, LEN indicates the actual length of the packet. Otherwise, the value is 0. Sequence Number: It indicates the sequence number of the transmitted CESoPSN packet. It is 16 bits long. The initial value is generated randomly. This value is increased by one when one packet is transmitted. The Real-time Transport Protocol (RTP) header is 12 bytes long, including the version number, Padding flag, and Timestamp field. At present, the CX uses only the Timestamp field. Other fields are reserved for later expansion. The Timestamp field is 32 bits long and is used for clock synchronization. For the format of the RTP header, refer to RFC 3550. Time slot n indicates a TS in TDM frames. Each TS uses 8 bits. All TSs constitute the encapsulated TDM data payload, excluding the Cyclic Redundancy Check (CRC) bit. The number of encapsulated frames and the number of TSs in each frame can be configured as required. The CESoPSN protocol identifies the TDM frame structure. Idle TSs are not transmitted. The TSs that are used to transmit TDM services are extracted from E1/T1 circuits and encapsulated into PW packets before being sent to the remote end. At the same time, Channel Associated Signaling (CAS) or Common Channel Signaling (CCS) in E1/T1 circuits are identified and transmitted.
Format of an SAToP Packet

The Structure Agnostic TDM over PSN (SAToP) standard can implement the emulation for the transmission of unchannelized TDM services. The TDM frame structure need not be identified. Only simple transparent transmission is implemented. The SAToP is defined in RFC4553. At present, the CX supports the construction of SAToP packets in MPLS mode. Figure 2-11 shows the format of an SAToP packet. Figure 2-11 Format of an SAToP packet
0 MPLS Label PW Label 0 0 0 0 L R RSV FRG LEN 20 EXP EXP 23 S 1 TTL TTL 31
Sequence Number
RTP header
TDM data
An SAToP packet contains a 4-byte MPLS frame header and a 4-byte PW frame header, which is described in "Encapsulation Position and Structure of the Label." TDM data indicates the TDM data payload in the format of serial data code streams. For details about other fields, see "Format of a CESoPSN Packet."
Issue 01 (2008-01-15)
2-17
2 TDMoPSN
SAToP divides TDM services as serial data streams. Packets are encapsulated and transmitted in PWs. Although SAToP cannot identify the TDM frame structure, it supports the transmission of synchronous timing information.
2.3.6 Calculation of TDM Frames and the Bandwidth

Conversion of TDM Data into Frames at the Network Side
TDM services are transmitted through TSs on channelized E1/T1 links and flows are transmitted on unchannelized E1/T1 links. Regardless of which mode is used, the CX encapsulates the TDM services into CESoPSN or SAToP packets before encapsulating them into Ethernet frames. Thus, the emulation for the transmission of TDM services is carried out across the PSN. For TDM services, the PWE3 frame header, MPLS frame header, and Ethernet frame header all belong to the overhead for transmission. The method of encapsulating TDM data determines the bandwidth that is consumed by E1/T1 links on the PSN, as shown in Figure 212. Figure 2-12 Networking diagram for the conversion of TDM data into frames at the network side
Unchannelized E1
PW1 E M PW f1 f2 fi f3 f2 f1
E1/T1 BTS /NodeB
MPLS network CX-A PW1 PW2 PW3 CX-B E1/T1 BSC /RNC
Channelized
TS0 TSb TSa
PW2 E M PW
E1
a3 a2 a1
PW3 E M PW a1 b1 a2 b2 ai bi
PW
In the preceding figure, E indicates the Ethernet frame header; M indicates the MPLS frame header; PW indicates the PWE3 frame header. CX-B at the network side is connected to the upstream BSC or RNC device. CX-A at the user side is connected to the downstream BTS device or Node B. Three PWs are set up between CX-A and CX-B. PW1 is a service PW configured on the unchannelized E1 interface. PW1 encapsulates TDM frames into SAToP packets. PW2 is the clock PW configured on the channelized E1 interface. PW3 is the service PW configured on the same E1 interface. PW2 and PW3 encapsulate TDM frames and TSs into CESoPSN packets.
2-18
Issue 01 (2008-01-15)
2 TDMoPSN
Each E1/T1 link can be configured with multiple PWs. The bandwidth of each PW at the network side should be calculated before the calculation of the bandwidth of the E1/T1 link at the network side. The bandwidth of all PWs on the E1/T1 interface in total at the network side is the bandwidth of the E1/T1 link at the network side.
Formula Used to Calculate the Bandwidth of a PW

The formula used to calculate the bandwidth of a PW is as follows:
If the bandwidth is expressed in kbit/s, the formula can be expressed by symbols as follows:
The meaning of each parameter in the formula is described as follows: B: indicates the bandwidth of a PW at the network side. T: indicates the number of TSs encapsulated in a PW frame in the PW. F: indicates the number of TDM frames encapsulated in a PW frame in the PW. The number of encapsulated TDM frames ranges from 1 to 512 for a channelized service PW and from 1 to 26 for a channelized clock PW or unchannelized PW. 64: indicates that the bandwidth of each TS is 64 kbit/s. 42: indicates that the overhead in the Ethernet frame header after the CESoPSN or SAToP packets are encapsulated into Ethernet frames contains 42 bytes. The overhead contains the 6-byte destination MAC address, 6-byte source MAC address, 4-byte 802.1Q tag, 2-byte frame type, 4-byte MPLS frame header, 4-byte PWE3 frame header, 4-byte TDM control word, and 12-byte RTP frame header. 4: indicates that the Frame Check Sequence (FCS) is 4 bytes long. The value of the FCS field is obtained after the CRC on the basis of the protocol type and user data. The total length of an Ethernet frame (that is, T x F + 46) should be between 64 and 1522 bytes. If an Ethernet frame is longer than 1522 bytes, this frame is directly discarded. If an Ethernet frame is shorter than 64 bytes, this frame is automatically filled with bytes to become 64-byte long before being forwarded.
Calculation of the Bandwidth of the Channelized E1/T1 Link

Each channelized E1/T1 interface can be configured with multiple PWs. The formula used to calculate the bandwidth of the channelized E1/T1 interface is as follows:
If the bandwidth is expressed in kbit/s, the formula can be expressed by symbols as follows:
In the formula, B indicates the bandwidth of the channelized E1/T1 interface. The meanings of T and F are described in "Formula Used to Calculate the Bandwidth of a PW." P indicates the number of PWs created on the E1/T1 interface. If an Ethernet frame (that is, T x F + 46) is
Issue 01 (2008-01-15)
2-19
2 TDMoPSN
shorter than 64 bytes, this frame is automatically filled with bytes to become 64-byte long before being forwarded. The following takes an example to introduce how to calculate the bandwidth of the channelized E1 interface at the network side. Two PWs are created on a channelized E1 interface. One PW transmits clock signals. In this PW, a PW frame has 26 TDM frames encapsulated and each TDM frame contains TS0 only. The other PW transmits services. In this PW, a PW frame has 50 TDM frames encapsulated and each TDM frame contains three TSs. With this configuration, the bandwidth of the E1 interface at the network side is calculated as follows: Bandwidth of the clock PW = 64 x (1 + 46 / 26) x 1 = 177 kbit/s Bandwidth of the service PW = 64 x (3 + 46 / 50) x 1 = 251 kbit/s Total bandwidth of the E1 interface = 177 + 251 = 428 kbit/s Therefore, the bandwidth of the E1 interface at the network side is 428 kbit/s.
A positive correlation exists between the bandwidth of the channelized E1/T1 interface at the network side and the number of encapsulated TSs (indicated by T) and PWs. A negative correlation exists between the bandwidth of the channelized E1/T1 interface at the network side and the number of encapsulated TDM frames (indicated by F).
If the number of encapsulated TDM frames in a PW frame is definite, the bandwidth decreases when encapsulated TSs decrease. If the number of encapsulated TSs in a PW frame is definite, the bandwidth decreases when encapsulated TDM frames increase. For an E1/T1 link, the bandwidth increases when more PWs are on the link.
Calculation of the Bandwidth of the Unchannelized E1/T1 Link

Each unchannelized E1/T1 interface can be configured with one PW only. The bandwidth of the single PW at the network side is the total bandwidth of the E1/T1 interface at the network side. If the bandwidth is expressed in kbit/s, the formula can be expressed by symbols as follows:
In the formula, B indicates the bandwidth of the unchannelized E1/T1 interface at the network side. The value of T is always 32. For the meaning of F, see "Formula Used to Calculate the Bandwidth of a PW." The following takes an example to illustrate how to calculate the bandwidth of the unchannelized E1 interface at the network side. Create one PW on an unchannelized E1 interface. The number of encapsulated TDM frames in a PW frame is 26. With this configuration, the bandwidth of the E1 interface at the network side is calculated as follows: Bandwidth of the unchannelized E1 interface at the network side = 64 x (32 + 46 / 26) = 2161 kbits = 2.161 Mbit/s
A negative correlation exists between the bandwidth of the unchannelized E1/T1 interface at the network side and the number of encapsulated TDM frames (indicated by F). A positive correlation exists between the bandwidth of the unchannelized E1/T1 interface at the network side and the number of encapsulated TSs (indicated by T).
The more TSs are used to transmit services, the better the unchannelized mode works. For a service PW, the bandwidth decreases if the encapsulated TDM frames increase.
2-20
Issue 01 (2008-01-15)
2 TDMoPSN
Formula Used to Calculate the Transmission Delay

For the transmission of TDM services across the PSN, the lower-layer transport mechanism changes from circuit switching to packet switching. To ensure that various services are carried to the peer end with high quality, the requirement for the total delay of TDM transmission must be met. According to empirical data, the total transmission delay is not more than 25 ms for 2G wireless services, not more than 40 ms for 3G wireless services, and not more than 50 ms for data services. In actual networks, the total transmission delay varies with the service type. The formula used to calculate the total transmission delay is as follows:
PD: indicates the process delay of the device. The delay is caused when the CX forwards the Ethernet frames that encapsulate TDM services. The delay is relatively fixed and usually less than 3 ms. TD: indicates the transmission delay on the line. The delay is caused when TDM services are transmitted from one side of the PSN to its other side. This delay is directly proportional to the length of the link but inversely proportional to the link transmission rate. Much influenced by network congestion, the delay varies greatly with the network status. JBD: indicates the jitter buffer delay. This delay refers to the period over which the data is in the jitter buffer before the transmission. The deeper the jitter buffer, the longer the delay. TDE: indicates the total delay of encapsulation. The delay is caused when multiple TDM frames are encapsulated into an Ethernet frame. The more the TDM frames are encapsulated, the longer the delay is.
Formula Used to Calculate the TDM Frames to Be Encapsulated

The number of TDM frames to be encapsulated is under the following constraints: Limit to the number of encapsulated TDM frames in a PW frame supported on the CX in theory For the service PW configured on a channelized E1/T1 interface, the number of encapsulated TDM frames ranges from 1 to 512. For the clock PW configured on a channelized E1/T1 interface or the service PW configured on an unchannelized E1/T1 interface, the number of encapsulated TDM frames ranges from 1 to 26. Formula used to calculate the length of Ethernet frame In the application of TDMoPSN, TDM frames are finally encapsulated into Ethernet frames. Therefore, the number of TDM frames encapsulated in an Ethernet frame is limited by the total length of the Ethernet frame. The total length of an Ethernet frame (that is, T x F + 42 + 4) should be between 64 and 1522 bytes. T indicates the number of TSs encapsulated in the PW frame. F indicates the number of TDM frames encapsulated in the PW frame. 42 indicates that the overhead of the Ethernet frame is 42 bytes. 4 indicates that the FCS is 4 bytes long. Based on the preceding formula, T x F 1476. Then, the number of TDM frames to be encapsulated in a PW frame is calculated as follows:
Formula used to calculate the bandwidth at the network side
Issue 01 (2008-01-15)
2-21
2 TDMoPSN
According to the network planning strategies, the uplink FE/GE bandwidth and the number of E1/T1 links (or BTS devices) that the uplink carries can be determined. In this case, the number of TDM frames to be encapsulated in a PW frame can be adjusted. Based on the formula described in "Formula Used to Calculate the Bandwidth of a PW", you can obtain the formula used to calculate the TDM frames to be encapsulated in a PW frame:
F: indicates the number of TDM frames encapsulated in the PW frame. B: indicates the bandwidth of the service PW at the network side. T: indicates the number of TSs encapsulated in the PW frame.
When the number of TSs encapsulated in a PW frame is definite and the required bandwidth at the network side decreases, the number of TDM frames to be encapsulated should increase. Formula used to calculate the total transmission delay In end-to-end communications, different services have different requirements for the total transmission delay. You can obtain the number of TDM frames to be encapsulated by reverse calculation. According to the description in "Formula Used to Calculate the Transmission Delay", the processing delay of device and transmission delay on the line are fixed. The depth of the jitter buffer, which can be configured by the user through command lines, directly determines the jitter buffer delay. The encapsulation delay of each TDM frame is 125 s. The formula used to calculate the number of TDM frames to be encapsulated is as follows:
F indicates the number of TDM frames encapsulated in the PW frame.
Strategy of Bandwidth Calculation for Services

Voice, video, and data services can be transmitted between a BTS and a BSC. Different services use different numbers of TSs, and their requirements for transmission delay and jitter are also different. Thus, a proper encapsulation strategy should be chosen with the consideration of the bandwidth at the network side and the requirement of the service for transmission delay and jitter. The encapsulation strategies for different services are described as follows: Wireless voice services Voice services use a few TSs (usually, not more than three) and are very sensitive to the transmission delay. The number of encapsulated TDM frames concerns the transmission delay and the network bandwidth. To reduce the transmission delay and prevent Ethernet frames from consuming the network bandwidth, 20 to 25 TDM frames are recommended.
In channelized mode: A PW frame in the clock PW has 24 TDM frames encapsulated, and each TDM frame contains TS0. A PW frame in a service PW has 24 TDM frames encapsulated, and each TDM frame contains two TSs. The total bandwidth of the E1 interface is 0.428 Mbit/s. An upstream FE interface with the bandwidth of 100 Mbit/s supports up to 230 (100/0.428 230) such channelized E1 links.
In unchannelized mode:
2-22
Issue 01 (2008-01-15)
2 TDMoPSN
An E1 link with the bandwidth of 2.161 Mbit/s supports up to 26 encapsulated TDM frames in a PW frame. An upstream FE interface supports a maximum of 45 (100 / 2.161 45) such unchannelized E1 links. Video services Video services use 5 to 10 TSs and are sensitive to the transmission delay. The encapsulation of 25 to 30 TDM frames in a PW frame is recommended to balance the transmission delay and bandwidth consumption.
In channelized mode: A PW frame in the clock PW has 27 TDM frames encapsulated, and each TDM frame contains TS0. A PW frame in a service PW has 27 TDM frames encapsulated, and each TDM frame contains eight TSs. The total bandwidth of the E1 interface is 0.798 Mbit/s. An upstream FE interface with the bandwidth of 100 Mbit/s supports up to 120 (100 / 0.798 120) such channelized E1 links.
In unchannelized mode: An E1 link with the bandwidth of 2.161 Mbit/s supports a maximum of 26 encapsulated TDM frames in a PW frame. An upstream FE interface supports up to 45 (100 / 2.161 45) such unchannelized E1 links.
Data services Data services use 15 to 20 TSs and are sensitive to the transmission delay. The encapsulation of 30 to 40 TDM frames in a PW frame is recommended to balance the transmission delay and bandwidth consumption.
In channelized mode: Different service PWs are created for different service flows. Assume there are 18 service PWs. Each PW uses one TS, and 35 TDM frames are encapsulated in a PW frame. The total bandwidth of the E1 link is 2.844 Mbit/s. An upstream FE interface supports up to 35 (100 / 2.844 35) such unchannelized E1 links.
In unchannelized mode: An E1 link with the bandwidth of 2.161 Mbit/s supports a maximum of 26 encapsulated TDM frames in a PW frame. An upstream FE interface supports up to 45 (100 / 2.161 45) such unchannelized E1 links.
If service TSs are few, the transmission in channelized mode saves more bandwidth. Otherwise, the unchannelized mode can be adopted to save the bandwidth. The number of TDM frames can also be adjusted to meet the requirement for the bandwidth at the network side. The following should be considered when you select encapsulation methods for different TDM services: Transmission delay Depth of the jitter buffer Number of encapsulated TDM frames
2.4 Clock Synchronization

A digital synchronization network is an important part of a digital communications network, because the former guarantees the timing performance of the network. A digital network transmits discrete pulses obtained after the encoding of information. If inconsistency in pulses or phases is found between any two digital switching devices, or digital bit streams are affected by phase drift or jitter during transmission, sliding damage is caused in the digital
Issue 01 (2008-01-15)
2-23
2 TDMoPSN
switching system. The effective control of slides is required to meet the requirements of transmitting various types of information on the network. For this reason, clock synchronization is needed.
2.4.1 Concept and Function of Clock Synchronization

Concept of Clock Synchronization
Clock synchronization is also called frequency synchronization, in which a strict and specified relation exists in terms of the frequency or phase between signals. All devices on the network can operate at the same rate. Discrete pulses are transmitted over digital communications networks after information is coded on the basis of the Pulse Code Modulation (PCM) technology. As for two transmission devices in a digital network, each device fixes its transmission rate based on its internal clock. If each device receives digital signals at a rate different from that of its internal clock, bit streams may slide. To prevent the sliding, the two devices must use the same reference clock. And the two devices constitute a part of the digital synchronization network. The synchronization of a digital network refers to the synchronization between the clocks of devices in the digital network, including the synchronization in terms of bit timing and frame timing.
Clock Synchronization Hierarchy

Now, SDH/PDH uses Building Integrated Timing Supply System (BITS) to build the digital synchronization network and forms a hierarchical timing allocation system. The master/slave clock mode is used for clock synchronization. A clock acts as the master clock. Other clocks synchronize with the master clock in a hierarchical manner to realize the hierarchical synchronization mechanism. As shown in Figure 2-13, this hierarchy includes the reference clock, stratum-2 clock, stratum-3 clock, and stratum-4 clock. Figure 2-13 Clock synchronization hierarchy
PRC/LPR primary reference clock
Stratum-2 clocks
Stratum-3 clocks
devices ...... ......
PRC or LPR reference clock
2-24
Issue 01 (2008-01-15)
2 TDMoPSN
The Primary Reference Clock (PRC) is called permanent primary reference clock. The caesium or hydrogen clock source provides high-precision reference signals, and cooperates with the clock synthesis system and clock allocation system. The Local Primary Reference (LPR) is called the local primary reference clock. The Global Positioning System (GPS) provides the high-precision clock source for the LPR. The PRC and LPR are stratum-1 primary reference clocks. Their performances comply with ITU-T G.811 Recommendation. The satellite receiver of the LPR decodes the satellite signals. The decoded signals are one pulse per second, that is, standard 1 Hz signals. After the phase lock, artificially superimposed interference and ionospheric interference are filtered out. Standard clock signals used on communications networks are finally obtained after frequency conversion and encoding, such as 2.048 Mbit/s signals, 1.544 Mbit/s signals, 2048 MHz signals, and 1544 MHz signals. The LPR is generally placed in ISP' important central offices. Usually, a standby LPR is placed in another pivotal building to provide backup and improve reliability. An STM-N line of the SDH system transmits the signals output by the LPR. The STM-N line is the timing bus. Along this timing bus, the primary reference clock signals are transmitted to communications buildings at the convergence layer, such as the central offices in the cities of a province. These central offices are usually equipped with stratum-2 node clocks. Stratum-2 node clocks A stratum-2 node clock (stratum-2 clock for short) is equipped with the digital phaselocked loop. This feature is carried out by the rubidium atomic oscillator. Such a clock has excellent performance in clock tracing, filtering, and holding. A stratum-2 clock extracts the timing signal from the STM-N line of the SDH system, and provides the timing signal for the communications devices in the equipment room after clock tracing and filtering. The signal output by the stratum-2 clock is transmitted to counties through the STM-N line of the SDH system. The equipment rooms in counties are usually equipped with stratum-3 node clocks. Stratum-3 node clocks A stratum-3 node clock (stratum-3 clock for short) is configured with the digital phaselocked loop. This feature is carried out by the oven controlled crystal oscillator. The stratum-3 clock has the same performance as a stratum-2 clock in clock tracing and filtering but has a weaker performance in clock holding. A stratum-3 clock, however, is much cheaper than a stratum-2 clock. Therefore, stratum-3 clocks are fit for the equipment rooms of counties in the local network. A number of stratum-3 clocks can be installed in these equipment rooms to obtain good timing quality. A stratum-3 clock extracts the timing signal from the STM-N line of the SDH system. It provides the timing signal for the communications devices in the equipment room after clock tracing and filtering. Stratum-4 node clocks Acting as a stratum-4 node clock (stratum-4 clock for short), a communications device extracts the timing signal from the stratum-3 clock. The device provides the timing signal for lower-end communications devices after clock tracing and filtering.
Clock Transmission Mechanism Based on Ethernet

Wireless communications have strict requirements for clock frequency. Now the communications between a BTS (or Node B) and a BSC (or RNC) are based on the SDH technology. Service interruption may occur when wireless terminals move between the coverage of BTSs (or Node Bs). The frequency between BTSs (or Node Bs) is synchronized within 50 ppb to prevent such service interruption and ensure the quality of clock synchronization.
Issue 01 (2008-01-15)
2-25
2 TDMoPSN
To transmit TDM services across the PSN, clock signals must be transmitted from one end to another end in the PSN. There are two modes of clock transmission.
2.4.2 Adaptive Clock

The adaptive clock means that clock signals are encapsulated into Layer 2 Ethernet frames for transmission. The CX at the core side encapsulates clock information into packets based on a certain algorithm. Packets are transmitted to the opposite end through the PSN. The CX at the user side recovers clock signals from the packets based on the same algorithm, reconstructs the TDM data flow, and keeps clock synchronization with the transmit end. The two CXs on the edge of the PSN transmit original clock pulse signals in packets to each other. Figure 2-14 shows the principle of the recovery algorithm of the adaptive clock. Figure 2-14 Principle of the recovery algorithm of the adaptive clock
Ta' PSN Ta BITS
BTS /NodeB
E1/T1 CX-A CX-B CX-C
E1/T1 BSC /RNC
Ta'
Ta
Ta
Ta Clock signal
CX-C at the BSC (or RNC) side obtains clock signal Ta from the core network side and transmits Ta to CX-A at the BTS (or Node B) side through the PSN. CX-A recovers clock signal Ta from packets. The adaptive clock recovery algorithm ensures that Ta' and Ta are roughly the same. In this way, clock information is transmitted through the PSN. The adaptive clock mode is end-to-end clock synchronization. The transit node need not process clock signals but forward packets. The performance of the adaptive clock, however, is closely related to the PSN bearer network and very sensitive to network delay distribution. The adaptive clock can satisfy the need of clock synchronization to a certain degree in the following situations: The load of the PSN is light. The topology of the network is simple. Transit nodes are few. The transmission delay and jitter are little on the network. The priority of the clock packet is high.
2.4.3 Synchronization Ethernet Clock

With the development of Ethernet transmission technology, synchronization Ethernet need be adopted to transmit clock signals in carrier-class networks large in scope. On the one hand, the clock transmission precision is improved; on the other hand, the stability of clock transmission is enhanced. Thus, it is required to reconstruct the Ethernet that works in asynchronous clock mode and introduce the thought of network-wide synchronous timing
2-26
Issue 01 (2008-01-15)
2 TDMoPSN
transmission of the SDH system into the design of the Ethernet. Clock signals are transmitted from the core to the edge of the network through the transmission on the physical layer of the Ethernet. The synchronization Ethernet clock adopts the point-to-point communication mode. Therefore, each CX that transmits clock signals in the Ethernet need be installed with a dedicated clock card. Clock signals are transmitted through serial code streams, and this ensures the quality of clock synchronization.
Clock Synchronization Mechanism

The PSN formed by the CXs can either adopt a flat mode to obtain clock from BITS or adopt a hierarchical mode to achieve synchronization layer by layer. Figure 2-15 shows the two clock synchronization modes. Figure 2-15 Clock synchronization mechanism
(a) BITS (b) BITS
CX-A
CX-B
CX-C
CX-D
CX-A Clock signal
CX-B
CX-C
CX-D
In flat mode, the BITS device is directly connected to all the CXs in the PSN and directly provides clock signals to multiple CXs to achieve network-wide clock synchronization, as show by (a) in Figure 2-15. The clock precision of all devices in the network is the same. However, the number of output interfaces on the BITS device increases, which makes the deployment difficult. The PSN can also adopt the hierarchical mode to obtain clock information from BITS. Multiple CXs are connected end to end. The upstream CX is directly connected to the BITS device to obtain clock and release the clock signals to the next CX. The next CX extracts clock signals from the Ethernet link. Filtered and processed to prevent jitter, the clock signals are released to the next downstream device. Thus, clock signals are released downstream, as shown by (b) in Figure 2-15. This mode saves output interfaces on the BITS device. However, the clock precision of downstream devices degrades along the downstream link. The clock detection device monitors the clock output by the last CX to achieve the network-wide clock synchronization.
Clock Extraction and Selection

Usually, the CX in the PSN may have one or more than one reference clock sources, as shown in Figure 2-16.
Issue 01 (2008-01-15)
2-27
2 TDMoPSN
Figure 2-16 Clock extraction and selection

BITS PSN BITS
BTS /NodeB
E1/T1
E1/T1 BSC /RNC Clock signal
It is required to select a clock source with the best stability and precision as the primary reference clock. There are three ways to select the clock source. The one based on the priorities of clock sources and the one based on the Synchronization Status Message (SSM) levels of clock sources belong to automatic selection. SSM messages are transmitted by OAM packets. Each SSM message records the precision level of the clock source. Manual selection The user judges the precision and stability of each clock reference source and selects the best one as the master clock source. If the selected clock source fails, the system automatically switches to one of the other two modes. This is the simplest way to select a clock source. However, the selected clock source may not be the optimal one. Selection based on the priorities of clock sources Set a priority for each reference clock source connected to the CX based on precision or stability. The system selects the clock source with the highest priority as the current master clock source. If the selected clock source fails, the system automatically switches to the clock source with the priority second to that of the selected clock source. Selection based on the SSM levels of clock sources The CXs exchange SSM OAM packets with each other. Such packets contain the information about clock levels. The higher the precision, the higher the SSM level. In normal situations, the system uses the clock source with the highest SSM level as the master clock source. When the clock source with the highest SSM level fails, the system automatically switches to the clock source with the SSM level second to that of the selected clock source. Usually, the BITS clock directly connected to the CX is selected as the master clock source. The clock card in the CX extracts clock signals and release clock information to Service Interface Cards (SICs) to ensure that all SICs and the clock card keep synchronization.
Clock Recovery
If the master clock source fails (for example, the link fails), there are two measures to recover the clock based on the level (the SSM level or the priority) of the faulty clock source. If the clock source at the same stratum fails, the system automatically switches to a slave clock source at the same level. If the clock source at a higher stratum fails, the system sticks to the current clock source for a period and then switches to another clock source when a time-out event occurs.
2-28
Issue 01 (2008-01-15)
2 TDMoPSN
Phase Lock and Frequency Holding

Phase lock means that the CX aligns the oscillator of the clock card based on the external clock source. The clock signal after alignment is used as the reference clock signal for other SICs. (a) and (b) in Figure 2-17 show the release of clock signals before phase lock and after phase lock. Figure 2-17 Influence of phase lock on the transmission of the clock signal
(a) (b)
GE/ RPR
E2GFET/ R2GFT/R2UF
BAK
TDM
GE/ E1/T1 RPR
E2GFET/ R2GFT/R2UF
BAK
TDM
E1/T1
GE/ RPR
GE/ RPR
GE/ RPR
GE/ RPR
Clock cable
Clock signal
The TDM SIC performing phase lock to the clock signal The external clock signal enters the CX backplane. It is directly released to other SICs. The TDM SIC does not perform phase lock to the clock signal. When the external clock source is lost, the system backplane has no clock input. Clock slip occurs to other SICs. The TDM SIC not performing phase lock to the clock signal The external clock signal is input to the TDM SIC through the CX backplane. The TDM SIC performs phase lock to the clock signal and then sends the signal to the backplane. The backplane receives the signal and releases it to other SICs. When the external clock source is lost, the TDM SIC continues to keep high precision clock based on its own oscillator. Thus, other SICs are able to keep clock synchronization.
2.5 Characteristics of TDMoPSN Implemented on the CX

2.5.1 Data Jitter Buffer
After traversing the MPLS network and reaching the egress PE, the PW packets may have different arrival intervals or the sequence of PW packets may be distorted. Therefore, the TDM service flow should be reconstructed in the egress PE in the following manner: Maintaining the time interval of PW packets through the jitter buffer technology Rearranging the sequence of distorted PW packets The capacity of jitter buffer can be configured. The jitter buffer of a larger capacity can accept a greater jitter in the transmission interval of packets on the network, but introduces a larger latency in the reconstruction of TDM service flow. Therefore, you must make flexible configurations based on the latency and jitter of different networks.
Issue 01 (2008-01-15)
2-29
2 TDMoPSN
2.5.2 Analysis on Latency of Data Packet

When the TDM data is transmitted through the TDM PWE3, the latency comes from the following sources:
Encapsulation
Encapsulation latency is introduced when the TDM service flow is encapsulated into the PW packets. It is unique in TDM PWE3. Take E1 as an example. The rate of E1 is 2.048 Mbit/s. That is, each frame contains 32 TSs, which are 256 bits. In each second, 8000 frames are transmitted. The duration of each frame is 0.125 ms. If the channelized encapsulation method is adopted and every four frames are encapsulated into one PW packet, the delay of encapsulating one PW packet is 4 x 0.125 ms = 0.5 ms. The encapsulation time increases in accordance with the number of encapsulated PW packets. The more PW packets are encapsulated, the greater the latency is.
Service Processing
The latency in service processing refers to the time that the device processes the packets: Validity check of packets Filtering of packets Calculation the checksum Encaspulation and transceiving of packets This latency is related to the service processing capacity of devices; therefore, it remains unchanged.
Network Transmission
The latency of network transmission refers to the latency that the PW packets are transmitted to the egress PE from the ingress PE through the PSN. This latency varies greatly with the structure of the network topology and service volume. Therefore, it is the main cause for service jitter. At present, the jitter can be resolved through the jitter buffer technology, but the latency cannot be resolved. The latency of TDM services is a combination of the preceding factors.
2.5.3 OAM Supported by TDM

MPLS OAM manages and maintains the public MPLS forwarding layer and provides effective protection when the fault occurs to the MPLS network. When MPLS OAM supports TTSI functions, members of the MPLS OAM protection group function as birectional LSPs to provide protection. The birectional LSPs thus need be configured manually on the tunnel interface. The status of the forward LSP and that of the reverse LSP need be identified so that protection switchover is performed. Whether TDMoPSN supports MPLS OAM depends on the binding of VLANIF interfaces and TDM SICs. If VLANIF interfaces are bound to TDM SICs, TDM does not support MPLS OAM. The TDM SICs complete MPLS/PW encapsulation and the upstream interface of PSN can be a common GE or FE interface.
2-30
Issue 01 (2008-01-15)
2 TDMoPSN
If VLANIF interfaces are bound to TDM SICs, TDM supports MPLS OAM. The TDM SICs perform PW encapsulation. The upstream interface of PSN is the enhanced GE interface that performs MPLS encapsulation.
2.6 Application of TDMoPSN on the CX

This section describes the typical networking diagrams for different services borne by TDMoPSN:
2.6.1 PSN Bearing GSM Wireless Access Services

The CXs in the PSN can be connected to one another and form an Ethernet of a star topology. They can also form a Resilient Packet Ring (RPR) or Rapid Ring Protection Protocol (RRPP) ring to provide rapid protection switching. Figure 2-18 shows the networking diagram for the PSN that bears 2G wireless access services. Figure 2-18 PSN bearing GSM wireless access services
CN-CS BITS
BTS
SS7 PSTN CX-A
/T E1
E1/T1 BTS MPLS network E1/T1 BTS CX-B
CX-C n*E1/T1 CLK BSC
MSC
SGSN
BITS BTS
Core Network CN-PS
BTS PW Clock cable Clock signal
As shown in Figure 2-18, CX-A and CX-B connect to BTS devices through E1/T1 cables. CX-A and CX-B are called service access points. CX-C connects to a BSC device through an E1/T1 cable. CX-C is called service convergence point.
The E1/T1 cables that are used to connect CX-A and CX-B to BTS devices not only bear TDM services but also transmit clock synchronization signals.
There is a PW between the E1/T1 interface of CX-A and that of CX-C, and between the E1/T1 interface of CX-B and that of CX-C. Thus, TDM services are transparently transmitted on the PSN.
Issue 01 (2008-01-15)
2-31
2 TDMoPSN
In this application, CX-C extracts clock signals from the services coming from the upstream BSC, or obtains clock signals from its directly connected BITS device. The PSN can adopt the adaptive clock mode or synchronization Ethernet mode to achieve clock synchronization. If synchronization Ethernet clock is adopted, CX-C selects the master clock source from multiple clock sources in automatic mode based on the priorities or the SSM levels of clock sources or just in manual mode. CX-A and CX-B at service access points extract clock signals from the PSN and release the signals to BTS devices through E1/T1 interfaces.
2.6.2 PSN Bearing R99/R4 WCDMA Wireless Access Services

The CXs in the PSN can be connected to one another and form an Ethernet of a star topology. They can also form an RPR ring or RRPP ring to provide rapid protection switching. The PSN can adopt the adaptive clock mode or synchronization Ethernet mode to achieve clock synchronization. Figure 2-19 shows the networking diagram for the PSN that bears R99 WCDMA wireless access services. Figure 2-19 PSN bearing R99/R4 WCDMA wireless access services
CN-CS BITS
Node B
A I M / T1 E1
RNC CX-A
I E1 MA /T 1
SS7 PSTN
Node B
IM E1 A / T1
CX-C MPLS network
MSC
CLK
I E1 MA /T 1
SGSN
CX-B Core Network CN-PS PW Clock cable Clock signal
Node B
BITS
CX-A and CX-B connect to BTS devices through E1/T1 cables. CX-A and CX-B are called service access points. CX-C connects to a BSC device through an E1/T1 cable. CX-C is called service convergence point.
Between service access points and Node B devices and between the service convergence point and RNC, the special clock interface on E1/T1 SICs is used to transmit clock signals.
There is a PW between the FE/GE interface of CX-A and that of CX-C, and between the FE/GE interface of CX-B and that of CX-C. Thus, TDM services are transparently transmitted on the PSN. In this application, RNC connects to CX-C through the IMA E1 interface. CX-C uses the clock signals coming from the RNC, or obtains clock signals from its directly connected BITS device. The PSN can adopt the adaptive clock mode or synchronization Ethernet mode to
2-32
Issue 01 (2008-01-15)
2 TDMoPSN
achieve clock synchronization. CX-A and CX-B at service access points extract clock signals from the PSN and release the clock signals to Node B devices through special E1/T1 clock interfaces.
2.6.3 PSN Bearing R5 WCDMA Wireless Access Services

The CXs in the PSN can be connected to one another and form an Ethernet of a star topology. They can also form an RPR ring or RRPP ring to provide rapid protection switching. Figure 2-20 shows the networking diagram for the PSN that bears R5 WCDMA wireless access services. Figure 2-20 PSN bearing R5 WCDMA wireless access services
CN-CS BITS
Node B RNC
FE FE /G E C LK LK C
SS7 PSTN
CX-A CX-C MSC
Node B
CL K FE
MPLS network CLK CX-B SGSN

E1 1 /T
FE C LK
Node B
BITS
BSC
Core Network CN-PS
Clock cable
Clock signal
As shown in Figure 2-20, CX-A and CX-B are connected to Node B devices through FE links. CX-C is connected to the RNC through an FE/GE cable.
PWs need not be set up within the PSN. Node B devices directly encapsulate TDM services into Ethernet frames and transmit the services to the CXs through FE links.
The FE/GE links connected to CX-A, CX-B, and CX-C are dedicated to transmitting TDM services. CX-A, CX-B, and CX-C receive or transmit clock signals through dedicated clock interfaces. In this application, the RNC is connected to CX-C through the FE/GE interface only. The FE/GE link does not transmit clock signals. Therefore, CX-C can obtain clock signals through the following methods: CX-C is installed with a TDM SIC, which has a dedicated clock interface to extract clock signals from the RNC. CX-C can use the clock signals coming from the BSC in the GSM network. CX-C is directly connected to the BITS device to obtain clock signals.
Issue 01 (2008-01-15)
2-33
2 TDMoPSN
The PSN can adopt only the synchronization Ethernet as the clock synchronization mechanism. CX-A and CX-B extract clock signals from the PSN and transmit the signals to Node B devices through dedicated clock interfaces.
2.6.4 PSN Bearing Traditional Services

The CXs in the PSN can be connected to one another and form an Ethernet of a star topology. They can also form an RPR ring or RRPP ring to provide rapid protection switching. Figure 2-21 shows the networking diagram for the PSN that bears traditional services such as PSTN, ATM, or FR services. Figure 2-21 PSN bearing traditional services
BITS
CLK PSTN
E1 / T1
CX-C
/ CX-F E1 T1
E1/T1
Frame Relay
CX-B CX-A Frame Relay

E1 / T1 / T1 E1
ATM
MPLS network CX-D
CX-E E1 / T1 PSTN
ATM
PW
Clock cable
Clock signal
As shown in Figure 2-21, CX-C connects a BITS device through an E1/T1 clock cable to receive clock signals. There is a PW between the E1/T1 interface of CX-A and that of CX-E to carry out transparent transmission of PSTN services across the PSN. You can configure static PWs or use LDP to set up PWs dynamically. In this application, CX-C obtains clock signals from BITS and adopts synchronization Ethernet to release the signals to CX-A and CX-B. CX-A extracts clock signals from the PSN and transmits the signals through the E1/T1 link to the connected PSTN. CX-B transmits the extracted clock signals to CX-D and CX-E. CX-D transmits clock signals to the ATM network connected by an E1/T1 link. CX-E transmits clock signals to the PSTN connected to an E1/T1 link.
2.6.5 MPLS OAM Supported by TDM

In a PSN, the CXs are connected to form networks of different topologies. Figure 2-22 shows the networking of MPLA OAM supported by TDM.
2-34
Issue 01 (2008-01-15)
2 TDMoPSN
Figure 2-22 MPLS OAM supported by TDM

CN-CS BITS
BTS
SS7 PSTN CX-A
/T E1
E1/T1
1
CX-C MPLS network n*E1/T1 CLK BSC MSC
BTS
SGSN
CX-B BTS
BITS
Core Network CN-PS
BTS Active LSP Backup LSP
Similar to the preceding networking requirements, there is a PW between the E1/T1 interface of CX-A and that of CX-C, and between the E1/T1 interface of CX-B and that of CX-C. You can configure static PWs or use LDP to set up PWs dynamically. Thus, TDM services are transparently transmitted on the PSN. Two LSP tunnels in reverse directions are set up between CX-A and CX-C, and between CXB and CX-C, to provide 1:1 backup. Through the MPLS OAM technology, LSP faults can be detected rapidly. The two LSPs form a protection group. When the primary LSP fails, TDM services switch to the backup LSP rapidly. After the primary LSP is restored, TDM services switch from the backup LSP to the primary LSP.
2.7 References
For more information about TDMoPSN, refer to the following documents. Document No. RFC 3550 RFC 3916 RFC 3985 RFC 4197 RFC4385 RFC4446 Description A Transport Protocol for Real-Time Applications Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3) Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching Networks Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)
Issue 01 (2008-01-15)
2-35
2 TDMoPSN
Document No. RFC 4553
Description Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP) draft-ietf-pwe3-cesopsn-07.txt
ITU-T Rec. G.703 ITU-T Rec. G.704 ITU-T Rec. G.706
Physical/electrical characteristics of hierarchical digital interfaces Synchronous Frame Structures Used At 1544, 6312, 2048, 8448 And 44 736 kbit/s Hierarchical Levels Frame Alignment And Cyclic Redundancy Check (CRC) Procedures Relating To Basic Frame Structures Defined In Recommendation G.704 Characteristics Of Primary PCM Multiplex Equipment Operating At 2048kbit/s The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy (Draft Recommendation )Timing and Synchronization aspects in Packet Networks. Digital Hierarchy Format Specification
ITU-T Rec. G.732 ITU-T Rec. G.823 ITU-T Rec. G.824 ITU-T Rec. G.8261 ANSI T1.107
2-36
Issue 01 (2008-01-15)

01-02 TDMoPSN

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

01-02 TDMoPSN

Загружено:

Авторское право:

Доступные форматы

Quidway CX200/300 Metro Services Platforms Feature Description - Services

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

2.7 References ...................................................................................................................................................2-35

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

2.2 PSN Overview 2.3 Principle of TDMoPSN

2.4 Clock Synchronization

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

2.1 TDM Overview

1 link, n channels MUX DEMUX

channel 1 channel 2 channel 3 channel n

Relationship Between Frames and TSs in TDM

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

Figure 2-2 Relationship between frames and TSs in TDM

F7999 TS1 TS2 TS3 F8000 TS1 TS2 TS3

TSn-1 TSn TSn-1 TSn

2.1.2 Digital Carrier System

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

1 frame = 193 bits:125us TS1 T1 TS2 TS24

2.1.3 Channelization Technology and Unchannelization Technology

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

2.1.4 Circuit Switching Technology

2.1.5 Typical Application of Circuit Switching

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

RAN Wireless Access Communications

2.2 PSN Overview

2.2.2 Virtual Circuit Technology

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

2.2.3 Typical Application of Packet Switching

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

2.3 Principle of TDMoPSN

TDMoPSN Circuit Emulation Technology

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

2.3.2 PWE3 Transmission Mechanism

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

Framework of a PWE3 Network

BTS/ NodeB ATM /PSTN /FR Forwarder

BSC/ RNC ATM /PSTN /FR

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

Setting Up and Maintaining a PW

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services

The PW between PE1 and PE2 is deleted.

2.3.4 Encapsulation and Forwarding of TDM Data Flows

0 MPLS Label PW Label

Encapsulation and Forwarding of 2G/3G Wireless Services

Huawei Technologies Proprietary

Quidway CX200/300 Metro Services Platforms Feature Description - Services