CN102638581B - A kind of cookie information storage means and system - Google Patents
A kind of cookie information storage means and system Download PDFInfo
- Publication number
- CN102638581B CN102638581B CN201210094095.9A CN201210094095A CN102638581B CN 102638581 B CN102638581 B CN 102638581B CN 201210094095 A CN201210094095 A CN 201210094095A CN 102638581 B CN102638581 B CN 102638581B
- Authority
- CN
- China
- Prior art keywords
- client
- cookie information
- cookie
- cloud server
- uploaded
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 235000014510 cooky Nutrition 0.000 title claims abstract description 411
- 238000003860 storage Methods 0.000 title claims abstract description 23
- 238000000034 method Methods 0.000 claims abstract description 52
- 230000005540 biological transmission Effects 0.000 claims abstract description 12
- 238000013475 authorization Methods 0.000 claims abstract description 8
- 230000008569 process Effects 0.000 claims description 23
- 230000006870 function Effects 0.000 claims description 16
- 230000000717 retained effect Effects 0.000 claims description 16
- 238000005314 correlation function Methods 0.000 claims description 13
- 238000012544 monitoring process Methods 0.000 claims description 9
- 230000006835 compression Effects 0.000 claims description 4
- 238000007906 compression Methods 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000004590 computer program Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 230000004044 response Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 241000931705 Cicada Species 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
- GOLXNESZZPUPJE-UHFFFAOYSA-N spiromesifen Chemical compound CC1=CC(C)=CC(C)=C1C(C(O1)=O)=C(OC(=O)CC(C)(C)C)C11CCCC1 GOLXNESZZPUPJE-UHFFFAOYSA-N 0.000 description 1
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
This application provides a kind of cookie information storage means and system, relate to field of computer technology.The method of the application comprises: the first client sends the first connection request to cloud server, obtains cloud server storing authorization; Described first connection request comprises user ID; For the cookie information that the first Client browse page generates, described cookie information is uploaded in cloud server, and stores according to described user ID; When the first client or the second client transmission company second connect request to cloud server, described second connection request comprises described user ID, if cloud server exists the cookie information of corresponding described user ID, then described cookie information is supplied to described first client or the second client downloads.The webpage that the application makes user side browsed before different clients is browsed, and improve the efficiency of server.
Description
Technical field
The application relates to field of computer technology, particularly relates to a kind of cookie information storage means and system.
Background technology
Cookie (plural form Cookies), Chinese is small-sized text file or cooky, refers to that some website is in order to distinguish that user identity is stored in the data (usually through encryption) on user's local client (ClientSide).Cookie is defined in RFC2109 (the official Cookies standard that W3C (World Wide Web Consortium, WorldWideWebConsortium) tissue first time is released).The arbitrariness that server can utilize Cookies to comprise information is screened and is regularly safeguarded these information, to judge the state in HTTP transmission.Whether the most typical application of Cookies judges registered user Website login, and user may be pointed out, whether upper once enter this website time retain user profile to simplify and log in formality, these are all the functions of Cookies.Another important application occasion is " shopping cart " and so on process: user may select different commodity within a period of time in the different pages of same website, and these information all can write Cookies, so that information extraction during in the end payment.
In prior art, website uses after among cookie recorded information to the storage file of first client (such as computer) of user, if user changes other clients, then be equivalent to all data all lost, so user continues calling party when a lot of website of the first client-access on other computers, or when user deletes the cookie information existed in the first client, user is needed to carry out re-entering the operations such as information, and the server of website needs again for this user generates corresponding cookie, affect the efficiency of server, user operation efficiency is also low.
Summary of the invention
Technical problems to be solved in this application are to provide a kind of cookie information storage means and system, solve because same user changes client end, or when deleting the cookie information in same client, the operating result to webpage before cannot continuing to use.
In order to solve the problem, this application discloses a kind of cookie information storage means, comprising:
First client sends the first connection request to cloud server, obtains cloud server storing authorization; Described first connection request comprises user ID;
For the cookie information that the first Client browse page generates, described cookie information is uploaded in cloud server, and stores according to described user ID;
When the first client or the second client transmission company second connect request to cloud server, described second connection request comprises described user ID, if cloud server exists the cookie information of corresponding described user ID, then described cookie information is supplied to described first client or the second client downloads.
Preferably, comprise when described cookie information being uploaded:
According to the operation of the first client to the page or browser, judge the opportunity of uploading cookie information in the first client, when opportunity is uploaded in arrival, described cookie information is uploaded automatically.
Preferably, comprise when described cookie information being uploaded:
Monitor in the first client the order that specific browser window is closed; When monitoring described shutdown command, each cookie information being uploaded to cloud server and storing according to user ID.
Preferably, described specific browser window comprises is the window that current browser is only deposited.
Preferably, comprise when described cookie information being uploaded:
For each page that the first client is opened, analyze the non-operating time of described first client to the described page, when the described non-operating time is more than or equal to threshold value, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
Preferably, comprise when described cookie information being uploaded:
For the page that the first client is opened, judge whether the described page closes or redirect, if closed or redirect, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
Preferably, comprised before described cookie information is uploaded:
Described cookie information is compressed.
Preferably, comprised before described cookie information is uploaded:
By key, described cookie information is encrypted.
Preferably, comprise after described cookie information is uploaded to cloud server:
The mode of the safety encipher cookie information corresponding to described user ID is adopted to store.
Preferably, comprise when described cookie information is uploaded to cloud server:
Call the correlation function of process cookie information;
The information of write cookie is obtained by the described correlation function called;
According to the domain name in described cookie information, build in-process cookie list;
According to described list, upload for the cookie content under list described in each domain Name acquisition.
Preferably, also comprise:
By each cookie information downloaded from cloud server, compared with each cookie information stored with the first client or the second client self, cookie information newer in corresponding cookie information is retained in described first client or the second client.
Preferably, comprise when cookie information newer in corresponding cookie information being retained in described first client or the second client:
Obtain the corresponding cookie information that domain name is identical and/or cookie name is identical for comparing, the cookie information that timestamp is wherein newer is retained in described first client or the second client as newer cookie information.
Preferably, when using same user ID to upload cookie information to high in the clouds by least two clients, for domain name and/or the identical cookie information of cookie name, retain the cookie information that its timestamp is newer.
Accordingly, disclosed herein as well is a kind of cookie information storage system, comprising:
First client and cloud server, and/or the second client;
Described first client comprises:
First connection request sending module, for sending the first connection request to cloud server, obtains cloud server storing authorization; Described connection request comprises user ID;
Transmission module in cookie information, for the cookie information that module generates for the first Client browse page, is uploaded to described cookie information in cloud server, and stores according to described user ID;
First download request sending module, downloads cookie information second connection request for sending;
Described cloud server comprises:
User ID memory module, for storing the cookie information respective user of the first client upload mark;
Request receiving module, for receiving the first connection request of the first client, receives the second connection request of the first client and/or the second client;
Information is downloaded and is provided module, for cookie information is supplied to client downloads;
Described second client comprises the second download request sending module, downloads cookie information second connection request for sending.
Preferably, described first client comprises judge module further, described judge module, for according to the operation of the first client to the page or browser, judge the opportunity of uploading cookie information in the first client, when opportunity is uploaded in arrival, described cookie information is uploaded automatically.
Preferably, described judge module comprises:
First opportunity judge module, for monitoring in the first client the order that specific browser window is closed; When monitoring described shutdown command, each cookie information being uploaded to cloud server and storing according to user ID.
Preferably, described specific browser window comprises is the window that current browser is only deposited.
Preferably, described disconnected module comprise further second opportunity judge module, described second opportunity judge module, for each page opened for the first client, analyze the non-operating time of described first client to described each page, when the described non-operating time is more than or equal to threshold value, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
Preferably, described judge module comprise further the 3rd opportunity judge module, described 3rd opportunity judge module, for the page opened for the first client, judge whether the described page closes or redirect, if closed or redirect, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
Preferably, in described first client, comprised before described cookie information is uploaded:
Compression module, for compressing described cookie information.
Preferably, it is characterized in that, in described first client, comprised before described cookie information is uploaded:
Encrypting module, for being encrypted described cookie information by key.
Preferably, in described cloud server, comprise after described cookie information is uploaded to cloud server:
Secure storage module, stores for the cookie information adopting the mode of safety encipher corresponding to described user ID.
Preferably, in described first client, comprising:
Function call module, for calling the correlation function of process cookie information;
Data obtaining module, the correlation function for calling described in passing through obtains the information of write cookie;
Process cookie list builder module, for according to the domain name in described cookie information, builds in-process cookie list;
Transmission module in first cookie information, for according to described list, uploads for the cookie content under list described in each domain Name acquisition.
Preferably, described first client or the second client also comprise:
Synchronization module, for each cookie information will downloaded from cloud server, compared with each cookie information stored with the first client or the second client self, cookie information newer in corresponding cookie information is retained in described first client or the second client.
Preferably, described synchronization module is further used for:
Obtain the corresponding cookie information that domain name is identical and/or cookie name is identical for comparing, the cookie information that timestamp is wherein newer is retained in described first client or the second client as newer cookie information.
Preferably, when using same user ID to upload cookie information to high in the clouds by least two clients, for domain name and/or the identical cookie information of cookie name, retain the cookie information that its timestamp is newer.
Compared with prior art, the application comprises following advantage:
The webpage that the application utilizes cloud server to browse same user and the cookie information obtained web page operation store with user ID, when user changes client, or when deleting the cookie information in former client, user is only needed to send the connection request with its user ID at active client, its history cookie information can be downloaded from cloud server, thus webpage browsed before user side can be browsed easily, and improve the efficiency of server.
Accompanying drawing explanation
Fig. 1 is the schematic flow sheet of a kind of cookie information storage means of the application;
Fig. 2 is the structural representation of a kind of cookie information storage system of the application.
Embodiment
For enabling above-mentioned purpose, the feature and advantage of the application more become apparent, below in conjunction with the drawings and specific embodiments, the application is described in further detail.
One of core concept of the application is: utilize cloud server, carry out corresponding according to user ID (such as the Accounting system such as user account and password) with the memory block of cloud server, then user is uploaded to cloud server at the cookie that the operation behaviors such as Client browse webpage produce and store; When user is more in other clients, or when user deletes the cookie of used client, the cookie information of history can be downloaded from cloud server according to user ID.
With reference to Fig. 1, show the schematic flow sheet of a kind of cookie information storage means of the application, specifically can comprise:
Step 110, the first client sends the first connection request to cloud server, obtains cloud server storing authorization; Described first connection request comprises user ID.
In this application, generally need account system, namely user's login account is needed, then the first connection request comprising user account and password is sent to cloud server by client, whether cloud server exists the account according to the user account received and cipher inquiry high in the clouds, if existed, then allow user place client that cookie is uploaded to cloud server and store.
Step 120, for the cookie information that the first Client browse page generates, is uploaded to described cookie information in cloud server, and stores according to described user ID.
Cookie is generally made up of variable name and value, and its form is as follows:
Cookie：NAME＝VALUE；Expires＝DATE；Path＝PATH；Domain＝DOMAIN_NAME；SECURE
Wherein, NAME=VALUE:
This is the part that each Cookie all must have.NAME is the title of this Cookie, and VALUE is the value of this Cookie.In character string " NAME=VALUE ", not containing characters such as branch, comma and spaces.
Expires=DATE:Expires variable is one and only writes variable, which provide a determination Cookie effective date of expiry.This property value DATE must write in a particular format: what day, DD-MM-YYHH:MM:SSGMT, GMT represent that this is the GMT.Otherwise do not write with such form, system is by None-identified.This variable can be economized, if default time, then the property value of Cookie can not be kept in the hard disk of user, and is only kept in the middle of internal memory, and the closedown along with browser disappears by Cookie file automatically.
This variable of Domain=DOMAIN-NAME:Domain is one and only writes variable, and the Web server which provide a determination in which Internet territory can read the Cookie that browser accesses, and namely only just can use the information in Cookie from the page in this territory.This setting is optional, if default time, the property value arranging Cookie is the domain name of this Web server.
The page on Path=PATH:Path attribute definition Web server under which path can to obtain the Cookie of Servers installed.If the path sections in the URL of general user's input comprises the character string that Path attribute defines from first character, browser is just thought by checking.If the value of Path attribute is "/", then all on Web server WWW resources all can read this Cookie.This setting same is optional, if default time, then the property value of Path is the pathname that the resource of browser passed to by Web server.
Can find out by the setting to Domain and Path Two Variables, can control Cookie file is accessed effectively scope.
Secure: mark this variable in Cookie, when showing to only have the communication protocol between browser and WebServer to be encrypting and authenticating agreement, browser just submits corresponding Cookie to server.Current this agreement only has one, is HTTPS.
The content that Cookies follows the tracks of with the mode recording conversation of key assignments. server by utilizing web response header Web Set-Cookie sends COOKIE information. and the form of the SET-COOKIE web response header Web defined in RFC2109 is:
Cookie：Name＝Value；Comment＝value；Domain＝value；Max-Age＝value；Path＝Value；Secure；Version＝1*DIGIT；
Name is the name of Cookie, Value be its value .Name=Value property value to must first occur, attribute-value is after this to occurring with any order.In Servlet specification, the name for the cookie of session tracking must be JSESSIONID, Comment attribute is optional, because Cookie may comprise the privately owned information of other associated subscriber.This attribute allows server that the use of this Cookie is described, user can check this message, right words determine that it is also optional for whether adding or continuing session .Domain attribute, it is effective in which territory that it is used to specify Cookie. and it is optional that specified territory must start .Max-Age attribute with period (.), for defining the life span of Cookie, in seconds.If exceeded this time, client just should abandon this cookie.If the number of seconds of specifying is 0, represent that this cookie should be dropped immediately.Path attribute is optional, is used to specify this cookie effective under which URL subset.Secure attribute is required, and its value is a decimal number, mark cookie according to the version of condition managing specification.Such as:
set-cookie：uid＝zhangsan；Max-Age＝3600；Domain＝.sun.org；Path＝/bbs；Version＝1
It represents a uid by name, is worth the cookie for zhangsan.Life span is 3600 seconds, under the bbs path in sunxin.org territory effectively.After 3600 seconds, client will abandon this cookie.When after this web response header Web above IE receives, if can select to accept or refuse this cookie. ID to receive this cookie, when browser transmit a request to the resource under http://www.sunxin.org/bbs path next time, also can send following request header simultaneously:
cookie：uid＝zhangsan。
So for above-mentioned cookie, when after the storing authorization being obtained high in the clouds by step 110, the cookie that user can produce by the application under Client browse webpage or the shopping cart in webpage add the situations such as content, is uploaded to cloud server according to user ID (account name of such as user and password) and stores.
Preferably, comprise when described cookie information being uploaded:
Step S120, according to the operation of the first client to the page or browser, judges the opportunity of uploading cookie information in the first client, when opportunity is uploaded in arrival, described cookie information is automatically uploaded.
At the Client browse page or in the operating process of browser, the application can intelligent decision upload cookie information upload opportunity, the cookie information of client is uploaded to high in the clouds.When uploading, also can upload in conjunction with user ID, ensureing that high in the clouds can store according to described user ID.
When carrying out cookie information storage beyond the clouds, can unify to store, then mark with user ID; Also can user ID storage area be divided to store.
Preferably, comprise when described cookie information being uploaded:
Step S121, monitors in the first client the order that specific browser window is closed; When monitoring described shutdown command, each cookie information being uploaded to cloud server and storing according to user ID.It is the window that current browser is only deposited that described specific browser window comprises.
Generally, can there is multiple window in browser, also can be the window of multiple browser, when browser in use, some cookie information are also in use, and when browser cuts out, browser just stops using cookie information.So now namely according to the first client cookie information store path, each cookie information is uploaded to cloud server and stores according to user ID.
Generally, the precondition of this step is that browser does not forbid cookie, i.e. in the timestamp Expires=DATE of cookie, DATE is not 0.
In this application, a mouse can be added and intercept event, and window number decision event.
When client opens a browser window, then window number is added 1; Occurring pressing action when listening to the pass closed region of mouse at browser window, namely occurring closing browser window action, then window number being subtracted 1; When window number record from non-zero become 0 time, namely judge that all browser windows are closed.Now, the cookie information in the storage file of client can be uploaded to cloud server, and store according to described user ID.
Or, preferably, comprise when described cookie information is uploaded:
Step S122, for each page that the first client is opened, analyze the non-operating time of described first client to described each page, when the described non-operating time is more than or equal to threshold value, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
When the page that user opens, and when this page not being operated for a long time, also cookie information corresponding for the page can be uploaded to cloud server and store according to user ID.
Preferably, comprise when described cookie information is uploaded:
Or, step S123, for the page that the first client is opened, judge whether the described page closes or redirect, if closed or redirect, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
After user opens a page, if carry out closing or skip operation for this page, so show that cookie information corresponding for the described page temporarily in access, now may can not can be uploaded to cloud server and store according to user ID by the cookie that this page is corresponding.
Further, described step S123 comprises:
Steps A 1, when there is new URL(uniform resource locator) in browser, counter counts described URL(uniform resource locator) by reference;
The application can arrange reference counter, when there is new URL (Uniform/UniversalResourceLocator, URL(uniform resource locator)) in browser, when namely user opens new web page, then and counter+1; For same URL, it occurs that several times then reference counter record several times in a browser, and namely user may open repeatedly by same webpage.
In this application, for the different URL that browser occurs simultaneously, correspondence arranges corresponding reference counter respectively, counts respectively to different URL.
Such as when certain page jump is to www.taobao.com, and browser is current there is not the page that URL is www.taobao.com, then the reference counter of corresponding www.taobao.com adds 1, and when certain page jump is to other pages or when closing, described reference count subtracts 1.
Steps A 2, when described URL(uniform resource locator) be recorded as 0 time, be 0 carry out timing by timer to the reference counter of described URL(uniform resource locator);
When the webpage for same URL, when user closes the webpage of this URL, the record of the reference counter of this URL subtracts 1.The application also can arrange timer, when described record becomes 0, then carries out timing for this URL distributes corresponding timer.
Steps A 3, threshold value is exceeded when the time that the counter of described URL(uniform resource locator) is 0, then determine that the page corresponding to described URL(uniform resource locator) has been closed or redirect, according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
For the timing of timer corresponding to above-mentioned URL, threshold value is exceeded when the time that described URL does not occur again, then determine that the page corresponding to described URL(uniform resource locator) has been closed or redirect, according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.Such as, if after 30 seconds, the reference counter of www.taobao.com adds is also 0, namely can judge that user finishes the operation to www.taobao.com, the cookie information corresponding to this URL can be uploaded to cloud server, and store according to user ID.
Preferably, comprise when described cookie information being uploaded to cloud server:
Step B1, calls the correlation function of process cookie information;
Further, by processing the function of cookie information in hook program pickup system api function.
In reality, the hook program by system hooks up in (hook) API calls and processes the function such as cookie information InternetSetCookie, InternetSetCookieEx, InternetSetCallback.
Step B2, obtains the information of write cookie by the described correlation function called;
For the correlation function of each process cookie information of aforementioned acquisition, by the described information being obtained each cookie of write by each function hooked up.
The domain name, content and the additional information that write cookie can be obtained by the function of above-mentioned hook.
Step B3, according to the domain name in described cookie information, builds in-process cookie list;
Further, comprise in this step:
Step C1, judges whether comprise timestamp in the information of each cookie; If do not comprised, then with the domain name in described cookie information for keyword, build in-process cookie list.
Generally, for in-process cookie, life period is not stabbed, and namely Expires=DATE is default; When spanned file, just by system function, timestamp can be added in the file of cookie information.
So for by the described information being obtained each cookie of write by each function hooked up, analyze in its additional information whether comprise timestamp, the cookie whether cookie belongs to in-process can be confirmed.
If do not comprised, then with the domain name in described cookie information for keyword, build in-process cookie list.
Step B4, according to described list, uploads for the cookie content under list described in each domain Name acquisition.
In reality, can according to described list, for each domain name, call the cookie content that InternetGetCookie obtains under this list one by one and upload.
When needs are preserved and uploaded cookie, the list using step B3 to generate, to each domain name, calls InternetGetCookie one by one to obtain content, and is stored to cloud server according to user ID by these content uploadings.
Preferably, comprised before described cookie information is uploaded:
Step C1, compresses described cookie information.Compress as by 128 zip being.
Preferably, comprised before described cookie information is uploaded:
Step C2, is encrypted described cookie information by key.
Generally, compression can be carried out with encryption simultaneously, such as uses the secret key encryption of zip+128 position.Then the transmission of data can use standard http to upload.
Preferably, comprise after described cookie information is uploaded to cloud server:
Step C3, adopts the mode of the safety encipher cookie information corresponding to described user ID to store.
Step 130, when the first client or the second client transmission company second connect request to cloud server, described second connection request comprises described user ID, if cloud server exists the cookie information of corresponding described user ID, then described cookie information is supplied to described first client or the second client downloads.
When user changes client, or the used client of user deletes the situations such as cookie information, when user send comprise user represent that the second connection request for downloading is to cloud server time, whether high in the clouds then exists cookie information corresponding to this user ID according in user ID inquiry cloud server, if existed, then the client that user uses then can download described cookie information.When such as user is logged in by the form of account and password, cloud server, according to searching cookie information corresponding to the account in account and password beyond the clouds server, if existed, is then supplied to the client that user uses and downloads.
Preferably, then comprise when described cookie information being supplied to described first client or the second client downloads:
Step H1, by each cookie information downloaded from cloud server, compared with each cookie information stored with the first client or the second client self, cookie information newer in corresponding cookie information is retained in described first client or the second client.
Further, comprise when cookie information newer in corresponding cookie information being retained in described first client or the second client:
Step H11, obtain the corresponding cookie information that domain name is identical and/or cookie name is identical for comparing, the cookie information that timestamp is wherein newer is retained in described first client or the second client as newer cookie information.
Preferably, step H1 comprises: step S130, for each cookie information downloaded from cloud server, according to the domain name in cookie information and/or cookie name, in each cookie information that the first client or the second client self exist, search whether there is the cookie information identical with each cookie information that cloud server is downloaded;
In this step, when there is cookie information in the client that user uses, if user is sent by the form such as user account and password and downloads request to cloud server, after the cookie information of this user of cloud server downloaded stored, using the domain name in cookie information and cookie name as keyword, each cookie information that each cookie information downloaded from high in the clouds and client this locality exist is carried out inquiry compare, confirm each cookie information downloaded from high in the clouds, whether to there is the cookie information identical with each cookie information that client this locality exists.
Step S131, if existed, then the distance of current time in the timestamp judging each cookie that domain name is identical with cookie name;
Each cookie information that each cookie information downloaded from high in the clouds and client this locality exist is carried out inquiry and is compared, confirm each cookie information downloaded from high in the clouds, to there is each cookie information domain name that exist local with the client cookie information identical with cookie name, so for the cookie information that described above-mentioned two aspects are identical, then corresponding according to its timestamp point writing time, compares with current time.In more described identical cookie information be from high in the clouds download close to current time, or this locality close to current time.
Step S132, when the timestamp of a cookie information of described cloud server self to exist the update of time stamp of described cookie information than described first client or the second client, then cover described first client by system api function InternetSetCookie or the second client self exists described cookie information;
When in the cookie information that domain name is identical with cookie name, from high in the clouds download certain cookie information more local than client correspondence cookie information from current time more close to, so calling system api function InternetSetCookie, covers described first client or the second client self exists described cookie information.
Step S133, self there is the update of time stamp of described cookie information when the timestamp of a cookie information of described cloud server in step, then retains described first client or the second client self exists described cookie information unlike described first client or the second client.
When in the cookie information that domain name is identical with cookie name, certain cookie information downloaded from high in the clouds corresponding cookie information more local than client is farther from current time, so retain described first client or the second client self exists described cookie information, delete the corresponding cookie information downloaded from high in the clouds.
In addition, when user is by two clients or more multi-client, use same user ID (such as same username and password) to send a request to high in the clouds simultaneously, after the cookie of each client is uploaded to high in the clouds, for the cookie information of same domain name and cookie name, the newer cookie information of its timestamp can be retained beyond the clouds.In this application, if same user uses same mark (when same account and code entry cloud server) in multiple client, such as user is simultaneously when customer end A and customer end B use same account 123 to log in cloud server, the cookie information then uploaded in customer end A for 123, so 123 can the cookie information uploaded of real-time update 123 customer end A in customer end B, its renewal process by step step S130 to step step S133.
With reference to Fig. 2, it illustrates the structural representation of a kind of cookie information storage system of the application, comprising:
First client 210 and cloud server 220, and/or the second client;
Described first client 210 comprises:
First connection request sending module 211, for sending the first connection request to cloud server, obtains cloud server storing authorization; Described connection request comprises user ID;
Transmission module 212 in cookie information, for the cookie information that module generates for the first Client browse page, is uploaded to described cookie information in cloud server, and stores according to described user ID;
First download request sending module 213, downloads cookie information second connection request for sending;
Described cloud server 220 comprises:
User ID memory module 221, for storing the cookie information respective user of the first client upload mark;
Request receiving module 222, for receiving the first connection request of the first client, receives the second connection request of the first client and/or the second client;
Information is downloaded and is provided module 223, for cookie information is supplied to client downloads;
Described second client comprises the second download request sending module, downloads cookie information second connection request for sending.
Wherein, described permissions module specifically can be used for license first client upload cookie information and is stored in cloud server, also can permit when the first client or the second client transmission company second connect request to cloud server, described second connection request comprises described user ID, if cloud server exists the cookie information of corresponding described user ID, then described cookie information is supplied to described first client or the second client downloads.
In the application, the cookie information of the first client upload can carry out download cookie information at least one second client according to user ID.
Preferably, described first client comprises judge module further, described judge module, for according to the operation of the first client to the page or browser, judge the opportunity of uploading cookie information in the first client, when opportunity is uploaded in arrival, described cookie information is uploaded automatically.
Preferably, upload opportunity judge module described in comprise:
First opportunity judge module, for monitoring in the first client the order that specific browser window is closed; When monitoring described shutdown command, each cookie information being uploaded to cloud server and storing according to user ID.
Preferably, described specific browser window comprises is the window that current browser is only deposited.
Preferably, described upload opportunity judge module comprise further second opportunity judge module, described second opportunity judge module, for each page opened for the first client, analyze the non-operating time of described first client to described each page, when the described non-operating time is more than or equal to threshold value, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
Preferably, described upload opportunity judge module comprise further the 3rd opportunity judge module, described 3rd opportunity judge module, for the page opened for the first client, judge whether the described page closes or redirect, if closed or redirect, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
Preferably, in described client, comprised before described cookie information is uploaded:
Compression module, for compressing described cookie information.
Preferably, in described client, comprised before described cookie information is uploaded:
Encrypting module, for being encrypted described cookie information by key.
Preferably, in described cloud server, comprise after described cookie information is uploaded to cloud server:
Secure storage module, stores for the cookie information adopting the mode of safety encipher corresponding to described user ID.
Preferably, in described first client, comprising:
Function call module, for calling the correlation function of process cookie information;
Data obtaining module, the correlation function for calling described in passing through obtains the information of write cookie;
Process cookie list builder module, for according to the domain name in described cookie information, builds in-process cookie list;
Transmission module in first cookie information, for according to described list, uploads for the cookie content under list described in each domain Name acquisition.
Preferably, also comprise:
Synchronization module, for each cookie information will downloaded from cloud server, compared with each cookie information stored with the first client or the second client self, cookie information newer in corresponding cookie information is retained in described first client or the second client.
Preferably, described synchronization module is further used for:
Obtain the corresponding cookie information that domain name is identical and/or cookie name is identical for comparing, the cookie information that timestamp is wherein newer is retained in described first client or the second client as newer cookie information.
Preferably, when using same user ID to upload cookie information to high in the clouds by least two clients, for domain name and/or the identical cookie information of cookie name, retain the cookie information that its timestamp is newer.
For system 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.
Each embodiment in this specification all adopts the mode of going forward one by one to describe, and what each embodiment stressed is the difference with other embodiments, between each embodiment identical similar part mutually see.
Finally, also it should be noted that, in this article, the such as relational terms of first and second grades and so on is only used for an entity or operation to separate with another entity or operating space, and not necessarily requires or imply the relation that there is any this reality between these entities or operation or sequentially.
Those skilled in the art should understand, the embodiment of the application can be provided as method, system or computer program.Therefore, the application can adopt the form of complete hardware embodiment, completely software implementation or the embodiment in conjunction with software and hardware aspect.And the application can adopt in one or more form wherein including the upper computer program implemented of computer-usable storage medium (including but not limited to magnetic disc store, CD-ROM, optical memory etc.) of computer usable program code.
The application describes with reference to according to the flow chart of the method for the embodiment of the present application, equipment (system) and computer program and/or block diagram.Should understand can by the combination of the flow process in each flow process in computer program instructions realization flow figure and/or block diagram and/or square frame and flow chart and/or block diagram and/or square frame.These computer program instructions can being provided to the processor of all-purpose computer, special-purpose computer, Embedded Processor or other programmable data processing device to produce a machine, making the instruction performed by the processor of computer or other programmable data processing device produce device for realizing the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.
These computer program instructions also can be stored in can in the computer-readable memory that works in a specific way of vectoring computer or other programmable data processing device, the instruction making to be stored in this computer-readable memory produces the manufacture comprising command device, and this command device realizes the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.
These computer program instructions also can be loaded in computer or other programmable data processing device, make on computer or other programmable devices, to perform sequence of operations step to produce computer implemented process, thus the instruction performed on computer or other programmable devices is provided for the step realizing the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.
Although described the preferred embodiment of the application, those skilled in the art once obtain the basic creative concept of cicada, then can make other change and amendment to these embodiments.So claims are intended to be interpreted as comprising preferred embodiment and falling into all changes and the amendment of the application's scope.
A kind of cookie information storage means above the application provided and system, be described in detail, apply specific case herein to set forth the principle of the application and execution mode, the explanation of above embodiment is just for helping method and the core concept thereof of understanding the application; Meanwhile, for one of ordinary skill in the art, according to the thought of the application, all will change in specific embodiments and applications, in sum, this description should not be construed as the restriction to the application.
Claims (28)
1. a cookie information storage means, is characterized in that, comprising:
First client sends the first connection request to cloud server, obtains cloud server storing authorization; Described first connection request comprises user ID; Described user ID, for the first client and the second client, logs in cloud server for the first client and the second client;
For the cookie information that the first Client browse page also generates in the client, described cookie information is uploaded in cloud server, and stores according to described user ID; Wherein, comprise when described cookie information is uploaded: according to the operation of the first client to each page of opened each website, described cookie information is uploaded to cloud server;
When the first client or the second client send the second connection request to cloud server, described second connection request comprises described user ID, if cloud server exists the cookie information of corresponding described user ID, then described cookie information is supplied to described first client or the second client downloads.
2. method according to claim 1, is characterized in that, comprises when described cookie information being uploaded:
According to the operation of the first client to the page or browser, judge the opportunity of uploading cookie information in the first client, when opportunity is uploaded in arrival, described cookie information is uploaded automatically.
3. method according to claim 1, is characterized in that, comprises when described cookie information being uploaded:
Monitor in the first client the order that specific browser window is closed; When monitoring described shutdown command, each cookie information being uploaded to cloud server and storing according to user ID.
4. method according to claim 3, is characterized in that:
It is the window that current browser is only deposited that described specific browser window comprises.
5. method according to claim 1, is characterized in that, comprises when described cookie information being uploaded:
For each page that the first client is opened, analyze the non-operating time of described first client to the described page, when the described non-operating time is more than or equal to threshold value, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
6. method according to claim 1, is characterized in that, comprises when described cookie information being uploaded:
For the page that the first client is opened, judge whether the described page closes or redirect, if closed or redirect, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
7. method according to claim 1, is characterized in that, comprises before described cookie information being uploaded:
Described cookie information is compressed.
8. the method according to claim 1 or 7, is characterized in that, comprises before described cookie information being uploaded:
By key, described cookie information is encrypted.
9. method according to claim 1, is characterized in that, comprises after described cookie information is uploaded to cloud server:
The mode of the safety encipher cookie information corresponding to described user ID is adopted to store.
10. method according to claim 8, is characterized in that, comprises after described cookie information is uploaded to cloud server:
The mode of the safety encipher cookie information corresponding to described user ID is adopted to store.
11. methods according to claim 1, is characterized in that, comprise when described cookie information is uploaded to cloud server:
Call the correlation function of process cookie information;
The information of write cookie is obtained by the described correlation function called;
According to the domain name in described cookie information, build in-process cookie list;
According to described list, upload for the cookie content under list described in each domain Name acquisition.
12. methods according to claim 1, is characterized in that, also comprise:
By each cookie information downloaded from cloud server, compared with each cookie information stored with the first client or the second client self, cookie information newer in corresponding cookie information is retained in described first client or the second client.
13. methods according to claim 12, is characterized in that, comprise when cookie information newer in corresponding cookie information being retained in described first client or the second client:
Obtain the corresponding cookie information that domain name is identical and/or cookie name is identical for comparing, the cookie information that timestamp is wherein newer is retained in described first client or the second client as newer cookie information.
14. methods according to claim 1, is characterized in that:
When using same user ID to upload cookie information to cloud server by least two clients, for domain name and/or the identical cookie information of cookie name, retain the cookie information that its timestamp is newer.
15. 1 kinds of cookie information storage systems, is characterized in that, comprising:
First client and cloud server, and/or the second client;
Described first client comprises:
First connection request sending module, for sending the first connection request to cloud server, obtains cloud server storing authorization; Described first connection request comprises user ID; Described user ID, for the first client and the second client, logs in cloud server for the first client and the second client;
Transmission module in cookie information, for the cookie information also generated in the client for the first Client browse page, is uploaded to described cookie information in cloud server, and stores according to described user ID; Wherein, comprise when described cookie information is uploaded: according to the operation of the first client to each page of opened each website, described cookie information is uploaded to cloud server;
First download request sending module, downloads cookie information second connection request for sending; Described second connection request comprises described user ID;
Described cloud server comprises:
User ID memory module, for storing the cookie information respective user of the first client upload mark;
Request receiving module, for receiving the first connection request of the first client, receives the second connection request of the first client and/or the second client;
Information is downloaded and is provided module, for the cookie information corresponding with described user ID is supplied to the first client or the second client downloads;
Described second client comprises the second download request sending module, downloads cookie information second connection request for sending; Described second connection request comprises described user ID.
16. systems according to claim 15, it is characterized in that: described first client comprises judge module further, described judge module, for according to the operation of the first client to the page or browser, judge the opportunity of uploading cookie information in the first client, when opportunity is uploaded in arrival, described cookie information is uploaded automatically.
17. systems according to claim 16, is characterized in that, described judge module comprises:
First opportunity judge module, for monitoring in the first client the order that specific browser window is closed; When monitoring described shutdown command, each cookie information being uploaded to cloud server and storing according to user ID.
18. systems according to claim 17, is characterized in that:
It is the window that current browser is only deposited that described specific browser window comprises.
19. systems according to claim 16, it is characterized in that: described judge module comprise further second opportunity judge module, described second opportunity judge module, for each page opened for the first client, analyze the non-operating time of described first client to described each page, when the described non-operating time is more than or equal to threshold value, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
20. systems according to claim 16, it is characterized in that: described judge module comprise further the 3rd opportunity judge module, described 3rd opportunity judge module, for the page opened for the first client, judge whether the described page closes or redirect, if closed or redirect, then according to the first client cookie information store path, cookie information corresponding for the described page is uploaded to cloud server and stores according to user ID.
21. systems according to claim 15, is characterized in that, in described first client, comprise before described cookie information being uploaded:
Compression module, for compressing described cookie information.
22. systems according to claim 15 or 21, is characterized in that, in described first client, comprised before described cookie information being uploaded:
Encrypting module, for being encrypted described cookie information by key.
23. systems according to claim 15, is characterized in that, in described cloud server, comprise after described cookie information is uploaded to cloud server:
Secure storage module, stores for the cookie information adopting the mode of safety encipher corresponding to described user ID.
24. systems according to claim 22, is characterized in that, in described cloud server, comprise after described cookie information is uploaded to cloud server:
Secure storage module, stores for the cookie information adopting the mode of safety encipher corresponding to described user ID.
25. systems according to claim 15, is characterized in that, in described first client, comprising:
Function call module, for calling the correlation function of process cookie information;
Data obtaining module, the correlation function for calling described in passing through obtains the information of write cookie;
Process cookie list builder module, for according to the domain name in described cookie information, builds in-process cookie list;
Transmission module in first cookie information, for according to described list, uploads for the cookie content under list described in each domain Name acquisition.
26. systems according to claim 15, is characterized in that, described first client or the second client also comprise:
Synchronization module, for each cookie information will downloaded from cloud server, compared with each cookie information stored with the first client or the second client self, cookie information newer in corresponding cookie information is retained in described first client or the second client.
27. systems according to claim 26, is characterized in that, described synchronization module is further used for:
Obtain the corresponding cookie information that domain name is identical and/or cookie name is identical for comparing, the cookie information that timestamp is wherein newer is retained in described first client or the second client as newer cookie information.
28. systems according to claim 15, is characterized in that:
When using same user ID to upload cookie information to cloud server by least two clients, for domain name and/or the identical cookie information of cookie name, retain the cookie information that its timestamp is newer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210094095.9A CN102638581B (en) | 2012-03-31 | 2012-03-31 | A kind of cookie information storage means and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210094095.9A CN102638581B (en) | 2012-03-31 | 2012-03-31 | A kind of cookie information storage means and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102638581A CN102638581A (en) | 2012-08-15 |
| CN102638581B true CN102638581B (en) | 2015-11-25 |
Family
ID=46622822
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210094095.9A Active CN102638581B (en) | 2012-03-31 | 2012-03-31 | A kind of cookie information storage means and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102638581B (en) |
Families Citing this family (33)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103631827B (en) | 2012-08-29 | 2016-08-10 | 腾讯科技（深圳）有限公司 | A kind of method and system of Synchronization Network page information |
| CN102917118A (en) * | 2012-09-13 | 2013-02-06 | 东莞宇龙通信科技有限公司 | Terminal and task display method |
| CN102932421A (en) * | 2012-09-28 | 2013-02-13 | 中国联合网络通信集团有限公司 | Cloud back-up method and device |
| CN105119973B (en) * | 2012-11-05 | 2019-03-08 | 北京奇虎科技有限公司 | User information processing method and server |
| CN103701844B (en) * | 2012-11-05 | 2017-06-23 | 北京奇虎科技有限公司 | The method and system of managing user information |
| CN103002030B (en) * | 2012-11-26 | 2016-03-16 | 北京百度网讯科技有限公司 | The method and system of file-sharing |
| CN104038518B (en) * | 2013-03-05 | 2018-06-01 | 联想(北京)有限公司 | information processing method, server and terminal device |
| CN103248631B (en) * | 2013-05-27 | 2016-05-25 | 百度在线网络技术（北京）有限公司 | Method, system and the browser of browser-cross identifying user identity |
| CN104348893B (en) * | 2013-08-09 | 2018-08-31 | 联想(北京)有限公司 | A kind of method and device that data synchronize |
| CN103618698B (en) * | 2013-11-08 | 2017-03-15 | 北京奇虎科技有限公司 | The processing method and processing device of cookie information |
| CN104796442B (en) * | 2014-01-17 | 2020-08-07 | 腾讯科技（深圳）有限公司 | Webpage access information synchronization method, device and system |
| CN104391974B (en) * | 2014-12-05 | 2018-04-17 | 北京奇虎科技有限公司 | The processing method of browser and its favorites data |
| CN104468790B (en) * | 2014-12-09 | 2018-09-11 | 北京奇虎科技有限公司 | The processing method and client of cookie data |
| CN105988805B (en) * | 2015-02-12 | 2020-01-14 | Oppo广东移动通信有限公司 | Application program management method and mobile terminal |
| CN105610802A (en) * | 2015-12-22 | 2016-05-25 | 北京奇虎科技有限公司 | Method and system for logging in by borrowing accounts of other people |
| CN105610798B (en) * | 2015-12-22 | 2019-02-12 | 北京奇虎科技有限公司 | A kind of method and system for borrowing other people accounts and realizing login |
| CN105610801A (en) * | 2015-12-22 | 2016-05-25 | 北京奇虎科技有限公司 | Method and system for logging in by borrowing accounts of other people |
| CN105516167B (en) * | 2015-12-22 | 2019-05-31 | 北京奇虎科技有限公司 | A kind of method and system for borrowing other people accounts and realizing login |
| CN109787967B (en) * | 2015-12-22 | 2021-09-24 | 北京奇虎科技有限公司 | Method and system for realizing login by borrowing account of other people |
| CN106933922A (en) * | 2015-12-31 | 2017-07-07 | 北京国双科技有限公司 | The method and apparatus for storing ID |
| CN105808731A (en) * | 2016-03-09 | 2016-07-27 | 北京小米移动软件有限公司 | Data storage method and device |
| CN107645527B (en) * | 2016-07-20 | 2021-06-04 | 平安科技（深圳）有限公司 | Information synchronization method and device |
| CN106060099A (en) * | 2016-08-15 | 2016-10-26 | 北京奇虎科技有限公司 | Data access method and system, and devices |
| CN106302792B (en) * | 2016-08-30 | 2019-07-09 | 福建天晴数码有限公司 | Compression sends the method and system of browser Cookie |
| CN106302791B (en) * | 2016-08-30 | 2019-08-13 | 福建天晴数码有限公司 | The transmission method and system of browser Cookie |
| CN106446640B (en) * | 2016-10-31 | 2019-11-08 | 东软集团股份有限公司 | User knows method for distinguishing and server |
| CN107172169A (en) * | 2017-05-27 | 2017-09-15 | 广东欧珀移动通信有限公司 | Method of data synchronization, device, server and storage medium |
| CN107885811B (en) * | 2017-11-03 | 2021-03-05 | 广州视源电子科技股份有限公司 | Shared file display method, device, equipment and storage medium |
| CN108388657B (en) * | 2018-03-06 | 2022-04-05 | 五八有限公司 | Cookie storage method, device, equipment and readable storage medium |
| WO2019194811A1 (en) * | 2018-04-05 | 2019-10-10 | Google Llc | Domain specific browser identifiers as replacement of browser cookies |
| CN112134855B (en) * | 2020-09-01 | 2023-07-14 | Vidaa(荷兰)国际控股有限公司 | Cookie encryption method and display device |
| CN114650272A (en) * | 2020-12-17 | 2022-06-21 | 上海嗨普智能信息科技股份有限公司 | User unique identifier processing method, device, storage medium and computer device |
| CN114339630B (en) * | 2021-11-30 | 2023-07-21 | 度小满科技(北京)有限公司 | Method and device for protecting short message |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101039317A (en) * | 2006-03-14 | 2007-09-19 | 中兴通讯股份有限公司 | Method for realizing browse service COOKIE of wireless application protocol gateway |
| CN101702647A (en) * | 2009-11-30 | 2010-05-05 | 中国电信股份有限公司 | Management method of Cookie information and Cookie server |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040049673A1 (en) * | 2002-09-05 | 2004-03-11 | Docomo Communications Laboratories Usa, Inc. | Apparatus and method for a personal cookie repository service for cookie management among multiple devices |
| US20070157304A1 (en) * | 2006-01-05 | 2007-07-05 | International Business Machines Corporation | Method, apparatus and computer program product for automatic cookie synchronization between distinct web browsers |
-
2012
- 2012-03-31 CN CN201210094095.9A patent/CN102638581B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101039317A (en) * | 2006-03-14 | 2007-09-19 | 中兴通讯股份有限公司 | Method for realizing browse service COOKIE of wireless application protocol gateway |
| CN101702647A (en) * | 2009-11-30 | 2010-05-05 | 中国电信股份有限公司 | Management method of Cookie information and Cookie server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102638581A (en) | 2012-08-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102638581B (en) | A kind of cookie information storage means and system | |
| US10313354B2 (en) | Systems and methods for efficient and secure temporary anonymous access to media content | |
| Ab Rahman et al. | Cloud incident handling and forensic‐by‐design: cloud storage as a case study | |
| CN104216700B (en) | System of cloud-computing-based HTML5 application packaging, installation, unloading and operation method | |
| US9106709B2 (en) | Server side mobile audience intelligence creation | |
| Jo et al. | Digital forensic practices and methodologies for AI speaker ecosystems | |
| CN103336774B (en) | By sandbox from retrieved web content | |
| CN103023710B (en) | A kind of safety test system and method | |
| US8799365B2 (en) | Broker-based management of mobile devices | |
| Borders et al. | Quantifying information leaks in outbound web traffic | |
| CN109886037B (en) | Electronic evidence auditing method based on blockchain | |
| CN106874778B (en) | Intelligent terminal file acquisition and data recovery system and method based on android system | |
| EP3557843A1 (en) | Content delivery network (cdn) bot detection using primitive and compound feature sets | |
| CN103037312A (en) | Message push method and message push device | |
| US10185822B2 (en) | Systems and methods for tracking and recording events in a network of computing systems | |
| CN112788270B (en) | Video backtracking method, device, computer equipment and storage medium | |
| CN109639819B (en) | File transmission method, client, server and system | |
| US20180205705A1 (en) | Network request proxy system and method | |
| US20150169392A1 (en) | System and method for providing an application programming interface intermediary for hypertext transfer protocol web services | |
| CN108667835A (en) | A kind of control remote equipment carries out method, system and the storage medium of network forensics | |
| US9471533B1 (en) | Defenses against use of tainted cache | |
| US20140351418A1 (en) | Method and server for monitoring users during their browsing within a communications network | |
| CN110958239B (en) | Method and device for verifying access request, storage medium and electronic device | |
| CN111258602A (en) | Information updating method and device | |
| CN112308561A (en) | Block chain-based evidence storing method and system, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: QIZHI SOFTWARE (BEIJING) CO., LTD. Effective date: 20121107 Owner name: BEIJING QIHU TECHNOLOGY CO., LTD. Free format text: FORMER OWNER: QIZHI SOFTWARE (BEIJING) CO., LTD. Effective date: 20121107 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 100016 CHAOYANG, BEIJING TO: 100088 XICHENG, BEIJING |
|
| TA01 | Transfer of patent application right |
Effective date of registration: 20121107 Address after: 100088 Beijing city Xicheng District xinjiekouwai Street 28, block D room 112 (Desheng Park) Applicant after: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Applicant after: Qizhi software (Beijing) Co.,Ltd. Address before: The 4 layer 100016 unit of Beijing city Chaoyang District Jiuxianqiao Road No. 14 Building C Applicant before: Qizhi software (Beijing) Co.,Ltd. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220715 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. |
|
| TR01 | Transfer of patent right |