SMS PDU SMS Receipt settings

One of the things that I used to do, to sort out the data. Today I studied the SMS PDU format for a morning and found a way to set up SMS receipts in the PDU string. It's in Pdu-type. This 8-bit group is generally set to 11: Contains TP-MTI (2bit), Tp-rd (1bit), TP-VPF (2bit), TP-RP (1bit), Tp-udhi (1bit), TP-SRR (1bit)
Binary representation: 0 0 0 10 0 01
Tp-mti:01
Tp-message-type-indicator (Message type indicator)
bit1,0:01 Indication for Sms-submit type
tp-rd:0
Tp-reject-duplicates (whether to reject the same duplicate message)
bit2:0 instructs the short message center to accept messages with the same TP-MR that are not forwarded.
Tp-vpf:10
Tp-validity-period-format (Expiration format)
Bit4,3:10 indicates the use of relative formatting.
tp-srr:0
Tp-status-report-request
Bit5:0 indicates that the status report is not used.
tp-udhi:0
Tp-user-data-header-indicator (User Data header Designation)
Bit6:0 indicates that this is an SMS message with no user data header. EMS messages need to be set.
tp-rp:0
Tp-reply-path (reply path)
Bit7:0 indicates that no reply path is set.

Only need to set BIT5 to 1 to receive the receipt is Pdu-type 11 points around the GSM modem hand immediately connected to the computer to start testing, the results make me cry ah ... N has not received a receipt. Had to check the information, while opening SMS with the Sms pdu-mode and Hesicong greatly there to find the development of the document began to chew, haha! Emperor. Finally found a message to receive the relevant at command At+cnmi=<mode>,<mt>,<bm>,<ds>,<brf>
parameter:
 mode:
 0--cached in terminal
 1--sent directly to TE
MT:
 0--receive new SMS does not return an event
 1--returns
  if received SMS stored in NA    +cmti:<mem>,<index>
 2--In addition to Class2 SMS, the new SMS is sent directly to the terminal, returning:
   &NBSP;+CMT:<LENGTH><CR><LF><PDU>
 3--class3 SMS uses mt=2 methods to return, and other types of methods that use Mt=1 are returned.
BM:
 0--Cell Broadcast does not notify
 2--new cell broadcast notification, return
    +CBM:<length><CR> <lf><pdu>
&NBSP;3--CLASS3 format cell broadcast notification, using bm=2 format
ds:
 0--Status Report does not notify
 1--new status Report notification, returns:
   +cds:<length><cr><lf><pdu>
 2--returns if the new status report is stored to me:
  +cdsi:<mem>,<index>
BRF:
 1--always 1

Open HyperTerminal input
At+cnmi again?
+cnmi:0,1,0,0,0
is a problem here.
Follow the previous mode definition
Reset CNMI
at+cnmi=1,1,0,1,1
OK
and send a text message back to OK after about 5s terminal returned
+cds:26
0006320d91683161721356f6506071415354005060714153640000
First paragraph 000632 meaning is not very clear (who knows the trouble to tell a lot)
0D receiver number length
683161721356f6 receiver number
50607141535400 the time that information arrives in the SMS center (I guess)
5060714153640000 the time (also guessed) that the message was sent to the receiver
The next thing to do is to receive the receipt of the cell phone number to parse out, you can carry out statistical analysis of the
current problem is almost solved, but the estimated encoding time will still produce a lot of problems, then
again