1041974 - [OPEN II_1.3]Parameters about Wap Push in the Datasheet for Ecuador

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Wappush, defect)

Description

[Yang Yue]

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; TCO_20140722161114)

Steps to reproduce:

We should to complete following infomations about Wap push

SI (Service Indicator) wap push supported:Yes
SL (Service Loading) wap push supported:Yes
Max size of Push message (KB):
Content applications supported in Push:
Content wml+xml supported in Push:
Content text supported in Push:
Max. Number of Push requests:
Encodings supported in Push:
Charset supported in Push:
Applications supported in Push:
Languages supported in Push:

Comment 1

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Gabriele -

Our partner has some questions about the WAP Push capability, could you kindly help to check these questions and feedback?

Thanks for your help

Comment 2

[Gabriele Svelto [:gsvelto]]

I'm not sure I'm qualified to answering the question here since part of the WAP Push supports is part of the RIL. Currently we support SI/SL messages as well as OTA content provisioning messages (though with a few limitations IIRC; :jaoo should be able to tell you more). I don't think we have any limitations regarding size and number of push messages. Regarding charsets, encodings & co. we support all charsets and encodings that are supported by Gecko and all languages supported by Gaia localizations.

Comment 3

[José Antonio Olivera Ortega [:jaoo]]

(In reply to Gabriele Svelto [:gsvelto] from comment #2)
> I'm not sure I'm qualified to answering the question here since part of the
> WAP Push supports is part of the RIL. 

I don't feel comfortable responding this either, sorry about that.

Chuck did the hacking on gecko side and he might know better that me.

> Currently we support SI/SL messages as
> well as OTA content provisioning messages (though with a few limitations
> IIRC; :jaoo should be able to tell you more).

Well we only support USERPIN and NETWPIN authentication mechanism at the moment.

Comment 4

[Chuck Lee [:chucklee, Triggered by NI, Review, and Feedback requests]]

I think partner should provide detail about what each item means than just a short confusing description, with an example will be better.

(In reply to Yang Yue from comment #0)
> SI (Service Indicator) wap push supported:Yes
> SL (Service Loading) wap push supported:Yes
> Max size of Push message (KB):
  Theoretically about 33 KB(34170 bytes, max size of Concatenated SMS), but not really tested.
> Content applications supported in Push:
> Content wml+xml supported in Push:
> Content text supported in Push:
  I don't understand what above 3 item means, maybe the native supported content type list could help: "application/vnd.wap.sic", "application/vnd.wap.slc", "application/vnd.wap.connectivity-wbxml", "text/vnd.wap.si", "text/vnd.wap.sl", "text/vnd.wap.connectivity-xml"
  For other content types, 3rd party apps have to handle them by receiving system message.
> Max. Number of Push requests: 
  I assume this is about "how many received request can be saved in system".
  We don't save it in gecko, so it's up to application.
  AFAIK, current WAP Push app saves messages in a indexedDB, so it could be no limit.
> Encodings supported in Push:
  I don't know what's this about, WBXML?
> Charset supported in Push:
  Reference to list in [1], from line 2784 to line 2811.

[1] http://mxr.mozilla.org/mozilla-central/source/dom/mobilemessage/src/gonk/WspPduHelper.jsm#2784
> Applications supported in Push:
  I don't know what this means, it's should be application supporting content of WAP Push, not reverse.
  If so, native app supportes SI, SL, and CP.
> Languages supported in Push:
  I think this is as same as charset.

Comment 5

[Yang Yue]

Thanks for your reply.
Encodings supported in Push:
There are some optional parameters in the datasheet.
base64
quoted-printable
base64&quoted-printable
xml UTF-8 encoding
Unkwnone
Which one we can choose for this item?

Comment 6

[Chuck Lee [:chucklee, Triggered by NI, Review, and Feedback requests]]

(In reply to Yang Yue from comment #5)
> Thanks for your reply.
> Encodings supported in Push:
> There are some optional parameters in the datasheet.
> base64
> quoted-printable
> base64&quoted-printable
> xml UTF-8 encoding
> Unkwnone
> Which one we can choose for this item?

Which datasheet are you referenced from? I can find these parameters in WAP Push-related spec.

For incoming message, it should only be encoded in WBXML(binary form) or UTF-8(plain text).
If this is about the content contained in system message, for SI, SL, and CP message which can be successfully decoded, the content will be UTF-8 encoding. Otherwise the content will be a typed array containing raw data of the incoming message.

Comment 7

[BMO Automation]

Firefox OS is not being worked on