CN103037312B - Information push method and device - Google Patents
Information push method and device Download PDFInfo
- Publication number
- CN103037312B CN103037312B CN201110302984.5A CN201110302984A CN103037312B CN 103037312 B CN103037312 B CN 103037312B CN 201110302984 A CN201110302984 A CN 201110302984A CN 103037312 B CN103037312 B CN 103037312B
- Authority
- CN
- China
- Prior art keywords
- message
- token
- account number
- application
- mobile terminal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The application relates to a kind of information push method and device, and the method comprises: send message token and obtain request, and described message token obtains request and comprises mobile terminal identifier number, application name and user account number identification information; Receive described mobile terminal identifier number, application name and the message token corresponding to user account number identification information; Send the message data search request carrying described message token; The message data that the described message token that reception finds out according to described message token mates.Therefore, the application is applicable to any mobile terminal, does not need to safeguard that keep-alive is shaken hands; Message token and dbase, mobile terminal identifier number and user account number identification information are bound together, message can accurately be delivered to mobile terminal.
Description
Technical field
The application relates to network communication field, particularly relates to a kind of information push method and device.
Background technology
At present, a lot of mobile terminal all supports wireless network, user can install client software on mobile terminals and subscribe to Internet service, and the service provider of the Internet can issue to client, PUSH message, and client to receive after these message by showing interface to user.In addition, service provider can also to some configuration informations of client push, version updating information, and the value increasing service message such as advertisement, marketing.
Propelling movement (push) server of current Apple is supported in PUSH message on iPhone cell phone platform.Its workflow is:
First stage: third-party server, the packing of the mark of the message that will send, object iPhone, issues the push server of apple;
Second stage: the push server of apple searches the iPhone having respective identification in the iPhone list of the registered Push service of self, and message is dealt into iPhone;
Phase III: iPhone gives corresponding application program the Message Transmission sent, and according to setting, ejects Push notice.
Before the push server formal communication of iphone mobile phone and Apple, need to set up a long-chain based on the encryption of safe transmission layer protocol (TransportLayerSecurity is called for short TLS) in advance and connect.Each normal iPhone has an exclusive device certificate, and push server also has a server certificate.Certificate validity each other can be verified time both establish the link.TLS link, once set up, in the absence of data, only need to carry out shaking hands of a keep-alive every 15 minutes, and once because accidental cause causes link interruption, iPhone can constantly be attempted setting up TLS link again, until success.TLS encryption connection needs mutually to verify with certificate each other, which dictates that this system can only be used for iPhone mobile phone, can not be applied to other mobile terminals.
But because long connection of mobile terminal client terminal in mobile Internet and server end is often cut off by the mobile gateway of operator, so safeguard that long a connection needs shaking hands of often transmission keep-alive, need time more to re-establish connection.
And each and push server of iPhone mobile phone sets up TLS when being connected, push server is by the unique device certificate checking of the normal iPhone of every platform, and this device certificate iPhone mobile phone activation key encrypts generation.After device certificate is verified, push server can return to iPhone the device token corresponding to every platform iPhone, and the Push application program of correspondence then directly sends to third party service provider returning the device token come.Like this, when third party service provider has Push message to send, just device token is sent to push server together with Push message, push server again according to the iPhone that device token finds corresponding TLS to link, and sends corresponding Push message.
Therefore, such scheme is by device token and iPhone handset binding, and distinguish message by device token, Push message can not accurately be pushed in affiliated application program by this, when there is multiple third-party application in an iPhone mobile phone, the message of an application program may be received by other application programs, same application program is after switching user account number, the user account number that the message of a user account number may be switched receives, this is that the device token of use is same due to for the multiple different application program on an iPhone mobile phone.Simultaneously because each PUSH message of third party service provider pushes according to device token, therefore third party service provider is when needs push same push message to multiple stage iPhone mobile phone, one by one this push message can only be sent to push server stores according to the token of every platform iphone mobile phone.
Summary of the invention
The object of the application is, provides a kind of information push method and device, message token and application name, mobile terminal identifier number and user account number identification information is bound, with realize accurately PUSH message in affiliated application program.
For achieving the above object, this application provides a kind of information push method, the method comprises:
Send message token and obtain request, described message token obtains request and comprises mobile terminal identifier number, application name and user account number identification information;
Receive described mobile terminal identifier number, application name and the message token corresponding to user account number identification information;
Send the message data search request carrying described message token;
The message data that the described message token that reception finds out according to described message token mates.
This application provides a kind of information push method, the method comprises:
Receipt message token obtains request, and described message token obtains request and comprises mobile terminal identifier number, application name and user account number identification information;
Send described mobile terminal identifier number, application name and the message token corresponding to user account number identification information;
Receipt message data preserve request, and the request of preserving of described message data comprises the message data of described message token and correspondence thereof, or the message data of application name and application version and its correspondence;
This message data is stored according to described message token or application name and application version;
Receive the message data search request carrying described message token;
The message data that the described message token that transmission finds out from the message data of described storage according to described message token mates.
Present invention also provides a kind of message push device, this device comprises:
Token request transmitting element, obtains request for sending message token, and described message token obtains request and comprises mobile terminal identifier number, application name and user account number identification information;
Token receiving element, for receiving the message token corresponding to described mobile terminal identifier number, application name and user account number identification information;
Message request transmitting element, for sending the message data search request carrying described message token;
Message reception units, for receiving the message data that the described message token that finds out according to described message token mates.
Present invention also provides a kind of message push device, this device comprises:
Token request receiving element, obtains request for receipt message token, and described message token obtains request and comprises mobile terminal identifier number, application name and user account number identification information;
Token transmitting element, for sending the message token corresponding to described mobile terminal identifier number, application name and user account number identification information;
Message preserves receiving element, preserves request for receipt message data, and the request of preserving of described message data comprises the message data of described message token and correspondence, or the message data of application name and application version and its correspondence;
Specimens preserving unit, for storing the message data of its correspondence according to described message token or application name and application version;
Message request receiving element, for receiving the message data search request carrying described message token;
Message sending unit, for sending the message data that the described message token that finds out from the message data of described storage according to described message token mates.
Therefore, the application is applicable to any mobile terminal, does not need to safeguard that keep-alive is shaken hands; Message token and dbase, mobile terminal identifier number and user account number identification information are bound together, message can accurately be delivered to mobile terminal.
Accompanying drawing explanation
Fig. 1 is the schematic diagram of the application one embodiment information push method;
Fig. 2 is the schematic diagram of another embodiment information push method of the application;
Fig. 3 is the schematic diagram of the application one embodiment message push device.
Fig. 4 is the schematic diagram of another embodiment message push device of the application;
Fig. 5 is the process schematic of information push method in the embodiment of the present application practical application;
Fig. 6 is the signaling method flow chart of the information push method in the application's practical application;
Fig. 7 is the schematic diagram of message push system in the application's practical application.
Embodiment
Below by drawings and Examples, the technical scheme of the application is described in further detail.
The application by message token and application name, mobile terminal identifier number and user account number identification information being bound, thus achieves the accurate propelling movement of message.
Fig. 1 is the schematic diagram of the application one embodiment information push method.As shown in the figure, the present embodiment method for pushing for client, such as, can use the various mobile terminals of network, include, but are not limited to desktop computer, mobile phone, notebook, panel computer etc.
The present embodiment comprises the following steps as shown in the figure:
Step 101, sends message token and obtains request, and described message token obtains request and comprises mobile terminal identifier number, application name and user account number identification information;
Send message token obtain request can be change at user state information, application version upgrades and/or time interval of presetting registers when obtaining described message token and carries out.Specifically, when on mobile terminal applications that registered for user account number after, occur user account number switch, user account number nullify time, mobile terminal can initiate to push server initiate message token obtain request; Or when application version is upgraded, also can initiate to initiate message token to push server and obtain request; Even can according to the time interval of mobile phone users setting, the message token under active user's account number of this application program of acquisition for mobile terminal.
For different application programs, message token obtains request and also just can trigger when installation, some application program can also when mobile terminal hangs up service, acquisition message token is registered as described above according to the time interval of setting, when specifically, Trigger message token obtains request, above-mentionedly be only example, do not limit, specifically set according to specifically different application programs.
Step 102, receives described mobile terminal identifier number, application name and the message token corresponding to user account number identification information;
Preferably, described message token generates according to described mobile terminal identifier number, application name and user account number identification information.
Step 103, sends the message data search request carrying described message token;
Step 104, receives the message data that the described message token that finds out according to described message token mates.
Further, the present embodiment also comprises before step 101:
Step 100, receives developer's account number and key stores.
Mobile terminal is when down load application program, and application program carries developer's account number and key, therefore, while mobile terminal down load application program, can receive the corresponding developer's account number of this application program and key.
Alternatively, obtain in request in the message token of step 101, except mobile terminal identifier number, application name and user account number identification information, also can comprise the signature and developer's account number that carry out according to developer's account number and key.
Alternatively, when the acquisition of message token described in step 101 request also comprises signature and developer's account number, verify legal when developer's account number and sign after authentication, then performing step 102.
Alternatively, in message data search request described in step 103 except comprising message token, the signature that also can comprise developer's account number and developer's account number and key are carried out.
Alternatively, when message data search request in step 103 also comprises signature and developer's account number, verify legal when developer's account number and sign after authentication, performing step 102.
Wherein, verify that authentication can be realized by other third-party server.Specific implementation can see associated description below.
Preferably, the present embodiment also can comprise: forward the described message token and described user account number identification information that receive.After mobile terminal receives message token, immediately this message token and user account number identification information can be transmitted to application server, also can be sent in certain moment, in this no limit.The corresponding relation of this user account number identification information and message token safeguarded by application server, such application server can when determining to send out message data to certain user, go out corresponding message token according to user account number identification information-enquiry, then this message token and message data are issued push server.
This embodiment of the application is by by corresponding to message token and mobile terminal identification number, application name and user account number identification information, and the user account number achieved for an application program on a mobile terminal carries out the accurate propelling movement of message data.
Fig. 2 is the schematic diagram of another embodiment information push method of the application.As shown in the figure, the present embodiment method for pushing for server end as main body, such as, for the push server of PUSH message.The present embodiment information push method comprises the following steps:
Step 1001, receipt message token obtains request, and described message token obtains request and comprises mobile terminal identifier number, application name and user account number identification information;
Step 1002, sends described mobile terminal identifier number, application name and the message token corresponding to user account number identification information;
Step 1003, receipt message data preserve request, and the request of preserving of described message data comprises the message data of described message token and correspondence thereof, or the message data of application name and application version and correspondence thereof;
Step 1004, stores the message data of its correspondence according to described message token or application name and application version;
When according to message token in a database storing message data time, due to the uniqueness of message token, what deposit is the message data of user account number for specific one application program.This process can be called as singly deposits message.
When according to application name and application version storing message data, can for every to all message token of application name and version carrying out the storage of message data, namely all user account numbers of this application program carry out storing message data, realize storing this message data to the user account number of application program multiple on multiple stage mobile terminal.This process can be called as group and deposit message.
Step 1005, receives the message data search request carrying described message token;
Step 1006, sends and from the message data of described storage, finds out according to described message token the message data that described message token mates.
Preferably, the present embodiment also can comprise:
Step 1000, receives developer's account number, described application name and application version and carries out one_to_one corresponding storage.
When developer's such as third-party application server that certain application program is corresponding is registered to Developer Central Control Server, developer's account number of the application server registers corresponding to application program, key and the information such as application name, version are carried out record by Developer Central Control Server, and notifying developer account number, application name and the version of push server through registering, push server receives developer's account number, described application name and application version and carries out one_to_one corresponding storage in a database.
Wherein, alternatively, Developer Central Control Server and this push server can be integrated, and are realized by a comprehensive server.
Preferably, as shown in the figure, between step 1001 and step 1002, the present embodiment also comprises the following steps:
Step 1011, according to described mobile terminal identifier number, application name and user account number identification information, retrieve in a database and whether there is described mobile terminal identifier number, application name and the message token corresponding to user account number identification information, if existed, perform step 1021; If there is no, 1022 are gone to step;
Step 1021, takes out this message token;
Step 1022, according to described mobile terminal identifier number, application name and user account number identification information generating messages token, and stores described mobile terminal identifier number, user account number identification information and message token.
If when sending message token acquisition request first, corresponding message token is generated according to the mobile terminal identifier uploaded number, application name and user account number identification information, and the related data of sending first is stored, after obtaining message token first, when each Trigger message token afterwards obtains request, from database 6, directly can obtain this message token.
Alternatively, in described step 1001, this message token to obtain in request except mobile terminal identifier number, application name and user account number identification information, also can comprise the signature carried out developer's account number and key, and developer's account number.
Preferably, the present embodiment also comprised before step 1001 as shown in the figure:
Step 200, checking developer account number is legal: checking developer account number is effectively, and described developer's account number had registered application program corresponding to described developer's account number in a database;
Wherein, verify that developer account number is for being effectively be then effective by this developer's account number is registered in retrieval Developer Central Control Server.
Step 300, obtains to the described message token received the signature carried in request and carries out authentication.Concrete authentication process can see associated description below.Alternatively, step 1003 message data is preserved in request, also can comprise the signature carried out developer's account number and key, and developer's account number.
The request of preserving of this message data can be sent by third-party server such as application server, or the applying unit of this push server sent.
Similarly, before step 1003 receipt message data preserve request, also can be passed through step 200 and whether 300 (not shown)s checking developer account number is legal, and the signature carried in request is preserved to the described message data received carry out authentication.
Alternatively, described in step 1005, message data search request is except comprising message token, yet can comprise the signature carried out developer's account number and key, and developer's account number.
Similarly, before step 1005 reception carries the message data search request of described message token, also can be passed through step 200 and whether 300 (not shown)s checking developer account number is legal, and authentication is carried out to the signature carried in the message data search request received.
Step 200 and 300 can be undertaken by the authentication unit in push server, or is undertaken by third-party server such as access server.
Preferably, when described message data preserve also carry developer's account number in request time, the embodiment of the present application step 1003 receive the message data comprising the message data of message token and correspondence thereof preserve please summation step 1004 to store its correspondence according to message token message data between also comprise:
Relatively receive this message token carried in message data preservation request whether consistent with the message token of storage; More whether the application name that developer's account number of relatively also carrying according to the message data request of preserving finds its correspondence of record is in a database consistent with the application name that the message token carried according to this finds, according to the consistency of comparative result, judge the validity (step 1030) of this message token, if namely all consistent, have validity.If message token has validity, then message data storage can be carried out.Can prevent application server from copying message token like this, attack other application, to improve the fail safe of application.
This embodiment of the application is by by corresponding to message token and mobile terminal identification number, application name and user account number identification information, and the user account number achieved for an application program on a mobile terminal carries out the accurate propelling movement of message data.
Described above is the embodiment of the present application information push method, the message push device realizing this method for pushing is described below.As shown in Figure 3, the embodiment of the present application message push device is for client, and this message push device comprises:
Token request transmitting element 31, obtains request for sending message token, and described message token obtains request and comprises mobile terminal identifier number, application name and user account number identification information;
Token receiving element 32, for receiving the message token corresponding to described mobile terminal identifier number, application name and user account number identification information;
Message request transmitting element 33, for sending the message data search request carrying described message token;
Message reception units 34, for receiving the message data that the described message token that finds out according to described message token mates.
As shown in the figure, the application's message push device also comprises:
Account key receiving element 35, for receiving developer's account number and key stores.
Retransmission unit 36, for the described message token forwarding described user account number identification information Yu receive.
As shown in Figure 4, be another embodiment message push device of the application, this message push device is for server end, and this message push device comprises:
Token request receiving element 41, obtains request for receipt message token, and described message token obtains request and comprises mobile terminal identifier number, application name and user account number identification information;
Token transmitting element 42, sends described mobile terminal identifier number, application name and the message token corresponding to user account number identification information;
Message preserves receiving element 43, preserves request for receipt message data, and the request of preserving of described message data comprises the message data of described message token and correspondence thereof, or the message data of application name and application version and correspondence thereof;
Specimens preserving unit 44, for storing the message data of its correspondence according to described message token or application name and application version;
Message request receiving element 45, for receiving the message data search request carrying described message token;
Message sending unit 46, for sending the message data that the described message token that finds out from the message data of described storage according to described message token mates.
This message push device also comprises:
Receiving element, carries out corresponding stored for receiving developer's account number, described application name and application version.
As shown in the figure, this message push device also comprises:
Retrieval unit 48, for retrieving the message token corresponding to described mobile terminal identifier number, application name and user account number identification information in a database;
Token retrieval unit 49, if for there is the message token corresponding to described mobile terminal identifier number, application name and user account number identification information, then take out this message token;
Token generation unit 50, for the message token corresponding to if there is no described mobile terminal identifier number, application name and user account number identification information, then according to described mobile terminal identifier number, application name and user account number identification information generating messages token, and described mobile terminal identifier number, user account number identification information and message token are stored in database 60.
This message push device also comprises:
Authentication unit, for verifying that described message token obtains request, to preserve developer's account number of carrying in request or message data search request be effective to message data, and described in developer's account number of carrying registered application program corresponding to described developer's account number in a database;
Authenticating unit, carries out authentication for obtaining the signature carried in request, message data preservation request or message data search request to the described message token received.
This message push device also comprises:
First comparing unit, for the message token of the described message token that carries described in relatively and storage;
Second comparing unit, the application name of the storage that the application name for comparing the storage found according to developer's account number of carrying in described message data search request finds with the described message token carried described in basis.
According to the comparison of this first comparing unit and the second comparing unit, determine the validity of message token, if effectively, then carry out message data storage.This first comparing unit and the second comparing unit can prevent application server from copying message token, attack other application, to improve the fail safe of application.
This embodiment of the application is by by corresponding to message token and mobile terminal identification number, application name and user account number identification information, and the user account number achieved for an application program on a mobile terminal carries out the accurate propelling movement of message data.
Introduce the information push method of the application's mobile terminal side and the information push method combined process in actual applications of server side below.See Fig. 5, it illustrates the process schematic of the application's information push method in actual application; And Fig. 6, it illustrates the signaling method flow chart of the information push method in the application's actual application.For the ease of understanding, each equipment related in the process be described below can see Fig. 7, it illustrates the schematic diagram of the application's message push system in actual applications.This information push method comprises:
Step 10, application server 2 registers developer's account number to Developer Central Control Server 3, gets corresponding key unique with developer's account number.
Particularly, in signaling method flow chart as shown in Figure 6, step 10 can comprise following process:
Step 201, application server 2 registers developer's account number to Developer Central Control Server 3, applies to become legal developer;
Step 202, Developer Central Control Server 3 generates unique developer's account number and key, returns to application server 2.Each request of later application server 2, application server 2 all needs to bring developer's account number and these 2 values of key to be encrypted authentication (namely below by the legitimacy of the checking application server of description).
Wherein, the corresponding application program of usual application server, therefore developer's account number of application server and key namely this Develop Application System person's account number and key.Developer's account number of the application server registers corresponding to application program, key and the information such as application name, version are carried out record by Developer Central Control Server, and notify developer account number, application name and the version of push server through registering, push server will record these information, as shown in Fig. 6 2021.
Step 11, the developer account number corresponding according to the application program on mobile terminal 1 and signature, and mobile terminal identifier number, application name and user account number identification information, mobile terminal obtains message token corresponding to application program to push server 5, and described message token is sent to application server 2;
Wherein, user is after mobile terminal downloads and installs this application program, and this application program carries this developer's account number and key, and application name and version information, and preserves on mobile terminals; And user's registered user's account number in this application program, generate the user account number identification information that this user account number is corresponding on mobile terminals, and be kept on this mobile terminal.User account number identification information is the unique identification of user's (being also user account number) of each application program of mark; Therefore, mobile terminal 1 is preserved the information such as user account number identification information of mobile terminal identifier number, certain Develop Application System person's account number and key, application name, version and this application program, and the message token that below will describe corresponding with these information.
Particularly, in signaling method flow chart as shown in Figure 2, this step 11 is specially:
As the step 203 in Fig. 6, the message token that described mobile terminal 1 initiates described application program by http protocol to access server 4 obtains request, this message token obtains request and comprises: the signature carried out this Develop Application System person's account number and key, and first transmits data, these the first transmission data comprise developer's account number, application name, application version and user account number identification information and mobile terminal identifier number;
Wherein, to the rule that developer's account number and key are signed can be, cryptography information digest algorithm 5 (messagedigestalgorithm5 is called for short md5) is utilized to be encrypted calculating to developer's account number, key, service parameter and timestamp.Wherein service parameter comprises these the first transmission data such as application name, application version and user account number identification information and mobile terminal identifier number.In addition service parameter also can comprise application programming interfaces title and application protocol version, and therefore the first transmission data also comprise these parameters relevant to application program of timestamp, application programming interfaces title and application protocol version.
Alternatively, other service parameter can be chosen according to actual conditions, the signature etc. of the parameter of such as specified response form, transparent transmission field, above-mentioned input, if service parameter also comprises these data, so the first transmission data also correspondingly comprise these data.
Preferably, above-mentioned message token obtains request except carrying developer's account number, application name, application version and user account number identification information and mobile terminal identifier number these the first transmission data, also carries application programming interfaces title, these the first transmission data of application protocol version.Namely message token obtains request and carries signature, and for carrying out all data in addition to the key of signature calculation.
As the step 204 in Fig. 6, access server 4, after checking developer account number is legal, carries out authentication according to signature, verifies the legitimacy of mobile terminal, carries out safety check to the first transmission data simultaneously.After legitimate verification and safety check pass through, the request that obtained by described message token, by far call agreement, is transmitted to described push server;
Wherein, far call agreement can use the service framework (High-speedServiceFramework is called for short HSF) of far call, also can use the corresponding far call agreement of other application programs.
The checking developer account number polymerization process performed before the step 204 is: step 2041 access server 4 according to the developer's account number received, to the key that Developer Central Control Server 3 asks developer's account number corresponding; If Developer Central Control Server 3 finds this developer's account number, prove that this developer's account number is effectively, then corresponding key is sent to access server 4; Step 2042 subsequently access server 4 is inquired about this developer's account number to push server 5 and whether was registered application program in its database, if find this application name in push server 5, then prove that this developer's account number registered this application program in push server, now complete checking developer account number legal.
Step 204, access server 4 carries out authentication to signature: the first transmission data (timestamp, developer's account number, application name, application version, user account number identification information and the mobile terminal identifier number utilizing this double secret key to pass over, preferably also comprise application programming interfaces title, application protocol version) be encrypted algorithm md5 generation signature, compared with the signature that this signature and the mobile terminal received before are sent, if consistent, then authentication is passed through, and verifies that this mobile terminal is legal.
Safety check is carried out mainly to developer's account number, application name, application version, user account number identification information and mobile terminal identifier number to the first transmission data, also have application programming interfaces title and these data of application protocol version to carry out rule to verify, such as numeral, character string, whether length is legal conforms with the regulations.Meet these rules, then the first transmission data security.Safety check can adopt existing techniques in realizing, repeats no more herein.
As the step 205 in Fig. 6, push server 5 is according to mobile terminal identifier number, application name and user account number identification information searching message token in a database;
As the step 206 in Fig. 6 to be returned to by HSF as described in access server, access server 4 sends to described mobile terminal 1 by http protocol;
The detailed process that above-mentioned steps 205 obtains can be: push server 5 is from database 6, retrieve described mobile terminal identifier number (as IMEI, InternationalMobileEquipmentIdentity, International Mobile Equipment Identity code), application name and the message token corresponding to user account number identification information (userinfo);
If described database 6 exists corresponding described message token, then message token is taken out; Meanwhile, if when the application version carried in discovery message token acquisition request is different from there is application version in database, the upgraded version of application version can be taken out, return to access server together with message token;
Wherein, the upgraded version of application version be application server 2 each upgrade application version time, be stored in the database 6 of push server 5 by access server 4;
If there is not corresponding described message token in described database 6, then generate described message token according to described mobile terminal identifier number, application name and user account number identification information, and message token is obtained the mobile terminal identifier of asking to carry number, the message token of user account number identification information and generation is stored in database 6;
Preferably, carry out in the form of a list preserving these data in database 6, what wherein a line item stored is developer's account number, application name, application version, a mobile terminal identifier number, a user account number identification information of this application program and the message token by number generation of this application name, user account number identification information and mobile terminal identifier;
Because message token is generated by mobile terminal identifier number, application name and user account number identification information, therefore this message token points to the specific user account number on specific mobile device corresponding to specific application program.Push server, by these records stored, achieves when to application program for mobile terminal PUSH message data, there will not be the situation that message data is received by other user account number that other application program have received or be employed program.
As the step 206 in Fig. 6, access server 4 passes through http protocol return messages token to mobile terminal; This message token and user account number identification information, by message token, with Develop Application System person account number and the corresponding preservation of key, are then sent to application server by step 207 mobile terminal.Communication mode between mobile terminal and application server can be determined by application server.
As the step 208 in Fig. 6, application server 2 is according to user account number identification information, safeguard the corresponding relation between the user account number of this application program and message token, namely the user account number of this user account number identification information mark is uniquely to should message token, like this when application server has message data will be pushed to this user account number, can inquire message token by this user account number, the request of preserving of the message data then by carrying this message token and message data sends to push server to store.Now, application server 2 saves developer's account number and key, user account number identification information, and message token.
Wherein, mobile terminal 1 to push server 5 obtain described message token corresponding to application program can be change at user state information, application version upgrade and/or time interval of presetting registers and obtains described message token time carry out.Specifically, when this application program generation user account number switching on mobile terminal, user account number are nullified, mobile terminal can be initiated to initiate message token to push server and be obtained request; Or when application version is upgraded, also can initiate to initiate message token to push server and obtain request; Even can according to the time interval of mobile phone users setting, the message token under active user's account number of this application program of acquisition for mobile terminal.
For different application programs, obtain message token also just to trigger when installation, some application program can also when mobile terminal hangs up service, acquisition message token is registered as described above according to the time interval of setting, specifically when triggering acquisition message token, above-mentionedly be only example, do not limit, specifically set according to specifically different application programs.
Each application program on mobile terminal 1 is when obtaining message token to push server 5, if when obtaining to push server 5 first while there is not message token in database 6 (as described above), according to the mobile terminal identifier uploaded number, application name and user account number, push server 5 represents that these parameters of information carry out corresponding generating messages token, and the related data of sending first is stored, after registering acquisition message token first, when each triggering obtains message token, directly can obtain from database 6.
Step 12, according to the described message token from described application server 2 through verification received, or the information of application name and application version, the message data received stores by described push server 5;
Particularly, described step 12 is:
As the step 209 in Fig. 6, application server 2 is initiated message data by http protocol to access server 4 and is preserved request, described message data is preserved request and is carried: to the signature of developer's account number and key, second transmission data, these the second transmission data comprise developer's account number, message token or application name and application version, and message data;
Wherein, message data mainly comprises the holding time of message content, type of message and message.Group is when depositing message, and message data preserves request portable application program name and application version, and message list is deposited when namely storing private message, and the message data request of preserving only carries message token.These message datas can be at least one in logistics information, lastest imformation, sales promotion information, the various value-added message of picture or video etc.
As the step 210 in Fig. 6, access server 4, after checking developer account number is legal, carries out authentication according to signature, verifies the legitimacy of application server 2, and safety check is carried out to the second transmission data of carrying, and described message data is preserved request forward to push server 5;
Namely first perform the process shown in step 2041 and 2042, after then performing step 210 authentication, be transmitted to server.
The rule of signing to developer's account number and key is consistent with foregoing description, does not repeat them here.
Checking developer account number is legal consistent with the process shown in 2042 with above-described step 2041.
Carry out authentication to signing similar to verify that application server legitimacy and previous step 204 describe, difference is that utilizing the second transmission data to be encrypted algorithm md5 generates signature, does not repeat them here.
Carry out safety check to the second transmission data to transmit data to first to above-described to carry out safety check similar.
If preserve in request in message data and carry message token, then illustrate it is private message, refer to the message that a user account number of this application program of a directed mobile terminal pushes.As the step 211 in Fig. 2, push server 5 checks that whether this message token is consistent with the message token of storage, if consistent, in database 6, the application name of its correspondence of record is found again according to developer's account number, more consistent with the application name found in database 6 according to this message token, to judge the validity (unanimously then having validity) of this message token, if message token has validity, then according to message token, this message data and private message are stored corresponding to the record position in database, result is completed to access server 4 by far call protocol return request.Judge that the validity of this message token is to prevent application server from copying message token, attacking other application.Private message is the message data sent for specific user's account number.
When pocket transmission news, push server 5 is preserved according to message data and is asked the application name that carries and application version, searching database, meeting the correspondence position of record of this application name and application version, stores this message data.
The application utilizes message data to preserve in request and carries the storage that application name and application version can realize carrying out the user account number of all this application programs of use message data, to realize carrying out message push to all user account numbers of this application program under every all mobile terminals having installed this application program, namely achieve pocket transmission news data.
As the step 212 in Fig. 6, access server 4 is returned by http protocol and sends message data and preserve the result of request as successfully to application server 2.
Step 13, according to the described message token of the described mobile terminal 1 through verification received, described push server 5 mates the corresponding described message data of described message token from the described message data of described storage, and described message data is sent to described mobile terminal.
Particularly, step 13 is:
As the step 213 in Fig. 6, mobile terminal 1 initiates message data search request by http protocol at set intervals to access server 4, described message data search request comprises the signature to carrying out developer's account number and key, and the 3rd transmits data, the 3rd transmission data comprise developer's account number message token corresponding with this application program user account number;
As the step 214 in Fig. 6, access server 4 is after checking developer account number is legal, authentication is carried out according to signature, verify the legitimacy of mobile terminal 1, and safety check is carried out to the 3rd transmission data (developer's account number and message token), and message data search request is passed through far call protocol forward to push server 5;
Namely first perform the process shown in step 2041 and 2042, after then performing step 214 authentication, be transmitted to server.
Wherein, the rule of signing to developer's account number and key is consistent with foregoing description, does not repeat them here.
Checking developer account number is legal consistent with the process shown in 2042 with above-described step 2041.
Carry out authentication to verify that the legitimacy of mobile terminal 1 is similar with what describe in step 204 to signature, difference is that utilizing the 3rd transmission data to be encrypted algorithm md5 generates signature, does not repeat them here.
Safety check is carried out with above-mentioned described to the 3rd transmission data.
As the step 215 in Fig. 6, push server 5 receives message data search request, according to the message data stored in message token searching database 6, the list of the message data of coupling is sent to access server 4 by hsf; Wherein, to intercept according to certain list size, then the list of these message datas is sent to access server 4.
As the step 216 in Fig. 6, list is sent to mobile terminal 1 by http protocol by access server 4, thus completes the propelling movement of message data.
In above process, database 6 preserves developer's account number, application name, application version, mobile terminal identifier number (imei), the uniquely identified user account number identification information identifying the user account number of each application program, message token and data-message, and these information become corresponding relational storage.Namely corresponding application name, application version, mobile terminal identifier number (imei), user account number identification information and data-message can be got by token message.
User account number identification information is certain user account number corresponding uniquely can specify message data when an application program has multiple user account number, prevents and message data is pushed other user account numbers giving same application.
When above-mentioned push server 5 is to the related news of mobile terminal pushing application program, initiatively initiate message data search request by mobile terminal, push server 5 carries out the propelling movement of message according to this message data search request, and therefore the application achieves and initiatively initiates acquisition request message to be pushed by mobile terminal.
In three processes that above-mentioned steps 11, step 12 and step 13 describe, before access push server 5, all need the checking through access server 4 to verify, therefore, make use of third-party access server 4 to carry out legitimate verification and safety check, the ihone mobile phone as only having exclusive device certificate in prior art can be avoided could to carry out verifying the situation accessing with apple push server, all mobile terminals can be realized and obtain message by access server access push server, and without the need to specific mobile terminal.
Below, the application's message push device message push system is in actual applications introduced.See the system schematic of Fig. 7 the application message push.The system of this message push comprises mobile terminal 1, application server 2, Developer Central Control Server 3, access server 4, push server 5 and database 6.
Mobile terminal 1, for obtaining message token corresponding to described application program, and sends described message token;
Application server 2, for receive described mobile terminal send described message token, and send message data preserve request carry out message data storage;
Push server 5, for according to developer's account number corresponding to the application program on mobile terminal and key, and mobile terminal identifier number, application name and user account number identification information obtain described message token, and described message token is sent to mobile terminal; Preserve the described message token in asking or application name and application version according to the message data from described application server through verification received and carry out message data storage; And according to the described message token in the message data search request of the described mobile terminal through verification received, from the message data of described storage, mate the described message data that described message token is corresponding, and described message data is sent to described mobile terminal.
Access server 4, for the legitimacy of mobile terminal according to described signature verification, carry out safety check to the first transmission data, described first transmission data comprise described developer's account number, mobile terminal identifier number, application name, application version and user account number identification information; The legitimacy of application server according to described signature verification, and safety check is carried out to the second transmission data that described application server sends, described second transmission data comprise described developer's account number, message token or application name and application version and message data, and described message data is preserved request forward to push server; And safety check is carried out to the 3rd transmission data that described mobile terminal sends, described 3rd transmission data comprise described developer's account number and message token, and described message data search request is transmitted to push server.
Developer Central Control Server 3, for developer's account number described in described application server registers, generates corresponding key unique with described developer's account number and sends to described application server.
Database 6, preserve developer's account number, application name, application version, mobile terminal identifier number, user account number identification information, message token and data-message, these information become corresponding relational storage.
Wherein, the corresponding application program of usual application server, therefore developer's account number of application server and key namely this Develop Application System person's account number and key, after this application program downloads and installs by mobile phone users, this application program just carries this developer's account number and key, preserves on mobile terminals; And developer's account number of the application server registers corresponding to application program, key and application name, these information of version are also carried out record by Developer Central Control Server 3, and notifying developer's account number, application name and the version through registering to push server 5, push server will record these information.
Wherein, user account number identification information is the unique identification of the user of each application program of mark; Mobile terminal 1 is preserved these information such as user account number identification information of mobile terminal identifier number, certain Develop Application System person's account number and key, application name, version and this application program, and the message token corresponding with these information.
Can preferably carry out in the form of a list preserving these data in database 6, what wherein a line item stored is developer's account number, application name, application version, a mobile terminal identifier number, a user account number identification information of this application program and the message token by number generation of this application name, user account number identification information and mobile terminal identifier;
Because message token is generated by mobile terminal identifier number, application name and user account number identification information, therefore this message token points to the specific user account number on specific mobile device corresponding to specific application program.Push server, by these records stored, achieves when to application program for mobile terminal PUSH message data, there will not be the situation that message data is received by other user account number that other application program have received or be employed program.
This message push system can perform the detailed process shown in said method, does not repeat them here.The ihone mobile phone as only having exclusive device certificate in prior art can be avoided like this could to carry out verifying the situation accessing with apple push server, all mobile terminals can be realized and obtain message by access server access push server, and without the need to specific mobile terminal.
The application's message token and application name, mobile terminal identifier number and the binding of user account number identification information; message can accurately be delivered to affiliated third-party application; and support message cluster transmition; and adopt the short connection of HTTP between mobile terminal and server; can use on any mobile terminal, and less than the long problem connected of keep-alive.
Those of ordinary skill in the art should recognize further, in conjunction with unit and the algorithm steps of each example of embodiment disclosed herein description, can realize with electronic hardware, computer software or the combination of the two, in order to the interchangeability of hardware and software is clearly described, generally describe composition and the step of each example in the above description according to function.These functions perform with hardware or software mode actually, depend on application-specific and the design constraint of technical scheme.Professional and technical personnel can use distinct methods to realize described function to each specifically should being used for, but this realization should not think the scope exceeding the application.
The software module that the method described in conjunction with embodiment disclosed herein or the step of algorithm can use hardware, processor to perform, or the combination of the two is implemented.Software module can be placed in the storage medium of other form any known in random asccess memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or technical field.
Above-described embodiment; the object of the application, technical scheme and beneficial effect are further described; be understood that; the foregoing is only the embodiment of the application; and be not used in the protection range limiting the application; within all spirit in the application and principle, any amendment made, equivalent replacement, improvement etc., within the protection range that all should be included in the application.
Claims (10)
1. an information push method, is characterized in that, comprising:
Receipt message token obtains request, and described message token obtains request and comprises mobile terminal identifier number, application name and user account number identification information; Described message token and described application name, described mobile terminal identifier number and described user account number identification information are bound;
Send described mobile terminal identifier number, application name and the message token corresponding to user account number identification information;
Receipt message data preserve request, and the request of preserving of described message data comprises the message data of described message token and correspondence thereof, or the message data of application name and application version and its correspondence;
The message data of its correspondence is stored according to described message token or application name and application version; Wherein, when according to application name and application version storing message data, for the message token of application name and version carrying out the storage of message data;
Receive the message data search request carrying described message token;
The message data that the described message token that transmission finds out from the message data of described storage according to described message token mates.
2. information push method according to claim 1, is characterized in that, also comprises:
Receive developer's account number, described application name and application version and corresponding stored.
3. information push method according to claim 1, it is characterized in that, after described receipt message token obtains request, before the described mobile terminal identifier of described transmission number, application name and the message token corresponding to user account number identification information, also comprise:
Retrieve described mobile terminal identifier number, application name and the message token corresponding to user account number identification information in a database;
If there is described mobile terminal identifier number, application name and the message token corresponding to user account number identification information, then take out this message token;
If there is no described mobile terminal identifier number, application name and the message token corresponding to user account number identification information, then according to described mobile terminal identifier number, application name and user account number identification information generating messages token, and store the message token of described mobile terminal identifier number, user account number identification information and correspondence.
4. information push method according to claim 1, is characterized in that, also comprises:
Verify that described message token obtains request, to preserve developer's account number of carrying in request or message data search request be effective to message data, and described in developer's account number of carrying registered application program corresponding to described developer's account number in a database;
The signature carried in request, message data preservation request or message data search request is obtained to the described message token received and carries out authentication.
5. information push method according to claim 1, is characterized in that,
After described receipt message data preserve request, described store the message data of its correspondence according to described message token before, also comprise:
The described message token relatively carried and the message token of storage, when comparative result is consistent, perform:
The application name of the storage that the application name comparing the storage found according to developer's account number of carrying in described message data search request finds with the described message token carried described in basis; When comparative result is consistent, perform the step of the message data storing its correspondence according to described message token.
6. a message push device, is characterized in that, comprising:
Token request receiving element, obtains request for receipt message token, and described message token obtains request and comprises mobile terminal identifier number, application name and user account number identification information; Described message token and described application name, described mobile terminal identifier number and described user account number identification information are bound;
Token transmitting element, for sending the message token corresponding to described mobile terminal identifier number, application name and user account number identification information;
Message preserves receiving element, preserves request for receipt message data, and the request of preserving of described message data comprises the message data of described message token and correspondence, or the message data of application name and application version and its correspondence;
Specimens preserving unit, for storing the message data of its correspondence according to described message token or application name and application version; Wherein, when according to application name and application version storing message data, for the message token of application name and version carrying out the storage of message data;
Message request receiving element, for receiving the message data search request carrying described message token;
Message sending unit, for sending the message data that the described message token that finds out from the message data of described storage according to described message token mates.
7. message push device according to claim 6, is characterized in that, also comprise:
Receiving element, carries out corresponding stored for receiving developer's account number, described application name and application version.
8. the device of message push according to claim 6, is characterized in that, also comprises:
Retrieval unit, for retrieving the message token corresponding to described mobile terminal identifier number, application name and user account number identification information in a database;
Token retrieval unit, if for there is the message token corresponding to described mobile terminal identifier number, application name and user account number identification information, then take out this message token;
Token generation unit, for when there is not the message token corresponding to described mobile terminal identifier number, application name and user account number identification information, according to described mobile terminal identifier number, application name and user account number identification information generating messages token, and store the message token of described mobile terminal identifier number, user account number identification information and correspondence.
9. message push device according to claim 6, is characterized in that, also comprise:
Authentication unit, for verifying that described message token obtains request, to preserve developer's account number of carrying in request or message data search request be effective to message data, and described in developer's account number of carrying registered application program corresponding to described developer's account number in a database;
Authenticating unit, carries out authentication for obtaining the signature carried in request, message data preservation request or message data search request to the described message token received.
10. message push device according to claim 6, is characterized in that, also comprise:
First comparing unit, whether consistent with the message token of storage for the described message token carried described in relatively;
Second comparing unit, whether the application name of the storage that the application name for comparing the storage found according to developer's account number of carrying in described message data search request finds with the described message token carried described in basis is consistent.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110302984.5A CN103037312B (en) | 2011-10-08 | 2011-10-08 | Information push method and device |
| HK13106365.9A HK1179459A1 (en) | 2011-10-08 | 2013-05-29 | Method and device for pushing information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110302984.5A CN103037312B (en) | 2011-10-08 | 2011-10-08 | Information push method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103037312A CN103037312A (en) | 2013-04-10 |
| CN103037312B true CN103037312B (en) | 2016-03-16 |
Family
ID=48023712
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110302984.5A Active CN103037312B (en) | 2011-10-08 | 2011-10-08 | Information push method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN103037312B (en) |
| HK (1) | HK1179459A1 (en) |
Families Citing this family (37)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103209389B (en) * | 2013-04-16 | 2016-04-20 | 百度在线网络技术（北京）有限公司 | Short message push method, note supplying system and note push cloud server |
| CN104125063B (en) * | 2013-04-28 | 2016-10-12 | 腾讯科技（深圳）有限公司 | Authorization and authentication method, equipment and system |
| CN103313245B (en) * | 2013-05-28 | 2016-04-20 | 中国联合网络通信集团有限公司 | Based on the Network access method of mobile phone terminal, equipment and system |
| CN104349288B (en) * | 2013-07-25 | 2020-04-07 | 腾讯科技（深圳）有限公司 | Message transmission method and device |
| CN103501486B (en) * | 2013-09-29 | 2016-09-28 | 华为软件技术有限公司 | A kind of information push method and push server |
| CN104767775B (en) * | 2014-01-06 | 2019-09-17 | 腾讯科技（深圳）有限公司 | Web application information push method and system |
| CN104023334B (en) * | 2014-05-19 | 2019-10-29 | 联想(北京)有限公司 | A kind of information processing method and electronic equipment |
| CN104158722B (en) * | 2014-07-21 | 2016-11-09 | 小米科技有限责任公司 | For light information push method, device, terminal and the server applied |
| CN105516221B (en) * | 2014-09-24 | 2018-12-14 | 阿里巴巴集团控股有限公司 | Information transmission system and method |
| CN105981356B (en) * | 2014-11-05 | 2020-01-10 | 华为技术有限公司 | Information sending and processing method and device |
| CN104539577A (en) * | 2014-11-27 | 2015-04-22 | 英业达科技有限公司 | Information push system and information push method |
| CN105991614B (en) * | 2015-03-03 | 2019-07-23 | 阿里巴巴集团控股有限公司 | It is a kind of it is open authorization, resource access method and device, server |
| CN104618517B (en) * | 2015-03-05 | 2018-08-07 | 国家电网公司 | A kind of method, system and device of PUSH message |
| US9749323B2 (en) * | 2015-03-27 | 2017-08-29 | Intel Corporation | Technologies for secure server access using a trusted license agent |
| CN106161563B (en) * | 2015-04-23 | 2019-02-15 | 博雅网络游戏开发（深圳）有限公司 | Information push method and device |
| CN105897696B (en) * | 2016-03-25 | 2019-08-23 | 努比亚技术有限公司 | A kind of terminal, server-side and terminal access management method |
| CN107592324B (en) * | 2016-07-06 | 2021-04-09 | 阿里巴巴（中国）有限公司 | Message pushing method and device and portable terminal equipment |
| CN106162582A (en) * | 2016-07-22 | 2016-11-23 | 努比亚技术有限公司 | A kind of message based on multi-user isolation method for pushing and system thereof |
| CN106385491B (en) * | 2016-09-05 | 2019-10-29 | 努比亚技术有限公司 | A kind of system, method and mobile terminal controlling PUSH message |
| CN108243158A (en) * | 2016-12-26 | 2018-07-03 | 中移(苏州)软件技术有限公司 | A kind of method and apparatus of safety certification |
| CN108259437B (en) * | 2016-12-29 | 2021-06-04 | 北京神州泰岳软件股份有限公司 | HTTP access method, HTTP server and system |
| CN109286648B (en) * | 2017-07-21 | 2020-11-06 | 比亚迪股份有限公司 | Data pushing method, device and system and terminal equipment |
| CN109756337B (en) * | 2017-11-06 | 2022-01-07 | 北京京东尚科信息技术有限公司 | Secure access method and device for service interface |
| CN108228451A (en) * | 2017-12-22 | 2018-06-29 | 五八有限公司 | A kind of information push method, equipment and computer readable storage medium |
| CN108234653A (en) * | 2018-01-03 | 2018-06-29 | 马上消费金融股份有限公司 | Method and device for processing service request |
| CN110381100B (en) * | 2018-04-13 | 2022-03-29 | 佛山市顺德区美的电热电器制造有限公司 | Message pushing method, server and computer readable storage medium |
| CN110753023B (en) * | 2018-07-24 | 2022-02-25 | 阿里巴巴集团控股有限公司 | Equipment authentication method, equipment access method and device |
| CN110149363A (en) * | 2019-04-15 | 2019-08-20 | 深圳壹账通智能科技有限公司 | A kind of information push method, device and storage medium |
| CN110071926B (en) * | 2019-04-26 | 2021-07-30 | 秒针信息技术有限公司 | Data processing method and device |
| CN110213234B (en) * | 2019-04-30 | 2022-06-28 | 深圳市腾讯计算机系统有限公司 | Application program file developer identification method, device, equipment and storage medium |
| CN111181908B (en) * | 2019-08-05 | 2021-11-26 | 腾讯科技（深圳）有限公司 | Applet login method, device and storage medium |
| CN111147746B (en) * | 2019-12-30 | 2020-10-23 | 深圳市金龙锋科技有限公司 | Intelligent early education equipment terminal management method |
| CN111835869B (en) * | 2020-07-30 | 2023-06-16 | 上海茂声智能科技有限公司 | Method, system, equipment and storage medium for centralized control of terminal content |
| CN114553814B (en) * | 2020-10-27 | 2024-02-09 | 花瓣云科技有限公司 | Method and device for processing push message |
| CN112905962B (en) * | 2021-03-04 | 2021-11-30 | 深圳市航顺芯片技术研发有限公司 | Method for protecting program codes in MCU, intelligent terminal and storage medium |
| CN113536134A (en) * | 2021-07-30 | 2021-10-22 | 北京乐学帮网络技术有限公司 | Message pushing method and device, electronic equipment and readable storage medium |
| CN116112236A (en) * | 2023-01-06 | 2023-05-12 | 深圳感臻智能股份有限公司 | Authentication and data transmission method based on intelligent device ecology and intelligent television |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101202753A (en) * | 2007-11-29 | 2008-06-18 | 中国电信股份有限公司 | Method and device for accessing plug-in connector applied system by client terminal |
| CN101507309A (en) * | 2006-08-21 | 2009-08-12 | Lm爱立信电话有限公司 | Selective control of user equipment capabilities |
| KR20110101964A (en) * | 2010-03-10 | 2011-09-16 | (주) 지겟츠 | Message receiving device within specific application and method thereof |
-
2011
- 2011-10-08 CN CN201110302984.5A patent/CN103037312B/en active Active
-
2013
- 2013-05-29 HK HK13106365.9A patent/HK1179459A1/en unknown
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101507309A (en) * | 2006-08-21 | 2009-08-12 | Lm爱立信电话有限公司 | Selective control of user equipment capabilities |
| CN101202753A (en) * | 2007-11-29 | 2008-06-18 | 中国电信股份有限公司 | Method and device for accessing plug-in connector applied system by client terminal |
| KR20110101964A (en) * | 2010-03-10 | 2011-09-16 | (주) 지겟츠 | Message receiving device within specific application and method thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| HK1179459A1 (en) | 2013-09-27 |
| CN103037312A (en) | 2013-04-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103037312B (en) | Information push method and device | |
| CN109961292B (en) | Block chain verification code application method, equipment and storage medium | |
| CN107294729B (en) | Communication method and device between different nodes in block chain | |
| CN109639661B (en) | Server certificate updating method, device, equipment and computer readable storage medium | |
| CN102970362B (en) | The method of a kind of high in the clouds data sharing and device | |
| CN102625297B (en) | For identity management method and the device of mobile terminal | |
| CN109831527B (en) | File processing method, user side, server and readable storage medium | |
| CN104349288B (en) | Message transmission method and device | |
| US20070038681A1 (en) | System and method of remote storage of data through connection from a server to a client | |
| CN102378170A (en) | Method, device and system of authentication and service calling | |
| CN102231746A (en) | Method for validating identification information and terminal thereof | |
| CN108989040B (en) | Information processing method and device based on block chain | |
| CN105262588A (en) | Log-in method based on dynamic password, account number management server and mobile terminal | |
| CN106664308B (en) | Device authentication prior to enrollment | |
| CN104486388A (en) | Accessing method and device of cloud storage file | |
| CN106790296B (en) | Domain name record verification method and device | |
| CN102970308B (en) | A kind of user authen method and server | |
| CN103780580A (en) | Method, server and system for providing capability access strategy | |
| CN102984277B (en) | Prevent the system and method that malice connects | |
| CN112311779B (en) | Data access control method and device applied to block chain system | |
| WO2011023122A1 (en) | Method, device and system for routing service | |
| CN112311769B (en) | Method, system, electronic device and medium for security authentication | |
| CN114841697A (en) | Block chain based electronic contract chain on-line verification, signing and checking system and method | |
| US9548969B2 (en) | Encryption/decryption method, system and device | |
| CN107318100B (en) | Method, device and system for binding mobile phone number |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1179459 Country of ref document: HK |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: GR Ref document number: 1179459 Country of ref document: HK |