1. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 1 Outline IN Standards Overview: IN Standards - North America IN Standards - Global IN Genealogy Domain Convergence Functional Convergence Essential Concepts IN Call Walkthrough

2. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 2 IN Standards - North America T1S1 - Focal point for development of North American consensus T1S1 - Focal point for development of North American consensus Bellcore RBOCs ITU-T T1S1 Canadian Participants Vendors IECs US National Study Group Canadian NSG STENTOR T1S1: ANS on IN Bellcore: TRs GRs American National Standards Institute (ANSI) Committee T1 (T1M1, T1P1, T1S1,...) Telecommunications Industry Forum (TIA) (TR45.2 - Wireless IN,...) TIA: Wireless IN TIA

3. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 3 IN Standards Bodies - Global ITU-T IN Standards: International Perspective T1S1 ITU-T European Participants Japan Australia Others ETSI US Participants Canada ETSI: CORE INAP CAMEL ITU-T: IN CS-x European Telecommunication Standardisation Institute (ETSI) Sub-Technical Committees (NA6, SPS3,...)

4. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 4 IN Genealogy Service-Specific IN (800, ACCS, VPN, …) AIN Rel. 1 & 2 AIN Rel. 0.0 AIN Rel. 0.1 GR1298 (Rel. 0.2) ITU-T CS-1 ITU-T CS-1R ITU-T CS-2 TR45.2 WIN ETSI Core INAP GSM CAMEL ITU-T CS-3 FPLMTS/IMT-2000UMTS ETSI Core INAP ANSI ANS on IN ITU-T Standards European (ETSI) Standards N.A. (Bellcore) de facto Standards N.A. (ANSI, TIA) de jure Standards Legend Benchmark: ITU-T Capability Sets 1, 2 Benchmark: ITU-T Capability Sets 1, 2

5. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 5 1987199019941997 800 Rel 0.0 AIN 0.1 GR1298 PVN/ ACCS Freephone/PVN/ ACCS CS-1R CS-1 CS-2 Service specific Originating/Terminating Services Architecture Future Services Architecture X.500 WIN CAMEL CS-3 FPLMTS BB? ANSI IN CITEL GR1298 Domain convergence provides service ubiquity Domain convergence provides service ubiquity Domain Convergence

6. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 6 Functional Convergence Functional convergence between IN standards Functional convergence between IN standards Functionality Level of detail GR1298 CS-2 (1997) CS-1 (1995) ETSI Core INAP 1 ANS on IN ETSI Core INAP 2

7. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 7 Outline IN Standards Overview Essential Concepts IN Conceptual Model Service Plane Global Functional Plane Call Model Distributed Functional Plane, Physical Plane IN Call Walkthrough

8. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 8 Intelligent Network Conceptual Model Service Plane Distributed Functional Plane Physical Plane Global Functional Plane Services and Service Features Service Independent Building Blocks Functional Entities and Information Flows Physical Nodes and Protocol Interfaces

9. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 9 Intelligent Network Conceptual Model SSP SCP Service Plane Distributed Functional Plane Physical Plane Global Functional Plane FreePhone Time of Day Originating Location Reverse Charging Call Forward Calling Party Services and Service Features Call Model Translation User Interaction FEA 1 FEA 2 FEA 3 Service Independent Building Blocks Functional Entities and Information Flows Physical Nodes and Protocol Interfaces FEA 4 FE A FE B FE C

10. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 10 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

11. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 11 Type “A” Range of Services 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 Busy Subscriber Conference Calling 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 (Busy/Don't Answer) Type “A” Services represent a significant set of implementable and commercially valuable services

12. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 12 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 1SIB 2SIB 3 SIB 4SIB 5 SIB 6 POIBasic Call ProcessPORPOR

13. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 13 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 CS-2 CS-1 SIBs + Authenticate End Initiate Service Process Join Message Handler Service Filter Split Basic Call Process Basic Call Unrelated Process Some SIBs: are too general: Algorithm represent significant aggregation of functions: Translate (time, day, holiday, etc.) have significant technical issues needing resolution: Join/Split are non-“atomic” and require “parallelism”: User Interaction, Charge require market specific implementation: Charge relate to multiple calls Queue, Limit, Service Filter A lot has been done, but SIB specifications are not yet at a point where multi-vendor implementations are possible.

14. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 14 Call Model 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 O-BCSMT-BCSMO-BCSMT-BCSM Calling Party Called Party Switch A Switch B

15. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 15 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 Exit Event DP PIC

16. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 16 Detection Point Types and Control Relationships Four classes of DP are defined. Relationship between SSF and service logic is either “Control” or “Monitoring”. time Control Relationship Monitoring Relationship Relationship with ServiceSuspend Call Processing - Logic existsResponse Required NoYesNoYes TDP-RInitiatesDisallowedx TDP-NProcessProcessx EDP-Rn/axx EDP-Nn/axx EDP-R/N EDP-N TDP-N TDP-R A TDP-R initiates a control relationship… EDP-R/N may be armed for the current call only. …which becomes a monitoring relationship when no EDP-Rs remain. TDP-Rs are ignored while a control relationship exists. TDP-Ns are always processed. Any EDPs left are discarded when the SSF-SCF relationship ends.

17. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 17 AIN Release 0.0 "Generalized Call State Model" Trigger Checkpoints Routing Digit Collection/ Analysis Off-Hook Idle Service Logic Interaction Digit Analysis (optional) Trigger Checkpoint: equivalent to TDP-R First DP used is “Point of Initiation” Effectively no “Points of Synchronization” “Point of Return” to BCSM when service logic finishes is always Routing

18. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 18 AIN Release 0.1 Call Model Originating Call ModelTerminating Call Model Null Authorizing Termination ExceptionDisconnect Termination Attempt Hunting Facility Authorizing Orig. Attempt Analyzing Information Call Proceeding Information Collected Information Analyzed NullExceptionDisconnect Origination Attempt Autorizing Call Setup Network Busy Selecting Route Collecting Information

19. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 19 CS-1 Call Model 6. O_Exception 1. O_Null & Authorize Origination Attempt 2. Collect Information 3. Analyze Information O_Disconnect 5.O_Active Orig.-Attempt_Authorized Collected_Info Analyzed_Info O_Called_Party_Busy 4. Routing and Alerting Route_Select_Failure O_No_Answer O_Abandon O_Mid_Call O_Answer 1 2 3 4 5 8 10 6 7 9 7. T_Null & Authorize Termination Attempt 8. Select_Facility and Present Call T_Disconnect Term. Attempt Authorized 9. T_Alerting 10. T_Active T_Mid_Call T_Called PartyBusy T_No_Answer T_Abandon T_Answer 12 13 14 15 16 17 18 Originating Half Call ModelTerminating Half Call Model

20. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 20 CS-2 Call Model Originating BCSM Terminating BCSM O_Null Auth_Orig_Attempt Collect_ Information Analyse_Information O_Exception Select_Route Auth_Call_Setup Send_Call O_Suspended O_Active O_Alerting route_busy Route_Select_Failure route_failure O_Mid_Call O_Disconnect O_Abandon O_Called_Party_Busy O_No_Answer auth_route_failure invalid_information collect_timeout origination_denied Origination_Attempt Origination_Attempt_Authorized Collected_Information Analysed_Information O_Term_Seized O_Answer O_Suspended o_active_failure o_suspend_failure reconnect Called PartyO_Re_Answer Calling Party T_Exception T_Disconnect T_Null Auth_Term_Attempt Select Facility Present_Call T_Suspended T_Active T_Alerting SS7 Failure presentation_failure T_Mid_Call T_Abandon T_No_Answer termination_denied Termination_Attempt Termination_Attempt_Authorized Facility_Selected_and_Available Call _Accepted T_Answer T_Suspended t_active_failure t_suspend_failure reconnect Called PartyT_Re_Answer Calling Party T_Busy call_rejected

21. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 21 Bellcore GR1298 Call Model Originating BCSMTerminating BCSM AIN Release 1 not used

22. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 22 IN Functional Architecture Bearer channel control Service control Management Defined in CS-1 Identified in CS-1 New in CS-2 Identified in CS-1 but not yet worked SMAF SSF CCF CCAF CCF SRF SCEF SMF to other SMFs to other SDFs to other SCFs SCUAF CUSF to SMFs to SDFs and SCFs to SDFs, SCFs and IAFs Network Boundary IAF SDF SCF

23. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 23 Example Physical Architectures 1 SCF SDF SMAF SSF CCF CCAF CCF SRF SCEF SMF SSP SCP IP

24. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 24 Example Physical Architectures 2 SCF SDF SMAF SSF CCF CCAF CCF SRF SCEF SMF SSP Service Node

25. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 25 Outline IN Standards Overview Essential Concepts Walkthrough

26. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 26 IN Call Walkthrough - 1 Call is processed through the basic call state model in the SSP A point in call processing where IN service logic may be invoked is reached (i.e. a TDP-R) Trigger criteria are checked 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 BCSM Armed DP Trigger item 1 - X Trigger item 2 - X Trigger item 3 - ¦ Trigger item 1 - X Trigger item 2 - X Trigger item 3 - ¦ Call Processing Suspended

27. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 27 IN Call Walkthrough - 2 Based on the conditions encountered, an INAP operation is selected and its argument populated with parameters The operation and its argument are encoded and a message is sent to the SCP This opens a control relationship with the SCP TDP, Trigger, Triggering Criteria SCP Message Encoding Rules 1.Select the operation based on conditions encountered 2.Apply parameter population rules for operation selected SCP Message Encoding Rules 1.Select the operation based on conditions encountered 2.Apply parameter population rules for operation selected TCAP Message to SCP

28. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 28 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 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 From data provided in the SSP message, the SCP determines which service logic program to invoke

29. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 29 IN Call Walkthrough - 4 Service logic at the SCP may generate new information for handling the call The appropriate SSP instruction message is selected and its parameters populated The message is encoded Instructions are sent to the SSP Instructions plus parameters generated by SCP based service logic to SSP SSP Message Encoding Rules 1.Select the operation based on service logic instructions 2.Apply parameter population rules for operation selected SSP Message Encoding Rules 1.Select the operation based on service logic instructions 2.Apply parameter population rules for operation selected TCAP Message

30. 98 01 27 INF: Intelligent Network Architecture and Basic Concepts Lewis Robart 30 IN Call Walkthrough - 5 SSP decodes reply from SCP From message contents, the SSP determines what information to update and what to do next 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. SSP retains responsibility for call integrity and resource management throughout AIN Call Processing Message from SCP At which PIC should call processing resume? At which PIC should call processing resume? SCP Message Decoding