JP2006209193A - Distribution destination management device, distribution destination management method, and program thereof - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a distribution destination management device and a distribution destination management method for changing distribution destinations quickly. <P>SOLUTION: A storage part 3b stores conditions showing propriety of changing destinations of the information held by a presentity set by an information provider using the presentity. A judgement part 3c judges whether to approve the change of destinations requested by an authority transfer request outputted by a receiving part 3a, according to the conditions stored in the storage part 3b. The judgment part 3c outputs the result of the judgment and the authority transfer request to a rewriting part 3d. When the judgment part 3c judges that the change of destinations is approved, the rewriting part 3d changes the destination of presence information of the presentity shown in the authority transfer request from the original watcher to a proxy watcher. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a distribution destination management apparatus, a distribution destination management method, and a program, and more particularly, to a distribution destination management apparatus, a distribution destination management method, and a program for managing a change in the distribution destination of information held by an information provider terminal.

  Conventionally, a presence system for managing the state of a user is known. For example, Patent Document 1 (Japanese Patent Laid-Open No. 2003-141038) describes a presence system using a buddy list (state monitoring target person list).

  The presence system is an example of a name of a presence service indicating a general system for managing the status of each user, and the basic architecture is shown in RFC (Request For Comment) 2778.

  The presence system includes a presentity, a watcher, and a presence service unit.

  The presentity holds state information (presence information) of the state information provider. Specifically, the presentity is an information provider terminal device that holds presence information of the status information provider.

  The watcher provides the status information recipient with the presence information held by the presentity. Specifically, the watcher is a recipient terminal device (distribution destination) that accepts presence information of the presentity.

  The watcher does not accept the presence information of all the presentities, but accepts the presence information of the presentity designated by the watcher. The presentity designated by the watcher is called a buddy (monitoring target). The watcher creates a buddy list (information monitoring target person list) indicating the buddies in order to acquire the presence information of the buddies.

  The presence service unit distributes the presence information of the buddies shown in the buddy list to the watcher.

  The presence service unit does not distribute the presence information of all buddies to the watcher, but distributes only the presence information of the buddies permitted to distribute the presence information to the watcher.

In addition, the presentity sets whether to permit distribution of presence information to the watcher after receiving a status notification request (presence information distribution request) from the watcher.
JP 2003-141038 A

  In a conventional presence system (presence service), when a watcher asks an alternate watcher to monitor a buddy, the alternate watcher sends a status notification request to the buddy, and then the buddy is present to the alternate watcher. A series of work of permitting distribution of information is required.

  Therefore, the substitute watcher cannot perform buddy monitoring while the series of operations is being performed. Therefore, there arises a problem that it takes time to change the watcher.

  An object of the present invention is to provide a distribution destination management apparatus, a distribution destination management method, and a program capable of quickly changing a distribution destination.

  In order to achieve the above object, a distribution destination management apparatus according to the present invention changes a distribution destination terminal based on a change request for changing a distribution destination terminal of information held by an information provider terminal. A management unit, a storage unit for storing conditions indicating whether or not the distribution destination terminal can be changed, set by an information provider using the information provider terminal; and a reception unit for receiving the change request A determination unit that determines whether or not to permit a change of a distribution destination requested by the change request received by the reception unit based on a condition stored in the storage unit, and the determination unit includes the distribution destination A change unit that changes the distribution destination terminal in response to the change request.

  The delivery destination management method of the present invention further includes a storage unit that stores conditions indicating whether or not a delivery destination terminal can be changed, which is set by an information provider using the information provider terminal, A delivery destination management method performed by a delivery destination management device that changes the delivery destination terminal based on a change request for changing a delivery destination terminal of information held by a user terminal, and accepting the change request A determination step of determining whether or not to permit a change of a delivery destination requested by the change request based on a condition stored in the storage unit; and when the change of the delivery destination is permitted, the change And a change step of changing a delivery destination terminal in response to the request.

  According to said invention, the decision | availability of the change of a delivery destination is determined based on the conditions stored in the storage part. The conditions stored in the storage unit are set by the information provider. Therefore, whether or not the distribution destination can be changed can be determined based on the policy of the information provider, and whether or not the information provider permits distribution of information to the terminal of the change destination when the distribution destination is changed. It is not necessary to perform the work of determining

  Therefore, it becomes possible to quickly change the delivery destination.

  The distribution destination management apparatus is connected to an access list management unit that manages an access permission list indicating a distribution destination to which the information provider permits distribution of the information, and the change of the distribution destination is permitted. It is desirable that the changed delivery destination terminal is described in the access permission list.

  According to the above invention, it is possible to manage the change of the distribution destination by the access permission list.

  In addition, the distribution destination management device is connected to an access list management unit that manages an access denial list indicating a distribution destination from which the information provider has refused to distribute the information, and the storage unit includes the condition as: It is desirable to store a rejection condition indicating that the change of the delivery destination terminal is rejected when the changed delivery destination terminal is described in the access denial list.

  According to the above invention, it becomes possible for an information provider to refuse to distribute the information to a terminal that the information provider does not want to give.

  Further, the distribution destination management device is connected to an access list management unit that manages an access permission list indicating a distribution destination that the information provider permits distribution of the information, and the storage unit includes the condition as: It is desirable to store permission conditions indicating that the change of the distribution destination terminal according to the change request is permitted when the changed distribution destination terminal is described in the access permission list.

  According to said invention, it becomes possible to distribute the information with respect to the terminal which the information provider has permitted distribution of information.

  The storage unit preferably stores a rejection condition indicating that the change of the distribution destination is rejected as the condition.

  According to said invention, it becomes possible to refuse changing a delivery destination.

  Further, the distribution destination management device is connected to an access list management unit that manages an access permission list indicating a distribution destination that the information provider permits distribution of the information, and the storage unit includes the condition as When the change request is transmitted from a distribution destination described in the access permission list, it is desirable to store a permission condition indicating that the change of the distribution destination terminal according to the change request is permitted.

  According to said invention, it becomes possible to permit the change request from the reliable delivery destination.

  In addition, it is preferable that a change history of the distribution destination is managed, and the storage unit stores, as the condition, a determination condition indicating that the change destination terminal can be changed based on the change history. .

  According to the above invention, it becomes possible to limit double and triple proxy monitoring.

  In addition, the distribution destination management apparatus is connected to an access list management unit that manages an access permission list indicating a distribution destination terminal before change, and a proxy list indicating a distribution destination terminal after change is managed. desirable.

  According to the above invention, it is possible to separately manage the list of terminals before the change and the list of terminals after the change.

  In addition, the change request requests that the delivery destination terminal be changed for a predetermined period, and when the changed delivery destination terminal is indicated in the proxy list and the predetermined period elapses, the delivery destination is changed. It is desirable to restore it.

  According to the above invention, when the predetermined period elapses, the delivery destination automatically returns. For this reason, it is possible to reduce the trouble of returning the delivery destination.

  Further, the program of the present invention provides the information provision to a computer connected to a storage unit that stores a condition set by the information provider using the information provider terminal and indicating whether or not the distribution destination terminal can be changed. A program for executing a delivery destination management process for changing the delivery destination terminal based on a change request for changing a delivery destination terminal of information held by the user terminal, and a reception process for accepting the change request; A determination process for determining whether to permit a change of a delivery destination requested by the change request based on a condition stored in the storage unit, and when the change of the delivery destination is permitted, In response, the computer is caused to execute a delivery destination management process including a change process for changing a delivery destination terminal.

  According to the above invention, it is possible to cause a computer to execute the delivery destination management method.

  According to the present invention, it is possible to quickly change the delivery destination.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a block diagram showing a distribution destination management apparatus according to the first embodiment of the present invention. Furthermore, FIG. 1 is a block diagram showing a presence system including the distribution destination management apparatus.

  In FIG. 1, a presence system includes a presence service unit 1, an authority delegation request generation unit (change request generation unit) 2, a temporary access management unit (distribution destination management device) 3, an information provider terminal 4, and a receiver. A terminal 5a and a substitute terminal 5b are included.

  Presence service unit 1 includes an access list management unit 1a and a buddy list management unit 1b.

  The authority delegation request generation unit 2 includes a buddy selection unit 2a, an authority delegation destination determination unit 2b, and an authority delegation request transmission unit 2c. In the following, the buddy selection unit 2a is referred to as “selection unit 2a”, the authority delegation destination determination unit 2b is referred to as “determination unit 2b”, and the authority delegation request transmission unit 2c is referred to as “transmission unit 2c”.

  The temporary access management unit 3 includes an authority delegation request receiving unit 3a, a storage unit 3b, a proxy availability determination unit 3c, and an access list rewriting unit 3d. In the following, the authority delegation request receiving unit 3a is referred to as “receiving unit 3a”, the proxy availability determining unit 3c is referred to as “determining unit 3c”, and the access list rewriting unit 3d is referred to as “rewriting unit 3d”.

  The information provider terminal (presentity) 4 is used by the information provider. The information provider terminal 4 has information (presence information) provided by the information provider.

  The receiver terminal (watcher) 5 a receives information held by the information provider terminal 4 and monitors the information provider terminal 4.

  The agent terminal (agent watcher) 5b receives the information received by the receiver terminal 5a on behalf of the receiver terminal 5a and monitors the information provider terminal 4.

  FIG. 1 shows an access list management unit 1a and a buddy list management unit 1b related to the present invention among the functions of a normal presence service unit 1 (presence system).

  The temporary access management unit 3 excluding the storage unit 3b may be realized by a computer that reads a program recorded in a memory and executes the read program. This program causes the computer to execute the delivery destination management method executed by the temporary access management unit 3.

  The access list management unit 1a indicates a distribution destination (watcher) permitted to distribute information held by the information provider at the information provider terminal and a distribution destination (watcher) prohibited from distribution by the information provider. Manage access lists.

  FIG. 2 is an explanatory diagram showing an example of an access list managed by the access list management unit 1a.

  In FIG. 2, the access list management unit 1a manages the presentity P1 access list 1a1, the presentity P2 access list 1a2, and the presentity P3 access list 1a3. The number of access lists is not limited to three and can be changed as appropriate.

  Each access list 1a1, 1a2, 1a3 includes an access permission list 1a1a and an access denial list 1a1b. Each access list 1a1, 1a2, 1a3 may include only one of the access permission list 1a1a and the access denial list 1a1b.

  The access permission list 1a1a includes a watcher (access permission watcher) permitted to distribute information by a presentity (specifically, an information provider using the presentity), and a watcher to which the distribution destination authority is delegated by the watcher. (Authority delegation destination watcher). Note that the access permission list 1a1a may indicate only the access permission watcher.

  The access denial list 1a1b indicates a watcher (access denial watcher) that the presentity (specifically, an information provider using the presentity) prohibits the distribution of information.

  Returning to FIG. 1, the buddy list management unit 1b manages the buddy list.

  FIG. 3 is an explanatory diagram showing an example of a buddy list managed by the buddy list management unit 1b.

  In FIG. 3, a buddy list management unit 1b manages a buddy list 1b1 for watcher W1, a buddy list 1b2 for watcher W2, and a buddy list 1b3 for watcher W3. The number of buddy lists is not limited to three and can be changed as appropriate.

  Returning to FIG. 1, the presence service unit 1 obtains presence information of the presentity (information provider terminal 4) based on the access list and the buddy list, as a watcher (recipient terminal 5 a) or an agent watcher (agent). To the terminal 5b).

  For example, the presence service unit 1 reads out buddies (presentities) shown in the buddy list.

  Subsequently, the presence service unit 1 determines whether the read presentity permits distribution of presence information to the watcher of the owner of the buddy list with reference to the access list.

  The presence service unit 1 distributes the presence information of the buddy to the watcher permitted to distribute by the buddies (presentity) shown in the buddy list.

  The authority delegation request generation unit 2 is an example of a change request generation unit. The authority delegation request generation unit 2 is used by a watcher, a user who has an access right to the watcher's buddy list, or an application having the access right, and can also access the buddy list management unit 1b.

  The authority delegation request generation unit 2 gives the authority to receive the presence information of the buddies shown in the buddy list from the watcher (recipient terminal 5a) who is the owner of the buddy list to the proxy watcher (proxy) The authority delegation request (change request) for requesting the change to the user terminal 5b) is generated.

  In other words, the authority delegation request generation unit 2 generates an authority delegation request for requesting to change the distribution destination of the buddy presence information indicated in the buddy list from the watcher of the owner of the buddy list to the substitute terminal. To do.

  In addition, a delegation request is for a watcher (former watcher) that is allowed to monitor the status of a presentity to temporarily delegate its monitoring authority to another watcher (substitute watcher). It is demanding that.

  For example, the selection unit 2a accesses the buddy list management unit 1b according to an instruction from the watcher, and selects a buddy (presentity) that requests monitoring from the substitute watcher from the buddy list of the watcher.

  The determination unit 2b specifies a substitute watcher, for example, according to an instruction from the former watcher.

  The transmission unit 2c generates an authority delegation request indicating a pair of the original watcher and the proxy watcher (authority delegation destination watcher) determined by the determination unit 2b for each buddy selected by the selection unit 2a. The transmission unit 2 c transmits the authority delegation request to the reception unit 3 a of the temporary access management unit 3.

  FIG. 4 is an explanatory diagram showing an example of the authority delegation request.

  In FIG. 4, the authority delegation request 21 indicates a set of an original watcher 21b and a substitute watcher 21c for each presentity 21a. The presentity 21a is selected by the selection unit 2a. The former watcher 21b is the watcher of the owner of the buddy list in which the presentity 21a was shown. The proxy watcher 21c is determined by the determination unit 2b.

  Returning to FIG. 1, the temporary access management unit 3 is an example of a distribution destination management apparatus.

  The temporary access management unit 3 manages changes in the distribution destination of presence information. Specifically, the temporary access management unit 3 changes the access list managed by the presence access unit 1 based on the authority delegation request received from the authority delegation request generation unit 2.

  The receiving unit 3a receives the authority delegation request transmitted by the transmitting unit 2c. The receiving unit 3a outputs the received authority delegation request to the determining unit 3c.

  The storage unit 3b stores a condition that is set by the information provider that uses the presentity and indicates whether or not the distribution destination of the information that the presentity has can be changed.

  For example, the storage unit 3b stores a refusal condition indicating that all changes of the delivery destination to the substitute watcher are rejected.

  Further, the storage unit 3b stores a refusal condition indicating that the change of the distribution destination to the substitute watcher is refused when the substitute watcher is described in the access denial list.

  Further, the storage unit 3b stores permission conditions indicating that the change of the distribution destination to the substitute watcher is permitted when the substitute watcher is described in the access permission list.

  In addition, the storage unit 3b stores permission conditions indicating that, when an authority delegation request is transmitted from a distribution destination (watcher) described in the access permission list, a change of the distribution destination to the proxy watcher is permitted. To do.

  Note that these conditions may be set differently for each presentity.

  Based on the condition stored in the storage unit 3b, the determination unit 3c determines whether to permit the change of the distribution destination requested by the authority delegation request output from the reception unit 3a.

  For example, when the storage unit 3b stores a rejection condition indicating that all changes to the delivery destination to the substitute watcher are rejected, the determination unit 3c rejects all changes to the delivery destination to the substitute watcher.

  Further, when the storage unit 3b stores a rejection condition indicating that the change of the delivery destination to the proxy watcher is rejected when the proxy watcher is described in the access denial list, the determination unit 3c When the substitute watcher is listed in the access denial list, the change of the delivery destination to the substitute watcher is refused.

  Further, when the storage unit 3b stores permission conditions indicating that the change of the delivery destination to the proxy watcher is permitted when the proxy watcher is described in the access permission list, the determination unit 3c When a substitute watcher is listed in the access permission list, change of a delivery destination to the substitute watcher is permitted.

  Further, when the storage unit 3b stores a permission condition indicating that when the authority delegation request is transmitted from the watcher described in the access permission list, the change of the distribution destination to the proxy watcher is permitted. When the authority delegation request is transmitted from the watcher described in the access permission list, the determination unit 3c permits the distribution destination to be changed to the proxy watcher.

  The determination unit 3c outputs the determination result and the authority transfer request to the rewriting unit 3d.

  When the determination unit 3c determines that the change of the distribution destination is permitted, the rewriting unit 3d changes the distribution destination of the presentity presence information indicated in the authority delegation request from the original watcher to the substitute watcher.

  Specifically, the rewriting unit 3d selects the presentity access permission list (see FIG. 2) indicated in the authority delegation request.

  The rewriting unit 3d searches the selected access permission list for the original watcher indicated in the authority transfer request.

  The rewriting unit 3d writes the proxy watcher indicated in the authority delegation request in the field of the authority delegation destination watcher corresponding to the retrieved original watcher.

  If the determination unit 3c determines that the change of the distribution destination is permitted when the access permission list 1a1a indicates only the access permission watcher, the rewrite unit 3d displays the original watcher indicated as the access permission watcher in the access permission list 1a1a. To the proxy watcher.

  If the determination unit 3c determines that the change of the delivery destination is permitted when the access permission list 1a1a indicates only the access permission watcher, the rewrite unit 3d does not delete the original watcher and does not delete the original watcher. May be added to

  If the substitute watcher is already shown in the access permission list 1a1a when the determination unit 3c determines that the change of the distribution destination is permitted, the rewrite unit 3d does not change the access permission list 1a1a.

  When the determination unit 3c determines that the change of the delivery destination is permitted and the proxy watcher is included in the access denial list, the rewrite unit 3d deletes the proxy watcher from the access denial list and performs the proxy Add watchers to the permissions list.

  Note that the access list management unit 1a and the buddy list management unit 1b may be centrally managed by a server or distributedly managed by clients depending on the presence service implementation method.

  Similarly, the authority delegation request generation unit 2 and the temporary access management unit 3 may be centrally managed by a server or distributedly arranged at clients.

  FIG. 5 is a block diagram illustrating an example where the presence service is a server centralized management model. In FIG. 5, the same components as those shown in FIG.

  In FIG. 5, the access list management unit 1 a and the buddy list management unit 1 b are centrally managed by the presence server 1. The presence server 1 is an example of a presence service unit.

  The temporary access management unit 3 and the authority delegation request generation unit 2 are also centrally managed by the presence server 1.

  In the configuration shown in FIG. 5, each function (selection unit 2 a, determination unit 2 b, and transmission unit 2 c) of the authority delegation request generation unit 2 receives a request from the receiver terminal (watcher i) 5 via the Web interface 6. And process the request.

  In the configuration shown in FIG. 5, one temporary access management unit 3 processes all authority transfer requests (proxy monitoring requests) from each watcher.

  FIG. 6 is a block diagram illustrating an example where the presence service is a distributed management model. In FIG. 6, the same components as those shown in FIG.

  In FIG. 6, the access list management unit 1aa is included in the presentity P, and the access list management unit 1ab is included in the presentity Q. The buddy list management unit 1ba is included in the watcher X, and the buddy list management unit 1bb is included in the watcher Y.

  The temporary access management unit 31 is included in the presentity P, and the temporary access management unit 32 is included in the presentity Q. The authority delegation request generation unit 2 is also managed by individual clients (watchers). Presentities P and Q correspond to the information provider terminal 4 shown in FIG. The watcher X corresponds to the recipient terminal 5a shown in FIG. 1, and the watcher Y corresponds to the agent terminal 5b shown in FIG.

  In the configuration shown in FIG. 6, the authority delegation request of the watcher is generated by the authority delegation request generation unit 2 attached to each watcher client, and thereafter, to the temporary access management unit 3 attached to each presentity client. Sent individually.

  Next, the operation of the first embodiment will be described.

  In step 101, the selection unit 2a accesses the buddy list management unit 1b according to an instruction from the original watcher, and selects a buddy for which the proxy watcher requests monitoring from the buddy list of the original watcher.

  When the buddy is selected, the determination unit 2b executes Step 102.

  In step 102, the determination unit 2b determines a proxy watcher to which the authority to receive (monitor) the buddy information is delegated from the former watcher.

  For example, the determination unit 2b determines a proxy watcher as follows.

  The determination unit 2b receives an identifier indicating the proxy witcher from the original watcher, and determines the proxy watcher based on the identifier.

  Note that the determination unit 2b may provide a list showing proxy watcher candidates to the original watcher, and determine a candidate selected by the user of the original watcher from the list as the proxy watcher.

  Further, the determination unit 2b may automatically determine a substitute watcher according to a program. For example, the determination unit 2b selects a buddy at random from buddies managed by the buddy list management unit 1b, and executes a process of determining the selected buddy as a substitute watcher according to a program.

  Note that the order of step 101 and step 102 may be reversed.

  When the selection of the buddy and the substitute watcher is completed, the transmission unit 2c executes Step 103.

  In step 103, the transmission unit 2c generates an authority delegation request (see FIG. 4) indicating a pair of the original watcher and the selected substitute watcher for each buddy selected by the selection unit 2a. The transmission unit 2 c transmits the authority delegation request to the reception unit 3 a of the temporary access management unit 3.

  When the authority delegation request is transmitted, the receiving unit 3a executes Step 104.

  In step 104, the reception unit 3a receives the authority delegation request and outputs the authority delegation request to the determination unit 3c.

  When the determination unit 3c receives the authority delegation request, the determination unit 3c executes Step 105.

  In step 105, the determination unit 3c determines whether or not to permit the change of the distribution destination requested by the authority delegation request based on the condition stored in the storage unit 3b.

  For example, when the storage unit 3b stores a rejection condition indicating that all changes to the delivery destination to the substitute watcher are rejected, the determination unit 3c rejects all changes to the delivery destination to the substitute watcher.

  Further, when the storage unit 3b stores a rejection condition indicating that the change of the delivery destination to the proxy watcher is rejected when the proxy watcher is described in the access denial list, the determination unit 3c When the substitute watcher is listed in the access denial list, the change of the delivery destination to the substitute watcher is refused.

  Further, when the storage unit 3b stores permission conditions indicating that the change of the delivery destination to the proxy watcher is permitted when the proxy watcher is described in the access permission list, the determination unit 3c When a substitute watcher is listed in the access permission list, change of a delivery destination to the substitute watcher is permitted.

  Further, when the storage unit 3b stores a permission condition indicating that when the authority delegation request is transmitted from the watcher described in the access permission list, the change of the distribution destination to the proxy watcher is permitted. When the authority delegation request is transmitted from the watcher described in the access permission list, the determination unit 3c permits the distribution destination to be changed to the proxy watcher.

  The determination unit 3c outputs the determination result and the authority delegation request to the rewriting unit 3d.

  When the rewriting unit 3d receives the determination result and the authority delegation request, it executes Step 106.

  In step 106, when the determination unit 3c determines that the change of the distribution destination is permitted, the rewriting unit 3d changes the distribution destination of the presence information of the presentity indicated in the authority delegation request from the original watcher to the proxy watcher.

  Specifically, the rewriting unit 3d selects the presentity access permission list (see FIG. 2) indicated in the authority delegation request. The rewriting unit 3d searches the selected access permission list for the original watcher indicated in the authority transfer request. The rewriting unit 3d writes the proxy watcher indicated in the authority delegation request in the field of the authority delegation destination watcher corresponding to the retrieved original watcher.

  If the determination unit 3c determines that the change of the distribution destination is permitted when the access permission list 1a1a indicates only the access permission watcher, the rewrite unit 3d displays the original watcher indicated as the access permission watcher in the access permission list 1a1a. To the proxy watcher.

  If the determination unit 3c determines that the change of the delivery destination is permitted when the access permission list 1a1a indicates only the access permission watcher, the rewrite unit 3d does not delete the original watcher and does not delete the original watcher. May be added to

  If the substitute watcher is already shown in the access permission list 1a1a when the determination unit 3c determines that the change of the distribution destination is permitted, the rewrite unit 3d does not change the access permission list 1a1a.

  When the determination unit 3c determines that the change of the delivery destination is permitted and the proxy watcher is included in the access denial list, the rewrite unit 3d deletes the proxy watcher from the access denial list and performs the proxy Add watchers to the permissions list.

  After that, when the substitute watcher uses the presence service and issues a status notification request (SUBSCRIBE) from the presentity, the rewritten access list is used for access control in the presence service, and buddy information is sent to the substitute watcher. be delivered.

  In order to cancel the authority delegation request, an authority delegation request from the authority delegation destination watcher (proxy watcher) to the authority delegation source watcher (original watcher) may be issued.

  Next, the operation when the presence service is configured in a distributed model will be described.

  FIG. 7 is a block diagram for explaining the operation when the presence service is configured in a distributed model.

  In FIG. 7, the configuration of each of the presentities P1 to P4 is the same as the configuration of the presentity P shown in FIG. The presentities P1 to P4 correspond to the information provider terminal 4 shown in FIG.

  The configuration of each of the watchers W1 and W2 is the same as that of the watcher X shown in FIG. The watcher W1 corresponds to the recipient terminal 5a shown in FIG. 1, and the watcher W2 corresponds to the agent terminal 5b shown in FIG.

  In the following, for ease of explanation, operations in the following cases will be described.

  Watcher W1 owns buddy list B1. In the buddy list B1, presentities P1 to P3 are described.

  Watcher W2 owns buddy list B2. In the buddy list B2, presentities P1 to P4 are described.

  The presentity P1 has an access permission list A1 and an access denial list D1. In the access permission list A1, the watcher W1 is described. The access denial watcher is not described in the access denial list D1.

  The presentity P2 has an access permission list A2 and an access denial list D2. In the access permission list A2, watchers W1 and W2 are described. In the access denial list D2, no access denial watcher is described.

  The presentity P3 has an access permission list A3 and an access denial list D3. Watcher W1 is described in access permission list A3. The watcher W2 is described in the access denial list D3.

  Presentity P4 owns access permission list A4 and access denial list D4. Watcher W2 is described in access permission list A4. The access denied watcher is not described in the access denied list D4.

  The watcher W1 requests the watcher W2 to perform monitoring of the presentity P1, the presentity P2, and the presentity P3 included in the buddy list B1 of the watcher W1. In other words, the watcher W1 designates the watcher W2 as a substitute watcher.

  Each storage unit 3b of the presentity P1, the presentity P2, and the presentity P3 stores permission conditions for permitting proxy monitoring by the proxy watcher if the proxy watcher is not included in the access denial list. In other words, the permission condition indicates that if the proxy watcher is not included in the access denial list, the distribution destination is permitted to be changed to the proxy watcher.

  Also, when the presentity P1, the presentity P2, and the presentity P3 are permitted to perform proxy monitoring, the presenter P1 does not replace the original watcher with the proxy watcher on the access permission list, but adds the proxy watcher to the access permission list.

  In step 201, the selection unit 2a of the watcher W1 selects the presentity P1, the presentity P2, and the presentity P3 among the buddies (presentities) included in the buddy list B2 of the watcher W1.

  When the presentity is selected, the determination unit 2b of the watcher W1 executes Step 202.

  In step 202, the determination unit 2b of the watcher W1 designates the watcher W2 as an alternate watcher.

  Note that the order of step 201 and step 202 may be reversed.

  When the designation of the presentity and the substitute watcher is completed, the transmission unit 2c of the watcher W1 executes Step 203.

  In step 203, the transmission unit 2c of the watcher W1 requests the presenter P1, the presentity P2, and the presentity P3 to delegate the monitoring authority by the watcher W1 (former watcher) to the watcher W2 (substitute watcher). An authority delegation request (see FIG. 4) is transmitted.

  When the authority delegation request is transmitted, the receiving unit 3a of the presentity P1 executes Step 204.

  In step 204, the receiving unit 3a of the presentity P1 receives the authority delegation request and outputs the authority delegation request to the determination unit 3c of the presentity P1.

  When receiving the authority delegation request, the determination unit 3c of the presentity P1 executes Step 205.

  In step 205, the determination unit 3c of the presentity P1 determines whether or not the change of the distribution destination requested by the authority delegation request is permitted based on the condition stored in the storage unit 3b of the presentity P1.

  Specifically, the determination unit 3c of the presentity P1 confirms that the watcher W2 as the substitute watcher is not included in the access denial list D1, and then permits the distribution destination to be changed from the watcher W1 to the watcher W2. To do.

  The determination unit 3c of the presentity P1 outputs the determination result and the authority delegation request to the rewrite unit 3d of the presentity P1.

  When the rewriting unit 3d of the presentity P1 receives the determination result and the authority delegation request, it executes Step 206.

  In step 206, when the determination unit 3c of the presentity P1 determines that the change of the distribution destination is permitted, the rewrite unit 3d of the presentity P1 determines that the distribution destination of the presence information of the presentity indicated in the authority delegation request is from the original watcher. The proxy watcher W2 is added to the access permission list A1 of the presentity P1 so as to be changed to the proxy watcher.

  On the other hand, when the receiving unit 3a of the presentity P2 receives the authority delegation request, the presentity P2 operates in the same manner as the presentity P1. In addition, since the watcher W2 is described in advance in the access permission list A2 of the presentity P2, the access permission list A2 is not changed.

  On the other hand, when the receiving unit 3a of the presentity P3 receives the authority delegation request, the presentity P3 operates in the same manner as the presentity P1. Since the watcher W2 is described in the access denial list D3 of the presentity P3, the access permission list A2 is not changed.

  According to the present embodiment, the following effects can be obtained.

  A watcher can delegate its monitoring authority to another watcher (substitute watcher) quickly and safely, such as when the presentity cannot be temporarily monitored or is urgent.

  According to the present embodiment, the following operational effects can be obtained.

  The determination unit 3c determines whether the distribution destination can be changed based on the conditions stored in the storage unit 3b. The conditions stored in the storage unit 3b are set by the information provider. Therefore, whether or not the distribution destination can be changed can be determined based on the policy of the information provider, and whether or not the information provider permits distribution of information to the watcher at the change destination when the distribution destination is changed. It is not necessary to perform the work of determining Therefore, it is possible to quickly change the distribution destination (watcher).

  In the present embodiment, the rewrite unit 3d describes the proxy watcher in the access permission list when the change of the distribution destination is permitted. In this case, it becomes possible to manage the change of the delivery destination by the access permission list.

  Further, in the present embodiment, the storage unit 3b stores a rejection condition indicating that, when the proxy watcher is described in the access denial list, the change of the delivery destination to the proxy watcher is rejected. In this case, it becomes possible for the information provider to refuse to distribute the information to a substitute watcher who does not want to give the information.

  Further, in the present embodiment, the storage unit 3b stores permission conditions indicating that the change of the distribution destination to the substitute watcher is permitted when the substitute watcher is described in the access permission list. In this case, it becomes possible to distribute the information to a proxy watcher that the information provider permits the distribution of information.

  Further, in the present embodiment, the storage unit 3b stores a rejection condition indicating that all changes of the delivery destination to the substitute watcher are rejected. In this case, it is possible to refuse to change the delivery destination to the substitute watcher.

  Further, in the present embodiment, the storage unit 3b sets a permission condition indicating that the change of the delivery destination to the substitute watcher is permitted when the authority delegation request is transmitted from the original watcher described in the access permission list. Store. In this case, it is possible to permit authority delegation requests from reliable delivery destinations.

  Next, a second embodiment will be described.

  FIG. 8 is a block diagram illustrating a distribution destination management apparatus according to the second embodiment. Furthermore, FIG. 8 is a block diagram showing a presence system including the distribution destination management apparatus. In FIG. 8, the same components as those shown in FIG.

  The main difference between the first embodiment and the second embodiment is that the temporary access management unit 30 of the second embodiment includes a proxy list management unit (hereinafter referred to as “management unit”) 3e.

  The management unit 3e is an example of a history management unit. The management unit 3e manages the change history of the delivery destination.

  The management unit 3e manages, for each presentity, a proxy list (change history) indicating a set of original watchers and proxy watchers to which authority transfer is permitted by the determination unit 3c.

  FIG. 9 is an explanatory diagram showing an example of a proxy list and an access list.

  In FIG. 9, the management unit 3e manages the presentity P1 substitution list 3e1, the presentity P2 substitution list 3e2, and the presentity P3 substitution list 3e3. The number of substitution lists is not limited to three and can be changed as appropriate.

  Each proxy list 3e1, 3e2, 3e3 shows a set of authority delegation source watcher (original watcher) and authority delegation destination watcher (delegation watcher).

  The access list management unit 1a manages the presentity P1 access list 1a4, the presentity P2 access list 1a5, and the presentity P3 access list 1a6. The number of access lists is not limited to three and can be changed as appropriate.

  Each access list 1a4, 1a5, 1a6 includes an access permission list 1a4a and an access denial list 1a4b. Each access list 1a4, 1a5, 1a6 may include only one of the access permission list 1a4a and the access denial list 1a4b.

  The access permission list 1a4a indicates an access permission watcher that the presentity has permitted distribution of information. The access refusal list 1a4b indicates an access refusal watcher whose presentity has prohibited the distribution of information.

  The proxy list is saved until the proxy monitoring is completed. The proxy list is used to return the access list to the state before the proxy monitoring is executed at the end of the proxy monitoring.

  Further, when the content of the access list is changed by the information provider during the proxy monitoring, the changed content is prioritized. For this reason, the access list is not changed even when the proxy monitoring ends.

  For example, when the delegation source watcher is added to the access denial list during the proxy monitoring, the delegation source watcher is not added to the access permission list after the proxy monitoring is completed.

  In addition, the storage unit 3b may store a determination condition indicating that it is determined based on the proxy list whether the delivery destination can be changed from the proxy watcher to another proxy watcher. In this case, the determination unit 3c can use the proxy list information to restrict the proxy watcher from being proxyed by another proxy watcher.

  FIG. 10 is a block diagram showing an example where the presence service of the second embodiment is a server centralized management model. In FIG. 10, the same components as those shown in FIGS. 8 and 5 are denoted by the same reference numerals.

  FIG. 11 is a block diagram showing an example where the presence service of the second embodiment is a distributed management model. In FIG. 11, the same components as those shown in FIGS. 8 and 6 are denoted by the same reference numerals.

  Next, the operation of the second embodiment will be described. In the following, the operation different from the first embodiment will be mainly described.

  The determination unit 3c outputs the determination result and the authority delegation request (see FIG. 4) to the rewrite unit 3d and the management unit 3e.

  If the determination unit 3c determines that the change of the delivery destination is permitted, the management unit 3e adds the content indicated in the authority transfer request to the proxy list.

  After that, when the substitute watcher uses the presence service and issues a status notification request (SUBSCRIBE) from the presentity, the rewritten access list is used for access control in the presence service, and buddy information is sent to the substitute watcher. be delivered.

  After that, when the former watcher issues an authority delegation release request in the same procedure, the determination unit 3c invalidates the authority delegated to the proxy watcher, and the management unit 3e transmits the proxy watcher from the original watcher to the proxy watcher. Delete the information indicating delegation of authority to.

  Next, an operation when the presence service of the second embodiment is configured by a distributed model will be described.

  FIG. 12 is a block diagram for explaining the operation when the presence service of the second embodiment is configured in a distributed model.

  In FIG. 12, the configuration of each of the presentities P1 to P4 is the same as the configuration of the presentity P shown in FIG. Each configuration of the watchers W1 and W2 is the same as that of the watcher X shown in FIG.

  In the following, for ease of explanation, operations in the following cases will be described.

  Watcher W1 owns buddy list B1. In the buddy list B1, presentities P1 to P3 are described.

  Watcher W2 owns buddy list B2. In the buddy list B2, presentities P1 to P4 are described.

  The presentity P1 has an access permission list A1, an access denial list D1, and a proxy list S1. In the access permission list A1, the watcher W1 is described. The access denial watcher is not described in the access denial list D1. Nothing is described in the proxy list S1.

  The presentity P2 has an access permission list A2, an access denial list D2, and a proxy list S2. In the access permission list A2, watchers W1 and W2 are described. In the access denial list D2, no access denial watcher is described. Nothing is described in the proxy list S2.

  The presentity P3 has an access permission list A3, an access denial list D3, and a proxy list S3. Watcher W1 is described in access permission list A3. The watcher W2 is described in the access denial list D3. Nothing is described in the proxy list S3.

  The presentity P4 has an access permission list A4, an access denial list D4, and a proxy list S3. Watcher W2 is described in access permission list A4. The access denied watcher is not described in the access denied list D4. Nothing is described in the proxy list S4.

  The watcher W1 requests the watcher W2 to perform monitoring of the presentity P1, the presentity P2, and the presentity P3 included in the buddy list B1 of the watcher W1. In other words, the watcher W1 designates the watcher W2 as a substitute watcher.

  Each storage unit 3b of the presentity P1, the presentity P2, and the presentity P3 stores permission conditions for permitting proxy monitoring by the proxy watcher if the proxy watcher is not included in the access denial list. In other words, the permission condition indicates that if the proxy watcher is not included in the access denial list, the distribution destination is permitted to be changed to the proxy watcher.

  Also, when the presentity P1, the presentity P2, and the presentity P3 are permitted to perform proxy monitoring, the presenter P1 does not replace the original watcher with the proxy watcher on the access permission list, but adds the proxy watcher to the access permission list.

  In the following, the operation different from the first embodiment will be mainly described.

  The determination unit 3c of the presentity P1 confirms that the watcher W2 serving as the substitute watcher is not included in the access denial list D1, and permits the distribution destination to be changed from the watcher W1 to the watcher W2.

  The determination unit 3c of the presentity P1 outputs the determination result and the authority delegation request to the rewrite unit 3d of the presentity P1 and the management unit 3e of the presentity P1.

  If the determination unit 3c of the presentity P1 determines that the change of the delivery destination is permitted, the management unit 3e of the presentity P1 adds the content indicated in the authority delegation request to the proxy list S1. For example, the management unit 3e of the presentity P1 adds that “the watcher W1 has delegated authority to the watcher W2” to the proxy list S1.

  On the other hand, when the receiving unit 3a of the presentity P2 receives the authority delegation request, the presentity P2 operates in the same manner as the presentity P1. Since the watcher W2 is described in advance in the access permission list A2 of the presentity P2, the access permission list A2 and the proxy list S2 are not changed. Note that “the watcher W1 has delegated authority to the watcher W2” may be added to the proxy list S2 of the presentity P2.

  On the other hand, when the receiving unit 3a of the presentity P3 receives the authority delegation request, the presentity P3 operates in the same manner as the presentity P1. Since the watcher W2 is described in the access denial list D3 of the presentity P3, the access permission list A2 and the proxy list S3 are not changed.

  According to this embodiment, the access list management unit 1a manages the access list, and the management unit 3e manages the proxy list. For this reason, the access list and the proxy list can be managed separately.

  Note that if the storage unit stores a determination condition indicating that the delivery destination from the proxy watcher to another proxy watcher can be changed based on the proxy list, the determination unit 3c can determine whether the proxy is a double or triple proxy. It becomes possible to limit the monitoring.

  Next, a third embodiment will be described.

  FIG. 13 is a block diagram illustrating a distribution destination management apparatus according to the third embodiment. Furthermore, FIG. 13 is a block diagram showing a presence system including the distribution destination management apparatus. In FIG. 13, the same components as those shown in FIG.

  The main difference between the third embodiment and the second embodiment is that the management section 3e, the determination section 3c, and the storage section 3b of the second embodiment exist in the access list management section 1a. Furthermore, the access list management unit 1a also serves as the access list rewriting unit 3d.

  In the third embodiment, the access list manager 1a can manage an access list (including an access permission list and an access denial list) and a proxy list. The determination unit 3c is included in the access list management unit 1a. Therefore, the determination unit 3c can immediately recognize a change in the access list.

  In the third embodiment, the determination unit 3c can flexibly change the determination of whether or not to change the distribution destination to the substitute watcher with respect to the change of the access list.

  For example, when it is necessary to consider whether or not the watcher is included in the access denial list when determining whether or not to add a watcher to the delegation destination watcher, the determination unit 3c updates the access denial list. Each time it is done, the legitimacy of the delegation watcher can be verified.

  In the second and third embodiments, the proxy watcher is managed as a proxy list separately from the regular access list. For this reason, for example, if the proxy list management unit 3e confirms the duration of the contents described in the proxy list, the risk of continuously giving the subscribing authority to the proxy watcher after the proxy monitoring is reduced is reduced. Can do.

  In the second embodiment and the third embodiment, it is possible to grasp the hierarchization of proxy monitoring by managing the proxy list. For this reason, double and triple proxy monitoring can be limited.

  In addition, the first and second embodiments can be realized without changing the function of the existing presence service.

  In the above embodiment, the delegation monitoring is completed by the authority delegation source watcher issuing the authority delegation release request.

  However, the authority delegation request has information specifying the authority delegation period, and when the period ends, the management unit 3e may automatically cancel the authority delegation and return the delivery destination from the proxy watcher to the original watcher. .

  In this case, when a predetermined period elapses, the delivery destination automatically returns from the substitute watcher to the original watcher. For this reason, it is possible to reduce the trouble of returning the delivery destination.

  In the above embodiment, the case where there is one authority delegation destination watcher has been described. However, a plurality of authority delegation destination watchers may be designated.

  Alternatively, the rewrite unit 3d may wait for the access list to be rewritten until the right delegation destination watcher actually starts the proxy monitoring.

  For example, the user of the former watcher inputs timing information indicating the timing at which the proxy watcher actually starts the proxy monitoring to the transmission unit 2c.

  The transmission unit 2c generates an authority delegation request to which the timing information is added, and transmits the generated authority delegation request to the reception unit 3a.

  The transmitted authority transfer request is provided to the rewriting unit 3d via the receiving unit 3a and the determining unit 3c.

  When the rewriting unit 3d determines that the determination unit 3c permits the change of the distribution destination, the rewriting unit 3d rewrites the access list at the timing added to the authority delegation request.

  In this case, delegation of authority from the authority delegation source watcher to the authority delegation destination watcher can be performed without time interval.

  In each of the embodiments described above, the illustrated configuration is merely an example, and the present invention is not limited to the configuration.

  Further, this embodiment can be used in the following fields, for example.

  Temporarily request monitoring from another person in situations where it is necessary to constantly check the condition of the subject, such as the safety of a family living away from home, checking the health status of a home-care patient, or monitoring the operating status of equipment. You can use it if you want to. The present embodiment is particularly effective in a situation where a requesting partner cannot be specified.

It is the block diagram which showed the delivery destination management apparatus of 1st Example of this invention. It is explanatory drawing which showed an example of the access management part. It is explanatory drawing which showed an example of the buddy list management part. It is explanatory drawing which showed an example of the authority transfer request. It is the block diagram which showed the specific example of 1st Example. It is the block diagram which showed the other example of 1st Example. It is a block diagram for demonstrating operation | movement of the example shown in FIG. It is the block diagram which showed the delivery destination management apparatus of 2nd Example of this invention. It is explanatory drawing which showed an example of the proxy list management part and the access management part. It is the block diagram which showed the specific example of 2nd Example. It is the block diagram which showed the other example of 2nd Example. It is a block diagram for demonstrating operation | movement of the example shown in FIG. It is the block diagram which showed the delivery destination management apparatus of 3rd Example of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Presence service part 1a Access list management part 1b Buddy list management part 2 Authority delegation request production | generation part 2a Buddy selection part 2b Authority delegation destination determination part 2c Authority delegation request transmission part 3 Temporary access management part 3a Authority delegation request reception part 3b Storage part 3c Proxy availability determination unit 3d Access list rewriting unit 3e Proxy list management unit 4 Information provider terminal 5 Receiver terminal 6 Web interface P, Q Presentity X, Y Watcher

Claims (19)

A distribution destination management device that changes a terminal of a distribution destination based on a change request for changing a terminal of a distribution destination of information held by an information provider terminal;
A storage unit configured to store a condition indicating whether or not the distribution destination terminal can be changed, which is set by the information provider using the information provider terminal;
A reception unit that receives the change request;
A determination unit that determines whether or not to permit a change of a delivery destination requested by the change request received by the reception unit based on a condition stored in the storage unit;
A distribution destination management apparatus comprising: a change unit that changes a distribution destination terminal in response to the change request when the determination unit determines that the change of the distribution destination is permitted. In the delivery destination management apparatus according to claim 1,
The distribution destination management device is connected to an access list management unit that manages an access permission list indicating a distribution destination where the information provider permits distribution of the information,
When the determination unit determines that the change of the distribution destination is permitted, the change unit describes the changed distribution destination terminal in the access permission list. In the delivery destination management apparatus according to claim 1 or 2,
The delivery destination management device is connected to an access list management unit that manages an access denial list indicating a delivery destination from which the information provider refuses to deliver the information,
The storage unit stores, as the condition, a delivery destination management that stores a rejection condition indicating that a change of the delivery destination terminal is rejected when the changed delivery destination terminal is described in the access denial list. apparatus. In the delivery destination management apparatus according to claim 1 or 2,
The distribution destination management device is connected to an access list management unit that manages an access permission list indicating a distribution destination where the information provider permits distribution of the information,
The storage unit stores, as the condition, a permission condition indicating that the change of the distribution destination terminal according to the change request is permitted when the distribution destination terminal after the change is described in the access permission list. A delivery destination management device. In the delivery destination management apparatus according to claim 1 or 2,
The said storage part is a delivery destination management apparatus which stores the rejection condition which shows rejecting all the changes of the said delivery destination as said conditions. In the delivery destination management apparatus according to claim 1 or 2,
The distribution destination management device is connected to an access list management unit that manages an access permission list indicating a distribution destination where the information provider permits distribution of the information,
The storage unit, as the condition, indicates permission to permit change of a distribution destination terminal in response to the change request when the change request is transmitted from a distribution destination described in the access permission list. A delivery destination management device that stores conditions. In the delivery destination management apparatus according to claim 1 or 2,
A history management unit for managing a change history of the delivery destination;
The storage unit is a distribution destination management apparatus that stores, as the condition, a determination condition indicating that whether or not the distribution destination terminal can be changed is determined based on the change history. In the delivery destination management apparatus according to claim 1 or 2,
The distribution destination management device is connected to an access list management unit that manages an access permission list indicating a distribution destination terminal before change,
A distribution destination management apparatus further including a proxy list management unit that manages a proxy list indicating a terminal of a distribution destination after change. In the delivery destination management apparatus according to claim 8,
The change request requests to change the delivery destination terminal for a predetermined period,
The delivery list management unit is configured to restore the delivery destination when the predetermined period has elapsed after the changed delivery destination terminal is shown in the substitute list. A storage unit configured to store conditions indicating whether or not to change a delivery destination terminal set by an information provider using the information provider terminal; and a delivery destination terminal of information included in the information provider terminal A distribution destination management method performed by a distribution destination management apparatus that changes the terminal of the distribution destination based on a change request to change,
An accepting step for accepting the change request;
A determination step of determining whether to permit a change of a delivery destination requested by the change request based on a condition stored in the storage unit;
And a change step of changing a distribution destination terminal in response to the change request when the change of the distribution destination is permitted. The delivery destination management method according to claim 10,
The distribution destination management device is connected to an access list management unit that manages an access permission list indicating a distribution destination where the information provider permits distribution of the information,
In the changing step, when the change of the distribution destination is permitted, the distribution destination terminal after the change is described in the access permission list. The delivery destination management method according to claim 10 or 11,
The delivery destination management device is connected to an access list management unit that manages an access denial list indicating a delivery destination from which the information provider refuses to deliver the information,
The storage unit stores, as the condition, a delivery destination management that stores a rejection condition indicating that a change of the delivery destination terminal is rejected when the changed delivery destination terminal is described in the access denial list. Method. The delivery destination management method according to claim 10 or 11,
The distribution destination management device is connected to an access list management unit that manages an access permission list indicating a distribution destination where the information provider permits distribution of the information,
The storage unit stores, as the condition, a permission condition indicating that the change of the distribution destination terminal according to the change request is permitted when the distribution destination terminal after the change is described in the access permission list. Distribution destination management method. The delivery destination management method according to claim 10 or 11,
The said storage part is a delivery destination management method which stores the rejection condition which shows rejecting all the changes of the said delivery destination as said conditions. The delivery destination management method according to claim 10 or 11,
The distribution destination management device is connected to an access list management unit that manages an access permission list indicating a distribution destination where the information provider permits distribution of the information,
The storage unit, as the condition, indicates permission to permit change of a distribution destination terminal in response to the change request when the change request is transmitted from a distribution destination described in the access permission list. A destination management method that stores conditions. The delivery destination management method according to claim 10 or 11,
A history management step of managing a change history of the delivery destination,
The said storage part is a delivery destination management method which stores the judgment condition which shows judging whether the change of the said delivery destination terminal is possible based on the said change history as said conditions. The delivery destination management method according to claim 10 or 11,
The distribution destination management device is connected to an access list management unit that manages an access permission list indicating a distribution destination terminal before change,
A delivery destination management method further comprising an agency list management step of managing an agency list indicating a delivery destination terminal after the change. The delivery destination management method according to claim 17,
The change request requests to change the delivery destination terminal for a predetermined period,
A delivery destination management method further comprising a re-changing step of restoring the delivery destination when the predetermined period has elapsed after the changed delivery destination terminal is shown in the proxy list. The distribution destination of the information that the information provider terminal has in a computer connected to a storage unit that is set by the information provider that uses the information provider terminal and that indicates whether or not the distribution destination terminal can be changed. A program for executing a delivery destination management process for changing the delivery destination terminal based on a change request to change the terminal of
An acceptance process for accepting the change request;
A determination process for determining whether to permit a change of a delivery destination requested by the change request based on a condition stored in the storage unit;
When the change of the delivery destination is permitted, a program for causing the computer to execute a delivery destination management process including a change process of changing a delivery destination terminal in response to the change request.

Images