Вы находитесь на странице: 1из 47

Study Themes - Overview

Lecture Block 1 - August 22 - 23, 2005

Study Theme 1: Introduction - NGN Services, Service Delivery Platforms and Standards

Study Theme 2: Intelligent Networks (IN) - Basics and Standards

Study Theme 3: Intelligent Networks (IN) in Wireless – 3GPP CAMEL

 

Study Theme 4: Open Network APIs (CORBA, Java) – OSA / Parlay / JAIN

Study Theme 5: Open Network APIs (Web Services) – Parlay X / OMA Web Services

Lecture Block 2 - October 3 - 4, 2005

Study Theme 6: NGN Protocols – SIP, DIAMETER

Study Theme 7: IMS Basics and Standards overview

Study Theme 8: IMS Architecture and Operation in Detail

Study Theme 9: IMS Application Server Options and Applications

Study Theme 10: Summary and Outlook

1

StudyStudy ThemeTheme 33 CAMELCAMEL

Mobile value added service: Prepaid, VPN, VHE

CAMEL architecture and service provisioning

3GPP Standardisation approach - Phases

Phase 1 - Starters CAMEL - Prepaid roaming: Services, architecture, protocols

Phase 2 - Real CAMEL/VPN, Services, architecture, protocols

Phase 3 - CAMEL for GPRS/SMS: Services, architecture, protocols

Phase 4 - CAMEL for Multiparty services: Services, architecture, protocols

CAMEL Deployment status and Interoperability issues

2

Motivation for CAMEL

• GSM is a big success

• based on strict standards ensuring interoperability but providing limited degree of service differentiation

• Value added services are key for new revenues Mobile Prepaid

• Service Nodes enhance service portfolio but are limited to own network (no roaming support or specific solutions!!!)

Idea:

Extend IN concept to mobile domain, but keep it focused CAMEL

• Main challenges:

– IN in fixed networks did never support service interoperability but in mobile networks we are confronted with roaming users

– In mobile networks we have strong heterogeneity of service platforms

3

Business Drivers for CAMEL

Service, Services, Services

• The 1st ( and still main) reason for implementing Camel is international roaming :

GSM PrePaid

– USSD- Call Back is a nightmare for end-users

– Temporary PostPaid subscription is a nightmare for operators (and refused by end users)

VPN : ‘virtual company’ doesn’t stop at the border

VHE : everywhere like at home.

– How to call my customer care ?

– How to get my voice mails ?

– How to recharge my PrePaid account ?

Ë Camel increases roaming revenues

4

Prepaid Roaming – A Killer Application Situation today with Service Node: NO Prepaid Roaming or
Prepaid Roaming – A Killer Application
Situation today with Service Node: NO Prepaid Roaming or very specific quick hack
• Different vendors
(IN,SSS)
HPLMN
VPLMN
• Different INAP versions
SN
INAP*
• No Roaming for Prepaid
MSC
MSC
MSC
MSC
subscribers
ISUP
ISUP
ISUP
IN
• Other IN Services are not
Subscriber
available abroad
Roaming not
possible for PPS
Subscriber
• Roaming for normal GSM
subscribers possible
5
Prepaid forecast: still growing !!
6
Evolution towards roaming Prepaid Support • Before CAMEL: USSD-based Call Back • CAMEL Phase 1:

Evolution towards roaming Prepaid Support

Before CAMEL: USSD-based Call Back

CAMEL Phase 1:

Simplified Call Handling

Home-network SCP based rerouting

CAMEL Phase 2:

The real thing!

7

based rerouting • CAMEL Phase 2: – The real thing! 7 Pre-CAMEL: USSD-based Call Back System

Pre-CAMEL: USSD-based Call Back

System works like wake-up call – SCP/SN initiates call (on request)

HPLMN VPLMN 2 HLR 1 SN USSD INAP SSP SSP MSC ISUP ISUP 3 Roaming
HPLMN
VPLMN
2
HLR
1
SN
USSD
INAP
SSP
SSP
MSC
ISUP
ISUP
3
Roaming
4
Subscriber =
Calling Party
Called Party

÷ Dial number (USSD String)

plus hang -up again

÷ IN-System calls back

÷ A-Party picks up

÷ B-Party picks up

8

Aspects concerning pre-CAMEL roaming

PROs:

- Prepaid cards can be used abroad

- Support of all common handsets with USSD capability

- Existing infrastructure can be upgraded easily

- Elimination of fraud due to online charging

- Roaming agreements for postpaid subscribers could be used

CONs:

- No online charging for SMS

- Additional speech trunks and longer call setup times

- Service is not the same for the user

9

3GPP CAMEL

CAMEL = Customized Applications for Mobile Enhanced Logic

CAMEL

Is the use of IN in mobile circuit switched and packet switched networks:

GSM/GPRS

IN-based architecture enabling to offer operator specific services (OSS) to mobile subscribers even when roaming in another network (international roaming)

CAMEL enables inter-network GSM/GPRS service control, by reusing the existing international signaling transport infrastructure

CAMEL Application Protocol (CAP) is based on IN Capability Sets 1 and 2

CAMEL additionally exploits Mobile Application Part (MAP)

CAMEL Standardisation started in 1994 (as a GSM Phase 2+ Feature)

CAMEL evolves in Phases, which are part of Releases!!!

10

Basic GSM / GPRS architecture HLR MA P Interrogating VLR Network VMSC GMSC PSTN Roaming
Basic GSM / GPRS architecture
HLR
MA
P
Interrogating
VLR
Network
VMSC
GMSC
PSTN
Roaming
PLMN
Leg
CS
PSTN/PLMN
PSTN/PLMN
GPRS
SGSN
GGSN
PDN
Visited Network
Home Network
11
CAMEL Phase 1 architecture
gsmSCF
MAP
HLR
MAP
CAP
Interrogating
gsmSSF
VLR
gsmSSF
Network
VMSC
GMSC
PSTN
Roaming
PLMN
Leg
CS
PSTN/PLMN
PSTN/PLMN
Visited Network
Home Network
12
 

Prepaid Roaming with CAMEL

 
HPLM VPLMN N SCP CAP INAP, CAP SSP SSP SSP SSP ISUP ISUP ISUP Roaming
HPLM
VPLMN
N
SCP
CAP
INAP,
CAP
SSP
SSP
SSP
SSP
ISUP
ISUP
ISUP
Roaming
IN
Subscriber
Roaming
possible for PPS
Subscriber

Standardized Interfaces CAMEL Application Part (CAP)

IN services are available internationally

Own IN Subscribers are able to roam

Foreign IN Subscribers may be supported, too

IN user database may be used for new / advanced services, e.g. m-payment

 

13

 

CAMEL Phases

Camel Phase 1

 

Basic Call Control functionalities for GSM calls

Camel Phase 2

 

– ApplyCharging in VPLMN : GSM calls are monitored directly in VPLMN

 

– Announcement : access to annoucements directly from the VPLMN

Camel Phase 3

 

– Handling of GPRS Sessions and pdp-contexts for session control, monitoring (location update, QoS,…) and charging (time and volume triggers)

 

– Support of SMS-MO through CS and PS networks

 

– Anytime interrogation and modification of customer data in HLR

 

– Mobility management enhancements

 

Camel Phase 4

– Multi-leg GSM call handling

– Creation of a new GSM call

– PLUS: Interworking with IP Multimedia Subsystem

 

14

 

CAMEL Phase 1: Re-routing via Home network

 
 

Limited CAP operations:

CSE

(SCP)

CAP

Dialogue

2

- i.e. no charging operations

Home

PLMN

Visited

PLMN

INAP 5 SSP 3 Dialogue VLR MSC 6 4 SSP SSP 1 HLR MSC GMSC
INAP
5
SSP
3
Dialogue
VLR
MSC
6
4
SSP
SSP
1
HLR
MSC
GMSC
7
7
Roaming
subscriber
Called user

2

3

1

5

4

6

7

-

-

-

-

-

Route to Home PLMN

Receive Connect

Subscriber dials number

Send Initial Detection Point (IDP)

Problem: network tromboning!

Connect to B-party via Gateway MSC

But: 80-90% of all calls are directed to the home network!

15

 

Aspects concerning CAMEL Phase 1 roaming

 

PROs:

- Support of all common handsets

 

- Existing infrastructure can be upgraded easily (parallel protocols supported many vendor solutions)

 

- Elimination of fraud due to online charging

 

- Roaming agreements for postpaid subscribers could be used

- First step towards standard implementation

- Enabling of inbound roaming with CAP1

- Service looks / feels the same as for postpaid users

CONs:

- No online charging for SMS

 

- Additional speech trunks needed

 

16

CAMEL Phase 2: Full Roaming

 
 

Enhanced CAP operations:

 

full charging operations

control of announcements

- CAP CSE - Dialogue (SCP) 2 SSP 3 VLR MSC IP
-
CAP
CSE
-
Dialogue
(SCP)
2
SSP
3
VLR
MSC
IP

HLR

SSP

MSC

SSP

GMSC

4

1

roaming

Home

PLMN

 

Visited

PLMN

1

2

3

4

-

-

-

-

subscriber

Subscriber dials number

Send Initial Detection Point (IDP)

Receive Connect

Connect to B-party directly

17

Aspects concerning CAMEL Phase 2 roaming

 

PROs:

- Support of all common handsets

 

- Existing infrastructure can be upgraded easily (parallel protocols supported by many vendors)

 

- Elimination of fraud due to online charging

 

- Roaming agreements for postpaid subscribers can be used

- Enabling of inbound roaming with CAP2

- Service looks / feels the same as for postpaid user

- Saving speech trunks for rerouting

CONs:

-

No online charging for SMS

 

18

CAMEL Phase 1

19

CAMEL Phase 1 Services

Control of outgoing calls at the served subscriber’s VMSC: number translation, selective barring or enabling of calls depending on location, time of day,

Control of incoming calls at the GMSC: re-routing, selective barring or enabling of calls depending on location, time of day, calling party identity, …

Clearing the call at any time, using the CAMEL control at the originating or terminating side

Any Time Interrogation: Location information and subscriber state

20

CAMEL Phase 1 architecture gsmSCF MAP HLR MAP CAP Interrogating gsmSSF VLR gsmSSF Network VMSC
CAMEL Phase 1 architecture
gsmSCF
MAP
HLR
MAP
CAP
Interrogating
gsmSSF
VLR
gsmSSF
Network
VMSC
GMSC
PSTN
Roaming
PLMN
Leg
CS
PSTN/PLMN
PSTN/PLMN
Visited Network
Home Network
21
CAMEL Subscription Information
• Major challenges in deploying IN services in mobile networks:
– lack of centralized Service management system (SMS) responsible for
trigger activation and criteria deployment
– Changing access networks (multiple visited networks)
• Solution: CAMEL Subscription Information (CSI) containing trigger
information
• CSI is defined in a service specific way as part of HLR data and will
thus be dynamically deployed in relevant service entities (e.g. VLR,
SGSN, HLR, SMS-C, etc.) for roamed in users
• Service triggering entities make use of CSI for determining if CSE
needs to be contacted
Ë Refer to 3GPP TS 23.078 for detailed descriptions of the various types of
CAMEL Subscription Information.
22
CAMEL Subscription Information (cont.) CSI Examples (for CAMEL Phase 1): – Originating CAMEL Subscription Information
CAMEL Subscription Information (cont.)
CSI Examples (for CAMEL Phase 1):
– Originating CAMEL Subscription Information (O-CSI)
is transferred to the VPLMN (at location update) and to the IPLMN (for an
incoming call in the GMSC).
O-CSI contains trigger information that is required to invoke a CAMEL Service
Logic for Mobile Originating calls (in the VMSC) and Mobile Forwarding calls (in
the VMSC and the GMSC).
– Terminating CAMEL Subscription Information (T-CSI)
is transferred to the IPLMN for an incoming call in the GMSC.
T-CSI contains trigger information which is required to invoke a CAMEL Service
Logic for Mobile Terminating calls in the GMSC.
23
CAMEL Phase 1 architecture
gsmSCF
MAP
HLR
MAP
CAP
O-CSI
Interrogating
gsmSSF
VLR
gsmSSF
Network
T-CSI
O-CSI
VMSC
GMSC
PSTN
Roaming
PLMN
Leg
CS
PSTN/PLMN
PSTN/PLMN
Visited Network
Home Network
24
CAMEL Phase 1 BCSMs and CAP CAMEL - BCSM and CAMEL Application Part (CAP) Protocol
CAMEL Phase 1 BCSMs and CAP
CAMEL - BCSM and CAMEL Application Part (CAP) Protocol
• CAMEL features are based on a simplified IN CS-1 BCSM supporting
– 6 Detection Points (3 DPs in O-BCSM, 3 DPs in T -BCSM)
– 2 Trigger Detection Points
• Collected Information (O-BCSM)
• Termination Attempt Received (T -BCSM)
• CAMEL Application Part (CAP)
is based on ETSI Core INAP comprising seven operations:
InitialDP, Continue, Connect, Release Call, EventReportBCSM,
RequestReportBCSMEvent, Activity Test
25
CAMEL Phase 1 O_BCSM
O_Null & Authorize_Orgination_
Attempt & Collect_Info
O_Exception
DP2
Collected_Info
Analyse, Routing & Alerting
DP7
O_Answer
DP9
O_Active
O_Disconnect
26
CAMEL Phase 1 T_BCSM T_Null T_Exception DP12 Term Attempt_Authorized Terminating Call Handling DP15 T_Answer DP17
CAMEL Phase 1 T_BCSM
T_Null
T_Exception
DP12
Term
Attempt_Authorized
Terminating Call Handling
DP15
T_Answer
DP17
T_Active
T_Disconnect
27
CAMEL Detection Point Types
Three different types of DPs are identified in CAMEL
• Trigger Detection Point - Request (TDP-R).
This detection point is statically armed and initiates a CAMEL control
relationship when encountered and there is no existing relationship due to
the same CSI. Processing is suspended when the DP is encountered.
• Event Detection Point - Request (EDP-R).
This detection point is dynamically armed within the context of a CAMEL
control relationship. Processing is suspended when encountering the DP
and the gsmSSF waits for instructions from the gsmSCF.
• Event Detection Point - Notification (EDP-N).
This detection point is dynamically armed within the context of a CAMEL
control relationship. Processing is not suspended when encountering the
DP.
28
Arming of DPs • A DP for mobile terminating call handling is statically armed in
Arming of DPs
• A DP for mobile terminating call handling is statically armed in GMSC as
result of T-CSI delivery from HLR.
• A DP for forwarding leg handling is statically armed in GMSC as result of O-
CSI delivery from HLR.
• A DP for mobile originating call or forwarded leg handling is statically armed
in VMSC as result of O-CSI delivery from VLR.
A DP is dynamically armed by the gsmSCF within the context of a
CAMEL control relationship (between the gsmSSF and the gsmSCF).
29
CAMEL 1 Detection Points List
TDP
TDP
30
 

CAMEL Application Protocol (CAP) Phase 1

gsmSSF to gsmSCF

– Activity Test Response

– Event Report BCSM

– Initial DP

gsmSCF to gsmSSF

– Activity Test

– Connect

– Continue

– Release Call

– Request Report BCSM Event

31

 

PrePaid for CAMEL Phase 1 (1)

PrePaid „light“ Service using CAMEL phase 1

 

no Announcements

USSD based account enquiry and top-up

gsmSCF releases call based on account balance

 

Advantage:

Works with CAMEL1

No tromboning of call legs

Disadvantage:

New User Interface,

Timer resources at SCP needed,

higher inaccuracy in account handling,

effectively new service to be designed

32

Example: MOC with CAMEL – CSI Provision

O-CSI CSE gsmSCF T-CSI Home Network HLR 2 1 Destination Network Visited Network O-CSI VLR
O-CSI
CSE gsmSCF
T-CSI
Home Network
HLR
2
1
Destination Network
Visited Network
O-CSI
VLR
gsmSSF
MSC
Location Update and Capability
Negotiation Phase
1 Location Update Request

2 Insert Subscriber Data (O-CSI)

33

MOC with CAMEL Phase 1 PrePaid „light“

CSE gsmSCF

with CAMEL Phase 1 PrePaid „light“ • C S E gsmSCF O-CSI T-CSI Home Network HLR
O-CSI T-CSI
O-CSI
T-CSI
Home Network HLR 4 7 5 Visited 6 Network O-CSI VLR gsmSSF MSC 3 6
Home Network
HLR
4
7
5
Visited
6
Network
O-CSI
VLR
gsmSSF
MSC
3
6 Initial Address Message
3
Call Setup

Destination Network

Call Setup and Completion

4 CAP_Initial DP (CalledPartyBCD, service key )

5 RequestReportBCSM (Answer), Connect Call to destination

7 EventReportBCSM (Answer)

34

PrePaid for CAMEL Phase 1 (2)

PrePaid „Rerouting“ Service using CAMEL phase 1

CAMEL used to take call back to HPLMN

Use of proprietary INAP or CAPv2 for call handling in HPLMN

Advantage: Service behaviour like in HPLMN

Disadvantage: Tromboning of call legs if destination not in HPLMN, more signalling, Non-desired Service interaction with Barring of outgoing international calls

35

Example: Prepaid „CAMEL1 Rerouting“

IP O-CSI CSE gsmSCF T-CSI SRF Home Network HLR 7 4 GMSC SSP 8 5
IP
O-CSI
CSE gsmSCF
T-CSI
SRF
Home Network
HLR
7 4
GMSC
SSP
8
5
Destination Network
6
O-CSI
VLR
gsmSSF
• Call Rerouting via Home Network
3
MSC
3 Call Setup

4 CAP_Initial DP (CalledPartyBCD, service key )

5 Connect call to GMSC+CorrelationId

6 Initial Address Message to HPLMN

Visited Network

7 IN_Initial DP (CorrelationId) and other Interactions as with CAMEL 2

8 Initial Address Message to destination

36

CAMEL Phase 2

37

CAMEL Phase 2

The second phase of CAMEL enhances the capabilities of Phase 1

The following capabilities have been added:

- Additional event detection points (for error handling)

- Interaction between a user and service using announcements, voice prompting and information collection via in band interaction or USSD interaction.

- Control of call duration and transfer of Advice of Charge Information to the mobile station.

- The CSE can be informed about the invocation of supplementary services (e.g ECT, CD, MPTY).

- For easy post processing, charging information from a serving node can be integrated in normal call records.

38

CAMEL Phase II enhancements CAMEL Phase 1 CAMEL Phase 2 • O-CSI • U-CSI, UG-CSI,
CAMEL Phase II enhancements
CAMEL Phase 1
CAMEL Phase 2
• O-CSI
• U-CSI, UG-CSI, SS-CSI, TIF-CSI
and T-CSI
• DPs including conditional triggers
-
triggering of events
Failure, Busy, No Answer, Abandon
• Basic DPs
• Basic call
• Charging facilities
operations
-
online charging, ticket information
• 2-step
• User dialogs and announcements
Interrogation
-
assist procedure
• Any Time
• SS Invocation notification
Interrogation
• USSD Operations
39
CAMEL Phase 2 architecture
gsmSCF
MAP
HLR
CAP
MAP
Interrogating
gsmSSF
VLR
gsmSRF
gsmSSF
Network
VMSC
GMSC
PSTN
Roaming
PLMN
Leg
CS
PSTN/PLMN
PSTN/PLMN
USSD
Visited Network
Home Network
40
Additional CAMEL Phase 2 CSI CSI form Phase 1 plus: • Supplementary Service Invocation Notification
Additional CAMEL Phase 2 CSI
CSI form Phase 1 plus:
• Supplementary Service Invocation Notification CAMEL Subscription Information (SS-
CSI)
is transferred to the VPLMN. SS-CSI is used to notify the CSE about the invocation of
certain Supplementary Services.
• Translation information Flag CAMEL Subscription Information (TIF-CSI)
is held in the HLR. TIF-CSI is used in the HLR for registering short Forwarded-to-
Numbers (FTNs). When TIF-CSI is present, the subscriber is allowed to register short
FTNs.
When the subscriber invokes Call Deflection, TIF-CSI in the VPLMN allows the
subscriber to deflect to short Deflected-to-Numbers.
• USSD CAMEL Subscription Information (U-CSI)
is held in the HLR; it is not sent to any other node. U-CSI contains trigger information
which is used to invoke a USSD application in the CSE for the served subscriber.
• USSD General CAMEL Subscription Information (UG-CSI)
is held in the HLR; it is not sent to any other node. UG-CSI contains trigger information
which is used to invoke a USSD application in the CSE for all subscribers.
41
CAMEL Phase 2 architecture
U-CSI
UG-CSI
gsmSCF
TIF-CSI
MAP
HLR
CAP
MAP
Interrogating
O-CSI
gsmSSF
VLR
gsmSRF
gsmSSF
Network
SS-CSI
O-CSI
T-CSI
VMSC
GMSC
PSTN
Roaming
PLMN
Leg
CS
PSTN/PLMN
PSTN/PLMN
USSD
Visited Network
Home Network
42
Special Resource Access in CAMEL Phase 2 1. SRF in HPLMN is accessed from VPLMN
Special Resource Access in CAMEL Phase 2
1. SRF in HPLMN
is accessed from
VPLMN
Bilateral agreement allows access
to SRFs in VPLMN.
Home Network
CSE
gsmSCF
gsmSRF
2a. Distributed
SRFs in VPLMN,
standalone or
integrated
2b. Centralized SRFs in VPLMN
gsmSRF
gsmSRF
gsmSSF
gsmSSF
gsmSRF
gsmSSF
gsmSSF
gsmSSF
Visited Network
43
CAMEL Phase 2 O_BCSM
DP10
O_Null & Authorise_Origination_
Attempt_Collect_Info
O_Exception
O_Abandon
Collected_Info
DP2
Route_Select_
DP4
Failure
DP5
Analyse, Routing
O_Busy
& Alerting
DP6
O_No_Answer
DP7
O_Answer
DP9
O_Active
O_Disconnect
Basic Call transition
44
Transition beyond Basic Call
CAMEL 2 O-BCSM Detection Points CAMEL Detection Point: DP Type Description: DP2 Collected_Info TDP-R Indication
CAMEL 2 O-BCSM Detection Points
CAMEL Detection Point:
DP Type
Description:
DP2 Collected_Info
TDP-R
Indication that the O-CSI is analysed.
DP 4 Route_Select_Failure
EDP -N, EDP -R
Indication that the call establishment failed
DP 5 O_Busy
EDP -N, EDP -R
Indication that:
- a busy indication is received from the terminating party,
- a not reachable event is determined upon a cause IE in the
ISUP release message.
DP6 O_No_Answer
EDP -N, EDP -R
Indication that an application timer associated with the
O_No_Answer DP expires
DP7 O_Answer
EDP -N, EDP -R
Indication that the call is accepted and answered by the
terminating party.
DP9 O_Disconnect
EDP -N, EDP -R
A disconnect indication is received from the originating party or
from the terminating party.
DP 10 O_Abandon
EDP-N
Indication that a disconnect indication is received from the
originating party during the call establishment procedure
45
CAMEL Phase 2 T_BCSM
T_Null
T_Exception
DP18
T_Abandon
Terminating_Attempt_Authorised
DP12
DP13
T_Busy
Terminating Call Handling
DP14
T_No_Answer
T_Disconnect
T_Answer
DP15
DP17
T_Active
Basic Call transition
Transition beyond Basic Call
46
 

CAMEL 2 O-BCSM Detection Points

 

CAMEL Detection Point:

DP Type

 

Description:

DP12

TDP-R

Indication that the T-CSI is analysed.

Terminating_Attempt_Authorised

DP 13 T_Busy

EDP -N, EDP -R

Indication that:

-

a busy indication is received from the destination

exchange,

Not reachable or call establishment failure event is determined from the HLR response or upon a cause

-

   

IE

DP 14 T_No_Answer

EDP -N, EDP -R

in the ISUP release message.

Indication that an application timer associated with the

T_No_Answer DP expires

DP15 T_Answer

EDP -N, EDP -R

Call is accepted and answered by terminating party

DP17 T_Disconnect

EDP -N, EDP -R

A

disconnect indication is received from the

terminating party or from the originating party.

DP 18 T_Abandon

EDP-N

A

disconnect indication is received from the originating

party during the call establishment procedure

 

47

 

CAP Phase 2

 

gsmSSF – CSE

CSE - gsmSSF

 
 

Activity Test ack

Activity Test

Apply Charging Report

Apply Charging

Call Information Report

Call Information Request

Event Report BCSM

Cancel

Initial DP

Connect

CSE – gsmSRF

 

Connect to Resource

 

Cancel

Continue

Play Announcement

Establish Temporary Connection

Prompt and Collect User Information

 

Furnish Charging Information

Release Call

Activity Test

Request Report BCSM Event

gsmSRF - CSE

 

Reset Timer

 

Assist Request Instructions

Send Charging Information

Prompt and Collect User Information ack

Specialized Resource Report

 

Activity Test ack

48

Conditional Triggering Criteria

Functionality:

Triggering of IN Services only under certain conditions like

number length

leading digits

bearer service and capability

whether call is originating or forwarded

Operator Benefit:

Improved services

Reduced signalling load between SSP and SCP

Applications:

Short code access to own mailbox from visited PLMN

49

Example: CAMEL2: Short code access to mail box

VPLMN HPLMN CSE „Visited MSC“ MSC SSF 1. <2200> „Home MSC“ Calling Mailbox MSC SRF
VPLMN
HPLMN
CSE
„Visited MSC“
MSC
SSF
1. <2200>
„Home MSC“
Calling Mailbox
MSC
SRF
Mail Box
2. <2200>
3. <+43.676.2200>

1. Subscriber dials a short number to reach mailbox

2. Digit analysis initiates IN handling of call

3. CSE translates short number to MSISDN

50

Example: MOC with CAMEL2 (1)

IP O-CSI CSE gsmSCF T-CSI Home Network gsmSRF HLR 2 1 Destination Network Visited Network
IP
O-CSI
CSE gsmSCF
T-CSI
Home Network
gsmSRF
HLR
2
1
Destination Network
Visited Network
O-CSI
VLR
gsmSSF
MSC
Location Update and Capability
Negotiation Phase
1 Location Update Request

2 Insert Subscriber Data (O-CSI)

51

Example: MOC with CAMEL2 (2)

IP 7 O-CSI CSE gsmSCF T-CSI gsmSRF Home Network HLR 8 9 4 X Destination
IP
7
O-CSI
CSE gsmSCF
T-CSI
gsmSRF
Home Network
HLR
8
9
4
X
Destination Network
5
6
O-CSI
VLR
gsmSSF
3
MSC
Call Setup Phase with User
Interaction
Visited Network
7 Assist Request Instruction
3 Call Setup
4 Initial DP (CalledPartyBCD, service key )
5 Establish Temporary Connection
8 Connect to Resource,
Play Announcement or
Prompt and Collect

6 Initial Address Message (ISUP)

9 Disconnect Forward Connection

52

Example: MOC with CAMEL2 (3) IP O-CSI CSE gsmSCF T-CSI gsmSRF Home Network HLR 10
Example: MOC with CAMEL2 (3)
IP
O-CSI
CSE gsmSCF
T-CSI
gsmSRF
Home Network
HLR
10
13
Destination Network
11
O-CSI
VLR
12
gsmSSF
MSC
Online charged connection Phase
Visited Network
10 Connect (CalledPartyNumber)
11 Apply Charging (Timer, Tariff Change, )
12 Initial Address Message (ISUP)
13 Apply Charging Report
53
CAMEL and USSD
USSD Notifications to CSE require Trigger (U-CSI + UG-CSI) in HLR
Home Network
HLR
MAP
gsmSCF
CAMEL USSD
application
USSD Handler
MAP
USSD
VLR
MSC
MS
Visiting Network
54

CAMEL USSD

Functional Elements:

HLR: The HLR stores for subscribers requiring CAMEL support the information relevant to the current subscription regarding U-CSI. The UG-CSI is stored as global data applicable to all subscribers. The U-CSI and the UG-CSI are stored in the HLR only.

gsmSCF: functional entity that contains the CAMEL service logic to imple ment OSS. It interfaces with the gsmSSF, the gsmSRF, the GMLC and the HLR.

Interfaces:

gsmSCF-HLR interface

This interface is used for USSD operations, both for gsmSCF-initiated dialogues and MS-initiated dialogues (relayed via HLR). It is a network operator option whether to support or not USSD operations on this interface.

55

CAMEL and USSD

Note that the procedure at the CAMEL USSD application at the HLR is implementation dependent. The following text describes a recommended procedure:

The CAMEL USSD application shall check the U-CSI data assigned to the specific subscriber. If the service code is present in the U-CSI the USSD is routed to the gsmSCF given by the gsmSCF address stored against the service code in the U-CSI.

If the service code is not present in the U-CSI (or the subscriber does not have U-CSI defined) then the CAMEL USSD application shall check the UG-CSI data assigned to the HLR. If the service code is present in the UG- CSI then the USSD is routed to the gsmSCF given by the gsmSCF address stored against the service code in the UG-CSI.

If the service code is not present in U-CSI or UG-CSI an error (unknown application) is returned to the USSD handler.

56

USSD to/from gsmSCF

gsmSCF to HLR operations

• Unstructured SS Request

• Unstructured SS Notify

• Process Unstructured SS Data ack

• Process Unstructured SS Request ack

HLR to gsmSCF operations

• Unstructured SS Request ack

• Unstructured SS Notify ack

• Process Unstructured SS Data

• Process Unstructured SS Request

• Begin Subscriber Activity

Requires exchange of USSD CAMEL Subscription Information (U-CSI)

Requires exchange of Content of the USSD General CAMEL Service Information (UG-CSI)

57

CAMEL Supplementary Service Notification

At the invocation of any of the services ECT, CD and MPTY the VLR checks whether the criteria for sending a notification are fulfilled, i.e. whether the subscriber is provisioned with the SS-CSI and the particular invoked supplementary service is marked in the SS-CSI.

Home Network

HLR MAP gsmSCF MAP MAP SS invoke VLR MSC Visited Network
HLR
MAP
gsmSCF
MAP
MAP
SS invoke
VLR
MSC
Visited Network

58

 

CAMEL SS related Functional Elements

HLR: For subscribers requiring CAMEL support, the HLR stores the information relevant to the current subscription regarding SS-CSI. The SS- CSI is sent to the VLR at Location Update, on Data Restoration or if the SS- CSI is updated by administrative action. When processing an invocation of the CCBS supplementary service, the HLR shall send a notification of the invocation of the supplementary service to the gsmSCF if required by the SS-CSI.

 

MSC: When processing an invocation of any of the supplementary services ECT, CD and MPTY, the MSC may receive an SS-CSI from the VLR, indicating that a notification of the invocation of the supplementary service shall be sent to the gsmSCF.

VLR: The VLR stores the SS-CSI as a part of the subscriber data for subscribers roaming in the VLR area.

gsmSCF: The gsmSCF receives the SS Invocation Notification from the MSC or HLR.

59

 

SS Notifications

MSC to gsmSCF operations

 

SS Invocation Notification

HLR to VLR operations

 

• Delete Subscriber Data

• Insert Subscriber Data

HLR to gsmSCF operations

SS Invocation Notification

VLR to MSC operations

 

• Invoke SS result

• Send Info For Incoming Call

 

Requires exchange of Supplementary Service Invocation Notification CAMEL Subscription Information (SS-CSI)

60

CAMEL Phase 3

61

CAMEL Phase 3

CAMEL phase 3 adds many new features:

– Services for MO SMS (basically charging and re-routing).

– Services for GPRS, both for the MO and MT sides (also basically for charging and re-routing). This includes to monitor from attach to detach or PDP Contexts individually.

– Notification of Mobility Management events (e.g. attach, detach, change of VLR area).

– New types of triggers (D-CSI, N-CSI, VT-CSI, etc).

– New triggering criteria (release cause for some events).

– AnyTimeModification operation.

– Interface to Location Services (based on MAP ATI).

The bigger changes are services for GPRS, SMS and Mobility Management.

62

 

CAMEL Phase 3 enhancements

 

CAMEL Phase 2

 

CAMEL Phase 3

   

O-CSI, T-CSI, U-CSI, UG-CSI, SS-CSI, TIF-CSI

GPRS-CSI, SMS-CSI, N-CSI, D-CSI, M-CSI, VT-CSI

DPs and operations for GPRS

Basic and conditional DPs

Basic call operations and charging

User dialogs

DPs and operations for MO-SMS

Mobility triggers

Enhanced MAP IF HLR - gsmSCF

- Any Time Subscription Interrogation

- AT Modification

USSD operations

- AT Notification

2-step Interrogation

SoLSA

Any Time Interrogation

 

63

 

CAMEL Phase 3 service examples

 

GPRS interaction

GPRS interaction Prepaid GPRS

Prepaid GPRS

 

Information related to the actual

Mobility Management

Mobility Management location: city phone, office zone, home zone

location: city phone, office zone, home zone

MO SMS triggering

MO SMS triggering Sending Prepaid SMSs when roaming

Sending Prepaid SMSs when roaming

Improved triggering

Improved triggering Improved terminating services

Improved terminating services

Dialled services

Dialled services B-number related services (short numbers, special numbers, VMS,…)

B-number related services (short numbers, special numbers, VMS,…)

 

64

CAMEL Phase 3 architecture gsmSCF MAP HLR MAP CAP Interrogating gsmSSF VLR gsmSRF gsmSSF Network
CAMEL Phase 3 architecture
gsmSCF
MAP
HLR
MAP
CAP
Interrogating
gsmSSF
VLR
gsmSRF
gsmSSF
Network
VMSC
GMSC
PSTN
Roaming
PLMN
Leg
CS
PSTN/PLMN
PSTN/PLMN
USSD
gprsSSF
SMS
GPRS
SGSN
GGSN
PDN
Visited Network
Home Network
65
CAMEL Phase 3 Functional Elements (cont.)
• gsmSCF: functional entity that contains the CAMEL service logic to
implement OSS. It interfaces with the gsmSSF, the gsmSRF, the GMLC
and the HLR.
• gsmSSF: functional entity that interfaces the MSC/GMSC to the gsmSCF.
The concept of the gsmSSF is derived from the IN SSF, but uses different
triggering mechanisms because of the nature of the mobile network.
• gsmSRF: functional entity which provides various specialized resources. It
interfaces with the gsmSCF and with the MSC. This entity is defined in
ITU-T Q.1214 with variations defined in the specification.
66

Additional CAMEL Phase 3 CSI

CSI from Phase 1 plus Phase 2 plus:

Dialled Services CAMEL Subscription Information (D-CSI)

is transferred to the VPLMN (at location update) and IPLMN (for an incoming call in GMSC). D-CSI contains trigger information which is required to invoke a CAMEL service logic for subscribers dialled services.

GPRS CAMEL Subscription Information (GPRS-CSI)

is transferred to the VPLMN. GPRS-CSI contains trigger information which is required to invoke a CAMEL Service Logic for GPRS Sessions and PDP Contexts.

Mobility Management CAMEL Subscription Information (M -CSI)

is transferred to the VPLMN. M-CSI is used to notify the CSE about Mobility Management events.

Network CAMEL Subscription Information (N-CSI)

is transferred to the VPLMN. N-CSI identifies services offered on a per-network basis by the serving PLMN operator for all subscribers. This CSI shall be stored in the MSC.

67

Additional CAMEL Phase 3 CSI (cont.)

Short Message Service CAMEL Subscription Information (SMS-CSI)

is transferred to the VPLMN. SMS-CSI contains trigger information which is required to invoke a CAMEL Service Logic for Mobile Originating Short Message submissions.

VMSC Terminating CAMEL Subscription Information (VT-CSI)

is transferred to the VPLMN at location update. VT-CSI contains trigger information which is required to invoke a CAMEL Service Logic for Mobile Terminating calls in the VMSC.

68

CAMEL Phase 3 architecture U-CSI UG-CSI gsmSCF MAP HLR TIF-CSI MAP CAP M-CSI O-CSI Interrogating
CAMEL Phase 3 architecture
U-CSI
UG-CSI
gsmSCF
MAP
HLR
TIF-CSI
MAP
CAP
M-CSI
O-CSI
Interrogating
gsmSSF
D-CSI
VLR
SS-CSI
gsmSRF
gsmSSF
Network
N-CSI
D-CSI
T-CSI
VMSC
GMSC
VT-CSI
O-CSI
PSTN
Roaming
SMS-CSI
PLMN
Leg
CS
PSTN/PLMN
gprs-CSI
PSTN/PLMN
USSD
gprsSSF
SMS-CSI
SMS
GPRS
SGSN
GGSN
PDN
Visited Network
Home Network
69
CAMEL Phase 3 O_BCSM
O_Null & Authorise_Origination_
Attempt_Collect_Info
O_Exception
O_Abandon
Collected_Info
invalid_information
Analyse_Information
Analysed_Information
Route_Select_
Routing
Failure
& Alerting
O_Busy
O_No_Answer
O_routing_and_alerting_failure
O_Answer
O_Active
O_active_failure
O_Disconnect
70
Basic Call transition
CAMEL 3 O-BCSM Detection Points CAMEL Detection Point: DP Type Description: DP Collected_Info TDP-R Indication
CAMEL 3 O-BCSM Detection Points
CAMEL Detection Point:
DP Type
Description:
DP Collected_Info
TDP-R
Indication that the O-CSI is analysed.
DP Analysed_Information
TDP-R
Availability of routeing address and nature of address.
DP Route_Select_Failure
TDP-R, EDP -N,
EDP-R
Indication that the call establishment failed.
DP O_Busy
EDP -N, EDP -R
Indication that:
-
a busy indication is received from the terminating party,
-
a not reachable event is determined upon a cause IE in the ISUP
DP O_No_Answer
EDP -N, EDP -R
release message.
Indication that:
-
an application timer associated with the O_No_Answer DP expires,
-
a
no answer event is determined upon a cause IE in the ISUP
release message.
DP O_Answer
EDP -N, EDP -R
Indication that the call is accepted and answered by the
terminating party.
DP O_Disconnect
EDP -N, EDP -R
A
disconnect indication is received from the originating party or
from the terminating party.
DP O_Abandon
EDP -N, EDP -R
Indication that a disconnect indication is received from the
originating party during the call establishment procedure.
71
CAMEL Phase 3 T_BCSM
T_Null
T_Exception
T_Abandon
Terminating_Attempt_Authorised
T_Busy
Terminating Call Handling
T_No_Answer
T_call_handling_failure
T_Disconnect
T_Answer
T_active_failure
T_Active
Basic Call transition
72
 

CAMEL 3 O-BCSM Detection Points

 

CAMEL Detection Point:

DP Type

Description:

DP Terminating_Attempt_ Authorised

TDP-R

Indication that the T-CSI / VT_CSI is analysed.

DP T_Busy

TDP-R (note 2), EDP -N, EDP -R

Indication that:

-

a

busy indication is received from the destination exchange,

 

-

Busy event is determined in the visited MSC,

-

Not reachable or call establishment failure event is determined from the HLR response or upon a cause IE in the ISUP release message.

DP T_No_Answer

TDP-R (note 2), EDP -N, EDP -R

Indication that an application timer associated with the T_No_Answer DP expires .

DP T_Answer

EDP -N, EDP -R

Call is accepted and answered by terminating party.

DP T_Disconnect

EDP -N, EDP -R

A

disconnect indication is received from the terminating party

or

from the originating party.

DP T_Abandon

EDP -N, EDP -R

A

disconnect indication is received from the originating party

during the call establishment procedure.

 

73

 

CAP Phase 3

 

gsmSSF – CSE

 

CSE - gsmSSF

 

Activity Test ack

Activity Test

Apply Charging Report

 

Apply Charging

Call Information Report

Call Information Request

Event Report BCSM

Cancel

Initial DP

Connect

CSE – gsmSRF

 

Connect to Resource

 

Cancel

Continue

Play Announcement

Continue with Argument

Prompt and Collect User Information

 

Disconnect Forward Connection

Establish Temporary Connection

Activity Test

Furnish Charging Information

gsmSRF - CSE

 

Release Call

 

Assist Request Instructions

 

Request Report BCSM Event

Prompt and Collect User Information ack

Reset Timer

Specialized Resource Report

Send Charging Information

Activity Test ack

74

CAMEL Phase 4

75

CAMEL Phase 4 (Release 5)

• CAMEL Phase 4 is an integral part of 3GPP Core Network Release 5

– Release 5 has been delivered in march 2002

• CAMEL Phase 4 enhances the capabilities of phase 3

– CAMEL Phase 4 circuit switched call control encompasses all features of previous CAMEL phases but extends these to completeness (see next slide)

– Support of 3GPP IP Multimedia Domain (IMS)

Ë Defined in separate document:

3GPP TS 23.278: (CAMEL) Phase 4 - Stage 2 IM CN Interworking (Rel 5)

• CAP V4 and previous CAP versions may be transported over IP (based on IETF SIGTRAN work)

NOTE:

With CAMEL Phase 4, it is possible that only a limited subset of the new functionalities is supported, in addition to the complete support of CAMEL Phase 3.

76

 

CAMEL Phase 4

CAMEL phase 4 adds many new features

 

– Call Party Handling for voice calls

– Midcall detection point

– Services for MT SMS (basically charging and re-routing)

– Mobility Management for GPRS

– Support of Optimal Routing

– Enhancements to Any Time Modification (ODB)

– Any Time Interrogation for Terminal Capabilities

– Flexible tones injection

– Location information during call

– Services for IMS

77

 

CAMEL Phase 4 Subsets

An entity may support

 

complete CAMEL phase 4 or, as a network option,

complete CAMEL phase 3 functionality and one or more subsets of CAMEL phase 4.

The subsets of CAMEL phase 4 are the following:

- Relative to Circuit switched Call Control

- CS call handling

- Charging notification (with CS call handling)

Relative to GPRS interworking

-

Notification of GPRS mobility management to CSE

- Relative to Short Message Services

 

-

CAMEL control over MT SMS

- Relative to Subscriber Location and State retrieval

 

-

GPRS Any Time Interrogation

78

CAMEL Phase 4 architecture U-CSI UG-CSI gsmSCF MAP HLR TIF-CSI MAP CAP M-CSI O-CSI Interrogating
CAMEL Phase 4 architecture
U-CSI
UG-CSI
gsmSCF
MAP
HLR
TIF-CSI
MAP
CAP
M-CSI
O-CSI
Interrogating
gsmSSF
D-CSI
VLR
SS-CSI
gsmSRF
gsmSSF
Network
N-CSI
D-CSI
T-CSI
VMSC
GMSC
VT-CSI
O-CSI
PSTN
Roaming
MO-SMS-CSI
PLMN
Leg
MT-SMS-CSI
CS
PSTN/PLMN
gprs-CSI
PSTN/PLMN
USSD
gprsSSF
MG-CSI
MT-SMS-CSI
SMS
MO-SMS-CSI
GPRS
SGSN
GGSN
PDN
Visited Network
Home Network
79
CAMEL in IMS
• CAMEL architecture is integrated with IMS
• New functionality added: IM SSF (IMS Service Switching Function).
• Interfaces:
– CSCF-IM SSF based on SIP (ISC: IMS Service Control).
– IM SSF-gsmSCF being defined (based on CAMEL Phase 3).
• IMS-CSI to define triggering criteria.
• State models based on CAMEL phase 3 with mapping to SIP
methods/responses:
– O-IM-BCSM for originating sessions.
– T-IM-BCSM for terminating sessions.
80
CAMEL Phase 4 in IMS Domain • IM-SSF provides – Triggering of CAMEL services in
CAMEL Phase 4 in IMS Domain
IM-SSF provides
– Triggering of CAMEL services in gsmSCF
– Call State model (O-IM-BCSM / T-IM-BCSM) based on CAMEL Phase 3!
CSE
MAP
HSS
CAP
Cx
over
Interrogating
IP
Network
IP Multimedia Subsystem
imSSF
proxy
S-CSCF
CSCF
SIP
SIP
SIP
T-SGW
MGCF
PSTN
MGW
PLMN
IP Multimedia
SGSN
GGSN
IP Multi
media
81
Visited Network
Home Network
CAMEL Functional components
• IP Multimedia Service Switching Function (IM-SSF)
functional entity that is a SIP Application Server interfaces SIP to CAP.
• IP Multimedia CAMEL Subscription Information (IM-CSI)
identifies the subscriber as having IP Multimedia CAMEL services.
• Service Platform Trigger Points (STP)
– the points in the SIP signalling that instruct the SIP AS, OSA SCS and IM-SSF
to trigger the service logic.
– For the IM-SSF the IP Multimedia Camel Subscriber Information (IM-CSI)
defines them.
• Initial Filter Criteria (iFC)
– filter criteria that are stored in the HSS as part of the user profile and are
downloaded to the S-CSCF upon user registration.
– They represent a provisioned subscription of a user to an application.
82
Release 5: CAP over IP API Interface SSF SCP SSF Appl SW SCP Appl SW
Release 5: CAP over IP
API Interface
SSF
SCP
SSF Appl SW
SCP Appl SW
SGW
Appl SW
Appl SW
CAP
CAP
CAP
CAP
CAP
TCAP
TCAP
TCAP
TCAP
TCAP
SCCP
SCCP
SCCP
SCCP
SCCP
M3UA
M3UA MTP3
MTP3
M3UA
M3UA
SCTP
SCTPMTP2
MTP2
SCTP
SCTP
IP
IP
IP
IP
LI
LI
SSF
SCP
SSF
SCP
Interworking node
CAP over IP stack
CAP over IP interworking with SS7
Based on the IETF SIGTRAN work!
83
MOC VoIP with CAMEL interaction
Visited network
Home network
A
UE
P-CSCF
I-CSCF
S-CSCF/imSSF
CSE
HSS
If calling subsc. is
not registered,
dialogue with HSS
is opened to obtain
O-CSI
Invite
InitialDP
CAP instructions
Analysis for calls
requiring IN i.e.
trigger criteria in
O-CSI
84

CAMEL Release 5 for IP Multimedia Subsystem

• As part of CAMEL Phase 4 CAP can be used for call, session, message control

– CAMEL for 3GPP Release 5 IP Multimedia Subsystem is defined in an extra specification:

3GPP TS 23.278: (CAMEL) Phase 4 - Stage 2 IM CN Interworking (Release 5)

• Further important References:

– 3GPP TS 22.078: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description, Stage 1"

– 3GPP TS 22.228: "3rd Generation Partnership Project; Technical Specification Group Systems Aspects; IP Multimedia (IM) Subsystem –Stage 1

– 3GPP TS 23.228: "3rd Generation Partnership Project; Technical Specification Group Systems Aspects; IP Multimedia (IM) Subsystem –Stage 2

– 3GPP TS 23.218: "3rd Generation Partnership Project; Technical Specification Group Core Networks; IP Multimedia (IM) Session Handling; IP Multimedia Call Model - Stage 2

85

CAMEL Evolution

Camel Phase 4 Camel Phase 1 + 2 CAMEL MAP (SCF) MAP HSS CAP 3G
Camel Phase 4
Camel Phase 1 + 2
CAMEL
MAP
(SCF)
MAP
HSS
CAP
3G IP based Voice
and Data Network
CAP
2G Circuit Switch
Voice Network
IM-SSF
HLR
SIP
CAP
MAP
S-CSCF
MSC
(SSF)
MAP
SGSN
(SSF)
2.5G Packet Switch
GPRS Data Network
Camel Phase 3
86

CAMEL Deployment

• Camel Phase 2 is ‘on the paper’ richer than Camel Phase 1, but in reality Camel Phase 1 is preferred so far:

– Direct routing from VPLMN1 to VPLMN2 is complex to handle from the charging view point

– Most of the roaming calls are made in direction of the HPLMN : re-routing

– calls in HPLMN with Camel Phase 1 do not provide huge tromboning overload

– Advice of charge and interactions can be made through USSD

Only few Operators have moved to Camel Phase 3

– mainly for GPRS PrePaid,

– but many operators did implement alternativ approaches to CAMEL as CAMEL 3 is considered to complex and expensive!

• Camel phase 4 is still a bit far away …

– No strong need for ‘conference’ types of applications yet

– IMS is not yet deployed globally and motivates other (SIP) application servers

87

Summary of CAMEL Deployment

• 40.96% of the operators interviewed to date have submitted responses (34 operators). Of this, 62% have deployed CAMEL (Phase 1 and/or 2).

• Of those operators who have not deployed CAMEL Phase II, 33.3% declared that Phase II would be deployed. The remaining has no plans or has not reached a decision on the matter

88

88

Wireless IN - WIN

• WIN falls under the ANSI, TIA and T1standards bodies :

• ANSI represents US interests abroad in terms of technical and policy postitions

• TIA and T1 create standards for wireline and wireless

– TR45 is a wireless division of TIA, TR45.2 subcommitte focuses on standards for mobile and personal communications; ANSI-41 and WIN

– T1 creates network inter-connection and interoperability standards for wireline and wireless, T1S1/T1P1 subgroups develops standards and techncial reports related to wireless networks and services

• WIN standards follow a development process different from CAMEL:

– As WIN standards are conceived they are assigned a project number, E.g. PN-4287 Prepaid charging

– Once adopted by TIA the PN becomes an interim standard, such as IS-771 WIN Phase 1

– After an interim standard has been published by TIA, there is a 3-year period of revision and acceptance

– When industry adopts the interim standard it becomes part of ANSI 41 e.g. IS-771 is targeted to become part of ANSI 41-E

89

WIN Phase 1

• WIN Phase 1 Service Drivers

– Calling Name Presentation IS-764 fast track, June 1988

– Voice Controlled Services

– Incoming Call Screening

– WIN Phase 1 services and features defined by IS-771

• WIN P1 is based on ANSI 41-D established the use of trigger profile for determining mobile user features and capabilities while roaming (Origination Request message):

– Based on IN capability set CS-2

– An Originating BCSM with 3 detection points

– A Terminating BCSM with 3 detection points

– Rules for use of triggers includes

• Service independence

• Trigger list includes service logic address info

• Triggered service logic has precedence

90

WIN 1 Architecture

WIN Phase 1: 3GPP2 N.S0013-0

WIN 1 Architecture • WIN Phase 1: 3GPP2 N.S0013-0 91

91

WIN Phase 2

• WIN Phase 2 service drivers were:

– Prepaid Charging PN 4287 fast track

– Preferred Language, Free Phone

– Other Billing Services - Advice of Charge and Premium Rate

– Charging)

– Call Management Capabilities – rejection of annoying calls

– Location-based Services – position request message provides serving MSC, Location and cell information

• WIN Phase 2 services and features defined by the IS-826 for Prepaid Charging and IS-818 for preferred language and location based phase 1 and 911 based services

92

WIN Phase 3

• WIN-based location infrastructure defined by SRD submission by CTIA to the TIA standards process:

• WIN Phase 3 service drivers are:

– Location based charging

– Fleet and asset management services

– Enhanced call routing services

– Location based information services

• WIN Phase 3 projects

– Location services and architecture (PN 4818)

– Location services authorization/privacy/security (PN 4746)

– Location Services Enhancements (PN 4747)

– Related project in support of the FCC wireless 911 (PN 3890)

93