CN104580433A - Method and device for calling favorite data - Google Patents
Method and device for calling favorite data Download PDFInfo
- Publication number
- CN104580433A CN104580433A CN201410836137.0A CN201410836137A CN104580433A CN 104580433 A CN104580433 A CN 104580433A CN 201410836137 A CN201410836137 A CN 201410836137A CN 104580433 A CN104580433 A CN 104580433A
- Authority
- CN
- China
- Prior art keywords
- data
- collection
- information
- request
- user
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
- H04L9/0643—Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Power Engineering (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention provides a method and a device for calling favorite data. The method comprises the following steps: receiving a calling request at the side of a cloud disk client, wherein the calling request comprises user information and verification information; adopting the user information and the verification information to carry out safety verification on the calling request; when safety verification is passed, acquiring favorite information corresponding to the user information from a database; sending the favorite information to the cloud disk client. Therefore, the problem that the cloud disk client cannot call the favorite data is solved, the effect of ensuring safety of the favorite information is obtained, risk of leaking the favorite information used as privacies is reduced and time spent in loading the favorite information at the side of a favorite server is saved, so that the efficiency in loading the favorite information at the side of the favorite server is improved.
Description
Technical field
The present invention relates to Internet technical field, what particularly relate to a kind of favorites data transfers method and apparatus.
Background technology
Cloud dish is the Internet storage tool, and cloud dish is the product of the Internet cloud, the service such as storage, reading, download that it provides information by the Internet for enterprises and individuals, has the feature of safety and stability, mass memory.There are Baidu.com's dish, 360 cloud dishes, Kingsoft fast disk, enough fast net dish, thin cloud etc. in more well-known Yun Pan service provider, is current hotter high in the clouds stores service.Nowadays, cloud dish be not only enterprise, business rich and influential family exclusive, also quietly enter individual life in.
Briefly, cloud dish is exactly provide space by the webserver of Internet firm.User no matter when and where, only just need can be uploaded by login cloud dish can the place of interconnection network, to download and leading subscriber exists personal document on the webserver.But user is only by cloud dish upload pictures and document at present, the favorites data in the mobile terminal such as PC or mobile phone cannot be uploaded to Yun Panzhong.
Summary of the invention
In view of the above problems, propose the present invention in case provide a kind of overcome the problems referred to above or the method for transferring of favorites data solved the problem at least in part and corresponding favorites data transfer device.
According to one aspect of the present invention, what provide a kind of favorites data transfers method, comprising:
What receive cloud dish client-side transfers request, and this is transferred request and comprises user profile and authorization information;
Described user profile and authorization information is adopted to transfer request carry out safety verification to described;
When described safety verification passes through, from database, obtain the collection information corresponding with described user profile;
Described collection information is sent to cloud dish client.
Optionally, described user profile comprises: log-on message; The described user profile of described employing transfers to described the step that safety verification is carried out in request, comprising:
Transfer request according to described log-on message carry out user validation checking to described.
Optionally, describedly transfer request according to described log-on message carry out user validation checking to described, comprising:
The user's registration information that described log-on message and server side store is compared;
When the user's registration information that described server side stores is consistent with described user login information, determine that the legitimate verification of described user passes through.
Optionally, the described authorization information of described employing transfers to described the step that safety verification is carried out in request, comprising:
Transfer request according to described authorization information carry out data validation to described.
Optionally, described authorization information comprises: the MD5 value of user ID QID, favorites data, data encryption string;
Describedly transfer request according to described authorization information carry out data validation to described, comprising:
Check described data encryption string, determine that whether Data Source is legal;
When determining that described Data Source is legal, whether corresponding with the described user ID QID that server side stores the MD5 value checking the MD5 value of described favorites data be identical;
When the MD5 value determining that described user ID QID that the MD5 value of favorites data and server side store is corresponding is not identical, determine that data validation is passed through.
Optionally, described authorization information also comprises: favorites data number; Described after determining that MD5 value that described user ID QID that the MD5 value of favorites data and server side store is corresponding is not identical, also comprise:
Check described favorites data number whether to be 0, when described favorites data number is not 0, determine that data validation is passed through.
Optionally, also comprise:
Determining that described Data Source is illegal, or, determine that the MD5 value that described user ID QID that the MD5 value of favorites data and server side store is corresponding is identical, or when described favorites data number is 0, determine data validation by and feedback prompts information give described cloud dish client.
Optionally, the request of transferring of described reception cloud dish client-side comprises:
What receive cloud dish client-side by data-interface transfers request, and described data-interface comprises: favorites data interface, and/or, collection number interface.
Optionally, the described collection information that acquisition is corresponding with described user profile from database, comprising:
Inquire about the database of PC collection and the database of mobile terminal collection respectively, obtain the collection information corresponding with described user profile.
Optionally, described described collection information is sent to cloud dish client, comprising:
The collection information comprising favorites data is returned by favorites data interface;
The collection information comprising collection number is returned by collection number interface.
According to a further aspect in the invention, what additionally provide a kind of favorites data transfers device, comprising: request receiving module, and transfer request for what receive cloud dish client-side, this is transferred request and comprises user profile and authorization information; Secure verification module, transfers request for adopting described user profile and authorization information carry out safety verification to described; Collection data obtaining module, for when described safety verification passes through, obtains the collection information corresponding with described user profile from database; Collection information sending module, for sending to cloud dish client by described collection information.
Optionally, described user profile comprises: log-on message; Described secure verification module, comprising: user validation checking subelement, for transferring request according to described log-on message carry out user validation checking to described.
Optionally, described user validation checking subelement, compares specifically for the user's registration information described log-on message and server side stored; When the user's registration information that described server side stores is consistent with described user login information, determine that the legitimate verification of described user passes through.
Optionally, described secure verification module, comprising: data validation subelement, for transferring request according to described authorization information carry out data validation to described.
Optionally, described authorization information comprises: the MD5 value of user ID QID, favorites data, data encryption string; Described data validation subelement, specifically for checking described data encryption string, determines that whether Data Source is legal; When determining that described Data Source is legal, whether corresponding with the described user ID QID that server side stores the MD5 value checking the MD5 value of described favorites data be identical; When the MD5 value determining that described user ID QID that the MD5 value of favorites data and server side store is corresponding is not identical, determine that data validation is passed through.
Optionally, described authorization information also comprises: favorites data number; Described data validation subelement, specifically also for checking described favorites data number whether to be 0, when described favorites data number is not 0, determines that data validation is passed through.
Optionally, described data validation subelement, concrete also for determining that described Data Source is illegal, or, determine that the MD5 value that described user ID QID that the MD5 value of favorites data and server side store is corresponding is identical, or when described favorites data number is 0, determine data validation by and feedback prompts information give described cloud dish client.
Optionally, described request receiver module, transfer request specifically for what received cloud dish client-side by data-interface, described data-interface comprises: favorites data interface, and/or, collection number interface.
Optionally, described collection data obtaining module, specifically for the database of the database and mobile terminal collection of inquiring about PC collection respectively, obtains the collection information corresponding with described user profile.
Optionally, described collection information sending module, specifically for returning the collection information comprising favorites data by favorites data interface; The collection information comprising collection number is returned by collection number interface.
Method of transferring according to favorites data of the present invention can adopt described user profile and authorization information to carry out safety verification to the request of transferring that cloud dish client-side sends by collection server, when described safety verification passes through, described collection server directly obtains the collection information corresponding with described user profile and sends to cloud dish client from database, solve the problem that cloud dish client cannot transfer favorites data thus, achieve the safety ensureing collection information, reduce collection information as privacy by the risk revealed, save the time that collection server side loads collection information, thus improve the efficiency that collection server side loads collection information, further increase cloud dish client transfers the efficiency of collection information beneficial effect from collection server side.
Above-mentioned explanation is only the general introduction of technical solution of the present invention, in order to technological means of the present invention can be better understood, and can be implemented according to the content of specification, and can become apparent, below especially exemplified by the specific embodiment of the present invention to allow above and other objects of the present invention, feature and advantage.
Accompanying drawing explanation
By reading hereafter detailed description of the preferred embodiment, various other advantage and benefit will become cheer and bright for those of ordinary skill in the art.Accompanying drawing only for illustrating the object of preferred implementation, and does not think limitation of the present invention.And in whole accompanying drawing, represent identical parts by identical reference symbol.In the accompanying drawings:
Fig. 1 shows a kind of according to an embodiment of the invention flow chart of method of transferring of favorites data;
Fig. 2 shows a kind of according to an embodiment of the invention flow chart of method of transferring of favorites data;
Fig. 3 shows a kind of according to an embodiment of the invention structured flowchart transferring device of favorites data; And
Fig. 4 shows the structured flowchart of secure verification module according to an embodiment of the invention.
Embodiment
Below with reference to accompanying drawings exemplary embodiment of the present disclosure is described in more detail.Although show exemplary embodiment of the present disclosure in accompanying drawing, however should be appreciated that can realize the disclosure in a variety of manners and not should limit by the embodiment set forth here.On the contrary, provide these embodiments to be in order to more thoroughly the disclosure can be understood, and complete for the scope of the present disclosure can be conveyed to those skilled in the art.
Embodiment one:
With reference to Fig. 1, show a kind of according to an embodiment of the invention flow chart of steps transferring embodiment of the method for favorites data, specifically can comprise the steps:
Step 102, what receive cloud dish client-side transfers request, and this is transferred request and comprises user profile and authorization information.
If cloud dish client-side wishes to transfer collection information, the request transferred can be sent to collection server by cloud dish client, it should be noted that, in the present embodiment, collection server can be World Wide Web (WWW) (Web) server, the server of such as browser, can also be the server of other types, the particular type of the present embodiment to collection server limit.
It should be noted that, the request of transferring that the present embodiment medium cloud dish client-side sends specifically can comprise: user profile and authorization information, wherein, described user profile can be specifically the log-on message that user registers at collection server side, based on user profile, described collection server can determine that whether the log-on message of described user is legal, this process may also be referred to as user validation checking; Described authorization information can be specifically the QID of user, QID is the unique identification of user, it can be specifically the identifier of numeral, character one class, described authorization information also can be the MD5 value of data, it can also be data encryption string, or other attribute informations, as whether derived from the browser etc. of mobile terminal.Whether described collection server can be legal based on authorization information determination data, and this process may also be referred to as data validation.In the present embodiment, described user validation checking and data validation can be called safety verification altogether.Described collection server carries out safety verification to the request of transferring that described cloud dish client sends, and after safety verification passes through, just can read the collection information feed back of this user to cloud dish client from database, therefore cloud dish client sends to the synchronization request of collection server to need to comprise user profile and authorization information.
Step 104, adopts described user profile and authorization information to transfer request carry out safety verification to described.
It should be noted that, in the present embodiment collection server receive cloud dish client send user profile and authorization information after, need to carry out safety verification according to described user profile and authorization information to the synchronization request that cloud dish client sends, the object of safety verification guarantees the legitimacy of user and data, because collection information belongs to the privacy information of user, if can not determine it is that collection information or synchronous collection information are transferred in user's request, collection server is can not the collection information of random calling and obtaining user, more have to by safety verification just by the collection information feed back of user to cloud dish client.
Step 106, when described safety verification passes through, obtains the collection information corresponding with described user profile from database.
It should be noted that, in the present embodiment when described safety verification is legal, collection server can determine the legitimacy of user identity, and now collection server can read the collection information corresponding with described user profile from database.It should be noted that, the collection information corresponding with described user profile can be stored in the database of collection server at the very start, and the collection information of such as browser is just stored in browser server; The collection information corresponding with described user profile also can be stored in other servers, and such as, collection information in mobile phone is generally stored in mobile phone assistant server.If similar above-mentioned browser collection folder information, in the database of collection server oneself, store the collection information of browser, directly can transfer the browser collection folder information in the database of oneself.If similar above-mentioned mobile phone collection information, collection server needs the server asking in advance to store collection information that collection information is sent to collection server, then described collection information is stored in the database of oneself by collection server, in this case collection server can also carry out the synchronous of collection information with the server storing collection information, the impact of described synchronization request is not sent by cloud dish client, collection server can carry out the synchronous of the communication information according to certain periodic request with the server storing collection information, guarantee that collection information upgrades in time.Certainly, when above-mentioned browser collection folder, collection server also according to the database of renewal of certain cycle oneself, can be guaranteed that the collection information in database upgrades in time, keeps the accuracy of collection information in database.
Step 108, sends to cloud dish client by described collection information.
After collection server reads the collection information corresponding with described user profile from database, especially by interface, described collection information can be sent to described cloud dish client.Interface in the present embodiment can be specifically favorites data interface, also can be collection number interface etc., it should be noted that, the particular type of the present embodiment docking port does not limit, as long as can ensure the transmission carrying out the communication information between described collection server and described cloud dish client.Certainly, in the present embodiment, collection server also can take other modes that described collection information is sent to cloud dish client, and the present embodiment sends collection information to collection server and do not limit to the concrete mode of cloud dish client.
What first the present embodiment collection server received cloud dish client-side transfers request, and this is transferred request and comprises user profile and authorization information; Then collection server adopts described user profile and authorization information to transfer request carry out safety verification to described; Then, when described safety verification passes through, collection server obtains the collection information corresponding with described user profile from database; Described collection information is sent to cloud dish client by last collection server.The present embodiment collection server adopts described user profile and authorization information to transfer request carry out safety verification to described, ensure that the safety of collection information, avoids collection information as privacy by the risk revealed; And when described safety verification is legal, collection server directly obtains the collection information corresponding with described user profile and sends to cloud dish client from database, illustrate that collection information stores in a database by collection server in advance, be not that after cloud dish client sends the request of transferring, collection server just obtains collection information from other places, save the time transferring collection information, thus improve collection information transfer efficiency.
Embodiment two:
On the basis of above-described embodiment, the present embodiment discuss favorites data transfer method.
With reference to Fig. 2, show a kind of according to an embodiment of the invention flow chart of steps transferring embodiment of the method for favorites data, specifically can comprise the steps:
Step 202, what receive cloud dish client-side transfers request, and this is transferred request and comprises user profile and authorization information, and described user profile comprises: log-on message.
In cloud dish client user want synchronous collection information time, send request to collection server, described synchronization request comprises: user profile and authorization information.User profile and authorization information are to carry out safety verification according to user profile and authorization information afterwards.In the present embodiment, described safety verification comprises user validation checking and data validation, the step 204 namely and step 206.Particularly, described collection server can carry out user validation checking based on user profile, and described collection server can carry out data validation based on authorization information.Described collection server carries out user validation checking and data validation to the request of transferring that described cloud dish client-side sends, and after described user validation checking and data validation are all passed through, the collection information that just can read this user from database sends to cloud dish client, and therefore cloud dish client sends to the request of transferring of collection server to need to comprise user profile and authorization information.
It should be noted that, the request of transferring receiving cloud dish client-side described in the present embodiment specifically can comprise: what receive cloud dish client-side by data-interface transfers request, described data-interface comprises: favorites data interface, and/or, collection number interface.Specifically can return by favorites data interface the collection information comprising favorites data; The collection information comprising collection number is returned by collection number interface.
It should be noted that, user profile described in the present embodiment specifically can comprise: log-on message, therefore described user profile is adopted to transfer to described the step that safety verification is carried out in request, specifically can comprise: transfer request according to described log-on message carry out user validation checking, the step 204 namely in the present embodiment to described.
Step 204, transfers request according to described log-on message carry out user validation checking to described.
The server of collection described in the present embodiment is transferred request according to described log-on message carry out user validation checking to described, specifically can realize in the following manner: first, the user's registration information that described log-on message and server side store compares by described collection server; Secondly, when the user's registration information that described server side stores is consistent with described user login information, determine that the legitimate verification of described user passes through.Because user's registration information is the log-on message that user registers at collection server side, if when therefore described in collection discovering server, the user's registration information of collection server stores is consistent with described log-on message, can determine that the log-on message of described user is legal, namely the legitimate verification of described user passes through.Log-on message described in the present embodiment can be specifically the login account that uses when logging in of user and password.
Step 206, transfers request according to described authorization information carry out data validation to described.
It should be noted that, authorization information described in the present embodiment specifically can comprise: the MD5 value of user ID QID, favorites data, data encryption string.Therefore transfer request according to described authorization information carry out data validation to described described in the present embodiment, specifically can realize in the following manner: first collection server checks described data encryption string, determine that whether Data Source is legal; Then, when determining that described Data Source is legal, whether corresponding with the described user ID QID that server side stores the MD5 value checking the MD5 value of described favorites data be identical; Finally when the MD5 value determining that described user ID QID that the MD5 value of favorites data and server side store is corresponding is not identical, determine that data validation is passed through.
In a kind of alternate exemplary of the embodiment of the present invention, described authorization information also comprises: favorites data number.Described after determining that MD5 value that described user ID QID that the MD5 value of favorites data and server side store is corresponding is not identical, also comprise: check described favorites data number whether to be 0, when described favorites data number is not 0, determine that data validation is passed through.
It should be noted that, described collection server is determining that described Data Source is illegal, or, determine that the MD5 value that described user ID QID that the MD5 value of favorites data and server side store is corresponding is identical, or when described favorites data number is 0, determine data validation by and feedback prompts information give described cloud dish client.When the server of collection described in the present embodiment determination Data Source is illegal, need to inform cloud dish client, namely collection server determination data validation is not passed through, can feedback validation failure information give described cloud dish client.
It should be noted that, the step 104 in the present embodiment in above-mentioned steps 204 and the corresponding embodiment of step 206 one adopts described user profile and authorization information to transfer request carry out safety verification to described.
Step 208, when described safety verification passes through, obtains the collection information corresponding with described user profile from database.
When described safety verification is legal, collection server can determine the legitimacy of user identity, and now collection server can read the collection information corresponding with described user profile from database.It should be noted that, the collection information corresponding with described user profile is stored in the database of collection server.Collection server can according to the collection information in certain update cycle more new database, and guarantee that collection information upgrades in time, ensures the accuracy of collection information in database, the described update cycle can by user's free setting.
From database, obtain the collection information corresponding with described user profile described in the present embodiment, specifically can comprise: inquire about the database of PC collection and the database of mobile terminal collection respectively, obtain the collection information corresponding with described user profile.It should be noted that, the database of PC collection and the database of mobile terminal collection is comprised in collection server described in the present embodiment, wherein, store the collection information of PC end in the database of described PC collection, in the database of described mobile terminal collection, store the collection information of mobile terminal side.Collection server according to user profile, can search the collection information corresponding with described user profile respectively in the database of described PC collection and the database of mobile terminal collection.Namely the information of collection described in the present embodiment specifically can comprise: the collection information of PC end and the collection information of mobile terminal side.It should be noted that, during specific implementation, described collection information can also comprise other guide, the restriction of the present embodiment not to described collection information particular content.
Step 210, sends to cloud dish client by described collection information.
It should be noted that, the information of collection described in the present embodiment specifically can be divided into the collection information comprising favorites data and the collection information comprising collection number.Described described collection information is sent to cloud dish client, specifically can realize in the following manner: returned the collection information comprising favorites data by favorites data interface; The collection information comprising collection number is returned by collection number interface.
After the present embodiment collection server reads the collection information corresponding with described user profile from database, especially by interface, described communication information can be sent to described cloud dish client.Cloud dish client receives the collection information that described collection server sends, and achieves cloud dish client transferring collection information.
For embodiment of the method, in order to simple description, therefore it is all expressed as a series of combination of actions, but those skilled in the art should know, the embodiment of the present invention is not by the restriction of described sequence of movement, because according to the embodiment of the present invention, some step can adopt other orders or carry out simultaneously.Secondly, those skilled in the art also should know, the embodiment described in specification all belongs to preferred embodiment, and involved action might not be that the embodiment of the present invention is necessary.
Embodiment three:
On the basis of above-described embodiment, what the present embodiment also disclosed a kind of favorites data transfers device.
With reference to Fig. 3, show a kind of according to an embodiment of the invention structured flowchart transferring device embodiment of favorites data, specifically can comprise as lower module: request receiving module 302, secure verification module 304, collection data obtaining module 306 and collection information sending module 308, wherein:
Request receiving module 302, transfer request for what receive cloud dish client-side, this is transferred request and comprises user profile and authorization information.
Secure verification module 304, transfers request for adopting described user profile and authorization information carry out safety verification to described.The user profile that secure verification module 304 adopts described request receiver module 302 to receive and authorization information are transferred request carry out safety verification to described.
Collection data obtaining module 306, for when described safety verification passes through, obtains the collection information corresponding with described user profile from database.When described secure verification module 304 safety verification passes through, collection data obtaining module 306 obtains the collection information corresponding with described user profile from database.
Collection information sending module 308, for sending to cloud dish client by described collection information.The collection information that collection data obtaining module 306 gets by collection information sending module 308 sends to cloud dish client.
What by request receiving module 302, first the collection server of the present embodiment received that cloud dish client-side sends transfers request, described in transfer request and comprise user profile and authorization information; Then secure verification module 304 user profile that adopts described request receiver module 302 to receive and authorization information are transferred request carry out safety verification to described; Then collection data obtaining module 306 is when described secure verification module 304 safety verification passes through, from database, obtain the collection information corresponding with described user profile; The collection information that collection data obtaining module 306 gets by last collection information sending module 308 sends to cloud dish client.The user profile that in the present embodiment, secure verification module 304 adopts described request receiver module 302 to receive and authorization information are transferred request carry out safety verification to described, ensure that the safety of collection information, avoid collection information as privacy by the risk revealed, and collection data obtaining module 306 is when described secure verification module 304 safety verification passes through, directly from database, the acquisition collection information corresponding with described user profile is given collection information sending module 308 and is sent to cloud dish client, illustrate that collection information stores in a database by collection server in advance, be not that after cloud dish client sends synchronization request, collection server just obtains collection information from other places, save the time that collection information server side loads collection information, thus improve the efficiency that collection server side loads collection information, further increase cloud dish client transfers collection information efficiency from collection server side.
In a kind of alternate exemplary as shown in Figure 4 of the embodiment of the present invention, described user profile comprises: log-on message; Described secure verification module 304, comprising: user validation checking subelement 3041, for transferring request according to described log-on message carry out user validation checking to described.In a kind of alternate exemplary of the embodiment of the present invention, described user validation checking subelement 3041, compares specifically for the user's registration information described log-on message and server side stored; When the user's registration information that described server side stores is consistent with described user login information, determine that the legitimate verification of described user passes through.
In a kind of alternate exemplary as shown in Figure 4 of the embodiment of the present invention, described secure verification module 304, comprising: data validation subelement 3042, for transferring request according to described authorization information carry out data validation to described.In a kind of alternate exemplary of the embodiment of the present invention, described authorization information comprises: the MD5 value of user ID QID, favorites data, data encryption string; Described data validation subelement 3042, specifically for checking described data encryption string, determines that whether Data Source is legal; When determining that described Data Source is legal, whether corresponding with the described user ID QID that server side stores the MD5 value checking the MD5 value of described favorites data be identical; When the MD5 value determining that described user ID QID that the MD5 value of favorites data and server side store is corresponding is not identical, determine that data validation is passed through.
In a kind of alternate exemplary of the embodiment of the present invention, described authorization information also comprises: favorites data number; Described data validation subelement 3042, specifically also for checking described favorites data number whether to be 0, when described favorites data number is not 0, determines that data validation is passed through.
In a kind of alternate exemplary of the embodiment of the present invention, described data validation subelement 3042, concrete also for determining that described Data Source is illegal, or, determine that the MD5 value that described user ID QID that the MD5 value of favorites data and server side store is corresponding is identical, or when described favorites data number is 0, determine data validation by and feedback prompts information give described cloud dish client.
In a kind of alternate exemplary of the embodiment of the present invention, described request receiver module 302, transfer request specifically for what received cloud dish client-side by data-interface, described data-interface comprises: favorites data interface, and/or, collection number interface.
In a kind of alternate exemplary of the embodiment of the present invention, described collection data obtaining module 306, specifically for the database of the database and mobile terminal collection of inquiring about PC collection respectively, obtains the collection information corresponding with described user profile.
In a kind of alternate exemplary of the embodiment of the present invention, described collection information sending module 308, specifically for returning the collection information comprising favorites data by favorites data interface; The collection information comprising collection number is returned by collection number interface.
For device embodiment, due to itself and embodiment of the method basic simlarity, so description is fairly simple, relevant part illustrates see the part of embodiment of the method.
Intrinsic not relevant to any certain computer, virtual system or miscellaneous equipment with display at this algorithm provided.Various general-purpose system also can with use based on together with this teaching.According to description above, the structure constructed required by this type systematic is apparent.In addition, the present invention is not also for any certain programmed language.It should be understood that and various programming language can be utilized to realize content of the present invention described here, and the description done language-specific is above to disclose preferred forms of the present invention.
In specification provided herein, describe a large amount of detail.But can understand, embodiments of the invention can be put into practice when not having these details.In some instances, be not shown specifically known method, structure and technology, so that not fuzzy understanding of this description.
Similarly, be to be understood that, in order to simplify the disclosure and to help to understand in each inventive aspect one or more, in the description above to exemplary embodiment of the present invention, each feature of the present invention is grouped together in single embodiment, figure or the description to it sometimes.But, the method for the disclosure should be construed to the following intention of reflection: namely the present invention for required protection requires feature more more than the feature clearly recorded in each claim.Or rather, as claims below reflect, all features of disclosed single embodiment before inventive aspect is to be less than.Therefore, the claims following embodiment are incorporated to this embodiment thus clearly, and wherein each claim itself is as independent embodiment of the present invention.
Those skilled in the art are appreciated that and adaptively can change the module in the equipment in embodiment and they are arranged in one or more equipment different from this embodiment.Module in embodiment or unit or assembly can be combined into a module or unit or assembly, and multiple submodule or subelement or sub-component can be put them in addition.Except at least some in such feature and/or process or unit be mutually repel except, any combination can be adopted to combine all processes of all features disclosed in this specification (comprising adjoint claim, summary and accompanying drawing) and so disclosed any method or equipment or unit.Unless expressly stated otherwise, each feature disclosed in this specification (comprising adjoint claim, summary and accompanying drawing) can by providing identical, alternative features that is equivalent or similar object replaces.
In addition, those skilled in the art can understand, although embodiments more described herein to comprise in other embodiment some included feature instead of further feature, the combination of the feature of different embodiment means and to be within scope of the present invention and to form different embodiments.Such as, in the following claims, the one of any of embodiment required for protection can use with arbitrary compound mode.
All parts embodiment of the present invention with hardware implementing, or can realize with the software module run on one or more processor, or realizes with their combination.It will be understood by those of skill in the art that the some or all functions transferring the some or all parts in method and apparatus equipment that microprocessor or digital signal processor (DSP) can be used in practice to realize the favorites data according to the embodiment of the present invention.The present invention can also be embodied as part or all equipment for performing method as described herein or device program (such as, computer program and computer program).Realizing program of the present invention and can store on a computer-readable medium like this, or the form of one or more signal can be had.Such signal can be downloaded from internet website and obtain, or provides on carrier signal, or provides with any other form.
The present invention will be described instead of limit the invention to it should be noted above-described embodiment, and those skilled in the art can design alternative embodiment when not departing from the scope of claims.In the claims, any reference symbol between bracket should be configured to limitations on claims.Word " comprises " not to be got rid of existence and does not arrange element in the claims or step.Word "a" or "an" before being positioned at element is not got rid of and be there is multiple such element.The present invention can by means of including the hardware of some different elements and realizing by means of the computer of suitably programming.In the unit claim listing some devices, several in these devices can be carry out imbody by same hardware branch.Word first, second and third-class use do not represent any order.Can be title by these word explanations.
The invention discloses A1, a kind of favorites data transfer method, comprising: what receive cloud dish client-side transfers request, and this is transferred request and comprises user profile and authorization information; Described user profile and authorization information is adopted to transfer request carry out safety verification to described; When described safety verification passes through, from database, obtain the collection information corresponding with described user profile; Described collection information is sent to cloud dish client.
A2, method as described in A1, described user profile comprises: log-on message; The described user profile of described employing is transferred request carry out the step of safety verification to described, comprising: transfer request according to described log-on message carry out user validation checking to described.
A3, method as described in A2, describedly transfer request according to described log-on message carry out user validation checking to described, comprising: compared by the user's registration information that described log-on message and server side store; When the user's registration information that described server side stores is consistent with described user login information, determine that the legitimate verification of described user passes through.
A4, method as described in A3, the described authorization information of described employing transfers to described the step that safety verification is carried out in request, comprising: transfer request according to described authorization information carry out data validation to described.
A5, method as described in A4, described authorization information comprises: the MD5 value of user ID QID, favorites data, data encryption string; Describedly transfer request according to described authorization information carry out data validation to described, comprising: check described data encryption string, determine that whether Data Source is legal; When determining that described Data Source is legal, whether corresponding with the described user ID QID that server side stores the MD5 value checking the MD5 value of described favorites data be identical; When the MD5 value determining that described user ID QID that the MD5 value of favorites data and server side store is corresponding is not identical, determine that data validation is passed through.
A6, method as described in A5, described authorization information also comprises: favorites data number; Described after determining that MD5 value that described user ID QID that the MD5 value of favorites data and server side store is corresponding is not identical, also comprise: check described favorites data number whether to be 0, when described favorites data number is not 0, determine that data validation is passed through.
A7, method as described in A6, also comprise: determining that described Data Source is illegal, or, determine that the MD5 value that described user ID QID that the MD5 value of favorites data and server side store is corresponding is identical, or when described favorites data number is 0, determine data validation by and feedback prompts information give described cloud dish client.
A8, method as described in A1, the request of transferring of described reception cloud dish client-side comprises: what receive cloud dish client-side by data-interface transfers request, and described data-interface comprises: favorites data interface, and/or, collection number interface.
A9, method as described in A8, describedly obtain the collection information corresponding with described user profile from database, comprising: the database of inquiry PC collection and the database of mobile terminal collection respectively, obtains the collection information corresponding with described user profile.
A10, method as described in A9, describedly send to cloud dish client by described collection information, comprising: returned the collection information comprising favorites data by favorites data interface; The collection information comprising collection number is returned by collection number interface.
The invention also discloses B11, a kind of favorites data transfer device, comprising: request receiving module, transfer request for what receive cloud dish client-side, this is transferred request and comprises user profile and authorization information; Secure verification module, transfers request for adopting described user profile and authorization information carry out safety verification to described; Collection data obtaining module, for when described safety verification passes through, obtains the collection information corresponding with described user profile from database; Collection information sending module, for sending to cloud dish client by described collection information.
B12, device as described in B11, described user profile comprises: log-on message; Described secure verification module, comprising: user validation checking subelement, for transferring request according to described log-on message carry out user validation checking to described.
B13, device as described in B12, described user validation checking subelement, compares specifically for the user's registration information described log-on message and server side stored; When the user's registration information that described server side stores is consistent with described user login information, determine that the legitimate verification of described user passes through.
B14, device as described in B13, described secure verification module, comprising: data validation subelement, for transferring request according to described authorization information carry out data validation to described.
B15, device as described in B14, described authorization information comprises: the MD5 value of user ID QID, favorites data, data encryption string; Described data validation subelement, specifically for checking described data encryption string, determines that whether Data Source is legal; When determining that described Data Source is legal, whether corresponding with the described user ID QID that server side stores the MD5 value checking the MD5 value of described favorites data be identical; When the MD5 value determining that described user ID QID that the MD5 value of favorites data and server side store is corresponding is not identical, determine that data validation is passed through.
B16, device as described in B15, described authorization information also comprises: favorites data number; Described data validation subelement, specifically also for checking described favorites data number whether to be 0, when described favorites data number is not 0, determines that data validation is passed through.
B17, device as described in B16, described data validation subelement, concrete also for determining that described Data Source is illegal, or, determine that the MD5 value that described user ID QID that the MD5 value of favorites data and server side store is corresponding is identical, or when described favorites data number is 0, determine data validation by and feedback prompts information give described cloud dish client.
B18, device as described in B11, described request receiver module, transfer request specifically for what received cloud dish client-side by data-interface, described data-interface comprises: favorites data interface, and/or, collection number interface.
B19, device as described in B18, described collection data obtaining module, specifically for the database of the database and mobile terminal collection of inquiring about PC collection respectively, obtains the collection information corresponding with described user profile.
B20, device as described in B19, described collection information sending module, specifically for returning the collection information comprising favorites data by favorites data interface; The collection information comprising collection number is returned by collection number interface.
Claims (10)
1. favorites data transfer a method, comprising:
What receive cloud dish client-side transfers request, and this is transferred request and comprises user profile and authorization information;
Described user profile and authorization information is adopted to transfer request carry out safety verification to described;
When described safety verification passes through, from database, obtain the collection information corresponding with described user profile;
Described collection information is sent to cloud dish client.
2. the method for claim 1, is characterized in that, described user profile comprises: log-on message; The described user profile of described employing transfers to described the step that safety verification is carried out in request, comprising:
Transfer request according to described log-on message carry out user validation checking to described.
3. method as claimed in claim 2, is characterized in that, describedly transfers request according to described log-on message carry out user validation checking to described, comprising:
The user's registration information that described log-on message and server side store is compared;
When the user's registration information that described server side stores is consistent with described user login information, determine that the legitimate verification of described user passes through.
4. method as claimed in claim 3, is characterized in that, the described authorization information of described employing transfers to described the step that safety verification is carried out in request, comprising:
Transfer request according to described authorization information carry out data validation to described.
5. method as claimed in claim 4, it is characterized in that, described authorization information comprises: the MD5 value of user ID QID, favorites data, data encryption string;
Describedly transfer request according to described authorization information carry out data validation to described, comprising:
Check described data encryption string, determine that whether Data Source is legal;
When determining that described Data Source is legal, whether corresponding with the described user ID QID that server side stores the MD5 value checking the MD5 value of described favorites data be identical;
When the MD5 value determining that described user ID QID that the MD5 value of favorites data and server side store is corresponding is not identical, determine that data validation is passed through.
6. method as claimed in claim 5, it is characterized in that, described authorization information also comprises: favorites data number; Described after determining that MD5 value that described user ID QID that the MD5 value of favorites data and server side store is corresponding is not identical, also comprise:
Check described favorites data number whether to be 0, when described favorites data number is not 0, determine that data validation is passed through.
7. method as claimed in claim 6, is characterized in that, also comprise:
Determining that described Data Source is illegal, or, determine that the MD5 value that described user ID QID that the MD5 value of favorites data and server side store is corresponding is identical, or when described favorites data number is 0, determine data validation by and feedback prompts information give described cloud dish client.
8. the method for claim 1, is characterized in that, the request of transferring of described reception cloud dish client-side comprises:
What receive cloud dish client-side by data-interface transfers request, and described data-interface comprises: favorites data interface, and/or, collection number interface.
9. method as claimed in claim 8, is characterized in that, the described collection information that acquisition is corresponding with described user profile from database, comprising:
Inquire about the database of PC collection and the database of mobile terminal collection respectively, obtain the collection information corresponding with described user profile.
10. favorites data transfer a device, comprising:
Request receiving module, transfer request for what receive cloud dish client-side, this is transferred request and comprises user profile and authorization information;
Secure verification module, transfers request for adopting described user profile and authorization information carry out safety verification to described;
Collection data obtaining module, for when described safety verification passes through, obtains the collection information corresponding with described user profile from database;
Collection information sending module, for sending to cloud dish client by described collection information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410836137.0A CN104580433B (en) | 2014-12-26 | 2014-12-26 | Favorites data transfers method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410836137.0A CN104580433B (en) | 2014-12-26 | 2014-12-26 | Favorites data transfers method and apparatus |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104580433A true CN104580433A (en) | 2015-04-29 |
| CN104580433B CN104580433B (en) | 2019-02-26 |
Family
ID=53095590
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410836137.0A Active CN104580433B (en) | 2014-12-26 | 2014-12-26 | Favorites data transfers method and apparatus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104580433B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115248803A (en) * | 2022-09-22 | 2022-10-28 | 天津联想协同科技有限公司 | Collection method and device suitable for network disk file, network disk and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101080056A (en) * | 2006-12-21 | 2007-11-28 | 腾讯科技（深圳）有限公司 | A management method and system of network browser collection folder of mobile terminal |
| CN101414906A (en) * | 2008-11-20 | 2009-04-22 | 腾讯科技（深圳）有限公司 | Method and apparatus for accessing network favorite by multiple account numbers |
| US20120216041A1 (en) * | 2009-08-28 | 2012-08-23 | Ripplex Inc. | Service system |
| CN102724192A (en) * | 2012-06-14 | 2012-10-10 | 北京奇乐客科技有限公司 | Collaborative editing based network collection method |
| CN102819554A (en) * | 2012-06-26 | 2012-12-12 | 北京奇虎科技有限公司 | Favorite data processing method and device and server |
| CN102915363A (en) * | 2012-10-18 | 2013-02-06 | 北京奇虎科技有限公司 | Website storing method and system |
-
2014
- 2014-12-26 CN CN201410836137.0A patent/CN104580433B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101080056A (en) * | 2006-12-21 | 2007-11-28 | 腾讯科技（深圳）有限公司 | A management method and system of network browser collection folder of mobile terminal |
| CN101414906A (en) * | 2008-11-20 | 2009-04-22 | 腾讯科技（深圳）有限公司 | Method and apparatus for accessing network favorite by multiple account numbers |
| US20120216041A1 (en) * | 2009-08-28 | 2012-08-23 | Ripplex Inc. | Service system |
| CN102724192A (en) * | 2012-06-14 | 2012-10-10 | 北京奇乐客科技有限公司 | Collaborative editing based network collection method |
| CN102819554A (en) * | 2012-06-26 | 2012-12-12 | 北京奇虎科技有限公司 | Favorite data processing method and device and server |
| CN102915363A (en) * | 2012-10-18 | 2013-02-06 | 北京奇虎科技有限公司 | Website storing method and system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115248803A (en) * | 2022-09-22 | 2022-10-28 | 天津联想协同科技有限公司 | Collection method and device suitable for network disk file, network disk and storage medium |
| CN115248803B (en) * | 2022-09-22 | 2023-02-17 | 天津联想协同科技有限公司 | Collection method and device suitable for network disk file, network disk and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104580433B (en) | 2019-02-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10515058B2 (en) | Unified file and object data storage | |
| CN105119973B (en) | User information processing method and server | |
| US20190181901A1 (en) | Local profile assistant and application programming interface | |
| CN104378330A (en) | Method and device for account registration and server | |
| CN104094576A (en) | Consolidating disparate cloud service data and behavior based on trust relationships between cloud services | |
| CN110445841B (en) | Cloud disk mounting method and device for cloud physical machine and storage medium | |
| US9471896B2 (en) | Memo synchronization system, mobile system, and method for synchronizing memo data | |
| CN111935110A (en) | Method and device for controlling permission of tenant to access container instance | |
| US20110082896A1 (en) | Dynamically Updated Web-Enabled and Embedded Contact Address in Communication Devices | |
| CN103916469A (en) | Method for acquiring contact person information, client end and server | |
| CN105554137A (en) | Backup system and method | |
| CN105100242A (en) | Data processing method and system | |
| US20100036892A1 (en) | Determination of an updated data source from disparate data sources | |
| CN105100224A (en) | Data transmission method and device | |
| US20090178113A1 (en) | Apparatus, methods, and computer program products for providing portable communication identity services | |
| US9584671B2 (en) | Techniques to transform network resource requests to zero rated network requests | |
| CN105553671A (en) | Digital certificate managing method, device and system | |
| KR102058407B1 (en) | Cloud-based virtual smartphone system | |
| US20150067766A1 (en) | Application service management device and application service management method | |
| US20160004850A1 (en) | Secure download from internet marketplace | |
| CN105262793B (en) | The method and system of audio file in intelligent sound box broadcasting memory | |
| CN109391658B (en) | Account data synchronization method and equipment, storage medium and terminal thereof | |
| US9648002B2 (en) | Location-based user disambiguation | |
| AU2014256198A1 (en) | Terminal, network side device, terminal application control method, and system | |
| CN104601671A (en) | Favorite data storing and obtaining method and device of mobile terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220714 Address after: Room 801, 8th floor, No. 104, floors 1-19, building 2, yard 6, Jiuxianqiao Road, Chaoyang District, Beijing 100015 Patentee after: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Address before: 100088 room 112, block D, 28 new street, new street, Xicheng District, Beijing (Desheng Park) Patentee before: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Patentee before: Qizhi software (Beijing) Co.,Ltd. |