Source: http://www.google.com/patents/US7953811?dq=6289460
Timestamp: 2016-12-05 05:31:36
Document Index: 279832971

Matched Legal Cases: ['Application No. 2003', 'Application No. 2003', 'Application No. 2003', 'art 105', 'art 204', 'art 204']

Patent US7953811 - Presence system and information processing equipment, dynamic buddy list ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA presentity service client has a presentity that issues presence information to a presence service and a watcher which observes presence information for other presentities; a presence change rule holding part holds a presence change rule; and a presence calculating part changes the presence information...http://www.google.com/patents/US7953811?utm_source=gb-gplus-sharePatent US7953811 - Presence system and information processing equipment, dynamic buddy list generation method in presence system, and presence notification destination controlling method and its program for use with presence systemAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS7953811 B2Publication typeGrantApplication numberUS 12/361,919Publication dateMay 31, 2011Filing dateJan 29, 2009Priority dateJan 22, 2003Fee statusPaidAlso published asDE602004026131D1, EP1441486A2, EP1441486A3, EP1441486B1, EP1786172A2, EP1786172A3, EP1786172B1, EP1786173A2, EP1786173A3, EP1786173B1, US7844667, US8458272, US20040153506, US20090138566, US20110078271Publication number12361919, 361919, US 7953811 B2, US 7953811B2, US-B2-7953811, US7953811 B2, US7953811B2InventorsNaoko Ito, Masafumi WatanabeOriginal AssigneeNec CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (22), Non-Patent Citations (4), Referenced by (3), Classifications (17), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetPresence system and information processing equipment, dynamic buddy list generation method in presence system, and presence notification destination controlling method and its program for use with presence system
the server includes a state monitoring part which stores said state information C and holds a buddy list J (population list) which manages said state information C, and a buddy list generating part which generates said selection list for each client based on the pre-set rule, and comprising:
tenth step wherein said buddy list managing part holds said selection list received from said buddy list generating part in said ninth step;
wherein said buddy list generating part includes a generation rule managing part which changes said generation rule, wherein said generation rule managing part has the third changing step of changing said generation rule by reflecting said state information C received in said ninth step, and
wherein said generation rule managing part has the fourth changing step of causing a generation rule to be changed in response to the action taken from each client to change said generation rule.
This is a Divisional Application of pending prior application Ser. No. 10/761,364 filed Jan. 22, 2004 which claims the priority of Japanese Patent Application No. 2003-013137 filed Jan. 22, 2003, Japanese Patent Application No. 2003-019298 filed Jan. 28, 2003 and Japanese Patent Application No. 2003-057895 filed Mar. 5, 2003.
The presence system consists of presentities, a watcher, and a presence service. A presentity provides own presence information (i.e., the state of the principal). A watcher observes presence information provided by presentities. The presence service receives presence information from presentities and delivers it to the watcher. There are two types of watcher: fetcher and subscriber. A fetcher requests the presence service to provide the current presence information for a particular presentity. A subscriber requests the presence service to notify whenever a change occurs in the presence information for a particular presentity. (For details, refer to, for example, “A Model for Presence and Instant Messaging,” February 2000, in RFC (Request for Comments) 2778).
Presently, it is not possible either to create a buddy list by restricting the current states of principals unless the user is aware of their URIs. One example of such a buddy list is one that shows taxis cruising near a prospective passenger based on location information. The number of taxis cruising in a town is by far too large for the passenger to identify the URI of every applicable taxi. Some conventional presence systems allow users to retrieve the URI of a principal using the name or e-mail address as a keyword. In this case, however large the number of users may be, the desired principals can be added to a buddy list from the name and address information. However, these system do not have a mechanism to retrieve URIs automatically based on a state. Representative technologies using buddy lists are disclosed in Japanese Patent Laying-Open (Kokai) No. 2002-074164 and No. 2002-170032, but neither of these solves the problems described above.
The presence change rules holding part 105 holds the rules pre-set by the user (“principal” as called in RFC2778), from which the presence information for the presentity 106 is derived. These presence change rules can take any form. One example is to require the own presence information to be changed to a pre-specified value when the presence information for other presentity matches a pre-specified value. For example, a presence change rule may be described in the form of “IF . . . THEN . . . .” In this case, the left term (IF . . . ) is a conditional expression for the presence value of the other presentity 102 being watched by the watcher 107. The right term (THEN . . . ) specifies to what value the own presence information for the presentity 106 should be changed. The content of this change would be as shown in the note to FIG. 1, that is, “IF the presence for Presentity A is X, THEN set the presence for Presentity B to Y.”
(Concrete Example of the First Embodiment)
(Concrete Example of the Second Embodiment)
(Concrete Example of the Third Embodiment)
The presentity 201 issues the presence value given by the presence calculating part 204 to the presence service 209 as its own presence (S27, S28) ((3-0) in FIG. 8). However, if the presence value passed from the presence calculating part 204 is the same as the previous presence value, the presentity 201 does not issue the presence.
(Another Concrete Example of the Third Embodiment)
(Description of the Operation of the Fourth Embodiment)
B. When a change occurs in the states (306-i) of the principals (305-i), the state managing modules (1 a-i) for the principals (305-i) (1≦i≦n) issue the change to the state monitoring modules.
2. Upon receiving a new state from any (301 a-i) of the state managing modules, (301 a-1), (301 a-2), . . . , (301 a-n), the presentity state monitoring part (322) compares the new state with the states of the principals (305-i) on the population list (308) stored in the presentity state storing part (321).
Using Concrete Example 1, the fourth embodiment will further be described, with focus on how the buddy list for User A will change in response to state changes. User A herein corresponds to the principal (305) in FIG. 10.
When the state of User A changes, the processing progresses in the order of Action 1-1, Action 2 and Action 3. When the state of a user other than User A changes, the processing progresses in the order of Action 1-2, Action 2 and Action 3. If User A changes the generation rule in his or her buddy list, Action 4 will take place.
As shown in FIG. 11, the clients for the principals (305-i) (1≦i≦n) are those with automatic buddy list generating capability. The presence server with automatic generating capability (402) includes a state monitoring module (302) and a buddy list generating module (303 a). One client has all the modules in the fourth embodiment, while in the fifth embodiment one server incorporates modules that are shared by a plurality of clients. All the clients are connected with each other via the presence server with automatic buddy list generating capability (402) and a network.
The state monitoring module (304) is the same as the state monitoring module (304) in the fourth embodiment.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS6757722 *Jul 16, 2002Jun 29, 2004Nokia CorporationSystem and method for providing partial presence notificationsUS20040059781 *Sep 19, 2002Mar 25, 2004Nortel Networks LimitedDynamic presence indicatorsJP2000004299A Title not availableJP2000167233A Title not availableJP2000287249A Title not availableJP2001167175A Title not availableJP2001313666A Title not availableJP2002016696A Title not availableJP2002073791A Title not availableJP2002074164A Title not availableJP2002077456A Title not availableJP2002108814A Title not availableJP2002168515A Title not availableJP2002170032A Title not availableJP2002368885A Title not availableJP2003296525A Title not availableJP2004030371A Title not availableJP2006511853A Title not availableJPH11213291A Title not availableWO2001045342A2Nov 27, 2000Jun 21, 2001Nortel Networks LimitedPresence management systemWO2002093959A1May 10, 2002Nov 21, 2002Nokia CorporationMobile instant messaging and presence serviceWO2004008178A2Jul 10, 2003Jan 22, 2004Nokia CorporationSystem and method for providing partial presence notifications* Cited by examinerNon-Patent CitationsReference1A. Silver et al. "Unified Network Presence Management," White Paper Nortel Networks, 2000, pp. 1-6, XP002234868.2M. Day et al. "A Model for Presence and Instant Messaging," RFC-Request for Comments 2778.3M. Day et al. "A Model for Presence and Instant Messaging," RFC—Request for Comments 2778.4Satoshi Okuyama: Instant messaging technology to support new mobile services. Fujitsu, Ltd., Jul. 13, 2001, vol. 52, No. 4, p. 262-p. 267.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8533306Sep 7, 2012Sep 10, 2013At&T Intellectual Property I, L.P.Personal presentity presence subsystemUS9258376 *Aug 4, 2009Feb 9, 2016At&T Intellectual Property I, L.P.Aggregated presence over user federated devicesUS20110035443 *Aug 4, 2009Feb 10, 2011At&T Intellectual Property I, L.P.Aggregated Presence Over User Federated Devices* Cited by examinerClassifications U.S. Classification709/206, 715/751, 709/204International ClassificationG06F15/16, G06F3/00, H04L29/06, H04L29/08, H04L12/58Cooperative ClassificationH04L67/24, H04L12/581, H04W4/02, H04L51/04, H04W4/18, H04W4/023European ClassificationH04L29/08N23, H04W4/02M, H04W4/18Legal EventsDateCodeEventDescriptionOct 29, 2014FPAYFee paymentYear of fee payment: 4RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services