BICC

HUAWEI GSM-T GTSOFTX3000
Technical Manual Signaling and Protocols
Contents
Contents
13 BICC..........................................................................................................................................13-1
13.1 Overview ...................................................................................................................................................13-2
13.1.1 Definition and Functions of the Nc Interface...................................................................................13-2
13.1.2 BICC Implementation in GTSOFTX3000 .......................................................................................13-2
13.1.3 Structure of the Protocol Stack.........................................................................................................13-3
13.2 Introduction of BICC Protocol ..................................................................................................................13-3
13.2.1 Basic Concepts.................................................................................................................................13-4
13.2.2 Message Structure ..........................................................................................................................13-14
13.3 Signaling Procedures...............................................................................................................................13-17
Issue 03 (2008-07-15)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Figures

Figures
Figure 13-1 BICC protocol implementation in GTSOFTX3000......................................................................13-2
Figure 13-2 BICC protocol stack .....................................................................................................................13-3
Figure 13-3 Diagram of separation of call and bearer of BICC .......................................................................13-8
Figure 13-4 Network model of BICC...............................................................................................................13-9
Figure 13-5 Generic protocol model of BICC..................................................................................................13-9
Figure 13-6 Format for BICC messages.........................................................................................................13-14
Figure 13-7 Delayed forward bearer setup, with notification.........................................................................13-18
Figure 13-8 Forward setup, with codec negotiation .......................................................................................13-19
Figure 13-9 Mid-call codec negotiation containing w....................................................................................13-20
Figure 13-10 Forward call and bearer release, forward bearer setup mode....................................................13-21
ii

Issue 03 (2008-07-15)

Tables
Tables
Table 13-1 Basic concepts of the BICC protocol..............................................................................................13-4
Table 13-2 Signaling capability sets of a BICC basic call ..............................................................................13-10
Table 13-3 Generic signaling procedures, supplementary services and additional functions/services of BICC
.........................................................................................................................................................................13-12
Table 13-4 BICC message type codes ............................................................................................................13-15
Issue 03 (2008-07-15)

iii

13 BICC
13
BICC
About This Chapter

The following table lists the contents of this chapter.
Section
Describes
13.1 Overview
The definition, function, and application of the BICC

protocol, and the structure of the protocol stack.
13.2 Introduction of BICC

Protocol
The concept and message structure of the BICC protocol.
13.3 Signaling Procedures
The signaling procedures of the ISUP protocol.
Issue 03 (2008-07-15)

13-1

13 BICC
13.1 Overview
The Bearer Independent Call Control (BICC) protocol is one of the application layer control
protocols. It has the following functions:
z
Establishing, modifying and terminating calls
Bearing comprehensive PLMN/PSTN/ISDN services
BICC evolves from the ISUP protocol and has it developed. The basic feature of BICC is the
separation between the call control level and the bearer control level. Thus the Call Service
Function (CSF) is independent of the Bearer Control Function (BCF).
In the GSM-T, BICC is applied to the call control interface between two MSC Servers.
13.1.1 Definition and Functions of the Nc Interface

Definition of the Nc Interface
Nc is an additional interface in R4. It is also named Nc reference point in 3GPP protocols. It is
the standard interface between two MSC Servers or GMSC Servers. This interface adopts
BICC or ISUP of the ITU-T.
Functions of the Nc Interface

To achieve the networking between networks, the Nc interface provides the GSM-T CS
domain service with the inter-office call control capability independent of the following
technologies:
z
User-level bearer technology
Control-level signaling transport technology
13.1.2 BICC Implementation in GTSOFTX3000

When the GTSOFTX3000 acts as an MSC Server or a GMSC Server, BICC is used for
interworking between the GTSOFTX3000 and another MSC Server, as shown in Figure 13-1.
Figure 13-1 BICC protocol implementation in GTSOFTX3000
MSC Server
(GTSOFTX3000)
BICC
GMSC Server
(GTSOFTX3000)
Nc
Mc
Mc
Nb
UMG8900
13-2
UMG8900

Issue 03 (2008-07-15)

13 BICC
13.1.3 Structure of the Protocol Stack

BICC can use any transport network to transmit signaling, such as IP, ATM and TDM
networks. According to implementation requirements, the GTSOFTX3000 can use four
transport modes:
z
TDM based MTP3
IP based M3UA
IP based SCTP
ATM based MTP3b
See Figure 13-2.

Figure 13-2 BICC protocol stack
Nc
Nc
(G)MSC Server
MSC Server
(G)MSC Server
MSC Server
BICC
BICC
BICC
BICC
M3UA
M3UA
MTP3
MTP3
SCTP
SCTP
IP
IP
MAC
MAC
L1
L1
MTP2
MTP2
MTP1
MTP1
a) TDM based
b) M3UA based
Nc
Nc
(G)MSC Server
MSC Server
BICC
BICC
SCTP
SCTP
IP
IP
MAC
MAC
L1
L1
(G)MSC Server
MSC Server
BICC
BICC
MTP3B
MTP3B
STC
STC
SAAL
SAAL
AAL5
AAL5
ATM
ATM
PL
PL
c) SCTP/IP based
d) ATM based
13.2 Introduction of BICC Protocol

The BICC signaling is developed based on the ISUP signaling. It is similar to the ISUP
protocol in the following aspects:
z
Supporting basic call procedures
Supporting supplementary service features
Issue 03 (2008-07-15)

13-3

13 BICC
The additional Application Transport Mechanism (APM) in BICC makes it possible to

exchange bearer related information between the call control nodes at the ends of the Nc
interface, including:
z
Bearer address
Connection reference
Bearer characteristics
Bearer setup mode
Supported Codec list
BICC can also provide an optional tunnel transport function on the Nc interface for the bearer
control signaling between MGWs.
BICC uses the idea of the separation between call signaling function and bearer signaling
function to define a new call control signaling protocol used in a backbone network. Thus it
can control a variety of networks, including SS7, ATM and IP networks.
The call control protocol is based on N-ISUP signaling. It uses related messages in ISUP and
uses APM to convey specific the bearer control information of BICC. Therefore, it can bear
overall PSTN/ISDN services. The separation between call and bearer makes the networking
between services provided by networks of different bearer types simple. What is needed is to
realize networking on bearer level. It is not needed to change services.
13.2.1 Basic Concepts

Terminology
BICC defines some new terms. Table 13-1 briefly introduces the terms.
Table 13-1 Basic concepts of the BICC protocol
Abbreviation
Full Name
Description
BNC
Backbone Network
Connection
Representing the edge to edge transport

connection within the backbone network,
consisting of one or more Backbone Network
Connection Links (BNCL)
Representing a segment of the end to end

Network Bearer Connection (NBC)
BNCL
13-4
Backbone Network
Connection Link
Representing the transport facility between two

adjacent backbone network entities containing a
bearer control function

Issue 03 (2008-07-15)

13 BICC
Abbreviation
Full Name
Description
BCF
Bearer Control
Function
Five types of BCFs are defined.

z
Bearer Control Joint Function (BCF-J):

Providing the control of the bearer switching
function, the communication capability with
two associated call service functions (CSF),
and the signaling capability necessary to
establish and release the backbone network
connection
Bearer Control Gateway Function (BCF-G):

function, the communication capability with its
associated call service function (CSF-G), and
the signaling capability necessary to establish
and release of the backbone network
connection
Bearer Control Nodal Function (BCF-N):

associated call service function (CSF-N), and
connection to its peer (BCF-N)
Bearer Control Relay Function (BCF-R):

function and relaying the bearer control
signaling requests to next BCF in order to
complete the edge to edge backbone network
connection
Bearer Control Transit Function (BCF-T):

associated call service function (CSF-T), and
connection
BCS
Bearer Control
Segment
Representing the signaling relationship between

two adjacent Bearer Control Functional entities
(BCF)
BIWF
Bearer
Inter-Working
Function
Providing BCF and media mapping/switching

functions within the scope of a Serving Node
(ISN/TSN/GSN).
Containing one BCF (BCF-N/BCF-T/BCF-G)

and one or more MCF and MMSF
Functionally equivalent to a Media Gateway

that incorporates bearer control
BIWN
Issue 03 (2008-07-15)
Bearer
Inter-Working Node
A physical unit functionality similar to a BIWF

13-5

13 BICC
Abbreviation
Full Name
Description
CCA
Call Control
Association
Defining the peer to peer signaling association

between Call, and Call & Bearer state machines
located in different physical entities
CMN
Call Mediation
Node
Providing CSF-C functions without an

associated BCF entity
CSF
Call Service
Function
Four types of CSF are defined.
GSN
13-6
Gateway Serving
Node
Call Service Nodal Function (CSF-N):

Providing the service control nodal actions
associated with the narrowband service by
interworking with narrowband and BICC
signaling, signaling to its peer (CSF-N) the
characteristics of the call, and invoking the
Bearer Control Nodal Functions (BCF-N)
necessary to transport the narrowband bearer
service across the backbone network
Call Service Transit Function (CSF-T):

Providing the service transit actions necessary
to establish and maintain a backbone network
call, and its associated bearer by relaying
signaling between CSF-N peers and invoking
the Bearer Control Transit Functions (BCF-T)
necessary to transport the narrowband bearer
service across the backbone network
Call Service Gateway Function (CSF-G):

Providing the service gateway actions
necessary to establish and maintain a backbone
network call and its associated bearer by
relaying signaling between CSF-N peers and
invoking the Bearer Control Gateway
Functions (BCF-G) necessary to transport the
narrowband bearer service between backbone
networks
Call Service Co-ordination Function (CSF-C):

Providing the call co-ordination and mediation
actions necessary to establish and maintain a
backbone network call by relaying signaling
between CSF-N peers. The CSF-C has no
association with any BCF
Providing gateway functionality between two

network domains
Containing one or more call service gateway

functions (CSF-G), and one or more bearer
interworking functions (BIWF)
Interacting with other GSNs in other backbone

network domains, and other ISNs and TSNs
within its own backbone network domain
Its network signaling flows equivalent to those

for a TSN

Issue 03 (2008-07-15)

13 BICC
Abbreviation
Full Name
Description
ISN
Interface Serving
Node
Providing the interface with non-BICC

networks and terminal equipment
Containing one or more call service nodal

functions (CSF-N), and one or more bearer
inter-working functions (BIWF)
Interacting with the non-BICC networks,

terminal equipment and its peers within the
BICC network
Interacting with the BCF
Providing the control of the bearer and MMSF.
MCF
Media Control
Function
(The precise functionality is outside the scope of

BICC.)
MMSF
Media
Mapping/Switching
Function
Providing the function of controlled

interconnection of two bearers and optionally the
conversion of the bearer from one technology
and adaptation/encoding technique to another
SN
Serving Node
Referring to ISN, GSN or TSN nodes
NBC
Network Bearer
Connection
Transporting user selected bearer services

between two or more TEs
STL
Signaling Transport
Layer
Any suite of protocol layers currently specified

to provide Transport and/or Network Layer
services to the BICC
(The functions, protocol and service primitives
are outside the scope of this specification.)
STC
SWN
Signaling Transport
Converter
A protocol layer between the STL and BICC
Enabling the BICC protocol to be independent

of the STL being used
Switching Node
Providing the switching functions within the

backbone core network
Containing a bearer control state machine

(BCF-R
Interacting with other SWNs and BIWFs
SCN
Switched Circuit
Network
A generic term for any network that uses circuit

switching technology, that is, ISDN, PSTN,
PLMN
TE
Terminal
Equipment
Representing the customers access equipment

used to request and terminate network associated
connectivity services
Issue 03 (2008-07-15)

13-7

13 BICC
Abbreviation
Full Name
Description
TSN
Transit Serving
Node
Providing transit functionality between ISNs

and GSNs
Containing one or more call service transit

functions (CSF-T), and one or more bearer
interworking functions (BIWF)
Interacting with other TSNs, GSNs and ISNs

within their own backbone network domain
Separation between Call and Bearer

The basic feature of BICC is the separation of call control and bearer control layers. This
enables the BICC specification to focus on Call Service Functions instead of taking bearer
control into account. See Figure 13-3. Such layered and independent architecture is fully
consistent with structurization and componentization design idea of a packet network.
Figure 13-3 Diagram of separation of call and bearer of BICC
Serving Node (SN)
Call Control Signaling
(BICC protocol)
Call Service Function

(CSF)
Call Control Signaling

(BICC protocol)
Main scope
of the BICC
specification
Bearer Control Signaling
Bearer Control Function

(BCF)
Bearer Control
Signaling
Bearer
As shown in Figure 13-4, the three-layer architecture of BICC is very clear:
13-8
BICC signaling is used between CSFs.
Bearer control signaling, such as Q.AAL2, is used between BCFs.
Transport of media streams (bearer streams) has nothing to do with BICC.

Issue 03 (2008-07-15)

13 BICC
Figure 13-4 Network model of BICC

BAT
ASE
ISUP
APM
ASE BICC
ASE
BICC
signaling
BICC
ASE
APM
ASE
BAT
ASE
BAT
ASE
CC
APM
ASE
BICC
ASE
CC
BCF
Bear
Bearer
control
signaling
Bearer
streams
Interface Serving Node (ISN)
BCF
BCF
Bear
Bear
Transit Serving Node (TSN)
APM: APplication transport Mechanism

BAT: Bearer Association Transport
ASE: Application Service Element

CC: Call Control
Protocol Model
Figure 13-5 shows the generic protocol model defined by BICC.
Figure 13-5 Generic protocol model of BICC
BICC procedures
generic interface
generic interface
Signaling
Transport
Converter
Mapping
Function
bearer specific
interface
transport specific
interface
Signaling
Transport
Layers
call control
protocol
Bearer
Control
bearer control
protocol
The protocol model of BICC regards the process of BICC as a "black box". It has two
interfaces to the BICC core network:
z
Signaling transport interface: It is used to package BICC messages in signaling transport

layer messages for interaction between BICC entities.
Bearer control interface: It is used for control and query of bearers.
BICC protocol model implies this idea: In order to make BICC fully independent of any other
parts of its interfaces such as signaling transport or bearer, BICC uses a converter to unify the
interfaces at the signaling transport interface point and the bearer control interface point.
From the point of view of BICC process, it provides only one set of abstracted operation
primitives externally. Then, by a "converting/mapping" component, primitive conversion with
the specific part, such as signaling transport or bearer, is achieved:
Issue 03 (2008-07-15)

13-9

13 BICC
z
At the signaling transport interface point, Signaling Transport Converter (STC) is used to
convert signaling transport primitives of BICC with specific Signaling Transport Layers
(STLs), such as with MTP3, MTP3B, SCTP, and M3UA.
At the bearer control interface point, the Bearer Mapping Layer is used to convert
abstract bearer control primitives of BICC with specific bearer control primitives, such
as with AAL1, AAL2, B-ISUP, IP, SS7-Bearer.
Signaling Capability Sets and Service Sets Supported by BICC

BICC protocol defines a call control signaling protocol used in a backbone network, including
SS7, ATM and IP networks. It can bear overall PSTN/ISDN services. Table 13-2 shows the
basic call signaling capability sets supported by BICC. Figure 13-4 shows the generic
signaling procedures, supplementary services and additional functions or services supported
by BICC.
Table 13-2 Signaling capability sets of a BICC basic call
13-10
Function/Service
National
International
Speech/3.1 kHz audio
64k bit/s unrestricted
Multirate connection types (Note

1)
N x 64k bit/s connection types
En bloc address signaling
Overlap address signaling
Transit network selection
Continuity indication
Forward transfer
Simple segmentation
Tones and announcements
Access delivery information
Transportation of User teleservice

information
Suspend and resume
Signaling procedures for

connection type allowing fallback
capability
Propagation delay determination

procedure
Simplified echo control signaling

procedures

Issue 03 (2008-07-15)

13 BICC
Function/Service
National
International
Automatic repeat attempt
Blocking and unblocking
CIC group query CIC
Dual seizure
Reset
Receipt of unreasonable signaling

information
Compatibility procedure (BICC

and BAT APM user application)
ISDN User Part signaling

congestion control
Note 2
Note 2
Automatic congestion control
Interaction with INAP
Unequipped CIC
ISDN User Part availability

control
Note 3
Note 3
MTP pause and resume
Note 2
Note 2
Overlength messages
Temporary Alternative Routing

(TAR)
Hop counter procedure
Collect call request procedure
Hard-to-Reach
Calling geodetic location

procedure
Carrier selection indication
Inter-nodal traffic group

identification
Codec negotiation and

modification procedures
Joint BIWF support
Global Call Reference procedure
Out of band transport of DTMF

tones and information
Issue 03 (2008-07-15)

13-11

13 BICC
"" indicates supported by ITU-T; "-" indicates not supported by ITU-T.
Multi rate connection types include 2 x 64, 384, 1536, and 1920 kbit/s.
If BICC uses MTP3B to transport signaling, these functions are provided by STC. Reference
Q.2150.1.
If BICC uses MTP3B to transport signaling, these processes are provided by STC. Reference
Q.2150.1.
Table 13-3 Generic signaling procedures, supplementary services and additional

functions/services of BICC
Function/Service
National
International
Generic number transfer
Generic digit transfer
Generic notification procedure
Service activation
Remote Operations Service

Element (ROSE) capability
Network specific facilities
Pre-release information transport
Application Transport Mechanism

(APM)
Redirection
Pivot routeing
Bearer redirection
Direct-Dialling-In (DDI)
Multiple Subscriber Number

(MSN)
Calling Line Identification

Presentation (CLIP)
Calling Line Identification

Restriction (CLIR)
Connected Line Identification

Presentation (COLP)
Connected Line Identification

Restriction (COLR)
Generic signaling procedures
Supplementary services
13-12

Issue 03 (2008-07-15)

13 BICC
Function/Service
National
International
Malicious Call Identification

(MCID)
Sub-addressing (SUB)
Call Forwarding Busy (CFB)
Call Forwarding No Reply

(CFNRy)
Call Forwarding Unconditional

(CFU)
Call Deflection (CD)
Explicit Call Transfer (ECT)
Call Waiting (CW)
Call HOLD (HOLD)
Completion of Calls to Busy

Subscriber (CCBS)
Completion of Calls on No Reply

(CCNR)
Terminal Portability (TP)
Conference calling (CONF)
Three-Party Service (3PTY)
Closed User Group (CUG)
Multi-Level Precedence and

Preemption (MLPP) (Note 1)
Global Virtual Network Service

(GVNS)
International telecommunication
charge card (ITCC)
Reverse charging (REV)
User-to-User Signaling (UUS)
Support of VPN applications with

PSS1 Information Flows
Support of GAT protocol
Support of Number Portability (NP)
Additional functions/services
Issue 03 (2008-07-15)

13-13

13 BICC
"" indicates supported by ITU-T; "-" indicates not supported by ITU-T.
Only information about transit MLPP is supported.
13.2.2 Message Structure

Message format for BICC is same as that for ISUP except that the routing label is absent and
Call Identification Code is replaced by Call Instance Code.
See Figure 13-6.
Figure 13-6 Format for BICC messages
Transmission sequence
8
Octet
Transmission sequence
Call Instance Code

Message type code
Mandatory fixed parameter A
Mandatory fixed part
Mandatory fixed parameter A
Pointer to parameter M
Pointer to parameter P
Pointer to start of optional part
Length indicator of parameter M
Mandatory variable part
Parameter M
Length indicator of parameter P

Parameter P
Parameter name = X
Length indicator of parameter X
Parameter X
Optional part
Parameter name = Z
Length indicator of parameter Z
Parameter Z
End of optional parameters
13-14

Issue 03 (2008-07-15)

13 BICC
Call Instance Code (CIC)

Call Instance Code (CIC) is a logic number associated with the inter-office calling relation. It
is used to identify which call instance this message corresponds to. From the point of view of
function, it is similar to Circuit Identification Code used in ISUP messages except that it does
not identify circuits and it is extended. The Circuit Identification Code has 12 bits. The Call
Instance Code is extended to 32 bits. Thus the number of inter-office call instances is up to
4,294,967,296 (232).
Message Type
The BICC message type code consists of a one-octet field and is mandatory for all messages.
The message type code uniquely defines the function and format of each BICC message, as
shown in Table 13-4. Code points marked as "ISUP only" in this table are reserved in BICC.
Table 13-4 BICC message type codes
Message Type
Code
Address complete
0000
0110
Answer
0000
1001
Application transport
0100
0001
Blocking
0001
0011
ISUP only
Blocking acknowledgement
0001
0101
ISUP only
Call progress
0010
1100
Circuit/CIC group blocking
0001
1000
Circuit/CIC group blocking

acknowledgement
0001
1010
Circuit/CIC group query (national use)
0010
1010
Circuit/CIC group query response

(national use)
0010
1011
Circuit/CIC group reset
0001
0111
Circuit/CIC group reset

acknowledgement
0010
1001
Circuit/CIC group unblocking
0001
1001
Circuit/CIC group unblocking

acknowledgement
0001
1011
Charge information (national use)
0011
0001
Confusion
0010
1111
Connect
0000
0111
Issue 03 (2008-07-15)
Description

13-15

13 BICC
13-16
Message Type
Code
Description
Continuity
0000
0101
Continuity check request
0001
0001
Facility
0011
0011
Facility accepted
0010
0000
Facility reject
0010
0001
Facility request
0001
1111
Forward transfer
0000
1000
Identification request
0011
0110
Identification response
0011
0111
Information (national use)
0000
0100
Information request (national use)
0000
0011
Initial address
0000
0001
Loop back acknowledgement (national

use)
0010
0100
Loop prevention
0100
0000
Network resource management
0011
0010
Overload (national use)
0011
0000
ISUP only
Pass-along (national use)
0010
1000
ISUP only
Pre-release information
0100
0010
Release
0000
1100
Release complete
0001
0000
Reset circuit/CIC
0001
0010
Resume
0000
1110
Segmentation
0011
1000
Subsequent address
0000
0010
Subsequent Directory Number (national

use)
0100
0011
Suspend
0000
1101

ISUP only
ISUP only
Issue 03 (2008-07-15)

13 BICC
Message Type
Code
Description
Unblocking
0001
0100
ISUP only
Unblocking acknowledgement
0001
0110
ISUP only
Unequipped CIC (national use)
0010
1110
User Part available
0011
0101
ISUP only
User Part test
0011
0100
ISUP only
User-to-user information
0010
1101
Reserved
0000
0000
0000
0010
0010
0010
0010
1010
1011
1111
0010
0011
0101
0110
used in 1984 version (Red

Book) ISUP
Reserved
0001
0001
0001
0010
1101
1100
1110
0111
used in 1988 version

(Blue Book) ISUP
Reserved
0011
1001
used in B-ISUP
to
Reserved for future extension
0011
1101
1000
0000
Parameter Parts
BICC message parameter parts include:
z
Mandatory fixed part
Mandatory variable part
Optional part
Each message type has unique parameters.
13.3 Signaling Procedures

Call procedures of the BICC protocol include:
z
Successful call setup procedures
Additional call setup procedures
Mid-call procedures
Normal release procedures
Issue 03 (2008-07-15)

13-17

13 BICC
Successful Call Setup Procedures

Bearer setup types lead to different call setup procedures. The main procedure types are:
z
Normal modes of each call corresponding to one bearer setup procedure: BNC forward
establishment, without notification; BNC forward establishment, notification; BNC
backward establishment
Tunnelling modes of each call corresponding to one bearer setup procedure: per-call
bearer setup using tunnelling fast forward; per-call bearer setup using tunnelling
delayed forward; per-call bearer setup using tunnelling backward
Modes of re-using idle bearer: use of idle BNC, established in the forward direction; use
of idle BNC, established in the backward direction
In the case of using IP bearer, the current procedure for tunnelling forward setup mode is
shown in Figure 13-7.
Figure 13-7 Delayed forward bearer setup, with notification
ISN-A
ISN-B
TSN
ISUP
BICC
ISUP
BICC
CSF-N
CSF-N
CSF-T
BCF-N
(x)
SWN-1
BCF-R
SWN-2
BCF-R
SWN-1
BCF-R
BCF-N
(y)
SWN-2
BCF-R
BCF-N
(z)
IAM
IAM (Action = Connect Forward) , (BNC characteristics)
APM (Action = Connect Forward, plus notification)
IAM (COT on previous), (Action = Connect Forward) ,

(BNC characteristics)
AAA
APM (Action = Connect Forward plus notification)
APM (Tunnel data)

APM (Tunnel data)
APM (Tunnel data)

APM (Tunnel data)
APM (Action = Connected)
COT
BBB
ACM
ACM
ACM
ACM
ANM
ANM
ANM
ANM
Additional Call Setup Procedures

To support the separation of bearer and control, BICC supports the following procedures:
z
Codec negotiation
Codec modification
See Figure 13-8.
13-18

Issue 03 (2008-07-15)

13 BICC
Figure 13-8 Forward setup, with codec negotiation

ISN-A
ISN-B
TSN
ISUP
BICC
ISUP
BICC
CSF-N
CSF-N
CSF-T
SWN-1
BCF-R
BCF-N
(x)
SWN-2
BCF-R
SWN-1
BCF-R
BCF-N
(y)
SWN-2
BCF-R
BCF-N
(z)
IAM
IAM (Action = Connect Forward) , (BNC
characteristics), ( Codec list)
IAM (COT on previous), (Action = Connect Forward) ,
(BNC characteristics), (Codec list)
AAA
APM (Action = Connect Forward plus notification
+ Selected
codec), (BNC-ID= z1), (BIWF Addr= z),
(Selectedcodec), (Available codec list)
APM (Action = Connect Forward, plus notification

+ Selected
codec), (BNC-ID=y1), (BIWF Addr=y)
(Selectedcodec), (Availablecodec list)
Bearer Set-up req. (BNC-ID= z1), (BIWF- Addr= z)
Bearer Set-up req. (BNC-ID=y1), (BIWF- Addr=y)
Bearer-Set-up
Bearer-Set-up req
Bearer-Set-up req
req
Bearer-Set-up req
Bearer-Setup-Connect

COT
ACM
ACM
BBB
ACM
ANM
ACM
ANM
ANM
ANM
Mid-Call Procedures
To support the separation of bearer and control, BICC supports the following procedures:
z
Mid-call codec negotiation
Codec modification
See Figure 13-9.
Issue 03 (2008-07-15)

13-19

13 BICC
Figure 13-9 Mid-call codec negotiation containing w

SN-A
SN-B
TSN
BICC
BICC
CSF-N
BCF-N
(x)
SWN-1
BCF-R
CSF-N
CSF-T
APM (Action = Suc cessful code c modific ation )
SWN-2
BCF-R
SWN-1
BCF-R
BCF-N
(y)
SWN-2
BCF-R
BCF-N
(z)
APM (Action = Mid-call codec negotiation), (Supported codec list)

APM (Action = Mid-call codec negotiation), (Supported codec list)
APM (Action = Modify to selected codec information), (Selected codec and/or Codec list)
Bearer Modify
Bearer Modify Bearer Modify
Bearer Modify Ack
Bearer Modify Ack
Bearer Modify Ack
Optionally sent to modify

codec profile and/or allocate
additional bandwidth.
APM (Action = Modify to selected codec information), (Selected codec and/or Codec list)
Bearer Modify
Bearer Modify
Bearer Modify
Bearer Modify Ack

Bearer Modify Ack
Optionally sent to modify

codec profile and/or allocate
additional bandwidth.
Bearer Modify Ack
APM (Action = Successful codec modification)

APM (Action = Successful codec modification)
Bearer Modify
Bearer Modify
Bearer Modify
Bearer Modify
Bearer Modify Bearer Modify
Optionally sent to
reduce bandwidth
Bearer Modify Ack
Bearer Modify Ack
when no longer
Bearer Modify Ack
Bearer Modify Ack
required.
Bearer Modify Ack
Bearer Modify Ack
Optionally sent to
reduce bandwidth
when no longer
required.
Normal Release Procedures

According to different bearer setup types, there are the following release procedures:
z
Forward call and bearer release
Forward bearer setup
Forward call and bearer release
Backward bearer setup
Forward call release
Bearers not released
See Figure 13-10.
13-20

Issue 03 (2008-07-15)

13 BICC
Figure 13-10 Forward call and bearer release, forward bearer setup mode
ISN-A
ISN-B
TSN
ISUP
BICC
BICC
CSF-N
ISUP
CSF-N
CSF-T
BCF-N
SWN-1
BCF-R
SWN-2
BCF-R
SWN-1
BCF-R
BCF-N
SWN-2
BCF-R
BCF-N
REL
REL
REL
RLC
REL
RLC
RLC
RLC
Bearer release req.

Bearer release Ack. Bearer release req.
Bearer release Ack.
Bearer release req.
Bearer release req.

Bearer release Ack. Bearer release req.
Bearer release Ack.

Bearer release Ack.
Bearer release req.

Bearer release Ack.
Issue 03 (2008-07-15)

13-21

BICC

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

BICC

Загружено:

Авторское право:

Доступные форматы

HUAWEI GSM-T GTSOFTX3000

Technical Manual Signaling and Protocols

Huawei Proprietary and Confidential

HUAWEI GSM-T GTSOFTX3000

Huawei Proprietary and Confidential

HUAWEI GSM-T GTSOFTX3000

Huawei Proprietary and Confidential

HUAWEI GSM-T GTSOFTX3000

About This Chapter

The definition, function, and application of the BICC

13.2 Introduction of BICC

The concept and message structure of the BICC protocol.

13.3 Signaling Procedures

The signaling procedures of the ISUP protocol.

Huawei Proprietary and Confidential

HUAWEI GSM-T GTSOFTX3000

Establishing, modifying and terminating calls

Bearing comprehensive PLMN/PSTN/ISDN services

13.1.1 Definition and Functions of the Nc Interface

Functions of the Nc Interface

User-level bearer technology

Control-level signaling transport technology

13.1.2 BICC Implementation in GTSOFTX3000

Huawei Proprietary and Confidential

HUAWEI GSM-T GTSOFTX3000

13.1.3 Structure of the Protocol Stack

TDM based MTP3

ATM based MTP3b

See Figure 13-2.

13.2 Introduction of BICC Protocol

Supporting basic call procedures

Supporting supplementary service features

Huawei Proprietary and Confidential

HUAWEI GSM-T GTSOFTX3000

The additional Application Transport Mechanism (APM) in BICC makes it possible to

Bearer setup mode

Supported Codec list

13.2.1 Basic Concepts

Representing the edge to edge transport

Representing a segment of the end to end

Representing the transport facility between two

Huawei Proprietary and Confidential

HUAWEI GSM-T GTSOFTX3000

Five types of BCFs are defined.

Bearer Control Joint Function (BCF-J):

Bearer Control Gateway Function (BCF-G):

Bearer Control Nodal Function (BCF-N):

Bearer Control Relay Function (BCF-R):

Bearer Control Transit Function (BCF-T):

Representing the signaling relationship between

Providing BCF and media mapping/switching

Containing one BCF (BCF-N/BCF-T/BCF-G)

Functionally equivalent to a Media Gateway

A physical unit functionality similar to a BIWF

Huawei Proprietary and Confidential

HUAWEI GSM-T GTSOFTX3000

Defining the peer to peer signaling association

Providing CSF-C functions without an

Four types of CSF are defined.

Call Service Nodal Function (CSF-N):

Call Service Transit Function (CSF-T):

Call Service Gateway Function (CSF-G):

Call Service Co-ordination Function (CSF-C):

Providing gateway functionality between two