Download INF: Intelligent Network Architecture and Basic Concepts

INF: Intelligent Network Architecture and Basic Concepts
Outline
• IN Standards Overview:
•
•
•
•
•
IN Standards - North America
IN Standards - Global
IN Genealogy
Domain Convergence
Functional Convergence
• Essential Concepts
• IN Call Walkthrough
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
IN Standards - North America
American National Standards Institute (ANSI)
• Committee T1 (T1M1, T1P1, T1S1, ...)
• Telecommunications Industry Forum (TIA)
(TR45.2 - Wireless IN, ...)
TIA:
Wireless IN
TIA
Bellcore:
TRs
GRs
Canadian
Participants
Vendors
Bellcore
STENTOR
T1S1
RBOCs
IECs
Canadian
NSG
T1S1:
ANS on IN
US National
Study Group
ITU-T
T1S1 - Focal point for development
of North American consensus
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
IN Standards Bodies - Global
European Telecommunication
Standardisation Institute (ETSI)
• Sub-Technical Committees (NA6, SPS3, ...)
Canada
US
Participants
European
Participants
T1S1
ETSI
ITU-T:
IN CS-x
ETSI:
CORE INAP
CAMEL
ITU-T
Australia
Japan
Others
ITU-T IN Standards: International Perspective
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Service-Specific IN
(800, ACCS, VPN, …)
IN Genealogy
AIN Rel. 1 & 2
Benchmark:
ITU-T Capability Sets 1, 2
AIN Rel. 0.0
AIN Rel. 0.1
ITU-T CS-1
GR1298 (Rel. 0.2)
ITU-T CS-1R
ITU-T CS-2
ETSI Core INAP
ETSI Core INAP
GSM CAMEL
ANSI ANS on
IN
ITU-T CS-3
TR45.2 WIN
FPLMTS/IMT-2000
UMTS
Legend
N.A. (Bellcore) de facto Standards
ITU-T Standards
N.A. (ANSI, TIA) de jure Standards
European (ETSI) Standards
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Domain Convergence
FPLMTS
GR1298
Future Services
Architecture
CS-3
GR1298
Originating/Terminating
Services Architecture
GR1298
ANSI IN
AIN 0.1
CS-2
X.500
BB?
WIN
CAMEL
CS-1R CITEL
X.500
Rel 0.0
Service
specific
PVN/
ACCS
800
1987
1990
CS-1
Freephone/PVN/
ACCS
1994
1997
Domain convergence provides
service ubiquity
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Functional Convergence
Level
of
detail
GR1298
ANS on IN
CS-1 (1995)
CS-2 (1997)
ETSI
Core
INAP 2
ETSI Core INAP 1
Functionality
Functional convergence between
IN standards
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Outline
• IN Standards Overview
• Essential Concepts
•
•
•
•
•
IN Conceptual Model
Service Plane
Global Functional Plane
Call Model
Distributed Functional Plane, Physical Plane
• IN Call Walkthrough
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Intelligent Network Conceptual Model
Service Plane
Global Functional Plane
Distributed Functional Plane
Physical Plane
98 01 27
Services
and
Service
Features
Service
Independent
Building
Blocks
Functional
Entities and
Information
Flows
Physical
Nodes and
Protocol
Interfaces
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Intelligent Network Conceptual Model
Call Forward
FreePhone
Services
and
Service
Features
Service
Independent
Building
Blocks
Functional
Entities and
Information
Flows
Physical
Nodes and
Protocol
Interfaces
98 01 27
Time of Day
Reverse
Charging Originating
Location
Calling Party
Service Plane
Translation
Call Model
Global Functional Plane
User
Interaction
FEA 1
FE A FEA 2
SSP
FEA 3
FEA 4
Distributed Functional Plane
FE B
FE C
SCP
Physical Plane
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Type “A” versus Type “B” Services
Type “A” services are:
• single-ended
• applies to one and only one party in a call
• orthogonal at service and topology levels to any other call parties
• single point of control
• same aspects of a call are influenced by only one SCF at a time
• single medium
• implicit assumption in call models developed for CS-1
• avoids issues in coordinating multiple connections within one context
Type “B” services:
• multiple subscribers
• service visible to multiple parties
• topology manipulation
• may alter topology of call as seen by one or more call parties
• multiple external entities
• each call party may have services on their own control nodes
• requires rich information flow to support distributed relationships
• distributed feature arbitration requires significant context sharing
• multi-media
• multiple bearers need to be controlled in a coordinated manner
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Type “A” Range of Services
FreePhone ("800")
Virtual Private Network (VPN)
Universal Personal Telecommunications
User-defined Routing
Abbreviated Dialling
Originating Call Screening
Terminating Call Screening
Call Forwarding
Call Distribution
Call Volume Distribution
Destination Call Routing
Selective Call Forwarding
Security Screening
Premium Rate
Split Charging
Credit Card Calling
Automatic Alternate Billing
Televoting
Mass Calling
Follow-Me-Diversion
Malicious Call Identification
Completion of Call to
Conference Calling
(Busy/Don't Answer)
Type “A” Services represent a
significant set of implementable and
commercially valuable services
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Global Capabilities - SIBs
What are SIBs?
• standard, reusable network-wide capabilities used to create service features
• independent from any specific functional or physical architecture
• each is a complete activity
• have one logical start point, possibly several end points
How are they are intended to be used?
• provide a chain of functions that represent a service feature interacting with a
basic call
SIB 1
SIB 2
SIB 4
POI
98 01 27
Basic Call Process
SIB 3
SIB 6
SIB 5
POR
POR
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Service Independent Building Blocks
CS-1
• Algorithm
• Charge
• Compare
• Distribution
• Limit
• Log Call Information
• Queue
• Screen
• Service Data Management
• Status Notification
• Translate
• User Interaction
• Verify
• Basic Call Model
Some SIBs:
• are too general:
• CS-1 SIBs +
• Algorithm
• Authenticate
• represent significant aggregation of
• End
functions:
• Initiate Service
• Translate (time, day, holiday, etc.)
Process
• have significant technical issues
• Join
needing resolution:
• Message Handler
• Join/Split
• Service Filter
• are non-“atomic” and require
• Split
“parallelism”:
• Basic Call Process
• User Interaction, Charge
• Basic Call
• require market specific
Unrelated Process
implementation:
• Charge
• relate to multiple calls
• Queue, Limit, Service Filter
CS-2
A lot has been done, but SIB specifications are not yet at
a point where multi-vendor implementations are possible.
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Call Model
O-BCSM
T-BCSM
Switch A
O-BCSM
T-BCSM
Switch B
Called Party
Calling Party
IN call model consists of two separate sets of call processing logic
• originating:
• originating call processing logic provides support to the Calling Party, and is
modelled by the Originating Basic Call State Model (O-BCSM)
• • terminating
• terminating call processing logic provides support to the Called Party, and is
modelled by the Terminating Basic Call State Model (T-BCSM)
• • both sides of the call model are active within a given node
• an intra-switch call still requires an O-BCSM and a T-BCSM
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Points in Calls (PICs)
PICs provide an external view of a call processing state or event to
IN service logic.
PICs are vendor independent, providing a standardized view of call
processing behaviour.
PICs are characterized entirely by means of:
•
•
•
•
entry event(s)
exit event(s)
actions performed within the PIC
information available at the end of the PIC
Detection points are placed
between PICs.
Entry Event
PIC
Exit Event
DP
PIC
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Detection Point Types and Control Relationships
Relationship with Service
Logic exists
No
Yes
Four classes of DP are
defined.
Relationship between
SSF and service logic
is either “Control” or
“Monitoring”.
TDP-R
Initiates
Disallowed
TDP-N
Process
Process
EDP-R
n/a
x
EDP-N
n/a
x
A TDP-R initiates a
control relationship…
Control Relationship
Suspend Call Processing Response Required
No
Yes
x
x
x
x
…which becomes
a monitoring
relationship when
no EDP-Rs remain.
Any EDPs left are
discarded when
the SSF-SCF
relationship ends.
Monitoring Relationship
EDP-R/N
EDP-N
EDP-R/N may be armed
for the current call only.
TDP-Ns are always
processed.
TDP-R
TDP-Rs are ignored while
a control relationship exists.
TDP-N
time
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
AIN Release 0.0 "Generalized Call State Model"
Idle
Trigger Checkpoint: equivalent to TDP-R
Off-Hook
Digit
Collection/
Analysis
Trigger
Checkpoints
Routing
Service Logic
Interaction
Digit
Analysis
(optional)
• First DP used is “Point of Initiation”
• Effectively no “Points of Synchronization”
• “Point of Return” to BCSM when service
logic finishes is always Routing
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
AIN Release 0.1 Call Model
Originating Call Model
Disconnect
Terminating Call Model
Null
Exception
Disconnect
Origination Attempt
Authorizing Orig. Attempt
Null
Exception
Termination Attempt
Authorizing Termination
Hunting Facility
Collecting Information
Information Collected
Analyzing Information
Information Analyzed
Selecting Route
Network Busy
Autorizing Call Setup
Call Proceeding
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
CS-1 Call Model
Originating Half Call Model
10
O_Abandon
Terminating Half Call Model
1. O_Null & Authorize
Origination Attempt
1
6. O_Exception
18
7. T_Null & Authorize
Termination Attempt
T_Abandon
Term. Attempt Authorized
12
8. Select_Facility and
13
Present Call
Orig.-Attempt_Authorized
2. Collect Information
2
T_Called PartyBusy
Collected_Info
9. T_Alerting
3. Analyze Information
4
Analyzed_Info
3
Route_Select_Failure
4. Routing and
Alerting
O_Called_Party_Busy
5
6
O_Answer
9
O_Disconnect
98 01 27
14
T_No_Answer
7
O_No_Answer
15 T_Answer
10. T_Active
17
T_Disconnect
16
T_Mid_Call
5.O_Active
8 O_Mid_Call
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
CS-2 Call Model
Originating BCSM
O_Abandon
Terminating BCSM
O_Exception
O_Null
Origination_Attempt
origination_denied
T_Exception
T_Null
Auth_Orig_Attempt
T_Abandon
Origination_Attempt_Authorized
collect_timeout
Termination_Attempt
termination_denied
Auth_Term_Attempt
Collect_ Information
Termination_Attempt_Authorized
Collected_Information
invalid_information
Select Facility
T_Busy
Analyse_Information
route_busy
SS7 Failure
Analysed_Information
Facility_Selected_and_Available
presentation_failure
Present_Call
Select_Route
Call _Accepted
Route_Select_Failure
route_failure
T_Alerting
auth_route_failure
Auth_Call_Setup
call_rejected
T_No_Answer
T_Answer
O_Called_Party_Busy
Send_Call
O_Mid_Call
T_Active
T_Mid_Call
Calling Party
O_Term_Seized
T_Suspended
O_Alerting
O_No_Answer
O_Mid_Call
Called Party
T_Suspended
t_active_failure
T_Re_Answer
reconnect
t_suspend_failure
T_Disconnect
O_Answer
O_Active
O_Mid_Call
Calling Party
Called Party
O_Suspended
O_Suspended
o_active_failure
O_Re_Answer
reconnect
o_suspend_failure
O_Disconnect
O_Mid_Call
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Bellcore GR1298 Call Model
Originating BCSM
(e9) Disconnected
Terminating BCSM
1. O_NULL
T (e1) Origination_
Attempt
(e10) Feature
Requested
Exception
(e14) Orig. Denied
2. AUTHORIZE_ORIG. _ATTEMPT
T
(e2) Origination_Attempt_Authorized
(e28) Cleared
11. T_NULL
T (e20) Termination_
Attempt
(e29) Term. Denied
(e15) Collect Timeout
12. AUTHORIZE_TERMINATION
3. COLLECT_INFORMATION
T
(e21) Call Presented
(e3) Info._Collected
(e10) Feature
Requested
(e30) T_Busy
(e16) Invalid Info.
T
E
(e4) Info._Analyzed
(e10) Feature
Requested
route busy
5. SELECT_ROUTE
(e22)
Term_Resource_
Available
(e17) Network_Busy
SS7 failure occurs
(e31) Call Rejected
14. PRESENT_CALL
(e23) Call
Accepted
T
(e5) Route Selected
(e10) Feature
Requested
T/E
13. SELECT_FACILITY
4. ANALYZE_INFORMATION
(e18) Auth. Failure
E
(e27) Mid-call
7. SEND_CALL
E
(e11) Mid-call
(e7)
O_Term_Seized
8. O_ALERTING
E
(e8) O_Answer
T/E
15. T_ALERTING
6. AUTHORIZE_CALL_SETUP
(e6) Call Setup Authorized
(e10) Feature
Requested
route busy
(e11) Mid-call
Exception
T/E
(e19) O_Called_
Party_Busy
T/E
(e33) O_No_Answer
(e32) T_No_Answer
(e24) T_Answer
16. ACTIVE
(e25) Disconnected
called party reconnected
(e27) Mid-call
17. RELEASE PENDING
(e26) Release Timeout
9. ACTIVE
(e12) Cleared
called party reconnected
(e11) Mid-call
10. RELEASE PENDING
(e13) Release Timeout
AIN Release 1 not used
(e11) Mid-call
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
IN Functional Architecture
• Defined in CS-1
• Identified in CS-1
• New in CS-2
• Identified in CS-1 but not yet worked
Network Boundary
SMAF
SMF
to SMFs
SCEF
to other SMFs
to SDFs and SCFs
SCF
CCAF
98 01 27
to other SDFs
SRF
to other SCFs
SCUAF
SDF
CUSF
IAF
to SDFs, SCFs and
IAFs
SSF
CCF
CCF
• Bearer channel control
• Service control
• Management
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Example Physical Architectures 1
SMAF
SMF
SCEF
SCP
SCF
SDF
SRF
IP
SSP
CCAF
98 01 27
SSF
CCF
CCF
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Example Physical Architectures 2
SMAF
SMF
SCEF
SDF
SCF
Service Node
SSP
CCAF
98 01 27
SRF
SSF
CCF
CCF
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
Outline
• IN Standards Overview
• Essential Concepts
• Walkthrough
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
IN Call Walkthrough - 1
• Call is processed through the basic
call state model in the SSP
BCSM
• A point in call processing where IN
service logic may be invoked is
reached (i.e. a TDP-R)
• Trigger criteria are checked
Armed DP
• Specific trigger criteria are met
relating to a specific trigger item
• Call processing is suspended
• SSP retains responsibility for call
integrity and resource management
throughout
98 01 27
Trigger item 1 - X
Trigger item 2 - X
Trigger item 3 - ¦
Call Processing Suspended
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
IN Call Walkthrough - 2
• Based on the conditions
encountered, an INAP
operation is selected and its
argument populated with
parameters
TDP, Trigger,
Triggering Criteria
SCP Message
Encoding Rules
• The operation and its
argument are encoded and a
message is sent to the SCP
• This opens a control
relationship with the SCP
1.
Select the operation
based on conditions
encountered
2.
Apply parameter
population rules for
operation selected
TCAP Message
to SCP
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
IN Call Walkthrough - 3
• The received message is
decoded at SCP
• Based on the information
received, the SCP 'identifies'
the service logic program to
be invoked and creates an
instance of it for this
transaction
98 01 27
Message from SSP
SSP Message
Decoding
Service 5
Service 4
Service 3
Service 2
Service 1
From data provided
in the SSP message,
the SCP determines
which service
logic program
to invoke
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
IN Call Walkthrough - 4
• Service logic at the SCP may
generate new information for
handling the call
Instructions plus
parameters generated
by SCP based service logic
• The appropriate SSP instruction
message is selected and its
parameters populated
SSP Message
Encoding Rules
• The message is encoded
1.
Select the operation
based on service logic
instructions
2.
Apply parameter
population rules for
operation selected
• Instructions are sent to the SSP
TCAP Message
to SSP
98 01 27
Lewis Robart
INF: Intelligent Network Architecture and Basic Concepts
IN Call Walkthrough - 5
SSP decodes reply from SCP
Message from SCP
From message contents, the SSP
determines what information to
update and what to do next
SCP Message
Decoding
If required, EDPs are armed
Call processing resumes at the
indicated PIC
Depending on the response, the
SSP-SCP relationship may
remain in control mode, change
to monitoring mode, or
terminate.
At which PIC
should call
processing
resume?
AIN Call
Processing
SSP retains responsibility for call
integrity and resource
management throughout
98 01 27
Lewis Robart