4, downlink SMS send WebService, downlink SMS Send service-feature detailed design--SMS platform

3, downlink SMS Send WebService

Develop a webservice for third-party system calls to send SMS messages. After the webservice receives the data, it stores the information into the database's SMS Send data table.

The webservice parameters include: App ID, mobile phone number (string array type), text message content, extension code (3-8 digits), priority (number 1 to 5), timed send time (nullable for instant delivery), Sender ID (ID of the internal agency Personnel Management System), sender full path.

At the same time, the development of another webservice, the same as the original old system interface, used to call the old SMS platform of the third-party system seamlessly switch to the new SMS platform.

The WebService is implemented as follows:

/// <summary>        ///Send SMS Service///success: Return Msggroup, formatted as "success:" + Msggroup///Exception: Return exception information/// </summary>        /// <param name= "Appcode" >App Identity</param>        /// <param name= "mobiles" >Phone number</param>        /// <param name= "Smscontent" >SMS Content</param>        /// <param name= "addserial" >Extension Code</param>        /// <param name= "smspriority" >Priority Level</param>        /// <param name= "Ismo" >whether to allow replies</param>        /// <param name= "Scheduletime" >Timing Time</param>        /// <param name= "Senduserid" >Sending Person</param>        /// <param name= "Senduserfullpath" >Sender Full Path</param>        /// <returns></returns>[WebMethod] Public stringSendsmswithsuccess (stringAppcode,string[] Mobiles,stringSmscontent,stringAddserial,intSmspriority =1,BOOLIsmo =trueDatetime? Scheduletime =NULL,stringSenduserid ="",stringSenduserfullpath ="")        {            //Performing checksum warehousing            stringresult =... ..returnresult; }

Where Msggroup is a unique 32-bit encoding for mobile requirements, the subsequent return of submitted reports, status reports are based on this.

WebService internal logic is first verified, including whether the application is registered, number of numbers, whether the number group includes duplicate number, whether the number has illegal characters, extension code length and so on. The officer data is then stored in the database.

Downlink SMS Data Sheet:

Sms_mt_data_info SMS Information Form
field code	Field name	Field type	Can be empty	Identity	Primary key
Msg_group	Batch Number	varchar (32)	N	N	Y
APP_CODE	App identity	VARCHAR (64)	N	N	N
Mobiles	Mobile phone Number Group	varchar (max)	N	N	N
Sms_content	SMS Content	varchar (max)	N	N	N
Add_serial	Extension code	varchar (32)	Y	N	N
Sms_priority	Priority level	Int	N	N	N
Is_mo	Do you need upstream	Bit	N	N	N
Schedule_time	Timing Time	Datetime	Y	N	N
send_user_id	Sender	varchar (36)	Y	N	N
Send_user_full_path	Sender full path	VARCHAR (512)	Y	N	N
Create_time	Creation time	Datetime	N	N	N

Sms_mt_data_his_info SMS Information History table
field code	Field name	Field type	Can be empty	Identity	Primary key
Msg_group	Batch Number	varchar (32)	N	N	Y
APP_CODE	App identity	VARCHAR (64)	N	N	N
Mobiles	Mobile phone Number Group	varchar (max)	N	N	N
Sms_content	SMS Content	varchar (max)	N	N	N
Add_serial	Extension code	varchar (32)	N	N	N
Sms_priority	Priority level	Int	N	N	N
Is_mo	Do you need upstream	Bit	N	N	N
Schedule_time	Timing Time	Datetime	Y	N	N
send_user_id	Sender	varchar (36)	Y	N	N
Send_user_full_path	Sender full path	VARCHAR (512)	Y	N	N
Create_time	Creation time	Datetime	N	N	N
Send_result	Return status	Int	N	N	N
Send_time	Send Time	Datetime	N	N	N
Has_mo	Do you have a reply?	Bit	N	N	N

4. Downlink SMS Sending Service

A windowsservice, timed access to the database, if there is data, call the Cloud MAS component to send text messages, and then move the sent text messages into the SMS Send history data table.

Since the cloud MAS platform needs to be logged in and used only once, the SDK needs to be encapsulated in a singleton mode.

Mobile Cloud MAS Platform has a certain processing logic, the specific I do not know, guess as follows: First receive the data after the mobile SMS information to review, and then submit the audited text messages to the internal sending system, the process will produce a report, internal decision if the mobile phone number, then by their own system to send text messages, There will be white list restrictions, text messages outside the whitelist can not be sent, if it is unicom or telecom mobile phone number, then call the corresponding system to send SMS, the mobile own white list is invalid, this process will produce status report.

The HTTP version of the Cloud MAS platform and the HTTP client data interaction process is as follows, for reference.

4, downlink SMS send WebService, downlink SMS Send service-feature detailed design--SMS platform