180 likes | 188 Views
This document highlights the key initiatives and programs related to transitioning to an all-IP network, including service transition, testbeds, routing architectures, and public safety applications. It also discusses the ATIS/SIP Forum IP-NNI Joint Task Force and the role of the Testbeds Landscape Team in validating solutions for the All-IP migration.
E N D
All-IP Transition Initiatives Jackie Voss Manager, Global Standards Development ATIS June 4, 2015
ATIS All-IP Program Highlights: • Service Transition • ATIS/SIP Forum IP-NNI Joint Task Force • Public Safety Related Applications Task Force • Testbeds
ATIS’ All-IP Program ASOG (including Ethernet Ordering) Testbeds Back Office TPBAG and COCAG (Numbering Guidelines) Rural Call Completion NRSC/CSRIC Best Practices Operations and Customer Care Industry Best Practices Lawful Intercept Public Safety Related Apps Business Application Wireless Emergency Alerts ESINet ATIS/SIP Forum Routing Architectures Routing Synchronization PSTN to IP Protocol Interworking Network Interconnection ATIS/SIP Forum IP-NNI Function Use Cases Requirements Architecture/ Design Protocol or Data Model Definition Implementation Verification Operations/ Maintenance Deliverable ->
Service Transition Work • ATIS is analyzing a basic set of services commonly provided in circuit switch PSTN, and addresses the technical issues surrounding support of these services in a mixed circuit switch/packet switch environment and, in the future, all-packet-switch environment. • Output to include detailed call flows, new ISUP/SIP and TCAP/IP inter-workings and extensions to SIP in support of: • Toll Free Calling • LIDB Services • CNAM • Operator Based Services • Priority Government Services
ATIS/SIP Forum IP-NNI Joint Task Force In December 2013, ATIS and SIP Forum launched a joint IP-NNI Task Force to simplify IP interconnection for voice: • Protocol: detailed specification of IP-NNI protocols • Routing: assess options for sharing NNI interconnection data and routing VoIP calls between service providers • IP Interconnection Routing (ATIS-1000062): • Identifies a range of routing options • Does not recommend a preferred approach • IP-NNI Profile (ATIS-1000063): • Detailed “on-the-wire” protocol specification Protocol and Routing documents published May 2015
IP-NNI Task Force – Business Value • Today’s reality: • IP-NNI: market segment focus • Specifications: similar, but not identical • FCC objective: all-IP interconnection. • Possible approaches: • IP “islands” • Market decides … eventually • Mandate single IP interconnect • Voluntary industry collaboration ATIS 3GPP/GSMA IP-NNI CableLabs SIP Connect Objective: prove option #4 is viable
Potential Phase 2 Topics • IP-NNI Phase 1 focused on: • Voice interconnection • Documented routing alternatives • IP-NNI Phase 2 could: • Enhance security mechanisms for IP-NNI • Specify secure caller-ID • Address services beyond voice: • Video, RCS • Further evaluate routing alternatives to validate interworking approach and “narrow options”.
Public Safety Related Applications Task Force (PSRA TF) • Objective is to address implications of all-IP migration on infrastructure associated with public safety. • Task Force is examining multiple, critical applications that will be impacted due to dependencies on legacy PSTN technologies and services and copper sunset. • ATIS addressing need for information and resources on available solutions and best practices. • Distributed an electronic Request for Information (RFI) to stakeholder organizations to collect data supporting analysis: • http://www.surveygizmo.com/s3/2055421/ATIS-RFI
PSRA TF Status • Continuing the collaboration with industry associations, ATIS collecting detail on target applications via the RFI. • RFI remains open as efforts continue to broaden response base. • Proposed actions (after RFI completion): • Develop Final Report and Conclusions • Share output with relevant regulatory and industry interest groups • Explore means for ATIS to host the information and communicate detailed solution data to industry (on a continuing basis) • Examine other opportunities for industry education
Testbeds Landscape Team Testbeds Landscape Team (LT) launchedin December 2014 to address: Business Problem: • Industry transition initiatives call for testbeds to validate solutions All-IP migration (e.g., numbering evolution, IP-NNI routing, authenticated caller-ID). • Individual testbeds duplicate many functions and are inefficient to implement and maintain. Scope of Work: • Evaluate existing testbed activities to identify common requirements and recommend path forward.
Testbeds: Context • ATIS Testbed LT is both broader and narrower than the FCC proposed testbed: • Broader: more than just “numbering” • E.164 + Toll Free • Routing architectures • Metadata and secure Caller-ID • Narrower: focus on priority business problems • Supporting transition to All-IP and IP-NNI • Includes target, but in the context of practical transition
Testbeds Use Cases • Numbering: • Just-in-time number assignment • Provisioning of routing information and metadata • Routing: • Scenarios to support IP-NNI • 800-number routing • Provider-to-provider: • Exchanging metadata between service providers • Anti-spoofing (secure Caller-ID)
Testbeds Use Cases by Title • Use Case #1: Individual and 1000s Block • Use Case #2: NS Records • Use Case #3: URIs • Use Case #4: Distributed Service Bureau • Use Case #5: 800 • Use Case #6: LERG IP Enhancements • Use Case #7: Exchange of data using in-band • Use Case #8: Data Verification - Anti-Spoofing • Use Case #9: Use of TN certificates – Anti-Spoofing • Use Case #10: Alternative Approach for Acquiring TN
Testbed Definition Physical Testbed Virtual Testbed A physical location for vendors to bring equipment for an “event” or for ongoing tests • Not our focus SP-A SP-B Test plans, methodology, and program management to facilitate SP-SP and vendor testing to progress business priorities • This is our focus
Status • Identify priority use cases • Assess level of interest in testbed participation • Initial summary of landscape • Analysis • Use cases vs. equipment / labs available • Synergies between use cases • Published initial report (Testbeds Landscape Team Assessment and Next Steps) • Recommendations and next steps • Implement recommendations
Testbeds LT Cooperation with IP-NNI Task Force • IP-NNI Task Force: • Identified alternatives for IP-NNI routing • Did not specify secure caller-ID • Industry solution still emerging • Testbeds LT use cases include: • IP-NNI routing • Anti-spoofing (secure caller-ID) • Proposed collaboration: • IP-NNI Task Force refines use cases • Testbeds LT validates key IP-NNI concepts
Next Steps • Develop formal recommendations for ATIS Testbed program. • Priority use cases • Commitment to participate in testing • Detailed test plans based on formal commitment • Final report with recommendations is targeted for delivery by 3Q2015.
Questions? If you have any questions or comments, please contact: Jackie Voss Manager, ATIS Global Standards Development jvoss@atis.org