11 02 Cn3410ben33gln0 Bicc

CN3410BEN33GLN0
BICC
1
1 Nokia Siemens Networks CN3410BEN33GLN0
Bearer Independent Call Control - BICC
Switching Core Network Signalling
M14/U4
CN3410BEN33GLN0
BICC
2
Nokia Siemens Networks Academy
Legal notice
Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Siemens Networks training
documentation, product documentation and slide presentation material, all of which are forthwith
known as Nokia Siemens Networks training material, are the exclusive property of Nokia
Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification,
translation, adaptation or derivatives including any improvements or developments. Nokia
Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license,
sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals
can use the Nokia Siemens Networks training material for their own personal self-development
only, those same individuals cannot subsequently pass on that same Intellectual Property to
others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens
Networks training material cannot be used outside of an agreed Nokia Siemens Networks
training session for development of groups without the prior written agreement of Nokia
Siemens Networks.
CN3410BEN33GLN0
BICC
3
Document change history
Customization for Orange (UK) Guido Schneiders 3 March 09
Small layout adaptations Guido Schneiders 2 Sept 08
Revised and update from M13 to M14/U4 Pubate Satienpoch 1 March 3, 08
Change comment Name Version Date
CN3410BEN33GLN0
BICC
4
BICC in 3GPP R4
MSC Server
H
.
2
4
8
I
P
MSC Server/
GCS
M
c
MGW
Nc
AAL2/AAL5
ATM
Nb
M
c
BICC CS-2
IP
MGW
RTP
IP
H
.
2
4
8
I
P
Control
plane
User
plane
or
CN3410BEN33GLN0
BICC
5
Bearer Independent Call Control - BICC
- call control protocol
- based on ISUP
- Separate set of procedures for call control signalling and transport of
bearer control signalling
- independent of
- bearer technology (e.g. IP, ATM)
- signalling message transport (e.g. MTP, MTP3b, SIGTRAN)
IP
BICC
ATM MTP1
SCTP SAAL MTP2
M3UA MTP3b MTP3
BICC over TDM BICC over ATM BICC over IP
CN3410BEN33GLN0
BICC
6
For IP backbones: bearer-information is transferred between MSSs in BICC
through APM-mechanism
MGW MGW MGW MGW
MSC Server MSC Server
MSC Server MSC Server
IP
SCTP
M3UA
BICC
IAM IAM
Sigtran Sigtran
.
.
IP address: 192.168.3.2
Port: 5964
Codec: AMR mode 7
.
.
.
.
IP address: 192.168.3.2
Port: 5964
Codec: AMR mode 7
.
.
Bearer information
carried inside call
control messages
Bearer information
carried inside call
control messages
IP: 192.168.3.2
port: 5964
IP: 192.168.3.2
port: 5964
BICC in 3GPP R4
CN3410BEN33GLN0
BICC
7
BICC Functional Blocks
CSF
BCF
Call Control
Signalling
Bearer Control
Signalling
BIWF
Bearer
SN
C
a
l
l

B
e
a
r
e
r

C
o
n
t
r
o
l
S
i
g
n
a
l
l
i
n
g

(
C
B
C
)
CSF
BCF
Call Control
Signalling
BIWF
SN
C
a
l
l

B
e
a
r
e
r

C
o
n
t
r
o
l
S
i
g
n
a
l
l
i
n
g

(
C
B
C
)
CSF
CMN
Bearer
SN : Serving Node Call Service Function (CSF) with associated Bearer Control Function (BCF)
CMN : Call Mediation Node CSF without associated BCF
BIWF : Bearer Inter-working Function, provides BCF and media mapping/switching function
Control
plane
User
plane
CN3410BEN33GLN0
BICC
8
Bearer Establishment Modes
MSS MSS
Forward
Backward
MSS
MGW
MSS
MGW
Bearer establishment direction
Bearer establishment direction
BICC:IAM
BICC:IAM
CN3410BEN33GLN0
BICC
9
Two ways to establish a bearer
1) ATM: separate bearer control signalling: AAL-Type-2 Signalling
2) IP: bearer information tunneled in call- and call bearer control
messages: IPBCP
Bearer Control Signalling
MSS MSS
Call Control Signalling
BICC or SIP
e.g: AAL2 signalling
IP backbone:
the IPBCP protocol is tunneled
inside H.248 and BICC (or SIP)
via the MSC Servers.
H.248
ATM backbone:
separate bearer control
signalling: AAL-Type-2
signalling
H.248
MGW MGW
CN3410BEN33GLN0
BICC
10
BICC call control related messages -1-
Q1902.3
Pre-Release Information 0100 0010 PRI
Initial Address Message 0000 0001 IAM
Information Request 0000 0011 INR
Information 0000 0100 INF
Identification Response 0011 0111 IRS
Identification Request 0011 0110 IDR
Connect 0000 0111 CON
Call Progress 0010 1100 CPG
Continuity 0000 0101 COT
Application Transport Message 0100 0001 APM
Answer Message 0000 1001 ANM
Address Complete Message 0000 0110 ACM
Description Code Message
CN3410BEN33GLN0
BICC
11
BICC call control related messages -2-
Q1902.3
User-to-User Information 0010 1101 USR
Suspend 0000 1101 SUS
Segmentation 0011 1000 SGM
Subsequent Address Message 0000 0010 SAM
Release Complete 0001 0000 RLC
Resume 0000 1110 RES
Release 0000 1100 REL
CN3410BEN33GLN0
BICC
12
BICC Maintenance related messages -1-
Q1902.3
Circuit / CIC Group Query Response 0010 1011 CQR
Circuit / CIC Group Query Message 0010 1010 CQM
Circuit / CIC Group Unblocking
Acknowledgement
0001 1011 CGUA
Circuit / CIC Group Unblocking 0001 1001 CGU
Circuit / CIC Group Reset Acknowledgement 0010 1001 GRA
Circuit / CIC Group Reset 0001 0111 GRS
Circuit / CIC Group Blocking Acknowledgement 0001 1010 CGBA
Circuit / CIC Group Blocking 0001 1000 CGB
CN3410BEN33GLN0
BICC
13
BICC Maintenance related messages -2-
Q1902.3
Unequipped Circuit Identification Code 0010 1110 UCIC
Reset Circuit / CIC message 0001 0010 RSC
Facility Request 0001 1111 FAR
Facility Reject 0010 0001 FRJ
Facility 0011 0011 FAC
Facility Accepted 0010 0000 FAA
Confusion 0010 1111 CFN
CN3410BEN33GLN0
BICC
14
Format of BICC messages
Formats and codes for BICC protocols are specified in ITU-T Q.1902.3
They are very similar to ISUP messages.
Optional part
Mandatory variable part
Mandatory fixed part
Message type code
CIC
CN3410BEN33GLN0
BICC
15
Example: Initial Address Message (IAM)
incomplete
5-?
3-?
4-?
1
1
2
1
1
Length
octets
Information sent in either direction to allow the peer-to-peer
communication of application transport users (BAT-ASE)
O Application transport
Information generated on the access side of a call and
transfered transparently in either direction between
originating and terminating local nodes.
O Access transport
Received digits to identify the called party. V Called party number
Speech, 3.1kHz audio, 64kbit/s, Nx64kbit/s, 1920 kbit/s, 1536
kbit/s, etc.
F Transmission medium
requirement
Ordinary, payphone, prioroty, operator language. F Calling party's category
National/international call, end-to-end method indicator,
CCS7 interworking indicator, end-to-end information
availability, ISUP use indicator, ISUP preference indicator,
ISDN access indicator, SCCP method indicator.
F Forward call indicators
Satellite connection included, Continuity check required/not
required, echo control device included/not included
F Nature of connection
indicators
IAM F Message type
Description Type Parameter
F: mandatory fixed parameter; V: mandatory variable parameter; O: optional parameter
CN3410BEN33GLN0
BICC
16
CIC (Call Instance Code)
CIC in the BICC protocol is used to identify a signalling relation between peer BICC
entities and to associate all the PDUs to that relation.
CIC allocates a signalling message to the (virtual) channel, carrying the call.
Bilateral agreement is required with regard to the CIC values provisioned.
4 CIC
3 CIC
2 CIC
1 CIC
1 2 3 4 5 6 7 8
LSB
MSB
CN3410BEN33GLN0
BICC
17
Application Transport Mechanism APM -1-
APM (ITU-T Q.765.5) is used to transmit bearer related information in BICC
messages
The application, using APM for bearer control, is called Bearer Association
Transport Application Service Element (BAT- ASE)
The application is running in parallel to call control instance in the node
Application specific data may be sent in CC messages or as a separate APM
message.
appl
CC
appl
CC
CC message + application data
application data
CC message + application data
(e.g. BICC:IAM)
(e.g. BICC:APM)
(e.g. BICC:CPG)
CN3410BEN33GLN0
BICC
18
APM for BICC carries among others
Action indicator (forward/backward)
BNC ID (reference used to associate the bearer with a call)
BIWF address (MGW address)
Codec(s)
Tunneling related information (used/not used, bearer control payload)
Carried in APP parameter of various BICC call control messages:
ACM, ANM, APM, CPG, CON, IAM, PRI
MSS
IAM APP param param
e.g. IAM or APM
message
BAT-ASE
MSS
BAT-ASE
Application Transport Mechanism APM -2-
CN3410BEN33GLN0
BICC
19
Application Transport Parameter (APP)
Q.765.5
ch 11
Q.1902.3
ch 6.4
n
4
3a
3
2
1a
1
APM user information
Segmentation local reference ext.
APM Segmentation Indicator SI ext.
RCI SNI spare ext.
MSB ext.
LSB Application Context Identifier (05=BAT-ASE) ext.
1 2 3 4 5 6 7 8
m Identifier 2
Length indicator 2
Compatibility Information 2
Content 2
n
4
3
2
1
:
Content 1
Compatibility information 1
Length indicator 1
Identifier 1
1 2 3 4 5 6 7 8
Application context identifier 0000101 = BAT ASE
If ext=0 then octet 1a is present
RCI=Release Call Indicator (1=Release call)
SNI=Send Notification Indicator (=1 send notification)
APM segment indicator (000000=Final segment) otherwise represents segment
number.(000001 to 001001)
SI= Sequence Indicator (1=New sequence)
CN3410BEN33GLN0
BICC
20
Contents of APM identifiers -1-
Identifies the bearer used e.g. IP/RTP, AAL1, AAL2,
TDM etc.
Bearer Network
Connection
Characteristics
0000 0111
Has a field called Organization identifier and codec
information subfield. Subfield has information about
the codec type and codec configuration.
Single codec 0000 0101
In the codec list, single codec information elements
are listed in decreasing order of preference level.
Codec list 0000 0100
Interworking function address is in NSAP format
according to X.213 (BIWF Address).
Interworking function
address
0000 0011
The content is bearer specific with maximum length of
4 octets (BNC_ID).
Backbone network
connection identifier
0000 0010
Can have codes like connect forward, connect
backward etc. see separate slide
Action Indicator 0000 0001
Information IE name Value
CN3410BEN33GLN0
BICC
21
Contents of APM identifiers -2-
Indicates whether bearer redirection capability is
supported at sending node and also indicates options
within the capability.
Bearer redirection
capability
0000 1100
Duration of a signal in milliseconds. Duration 0000 1000
Indicates the signal type e.g. DTMF tones, dial tone,
ringing tone, busy tone etc.
Signal type 0000 1110
Signal to be applied Signal 0000 1011
Contains information about the BCU. It includes
Network ID and Local BCU-ID.
Bearer control unit
identifier
0000 1010
Indicates whether tunnelling is used or not Bearer control
tunnelling
0000 1001
Contains PDU (Protocol Data Unit) of BCTP
(see separate section)
Bearer control
information
0000 1000
Instructions on received, unrecognized information BAT compatibility
report
0000 0110
Information IE name Value
CN3410BEN33GLN0
BICC
22
Action Indicator: used for a lot of indications
Bearer Setup Control, for example
no indication
connect backward
connect forward
connect forward, no notification
connect forward plus notification required
Bearer Setup Indication, for example
connected
Codec Selection and Modification, for example
selected codec
modify codec
successful codec modification
codec modification failure
mid-call codec negotiation
DTMF Interaction, for example
start signal, notify
start signal, no notify
stop signal, notify
stop signal, no notify
CN3410BEN33GLN0
BICC
23
Action Indicator (AI): usage in BICC:IAM and
BICC:APM
IAM contains one of the following action indicator values:
connect forward or connect backward
APM (as IAM response) without codec negotiation:
connect forward, no notification
APM (as IAM response) with codec negotiation:
connect forward, no notification + selected codec,
selected codec
APM, if the out of band bearer establishment notification is requested from the peer MSS
without codec negotiation (i.e. BICC:APM notifies the peer MSS about an established
bearer):
connect forward, plus notification
APM, if the out of band bearer establishment notification is requested from the peer MSS
with codec negotiation:
connect forward, plus notification + selected codec
APM as out of band bearer establishment notification to the peer MSS:
connected
APM transferring only Bearer Control Information (IPBCP) in case of IP tunneling:
no action indicator.
CN3410BEN33GLN0
BICC
24
Codec list
ETSI 0x02
ITU-T 0x01
no indication 0x00
Single codec IE
Single codec IE
Single codec IE
CODEC LIST
Organization Identifier
Single Codec IE
Codec type (codec ID)
Codec configuration
UMTS AMR 0x05
UMTS AMR2 0x06
GSM HR AMR 0x04
GSM FR AMR 0x03
GSM EFR 0x02 G.711 (64 kbps, u-law) 0x02
GSM HR 0x01 G.711 (64 kbps, A-law) 0x01
GSM FR 0x00 No indication 0x00
ETSI ITU-T
Organization ID
Codec Type (Codec ID)
Only if codec
negotiation is used
ZJFI:
CN3410BEN33GLN0
BICC
25
BCTP Bearer Control Tunnelling Protocol
tunnelling bearer control protocols (BCP) through Nc and Mc interface
ITU-T Q.1990
In Rel.4 networks, IPBCP is tunnelled by means of BCTP through BICC
BCTP adds 2 octets - BCTP version indicator
- Tunnelled Protocol Indicator
CN3410BEN33GLN0
BICC
26
Tunneling bearer information
IPBCP
(Q.1970)
SDP
(RFC2327)
BCTP
(Q.1990)
APM
(Q.765.5)
BICC
(Q.1902.2)
IPBCP
(Q.1970)
SDP
(RFC2327)
BCTP
(Q.1990)
MEGACO
(H.248)
MGW MGW
MSS MSS
M3UA
SCTP
IP
SCTP
IP
Nc
Mc
IP_BB
Mc
CN3410BEN33GLN0
BICC
27
IPBCP IP Bearer Control Protocol
Establishes and allows the modification of IP bearers.
Encoded by Session Description Protocol (SDP; text)
Four messages:
Request - Sent by a BIWF to initiate an IP bearer establishment or
modification request.
Accepted - Sent by a BIWF that receives an IP bearer establishment or
modification message if it accepts the request.
Confused - Sent by a BIWF in response to an IP bearer
establishment or modification message if it cannot process
the received message.
Rejected - Sent by a BIWF in response to an IP bearer establishment or
modification message if it rejects the request
CN3410BEN33GLN0
BICC
28
IPBCP in SDP format acc. RFC2327
v= 0
o= - 0 0 IN IP4 10.33.16.136
s= IP Tunneling
c= IN IP4 10.33.16.136
t= 0 0
a= ipbcp:1 Request
m= audio 1026 RTP/AVP 96
a= rtpmap: 96 VND.3GPP.IUFP/16000
SDP
SDP version (v) : 0
Owner/Creator, Session ID (o) :
Owner Username : -
Session ID : 0
Session Version : 0
Owner Network Type : IN
Owner Address Type : IPv4
Owner Address : 10.33.16.136
Session name (s): IP Tunneling
Connection Information (c):
Connection Network Type : IN
Connection Address Type : IPv4
Connection Address : 10.33.16.136
Time Description, active time (t) :
Session Start Time : 0
Session Stop Time : 0
Session Attribute (a) :
Session Attribute Fieldname : ipbcp
IPBCP protocol version : 1
IPBCP command type : Request
Media Description, name and address (m):
Media Type : audio
Media Port : 1026
Media Proto: RTP/AVP
Media Format : 96
Media Attribute (a) :
Media Attribute Fieldname : rtpmap
Media Format : 96
MIME Type : VND.3GPP.IUFP
CN3410BEN33GLN0
BICC
29
Codecs represented in SDP
m=audio 1234 RTP/AVP 96
a=rtpmap:96 AMR/8000
a=fmtp:96 mode-set=1,2,3,4,5,6,7
AMR
a=rtpmap:4 G723/8000
G.723.1
a=rtpmap:0 PCMU/8000
G.711 u-law
a=rtpmap:8 PCMA/8000
G.711 A-law
a=rtpmap:3 GSM/8000
FR
a=rtpmap:103 GSM-EFR/8000
EFR
SDP representation Codec
a=rtpmap:4 G723/8000
a=fmtp:4 annexa=yes
G.723.1
Annex A
a=rtpmap:100 CLEARMODE/8000
Clearmode
a=rtpmap:97 iLBC/8000
iLBC
a=rtpmap:18 G729A/8000
a=fmtp:18 annexb=yes
G.729a
Annex B
a=rtpmap:18 G729A/8000
G.729a
SDP representation Codec
CN3410BEN33GLN0
BICC
30
Terms, describing call setup scenarios (1)
Forward call setup: The bearer connection at Nb is established in the same
direction as the initial call setup message at Nc (from A-side
MGW towards B-side MGW; SAI=FORW).
Backward call setup: The bearer connection at Nb is established in the opposite
direction as the initial call setup message at Nc (from B-side
MGW towards A-side MGW; SAI=BACK).
Delayed MGW selection: MGW selection method in the originating MSC Server when
the originating MGW is selected after the succeeding MSC
Server has selected the MGW (originating MGW selection is
based on the MGW of the succeeding MSS).
Forward bearer establishment.
SAI=DFORW, supported only with ATM bearer currently
CN3410BEN33GLN0
BICC
31
Terms, describing call setup scenarios (2)
Forward tunnelling: The initial bearer control protocol message (IPBCP:Request)
is tunneled in the same direction as the initial call setup
message at Nc (from A-side MGW towards B-side MGW).
Backward tunnelling: The initial bearer control protocol message (IPBCP:Request)
is tunneled in the opposite direction to the initial call setup
message at Nc (from B-side MGW towards A-side MGW).
Fast tunnelling: The initial bearer control protocol message (IPBCP:Request)
is exchanged in the first IAM APM message pair.
Delayed tunnelling: The initial bearer control protocol message (IPBCP:Request)
is exchanged in the second and third APM messages (i.e.
after the first IAM APM message pair).
CN3410BEN33GLN0
BICC
32
Note: The AddReply
and NotifyReq
commands are
conveyed in the same
H.248 message.
Note: The AddReply
and NotifyReq
commands are
H.248 message.
Forward IP bearer establishment with fast forward
tunneling, no codec negotiation
1
.
A
d
d
R
e
q
(
T
1
,

E
v
e
n
t
=
T
u
n
n
e
l

I
n
d
.
T
u
n
O
p
t
=
1
)
2
.
A
d
d
R
e
p
l
y
5. IAM(APP ( "connect forward", BCU-ID1, BNC Char:
IP/RTP BCI = IPBCP1, BCT = Tunneling to be used))
10. APM(APP ( "connect forward, no notifification",
BCU-ID2, BCI = IPBCP2))
1
1
.
M
o
d
d
R
e
q
(
I
P
B
C
P
2
)
1
2
.
M
o
d
R
e
p
l
y
19. ANM
14. NbUP Init
15. NbUP Init Ack
Fast forward tunneling is initiated only without codec negotiation and only with
forward bearer establishment.
3
.

N
o
t
i
f
y
R
e
q
(
I
P
B
C
P
1
)
4
.
N
o
t
i
f
y
R
e
p
l
y
8
.

N
o
t
i
f
y
R
e
q
(
I
P
B
C
P
2
)
9
.
N
o
t
i
f
y
R
e
p
l
y
18. ACM
ACM depends on
the terminating
side call setup in
MSS2.
1
5
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
6
.
N
o
t
i
f
y
R
e
p
l
y
1
6
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
7
.
N
o
t
i
f
y
R
e
p
l
y
6
.
A
d
d
R
e
q
(
T
2
,

E
v
e
n
t
=
T
u
n
n
e
l

I
n
d
,

T
u
n
O
p
t
=
1
,

I
P
B
C
P
1
)
7
.
A
d
d
R
e
p
l
y
SAI = FORW
UPD.STOM = DC
UPD.STOM = DC
13. User Plane established.
The purple parts are the IP
tunneling specific items.
The most efficient tunneled bearer establishment method in the terms of the network
resource usage. The Nc and Mc interface resource usage is optimised by
transporting the IPBCP PDUs inside the same protocol messages with the other call
control and bearer establishment related information.
Practical notes about the BIWF, BCU-ID, IPBCP information elements:
-T1 termination is reserved with AddReq message.
-The Event = TunnelInd parameter indicates that IP tunneling will be used.
-The TunOpt (Tunneling Option) = 1 (Same Message) indicates that fast
establishment will be done. Therefore the IPBCP routing info is requested in
the same message as the response to this AddReq.
-In Fast Forward tunneling case the TunOpt = 1 (Same Message) tunneling option
value is used in the AddReq H,248 message. That means that the IPBCP data is
requested in the same message as the AddReply, the IPBCP is transferred in the
NotifyReq. In this special case the AddReply and the NotifyReq are transferred in
one H.248 message. (See the H.248 protocol training for details.)
-BCU-ID1 (BCU-ID of MGW1) and the IPBCP are included in BICC: IAM message
-It is beneficial for influencing the MGW selection in MSS2 via the PBCU
attribute (equals to BCU-ID1) in the Preceding UPD determination analysis.
-The IPBCP1 is transferred to MSS2 in BICC: IAM message in the BCI
parameter.
-The BCT flag indicates that tunneling is used in this call setup.
-The IPBCP1 is transferred to MGW2 during the T2 termination creation in AddReq
sent by MSS2. The same TunOpt = 1 value is used here.
-The IPBCP2 is received from MGW2 by MSS2 in the NotifyReq message.
-Then the IPBCP2 is packed to the BCI parameter of the APM message towards
MSS1.
-Then the ModReq transfers the IPBCP2 to MGW1 from MSS1. The user plane is
established in this time.
CN3410BEN33GLN0
BICC
33
Forward IP bearer establishment with delayed forward
tunneling and codec negotiation
1
.
A
d
d
R
e
q
(
T
1
,

n
o

c
o
d
e
c
,

T
u
n
O
p
t
=
2
)
2
.
A
d
d
R
e
p
l
y
3. IAM(APP ( "connect forward", BCU-ID1, BNC Char: IP/RTP,
BCT = Tunneling to be used, supported codec list))
4
.
A
d
d
R
e
q
(
T
2
,

c
o
d
e
c
,

T
u
n
O
p
t
=
2
)
5
.
A
d
d
R
e
p
l
y
6. APM(APP ( "connect forw, no notif+sel cdc", BCU-ID2,
selected codec, available codec list))
1
7
.
M
o
d
R
e
q
(
I
P
B
C
P
2
)
1
8
.
M
o
d
R
e
p
l
y
25. ANM
20. NbUP Init
21. NbUP Init Ack
Delayed forward tunneling is initiated only with codec negotiation.
9
.

N
o
t
i
f
y
R
e
q
(
I
P
B
C
P
1
)
1
0
.
N
o
t
i
f
y
R
e
p
l
y
1
4
.

N
o
t
i
f
y
R
e
q
(
I
P
B
C
P
2
)
1
5
.
N
o
t
i
f
y
R
e
p
l
y
24. ACM
ACM depends on
the terminating
side call setup in
MSS2.
7
.
M
o
d
d
R
e
q
(
E
s
t
a
b
l
i
s
h

B
N
C
,

s
e
l
e
c
t
e
d

c
o
d
e
c
,

E
v
e
n
t
=
T
u
n
n
e
l

I
n
d
.
)
8
.
M
o
d
R
e
p
l
y
1
2
.
M
o
d
R
e
q
(
I
P
B
C
P
1
,
E
v
e
n
t
=
T
u
n
n
e
l

I
n
d
,
)
1
3
.
M
o
d
R
e
p
l
y
11. APM(APP (BCI = IPBCP1))
2
2
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
2
3
.
N
o
t
i
f
y
R
e
p
l
y
2
2
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
2
3
.
N
o
t
i
f
y
R
e
p
l
y
SAI = FORW
UPD.STOM = CN
UPD.STOM = CN
The delayed forward tunneling establishment method offers a separate negotiation phase about the
bearer control tunneling usage before the actual bearer control protocol PDU exchange between the
MGWs takes place. In practice the negotiation is not considered to bring benefit in the current networks
where the bearer control tunneling is used exclusively for establishing IP bearer connections and the only
means for IP bearer connection establishment is by using IPBCP tunneling. See ITU-T Q.1902.4,
chapters 7.4.4 and 7.5.4 for more details about the different options.
The negotiation phase can also be utilised with the codec negotiation to negotiate the selected speech
codec before the bearer establishment. The IPBCP is based on the Session Description Protocol (SDP)
and includes Media Announcement and Media Attributes that can in some environments be dependent
on the used speech codec; therefore the speech codec should be known before the tunneled bearer
establishment. In the pure 3GPP environment this is not necessarily significant because the Media
Announcement and Media Attributes always follow the same encoding that is defined in the 3GPP TS
29.414. See ITU-T Q.1970 and 3GPP TS 29.414 for more information about the IPBCP and its usage in
the 3GPP environment. However, depending on the MGW implementation, it may be a requirement that
the selected codec is known before the bearer establishment.
The delayed forward tunneling establishment method also offers a possibility for the originating MSS to
delay the selection of the MGW and the reservation of the Nc interface resource until the tunneling usage
has been verified with the succeeding MSS, possibly the identity of the succeeding MSS selected MGW
is known and the selected codec is known. The information about the identify of the succeeding MSS
selected MGW and the selected codec can be used for optimising the MGW selection by the originating
MSS.
The possibility to negotiate the selected speech codec before bearer establishment and to delay the
MGW selection by originating MSS are considered the main benefits of this bearer establishment
method.
Because of these benefits NSN recommends using the delayed forward tunneling establishment with
calls that include codec negotiation. The delayed MGW selection is currently left for further development.
The most efficient tunneled bearer establishment method in the terms of the network resource usage.
The Nc and Mc interface resource usage is optimised by transporting the IPBCP PDUs inside the same
protocol messages with the other call control and bearer establishment related information.
Because of the efficient network resource usage NSN recommends using the fast forward tunneling
establishment with calls that do no include codec negotiation.
Practical notes about the BIWF, BCU-ID, IPBCP information elements (in addition to the description
written to the fast forward tunneling):
-In Delayed Forward tunneling case the TunOpt = 2 (Any Time) tunneling option value is used in the
AddReq H,248 message. That means that the IPBCP data is requested in later phase of the call setup.
-Later, the EstablishBNC signal instructs the MGW that the IPBCP information is needed in the MSS.
-EstablishBNC is set in the ModReq message.
-Therefore, the IPBCP is transferred to the MSS in a NotifyReq after ModReply.
-The IPBCP exchange is performed in the second half of the bearer establishment period.
CN3410BEN33GLN0
BICC
34
Note: The AddReply
and NotifyReq
commands are
H.248 message.
Forward IP bearer establishment with fast forward
1. IAM(APP ( "connect forward", BCU-ID1, BNC char:
IP/RTP BCI = IPBCP1, BCT = Tunneling to be used,
supported codec list))
2
.
A
d
d
R
e
q
(
T
2
,

E
v
e
n
t
=
T
u
n
n
e
l

I
n
d
,

T
u
n
O
p
t
=
1
,

I
P
B
C
P
1
)
3
.
A
d
d
R
e
p
l
y
6. APM(APP ( "connect forw, no notif.+sel codec", BCU-
ID2, BCI = IPBCP2, selected codec, available codec list))
13. ANM
8. NbUP Init
9. NbUP Init Ack
4
.

N
o
t
i
f
y
R
e
q
(
I
P
B
C
P
2
)
5
.
N
o
t
i
f
y
R
e
p
l
y
12. ACM
ACM depends on
the terminating
side call setup in
MSS2.
Fast forward tunneling with codec
negotiation is never initiated by NSN MSC
Server.
It is supported only on the terminating
side (MSS2).
Differences in red
compared to the
previous slide.
Other vendors
MSC Server
1
0
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
1
.
N
o
t
i
f
y
R
e
p
l
y
UPD.STOM = CN
The codec negotiation related differences are highlighted on this slide. It is quite
similar to the ATM BB related slide.
CN3410BEN33GLN0
BICC
35
Forward IP bearer establishment with delayed forward
1. IAM(APP ( "connect forward", BCU-ID1, BNC Char:
IP/RTP, BCT = Tunneling to be used))
4. APM(APP ( "connect forw, no notif", BCU-ID2))
17. ANM
12. NbUP Init
13. NbUP Init Ack
16. ACM
ACM depends on
the terminating
side call setup in
MSS2.
Delayed forward tunneling without codec
Server.
It is supported only on the terminating
side (MSS2).
Differences in red
compared to the
previous slide.
Other vendors
MSC Server
UPD.STOM = DC
2
.
A
d
d
R
e
q
(
T
2
,

c
o
d
e
c
,

T
u
n
O
p
t
=
2
)
3
.
A
d
d
R
e
p
l
y
8
.

N
o
t
i
f
y
R
e
q
(
I
P
B
C
P
2
)
9
.
N
o
t
i
f
y
R
e
p
l
y
6
.
M
o
d
R
e
q
(
I
P
B
C
P
1
,
E
v
e
n
t
=
T
u
n
n
e
l

I
n
d
,
)
1
4
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
5
.
N
o
t
i
f
y
R
e
p
l
y
7
.
M
o
d
R
e
p
l
y
CN3410BEN33GLN0
BICC
36
Backward IP bearer establishment with fast forward
1. IAM(APP ( "connect backward", BCU-ID1, BNC Char:
IP/RTP, BCT = Tunneling to be used, BCI = IPBCP1))
2
.
A
d
d
R
e
q
(
T
2
,

c
o
d
e
c
,

I
P
B
C
P
1
,
T
u
n
O
p
t
=
1
,
E
v
e
n
t
=
T
u
n
n
e
l

I
n
d
)
3
.
A
d
d
R
e
p
l
y
12. ANM
8. NbUP Init
9. NbUP Init Ack
4
.

N
o
t
i
f
y
R
e
q
(
I
P
B
C
P
2
)
5
.
N
o
t
i
f
y
R
e
p
l
y
11. ACM
ACM depends on
the terminating
side call setup in
MSS2.
10. APM(APP (connected))
This case is similar to the Forward
bearer establishment with fast
forward tunneling case, the only
difference is the action indicator in
the IAM.
Fast forward tunneling with
backward bearer establishment is
never initiated by NSN MSC Server.
Other vendors
MSC Server
UPD.STOM = DC
CN3410BEN33GLN0
BICC
37
Backward IP bearer establishment with fast forward
1. IAM(APP ( "connect backward", BCU-ID1, BNC Char:
IP/RTP, BCT = Tunneling to be used, BCI = IPBCP1,
supported codec list))
2
.
A
d
d
R
e
q
(
T
2
,

c
o
d
e
c
,

I
P
B
C
P
1
,

T
u
n
O
p
t
=
1
)
3
.
A
d
d
R
e
p
l
y
13. ANM
9. NbUP Init
10. NbUP Init Ack
4
.

N
o
t
i
f
y
R
e
q
(
I
P
B
C
P
2
)
5
.
N
o
t
i
f
y
R
e
p
l
y
12. ACM
ACM depends on
the terminating
side call setup in
MSS2.
11. APM(APP (connected))
Fast forward tunneling with backward
bearer establishment is never initiated by
NSN MSC.
Codecs and IPBCP can be sent back in 1
APM message (instead of 2 APM
messages) according to the standards.
NSN MSC Server prefers the version with 2
APM messages.
Differences in red compared
to the previous slide.
Other vendors
MSC Server
6. APM(APP (selected codec,
UPD.STOM = CN
CN3410BEN33GLN0
BICC
38
Backward IP bearer establishment with delayed backward
1. IAM(APP ( "connect backward", BCU-ID1,
BNC Char: IP/RTP, BCT = Tunneling to be used))
2
.
A
d
d
R
e
q
(
T
2
,

c
o
d
e
c
,

E
v
e
n
t
=
T
u
n
n
e
l

I
n
d
T
u
n
O
p
t
=
1
,

E
s
t
a
b
.

B
e
a
r
e
r
)
3
.
A
d
d
R
e
p
l
y
16. ANM
4
.

N
o
t
i
f
y
R
e
q
(
I
P
B
C
P
2
)
5
.
N
o
t
i
f
y
R
e
p
l
y
15. ACM
ACM depends on
the terminating
side call setup in
MSS2.
8
.
M
o
d
R
e
q
(
I
P
B
C
P
1
)
9
.
M
o
d
R
e
p
l
y
Delayed backward tunneling without
codec negotiation is never initiated by
NSN MSC Server. It is supported only on
the terminating side (MSS2).
Other vendors
MSC Server
1
3
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
4
.
N
o
t
i
f
y
R
e
p
l
y
UPD.STOM = DC
11. NbUP Init
12. NbUP Init Ack
NbUP (IuUP also)
initialisation is executed
end-to-end and it is always
done in forward direction
regardless of the bearer
establishment direction.
The delayed backward tunneling establishment method does not offer similar
negotiation about the bearer control tunneling usage as the delayed forward
tunneling establishment method does. Nor does it offer the possibility for delayed
MGW selection by the originating MSS or the efficiency of the fast forward
establishment method. See ITU-T Q.1902.4, chapters 7.4.5 and 7.5.5 for more
details about the different options.
Similarly to the delayed forward tunneling establishment method the codec
negotiation can be completed before the bearer establishment.
It may be possible that the establishment method has interworking problems with the
Nb interface user plane protocol; since the bearer establishment is made in an
opposite direction compared to the Nb interface user plane protocol initialisation, it is
possible that the originating side MGW will start the initialisation attempts before the
bearer connection has been end-to-end established. This is due to the fact that the
originating side MGW will consider the establishment complete from its point of view
after sending the IPBCP Accepted message, however the bearer establishment is
not completed until the succeeding MGW has received and processed the message.
CN3410BEN33GLN0
BICC
39
Backward IP bearer establishment with delayed backward
1. IAM(APP ( "connect backward", BCU-ID1, BNC Char: IP/RTP,
BCT = Tunneling to be used, supported codec list))
17. ANM
16. ACM
ACM depends on
the terminating
side call setup in
MSS2.
Delayed backward tunneling with codec
Server. It is supported only on the
terminating side (MSS2).
Codecs and IPBCP can be sent back in 1
APM message (instead of 2 APM
messages) according to the standards.
NSN MSC Server prefers the version with 2
APM messages.
Differences in red compared
to the previous slide.
Other vendors
MSC Server
6. APM(APP (selected codec,
UPD.STOM = CN
2
.
A
d
d
R
e
q
(
T
2
,

c
o
d
e
c
,

E
v
e
n
t
=
T
u
n
n
e
l

I
n
d
T
u
n
O
p
t
=
1
,

E
s
t
a
b
.

B
e
a
r
e
r
)
3
.
A
d
d
R
e
p
l
y
4
.

N
o
t
i
f
y
R
e
q
(
I
P
B
C
P
2
)
5
.
N
o
t
i
f
y
R
e
p
l
y
9
.
M
o
d
R
e
q
(
I
P
B
C
P
1
)
1
0
.
M
o
d
R
e
p
l
y
1
4
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
5
.
N
o
t
i
f
y
R
e
p
l
y
12. NbUP Init
13. NbUP Init Ack
CN3410BEN33GLN0
BICC
40
1
.
A
d
d
R
e
q
(
T
1
,

c
o
d
e
c
,

R
e
q
u
e
s
t
i
n
g

B
I
W
F
1
)
2
.
A
d
d
R
e
p
l
y
(
B
I
W
F
1
)
3. IAM(APP ( "connect forward", BCU-ID1, BIWF1,
BNC Char: ATM AAL2))
4
.
A
d
d
R
e
q
(
T
2
,

R
e
q
u
e
s
t
i
n
g

B
I
W
F
2
,

B
N
C
-
I
D
2
)
5
.
A
d
d
R
e
p
l
y
(
B
I
W
F
2
,

B
N
C
-
I
D
2
)
6. APM(APP ( "connect forward, no notification",
BCU-ID2, BNC-ID2, BIWF2))
7
.
M
o
d
d
R
e
q
(
B
I
W
F
2
,

B
N
C
-
I
D
2
,

E
s
t
.

B
e
a
r
e
r

s
i
g
n
a
l
)
9
.
M
o
d
R
e
p
l
y
16. ANM
8. AAL2 ERQ
10. AAL2 ECF
15. ACM
ACM depends on
the terminating
side call setup in
MSS2.
11. NbUP Init
12. NbUP Init Ack
1
3
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
4
.
N
o
t
i
f
y
R
e
p
l
y
1
3
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
4
.
N
o
t
i
f
y
R
e
p
l
y
SAI = FORW
UPD.STOM = DC
UPD.STOM = DC
Forward ATM bearer establishment, no codec negotiation
Practical notes about the BIWF, BCU-ID, BNC-ID information elements:
-T1 termination reservation is requested from MGW1 with codec information. The
BIWF1 address is requested from the MGW1.
-BIWF1 is received from the MGW1 in AddReply in MSS1 as a result of the T1
termination reservation.
-BNC-ID1 is not requested from MGW1 as MSS1 doesnt need BNC-ID information.
MSS2/MGW2 dont need BNC-ID as well as the forward establishment is used in this
case.
-BIWF1 and BCU-ID1 is transferred in BICC: IAM to MSS2 from MSS1 only for
supporting the optimal MGW selection:
-If a physical MGW is shared between the MSS1 and MSS2 then the MSS2
can realize that MSS1 selected the common physical MGW based on the
BIWF1 information.
See User Plane Routing Functional Description (dn01163601) chapter 7.2
MGW selection optimisation based on BIWF address for details.
-BCU-ID1 (MGW ID of MGW1) can influence the MGW selection in MSS2 in
the Preceding UPD determination analysis. The PBCU attribute of the PUPD
determination analysis has the value of BCU-ID1.
-The T2 termination reservation is requested from MGW2 by MSS2. The BIWF2 and
BNC-ID2 information is requested from MGW2 in the AddReq message.
-After the T2 termination is reserved in MGW2 the BNC-ID2 and BIWF2 parameters
are received in AddReply from MGW2.
-Then these parameters are transferred to MSS1 in the APM message (IAM
response).
-Next MSS1 sends these information to MGW1 in ModReq message in order to be
able to establish the bearer in forward direction. The bearer establishment is
requested by the Establish Bearer signal in the ModReq message.
-Then the connection between the MGWs are setup with the AAL2 ERQ and AAL2
ECF messages between MGW1 and MGW2.
-After the bearer is established end to end (NbUP framing protocol initialisation is
successfully finished.) a NotifyReq message is sent to MSS1 and MSS2 from MGW1
and MGW2 respectively The ObscuredEvent is BNC Established
CN3410BEN33GLN0
BICC
41
Forward ATM bearer establishment, with codec negotiation
1
.
A
d
d
R
e
q
(
T
1
,

n
o

c
o
d
e
c
,

R
e
q
u
e
s
t
i
n
g

B
I
W
F
1
)
2
.
A
d
d
R
e
p
l
y
(
B
I
W
F
1
)
3. IAM(APP ( "connect forward", BCU-ID1, BIWF1,
BNC Char: ATM AAL2, supported codecs list))
4
.
A
d
d
R
e
q
(
T
2
,

R
e
q
u
e
s
t
i
n
g

B
I
W
F
2
,

B
N
C
-
I
D
2
)
5
.
A
d
d
R
e
p
l
y
(
B
I
W
F
2
,

B
N
C
-
I
D
2
)
6. APM(APP ( "connect forw, no notif + selected codec",
BCU-ID2, BNC-ID2, BIWF2, sel codec, avail. codecs list))
7
.
M
o
d
d
R
e
q
(
B
I
W
F
2
,

B
N
C
-
I
D
2
,

c
o
d
e
c
,
E
s
t
.

B
e
a
r
e
r

s
i
g
n
a
l
)
9
.
M
o
d
R
e
p
l
y
16. ANM
8. AAL2 ERQ
10. AAL2 ECF
Differences in red compared to the previous slide.
15. ACM
ACM depends on
the terminating
side call setup in
MSS2.
11. NbUP Init
12. NbUP Init Ack
1
3
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
4
.
N
o
t
i
f
y
R
e
p
l
y
1
3
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
4
.
N
o
t
i
f
y
R
e
p
l
y
SAI = FORW
UPD.STOM = CN
UPD.STOM = CN
Only the codec negotiation related information differs compared to the previous slide.
-The STOM parameter of the used UPDs shall be modified to CN value in both
MSSs configuration. See JF MML command group for more details.
-No codec is sent to the MGW1 in the first AddReq message.
-The Supported Codec List is filled in the BICC: IAM message.
-Different action indicator (* + selected codec) is used in the response: APM
message. Additionally, the Available Codec List and the Selected Codec is
transferred to MSS1 in the APM message.
-The selected codec is transferred to the MGW1 in the ModReq message.
CN3410BEN33GLN0
BICC
42
5
.
A
d
d
R
e
q
(
T
1
,

B
I
W
F
2
,

B
N
C
-
I
D
2
,

E
s
t
a
b
l
i
s
h

B
e
a
r
e
r

s
i
g
n
a
l
)
Forward ATM bearer establishment with delayed MGW
selection, no codec negotiation
7
.
A
d
d
R
e
p
l
y
1. IAM(APP ( "connect forward, BNC Char: ATM AAL2"))
2
.
A
d
d
R
e
q
(
T
2
,

R
e
q
u
e
s
t
i
n
g

B
I
W
F
2
,

B
N
C
-
I
D
2
)
3
.
A
d
d
R
e
p
l
y
(
B
I
W
F
2
,

B
N
C
-
I
D
2
)
4. APM(APP ( "connect forward, no notif.", BCU-ID2,
BNC-ID2, BIWF2))
14. ANM
6. ERQ
8. ECF
13. ACM
ACM depends on
the terminating
side call setup in
MSS2.
1
1
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
2
.
N
o
t
i
f
y
R
e
p
l
y
1
1
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
2
.
N
o
t
i
f
y
R
e
p
l
y
9. NbUP Init
10. NbUP Init Ack
The SUPD
determination
analysis is
executed again.
This is the main
benefit of this
method: the
preceding side
MGW selection
can be based on
the SBCU.
There is no
change in the
succeeding
MSS in case of
delayed MGW
selection. The
forward
establishment
works in the
same way with
delayed and
non-delayed
MGW selection.
SAI = DFORW
UPD.STOM = DC
UPD.STOM = DC
The bearer related information exchange is similar to the forward establishment with
non-delayed MGW selection as both cases are about forward bearer establishment.
The differences are the following:
-As there is no MGW selected in the MSS1 no BIWF1 and BCU-ID1 is transferred to
MSS2 in the BICC: IAM message.
-BNC-ID2 and BIWF2 parameters are transferred to MGW1 in the same way as
described at the non-delayed MGW selection.
-MSS2 requests BIWF and BNC-ID from MGW2 in AddReq
-MGW2 send BIWF2 and BNC-ID2 to MSS2 in AddReqply
-BIWF2 and BNC-ID2 are included in BICC: APM
-MSS1 reserves T1 termination and send the BIWF2 and BNC-ID2
parameters in AddReq.
-The Succeeding UPD determination analysis is executed again when the APM
message (IAM response) is received.
-This is the main benefit of the delayed MGW selection procedure.
-The Succeeding UPD determination analysis can be influenced with the
Succeeding BCU-ID (SBCU). Therefore more optimal MGW selection can be
supported in MSS1 as the MGW selection procedure depends on the
selected MGW under MSS2.
-Please refer to User Plane Routing Functional Description (dn01163601) chapter
7.3 MGW selection optimisation based on BCU-ID for details.
CN3410BEN33GLN0
BICC
43
1
.
A
d
d
R
e
q
(
T
1
,

c
o
d
e
c
,

R
e
q
u
e
s
t
i
n
g

B
I
W
F
1
,

B
N
C
-
I
D
1
)
Backward ATM bearer establishment, no codec negotiation
2
.
A
d
d
R
e
p
l
y
(
B
N
C
-
I
D
1
,

B
I
W
F
1
)
3. IAM(APP ( "connect backward", BCU-ID1,
BIWF1, BNC-ID1, BNC Char: ATM AAL2))
4
.
A
d
d
R
e
q
(
T
2
,

B
I
W
F
1
,

B
N
C
-
I
D
1
,

E
s
t
a
b
l
i
s
h

B
e
a
r
e
r

s
i
g
n
a
l
)
6
.
A
d
d
R
e
p
l
y
13. ANM
5. ERQ
7. ECF
12. ACM
ACM depends on the
terminating side call
setup in MSS2.
8. NbUP Init
9. NbUP Init Ack
1
0
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
1
.
N
o
t
i
f
y
R
e
p
l
y
SAI = BACK
UPD.STOM = DC
UPD.STOM = DC
1
0
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
1
.
N
o
t
i
f
y
R
e
p
l
y
NbUP (IuUP also)
initialisation is
executed end-to-
end and it is always
done in forward
direction regardless
of the bearer
establishment
direction.
Practical notes about the BIWF, BCU-ID, BNC-ID information elements in case of
backward establishment method:
-T1 termination reservation is requested from MGW1 with codec information. The
BIWF1 and BNC-ID1 are requested from the MGW1.
-MSS1 receives the BNC-ID1 and BIWF1 from MGW1 in AddReply when the T1
termination is reserved.
-MSS1 packs the BCU-ID1, BNC-ID1, BIWF1 into the BICC: IAM message. All the
user plane routing information is needed at the terminating side in case of backward
establishment.
-The MGW selection optimisation based on BIWF address functionality can
be used here also.
See User Plane Routing Functional Description (dn01163601) chapter 7.2
MGW selection optimisation based on BIWF address for details.
-BCU-ID1 (MGW ID of MGW1) can influence the MGW selection in MSS2 in
the Preceding UPD determination analysis. The PBCU attribute of the PUPD
determination analysis has the value of BCU-ID1.
-MSS2 sends the BNC-ID1 and BIWF1 to MGW2 in the AddReq during T2
termination creation. Therefore the backward establishment can be done in this
phase.
The later phases are similar to the forward establishment case:
-NbUP framing protocol initialisation is done.
-NbUP (IuUP also) initialisation is executed end-to-end and it is always done
in forward direction regardless of the bearer establishment direction.
-Then notifications about Bearer Establishment is sent by the MGWs.
-Call setup is finished on control plane.
CN3410BEN33GLN0
BICC
44
Backward ATM bearer establishment with codec
negotiation
1
.
A
d
d
R
e
q
(
T
1
,

n
o

c
o
d
e
c
,

R
e
q
u
e
s
t
i
n
g

B
I
W
F
1
,

B
N
C
-
I
D
1
)
2
.
A
d
d
R
e
p
l
y
(
B
N
C
-
I
D
1
,

B
I
W
F
1
)
4
.
A
d
d
R
e
q
(
T
2
,

B
I
W
F
1
,

B
N
C
-
I
D
1
,

E
s
t
a
b
l
i
s
h

B
e
a
r
e
r

s
i
g
n
a
l
)
6
.
A
d
d
R
e
p
l
y
16. ANM
5. ERQ
7. ECF
15. ACM
ACM depends on the
terminating side call
setup in MSS2.
11. NbUP Init
12. NbUP Init Ack
1
3
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
4
.
N
o
t
i
f
y
R
e
p
l
y
SAI = BACK
UPD.STOM = CN
UPD.STOM = CN
1
3
.

N
o
t
i
f
y
R
e
q
(
B
N
C
E
s
t
.
)
1
4
.
N
o
t
i
f
y
R
e
p
l
y
Differences in red compared to the previous slide.
3. IAM(APP ( "connect backward", BCU-ID1, BNC-ID1,
BIWF1, BNC Char: ATM AAL2, supported codec list))
8. APM(APP ( selected codec",
9
.
M
o
d
d
R
e
q
(
s
e
l
e
c
t
e
d

c
o
d
e
c
)
1
0
.
M
o
d
R
e
p
l
y
Only the codec negotiation related information differs compared to the previous slide.
-The STOM parameter of the used UPDs shall be modified to CN value in both
MSSs configuration. See JF MML command group for more details.
-No codec is sent to the MGW1 in the first AddReq message.
-The Supported Codec List is filled in the BICC: IAM message.
-An additional APM message is used from MSS2 to MSS1 to transfer the codec
information. The selected codec action indicator is used in the APM message and
the Available Codec List and the Selected Codec are included.
-The selected codec is transferred to the MGW1 in the ModReq message.
-Note: T1 termination modification in MGW1 (e.g. with codec) is possible after ATM
AAL2 connection establishment if the NbUP protocol layer is not yet built up.
-The NbUP framing protocol initialisation is done later.
-The other steps are similar to the backward establishment without codec
negotiation.
CN3410BEN33GLN0
BICC
45
BICC usage in MSS : BICC supports
Call and bearer establishment over AAL2 and IP
Codec negotiation procedure
Codec modify procedure
Out of band transport of DTMFs
APM/BAT ASE functionality
Bearer Redirection
Enable rerouting of user plane after some sort of optimization is needed
Automatic Rerouting (Crankback mechanism)
Allows the call set-up to return to the preceding Serving Network (SN) so that the call can
automatically be rerouted from there
New functionality defined for BICC
CN3410BEN33GLN0
BICC
46
Action Indicator supported in MSS (M14)
Not Supported Supported Connect backward Delayed backward est. (IP)
Not Supported Supported Connect backward Fast backward est. (IP)
Supported
2
Supported Connect forward Delayed forward est. (IP)
Supported
1
Supported Connect forward Fast forward est. (IP)
Supported Supported Connect forward Forward est. with delayed MGW
selection (ATM)
Supported Supported Connect backward Backward est (ATM)
Supported Supported Connect forward Forward est. (ATM)
Support in outgoing
call from MSS
Support in incoming
call to MSS
Action Indicator value BICC bearer establishment
method
1. Establishment with codec negotiation is not supported.
2. Only establishment with codec negotiation is supported.
CN3410BEN33GLN0
BICC
47
BICC parameter and their sources in incoming and
outgoing call in MSS
BCU identifier from the selected MGW's
data or Succeeding Bearer Control Unit
identifier (SBCU) in user plane analysis.
Preceding Bearer Control Unit
identifier (PBCU) in user plane analysis
or BCU identifier from the selected
MGW's data.
Bearer Control Unit Identifier
None. Parameter is present when
bearer control tunnelling is used for
establishing bearer connections.
None. Parameter is present when
bearer control tunnelling is used for
establishing bearer connections.
Bearer Control Tunneling
None. Parameter is conveyed as such
to the MGW.
to the MGW.
Bearer Control Information
Succeeding Bearer Network
Characteristics (SBNC) is the result of
user plane analysis.
Preceding Bearer Network
Characteristics (PBNC) attribute can be
analysed in user plane analysis
Bearer Network Connection
Characteristics
to the MGW.
to the MGW.
Interworking Function Address
to the MGW.
to the MGW.
Backbone Network Connection
Identifier
Succeeding Action Indicator (SAI) is
the result of user plane analysis.
Preceding Action Indicator (PAI)
attribute can be analysed in user plane
analysis.
Action Indicator
Configurable parameter in MSS,
If any
If any
BICC parameter
Outgoing Call Incoming Call
CN3410BEN33GLN0
BICC
48
BICC parameter generated internally in MSS in
incoming and outgoing call
Succeeding Signaling type (SSIGT) Route data (OUTR)
Succeeding User Plane Destination reference
(SUPDR)
Route data (UPDR) Outgoing call from MSS
Preceding Emergency call indicator (EMCI) Dialing pre-analysis
Preceding Signaling type (PSIGT) Circuit groups data (UPART)
Preceding User Plane Destination reference
(PUPDR)
Circuit groups data (UPDR) Incoming call to MSS
If any
Location of data Call direction
CN3410BEN33GLN0
BICC
49
Codec Selection : Tandem Free Operation (TFO) vs
Transcoder Free Operation (TrFO)
- TFO
CN3410BEN33GLN0
BICC
50
Codec Selection : Tandem Free Operation (TFO) vs
Transcoder Free Operation (TrFO)
- TrFO : Codec negotiation using BICC APP parameter
CN3410BEN33GLN0
BICC
51
Successful BICC codec negotiation
CN3410BEN33GLN0
BICC
52
Transcoder at the edge
CN3410BEN33GLN0
BICC
53
Transcoder at the edge : UE originated call
CN3410BEN33GLN0
BICC
54
Transcoder at the edge : PSTN originated call
CN3410BEN33GLN0
BICC
55
Transcoder at the edge : TDM routed call
CN3410BEN33GLN0
BICC
56
Payload optimization with TFO
CN3410BEN33GLN0
BICC
57
Basic codec modification with BICC signaling

11 02 Cn3410ben33gln0 Bicc

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

11 02 Cn3410ben33gln0 Bicc

Uploaded by

Copyright:

Available Formats

CN3410BEN33GLN0

You might also like