×

Discussion Board

Results 1 to 3 of 3
  1. #1
    Registered User
    Join Date
    Mar 2003
    Posts
    5

    code pages and SWITCH_PAGE

    Hi,

    I've read through the OMA documents on OMA Provisioning [OMA-WAP-ProvCont-v1_1-20021112-C] and the WBXML specs [WAP Binary XML Content Format]. I thought I understood about code pages but then I looked at the nokia document for the Nokia 6600 from:

    http://www.forum.nokia.com/main/1,,0...ml&fileID=4066

    There is an example at the end of this document showing what the sample XML document encodes to.

    Here is a part of that encoding

    ...
    C6 55 01 NAPDEF
    . . 87 11 06 03 42726F7773696E675F4750525300 01 NAPID
    . . 87 10 06 AB 01 BEARER
    . . 87 07 06 03 42726F7773696E67204750525300 01 NAME
    . . 87 08 06 03 696E7465726E657400 01 NAP-ADDRESS
    . . 87 09 06 89 01 NAP_ADDRTYPE
    . . C6 5A 01 NAPAUTHINFO
    . . . . 87 0C 06 9A 01 AUTHTYPE
    . . . . 87 0D 06 03 6E616D6500 01 AUTHNAME
    . . . . 87 0E 06 03 70617373776F726400 01 AUTHSECRET
    . . 01 NAPAUTHINFO END
    01 NAPDEF END

    C6 00 01 55 01 (code page 1) APPLICATION
    . . 87 36 06 03773200 01 APPID
    . . 87 39 06 0350524F58593200 01 TO-PROXY
    . . C6 59 01 RESOURCE
    . . . . 87 00 00 07 06 03 426F6F6B6D61726B204E616D6500 01 (code page 0) NAME <---------- Why ??? 'NAME' is listed in code page 1 table too!
    . . . . 87 00 01 3A 06 03 687474703A2F2F7761702E636F6D0001 (code page 1) URI
    . . . . 87 00 00 1C 01 (code page 0) STARTPAGE
    . . 01 RESOURCE END
    01 APPLICATION END
    ...

    Why is there a SWITCH_PAGE for the 'NAME' attribute? In the OMA document [OMA-WAP-ProvCont-v1_1-20021112-C], there are two tables which list "Parm Attribute Start Tokens". The first table is for code page 0 attributes, the second is for code page 1 attributes. The 'NAME' attribute is listed in both tables! Is this a mistake? (See pages 54 and 57 of the OMA-WAP-ProvCont-v1_1-20021112-C document to see the two entries.

    Anyway, I'm confused. If 'NAME' is listed in both tables, why the SWITCH_PAGE, to code page 0?

    Any help appreciated. Thanks...
    Last edited by sbarlow; 2004-01-09 at 09:03.

  2. #2
    Regular Contributor
    Join Date
    Mar 2003
    Posts
    474
    Hello -- very good question -- afraid I don't have an answer for you. As far as I can see, you are absolutely right -- there should be no need for a code page switch, and we just wasted valueable bytes.

    I'll send a message to the person who wrote the document (and the sample).

    -paul / ForumNokia

  3. #3
    Regular Contributor
    Join Date
    Mar 2003
    Posts
    474
    Alright, here is a good answer to your question:

    The parameter NAME is indeed specified in two tables. There are a couple of other similar examples, like PORTNBR, INTERNET, STARTPAGE, etc. We haven't been involved in standardization of OMA Provisioning token values, so the reason for duplication is not entirely clear. Our guess is that this is a small optimization. If the parameter NAME is used in characteristic APPLICATION, whose token is found on code page 1, it isn't necessary to switch to page 0 just to specify NAME.

    In practice the optimization is so small that many encoders seem to ignore this possibility, and switch to page 0 always when specifying NAME. This is the case in the example of the User's Guide.

    -paul / ForumNokia

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×