Nokia SERIES 30 Developer's Manual
WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser FORUM NOKIA Version 1.1; Ju ne 09, 2003 Browsing
Forum.Nokia.com Contents 1 Introduction ................................................................................................................................................ 7 1.1 Chapter Topics ................................................................................................................. ..........................7 2 Guidelines for Design.......................................................................................................... ...................... 8 2.1 Applications fo r Mobile Use.................................................................................................... ...............8 2.2 Validating WML ................................................................................................................. ........................8 2.3 GPRS Usab ility ................................................................................................................. ...........................8 2.3.1 No changes required by deve lopers ...................................................................................8 2.3.2 Cache utilization .............................................................................................................. ..........8 2.3.3 Usabilit y tips ................................................................................................................. ..............8 2.3.4 Infrastructure optimiza tion ...................................................................................................9 2.4 Site Orga nization .............................................................................................................. ........................9 2.4.1 Doormat pages.................................................................................................................. .........9 2.4.2 Login .......................................................................................................................... ....................9 2.4.3 Detecting th e browser .......................................................................................................... ...9 2.4.4 Optimizing for size............................................................................................................ ........9 2.4.5 The first screen ............................................................................................................... ......... 10 2.5 Pictures an d Tabl es ............................................................................................................ ................... 10 2.6 Efficient Na vigation ........................................................................................................... ................... 10 2.7 Search ......................................................................................................................... ............................... 10 2.8 Titles and El ement Labels ...................................................................................................... ............. 10 2.9 Error Messages an d Confirmations ............................................................................................... ... 11 2.10 A Usability Test ............................................................................................................... ........................ 11 3 Introduction to the User Interface ............................................................................................. ......... 12 3.1 Nokia Phones with 96 x 65 Pixel Screen Resolution.................................................................. 12 3.2 User Interface Hardware â Keys and Display ................................................................................ 12 3.2.1 Two Soft Ke y Display ............................................................................................................. 12 3.2.2 Keys in Two Soft Ke y User Inte rface ................................................................................. 13 3.3 Display Fonts .................................................................................................................. ......................... 13 3.4 Accessing the WAP Browser...................................................................................................... ......... 13 3.5 Navigation, Labe ls, and Titles ................................................................................................. .......... 13 3.6 Scrolling ...................................................................................................................... .............................. 14 3.7 Picture Viewer ................................................................................................................. ....................... 14 3.8 Cache ......................................................................................................................................................... 14 4 WML Elements for the Nokia User Interface ..................................................................................... 15 4.1 Text Form atting ................................................................................................................ ..................... 15 4.1.1 Paragraph and cont ent alignment ................................................................................... 15 WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 2
Forum.Nokia.com 4.1.2 Line break ..................................................................................................................... ............ 15 4.1.3 Fieldset element ............................................................................................................... ...... 16 4.1.4 Pre el ement .................................................................................................................... .......... 16 4.2 Table .......................................................................................................................... ................................ 16 4.3 Images ......................................................................................................................... ............................. 17 4.3.1 Animated GIF ................................................................................................................... ........ 18 4.4 Links .......................................................................................................................... ................................. 18 4.5 Do Element ..................................................................................................................... ......................... 18 4.5.1 Prev task ...................................................................................................................... .............. 19 4.5.2 Cardwide and deck wide scope .......................................................................................... 19 4.6 WML Input Processing ........................................................................................................... .............. 20 4.6.1 Input el ements ................................................................................................................. ....... 20 4.6.2 Direct inpu t access ............................................................................................................ ..... 21 4.6.3 Select element ................................................................................................................. ........ 21 5 Additional WAP 1.2.1 features .................................................................................................. ........... 23 5.1 Push ........................................................................................................................... ................................ 23 5.1.1 Service inbox .................................................................................................................. .......... 23 5.1.2 Service In dication ............................................................................................................. ...... 23 5.2 Wireless Telephony Applications Inte rface (WTAI) Publ ic Library ........................................ 24 5.2.1 Making a ph one call............................................................................................................ ... 24 5.2.2 Incoming call wh ile browsing............................................................................................ 24 5.2.3 Sending DT MF tone .............................................................................................................. .. 24 5.2.4 Adding a phone book entry ................................................................................................ 25 5.3 Cookies ...................................................................................................................................................... 25 5.4 Accessk ey ...................................................................................................................... ........................... 25 5.5 Content Download over WAP ...................................................................................................... ...... 25 5.6 Segmentation and Re assembly (SAR)............................................................................................. 2 6 6 Terms and Abbreviations ........................................................................................................ .............. 27 7 References ..................................................................................................................... ............................ 29 Appendix A. Wireless Applicat ion Protocol (WAP) ................................................................................ .. 30 Introduc tion ................................................................................................................... ........................................ 30 WAP Archit ecture .................................................................................................................................................. 30 WAP and Internet architecture .................................................................................................. ....... 30 Wireless Application En vironment (WAE)...................................................................................... 31 Wireless Session Pr otocol (WSP) ................................................................................................ ...... 31 Wireless Transport Protocol (WTP).............................................................................................. .... 31 Wireless Transport Laye r Security (WTLS) ..................................................................................... 31 Developing Applications for Mobile Browsing.................................................................................... ........ 31 WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 3
Forum.Nokia.com Additional In formation ......................................................................................................... ............................. 32 WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 4
Forum.Nokia.com Change History 04 Nov 2002 V1.0 Initial document release. 09 June 2003 V1.1 Template changed, Noki a 3510i and Nokia 8910 i information removed. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 5
Forum.Nokia.com Disclaimer The information in this document is provided âÂÂas is,â with no warranties whatsoever, including any warranty of merchantability, fitness for any particular purpose, or any warranty otherwise arising out of a ny proposal, specification, or sample. Furthermore, information provided i n this document is preliminary, and may be changed substantially prior to final release. This docume nt is provided for informational purposes only. Nokia Corporation disclaims all liability, includ ing liabilit y for infringement of any proprietary rights, relating to implementation of information presen ted in this document. Nokia Corporat ion does not w arrant or represent that such use will not inf ringe such rights. Nokia Corporation re tains the right to make c hanges to this specification at any time, without notice. The phone UI images shown in this document are for illustra tive purposes and do not re present any real device . Copyright é 2003 Nokia Co rporation. Nokia and Nokia Connecting People are regist ered trademarks of Nokia Corporation. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. Other product and company names ment ioned herein may be trademarks or trade names of their respective owners. License A license is hereby granted to downlo ad and print a copy of this specific ation for personal use only. No other license to any other intellectual pr operty rights is granted here in. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 6
Forum.Nokia.com WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser Version 1.1; Ju ne 09, 2003 1 Introduction The following document provides info rmation and pr actical examples for dev elopers who want to optimize their WAP services for Nokia Series 30 devices with a WML browse r. It is written for service developers as well as anyone involve d in creating the wireless information society who needs to know more about service creation on mobile t erminals. This guide is not intended to describe WAP in detail, nor is it meant to replace an y WAP specification. 1.1 Chapter Topics Chapter 2 of this document describes several ge neral usability issues concerning WAP service development. Chapter 3 intr oduces the browser's user interface elements, keys, display, an d browsing conventions. Chapter 4 outlines some general WML elements that are man datory features for WAP 1.2.1, according to the W AP Forum specifications. Ch apter 5 introduces addit ional WAP 1.2.1 features that are supported in Nokia Series 30 pho nes. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 7
Forum.Nokia.com 2 Guidelines for Design The Nokia Series 30 UI is des igned to be easy to use and intuitive. The following section off ers general g u i d e l i n e s t o h e l p d e v e l o p e r s c r e a t e b r o w s i n g a p p l i c a t i o n s t h a t w i l l b e p e r c e i v e d a s u s a b l e a n d e a s y to understand . 2.1 Applications for Mobile Use When deciding what information to include in vari ou s applications on a mobile terminal, developers should consider the types of situations where th e mobile phone will be used. The content of the service should fulfill the needs of the target user group and be optimized fo r the most common tasks. Because of the mobility of the small display, the use r might primarily use the mobile phone when there is no PC access to the Internet, and for quick information. Exam ples might include speedy access to flight schedules, short news flashes, and access to weather infor mation or checking the temperature at a travelerâÂÂs destination. It is less l i kely that users will use their mobile phones to surf. 2.2 Validating WML There are several XML validators availa ble that validate documents against WML Docu ment Type Definition. It is recommended th at authors vali date their WAP pages, because inv alid WML is always treated as an erro r and disc arded (that is, it is not shown to the user). Several XML validators c an be found at ht tp://www.wapdevelopers.org/. 2.3 GPRS Usability GPRS enables efficient us e of resources, instant acce ss, fast delivery of information, and innovative charging models. 2.3.1 No changes re quired by dev elopers Since the WAP standard was designed to allow content to be delivere d over any bearer service, it is not necessary for develope rs to make changes to thei r WAP services or application s. This is true even when delivery of th e services is en abled over GPRS, 3G, or any other n etworks. 2.3.2 Cache utilization Developers should use HTTP pro xy to cache WML content whenever the content is accessed through the Internet. The proxy should be pl aced close to the WAP gateway to minimize the dist ance for data transfer between the two components. T he home page (first page) can alternatively be kept on a local server, close to the WAP gateway. Most clients have a cache; using it is a good way to imp rove the user's experience. Cache headers should be sent with documents to ensure that page s are cached on the client if possible. Content developers should n ot assume that pages are cache d by default. 2.3.3 Usability tips Round trips in the network add a minimum two-second delay to the response time. Th erefore the number of round trips should be minim ized. The resp onse time of a first page h as a strong impact on the user experience, so it is worth optimizing. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 8
Forum.Nokia.com 2.3.4 Infrastructure optimization The latency between the WAP gatew ay and content server should be minimized. Each query traverses this link twice, once as a request and once as a response. The WAP gateway should be pl aced close to the GPRS gateway. (The GPRS gateway is technically calle d a â G a t e w a y G P R S S u p p o r t N o d e , â o r G G S N . ) â C l o s e â i n t h i s i n s t a n c e r e f e r s t o b o t h l a t e n c y a n d t h e probability of packet loss. L ost messages cause additional delays due to HTTP retransmission. 2.4 Site Organization 2.4.1 Doormat pages It is not recommended to start the site using a doormat page, which se rves no other purpose than to perhaps greet the vis i tor and display a lo go. It is better if the user can go to the service directly. 2.4.2 Login Entering login informatio n can be time consuming with a mobile phone. Login information should be requested only once during the session, not each time after starting navigation from the main page. Case-sensitive checking of user name s an d passwords should be avoided. 2.4.3 Detecting the browser When using a modern Web site hosting enviro nment, it is possible to detect the browser as well as the language mode and supply the correct content t ransparently, without user interaction. The Nokia Series 30 mobile browser sends a user agent field in the WSP header to the WAP gateway when the content is fetched from the origin server. Th is user agent field can be used to define the type of browser and then build a logic on the origin server to serve suitable content. From the WAP gateway, it is then delivered insi de the HTTP he ader. 2.4.4 Optimizing for s ize Interactive pages should be short; informative pa ges, long. Having pages that are too short an d require many downloads is worse th an having close-knit information on one longe r page. In particular, interactive pages with forms should not be too long, as users start to lose their feel ing of control if the form is more than two screenfuls. Empty rows can be mislead ing, as users may think there i s no more cont ent belo w. If, for example, a page con tains a story or instru ctions, the entire content should be on on e page. Subtitles that take the user to points within a page help when browsing long, informative pa ges. It is di ff ic ul t t o giv e ha rd a nd f ast gu idel ine s a bou t ho w many links should be provided on one link list page. If the links clearly belong together and are easy t o b r o w s e ( o n e l i n e p e r l i n k , i n a l p h a b e t i c a l o r other logical order), it is better to provide 30 links on one page than 5 links on six pages. As for the total downlo ading time, some studies place an upp er limit for acceptable delay on a PC- based browser at 10 to 15 s econds, including all images. It is highly recommen ded to have a resp onse time (excludin g connection time) of less than 10 seco nds in a mobile environment. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 9
Forum.Nokia.com 2.4.5 The first screen The first (topmost) screenful of any page is the most important. All often-us ed navigation al links, search fields, login screens, and the bulk of the informat ion should reside there. The user can then navigate forward before the rest of the page h as been loaded, an d will not have to scroll the page. Wasting the top of the page o n banner advertis ements or non-informativ e graphics should be avoided. It is better to place advertisements at the left or right edge. 2.5 Pictures and Tables Downloading images takes time, an d many users ma y opt to switch off the loading of images for more speed. Authors should try to optimize image size . If there are l arge pictures on the site, authors should consider using thum bnails for the image index. Color images should be te sted for visibility on a monochrome display. Usu ally, the same image cannot be used for color and mo nochrome displays. An alternative text (usin g the alt attribute of the <img> element) should be provided for images that convey information. A null alte rnative text (alt=âÂÂâÂÂ) should b e used for images that do not convey information, or th at are used fo r page layout or decorative purposes only. The table width or height should not exceed the sc ree n size, since scrolling will make the table less readable (e.g., column t itles are not visible after scrolling down). 2.6 Efficient Navigation The service provider must be responsible for naviga tion as a whole. A consistent navigation met hod should be provided within the service. Each page sh ould contain links to the main page of the site and to the possible subsection main pages. The back function can also be provided as a link on the page, but should not be used, for example, on pages th at will r eturn th e user to a purchasing or confirmation page. If access keys are used, their definitio ns should be co nsistent fo r the main page link s, e.g., âÂÂ1â always takes the user to the main page of the service. 2.7 Search A piece of information in the service can be found by movin g ahead in a tree hie rarchy or by conducting a search. Ideally, both methods should be provide d. The tree hierarchy helps the first-time user clarify the serv ice structure, but it may be too slo w for an experie nced user. Search results should be optimized to include only a few items; if m ore are found, the user should have the opportunity to narrow the search criteria. 2.8 Titles and Element Labels The title describes the contents of the display. Use of titles is reco mmended in WML. Titles help the user navigate in the application be cause they remind th e user where s/he is within the application. It may be a good idea to start the title wit h the serviceâÂÂs name and keep the tot al length of the title short. The item previously selected by t he user should determine the header text. For instance, the title âÂÂBookmarksâ tells the user th at the display co ntains a list of bookmark s in the applicat ion and that the options item previously selected was Bookmarks. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 10
Forum.Nokia.com Proportional fonts are used in header text, an d if the header text is too long, it is cut automatically. Cut titles are usually better than abbreviations, be cause the user may be confused by unf amiliar abbrevia tions. Although short words are re commended for element l abels, acronyms that are not well known by the target user group should be avoided. The same la bel should alw ays be used for the same thing, especially with funct ion labels such as D elete, Remove, Erase, Cle ar, and Destroy. 2.9 Error Messages and Confirmations It is especially irritating for users to recei ve error mess ages and be asked to correct the input. Servic es should be very flexible when interpreting inp ut, e.g., allowing several diffe rent formats for date and time. If an error message must be sho wn, it should be helpful and pol ite, explaining why the act ion could not be executed, and providing an easy way to correct the situ ation. After the user has chosen a comman d that will carry out an action such as destroying information or moving money, it is essent ial to provide a confirma tion page before executing the action. It s hould also be easy for the user to check the effects of the action. For example, when deleting an ite m, it is best to first ask for confirmation and then inform the user t hat the deletion was executed successfully. 2.10 A Usability Test It is always good to perform a usability test for new applications. People who have not been involved in the design or development of an appl ication tend to notice potential usability problems that are often not obvious to those who know the des ign by heart. Usability tests should always be performed as early as possible in the development process. Any necessary changes resultin g from the tests can then be implemented w ithin the development timetabl e. Testers who are representat ive of the future end users should be used. At the least, tests should be conducted on a small scale if the schedule does not allow for extensive testing. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 11
Forum.Nokia.com 3 Introduction to the User Interface The followi ng chapt er offers a brief ov erview of t he user inte rface sty le in 96 x 65 pixe l screen resolution phones. The m ain focus is on the W AP services element (W AP browser) of the phone. The WAP browser user interface is designed to comply with the user interaction handling known from other applications in the phone. The user interface style is a combi nation of specifi c user inte rface hardware such as keys and display; user interaction conventions, which include input an d output functions and thei r relationsh ips; and the audio-visual appe arance, which is used in the user interaction conven tions. This chapter concentrates on the hardware pa rt of the 96 x 65 pixel resolution user interface. 3.1 Nokia Phones with 96 x 65 Pixel Screen Resolution Nokia Series 30 phones have a WAP bro wser with enha nced features and increased usability. Predictive text input (T9) can be used in the WAP bro wser; predictive text input in WAP and a picture viewer are also supported. Nokia Series 30 phones support Push service in dication; in addition most of the June 2000 conformance (WAP 1.2.1) pho nes support WTAI public library and cookies â . For more detailed information, see the WAP characteris tics table at http://forum.nokia.com. Nokia 3410 Nokia 3510 Nokia 6310 Nokia 6310i Nokia 6510 WAP 1.1 Push WAP 1.2.1 WAP 1.2.1 WAP 1.2.1 WAP1.2.1 GSM900/1 80 0 GSM900/1 80 0 GSM900/1 80 0 GSM900/1 80 0/1900 GSM900/1 80 0 CSD CSD, GPRS CSD, GPRS CSD, GPRS CSD, GPRS Two soft key UI Two soft key UI Two soft key UI Two soft key UI Two soft key UI 3.2 User Interface Hardware â Keys and Display 3.2.1 Two Soft Key Displ ay The display is a full dot-ma trix display with a displ ay resolution of 96 pixels (horizontal) by 65 pixels (vertical). The display consists of t he application area, header area, and an area used for the soft keys. â Excluding Nokia 3410 WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 12
Forum.Nokia.com Figure 1: Struct ure of the browser screen The applicat ion area is 96 pixels (horizontal) b y 45 pixels (ver tical). It includes four lines of main text and can also b e used for display i ng graphics, whic h can be scrolle d four ways (pictu re viewer) until the maximum deck size. 3.2.2 Keys in Two Soft Key Use r Interface The Send/Talk key works as a select ion key. The End key exits a data call/GRPS connection an d goes into idle state when pressed twice. The two soft keys are assign ed actions that en able the user to manipulate the user interf ace by making selections and enterin g, editing, an d deleting text. I n Nokia 68xx there is also a third soft key, which is used only as profile key. -The left soft key is use d as a yes/positive k ey. It contains opt ions that execute commands an d go deeper into the menu structure. Some exam ple functions are Select, OK, and Options. -The right soft key is used as a no/negative key. It contains o p tions that can cel commands, delete text, an d go backwards in the menu structu re, such as Back, Ex it, and Clear. The scroll keys (arrow keys) allow the use r to scroll the options or te xt in the current displ ay. 3.3 Display Fonts All fonts are proportional font s. Proportional fon ts give a dyn amic and minimize d width for each characte r, improve re adability of the display texts, and g enerally allow mor e characters to be displayed per line. On the othe r hand, having pro portional fonts means that it is difficult to tell how many characte rs there can b e in each line, e.g., compare characters âÂÂWâ an d âÂÂi.â 3.4 Accessing the WAP Browser The browser is accessed by selecting Services from the menu and entering a home page define d for the currently active settings or a bookmark. For quick access to the browser, the user can make a long key press on the 0 key; t he user is then taken to the home page th at is defined fo r the currently activ e settings set. The access point and home page can be set in the Serv ices -> Settings menu. 3.5 Navigation, Labels, and Titles The user should b e provided with cons istent card headers, ele ment titles and do-element labels. The title of a <select> element is used in the header of a sel ection list or option groups list. The title of an <optgroup > element is used as an option group title and in the header of its selection l ist. The title of WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 13
Forum.Nokia.com an input elem ent is used in the e d itor title. The label of a do element is used in the Service option s behind the Options soft key. 3.6 Scrolling The user can move u p and down in a card view when it contai ns elements (hotlin ks, input elements, and selection list items) and static text areas between the m. This is done by âÂÂjumpingâ fro m element to element. Scrol ling through long static sect ions (that is, t ext lines) is done line by line. The first element of a card is h ighlighted by default if it is on the first displ ay. 3.7 Picture Viewer The picture viewer lets user s perform horizontal and vertical scrolling of pict ures /anim ation s that a re too wide/high for the displ ay. The picture viewer ca n on ly be activated by sele cting the options lis t item View Picture if the currently active page conta ins at least one p icture/animat ion. In the pict ure viewer , picture s/anima tions ar e display ed simil arly to the way pict ures/a nimati ons are disp layed in the browser display except that only one picture/animation can be viewed at a t ime. 3.8 Cache The browser places viewed cards in cache, which allows previously visi ted cards to be quickly accessed, as there is no need to reload them. T he cards stay in cache u ntil it is manually cleared by the user or until the memory is full. See the Nokia WAP Phone Characteristics document for information on cache size in different Nokia WAP phones. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 14
Forum.Nokia.com 4 WML Elements for the Nokia User Interface This chapter s erves as a gui de for using WML in designing services. It provides an overview of graphical user interf ace elements, that is, th e WML ele ments that are critical f rom the rendering point of view and their WML capabilities supported by t he browser. The docum ent does not include all possible WML elements and attributes. WAP service developers s hould pay special attention to Sections 4.2: T able and 4.3: Im ages. The WML elements are b riefly described and demonstr ated with screenshots. Code examples include only the essential part related to using the ele ments, i.e., the document prologue is not shown after Example 1. 4.1 Text Formatting The contents of a WML card are displayed in the Application area of the display (see Figures 4.1 and 4.2). The card is a container of text, images, tables, and input elements. Th e order of elements in a card is signific ant, as they appear on t he screen in the same order. 4.1.1 Paragraph and content alignment The paragraph element, p, enables word wr apping and content alignment. A paragraph always starts on a ne w line. Norm al static text information is alw ays wrapped on a d isplay, unless word wrapping is set off in the browser settings. Insigni ficant whi te space i s ignored. If more than on e white spac e separa tes the consti tuents of a text, these white spaces are ignored unless th e pre element is us ed. See Section 4.1. 4 for more information o n the pre element. The content inside a paragraph can be aligned to the left, center, or right by option; left alignment is displayed by default. Alignment is determined in par agraph attributes ( for example, <p align="right ">). Word wrapping can be set to wrap or nowrap by using the mode attribute in paragrap h. <p align="center"> Align "center" </p> <p align="right"> Align "right" </p> <p align="right"> <img alt="3510i" src="file://C:/USERS/wml/3510i.gif" align="top" hspace="0" vspace="0"/> </p> Example 1: Alignment <align> 4.1.2 Line break New lines in text can be defined by a line break. The line break eleme nt, br , can be used inside other elements as well, as long as it belongs to a paragraph. If a line break is defined after an a element, the line b reak is ignored. If an empty line is needed betwe en two links, it is necessary to add two line breaks between the a elements. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 15
Forum.Nokia.com 4.1.3 Fieldset element The fieldset element allows the groupin g of related fields and text. The b asic idea of group ing is to show the grouped items on the same displa y if possible. If the items cannot be displayed on the same display, the user is not given any no tification. Fieldset always starts a new line and ends with a line break. 4.1.4 Pre element The pre element is supported. When the pre element is used, the content shown is rendered as âÂÂpreformattedâ to the extent possible. This implies that white spac e is left intact when render ed, that the font in the cards remain s the same as for plain t ext in a card, and t hat word wrapping is enabled/dis abled according to how the browser is set. 4.2 Table The <table> element is used together with the <tr> and <td> ele ments to create set s of rows and columns of data, such as text, images, and so on. It is po ssible to have text, images, and tables on the same card. The cells are sho w n in bordered rows an d columns. The size of the cells is dynamic, according to th e cont ent of the cells. The widest cells affect the width of the other cells in the same column. There is a minimum cell width of 10 pixels in order for the columns to re main discernible. The width of the rows w ill be adapted so that all can fit. When more cells are define d than can be on the screen, the cells will all be of the defined minimum width. When the content of the cel ls is too large to fit the cell, its content is truncated and three dots ar e added. A maximum of one text, image, or link element can be shown in each cell when n o row in the table has bee n selected. Otherwise text, image, as well as link el ements can be sho wn in a cell. In a text element, if line breaks are defin ed, several lines can b e shown at a t ime. When no ro w has been selected, the longest line in a ce ll defines the width of the cell if the cell can be shown in full width. Otherwise lines of excessive length a re truncated an d three dots a re added. The full content of each cell c an be viewed by scrolling. The title of the table is s hown when a row is selected. If the table has no title, the title of the card in whi ch the ta ble is situa ted is u sed as a tit le for the tab le. <table align="LCC" columns="3"> <tr> <td>Date</td> <td>F'cast</td> <td>T ðC</td> </tr> <tr> <td> <anchor title="date">M 6/7 <go href="#date" method="get" sendreferer="false"/> </anchor> </td> <td> <anchor> <img alt="rain"src="file://â¦/rainy.wbmp" align="bottom"/> <go href="#descr" method="get" sendreferer="false"/> </anchor> </td> <td>25ðC</td> </tr> <tr> <td>T 6/8</td> WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 16
Forum.Nokia.com <td> <img alt="part cldy" src="file://â¦/partcldy.wbmp" align="bottom"/> </td> <td>27ðC</td> </tr> <tr> <td>W 6/9</td> <td> <img alt="cloudy" src="file://â¦/cloudy.wbmp" align="bottom"/> </td> <td>24ðC</td> </tr> <tr> <td>T 6/10</td> <td> <img alt="rainy" src="file://â¦/rainy.wbmp" align="bottom"/> </td> <td>28ðC</td> </tr> <tr> <td>F 6/11</td> <td> <img alt="sunny" src="sunny.wbmp" align="bottom"/> </td> <td>29ðC</td> </tr> </table> Example 2: Table element 4.3 Images The graphics form ats Wireless Bitmap (wbmp), stati c gif (.gif 87a), and animat ed gif (.gif 89a) are supported . The static gr aphics area is at maximum 78 pixels wide and 30 pixels high, but vertically and horizontally scrollable until the maximum deck size. Ho wever, the animate d gif graphics area is a t maximum 78 pixe ls wide and 30 pixels high. Ima ges fitting in t he graphics area are centered unless specified otherwise by the service provider. St atic images that are too wide are leftâ aligned and tr uncated on the r ight. Images tha t are too long are topâÂÂaligne d but scrollable down. The displaying of images is optional and can be turne d off in the bro wser appearance settings. Images can al so be used inside a table and as a link (se e Example 4.2 above). An image th at functions as a link is represented with a full-line frame around it. Images appear in a separate line than text. Figure 2: Image in Nokia 6310 Image sizes of a maximum of one line, that is, 10 pixels high, may be shown with two lines of text on the same display above and/or below the image. Similarly, with an image of a maximum of 20 pixels there can be one li ne of text.. There cannot be text next to an image; the image wi ll always start its own line. If a requested image does not ex ist, a small default picture will be sho wn. Use of the image alt attribute value is recommended. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 17
Forum.Nokia.com 4.3.1 Animated GIF Most recent Nokia browsers 1 support ima ge format animate d gif (.gif 8 9a). The maximum number of frames allowed is 13 (not e, maximum file size is 2.4 kb). The animatio n can be viewed in the browser vie w. After running th e animation i n looping mode for 50 loops the animation will stop . The last frame of the an imation will be shown as a static gif. 4.4 Links The anchored link ele ment specifies a hotl ink. Links are underline d; in Nokia 3510i links are displayed and underline d in blue. An activ e link is shown in inverse colors. When a user selects a link, the associ ated task is pe rformed. When th e link is active, the options list of the browser display is extende d with the option Select. The user can also select a link by press ing the Send key. Figure 3: Selected link is highlighted The a element is a short form of the anch or element, and is boun d to a go task wi thout variables. In general it is recommended to use the a element instead of the anchor where possible, to allow mo re efficient tokenization. A hotlink is automat ically followed by a line break. If a line break is defined after an a el ement, the line break is ignore d. If an empty line is neede d between two links, it is necessary to add two line breaks between t he a elements. If a hotlink does not hav e a title or label, t he URL address of the link is displayed in its full le ngth, and functions as a normal hotlink. <anchor>text<go href="#card2"/> </anchor> <anchor> <img alt="golf" src="file://â¦/golf.wbmp"/> <go href="#card2"/> </anchor> Example 3: Image as a link 4.5 Do Element The do element provides a general mech anism for the user to act upon the current card. The do elements are mapped behind the b rowserôs options list togeth er with the preloa ded options. If a do element contains a prev task, the right soft key is labeled "Back." Use of a prev task is highly recom mended in every card because it e nables backward navigatio n. Do elements have a label, i.e., the text of the item in the br owserâÂÂs options list. If th e label is available it is used as an op tion list item. If there is no label, a default text is displayed, according to T able 4.1 below. However, it is highly recommended to use the label att ribute. 1 All phones that are in troduced in this documen t support gif image formats in the WAP browser. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 18
Forum.Nokia.com Type Static text Accept OK Prev Back Help Help Reset Reset Options Options Delete Erase Unknown Unknown Table 1: do elements label default text 4.5.1 Prev task The author of the WAP service is always respon sible for the working n avigation model inside its own service. If there is a need for back functi onal ity, it should be explicitly def ined with the prev type do element. Th e WAP browser does not have any implicit b ack functionality. 4.5.2 Ca rdwide and d eckwide scope The do element c an be expressed in two ways: in c ardwide scope or in deckwide s cope in template. Do elements will be stored in the browserâÂÂs options list together with the preloaded options. <template> <do type="prev" label="Back"> <prev/> </do> </template> Example 4: Deckwide bac kward navigation, prev <do type="prev" label="Back" <prev/> </do> Example 5: Cardwide back ward navigation WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 19
Forum.Nokia.com <wml> <template> <do name="help-button" type="options" label="Ask Help"> <go href="http://.../help.wml" method="get"/> </do> <do type="options" label="Contact"> <go href="http://.../contact.wml" method="get" sendreferer="false"/> </do> <do type="prev" optional="false"> <prev/> </do> </template> <card id="card1" title="Homepage" ordered="true"> <p align="left"> Please, register <br/> Username: <input name="username" type="text" title="Username" emptyok="false"/> Password: <input name="password" type="password" title="Password" emptyok="false"/> <do type="accept" label="Enter"> <go href="#confirm" method="get" sendreferer="false"/> </do> </p> </card> <card id="confirm" title="Confirmation" ordered="true" newcontext="false"> <p align="left"> $(username), thank you for registering. </p> </card> </wml> Example 6: Do element 4.6 WML Input Processing Input processing lets the us er input reques ted information to the serv ice. There are two kin ds of input elements: t ext fields determined by an input element and selection lists determined by a select element. Option elements are used to specify a single choice option in a select element. Option elements can be grouped by using an optgroup element (se e Example 4.9). 4.6.1 Input elements The input element, which is displayed with brackets, specif ies a character entry object. By selecting the input element, the use r evokes the editor. The e ditor is never displaye d directly in the card view. The options list of the browser display is then ex tended with the "Edit" option. T he T9 option is enabled in the browser. Th e user can select the input element by pressing the Send key. The in put element consists of a title, brackets, and a value. There can be a default value inside the brackets. The title of the element is o nly displayed when the e ditor box is displayed, which is after h aving selected the input element. Th e value with the brackets is al ways wrapped to the next line. If the value cannot fit into one line, the end of the content is truncated and three dots are added. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 20
Forum.Nokia.com 4.6.2 Direct input access The user can also select the input element by pressing any numeric key when the e dit box appears and t he pressed key is al ready placed in the ed it box, i.e., the user c an just start inputting characters an d the edit box appears automatically. When T9 (predictive text input) is act ivated, the sof t keys are "Options" and "Back" when the editor is empty. Otherwise the soft keys are "Options" and "Clear ." This also appl ies if T9 is deactiv ated. Input fields can be specif ied by the in put element's type an d format attributes. <template> <do type="previous" label="Back" optional="false"> <prev/> </do> </template> <card id="card1" title="Homepage"> <p align="left"> Please, register <br/> Username: <input name="username" type="text" title="Username"/> Password: <input name="password" type="password" title="Password"/> <do type="accept" label="Enter" optional="false"> <go href="#confirm" method="get" sendreferer="false"/> </do> </p> </card> <card id="confirm" title="Confirmation" ordered="true"> <p align="left"> $(username), thank you for registering. </p> </card> </wml> Example 7: Text input <input> 4.6.3 Select element Selection lists are elements that s pecify a list of options for th e user to choose from. There are two kinds of selection l ists supported: single-c hoice and multip le-choice l ists. The user can select multiple choice, if the multiple attribute is set as true (sel ected items are marke d with a selection symbol). The user can h ighlight and se lect the selection list item on a card. The options list of the browser display is extend e d with "Select." The user can also select the selection list by pr essing the Send key. That same ite m will be highligh ted and displ ayed with a selected ico n in front of it once the user re-e nte rs th e list during the same browsing session. A selection list item on a card looks similar to an input element item; it consists of a title, brackets, and a v alue. There is always a default value inside the brackets in a singl e selection list (in a multi-selection list there are by default three dots between the brackets u nless specified othe rwise by the s ervice provide r). If there are no options in the selection list, three dots are displ ayed between the brackets. The title is not displ a yed in the card itself. The value with the brackets is al ways wrapped to th e ne xt line, w hich means that t here will never be text and a valu e with brackets on the same line. If the value cannot fit onto one line, the remaini ng part of the con tent is tru ncated a nd replac ed with thre e dots. The title of the selection list is the first item of the card containing the selection list . If the value is a valu e of a multi-selection, the selections are separated with commas. If the value cannot fit into one l ine, the end of the co ntent is truncated an d replaced with three dots. The WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 21
Forum.Nokia.com user can view the v alue between brackets in full by pressing the # key. Until the # key is released, the content that can fit on the screen is viewed. The soft keys are hidden while t he content is viewed in full. The layout in f ull view is th e same as the on e selected by the use r for browsing. The option element specifies a single choice option in a sele ct element. Options can be grouped with an optgroup element, which specifies a grou p of choice items in a select element. An optgroup element is dis played with an icon in front of the t itle of the optgroup element. An optgroup elem ent can be used in single selection lists as well as multiple selection lists. Only in multiple selection lists it is possible to have option groups that allow multiple selections. <wml> <card id="phones" title="Information Request"> <p align="left"> Send me more information about: <select name="models" title="Products" multiple="true"> <optgroup title="Phones"> <option value="Nokia 7650"> 7650 </option> <option value="Nokia 9210"> 9210 </option> <option value="Nokia 6310"> 6310 </option> </optgroup> <optgroup title="Accessories"> <option value="Battery"> Battery </option> <option value="Desktop stand"> Desktop stand </option> <option value="Charger"> Charger </option> <option value="Headset"> Headset </option> </optgroup> </select> Please, provide your <br/> Name: <input name="name" type="text" title="Name" emptyok="false"/> </p> <do type="accept" label="Confirm" optional="false"> <go href="#confirm" method="get" sendreferer="false"/> </do> <do type="prev" optional="false"> <prev/> </do> </card> </wml> Example 8: Select and optgroup WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 22
Forum.Nokia.com 5 Additional WAP 1.2.1 features 5.1 Push Nokia Series 30 phone is abl e to receive Push Se rvic e Indication (SI) type serv ice messages. Push service messages are an ideal way for service providers to activate users, sinc e they can be used to notify users of updated content or to alert them about information in their are as of interest (e.g., new e-m ails, changes in sto ck prices, flight schedule change s or news headlines ). Se rvice messages indicate downloadable content. The user can view indicate d content by using the Se rvice Inbox and the WAP browser. 5.1.1 Service inbox The service provider can p ush a Service Indicat ion message to the ph one, which is then saved to the Service Inbox in the Services menu. The user can view indicated conte nt afterwards by using the Service Inbox. In the Service Inbox, the received service messages can be viewed, deleted, downloaded, or moved to another folder. Users can define in the Service message se ttings whether to re ceive service messages or not. Servic e messages are sorted in th e Service In box into the fol lowing ord er: 1. All unread Service Indications appear hi ghest on the list and are gr ouped ac cording t o the applied priority level, starting with âÂÂsignal-high, â then âÂÂsignal-medium,â and finally âÂÂsignal-lowâ (see Section 5.1.2 for more info rmation about the priority lev els). The messages in each group are shown in chronological orde r according to the rece iving time. 2. All read service mess a ges appear below unread service messages and are shown in chronological order according to wh en the Service Indications were created. 5.1.2 Service Indication At the least, a Service Indic ation should contain te xt that is displayed to the user and a U RL addre ss of content that may be dynamically generate d for each push message in the application serve r. The Service Indication can contain the following information: ⢠Text ⢠URL address ⢠Creation date ⢠Creation time ⢠Expiration date ⢠Expiration time Each Service Indication has a Service Indication ID, which is used to uniqu ely identify different k inds of Service Indications. Service providers s et the Serv ice Indication IDs for mess ages. The ID allows reception of multiple Service Indications with the same URL address and priority level. If the rec eived Service Indication has the same ID as the one stored in memory, the received Se rvice Indication will replace the stored one only if it is n ewer. Servic e providers ca n determine t he priori ty level of the message. Priority levels are signal-high, signal- medium, signal-low, signal-none, and del ete. Prio rity level defi nes how th e received messages are WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 23
Forum.Nokia.com ordered in the Service Inbox and also whether the user is notified abou t received Service Indicat ion. The defined priority level has the following impact: ⢠signal-high: Notification with an SMS alert tone is presented. ⢠signal-medium: Notification with an SMS alert tone is presented. ⢠signal-low: No indication of received Service In dicati on is displayed to the user. The Service Indication is silently stored in the Service Inbox. ⢠signal-none: Service Indication is automatically disc arded. The user is not notified. ⢠delete: If a Service Indic ation already exists, the Service Indication with the same I D in the Serv ice Inbox is deleted. If there is no Service Indication with t he same ID in the Service Inbox, the received Service Indic ation is discar ded. The user is not notified. ⢠If no attr ibute ha s been sp ecifi ed, Servi ce Indic ations w ill be rec eived as signal -medium . 5.2 Wireless Telephony Applications Interface (WTAI) Public Library The WAP browser suppo rts three Wireless Telephony Applications Interface (WTAI) public library functions: makin g a ca ll while browsing, s ending DTMF tones, and saving nu mbers and names to the phone book. These functions, MakeCall, SendDT MF, and AddPBEntry, can be used anywhere in the WML code in the same way as when URI or script ref erences are used fo r normal non-WTAI ref erences. 5.2.1 Making a phone call The MakeCall function is used for making a phone call directly f rom the WML browser application. A typical example of the usage of Ma keCall is when the user selects an anchored link, whic h initia tes a phone call . When a MakeCa ll functi on is execut ed, the user is asked to confirm that the dial-up is to be made. If the phone number th at is about to be call ed does not exist in the phone book, a confirmation query with the phone numbe r is displayed. If the number to be calle d exists in the phone b ook, a confirmation query is displayed with the name fetched fr om the phon e book. If the u ser accep ts making th e phone call , another c onfirma tion query is displaye d with text "Quit browsing?" If the user accepts both que ries, the browser sess ion will be terminated and the browser application will close down. The c all will then be i nitiated. When the call is ter minated, the phone is in idl e state. If the user rejects the latter conf irmation query, the call will be initiated from within the browser display and the user ca n b rowse cached content during the call. No in-call options such as Mute, Hold, etc., are acce ss ible from within the browser application. The options list belongin g to the browser display remains unaffected by the fact that a call is active. 5.2.2 Incoming call while bro wsing Normal call handlin g applies when a call is initiated f rom the browser part (e.g., th e called party is busy, call barring is enable d, etc.). 5.2.3 Sending DTMF tone The user can send DTMF tones through the net work by executing a WTAI function called SendDTMF. Just like MakeCall , a typical way of us ing SendDTMF is to assign the SendD TMF function to an an chored link. The user must hav e a voice call active. When the DTMF tone has WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 24
Forum.Nokia.com been sent, the user returns to the card/deck wh ere s/he initiated the sending. The voice ca ll remains active. 5.2.4 Adding a phone book entry The AddPBEntry functio n offers an easy w ay to store a phone nu mber and a corresponding name onto the phone book application fr om a WML card. The service provider provides the name and number. When t he user activates an AddPBEntry function and the service provider has declared a name an d a number, the phone displ ays a confirmation que ry with the text "Save name." W hen the user a ccepts the conf irmati on query , anoth er confirm ation qu ery wi th the text "With number 44 123 123 45 67" is disp layed and the number is stored in the phone book application. When saving is comple te, the currently active card is displayed again. Note that the user does not have to be onl ine or have any voice calls act ive in order t o use the AddPBEntry function. 5.3 Cookies Cookies enable the storage of data such as user in formation to ease browsing by reducing the amount of informat ion the user must enter . For exampl e, lo gin can be configure d dynamically so that it is displayed only if the application cann ot identify the user. Cookies in cached files are ignored. 5.4 Accesskey Service providers have the possibility of us ing the accesskey attribute of the a element an d the anchor element. This allows users to open links with a long press of the associated access keys. Keys allow ed for access ke y use are the 0 -9 number keys. The service provider should indicate to the user which keys to press in order to open the desired links; thi s can be accomplish ed by adding the label of the key to the link concerned, e. g., if the service pr ovider associates the âÂÂ2â key to a link, the service provider should add the number âÂÂ2â to the label of the link. < a accesskey="2" href="phone.wml">(2)a </a> Example 9: Using accesskey "2" Only one link can be associated wit h each access ke y. A key will also o pen its corresponding link if the service provider has ass igned it as an access key but does not indicate this to th e user. If the user tries to open a link by using a key that the service prov ider has not associated with any link, the key will not react to the action of the user. An access key h as an e ffect on a li nk even if the link i s not highlighted. The link chosen by the user is highlighte d after the corresponding access key has been given a lon g press. This is v isible while the terminal is fetching the content of the link. A long press of an access key also has an effect when a card contains bo th acce ss keys and a highlighted input element. An input element can be activate d by an associated access key through a long press in the same way as anchored links (des cribed above). 5.5 Content Download over WAP Content download is a technology that is used to deliver di gital content such as entertainm ent and business applications to mobile terminals. Another important application is for personalizi ng terminals according to a userâÂÂs preferences and l ifestyle. Content downloading can be initiated by an end u ser or by a network application. The content download mechanis m between the mobile termin al and content source is based on open technologies such as HTTP (and WSP) and J ava Community Process technology. This technology allows the creation of an ope n, multivendor market for te rminal vendors as w ell as for network server and broker vendors. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 25
Forum.Nokia.com For more information about content download, please go to h ttp://www.forum.nokia.com/ . 5.6 Segmentation and Reassembly (SAR) Some of the Series 30 phones support Segment ation and Reassembly (SAR) functionality, wh ich is an optional feature in the Wireless Transport Protocol (WTP) lay er defined by the WAP Forum. SAR is used to split large WTP messages into a number of sma ller datagrams and selectively retrans mit failed datagrams. The use of SAR improves over-the-air efficiency for downloading large messages to the phone and makes content downlo ad (e.g., Java MIDlet download) and MMS tr ansfer faster and more reliable. The use of SAR e nables t he transm ission of lar ge data fil es through WAP to the mobile phone . To use SAR, it must be supported by both of the communi cating parties, typically the WAP gateway and the WAP browser. WAP se rvice developers do not nee d to take any actio ns to enable SAR in their s ervice development. Even t hough phones suppor ting SAR allows do wnloading of large files, it s hould be noted that other elements in the network (W AP gateways) might restrict the downl oadable file sizes. Nokia WAP gateways let through files up to 100 KB b ut the limit might be small er than that in some gateways. Another factor to keep in min d is th at SAR can only be used in connection-oriented (permanent) mode. Further information about SAR funct ionality can be found in th e "Segmentation an d Reassembly in the Wireless Transaction Protocol" document, which is available at the Forum Nokia Web site, http://forum.nokia.com. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 26
Forum.Nokia.com 6 Terms and Abbreviations Card A single WML unit of navi gation and user interface. Deck A collection of WML cards th at is the smallest downloadable unit. You cannot download a single card in a deck; you m ust download the en tire deck. Serv ice developers should be aware of this, and n ot create large applications in a single dec k. Do element A way of defining the binding between ev ents (such as a user selection) an d a task (for e xample, to go somewhere). DTMF tone Standard tone used to transmit numeric data via telephone. Generated when numeric keys are pressed. GPRS General Packet Ra dio Service. Mob ile service that gives a packet switched access over GSM to external data networks wi th high pea k transfer ca pacity. GUI Graphical User Inte rface. HTML Hypertext Markup Language . The markup language used for publishing hypertext on the Worl d Wide Web. HTTP Hypertext Transfer Protocol . An application-level protocol for transferring HTML documents in the Internet. Hyperlink A link within a documen t or card that allo ws quick navigation to another document (card). Input element A markup element t hat allows for interaction with the user, that is, lettin g the user input te xtual values. These can be used f or inputs to lo cally stored scripts, or for parsing to origin serv ers. Multiselection list A selection list, which allows the user to scroll and sele ct several (or none) options to be active. Navigation The concept of moving between menu items, decks, and cards. Proportional font A font in which different let ter widths do not necessarily have the same number of pixels. "W" and "I" are good examples. SAR Segmentation and Re-assembly. A functionality used to split large WTP mess ages into a number of small er datagrams an d selectively retransmit fail ed datagrams. Selection list List of user-selectable options. Soft key The phone has one or more function keys whose function depends on th e state of the phone. Th ese keys are called soft keys because there is an associated text on the display. UI User Interface. URL Uniform Resource Locator. St ring that identifies resources in the Web. W3C World Wide Web Consortium. An organiz ation that develops interoperable technologies for Web. Word wrapping Formatting rule for text appear ance. WML Wireless Mark up Language. Markup language based on Extensible Marku p Lan g ua g e ( XML ) , which is intended for Term or Abbreviation De scription WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 27
Forum.Nokia.com use in specifying content and user interf ace for narrowband devices, including cellular phones and pagers. WSP Wireless Session Protocol. A layer of WAP stack, which is optimized for low bandwidt h bearer networks with long latency. WTAI Wireless Telephony Applic ations Interface. Feature th at provides the means to create telephony applications by using a WAE user-ag ent with the appr opriate WTAI function libraries. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 28
Forum.Nokia.com 7 References GPRS-related documentatio n http://www.mobilegprs.com Nokia Mobile Internet Toolk it 4.0 http://forum.nokia.com Nokia Phone User's Guides http://www.nokia.com Segmentation and Re-ass embly-related document ation http://forum.nokia.com WAP Push-related documentation http://forum.nokia.com Wireless application specificat ions http://www.openmobilealliance.org WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 29
Forum.Nokia.com Appendix A. Wireless Application Protocol (WAP) Introduction The Wireless Application Protocol (WAP) is a set o f protocols that allows the development of applications and services for use with mobile phones and other mobil e devices. The WAP Forum maintains these protocols and their re lated standa rds and spec ifications. The WAP Forum consists of a number of high-tech companies from the information technology, software, and telecommunication industries. The objectives of the WAP Forum are to: ⢠Bring I nternet content and advanced data appl ications to digital mobile phones ⢠Create a global wireless protocol specificatio n that works across di fferent wireless network technologies ⢠Enable the creation of con tent and applicatio ns that scale across a wide ran ge of bearer networks and device types ⢠Embrace existing standards and technology wherever possible WAP Architecture WAP and Internet ar chitecture In order to apply as much leverage to the existing Internet standard as poss ible, the WAP stack closely follows the Internet model. This is illustrated in Figu re 1A. Internet HTML JavaScript TM HTTP TLS - SSL TCP/IP UDP/IP SMS USSD CSD IS-136 CDMA CDPD PDC-P Etc.. Bearers: Wireless Application Wireless A pplication Environment (WAE) Wireless Session Layer (WSP) Wireless Tran sport Layer Sec urity (WTLS) Wireless Datagram Protocol (WDP) Other Services and Applications Wireless Tra nsaction Pr otocol (WTP) Figure 1A: Comparison of Inte rnet and WAP architecture This layered arc hitecture allows applicat ions to use the features of the WAP st ack through well- defined interfaces. This close link to the Interne t architecture allows developers to use their existing knowledge and expertise when develo ping applications for mobile terminals. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 30
Forum.Nokia.com Wireless Application Environment (WAE) The Wireless Application Environment (WAE) is a gene ral-purpose ap plication environment that uses a combination of Internet and mobile termin al technology. It prov ides a framework for the development of applicati ons on a mobile terminal. WAE contains sup port for the following functionality: ⢠Wireless Markup La nguag e (WML) - a li ghtweig ht pres entation langua ge, simi lar to Hyper text Markup Language (HTML) but optimized fo r use with mobile terminals. ⢠Wireless Markup Language Script (WMLS) - a lightweight script la nguage, similar to JavaScriptâ¢. ⢠Wireless Tele phony Application / Int erface (WTA / WT AI) - telephony services and programming interf aces. ⢠Content fo rmats - defined d ata formats, such as vCard and vC alendar. Wireless Session Protocol (WSP) The Wireless Session Protocol (WSP) pro vides the a pplication lay er of WAP with an interface f or two session services. The first is a connection-oriented service that operates abov e the transaction layer protocol. The second is a connectionless s ervice that operates above a secure or non-secure datagram service. The WSP is optimized for lo w bandwidth be arer networks with long latency. Wireless Transport Protocol (WTP) The Wireless Transport Protocol (WTP) runs on top of the datagram service an d provides a lightweight transaction-oriented proto col, suitable for use in mobile termin als. WTP operates over secure o r non- secure wireles s datagram networks. Wireless Transport Layer Security (WTLS) Wireless Transport Layer Security (WTLS) is based on the industry standard T ransport Layer Security (TLS) and is optimized for use over narrowband com munication channels. WTLS may be used for secure communicatio n between terminals, an d applications can sele ctively enable WTLS features . Developing Applications for Mobile Browsing Application develope rs can use the prin ciples of WAP to develop new services or ad apt existing Internet applicat ions for use with mob ile terminals. Appl ications are wr itten in Wireless Markup Language (WML) and WMLScript, an d stored on either a normal Web server (origin serv er) or directly on the WAP gateway. The content sto red on the Web s erver is accessible from mobi le terminals via the cellular network and a WAP gateway or proxy. The proxy server acts as a gateway between the cell ular network and the Internet or Intranet. The data sent between the origin serve r and the handset is binary en coded to optimize transmissio n over the narrow bandwidth of the cellular network. Not e that th e content st ored on th e Web ser ver mig ht be in either textual or binary format. When the WAP gateway fetches textual content, it automatically compiles this to the encoded fo rmat to minimize network load. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 31
Forum.Nokia.com Figure 2A shows the network-related elements require d for developing and offering services to mobile users. Wireless Netw ork WA P Proxy WT A Server Binar y Binary WML HTML Filte r WML WML HTML Web Server Figure 2A: Elements related to mobile browsing Web server The Web server stores the applications written in WM L. Alternatively, existing HTML applications can be used. HTML filter Any applications wr itten in HTML will hav e to be co nverted to WML b efore they are sent to the mobile terminal. This HTML filter may form part of the Web server o r the WAP proxy. WAP proxy The WAP proxy acts as the gateway between the cel lular network and the Internet or Intranet. It encodes the information, which is to be sent to the mobile terminal in binary format and decodes information sent f rom the mobile terminal. WTA server The WTA server handle s networ k-speci fic app licati o ns. These applications are no t discussed in this document. Additional Information Further infor mation on WAP is available at http://ww w.openmobilealliance.org/ . WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 32
Forum.Nokia.com Build Test Sell Developing and m arketing mobile a pplications with Nokia 1 Go to Forum.Nokia.com Forum.Nokia.com provides the tools an d resources you need for content and application development as well as the channels fo r sales to op erators, enterpris e s, and consumers. Forum.Nokia.com Download tools and emulators 2 Forum.Nokia.com/tools has links to tools from Noki a and other industry leaders including Bo rland, Adobe, AppForge, Macromed ia, Metrowerks, and Sun. Forum.Nokia.com/tools Get documents and specifications 3 The documents area co ntains useful white papers, FAQs, tutorials, an d APIs for Symbian OS an d Series 60 Platform, J2ME, messaging (including MMS), and oth er technologies. Forum.Nokia.com/devices lists detailed technical specifications for Nokia devices. Forum.Nokia.com/document s Forum.Nokia.com/devices Test your application and g et support 4 Forum Nokia offers free an d fee-based suppor t that pr ovides y ou with direct access to Nokia en gineers and eq uipment and c onnect s you wi th other devel o pers around the world. The Nokia OK testin g program enables your application to enjoy premium placement in Nokia's sales channels. Forum.Nokia.com/support Forum.Nokia.com/ok Market through Nokia channels 5 Go to Forum.Nokia.com/business to learn about all of the marketin g channels open to you, including Nokia Tradepoint, an online B2B ma rketplace. Forum.Nokia.com/business Reach buyers around the globe 6 Place your applicatio ns in Nokia Tradepoint and th ey're available to dozens of buying organiz ations around the world, ranging from leadin g global op erators and enterpris e s to regional operators and XSPs. Your company and appli cations will also be co nsidered for the regi onal Nokia Software Markets as well as other global and regional opportuni ties, including personal introductio ns to operators, on- device and in-box placement, and particip ation in invitation-only events around the world. Forum.Nokia.com/business WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 33
Forum.Nokia.com Contents 1 Introduction ................................................................................................................................................ 7 1.1 Chapter Topics ................................................................................................................. ..........................7 2 Guidelines for Design.......................................................................................................... ...................... 8 2.1 Applications fo r Mobile Use.................................................................................................... ...............8 2.2 Validating WML ................................................................................................................. ........................8 2.3 GPRS Usab ility ................................................................................................................. ...........................8 2.3.1 No changes required by deve lopers ...................................................................................8 2.3.2 Cache utilization .............................................................................................................. ..........8 2.3.3 Usabilit y tips ................................................................................................................. ..............8 2.3.4 Infrastructure optimiza tion ...................................................................................................9 2.4 Site Orga nization .............................................................................................................. ........................9 2.4.1 Doormat pages.................................................................................................................. .........9 2.4.2 Login .......................................................................................................................... ....................9 2.4.3 Detecting th e browser .......................................................................................................... ...9 2.4.4 Optimizing for size............................................................................................................ ........9 2.4.5 The first screen ............................................................................................................... ......... 10 2.5 Pictures an d Tabl es ............................................................................................................ ................... 10 2.6 Efficient Na vigation ........................................................................................................... ................... 10 2.7 Search ......................................................................................................................... ............................... 10 2.8 Titles and El ement Labels ...................................................................................................... ............. 10 2.9 Error Messages an d Confirmations ............................................................................................... ... 11 2.10 A Usability Test ............................................................................................................... ........................ 11 3 Introduction to the User Interface ............................................................................................. ......... 12 3.1 Nokia Phones with 96 x 65 Pixel Screen Resolution.................................................................. 12 3.2 User Interface Hardware â Keys and Display ................................................................................ 12 3.2.1 Two Soft Ke y Display ............................................................................................................. 12 3.2.2 Keys in Two Soft Ke y User Inte rface ................................................................................. 13 3.3 Display Fonts .................................................................................................................. ......................... 13 3.4 Accessing the WAP Browser...................................................................................................... ......... 13 3.5 Navigation, Labe ls, and Titles ................................................................................................. .......... 13 3.6 Scrolling ...................................................................................................................... .............................. 14 3.7 Picture Viewer ................................................................................................................. ....................... 14 3.8 Cache ......................................................................................................................................................... 14 4 WML Elements for the Nokia User Interface ..................................................................................... 15 4.1 Text Form atting ................................................................................................................ ..................... 15 4.1.1 Paragraph and cont ent alignment ................................................................................... 15 WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 2
Forum.Nokia.com 4.1.2 Line break ..................................................................................................................... ............ 15 4.1.3 Fieldset element ............................................................................................................... ...... 16 4.1.4 Pre el ement .................................................................................................................... .......... 16 4.2 Table .......................................................................................................................... ................................ 16 4.3 Images ......................................................................................................................... ............................. 17 4.3.1 Animated GIF ................................................................................................................... ........ 18 4.4 Links .......................................................................................................................... ................................. 18 4.5 Do Element ..................................................................................................................... ......................... 18 4.5.1 Prev task ...................................................................................................................... .............. 19 4.5.2 Cardwide and deck wide scope .......................................................................................... 19 4.6 WML Input Processing ........................................................................................................... .............. 20 4.6.1 Input el ements ................................................................................................................. ....... 20 4.6.2 Direct inpu t access ............................................................................................................ ..... 21 4.6.3 Select element ................................................................................................................. ........ 21 5 Additional WAP 1.2.1 features .................................................................................................. ........... 23 5.1 Push ........................................................................................................................... ................................ 23 5.1.1 Service inbox .................................................................................................................. .......... 23 5.1.2 Service In dication ............................................................................................................. ...... 23 5.2 Wireless Telephony Applications Inte rface (WTAI) Publ ic Library ........................................ 24 5.2.1 Making a ph one call............................................................................................................ ... 24 5.2.2 Incoming call wh ile browsing............................................................................................ 24 5.2.3 Sending DT MF tone .............................................................................................................. .. 24 5.2.4 Adding a phone book entry ................................................................................................ 25 5.3 Cookies ...................................................................................................................................................... 25 5.4 Accessk ey ...................................................................................................................... ........................... 25 5.5 Content Download over WAP ...................................................................................................... ...... 25 5.6 Segmentation and Re assembly (SAR)............................................................................................. 2 6 6 Terms and Abbreviations ........................................................................................................ .............. 27 7 References ..................................................................................................................... ............................ 29 Appendix A. Wireless Applicat ion Protocol (WAP) ................................................................................ .. 30 Introduc tion ................................................................................................................... ........................................ 30 WAP Archit ecture .................................................................................................................................................. 30 WAP and Internet architecture .................................................................................................. ....... 30 Wireless Application En vironment (WAE)...................................................................................... 31 Wireless Session Pr otocol (WSP) ................................................................................................ ...... 31 Wireless Transport Protocol (WTP).............................................................................................. .... 31 Wireless Transport Laye r Security (WTLS) ..................................................................................... 31 Developing Applications for Mobile Browsing.................................................................................... ........ 31 WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 3
Forum.Nokia.com Additional In formation ......................................................................................................... ............................. 32 WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 4
Forum.Nokia.com Change History 04 Nov 2002 V1.0 Initial document release. 09 June 2003 V1.1 Template changed, Noki a 3510i and Nokia 8910 i information removed. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 5
Forum.Nokia.com Disclaimer The information in this document is provided âÂÂas is,â with no warranties whatsoever, including any warranty of merchantability, fitness for any particular purpose, or any warranty otherwise arising out of a ny proposal, specification, or sample. Furthermore, information provided i n this document is preliminary, and may be changed substantially prior to final release. This docume nt is provided for informational purposes only. Nokia Corporation disclaims all liability, includ ing liabilit y for infringement of any proprietary rights, relating to implementation of information presen ted in this document. Nokia Corporat ion does not w arrant or represent that such use will not inf ringe such rights. Nokia Corporation re tains the right to make c hanges to this specification at any time, without notice. The phone UI images shown in this document are for illustra tive purposes and do not re present any real device . Copyright é 2003 Nokia Co rporation. Nokia and Nokia Connecting People are regist ered trademarks of Nokia Corporation. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. Other product and company names ment ioned herein may be trademarks or trade names of their respective owners. License A license is hereby granted to downlo ad and print a copy of this specific ation for personal use only. No other license to any other intellectual pr operty rights is granted here in. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 6
Forum.Nokia.com WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser Version 1.1; Ju ne 09, 2003 1 Introduction The following document provides info rmation and pr actical examples for dev elopers who want to optimize their WAP services for Nokia Series 30 devices with a WML browse r. It is written for service developers as well as anyone involve d in creating the wireless information society who needs to know more about service creation on mobile t erminals. This guide is not intended to describe WAP in detail, nor is it meant to replace an y WAP specification. 1.1 Chapter Topics Chapter 2 of this document describes several ge neral usability issues concerning WAP service development. Chapter 3 intr oduces the browser's user interface elements, keys, display, an d browsing conventions. Chapter 4 outlines some general WML elements that are man datory features for WAP 1.2.1, according to the W AP Forum specifications. Ch apter 5 introduces addit ional WAP 1.2.1 features that are supported in Nokia Series 30 pho nes. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 7
Forum.Nokia.com 2 Guidelines for Design The Nokia Series 30 UI is des igned to be easy to use and intuitive. The following section off ers general g u i d e l i n e s t o h e l p d e v e l o p e r s c r e a t e b r o w s i n g a p p l i c a t i o n s t h a t w i l l b e p e r c e i v e d a s u s a b l e a n d e a s y to understand . 2.1 Applications for Mobile Use When deciding what information to include in vari ou s applications on a mobile terminal, developers should consider the types of situations where th e mobile phone will be used. The content of the service should fulfill the needs of the target user group and be optimized fo r the most common tasks. Because of the mobility of the small display, the use r might primarily use the mobile phone when there is no PC access to the Internet, and for quick information. Exam ples might include speedy access to flight schedules, short news flashes, and access to weather infor mation or checking the temperature at a travelerâÂÂs destination. It is less l i kely that users will use their mobile phones to surf. 2.2 Validating WML There are several XML validators availa ble that validate documents against WML Docu ment Type Definition. It is recommended th at authors vali date their WAP pages, because inv alid WML is always treated as an erro r and disc arded (that is, it is not shown to the user). Several XML validators c an be found at ht tp://www.wapdevelopers.org/. 2.3 GPRS Usability GPRS enables efficient us e of resources, instant acce ss, fast delivery of information, and innovative charging models. 2.3.1 No changes re quired by dev elopers Since the WAP standard was designed to allow content to be delivere d over any bearer service, it is not necessary for develope rs to make changes to thei r WAP services or application s. This is true even when delivery of th e services is en abled over GPRS, 3G, or any other n etworks. 2.3.2 Cache utilization Developers should use HTTP pro xy to cache WML content whenever the content is accessed through the Internet. The proxy should be pl aced close to the WAP gateway to minimize the dist ance for data transfer between the two components. T he home page (first page) can alternatively be kept on a local server, close to the WAP gateway. Most clients have a cache; using it is a good way to imp rove the user's experience. Cache headers should be sent with documents to ensure that page s are cached on the client if possible. Content developers should n ot assume that pages are cache d by default. 2.3.3 Usability tips Round trips in the network add a minimum two-second delay to the response time. Th erefore the number of round trips should be minim ized. The resp onse time of a first page h as a strong impact on the user experience, so it is worth optimizing. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 8
Forum.Nokia.com 2.3.4 Infrastructure optimization The latency between the WAP gatew ay and content server should be minimized. Each query traverses this link twice, once as a request and once as a response. The WAP gateway should be pl aced close to the GPRS gateway. (The GPRS gateway is technically calle d a â G a t e w a y G P R S S u p p o r t N o d e , â o r G G S N . ) â C l o s e â i n t h i s i n s t a n c e r e f e r s t o b o t h l a t e n c y a n d t h e probability of packet loss. L ost messages cause additional delays due to HTTP retransmission. 2.4 Site Organization 2.4.1 Doormat pages It is not recommended to start the site using a doormat page, which se rves no other purpose than to perhaps greet the vis i tor and display a lo go. It is better if the user can go to the service directly. 2.4.2 Login Entering login informatio n can be time consuming with a mobile phone. Login information should be requested only once during the session, not each time after starting navigation from the main page. Case-sensitive checking of user name s an d passwords should be avoided. 2.4.3 Detecting the browser When using a modern Web site hosting enviro nment, it is possible to detect the browser as well as the language mode and supply the correct content t ransparently, without user interaction. The Nokia Series 30 mobile browser sends a user agent field in the WSP header to the WAP gateway when the content is fetched from the origin server. Th is user agent field can be used to define the type of browser and then build a logic on the origin server to serve suitable content. From the WAP gateway, it is then delivered insi de the HTTP he ader. 2.4.4 Optimizing for s ize Interactive pages should be short; informative pa ges, long. Having pages that are too short an d require many downloads is worse th an having close-knit information on one longe r page. In particular, interactive pages with forms should not be too long, as users start to lose their feel ing of control if the form is more than two screenfuls. Empty rows can be mislead ing, as users may think there i s no more cont ent belo w. If, for example, a page con tains a story or instru ctions, the entire content should be on on e page. Subtitles that take the user to points within a page help when browsing long, informative pa ges. It is di ff ic ul t t o giv e ha rd a nd f ast gu idel ine s a bou t ho w many links should be provided on one link list page. If the links clearly belong together and are easy t o b r o w s e ( o n e l i n e p e r l i n k , i n a l p h a b e t i c a l o r other logical order), it is better to provide 30 links on one page than 5 links on six pages. As for the total downlo ading time, some studies place an upp er limit for acceptable delay on a PC- based browser at 10 to 15 s econds, including all images. It is highly recommen ded to have a resp onse time (excludin g connection time) of less than 10 seco nds in a mobile environment. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 9
Forum.Nokia.com 2.4.5 The first screen The first (topmost) screenful of any page is the most important. All often-us ed navigation al links, search fields, login screens, and the bulk of the informat ion should reside there. The user can then navigate forward before the rest of the page h as been loaded, an d will not have to scroll the page. Wasting the top of the page o n banner advertis ements or non-informativ e graphics should be avoided. It is better to place advertisements at the left or right edge. 2.5 Pictures and Tables Downloading images takes time, an d many users ma y opt to switch off the loading of images for more speed. Authors should try to optimize image size . If there are l arge pictures on the site, authors should consider using thum bnails for the image index. Color images should be te sted for visibility on a monochrome display. Usu ally, the same image cannot be used for color and mo nochrome displays. An alternative text (usin g the alt attribute of the <img> element) should be provided for images that convey information. A null alte rnative text (alt=âÂÂâÂÂ) should b e used for images that do not convey information, or th at are used fo r page layout or decorative purposes only. The table width or height should not exceed the sc ree n size, since scrolling will make the table less readable (e.g., column t itles are not visible after scrolling down). 2.6 Efficient Navigation The service provider must be responsible for naviga tion as a whole. A consistent navigation met hod should be provided within the service. Each page sh ould contain links to the main page of the site and to the possible subsection main pages. The back function can also be provided as a link on the page, but should not be used, for example, on pages th at will r eturn th e user to a purchasing or confirmation page. If access keys are used, their definitio ns should be co nsistent fo r the main page link s, e.g., âÂÂ1â always takes the user to the main page of the service. 2.7 Search A piece of information in the service can be found by movin g ahead in a tree hie rarchy or by conducting a search. Ideally, both methods should be provide d. The tree hierarchy helps the first-time user clarify the serv ice structure, but it may be too slo w for an experie nced user. Search results should be optimized to include only a few items; if m ore are found, the user should have the opportunity to narrow the search criteria. 2.8 Titles and Element Labels The title describes the contents of the display. Use of titles is reco mmended in WML. Titles help the user navigate in the application be cause they remind th e user where s/he is within the application. It may be a good idea to start the title wit h the serviceâÂÂs name and keep the tot al length of the title short. The item previously selected by t he user should determine the header text. For instance, the title âÂÂBookmarksâ tells the user th at the display co ntains a list of bookmark s in the applicat ion and that the options item previously selected was Bookmarks. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 10
Forum.Nokia.com Proportional fonts are used in header text, an d if the header text is too long, it is cut automatically. Cut titles are usually better than abbreviations, be cause the user may be confused by unf amiliar abbrevia tions. Although short words are re commended for element l abels, acronyms that are not well known by the target user group should be avoided. The same la bel should alw ays be used for the same thing, especially with funct ion labels such as D elete, Remove, Erase, Cle ar, and Destroy. 2.9 Error Messages and Confirmations It is especially irritating for users to recei ve error mess ages and be asked to correct the input. Servic es should be very flexible when interpreting inp ut, e.g., allowing several diffe rent formats for date and time. If an error message must be sho wn, it should be helpful and pol ite, explaining why the act ion could not be executed, and providing an easy way to correct the situ ation. After the user has chosen a comman d that will carry out an action such as destroying information or moving money, it is essent ial to provide a confirma tion page before executing the action. It s hould also be easy for the user to check the effects of the action. For example, when deleting an ite m, it is best to first ask for confirmation and then inform the user t hat the deletion was executed successfully. 2.10 A Usability Test It is always good to perform a usability test for new applications. People who have not been involved in the design or development of an appl ication tend to notice potential usability problems that are often not obvious to those who know the des ign by heart. Usability tests should always be performed as early as possible in the development process. Any necessary changes resultin g from the tests can then be implemented w ithin the development timetabl e. Testers who are representat ive of the future end users should be used. At the least, tests should be conducted on a small scale if the schedule does not allow for extensive testing. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 11
Forum.Nokia.com 3 Introduction to the User Interface The followi ng chapt er offers a brief ov erview of t he user inte rface sty le in 96 x 65 pixe l screen resolution phones. The m ain focus is on the W AP services element (W AP browser) of the phone. The WAP browser user interface is designed to comply with the user interaction handling known from other applications in the phone. The user interface style is a combi nation of specifi c user inte rface hardware such as keys and display; user interaction conventions, which include input an d output functions and thei r relationsh ips; and the audio-visual appe arance, which is used in the user interaction conven tions. This chapter concentrates on the hardware pa rt of the 96 x 65 pixel resolution user interface. 3.1 Nokia Phones with 96 x 65 Pixel Screen Resolution Nokia Series 30 phones have a WAP bro wser with enha nced features and increased usability. Predictive text input (T9) can be used in the WAP bro wser; predictive text input in WAP and a picture viewer are also supported. Nokia Series 30 phones support Push service in dication; in addition most of the June 2000 conformance (WAP 1.2.1) pho nes support WTAI public library and cookies â . For more detailed information, see the WAP characteris tics table at http://forum.nokia.com. Nokia 3410 Nokia 3510 Nokia 6310 Nokia 6310i Nokia 6510 WAP 1.1 Push WAP 1.2.1 WAP 1.2.1 WAP 1.2.1 WAP1.2.1 GSM900/1 80 0 GSM900/1 80 0 GSM900/1 80 0 GSM900/1 80 0/1900 GSM900/1 80 0 CSD CSD, GPRS CSD, GPRS CSD, GPRS CSD, GPRS Two soft key UI Two soft key UI Two soft key UI Two soft key UI Two soft key UI 3.2 User Interface Hardware â Keys and Display 3.2.1 Two Soft Key Displ ay The display is a full dot-ma trix display with a displ ay resolution of 96 pixels (horizontal) by 65 pixels (vertical). The display consists of t he application area, header area, and an area used for the soft keys. â Excluding Nokia 3410 WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 12
Forum.Nokia.com Figure 1: Struct ure of the browser screen The applicat ion area is 96 pixels (horizontal) b y 45 pixels (ver tical). It includes four lines of main text and can also b e used for display i ng graphics, whic h can be scrolle d four ways (pictu re viewer) until the maximum deck size. 3.2.2 Keys in Two Soft Key Use r Interface The Send/Talk key works as a select ion key. The End key exits a data call/GRPS connection an d goes into idle state when pressed twice. The two soft keys are assign ed actions that en able the user to manipulate the user interf ace by making selections and enterin g, editing, an d deleting text. I n Nokia 68xx there is also a third soft key, which is used only as profile key. -The left soft key is use d as a yes/positive k ey. It contains opt ions that execute commands an d go deeper into the menu structure. Some exam ple functions are Select, OK, and Options. -The right soft key is used as a no/negative key. It contains o p tions that can cel commands, delete text, an d go backwards in the menu structu re, such as Back, Ex it, and Clear. The scroll keys (arrow keys) allow the use r to scroll the options or te xt in the current displ ay. 3.3 Display Fonts All fonts are proportional font s. Proportional fon ts give a dyn amic and minimize d width for each characte r, improve re adability of the display texts, and g enerally allow mor e characters to be displayed per line. On the othe r hand, having pro portional fonts means that it is difficult to tell how many characte rs there can b e in each line, e.g., compare characters âÂÂWâ an d âÂÂi.â 3.4 Accessing the WAP Browser The browser is accessed by selecting Services from the menu and entering a home page define d for the currently active settings or a bookmark. For quick access to the browser, the user can make a long key press on the 0 key; t he user is then taken to the home page th at is defined fo r the currently activ e settings set. The access point and home page can be set in the Serv ices -> Settings menu. 3.5 Navigation, Labels, and Titles The user should b e provided with cons istent card headers, ele ment titles and do-element labels. The title of a <select> element is used in the header of a sel ection list or option groups list. The title of an <optgroup > element is used as an option group title and in the header of its selection l ist. The title of WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 13
Forum.Nokia.com an input elem ent is used in the e d itor title. The label of a do element is used in the Service option s behind the Options soft key. 3.6 Scrolling The user can move u p and down in a card view when it contai ns elements (hotlin ks, input elements, and selection list items) and static text areas between the m. This is done by âÂÂjumpingâ fro m element to element. Scrol ling through long static sect ions (that is, t ext lines) is done line by line. The first element of a card is h ighlighted by default if it is on the first displ ay. 3.7 Picture Viewer The picture viewer lets user s perform horizontal and vertical scrolling of pict ures /anim ation s that a re too wide/high for the displ ay. The picture viewer ca n on ly be activated by sele cting the options lis t item View Picture if the currently active page conta ins at least one p icture/animat ion. In the pict ure viewer , picture s/anima tions ar e display ed simil arly to the way pict ures/a nimati ons are disp layed in the browser display except that only one picture/animation can be viewed at a t ime. 3.8 Cache The browser places viewed cards in cache, which allows previously visi ted cards to be quickly accessed, as there is no need to reload them. T he cards stay in cache u ntil it is manually cleared by the user or until the memory is full. See the Nokia WAP Phone Characteristics document for information on cache size in different Nokia WAP phones. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 14
Forum.Nokia.com 4 WML Elements for the Nokia User Interface This chapter s erves as a gui de for using WML in designing services. It provides an overview of graphical user interf ace elements, that is, th e WML ele ments that are critical f rom the rendering point of view and their WML capabilities supported by t he browser. The docum ent does not include all possible WML elements and attributes. WAP service developers s hould pay special attention to Sections 4.2: T able and 4.3: Im ages. The WML elements are b riefly described and demonstr ated with screenshots. Code examples include only the essential part related to using the ele ments, i.e., the document prologue is not shown after Example 1. 4.1 Text Formatting The contents of a WML card are displayed in the Application area of the display (see Figures 4.1 and 4.2). The card is a container of text, images, tables, and input elements. Th e order of elements in a card is signific ant, as they appear on t he screen in the same order. 4.1.1 Paragraph and content alignment The paragraph element, p, enables word wr apping and content alignment. A paragraph always starts on a ne w line. Norm al static text information is alw ays wrapped on a d isplay, unless word wrapping is set off in the browser settings. Insigni ficant whi te space i s ignored. If more than on e white spac e separa tes the consti tuents of a text, these white spaces are ignored unless th e pre element is us ed. See Section 4.1. 4 for more information o n the pre element. The content inside a paragraph can be aligned to the left, center, or right by option; left alignment is displayed by default. Alignment is determined in par agraph attributes ( for example, <p align="right ">). Word wrapping can be set to wrap or nowrap by using the mode attribute in paragrap h. <p align="center"> Align "center" </p> <p align="right"> Align "right" </p> <p align="right"> <img alt="3510i" src="file://C:/USERS/wml/3510i.gif" align="top" hspace="0" vspace="0"/> </p> Example 1: Alignment <align> 4.1.2 Line break New lines in text can be defined by a line break. The line break eleme nt, br , can be used inside other elements as well, as long as it belongs to a paragraph. If a line break is defined after an a element, the line b reak is ignored. If an empty line is needed betwe en two links, it is necessary to add two line breaks between the a elements. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 15
Forum.Nokia.com 4.1.3 Fieldset element The fieldset element allows the groupin g of related fields and text. The b asic idea of group ing is to show the grouped items on the same displa y if possible. If the items cannot be displayed on the same display, the user is not given any no tification. Fieldset always starts a new line and ends with a line break. 4.1.4 Pre element The pre element is supported. When the pre element is used, the content shown is rendered as âÂÂpreformattedâ to the extent possible. This implies that white spac e is left intact when render ed, that the font in the cards remain s the same as for plain t ext in a card, and t hat word wrapping is enabled/dis abled according to how the browser is set. 4.2 Table The <table> element is used together with the <tr> and <td> ele ments to create set s of rows and columns of data, such as text, images, and so on. It is po ssible to have text, images, and tables on the same card. The cells are sho w n in bordered rows an d columns. The size of the cells is dynamic, according to th e cont ent of the cells. The widest cells affect the width of the other cells in the same column. There is a minimum cell width of 10 pixels in order for the columns to re main discernible. The width of the rows w ill be adapted so that all can fit. When more cells are define d than can be on the screen, the cells will all be of the defined minimum width. When the content of the cel ls is too large to fit the cell, its content is truncated and three dots ar e added. A maximum of one text, image, or link element can be shown in each cell when n o row in the table has bee n selected. Otherwise text, image, as well as link el ements can be sho wn in a cell. In a text element, if line breaks are defin ed, several lines can b e shown at a t ime. When no ro w has been selected, the longest line in a ce ll defines the width of the cell if the cell can be shown in full width. Otherwise lines of excessive length a re truncated an d three dots a re added. The full content of each cell c an be viewed by scrolling. The title of the table is s hown when a row is selected. If the table has no title, the title of the card in whi ch the ta ble is situa ted is u sed as a tit le for the tab le. <table align="LCC" columns="3"> <tr> <td>Date</td> <td>F'cast</td> <td>T ðC</td> </tr> <tr> <td> <anchor title="date">M 6/7 <go href="#date" method="get" sendreferer="false"/> </anchor> </td> <td> <anchor> <img alt="rain"src="file://â¦/rainy.wbmp" align="bottom"/> <go href="#descr" method="get" sendreferer="false"/> </anchor> </td> <td>25ðC</td> </tr> <tr> <td>T 6/8</td> WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 16
Forum.Nokia.com <td> <img alt="part cldy" src="file://â¦/partcldy.wbmp" align="bottom"/> </td> <td>27ðC</td> </tr> <tr> <td>W 6/9</td> <td> <img alt="cloudy" src="file://â¦/cloudy.wbmp" align="bottom"/> </td> <td>24ðC</td> </tr> <tr> <td>T 6/10</td> <td> <img alt="rainy" src="file://â¦/rainy.wbmp" align="bottom"/> </td> <td>28ðC</td> </tr> <tr> <td>F 6/11</td> <td> <img alt="sunny" src="sunny.wbmp" align="bottom"/> </td> <td>29ðC</td> </tr> </table> Example 2: Table element 4.3 Images The graphics form ats Wireless Bitmap (wbmp), stati c gif (.gif 87a), and animat ed gif (.gif 89a) are supported . The static gr aphics area is at maximum 78 pixels wide and 30 pixels high, but vertically and horizontally scrollable until the maximum deck size. Ho wever, the animate d gif graphics area is a t maximum 78 pixe ls wide and 30 pixels high. Ima ges fitting in t he graphics area are centered unless specified otherwise by the service provider. St atic images that are too wide are leftâ aligned and tr uncated on the r ight. Images tha t are too long are topâÂÂaligne d but scrollable down. The displaying of images is optional and can be turne d off in the bro wser appearance settings. Images can al so be used inside a table and as a link (se e Example 4.2 above). An image th at functions as a link is represented with a full-line frame around it. Images appear in a separate line than text. Figure 2: Image in Nokia 6310 Image sizes of a maximum of one line, that is, 10 pixels high, may be shown with two lines of text on the same display above and/or below the image. Similarly, with an image of a maximum of 20 pixels there can be one li ne of text.. There cannot be text next to an image; the image wi ll always start its own line. If a requested image does not ex ist, a small default picture will be sho wn. Use of the image alt attribute value is recommended. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 17
Forum.Nokia.com 4.3.1 Animated GIF Most recent Nokia browsers 1 support ima ge format animate d gif (.gif 8 9a). The maximum number of frames allowed is 13 (not e, maximum file size is 2.4 kb). The animatio n can be viewed in the browser vie w. After running th e animation i n looping mode for 50 loops the animation will stop . The last frame of the an imation will be shown as a static gif. 4.4 Links The anchored link ele ment specifies a hotl ink. Links are underline d; in Nokia 3510i links are displayed and underline d in blue. An activ e link is shown in inverse colors. When a user selects a link, the associ ated task is pe rformed. When th e link is active, the options list of the browser display is extende d with the option Select. The user can also select a link by press ing the Send key. Figure 3: Selected link is highlighted The a element is a short form of the anch or element, and is boun d to a go task wi thout variables. In general it is recommended to use the a element instead of the anchor where possible, to allow mo re efficient tokenization. A hotlink is automat ically followed by a line break. If a line break is defined after an a el ement, the line break is ignore d. If an empty line is neede d between two links, it is necessary to add two line breaks between t he a elements. If a hotlink does not hav e a title or label, t he URL address of the link is displayed in its full le ngth, and functions as a normal hotlink. <anchor>text<go href="#card2"/> </anchor> <anchor> <img alt="golf" src="file://â¦/golf.wbmp"/> <go href="#card2"/> </anchor> Example 3: Image as a link 4.5 Do Element The do element provides a general mech anism for the user to act upon the current card. The do elements are mapped behind the b rowserôs options list togeth er with the preloa ded options. If a do element contains a prev task, the right soft key is labeled "Back." Use of a prev task is highly recom mended in every card because it e nables backward navigatio n. Do elements have a label, i.e., the text of the item in the br owserâÂÂs options list. If th e label is available it is used as an op tion list item. If there is no label, a default text is displayed, according to T able 4.1 below. However, it is highly recommended to use the label att ribute. 1 All phones that are in troduced in this documen t support gif image formats in the WAP browser. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 18
Forum.Nokia.com Type Static text Accept OK Prev Back Help Help Reset Reset Options Options Delete Erase Unknown Unknown Table 1: do elements label default text 4.5.1 Prev task The author of the WAP service is always respon sible for the working n avigation model inside its own service. If there is a need for back functi onal ity, it should be explicitly def ined with the prev type do element. Th e WAP browser does not have any implicit b ack functionality. 4.5.2 Ca rdwide and d eckwide scope The do element c an be expressed in two ways: in c ardwide scope or in deckwide s cope in template. Do elements will be stored in the browserâÂÂs options list together with the preloaded options. <template> <do type="prev" label="Back"> <prev/> </do> </template> Example 4: Deckwide bac kward navigation, prev <do type="prev" label="Back" <prev/> </do> Example 5: Cardwide back ward navigation WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 19
Forum.Nokia.com <wml> <template> <do name="help-button" type="options" label="Ask Help"> <go href="http://.../help.wml" method="get"/> </do> <do type="options" label="Contact"> <go href="http://.../contact.wml" method="get" sendreferer="false"/> </do> <do type="prev" optional="false"> <prev/> </do> </template> <card id="card1" title="Homepage" ordered="true"> <p align="left"> Please, register <br/> Username: <input name="username" type="text" title="Username" emptyok="false"/> Password: <input name="password" type="password" title="Password" emptyok="false"/> <do type="accept" label="Enter"> <go href="#confirm" method="get" sendreferer="false"/> </do> </p> </card> <card id="confirm" title="Confirmation" ordered="true" newcontext="false"> <p align="left"> $(username), thank you for registering. </p> </card> </wml> Example 6: Do element 4.6 WML Input Processing Input processing lets the us er input reques ted information to the serv ice. There are two kin ds of input elements: t ext fields determined by an input element and selection lists determined by a select element. Option elements are used to specify a single choice option in a select element. Option elements can be grouped by using an optgroup element (se e Example 4.9). 4.6.1 Input elements The input element, which is displayed with brackets, specif ies a character entry object. By selecting the input element, the use r evokes the editor. The e ditor is never displaye d directly in the card view. The options list of the browser display is then ex tended with the "Edit" option. T he T9 option is enabled in the browser. Th e user can select the input element by pressing the Send key. The in put element consists of a title, brackets, and a value. There can be a default value inside the brackets. The title of the element is o nly displayed when the e ditor box is displayed, which is after h aving selected the input element. Th e value with the brackets is al ways wrapped to the next line. If the value cannot fit into one line, the end of the content is truncated and three dots are added. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 20
Forum.Nokia.com 4.6.2 Direct input access The user can also select the input element by pressing any numeric key when the e dit box appears and t he pressed key is al ready placed in the ed it box, i.e., the user c an just start inputting characters an d the edit box appears automatically. When T9 (predictive text input) is act ivated, the sof t keys are "Options" and "Back" when the editor is empty. Otherwise the soft keys are "Options" and "Clear ." This also appl ies if T9 is deactiv ated. Input fields can be specif ied by the in put element's type an d format attributes. <template> <do type="previous" label="Back" optional="false"> <prev/> </do> </template> <card id="card1" title="Homepage"> <p align="left"> Please, register <br/> Username: <input name="username" type="text" title="Username"/> Password: <input name="password" type="password" title="Password"/> <do type="accept" label="Enter" optional="false"> <go href="#confirm" method="get" sendreferer="false"/> </do> </p> </card> <card id="confirm" title="Confirmation" ordered="true"> <p align="left"> $(username), thank you for registering. </p> </card> </wml> Example 7: Text input <input> 4.6.3 Select element Selection lists are elements that s pecify a list of options for th e user to choose from. There are two kinds of selection l ists supported: single-c hoice and multip le-choice l ists. The user can select multiple choice, if the multiple attribute is set as true (sel ected items are marke d with a selection symbol). The user can h ighlight and se lect the selection list item on a card. The options list of the browser display is extend e d with "Select." The user can also select the selection list by pr essing the Send key. That same ite m will be highligh ted and displ ayed with a selected ico n in front of it once the user re-e nte rs th e list during the same browsing session. A selection list item on a card looks similar to an input element item; it consists of a title, brackets, and a v alue. There is always a default value inside the brackets in a singl e selection list (in a multi-selection list there are by default three dots between the brackets u nless specified othe rwise by the s ervice provide r). If there are no options in the selection list, three dots are displ ayed between the brackets. The title is not displ a yed in the card itself. The value with the brackets is al ways wrapped to th e ne xt line, w hich means that t here will never be text and a valu e with brackets on the same line. If the value cannot fit onto one line, the remaini ng part of the con tent is tru ncated a nd replac ed with thre e dots. The title of the selection list is the first item of the card containing the selection list . If the value is a valu e of a multi-selection, the selections are separated with commas. If the value cannot fit into one l ine, the end of the co ntent is truncated an d replaced with three dots. The WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 21
Forum.Nokia.com user can view the v alue between brackets in full by pressing the # key. Until the # key is released, the content that can fit on the screen is viewed. The soft keys are hidden while t he content is viewed in full. The layout in f ull view is th e same as the on e selected by the use r for browsing. The option element specifies a single choice option in a sele ct element. Options can be grouped with an optgroup element, which specifies a grou p of choice items in a select element. An optgroup element is dis played with an icon in front of the t itle of the optgroup element. An optgroup elem ent can be used in single selection lists as well as multiple selection lists. Only in multiple selection lists it is possible to have option groups that allow multiple selections. <wml> <card id="phones" title="Information Request"> <p align="left"> Send me more information about: <select name="models" title="Products" multiple="true"> <optgroup title="Phones"> <option value="Nokia 7650"> 7650 </option> <option value="Nokia 9210"> 9210 </option> <option value="Nokia 6310"> 6310 </option> </optgroup> <optgroup title="Accessories"> <option value="Battery"> Battery </option> <option value="Desktop stand"> Desktop stand </option> <option value="Charger"> Charger </option> <option value="Headset"> Headset </option> </optgroup> </select> Please, provide your <br/> Name: <input name="name" type="text" title="Name" emptyok="false"/> </p> <do type="accept" label="Confirm" optional="false"> <go href="#confirm" method="get" sendreferer="false"/> </do> <do type="prev" optional="false"> <prev/> </do> </card> </wml> Example 8: Select and optgroup WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 22
Forum.Nokia.com 5 Additional WAP 1.2.1 features 5.1 Push Nokia Series 30 phone is abl e to receive Push Se rvic e Indication (SI) type serv ice messages. Push service messages are an ideal way for service providers to activate users, sinc e they can be used to notify users of updated content or to alert them about information in their are as of interest (e.g., new e-m ails, changes in sto ck prices, flight schedule change s or news headlines ). Se rvice messages indicate downloadable content. The user can view indicate d content by using the Se rvice Inbox and the WAP browser. 5.1.1 Service inbox The service provider can p ush a Service Indicat ion message to the ph one, which is then saved to the Service Inbox in the Services menu. The user can view indicated conte nt afterwards by using the Service Inbox. In the Service Inbox, the received service messages can be viewed, deleted, downloaded, or moved to another folder. Users can define in the Service message se ttings whether to re ceive service messages or not. Servic e messages are sorted in th e Service In box into the fol lowing ord er: 1. All unread Service Indications appear hi ghest on the list and are gr ouped ac cording t o the applied priority level, starting with âÂÂsignal-high, â then âÂÂsignal-medium,â and finally âÂÂsignal-lowâ (see Section 5.1.2 for more info rmation about the priority lev els). The messages in each group are shown in chronological orde r according to the rece iving time. 2. All read service mess a ges appear below unread service messages and are shown in chronological order according to wh en the Service Indications were created. 5.1.2 Service Indication At the least, a Service Indic ation should contain te xt that is displayed to the user and a U RL addre ss of content that may be dynamically generate d for each push message in the application serve r. The Service Indication can contain the following information: ⢠Text ⢠URL address ⢠Creation date ⢠Creation time ⢠Expiration date ⢠Expiration time Each Service Indication has a Service Indication ID, which is used to uniqu ely identify different k inds of Service Indications. Service providers s et the Serv ice Indication IDs for mess ages. The ID allows reception of multiple Service Indications with the same URL address and priority level. If the rec eived Service Indication has the same ID as the one stored in memory, the received Se rvice Indication will replace the stored one only if it is n ewer. Servic e providers ca n determine t he priori ty level of the message. Priority levels are signal-high, signal- medium, signal-low, signal-none, and del ete. Prio rity level defi nes how th e received messages are WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 23
Forum.Nokia.com ordered in the Service Inbox and also whether the user is notified abou t received Service Indicat ion. The defined priority level has the following impact: ⢠signal-high: Notification with an SMS alert tone is presented. ⢠signal-medium: Notification with an SMS alert tone is presented. ⢠signal-low: No indication of received Service In dicati on is displayed to the user. The Service Indication is silently stored in the Service Inbox. ⢠signal-none: Service Indication is automatically disc arded. The user is not notified. ⢠delete: If a Service Indic ation already exists, the Service Indication with the same I D in the Serv ice Inbox is deleted. If there is no Service Indication with t he same ID in the Service Inbox, the received Service Indic ation is discar ded. The user is not notified. ⢠If no attr ibute ha s been sp ecifi ed, Servi ce Indic ations w ill be rec eived as signal -medium . 5.2 Wireless Telephony Applications Interface (WTAI) Public Library The WAP browser suppo rts three Wireless Telephony Applications Interface (WTAI) public library functions: makin g a ca ll while browsing, s ending DTMF tones, and saving nu mbers and names to the phone book. These functions, MakeCall, SendDT MF, and AddPBEntry, can be used anywhere in the WML code in the same way as when URI or script ref erences are used fo r normal non-WTAI ref erences. 5.2.1 Making a phone call The MakeCall function is used for making a phone call directly f rom the WML browser application. A typical example of the usage of Ma keCall is when the user selects an anchored link, whic h initia tes a phone call . When a MakeCa ll functi on is execut ed, the user is asked to confirm that the dial-up is to be made. If the phone number th at is about to be call ed does not exist in the phone book, a confirmation query with the phone numbe r is displayed. If the number to be calle d exists in the phone b ook, a confirmation query is displayed with the name fetched fr om the phon e book. If the u ser accep ts making th e phone call , another c onfirma tion query is displaye d with text "Quit browsing?" If the user accepts both que ries, the browser sess ion will be terminated and the browser application will close down. The c all will then be i nitiated. When the call is ter minated, the phone is in idl e state. If the user rejects the latter conf irmation query, the call will be initiated from within the browser display and the user ca n b rowse cached content during the call. No in-call options such as Mute, Hold, etc., are acce ss ible from within the browser application. The options list belongin g to the browser display remains unaffected by the fact that a call is active. 5.2.2 Incoming call while bro wsing Normal call handlin g applies when a call is initiated f rom the browser part (e.g., th e called party is busy, call barring is enable d, etc.). 5.2.3 Sending DTMF tone The user can send DTMF tones through the net work by executing a WTAI function called SendDTMF. Just like MakeCall , a typical way of us ing SendDTMF is to assign the SendD TMF function to an an chored link. The user must hav e a voice call active. When the DTMF tone has WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 24
Forum.Nokia.com been sent, the user returns to the card/deck wh ere s/he initiated the sending. The voice ca ll remains active. 5.2.4 Adding a phone book entry The AddPBEntry functio n offers an easy w ay to store a phone nu mber and a corresponding name onto the phone book application fr om a WML card. The service provider provides the name and number. When t he user activates an AddPBEntry function and the service provider has declared a name an d a number, the phone displ ays a confirmation que ry with the text "Save name." W hen the user a ccepts the conf irmati on query , anoth er confirm ation qu ery wi th the text "With number 44 123 123 45 67" is disp layed and the number is stored in the phone book application. When saving is comple te, the currently active card is displayed again. Note that the user does not have to be onl ine or have any voice calls act ive in order t o use the AddPBEntry function. 5.3 Cookies Cookies enable the storage of data such as user in formation to ease browsing by reducing the amount of informat ion the user must enter . For exampl e, lo gin can be configure d dynamically so that it is displayed only if the application cann ot identify the user. Cookies in cached files are ignored. 5.4 Accesskey Service providers have the possibility of us ing the accesskey attribute of the a element an d the anchor element. This allows users to open links with a long press of the associated access keys. Keys allow ed for access ke y use are the 0 -9 number keys. The service provider should indicate to the user which keys to press in order to open the desired links; thi s can be accomplish ed by adding the label of the key to the link concerned, e. g., if the service pr ovider associates the âÂÂ2â key to a link, the service provider should add the number âÂÂ2â to the label of the link. < a accesskey="2" href="phone.wml">(2)a </a> Example 9: Using accesskey "2" Only one link can be associated wit h each access ke y. A key will also o pen its corresponding link if the service provider has ass igned it as an access key but does not indicate this to th e user. If the user tries to open a link by using a key that the service prov ider has not associated with any link, the key will not react to the action of the user. An access key h as an e ffect on a li nk even if the link i s not highlighted. The link chosen by the user is highlighte d after the corresponding access key has been given a lon g press. This is v isible while the terminal is fetching the content of the link. A long press of an access key also has an effect when a card contains bo th acce ss keys and a highlighted input element. An input element can be activate d by an associated access key through a long press in the same way as anchored links (des cribed above). 5.5 Content Download over WAP Content download is a technology that is used to deliver di gital content such as entertainm ent and business applications to mobile terminals. Another important application is for personalizi ng terminals according to a userâÂÂs preferences and l ifestyle. Content downloading can be initiated by an end u ser or by a network application. The content download mechanis m between the mobile termin al and content source is based on open technologies such as HTTP (and WSP) and J ava Community Process technology. This technology allows the creation of an ope n, multivendor market for te rminal vendors as w ell as for network server and broker vendors. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 25
Forum.Nokia.com For more information about content download, please go to h ttp://www.forum.nokia.com/ . 5.6 Segmentation and Reassembly (SAR) Some of the Series 30 phones support Segment ation and Reassembly (SAR) functionality, wh ich is an optional feature in the Wireless Transport Protocol (WTP) lay er defined by the WAP Forum. SAR is used to split large WTP messages into a number of sma ller datagrams and selectively retrans mit failed datagrams. The use of SAR improves over-the-air efficiency for downloading large messages to the phone and makes content downlo ad (e.g., Java MIDlet download) and MMS tr ansfer faster and more reliable. The use of SAR e nables t he transm ission of lar ge data fil es through WAP to the mobile phone . To use SAR, it must be supported by both of the communi cating parties, typically the WAP gateway and the WAP browser. WAP se rvice developers do not nee d to take any actio ns to enable SAR in their s ervice development. Even t hough phones suppor ting SAR allows do wnloading of large files, it s hould be noted that other elements in the network (W AP gateways) might restrict the downl oadable file sizes. Nokia WAP gateways let through files up to 100 KB b ut the limit might be small er than that in some gateways. Another factor to keep in min d is th at SAR can only be used in connection-oriented (permanent) mode. Further information about SAR funct ionality can be found in th e "Segmentation an d Reassembly in the Wireless Transaction Protocol" document, which is available at the Forum Nokia Web site, http://forum.nokia.com. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 26
Forum.Nokia.com 6 Terms and Abbreviations Card A single WML unit of navi gation and user interface. Deck A collection of WML cards th at is the smallest downloadable unit. You cannot download a single card in a deck; you m ust download the en tire deck. Serv ice developers should be aware of this, and n ot create large applications in a single dec k. Do element A way of defining the binding between ev ents (such as a user selection) an d a task (for e xample, to go somewhere). DTMF tone Standard tone used to transmit numeric data via telephone. Generated when numeric keys are pressed. GPRS General Packet Ra dio Service. Mob ile service that gives a packet switched access over GSM to external data networks wi th high pea k transfer ca pacity. GUI Graphical User Inte rface. HTML Hypertext Markup Language . The markup language used for publishing hypertext on the Worl d Wide Web. HTTP Hypertext Transfer Protocol . An application-level protocol for transferring HTML documents in the Internet. Hyperlink A link within a documen t or card that allo ws quick navigation to another document (card). Input element A markup element t hat allows for interaction with the user, that is, lettin g the user input te xtual values. These can be used f or inputs to lo cally stored scripts, or for parsing to origin serv ers. Multiselection list A selection list, which allows the user to scroll and sele ct several (or none) options to be active. Navigation The concept of moving between menu items, decks, and cards. Proportional font A font in which different let ter widths do not necessarily have the same number of pixels. "W" and "I" are good examples. SAR Segmentation and Re-assembly. A functionality used to split large WTP mess ages into a number of small er datagrams an d selectively retransmit fail ed datagrams. Selection list List of user-selectable options. Soft key The phone has one or more function keys whose function depends on th e state of the phone. Th ese keys are called soft keys because there is an associated text on the display. UI User Interface. URL Uniform Resource Locator. St ring that identifies resources in the Web. W3C World Wide Web Consortium. An organiz ation that develops interoperable technologies for Web. Word wrapping Formatting rule for text appear ance. WML Wireless Mark up Language. Markup language based on Extensible Marku p Lan g ua g e ( XML ) , which is intended for Term or Abbreviation De scription WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 27
Forum.Nokia.com use in specifying content and user interf ace for narrowband devices, including cellular phones and pagers. WSP Wireless Session Protocol. A layer of WAP stack, which is optimized for low bandwidt h bearer networks with long latency. WTAI Wireless Telephony Applic ations Interface. Feature th at provides the means to create telephony applications by using a WAE user-ag ent with the appr opriate WTAI function libraries. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 28
Forum.Nokia.com 7 References GPRS-related documentatio n http://www.mobilegprs.com Nokia Mobile Internet Toolk it 4.0 http://forum.nokia.com Nokia Phone User's Guides http://www.nokia.com Segmentation and Re-ass embly-related document ation http://forum.nokia.com WAP Push-related documentation http://forum.nokia.com Wireless application specificat ions http://www.openmobilealliance.org WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 29
Forum.Nokia.com Appendix A. Wireless Application Protocol (WAP) Introduction The Wireless Application Protocol (WAP) is a set o f protocols that allows the development of applications and services for use with mobile phones and other mobil e devices. The WAP Forum maintains these protocols and their re lated standa rds and spec ifications. The WAP Forum consists of a number of high-tech companies from the information technology, software, and telecommunication industries. The objectives of the WAP Forum are to: ⢠Bring I nternet content and advanced data appl ications to digital mobile phones ⢠Create a global wireless protocol specificatio n that works across di fferent wireless network technologies ⢠Enable the creation of con tent and applicatio ns that scale across a wide ran ge of bearer networks and device types ⢠Embrace existing standards and technology wherever possible WAP Architecture WAP and Internet ar chitecture In order to apply as much leverage to the existing Internet standard as poss ible, the WAP stack closely follows the Internet model. This is illustrated in Figu re 1A. Internet HTML JavaScript TM HTTP TLS - SSL TCP/IP UDP/IP SMS USSD CSD IS-136 CDMA CDPD PDC-P Etc.. Bearers: Wireless Application Wireless A pplication Environment (WAE) Wireless Session Layer (WSP) Wireless Tran sport Layer Sec urity (WTLS) Wireless Datagram Protocol (WDP) Other Services and Applications Wireless Tra nsaction Pr otocol (WTP) Figure 1A: Comparison of Inte rnet and WAP architecture This layered arc hitecture allows applicat ions to use the features of the WAP st ack through well- defined interfaces. This close link to the Interne t architecture allows developers to use their existing knowledge and expertise when develo ping applications for mobile terminals. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 30
Forum.Nokia.com Wireless Application Environment (WAE) The Wireless Application Environment (WAE) is a gene ral-purpose ap plication environment that uses a combination of Internet and mobile termin al technology. It prov ides a framework for the development of applicati ons on a mobile terminal. WAE contains sup port for the following functionality: ⢠Wireless Markup La nguag e (WML) - a li ghtweig ht pres entation langua ge, simi lar to Hyper text Markup Language (HTML) but optimized fo r use with mobile terminals. ⢠Wireless Markup Language Script (WMLS) - a lightweight script la nguage, similar to JavaScriptâ¢. ⢠Wireless Tele phony Application / Int erface (WTA / WT AI) - telephony services and programming interf aces. ⢠Content fo rmats - defined d ata formats, such as vCard and vC alendar. Wireless Session Protocol (WSP) The Wireless Session Protocol (WSP) pro vides the a pplication lay er of WAP with an interface f or two session services. The first is a connection-oriented service that operates abov e the transaction layer protocol. The second is a connectionless s ervice that operates above a secure or non-secure datagram service. The WSP is optimized for lo w bandwidth be arer networks with long latency. Wireless Transport Protocol (WTP) The Wireless Transport Protocol (WTP) runs on top of the datagram service an d provides a lightweight transaction-oriented proto col, suitable for use in mobile termin als. WTP operates over secure o r non- secure wireles s datagram networks. Wireless Transport Layer Security (WTLS) Wireless Transport Layer Security (WTLS) is based on the industry standard T ransport Layer Security (TLS) and is optimized for use over narrowband com munication channels. WTLS may be used for secure communicatio n between terminals, an d applications can sele ctively enable WTLS features . Developing Applications for Mobile Browsing Application develope rs can use the prin ciples of WAP to develop new services or ad apt existing Internet applicat ions for use with mob ile terminals. Appl ications are wr itten in Wireless Markup Language (WML) and WMLScript, an d stored on either a normal Web server (origin serv er) or directly on the WAP gateway. The content sto red on the Web s erver is accessible from mobi le terminals via the cellular network and a WAP gateway or proxy. The proxy server acts as a gateway between the cell ular network and the Internet or Intranet. The data sent between the origin serve r and the handset is binary en coded to optimize transmissio n over the narrow bandwidth of the cellular network. Not e that th e content st ored on th e Web ser ver mig ht be in either textual or binary format. When the WAP gateway fetches textual content, it automatically compiles this to the encoded fo rmat to minimize network load. WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 31
Forum.Nokia.com Figure 2A shows the network-related elements require d for developing and offering services to mobile users. Wireless Netw ork WA P Proxy WT A Server Binar y Binary WML HTML Filte r WML WML HTML Web Server Figure 2A: Elements related to mobile browsing Web server The Web server stores the applications written in WM L. Alternatively, existing HTML applications can be used. HTML filter Any applications wr itten in HTML will hav e to be co nverted to WML b efore they are sent to the mobile terminal. This HTML filter may form part of the Web server o r the WAP proxy. WAP proxy The WAP proxy acts as the gateway between the cel lular network and the Internet or Intranet. It encodes the information, which is to be sent to the mobile terminal in binary format and decodes information sent f rom the mobile terminal. WTA server The WTA server handle s networ k-speci fic app licati o ns. These applications are no t discussed in this document. Additional Information Further infor mation on WAP is available at http://ww w.openmobilealliance.org/ . WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 32
Forum.Nokia.com Build Test Sell Developing and m arketing mobile a pplications with Nokia 1 Go to Forum.Nokia.com Forum.Nokia.com provides the tools an d resources you need for content and application development as well as the channels fo r sales to op erators, enterpris e s, and consumers. Forum.Nokia.com Download tools and emulators 2 Forum.Nokia.com/tools has links to tools from Noki a and other industry leaders including Bo rland, Adobe, AppForge, Macromed ia, Metrowerks, and Sun. Forum.Nokia.com/tools Get documents and specifications 3 The documents area co ntains useful white papers, FAQs, tutorials, an d APIs for Symbian OS an d Series 60 Platform, J2ME, messaging (including MMS), and oth er technologies. Forum.Nokia.com/devices lists detailed technical specifications for Nokia devices. Forum.Nokia.com/document s Forum.Nokia.com/devices Test your application and g et support 4 Forum Nokia offers free an d fee-based suppor t that pr ovides y ou with direct access to Nokia en gineers and eq uipment and c onnect s you wi th other devel o pers around the world. The Nokia OK testin g program enables your application to enjoy premium placement in Nokia's sales channels. Forum.Nokia.com/support Forum.Nokia.com/ok Market through Nokia channels 5 Go to Forum.Nokia.com/business to learn about all of the marketin g channels open to you, including Nokia Tradepoint, an online B2B ma rketplace. Forum.Nokia.com/business Reach buyers around the globe 6 Place your applicatio ns in Nokia Tradepoint and th ey're available to dozens of buying organiz ations around the world, ranging from leadin g global op erators and enterpris e s to regional operators and XSPs. Your company and appli cations will also be co nsidered for the regi onal Nokia Software Markets as well as other global and regional opportuni ties, including personal introductio ns to operators, on- device and in-box placement, and particip ation in invitation-only events around the world. Forum.Nokia.com/business WAP Servic e Developer's Guide for Nokia Series 30 Phones with WML B rowser 33