IDO Corporation

WAP Forum:Update, Organization, & Call for Action

January 18, 2000 presentation to 3GPP2 TSG-S

IDO Corporation

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

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

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

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

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

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

WAP Forum: Organization

Board of D irectors& CEO

Arch itectureW orking G roup

Specifica tionsC om m ittee

Spec R equ irem entsC om m ittee

A pps

(W AG )In terop

(W IG )P rotoco ls

(W PG )Telephony

A pps (W TA )M ultim edia

(M M E G )C arrier(C E G )

B illing(B E G )

S m art C ard(S C E G )

Telem atics(TE G )

S M S(S M S E G )

A s ian(A E G )

M arketing(M C E G )

- P ush- U ser A gent P ro file- JA V A- M ultim edia- W A G N G

- P rov is ion ing (O TA )- E 2E S ecurity- (W P G N G )

- (W IG N G )

O versees fu ture W A Pfeature prioritiza tion

- E nsures spec cons is tency- R esolves techn ica l issues

- P ro jec t M anagem ent- O versees LIa isons- Appointed by Board m em bers

Technical Working Groups: Create SpecificationsExpert Groups; represent specitic interests

Often work directly with external groups (EX: MMEG and 3GPP1)

D evelopers(W D E G )

13 board m em bers- 4 perm anent (vendors)- 9 e lected (6 carriers , 3 vendors)

IDO Corporation

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

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

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

99Dec (Sydney) Meeting Update. Hot Topic 1: Interoperability (a)

• Carriers (CEG) push for greater stress• “Top Task” for 2000• WAP v1.1 “Certification” Process essentia

lly complete– WAP certification = use of WAP Logo– WAP trademark usage guidelines looser

• AnyoneAnyone (WAP member or not) can submit Interoperability-related questions to IOT-Questions@mail.wapforum.org

IDO Corporation

Sydney Update. Hot Topic 1: Interoperability (b)

InteroperabilityIssue

Important toCarriers

WIG Focus(InteroperabilityGroup)

WAP Forumactivity

FaultyImplementation X X WIG

WAP InteropWorking Group

SpecAmbiguities X X WIGGaps inSpecifications X Input Papers

(members)

InconstentContentRenderingAcross Devices

X- “Generic Authoring Guidelines”- Correct in future versions

BackwardCompatibility X Expected as

specs mature

IDO Corporation

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

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) meetin

g– Plan to work closely with 3GPP and W3C

• “what is 3GPP2??”

IDO Corporation

Starting a new WAP activity: Process and Example (Multimedia Expert Group)

1 Hold Workshop during WAP meeting

2 Workshop outputs “Activity Proposal”

3 Spec Com approves establishment of new Expert Group

4 EG drafts charter, which is approved by Board

5 Work commences– Liaison with external bodi

es

– 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 co

mmences

IDO Corporation

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

WAP Work / Ext Group LiaisonsOrganizations etc

Non-cdmaOne cdmaOneFeature / Item W3C 3GPP/

ETSI/SERG

Non-cdmaOnecarriers /vendors

3GPP2/TIA/CDG

cdmaOnecarriers /vendors

Multimedia X X XSecurity X XProvisioning X XSmart Card X XBilling XPush XUA Profile X XTelematics X XFuture WAPArchitecture

X X X

XML/WMLconvergence

X X

WTA X X X

Possibility WAP specifications may not function optimally in 3GPP2-related networks

IDO Corporation

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 s

plit– same people attend 3GPP and WAP WGs

IDO Corporation

Liaison Ex: 3GPP/WAP joint Multimedia work

ArchitectureWorking GroupChair: NOKIA Multimedia

Expert Group(MMEG)

Co-chairs:NOKIA

DocomoApps

( WAG )Protocols

(WPG)

3GPP1

MultimediaPresentation

Drafting Com (DC)

MultimediaEncapsulation

Drafting Com (DC)

Liaison: NOKIA

WAPForum

OutsideWAP Forum

Technical WorkingGroups

• Nokia 3GPP/MMEG Liaison is Working Level• Motorola is top-level 3GPP/WAP Liaison• MMEG coordinates interfaces between 3GPP and WAP WGs

IDO Corporation

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

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

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

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 we

ll with 3GPP2 technology networks• Call for Action: 3GPP2 liaison actively wit

h WAP Forum

IDO Corporation

Thank You