3.4.1 New Message Indications to TE +CNMI Parameter Command Syntax |Command |Possible response(s) | |+CNMI=[[,[,[,[,|+CMS ERROR: | | | | |]]]]] | | |+CNMI? |+CNMI: ,,,, | |+CNMI=? |+CNMI: (list of supported | | |s),(list of supported | | |s),(list of supported s),(list| | |of supported s),(list of supported| | |s) | Description Set command selects the procedure, how receiving of new messages from the network is indicated to the TE when TE is active, e.g. DTR signal is ON. If TE is inactive (e.g. DTR signal is OFF), message receiving should be done as specified in GSM 03.38. NOTE: When DTR signal is not available or the state of the signal is ignored (V.25ter command &D0), reliable message transfer can be assured by using +CNMA acknowledgement procedure. controls the processing of unsolicited result codes specified within this command, sets the result code indication routing for SMS- DELIVERs, for CBMs and for SMS-STATUS-REPORTs. defines the handling method for buffered result codes when 1, 2 or 3 is enabled. If ME does not support requested item (although TA does), final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. Test command gives the settings supported by the TA as compound values. NOTE: Command Select Message Service +CSMS should be used to detect ME support of mobile terminated SMs and CBMs, and to define whether a message routed directly to TE should be acknowledged or not (refer command +CNMA). Defined Values (refer figure 2; NOTE: The buffering mechanism may as well be located in the ME; the setting affects only to unsolicited result codes specified within this command): 0 Buffer unsolicited result codes in the TA. If TA result code buffer is full, indications can be buffered in some other place or the oldest indications may be discarded and replaced with the new received indications. 1 Discard indication and reject new received message unsolicited result codes when TA-TE link is reserved (e.g. in on-line data mode). Otherwise forward them directly to the TE. 2 Buffer unsolicited result codes in the TA when TA-TE link is reserved (e.g. in on-line data mode) and flush them to the TE after reservation. Otherwise forward them directly to the TE. 3 Forward unsolicited result codes directly to the TE. TA-TE link specific inband technique used to embed result codes and data when TA is in on-line data mode. NOTE: It is possible that ME/TA result code buffer is in volatile memory. In this case messages may get lost if the power of ME/TA is switched off before codes are sent to TE. Thus, it is not recommended to use direct message routing (=2 or 3, =2 or 3, or =1) with value 0 or 2. [pic] Figure 2: parameter (the rules for storing received SMs depend on its data coding scheme (refer GSM 03.38 [2]), preferred memory storage (+CPMS) setting and this value; refer table 1; NOTE: If AT command interface is acting as the only display device, the ME must support storing of class 0 messages and messages in the message waiting indication group (discard message); refer table 2): 0 No SMS-DELIVER indications are routed to the TE. 1 If SMS-DELIVER is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: +CMTI: , 2 SMS-DELIVERs (except class 2 messages and messages in the message waiting indication group (store message)) are routed directly to the TE using unsolicited result code: +CMT: [], (PDU mode enabled) or +CMT: , [],[,,,,,,, ] (text mode enabled; about parameters in italics, refer command Show Text Mode Parameters +CSDH) If ME has its own display device then class 0 messages and messages in the message waiting indication group (discard message) may be copied to both ME display and to TE. In this case, ME shall send the acknowledgement to the network (refer table 2). Class 2 messages and messages in the message waiting indication group (store message) result in indication as defined in =1. 3 Class 3 SMS-DELIVERs are routed directly to TE using unsolicited result codes defined in =2. Messages of other data coding schemes result in indication as defined in =1. Table 1: parameter | |Receiving procedure for different message data coding schemes | | |(refer GSM 03.38 [2]) | |0 |no class: as in GSM 03.38, but use as preferred memory | | |class 0: as in GSM 03.38, but use as preferred memory if | | |message is tried to be stored | | |class 1: as in GSM 03.38, but use as preferred memory | | |class 2: as in GSM 03.38 | | |class 3: as in GSM 03.38, but use as preferred memory | | |message waiting indication group (discard message): as in GSM | | |03.38, but use as preferred memory if message is tried to | | |be stored | | |message waiting indication group (store message): as in GSM | | |03.38, but use as preferred memory | |1 |as =0 but send indication if message stored successfully | |2 |no class: route message to TE | | |class 0: as in GSM 03.38, but also route message to TE and do not| | |try to store it in memory | | |class 1: route message to TE | | |class 2: as =1 | | |class 3: route message to TE | | |message waiting indication group (discard message): as in GSM | | |03.38, but also route message to TE and do not try to store it in| | |memory | | |message waiting indication group (store message): as =1 | |3 |class 3: route message to TE | | |others: as =1 | Table 2: SMS-DELIVER result code and acknowledgement summary | |no class or |class 0 or |class 2 or |class 3 | | |class 1 |message waiting |message waiting| | | | |indication group|indication | | | | |(discard) |group (store) | | |1 |+CMTI |[+CMTI1)] |+CMTI |+CMTI | |2 |+CMT & +CNMA3)|+CMT [& +CNMA2)]|+CMTI |+CMT & +CNMA3) | |3 |+CMTI |[+CMTI1)] |+CMTI |+CMT & +CNMA3) | |1) result code is sent when ME does not have other display device | |than AT interface | |2) acknowledgement command must be sent when +CSMS value | |equals 1 and ME does not have other display device than AT interface | |3) acknowledgement command must be sent when +CSMS value | |equals 1 | (the rules for storing received CBMs depend on its data coding scheme (refer GSM 03.38 [2]), the setting of Select CBM Types (+CSCB) and this value; refer table 3): 0 No CBM indications are routed to the TE. 1 If CBM is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: +CBMI: , 2 New CBMs are routed directly to the TE using unsolicited result code: +CBM: (PDU mode enabled) or +CBM: ,,,, (text mode enabled) If ME supports data coding groups which define special routing also for messages other than class 3 (e.g. SIM specific messages), ME may choose not to route messages of such data coding schemes into TE (indication of a stored CBM may be given as defined in =1). 3 Class 3 CBMs are routed directly to TE using unsolicited result codes defined in =2. If CBM storage is supported, messages of other classes result in indication as defined in =1. Table 3: parameter | |Receiving procedure for different message data coding schemes | | |(refer GSM 03.38 [2]) | |0 |all schemes: as in GSM 03.38; if CBM storage is supported, store | | |message to "BM" (or some manufacturer or data coding scheme | | |specific memory) | |1 |all schemes: as =0 but send indication if message stored | | |successfully | |2 |all schemes: route message to TE unless ME has detected a special | | |routing to somewhere else (e.g. to SIM; an indication may be sent | | |if message stored successfully) | |3 |class 3: route message to TE | | |others: as =1 (if CBM memory storage is supported) | : 0 No SMS-STATUS-REPORTs are routed to the TE. 1 SMS-STATUS-REPORTs are routed to the TE using unsolicited result code: +CDS: (PDU mode enabled) or +CDS: ,,[],[],,
, (text mode enabled) 2 If SMS-STATUS-REPORT is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: +CDSI: , Table 4: SMS-STATUS-REPORT result code and acknowledgement summary | |result codes and commands | |1 |+CDS & +CNMA1) | |2 |+CDSI | |1) acknowledgement command must be | |sent when +CSMS value | |equals 1 | : 0 TA buffer of unsolicited result codes defined within this command is flushed to the TE when 1...3 is entered (OK response shall be given before flushing the codes). 1 TA buffer of unsolicited result codes defined within this command is cleared when 1...3 is entered. Implementation Mandatory when any of the new message indications implemented.