Module 2 Protocol Stackv1

Module4
Protocol Stack
Confidential
1
Nokia Siemens Networks
6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009
All IP/ Ethernet in NSN 2G Radio Access elements

Entire NSN GSM interfaces supporting IP/ ETH
BSS
Core Site
BSC
SML
C
Lb+
BS
C
TCSM /
TRAU
BSCBSC
Ater
MGW
A
A
Sigtran
Abis
MSC
Abis
BTS
Gb
O&M
NetActT
M
Before
BSS13
RG10
RG20
(CESoPSN)
(CESoPSN)
Packet Abis
A over IP
Confidential
2
SGSN
What basically is Packet Abis?

Ethernet or
MLPPP/HDLC
IP
UDP
RTP
RG20
CODECx
Codec is packed into packet directly instead of TRAU frame

Bandwidth is pooled for all types of traffic
(no dedicated allocation anymore)

e.g. PS data traffic can utilize all bandwidth available
Nothing is sent, when there is nothing to sent

Physical media is
PDH/SDH (E1/T1, STM1/OC3)
Ethernet
Confidential
3
Packet Abis Protocol Stack
PS U-plane
CS U-plane
C-plane
M-plane
NSN RTP
IUA
UDP
SCTP
ICMP
IP
ARP
MC ML PPP
Ethernet MAC
TDM
Ethernet PHY
Confidential
4
New Transport Protocols For Packet Abis

Packet Abis requires the adoption of new transport protocols
with respect to the Legacy Abis.
The transport protocols to be used, on the one hand depend on:
The type of traffic flow that has to be conveyed over the Abis
interface, on the other hand are conditioned to the two possible
variants;
Packet Abis over TDM based backhaul (E1/T1)
Packet Abis over PSN based backhaul (Ethernet).
Both variants make use of the IP layer but each one has of
course different requisites in terms of lower layers in order to
cope with the specific physical layer/media.
Confidential
5
New transport protocols for Packet Abis

In case of Packet Abis over PSN the foreseen lower layers are
(as familiar) based on Ethernet MAC and Ethernet Layer 1.
The Packet Abis over TDM variant is rather designed to keep
the currently (widely) adopted TDM backhaul and therefore,
instead of sending the IP packets through Ethernet, they are
sent using ML/MC PPP and HDLC protocols on top of e.g.
E1/T1
Confidential
6
ML PPP (Multi Link Point to Point Protocol)

ML PPP (Multi Link Point to Point Protocol) is defined in RFC 1990 [7] and
used to aggregate (bundle) multiple physical links into a single logical/virtual
link.
This ability to combine multiple lower-speed links into a single, higher-speed
data path is often referred to as packet-based inverse multiplexing.
In Packet Abis over TDM, ML PPP is to be used for aggregation of HDLC
channels and treat them as a single physical pipe for transporting the higher
layer IP packets.
In the transmit direction, ML PPP takes a packet, optionally fragments it, and
adds a ML PPP header which includes sequence number (and 2 bits
indicating beginning and end of fragment). Each resulting fragment (or whole
packet) is transmitted across a separate physical link of the bundle. At the
receiver side, the headers are used to reconstruct the complete packet.
Confidential
7
User Plan
Concerning CS /PS User-plane, the traffic is to be sent across
the Abis interface over the UDP/IP protocol stack; this
regardless of the nature of the traffic itself (i.e. speech, data).
Abis CS /PS User-plane frame format including NSN
Multiplexed RTP
Confidential
8
Control Plan
As far as C-plane is concerned, the signaling flow (TRXSIG) is
to be transferred via IUA (ISDN User Adaptation) protocol layer.
IUA (RFC 4233 [6]) defines a protocol for backhauling of
Integrated Services Digital Network (ISDN) Q.921 User
messages (i.e. LAPD user messages) over IP using the Stream
Control Transmission Protocol (SCTP) in between.
IUA essentially uses SCTP to adapt LAPD channels to be
transferred over IP
Confidential
9
Header compression
In short, IP header compression is the process of compressing
excess protocol headers before transmitting them on a link and
uncompressing them to their original state on reception at the
other end of the link. It is possible to compress the protocol
headers due to the redundancy in header fields of the same
packet as well as consecutive packets of the same packet
stream.
Confidential
10
Header compression
Considering the constraint above and the fact that header
compression might not be available in all network elements, the
functionality is regarded as optional and to be enabled/disabled
by configuration.
Header compression is considered as essential for Packet Abis
over TDM where reducing the overhead allows a more efficient
use of the bandwidth compared to legacy Abis. For Packet Abis
over PSN (Ethernet) the functionality is instead considered as
beneficial (i.e. important but not essential and so deferrable to
future releases) since in this case bandwidth saving is less
crucial than in the TDM one.
Confidential
11
MC PPP (Multi Class Point to Point Protocol),

MC PPP (Multi Class Point to Point Protocol), as defined in
RFC 2686 [8], is an extension of ML PPP that allows defining
more than one instance of ML PPP each one distinguished with
a class number (by profiting of previously unused bits). This
way, for each class it is possible to use a separate sequence
number space and reassembly buffer to be able to ensure that
that most important traffic types are treated with higher priority.
The multiple ML PPP instances are still using the very same
data links (traffic is not separated on the links, but multiplexed
together).
In case of Packet Abis over TDM, MC PPP is to be used for
separation of traffic classes (C-plane, CS, PS, M-plane).
Confidential
12
Packet Abis over TDM
Confidential
13
CS Domain User Plane
BTS
BSC
Abis
TC
Ater
MSC
Transcoding
Codec
NSN muxd RTP
Codec
NSN muxd RTP TRAU frame
UDP
UDP
IP
IP
ML/MC-PPP
ML/MC-PPP
HDLC
HDLC
TDM L1
TDM L1
G.711
G.711
TDM L1
TDM L1
TRAU frame
TDM L1
TDM L1
Packet Abis over TDM; CS domain protocol stack (U-plane)
Confidential
14
CS Domain Control Plane
BTS
BSC
Abis
Abis L3
Abis L3
IUA
IUA
SCTP
SCTP
IP
IP
ML/MC-PPP
ML/MC-PPP
HDLC
HDLC
TDM L1
TDM L1
MSC
BSSMAP
BSSMAP
SCCP
SCCP
MTP
MTP
TDM L1
TDM L1
Packet Abis over TDM; CS domain protocol stack (C-plane)

with Legacy A interface
Confidential
15
CS Domain Control Plane With SIGTRAN
BTS
BSC
Abis
Abis L3
Abis L3
MSC
BSSMAP
BSSMAP
SCCP
SCCP
IUA
IUA
M3UA
M3UA
SCTP
SCTP
SCTP
SCTP
IP
IP
IP
IP
ML/MC-PPP
ML/MC-PPP
HDLC
HDLC
Eth L2
Eth L2
TDM L1
TDM L1
Eth L1
Eth L1
Packet Abis over TDM; CS domain protocol stack (C-plane)

with SIGTRAN at A interface
Confidential
16
PS Domain User Plane

MS
BTS
Um
BSC
Abis
SGSN
Gb
Data application
TCP/UDP
IP
SNDCP
SNDCP
LLC
LLC
RLC
RLC
BSSGP
BSSGP
MAC
MAC
NS
NS
L1
L1
GSM L1
GSM L1
PA-FP
PA-FP
NSN muxd RTP
NSN muxd RTP
UDP
UDP
IP
IP
ML/MC-PPP
ML/MC-PPP
HDLC
HDLC
TDM L1
TDM L1
Packet Abis over TDM; PS domain protocol stack (U-plane)

with Legacy Gb interface
Confidential
17
PS Domain User Plane With Gb Over IP

MS
BTS
Um
BSC
Abis
SGSN
Gb
Data application
TCP/UDP
IP
SNDCP
SNDCP
LLC
LLC
RLC
RLC
BSSGP
BSSGP
MAC
MAC
NS
NS
GSM L1
GSM L1
PA-FP
PA-FP
NSN muxd RTP
NSN muxd RTP
UDP
UDP
IP
IP
UDP
UDP
ML/MC-PPP
ML/MC-PPP
IP
IP
HDLC
HDLC
Eth L2
Eth L2
TDM L1
TDM L1
Eth L1
Eth L1
Packet Abis over TDM; PS domain protocol stack (U-plane)

with Gb over IP interface
Confidential
18
PS Domain Control Plane

MS
BTS
Um
BSC
Abis
SGSN
Gb
GMM/SM
LLC
LLC
RLC
RLC
BSSGP
BSSGP
MAC
MAC
NS
NS
L1
L1
GSM L1
GSM L1
PA-FP
PA-FP
NSN muxd RTP
NSN muxd RTP
UDP
UDP
IP
IP
ML/MC-PPP
ML/MC-PPP
HDLC
HDLC
TDM L1
TDM L1
Packet Abis over TDM; PS domain protocol stack (C-plane)

Confidential
19
Management Plane
BTS
BSC
Abis
Abis O&M
Abis O&M
IUA
IUA
SCTP
SCTP
IP
IP
ML/MC-PPP
ML/MC-PPP
HDLC
HDLC
TDM L1
TDM L1
Packet Abis over TDM; O&M signaling protocol stack (M-plane)
Confidential
20
Packet Abis over PSN
Confidential
21
CS Domain User Plane
BTS
BSC
Abis
TC
Ater
MSC
Transcoding
Codec
NSN muxd RTP
Codec
NSN muxd RTP TRAU frame
UDP
UDP
IP
IP
Eth L2
Eth L2
Eth L1
Eth L1
TDM L1
G.711
G.711
TDM L1
TDM L1
TRAU frame
TDM L1
Packet Abis over PSN; CS domain protocol stack (U-plane)
Confidential
22
CS Domain Control Plane
BTS
BSC
Abis
Abis L3
Abis L3
IUA
IUA
SCTP
SCTP
IP
IP
Eth L2
Eth L2
Eth L1
Eth L1
MSC
BSSMAP
BSSMAP
SCCP
SCCP
MTP
MTP
TDM L1
TDM L1
Packet Abis over PSN; CS domain protocol stack (C-plane)

with Legacy A interface
Confidential
23
CS Domain Control Plane With SIGTRAN
BTS
BSC
Abis
Abis L3
Abis L3
MSC
BSSMAP
BSSMAP
SCCP
SCCP
IUA
IUA
M3UA
M3UA
SCTP
SCTP
SCTP
SCTP
IP
IP
IP
IP
Eth L2
Eth L2
Eth L2
Eth L2
Eth L1
Eth L1
Eth L1
Eth L1
Packet Abis over PSN; CS domain protocol stack (C-plane)

with SIGTRAN at A interface
Confidential
24
PS Domain User Plane
MS
BTS
Um
BSC
Abis
SGSN
Gb
Data application
TCP/UDP
IP
SNDCP
SNDCP
LLC
LLC
RLC
RLC
BSSGP
BSSGP
MAC
MAC
NS
NS
L1
L1
GSM L1
GSM L1
PA-FP
PA-FP
NSN muxd RTP
NSN muxd RTP
UDP
UDP
IP
IP
Eth L2
Eth L2
Eth L1
Eth L1
Packet Abis over PSN; PS domain protocol stack (U-plane)

Confidential
25
PS Domain User Plane With Gb Over IP

MS
BTS
Um
BSC
Abis
SGSN
Gb
Data application
TCP/UDP
IP
SNDCP
SNDCP
LLC
LLC
RLC
RLC
BSSGP
BSSGP
MAC
MAC
NS
NS
GSM L1
GSM L1
PA-FP
PA-FP
NSN muxd RTP
NSN muxd RTP
UDP
UDP
UDP
UDP
IP
IP
IP
IP
Eth L2
Eth L2
Eth L2
Eth L2
Eth L1
Eth L1
Eth L1
Eth L1
Packet Abis over PSN; PS domain protocol stack (U-plane)

with Gb over IP interface
Confidential
26
PS Domain Control Plane
MS
BTS
Um
BSC
Abis
SGSN
Gb
GM/SM
LLC
LLC
RLC
RLC
BSSGP
BSSGP
MAC
MAC
NS
NS
L1
L1
GSM L1
GSM L1
PA-FP
PA-FP
NSN muxd RTP
NSN muxd RTP
UDP
UDP
IP
IP
Eth L2
Eth L2
Eth L1
Eth L1
Packet Abis over PSN; PS domain protocol stack (C-plane)

Confidential
27
PS Domain Control Plane With Gb Over IP
MS
BTS
Um
BSC
Abis
SGSN
Gb
GM/SM
LLC
LLC
RLC
RLC
BSSGP
BSSGP
MAC
MAC
NS
NS
GSM L1
GSM L1
PA-FP
PA-FP
NSN muxd RTP
NSN muxd RTP
UDP
UDP
UDP
UDP
IP
IP
IP
IP
Eth L2
Eth L2
Eth L2
Eth L2
Eth L1
Eth L1
Eth L1
Eth L1
Packet Abis over PSN; PS domain protocol stack (C-plane)

with Gb over IP
Confidential
28
Management Plane
BTS
BSC
Abis
Abis O&M
Abis O&M
IUA
IUA
SCTP
SCTP
IP
IP
Eth L2
Eth L2
Eth L1
Eth L1
Packet Abis over PSN; O&M signaling protocol stack (M-plane)
Confidential
29
Possible Scenarios
There are two possible scenarios pertaining to Packet Abis
feature:
Packet Abis using IP over TDM based backhaul (e.g. E1/T1)
Packet Abis using IP over PSN based backhaul (e.g. Ethernet)
Confidential
30
RG10
Scenario A: Legacy and PWE CESoPSN
BSC
Legacy Abis
TDM
TDM
TDM
TDM
TCSM
Ater
TDM
TDM
TDM
Legacy Abis (PWE3)

PWE
IPoEth
IPoEth
Any vendors
MGW
PWE
PWE
PWE
PWE
Gateway
PWE
*A.2200
Alternative interface
Mixed mode (TDM / Ethernet) possible

BSC3i 1000/2000 or FlexiBSC required
Confidential
31
MGW
RG10
Scenario A1: with TC in MGW
Legacy Abis
TDM
TDM
TDM
NSN
MGW
BSC
TDM
TDM
Ater
PWE
Gateway
Legacy Abis
PWE
IPoEth
IPoEth
PWE
TC
PWE
*A.2200
Packet / TDM conversion

Mixed mode (TDM / Ethernet) possible

Confidential
32
MGW
RG20
Scenario B: Packet Abis and A over IP (TC

in BSS)
PAbis oTDM
TDM
IPoTD
IPoTD
MM
BSC
TCSM
TDM
PAbis oEth
Eth
IPoEth
IPoEth
Ater
Eth
Any vendors
MGW
TDM
TDM
PWE
PWE
TDM
MGW
Eth
Legacy Abis
TDM
AoIP
TDM
(G.711)
TC in BSS
TDM
TDM
PWE capabilities (Abis/A) same, but partly not shown due to simplicity reasons
Any mixed mode possible
Confidential
33
RG20
Scenario C1: Packet Abis and A over IP
Any vendors
MGW
PAbis oTDM
TDM
IPoTD
IPoTD
MM
BSC
TDM
AoIP
Eth
PAbis oEth
Eth
IPoEth
IPoEth
TCSM
Eth
TDM
Legacy Abis
TDM
(CodecX )
TC in MGW
TDM
Ater
PWE
TC
MGW
A
TDM
TDM
PWE
Eth
TDM
TDM
AoIP
(G.711)
TC in BSS
PWE capabilities (Abis/A) same, but partly not shown due to simplicity reasons
except Legacy Abis <-> AoIP (TC in MGW)
Confidential
34
RG20
Scenario C2: RG20

Packet Abis and A over IP
NSN
MGW
PAbis oTDM
TDM
IPoTD
IPoTD
MM
BSC
TDM
(CodecX )
TC in MGW
PAbis oEth
Eth
IPoEth
IPoEth
Eth
TDM
Ater
TDM
MGW
PWE
Gateway
PWE
Legacy Abis
TC
AoIP
Eth
TDM
*A.2200
TDM
TDM
PWE Legacy Abis capabilities same, but not shown due to simplicity reasons
except Legacy Abis <-> AoIP (TC in MGW)
* RG10 late feature

Confidential
35
Scenario C: RG30 Study item

All Abis types and A over IP (TC in MGW)
Any vendors
MGW
PAbis oTDM
TDM
RG30
IPoTD
IPoTD
MM
BSC
TDM
PAbis oEth
Eth
IPoEth
IPoEth
Eth
(CodecX )
TC in MGW
Legacy Abis
TDM
AoIP
Eth
MGW
TC
TC
TDM
TDM
TDM
PWE Legacy Abis capabilities same, but not shown due to simplicity reasons
Confidential
36
Packet Abis - HW/SW Requirements

Supported in BSC3i 1000/2000 and FlexiBSC (new and
upgraded)
New ETP unit needed
Supported in FlexiEDGE BTS and FlexiMultiradio BTS

Media conversion (legacy Abis) to PWE3 CESoPSN
supported for co-sited UltraSite / BTSplus.

A BTS site (BCF) operates either in Dynamic Abis or Packet
Abis mode.
Supported with PCU2-D and PCU2-E
A single PCU operates either in Dynamic Abis or Packet Abis mode.
Confidential
37
RG20
A over IP Implementation Scenarios

(RG20)
ETP
Packet Abis + AoIP

TC in MGW
Eth
ETP-A
Packet Abis
over IP
Eth
A
over IP
Core
A
over IP
Core
A
over IP
Core
FlexiEDGE
ETS2 ETP
Packet Abis + AoIP

TC in BSS
TCSM3i
ETP-A
Packet Abis
over TDM
TDM
FlexiEDGE
Flexi BSC or BSC3i 1000/2000
TCSM3i
ETP-A
Legacy Abis + AoIP

TC in BSS
Confidential
38
BTS
Legacy Abis
AoIP interfaces in S15
ETPA
PAbis oEth
AoIP (FI) U-plane

Compressed codecs
Eth
MGW
BSC
Eth
Nb
TCSM
ETPE
ETPC
PAbis oTDM
TDM
ETPT
G
S
W
B
Ater
TDM
Eth
AoIP (PI) U-plane

G.711/CS Data
TDM
TDM
Legacy Abis
AoTDM (PT)
G.711/CS Data
TDM
Mc
AoIP C-plane
Confidential
39
Presentation
/ Author
Date
6.
Multi-operator
BSS /(MOBSS)
/ KH /03 2009 / RN2009
MSS
A over IP
Description:
The A-interface between BSS and MGW will be based on IP / Ethernet
3GPP Rel-8 defines two basic scenarios for AoIP functionality:
AoIP Transcoder in the BSS
The G.711 / RTP / IP protocol is employed
Supported in TCSM3i (stand-alone and combi)
AoIP Transcoder in the Core Network (MGW)
The CODECx / RTP / IP protocol is employed
Supported only with Packet Abis in S15
Benefits:
Simplifies the system configuration in Multipoint A / Flexible A scenarios
Improved transport efficiency and speech quality for the Transcoder in the Core
Network scenario through standardising TrFO for GSM/EDGE
Confidential
40
A-interface Alternatives
MSS
BSSAP/
SIGTRAN
AoIP (TC in MGW)
BSC
BTS
TCSM
BTS
Abis
(TDM/IP)
BTS
MGW
AoIP (TC in MGW):

CodecX
TrFO
TC
TFO
AoIP (TC in BSS)
AoIP
(IP)
BTS
Abis
(TDM/IP)
H.248
BSSAP, RANAP,
ISUP, BICC, SIP-I
RTP
UDP
Peer
System
IP
A, Ater, AoIP,
Iu, Nb, Nb(SIP-I) or PSTN
AoIP (TC in BSS):

G.711
RTP
UDP
Legacy A
(TDM,
G.711)
IP
TC
Ater
(TDM)
BSC
Confidential
41
Ater
(TDM)
GSM EFR, GSM FR, GSM HR,

CodecX = FR AMR, HR AMR,
FR AMR-WB, Clearmode
PWE Concept
Confidential
42
Pseudo Wire Emulation End-to-End

(PWE3)
Overview on PWE3
PWE3 is standardized mechanism which emulates the essential attributes of a
service into Packet Switched Network (PSN)
-
different services can be emulated by PWE3, e.g. TDM, Frame Relay, ATM, SDH/SONET
emulation basically means conversion of the TDM traffic to packets according to PWE3
PWE3 of TDM traffic is referred to as CESoPSN (Circuit Emulation Services over PSN)
the required functions of PWE3 include

-
encapsulating service-specific set of information (=> forming PW) arriving at an ingress port,
carrying the PW transparently across a communication path (PSN tunnel),
managing the PWs timing and order,
re-converting to the original signal (native service) in the far end of the PSN tunnel
PWE3 does not intend to guarantee that the emulated service will be
indistinguishable from its origin (i.e. the one which is subject to emulation)
-
the emulation must be sufficient for the proper operation of the service with required QoS
the emulation introduces a trade-off between cost (bandwidth) and performance (delay)
Confidential
43

(PWE3)
PWE3 reference model (1/2)
Customer Edge (CE)
a device where a native service originates and/or terminates

the CE is not aware that it is using an emulated service rather than a native one
Provider Edge (PE)
a device that provides PWE3 to CE
PSN tunnel
a path over PSN which the content of one or more PWs is conveyed through
PW
a set of PDU sent through the PSN tunnel that contains all of the data (i.e. payload and control information) required
to provide the desired service
Confidential
44

(PWE3)
PWE3 reference model (2/2)
PSN-bound
CE-bound
CE1
CE2
PE1
PE2
Customer Edge
Provider Edge
AC
Native service
AC
PSN Tunnel
Packet Switched Network
Attachment Circuit
PW
Pseudowire
PSN bound
traffic direction in which information derived from a native service (in a CE) are adapted to a PW (and next, when
formed, PW PDUs are sent through PSN tunnel)
CE bound
traffic direction in which data conveyed through PW PDUs are received, processed, re-converted back to the native
service and delivered to a CE
Native service
a service which is subject to emulation (i.e. TDM signal in case of the feature)
Attachment Circuit (AC)

the physical (or logical) circuit linking a PE to the CE (e.g. connection within the HW module responsible for PWE3)
Confidential
45
PWE3 realization in BSS: CESoPSN

General feature information
Overview on CESoPSN functionality

Circuit Emulation Service over PSN performs the following activities:
-
the TDM bit stream is segmented according to the user specified TSS
- bits transmitted by indicated PCM TS in subsequent TDM frames
headers are added to each segment to form a manageable packet (encapsulation)
packets are forwarded to the PSN tunnel and transmitted to its destination over Ethernet network
at destination, the original bit stream is reconstructed by removing headers, concatenating frames
and regenerating the timing
an E1 line
TDM frame #1
TS31
Ch24
Ch2
TS1
Ch1
TS0
TDM frame #2
TS31
Ch24
Ch2
TS1
Ch1
TS0
TDM frame #3
TS31
Ch24
Ch2
TS1
Ch1
TS0
a resulting PW (also called CESoPSN packet)

- 3 TDM frames mapped
- PW composed of 31 TS
Ch24
TS31
Ch2
TS2
Ch24
Ch1 TS31
TS1
Ch2
TS2
payload
TSS composed of 31 TS
Confidential
46
Ch1 TS31
TS1
Ch24
Ch2
TS2
Ch1
TS1
CESoPSN Header
header
Ref. P. Spennemann, Internal Ethernet/IP Interfaces for BSS
Feature Request Sheet, FRS 94060, version 2.0, May 2007
CESoPSN
Structure of payload (1/3)

PCM basics
125 s
TS 0 TS 1 TS 2 TS 3 TS 4 TS 5 TS 6 TS 7
8 bits
encoding resolution
sampling frequency
1 TS 8 bit 8 kHz = 8 bit / 125 s = 64 kbit/s
1 PCM30 32 64 kbit/s = 2.048 Mbit/s
Confidential
47
TS 31
CESoPSN
a PCM line is structured by a sequence of frames, a TDM frame lasts 125 s and carries 32
channels of 64 kbps (in case of E1)
the feature allows to select a set of TSs from consecutively transmitted frames of
a given PCM line and to bundle them together into separate set (called TimeSlot map or
TimeSlot Set, TSS)
-
a user defines how many TSs and which particular ones form particular TSS, the selection is permanent, TS0 is always excluded
a user defines how many consecutive TDM frames contribute to a single Ethernet packet
this selection has impact on the required Ethernet bandwidth as well as introduced delay
a connection which transmits a TSS relevant contribution of chosen amount of frames is called Pseudo Wire (PW)
a PW is established between 2 Provider Edges (PEs) carried over PSN tunnel
Confidential
48
CESoPSN

the described structure preserves both the sequence of TSs within the particular TDM frame
as well as the sequence of frames
each CESoPSN packet gets a leading control word (CW) where a packet sequence number is
stored, this allows to preserve the sequence of CESoPSN packets as well
this allows to re-construct the original PCM data in the receiving end
Confidential
49
CESoPSN
CESoPSN protocol stack
standard version of CESoPSN protocol stack is shown below:
worst case protocol header
4
12
8
20
4
38 (26+12)
86
the protocol stack introduces (in the worst case) header with length of 86 bytes
-
different vendors may use modified protocol stacks, e.g. RTP is not supported in BSS14
thus in S14 implementation the header length is either 74 bytes or 70 bytes (depending on whether VLAN is enabled or not)
Confidential
50
Planning Parameter
Confidential
51
Packet Abis - C-plane protocol stack

Packet Abis over TDM; CS domain protocol stack (C-plane) with Legacy A
interface
Logical links:
OMU signaling link for each BCF
TRX signaling link for each TRX
ISDN Q.921 User Adaptation Layer (IUA)
Stream Control Transmissin Protocol
(SCTP)
Default port for OMUsig: minSctpPort =
49152
Default port for TRXi: minSctpPort =
49152 + i
Multi Link Multi Class Point to Point
protocol (ML/MC-PPP) bundles several
HDLC to form one large capacity recourse
HDLC object to allocate capacity from an
E1/T1 (BTS end definition must mact to
to BSC
end
one)
BSC
end
one)
Confidential
52
IP address for each BCSU

IP address for M-plane
IP address for C-plane
M-plane and C-plane IP address
may have the same value within a
BCSU (collapsed IP address)
Packet Abis - C-plane protocol stack

Packet Abis over TDM; CS domain protocol stack (C-plane) with SIGTRAN at A
interface
IP address for Flexi EDGE BTS

IP address for M-plane
IP address for C/U-plane
M-plane and C/U-plane IP
address may have the same value
(collapsed IP address)
Confidential
53
U-plane protocol stack

CS U-plane
PS U-plane
TRAU
handling
TRAU
handling
PCU
frame
PCU
frame
RTP 1)
RTP 1)
RTP 1)
RTP 1)
UDP
UDP
UDP
UDP
IP
IP
IP
IP
ML/MCPPP
Ethernet
ML/MCPPP
Ethernet
HDLC
L1
HDLC
L1
TDM L1
TDM L1
CS-UDP
mux port 2)
Note1) NSN specific multiplexing used

Confidential
54
RTP multiplexing parameters

(for optimization)
PS-UDP mux port
2)
BSC:
U-plane-IP address =
ETP-IP address
BTS:
U-plane IP address =
C-plane IP address
The Main plannable parameters

IUA (LAPD D-channels for OMUsig and TRXsig)
SAPI
TEI
SCTP (one for BCF + one for each TRX)
SCTP association
SCTP parameter set (Packet Abis Fast, Packet Abis Medium, Packet Abis over Satellite, user
defined set)
Source & Destination port number (Source port number = Destination port number on Abis
interface)
IP
Source and Destination IP address

DSCP to plane mapping (QoS)
ML/MC-PPP
MC-PPP class mapping (QoS)
HDLC (one per E1/T1, 1 to 8 per BCF)
PCM-ID
Start TSL
BW
Confidential
55
Packet Abis SCTP association

Flexi EDGE BTS
TRX is associated with a BCSU

Balancing the BCSU load (up to 500
TRX per Flexi BSC BCSU)
Both TRXs of a dual TRX module to
the very same BCSU
BCF is associated with a BCSU
SCTP association
SRC/SDT IP address and SRC/DST
UDP port number
Default port for OMUsig:
minSctpPort = 49152
Default port for TRXi: minSctpPort =
49152 + i
Packet Abis site
Confidential
56
Flexi BSC
BCF
TRX1
TRX3
TRX5
DTRX
DTRX
DTRX
BCSU
TRX2
BCSU
TRX4
BCSU
TRX6
BCSU
Flexi EDGE BTS

BCF
TRX1
TRX3
TRX5
DTRX
DTRX
DTRX
TRX2
TRX4
TRX6
BCSU
Benefits
Confidential
57
Dynamic Abis today
Legacy TDM
PWE CESoPSN
Each voice channel is allocated to a dedicated air interface channel

PWE transports timeslots snapshots (empty or not)
Constant bandwidth need!!
Some savings can be achieved (unallocated timeslots by configuration)
Confidential
58
Packet Abis pools all traffic types
Almost same packets in TDM and Ethernet options
TDM: All timeslots/E1 are pooled single bit-pipe

similar to Ethernet media
No dedicated bandwidth reserved
TRAU framing and bit stuffing removed
No empty packets are sent (Unused, silence )
Confidential
59
Packet Abis - Benefits

The bandwidth savings achieved are significant due to only transferring
packets that contain data, compared with the previous technology that
required empty timeslots to maintain a constant bit rate.
Abis bandwidth gains are achieved by
Removing unneeded bits and header information from TRAU/PCU frames
Savings due to silence frames are shorter
All traffic (CS- and PS u-planes, c-plane (TRXSIGs) and m-plane (OMUSIGs))
pooled to the same bandwidth (multiplexing gain)

Bandwidth required depends on actual need (no longer constant)
Multiplexing of traffic to same packets
Header compression
Aggregation and oversubscription possible in the network
Cost of transmission
Ethernet transport is cost efficient in many areas
Efficient utilization of the current TDM transport
CS voice quality and CS data throughput not affected
Confidential
60

Module 2 Protocol Stackv1

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Module 2 Protocol Stackv1

Diunggah oleh

Hak Cipta:

Format Tersedia

Module4

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

All IP/ Ethernet in NSN 2G Radio Access elements

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

What basically is Packet Abis?

Codec is packed into packet directly instead of TRAU frame

(no dedicated allocation anymore)

Nothing is sent, when there is nothing to sent

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

Packet Abis Protocol Stack

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

New Transport Protocols For Packet Abis

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

New transport protocols for Packet Abis

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

ML PPP (Multi Link Point to Point Protocol)

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

MC PPP (Multi Class Point to Point Protocol),

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

Packet Abis over TDM

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

CS Domain User Plane

Packet Abis over TDM; CS domain protocol stack (U-plane)

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

CS Domain Control Plane

Packet Abis over TDM; CS domain protocol stack (C-plane)

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

CS Domain Control Plane With SIGTRAN

Packet Abis over TDM; CS domain protocol stack (C-plane)

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

PS Domain User Plane

NSN muxd RTP

NSN muxd RTP

Packet Abis over TDM; PS domain protocol stack (U-plane)

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

PS Domain User Plane With Gb Over IP

NSN muxd RTP

NSN muxd RTP

Packet Abis over TDM; PS domain protocol stack (U-plane)

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

PS Domain Control Plane

NSN muxd RTP

NSN muxd RTP

Packet Abis over TDM; PS domain protocol stack (C-plane)

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

Packet Abis over TDM; O&M signaling protocol stack (M-plane)

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

Packet Abis over PSN

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

CS Domain User Plane

Packet Abis over PSN; CS domain protocol stack (U-plane)

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

CS Domain Control Plane

Packet Abis over PSN; CS domain protocol stack (C-plane)

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009

CS Domain Control Plane With SIGTRAN

Packet Abis over PSN; CS domain protocol stack (C-plane)

6. Multi-operator BSS (MOBSS) / KH /03 2009 / RN2009