1. 4/22/20031 Data Interchange Initiative Lower the Barrier of Entry to B2B eBusiness Prepared by Bennet Pang Bennet.pang@qwest.cm

2. 4/22/20032 What are the Barriers? Multiple B2B Gateways (File Formats, Transport Protocols, etc.) for OSS Interconnection Costly to Establish B2B Business Relationship – (Interconnection Agreement, Joint Implementation Agreement, Interoperability Testing, Disclosure of Technical Interface and Implementation Guidelines) Some Medium to Small Size Carriers Cannot Afford Large Computer Systems To Support Existing B2B Gateways Additional Expenses for Large Carriers to Provide Browser/GUI and FAX Services

3. 4/22/20033 How To Lower the Entry Barrier Utilize Ubiquitous and Proven Technology – XML Web Services – That Operates on Both Small (PCs) and Large Platforms Provide a Comprehensive E-Business Model to Establish and Maintain Business Relationship Leverage a Single OSS Gateway to Enable OSS Interconnections with Consistent File Format, Transport Protocol, and Support Reduce Cost and Cycle Time

4. 4/22/20034 What is XML Web Services Technology? Web Services Are IP Based Internet Tools that Facilitate B2B Business Transactions Definition from “Web Services Essentials”, published by O’Reilly & Associates, Inc. –A web service is any service that: Is available over the Internet or private (intranet) networks Uses a standardized XML messaging system Is not tied to any one operating system or programming language Is self-describing via a common XML grammar Is discoverable via a simple find mechanism

5. 4/22/20035 Why XML Web Services? Utilize Ubiquitous IP Based Networks, i.e., Internet and Intranet Operate on Small (PCs) and Large Platforms Supported by Major Standard Organizations – W3C, OASIS, IETF, ANSI ASC X12,.. Tools Are Widely Available – Open Source, Open Architecture Leverage Your Corporate Investments on XML Web Services A Potential Solution to the Data Interchange Initiative

6. 4/22/20036 Web Services Tools Are Widely Available Service Transport –Transport business transactions using HyperText Transfer Protocol (HTTP or HTTPS) XML Messaging –Format business transactions using XML –Validate business transactions using XML Schema –Envelope business transaction, control header and security header using Simple Object Access Protocol (SOAP) –Transform XML to Application Data using Extensible Stylesheet Language Transformations (XSLT) Service Description –Disclose public interface using Web Services Description Language (WSDL) Service Discovery –Provide a common registry to easily publish/find web services using Universal Description, Discovery, and Integration (UDDI)

7. 4/22/20037 A “Mail Order” Analogy To Web Services Tools Mail Order ModelWeb Services Model Browse Mail Order Classified Advertising – newspapers, magazines, yellow pages Service Discovery - UDDI Select Products/Services from CatalogService Description - WSDL Place Order – Envelope, Order Forms, Mail Carrier XML Messaging – SOAP envelope, XML Document, HTTP(S) Process Order - Fulfill order using local procedure Send order data to OSS. Use XSLT to transform XML data to application data Confirm Order – Envelope, Order confirmation letter or shipping notice, Mail Carrier XML Messaging – SOAP envelope, XML Document, HTTP(S)

8. 4/22/20038 Why XML Web Services is a Potential Solution to The Data Interchange Initiative? The Evolution Has Begun –Industry is moving towards XML: –tML Framework Approved –Access Ordering UOM using tML –Trouble Administration using tML –DSL Provisioning using tML –tML Transport Profile Specifications under review Complete The Evolution With A Plan –Create a Comprehensive E-business Model –Support Work In Progress tML Activities – Migrate Other Work Activities To tML

9. 4/22/20039 Create a Comprehensive ebusiness Model Learn from existing ebusiness models: ebXML UDDI Develop a model to support a wide spectrum of business activities, ranging from simple file transfers to complex business transactions Facilitate the Establishment of B2B Business Relationship by Streamlining/Automating the following processes: Interconnection Agreement Joint Implementation Agreement Disclosure of Technical Interface Specifications and Implementation Guidelines Interoperability Testing

10. 4/22/200310 Support Work In Progress tML Activities UOM Access Ordering tML/XML Design and Analysis XML Schema Interface for Trouble Administration (Trial-Use Standard) tML Transport Profile Specifications

11. 4/22/200311 Migrate Other Work Activities To tML Local Service Ordering (LSOG) Billing Provisioning

12. 4/22/200312 Reduce Cost Leverage Existing XML Web Services Investments To Develop tML Gateway Replace Multiple OSS Gateways With A Single tML Web Services Gateway Consolidate Gateway Support and Help Desk Functions Competitive Software Products May Be Available: Large Carrier may not have to provide proprietary GUI or Fax solution to Small Carriers Small Carriers may enjoy better integration with their own systems/PCs

13. 4/22/200313 Reduce Cycle Time E-business Model Streamlines The Establishment and Maintenance of Business Relationship Less Effort To Define tML Schemas (for ASOG, LSOG, etc) Than EDI Mapping Guides (ELMS) or Other Data Models Reduce Development Cycle Compared to EDI