CN103037312A - Message push method and message push device - Google Patents
Message push method and message push device Download PDFInfo
- Publication number
- CN103037312A CN103037312A CN2011103029845A CN201110302984A CN103037312A CN 103037312 A CN103037312 A CN 103037312A CN 2011103029845 A CN2011103029845 A CN 2011103029845A CN 201110302984 A CN201110302984 A CN 201110302984A CN 103037312 A CN103037312 A CN 103037312A
- Authority
- CN
- China
- Prior art keywords
- message
- token
- account number
- request
- application
- 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.)
- Granted
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention relates to a message push method and a message push device. The message push method includes sending a message token acquisition request, wherein the message token acquisition request comprises a mobile terminal device identification number, an application program name and user account identification information; receiving message tokens corresponding to the mobile terminal device identification number, the application program name and the user account identification information; sending message data searching requests carrying the message tokens; and receiving the message data matched with the message tokens and searched out according to the message tokens. Therefore, the message push method and the message push device are applicable to any mobile terminal and do not need maintenance of a keep-alive hand grip. Due to the fact that the message tokens, the software name, the mobile terminal device identification number and the user account identification information are bound together, a message can be transmitted to the mobile terminal accurately.
Description
Technical field
The application relates to network communication field, relates in particular to a kind of information push method and device.
Background technology
At present, a lot of portable terminals are all supported wireless network, the user can install client software at portable terminal and subscribe to Internet service, and the service provider of the Internet can issue to client, PUSH message, and client is received after these message by showing interface to the user.In addition, the service provider can also be 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 Apple is supported in PUSH message on the iPhone cell phone platform at present.Its workflow is:
Phase I: third-party server is issued the push server of apple to the packing of the sign of the message that will send, purpose iPhone;
Second stage: the push server of apple is searched the iPhone that respective identification is arranged in the iPhone tabulation of the registered Push service of self, and message is dealt into iPhone;
Phase III: iPhone passes to corresponding application program to the message of sending, and according to setting, ejects the Push notice.
Before the push server of iphone mobile phone and Apple is formally communicated by letter, need to set up in advance a long-chain based on the encryption of safe transmission layer protocol (Transport Layer Security is called for short TLS) and connect.Each normal iPhone has an exclusive device certificate, and the push server also has a server certificate.When setting up link, both can verify certificate validity each other.The TLS link is in case foundation in the situation that there are not data, only need to carry out every 15 minutes shaking hands of a keep-alive, and in case because accidental cause causes link interruption, iPhone can constantly attempt setting up the TLS link again, until successful.The TLS encryption connection need to verify mutually with certificate each other, and this has determined that this system can only be used for the iPhone mobile phone, can not be applied to other portable terminals.
But because mobile terminal client terminal is connected long connection often by the cut-out of the mobile gateway of operator in the mobile Internet with server end, need often to send shaking hands of keep-alive so safeguard a long connection, need to rebulid connection in the time of more.
And when the iPhone mobile phone was connected the TLS connection at every turn with the push server, the push server was by every device certificate checking that normal iPhone is unique, and this device certificate is encrypted generation with iPhone mobile phone activation key.After the device certificate checking was passed through, the push server can return to iPhone to the device token corresponding to every iPhone, and corresponding Push application program then directly sends to third party service provider returning the device token of coming.Like this, when third party service provider has Push message to send, just device token and Push message are sent to the push server together, the push server finds the iPhone of corresponding TLS link again according to device token, and sends corresponding Push message.
Therefore, such scheme is with device token and iPhone handset binding, and distinguish message with device token, on the application program under this can not accurately be pushed to Push message, when an iPhone mobile phone exists a plurality of third parties to use, 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 because for a plurality of different application program on the iPhone mobile phone, the device token of use is same.Simultaneously because the each PUSH message of third party service provider is to push according to device token, therefore third party service provider can only one by one send to the push server stores with this push message according to the token of every iphone mobile phone when needs push same push message to many iPhone mobile phones.
Summary of the invention
The application's purpose is, a kind of information push method and device are provided, with message token and application name, mobile terminal equipment to identify number and the binding of user account number identification information, to realize that accurately PUSH message is in affiliated application program.
For achieving the above object, the application provides a kind of information push method, and the method comprises:
Send the message token and obtain request, the request of obtaining of described message token comprises mobile terminal equipment to identify number, application name and user account number identification information;
Receive described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information;
Transmission carries the message data search request of described message token;
The message data that the described message token that reception goes out according to described message token lookup mates.
The application provides a kind of information push method, and the method comprises:
The receipt message token obtains request, and the request of obtaining of described message token comprises mobile terminal equipment to identify number, application name and user account number identification information;
Send described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information;
The request of preserving of receipt message data, the request of preserving of described message data comprises described message token and corresponding message data thereof, perhaps application name and application version with and corresponding message data;
Store this message data according to described message token or application name and application version;
Reception carries the message data search request of 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.
The application also provides a kind of message push device, and this device comprises:
The token request transmitting element be used for to send the message token and obtains request, and the request of obtaining of described message token comprises mobile terminal equipment to identify number, application name and user account number identification information;
The token receiving element is used for receiving described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information;
The message request transmitting element is used for sending the message data search request that carries described message token;
The message sink unit, the message data that the described message token that goes out according to described message token lookup for reception mates.
The application also provides a kind of message push device, and this device comprises:
The token request receiving element is used for the receipt message token and obtains request, and the request of obtaining of described message token comprises mobile terminal equipment to identify number, application name and user account number identification information;
The token transmitting element is used for sending described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information;
Message is preserved receiving element, is used for the receipt message data and preserves request, and the request of preserving of described message data comprises described message token and corresponding message data, perhaps application name and application version with and corresponding message data;
Preserve processing unit, be used for storing its corresponding message data according to described message token or application name and application version;
The message request receiving element is used for receiving the message data search request that carries described message token;
Message sending unit be used for to send 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 portable terminal, does not need to safeguard that keep-alive shakes hands; Message token and dbase, mobile terminal equipment to identify number and user account number identification information are bound together, and message can accurately be delivered to portable terminal.
Description of drawings
Fig. 1 is the schematic diagram of the application's 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's 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 diagram 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 application's technical scheme is described in further detail.
The application is by binding message token and application name, mobile terminal equipment to identify number and user account number identification information, thereby realized the accurate propelling movement of message.
Fig. 1 is the schematic diagram of the application's one embodiment information push method.As shown in the figure, the present embodiment method for pushing for example can use the various portable terminals of network for client, includes, but are not limited to desktop computer, mobile phone, notebook, panel computer etc.
The present embodiment may further comprise the steps as shown in the figure:
Send that the request of obtaining of message token can change at user state information, application version upgrades and/or the predefined time interval registers when obtaining described message token and carries out.Specifically, after this application program on the portable terminal had been registered user account number, when user account number switching, user account number cancellation occured, portable terminal can be initiated to initiate the message token to push server and be obtained request; Perhaps when application version is upgraded, also can initiate to initiate the message token to push server and obtain request; Even can be 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, the message token obtains request and also can just trigger when installing, some application program can also be when portable terminal be hung up service, register according to the time interval of setting as described above and obtain the message token, specifically trigger the message token when and obtain request, above-mentioned is example only, does not limit, and specifically sets according to concrete different application program.
Preferably, described message token generates according to described mobile terminal equipment to identify number, application name and user account number identification information.
Further, the present embodiment also comprises before step 101:
Step 100 receives developer's account number and key and stores.
Portable terminal is when the down load application program, and application program carries developer's account number and key, therefore, in portable terminal down load application program, can receive this application program corresponding developer's account number and key.
Alternatively, obtain in the request at the message token of step 101, except mobile terminal equipment to identify number, application name and user account number identification information, also can comprise signature and developer's account number of carrying out according to developer's account number and key.
Alternatively, when the request of obtaining of the token of message described in the step 101 also comprises signature and during developer's account number, after legal and signature passed through authentication when the checking of developer's account number, execution in step 102 again.
Alternatively, except comprising the message token, also can comprise developer's account number and the signature that developer's account number and key are carried out in the described message data search request of step 103.
Alternatively, when message data search request in the step 103 also comprises signature and during developer's account number, after legal and signature passes through authentication when the checking of developer's account number, execution in step 102.
Wherein, the checking authentication can be realized by other third-party server.Specific implementation can be referring to following associated description.
Preferably, the present embodiment also can comprise: transmit the described message token and the described user account number identification information that receive.After portable terminal receives the message token, can immediately this message token and user account number identification information be transmitted to application server, also can certain constantly with its transmission, be not construed as limiting at this.Application server is safeguarded the corresponding relation of this user account number identification information and message token, application server can be when determining to send out message data to certain user like this, inquire corresponding message token according to the user account number identification information, then this message token and message data are issued push server.
This embodiment of the application has realized carrying out for a user account number of an application program on the portable terminal the accurate propelling movement of message data by message token and mobile terminal identification number, application name and user account number identification information is corresponding.
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 as main body, for example is used for the push server of PUSH message for server end.The present embodiment information push method may further comprise the steps:
Step 1001, the receipt message token obtains request, and the request of obtaining of described message token comprises mobile terminal equipment to identify number, application name and user account number identification information;
Step 1002 sends described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information;
Step 1003, the receipt message data are preserved request, and the request of preserving of described message data comprises described message token and corresponding message data thereof, perhaps application name and application version and corresponding message data thereof;
Step 1004 is stored its corresponding message data according to described message token or application name and application version;
When according to the message token in database during the storing message data because the uniqueness of message token, what deposit is message data for the user account number of a specific 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 should application name and all message tokens of version carry out the storage of message data, namely all user account numbers of this application program carry out the storing message data, realize storing this message data to the user account number of a plurality of application programs on many portable terminals.This process can be called as the group and deposit message.
Step 1005 receives the message data search request that carries described message token;
Step 1006 sends and finds out the message data that described message token mates according to described message token from the message data of described storage.
Preferably, the present embodiment also can comprise:
Step 1000 receives developer's account number, described application name and application version and carries out one by one corresponding stored.
As developer corresponding to certain application program when for example third party's application server is registered to the Developer Central Control Server, the Developer Central Control Server carries out record with information such as developer's account number, key and the application name of the corresponding application server registers of application program, versions, and developer's account number, application name and the version of the process registration of notice push server, push server receives developer's account number, described application name and application version and carry out one by one corresponding stored in 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 steps:
Obtain when asking if send first the message token, generate corresponding message token according to the mobile terminal equipment to identify of uploading number, application name and user account number identification information, and the related data that will send is first stored, after obtaining first the message token, when each triggering message token afterwards obtains request, can from database 6, directly obtain this message token.
Alternatively, in the described step 1001, this message token obtains in the request except mobile terminal equipment to identify number, application name and user account number identification information, also can comprise the signature that developer's account number and key are carried out, and developer's account number.
Preferably, the present embodiment also comprised before step 1001 as shown in the figure:
Wherein, checking developer account number is for effectively being to have registered then for effective by this developer's account number in the retrieval Developer Central Control Server.
Step 300 is obtained the signature that carries in the request to the described message token that receives and is carried out authentication.Concrete authentication process can be referring to following associated description.Alternatively, in the request of preserving of step 1003 message data, also can comprise the signature that developer's account number and key are carried out, and developer's account number.
This message data request of preserving can by third-party server for example application server send, perhaps the applying unit of this push server sends.
Similarly, before step 1003 receipt message data are preserved request, also can whether legal through step 200 and 300 (not shown)s checking developer account number, and the described message data that receives is preserved the signature that carries in the request carry out authentication.
Alternatively, the described message data search request of step 1005 yet can comprise the signature that developer's account number and key are carried out except comprising the message token, and developer's account number.
Similarly, before step 1005 reception carries the message data search request of described message token, also can verify whether developer's account number is legal through step 200 and 300 (not shown)s, and the signature that carries in the message data search request that receives is carried out authentication.
Step 200 and 300 can be to be undertaken by the authentication unit in the push server, perhaps by third-party server for example access server carry out.
Preferably, when described message data is preserved when also carrying developer's account number in the request, the embodiment of the present application receives the message data that comprises message token and corresponding message data thereof in step 1003 and preserves request and step 1004 and also comprise between according to its corresponding message data of message token store:
Relatively receive this message token that carries in the message data preservation request whether consistent with the message token of storage; Developer's account number that more relatively request of preserving is also carried according to message data finds its corresponding application name of record in database consistent with the application name that the message token lookup of carrying according to this arrives, consistency according to comparative result, judge the validity (step 1030) of this message token, if namely all unanimously then possess validity.If the message token possesses validity, then can carry out the message data storage.Can prevent like this application server imitation message token, the application of attacking other is to improve the fail safe of using.
This embodiment of the application has realized carrying out for a user account number of an application program on the portable terminal the accurate propelling movement of message data by message token and mobile terminal identification number, application name and user account number identification information is corresponding.
The above has described the embodiment of the present application information push method, the following describes to realize the message push device of this method for pushing.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 be used for to send the message token and obtains request, and the request of obtaining of described message token comprises mobile terminal equipment to identify number, application name and user account number identification information;
Token receiving element 32 is used for receiving described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information;
Message request transmitting element 33 is used for sending the message data search request that carries described message token;
As shown in the figure, the application's message push device also comprises:
Account number key reception unit 35 is used for receiving developer's account number and key is stored.
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 is used for the receipt message token and obtains request, and the request of obtaining of described message token comprises mobile terminal equipment to identify number, application name and user account number identification information;
Token transmitting element 42 sends described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information;
Message is preserved receiving element 43, is used for the receipt message data and preserves request, and the request of preserving of described message data comprises described message token and corresponding message data thereof, perhaps application name and application version and corresponding message data thereof;
Preserve processing unit 44, be used for storing its corresponding message data according to described message token or application name and application version;
Message request receiving element 45 is used for receiving the message data search request that carries described message token;
This message push device also comprises:
Receiving element is used for receiving developer's account number, described application name and application version and carries out corresponding stored.
As shown in the figure, this message push device also comprises:
This message push device also comprises:
Authentication unit, be used for verifying that developer's account number that the described message token request of obtaining, message data preservation request or message data search request are carried is effectively, and described developer's account number of carrying had been registered application program corresponding to described developer's account number in database;
Authenticating unit is used for the signature that the described message token request of obtaining, message data preservation request or the message data search request that receive are carried is carried out authentication.
This message push device also comprises:
The first comparing unit is used for the more described described message token that carries and the message token of storage;
The second comparing unit, the application name of the application name of the storage that the developer's account number that is used for relatively carrying according to described message data search request finds and the storage of arriving according to described described message token lookup of carrying.
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 the message data storage.This first comparing unit and the second comparing unit can prevent application server imitation message token, and the application of attacking other is to improve the fail safe of using.
This embodiment of the application has realized carrying out for a user account number of an application program on the portable terminal the accurate propelling movement of message data by message token and mobile terminal identification number, application name and user account number identification information is corresponding.
The below introduces the information push method combined process in actual applications of information push method and the server side of the application's mobile terminal side.Referring to Fig. 5, it shows the process schematic diagram of the application's information push method in the actual application; And Fig. 6, it shows the signaling method flow chart of the information push method in the application's actual application.For the ease of understanding, each equipment that relates in the process that is described below can be referring to Fig. 7, and it shows the in actual applications schematic diagram of message push system of the application.This information push method comprises:
Particularly, in the signaling method flow chart as shown in Figure 6, step 10 can comprise following process:
Step 201, application server 2 applies to become legal developer to Developer Central Control Server 3 registration developer account numbers;
Step 202, Developer Central Control Server 3 generates unique developer's account number and key, returns to application server 2.Later on each request of application server 2, application server 2 all needs to be encrypted authentication (legitimacy of the checking application server that namely below will describe) with upper developer's account number and these 2 values of key.
Wherein, usually corresponding application program of application server, so developer's account number of application server and key be developer's account number and the key of this application program namely.The Developer Central Control Server carries out record with information such as developer's account number, key and the application name of the corresponding application server registers of application program, versions, and developer's account number, application name and the version of the process registration of notice push server, push server will record these information, shown among Fig. 6 2021.
Wherein, the user is after portable 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 is kept on the portable terminal; And user's registered user's account number on this application program, generate the corresponding user account number identification information of this user account number at portable terminal, and be kept on this portable terminal.The user account number identification information is user's's (also being user account number) of each application program of sign unique identification; Therefore, preserve mobile terminal equipment to identify number, developer's account number of certain application program and the information such as user account number identification information of key, application name, version and this application program on the portable terminal 1, and corresponding with these information below with the message token of describing.
Particularly, in the signaling method flow chart as shown in Figure 2, this step 11 is specially:
Such as the step 203 among Fig. 6, the message token that described portable terminal 1 is initiated described application program by http protocol to access server 4 obtains request, the request of obtaining of this message token comprises: the signature that developer's account number and the key of this application program carried out, and first the transmission of data, this first the transmission of data comprises developer's account number, application name, application version and user account number identification information and mobile terminal equipment to identify number;
Wherein, the rule that developer's account number and key are signed can be, utilize cryptographic algorithm message digest algorithm 5 (message digest algorithm 5 is called for short md5) that developer's account number, key, service parameter and timestamp are encrypted calculating.Wherein service parameter comprises these first the transmission of datas such as application name, application version and user account number identification information and mobile terminal equipment to identify number.In addition service parameter also can comprise application programming interfaces title and application protocol version, and therefore the first the transmission of data also comprises these parameters relevant with application program of timestamp, application programming interfaces title and application protocol version.
Alternatively, other service parameter can be chosen according to actual conditions, and such as signature of the parameter of specified response form, transparent transmission field, above-mentioned input etc., if service parameter also comprises these data, the first the transmission of data also correspondingly comprises these data so.
Preferably, the request of obtaining of above-mentioned message token is also carried application programming interfaces title, these first the transmission of datas of application protocol version except having carried developer's account number, application name, application version and user account number identification information and mobile terminal equipment to identify number these first the transmission of datas.Be that the request of obtaining of message token carries signature, and all data except key that are used for carrying out signature calculation.
Such as the step 204 among Fig. 6, access server 4 according to signature is carried out authentication, is verified the legitimacy of portable terminal after checking developer account number is legal, simultaneously the first the transmission of data is carried out safety check.After legitimate verification and safety check pass through, the request of obtaining of described message token by the far call agreement, is transmitted to described push server;
Wherein, the service framework (High-speed Service Framework is called for short HSF) that the far call agreement can be used far call also can use the corresponding far call agreement of other application programs.
The legal process of checking developer account number of carrying out before step 204 is: step 2041 access server 4 is according to the developer's account number that receives, to the corresponding key of Developer Central Control Server 3 request developer's account numbers; 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; Whether step 2042 subsequently access server 4 registered application program to push server 5 these developer's account numbers of inquiry in its database, if in push server 5, find this application name, prove that then this developer's account number registered this application program in push server, it is legal that finished checking developer account number this moment.
Step 204,4 pairs of signatures of access server carry out authentication: utilize this key to the first the transmission of data of passing over (timestamp, developer's account number, application name, application version, user account number identification information and mobile terminal equipment to identify number, preferably also comprise application programming interfaces title, application protocol version) be encrypted algorithm md5 and generate signature, this signature is compared with the signature that the portable terminal that receives before sends, if consistent, then authentication is passed through, and verifies that this portable terminal is legal.
It mainly is to developer's account number, application name, application version, user account number identification information and mobile terminal equipment to identify number that the first the transmission of data is carried out safety check, also have application programming interfaces title and these data of application protocol version to carry out regular verification, whether legal up to specification such as numeral, character string, length.Meet these rules, then the first the transmission of data safety.Safety check can adopt existing techniques in realizing, repeats no more herein.
Such as the step 205 among Fig. 6, push server 5 is according to mobile terminal equipment to identify number, application name and user account number identification information searching message token in database;
Access server as described in returning to by HSF such as the step 206 among Fig. 6, access server 4 sends to described portable terminal 1 by http protocol;
The detailed process that above-mentioned steps 205 is obtained can be: push server 5 is from database 6, retrieve described mobile terminal equipment to identify number (such as IMEI, International Mobile Equipment Identity, International Mobile Equipment Identity code), application name and the corresponding message token of user account number identification information (userinfo);
If there is corresponding described message token in described database 6, then the message token is taken out; Meanwhile, if finding that the message token obtains in the application version that carries in the request and the database exists application version not simultaneously, can be with the upgraded version taking-up of application version, and the message token returns to access server together;
Wherein, the upgraded version of application version is application server 2 each when upgrading application version, is stored into by access server 4 in the database 6 of push server 5;
If there is not corresponding described message token in described database 6, then generate described message token according to described mobile terminal equipment to identify number, application name and user account number identification information, and the message token store of the mobile terminal equipment to identify that the request of obtaining of message token is carried number, user account number identification information and generation is in database 6;
Preferably, in database 6, preserve these data with the form of tabulation, wherein line item storage is developer's account number, application name, application version, mobile terminal equipment to identify number, user account number identification information of this application program and the message token that number is generated by this application name, user account number identification information and mobile terminal equipment to identify;
Because the message token is generated by mobile terminal equipment to identify number, application name and user account number identification information, so this message token points to the specific corresponding specific user account number of application program on the specific mobile device.Push server has realized to application program for mobile terminal PUSH message data the time by these records of storage, message data had been received or be employed other user account number reception of program by other application program situation can not occur.
Such as the step 206 among Fig. 6, access server 4 passes through http protocol return messages token to portable terminal; Step 207 portable terminal is with the message token, and then developer's account number and the corresponding preservation of key with application program send to application server with this message token and user account number identification information.Communication mode between portable terminal and the application server can be determined by application server.
Such as the step 208 among Fig. 6, application server 2 is according to the user account number identification information, safeguard the user account number of this application program and the corresponding relation between the message token, namely the user account number of this user account number identification information sign is unique to should the message token, like this when application server has message data will be pushed to this user account number, can inquire the message token by this user account number, then send to push server by the message data request of preserving that carries this message token and message data and store.At this moment, developer's account number and key have been preserved at application server 2, user account number identification information, and message token.
Wherein, portable terminal 1 obtains that described message token corresponding to application program can change at user state information, application version upgrades and/or the predefined time interval registers and carries out when obtaining described message token to push server 5.Specifically, when this application program generation user account number switching on the portable terminal, when user account number is nullified, portable terminal can be initiated to initiate the message token to push server and be obtained request; Perhaps when application version is upgraded, also can initiate to initiate the message token to push server and obtain request; Even can be 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, obtaining the message token also can just trigger when installing, some application program can also be when portable terminal be hung up service, register according to the time interval of setting as described above and obtain the message token, specifically when trigger and obtain the message token, above-mentioned is example only, does not limit, and specifically sets according to concrete different application program.
Each application program on the portable terminal 1 is when obtaining the message token to push server 5, if when obtaining to push server 5 first (when in database 6, not having the message token as described above), push server 5 represents that according to the mobile terminal equipment to identify of uploading number, application name and user account number these parameters of information come corresponding generating messages token, and the related data that will send is first stored, after the message token is obtained in registration first, when the message token is obtained in each triggering, can from database 6, directly obtain.
Particularly, described step 12 is:
Such as the step 209 among Fig. 6, application server 2 is initiated message data by http protocol to access server 4 and is preserved request, the request of preserving of described message data carries: to the signature of developer's account number and key, the second the transmission of data, this second the transmission of data comprises 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.When the group deposited message, message data was preserved request portable application program name and application version, and message is singly deposited when namely storing private message, and the message token is only carried in the message data request of preserving.These message datas can be at least a in the various increment message of logistics information, lastest imformation, sales promotion information, picture or video etc.
Such as the step 210 among Fig. 6, access server 4 according to signature is carried out authentication, is verified the legitimacy of application server 2 after checking developer account number is legal, and the second the transmission of data that carries carried out safety check, and the request of preserving of described message data is transmitted to push server 5;
Be the process shown in first execution in step 2041 and 2042, then be transmitted to server after execution in step 210 authentications.
The rule that developer's account number and key are signed 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.
Signature is carried out authentication verify the similar of application server legitimacy and the description of top step 204, difference is to utilize the second the transmission of data to be encrypted algorithm md5 and generates signature, does not repeat them here.
The second the transmission of data is carried out safety check and above-described that the first the transmission of data is carried out safety check is similar.
If carry the message token in the message data request of preserving, then explanation is private message, refers to the message that a user account number of this application program of a directed portable terminal pushes.Such as the step 211 among Fig. 2, push server 5 checks whether this message token is consistent with the message token of storage, if consistent, in database 6, find again its corresponding application name of record according to developer's account number, more consistent with the application name that in database 6, finds according to this message token, with the validity (validity is unanimously then arranged) of judging this message token, if the message token has validity, then according to the message token, be that private message is stored corresponding to the record position in the database with this message data, finish the result to access server 4 by what the far call agreement was returned request.The validity of judging this message token is in order to prevent application server imitation message token, the application of attacking other.Private message is the message data that sends for specific user's account number.
When pocket transmission news, push server 5 request of preserving is carried according to message data application name and application version, searching database at the correspondence position of the record that satisfies this application name and application version, is stored this message data.
The application utilizes and carries application name in the message data request of preserving and application version can be realized using the user account number of this application program to carry out the storage of message data to all, in order to realize all user account numbers of this application program under every all portable terminals that this application program has been installed are carried out message push, namely realized the pocket transmission news data.
Such as the step 212 among Fig. 6, access server 4 returns by http protocol and sends result that message data preserves request as successfully to application server 2.
Particularly, step 13 is:
Such as the step 213 among Fig. 6, portable terminal 1 is initiated the message data search request by http protocol at set intervals to access server 4, described message data search request comprises the signature that carries out to developer's account number and key, and the 3rd the transmission of data, the 3rd the transmission of data comprises developer's account number and message token corresponding to this application program user account number;
Such as the step 214 among Fig. 6, access server 4 is after checking developer account number is legal, carry out authentication according to signature, verify the legitimacy of portable terminal 1, and the 3rd the transmission of data (developer's account number and message token) carried out safety check, and with the message data search request by the far call protocol forward to push server 5;
Be the process shown in first execution in step 2041 and 2042, then be transmitted to server after execution in step 214 authentications.
Wherein, the rule that developer's account number and key are signed 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.
Signature is carried out authentication, and to verify that the legitimacy of portable terminal 1 coexists and describes in the step 204 similar, and difference is to utilize the 3rd the transmission of data to be encrypted algorithm md5 and generates signature, does not repeat them here.
The 3rd the transmission of data is carried out safety check with above-mentioned described.
Such as the step 215 among Fig. 6, push server 5 is received the message data search request, according to the message data of storage in the message token searching database 6, the tabulation of message data of coupling is sent to access server 4 by hsf; Wherein, do intercepting according to certain list size, the tabulation with these message datas sends to access server 4 again.
Such as the step 216 among Fig. 6, access server 4 sends to portable terminal 1 by http protocol with tabulation, thereby finishes the propelling movement of message data.
In said process, database 6 is preserved developer's account number, application name, application version, mobile terminal equipment to identify number (imei), is identified uniquely identified user account number identification information, message token and the data-message of the user account number of each application program, and these information become corresponding relational storage.Namely can get access to corresponding application name, application version, mobile terminal equipment to identify number (imei), user account number identification information and data-message by token message.
The user account number identification information prevents other user account numbers that message data have been pushed to same application can unique specify message data being corresponding certain user account numbers when an application program has a plurality of user account number.
Above-mentioned push server 5 is during to the related news of portable terminal pushing application program, initiatively to initiate the message data search request by portable terminal, push server 5 is carried out the propelling movement of message according to this message data search request, so the application has realized initiatively initiating acquisition request message to be pushed by portable terminal.
In three processes that above-mentioned steps 11, step 12 and step 13 are described, before access push server 5, all need the checking verification through access server 4, therefore, utilized third-party access server 4 to carry out legitimate verification and safety check, can avoid as the ihone mobile phone that only has exclusive device certificate in the prior art could with the apple push server verify the access situation, can realize that all portable terminals obtain message by access server access push server, and need not specific portable terminal.
Below, introduce the application's message push device message push system in actual applications.System schematic referring to Fig. 7 the application message push.The system of this message push comprises portable terminal 1, application server 2, Developer Central Control Server 3, access server 4, push server 5 and database 6.
Portable terminal 1 is used for obtaining message token corresponding to described application program, and described message token is sent;
Application server 2 is used for receiving the described message token that described portable terminal sends, and the message data storage is carried out in the request of preserving of transmission message data;
Push server 5, be used for developer account number and the key corresponding according to the application program on the portable terminal, and mobile terminal equipment to identify number, application name and user account number identification information obtain described message token, and described message token is sent to portable terminal; According to the preserving described message token in the request or application name and application version from the message data of described application server and carry out the message data storage through verification that receives; And according to the described message token in the message data search request of the described portable terminal that passes through verification that receives, from the message data of described storage, mate the corresponding described message data of described message token, and described message data is sent to described portable terminal.
Access server 4, be used for the legitimacy according to the described portable terminal of described signature verification, the first the transmission of data is carried out safety check, and described the first the transmission of data comprises described developer's account number, mobile terminal equipment to identify number, application name, application version and user account number identification information; Legitimacy according to the described application server of described signature verification, and the second the transmission of data that described application server is sent carries out safety check, described the second the transmission of data comprises described developer's account number, message token or application name and application version and message data, and the request of preserving of described message data is transmitted to push server; And the 3rd the transmission of data that described portable terminal is sent carries out safety check, and described the 3rd the transmission of data comprises described developer's account number and message token, and described message data search request is transmitted to push server.
Developer Central Control Server 3 is used for the described developer's account number of described application server registers, and generation is with the unique corresponding key of described developer's account number and send to described application server.
Database 6 is preserved developer's account number, application name, application version, mobile terminal equipment to identify number, user account number identification information, message token and data-message, and these information become corresponding relational storage.
Wherein, the corresponding application program of common application server, therefore namely developer's account number and the key of this application program of developer's account number of application server and key, after mobile phone users downloads and installs this application program, this application program just carries this developer's account number and key, is kept on the portable terminal; And Developer Central Control Server 3 also carries out record with developer's account number, key and application name, these information of version of the corresponding application server registers of application program, and to push server 5 notices through developer's account number, application name and the version of registration, push server will record these information.
Wherein, the user account number identification information is the user's of each application program of sign unique identification; Preserve mobile terminal equipment to identify number, developer's account number of certain application program and these information such as user account number identification information of key, application name, version and this application program on the portable terminal 1, and the message token corresponding with these information.
In database 6, can preferably preserve these data with the form of tabulation, wherein line item storage is developer's account number, application name, application version, mobile terminal equipment to identify number, user account number identification information of this application program and the message token that number is generated by this application name, user account number identification information and mobile terminal equipment to identify;
Because the message token is generated by mobile terminal equipment to identify number, application name and user account number identification information, so this message token points to the specific corresponding specific user account number of application program on the specific mobile device.Push server has realized to application program for mobile terminal PUSH message data the time by these records of storage, message data had been received or be employed other user account number reception of program by other application program situation can not occur.
This message push system can be carried out the detailed process shown in the said method, does not repeat them here.Can avoid like this as the ihone mobile phone that only has exclusive device certificate in the prior art could with the apple push server verify the access situation, can realize that all portable terminals obtain message by access server access push server, and need not specific portable terminal.
The application's message token and application name, mobile terminal equipment to identify number and the binding of user account number identification information; third party under message can accurately be delivered to uses; and support message cluster transmition; and adopt the short connection of HTTP between portable terminal and the server; can use at any portable terminal, and less than the long problem that connects of keep-alive.
Those of ordinary skills should further recognize, unit and the algorithm steps of each example of describing in conjunction with embodiment disclosed herein, can realize with electronic hardware, computer software or the combination of the two, for the interchangeability of hardware and software clearly is described, composition and the step of each example described in general manner according to function in the above description.These functions are carried out with hardware or software mode actually, depend on application-specific and the design constraint of technical scheme.The professional and technical personnel can specifically should be used for realizing described function with distinct methods to each, but this realization should not thought the scope that exceeds the application.
The method of describing in conjunction with embodiment disclosed herein or the step of algorithm can use the software module of hardware, processor execution, and perhaps the combination of the two is implemented.Software module can place the storage medium of any other form 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 the technical field.
Above-described embodiment; purpose, technical scheme and beneficial effect to the application further describe; institute is understood that; the above only is the application's embodiment; and be not used in the protection range that limits the application; all within the application's spirit and principle, any modification of making, be equal to replacement, improvement etc., all should be included within the application's the protection range.
Claims (18)
1. an information push method is characterized in that, comprising:
Send the message token and obtain request, the request of obtaining of described message token comprises mobile terminal equipment to identify number, application name and user account number identification information;
Receive described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information;
Transmission carries the message data search request of described message token;
The message data that the described message token that reception goes out according to described message token lookup mates.
2. information push method according to claim 1 is characterized in that, described message token generates according to described mobile terminal equipment to identify number, application name and user account number identification information.
3. information push method according to claim 1, it is characterized in that, the request of obtaining of described transmission message token changes at user state information, application version upgrades and/or the predefined time interval registers when obtaining described message token and carries out.
4. information push method according to claim 1 is characterized in that, also comprises:
Receiving developer's account number and key stores.
5. information push method according to claim 1 is characterized in that, also comprises:
Transmit described user account number identification information and the described message token that receives.
6. an information push method is characterized in that, comprising:
The receipt message token obtains request, and the request of obtaining of described message token comprises mobile terminal equipment to identify number, application name and user account number identification information;
Send described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information;
The request of preserving of receipt message data, the request of preserving of described message data comprises described message token and corresponding message data thereof, perhaps application name and application version with and corresponding message data;
Store its corresponding message data according to described message token or application name and application version;
Reception carries the message data search request of 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.
7. information push method according to claim 6 is characterized in that, also comprises:
Receive developer's account number, described application name and application version and corresponding stored.
8. information push method according to claim 6, it is characterized in that, after described receipt message token obtains request, before the described mobile terminal equipment to identify of described transmission number, application name and the corresponding message token of user account number identification information, also comprise:
Retrieval described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information in database;
If have described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information, then take out this message token;
If there is no described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information, then according to described mobile terminal equipment to identify number, application name and user account number identification information generating messages token, and store described mobile terminal equipment to identify number, user account number identification information and corresponding message token.
9. information push method according to claim 6 is characterized in that, also comprises:
Verify that it is effectively that the described message token request of obtaining, message data are preserved developer's account number of carrying in request or the message data search request, and described developer's account number of carrying had been registered application program corresponding to described developer's account number in database;
The described message token request of obtaining, the message data that receive are preserved the signature that carries in request or the message data search request carry out authentication.
10. information push method according to claim 6 is characterized in that,
After described receipt message data are preserved request, described according to before its corresponding message data of described message token store, also comprise:
The described message token that relatively carries and the message token of storage, when comparative result when being consistent, carry out:
Compare the application name of the storage that finds according to developer's account number of carrying in the described message data search request and the application name of the storage of arriving according to described described message token lookup of carrying; When comparative result when being consistent, the step of described its corresponding message data of message token store of executive basis.
11. a message push device is characterized in that, comprising:
The token request transmitting element be used for to send the message token and obtains request, and the request of obtaining of described message token comprises mobile terminal equipment to identify number, application name and user account number identification information;
The token receiving element is used for receiving described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information;
The message request transmitting element is used for sending the message data search request that carries described message token;
The message sink unit, the message data that the described message token that goes out according to described message token lookup for reception mates.
12. the method for message push according to claim 11 is characterized in that, also comprises:
Account number key reception unit is used for receiving developer's account number and key is stored.
13. the method for message push according to claim 11 is characterized in that, also comprises:
Retransmission unit is used for transmitting described user account number identification information and the described message token that receives.
14. a message push device is characterized in that, comprising:
The token request receiving element is used for the receipt message token and obtains request, and the request of obtaining of described message token comprises mobile terminal equipment to identify number, application name and user account number identification information;
The token transmitting element is used for sending described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information;
Message is preserved receiving element, is used for the receipt message data and preserves request, and the request of preserving of described message data comprises described message token and corresponding message data, perhaps application name and application version with and corresponding message data;
Preserve processing unit, be used for storing its corresponding message data according to described message token or application name and application version;
The message request receiving element is used for receiving the message data search request that carries described message token;
Message sending unit be used for to send the message data that the described message token that finds out from the message data of described storage according to described message token mates.
15. information push method according to claim 14 is characterized in that, also comprises:
Receiving element is used for receiving developer's account number, described application name and application version and carries out corresponding stored.
16. the method for message push according to claim 14 is characterized in that, also comprises:
Retrieval unit is used at the described mobile terminal equipment to identify of database retrieval number, application name and the corresponding message token of user account number identification information;
The token retrieval unit if be used for existing described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information, then takes out this message token;
The token generation unit, be used for when not having described mobile terminal equipment to identify number, application name and the corresponding message token of user account number identification information, according to described mobile terminal equipment to identify number, application name and user account number identification information generating messages token, and store described mobile terminal equipment to identify number, user account number identification information and corresponding message token.
17. information push method according to claim 14 is characterized in that, also comprises:
Authentication unit, be used for verifying that developer's account number that the described message token request of obtaining, message data preservation request or message data search request are carried is effectively, and described developer's account number of carrying had been registered application program corresponding to described developer's account number in database;
Authenticating unit is used for the signature that the described message token request of obtaining, message data preservation request or the message data search request that receive are carried is carried out authentication.
18. information push method according to claim 14 is characterized in that, also comprises:
The first comparing unit is used for the more described described message token that carries whether consistent with the message token of storage;
The second comparing unit, whether the application name of the storage that the developer's account number that is used for relatively carrying according to described message data search request finds is consistent with the application name of the storage of arriving according to described described message token lookup of carrying.
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 true CN103037312A (en) | 2013-04-10 |
| CN103037312B 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) |
Cited By (37)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103209389A (en) * | 2013-04-16 | 2013-07-17 | 百度在线网络技术（北京）有限公司 | Method, system and cloud server for short message pushing |
| CN103313245A (en) * | 2013-05-28 | 2013-09-18 | 中国联合网络通信集团有限公司 | Network service access method, equipment and system based on mobile phone terminal |
| CN103501486A (en) * | 2013-09-29 | 2014-01-08 | 华为软件技术有限公司 | Message pushing method and pushing server |
| CN104023334A (en) * | 2014-05-19 | 2014-09-03 | 联想(北京)有限公司 | Information processing method and electronic equipment |
| CN104125063A (en) * | 2013-04-28 | 2014-10-29 | 腾讯科技（深圳）有限公司 | Authentication method, equipment and system |
| CN104158722A (en) * | 2014-07-21 | 2014-11-19 | 小米科技有限责任公司 | Message push method and device used for light applications, as well as terminal and server |
| CN104349288A (en) * | 2013-07-25 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Message transmission method and device |
| CN104539577A (en) * | 2014-11-27 | 2015-04-22 | 英业达科技有限公司 | Information push system and information push method |
| CN104618517A (en) * | 2015-03-05 | 2015-05-13 | 国家电网公司 | Message pushing method, system and device |
| CN104767775A (en) * | 2014-01-06 | 2015-07-08 | 腾讯科技（深圳）有限公司 | Webpage application information push method and webpage application information push system |
| CN105516221A (en) * | 2014-09-24 | 2016-04-20 | 阿里巴巴集团控股有限公司 | Information push system and method |
| CN105897696A (en) * | 2016-03-25 | 2016-08-24 | 努比亚技术有限公司 | Terminal, server side, and terminal access management method |
| CN105981356A (en) * | 2014-11-05 | 2016-09-28 | 华为技术有限公司 | Information transmission and processing method and device |
| CN105991614A (en) * | 2015-03-03 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Open authorization, resource access method and device, and a server |
| CN106162582A (en) * | 2016-07-22 | 2016-11-23 | 努比亚技术有限公司 | A kind of message based on multi-user isolation method for pushing and system thereof |
| CN106161563A (en) * | 2015-04-23 | 2016-11-23 | 博雅网络游戏开发（深圳）有限公司 | Information push method and device |
| CN106385491A (en) * | 2016-09-05 | 2017-02-08 | 努比亚技术有限公司 | System and method for controlling push information, mobile terminal and push server |
| CN107409128A (en) * | 2015-03-27 | 2017-11-28 | 英特尔公司 | Techniques for secure server access using trusted license agents |
| CN107592324A (en) * | 2016-07-06 | 2018-01-16 | 广州市动景计算机科技有限公司 | Information push method and device and portable terminal |
| CN108234653A (en) * | 2018-01-03 | 2018-06-29 | 马上消费金融股份有限公司 | Method and device for processing service request |
| CN108228451A (en) * | 2017-12-22 | 2018-06-29 | 五八有限公司 | A kind of information push method, equipment and computer readable storage medium |
| CN108243158A (en) * | 2016-12-26 | 2018-07-03 | 中移(苏州)软件技术有限公司 | A kind of method and apparatus of safety certification |
| CN108259437A (en) * | 2016-12-29 | 2018-07-06 | 北京神州泰岳软件股份有限公司 | A kind of http access methods, http-server and system |
| CN109286648A (en) * | 2017-07-21 | 2019-01-29 | 比亚迪股份有限公司 | Data push method, device, system and terminal device |
| CN109756337A (en) * | 2017-11-06 | 2019-05-14 | 北京京东尚科信息技术有限公司 | A kind of safety access method and device of service interface |
| CN110071926A (en) * | 2019-04-26 | 2019-07-30 | 秒针信息技术有限公司 | A kind of data processing method and device |
| CN110149363A (en) * | 2019-04-15 | 2019-08-20 | 深圳壹账通智能科技有限公司 | A kind of information push method, device and storage medium |
| CN110213234A (en) * | 2019-04-30 | 2019-09-06 | 深圳市腾讯计算机系统有限公司 | Developer's recognition methods, device, equipment and the storage medium of application file |
| CN110381100A (en) * | 2018-04-13 | 2019-10-25 | 佛山市顺德区美的电热电器制造有限公司 | A kind of information push method, server and computer readable storage medium |
| CN110753023A (en) * | 2018-07-24 | 2020-02-04 | 阿里巴巴集团控股有限公司 | Equipment authentication method, equipment access method and device |
| CN111147746A (en) * | 2019-12-30 | 2020-05-12 | 深圳市金龙锋科技有限公司 | Intelligent early education equipment terminal management method |
| CN111181908A (en) * | 2019-08-05 | 2020-05-19 | 腾讯科技（深圳）有限公司 | Login method, device and storage medium |
| CN111835869A (en) * | 2020-07-30 | 2020-10-27 | 上海茂声智能科技有限公司 | Method, system, equipment and storage medium for centralized control of terminal content |
| CN112905962A (en) * | 2021-03-04 | 2021-06-04 | 深圳市航顺芯片技术研发有限公司 | 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 |
| WO2022089121A1 (en) * | 2020-10-27 | 2022-05-05 | 华为技术有限公司 | Method and apparatus for processing push message |
| 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 |
Cited By (64)
| 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 |
| CN103209389A (en) * | 2013-04-16 | 2013-07-17 | 百度在线网络技术（北京）有限公司 | Method, system and cloud server for short message pushing |
| CN104125063B (en) * | 2013-04-28 | 2016-10-12 | 腾讯科技（深圳）有限公司 | Authorization and authentication method, equipment and system |
| CN104125063A (en) * | 2013-04-28 | 2014-10-29 | 腾讯科技（深圳）有限公司 | Authentication method, equipment and system |
| WO2014176808A1 (en) * | 2013-04-28 | 2014-11-06 | Tencent Technology (Shenzhen) Company Limited | Authorization authentication method and apparatus |
| US10063547B2 (en) | 2013-04-28 | 2018-08-28 | Tencent Technology (Shenzhen) Company Limited | Authorization authentication method and apparatus |
| CN103313245A (en) * | 2013-05-28 | 2013-09-18 | 中国联合网络通信集团有限公司 | Network service access method, equipment and system based on mobile phone terminal |
| CN103313245B (en) * | 2013-05-28 | 2016-04-20 | 中国联合网络通信集团有限公司 | Based on the Network access method of mobile phone terminal, equipment and system |
| CN104349288A (en) * | 2013-07-25 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Message transmission method and device |
| CN103501486A (en) * | 2013-09-29 | 2014-01-08 | 华为软件技术有限公司 | Message pushing method and pushing server |
| CN103501486B (en) * | 2013-09-29 | 2016-09-28 | 华为软件技术有限公司 | A kind of information push method and push server |
| CN104767775A (en) * | 2014-01-06 | 2015-07-08 | 腾讯科技（深圳）有限公司 | Webpage application information push method and webpage application information push system |
| WO2015101357A1 (en) * | 2014-01-06 | 2015-07-09 | Tencent Technology (Shenzhen) Company Limited | Method and system for pushing web application message |
| CN104767775B (en) * | 2014-01-06 | 2019-09-17 | 腾讯科技（深圳）有限公司 | Web application information push method and system |
| US10277697B2 (en) | 2014-01-06 | 2019-04-30 | Tencent Technology (Shenzhen) Company Limited | Method and system for pushing web application message |
| CN104023334B (en) * | 2014-05-19 | 2019-10-29 | 联想(北京)有限公司 | A kind of information processing method and electronic equipment |
| CN104023334A (en) * | 2014-05-19 | 2014-09-03 | 联想(北京)有限公司 | Information processing method and electronic equipment |
| CN104158722A (en) * | 2014-07-21 | 2014-11-19 | 小米科技有限责任公司 | Message push method and device used for light applications, as well as terminal and server |
| CN105516221A (en) * | 2014-09-24 | 2016-04-20 | 阿里巴巴集团控股有限公司 | Information push system and method |
| CN105516221B (en) * | 2014-09-24 | 2018-12-14 | 阿里巴巴集团控股有限公司 | Information transmission system and method |
| CN105981356A (en) * | 2014-11-05 | 2016-09-28 | 华为技术有限公司 | Information transmission and processing method and device |
| EP3188462A4 (en) * | 2014-11-05 | 2017-11-01 | Huawei Technologies Co., Ltd. | Information transmission and processing method and device |
| US10142832B2 (en) | 2014-11-05 | 2018-11-27 | Huawei Technologies Co., Ltd. | Information sending and processing method and apparatus |
| 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 |
| CN105991614A (en) * | 2015-03-03 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Open authorization, resource access method and device, and a server |
| CN104618517B (en) * | 2015-03-05 | 2018-08-07 | 国家电网公司 | A kind of method, system and device of PUSH message |
| CN104618517A (en) * | 2015-03-05 | 2015-05-13 | 国家电网公司 | Message pushing method, system and device |
| CN107409128A (en) * | 2015-03-27 | 2017-11-28 | 英特尔公司 | Techniques for secure server access using trusted license agents |
| CN106161563A (en) * | 2015-04-23 | 2016-11-23 | 博雅网络游戏开发（深圳）有限公司 | Information push method and device |
| 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 |
| CN105897696A (en) * | 2016-03-25 | 2016-08-24 | 努比亚技术有限公司 | Terminal, server side, and terminal access management method |
| CN107592324A (en) * | 2016-07-06 | 2018-01-16 | 广州市动景计算机科技有限公司 | Information push method and device and portable terminal |
| 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 |
| CN106385491A (en) * | 2016-09-05 | 2017-02-08 | 努比亚技术有限公司 | System and method for controlling push information, mobile terminal and push server |
| 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 |
| CN108259437A (en) * | 2016-12-29 | 2018-07-06 | 北京神州泰岳软件股份有限公司 | A kind of http access methods, http-server and system |
| CN109286648A (en) * | 2017-07-21 | 2019-01-29 | 比亚迪股份有限公司 | Data push method, device, system and terminal device |
| CN109286648B (en) * | 2017-07-21 | 2020-11-06 | 比亚迪股份有限公司 | Data pushing method, device and system and terminal equipment |
| CN109756337A (en) * | 2017-11-06 | 2019-05-14 | 北京京东尚科信息技术有限公司 | A kind of safety access method and device of 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 |
| CN110381100A (en) * | 2018-04-13 | 2019-10-25 | 佛山市顺德区美的电热电器制造有限公司 | A kind of information push method, server and computer readable storage medium |
| CN110381100B (en) * | 2018-04-13 | 2022-03-29 | 佛山市顺德区美的电热电器制造有限公司 | Message pushing method, server and computer readable storage medium |
| CN110753023A (en) * | 2018-07-24 | 2020-02-04 | 阿里巴巴集团控股有限公司 | Equipment authentication method, equipment access method and device |
| 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 |
| CN110071926A (en) * | 2019-04-26 | 2019-07-30 | 秒针信息技术有限公司 | A kind of data processing method and device |
| CN110213234A (en) * | 2019-04-30 | 2019-09-06 | 深圳市腾讯计算机系统有限公司 | Developer's recognition methods, device, equipment and the storage medium of application file |
| CN110213234B (en) * | 2019-04-30 | 2022-06-28 | 深圳市腾讯计算机系统有限公司 | Application program file developer identification method, device, equipment and storage medium |
| CN111181908A (en) * | 2019-08-05 | 2020-05-19 | 腾讯科技（深圳）有限公司 | Login method, device and storage medium |
| CN111181908B (en) * | 2019-08-05 | 2021-11-26 | 腾讯科技（深圳）有限公司 | Applet login method, device and storage medium |
| CN111147746A (en) * | 2019-12-30 | 2020-05-12 | 深圳市金龙锋科技有限公司 | Intelligent early education equipment terminal management method |
| CN111835869A (en) * | 2020-07-30 | 2020-10-27 | 上海茂声智能科技有限公司 | Method, system, equipment and storage medium for centralized control of terminal content |
| CN111835869B (en) * | 2020-07-30 | 2023-06-16 | 上海茂声智能科技有限公司 | Method, system, equipment and storage medium for centralized control of terminal content |
| WO2022089121A1 (en) * | 2020-10-27 | 2022-05-05 | 华为技术有限公司 | Method and apparatus for processing push message |
| CN112905962A (en) * | 2021-03-04 | 2021-06-04 | 深圳市航顺芯片技术研发有限公司 | 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| HK1179459A1 (en) | 2013-09-27 |
| CN103037312B (en) | 2016-03-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103037312B (en) | Information push method and device | |
| CN103155513B (en) | Accelerate the method and apparatus of certification | |
| US10084767B2 (en) | Method and apparatus for authenticating a communication device | |
| CN101258505B (en) | Secure software updates | |
| CN103873454B (en) | Authentication method and equipment | |
| CN103916244B (en) | Verification method and device | |
| WO2020224239A1 (en) | Block chain implementation method,device, system and storage medium | |
| WO2012081404A1 (en) | Authentication system, authentication server, service provision server, authentication method, and computer-readable recording medium | |
| JP2017187777A (en) | Smartphone fraud-proof authorization and authentication for secure interactions | |
| US8959653B2 (en) | Automatic license key injection | |
| US9331995B2 (en) | Secure configuration of mobile application | |
| CN107241336B (en) | Identity verification method and device | |
| CN108259502A (en) | For obtaining the identification method of interface access rights, server-side and storage medium | |
| KR20150036104A (en) | Method, client, server and system of login verification | |
| CN102186173B (en) | Identity authentication method and system | |
| CN102970308B (en) | A kind of user authen method and server | |
| CN104486388A (en) | Accessing method and device of cloud storage file | |
| CN105262588A (en) | Log-in method based on dynamic password, account number management server and mobile terminal | |
| CN108989040B (en) | Information processing method and device based on block chain | |
| CN103905399A (en) | Account registration management method and apparatus | |
| CN102624687A (en) | Networking program user authentication method based on mobile terminal | |
| CN102143131B (en) | User logout method and authentication server | |
| CN106656969A (en) | Payment state management method and system thereof, and network payment system | |
| US20130198863A1 (en) | Digital asset authentication system and method | |
| US9300625B1 (en) | Network address verification |
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 |