EMS format explanation needed

Hello!

I do need the explanation of EMS format messages, i.e. PICTURE, ANIMATION, FORM, etc...

I have various documentation, but there's no byte-by-byte (octet-by-octet) explanation of the headers, user data, etc.

Without this information and basing only on overall information, i surely can't program the format :)

Thanks in advance,
Dmitry.
wizzardAsked:
Who is Participating?
 
svindlerConnect With a Mentor Commented:
0
 
wizzardAuthor Commented:
actually, i was seeking for the examples on coding the graphics, inserting it to the object, etc, for i of course have the specificatios from 3gpp and other sources and figured out most of the thingies.
0
 
svindlerCommented:
The format of the bitmaps are defined in Annex E
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
wizzardAuthor Commented:
It's written in any specification, that's clear.

but regarding defining the Extended Object itself... there should be position or something... or can I send the logo or picture just glueing it to the HEADER? header, then UDH then UD - just my coded picture? That's how it works for logos and plain pictures, without text? Am I correct?

Finalize this and you'll get the points ;)
0
 
svindlerCommented:
It's explained in 9.2.3.24.10.1. You have to specify the type, position and length of each object. If that's what you mean by gluing then you are correct.
You probably want to read all of 9.2.3.24, and skim through the rest of the document.
I am very vague on details as I haven't written any programs for this myself. I just RTFM ;-)
0
 
wizzardAuthor Commented:
hmm, last question - is EMS operator-independant? meaning does the operator have to support EMS in order to just simply pass ems messages to the recepients supporting it?
0
 
svindlerCommented:
The SMSC probably does some parameter checking in the messages and provide for a way to allow only certain types of messages/objects through. Allowing new types through could require reconfiguration or upgrade of the SMSC.
I would expect (suspect) some operators to use this to charge more for EMS, or to block new types.
0
 
wizzardAuthor Commented:
hmm, there are no information how to send SIEMENS or any other LOGO... gmmmm......
0
 
svindlerCommented:
For logo programming you would have to contact each phone manufaturer, like Nokia, Siemens, Ericcson etc as the logos are in proprietary format as far as I know.
0
 
wizzardAuthor Commented:
Ahaa... hmmm... for nokia is using it's personal SmartMessaging and that I cracked long ago... they have special PORTS for that... it's being pointed in the IEDL. but for EMS - nothing like that can be found, sadly...

* If you will ever develop something based on 3gpp docs, i'm warning you that they've got lotsa bugs i discovered and "repaired"...

I'll grant you with the points now... But please, if you'll find anything regarding LOGO ports or etc for siemens, ericsson, etc EMS phones... tell me :)

And i will make a new question and you'll get more points ;)
0
 
svindlerCommented:
I found some references to source code to manage Siemens phones. You'll have to check the quality and usability yourself.
0
 
wizzardAuthor Commented:
ohh, will you send that to me or want me to create another question? :)
0
 
wizzardAuthor Commented:
svindler, where are you? I *AM* interested in the sources.... :-\
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.