In what scenario would a content provider or developer send large content (e.g., image) using the SMS bearer (vs. WSP)?
The SMS bearer may be used if a WAP session is not available. Message size for this bearer is dependent on the individual type of network involved, for example in GSM SMS it is 160 Bytes. Messages greater than 160 bytes are segmented and reassembled automatically, using the WAP WDP specification. In terms of the maximum SDU (Service Data Unit) allowed by the session, the current WAP default limit is 1400 bytes, but is dependent on the handset negotiation. Even then you are talking about segmenting over 9 SMS messages, which can be done, but it just takes time in the handset. For larger messages try for 1-2 SMS Messages = about 300 Bytes. Also, remember that these are encoded bytes for over the air transport. For example if this was a Service Indication you would be looking at the overhead on the text label and URL of about 30-50 bytes for encoding, giving you 80-120 chars to play with in a single GSM SMS message.
Related Questions
- Medical image files can be quite large. How is it possible that the mVisum system can send and receive multi-slice CT scans, MRIs and ultrasound movies without lengthy download times?
- In what scenario would a content provider or developer send large content (e.g., image) using the SMS bearer (vs. WSP)?
- Can I send SMS messages from the developer sandbox number?
