IN explained

8/7/2019 IN explained

1/40

Chung-Min Chen

TELCORDIA TECHNOLOGIES, INC. PROPRIETARY - INTERNAL USE ONLYThis document contains proprietary information that shall be distributed, routed or made available only within Telcordia, except with written permission of Telcordia.


2/40

n e gen e wor

Services

Call forwarding ac s

Dont call

o - ne LNP

Pre-paid

TELCORDIA PROPRIETARY - INTERNAL USE ONLYSee proprietary restrictions on title page.

2


3/40

from Operations

IN Service Logic

Hooks Hooks Hookssupplementary

services Basic call Basic call Basic call

to customers

process ng process ng process ng

NODE A NODE B NODE C


3


4/40

u ne

IN Background

an ar

IN Network Architecture

IN Services

Next Generation IN


4


5/40

ncep on

1970-1980s

Assembly codes manually installed in switches

-

Late 1980s

Intelligent Network) concept

Simplify deployment and management of value added serviceswith central control

1993

ITU published IN standard series Q.1200-1205, 1208, 1290.


5


6/40

an ar s

ITU

Service capabilities out of which services can be built

CS-1: 1992, CS-2: 1997, CS-3 1999, CS-4: 2001.

Defines INAP as the message exchange protocol

US Telcordia de facto standard

ANSI T1S1 Group

Europe Ado tin ITU standard

Extensions: core-INAP, CAMEL


6


7/40

-

IN Conceptual Model (INCM)

Service Plane (SP)

Top level

Distributed Functional Plane (DFP)

Ph sical Plane PP


7


8/40


9/40

erv ce ane con .

Exam le

Freephone service is composed of two features

One-number feature: routes incoming calls made to a single number to

, , ,

Reverse charging feature: charge calls to freephone number owner

instead of caller

Feature:One-number

Feature:Reverse charging

Service Plane


9


10/40

erv ce ane con .

CS-1 defined features

Numbering One number, abbreviated dialing (e.g. *077),

, ,

Charging Reverse, premium rate,

Access Authentication, authorization code

Restriction Call screening (both originating and terminating),

Customization Customized ringing, customer recorded announcement,

User Interaction User prompting (both originating and terminating)

Miscellaneous Call waiting, automatic call-back,


10


11/40

o a unc ona ane con .

Looks at services from service providerspoint of view

Define SIB Service Inde endent Buildin Blocks

Software components that make up services

Each feature is implemented by one or more SIBs

Service provider must implement SIBs to deploy services

Feature:One-number

Feature:Reverse charging

Service: Freephone

Service Plane

BCP

TranslateSIB Charge

SIB

Log call infoSIB


11

Global Functional Plane


12/40


SIB connectors

Connects to a logical end of apreceding SIB

service support data(SSD)

ne or mu p e og ca en s

Allows conditional branching

SIB arameters Logical start Lo ical

Call-instance data (CID)

Call-dependent data such as

ends

or g na ng num er, a e

number,

Service support data (SSD) Call instance data

input output

Call-independent data, e.g., call-screening list, call-forwarding table,

charging scheme,

(CID)


12


13/40

o a unc on ane con . -

SIB Description

Authenticate Authenticates user and verifies privilege

Charge Applies a special charging algorithm

Compare Compares input parameters against a reference values

Distribution Conditional branch

Log call information Log call detail records

Queue Queues calls made to a specific number

Screen Compares input parameters against a list

Service data Add./u date/delete service data in the databasemanagement

Service filter Accepts or rejects calls according to specified parameters

Translate Translate in ut arameters into out ut numbers usin a s ecified al .

User interaction Input via DTMF, IVR (interactive voice response)

Verify Performs syntactic check on input parameters


13

- -


14/40


Screen SIB [Originating]

CID: dialed phone number

SSD: screening list Logical ends

service supportData (SSD)

Screeninglist

-the list

Not-on-the-list: dialed number is start LogicalScreen

in list

Enabled services:

Block calls to international or

SIBnot in list

premium-rate (1-900 calls)

numbers

Call instance data

Input: dialed number

Fig 2.7

(CID)


14


15/40


Screen SIB [Terminating]

CID: originating phone

number SSD: screening list

service supportData (SSD)

blacklist

Logical ends

inthe-list: originating start LogicalScreen

in list

number is on the list

Not-in-the-list: originatingnumber is not on the list

SIBnot in list

Enabled services Block unwanted calls or

Call instance data

Input: originating number

(CID)


15


16/40


Basic Call Process (BCP) SIB

Describes phases of setting up a point-to-point call

POI (Point of Initiation): interrupted to execute service logic (like afunction call)

POR Point of Return : return control to BCP

Example [Calling-card call service] SIBs: BCP, UI, Authenticate, Charge

Not OK(2)(3)

UserInteraction

Authenticate

ChargeOK

POR

Connect to destination number Clear call(1)

(4)(5)


16


17/40

o a unc on ane

Calling-card call service example

1. dialed number is detected as a special number; trigger the

calling-card call service2. UI SIB request caller to input credit card #, PIN, destination

3. Authenticate SIB verifies the input data

4. If credit card number and PIN are correct, Char e SIB startscharging. Return control (with destination number) to BCP,which resumes execution and proceed to call the destination

5. If the credit card number or PIN is incorrect, instructs BCP toterminates the call by jumping to the clear-call POR.


17


18/40

s r u e unc ona ane

Map GFP SIBs to functional entities(FE) in the network

A single SIB may be supported by one or more FEs

escr es n orma on ows e ween s

in terms of SDL (specification and development language) and MSC (messagesequence chart)

Note a FE is still a logicalentity

BCP

SIB

SIB ChargeSIB

og ca n oSIB

SSF

CCF SRF

SCF

SDF

SMF


18

Distributed Functional Plane


19/40

s r u e unc ona ane

Functional Entities

Call control function (CCF): controls the state and progress of a

ca Service switching function (SSF): handles bearer connections

Service control function SCF : hosts service ro rams

Service data function (SDF): database that keeps the servicesupport data

functions

Service resource function (SRF): contains special resourcesnee e o rea ze e serv ce

Note conce t se aration of

calls (by CCF): signaling

connections ( by SSF): voice trunk


19


20/40

s r u e unc ona ane

Example freephone


20


21/40

s r u e unc ona ane

BCP SIB further divided into two halves

Originating basic-call-state model (O-BCSM)

Terminating basic-call-state model (T-BCSM)

SCF

O-BCSM T-BCSM

SSF

Calling phone a e p one


21


22/40

s r u e unc ona ane

Half call is modeled as state-transition diagram

State: point in call (PIC)

Event: triggers transition; an event can be associated with a DetectionPoint

Detection Point DP

Implementation of GFPs POI

Points at which the SSF can suspend call processing and hand over


22


23/40

mp e

-

Off-hook

-

Number dialed

the call

Final routeringing

Selecta circuit

Callee answer


23


24/40

O-BCSM for a-


24


25/40

T-BCSM for a-

call


25


26/40

s r u e unc ona ane

Detection Points Tri er DP: set staticall at the time of service de lo ment

(e.g. 800 number detection) Event DP: set dynamicallyby service logic during the

. .

Actions at DP

halting process of the call

Request: the BCSM suspends call and sends a request to, resumes ca w en a request s rece ve rom

TDP-N, TDP-R, EDP-N, EDP-R


26


27/40


28/40

s r u e unc ona ane

Referring to the BCSM on previous slide

1. DP not armed, call continues.

2. An armed TDP-N encountered. Notification sent. Call continueswithout halting.

. n arme - encountere . a suspen e w e a requestis sent to SCF. Call resumed after response is received from

SCF. The response sets a (dynamic) EDP-R later in the BCSM.4. The previously set EDP-R encountered. Call suspended while a

request is sent to SCF. Call resumes after receiving theres onse from SCF.


28


29/40

ys ca ane

Maps from logical FEs to physicalnodes

A physical node is a server that hosts software

Straightforward mapping: Each FE mapped to a dedicated node

,


CCF SRF SDF


IPSDP


29

IP: Intelligent Peripheral


30/40

ys ca ane

Combine SCF and SDF into a single SCP for better performanceconsideration


CCF SRF SDF


IP


30


31/40

ys ca ane

Service Node deployment

Co-located SCF, SDF and SRF on one machine

Some switch vendors even combines these functions with the switch(SSF, CCF)

Chea er and tar eted for small carriers


CCF SRF SDF



31


32/40

ro oco

INAP: IN Application Part

Defines message exchangeetween

SSF and SCF

SCF and SRF

Specified in terms of ASN.1(abstract syntax notation 1)

ensuring transaction property


32


33/40

Example: Free Phone ervice

SSP SCP SDP

SWITCH

1

Detect

2

1. 1-800 number recognized. Triggered a

detection point

2. SSP sends a message to SCP including

BCSM

Collected_Info

Anal ze Info

TDP-R

initialDP(call_id,

Service Logic

Data Function45

the dialed 1-800 number

3. Service Logic function sends a

message to SDP for number translation.

_ _ ,

connect(call_id, dest id)

requestInfo (freephoneDB,Dialed number)

Service Logic

6

4. SDP returns destination number (and

possibly charging information).

5. SCP sends message to switch

O_Answer TDP-N

requestReport (O_Answer,O_Disconnect)

eventReport(call_id,

O_Answer, timestamp)

(dest_id)

ConnectService logic

(including charging information) and

indicates DPs for notification

6. When callee answers the call a DP7

O_Active

O_Disconnect TDP-ReventReport(call_id,O_Disconnect,time stamp)

reversecharging

is triggered. SCP starts reverse charging.

7. When call completes, another DP istriggered. SCP stops reverse charging.

ConnectService logic

O_Null and AuthorizeOrigination Attempt

_

GFP SIBs are mapped to a sequence of program executions in FEs and INAP messageExchanges between FEs.


33


34/40

-

Extensions to CS-1

Allows SCFSCF and SDFSDFcommun ca ons

Allows user interactions to use non-SS7 signalinge.g. s ort message,

Generalizes SIB model (e.g. allows recursion)


34


35/40

- , -

CS-3 CS-2 contains ambi uities causin difficult in inter retin

the specs CS-3 is a revised version of CS-2, providing refinements

-

CS-4

Internet, mobile network, telecom deregulation

Voice, video, multimedia, data

Packet-switch connections

o a e, - rema ns e mos n uen a anwidely adopted standard!!


35


36/40

e cor a

Rapid-to-market

services


36


37/40

ys em equ remen s

Availability > 99.9%

SNMP fault monitoring

Performance monitoring

Ca acit lannin tools

Disaster recovery support

24x7x365 support m nu e response me

4 hour resolution time for severity 1 issues


37


38/40

ca a y equ remen s

Current opportunity includes 10 DRS servers in 2008 growing to 20 in 2009

Not all DRS servers in same data center

-

~3500 inserts per second per DRS server Concurrent query workload from customer care

-.

24M subs in 2008, growing to 60M in 2009

Latency requirements

Time from when DRS sends the SQL command to insert a record until Customer Carecan retrieve that record should be less than 5 seconds 95% of the time, less than 10seconds 99% of the time.

Time for customer care to receive a response to a typical query (e.g. last 15 days callhistory for a single subscriber) should be less than 10 seconds 95% of the time, less

an secon s o e me

Concurrent query workload from financial systems Typically will pull all new records once per day.

Customer care has rapid access (as above) to last 15 days history.

Longer term provide the option to engineer long-term storage for business intelligenceapplications


38


39/40


40/40

ere erv ces

Prepaid Allows operators to offer services with prepaidaccount and perform call control in real-time (balance check).

Number portability Allows subscribers to keep old phonenumber when changing service provider

Black list allows subscribers to screen calls made from

certain originating phone numbers White list allows only calls from certain originating phone

numbers

Caller ID display caller phone number on receivers displaydevice

Caller Name Delivery display caller name on receiversdis la device


40

Date post:	08-Apr-2018
Category:	Documents
Upload:	chocochipgem
View:	218 times
Download:	0 times

IN explained

Documents