CIMD Interface Specification - Telenor

More documents

Recommendations

Info

Note CIMD Interface Specification In some cases the operator may want to restrict the use of some parameters. These are configured by the operator in the interface profiles. In this interface specification, the operations and the parameters specified for each operation represent the maximum amount of information the application or the SMS Center may provide. It is very important to notice that in most cases it is not reasonable for the application to send all the possible parameters. 8 (77) # Nokia Corporation dn03305755 Issue 5-0 en
3 CIMD operations The operations are divided into operations originated by the application, operations originated by the SMS Center, and operations that can be originated by both the application and the SMS Center. The parameters related to each operation are specified in Parameters related to CIMD operations, and the values of the parameters are specified in CIMD parameters in CIMD Interface Specification (PDF). 3.1 Application types dn03305755 Issue 5-0 en CIMD operations The type of the application must be specified before the application may operate. The type, along with other information about the application, is stored in the SMS Center. When defining the operations the different applications might use, three basic types of applications can be distinguished: 1. Send-only applications that can only submit messages to the SMS Center. The messages can be destined to mobile stations. Status reports of the sent messages must be explicitly requested by the application. 2. Querying applications that do not receive anything from the SMS Center automatically, but make queries if there is something to be retrieved. The application can retrieve messages coming from mobile stations, but only on demand. The application is typically connected to the SMS Center every now and then to submit a message and may at the same time also check if there is something to be received. An example of this kind of application is a PC application with a modem connection to the SMS Center. Status reports, if desired, must be explicitly requested by the application. 3. Receiving applications that are always ready to receive messages if the SMS Center has something to send to it (that is, messages or status reports). A receiving application can automatically receive messages stored in the SMS Center, when logging in to the SMS Center. This allows fast two-way message exchange between the application and SMS Center. The receiving applications can also be set up in such a way that when connected to an # Nokia Corporation 9 (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: 2 CIMD2 interface overview dn033057
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 and 18: 4.1.3 Trailer dn03305755 Issue 5-0
Page 19 and 20: Note 4.3 Checksum dn03305755 Issue
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 46 and 47: CIMD Interface Specification 46 (77
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 60 and 61:
CIMD Interface Specification 60 (77
Page 62 and 63:
Table 34. Default character convers
Page 64 and 65:
Page 66 and 67:
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

Create successful ePaper yourself

Delete template?

Save as template?