JP2004246397A - Dynamic generation method of buddy list - Google Patents

Dynamic generation method of buddy list Download PDF

Info

Publication number
JP2004246397A
JP2004246397A JP2003019298A JP2003019298A JP2004246397A JP 2004246397 A JP2004246397 A JP 2004246397A JP 2003019298 A JP2003019298 A JP 2003019298A JP 2003019298 A JP2003019298 A JP 2003019298A JP 2004246397 A JP2004246397 A JP 2004246397A
Authority
JP
Japan
Prior art keywords
list
buddy list
status
state
client
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
JP2003019298A
Other languages
Japanese (ja)
Other versions
JP2004246397A5 (en
JP4168762B2 (en
Inventor
Naoko Ito
Masabumi Watabe
直子 伊東
正文 渡部
Original Assignee
Nec Corp
日本電気株式会社
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Nec Corp, 日本電気株式会社 filed Critical Nec Corp
Priority to JP2003019298A priority Critical patent/JP4168762B2/en
Priority claimed from EP07102367.5A external-priority patent/EP1786173B1/en
Publication of JP2004246397A publication Critical patent/JP2004246397A/en
Publication of JP2004246397A5 publication Critical patent/JP2004246397A5/ja
Application granted granted Critical
Publication of JP4168762B2 publication Critical patent/JP4168762B2/en
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Abstract

A method for dynamically generating a buddy list is provided.
A buddy list is generated from a set (population list (8)) of PRINCIPAL (5-i) (1 ≦ i ≦ n) forming a certain population by a state monitoring module (2). Of the PRINCIPAL states (6), dynamically changing ones are monitored, and then the buddy list generation module (3) selects PRINCIPAL having a state that matches the generation rule (10). Thereby, a subset (selection list (9)) consisting of the selected PRINCIPAL is provided to the user.
[Selection diagram] Fig. 1

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a method for dynamically generating a buddy list, and more particularly, to a method for dynamically generating a buddy list for automatically generating a buddy list of an arbitrary form.
[0002]
[Prior art]
It is common to use a buddy list when grasping the state of a user on a network. A representative technique using a buddy list is a presence system.
[0003]
The presence system generally refers to a system that manages the communication state of each user, and its basic architecture is described in RFC2778. The presence system includes a presentity that provides the status of PRINCIPAL, a watcher that observes the status, and a presence service that receives the status from the presentity and distributes the status to the watcher.
[0004]
Many presence systems display PRINCIPAL status collected by watchers as a buddy list. The buddy list must be managed by each user of the presence service. When the number of communication partners increases while using the presence service, there is a problem that the burden on the user for managing the buddy list increases. When changing the party to observe the state according to the situation such as time or place, a separate buddy list must be prepared for each, and the burden on the user is further increased.
[0005]
Buddy lists with static content have problems besides the administrative burden. For example, consider that a user has a private buddy list separate from a work buddy list. The user wants to have this buddy list to contact when both parties are not working. However, it is difficult for a user to create such a buddy list. This is because the people displayed on this private buddy list are always included in this buddy list regardless of whether they are working or not. It is impossible to create a buddy list that restricts the other party's state using a conventional static buddy list.
[0006]
Furthermore, at present, it is not possible to create a buddy list by limiting the current state of PRINCIPAL where the user does not know the URI. For example, a buddy list in which taxis running near passengers are always displayed based on location information can be considered. The number of taxis running in the city is too large for passengers to know each URI one by one. In a conventional presence system, a user himself / herself searches for a PRINCIPAL URI from a name or an e-mail address. Even if the number of users is large, a user can register a target PRINCIPAL in a buddy list from such information. However, there is no mechanism for automatically retrieving a URI from a state. Representative techniques using a buddy list include those described in Patent Documents 1 and 2, but none of these techniques overcomes the above problems.
[0007]
[Patent Document 1]
JP 2002-074164 A
[Patent Document 2]
JP 2002-170032 A
[0008]
[Problems to be solved by the invention]
The present invention has been made in view of the above problems, and has the following objects for each claim.
[0009]
In the invention according to claim 1, the buddy list can be automatically generated in accordance with both the status of the user who owns the buddy list and the status of another PRINCIPAL included in the buddy list, and the buddy list can be easily viewed. It is intended to provide a dynamic generation method.
[0010]
An object of the invention according to claim 2 is to provide a method of dynamically generating a buddy list in which a user only needs to set conditions for registering PRINCIPAL in a buddy list.
[0011]
An object of the invention according to claim 3 is to provide a method for dynamically generating a buddy list in which a user only needs to set conditions for registering PRINCIPAL in a buddy list.
[0012]
In the invention according to claim 4, the buddy list can be automatically generated in accordance with both the status of the user who owns the buddy list and the status of other PRINCIPAL included in the buddy list. It is an object of the present invention to provide a method for dynamically generating a buddy list in which a server can provide a user with a required presentity URI included in a buddy list without knowing the URI.
[0013]
An object of the invention according to claim 5 is to provide a method of dynamically generating a buddy list in which a user only needs to set conditions for registering PRINCIPAL in a buddy list.
[0014]
An object of the invention according to claim 6 is to provide a method for dynamically generating a buddy list in which a user only needs to set conditions for registering PRINCIPAL in a buddy list.
[0015]
[Means for Solving the Problems]
In order to solve this object, the invention according to claim 1 is a method for dynamically generating a buddy list when each client on a network automatically generates a buddy list for managing state information relating to its own client or another client. Each client has status management means for storing status information A about its own client, status monitoring means for storing status information B about other clients, and holding a buddy list (population list) for managing status information B. A buddy list generating means for generating a buddy list (selection list) based on a predetermined generation rule, and a buddy list managing means for holding a selection list, when a state of either the own client or another client changes. First, the state management unit updates the state information A and transmits the state information A to the buddy list generation unit. And the status monitoring means transmits status notification request information for acquiring the changed status to the other clients included in the population list, and the status change notification corresponding to the status notification request information is transmitted from the other client. A second step of receiving the information and the status information B, wherein the status monitoring means updates the status information B managed by the population list based on the status change notification information, and converts the population list into a buddy list generation means. And the buddy list generating means transmits the state information A received from the state managing means in the first step, and the state information B managed by the population list received from the state monitoring means in the third step. And a fourth step of generating a selection list based on the generation rule and transmitting the selection list to the buddy list management means. The buddy list management means receives the selection list from the buddy list generation means in the fourth step. Characterized in that it comprises a fifth step of holding the selection list.
[0016]
According to a second aspect of the present invention, in the first aspect of the present invention, the buddy list generation unit includes a generation rule management unit for changing a generation rule, and the generation rule management unit receives the state received in the fourth step. The method includes a first change step of changing the generation rule based on the information A or B.
[0017]
According to a third aspect of the present invention, in the second aspect, the generation rule management unit includes a second change step of changing the generation rule by performing an operation of changing the generation rule from the client. It is characterized by.
[0018]
The invention according to claim 4 is a method for dynamically generating a buddy list when a server on a network automatically generates a buddy list for managing state information on each client, wherein each client has state information C on its own. And a buddy list managing means for storing a buddy list (selection list) generated and transmitted by the server, wherein the server stores the state information C and manages the state information C. (A population list), and buddy list generating means for individually generating a selection list for each client based on a predetermined generation rule. In the sixth step, the state management means updates the state information C, and the state monitoring means sends a message to each client included in the population list. A seventh step of transmitting state notification request information for obtaining the changed state, and receiving state change notification information and state information C corresponding to the state notification request information from each client; The eighth step of updating the state information C managed by the population list based on the change notification information and transmitting the population list to the buddy list generation unit, and the buddy list generation unit performs the following steps: A selection list is individually generated for each client based on the state information C managed by the population list received from the state monitoring unit and the generation rule, and the selection list is transmitted to the buddy list management unit of each client. A ninth step and the tenth step in which the buddy list management means holds the selection list received from the buddy list generation means in the ninth step.
[0019]
According to a fifth aspect of the present invention, in the fourth aspect of the present invention, the buddy list generating means includes a generating rule managing means for changing a generating rule, wherein the generating rule managing means receives the state received in the ninth step. It is characterized by including a third change step of changing the generation rule by the information C.
[0020]
The invention according to claim 6 is the invention according to claim 5, wherein the generation rule management means includes a fourth change step of changing the generation rule by performing an operation of changing the generation rule from each client. It is characterized by.
[0021]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the present embodiment, a method of dynamically generating a buddy list in a presence system will be described, but the scope of the present invention is not limited to the presence system.
[0022]
(Configuration of Embodiment 1)
FIG. 1 shows the configuration of the first embodiment of the present invention. The first embodiment includes a client (100) with a buddy list automatic generation function and a state management module (1a) belonging to another client. The client (100) with a buddy list automatic generation function includes a state management module (1), a state monitoring module (2), a buddy list generation module (3), and a buddy list management module (4). All clients are connected to each other via a network. However, it may not be connected to the network.
[0023]
The state management module (1) collects states related to PRINCIPAL (5) and stores them internally. When the state of PRINCIPAL changes, the state (6) stored in the PRINCIPAL state storage unit (11) is changed and issued to the buddy list generation module (3). The PRINCIPAL status is stored in the PRINCIPAL status storage unit (11). The monitoring and collection of the status of PRINCIPAL is executed by the PRINCIPAL status monitoring unit (12). The status management module (1a) belonging to another client issues a status (6) to the status monitoring module (2) via the network.
[0024]
The states described above are represented by various attributes. For example, whether or not communication is indicated as "online" or "offline", a position represented by latitude and longitude, individual intentions and requests such as "want to take a taxi" or "want to take a train", "hot", "cold" And "comfortable" individual moods can also be defined as states. For example, one PRINCIPAL state is described as “online, hot” and another PRINCIPAL is described as “online, want to take a taxi, cold”. The presence service manages PRINCIPAL as an attribute value from various aspects.
[0025]
In this embodiment, two types of buddy lists called a population list (8) and a selection list (9) are used. The buddy list is a list having URI (7) of PRINCIPAL as an element. Each element of the buddy list can have one or more states (6) related to the PRINCIPAL in addition to the URI (7) of the PRINCIPAL. The population list (8) is a buddy list held by the status monitoring module (2). The selection list (9) is generated by the buddy list generation module (3) and held by the status providing module (4), and is a buddy list displayed on a screen via a GUI or the like.
[0026]
The status monitoring module (2) issues a status notification request (subscribe) to one or more PRINCIPAL (5-i) (1 ≦ i ≦ n) included in the population list (8), and notifies the status change. And updates the internally held state when the state (6) issued by the state management module (1a) is received. The presentity state storage unit (21) inside the state monitoring module (2) holds the state of PRINCIPAL (5-i) as a population list (8). Even if the number of PRINCIPAL included in the population list (8) is 0, the list is retained as an unregistered list. The presentity state monitoring unit (22) waits for the state (6) issued by the state management module (1a).
[0027]
The buddy list generation module (3) compares each element of the population list (8) obtained from the state monitoring module (2) with the state (6) of PRINCIPAL (5) obtained from the state management module (1). , A selection list (9) composed of elements of PRINCIPAL (5-i) having a state that has a specific relationship with the state (6) of PRINCIPAL (5). The generation processing of the selection list (9) is executed in the selection list generation unit (31). When using an unregistered list in which the population list (8) includes 0 PRINCIPAL, the selection list generation unit (31) generates an unregistered selection list. The generation rule (10) describing the relationship between the state (6) of PRINCIPAL (5) and the state of PRINCIPAL (5-i) of the population list (8) is stored in the generation rule storage unit (32). The generation rule management unit (33) is in the generation rule storage unit (32) when the PRINCIPAL operates, when the PRINCIPAL status is input, or when other information (such as time) is input. The generation rule (10) is changed.
[0028]
The buddy list management module (4) holds the selection list (9). The selection list (9) is stored in a buddy list storage unit (41) inside the buddy list management module (4).
[0029]
(Description of the operation of the first embodiment)
The operation of the first embodiment will be described in steps (1) to (5).
[0030]
{Circle around (1)} When the state of PRINCIPAL (5) changes, the state management module (1) of PRINCIPAL (5) issues this to the buddy list generation module (3).
[0031]
1. When the PRINCIPAL status monitoring unit (12) acquires the status from the PRINCIPAL (5), it compares this with the status (6) stored in the PRINCIPAL status storage unit (11).
[0032]
2. If state (6) is different from the previous state,
2-1. The PRINCIPAL state storage unit (11) updates the state (6) with a new state.
2-2. The PRINCIPAL state storage unit (11) issues a new state (6) to the buddy list generation module (3).
[0033]
{Circle around (2)} The state management module (1a-i) of PRINCIPAL (5-i) (1 ≦ i ≦ n) changes the state (6-i) of PRINCIPAL (5-i) to the state monitoring module. Issue.
[0034]
{Circle around (3)} The status monitoring module (2) receives the notification of the status change of the other PRINCIPAL (5-i) and issues it to the buddy list generation module (3).
[0035]
1. The presentity state monitoring unit (22) includes PRINCIPAL state management modules (1a-1), (1a-2),. . . , (1a-n) until a new state is issued.
[0036]
2. The presentity state monitoring unit (22) includes state management modules (1a-1), (1a-2),. . . , (1a-n), when a new state is received from (1a-i), the state of PRINCIPAL (5-i) stored in the population list (8) of the presentity state storage unit (21) Compare.
[0037]
3. If the new state is different from the previous state,
3-1. The presentity state storage unit (21) updates the state of PRINCIPAL (5-i) in the population list (8).
3-2. When the status of the elements of the population list is updated, the presentity status storage unit (21) passes the population list (8) to the buddy list generation module (3).
[0038]
(4) When the buddy list generation module (3) receives the change in the state of PRINCIPAL (5) or another PRINCIPAL in the step (1) or (3), the buddy list generation module (3) regenerates the selection list and generates a new selection list. Issued to the buddy list management module (4).
[0039]
1. The selection list generation unit (31) waits for a new PRINCIPAL (5) state (6) issued by the state management module (1). At the same time, it waits for a new population list (8) issued by the state monitoring module (2).
[0040]
2. Upon receiving either the new state (6) of the PRINCIPAL (5) or the new population list (8), the selection list generation unit (31) performs the following processing.
2-1. When a new state (6) of PRINCIPAL (5) is received from the state management module (1), a population list (8) is acquired from the state monitoring module (2).
2-2. When a new population list (8) is received from the status monitoring module (2), the status (6) is acquired from the status management module (1).
[0041]
3. The selection list generation unit (31) searches the population list (8) for an element having a state defined by the state (6) of PRINCIPAL (5) and the generation rule (10). Zero or more elements found by this search are set as elements of the new selection list. The selection list generation unit (31) passes the generated selection list (9) to the buddy list management module (4).
[0042]
(5) The buddy list management module (4) holds the latest selection list (9) issued by the buddy list generation module and presents it to PRINCIPAL.
[0043]
(Specific example 1)
In the first embodiment, how the buddy list of the user A changes according to the change in the state will be described step by step using the first specific example. Here, the user A corresponds to PRINCIPAL (5) in FIG.
[0044]
Many users (user B, user C,...) In addition to user A subscribe to the presence service. These users correspond to PRINCIPAL (5-i) in FIG. All subscribers of the presence service have their communication status and location as presence information. In addition, it is possible to monitor (subscribe) the communication state and position of an arbitrary user.
[0045]
Possible values of the communication state include “online” and “offline”. "Online" indicates that the phone call can be answered, and "Offline" indicates that the call cannot be answered. The position in the specific example 1 is represented by the name of the nearest station. If the position of a certain user is “Tokyo”, it indicates that the nearest station of the person's current location is Tokyo Station.
[0046]
When the state of the user A changes, the processing proceeds in the order of operation 1-1, operation 2 and operation 3. When the state of a user other than the user A changes, the processing proceeds in the order of operation 1-2, operation 2, and operation 3. When the user A changes the buddy list generation rule, the operation 4 is performed.
[0047]
(Operation 1-1)
1. User A inputs a new location “Yokohama” into the status management module. When a new state is input from the user A, the state management module executes the following processing.
[0048]
2. If the input state is different from the state held inside the state management module, the old state is discarded and the input state is held internally. For example, if the position of the user A held by the current state management module is “Tokyo”, this is replaced with “Yokohama”.
[0049]
3. The processing of the buddy list generation module is started.
[0050]
(Operation 1-2)
1. The status monitoring module waits until receiving a status change notification message from any of the users included in the population list.
[0051]
2. User B changes the location from “Shinjuku” to “Tokyo” and issues a status change notification to the status monitoring module.
[0052]
3. The state monitoring module searches for an element corresponding to the user B from the list of all users in the population list held and changes the position state to “Tokyo”.
[0053]
4. The processing of the buddy list generation module is started.
[0054]
(Operation 2)
The buddy list generation module performs the following processing.
[0055]
1. The position of the user A is obtained from the state management module. The status management module passes the status of the position of the user A held internally to the buddy list generation module.
[0056]
2. From the status monitoring module, a population list including URIs and location presences of all users monitored by the status monitoring module is obtained.
[0057]
3. Search the population list for elements that meet the production rules. Copy zero or more elements found as a result of the search and store them in the selection list. It is assumed that the generation rule is described as “position of user in IF population list = position of user A THEN registers user of population list”. If the position of the user A is “Tokyo” and the positions of the users B and E are “Tokyo”, the elements of the users B and E are stored in the selection list.
[0058]
4. Pass the selection list to the buddy list management module.
[0059]
(Operation 3)
The buddy list management module performs the following processing.
[0060]
1. Obtain a new selection list from the buddy list generation module.
[0061]
2. The communication state of the user included in the new selection list is presented to the user A.
[0062]
When user A changes the generation rule, the process of operation 4 is performed.
[0063]
(Operation 4)
1. The user A inputs a new generation rule “the user position of the IF population list is within two stations from the position of the user A and registers the user of the THEN population list” to the buddy list generation module.
[0064]
2. The buddy list generation module discards the old generation rules held therein and saves the input new generation rules.
[0065]
(Specific example 2)
As another specific example, an example in which the present invention is applied to a telephone directory function of a mobile phone will be described. In this example, the user publishes the work status and the manner mode setting status to the presence service. The work state is represented by “working” and “private”, and the manner mode setting state is represented by “manner setting” and “manner release”. The state management module mounted on the mobile phone acquires and holds the states of the two from the button operation of the user. When the state changes, a new state is issued to the buddy list generation module.
[0066]
The status monitoring module monitors the work status and manner mode setting status of each person registered in the telephone directory of the mobile phone. The population list held by the status monitoring module is integrated with the telephone directory, and the work status and the manner mode setting status are stored together with the telephone numbers of each person. When the status of someone in the phone book changes, the status monitoring module issues a new population list to the buddy list generation module.
[0067]
The user, in the buddy list generation module mounted on the mobile phone, generates the rule “work status of person registered in IF phonebook = own work status AND work status of person registered in AND phonebook = manner cancellation” "Register the person registered in the THE phonebook in the selection list" is set. The buddy list generation module generates the selection list by applying the above-described generation rule when receiving the own status issued by the status management module or the population list issued by the status monitoring module.
[0068]
The generated selection list is displayed on the screen when the user presses the telephone directory display key of the mobile phone. When the user's work state is "private", only the person whose work state is "private" and whose manner mode setting state is "cancel manner" is displayed on the screen from the telephone directory. The state of the user and the state of the person registered in the telephone directory continue to change over time. However, the selection list displayed when the user presses the key always reflects the state of the user at that time and the state of the person registered in the telephone directory.
[0069]
(Example 2)
FIG. 2 shows the configuration of the second embodiment of the present invention. The second embodiment includes a client (101) with a buddy list automatic generation function, a presence server (102) with a buddy list automatic generation function, and a state management module (1a) belonging to another client. The client with a buddy list automatic generation function (101) includes a state management module (1a) and a buddy list management module (4). There are a total of n clients, including the client (101) with a buddy list automatic generation function.
[0070]
FIG. 2 shows that the client of PRINCIPAL (5-i) (1 ≦ i ≦ n) is a client with a buddy list automatic generation function. The presence server with a buddy list automatic generation function (102) includes a status monitoring module (2) and a buddy list generation module (3a). In the first embodiment, one client has all modules, while in the second embodiment, one server has a module commonly used by a plurality of clients. All clients connect to the presence server (102) with a buddy list automatic generation function via a network.
[0071]
The status management module (1a) issues a status (6-i) to the status monitoring module (2) via the network.
[0072]
The status monitoring module (2) of the second embodiment has the same function as the status monitoring module (2) of the first embodiment. However, since this module is on a server, the population list (8) includes all PRINCIPAL URIs (7) and states (6).
[0073]
The buddy list generation module (3a) obtains a population list (8) from the state monitoring module (2). The selection list is generated individually for each element of the population list (8). Therefore, the buddy list generation module (3a) can generate a plurality of selection lists. An identifier is assigned to the selection list (9-i). The buddy list generation module (3a) selects a selection list (9-i) for each PRINCIPAL (5-i) (1 ≦ i ≦ n) having a client (101) with a buddy list automatic generation function connected via a network. Issue The selection list generation processing is executed in the selection list generation unit (31a). The generation rule storage unit (32) stores the selection list generation rule (10).
[0074]
The status monitoring module (4) is the same as the status monitoring module (4) of the first embodiment.
[0075]
In the first and second embodiments, the buddy list generation module obtains a population list including all PRINCIPALs from the state monitoring module every time the state of any PRINCIPAL is changed. It is possible for a module to keep a buddy list permanently. When the status of a certain PRINCIPAL is changed, only the selection list for adding a URI and the selection list for deleting are updated, and the updated selection list is transmitted to the client having the selection list before the update. According to this method, when a plurality of users share one buddy list generation module, it is possible to reduce the selection list generation time per user.
[0076]
Alternatively, the life time of the buddy list held by the buddy list generation module may not be permanent but may be a fixed period.
[0077]
In the buddy list generation module holding the selection list as described above, the selection list may include its own URI. To prevent this, it is possible to design a buddy list generation module that excludes the URI of the PRINCIPAL to be issued from the selection list when issuing the selection list.
[0078]
In the second embodiment, by managing the population list for each PRINCIPAL, each PRINCIPAL can restrict other PRINCIPALs that may be included in the buddy list in advance. The population list of each PRINCIPAL can specify a set of other PRINCIPAL URIs that may be included in the buddy list using a wildcard.
[0079]
【The invention's effect】
As apparent from the above description, the following effects can be obtained by the present invention.
[0080]
In the invention according to claim 1, the buddy list can be automatically generated according to the status of both the user who owns the buddy list and other PRINCIPALs included in the buddy list. For example, if the present invention is used in a presence service that treats a state of work or a break in addition to a communication state, the communication state is displayed only when the user and the other party are in the same situation (during a break, at work, etc.). Buddy lists are possible. Also, the buddy list is easy to see. PRINCIPAL displayed in the buddy list can be automatically selected according to the state of the user having the buddy list and the state of PRINCIPAL included in the buddy list. Therefore, there is no need to switch display pages for each buddy list or to scroll and display a long buddy list.
[0081]
According to the second aspect of the invention, only one piece of information managed by the user is required. The user simply sets the conditions for registering PRINCIPAL in the buddy list. The present invention automatically changes the PRINCIPAL included in the buddy list according to the status of both the user and the other PRINCIPAL. Therefore, the user does not need to prepare a plurality of buddy lists according to his / her situation. There is no need to register and manage the same PRINCIPAL in a plurality of buddy lists.
[0082]
In the invention according to the third aspect, only one piece of information managed by the user is required. The user simply sets the conditions for registering PRINCIPAL in the buddy list. The present invention automatically changes the PRINCIPAL included in the buddy list according to the status of both the user and the other PRINCIPAL. Therefore, the user does not need to prepare a plurality of buddy lists according to his / her situation. There is no need to register and manage the same PRINCIPAL in a plurality of buddy lists.
[0083]
In the invention according to claim 4, the buddy list can be automatically generated in accordance with the status of both the user who owns the buddy list and the other PRINCIPAL included in the buddy list. For example, if the present invention is used in a presence service that treats a state of work or a break in addition to a communication state, the communication state is displayed only when the user and the other party are in the same situation (during a break, at work, etc.). Buddy lists are possible. Also, the buddy list is easy to see. PRINCIPAL displayed in the buddy list can be automatically selected according to the state of the user having the buddy list and the state of PRINCIPAL included in the buddy list. Therefore, there is no need to switch display pages for each buddy list or to scroll and display a long buddy list. In particular, even if the user does not know the URI, the server can provide the user with the necessary presentity URI included in the buddy list. In the second embodiment, such an effect is obtained. For example, in a presence service that treats a location as presence information in addition to a communication state, it is possible to include only a taxi currently near a passenger in a buddy list. Since the intermediate server provides the buddy list according to the location of the passenger, the passenger himself / herself registers hundreds of taxis in the buddy list, eliminating the need to search for a nearby taxi from the buddy list.
[0084]
In the invention according to claim 5, only one piece of information managed by the user is required. The user simply sets the conditions for registering PRINCIPAL in the buddy list. The present invention automatically changes the PRINCIPAL included in the buddy list according to the status of both the user and the other PRINCIPAL. Therefore, the user does not need to prepare a plurality of buddy lists according to his / her situation. There is no need to register and manage the same PRINCIPAL in a plurality of buddy lists.
[0085]
In the invention according to claim 6, only one piece of information managed by the user is required. The user simply sets the conditions for registering PRINCIPAL in the buddy list. The present invention automatically changes the PRINCIPAL included in the buddy list according to the status of both the user and the other PRINCIPAL. Therefore, the user does not need to prepare a plurality of buddy lists according to his / her situation. There is no need to register and manage the same PRINCIPAL in a plurality of buddy lists.
[Brief description of the drawings]
FIG. 1 is a configuration diagram according to a first embodiment.
FIG. 2 is a configuration diagram according to a second embodiment.
[Explanation of symbols]
1 status management module
2 Condition monitoring module
3 Buddy list generation module
4 Buddy list management module
5 PRINCIPAL
6 states
7 URI
8 Population list
9 Selection list
10 Production rules

Claims (6)

  1. A method for dynamically generating a buddy list when each client on a network automatically generates a buddy list for managing state information about the own client or another client,
    Each client has state management means for storing state information A about its own client, state monitoring means for storing state information B about other clients, and holding a buddy list (population list) for managing the state information B, Buddy list generation means for generating a buddy list (selection list) based on a predetermined generation rule; and buddy list management means for holding the selection list.
    When the status of either the own client or another client changes,
    A first step of updating the state information A and transmitting the updated state information A to the buddy list generating means;
    The status monitoring means transmits status notification request information for obtaining a changed status to other clients included in the population list, and a status change notification corresponding to the status notification request information from the other client. A second step of receiving information and said state information B;
    A third step of, based on the status change notification information, updating the status information B managed by the population list and transmitting the population list to the buddy list generation unit;
    The buddy list generating means includes: the state information A received from the state managing means in the first step; and the state information B managed by the population list received from the state monitoring means in the third step. A fourth step of generating the selection list based on the generation rule and transmitting the selection list to the buddy list management means;
    The buddy list management method includes a fifth step of holding the selection list received from the buddy list generating means in the fourth step.
  2. The buddy list generation unit includes a generation rule management unit that changes the generation rule, and the generation rule management unit changes the generation rule based on the status information A or B received in the fourth step. The method for dynamically generating a buddy list according to claim 1, further comprising a changing step.
  3. The dynamic generation of a buddy list according to claim 2, wherein the generation rule management unit includes a second change step of changing the generation rule by performing an operation of changing the generation rule from the client. Method.
  4. A method for dynamically generating a buddy list when a server on a network automatically generates a buddy list for managing state information about each client,
    Each client includes state management means for storing state information C relating to itself, and buddy list management means for holding a buddy list (selection list) generated and transmitted by the server.
    A server that stores the state information C and that stores a buddy list (population list) that manages the state information C; and that individually stores the selection list for each client based on a predetermined generation rule. Buddy list generating means for generating
    When any client changes state,
    A sixth step of updating the state information C,
    The status monitoring means transmits status notification request information for obtaining a changed status to each client included in the population list, and a status change notification corresponding to the status notification request information from each client. A seventh step of receiving information and said state information C;
    An eighth step of, based on the status change notification information, updating the status information C managed by the population list and transmitting the population list to the buddy list generation unit;
    The buddy list generation unit individually stores the selection list for each client based on the status information C managed by the population list received from the status monitoring unit in the eighth step and the generation rule. Generating a ninth step of transmitting the selection list to the buddy list management means of each client;
    The buddy list dynamic generation method according to claim 10, further comprising a tenth step in which the buddy list management unit holds the selection list received from the buddy list generation unit in the ninth step.
  5. The buddy list generation means includes a generation rule management means for changing the generation rule, and the generation rule management means changes the generation rule based on the state information C received in the ninth step. The method for dynamically generating a buddy list according to claim 4, further comprising:
  6. The dynamic generation of a buddy list according to claim 5, wherein the generation rule management unit includes a fourth change step of changing the generation rule by performing an operation of changing the generation rule from each client. Method.
JP2003019298A 2003-01-28 2003-01-28 Buddy list dynamic generation method, client, server, system, program Active JP4168762B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2003019298A JP4168762B2 (en) 2003-01-28 2003-01-28 Buddy list dynamic generation method, client, server, system, program

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
JP2003019298A JP4168762B2 (en) 2003-01-28 2003-01-28 Buddy list dynamic generation method, client, server, system, program
EP07102367.5A EP1786173B1 (en) 2003-01-22 2004-01-22 Dynamic buddy list generation method
DE602004026131T DE602004026131D1 (en) 2003-01-22 2004-01-22 attendance system
EP07102346.9A EP1786172B1 (en) 2003-01-22 2004-01-22 Presence system and process for controlling the destination of presence notification
US10/761,364 US7844667B2 (en) 2003-01-22 2004-01-22 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 system
EP04001365A EP1441486B1 (en) 2003-01-22 2004-01-22 Presence system
US12/361,919 US7953811B2 (en) 2003-01-22 2009-01-29 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 system
US12/964,171 US8458272B2 (en) 2003-01-22 2010-12-09 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 system

Publications (3)

Publication Number Publication Date
JP2004246397A true JP2004246397A (en) 2004-09-02
JP2004246397A5 JP2004246397A5 (en) 2006-01-19
JP4168762B2 JP4168762B2 (en) 2008-10-22

Family

ID=33018716

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2003019298A Active JP4168762B2 (en) 2003-01-28 2003-01-28 Buddy list dynamic generation method, client, server, system, program

Country Status (1)

Country Link
JP (1) JP4168762B2 (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1679650A1 (en) 2005-01-06 2006-07-12 NEC Corporation List management server for managing updating of list by third-party terminal, list management system, list managing method, and program
EP1837812A2 (en) * 2006-03-22 2007-09-26 NEC Corporation Abstract state monitoring system and method for the same
JP2009514321A (en) * 2005-10-26 2009-04-02 サムスン エレクトロニクス カンパニー リミテッド System and method for sending connection list entries with presence subscriptions
JP2010257273A (en) * 2009-04-27 2010-11-11 Hitachi Ltd Buddy list generation method
US8016931B2 (en) 2007-07-19 2011-09-13 Seiko Epson Corporation Ink set
US8016930B2 (en) 2005-11-16 2011-09-13 Seiko Epson Corporation Magenta ink composition, ink cartridge, and recording system and recorded matter using the same
US8038783B2 (en) 2008-09-10 2011-10-18 Seiko Epson Corporation Ink set, recording method, and recording apparatus
US8092583B2 (en) 2008-08-25 2012-01-10 Seiko Epson Corporation Ink set
US8277551B2 (en) 2009-02-23 2012-10-02 Seiko Epson Corporation Ink set, recording apparatus, and recording method
US8277552B2 (en) 2009-12-04 2012-10-02 Seiko Epson Corporation Ink set, recording apparatus, and recording method

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7814120B2 (en) 2005-01-06 2010-10-12 Nec Corporation List management server for managing updating of list by third-party terminal, list management system, list managing method, and program
JP2006190076A (en) * 2005-01-06 2006-07-20 Nec Corp Server, system and method for list management, and program
EP1679650A1 (en) 2005-01-06 2006-07-12 NEC Corporation List management server for managing updating of list by third-party terminal, list management system, list managing method, and program
JP4544417B2 (en) * 2005-01-06 2010-09-15 日本電気株式会社 List management server, list management system, list management method and program
JP2009514321A (en) * 2005-10-26 2009-04-02 サムスン エレクトロニクス カンパニー リミテッド System and method for sending connection list entries with presence subscriptions
US8016930B2 (en) 2005-11-16 2011-09-13 Seiko Epson Corporation Magenta ink composition, ink cartridge, and recording system and recorded matter using the same
US8486186B2 (en) 2005-11-16 2013-07-16 Seiko Epson Corporation Magenta ink composition, ink cartridge, and recording system and recorded matter using the same
US7782186B2 (en) 2006-03-22 2010-08-24 Nec Corporation Abstract state monitoring system and method for the same
EP1837812A2 (en) * 2006-03-22 2007-09-26 NEC Corporation Abstract state monitoring system and method for the same
EP1837812A3 (en) * 2006-03-22 2014-12-17 NEC Corporation Abstract state monitoring system and method for the same
US8016931B2 (en) 2007-07-19 2011-09-13 Seiko Epson Corporation Ink set
US8092583B2 (en) 2008-08-25 2012-01-10 Seiko Epson Corporation Ink set
US8172933B2 (en) 2008-08-25 2012-05-08 Seiko Epson Corporation Ink set
US8038783B2 (en) 2008-09-10 2011-10-18 Seiko Epson Corporation Ink set, recording method, and recording apparatus
US8277551B2 (en) 2009-02-23 2012-10-02 Seiko Epson Corporation Ink set, recording apparatus, and recording method
JP2010257273A (en) * 2009-04-27 2010-11-11 Hitachi Ltd Buddy list generation method
US8277552B2 (en) 2009-12-04 2012-10-02 Seiko Epson Corporation Ink set, recording apparatus, and recording method

Also Published As

Publication number Publication date
JP4168762B2 (en) 2008-10-22

Similar Documents

Publication Publication Date Title
US7203294B2 (en) System and method for dynamically routing communications
CN1846401B (en) Group service with information on group members
US6973299B2 (en) Unified contact list
US7675903B2 (en) Dynamic contact list management system and method
US7813488B2 (en) System and method for providing information regarding an identity's media availability
DE602004005765T2 (en) Messenger assistant for personal information manager
CN100574203C (en) Informing method and system for presenting information
US7246371B2 (en) System and method for filtering unavailable devices in a presence and availability management system
KR101031942B1 (en) Method and system for locating contact information collected from contact sources
US7373173B2 (en) Sharing image items
US7836126B2 (en) Business presence system and method
JP4605749B2 (en) Method for supplying communication information of a communication unit and apparatus for carrying out the method
US5870744A (en) Virtual people networking
US20090110179A1 (en) Technique for providing personalized information and communication services
US8200755B2 (en) Presence administration method and device
US6807423B1 (en) Communication and presence spanning multiple access networks
US20060288099A1 (en) Method of and System for Presence Management in Telecommunications
EP1672896B1 (en) Providing customized messages to callers of unavailable called subscribers
EP1397923B1 (en) Mobile instant messaging and presence service
FI117079B (en) Method and apparatus for displaying reminders in a portable device
EP0944003A1 (en) Notification subsystem
US20040098491A1 (en) Accessing presence information
US20150236989A1 (en) Server apparatus and client apparatus in presence display system
US20040002329A1 (en) Method and system for supporting non-intrusive and effective voice communication among mobile users
US20050235038A1 (en) Method of and apparatus for server-side management of buddy lists in presence based services provided by a communication system

Legal Events

Date Code Title Description
A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20051130

A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20051213

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20080410

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20080422

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20080623

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20080715

A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20080728

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20110815

Year of fee payment: 3

R150 Certificate of patent or registration of utility model

Free format text: JAPANESE INTERMEDIATE CODE: R150

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20110815

Year of fee payment: 3

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20120815

Year of fee payment: 4

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20130815

Year of fee payment: 5