CN102387026B - Management method and device for user data in system based on universal relation link model - Google Patents
Management method and device for user data in system based on universal relation link model Download PDFInfo
- Publication number
- CN102387026B CN102387026B CN201010276127.8A CN201010276127A CN102387026B CN 102387026 B CN102387026 B CN 102387026B CN 201010276127 A CN201010276127 A CN 201010276127A CN 102387026 B CN102387026 B CN 102387026B
- Authority
- CN
- China
- Prior art keywords
- user
- subscriber data
- picture information
- historical materials
- written historical
- 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
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention provides a management method and device for user data in a system based on a universal relation link model. The system takes a client side as a carrier and comprises a server for providing service for a system user. The management method comprises the following steps: according to the requirement of a user who logs in the client side, a management device positioned in the client side or connected with the client side pulls the user data of the system from the server; different types of user data are stored in a client side locality in different storage modes; and the management device manages the stored user data according to a preset strategy. The pulled user data comprises the data of the user who logs in the client side and can comprise the data of other users. According to the embodiment disclosed by the invention, the user data can be effectively managed and quickly displayed.
Description
Technical field
The present invention relates to networking technology area, be specifically related to management method and the device of subscriber data in the system based on universal relation chain model.
Background technology
Along with the development of network technology, various network communication systems have been there are.Wherein, the system based on universal relation chain model is subject to more and more network users' favor.In the system based on universal relation chain model, can be not between the user of system just opening relationships easily of mode by request, checking.Therefore, this system make Internet chat pattern from one to one, a pair of N crosses a pair of infinite.This pair of infinite chat pattern means that a user can spread news to infinite other many users, and can receive more than ten thousand grades user's message simultaneously.In this system, audience and speaker's quantity is very large, and user sends a piece of news and can be listened to by other countless users.Therefore, this system has the information of magnanimity, such as having the subscriber data of magnanimity.
At present, the conventional system based on universal relation chain model can also can be take client (as IM client etc.) as carrier take webpage as carrier, and the subscriber data of system all carries out maintenance and management by system server unification.In the system take client as carrier, when user passes through client login system, need to a large amount of subscriber datas be represented to this user by client by system server, and when this user is constantly switched perpetual object, system server needs by client constantly for user upgrades the subscriber data that it is paid close attention to.As can be seen here, when user thinks inquiring user data, all must just can obtain via system server, and can not be in client terminal local inquiring user data, therefore cause user can not know quickly and easily subscriber data, client can not represent subscriber data rapidly.And client must frequently constantly be carried out alternately with system server, thereby causes the communication pressure of system server excessive, even cause system server paralysis.Therefore, be badly in need of the subscriber data of the system based on universal relation chain model to carry out more effective management.
At present, the most widely used system based on universal relation chain model is microblogging system.In microblogging system, user spreads news by a word of 140 word left and right.This communication mode is brief, convenient, can carry out rapidly propagation and the transmission of information.The a pair of infinite chat pattern that microblogging adopts makes microblogging system have the subscriber data of magnanimity.In the microblogging take client as carrier, client must be continually with microblogging server interaction to obtain the subscriber data of microblogging, and the subscriber data quantity of microblogging is huge, thereby cause client can not represent rapidly the subscriber data of microblogging, and cause microblogging server communication pressure excessive, even cause microblogging servers go down.
Summary of the invention
In view of this, main purpose of the present invention is to provide management method and the device of subscriber data in the system based on universal relation chain model, and the method and device can make client effectively manage the subscriber data of magnanimity.
The embodiment of the present invention provides the management method of subscriber data in the system based on universal relation chain model, and this system is take client as carrier and comprise the server that service is provided to system user.The method comprises:
Be positioned at described client management devices inner or that be connected with described client and from server, pull the subscriber data of system according to this client user's of login demand, and adopt different preserving types to be stored in client terminal local dissimilar subscriber data; Management devices, according to predetermined strategy, manages the subscriber data of preserving.Wherein, subscriber data at least comprises the data of logining this client user.
The embodiment of the present invention also provides the management devices of subscriber data in the system based on universal relation chain model, and this system is take client as carrier and comprise the server that is used to system user that service is provided, and is positioned at the client-side of this system.This device comprises:
Pull module, for pulling subscriber data according to this client user's of login demand from the server of system, wherein, subscriber data at least comprises the data of logining this client user;
Preserve module, for adopting different preserving types to preserve dissimilar subscriber data;
Administration module, for according to predetermined strategy, manages the subscriber data of preserving module preservation.
Client manages and comprises local subscriber data: according to predetermined strategy, and inquiry, renewal and/or deletion subscriber data, and/or to user notification subscriber data event.
According to the embodiment of the present invention, because dissimilar subscriber data adopts different preserving types, thereby can more sufficiently and reasonably utilize memory space at client terminal local.And, because subscriber data is kept at client terminal local after pulling, when user is again during inquiring user data, management devices is first at local search, rather than directly to microblogging server request subscriber data, therefore invoke user data more quickly, and can represent rapidly subscriber data.In addition, when local subscriber data is managed, also can select different way to manages according to different subscriber data types and different scenes, and then can more reasonably to subscriber data, manage.Such as, during user's login, when user user data, (while checking other people subscriber data such as user) just upgrades once, and the subscriber data this time having upgraded during login no longer upgrades, avoided repeating to pull, reduced and the interaction times of microblogging server, reduced the communication pressure of microblogging server.
Accompanying drawing explanation
In accompanying drawing of the present invention,
Fig. 1 is according to the management method flow chart of subscriber data in the system based on universal relation chain model of the embodiment of the present invention;
Fig. 2 shows according to the particular flow sheet that pulls and preserve subscriber data in the embodiment of the present invention;
Fig. 3 is the management flow chart of user's written historical materials in microblogging system in the embodiment of the present invention;
Fig. 4 is the management flow chart of user's picture information in microblogging system in the embodiment of the present invention;
Fig. 5 is according to the structure chart of the management devices of subscriber data in the system based on universal relation chain model of the embodiment of the present invention;
Fig. 6 is according to a kind of building-block of logic of the management devices of subscriber data in the system based on universal relation chain model of the embodiment of the present invention.
Embodiment
Below in conjunction with the drawings and specific embodiments, the present invention is described in detail.
At present, in the system based on universal relation chain take client as carrier, there is the subscriber data of magnanimity, problem demanding prompt solution while how effectively to manage the subscriber data of magnanimity.At present, the subscriber data of system mostly administers and maintains via system server, rather than manages and safeguard at client terminal local, thus cause client can not be rapidly for user provide subscriber data inquiry, represent etc.And, in to the management of subscriber data, do not consider the type of subscriber data and different scenes, lack of control flexibility.
In order to overcome the problems referred to above, the embodiment of the present invention provides the management method of subscriber data in the system based on universal relation chain model, this system take client as carrier and user by this client, enter system, this system comprises server, is used to system user that service is provided.Fig. 1 is according to the management method flow chart of subscriber data in the system based on universal relation chain model of the embodiment of the present invention.As shown in Figure 1, in step 101, management devices pulls user's data according to the demand of the user A of this client of login from the server of system, and adopts different preserving types at client terminal local, to preserve the subscriber data pulling according to different subscriber data types; In step 102, management devices, according to predetermined strategy, manages the subscriber data of preserving.The subscriber data pulling comprises the data of user A, can also comprise other users' data.Wherein, management devices be positioned at client inside for realize the module of management method or be positioned at client outside and coupled for realizing the management devices of management method.In following examples, take management devices, be positioned at client inside and describe as example.
In the present embodiment, client can pull the data of user A self when user A logins client first from system server, with the subscriber data of user A appointment, and adopt different preserving types at client terminal local, to preserve the subscriber data pulling according to the type of the subscriber data pulling.The subscriber data that user A specifies can be the subscriber data of the interested or frequent use of user A, can be also the user's of the current concern of user A data.Because user A is interested or the subscriber data of frequent use is stored in client terminal local after user A login, and managed according to predetermined strategy by client.Thereby when these subscriber datas of follow-up use, client can be in local invoke user data, thereby can represent rapidly subscriber data.And, because client is when representing subscriber data, can be in client terminal local invoke user data, and need not all from server, pull subscriber data at every turn, therefore the interaction times of client and server has reduced, thereby can reduce the communication pressure of server, guarantee that server provides service more quickly and efficiently.
The type of subscriber data at least comprises written historical materials and picture information.Wherein written historical materials is generally used for the essential information of describing user, such as user identification code UIN or user ID ID, user name, occupation, interest etc.Picture information is generally used for the image that shows user, and such as user's head portrait, it comprises URL information and/or the picture file of picture file.
Further, client can comprise inquiry, the renewal of subscriber data and/or delete subscriber data and/or notify subscriber data event to user A the management of the subscriber data of preserving.
The application at present more widely system based on universal relation chain model has microblogging system, and in microblogging system take client as carrier, client can be microblogging private client, also can be existing telecommunication customer end, as QQ, MSN, the telecommunication customer end of the instant messaging IM clients such as ICQ or other types.In following examples, the microblogging system take IM client as carrier is illustrated to the management method of subscriber data in the system based on universal relation chain model as example.
In the microblogging system take IM client as carrier, can add a microblogging Tab page at the interface of IM client, user can enter microblogging system as long as click microblogging Tab page.User logins IM client, can enter microblogging system by microblogging Tab page.
In embodiments of the present invention, microblog users data is independent of IM data, and its picture information can be the head portrait of microblog users.Head portrait can be the acquiescence head portrait of self-defined head portrait or client.In the microblogging system take IM client as carrier, microblog users data and IM data are separate, make the management of microblog users data of magnanimity convenient.
Fig. 2 shows according to the particular flow sheet that pulls and preserve subscriber data in the step 101 of the embodiment of the present invention.As shown in Figure 2, step 101 comprises:
The subscriber data of the user A of step 201:IM client login IM client pulls instruction, wherein carries corresponding user identification code UIN or the user ID ID of subscriber data that need to pull.
In this step, when user A login IM client is equivalent to have sent subscriber data to IM client, pull instruction, wherein carry UIN or the ID of user A.Certainly, user A can select the user of own interested or frequent access and send subscriber data to IM client to pull instruction after login, wherein carries the interested user's of user A UIN or ID.Step 202:IM client sends subscriber data to microblogging server and pulls request, and this subscriber data pulls request and carries the user identification code UIN corresponding with subscriber data or user ID ID.
Step 203:IM client microblogging server pulls according to this subscriber data the response that UIN in request or ID return to IM client, carries the subscriber data corresponding with UIN or ID in this response.
In this step, when microblogging server returns to response, according to dissimilar subscriber data type, do different processing.For written historical materials, be directly carried in response and return to IM to client; For head portrait, the URL information of head portrait file is carried at and in response, returns to IM client, IM client is downloaded head portrait file from microblogging server or the Business Information and IT Solution Mgmt Dep that is arranged at microblogging server outside again according to the URL information of receiving.
Preferably, IM client judges that whether the URL information of local storage is identical with the URL information of receiving before head portrait file in next week, if identical, then would confirm that whether this locality stores the head portrait file corresponding with URL, if had, does not download head portrait file; If URL information difference, downloads head portrait file.
Step 204:IM client is kept at this locality by the subscriber data corresponding with UIN or ID carrying in response.
In this step, IM client adopts different preserving types to preserve dissimilar subscriber data.Particularly, for the written historical materials in subscriber data, because its space taking is smaller, the speed of downloading from microblogging server is also just than comparatively fast, and therefore IM client can be kept at written historical materials in local internal memory.Therefore, IM client can, according to the written historical materials in the local internal memory of predetermined tactical management, improve the speed of calling of written historical materials, and then improve the efficiency of management to subscriber data.Certainly, written historical materials also can be kept in local disk.But, the relative picture information of written historical materials, speed of download, than very fast, is downloaded written historical materials from microblogging server during each user A login IM client little on the communication pressure impact of microblogging server again.Therefore, the embodiment of the present invention has been selected the preserving type that written historical materials is kept to local internal memory.
In addition, for picture information, need to take different preserving types according to different scenes.Picture information generally comprises picture file URL information and picture file itself, and the space that need to take is larger, therefore the preservation of picture information is also needed to consider different scenes.
In embodiments of the present invention, about the preservation of picture information, at least can consider following three kinds of scenes: the demand that 1) shows and/or frequently use in enormous quantities picture file, as the head portrait of the message publisher in microblogging homepage or@page, the message that the people that wherein microblogging homepage displaying user A listens to delivers, in@page, be the page of user A oneself, show user A message that deliver or that mention user A; 2) single demand of checking picture file, as enter the demand that microblogging guest page is checked guest's head portrait; 3) during login, may only need to show the demonstration demand of picture file in enormous quantities once, such as other users' idol or bean vermicelli list.
For the 1st) plant scene, IM client is preserved URL information and the picture file of picture file at local disk.For the 2nd) plant scene, IM client is preserved URL information and the picture file of picture file after checking picture file at local disk.For the 3rd) plant scene, IM client is kept at local internal memory by the URL information of picture file, and picture file is kept to local disk temporarily, and after user A exits IM client, removes the interim picture file of preserving.
As can be seen here, in embodiments of the present invention, the preserving type difference to picture information under different scenes, thus can to picture information, manage flexibly and easily at IM client terminal local.
For the 1st) plant the picture information in scene, because the picture file occupied bandwidth showing in enormous quantities is many, the speed of downloading from microblogging server is just slow, and can take a large amount of internal memories, therefore adopt and be kept at the preserving type of local disk, thereby can call rapidly and represent large batch of picture literary composition file in IM client.In addition, for the picture file of frequent use, if each, use all and download from microblogging server, need continually and microblogging server interaction, thereby increased and the interaction times of microblogging server, and then increase the communication pressure of microblogging server.And the speed of download of picture file is slower, IM client also can be influenced to the speed that represents of picture file.Therefore the frequent picture file using also adopts the preserving type that is kept at local disk.Because picture file is preserved in this locality, can facilitate IM client according to predetermined strategy, subscriber data to be managed, such as inquiring about quickly and easily and represent.
For the 2nd) kind scene, because user A needs the single picture file of checking, it is generally the interested or frequent use of user, therefore after checking picture file, at local disk, preserve URL information and the picture file of picture file, by the local subscriber data of preserving of IM client-side management, so that more convenient when subsequent user A checks, in the subscriber data that can be preserved in this locality by IM client, call this picture file and represent the A to user, thereby it is faster to represent speed.
The 1st) and the 2nd) plant in scene, IM client can be kept at picture information under the particular category of local disk.
For the 3rd) plant scene, owing to may only needing to show once during login, can preserve temporarily or preserve at internal memory; And owing to being large batch of picture, need to take larger space, being kept at internal memory can increase memory pressure, therefore preferably preserving type for be kept at local disk temporarily, such as being kept under temp directory.Preferably, the 3rd) the URL information of the picture file in Scene can be kept in internal memory, and picture file is kept under the temp directory of local disk.
In addition, in IM client, pull picture file failure and local also there is no self-defined picture file in the situation that, IM client is used the picture file (as the head portrait of microblog users) of acquiescence picture file as microblog users.
As can be seen from the above, by adopting different preserving types to preserve to dissimilar subscriber data, can more fully, reasonably utilize local internal memory and disk space, and can facilitate IM client in this locality, subscriber data to be managed, thereby bring better experience can to user A, and alleviate the communication pressure of microblogging server.
Below with reference to the management process to subscriber data in drawings and the specific embodiments explanation step 102 of the present invention.According to the embodiment of the present invention, strategy predetermined in step 102 can be different and different according to the type of subscriber data.In following examples, by the concrete management process of difference comment data and this subscriber data of two types of picture information, comprise inquiry, renewal and/or the deletion of subscriber data and/or notify subscriber data event to user A.
Fig. 3 is the management flow chart of user's written historical materials in microblogging system in the embodiment of the present invention.As shown in Figure 3, IM client, according to predetermined strategy, manages and comprises the written historical materials of preserving:
The subscriber data inquiry request of step 301:IM client user A.This subscriber data inquiry request is at least carried user identification code UIN or the user ID ID of subscriber data to be checked institute respective user, and subscriber data type is written historical materials.
Step 302:IM client is searched written historical materials.Particularly, IM client judges when subscriber data type to be checked is written historical materials, in local internal memory, searches written historical materials.
Step 303: when finding written historical materials, return to local written historical materials to user A; When not finding written historical materials, to user A, return to inquiry failed message.
In this step, when not finding written historical materials, also can not return to inquiry failed message, but execution step 305 and 306 is to pull the local written historical materials that there is no preservation, and be kept in internal memory, and return to user A the written historical materials pulling after IM client pulls the written historical materials of user A inquiry.
Or IM client is returned after inquiry failed message to user A, if receive that the subscriber data for this UIN or ID of user A pulls instruction, then performs step 305 and 306 to return to the written historical materials pulling to user A.
Step 304: when user A is used written historical materials, IM client triggers the renewal of this written historical materials.
In this step, user A is used written historical materials to refer generally to check certain user's the page.At user A, check like this certain User Page time, IM client trigger upgrade, thereby can guarantee that user A checks up-to-date subscriber data, avoids unnecessary renewal.
In this step, can be also that user A manually upgrades written historical materials.But, if user A manually upgrades written historical materials too continually, can increase the communication pressure of microblogging server.Therefore, can a frequency limitation of manually upgrading be set at this, weekly or biweekly etc.
Step 305:IM client sends subscriber data to microblogging server and pulls request.
In this step, IM client judges whether written historical materials to be updated this time upgraded during login IM client at user A; If upgraded, do not send subscriber data and pull request, if not yet upgraded, send subscriber data and pull request to pull this written historical materials.
Particularly, can stamp label for the written historical materials upgrading, thereby can judge which which written historical materials upgraded and also do not upgrade according to label.
Step 306: microblogging server returns to response to IM client, wherein carries the written historical materials of request.
Step 307:IM client is upgraded processing.Specifically, judge that whether the local written historical materials of preserving is consistent with the written historical materials pulling, if consistent, do not preserve the written historical materials pulling; Otherwise replace local written historical materials with the written historical materials pulling, and perform step 308.
Step 308:IM client is to more new events of user A notice written historical materials.Particularly, written historical materials is upgraded to event notice to interface, by the user oriented A of boundary, represent the written historical materials after renewal.
In above-mentioned steps 301-308, can only carry out query script (step 301-303), and not carry out renewal process (step 304-307).The notification procedure of step 308 also can not carried out, but again the written historical materials after upgrading is returned to user A when user A inquires about.
Above-mentioned management process can also comprise the written historical materials of deleting in local internal memory.At user A, exit after IM client, delete the subscriber data that internal memory is preserved.
By above management process, can be found out, according to the local subscriber data of preserving of predetermined tactical management, such as when user A inquires about other users' subscriber data, IM client is first in local internal memory inquiry, rather than directly to microblogging server request subscriber data, therefore the needed subscriber data of invoke user A more quickly, and can represent rapidly subscriber data.In addition, according to the local subscriber data of preserving of predetermined tactical management, such as controlling update times, during user A once logins, user A user just upgrades once during data, and the subscriber data having upgraded during this time login no longer upgrades, and can avoid repeating to pull subscriber data, reduced and the interaction times of microblogging server, reduced the communication pressure of microblogging server.
Fig. 4 is the management flow chart of user's picture information in microblogging system in the embodiment of the present invention.As shown in Figure 4, IM client, according to predetermined strategy, manages and comprises the picture information of preserving:
The subscriber data inquiry request of step 401:IM client user A.This subscriber data inquiry request is at least carried user identification code UIN or the user ID ID of subscriber data to be checked institute respective user, and subscriber data type is picture information.
Step 402:IM client is searched picture information.Particularly, IM client judges when subscriber data type to be checked is picture information, searches picture information in local disk.
Particularly, because picture information adopts different preserving types to preserve according to different scenes, for scene 1) and 2) in picture information, generally be kept under the particular category of local disk and for scene 3) in picture information, generally preserve picture file under local temp directory and the URL information of preserving picture file at local internal memory.Therefore, IM client can selected query context according to different scenes, thereby can save query time.
Step 403: when finding picture information, IM client is returned to local picture information to user A; When not finding picture information, to user A, return to inquiry failed message.When returning to picture information, can to user A, represent the picture file in picture information by IM client, such as the head portrait of microblog users.
Similar with step 303, when not finding picture information, also can not return to inquiry failed message, but execution step 406 and 407 is to pull the local picture information that there is no preservation, and according to different scenes, preserve pull the picture word data of user A inquiry in IM client after, and return to user A the picture information pulling.
Or IM client is returned after inquiry failed message to user A, if receive that the subscriber data for this UIN or ID of user A pulls instruction, then performs step 406 and 407 to return to the picture information pulling to user A.
Or IM client represents the picture file of acquiescence when returning to inquiry failed message.
Step 404: upgrade triggering.
In this step, user A can manually upgrade triggering; Also can according to predetermined update condition, upgrade triggering by IM client.The embodiment of the present invention illustrates to upgrade to trigger as example according to predetermined update condition by IM client.
Step 405:IM client, according to the scene of update condition, judges whether to pull the URL information of picture file.If need, perform step 406; Otherwise finish this renewal process.
In this step, the scene of update request can be three kinds of above-mentioned scenes, 1) for demonstration in enormous quantities and/or frequently use the renewal of picture file; 2) to the single renewal of checking picture file; 3) to may only needing to show the renewal of picture file in enormous quantities once during login.
According to the embodiment of the present invention, under different scenes, adopt different more new logics.Particularly, the 1st) to plant under scene, IM client of the every login of user A is upgraded a picture information; The 2nd) under scene, as long as user checks certain picture file, upgrade this picture file, adopt the logic of forcing to upgrade picture information; The 3rd) plant under scene, pull a collection of picture information (as the head portrait of a collection of microblog users).
Therefore in this step, first IM client needs to judge that picture information to be updated belongs to the update condition of which kind of scene.If belong to the 1st) plant scene, due to the mode of a picture information of an IM client renewal of the every login of user A under this scene, therefore first IM client judges whether picture information this time upgraded during login at user A.If upgraded once, determine the URL information that does not need to pull picture file; Otherwise, determine the URL information that need to pull picture file.If belong to the 2nd) and 3) plant scene, determine the URL information that need to pull picture file.
Step 406:IM client sends subscriber data to microblogging server and pulls request for pulling picture information.
Step 407: microblogging server receives that subscriber data pulls request and determines that the subscriber data pulling comprises picture information, returns to response to IM client, wherein carries the URL information of picture file.
The URL information that 408:IM client comparison microblogging server returns and local URL information of preserving.If the URL information that microblogging server returns is inconsistent with local URL information of preserving, perform step 409; Otherwise, do not revise local URL information, finish this management process.
Step 409:IM client is revised as by local URL information the URL information that microblogging server returns, and to image Business Information and IT Solution Mgmt Dep, asks download pictures file according to the URL information of returning.
In the present embodiment, the head portrait that picture information is microblog users, and head portrait is divided into self-defined head portrait, system head portrait and acquiescence head portrait.When IM client pulls head portrait failure and there is no local self-defined head portrait, IM client shows acquiescence head portrait.
The URL form of head portrait is: http://Domain/key.Wherein, Domain is domain name, and key is picture identification.The information such as user identification code UIN and timestamp for self-defined head portrait, have also been comprised, and for system head portrait, such as Mytip head portrait etc., containing UIN information.At server end, the key of the self-defined head portrait of different user is different, and the identical Mytip of different user or the key of system head portrait are identical.
IM client is when URL information that relatively microblogging server returns and local URL information of preserving, and whether main judgement key wherein changes.If changed, prepare to download head portrait file to the request of image Business Information and IT Solution Mgmt Dep.But before downloading head portrait file, IM client judges the local head portrait corresponding with this URL information (it doesn't matter for judgement now and UIN) of whether having preserved; If do not preserved, download this head portrait file, otherwise no longer download.For the URL information of different UIN, if key is identical and there is this head portrait file this locality, no longer download this head portrait.In URL information for identical UIN, if the head portrait file that key does not become and local this URL information is corresponding exists, do not download head portrait file; And if key does not become but local header as file corruption or loss, download head portrait file.
Head portrait conventional in client is of a size of: 40*40 and 20*20, so can add after URL that these two kinds of sizes download this two kinds of head portraits, i.e. http://Domain/key/20 and http://Domain/key/40 while downloading.
When downloading head portrait, can adopt HttpP2PDownload assembly.
Step 410: image Business Information and IT Solution Mgmt Dep returns to new picture file to IM client.
Step 411:IM client is preserved the URL information of returning and new picture file according to different scenes.
This step can be preserved picture information, i.e. URL information and the picture file of picture file according to the preserving type of describing above.Such as for the 1st) plant scene, IM client is preserved URL information and the picture file of picture file at local disk.For the 2nd) plant scene, IM client is preserved URL information and the picture file of picture file after checking picture file at local disk.For the 3rd) plant scene, IM client is stored in internal memory by URL information, and preserves picture file temporarily, and after user A exits IM client, removes the interim picture file of preserving.Preserving type difference to picture information under different scenes, can manage picture information flexibly and easily at IM client terminal local, thereby improves the efficiency of user information management.
Step 412:IM client is to more new events of user A notice picture information.Particularly, for the 1st) and 2) plant scene, after picture information changes, notice picture file change events; For the 3rd) plant scene, notify picture to download event.
Further, this management process can also comprise the picture information of deleting local preservation.Such as deleting the 3rd) picture information under Scene, or delete certain or some picture informations according to the instruction of user A.Thereby can more reasonably utilize memory space, and then improve the management speed of client to picture information.
By above management process, can be found out, when user A inquires about other users' subscriber data, IM client is first inquired about at local disk, rather than directly to microblogging server request subscriber data, therefore the needed subscriber data of invoke user A more quickly, and can represent rapidly subscriber data.Especially for the larger picture information that takes up room, according to the present embodiment, can greatly improve that to represent speed fast.In addition, according to predetermined strategy, subscriber data is managed, when especially picture information is managed, different scenes is used different strategies, such as selecting to upgrade and preserving type according to different scenes, divide and rule, fully, reasonably utilized the preservation resource of client, the flexibility that has improved user information management.And the number of times that utilizes predetermined policy control picture information to upgrade, has reduced the interaction times of client and server, has lowered the communication pressure of server.
Although described respectively the management process of written historical materials and this subscriber data of two types of picture information in the management process of Fig. 3 and Fig. 4, but in actual management process, user A can inquire about written historical materials and picture in a subscriber data inquiry request simultaneously, in this case, the processing of IM client is also similar with Fig. 3 and Fig. 4, and just microblogging server will carry the subscriber data of two types in the response of returning to IM client simultaneously.
The embodiment of the present invention also provides the management devices of subscriber data in the system based on universal relation chain model, and this system is take client as carrier, and user enters this system by client, and comprises server, is used to system user that service is provided.This management devices can be positioned at client inside, can be also connected with client one independently management devices, and be connected and manage for the subscriber data to system with system server.
Fig. 5 is according to the structure chart of the management devices of subscriber data in the system based on universal relation chain model of the embodiment of the present invention.As described in Figure 5, described management devices is positioned at the client-side of system, comprising:
Subscriber data can be the subscriber data of user A, can also comprise the user's of the interested or frequent concern of user A data.
In this enforcement, the microblogging system take IM client as carrier illustrates the management devices of subscriber data in the system based on universal relation chain model as example.According to the embodiment of the present invention, the type of subscriber data at least comprises written historical materials and picture information, and in microblogging system, picture information can be user's head portrait.Particularly, preserving module 502 can adopt different preserving types to preserve to written historical materials and picture information, and administration module 503 can comprise inquiry, the renewal of subscriber data and/or delete subscriber data and/or notify subscriber data event to user A the management of the subscriber data of preserving.
According to the embodiment of the present invention, pull module 501 and from the server of system, pull subscriber data and above-mentioned steps 201-203 is similar according to the demand of user A, do not repeat them here.
According to the embodiment of the present invention, preserve module 502 and comprise:
Type judges submodule, for judging the type of subscriber data; With
Preserve submodule, for the type of subscriber data that judge that according to type submodule judges, select corresponding preserving type to preserve and pull the subscriber data that module 501 pulls.Particularly, when type judges that submodule judges that the type of subscriber data is written historical materials, preserve submodule and select to be stored in the preserving type of local internal memory, and preserve written historical materials according to the preserving type of selecting; When type judges that submodule judges that the type of the subscriber data pulling is picture information, preserve submodule and select different preserving types according to different scenes, and preserve according to the preserving type of selecting the picture information pulling.Wherein, according to different scenes select different preserving types and above-mentioned steps 204 similar, do not repeat them here.
According to the embodiment of the present invention, because the storage demand of written historical materials and picture information there are differences, adopt two preservation submodules can reduce the coupling of two class subscriber datas, therefore preserve submodule and can also comprise that written historical materials is preserved submodule and picture information is preserved submodule.
In like manner, according to the embodiment of the present invention, the management of basic document and picture information also there are differences, in order to reduce the coupling of two class subscriber datas, predetermined strategy in administration module 503 is divided into based on the tactful of written historical materials and the strategy based on picture information, can comprise:
Written historical materials management submodule, for managing according to predetermined strategy the written historical materials of subscriber data; With
Picture data management submodule, for managing according to predetermined strategy the picture information of subscriber data.
Further, administration module 503 also comprises judgement submodule, in the information of judgement from user A or server, subscriber data comprises written historical materials or picture information, and the information that relates to written historical materials is issued to written historical materials management submodule manage, the information that relates to picture information is issued to picture data management submodule and manage.
According to the embodiment of the present invention, written historical materials management submodule comprises: written historical materials inquiry submodule, for receiving the subscriber data inquiry request about written historical materials that judges submodule, in client terminal local internal memory, search the written historical materials in subscriber data to be checked; When finding described written historical materials, in client, to user A, return to described written historical materials; When not finding described written historical materials, client is returned to inquiry failed message to user A.
According to the embodiment of the present invention, described picture data management submodule comprises: picture information inquiry submodule, for receiving the subscriber data inquiry request about picture information that judges submodule, in local disk, search described picture information; When finding after described picture information, client represents described picture information to user A; When not finding described picture information, client is returned to inquiry failed message to user A.
According to the embodiment of the present invention, written historical materials management submodule also comprises: written historical materials upgrades submodule, when receiving the subscriber data inquiry request about written historical materials whenever text query submodule, upgrades one time written historical materials.Picture data management submodule also comprises: picture information upgrades submodule, for according to different scene update picture informations.
According to the embodiment of the present invention, administration module 503 also comprises: pull triggering submodule, for when user A is used written historical materials, triggering pulls module 501 and pulls written historical materials from server, and the written historical materials pulling is issued to written historical materials and upgrade submodule.Wherein, whether written historical materials renewal submodule is also consistent with the written historical materials newly pulling for judging the written historical materials of client terminal local preservation; If consistent, do not preserve the written historical materials newly pulling; Otherwise notice is preserved the local written historical materials of preserving of written historical materials replacement that module 502 use newly pull.
Described picture information upgrades submodule and comprises:
Scene judges submodule, for judging which kind of scene picture information to be updated belongs to;
First upgrades submodule, when belonging to demonstration in enormous quantities and/or the frequent scene of using when picture information to be updated, and once described picture information of renewal when user A login client;
Second upgrades submodule, and when belonging to the single picture information of checking of user A when picture information to be updated, user A checks once once described picture information of described single picture information renewal;
The 3rd upgrades submodule, when only needing to show picture information in enormous quantities once when picture information to be updated belongs to login during, pull described in notice and trigger submodule and pull module described in triggering and pull and describedly only need to show that the URL information of picture information once the URL information that basis pulls downloads corresponding picture file from server.
According to the embodiment of the present invention, pull trigger submodule also for: according to the first renewal submodule and/or second, upgrade the request of submodule, triggering pulls module and to the URL information of server request picture information to be updated and from server, receives the URL information of asking, and sends to the first renewal submodule and/or second to upgrade submodule the URL information of request by pulling module; First upgrades submodule and/or second upgrades submodule also for judging that whether asked URL information is identical with the URL information of client terminal local preservation; If different, according to asked URL information, download new picture file, and notice is preserved the URL information of module 502 preservation requests and new picture file.
According to the embodiment of the present invention, the 3rd upgrade submodule also for by interim the picture file of having downloaded preserve and by for URL information preserve internal memory, after user exits client, remove the picture file of interim preservation.
According to the embodiment of the present invention, administration module 503 also comprises notice submodule, for when local written historical materials changes, and more new events of notice written historical materials; When local picture information changes, more new events of notice picture information; When having downloaded while needing to show picture file once, notice has been downloaded event.
According to the embodiment of the present invention, administration module 503 also comprises deletion submodule, for according to user's request, deletes the local subscriber data of preserving.
Further, management devices also comprises codec, at server with pull between module 501, for the written historical materials to from server and picture information, carries out coding and decoding, to pulling module 501, sends to the data of server to carry out coding and decoding.
By above management devices, when user A inquires about other users' subscriber data, management devices can first be inquired about at IM client terminal local, rather than directly to microblogging server request subscriber data, therefore the needed subscriber data of invoke user A more quickly, and can represent rapidly subscriber data.Especially for the larger picture information that takes up room, the speed that represents of picture information is greatly improved.In addition, owing to utilizing predetermined strategy to manage subscriber data, such as the picture information under different scenes is used different renewals and preserving type, divide and rule, fully, reasonably utilize the preservation resource of client, given prominence to the flexibility of user information management.And, can control update times, thereby avoid repeating to pull, reduce and the interaction times of microblogging server, and then reduced the communication pressure of microblogging server.
Fig. 6 is the logical construction schematic diagram of management devices in Fig. 5.As shown in Figure 6, this management devices mainly comprises written historical materials manager and head portrait data management device.
Particularly, in implementation procedure, written historical materials manager can be defined as CTXWBlogContactInfoMgr, it realizes written historical materials manager external interface ITXWBlogContactInfoMgr, written historical materials is managed, comprise pulling FetchlistWBlogInfo (), upgrade UpdateListWBLogInfo (), inquiring about QueryWBLogInfo () for user of written historical materials, and written historical materials is notified user while upgrading.
Preferably, management devices also comprises data updating event interface ITXWBlogContactInfoEvtExt, when the written historical materials of CTXWBlogContactInfoMgr inside upgrades, call this interface and notify user, and user can carry out registered letter data updating event by this interface.
Preferably, management devices also comprise written historical materials more new events realize class CTXWBlogContactInfoEvtExt, for realizing written historical materials, upgrade event interface ITXWBlogContactInfoEvtExt.
In implementation procedure, head portrait manager can be defined as CWBlogCustomerHeadMgr, it realizes head portrait manager external interface ITXWBlogCustomHeadMgr, head portrait is managed, what comprise head portrait pulls FetchlistWBlogCustomHead (), upgrade and (comprising: head image information upgrades UpdateWBlogCustomHeadInfo (), head portrait list update UpdateListWBlogCustomHead (), head portrait forces to upgrade ForceUpdateWBlogCustomHead ()), for user, inquire about QueryCustomHead (), download head portrait file DownloadUserHeadImage (), and head portrait is notified user while upgrading.
Preferably, management devices also comprises that head portrait upgrades event interface ITXWBlogCustomHeadEvtExt, when head portrait manager CWBlogCustomerHeadMgr internal head picture upgrades, call this interface and notify user, and user can register more new events of head portrait by this interface.
Preferably, management devices also comprise head portrait more new events realize class CTXWBlogCustomHeadEvtExt, realize head portrait and upgrade event interface ITXWBlogCustomHeadEvtExt.
Preferably, management devices also comprises codec CCSWBlogContactInfoCodec, the Code And Decode when with microblogging server interaction data.Particularly, when CTXWBlogContactInfoMgr and CWBlogCustomerHeadMgr send data to microblogging server, the encoder calling in CCSWBlogContactInfoCodec is encoded the data of transmission by the requirement of microblogging server, when receiving the data that microblogging server returns, the decoder calling in CCSWBlogContactInfoCodec carries out Data Analysis.
The foregoing is only preferred embodiment of the present invention, not in order to limit the present invention, all any modifications of doing within the spirit and principles in the present invention, be equal to and replace and improvement etc., within all should being included in protection scope of the present invention.
Claims (28)
1. the management method of subscriber data in the system based on universal relation chain model, is characterized in that, described system is take client as carrier and comprise the server for service is provided to system user, said method comprising the steps of:
Be positioned at described client management devices inner or that be connected with described client pulls system from server subscriber data according to the user's of the described client of login demand, and adopting different preserving types to be stored in client terminal local dissimilar subscriber data, wherein said subscriber data at least comprises described user's data;
Described management devices, according to predetermined strategy, manages the subscriber data of preserving; Described subscriber data comprises written historical materials and picture information; Wherein, for demonstration in enormous quantities and/or the frequent picture information using, whenever logining client, described user upgrades picture information one time; For the current single picture information of checking of user, whenever checking a picture information, described user upgrades once described picture information; During logining client for described user, only need to show picture information in enormous quantities once, when user asks described picture information, from server, pull the URL information of described picture information the URL information download pictures file that basis pulls.
2. the method for claim 1, is characterized in that, described subscriber data also comprises other users' data; Wherein written historical materials at least comprises user identification code UIN or user ID ID, and described picture information comprises URL information and the picture file of picture file.
3. method as claimed in claim 2, is characterized in that, the subscriber data that described management devices pulls system according to this client user's of login demand from the server of system comprises:
Management devices receives that described user's subscriber data pulls after instruction, sends subscriber data pull request to server, and this subscriber data pulls request and carries the UIN corresponding with subscriber data or ID;
Management devices reception server pulls according to this subscriber data the response that UIN in request or ID return to management devices, carries the subscriber data corresponding with described UIN or ID in this response.
4. method as claimed in claim 3, is characterized in that, also comprises: when the subscriber data type of carrying in response is written historical materials, described management devices directly extracts written historical materials from described response;
When the subscriber data that carries in response comprises the unified resource location URL information of picture file, management devices according to described URL information from server or image Business Information and IT Solution Mgmt Dep download pictures file.
5. method as claimed in claim 2, is characterized in that, described management devices manages and comprises local subscriber data: according to predetermined strategy, inquire about, upgrade and/or delete described subscriber data, and/or to described user notification subscriber data event.
6. method as claimed in claim 5, is characterized in that, describedly the subscriber data pulling is stored in to client terminal local comprises:
Management devices is kept at written historical materials in client terminal local internal memory; And/or
According to different scenes, preserve described picture information.
7. method as claimed in claim 6, is characterized in that, described management devices comprises according to the subscriber data of predetermined policy lookup this locality:
Management devices receives user's subscriber data inquiry request, and this subscriber data inquiry request is at least carried user identification code UIN or the user ID ID of subscriber data to be checked institute respective user;
Management devices judges whether described subscriber data to be checked comprises written historical materials and/or picture information;
When described subscriber data only includes written historical materials, management devices is searched described written historical materials in client terminal local internal memory; When finding after described written historical materials, to user, return to described written historical materials; When not finding described written historical materials, to user, return to inquiry failed message;
When described subscriber data only includes picture information, management devices according to described picture information the preserving type under different scenes search described picture information; When finding after described picture information, to user, return to described picture information; When not finding described picture information, to user, return to inquiry failed message;
When described subscriber data comprises written historical materials and picture information, management devices in client terminal local internal memory, search described written historical materials and according to described picture information the preserving type under different scenes search described picture information; When finding described written historical materials and picture information, to user, return to described written historical materials and picture information; When not finding described written historical materials and picture information, to user, return to inquiry failed message.
8. method as claimed in claim 7, is characterized in that, also comprises:
When management devices returns after inquiry failed message, management devices pulls instruction according to described user's subscriber data and pulls subscriber data to be checked from server;
If described subscriber data is picture information, at management devices, return after inquiry failed message, judge whether client terminal local has described picture information, if do not had, to user, represent the acquiescence picture file of client.
9. method as claimed in claim 6, is characterized in that, subscriber data comprises described in the predetermined policy update of described basis:
When described subscriber data comprises written historical materials,, when described user uses described written historical materials, upgrade once described written historical materials, and preserve the written historical materials upgrading;
When described subscriber data comprises picture information, according to picture information described in different scene updates.
10. method as claimed in claim 9, is characterized in that, described when user uses described written historical materials upgrade once described written historical materials comprise:
Management devices pulls the user's corresponding with described UIN or ID written historical materials from server, and judges that whether the written historical materials of local internal memory preservation is consistent with the written historical materials pulling from server;
If inconsistent, with the written historical materials pulling, replace the local written historical materials of preserving.
11. the method for claim 1, is characterized in that, described for demonstration in enormous quantities and/or the frequent picture information using, and whenever user logins client, upgrade a picture information and comprise:
Management devices judges that whether the rear described demonstration in enormous quantities of this time login of user and/or the frequent picture information using upgraded, if upgraded once, no longer upgraded; Otherwise, upgrade the picture information not upgrading after this time login.
12. methods as described in claim 1 or 11, is characterized in that, described renewal once described picture information comprises:
Management devices is to the URL information of server request picture information to be updated, and the URL information of asking from server reception;
Management devices judges that whether the URL information of request is identical with local URL information of preserving;
If not identical, according to asked URL information, download new picture file, and preserve the URL information of request and new picture file.
13. methods as claimed in claim 12, is characterized in that, described URL information comprises domain name domain and picture identification key;
Described management devices judges the URL information and local whether identical comprising of URL information of preserving of request:
Whether the key that judges the URL information of asking is identical with the key of local URL information of preserving, if identical, these two URL information are identical, otherwise these two URL information differences.
14. methods as described in claim 6 or 9, is characterized in that, describedly according to different scenes, preserve described picture information and comprise:
For demonstration in enormous quantities and/or the frequent picture information using, URL information and picture file are kept under the particular category of local disk;
For the current single picture information of checking of user, URL information and picture file are kept under the particular category of local disk;
For only needing to show picture information once, URL information is kept in internal memory, and after having downloaded picture file according to URL information, the picture file of download is kept under the temp directory of local disk, and after exiting client, user removes the picture file of preserving.
15. methods as claimed in claim 5, is characterized in that, described notice subscriber data event comprises:
When described written historical materials changes, more new events of management devices notice written historical materials;
When described picture information changes, more new events of management devices notice picture information;
When having downloaded a need, show after picture file once, management devices notice has been downloaded event.
16. methods as claimed in claim 5, is characterized in that, the described subscriber data of described deletion comprises: according to user's request, delete the subscriber data of preserving.
17. methods as described in any one in claim 1-5, is characterized in that, the described system based on universal relation chain model is microblogging system, and described client is instant messaging IM client.
18. the management devices of subscriber data, is characterized in that in the system based on universal relation chain model, this system is take client as carrier and comprise the server that is used to system user that service is provided, and this management devices is positioned at the client-side of this system, comprising:
Pull module, for pulling subscriber data according to this client user's of login demand from the server of system;
Preserve module, for adopting different preserving types to preserve dissimilar subscriber data;
Administration module, for according to predetermined strategy, manages the subscriber data of preserving module preservation; Described subscriber data comprises written historical materials and picture information; Wherein, for demonstration in enormous quantities and/or the frequent picture information using, whenever logining client, described user upgrades picture information one time; For the current single picture information of checking of user, whenever checking a picture information, described user upgrades once described picture information; During logining client for described user, only need to show picture information in enormous quantities once, when user asks described picture information, from server, pull the URL information of described picture information the URL information download pictures file that basis pulls.
19. devices as claimed in claim 18, is characterized in that, described administration module comprises:
Written historical materials management submodule, for managing according to predetermined strategy the written historical materials of subscriber data; With
Picture data management submodule, for managing according to predetermined strategy the picture information of subscriber data.
20. devices as claimed in claim 19, it is characterized in that, described administration module also comprises judgement submodule, for judging the information from user or server, described subscriber data comprises written historical materials or picture information, and the information that relates to written historical materials is issued to written historical materials management submodule manage, the information that relates to picture information is issued to picture data management submodule and manage.
21. devices as claimed in claim 20, it is characterized in that, described written historical materials management submodule comprises: written historical materials inquiry submodule, for receiving the subscriber data inquiry request about written historical materials from described judgement submodule, in client terminal local internal memory, search the written historical materials in subscriber data to be checked; When finding described written historical materials, to user, return to described written historical materials; When not finding described written historical materials, to user, return to inquiry failed message;
Described picture data management submodule comprises: picture information inquiry submodule, for receiving the subscriber data inquiry request about picture information from described judgement submodule, for according to picture information the preserving type under different scenes search described picture information; When finding after described picture information, to user, return to described picture information; When not finding described picture information, to user, return to inquiry failed message.
22. devices as claimed in claim 21, is characterized in that, described written historical materials management submodule comprises: written historical materials upgrades submodule, for when user uses written historical materials, upgrades once described written historical materials;
Described picture data management submodule comprises: picture information upgrades submodule, for according to picture information described in different scene updates.
23. devices as claimed in claim 22, it is characterized in that, described administration module also comprises: pull triggering submodule, for when user uses described written historical materials, described in triggering, pull module and pull described written historical materials from server, and the written historical materials pulling is issued to described written historical materials and upgrade submodule;
Wherein, whether described written historical materials renewal submodule is also consistent with the written historical materials newly pulling for judging the written historical materials of client terminal local preservation; If inconsistent, notify the described preservation module written historical materials newly pulling to replace the local written historical materials of preserving.
24. devices as claimed in claim 18, it is characterized in that, described pull trigger submodule also for: according to the first renewal submodule and/or second, upgrade the request of submodule, described in triggering, pull module and to the URL information of server request picture information to be updated and from server, receive the URL information of asking, and send to the first renewal submodule and/or second to upgrade submodule the URL information of request by the described module that pulls;
Described first upgrades submodule and/or second upgrades submodule also for judging that whether asked URL information is identical with the URL information of client terminal local preservation; If different, according to asked URL information, download new picture file, and notice is preserved the URL information of module preservation request and new picture file;
The 3rd upgrades submodule also for the picture file of having downloaded is preserved temporarily, and after user exits client, removes the interim picture file of preserving.
25. devices as claimed in claim 24, is characterized in that, described preservation module is upgraded the notice of submodule according to described the first renewal submodule and/or second, the URL information of request and new picture file are saved in the particular category of local disk.
26. devices as claimed in claim 18, is characterized in that, described preservation module comprises: type judges submodule, for judging that the type of the subscriber data pulling is written historical materials or picture information;
Preserve submodule, for when type judges that submodule determines that subscriber data comprises written historical materials, select written historical materials to be stored in local internal memory; When type judges that submodule determines that subscriber data comprises picture information, the different scenes of selective basis adopt different preserving types to preserve picture information.
27. devices as claimed in claim 26, it is characterized in that, described preservation submodule also for: when belonging to demonstration in enormous quantities and/or the frequent scene of using wait the picture information of preserving or belonging to the single picture information of checking of user, described picture information is kept under the particular category of local disk;
While only needing to show picture information in enormous quantities once during picture information to be updated belongs to user to login client, preserve URL information in local internal memory, and picture file is stored in local disk temporary folder.
28. devices as claimed in claim 18, also comprise: notice submodule, and for when described written historical materials changes, more new events of notice written historical materials; When described picture information changes, more new events of notice picture information; When only needing to show picture file once described in having downloaded, notice has been downloaded event.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010276127.8A CN102387026B (en) | 2010-09-01 | 2010-09-01 | Management method and device for user data in system based on universal relation link model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010276127.8A CN102387026B (en) | 2010-09-01 | 2010-09-01 | Management method and device for user data in system based on universal relation link model |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102387026A CN102387026A (en) | 2012-03-21 |
| CN102387026B true CN102387026B (en) | 2014-04-16 |
Family
ID=45826030
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010276127.8A Active CN102387026B (en) | 2010-09-01 | 2010-09-01 | Management method and device for user data in system based on universal relation link model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102387026B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106789552B (en) * | 2016-11-24 | 2020-09-29 | 青岛海信移动通信技术股份有限公司 | Friend head portrait updating method and device of social account |
| CN112118477B (en) * | 2020-09-21 | 2023-05-09 | 北京达佳互联信息技术有限公司 | Virtual gift display method, device, equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101075939A (en) * | 2006-09-28 | 2007-11-21 | 腾讯科技（深圳）有限公司 | Method and system for acquiring user data at instant telecommunication customer end |
| CN101083631A (en) * | 2006-05-31 | 2007-12-05 | 阿里巴巴公司 | Method for establishing contact list and managing contact information in instant communication |
| CN101764868A (en) * | 2009-12-16 | 2010-06-30 | 惠州Tcl移动通信有限公司 | Method for adding map picture in address list and mobile communication terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8392545B2 (en) * | 2004-07-01 | 2013-03-05 | Nokia Corporation | Device management system |
-
2010
- 2010-09-01 CN CN201010276127.8A patent/CN102387026B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101083631A (en) * | 2006-05-31 | 2007-12-05 | 阿里巴巴公司 | Method for establishing contact list and managing contact information in instant communication |
| CN101075939A (en) * | 2006-09-28 | 2007-11-21 | 腾讯科技（深圳）有限公司 | Method and system for acquiring user data at instant telecommunication customer end |
| CN101764868A (en) * | 2009-12-16 | 2010-06-30 | 惠州Tcl移动通信有限公司 | Method for adding map picture in address list and mobile communication terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102387026A (en) | 2012-03-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8224886B2 (en) | System for an open architecture deployment platform with centralized synchronization | |
| EP2282272B1 (en) | Method, system and device for presenting advertisement | |
| CN101448247B (en) | Updating data on a remote device | |
| US20130159842A1 (en) | Display placeholders for rich media content | |
| US9456048B2 (en) | System, method, and computer program product for server side processing in a mobile device environment | |
| CN101365118B (en) | Video monitoring system based on computer network | |
| CN101365120B (en) | Data centralized management method for network video monitoring system | |
| CN102664909A (en) | Re-establishing push notification channels via user identifiers | |
| US20040199550A1 (en) | Information management technique | |
| CN102291243A (en) | Service processing server, system and method | |
| CN102984278A (en) | System and method for realizing browser data synchronization | |
| CN111177613A (en) | Page processing method, device, equipment and storage medium | |
| CN101388891A (en) | Apparatus and method for managing presence information of a presentity | |
| CN107438084A (en) | Multi-client data synchronization method and apparatus | |
| CN115278339B (en) | Mixed broadcast processing method and system | |
| CN105677536A (en) | Implementing method for task messages and task system for implementing task messages | |
| CN112231055A (en) | Mirror image management method and device | |
| CN103716230A (en) | Message sending method, device and server | |
| EP1872256B1 (en) | System and method of waste management | |
| CN103024049B (en) | Realize the system that browser data is synchronous | |
| CN101296201B (en) | Network information sharing method, system and instant communication device | |
| US20050071754A1 (en) | Pushing information to distributed display screens | |
| CN102387026B (en) | Management method and device for user data in system based on universal relation link model | |
| CN109213955A (en) | Data processing method and relevant device | |
| CN111241438B (en) | Cartoon picture display method, cartoon picture display device, cartoon picture display computer readable storage medium and cartoon picture display computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20180911 Address after: 100090 Beijing Haidian District Zhichun Road 49 No. 3 West 309 Patentee after: Tencent cloud computing (Beijing) limited liability company Address before: 518044 East 403 room, Sai Ge science and Technology Park, Futian District Zhenxing Road, Shenzhen, Guangdong, China, 2 Patentee before: Tencent Technology (Shenzhen) Co., Ltd. |
|
| TR01 | Transfer of patent right |