CIMD Interface Specification - Elisa

More documents

Recommendations

Info

CIMD Interface Specification Section CIMD protocol messages introduces the question of how to communicate between the SME and the MC, that is, the coding of information related to operations and parameters. The parameters are specified in section CIMD parameters of this document. Note 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 document, the operations and the parameters specified for each operation represent the maximum amount of information the SME or the MC may provide. It is very important to notice that in most cases it is not reasonable for the SME to send all the possible parameters. 14 (74) © Nokia Corporation DN99255924 Nokia Proprietary and Confidential Issue 5a-0 en
3 CIMD operations 3.1 SME types CIMD operations This section defines the operations between the SME and the MC. The parameters related to each operation are specified in Chapter 5 Operation details and the values of the parameters are specified in Chapter 7 CIMD parameters. The operations are divided into operations originated by the SME, operations originated by the MC, and operations that can be originated by both the SME and the MC. When defining the operations the different SMEs might use, three basic types of SMEs can be distinguished: 1. Send-only SMEs. 2. Querying SMEs. 3. Receiving SMEs. A send-only SME can only submit messages to the MC. The short messages are destined to MSs or other SMEs. Status reports of sent messages must be requested by the SME explicitly. A querying SME does not receive anything from the MC automatically, but merely queries if there is something to be retrieved. The application can retrieve messages coming from mobile stations, but only on demand. The SME is typically connected to the MC 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 SME is a PC application with a modem connection to the MC. Status reports, if desired, must be requested by the SME explicitly. Note that, due to the nature of USSD, querying type of SMEs are not supported for USSD Center connections, as the USSD Center will not store messages nor status reports for later retrieval by the SME. A receiving SME is always ready to receive messages if the MC has something to send to it (that is, messages or status reports). A receiving SME can automatically receive messages stored in the MC, when logging in to the MC. This allows fast two-way message exchange between the SME and MC. DN99255924 © Nokia Corporation 15 (74) Issue 5a-0 en Nokia Proprietary and Confidential
Page 1 and 2: Nokia Artuse SMS Center Release SC5
Page 3 and 4: Contents Contents 3 List of tables
Page 5 and 6: List of tables Table 1. Operations
Page 7 and 8: List of figures Figure 1. CIMD prot
Page 9 and 10: Summary of changes Changes between
Page 11 and 12: 1 About this document Note 1.1 Scop
Page 13: 2 Overview Overview A short message
Page 17 and 18: Operation Definition Table 2. Opera
Page 19 and 20: 4 CIMD protocol messages 4.1 Messag
Page 21 and 22: Example 1. Password parameter (11)
Page 23 and 24: while (petx - p >= 2 ){ checksum+=
Page 25 and 26: 4.4.4 General error response messag
Page 27 and 28: 5 Operation details Symbol Meaning
Page 29 and 30: Operation details The submitted mes
Page 31 and 32: 021:22222060:971107131212021:333900
Page 33 and 34: Table 16. Negative response paramet
Page 35 and 36: Delivery Request -----> 05:007 05:
Page 37 and 38: Positive response for cancel messag
Page 39 and 40: 5.9 Set (08) Operation details The
Page 41 and 42: Negative response will follow if th
Page 43 and 44: 03:001021:daddr033:Data 03:009021:
Page 45 and 46: 6 Windowing for applications Window
Page 47 and 48: 6.2 Restrictions Table 32. Windowin
Page 49 and 50: 7 CIMD parameters 7.1 Parameter typ
Page 51 and 52: 7.2 Parameters Name ID Max Length C
Page 53 and 54: Name ID Max Length Message Type (#)
Page 55 and 56: Name ID Max Length Status Report Re
Page 57 and 58: Name ID Max Length 7.3 Error codes
Page 59 and 60: Error code Error text 321 Incorrect
Page 61 and 62: Value Meaning 88 The MS purged for
Page 63 and 64: Character conversion for user data
Page 65 and 66:
Character conversion for user data
Page 67 and 68:
Character conversion for user data
Page 69 and 70:
Symbol ] Closing bracket ~ Tilde \
Page 71 and 72:
9 Example sessions 9.1 Example sess
Page 73 and 74:
Deliver Message 70:002 Example ses
show all

CIMD Interface Specification - Elisa

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

Delete template?

Save as template?