| MMS UAProf |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Murali Mohan.K |
Hi, I was looking at the WAP-206-MMSCTR.pdf where a UAProf sample is given in xml format. It is having some MMS Attributes MmsMaxMessageSize , MmsCcppAccept etc... My doubt is where can i get the binary encoding for these attributes, like how we have encoding for Push , Software, hardware.. etc.. characteristics in WAP-UAProf Specification. Plz let me know abt it... Thanx in advance | |||
| Bryce Norwood - NowSMS Support (Bryce) |
I'm not aware of anywhere that that the UAProf is encoded in WBXML. I've always seen it as plain text. When a phone supports UAProf, it transmits a URL for the UAProf file in the "Profile:" header. Some phones transmit this only in the WSP CONNECT request, others transmit it on every WSP GET or POST request. It is then up to the WAP gateway whether or not it gets forwarded to content servers on requests proxied by the WAP gateway. When it is forwarded, it appears as a "Profile:" header in HTTP GET and POST requests. -bn | |||
| Murali Mohan.K |
But how can a phone store the file and provide a link for the UAProf file, since a phone is not something similar to a server to do this. Is there any way to store the UAProf file in some http server of the phone's service provider and send the link as UAProf link??. But are there any service providers who providing this facility?? How exactly this is being done in phones which are in the market??. -Murali | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Murali, The UAProf describes characteristics of the particular model of the phone in use (actually there are often different links for different versions of the firmware). So it is not really phone specific. The authors of the client software that runs on the phone publish a user-agent profile for their software on the web somewhere. The browser sends a link out to that profile. For example, the User-Agent profile link for the Nokia 3650 is: http://nds.nokia.com/uaprof/N3650r100.xml -bn | |||
| ooze |
the WAP-206-MMSCTR.pdf demands that Upon opening a WSP session with a WAP gateway, the UAProf-aware client conveys its profile information using Profile and Profile-Diff headers within the WSP Connect request. The values of these headers are constructed by encoding the CPI using a WBXML encoding. so how could the non wbxml-encoded profile without profile-diff header inclueded work right? what file extension should the uaprof be? must be xml? thanks in advance | |||
| Bryce Norwood - NowSMS Support |
Ooze, I agree that it doesn't make much sense. I believe this is one of the reasons why you don't see the Profile-Diff header used very frequently. I do remember seeing it once in a debug log from somebody's system, but I can't remember what device was actually generating it. In any event, the WBXML encoding for a UAProf file is defined in Section 8 of the UAProf specification. So there is a WBXML encoding defined for UAProf files ... however when you use the "Profile:" header, the file is in plain text, not WBXML format. I can only suppose that the reason for the "Profile:" header to point to a plain text XML UAProf file, and the "Profile-Diff:" to contain WBXML encoded UAProf information was to discourage people from using the "Profile-Diff:" header.  The file extension can be anything. Most UAProf seem to be using ".xml" as the file extension, but I've seen some others as well. Here's a link that you might find helpful which has a collection of various UAProf files: http://w3development.de/rdf/uaprof_repository/ | |||
| OOZE |
thank u! you are so kind, you answered almost the whole messages in this sub-forum! | |||
