CN105187294A - Management method for user state - Google Patents
Management method for user state Download PDFInfo
- Publication number
- CN105187294A CN105187294A CN201510474613.3A CN201510474613A CN105187294A CN 105187294 A CN105187294 A CN 105187294A CN 201510474613 A CN201510474613 A CN 201510474613A CN 105187294 A CN105187294 A CN 105187294A
- Authority
- CN
- China
- Prior art keywords
- client
- list
- concern
- propelling movement
- management method
- 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.)
- Pending
Links
Abstract
The invention discloses a management method for a user state. The management method comprises the following steps of adding a second client to a watchlist by a first client, and adding the first client to a push list of the second client; when the state of the second client is changed, pushing the own latest state information to the first client according to the push list; deleting the concerned second client by the first client in the watchlist, and deleting the first client by the second client in the push list. The management method for the user state provided by the invention has the following beneficial effects that the states of a large amount of users are managed efficiently; the real-time, high efficiency and accuracy of state change notification are improved; each access terminal can customize state schemes as required and the effect that the terminals are configurable can be achieved.
Description
Technical field
The present invention relates to instant messaging technical field, more particularly, relate to a kind of management method of User Status.
Background technology
State is absolutely necessary focus in current IM (instant messaging), is also the feature that IM is different from other medium of communications (cell phone address book, microblogging, blog).In existing IM technology, condition managing mainly adopts following two kinds of situations:
1, full dose is pushed to the client (as Fig. 1) of all online users in relation chain, and it is fewer that this scheme is applicable to personnel in relation chain, is indifferent in the application scenarios of flow.But mobile terminal is pressed to the application of flow charging, along with the user of relation chain increases, flow can constantly increase; And the status change data that major part receives may be oneself and unconcerned, such as seldom participate in the user under the uncorrelated department of milli in the member in the group linked up, company, also these status change data of passive reception, so, both waste the flow of client, waste the process resource of server.
2, client timing pulls the state (as Fig. 2) of designated user as required, this scheme can pull the state of designated user by the various timing as required that accesses terminal, although the program solves the problems referred to above, but also bring other problem: the frequency pulled is too fast, waste resource and flow, User Status not change when major part pulls; Frequency is too slow, and the state change of personnel does not upgrade in time.
Summary of the invention
The technical problem to be solved in the present invention is, for the defect of the process resource of the flow and server of wasting client in prior art, provides a kind of management method of User Status.
The technical solution adopted for the present invention to solve the technical problems is:
Construct a kind of management method of User Status, comprising:
First client adds the second client to paying close attention in list, described first client is added in the propelling movement list of described second client simultaneously;
The latest state information of self is pushed to described first client according to described propelling movement list by described second client when state changes;
Described first client deletes the second client paid close attention in described concern list, and described second client deletes described first client in described propelling movement list simultaneously.
In management method of the present invention, described first client adds the second client to paying close attention in list, and by described first client, the step be added in the propelling movement list of described second client comprises described second client simultaneously:
Described first client-access service access layer to add the concern user ID corresponding with described second client extremely in described concern list, and by described concern list storage in data storage layer;
Described in described first client-access, service access layer is added in described propelling movement list with the device id and device type that add self, and by described propelling movement list storage to described data storage layer.
In management method of the present invention, described concern list storage to add in the concern user ID corresponding with described second client to described concern list, and comprises to the step in data storage layer by described first client-access service access layer:
Described first client is paid close attention to the described service access layer transmission interpolation corresponding with described second client and is asked;
Described interpolation is paid close attention to request forward to described data storage layer by described service access layer;
Described data storage layer adds in the concern user ID corresponding with described second client to described concern list;
Described data storage layer returns event memory according to described concern list to described service access layer;
Request is paid close attention in the interpolation that described service access layer responds described client according to described event memory.
In management method of the present invention, the step that the latest state information of self to be pushed to described first client according to described propelling movement list by described second client when state changes comprises:
Service access layer described in described second client-access changes request with transmission state and revises the log-on message of self.
Described second client obtains the propelling movement list of self in data storage layer, and the latest state information of self is pushed to described first client in described propelling movement list.
In management method of the present invention, described first client deletes the second client paid close attention in described concern list, and the step that simultaneously described second client deletes described first client in described propelling movement list comprises:
Described first client-access service access layer to delete the concern user ID corresponding with described second client in described concern list, and by described concern list storage in data storage layer;
The device id of described first client and device type are deleted by described second client in the propelling movement list of self, and by described propelling movement list storage to described data storage layer.
In management method of the present invention, described concern list storage to delete the concern user ID corresponding with described second client in described concern list, and comprises to the step in data storage layer by described first client-access service access layer:
Described first client is paid close attention to the described service access layer transmission deletion corresponding with described second client and is asked;
Described deletion is paid close attention to request forward to described data storage layer by described service access layer;
Described data storage layer is deleted the concern user ID corresponding with described second client and is notified that described second client revises the propelling movement list of himself in described concern list;
Described data storage layer returns event memory according to described propelling movement list to described service access layer;
Request is paid close attention in the deletion that described service access layer responds described client according to described event memory.
In management method of the present invention, in described management method:
The storage organization of described current state is: stored as one-level key assignments by login user ID, the device id of described client stores as secondary key assignments.
In management method of the present invention, in described management method:
The storage organization of described concern list is: stored as one-level key assignments by login user ID, the device id of described client stores as secondary key assignments.
In management method of the present invention, in described management method:
The storage organization of described propelling movement list is: stored as key assignments by login user ID.
The management method of above-mentioned disclosed a kind of User Status has following beneficial effect: the state managing mass users efficiently; Improve the real-time of state change notification, high efficiency and accuracy; Respectively accessing terminal can on-demand customization state schedule, reaches the configurable effect of terminal.
Accompanying drawing explanation
Fig. 1 is that the full dose of prior art pushes state schedule schematic diagram;
Fig. 2 be prior art pull state schedule schematic diagram as required;
Fig. 3 is the flow chart of the management method of a kind of User Status provided by the invention;
Fig. 4 is the flow chart adding concern provided by the invention;
Fig. 5 is the flow chart of change state provided by the invention;
Fig. 6 is the flow chart deleting concern provided by the invention;
Fig. 7 is the storage organization schematic diagram of current state provided by the invention;
Fig. 8 is the storage organization schematic diagram of concern list provided by the invention;
Fig. 9 is the storage organization schematic diagram of propelling movement list provided by the invention.
Embodiment
In order to make object of the present invention, technical scheme and advantage clearly understand, below in conjunction with drawings and Examples, the present invention is further elaborated.Should be appreciated that specific embodiment described herein only in order to explain the present invention, be not intended to limit the present invention.
The invention provides a kind of management method of User Status, its object is to, a kind of efficient, manageable, the state management scheme that can subscribe to is provided, to reach the presence management supporting mass users; The real-time informing that state changes; Difference accesses terminal and can subscribe to the state of associated user as required, the demand of the unified process of service end.The method is for solving the condition managing of magnanimity online user in IM system: both can real-time and efficiently by the client of the status change notification of self to the user of concern oneself; The demand of different access device subscriber state as required can be reached again, thus make service end accomplish unified efficient process.
The architecture design scheme that the present invention adopts service access layer to be separated with data storage layer.At service access floor, respectively different business logic processing is carried out by function number to the service request of user, and forward user state, pay close attention to list, push list to data storage layer; The request of data of data storage layer routine processes service access layer program, stores the state of user, pays close attention to list, pushes the data such as list, managing internal memory data, and the fail safe ensureing data.
Be the flow chart of the management method of a kind of User Status provided by the invention see Fig. 3, Fig. 3, the management method of this kind of User Status comprises:
S1, the first client add the second client to paying close attention in list, described first client are added in the propelling movement list of described second client simultaneously; This step S1 comprises following sub-step:
S11, described first client-access service access layer to add the concern user ID corresponding with described second client extremely in described concern list, and by described concern list storage in data storage layer; The user ID being about to pay close attention to is added in the concern list of oneself, is forwarded to data storage layer and stores.Participating in Fig. 4, Fig. 4 is the flow chart adding concern provided by the invention; This step S11 comprises following sub-step:
S111, described first client are paid close attention to the described service access layer transmission interpolation corresponding with described second client and are asked;
Described interpolation is paid close attention to request forward to described data storage layer by S112, described service access layer;
S113, described data storage layer add in the concern user ID corresponding with described second client to described concern list;
S114, described data storage layer return event memory according to described concern list to described service access layer;
Request is paid close attention in the interpolation that S115, described service access layer respond described client according to described event memory.
Described in S12, described first client-access, service access layer is added in described propelling movement list with the device id and device type that add self, and by described propelling movement list storage to described data storage layer.Be added in the propelling movement list paying close attention to user by self login user ID and device type, be forwarded to data storage layer and store.This step and step S11 can synchronously perform also can asynchronous execution.
The latest state information of self is pushed to described first client according to described propelling movement list by S2, described second client when state changes; This step S2 comprises following sub-step:
Service access layer described in S21, described second client-access changes request with transmission state and revises the log-on message of self; See the flow chart that Fig. 5, Fig. 5 are change state provided by the invention.S22, described second client obtain the propelling movement list of self in data storage layer, and the latest state information of self are pushed to described first client in described propelling movement list.The login user ID of self and device type are deleted from the propelling movement list paying close attention to user, is forwarded to data storage layer and stores.This step and step S11 can synchronously perform also can asynchronous execution.
S3, described first client delete the second client paid close attention in described concern list, and described second client deletes described first client in described propelling movement list simultaneously.Namely the user ID will deleted is deleted from the concern list of oneself, and is forwarded to data storage layer and stores.See the flow chart that Fig. 6, Fig. 6 are deletion concern provided by the invention; This step S3 comprises following sub-step:
S31, described first client-access service access layer to delete the concern user ID corresponding with described second client in described concern list, and by described concern list storage in data storage layer.Described step S31 comprises following sub-step:
S311, described first client are paid close attention to the described service access layer transmission deletion corresponding with described second client and are asked;
Described deletion is paid close attention to request forward to described data storage layer by S312, described service access layer;
S313, described data storage layer are deleted the concern user ID corresponding with described second client and are notified that described second client revises the propelling movement list of himself in described concern list; Namely step S32 can be performed after step S313.
S314, described data storage layer return event memory according to described propelling movement list to described service access layer;
Request is paid close attention in the deletion that S315, described service access layer respond described client according to described event memory.
The device id of described first client and device type are deleted by S32, described second client in the propelling movement list of self, and by described propelling movement list storage to described data storage layer.
To sum up, to the request of service access layer, according to processing logic above, be distributed to corresponding data storage layer by certain rule, carry out data storage.The request of data of data storage layer routine processes service access layer program, store the state of user, pay close attention to list, push the data such as list, efficiently manage internal storage data, data store organisation is as follows:
See the storage organization schematic diagram that Fig. 7, Fig. 7 are current state provided by the invention.The storage organization of described current state is: stored as one-level key assignments by login user ID, the device id of described client stores as secondary key assignments.So, to revise and the state of inquiring about certain user can efficiently process.
See the storage organization schematic diagram that Fig. 8, Fig. 8 are concern list provided by the invention.The storage organization of described concern list is: stored as one-level key assignments by login user ID, the device id of described client stores as secondary key assignments.So, to revise and the state of inquiring about certain user can efficiently process.
See the storage organization schematic diagram that Fig. 9, Fig. 9 are propelling movement list provided by the invention.The storage organization of described propelling movement list is: stored as key assignments by login user ID.So, to revise and the state of inquiring about certain user can efficiently process.
By reference to the accompanying drawings embodiments of the invention are described above; but the present invention is not limited to above-mentioned embodiment; above-mentioned embodiment is only schematic; instead of it is restrictive; those of ordinary skill in the art is under enlightenment of the present invention; do not departing under the ambit that present inventive concept and claim protect, also can make a lot of form, these all belong within protection of the present invention.
Claims (9)
1. a management method for User Status, is characterized in that, comprising:
First client adds the second client to paying close attention in list, described first client is added in the propelling movement list of described second client simultaneously;
The latest state information of self is pushed to described first client according to described propelling movement list by described second client when state changes;
Described first client deletes the second client paid close attention in described concern list, and described second client deletes described first client in described propelling movement list simultaneously.
2. management method according to claim 1, it is characterized in that, described first client adds the second client to paying close attention in list, and by described first client, the step be added in the propelling movement list of described second client comprises described second client simultaneously:
Described first client-access service access layer to add the concern user ID corresponding with described second client extremely in described concern list, and by described concern list storage in data storage layer;
Described in described first client-access, service access layer is added in the propelling movement list of described second client with the device id and device type that add self, and by described propelling movement list storage to described data storage layer.
3. management method according to claim 2, it is characterized in that, described concern list storage to add in the concern user ID corresponding with described second client to described concern list, and comprises to the step in data storage layer by described first client-access service access layer:
Described first client is paid close attention to the described service access layer transmission interpolation corresponding with described second client and is asked;
Described interpolation is paid close attention to request forward to described data storage layer by described service access layer;
Described data storage layer adds in the concern user ID corresponding with described second client to described concern list;
Described data storage layer returns event memory according to described concern list to described service access layer;
Request is paid close attention in the interpolation that described service access layer responds described client according to described event memory.
4. management method according to claim 1, is characterized in that, the step that the latest state information of self to be pushed to described first client according to described propelling movement list by described second client when state changes comprises:
Service access layer described in described second client-access changes request with transmission state and revises the log-on message of self;
Described second client obtains the propelling movement list of self in data storage layer, and the latest state information of self is pushed to described first client in described propelling movement list.
5. management method according to claim 1, is characterized in that, described first client deletes the second client paid close attention in described concern list, and the step that simultaneously described second client deletes described first client in described propelling movement list comprises:
Described first client-access service access layer to delete the concern user ID corresponding with described second client in described concern list, and by described concern list storage in data storage layer;
The device id of described first client and device type are deleted by described second client in the propelling movement list of self, and by described propelling movement list storage to described data storage layer.
6. management method according to claim 5, it is characterized in that, described concern list storage to delete the concern user ID corresponding with described second client in described concern list, and comprises to the step in data storage layer by described first client-access service access layer:
Described first client is paid close attention to the described service access layer transmission deletion corresponding with described second client and is asked;
Described deletion is paid close attention to request forward to described data storage layer by described service access layer;
Described data storage layer is deleted the concern user ID corresponding with described second client and is notified that described second client revises the propelling movement list of himself in described concern list;
Described data storage layer returns event memory according to described propelling movement list to described service access layer;
Request is paid close attention in the deletion that described service access layer responds described client according to described event memory.
7. management method according to claim 6, is characterized in that, in described management method:
The storage organization of described current state is: stored as one-level key assignments by login user ID, the device id of described client stores as secondary key assignments.
8. management method according to claim 6, is characterized in that, in described management method:
The storage organization of described concern list is: stored as one-level key assignments by login user ID, the device id of described client stores as secondary key assignments.
9. management method according to claim 6, is characterized in that, in described management method:
The storage organization of described propelling movement list is: stored as key assignments by login user ID.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510474613.3A CN105187294A (en) | 2015-08-05 | 2015-08-05 | Management method for user state |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510474613.3A CN105187294A (en) | 2015-08-05 | 2015-08-05 | Management method for user state |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105187294A true CN105187294A (en) | 2015-12-23 |
Family
ID=54909146
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510474613.3A Pending CN105187294A (en) | 2015-08-05 | 2015-08-05 | Management method for user state |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105187294A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776079A (en) * | 2016-12-28 | 2017-05-31 | Tcl集团股份有限公司 | A kind of method and system for managing user data |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040059781A1 (en) * | 2002-09-19 | 2004-03-25 | Nortel Networks Limited | Dynamic presence indicators |
| US20070253340A1 (en) * | 2006-04-28 | 2007-11-01 | Lucent Technologies Inc. | Method and apparatus for selective presence notification |
| CN102484617A (en) * | 2009-06-30 | 2012-05-30 | 阿尔卡特朗讯公司 | Method and system for reducing the number of presence events within a network |
| CN103747014A (en) * | 2014-01-24 | 2014-04-23 | 腾讯科技（深圳）有限公司 | User state acquiring method and service agent server |
| CN103778490A (en) * | 2012-10-23 | 2014-05-07 | 金蝶软件（中国）有限公司 | Acquisition method of ERP service object dynamic information, device thereof and system thereof |
-
2015
- 2015-08-05 CN CN201510474613.3A patent/CN105187294A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040059781A1 (en) * | 2002-09-19 | 2004-03-25 | Nortel Networks Limited | Dynamic presence indicators |
| US20070253340A1 (en) * | 2006-04-28 | 2007-11-01 | Lucent Technologies Inc. | Method and apparatus for selective presence notification |
| CN102484617A (en) * | 2009-06-30 | 2012-05-30 | 阿尔卡特朗讯公司 | Method and system for reducing the number of presence events within a network |
| CN103778490A (en) * | 2012-10-23 | 2014-05-07 | 金蝶软件（中国）有限公司 | Acquisition method of ERP service object dynamic information, device thereof and system thereof |
| CN103747014A (en) * | 2014-01-24 | 2014-04-23 | 腾讯科技（深圳）有限公司 | User state acquiring method and service agent server |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776079A (en) * | 2016-12-28 | 2017-05-31 | Tcl集团股份有限公司 | A kind of method and system for managing user data |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109684358B (en) | Data query method and device | |
| CN102255935B (en) | Cloud service consuming method, cloud service intermediary and cloud system | |
| CA2707536C (en) | Processing of network content and services for mobile or fixed devices | |
| US8051057B2 (en) | Processing of network content and services for mobile or fixed devices | |
| KR102048211B1 (en) | Techniques for communicating notifications to subscribers | |
| CN104604189A (en) | Efficient presence distribution mechanism for a large enterprise | |
| US8838712B2 (en) | Processing of associated messages from plural social network services | |
| JP7032377B2 (en) | How to make notifications, devices and systems | |
| JP2009146455A5 (en) | ||
| WO2011109404A2 (en) | Automated communications system | |
| CN104113466A (en) | Harassing phone call identification method, client, server and system | |
| CN106470149A (en) | Message method and device | |
| WO2017016084A1 (en) | Alarm information notification method and apparatus, and alarm information filtering device | |
| US20190007359A1 (en) | Mail information management method and associated apparatus | |
| CN102299810A (en) | Method and system for notifying group change event | |
| CA2923896C (en) | Email webclient notification queuing | |
| US8948352B2 (en) | Multi-channel interactive message response system | |
| CN106095789A (en) | A kind of message subscribing managing device and method | |
| CN102904801A (en) | Message alert method and device | |
| CN108366098B (en) | Data interaction method and device for network nodes | |
| CN105704001A (en) | WeChat server message distribution method and WeChat server message distribution system | |
| CN102201931A (en) | Device management method and system and related apparatus | |
| KR101606319B1 (en) | Method of push messages management using database | |
| CN105187294A (en) | Management method for user state | |
| CN103368988B (en) | resource sharing method, system and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20151223 |