1 / 25

WAP Forum: Update, Organization, & Call for Action January 18, 2000 presentation to 3GPP2 TSG-S

WAP Forum: Update, Organization, & Call for Action January 18, 2000 presentation to 3GPP2 TSG-S. Intro: WML/HDML content exploding. Examples:. Columbia Pictures movie site Audio Trailer Movie description Theatres and showtimes WML: mobile.sonypictures.com Amazon.com

cala
Télécharger la présentation

WAP Forum: Update, Organization, & Call for Action January 18, 2000 presentation to 3GPP2 TSG-S

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. WAP Forum: Update, Organization, & Call for Action January 18, 2000 presentation to 3GPP2 TSG-S IDO Corporation

  2. Intro: WML/HDML content exploding. Examples: • Columbia Pictures movie site • Audio Trailer • Movie description • Theatres and showtimes • WML: mobile.sonypictures.com • Amazon.com • Purchase from WAP phone • Ameritrade • Stock trading from WAP phone • Traffic Station, Inc. • Personalized realtime traffic information • ETC, ETC, ETC IDO Corporation

  3. Deployed Microbrowser MarkUp Languages:HDML/WML content CLEAR global leader • HDML/WML • N. America (many carriers, much content) • Europe (many carriers, much content) • Asia (Japan, Korea, Australia, etc) • C-HTML • NTT Docomo only (and unresolved IPR issues) • MML • Japan Telecom only • Microsoft HTML for microbrowser • British Telecom? IDO Corporation

  4. ML compare: Developer Perspective • There is virtually no difference to rendering content between MLs • For an HTML-experienced developer, • Learning how to use each of the described MLs is easy and equal (one day). • Rendering content in each of the described MLs equal in terms of skill and time required. IDO Corporation

  5. Note on HTML content and microbrowsers • NO technology allows all “Regular” HTML content to be satisfactorily rendered on handset display • methods for making content microbrowser-ready: • write in microbrowser-oriented ML • use dynamic converter or filter (eg HTML-to-WML) • BUT, the “Regular” HTML content being accessed need be aware of converter • Examples: Spyglass Prism; Oracle Portal-on-the-Go IDO Corporation

  6. WAP Forum PRIMARY GOAL bring together companies from all segments of the wireless industry value chain to ensure product interoperability and growth of wireless market. IDO Corporation

  7. WAP Forum Membership • Two Classes • (1) Full member (Cxrs & Large vendors) • (2) Associate member (mainly content developers) • Members • Full members: • Ex: Carriers: +40 (7 CDMA, 29 GSM, 5 PDC, 4 TDMA, 1 iDEN) • Ex: Mastercard, Visa, Schwab, Sony • Associate members: 820 and growing fast • Ex: Amazon.com, 724 Solutions IDO Corporation

  8. WAP Forum: Organization IDO Corporation

  9. Specifications Evolution • 1998: v1.0 • did not meet carrier needs • 99Jun: v1.1 • mainly fixed problems in v1.0 • commercially deployed • 99Dec: v1.2 • 00Jun: v1.3 • may include Multimedia and Provisioning • 00Dec: v1.4 ? V2.0 (2.5G/3G)? IDO Corporation

  10. WAP Meetings • General Meeting held 5 times yearly • Global locations • One week duration • Individual group meetings concurrent • Last meeting: Dec 99 (Australia) • Individual WAP Groups hold meetings between General Meetings • F2F and Teleconference IDO Corporation

  11. WAP General Meetings in 2000 • Feb 7 - 11 (Rome, Italy) • Apr 2 - 7 (Miami, FL, USA) • Jun 18-23 (Beverly Hills, CA, USA) • Sep 10-15 (Hong Kong) • Dec 10-15 (Munich, Germany) IDO Corporation

  12. 99Dec (Sydney) Meeting Update. Hot Topic 1: Interoperability (a) • Carriers (CEG) push for greater stress • “Top Task” for 2000 • WAP v1.1 “Certification” Process essentially complete • WAP certification = use of WAP Logo • WAP trademark usage guidelines looser • Anyone(WAP member or not) can submit Interoperability-related questions to IOT-Questions@mail.wapforum.org IDO Corporation

  13. Sydney Update. Hot Topic 1: Interoperability (b) IDO Corporation

  14. Sydney Update. Hot Topic 2 (for CDMA):Sprint PCS paper:WAP over CDMA • Doubts about how well WAP will function over CDMA QNC and packet • Sprint PCS presentation to WPG requested that problem be addressed • Bottom Line: OK to request, but need to commit resources to address problem IDO Corporation

  15. Sydney Update. Hot Topic 3:Future WAP Architecture • NTT Docomo / Ericsson propose guidelines and schedule for high-bw (2.5G/3G) WAP specs • Propose completion by end 2000 • Propose architecture be set by Feb (Rome) meeting • Plan to work closely with 3GPP and W3C • “what is 3GPP2??” IDO Corporation

  16. Hold Workshop during WAP meeting Workshop outputs “Activity Proposal” Spec Com approves establishment of new Expert Group EG drafts charter, which is approved by Board Work commences Liaison with external bodies Work with WAP Technical WGs 99Feb: Docomo and Nokia hold Multimedia Workshop (Ft. Worth) “Activity Proposal” and “Charter” (same document) generated 99Apr: 1st MM Expert Group meeting (Montreux) Joint work with W3C 99Jun: 2nd MMEG meeting (San Fran) relationship with 3GPP commences Starting a new WAP activity: Process and Example (Multimedia Expert Group) IDO Corporation

  17. Starting a new WAP activity: another method (Future WAP Architecure) • 99Dec: Docomo (and Ericsson) hold Workshop (Sydney) • WAP for high bandwidth (but applicable to 2G networks) • Stated Goals (from presentation): • Convergence with wireless-adapted IETF and W3C specs • Maintain service continuity and scalability across 2G and 3G mobile networks for WAP services • Proposed Schedule: • Dec99- Feb00: Architecture, protocols, security, multimedia • Feb00- Sep00: Detailed specification work and drafting • Oct00- Dec00: Public review & voting • Proposed Liaisons: • 3GPP, ETSI, W3C • Proposed Organization: • new “NG” subgroups in WAP WGs (eg WAG-NG, WPG-NG) IDO Corporation

  18. WAP Work / Ext Group Liaisons Possibility WAP specifications may not function optimally in 3GPP2-related networks IDO Corporation

  19. Ex: Active Liaisons • W3C • convergence of WML with XML • location-related specifications • future WAP architecture (new) • ETSI • MOU to cooperate signed at Telecom ‘99 (Oct) • 3GPP • Multimedia Specifications development workload split • same people attend 3GPP and WAP WGs IDO Corporation

  20. Liaison Ex: 3GPP/WAP joint Multimedia work Technical Working WAP Outside Groups Forum WAP Forum Architecture Working Group NOKIA Chair: Multimedia Expert Group (MMEG) 3GPP1 Liaison: NOKIA Co-chairs: NOKIA Apps Protocols Docomo (WPG) ( WAG ) Multimedia Multimedia Presentation Encapsulation Drafting Com (DC) Drafting Com (DC) • Nokia 3GPP/MMEG Liaison is Working Level • Motorola is top-level 3GPP/WAP Liaison • MMEG coordinates interfaces between 3GPP and WAP WGs IDO Corporation

  21. 3GPP2-related activities in WAP Forum • Many WAP WGs have put out calls for cdmaOne expertise. (almost no response) • MMEG has not, focussing exclusively on 3GPP • WAP Carriers (CEG) output Position Statement supporting WAP Multimedia in Jan. Urged contact with both 3GPPs. • IDO drafted LS to 3GPP2 from MMEG and put on 18-19Jan MMEG meeting agenda. • IDO representative attending (Finland) IDO Corporation

  22. General Recommendation to TSG-S / 3GPP2: Establish Formal Relationship with WAP Forum • Send Liaison Letter to WAP Board and Specifications Committee • Propose relationship between 3GPP2 and WAP Forum • Goals of relationship: • Share development effort in overlapping work areas • Avoid developing divergent solutions • Avoid duplication of effort • Recruit Active Liaison person (preferably vendor) IDO Corporation

  23. Specific Recommendation to TSG-S / 3GPP2: Establish Working Relationships with WAP Multimedia Expert Group • Send Liaison Letter to MMEG, Specifications Committee, and Board. • Propose to share information on Multimedia work • Welcome 3GPP participation in such work • Recruit Active Liaison person (preferably vendor) • Review 3GPP Stage 1 - 3 Multimedia documents. • Identify areas that may conflict with 3GPP2 work • Prepare input to WAP Forum based on this review • If necessary, modify 3GPP2 structure • to ensure effective cooperation on specific work items, such as Multimedia IDO Corporation

  24. Summary • WML content is exploding, representing a huge opportunity • Like it or not, WAP is the defacto standard • WAP Forum is working closely with W3C, ETSI, 3GPP • 3GPP2 is MIA. WAP thus may not work well with 3GPP2 technology networks • Call for Action: 3GPP2 liaison actively with WAP Forum IDO Corporation

  25. Thank You IDO Corporation

More Related