Professional Documents
Culture Documents
[
1]
O-BCSM (Originating BCSM)
T-BCSM (Terminating BCSM)
A fundamental concept for IN control is the basic call state model (BCSM). When
a call is
processed by an exchange, the call goes through a number of pre-defined phases.
These phases of the call are described in the BCSM. The BCSM generally follows t
he ISUP
signalling of a call
O-BCSM
Points in call
1. O_Null & Authorize Origination Attempt
2. Collect_info (Merged with 1. in CAMEL Ph1)
3. Analyze_Info
4. Routing & Alerting (Merged with 3. in CAMEL Ph1)
5. O_Active
6. O_Exception
Detection Points
1 Origination_Attempt_Authorized
2 Collected_Info
3 Analyzed_Info (this is the only Statically armed DP, others are dynamically ar
med using "Request Report BCSM (RRBE)" message by the SCP)
4 Route_Select_Failure
5 O_Called_Party_Busy
6 O_No_Answer
7 O_Answer
8 O_Mid_Call
9 O_Disconnect
10 O_Abandon
T-BCSM
Points in call
7. T_Null & Authorize Termination_Attempt
8. Select_Facility & Present_Call
9. T_Alerting (Merged with 8. in CAMEL Ph1)
10. T_Active
11. T_Exception
Detection Points
12 Termination_Attempt_Authorized
13 T_Called_Party_Busy
14 T_No_Answer
15 T_Answer
16 T_Mid_Call
17 T_Disconnect
18 T_Abandon
Messages
basic INAP call example
Initial Detection Point (IDP)
RRB (Request Report BCSM)
Event Report BCSM (ERB)
Connect (CON)
Continue (CONT)
Send Charging Information (SCI)
ACH (Apply Charging)
ACR (Apply Charging Report)
================================================================================
==
http://telecomprotocols.blogspot.com.br/2012/09/intelligent-networks-in-and-came
l.html
SPS-Teklec STP -EIR - M2PA
SPS-MSS(Msoft) - M3UA
=========================================================
Intelligent Networks (IN):Intelligent Networks is a concept service intelligence resides in a central node
called an SCP and SSPs (residing on Switches) relinquish control to this node a
t particular stages in a call so that appropriate service logic can be applied.
Objectives of IN:
-
Network Before IN: Before IN application, there was messed network for every nod
e:
Network with IN: After IN implementation, Network is organised.
Basic Concepts
to notify
it of an event. Processing is not suspended when encountering the DP.
- Event Detection Point
Request (EDP-R): This detection point is dynamically armed within
the context of a CAMEL control relationship. Processing is suspended when encou
ntering the DP
and the gsmSSF waits for instructions from the gsmSCF.
- Service Switching Function (SSF) This is co-located with the MSC itself, and a
cts as the
trigger point for further services to be invoked during a call.
- Service Control Function (SCF) This is a separate set of platforms that receiv
e queries
from the SSP.
- Service Data Function (SDF) This is a database that contains additional subscr
iber data, or
other data required to process a call.
- Specialized Resource Function (SRF) or Intelligent Peripheral (IP) This is a n
ode which can
connect to both the SSP and the SCP and delivers additional special resources in
to the call,
for example play voice announcements or collect DTMF tones from the user.
Customized Applications for Mobile networks Enhanced Logic, or CAMELfor short, i
s a set of
standards designed to work on either a GSM core network or UMTS network. They al
low an operator
to define services over and above standard GSM services/UMTS services. The CAME
L architecture
is based on the Intelligent Network (IN) standards, and uses the CAP protocol an
d it is particularly
effective in allowing these services to be offered when a subscriber is roaming
.
CAMEL Network Structure:
-CSI identifies if the subscriber requires CAMEL support. CSI identifies which g
smSCF to use
for that CAMEL support. CSI contains information related to the Operator Specifi
c Service (OSS)
of the subscriber, for example the Service Key.
Originating-CSI identifies subscriber as having originating CAMEL Services. O-CS
I is stored in
the VLR as part of subscriber data for roaming subscriber in the VLR area.
Terminating-CSI identifies subscriber as having terminating CAMEL Services. T-CS
I is fetched by
the GMSC when the HLR of the called subscriber is being interrogated by the GMSC
.
Originating-CSI is sent to the GMSC for forwarding.
CSI CONTENT gsmSCF address: as an E.164 number
Service Key : which identifies to the gsmSCF the service logic that should be
used.
Default call handling: that indicates how to proceed the call in case of error
in the dialogue (release or continue).
TDP list: that indicates on which Detection Point (DP) triggering shall take pla
ce. Only DP2 for O-CSI and only DP12 for T-CSI.
MSC
VLR
B-Party
============================================================
Setup
>
SIOC(IN) ->
< Complete Call(IN)
INITDP(2) >
<
Continue
SIOC(No IN) ->
< Complete Call
< Call Proc/Assnmt ->
IAM
>
SCP
DP2 (OCSI)
Service Screened in first SIOC: COS, ODB (BAOC & BAOC roaming outside the HPLMN
Country), BAOC, CUG, IN (O-CSI)
Service screened in second SIOC: Remaining flavos if ODB and barring, LCO, OSSP
screening.
DP12 Trigger Detection Point:
A-Party
MSC
HLR
B-Party
============================================================
IAM
>
SRI
->
< SRI ACK(IN)
INITDP(12)
>
<
CONTINUE
SRI
->
< SRI ACK
Paging
SCP
>
>
A-Party
MSC-A
HLR
SCP
PSTN
==================================================================
IAM
>
SRI
>
<-SRI ACK(CFU,TCSI & OCSI)
-INITDP(12)
>
<
CONTINUE
INITDP(2)
>
<
CONNECT
-IAM
>
Applying O-CSI to a call forwarded by CAMEL (T-CSI) : CAMEL can be used to forwa
rd calls, instead of using GSM Call Forwarding. It is possible to apply an O-CSI
CAMEL service to the outgoing leg created by a CAMEL forwarding service.
A-Party
MSC-A
HLR
SCP
PSTN
===================================================================
IAM
>
SRI
->
< -SRI ACK (TCSI & OCSI)
-INITDP (12) ->
< -CONNNECT(DRA + OCSI)
INITDP(2)
>
<
CONNECT(CLI Modified) IAM(with modified CLI) >
ANSWER Event Detection Point- Notify:
A-Party
MSC
HLR
SCP
PSTN
==================================================================
IAM
>
SRI
->
< -SRI ACK(TCSI )
INITDP(12)
>
< -RRBE(EDP, T_Answer)
CONNECT(PSTN)
->
-IAM
->
<
-ACM
<
-ACM
<
-ANM
<
-ANM
Disconnect Event Detection Point- Request:
A-Party
MSC
HLR
SCP
PSTN
=================================================================
IAM
>
SRI
>
< -SRI ACK(TCSI )
-INITDP(12)
>
<
-RRBE(EDP, T_Answer)
ERB
->
CONNECT(PSTN)
-IAM
<
<
-ACM
<
-ANM
<
REL ->
-ACM
-ANM
->
-ERB
Continue
<
>
-REL
-REL
<
<
->
>
RLC -
External IP Connection:
A-Party
MSC
VLR
SCP
IP
MS
================================================================================
setup
>
SIOC
->
< Continue(OCSI ) INITDP(2)
>
< ETC(IP)
-PRI Connection Established
>
-DFC
-PRI Connection Trerminated
Continue
-Paging
>
Example of VPN: An example of MO CAMEL Phase 1 service is VPN. User A subscribes
to VPN,
the CSI (stored in the HLR) is copied to the VLR at Location Update.
After dialing a short number (1) (e.g.colleague s extension), the call is
stopped by the SSF which requests instructions from the SCF (2). The SCF gives t
he SSF
the full number (3) that the VMSC uses to route the call to the GMSC (4).
Callee
VMSC
SCP
GMSC
================================================================================
Setup(1234)
>
<
<
<
<
-INITDP(1234)
>
-CONNECT(0122334343)
IAM
>
An example of an MT CAMEL Phase 1 service is Time Dependent Routing (TDR).
A subscriber can decide where his calls will be routed depending on the period o
f the
month/ week or even the time of the day (e.g. to his mobile, voice mail, secreta
ry fixed line).
When the GMSC receives the called party CSI (6),the SSF stops the call to reques
t instructions
from the SCF (7).The SCF provides routing information to the SSF so that the ca
ll is routed
to the subscriber s mobile since he is willing to accept calls at this time of the
day (8).
Within CAMEL we are CAMEL Phase 1 compliant. Hence all the following CAMEL Phase
1
operations are available currently in the MSC/SSP:
ActivityTest
Connect
Continue
EventReportBCSM (ERB)
InitialDP
ReleaseCall
RequestReportBCSMEvent (RRBE)
The following new operations are implemented to support CAMEL Phase 2:
ETC (EstablishTemporaryConnection)
DFC (DisconnetForwardConnection)
FCI (FurnishChargingInformation)
ResetTimer
ApplyCharging (AC)
ApplyChargingReport (ACR)
Send Charging Information (SCI)
Play Announcement
Connect To Resource (for SRF)
Prompt and Collect User Information
Call Information Request (CIR)
Call Information Report
IEs:
Initial DP (IDP): - from gsmSSF to gsmSCF to collect the information
Called PartyNumber
Calling party Number
Calling Party category
Location Number
Original Called Party ID
Additional CallingParty Numer
Bearer Capability
Redirection PartyID (Redirection Number)
IMSI
Location Information
ext-Basic Service Code
Callforwarding SS Pending
MSC Address
time and timezone
carrier
service key (m)
highLayer capability (HLC)
eventtype BCSM
Redirection Information
subscriber state
cug-index/cug-interlock/cug-OutgoingAccess
High Layer Capability (HLC)
CONNECT:
- from gsmSCF to gsmSSF to connect to new number.
Destination Routing Address (DRA)
Alerting Pattern
Original Call party ID
carrier
Calling Party Category
Redirection Party ID
Redirection Info
Generic Number
charge number
supperssion of annoucement
oCSI Applicable
Activity Test: - AT is used to check for the continued existance of a relationship
between the gsmSCF and gsmSSF. no IE.
Apply Charging:- from gsmSCF to gsmSSF, charging mechanisms to control the call
duration.
-ACh Billing Charging Characteristics:- Time Duration Charging:- Max call period
=====================================================
Interfaces
We next explore the GSM-MAP interfaces between the equipment entities of
There are some differences from the IS-MAP interfaces.
The interface between a MSC and its associated VLR is known as the B interface.
ETSI considers the B interface as internal and does not define it. The
message transfer does not involve the signaling network.
The C interface is between a gateway MSC and the HLR in its PLMN. The D
interface is between a VLR and a HLR, in the same or different PLMNs.
The E interface is between adjacent MSCs in a PLMN and is used in handover
operations.
The F interface is an intra-PLMN interface, between a MSC and the EIR.
The G interface is between VLRs, in the same or in different PLMNs. This interfa
ce
does not exist in IS-MAP.
In GSM-MAP, the AUC is an integral part of HLR, and no interface is defined.
======================================================
Information in SIM
.
.
.
.
.
IMSI (S)
TMSI (T)
LAI (T)
Ki (S), authentication key
Kc (T), cipher key
subsystem
(SSNs):
0000 0110
0000 0111
0000 1000
0000 1001
numbers
Home location register
Visitor location register
Mobile switching center
Equipment identity register
HLR
VLR
MSC
EIR
In SCCP called (CDA) and calling (CGA) addresses, SSN is always present. In
addition, the addresses include a point code (PC) and/or a global title (GT). Th
is
depends on locations of the entities involved in the transaction:
. If both entities are in the same PLMN, the address is a point code.
. If both entities are in the same country but in different PLMNs, the address i
s a
global title with the format of an E.164 number, according to the numbering
plan for the fixed network in that country.
. If the entities are in different countries, the address is a global title with
a format
defined in ITU-T Rec. E.214
==========================================