SP messaging development - the basis of knowledge articles
Source: Unknown
The topic is soil, but recently helped a friend do this thing, so write something up for reference for beginners.
First, prepare the information
SP development site there are a lot of information, but primarily the following documents:
1, MISC1.6 SP order to inform the interface requirements
2, SMPP protocol
3, MISC SMS SP system access training (Starter Edition). Ppt
4, DSMP norms regulate the SSO platform access details v1.5.1.pdf
5, for the SP to view the error code
6, DSMP norms regulate access to the SSO platform. Pdf
7, the Internet CMPP V3.0
II, Short Message Service Category
SMS main two kinds, one is the on-demand business, is another custom business
1, on-demand business
Not in front of their service_id - No. For example, YLSH
Description: billing codes, and what is a service_id
Mobile phone users have sent messages, sp issued to information, mobile uplink based on a distribution of a linkid, a certain amount of time sp issued to give him information may be issued a number of information, but each message is the same linkid
, One can take a linkid billing code (this is declared in the mobile, with this code扣费, 1 yuan or two yuan, or N-)
For example, a cell phone made a 13912345678 uplink information A, the command is declared in the mobile, misc platform through him, then returned to the linkid assigned a sp, sp instructions A judge in accordance with what the business users, and then to the user under the
Fat information must be issued to bring information and billing lingkid code can not be issued, for example, issued three, each linkid and billing information are the same code (because there is only one uplink user commands), so in fact, made a 3 Although sp
Be deducted only to the cost of a. Linkid and billing with code only in order to ensure the success of information issued by a parameter. So all the business, on-demand, as well as the back of that custom
2, customized business:
Its front service_id - number, for example-YLQTYX
Mobile phone users sent a message, after authentication misc, admitted that he was willing to use custom business, he will be customized as the user, and then, even if users do not have to issue information, sp can also take the initiative to issue him with information, this time on the not allocated
linkid, but service_id, that is, billing code information for each issue must be brought before the service_id.
He also divided into two categories
1), customized in accordance with Article
sp relations can be ordered to have issued the user information, the user received each one service_id marked in accordance with扣费charges, a month, deducted up to 10 users, more than 10 yuan in part, or whether they need service_id issued with only
Mobile no longer扣费(that part, sp do not need to pipe)
2), monthly business
sp relations can be ordered to have issued the user information, all information should be issued with service_id,扣费initiated by the mobile, sp regardless.
Third, the development of technology
As long as the first point of agreement to meet and regulatory requirements, with the current development of the popular database language and can do so.
1, the key is the network programming, and programming SOAP
2, the relevant terms explained
MISC (Mobile Information Service Center Mobile Information Service Center) is a completely in line with China's mobile data service management platform technical specifications (DSMP) operating platform of the data, it completed the operational data management and control of reactive power
Able, user management, business management and SP management, provide an open, uniform standard Web Service interface, and can be the gateway for all business, SP-generation billing provided.
SMPP Interface Protocol is included in the initial GSM03.39 by ETSI specification, describes the short message center and a short message communications between the entities, relations and interactive data transmission protocol format, the SMPP interface protocol specification for a description of
Mainly for simple communications interaction, manufacturers will be to develop a standardized version of its agreement for V3.30; by the developer SMPP protocol version will forward the Forum has evolved into the V3.40, SMPP V3.40 protocol specification is fully compatible with G
SM 03.39 protocol standard. This specification, using SMS Short Message Center equipment and stock business processing platform interface between the protocol used GSM03.39 V3.30, in the absence of special note to the Association all
Norms that prevail. SMPP protocol can be TCP / IP or X.25 communication as the bottom bearing.
ISMG Intenet Short Message Gateway Internet Short Message Gateway
DSMP Data Service Manage Platform data service management platform
SMPP Short Message Peer to Peer Protocol Short Message Peer-to-Peer
CMPP China Mobile Peer to Peer China Mobile Point to Point Protocol
CMPP agreement to provide the following main types of business operations:
(1) SMS (Short Message Mobile Originate, SM MO)
Please refer to the process in detail "Monternet signaling processes regulate SMS V3.0.0";
(2) to receive SMS (Short Message Mobile Terminated, SM MT)
Please refer to the process in detail "Monternet signaling processes regulate SMS V3.0.0";
SMSC Short Message Service Center Short Message Center
GNS Gateway Name Server Gateway Name Server (Tandem Gateway)
SP Service Provider Service Provider
Gateway ISMG_Id code: 0XYZ01 ~ 0XYZ99, which is the capital of XYZ code, the median less than zero when the left, such as the Beijing No. 1 gateway code 001001, Jiangxi No. 1 gateway code 079101, and so on
Corporate code SP_Id SP: SP network address and the identity of the logo, address translation, billing, settlement and so on are based on enterprise code. Code to the number of enterprises said that a total of six, from "9XY000" to "9XY999", which "
XY "code for the mobile company
Service code SP_Code SP: Service code is the way in the use of SMS in the upstream business, available to users of the service provider code. Service code figures said the length of operational service code 4, that is, "1000
"-" 9999 "; local business services unified code length 5, that is," 01000 "-" 09999 "; MII for the new service code of the SP allocation of a new request to" 1061 "-" 1069 "As a prefix, the current shift in China
Dynamic distribution as follows:
1062: SP services for the province code
1066: SP services for the country code
Other No. retain paragraph.
Service_Id SP business types, numbers, letters and symbols by the SP custom, such as the picture may be set for Regards TPCQ, stock query can be defined as 11
DSMP data management platform
SSO Single Sign On, Single Sign -
HTTP Hyper Text Transfer Protocol, Hypertext Transfer Protocol.
HTTPS Hyper Text Transfer Protocol over Secure Socket Layer, Secure Sockets Layer based on the Hypertext Transfer Protocol.
ICP Internet Content Provider, Internet content providers
WWW World Wide Web
XML eXtensible Markup Language, Extensible Markup Language
Session refers to the process of HTTP access to a complete course of conversation
Internet Short Message Gateway (ISMG) is a service provider (SP) and mobile network SMSC intermediary entity between the Internet gateway, on the one hand responsible for receiving text messages sent to mobile users SP information and submitted to the SMS Center. On the other hand, mobile
SP-demand business users of information centers will be SMS Gateway SMS sent via the Internet SP. In addition, short message center in order to reduce signaling load, the Internet messaging gateway should be in accordance with the principle of routing information will be submitted SP forwarded to the appropriate Internet Short
Gateway letter. SMS Gateway Internet Gateway to the aggregation (GNS) query access gateway routing information between the transponder.
In addition, ISMG also be DSMP data management platform to connect, in the business processes of customers, the relationship between business and ordered to carry out the operations of authentication and grant price.
3, interface naming convention
Interface name using the first letter of the word capital, the way other letters lowercase. Abbreviations in all capital letters; interface with parameters and information
Allow definition of the basic data type of field naming convention using the first letter of the word capital, there is no connection between the word at the way; for a single abbreviation
Words, such as ID, URL, ICP, MSISDN, etc., will be uniform application of capital.
SSO platform for user ownership of land is actually part of DSMP function. When users log on to the ownership of the need to redirect users to DSMP on self-service portal, regardless of SP or the entire network of local SP, are vested in the user's SSO user boarding platform
Recorded, and the completion of Session management, user subscription information is stored in the attribution to DSMP platform and user authentication to complete by the attribution to DSMP. Therefore, SP needs and access to the SSO platform in order to complete the management of Session.
At the same time, in various SSO platforms, but also requires a mechanism for the management and synchronization between the user data need to ensure that SSO user data in any platform can be. To achieve this requirement, it is recommended the use of centralized control, all the points by
Means to be synchronized, which is deployed throughout the DSMP structure there is a central node, a central repository of all user login data, the SSO platform provinces need to log in the user through the user redirected to the central SSO Ping
Log in Taiwan to complete the operation. See below in the specific process of the user registry, business purchase / on-demand and user processes that sign back.
Fourth, the relevant data
1, SyncOrderRelationReq
<? xml version = "1.0" encoding = "utf-8"?>
<SOAP-ENV: Envelope xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance"
xmlns: xsd = "http://www.w3.org/2001/XMLSchema"
xmlns: SOAP-ENV = "http://schemas.xmlsoap.org/soap/envelope/"
xmlns: SOAP-ENC = "http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Header>
<TransactionID Xmlns="http://www.monternet.com/dsmp/schemas/"> 00110338785301 </ TransactionID> the source code
</ SOAP-ENV: Header>
<SOAP-ENV:Body>
<SyncOrderRelationReq Xmlns="http://www.monternet.com/dsmp/schemas/">
<Version> 1.5.0 </ Version> the interface version number information
<MsgType> SyncOrderRelationReq </ MsgType> Message type
<Send_Address> Sender's address
<DeviceType> 0 </ DeviceType> device type 0: DSMP
<DeviceID> 0011 </ DeviceID> device ID
</ Send_Address>
The recipient's address <Dest_Address> use user ID when using the user and billing the user for the same time users, FeeUser_ID and DestUser_ID the same value.
<DeviceType> 400 </ DeviceType> device type 400: SP
<DeviceID> 0 </ DeviceID> device ID
</ Dest_Address>
Billing <FeeUser_ID> User ID
<UserIDType> 1 </ UserIDType> User ID type 1: identification number using a mobile phone
<MSISDN> 13912345678 </ MSISDN> user mobile phone number
<PseudoCode> </ PseudoCode> pseudo-code users
</ FeeUser_ID>
<DestUser_ID> The use of user ID
<UserIDType> 1 </ UserIDType> User ID type 1: identification number using a mobile phone
<MSISDN> 13912345678 </ MSISDN> user mobile phone number
<PseudoCode> </ PseudoCode> pseudo-code users
</ DestUser_ID>
<LinkID> SP </ LinkID> Provisional Order ID affairs
<ActionID> 2 </ ActionID> state management service action code, specific values are as follows: 1: open services; 2: stop services; 3: activation of services; 4: suspended;
<ActionReasonID> 1 </ ActionReasonID>
ActionReasonID: state management services have a cause of action code, specific values are as follows: 1: client-initiated behavior management services to state causes of action code, specific values are as follows:
1: client-initiated behavior
2: Admin & 1860 initiated act
3: Boss stands
4: Boss Boot
5: Boss transfer
6: Boss households sell
7: Boss Number
8:扣费service failure caused by the abolition of
9: Other
<SPID> 419613 </ SPID> SP corporate code
<SPServiceID>-LTYLBY </ SPServiceID> SP in the service code, label the contents of each type of business, and is also called the billing code, business code
<AccessMode> 3 </ AccessMode> services access 3: SMS 2: WAP 1: WEB
<FeatureStr> MTA2NjIxNDQgVERBRA == </ FeatureStr> services ordered parameters, encoded using BASE64
</ SyncOrderRelationReq>
</ SOAP-ENV: Body>
</ SOAP-ENV: Envelope>
2, SyncOrderRelationResp
<SOAP-ENV: Envelope
xmlns: SOAP-ENV = "http://schemas.xmlsoap.org/soap/envelope/"
xmlns: SOAP-ENC = "http://schemas.xmlsoap.org/soap/encoding/"
xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance"
xmlns: xsd = "http://www.w3.org/2001/XMLSchema" xmlns: dsmp = "http://www.monternet.com/dsmp/schemas/">
<SOAP-ENV:Header>
<dsmp:TransactionID xmlns:dsmp="http://www.monternet.com/dsmp/schemas/">
<% = TransactionID%>
</ dsmp: TransactionID> the source code
</ SOAP-ENV: Header>
<SOAP-ENV:Body>
<dsmp:SyncOrderRelationResp xmlns:dsmp="http://www.monternet.com/dsmp/schemas/">
<MsgType> SyncOrderRelationResp </ MsgType>
<Version> <% = Version%> </ Version> the interface version number information, the interfaces of all the versions of the news as "1.5.0
<hRet> <% = hRet%> </ hRet>
</ dsmp: SyncOrderRelationResp>
</ SOAP-ENV: Body>
</ SOAP-ENV: Envelope>
3, cancellation of service request packet
Reverse the abolition of the process described:
Reverse the abolition of SP was launched from the cancellation of the process, MISC from the SP in dealing with news of the cancellation, the process and from other network elements to deal with the news the same, process as follows:
(0) SP in place of the user to cancel the request MISC launched UnSubscribeServiceReq back and wait for MISC processing;
(0) MISC source of the message address, enterprise authentication code to determine whether or not to allow reverse the abolition of the SP;
(0) after a successful access authentication, user authentication and re-ordering the relationship between authentication to determine whether the correct user status and the relationship between the existence of order;
(0) above authentication is successful, MISC to the SP to send a request to order the relationship between synchronization packets SyncOrderRelationReq;
(0) SP received synchronization request, the request for order cancellation and do the deal, and ordered to return to the relationship between response synchronization SyncOrderRelationResp;
(0) MISC response received after the response to determine whether the value is 0. If the response value is 0, then in order to remove the relationship between MISC and the success of the SP to return to reverse the abolition of the response packet processing UnSubscribeServiceResp; If the response value is 0, then
Ordered not to lift the relationship to the SP failed to return to reverse the abolition of the response packet UnSubscribeServiceResp;
(0) SP error MISC if the response received, then the abolition of the failure, SP must be done on the failure of the corresponding information processing, such as the order has been canceled to resume relations, etc.;
(0) MISC if you receive the correct response, the SP can not do anything to deal with;
<? xml version = "1.0" encoding = "UTF-8"?>
<SOAP-ENV: Envelope xmlns: SOAP-ENV = "http://schemas.xmlsoap.org/soap/envelope/" xmlns: SOAP-ENC = "http://schemas.xmlsoap.org/soap/encoding/"
xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns: xsd = "http://www.w3.org/2001/XMLSchema" SOAP -
ENV: encodingStyle = "http://schemas.xmlsoap.org/soap/encoding/" xmlns = "http://www.monternet.com/dsmp/schemas/">
<SOAP-ENV:Header>
<TransactionID Xmlns="http://www.monternet.com/dsmp/schemas/" xsi:type="xsd:string"> 9130020301801050 </ TransactionID> the source code
</ SOAP-ENV: Header>
<SOAP-ENV:Body>
<UnSubscribeServiceReq Xmlns="http://www.monternet.com/dsmp/schemas/">
<Version> 1.5.0 </ Version>
<MsgType> UnSubscribeServiceReq </ MsgType> Message type
<Send_Address> Sender's address
<DeviceType> 400 </ DeviceType>
<DeviceID> 913002 </ DeviceID>
</ Send_Address>
<Dest_Address> The recipient's address
<DeviceType> 0 </ DeviceType>
<DeviceID> 0024 </ DeviceID>
</ Dest_Address>
Billing <FeeUser_ID> User ID
<UserIDType> 1 </ UserIDType> See below the definition of
<MSISDN> 13805002424 </ MSISDN> user mobile phone number
<PseudoCode />
</ FeeUser_ID>
<DestUser_ID> Use user ID when using the user and billing the user for the same time users, FeeUser_ID and DestUser_ID the same value.
<UserIDType> 1 </ UserIDType>
<MSISDN> 13805002424 </ MSISDN>
<PseudoCode />
</ DestUser_ID>
<Service_ID> Service marks of
<ServiceIDType> 1 </ ServiceIDType>
<SPID> 913002 </ SPID>
<SPServiceID>-TQAAU </ SPServiceID>
<AccessNo />
<FeatureStr />
</ Service_ID>
<FeatureStr />
</ UnSubscribeServiceReq>
</ SOAP-ENV: Body>
</ SOAP-ENV: Envelope>
In response to the abolition of service package
<? xml version = "1.0" encoding = "UTF-8"?>
<SOAP-ENV: Envelope xmlns: SOAP-ENV = "http://schemas.xmlsoap.org/soap/envelope/" xmlns: SOAP-ENC = "http://schemas.xmlsoap.org/soap/encoding/"
xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns: xsd = "http://www.w3.org/2001/XMLSchema" xmlns: dsmp = "http://www .monternet.com / dsmp / schemas / ">
<SOAP-ENV:Header>
<dsmp:TransactionID xmlns:dsmp="http://www.monternet.com/dsmp/schemas/"> 9130020301801050 </ dsmp: TransactionID>
</ SOAP-ENV: Header>
<SOAP-ENV:Body>
<UnSubscribeServiceResp Xmlns="http://10.1.2.122/misc/dsmp.xsd">
<Version> 1.5.0 </ Version>
<MsgType> UnSubscribeServiceResp </ MsgType>
<hRet> 0 </ hRet> return value: see definition below
</ UnSubscribeServiceResp>
</ SOAP-ENV: Body>
</ SOAP-ENV: Envelope>
4, the definition of return value
Communication at the time of the HTTP status code please refer to the provisions of the agreement HTTP/1.1 status code values are not included in this
Regulate the return value of a unified definition.
Specifically described as follows:
0: Successful
1: Unknown error
2-99: reservations
MISC and 4000-4999 for the interface between the SP of the error code message:
4000: Invalid msgtype
4001: Invalid action_id;
4002: Invalid action_reasonid;
4003: SP ID invalid
4004: Invalid serviceID
4005: Invalid pseudocode
4006: Invalid accessmode
4007: MISC opened simultaneously, but SP has been in existence for ordering the relationship between client and state for the opening of
4008: MISC simultaneous opening of service, and ordered SP client relationship does not exist, but fail to open service
4009: MISC opened simultaneously, but SP has been in existence for ordering the relationship between client and for the suspension of state
4010: MISC simultaneously closed, and the existence of SP-side order, but the abolition of service failure
4011: MISC synchronous stop service, but ordered SP client relationship does not exist
4012: MISC simultaneous suspension of services, and the existence of SP-side order, but suspended service failure
4013: MISC simultaneous suspension of service, but ordered SP client relationship does not exist
4014: MISC suspended simultaneously, but SP has been in existence for ordering the relationship between client and for the suspension of state
4015: MISC synchronous activation of services, but SP has been in existence for ordering the relationship between client and state for the opening of
4016: MISC synchronous activation of service, but ordered SP client relationship does not exist
4017: MISC synchronous activation of services, and the existence of SP-side order, but failed to activate service
9000-9999 for system-level error:
9000: read and write system disk error
9001: Network Anomaly
9002: Network error
9003: Business Gateway is busy, the business gateway cache
9004: Business Gateway is busy and full business gateway buffer, MISC cache and not to send a message,
Wait and try again.
9005: MISC busy, MISC cache
9006: MISC busy over the buffer zone and MISC, the business gateway cache and not to send a message and wait for some time and try again.
9007: Business Gateway over the prescribed limit the flow of
9008: MISC anomaly is not available
9009: Business Gateway anomaly is not available
9010: The business does not have permission to call the gateway interface information
9011: MISC does not have permission to send the message to the business interface gateway
9012: Version does not support
Page 6
Reverse MISC SP business interface
9013: Message type is not, the system does not support
9014: authentication error, can not resolve the structure of SOAP and XML, the lack of the field must exist, or information not in the correct format
9015: Refusal of information, the server can not complete the requested service
5, DeviceType definition
Device type
0: DSMP
100: ISMG
101: WAP SP PROXY
1XX: other business gateway
200: WAP PORTAL
201: WWW PORTAL
202: VOICE PORTAL
203: PDA PORTAL
2XX: other portal
300: MMSC
301: KJAVA SERVER
302: LSP
3XX: other application platform
400: SP
6, DeviceID definition
Equipment number, equipment number of the network using the device ID, such as the SMS gateway using the gateway ID, on the SP to use its enterprise code, the device ID from DSMP distribution, and in the same device type in the code only
7, UserIDType the definition of
User ID Type
1: identification number using a mobile phone
2: The pseudo-code marking
3: both ID
8, SPType
SP business types
1: All SP
2: the provision of SMS services, SP
3: SP to provide WAP services
4: SP to provide MMS services
5: KJAVA services provided by SP
6: MAIL services provided by SP
7: the provision of LBS services, SP
8: the provision of WWW services, SP
9 ~: expansion
9, ServiceIDType
Logo type of service by:
1: SPID + SPServiceID
2: AccessNo + FeatureStr
5, MISC match of MO business process description
Handling Description:
1, SP business applications, in accordance with the different types of business operations to fill orders, according to different types of business, there may be "ordering instructions, cancellation of orders, on-demand instruction and the general MO" 4 species command mode, setting directions, need to refer to
Will be sent instructions corresponding number (long number) and the content of directive and assigned number and instructions to send content to match needs to be done accurately.
Exact matching means that the match only if the content and the need for exactly the same instruction set (including the same length), the only match. For example, if set up to send the number to "800101", only when a user send a MO to
"80010123" will not match the "800101" of that instruction; only sent to "800101" and the command will be matched.
【Note】 a directive for the same model, each service can set up more than, for example, a service can be set up instructions and 5 order cancellation instruction 5, the current MISC can support more than five instructions, but from the convenience of the management point of view, For the same
A mode of instruction, it is recommended not to SP set up more than 5 hours.
2, the user's MO message from the two parts: sending number and send the contents of application coupled with the business model set up to match, these three constitute the basis for matching.
3, when a MO at the MISC for authentication, MISC first send the number (L number) match, in accordance with the maximum matching + the principle of exact match. If there is a successful match, then took out the corresponding command code and the type of business; if the horse
Not good enough, then authentication fails, the MO will not be issued to SP.
4, in the previous step from the list of matches, and then match the content of directive, but also the biggest match + in accordance with the principles of exact match. If there is to match the results, then remove the corresponding code and command the type of business; if there is no will
Corresponds to the results of the match, then the value of Service ID to return to space, at the same time to inform the SMS text messages as a gateway to this common MO transmitted to the SP.
5, SP in order to fill orders MO is to avoid nested commands (for example, the existence of "888801" and "8888011" and AccessNO).
6, to match the success of the Directive, MISC out in accordance with the instructions to match the patterns are different, the treatment is as follows:
? For ordering instructions, while MISC will check whether the user has been ordered by the service, if there is no order, the order will be completed MISC, MO At the same time, users will be content to order the relationship between the user interface data synchronization (Provision interface
) Transmitted to the SP, in the Provision field FeatureStr interface users will have long-MO number and content of instruction, the contents of a long number and instructions will be a space between the delimited. MISC will be notified at the same time this is a short message gateway ordering instructions, short
Letter to the SP gateway will not be forwarded to the MO.
If the user has been ordered by the service, the type of services for a monthly subscription, MISC will be the general MO as MO SMS Gateway to return to the successful outcome of the authentication, SMS Gateway will notice this as a general MO SMS forwarding to the SP; custom category for a monthly subscription service,
While MISC will demand the type of MO as MO SMS Gateway to return to the successful outcome of the authentication, notification SMS text messages as a gateway to this demand to the SP transmitted MO.
? As for the cancellation of orders, while MISC will check whether the user has been ordered by the service, if you have ordered, you will be able to complete abolition of MISC, MO At the same time, users will be content to order the relationship between the user interface data synchronization (Provision interface
) Transmitted to the SP, in the Provision field FeatureStr interface users will have long-MO number and content of instruction, the contents of a long number and instructions will be a space between the delimited.
If the user did not order the service, MISC will return to the SMS gateway authentication failure message to the SP gateway will not be forwarded to the MO.
? Instructions for on-demand, MISC need to determine the type of business is custom on-demand on-demand business or general business
1) For customized on-demand business, users need to determine whether the service has been ordered, if ordered, it will generate the provisional order MISC relations (LinkID), at the same time to return to the SMS gateway authentication success, and returned to the SMS network LinkID
Clearance from the MO short message gateway to the SP as an on-demand forwarding MO; if the user did not order, then MISC simply return to the SMS Gateway in response to successful authentication, SMS Gateway will notice this as an ordinary SMS MO to SP forward.
2) In the case of on-demand business, while MISC will have a direct relationship between the generation of the provisional order (LinkID), at the same time to return to the SMS gateway authentication success, and returned to the LinkID SMS gateway, SMS gateway from the MO as MO to the SP-demand forward.
? For ordinary MO SMS, MISC to return to the SMS Gateway in response to successful authentication, notification SMS text messages as a gateway to this common MO forward to the SP.
Example Description:
seq AccessNO FeatureStr ANCheckFlag FSCheckFlag
1 8888 xw 1 0
2 888801 xw 0 0
3 888801 xw1 0 1
4 8888 01xw 1 1
5 8888 (null) 0 0 (HELP)
【Note】 AccessNO that sent the number of MO
That the content of directive FeatureStr
ANCheckFlag expressed whether or not to use exact match AccessNO
That the content of directive FSCheckFlag whether or not to use exact match
For the above settings,
Xw1 send to 8888011, we match the first three records
Send xw01 to 888,801 users and we will match the first two records (access to matching its longest)
Users to send 888,802 of our 01xw to match the first five records (will not be matched to the first four records, because the first four records are exact match AccessNO)
01xw send to 8888, we match the first four records
Xw01 send to 8888 to match the first one we recorded
A send to 8888, we matched the first five records,
VI, for example Operational Directive
Business Type Business Name IOD PUSH STK Product Description
Operational code instructions on-demand billing prices to return to be the type of business code number of the type of price billing code to send the frequency of business
Billing type of the price return to be the number of
Apps哈妮HY-fat natural XXX monthly statements to 5 yuan 1, through natural language and virtual master
Holders "哈妮" exchange
LT chat靓妹handsome XXX Fat A to 0.2 yuan in accordance with Article 1, the distribution of user registration ID number, Qualcomm
ID No. chatters have been looking for an anonymous chat with friends
In fact, you do not know how to test the hearts of CS-fat XXX monthly P to 7 yuan a psychological test Guinness
Pretty Woman, Temptress Moon game JR Law M to 7 yuan monthly XXX role of a love game
The game is very Confession GB to GB law XXX Article 0.2 yuan by 1, emotional story
NV testing method for men and women know love XXX by NV to be 0.2 yuan 1 love test game
Regards language the story of fish and water YS Act XXX by YS to be 0.1 yuan 1,2 Regards language
Official test method YU Yun YU wealth luck with the opposite sex to XXX according to Article 0.2 yuan 1 birthday test
YG Act Play State YG daughter to XXX according to Article 0.2 yuan 1 Journey to the West the role of the new games
Turn Left, Turn Right game ZY law ZY to be 0.2 yuan by XXX comics 1,2 SMS story
XR sweetheart game XR law to XXX according to Article 0.3 yuan 1, through each other's messages to his mobile phone number to guess
The Stars Know My Heart Test Method XX Article XX to XXX by 0.2 yuan 1,3 Constellation test
Yi Cheng TL Tarot TL method to 7.0 yuan monthly XXX SMS Tarot version 1,3
Easy way of life XM name and XM law to be XXX by the name of the test 0.4 yuan 1,4
Many Lives, Many Masters Games QS to QS method XXX in accordance with Article 0.5 yuan 1,4 birthday game
- That is, as long as they are at the beginning of the above letter is sent to the corresponding port at the beginning of the mobile that the relationship between the existence of on-demand or custom, What is the difference between how a specific business, there is provision to deal with packet received, the current fundamental has been done.
- As a result of the mobile has no free code, that is free and so the original can not be used, so no error message, if some have been designed, it is扣费information;
- As long as the user the existence of the relationship between the order, all must use the downlink downlink billing code, custom business will扣费, monthly business issued by billing code, then the mobile will not be silent as the user
Source: Unknown
The topic is soil, but recently helped a friend do this thing, so write something up for reference for beginners.
First, prepare the information
SP development site there are a lot of information, but primarily the following documents:
1, MISC1.6 SP order to inform the interface requirements
2, SMPP protocol
3, MISC SMS SP system access training (Starter Edition). Ppt
4, DSMP norms regulate the SSO platform access details v1.5.1.pdf
5, for the SP to view the error code
6, DSMP norms regulate access to the SSO platform. Pdf
7, the Internet CMPP V3.0
II, Short Message Service Category
SMS main two kinds, one is the on-demand business, is another custom business
1, on-demand business
Not in front of their service_id - No. For example, YLSH
Description: billing codes, and what is a service_id
Mobile phone users have sent messages, sp issued to information, mobile uplink based on a distribution of a linkid, a certain amount of time sp issued to give him information may be issued a number of information, but each message is the same linkid
, One can take a linkid billing code (this is declared in the mobile, with this code扣费, 1 yuan or two yuan, or N-)
For example, a cell phone made a 13912345678 uplink information A, the command is declared in the mobile, misc platform through him, then returned to the linkid assigned a sp, sp instructions A judge in accordance with what the business users, and then to the user under the
Fat information must be issued to bring information and billing lingkid code can not be issued, for example, issued three, each linkid and billing information are the same code (because there is only one uplink user commands), so in fact, made a 3 Although sp
Be deducted only to the cost of a. Linkid and billing with code only in order to ensure the success of information issued by a parameter. So all the business, on-demand, as well as the back of that custom
2, customized business:
Its front service_id - number, for example-YLQTYX
Mobile phone users sent a message, after authentication misc, admitted that he was willing to use custom business, he will be customized as the user, and then, even if users do not have to issue information, sp can also take the initiative to issue him with information, this time on the not allocated
linkid, but service_id, that is, billing code information for each issue must be brought before the service_id.
He also divided into two categories
1), customized in accordance with Article
sp relations can be ordered to have issued the user information, the user received each one service_id marked in accordance with扣费charges, a month, deducted up to 10 users, more than 10 yuan in part, or whether they need service_id issued with only
Mobile no longer扣费(that part, sp do not need to pipe)
2), monthly business
sp relations can be ordered to have issued the user information, all information should be issued with service_id,扣费initiated by the mobile, sp regardless.
Third, the development of technology
As long as the first point of agreement to meet and regulatory requirements, with the current development of the popular database language and can do so.
1, the key is the network programming, and programming SOAP
2, the relevant terms explained
MISC (Mobile Information Service Center Mobile Information Service Center) is a completely in line with China's mobile data service management platform technical specifications (DSMP) operating platform of the data, it completed the operational data management and control of reactive power
Able, user management, business management and SP management, provide an open, uniform standard Web Service interface, and can be the gateway for all business, SP-generation billing provided.
SMPP Interface Protocol is included in the initial GSM03.39 by ETSI specification, describes the short message center and a short message communications between the entities, relations and interactive data transmission protocol format, the SMPP interface protocol specification for a description of
Mainly for simple communications interaction, manufacturers will be to develop a standardized version of its agreement for V3.30; by the developer SMPP protocol version will forward the Forum has evolved into the V3.40, SMPP V3.40 protocol specification is fully compatible with G
SM 03.39 protocol standard. This specification, using SMS Short Message Center equipment and stock business processing platform interface between the protocol used GSM03.39 V3.30, in the absence of special note to the Association all
Norms that prevail. SMPP protocol can be TCP / IP or X.25 communication as the bottom bearing.
ISMG Intenet Short Message Gateway Internet Short Message Gateway
DSMP Data Service Manage Platform data service management platform
SMPP Short Message Peer to Peer Protocol Short Message Peer-to-Peer
CMPP China Mobile Peer to Peer China Mobile Point to Point Protocol
CMPP agreement to provide the following main types of business operations:
(1) SMS (Short Message Mobile Originate, SM MO)
Please refer to the process in detail "Monternet signaling processes regulate SMS V3.0.0";
(2) to receive SMS (Short Message Mobile Terminated, SM MT)
Please refer to the process in detail "Monternet signaling processes regulate SMS V3.0.0";
SMSC Short Message Service Center Short Message Center
GNS Gateway Name Server Gateway Name Server (Tandem Gateway)
SP Service Provider Service Provider
Gateway ISMG_Id code: 0XYZ01 ~ 0XYZ99, which is the capital of XYZ code, the median less than zero when the left, such as the Beijing No. 1 gateway code 001001, Jiangxi No. 1 gateway code 079101, and so on
Corporate code SP_Id SP: SP network address and the identity of the logo, address translation, billing, settlement and so on are based on enterprise code. Code to the number of enterprises said that a total of six, from "9XY000" to "9XY999", which "
XY "code for the mobile company
Service code SP_Code SP: Service code is the way in the use of SMS in the upstream business, available to users of the service provider code. Service code figures said the length of operational service code 4, that is, "1000
"-" 9999 "; local business services unified code length 5, that is," 01000 "-" 09999 "; MII for the new service code of the SP allocation of a new request to" 1061 "-" 1069 "As a prefix, the current shift in China
Dynamic distribution as follows:
1062: SP services for the province code
1066: SP services for the country code
Other No. retain paragraph.
Service_Id SP business types, numbers, letters and symbols by the SP custom, such as the picture may be set for Regards TPCQ, stock query can be defined as 11
DSMP data management platform
SSO Single Sign On, Single Sign -
HTTP Hyper Text Transfer Protocol, Hypertext Transfer Protocol.
HTTPS Hyper Text Transfer Protocol over Secure Socket Layer, Secure Sockets Layer based on the Hypertext Transfer Protocol.
ICP Internet Content Provider, Internet content providers
WWW World Wide Web
XML eXtensible Markup Language, Extensible Markup Language
Session refers to the process of HTTP access to a complete course of conversation
Internet Short Message Gateway (ISMG) is a service provider (SP) and mobile network SMSC intermediary entity between the Internet gateway, on the one hand responsible for receiving text messages sent to mobile users SP information and submitted to the SMS Center. On the other hand, mobile
SP-demand business users of information centers will be SMS Gateway SMS sent via the Internet SP. In addition, short message center in order to reduce signaling load, the Internet messaging gateway should be in accordance with the principle of routing information will be submitted SP forwarded to the appropriate Internet Short
Gateway letter. SMS Gateway Internet Gateway to the aggregation (GNS) query access gateway routing information between the transponder.
In addition, ISMG also be DSMP data management platform to connect, in the business processes of customers, the relationship between business and ordered to carry out the operations of authentication and grant price.
3, interface naming convention
Interface name using the first letter of the word capital, the way other letters lowercase. Abbreviations in all capital letters; interface with parameters and information
Allow definition of the basic data type of field naming convention using the first letter of the word capital, there is no connection between the word at the way; for a single abbreviation
Words, such as ID, URL, ICP, MSISDN, etc., will be uniform application of capital.
SSO platform for user ownership of land is actually part of DSMP function. When users log on to the ownership of the need to redirect users to DSMP on self-service portal, regardless of SP or the entire network of local SP, are vested in the user's SSO user boarding platform
Recorded, and the completion of Session management, user subscription information is stored in the attribution to DSMP platform and user authentication to complete by the attribution to DSMP. Therefore, SP needs and access to the SSO platform in order to complete the management of Session.
At the same time, in various SSO platforms, but also requires a mechanism for the management and synchronization between the user data need to ensure that SSO user data in any platform can be. To achieve this requirement, it is recommended the use of centralized control, all the points by
Means to be synchronized, which is deployed throughout the DSMP structure there is a central node, a central repository of all user login data, the SSO platform provinces need to log in the user through the user redirected to the central SSO Ping
Log in Taiwan to complete the operation. See below in the specific process of the user registry, business purchase / on-demand and user processes that sign back.
Fourth, the relevant data
1, SyncOrderRelationReq
<? xml version = "1.0" encoding = "utf-8"?>
<SOAP-ENV: Envelope xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance"
xmlns: xsd = "http://www.w3.org/2001/XMLSchema"
xmlns: SOAP-ENV = "http://schemas.xmlsoap.org/soap/envelope/"
xmlns: SOAP-ENC = "http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Header>
<TransactionID Xmlns="http://www.monternet.com/dsmp/schemas/"> 00110338785301 </ TransactionID> the source code
</ SOAP-ENV: Header>
<SOAP-ENV:Body>
<SyncOrderRelationReq Xmlns="http://www.monternet.com/dsmp/schemas/">
<Version> 1.5.0 </ Version> the interface version number information
<MsgType> SyncOrderRelationReq </ MsgType> Message type
<Send_Address> Sender's address
<DeviceType> 0 </ DeviceType> device type 0: DSMP
<DeviceID> 0011 </ DeviceID> device ID
</ Send_Address>
The recipient's address <Dest_Address> use user ID when using the user and billing the user for the same time users, FeeUser_ID and DestUser_ID the same value.
<DeviceType> 400 </ DeviceType> device type 400: SP
<DeviceID> 0 </ DeviceID> device ID
</ Dest_Address>
Billing <FeeUser_ID> User ID
<UserIDType> 1 </ UserIDType> User ID type 1: identification number using a mobile phone
<MSISDN> 13912345678 </ MSISDN> user mobile phone number
<PseudoCode> </ PseudoCode> pseudo-code users
</ FeeUser_ID>
<DestUser_ID> The use of user ID
<UserIDType> 1 </ UserIDType> User ID type 1: identification number using a mobile phone
<MSISDN> 13912345678 </ MSISDN> user mobile phone number
<PseudoCode> </ PseudoCode> pseudo-code users
</ DestUser_ID>
<LinkID> SP </ LinkID> Provisional Order ID affairs
<ActionID> 2 </ ActionID> state management service action code, specific values are as follows: 1: open services; 2: stop services; 3: activation of services; 4: suspended;
<ActionReasonID> 1 </ ActionReasonID>
ActionReasonID: state management services have a cause of action code, specific values are as follows: 1: client-initiated behavior management services to state causes of action code, specific values are as follows:
1: client-initiated behavior
2: Admin & 1860 initiated act
3: Boss stands
4: Boss Boot
5: Boss transfer
6: Boss households sell
7: Boss Number
8:扣费service failure caused by the abolition of
9: Other
<SPID> 419613 </ SPID> SP corporate code
<SPServiceID>-LTYLBY </ SPServiceID> SP in the service code, label the contents of each type of business, and is also called the billing code, business code
<AccessMode> 3 </ AccessMode> services access 3: SMS 2: WAP 1: WEB
<FeatureStr> MTA2NjIxNDQgVERBRA == </ FeatureStr> services ordered parameters, encoded using BASE64
</ SyncOrderRelationReq>
</ SOAP-ENV: Body>
</ SOAP-ENV: Envelope>
2, SyncOrderRelationResp
<SOAP-ENV: Envelope
xmlns: SOAP-ENV = "http://schemas.xmlsoap.org/soap/envelope/"
xmlns: SOAP-ENC = "http://schemas.xmlsoap.org/soap/encoding/"
xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance"
xmlns: xsd = "http://www.w3.org/2001/XMLSchema" xmlns: dsmp = "http://www.monternet.com/dsmp/schemas/">
<SOAP-ENV:Header>
<dsmp:TransactionID xmlns:dsmp="http://www.monternet.com/dsmp/schemas/">
<% = TransactionID%>
</ dsmp: TransactionID> the source code
</ SOAP-ENV: Header>
<SOAP-ENV:Body>
<dsmp:SyncOrderRelationResp xmlns:dsmp="http://www.monternet.com/dsmp/schemas/">
<MsgType> SyncOrderRelationResp </ MsgType>
<Version> <% = Version%> </ Version> the interface version number information, the interfaces of all the versions of the news as "1.5.0
<hRet> <% = hRet%> </ hRet>
</ dsmp: SyncOrderRelationResp>
</ SOAP-ENV: Body>
</ SOAP-ENV: Envelope>
3, cancellation of service request packet
Reverse the abolition of the process described:
Reverse the abolition of SP was launched from the cancellation of the process, MISC from the SP in dealing with news of the cancellation, the process and from other network elements to deal with the news the same, process as follows:
(0) SP in place of the user to cancel the request MISC launched UnSubscribeServiceReq back and wait for MISC processing;
(0) MISC source of the message address, enterprise authentication code to determine whether or not to allow reverse the abolition of the SP;
(0) after a successful access authentication, user authentication and re-ordering the relationship between authentication to determine whether the correct user status and the relationship between the existence of order;
(0) above authentication is successful, MISC to the SP to send a request to order the relationship between synchronization packets SyncOrderRelationReq;
(0) SP received synchronization request, the request for order cancellation and do the deal, and ordered to return to the relationship between response synchronization SyncOrderRelationResp;
(0) MISC response received after the response to determine whether the value is 0. If the response value is 0, then in order to remove the relationship between MISC and the success of the SP to return to reverse the abolition of the response packet processing UnSubscribeServiceResp; If the response value is 0, then
Ordered not to lift the relationship to the SP failed to return to reverse the abolition of the response packet UnSubscribeServiceResp;
(0) SP error MISC if the response received, then the abolition of the failure, SP must be done on the failure of the corresponding information processing, such as the order has been canceled to resume relations, etc.;
(0) MISC if you receive the correct response, the SP can not do anything to deal with;
<? xml version = "1.0" encoding = "UTF-8"?>
<SOAP-ENV: Envelope xmlns: SOAP-ENV = "http://schemas.xmlsoap.org/soap/envelope/" xmlns: SOAP-ENC = "http://schemas.xmlsoap.org/soap/encoding/"
xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns: xsd = "http://www.w3.org/2001/XMLSchema" SOAP -
ENV: encodingStyle = "http://schemas.xmlsoap.org/soap/encoding/" xmlns = "http://www.monternet.com/dsmp/schemas/">
<SOAP-ENV:Header>
<TransactionID Xmlns="http://www.monternet.com/dsmp/schemas/" xsi:type="xsd:string"> 9130020301801050 </ TransactionID> the source code
</ SOAP-ENV: Header>
<SOAP-ENV:Body>
<UnSubscribeServiceReq Xmlns="http://www.monternet.com/dsmp/schemas/">
<Version> 1.5.0 </ Version>
<MsgType> UnSubscribeServiceReq </ MsgType> Message type
<Send_Address> Sender's address
<DeviceType> 400 </ DeviceType>
<DeviceID> 913002 </ DeviceID>
</ Send_Address>
<Dest_Address> The recipient's address
<DeviceType> 0 </ DeviceType>
<DeviceID> 0024 </ DeviceID>
</ Dest_Address>
Billing <FeeUser_ID> User ID
<UserIDType> 1 </ UserIDType> See below the definition of
<MSISDN> 13805002424 </ MSISDN> user mobile phone number
<PseudoCode />
</ FeeUser_ID>
<DestUser_ID> Use user ID when using the user and billing the user for the same time users, FeeUser_ID and DestUser_ID the same value.
<UserIDType> 1 </ UserIDType>
<MSISDN> 13805002424 </ MSISDN>
<PseudoCode />
</ DestUser_ID>
<Service_ID> Service marks of
<ServiceIDType> 1 </ ServiceIDType>
<SPID> 913002 </ SPID>
<SPServiceID>-TQAAU </ SPServiceID>
<AccessNo />
<FeatureStr />
</ Service_ID>
<FeatureStr />
</ UnSubscribeServiceReq>
</ SOAP-ENV: Body>
</ SOAP-ENV: Envelope>
In response to the abolition of service package
<? xml version = "1.0" encoding = "UTF-8"?>
<SOAP-ENV: Envelope xmlns: SOAP-ENV = "http://schemas.xmlsoap.org/soap/envelope/" xmlns: SOAP-ENC = "http://schemas.xmlsoap.org/soap/encoding/"
xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns: xsd = "http://www.w3.org/2001/XMLSchema" xmlns: dsmp = "http://www .monternet.com / dsmp / schemas / ">
<SOAP-ENV:Header>
<dsmp:TransactionID xmlns:dsmp="http://www.monternet.com/dsmp/schemas/"> 9130020301801050 </ dsmp: TransactionID>
</ SOAP-ENV: Header>
<SOAP-ENV:Body>
<UnSubscribeServiceResp Xmlns="http://10.1.2.122/misc/dsmp.xsd">
<Version> 1.5.0 </ Version>
<MsgType> UnSubscribeServiceResp </ MsgType>
<hRet> 0 </ hRet> return value: see definition below
</ UnSubscribeServiceResp>
</ SOAP-ENV: Body>
</ SOAP-ENV: Envelope>
4, the definition of return value
Communication at the time of the HTTP status code please refer to the provisions of the agreement HTTP/1.1 status code values are not included in this
Regulate the return value of a unified definition.
Specifically described as follows:
0: Successful
1: Unknown error
2-99: reservations
MISC and 4000-4999 for the interface between the SP of the error code message:
4000: Invalid msgtype
4001: Invalid action_id;
4002: Invalid action_reasonid;
4003: SP ID invalid
4004: Invalid serviceID
4005: Invalid pseudocode
4006: Invalid accessmode
4007: MISC opened simultaneously, but SP has been in existence for ordering the relationship between client and state for the opening of
4008: MISC simultaneous opening of service, and ordered SP client relationship does not exist, but fail to open service
4009: MISC opened simultaneously, but SP has been in existence for ordering the relationship between client and for the suspension of state
4010: MISC simultaneously closed, and the existence of SP-side order, but the abolition of service failure
4011: MISC synchronous stop service, but ordered SP client relationship does not exist
4012: MISC simultaneous suspension of services, and the existence of SP-side order, but suspended service failure
4013: MISC simultaneous suspension of service, but ordered SP client relationship does not exist
4014: MISC suspended simultaneously, but SP has been in existence for ordering the relationship between client and for the suspension of state
4015: MISC synchronous activation of services, but SP has been in existence for ordering the relationship between client and state for the opening of
4016: MISC synchronous activation of service, but ordered SP client relationship does not exist
4017: MISC synchronous activation of services, and the existence of SP-side order, but failed to activate service
9000-9999 for system-level error:
9000: read and write system disk error
9001: Network Anomaly
9002: Network error
9003: Business Gateway is busy, the business gateway cache
9004: Business Gateway is busy and full business gateway buffer, MISC cache and not to send a message,
Wait and try again.
9005: MISC busy, MISC cache
9006: MISC busy over the buffer zone and MISC, the business gateway cache and not to send a message and wait for some time and try again.
9007: Business Gateway over the prescribed limit the flow of
9008: MISC anomaly is not available
9009: Business Gateway anomaly is not available
9010: The business does not have permission to call the gateway interface information
9011: MISC does not have permission to send the message to the business interface gateway
9012: Version does not support
Page 6
Reverse MISC SP business interface
9013: Message type is not, the system does not support
9014: authentication error, can not resolve the structure of SOAP and XML, the lack of the field must exist, or information not in the correct format
9015: Refusal of information, the server can not complete the requested service
5, DeviceType definition
Device type
0: DSMP
100: ISMG
101: WAP SP PROXY
1XX: other business gateway
200: WAP PORTAL
201: WWW PORTAL
202: VOICE PORTAL
203: PDA PORTAL
2XX: other portal
300: MMSC
301: KJAVA SERVER
302: LSP
3XX: other application platform
400: SP
6, DeviceID definition
Equipment number, equipment number of the network using the device ID, such as the SMS gateway using the gateway ID, on the SP to use its enterprise code, the device ID from DSMP distribution, and in the same device type in the code only
7, UserIDType the definition of
User ID Type
1: identification number using a mobile phone
2: The pseudo-code marking
3: both ID
8, SPType
SP business types
1: All SP
2: the provision of SMS services, SP
3: SP to provide WAP services
4: SP to provide MMS services
5: KJAVA services provided by SP
6: MAIL services provided by SP
7: the provision of LBS services, SP
8: the provision of WWW services, SP
9 ~: expansion
9, ServiceIDType
Logo type of service by:
1: SPID + SPServiceID
2: AccessNo + FeatureStr
5, MISC match of MO business process description
Handling Description:
1, SP business applications, in accordance with the different types of business operations to fill orders, according to different types of business, there may be "ordering instructions, cancellation of orders, on-demand instruction and the general MO" 4 species command mode, setting directions, need to refer to
Will be sent instructions corresponding number (long number) and the content of directive and assigned number and instructions to send content to match needs to be done accurately.
Exact matching means that the match only if the content and the need for exactly the same instruction set (including the same length), the only match. For example, if set up to send the number to "800101", only when a user send a MO to
"80010123" will not match the "800101" of that instruction; only sent to "800101" and the command will be matched.
【Note】 a directive for the same model, each service can set up more than, for example, a service can be set up instructions and 5 order cancellation instruction 5, the current MISC can support more than five instructions, but from the convenience of the management point of view, For the same
A mode of instruction, it is recommended not to SP set up more than 5 hours.
2, the user's MO message from the two parts: sending number and send the contents of application coupled with the business model set up to match, these three constitute the basis for matching.
3, when a MO at the MISC for authentication, MISC first send the number (L number) match, in accordance with the maximum matching + the principle of exact match. If there is a successful match, then took out the corresponding command code and the type of business; if the horse
Not good enough, then authentication fails, the MO will not be issued to SP.
4, in the previous step from the list of matches, and then match the content of directive, but also the biggest match + in accordance with the principles of exact match. If there is to match the results, then remove the corresponding code and command the type of business; if there is no will
Corresponds to the results of the match, then the value of Service ID to return to space, at the same time to inform the SMS text messages as a gateway to this common MO transmitted to the SP.
5, SP in order to fill orders MO is to avoid nested commands (for example, the existence of "888801" and "8888011" and AccessNO).
6, to match the success of the Directive, MISC out in accordance with the instructions to match the patterns are different, the treatment is as follows:
? For ordering instructions, while MISC will check whether the user has been ordered by the service, if there is no order, the order will be completed MISC, MO At the same time, users will be content to order the relationship between the user interface data synchronization (Provision interface
) Transmitted to the SP, in the Provision field FeatureStr interface users will have long-MO number and content of instruction, the contents of a long number and instructions will be a space between the delimited. MISC will be notified at the same time this is a short message gateway ordering instructions, short
Letter to the SP gateway will not be forwarded to the MO.
If the user has been ordered by the service, the type of services for a monthly subscription, MISC will be the general MO as MO SMS Gateway to return to the successful outcome of the authentication, SMS Gateway will notice this as a general MO SMS forwarding to the SP; custom category for a monthly subscription service,
While MISC will demand the type of MO as MO SMS Gateway to return to the successful outcome of the authentication, notification SMS text messages as a gateway to this demand to the SP transmitted MO.
? As for the cancellation of orders, while MISC will check whether the user has been ordered by the service, if you have ordered, you will be able to complete abolition of MISC, MO At the same time, users will be content to order the relationship between the user interface data synchronization (Provision interface
) Transmitted to the SP, in the Provision field FeatureStr interface users will have long-MO number and content of instruction, the contents of a long number and instructions will be a space between the delimited.
If the user did not order the service, MISC will return to the SMS gateway authentication failure message to the SP gateway will not be forwarded to the MO.
? Instructions for on-demand, MISC need to determine the type of business is custom on-demand on-demand business or general business
1) For customized on-demand business, users need to determine whether the service has been ordered, if ordered, it will generate the provisional order MISC relations (LinkID), at the same time to return to the SMS gateway authentication success, and returned to the SMS network LinkID
Clearance from the MO short message gateway to the SP as an on-demand forwarding MO; if the user did not order, then MISC simply return to the SMS Gateway in response to successful authentication, SMS Gateway will notice this as an ordinary SMS MO to SP forward.
2) In the case of on-demand business, while MISC will have a direct relationship between the generation of the provisional order (LinkID), at the same time to return to the SMS gateway authentication success, and returned to the LinkID SMS gateway, SMS gateway from the MO as MO to the SP-demand forward.
? For ordinary MO SMS, MISC to return to the SMS Gateway in response to successful authentication, notification SMS text messages as a gateway to this common MO forward to the SP.
Example Description:
seq AccessNO FeatureStr ANCheckFlag FSCheckFlag
1 8888 xw 1 0
2 888801 xw 0 0
3 888801 xw1 0 1
4 8888 01xw 1 1
5 8888 (null) 0 0 (HELP)
【Note】 AccessNO that sent the number of MO
That the content of directive FeatureStr
ANCheckFlag expressed whether or not to use exact match AccessNO
That the content of directive FSCheckFlag whether or not to use exact match
For the above settings,
Xw1 send to 8888011, we match the first three records
Send xw01 to 888,801 users and we will match the first two records (access to matching its longest)
Users to send 888,802 of our 01xw to match the first five records (will not be matched to the first four records, because the first four records are exact match AccessNO)
01xw send to 8888, we match the first four records
Xw01 send to 8888 to match the first one we recorded
A send to 8888, we matched the first five records,
VI, for example Operational Directive
Business Type Business Name IOD PUSH STK Product Description
Operational code instructions on-demand billing prices to return to be the type of business code number of the type of price billing code to send the frequency of business
Billing type of the price return to be the number of
Apps哈妮HY-fat natural XXX monthly statements to 5 yuan 1, through natural language and virtual master
Holders "哈妮" exchange
LT chat靓妹handsome XXX Fat A to 0.2 yuan in accordance with Article 1, the distribution of user registration ID number, Qualcomm
ID No. chatters have been looking for an anonymous chat with friends
In fact, you do not know how to test the hearts of CS-fat XXX monthly P to 7 yuan a psychological test Guinness
Pretty Woman, Temptress Moon game JR Law M to 7 yuan monthly XXX role of a love game
The game is very Confession GB to GB law XXX Article 0.2 yuan by 1, emotional story
NV testing method for men and women know love XXX by NV to be 0.2 yuan 1 love test game
Regards language the story of fish and water YS Act XXX by YS to be 0.1 yuan 1,2 Regards language
Official test method YU Yun YU wealth luck with the opposite sex to XXX according to Article 0.2 yuan 1 birthday test
YG Act Play State YG daughter to XXX according to Article 0.2 yuan 1 Journey to the West the role of the new games
Turn Left, Turn Right game ZY law ZY to be 0.2 yuan by XXX comics 1,2 SMS story
XR sweetheart game XR law to XXX according to Article 0.3 yuan 1, through each other's messages to his mobile phone number to guess
The Stars Know My Heart Test Method XX Article XX to XXX by 0.2 yuan 1,3 Constellation test
Yi Cheng TL Tarot TL method to 7.0 yuan monthly XXX SMS Tarot version 1,3
Easy way of life XM name and XM law to be XXX by the name of the test 0.4 yuan 1,4
Many Lives, Many Masters Games QS to QS method XXX in accordance with Article 0.5 yuan 1,4 birthday game
- That is, as long as they are at the beginning of the above letter is sent to the corresponding port at the beginning of the mobile that the relationship between the existence of on-demand or custom, What is the difference between how a specific business, there is provision to deal with packet received, the current fundamental has been done.
- As a result of the mobile has no free code, that is free and so the original can not be used, so no error message, if some have been designed, it is扣费information;
- As long as the user the existence of the relationship between the order, all must use the downlink downlink billing code, custom business will扣费, monthly business issued by billing code, then the mobile will not be silent as the user