1 / 30

Outline

Outline. IN Standards Overview: IN Standards - North America IN Standards - Global IN Genealogy Domain Convergence Functional Convergence Essential Concepts IN Call Walkthrough. IN Standards - North America. American National Standards Institute (ANSI)

baina
Download Presentation

Outline

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Outline • IN Standards Overview: • IN Standards - North America • IN Standards - Global • IN Genealogy • Domain Convergence • Functional Convergence • Essential Concepts • IN Call Walkthrough

  2. 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 Vendors Participants Bellcore STENTOR T1S1 T1S1: ANS on IN RBOCs Canadian NSG IECs US National Study Group ITU-T T1S1 - Focal point for development of North American consensus

  3. US Participants IN Standards Bodies - Global • European TelecommunicationStandardisation Institute (ETSI) • Sub-Technical Committees (NA6, SPS3, ...) Canada European Participants T1S1 ETSI ITU-T: IN CS-x ETSI: CORE INAP CAMEL ITU-T Australia Japan Others ITU-T IN Standards: International Perspective

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

  5. Domain Convergence FPLMTS GR1298 Future Services Architecture CS-3 GR1298 BB? Originating/Terminating Services Architecture GR1298 CS-2 WIN ANSI IN CAMEL X.500 AIN 0.1 CS-1R CITEL X.500 CS-1 Rel 0.0 Service specific PVN/ ACCS Freephone/PVN/ ACCS 800 1987 1990 1994 1997 Domain convergence provides service ubiquity

  6. Level of detail Functional Convergence GR1298 ANS on IN CS-1 (1995) CS-2 (1997) ETSI Core INAP 2 Functionality ETSI Core INAP 1 Functional convergence between IN standards

  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. Services and Service Features Service Plane Service Independent Building Blocks Global Functional Plane Functional Entities and Information Flows Distributed Functional Plane Physical Nodes and Protocol Interfaces Physical Plane Intelligent Network Conceptual Model

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

  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. 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. SIB 1 SIB 2 SIB 3 SIB 6 SIB 4 SIB 5 POI Basic Call Process POR POR 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

  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 • 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 • CS-2 • CS-1 SIBs + • Authenticate • End • Initiate Service Process • Join • Message Handler • Service Filter • Split • Basic Call Process • Basic Call Unrelated Process A lot has been done, but SIB specifications are not yet at a point where multi-vendor implementations are possible.

  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-BCSM T-BCSM O-BCSM T-BCSM Called Party Switch A Switch B Calling Party

  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 PIC Exit Event DP PIC

  16. TDP-R TDP-N Detection Point Types and Control Relationships Relationship with Service Suspend Call Processing - Logic exists Response Required No Yes No Yes • Four classes of DP are defined. • Relationship between SSF and service logic is either “Control” or “Monitoring”. TDP-R Initiates Disallowed x TDP-N Process Process x EDP-R n/a x x EDP-N n/a x x …which becomes a monitoring relationship when no EDP-Rs remain. Any EDPs left are discarded when the SSF-SCF relationship ends. A TDP-R initiates a control relationship… Control Relationship Monitoring Relationship EDP-R/N EDP-N EDP-R/N may be armed for the current call only. TDP-Rs are ignored while a control relationship exists. TDP-Ns are always processed. time

  17. AIN Release 0.0 "Generalized Call State Model" Idle Trigger Checkpoint: equivalent to TDP-R Off-Hook Digit Collection/ Analysis Trigger Checkpoints Service Logic Interaction Digit Analysis (optional) Routing • 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. Originating Call Model Terminating Call Model Disconnect Null Exception Disconnect Null Exception Origination Attempt Termination Attempt Authorizing Orig. Attempt Authorizing Termination Hunting Facility Collecting Information Information Collected Analyzing Information Information Analyzed Selecting Route Network Busy Autorizing Call Setup Call Proceeding AIN Release 0.1 Call Model

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

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

  21. 1. O_NULL (e1) Origination_ T Exception Attempt (e10) Feature (e9) Disconnected Requested (e14) Orig. Denied 11. T_NULL 2. AUTHORIZE_ORIG. _ATTEMPT Exception (e20) Termination_ T T (e2) Origination_Attempt_Authorized Attempt (e28) Cleared (e29) Term. Denied (e15) Collect Timeout 12. AUTHORIZE_TERMINATION 3. COLLECT_INFORMATION (e21) Call Presented T (e3) Info._Collected (e10) Feature (e30) T_Busy Requested (e16) Invalid Info. T/E 13. SELECT_FACILITY 4. ANALYZE_INFORMATION E (e22) T (e4) Info._Analyzed Term_Resource_ SS7 failure occurs (e10) Feature Available Requested (e31) Call Rejected route busy (e17) Network_Busy 5. SELECT_ROUTE 14. PRESENT_CALL T (e23) Call (e5) Route Selected Accepted (e10) Feature Requested (e18) Auth. Failure T/E 15. T_ALERTING 6. AUTHORIZE_CALL_SETUP (e6) Call Setup Authorized E (e32) T_No_Answer (e24) T_Answer (e10) Feature (e27) Mid-call Requested route busy 16. ACTIVE 7. SEND_CALL (e19) O_Called_ (e25) Disconnected E (e7) Party_Busy called party reconnected T/E O_Term_Seized (e27) Mid-call (e11) Mid-call T/E 8. O_ALERTING 17. RELEASE PENDING E (e33) O_No_Answer (e26) Release Timeout (e8) O_Answer (e11) Mid-call 9. ACTIVE (e12) Cleared called party reconnected (e11) Mid-call 10. RELEASE PENDING (e13) Release Timeout (e11) Mid-call Bellcore GR1298 Call Model Originating BCSM Terminating BCSM AIN Release 1 not used

  22. Bearer channel control • Service control • Management 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 to other SDFs SDF SCF SRF to other SCFs IAF to SDFs, SCFs and IAFs CUSF SSF SCUAF CCF CCAF CCF

  23. Example Physical Architectures 1 SMAF SMF SCEF SCP SDF SCF SRF IP SSP SSF CCF CCAF CCF

  24. SMAF SCEF Example Physical Architectures 2 SMF SDF SCF SRF Service Node SSP SSF CCF CCAF CCF

  25. Outline • IN Standards Overview • Essential Concepts • Walkthrough

  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 - ¦ Call Processing Suspended

  27. SCP Message Encoding Rules 1. Select the operation based on conditions encountered 2. Apply parameter population rules for operation selected 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 TCAP Message to SCP

  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 From data provided in the SSP message, the SCP determines which service logic program to invoke Service 5 Service 4 Service 3 Service 2 Service 1

  29. SSP Message Encoding Rules 1. Select the operation based on service logic instructions 2. Apply parameter population rules for operation selected 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 TCAP Message to SSP

  30. IN Call Walkthrough - 5 Message from SCP • 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 SCP Message Decoding At which PIC should call processing resume? AIN Call Processing

More Related