| Author |
Message |
elcin haktanir
New member
Username: Elcinhaktanir
Post Number: 1
Registered: 06-2007
| | Posted on Wednesday, June 27, 2007 - 01:01 pm: | |
i have prepared two SUPL INIT messages for SUPL Enabled Assisted GPS enabled phonesBut none of them worked.I have a suspicion that the header part of the WAP PUSH message is wrong.Could you please tell me which one is the right header?
Alternative 1:
PUSH HEADER = "0605040B8423F0"
TID = "01"
WSP Push Type = "06"
Headers Length = "23"
Content type value length given as "Length-quote Length" = "1F21"
Content Type ('application/oma-supl-ulp')= "6170706C69636174696F6E2F6F6D612D7375706C2D756C70"+"00"
x-wap-application-id = "AF"
x-application-Id-field ('ulp.ua') = "756C702E7561"+"00"
Alternative 2:
PUSH USER DATA HEADER = "0605040B8423F0"
TID = "01"
WSP Push Type = "06"
Headers Length (33 units = "application/oma-supl-ulp".length + "00".length + "AF".length + "756C702E7561".length + "00".length)= "21"
Content Type ('application/oma-supl-ulp') = "6170706C69636174696F6E2F6F6D612D7375706C2D756C70"+"00"
x-wap-application-id = "AF"
x-application-Id-field ('ulp.ua') = "756C702E7561"+"00" |
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce
Post Number: 7297
Registered: 10-2002
| | Posted on Wednesday, June 27, 2007 - 08:16 pm: | |
Hi,
I believe that the X-WAP-Application-ID field value must be "x-oma-application:ulp.ua", not just "ulp.ua".
Beyond that, without spending too much time analysing your alternatives, I would say ...
Alternative 1 is not correct, because your "content type value length" includes the X-WAP-Application-ID header. The X-WAP-Application-ID header is not part of the content type header. It should be included in the WSP header length count, but it is not a parameter of the content-type as implied by this encoding.
Alternative 2 looks more correct, but I don't think you are encoding the X-WAP-Application-ID value correctly, based upon my read of the relevant specification.
Product plug (as it is our web site) ... this was a good example for me to test out the new Advanced WAP Push web form in NowSMS 2007.
From the web form, I could plug in "application/oma-supl-ulp" as the push content type. I cut & paste some hex data for the content from the "OMA Secure User Plane Location" spec. And I put "x-oma-application:ulp.ua" into the "X-WAP-Application-ID" field in the web form.
Now all I need is a phone that could understand this protocol. What phone are you using?
Does the Nokia N95 support this protocol perhaps?
-bn |
elcin haktanir
New member
Username: Elcinhaktanir
Post Number: 2
Registered: 06-2007
| | Posted on Thursday, June 28, 2007 - 06:45 am: | |
When it comes to Talking about alternative 1;
When I look at OMA-WAP-ProvCont-v1_1-20021112-c.pdf
or When I look at DG_wap_provision_ota_P800_P900_R2A.pdf
from Ericsson
or When I look at
OMA_Client_Provisioning_for_Series_40_v1_1_en.pdf
documents i always encounter this "1F2D".And when i count octets this 2D shows number of octets before WBXML data starts..So that is why i calculated all of the octets including x-wap-applicatin-id and its value.
Very very much thanks to you.You showed me my mistakes.
When it comes to Talking about alternative 2;
According to spec
OMA-TS-ULP-V1_0-20050719-C.pdf
Page 61:
x-application-Id-field is said to be 'ulp.ua'
that is why i encoded that field as i did.That is why I never thought that field must be "x-oma-application:ulp.ua".
And when it comes to the phone issue Nokia n95 release pr1.2, Nokia E90 pr2.0, Nokia 6110 Navigator supports SUPL protocol.. the only phone that is available in the market now is Nokia 6110 navigator.the others' release numbers hasn't been released yet..if you attempt to buy nokia n95 wait for a few months for release pr1.2.. |
elcin haktanir
New member
Username: Elcinhaktanir
Post Number: 3
Registered: 06-2007
| | Posted on Thursday, June 28, 2007 - 06:53 am: | |
When it comes to Talking about alternative 1;
When I look at OMA-WAP-ProvCont-v1_1-20021112-c.pdf
or When I look at DG_wap_provision_ota_P800_P900_R2A.pdf
from Ericsson
or When I look at
OMA_Client_Provisioning_for_Series_40_v1_1_en.pdf
documents i always encounter this "1F2D".And when i count octets this 2D shows number of octets before WBXML data starts..So that is why i calculated all of the octets including x-wap-applicatin-id and its value.
Very very much thanks to you.You showed me my mistakes.
When it comes to Talking about alternative 2;
According to spec
OMA-TS-ULP-V1_0-20050719-C.pdf
Page 61:
x-application-Id-field is said to be 'ulp.ua'
that is why i encoded that field as i did.That is why I never thought that field must be "x-oma-application:ulp.ua".
And when it comes to the phone issue Nokia n95 release pr1.2, Nokia E90 pr2.0, Nokia 6110 Navigator supports SUPL protocol.. the only phone that is available in the market now is Nokia 6110 navigator.the others' release numbers hasn't been released yet..if you attempt to buy nokia n95 wait for a few months for release pr1.2.. |
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce
Post Number: 7310
Registered: 10-2002
| | Posted on Thursday, June 28, 2007 - 07:58 pm: | |
Yes, it is confusing. The reason you see "1F2D" before as a content type length field in the OMA Provisioning Content example is because that particular example has parameters to the content-type.
So the content-type parameter being encoded is:
Content-Type: application/vnd.wap.connectivity-wbxml; SEC=USERPIN; MAC=xxxxxxxxxxxxxxxxxxxxxxxxxx
You must use the length field if you are encoding a Content-Type header that includes any parameters. If there are no parameters, you can still include a length field, but it should count only the size of the Content-Type header.
Regarding the OMA-TS-ULP spec, it looks like I have an updated version (OMA-TS-ULP-V1_0-20070122-C.pdf). You might want to take a look at the Open Mobile Alliance web site where this is available for download on the "OMA Release Program and Specifications" page.
Good luck ... and thanks for the info on the phones. Hopefully the N95 will see a firmware update for this, we'll see!
|
elcin haktanir
New member
Username: Elcinhaktanir
Post Number: 4
Registered: 06-2007
| | Posted on Tuesday, July 10, 2007 - 02:41 pm: | |
hi bryce i now have the new firmware upgraded nokia n95 and i have prepared my sms message as it is stated in OMA-TS-ULP-V1_0-20070122-C.pdf page 56.
here it is:
My problem is it is still not working.it is driving me crazy.
could you please tell me where have i done wrong.Thanks in advance .
PUSH USER DATA HEADER = "0605040B8423F0"
TID = "01"
WSP Push Type = "06"
Headers Length (33 units = "application/vnd.omaloc-supl-init".length + "00".length ) = "21"
Content Type ('application/vnd.omaloc-supl-init') = "6170706C69636174696F6E2F766E642E6F6D616C6F632D7375706C2D696E6974"+"00"
x-wap-application-id = "AF"
x-application-Id-field ('x-oma-application:ulp.ua') = "782D6F6D612D6170706C69636174696F6E3A756C702E7561"+"00"
0605040B8423F00106216170706C69636174696F6E2F766E642E6F6D616C6F632D7375706C2D696E 697400AF782D6F6D612D6170706C69636174696F6E3A756C702E756100
|
elcin haktanir
New member
Username: Elcinhaktanir
Post Number: 5
Registered: 06-2007
| | Posted on Wednesday, July 11, 2007 - 06:27 am: | |
hi bryce i now have the new firmware upgraded nokia n95 and i have prepared my sms message as it is stated in OMA-TS-ULP-V1_0-20070122-C.pdf page 56.
here it is:
My problem is it is still not working.it is driving me crazy.
could you please tell me where have i done wrong.Thanks in advance .
PUSH USER DATA HEADER = "0605040B8423F0"
TID = "01"
WSP Push Type = "06"
Headers Length (33 units = "application/vnd.omaloc-supl-init".length + "00".length ) = "21"
Content Type ('application/vnd.omaloc-supl-init') = "6170706C69636174696F6E2F766E642E6F6D616C6F632D7375706C2D696E6974"+"00"
x-wap-application-id = "AF"
x-application-Id-field ('x-oma-application:ulp.ua') = "782D6F6D612D6170706C69636174696F6E3A756C702E7561"+"00"
0605040B8423F00106216170706C69636174696F6E2F766E642E6F6D616C6F632D7375706C2D696E 697400AF782D6F6D612D6170706C69636174696F6E3A756C702E756100
|
elcin haktanir
New member
Username: Elcinhaktanir
Post Number: 6
Registered: 06-2007
| | Posted on Thursday, July 12, 2007 - 06:31 pm: | |
hi bryce i now have the new firmware upgraded nokia n95 and i have prepared my sms message as it is stated in OMA-TS-ULP-V1_0-20070122-C.pdf page 56.
here it is:
My problem is it is still not working.it is driving me crazy.
could you please tell me where have i done wrong.Thanks in advance .
PUSH USER DATA HEADER = "0605040B8423F0"
TID = "01"
WSP Push Type = "06"
Headers Length (33 units = "application/vnd.omaloc-supl-init".length + "00".length ) = "21"
Content Type ('application/vnd.omaloc-supl-init') = "6170706C69636174696F6E2F766E642E6F6D616C6F632D7375706C2D696E6974"+"00"
x-wap-application-id = "AF"
x-application-Id-field ('x-oma-application:ulp.ua') = "782D6F6D612D6170706C69636174696F6E3A756C702E7561"+"00"
|
elcin haktanir
New member
Username: Elcinhaktanir
Post Number: 7
Registered: 06-2007
| | Posted on Thursday, July 12, 2007 - 06:36 pm: | |
hi bryce i now have the new firmware upgraded nokia n95 and i have prepared my sms message as it is stated in OMA-TS-ULP-V1_0-20070122-C.pdf page 56.
What is wrong with this prefix#1 =
0605040B8423F0
01
06
0603020312
AF
90
OR What is Still Wrong with this alternative#2
0605040B8423F0
01
04
0603020312
AF
90 |
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce
Post Number: 7388
Registered: 10-2002
| | Posted on Tuesday, July 17, 2007 - 09:23 pm: | |
The headers in the last message look correct to me ... assuming that the short encodings are supported by the device (with them used in an example in the spec, I would expect them to be, but you never know).
Well, alternative #1 is ok ... but #2 has changed from the WSP Push PDU (06) to the WSP Reply PDU (04), which is a problem.
The long header examples in the messages preceding that one do have a problem ...
quote:PUSH USER DATA HEADER = "0605040B8423F0"
TID = "01"
WSP Push Type = "06"
Headers Length (33 units = "application/vnd.omaloc-supl-init".length + "00".length ) = "21"
Content Type ('application/vnd.omaloc-supl-init') = "6170706C69636174696F6E2F766E642E6F6D616C6F632D7375706C2D696E6974"+"00"
x-wap-application-id = "AF"
x-application-Id-field ('x-oma-application:ulp.ua') = "782D6F6D612D6170706C69636174696F6E3A756C702E7561"+"00"
The length field applies to the entire header ... not just the content type parameter. I calculate the "21" length should be "3B" ... but that is based on a quick check, and I could be off by a byte or two.
You might want to give that a try. If the device firmware might have been finalised before the short encoding number assignments were completed.
As a sanity check, you are able to send other types of WAP push messages to the device, right? |
Search
Last
