| Smart trust wib |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| alya New member Username: Alya Post Number: 16 Registered: 12-2003 |
i'm using wig application creator from smart trust to convert wml into bytecode : --- <?xml version="1.0" encoding="ISO-8859-1" ?> <!DOCTYPE wml PUBLIC "-//SmartTrust//DTD WIG-WML 4.0//EN" "http://www.smarttrust.com/DTD/WIG-WML4.0.dtd"> <wml> <card id="Main"> <p> hallo world </p> </card> </wml> --- and get bytecode : 0014100102210D030B68616C6C6F20776F726C640600 ----- in nowsms , i think it will be as binary data. could you tell how about the : UDH, DCS and PID value? if we can completed the udh, dcs and pid, is it possible we can send this binary data from nowsms? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6408 Registered: 10-2002 |
Hi Alya, This is a new one to me. The byte code encoding that you show above is not the standard WML to WBXML conversion. It appears that SmartTrust has defined their own variation of WML, with its own binary encoding specific to their browser (and it does not appear to be WBXML based), with their browser is apparently installed on a SIM card. (Their browser is called the Wireless Internet Browser, or WIB.) As such, I don't know what the protocol is that SmartTrust has defined for sending a message to their browser (WIB) that resides on a SIM card. The only information that I can find published by SmartTrust about this is that you are supposed to use the Push Access Protocol (PAP) to submit your content to their Wireless Internet Gateway (WIG). And the WIG converts this into the appropriate over the air format for delivery to the WIB. NowSMS does support PAP ... which is used for sending WAP push messages to a mobile ... and there are various other mobile protocols built on top of WAP Push. However, I don't think the protocol defined by SmartTrust uses the actual OMA push over the air protocol. They are just using PAP and WML because it is familiar to mobile developers. If you submitted a PAP request to NowSMS, and byte coded the content (as NowSMS would not know how to byte code this content) ... then NowSMS would package the content as a WAP push and send it to the device. But a browser on the phone would see the push ... not a browser on the SIM. That is why I believe that SmartTrust is using a different protocol for actually encoding the content over the air ... and I can't see any document that defines this protocol. The WIG Application Creator User Guide makes reference to GSM 03.48 headers being included with the generated byte code. GSM 03.48 is the specification that defines the security mechanisms for SIM toolkit commands ... and it is not clear to me what headers would be required for this type of application. The bottom line is that it looks like you would need the SmartTrust WIG. I believe their WIB is designed to work specifically with their WIG, not with openly defined protocols. -bn | |||
