BICC_call Flow

1 Nokia Siemens Networks Presentation / Author / Date / Document NumberFor public use IPR applies

Bearer Independent Call Control - BICCSwitching Core Network SignallingM14/U4


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-2IP

MGWRTP IP

H

.

2

4

8

I

P

Control plane

User plane

or


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)

BICC

MTP3 MTP3b M3UA

MTP2 SAAL SCTP

MTP1 ATM IP

BICC over TDM BICC over ATM BICC over IP


For IP backbones: bearer-information is transferred between MSSs in BICC through APM-mechanism

MGWMGWMGWMGW

MSC ServerMSC ServerMSC ServerMSC Server

IP

SCTP

M3UA

BICC

IAMIAM

SigtranSigtran

.

. 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.2port: 5964IP: 192.168.3.2port: 5964

BICC in 3GPP R4


BICC Functional Blocks

CSF

BCF

Call ControlSignalling

Bearer ControlSignalling

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 ControlSignalling

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 BCFBIWF : Bearer Inter-working Function, provides BCF and media mapping/switching function

Control plane

User plane


Bearer Establishment ModesMSS MSS

Forward

Backward

MSS

MGW

MSS

MGW

Bearer establishment direction

Bearer establishment direction

BICC:IAM

BICC:IAM

ATM and IP bearers

ATM bearersIP bearers only if originating side

is another vendor


Two ways to establish a bearer

1) ATM: separate bearer control signalling: AAL-Type-2 Signalling2) IP: bearer information tunneled in call control and call bearer control

messages: IPBCP

Bearer Control Signalling

MSS MSSCall 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


Main BICC call control related messages -1- Q1902.3

Message Code Description

ACM 0000 0110 Address Complete MessageANM 0000 1001 Answer Message

APM 0100 0001 Application Transport Message

CPG 0010 1100 Call Progress

CON 0000 0111 Connect

IAM 0000 0001 Initial Address Message

IDR 0011 0110 Identification Request

IRS 0011 0111 Identification Response

INF 0000 0100 Information

INR 0000 0011 Information Request


Main BICC call control related messages -2- Q1902.3


REL 0000 1100 ReleaseRES 0000 1110 Resume

RLC 0001 0000 Release Complete

SAM 0000 0010 Subsequent Address Message

SGM 0011 1000 Segmentation

SUS 0000 1101 Suspend

USR 0010 1101 User-to-User Information


Main BICC Maintenance related messages -1- Q1902.3


CGB 0001 1000 Circuit / CIC Group Blocking

CGBA 0001 1010 Circuit / CIC Group Blocking Acknowledgement

GRS 0001 0111 Circuit / CIC Group Reset

GRA 0010 1001 Circuit / CIC Group Reset Acknowledgement

CGU 0001 1001 Circuit / CIC Group Unblocking

CGUA 0001 1011 Circuit / CIC Group Unblocking Acknowledgement

CFN 0010 1111 Confusion

RSC 0001 0010 Reset Circuit / CIC message


General BICC PDU format (ASN1)


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.

CIC

Message type code

Mandatory fixed part

Mandatory variable part

Optional part


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.

8 7 6 5 4 3 2 1CIC 1CIC 2CIC 3CIC 4

LSB

MSB


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)


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

IAMAPP paramparam

e.g. IAM or APM message

BAT-ASE

MSS

BAT-ASE

Application Transport Mechanism APM -2-


Application Transport Parameter (APP)

n43a321a1

Release Call Indicator 1=Release call

APM user information

Segmentation local referenceext.APM Segmentation IndicatorSIext.

RCISNIspareext.MSBext.

LSBApplication Context Identifier (BAT-ASE)ext.12345678

8 7 6 5 4 3 2 1Identifier 1 1

Length indicator 1 2Compatibility information 1 3

Content 14

Identifier 2 mLength indicator 2

Compatibility Information 2

Content 2

:n

Send Notification Indicator1=send notification

000000=Final segment 000001 to 001001= segment number

Sequence Indicator1=New sequence0=Subsequent

ext=0 octet 1a present

000010= BAT ASE application used


Contents of APM identifiers -1-Value IE name Information

0000 0001 Action Indicator Can have codes like connect forward, connect backward etc.

0000 0010 Backbone Network Connection Identifier(BNC_ID)

Identifies the logical connection between a local and remote termination. (Similar to the port in the IP technology)

0000 0011 Bearer Interworking Function address(BIWF)

ATM AAL2 level address which is needed for the ATM AAL2 connection setup. (Similar to the IP address in the IP technology)NSAP format

0000 0100 Codec list In the codec list, single codec information elements are listed in decreasing order of preference level.

0000 0101 Single codec Has a field called Organization identifier and codec information subfield. Subfield has information about the codec type and codec configuration.

0000 0111 Bearer Network Connection Characteristics

Identifies the bearer used e.g. IP/RTP, AAL1, AAL2, TDM etc.


Contents of APM identifiers -2-Value IE name Information

0000 0110 BAT compatibility report

Instructions on received, unrecognized information

0000 1000 Bearer Control information

Contains PDU (Protocol Data Unit) of BCTP

0000 1001 Bearer control tunnelling

Indicates whether tunnelling is used or not

0000 1010 Bearer Control Unit identifier

Contains information about the BCU. It includes Network ID and Local BCU-ID. A logical MGW identifier which can be used for optimal MGW selection purposes.

0000 1011 Signal Signal to be applied

0000 1110 Signal type Indicates the signal type e.g. DTMF tones, dial tone, ringing tone, busy tone etc.

0000 1100 Bearer redirection capability

Indicates whether bearer redirection capability is supported at sending node and also indicates options within the capability.

0000 1000 Duration Duration of a signal in milliseconds.


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


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.


Codec list

0x00 no indication

0x01 ITU-T

0x02 ETSI

Single codec IE

Single codec IE

Single codec IE

CODEC LIST

Organization Identifier

Single Codec IE

Codec type (codec ID)

Codec configuration

ITU-T ETSI0x00 No indication 0x00 GSM FR

0x01 G.711 (64 kbps, A-law) 0x01 GSM HR

0x02 G.711 (64 kbps, u-law) 0x02 GSM EFR

0x03 GSM FR AMR

0x04 GSM HR AMR

0x05 UMTS AMR

0x06 UMTS AMR2

Organization ID

Codec Type (Codec ID)

Only if codec negotiation is used

ZJFI:


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

MSSMSS

M3UA

SCTPIP

SCTPIP

Nc

Mc

IP_BB

Mc


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


IPBCP in SDP format

v= 0 o= - 0 0 IN IP4 10.33.16.136s= IP Tunnelingc= IN IP4 10.33.16.136t= 0 0a= ipbcp:1 Requestm= audio 1026 RTP/AVP 96a= rtpmap: 96 VND.3GPP.IUFP/16000

SDPSDP version (v) : 0Owner/Creator, Session ID (o) :

Owner Username : - (not used by IPBCP)Session ID : 0 (not used by IPBCP)Session Version : 0Owner Network Type : IN (internet)Owner Address Type : IPv4 or IPv6Owner Address : IP address of the MGW

Session name (s): Session type (ignored when received)Connection Information (c):

Connection Network Type : INConnection Address Type : IPv4 or IPv6Connection Address : IP address of the MGW

Time Description, active time (t) : Session Start Time : 0 Session Stop Time : 0

(0 indicate permanent session)

Session Attribute (a) :Session Attribute Fieldname : IPBCP protocol version : 1IPBCP command type : Request/Accepted/Confused/Rejected

Media Description, name and address (m):Media Type : audio or videoMedia Port : port number valueMedia Proto: RTP/AVPMedia Format :

Media Attribute (a) :Media Attribute Fieldname : rtpmap or fmtpMedia Format : Multi-Purpose Internet Mail Extension Type :


Codecs represented in SDP

Codec SDP representation

AMR m=audio 1234 RTP/AVP 96 a=rtpmap:96 AMR/8000 a=fmtp:96 mode-set=1,2,3,4,5,6,7

EFR m=audio 1234 RTP/AVP 103a=rtpmap:103 GSM-EFR/8000

FR m=audio 1234 RTP/AVP 3a=rtpmap:3 GSM/8000

G.711 A-law m=audio 1234 RTP/AVP 8a=rtpmap:8 PCMA/8000

G.711 u-law m=audio 1234 RTP/AVP 0a=rtpmap:0 PCMU/8000

G.723.1 m=audio 1234 RTP/AVP 4a=rtpmap:4 G723/8000

Codec SDP representation

G.723.1 Annex A

m=audio 1234 RTP/AVP 4a=rtpmap:4 G723/8000a=fmtp:4 annexa=yes

G.729a m=audio 1234 RTP/AVP 18a=rtpmap:18 G729A/8000

G.729a Annex B

m=audio 1234 RTP/AVP 18a=rtpmap:18 G729A/8000a=fmtp:18 annexb=yes

iLBC m=audio 1234 RTP/AVP 97a=rtpmap:97 iLBC/8000

Clearmode m=audio 1234 RTP/AVP 100a=rtpmap:100 CLEARMODE/8000


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


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).


Note: The AddReply and NotifyReq commands are conveyed in the same H.248 message.

Note: The AddReply and NotifyReq commands are conveyed in the same 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 Init15. 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

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

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.


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


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


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))16. APM(APP (BCI = IPBCP2))

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


CN

UPD.STOM = CN

19. User Plane established.

The purple parts are the IP tunneling specific items.


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 ERQ10. AAL2 ECF

15. ACM



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


DC

UPD.STOM = DC

Forward ATM bearer establishment, no codec negotiation


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 ERQ10. AAL2 ECF

Differences in red compared to the previous slide.

15. ACM



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


CN

UPD.STOM = CN


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. ERQ7. ECF

12. ACM

ACM depends on the terminating side call

setup in MSS2.


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.


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. ERQ7. ECF

15. ACM

ACM depends on the terminating side call

setup in MSS2.


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", selected codec, available codec list))

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


Codec Selection : Tandem Free Operation (TFO) vs Transcoder Free Operation (TrFO)- TFO


Codec Selection : Tandem Free Operation (TFO) vs Transcoder Free Operation (TrFO)- TrFO : Codec negotiation using BICC APP parameter


Successful BICC codec negotiation

Bearer Independent Call Control - BICCBICC in 3GPP R4Bearer Independent Call Control - BICCBICC in 3GPP R4BICC Functional BlocksBearer Establishment ModesTwo ways to establish a bearerMain BICC call control related messages -1- Q1902.3Main BICC call control related messages -2- Q1902.3Main BICC Maintenance related messages -1- Q1902.3General BICC PDU format (ASN1)Format of BICC messagesCIC (Call Instance Code) Application Transport Mechanism APM -1-Application Transport Mechanism APM -2-Application Transport Parameter (APP)Contents of APM identifiers -1-Contents of APM identifiers -2-Action Indicator: used for a lot of indicationsAction Indicator (AI): usage in BICC:IAM and BICC:APMCodec listTunneling bearer informationIPBCP IP Bearer Control ProtocolIPBCP in SDP formatCodecs represented in SDP Terms, describing call setup scenarios (1)Terms, describing call setup scenarios (2)Forward IP bearer establishment with fast forward tunneling, no codec negotiationForward IP bearer establishment with delayed forward tunneling and codec negotiationForward ATM bearer establishment, no codec negotiationForward ATM bearer establishment, with codec negotiationBackward ATM bearer establishment, no codec negotiationBackward ATM bearer establishment with codec negotiationCodec Selection : Tandem Free Operation (TFO) vs Transcoder Free Operation (TrFO)Codec Selection : Tandem Free Operation (TFO) vs Transcoder Free Operation (TrFO)Successful BICC codec negotiation

Date post:	29-Oct-2015
Category:	Documents
Upload:	jitender-arora
View:	953 times
Download:	0 times

BICC_call Flow

Documents