BICC - Call Flow
BICC - Call Flow
BICC in 3GPP R4
Control plane
H.248 IP
User plane
H.248 IP
Mc
Mc
BICC over IP
BICC in 3GPP R4
For IP backbones: bearer-information is transferred between MSSs in BICC
through APM-mechanism
Bearer information carried inside call control messages MSC Server IAM MSC Server
MGW
CSF
Call Bearer Control Signalling (CBC)
Signalling
CSF
CSF
Call Bearer Control Signalling (CBC)
BIWF
User plane
BIWF
Bearer Control Signalling
BCF
BCF
Bearer
Bearer
SN : CMN : BIWF :
Serving Node Call Service Function (CSF) with associated Bearer Control Function (BCF) Call Mediation Node CSF without associated BCF Bearer Inter-working Function, provides BCF and media mapping/switching function
MSS
Forward
ATM and IP bearers Bearer establishment direction
MSS
BICC:IAM
MSS
Backward
ATM bearers IP bearers only if originating side is another vendor Bearer establishment direction
MGW
For public use IPR applies 8 Nokia Siemens Networks Presentation / Author / Date / Document Number
MGW
MSS
IP backbone: the IPBCP protocol is tunneled inside H.248 and BICC (or SIP) via the MSC Servers.
H.248
H.248 ATM backbone: separate bearer control signalling: AAL-Type-2 signalling Bearer Control Signalling e.g: AAL2 signalling
MGW
For public use IPR applies 9 Nokia Siemens Networks
MGW
Presentation / Author / Date / Document Number
Code 0000 1100 0000 1110 0001 0000 0000 0010 0011 1000 0000 1101 0010 1101
Description Release Resume Release Complete Subsequent Address Message Segmentation Suspend User-to-User Information
CIC Message type code Mandatory fixed part Mandatory variable part Optional part
1
LSB
1 2 3 4
MSB
CIC
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
Application Transport Mechanism APM -2 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 BAT-ASE
param
MSS
APP
param
IAM
BAT-ASE
8 ext. ext.
Sequence Indicator 1=New sequence 0=Subsequent
7 MSB
1 LSB 1 1a 2 3 3a n
Send Notification 1=send notification 000000=Final segment 000001 to 001001= segment number Release Call Indicator 1=Release call
Application Context Identifier (BAT-ASE) spare SI APM Segmentation Indicator Segmentation local reference APM user information SNI
RCI
4 Indicator
Identifier 1 Length indicator 1 Compatibility information 1 Content 1 Identifier 2 Length indicator 2 Compatibility Information 2 Content 2 :
For public use IPR applies 18 Nokia Siemens Networks
1 2 3 4 m
Contents of APM identifiers -1Value 0000 0001 0000 0010 IE name Action Indicator Backbone Network Connection Identifier (BNC_ID) Bearer Interworking Function address (BIWF) Codec list Single codec Information Can have codes like connect forward, connect backward etc. Identifies the logical connection between a local and remote termination. (Similar to the port in the IP technology) ATM AAL2 level address which is needed for the ATM AAL2 connection setup. (Similar to the IP address in the IP technology) NSAP format In the codec list, single codec information elements are listed in decreasing order of preference level. Has a field called Organization identifier and codec information subfield. Subfield has information about the codec type and codec configuration. Identifies the bearer used e.g. IP/RTP, AAL1, AAL2, TDM etc.
0000 0011
0000 0111
BAT compatibility report Bearer Control information Bearer control tunnelling Bearer Control Unit identifier
Instructions on received, unrecognized information Contains PDU (Protocol Data Unit) of BCTP Indicates whether tunnelling is used or not 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. Signal to be applied Indicates the signal type e.g. DTMF tones, dial tone, ringing tone, busy tone etc. Indicates whether bearer redirection capability is supported at sending node and also indicates options within the capability. Duration of a signal in milliseconds.
0000 1000
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
Codec list
CODEC LIST
Single codec IE Single Codec IE
Organization Identifier
Single codec IE
Codec configuration
ITU-T
0x00 0x01 No indication G.711 (64 kbps, A-law) G.711 (64 kbps, u-law) 0x00 0x01 0x02 0x03 0x04 0x05 0x06
ETSI
GSM FR GSM HR GSM EFR GSM FR AMR GSM HR AMR UMTS AMR UMTS AMR2
0x02
SDP
(RFC2327) MSS MSS
BCTP
(Q.1990)
Nc IPBCP Mc
(Q.1970)
APM
(Q.765.5)
BICC
(Q.1902.2)
Mc
SDP
(RFC2327)
M3UA SCTP IP
MGW MGW IP_BB
BCTP
(Q.1990)
MEGACO
(H.248)
SCTP IP
- Sent by a BIWF to initiate an IP bearer establishment or modification request. - Sent by a BIWF that receives an IP bearer establishment or modification message if it accepts the request. - Sent by a BIWF in response to an IP bearer establishment or modification message if it cannot process the received message. - Sent by a BIWF in response to an IP bearer establishment or modification message if it rejects the request
Rejected
v= 0 SDP 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
Media Description, name and address (m): Media Type : audio or video Media Port : port number value Media Proto: RTP/AVP Media Format : Media Attribute (a) : Media Attribute Fieldname : rtpmap or fmtp Media Format : Multi-Purpose Internet Mail Extension Type :
iLBC Clearmode
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). 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). 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
Backward tunnelling:
Fast tunnelling:
Delayed tunnelling:
UPD.STOM = DC
17. NotifyReply
13. User Plane established. Note: The AddReply and NotifyReq commands are conveyed in the same H.248 message. 14. NbUP Init 15. NbUP Init Ack
Note: The AddReply and NotifyReq commands are conveyed in the same H.248 message.
Fast forward tunneling is initiated only without codec negotiation and only with forward bearer establishment.
For public use IPR applies 30 Nokia Siemens Networks Presentation / Author / Date / Document Number
17. NotifyReply
4. NotifyReply
9. NotifyReply
12. ModReply
2. AddReply
7. AddReply
Forward IP bearer establishment with delayed forward tunneling and codec negotiation
SAI = FORW UPD.STOM = CN
3. IAM(APP ( "connect forward", BCU-ID1, BNC Char: IP/RTP, BCT = Tunneling to be used, supported codec list)) 6. APM(APP ( "connect forw, no notif+sel cdc", BCUID2, selected codec, available codec list)) 11. APM(APP (BCI = IPBCP1)) 16. APM(APP (BCI = IPBCP2)) 24. ACM 2. AddReply 7.ModdReq(Establish BNC, selected codec, Event=Tunnel Ind.) 1. AddReq(T1, no codec, TunOpt=2) 25. ANM 22. NotifyReq(BNC Est.) 22. NotifyReq(BNC Est.) 4. AddReq(T2, codec, TunOpt=2) 14. NotifyReq(IPBCP2) 9. NotifyReq(IPBCP1) 17.ModReq(IPBCP2) 12.ModReq(IPBCP1, Event=Tunnel Ind,) 10. NotifyReply 23. NotifyReply 15. NotifyReply 23. NotifyReply
UPD.STOM = CN
18. ModReply
19. User Plane established. 20. NbUP Init 21. NbUP Init Ack
13. ModReply
8. ModReply
5. AddReply
UPD.STOM = DC
14. NotifyReply
8. AAL2 ERQ 10. AAL2 ECF 11. NbUP Init 12. NbUP Init Ack
14. NotifyReply
9. ModReply
5. AddReply(BIWF2, BNC-ID2)
UPD.STOM = CN
14. NotifyReply
8. AAL2 ERQ 10. AAL2 ECF 11. NbUP Init 12. NbUP Init Ack
14. NotifyReply
11. NotifyReply
NbUP (IuUP also) initialisation is executed end-toend and it is always done in forward direction regardless of the bearer establishment direction.
11. NotifyReply
UPD.STOM = CN
14. NotifyReply
14. NotifyReply
10. ModReply
6. AddReply
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