BELL ATLANTIC VOIP SERVICES OPERATIONS & STANDARDS ISSUES

1. BELL ATLANTIC VOIP SERVICESOPERATIONS & STANDARDS ISSUES RAJ SRIKANTIAH BELL ATLANTIC TECHNOLOGY 500 WHITE PLAINS, NEW YORK NY 10604 914-644-2385; rajs@basit.com

2. CONTENTS • BA VOIP SERVICE HIGHLIGHTS • NETWORK ARCHITECTURE - KEY ELEMENTS • SERVICE FEATURES • NETWORK MANAGEMENT • KEY GOALS • INTEROPERABILITY - SERVICE PERSPECTIVE • BILLING & USAGE ACCOUNTING - FEATURE REQUIREMENTS • BILLING ARCHITECTURE - NOW

3. CONTENTS (CONTD.) • SETTLEMENT ARCHITECTURE OPTIONS • VOIP NM ARCHITECTURE GOALS • BA VOIP SERVICE EVOLUTION & RELATED ISSUES • PLATFORM INTEROPERABILITY - NETWORK PERSPECTIVE • SUMMARY & CONCLUSIONS - WHERE WE ARE TODAY & WHERE WE WANT TO BE

4. BA VOIP HIGHLIGHTS • WHOLESALE (CARRIER - CARRIER) VOICE OVER IP TELEPHONY TERMINATING SERVICE INITIALLY • SERVICES OFFERED VIA VOIP GW; 12 LATA’S EQUIPPED NOW; ALL 31 LATA’S IN BELL ATLANTIC FOOTPRINT WILL BE COVERED SOON • WHOLESALE ORIGINATING SERVICE - MID YEAR 2000 • RETAIL AND VALUE ADDED SERVICES TO FOLLOW

5. BA VOIP ARCHITECTURE - KEY ELEMENTS (SYSTEMS) • GATEWAYS (CISCO) • GATEKEEPERS (VOCALTEC) • FIREWALLS (PIX) • USAGE DATA COLLECTION SYSTEM (MINDCTI) • PERFORMANCE MONITORING & DATA COLLECTION (CONCORD)

6. VOIP RELEASE 1 GENERIC ARCHITECTURE

7. BA VOIP ARCHITECTURE - KEY ELEMENTS (SYSTEMS) CONTD. • BELL ATLANTIC INTERNET TELEPHONY NETWORK REFERENCE MODEL BASED ON ETSI TIPHON DOCUMENT DTS / TIPHON - 02002, V0.2.0. THIS SPECIFIES LOGICAL REFERENCE POINTS BETWEEN: - GW & GKPR, - GW POP & BECK-END SERVICES, - HKPR NOC & BACK-END SERVICES

8. BA VOIP SERVICE FEATURES • PSTN SWITCHED ACCESS VIA FCC ACCESS TARIFF FEATURE GROUPS • INTERNET ACCESS VIA T1 OR GREATER PER ITSP • H.323 PROTOCL SUPPORT • AVAILABILITY OBJECTIVE 99.98 % • ROUTING TO SUPPORT DIFFERENT ROUTES FOR DIFFERENT CARRIERS • TRAFFIC FROM A SPECIFIC ITSP END USER DELIVERED TO THE NETWORK SPECIFIED BY THE ITSP

9. BA VOIP NETWORK MANAGEMENT • IROC CENTER IN HARRISBURG, VA PROVIDES - ON-GOING OPERATIONS SUPPORT, - PERFORMANAGMENT & FAULT MANAGEMENT FUNCTIONS, & - LEGACY OSS INTERFACING / INTEGRATION SUPPORT

10. KEY ARCHITECTURE GOALS • INTEROPERABILITY • WHOLESALE / RETAIL TRAFFIC SEPARATION IN THE GATEWAY • TERMINATING / ORIGINATING TRAFFIC SEPARATION IN THE GATEWAY • SECURITY • COMMON / IINTEGRATED MANAGEMENT SYSTEM

11. KEY ARCHITECTURE GOALS CONTD. - KEY REQUIREMENTS TO BE MET BY VENDORS • TOTAL SOLUTION BASED ON COMMODITIZED, STDS.-COMPLIANT OFF THE SHELF COMPONENTS THAT WOULD SUPPORT PLUG & PLAY • SUPPORT FOR OSP, SIP & H.323, SNMP V.2, ETC. • SYSTEMS TO SUPPORT BILLING & SETTLEMENT IN CONFORMANCE WITH ESTABLISHED (& EVOLVING) STANDARDS • SYSTEM INTERFACES & INTEROPERABILTY BETWEEN GW - GW, GW -GKPR, GPR - GKPR, GKPR - CLEARING HOUSE (CH) AND CH - CH (OSP)

12. INTEROPERABILITY - SERVICE PERSPECTIVE THE FOLLOWING NEED TO BE SUPPORTED: BA Voip Sys Remote Voip Sys BA Voip Sys Local Voip GW BA Voip Sys Local / Remote Voip Trmnl BA Voip Sys Local Voip GKPR

13. BILLING & USAGE ACCOUNTING REQUIREMENTS • CALL DETAIL RECORDS (CDR’S) REQUIRED FOR ALL CALLS, DISTINGUISHED BETWEEN COMPLETED, RING NO ANSWER, & NON-COMPLETED ( BUSY) CALLS • CDR’S TO BE SENT IN A SECURE FASHION TO THE BILLED CARRIER’S (ITSP’S) BILLING SYSTEM, FOR REAL TIME ACCOUNTING INFORMATION, ON A PER CALL BASIS • SYSTEM MUST AGGREGATE, BY ITSP, CDR’S AND DOWNLOADTO BA CABS • SUPPORT OF BILLING DATA EXCHANGE BETWEEN BA & WHOLESALE CUSTOMER

14. BELL ATLANTIC VOIP BILLING ARCHITECTURE - NOW To Customers Generates & Renders Bill CABS Converts CDR into AMA format EBAC MindCTI Billing Sys Generates CDR VOIP GW COLLECTS USAGE DATA

15. BELL ATLANTIC VOIP BILLING & SETTLEMENT ARCHITECTURE - OPTION 1 (CONCEPTUAL) ITSP 1 CABS ITSP 2 MIND CTI ITSP 3 VOIP GW BELL ATLANTIC

16. BA VOIP BILLING & SETTLEMENT ARCHITECTURE - OPTION 2 (CONCEPTUAL) CH ITSP 1 CABS ITSP 2 MIND CTI ITSP 3 VOIP GW BELL ATLANTIC STANDARD I/F’S

17. BA VOIP NETWORK MANAGEMENT ARCHITECTURE GOALS • TMN COMPLIANCE • SUPPORT OF STANDARD INTERFACES BETWEEN • EMS - OSS • EMS - EMS • SUPPORT OF STANDARD INTERFACES BETWEEN • CH - CH • BILLING SYSTEMS

18. TMN • TMN IS A STANDARDS BASED NATIONAL (T1M1) AND INTERNATIONAL (ITU-T) RECOGNIZED NETWORK MANAGEMENT SOLUTION FOR TELECOMMUNICATIONS • PROVIDES A LAYERED MODEL BASED ON FUNCTIONAL AREAS. THESE ARE: FM, CM, AM, PM & SM

19. WHY TMN • PROVIDES A COMMON UNDERSTANDING AND FRAMEWORK FOR MANAGING A TELECOM. NETWORK VIA STANDARDS COMPLIANT SYSTEMS AND INTERFACES • ENABLES MULTI VENDOR SYSTEMS INTEROPERABILITY BASED ON STANDARD FUNCTIONAL, INFORMATION AND INTERFACE MODELS • SUPPORTS OPEN SYSTEMS & INTEROPERABILITY REQUIRED BY REGULATORY MANDATE • TMN IS BELL ATLANTIC’S TARGET ARCHITECTURE FOR NETWORK MANAGEMENT

20. VOIP EVOLUTION IN BA • SERVICES PLANNED FOR THE NEXT PHASE - RETAIL SERVICES - BASIC & ENHANCED CALLING FEATURES (PSTN CALL WAITING, DIRECTORY SERVICES, 3-WAY CALLING, ETC. - TWO-STAGE AND SINGLE-STAGE DIALING - INTERNET CALL WAITING - UNIFIED MESSAGING - IVR CAPABILITY - ETC.

21. VOIP EVOLUTION IN BA - ISSUES • TO SUPPORT MANY OF THE SERVICES, THE VOIP PLATFORM MUST SUPPORT: • SS7 INTERCONNECTION - ISSUE: MOVING FROM A ‘CLOSED” SIGNALING NETWORK TO AN “OPEN INTERCONNECTEDSIG. NTWK. SCENARIO • END - TO - END QOS & SLA - ISSUE: 1. NO CLEAR DEFINITION 2. PROBE POINTS (“WHERE”) 3. “STANDARD” METHODS /TOOLS • VENDOR TESTING BEFORE DELIVERING

22. PLATFORM INTEROPERABILITY - DIFFERENT LEVELS, JUST A FEW OF THEM: • SW VERSIONS, SAME SYSTEM, SAME VENDOR • DIFFERENT SYSTEMS (EG., GW, GKPR) SAME VENDOR • DIFEERENT SYSTEMS, DIFFERENT VENDORS • VENDOR SPECIFIC TEST BEDS & TEST SCENARIOS

23. SUMMARY & CONCLUSIONS - WHERE WE ARE NOW, WHERE WE WANT TO BE • STANDARD PRODUCTS EVOLVING, BUT MORE SO WITHIN A VENDOR PRODUCT LINE: MULTI-VENDOR INTEROPERABILITY MAJOR ISSUE • COMMON MANAGEMENT SYSTEM CAPABILITY IN INFANCY - NEED TO MOVE QUICKLY TO A STANDARD (TMN) STRUCTURE • VENDORS NEED TO DEMONSTRATE PLUG & PLAY TYPE CAPABILITY FOR MULTI-VENDOR ENVIRONMENT; THIS IS VERY LIMITED NOW. • INTEROPERABILITY AMONG OSS SYSTEMS &/OR MGMT. SYSTEMS STILL VERY DIFFICULT.

24. SUMMARY & CONCLUSIONS - WHERE WE ARE NOW, WHERE WE WANT TO BE (CONTD.) • IMTC MUST FURTHER THE WORK ON BILLING & SETTLEMENT INTEROP. RQMNTS • IMTC MUST CONTINUE ITS ROLE IN ENCOURAGING VENDORS TO MOVE MORE QUICKLY TOWARDS INTER-OPERABLE SYSTEMS IN AN OPEN, STANDARDS COMPLIANT FASHION • VENDORS MUST AGREE UPON AND IMPLEMENT VOIP TEST BED THAT WOULD ENABLE THEM TO JOINTLY PERFORM SYSTEM INTEROPERABILITY TESTS BEFORE THEY SHIP PRODUCTS TO THEIR CUSTOMERS.