Tdmoip: Introduction - Clock Recovery & Measurement
Tdmoip: Introduction - Clock Recovery & Measurement
• TDMoIP: Introduction
• Clock Recovery & Measurement
v.1.0 1
1
1. TDMoIP:
Introduction
v.1.0 2
2
Pseudowires
v.1.0 3
3
Tunneling - interworking
Mating different network protocols is
called interworking
various names :
interworking
function (IWF)
gateway (GW)
Native network Native
Service Service
Simplest case is network
4
interworking
v.1.0
4
Emulating TDM
v.1.0 5
5
Classic Telephony
Access Network Core (Backbone) Network
analog lines
CO SONET/SDH CO P
B
T1/E1 SWITCH NETWORK SWITCH X
P
B
X
extensions Synchronous
Non-packet network
T1/E1
6
TDMoPSN
Access Network
analog lines
Packet
P
T1/E1/T3/E3
Switched B
X
extensions
P Network
B
X
Asynchronous network
T1/E1
No timing information transfer
7
A few G.XXX sayings …
G.114 (One-way transmission time)
delay < 150 ms acceptable
150 ms < delay < 400 ms conditionally acceptable
delay > 400 ms unacceptable
G.126/G.131 echo control may be needed
G.823/G.824 (timing)
Primary vs. secondary clocks
jitter masks
wander masks
8
TDMoIP vs. VoIP
Two ways to integrate TDM services into
PSNs
VoIP
Voice centric!
Revolution - complete (forklift) CPE
replacement
New signaling protocols (translation
needed)
New functionality (e.g. video-phone, presence)
TDMoIP
v.1.0 9
9
TDMoIP as a Migration Path
10
TDMoIP Protocol Processing
TDM TDM
IP Packets IP Packets
frames frames
PSN
Steps in TDMoIP
The synchronous bit stream is
segmented
The TDM segments are adapted
TDMoIP control word is prepended
PSN (IP/MPLS) headers are
prepended v.1.0 11
11
TDMoIP Protocol Processing
TDM TDM
IP Packets IP Packets
frames frames
PSN
Traffic Types:
Structured (framed)
Unstructured (unframed)
v.1.0 12
12
TDMoIP encap formats
- For Structured Traffic
(TDMoIP: IETF draft-Anavi-
tdmoip-06)
13
Functionality
What needs to be transported
from end to end?
Voice (telephony quality, low delay,
echo-less)
Tones (for dialing, PIN, etc.)
Fax and modem“timeslots”
transmissions
Signaling (there are 1000s of PSTN
T1/E1 features!)
frame
CCS TS1
SYNC (comon
TS2 TS3 … Signaling), CAS…
CAS
Channel signaling
bits
TSn
(Channel
(1 byte) Associated Signaling)
Timing v.1.0 14
14
Why isn’t it easy
Why don’t we simply encapsulate
the T1/E1 frame? 24 or 32 bytes
15
The basic idea
Those problems can be solved
by:
adding a packet sequence number
adding a pointer to the next superframe
boundary
only sending timeslots in use
UDP/IP seqnum ptr T1/E1 frames (only timeslots in use)
allowing multiple TDM frames per
(with CRC)
for example
packet 7 @ TS1 TS2 TS5 TS7 TS1 TS2 TS5 TS7
16
why AAL1 – For Static
Structured Traffic
“AAL1” is the simplest method
to transport structured TDM
traffic (voice, sync, signaling)
ATM community has done the
debugging for us!
are used
we can not change this configuration in real-
time!
18
AAL2 for Dynamic BW
Traffic
AAL1 is BW inefficient when
timeslots are dynamic
Even with GB rates we should consider efficiency
considerations
19
Isn’t this just ATM?
AAL1 and AAL2 are adaptation protocols
originally designed to massage data into a format
that can be readily used
As we have shown, they are natural
candidates for
any application which needs to multiplex
timeslots
20
Service Inter-working
TDMoIP is not the first TDM emulation technology
We should also provide service interworking,
existing ATM circuit emulation services (AAL1, AAL2)
PSN
ATM-CES GW
21
One More Payload type: HDLC
Efficiently
transfer CCS traffic
(such as SS7 embeded in
TDM traffic)
22
TDMoIP layering structure –
Structured Traffic
PSN / multiplexing
TDMoIP Encapsulation
higher layers
23
TDMoIP Control Word
FORMID flags Res Length Sequence Number
Flags (2 b)
L bit (Local failure)
R bit (Remote failure)
Res (4 b):
Length (6 b) used when packet may be padded
Sequence Number (16 b) used to detect packet loss /
miss-ordering v.1.0 24
24
TDMoIP encap formats
- For UnStructured
Traffic
(SATOP: Draft-ietf-pwe3-satop)
v.1.0 25
25
Payload Type of UnStructured
Traffic
TDM traffic is treated as RAW data
TDM bit stream is put into payload field
The payload size is defined during setup
Payload size remains the same
It should support the payload size:
T1: 192 bytes
E1: 256 bytes
T3 and E3: 1024 bytes
26
TDMoIP encap formats
Summary
v.1.0 27
27
TDMoIP layering structure
PSN / multiplexing
TDMoIP Encapsulation
higher layers
v.1.0 28
28
TDMoIP Control Word
FORMID flags Res Length Sequence Number
Flags (2 b)
L bit (Local failure)
R bit (Remote failure)
Res (4 b):
Length (6 b) used when packet may be padded
Sequence Number (16 b) used to detect packet loss /
miss-ordering v.1.0 29
29
TDMoIP packet format
IP header (5*4bytes)
TDMoIP payload
30
IP/UDP/RTP Encapsulation 32 Bit
Destination IP address
CRC-32
Ethernet
Header Payload
TOS Src Bundle# Control
Src adr (AAL1,AAL2,
Dst adr Dst= 0x085E Word
HDLC, RAW)
UDP Source Port Number is used as the bundle number designator , UDP Destination port number
v.1.0 31
set to hex 085E (2142) assigned by IANA for TDMoIP.
31
TDMoMPLS packet format
outer inner control TDM
label label word Payload
32
MPLS Encapsulation
• Example of MPLS Header :
Adapated
CRC-32
Ethernet
v.1.0 33
33
TDM o L2TPv3
IP header (5*4 B)
Session ID (4 B)
Optional cookie (4 or 8 B)
higher layers
TDMoIP header (4 B)
TDMoIP payload
34
TDMoIP in Ethernet Frame
TDMoIP Frame
35
TDMoIP Frame w QoS Support
TOS -Type of Service
Field (Diffserv) Priority TDMoIP
Control Word
• Header Compression can be used to decrease the header down to a few bytes
• Ethernet Packet Min 64 bytes Max 1536 bytes
v.1.0 36
36
TDM Timing Recovery
v.1.0 37
37
Introduction
PSN (e.g. IP) have no clock distribution
mechanism
38
Introduction cont.
Result of RTP can not meet the G.823,
G.824
Due to time stamp quantization error, packet
loss, ..
Use 12 bytes for RTP
Require reference clock in both side
(expensive for high accurate reference clock)
39
Introduction cont.
TXC PacketTrunk-4 chip's innovative
clock recovery scheme
retains robustness of conventional
scheme
improved capabilities
Two phases
acquisition phase
rapid frequency lock is attained.
tracking phase
the achieved frequency
v.1.0
lock is sustained 40
40
Frequency Hold-over
Rx buffer starvation (under-run) can be
caused by:
Network congestion
packet loss
In dynamic application when there is no
activity
While shifting to an alternate bundle, in
redundancy mode
41
Why TDMoIP?
Complementary to VoIP.
Provides high voice quality with low latency.
Can support all applications that run over E1/T1 circuits, not just
voice.
Can be made transparent to protocols and signaling.
An evolutionary – not revolutionary – approach, so investment
protection is maximized.
v.1.0 42
42
Voice Evolution
v.1.0 43
43
TDM over GbE MAN
TDM Leased
Lines
CLASS Central
PSTN
Switch Office
TDMoIP GW
TDMoIP
GW
POP
GbE
Customer
Premise
Public
INTERNET
v.1.0 44
44
TDM Concentration
Features:
TDM concentration (grooming multiple T1/E1 into OC-3/STM-1 trunks)
E3/T3 Carrier Trunking
With:
GbE Network I/F PBX
PBX
OC-3/STM-1 TDM interface
ADM TDMoIP
GW
TDMoIP
GW
SDH/
CLASS SONET IPIP
Switch
TDMoIP
GW
SS7 TDMoIP
GW
ADM
PSTN
PBX
v.1.0 45
45
Metro MTU Application
TDMoIP GW PBX
PBX
Corporate Site B
TDMoIP GW PBX
POTS
PBX
PBX
Switch TDMoIP Switch Switch TDMoIP
Switch/Router GW GW
IP/MPLS
Network PSTN
TDMoIP GW
v.1.0 46
46
IP/Ethernet
Fixed Wireless, Coax, or /Cell sites w
/Switch site w
TDMoIP GW
Fiber FT1/T1/n*T1
CMTS
T1/ T3/ E1
100 Mbps Metro
(GbE, IP, RPR, Coax
HFC, EoS)
GW GW
FT1/T1/n*T1
Fixed
Wireless
FT1/T1/n*T1
v.1.0 47
47
SS7 over IP
User’s needs: Potential customers:
• Transparent SS7 forwarding over IP • Voice carriers
• Voice transferred as VoIP • Satellite providers
• Cross Connect functionality • Cellular operators
• MAN providers
Intelligent
Network
SS#7
PSTN Server
TDMoIP-based
signaling GW
TDMoIP-based TDMoIP-based
signaling GW signaling GW
GbE
Switch IP Network GbE
Switch
Public Public
Voice VoIP Voice
VoIP
Switch GW Switch
GW
v.1.0 48
48
TDMoIP Summary