the new parlay group current status n.
Skip this Video
Loading SlideShow in 5 Seconds..
The New Parlay Group Current Status PowerPoint Presentation
Download Presentation
The New Parlay Group Current Status

The New Parlay Group Current Status

126 Vues Download Presentation
Télécharger la présentation

The New Parlay Group Current Status

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. The New Parlay GroupCurrent Status January 9-11, 2001 Grand Hyatt Hotel Scotts Road Singapore Zygmunt Lozinski Vice President, The Parlay Group 20010108 Parlay Status Z.A.Lozinski.ppt

  2. Parlay is growing Parlay Group Triples Membership Since June Interest Grows with JAIN, 3GPP and OMG Liaison Activities Date of release Nov. 2, 2000 San Ramon, CA, USA, November 2, 2000 - The Parlay Group announced today that membership has tripled since their June member meeting as a result of continuing interest in the Parlay APIs and a strengthening liaison with the JAIN™, 3GPP and OMG organizations. Recent additions to the Parlay membership include Aepona, Alcatel, Appium, Compaq Computers, CSELT, France Telecom, Fujitsu, Hewlett-Packard, Intel, Kabira Technologies, Logica, NEC, Net4Call, Nokia Networks Oy, SBC TRI, SS8 Networks, Sun Microsystems, Telcordia Technologies, Tundo Communications and Westwave Communications. More than 105 attendees from 45 companies were represented at the Parlay Group’s Fall 2000 Member Meeting held in Stockholm, Sweden, September 27-28, 2000.

  3. Organization • The new Parlay group is growing rapidly • incorporated as a not-for-profit organization in June 2000 • 40members (as of Jan 2001) • Close linkages and liason established with related groups • 3GPP, JAIN, OMG, PAM Forum • There has been widespread interest in the new Parlay Group

  4. Liason: JAIN and Parlay Margaret Nilson will be speaking on Tue 9 Jan, at 10:30 in Hibiscus Room

  5. Liason: Charging Contributions Parlay 3GPP Lucent(#302) Siemens(#319) SiemensFunctionalDescription LS (#348) Ericsson API Specification Parlay-LS ConsolidatedSpecifications 3GPP Scottsdale Parlay Singapore 3GPP Helsinki

  6. Geographic Distribution of Member Companies Source: Parlay Group membership, Jan 2001

  7. Aepona Alcatel Appium Technologies AT&T BT Cisco Systems Compaq Computers CSELT Ericsson France Telecom Fujitsu Limited GMD FOKUS Hewlett-Packard IBM Incomit AB Intel Kabira Technologies Logica Lucent Technologies MAERSK IT AS Marconi Communications Microsoft NEC Corporation Net4Call Nokia Networks Oy NTT Open Telecommunications Oxygen Technologies S.E.S.A. AG SBC Technology Resources Inc. Septier Communication Ltd. Siemens AG SS8 Networks, Inc. Sun Microsystems Tecnomen Telecommunications Telcordia Technologies Telenor AS Tundo Communications Ulticom, Inc. Westwave Communications The Parlay Group • Membership Includes the Following Companies

  8. The Next Gen Service Space IP Wireless Fixed Acceptance of Parlay • We are starting to see PARLAY acceptance in the industry. • The members of the Parlay Group are reporting: • RFIs, bids and RFPs are now asking for Parlay-based solutions • Parlay is being incorporated in the roadmaps and product plans of telecommunications suppliers • Network operators are conducting beta-tests of Parlay solutions in the network • North America, Europe and Asia Pacific • AT&T Trial, Eurescom P909 • There are a number of venture capital backed companies in The White Space. • Parlay education is becoming available • Now is a good time for Parlay applications

  9. Analyst interest in Parlay Topic: The Promise of Open APIs in Carrier Networks: Will It Really Work? Executive Summary Over the past year, The Yankee Group has mapped out the overall trends we see in carrier- converged infrastructure. Our research on the three-tiered architecture differentiated the packet infrastructure, or bearer channel, layer from the call control layer and the open application layer. In prior research we discussed elements in the bearer channel such as ATM switches and carrier convergence packet switches. We also addressed the open call control layer in a Report covering softswitching technologies and vendors. For the most part, service providers and vendors have been in agreement about the tools and technology involved in communicating between the packet infrastructure layer and the open call control layer. Although each product has its unique interpretation and execution of those technologies, there is industry agreement on the overarching issues. For example, the packet infrastructure layer will speak to the call control layer using a set of protocols such as Q.931, Media Gateway Control Protocol (MGCP), and Megaco. Session Initiated Protocol (SIP) is also gaining momentum as a user-to-networkbased protocol for delivering services down to the customer site. But what about the application development layer and its connection to the underlying technology? The application programming interface (API) for converged carrier networks is clearly in a state of flux. Despite the proliferation of proprietary APIs from an extensive array of vendors and their partnership programs, The Yankee Group believes that vendors will eventually settle into a quasi-standard that will take advantage of the best of what the vendors have to offer. The JAIN and Parlay sets of APIs are among the first to emerge that hold the promise of this simplified, collaborative development environment. Exhibit 1 illustrates the softswitch-based network, and the placement of the open APIs within the three-tiered architecture. Source: The Yankee Group, 2000 Volume #: 1 Issue #: 7 Date:September 26, 2000

  10. Activities • New Parlay Web Site is now online • New working groups have been chartered by the Parlay Board • Call Control • Content Based Charging • Policy Management • Framework • Presence and Availability Management • Realization & Developer • Additional working groups are in the process of forming • User Profile Data • Mobile E-Commerce

  11. Working Groups • Approved Working Groups • Call Control AT&T/BT • Includes Mobility Mgmt and User Interaction API Enhancements • Content Based Charging Siemens • Policy Management Lucent/Cisco • Presence and Availability Management Lucent • Framework Lucent • Developer Realization IBM • Proposed Working Groups • User Profile Data ? • Mobile E-Commerce Ericsson • Working Groups to be Created • Messaging In addition, there is a Technical Advisory Committee, TAC. Only the Full Members can become the chairs of the WGs.

  12. Framework Working Group Objectives: • To maintain and enhance the Parlay Framework APIs used by service objects and client applications • Updates from Parlay 2.1 • Security, Interoperability, Completeness Leaders: • Andy Bennett, Lucent Chartered: 7 Dec 2000 Deliverables: • updated FrameworkAPI specification as part of Parlay 3.0 release • Framework-specific Policy API definitions • Framework API collateral

  13. Call Control Working Group Objectives: • To define Parlay Call Control API to enable services for the real-time multimedia (audio, video, and/or data) applications independent of platforms and networks Leaders: • Radhika Roy, AT&T & Richard Stretch, BT Chartered: 5 Sep 2000 Deliverables: • Comments on CC API 2.1 • Call Control API specification as part of Parlay 3.0 release

  14. Policy Management Working Group Objectives: • Define Parlay Policy Management APIs, to Manage Policy Domains within the Network. • Independent of Network Architectures • Independent of Transport/Application Protocols Leaders: • Shehryar Qutub, Lucent Technologies • Peter Heitman, Cisco Systems Chartered: 5 Sep 2000 Deliverables: • Policy Management API Specifications • Use Cases • Working White Paper

  15. Content Based Charging Working Group Objectives: • Allow the network operators to generate additional revenue, e.g. from their subscriber base or by share revenues • Standardize API’s that open up operator’s charging and billing processes towards 3rd parties (application providers). • Allow 3rd party application providers to take advantage of the large subscriber base and well-established business relationship between network operators and their subscribers and from existing billing infrastructure • Leaders: Chartered: 5 Sep 2000 Deliverables: • A Conceptual Document (White Paper) • A Functional Description of each API to be standardized by WG

  16. Presence & Availability Working Group Objectives: • Define Parlay Presence and Availability management APIs to export and to manage presence information in the network and policy or preference based availability of users. • Independent of Network Architectures • Independent of Transport/Application Protocols • Coordinate with PAMforum ( to promote a single and consistent standard • Leaders: • Guda Venkatesh, Lucent Technologies Chartered: Oct 2000 Deliverables: • Presence and Availability Management API Specifications • Develop Use Cases illustrating application of Presence and Availability Management Classes.

  17. PARLAY Realization and Developer Working Group Objectives: • To encourage the use of PARLAY. • To encourage software developers to use the Parlay APIs to create cool apps. • To help the end-user community understand the valuePARLAY given them. • To help network operators to deploy cool applications using the PARLAY APIs. • To encourage platform providers to support the PARLAY APIs as a base for ISVs and operators. Leaders: • Zygmunt Lozinski, IBM Charter: yes Deliverables: • Parlay Interoperability & Conformance Tests • PARLAY technical & marketing white papers • “How-to “

  18. Thank You! The Parlay Group, Inc. 2694 Bishop Drive, Suite 275 San Ramon, CA 94583, USA Phone: +1.925.277.8110 Fax: +1.925.277.8111 Contact: Paul Ritchie, Executive Director,