CIMD Interface Specification - Telenor

More documents

Recommendations

Info

ZZ:NNNPPP:parameter1QQQ:parm2 When real values for ZZ, NNN and so on, are used, you get a message such as: or: 01:001010:wwwstat011:wwwstat 03:011021:123456789033:hi there 4.2 Message packet numbering CIMD Interface Specification All CIMD2 messages are assigned a packet sequence number. This packet sequence number is used for detecting duplicate packets or missing packets. The number is assigned according to the following rules: . Operations from the application to the SMS Center are assigned an odd packet number, starting from one. Subsequent packet numbers are incremented by two. After reaching 255, the number wraps back to one again. Using the coding described before the three-character NNN field (see the previous example), the message packet numbering for a list of application-originated packets is as follows: 001, 003, 005, ... 253, 255, 001, 003, ... . Operations from the SMS Center to the application are assigned an even packet number starting from zero. Subsequent packet numbers are incremented by two. After reaching 254, the number wraps back to zero again. This means that the message packet numbering for SMS Centeroriginated packets is as follows: 000, 002, 004, ... 252 , 254, 000, 002, 004, ... . All response messages are assigned the same packet number as the request. Thus, the responses from the application to the SMS Center have even numbers and the responses from the SMS Center to the application have odd numbers. 18 (77) # Nokia Corporation dn03305755 Issue 5-0 en
Note 4.3 Checksum dn03305755 Issue 5-0 en Applications may not use the same packet sequence number more than once. The applications must always increment the sequence number by two for a new message. If an application erroneously uses the same packet sequence number repeatedly for several messages, ASE will repeat the first response to all the requests that use the same sequence number The checksum is an optional field, but when it is used you can calculate it according to the following procedure: 1. At the beginning of the message, set the checksum to 0. 2. Retrieve the first byte of the message. 3. Add the value of the byte to the checksum. 4. Truncate the checksum so that it contains only the least significant byte. 5. If available, retrieve the next byte from the message and repeat step 3. The process stops when the field is found 2 bytes further in the message. Example Checksum calculation using C language int GetChecksum ( char *pstx, char *petx ) /***************************************************/ /* pstx points to the in the message */ /* petx points to the in the message */ /***************************************************/ { int checksum = 0; char *p = pstx; while (petx - p >= 2 ) { checksum += *p; checksum &= 0xFF; p++; } return ( checksum ); CIMD protocol messages # Nokia Corporation 19 (77)
Page 1 and 2: dn03305755 Issue 5-0 en SMSCDOC8100
Page 3 and 4: Contents dn03305755 Issue 5-0 en Co
Page 5 and 6: 1 About this document This document
Page 7 and 8: 2 CIMD2 interface overview dn033057
Page 9 and 10: 3 CIMD operations The operations ar
Page 11 and 12: 3.3 Operations from the SMS Center
Page 13 and 14: dn03305755 Issue 5-0 en Table 4. Op
Page 15 and 16: 4 CIMD protocol messages 4.1 Messag
Page 17: 4.1.3 Trailer dn03305755 Issue 5-0
Page 21 and 22: 4.4.1 Positive response message Aft
Page 23 and 24: 5 Parameters related to CIMD operat
Page 25 and 26: dn03305755 Issue 5-0 en When the ap
Page 27 and 28: Note A submit to multiple destinati
Page 29: Table 13. Enquire message status pa
Page 32 and 33: Delivery Request -----> 05:007 05:
Page 34 and 35: Table 20. Negative response paramet
Page 36 and 37: 710-729 delivery not OK, message le
Page 38 and 39: 5.10 Get (09) Table 24. Set paramet
Page 40 and 41: Example Application-originated Aliv
Page 42 and 43: CIMD Interface Specification 42 (77
Page 44 and 45: Table 29. Windowing scenario 1 ASE
Page 48 and 49: Example Sending six bytes of binary
Page 50 and 51: Name ID Max Length Originated Visit
Page 52 and 53: Name ID Max Length First Delivery T
Page 54 and 55: Name ID Max Length Delivery Request
Page 56 and 57: Table 32. Parameter error codes and
Page 58 and 59: Table 32. Parameter error codes and
Page 62 and 63: Table 34. Default character convers
Page 68 and 69:
Symbol Table 35. Extension characte
Page 70 and 71:
CIMD Interface Specification 70 (77
Page 72 and 73:
Number UDH information 0B Length of
Page 74 and 75:
The DCS is coded as defined in ETSI
Page 76 and 77:
there ! How are you doing ? Submit
show all

CIMD Interface Specification - Telenor

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?