JP2011210261A - Information exchange system, resource list server and network load reduction method used for the them - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information exchange system reducing network loads by NOTIFY to be transmitted from a notifier of resources to a subscriber.SOLUTION: A resource list server 2 issues, on receiving a SUBSCRIBE request to a list, the SUBSCRIBE request to each of the resources included in the list, and on receiving the NOTIFY of states of the resources from the notifier 3 of the resources, transmits the NOTIFY to the subscriber 1 having subscription to the list in which the resources are included. When an update request to subscription in which the notifier 3 already exists is received, a NOTIFY with the empty content is transmitted from the resource list server 2 to the subscriber 1.

Description

  The present invention relates to an information exchange system, a resource list server, a network load reduction method used therefor, and a program thereof, and more particularly to a network load reduction between a subscriber and a notifier.

  Non-Patent Document 1 discloses a framework between a subscriber who observes a resource state for a certain period and a notifier that notifies the subscriber of a resource state. As an example of applying this framework, there is an example applied to a presence service (for example, see Non-Patent Document 2). Here, the presence service refers to a general system for managing the state of each resource, and its basic architecture is shown in Non-Patent Document 3. Note that the resource indicates an observation target for the subscriber to observe the state.

  In the case where the above subscribers are not observing only one resource but observing the state of a plurality of resources, in general, a SUBSCRIBE (registration, subscription) request (request) is individually requested for each resource. ) To the notifier, and the subscription (subscription) needs to be managed. Here, the subscription is a summary of the relationship between subscribers and notifiers, event packages to be used, and the like.

  However, (1) If subscriptions to multiple resources are started and updated simultaneously, the temporary traffic flowing through the network increases. (2) The notifier accepts the subscription update interval requested by the subscriber. If a frequent update is requested, the subscriber must issue a frequent SUBSCRIBE request. (3) An unnecessary NOTIFY if the notifier frequently notifies the status of the resource by the subscriber's SUBSCRIBE request. There is a problem that network traffic increases due to (notification).

  In order to solve these problems, as shown in FIG. 14, a resource list server that accepts SUBSCRIBE requests for a plurality of resources and issues one NOTIFY including the states of the plurality of resources has been proposed (for example, Non-Patent Documents 4 and 5). However, this method can reduce the network load due to the SUBSCRIBE request, but the network load due to NOTIFY and the processing load on the subscriber may also increase.

  On the other hand, a method of reducing the network load due to NOTIFY by filtering the status notification has also been proposed (see, for example, Non-Patent Documents 6 and 7), but the load on the back-end subscription from the resource list server to the resource It does not directly filter the contents of NOTIFY notified from the resource list server to the subscriber.

  Patent Document 1 below discloses a technology in which a presence server manages presence information from a presence supplier, and when a subscription request is received from a watcher, a notification of related presence information is transmitted to the watcher. Patent Document 2 discloses a technique for providing notification for each resource to notify one or a plurality of subscribers.

International Publication No. 2004/008178 US Patent Application Publication No. 2004/0205142

“Session Initiation Protocol (SIP) —Specific Event Notification 3. Node Behavior” [RFC (Request For Comments) 3265, June 2002]. “A Presence Event Package for the Session Initiation Protocol (SIP) Status of this Memo” (RFC3856, August 2004) “A Model for Presence and Instant Messaging” (RFC 2778, February 2000). "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists 4.Operation of List Subscriptions, 5.Using multipart / related to Convey Aggregate State" [IETF (Internet Engineering Task Force) Internet Draft, December 15,2004 (http: //Www.ietf.org/internet-drafts/draft-ietf-simple-event-list-07.txt)] “Extensible Markup Language (XML) Formats for Representing Resource Lists” [IETF Internet Draft, February 7, 2005 (http: //www.etfetred/t-et-t/t-et-t/t-et-t/t-et-t-t/t-t-t-t/t-t-t-t/t-t-t/t-t-t/t-t-t/t-t-t/t-t/t-t/t-t- .Txt)] “An Extensible Markup Language (XML) Based Format for Event Notification Filtering” [IETF Internet Draft, March 15, 2005-http://www.itet.//-. .Txt)] “Functional Description of Event Notification Filtering draft-ietf-simple-event-filter-funct-05” [IETF Internet Draft, March 15, 2005 (http://t./f-t/t-et/t. -Event-filter-funct-05.txt)]

  In the above-described conventional resource list server, in the case of the method described in Non-Patent Document 4, when a subscriber issues a SUBSCRIBE request to a list of resources managed by the resource list server, the status of resources included in the list Is included in the content of one NOTIFY.

  As a result, the method described in Non-Patent Document 4 can reduce the load on the network as compared to a case where a SUBSCRIBE request is issued for individual resources. Further, in the method described in Non-Patent Document 4, the resource list server can absorb the difference in the request for the subscription validity period and the NOTIFY transmission frequency between the subscriber and the resource notifier.

  However, in the case of the method described in Non-Patent Document 4 above, if the status of a plurality of resources included in the list is sent as the contents of one NOTIFY, the load on the network temporarily increases, and the subscriber receives it. The processing load for interpreting the contents of the NOTIFY is also increased. This problem cannot be solved by combining the techniques of Patent Documents 1 and 2 described above.

  Accordingly, an object of the present invention is to solve the above-described problems and to reduce the network load due to NOTIFY transmitted from a resource notifier to a subscriber, an information exchange system, a management server, a terminal device, and a network load used for them It is in providing the mitigation method and its program.

An information exchange system according to the present invention is an information exchange comprising a subscriber that observes a resource state for a certain period, a notifier that notifies the subscriber of the resource state, and a resource list server that manages the list of resources. A system,
The notifier includes means for monitoring the state of one or more resources, and notification means for notifying the resource list server of the state of the resource by NOTIFY,
The subscriber includes a SUBSCRIBE request transmitting unit configured to transmit a SUBSCRIBE request including designation information for designating a resource list including one or more resources to the resource list server;
The resource list server is included in the resource list when it receives a resource status holding means for receiving and holding the status of the resource notified by the NOTIFY from the notifier and a SUBSCRIBE request for the resource list. A means for issuing a SUBSCRIBE request for each resource, and a NOTIFY of the status of the resource from the notifier is included in the resource list for a subscriber who has a subscription to the resource list containing the resource And a means for transmitting a plurality of NOTIFYs having the state of the resource to be stored.

The resource list server according to the present invention includes a notifier including means for monitoring the state of one or more resources, a notification means for notifying the resource list server of the state of the resource by NOTIFY, and a resource including one or more resources A resource list server for managing a list of resources in an information exchange system comprising a subscriber including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request including designation information for designating a list to a resource list server,
Resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier;
Means for issuing a SUBSCRIBE request for each of the resources included in the resource list when a SUBSCRIBE request for the resource list is received;
When NOTIFY of the state of the resource is received from the notifier, a plurality of NOTIFYs including the state of the resource included in the resource list are transmitted to a subscriber who has a subscription to the resource list including the resource. Means.

The network load reduction method according to the present invention includes a notifier including means for monitoring the state of one or more resources, and a notification means for notifying the resource list server of the state of the resource by NOTIFY, and one or more resources. Network load reduction for use in a resource list server for managing a list of resources in an information exchange system comprising a subscriber including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request including a specification information for specifying a resource list to a resource list server A method,
The resource list server is provided with resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier,
When the resource list server receives a SUBSCRIBE request for the resource list, it receives a SUBSCRIBE request for each of the resources included in the resource list, and receives NOTIFY of the state of the resource from the notifier In this case, a process of transmitting a plurality of NOTIFYs including the state of the resource included in the resource list to a subscriber who has a subscription to the resource list including the resource is executed.

The program according to the present invention includes a notifier including means for monitoring the state of one or more resources, a notification means for notifying the resource list server of the state of the resource by NOTIFY, and a resource list including one or more resources. A program executed by a computer in a resource list server that manages the list of resources in an information exchange system comprising a subscriber including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request including specified information to be specified to a resource list server There,
The resource list server is provided with resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier,
When a SUBSCRIBE request for the resource list is received, a process for issuing a SUBSCRIBE request to each of the resources included in the resource list, and when the NOTIFY of the state of the resource is received from the notifier, the resource is included And a process of transmitting a plurality of NOTIFYs containing the state of the resource included in the resource list to a subscriber who has a subscription to the resource list.

  That is, the information exchange system of the present invention includes a subscriber that observes a resource state for a certain period, a notifier that notifies the subscriber of the resource state, and a resource list server that manages a list of resources. When a SUBSCRIBE (registration, subscription) request (request) for the list is received, the state of the resource included in the list is transmitted as the contents of individual NOTIFY (notification).

  More specifically, in the information exchange system of the present invention, when the resource list server receives a SUBSCRIBE request for a list, it issues a SUBSCRIBE request to each of the resources included in the list, and the resource notifier issues a resource. When NOTIFY in the state is received, NOTIFY is transmitted to a subscriber who has a subscription to the list including the resource.

  As a result, in the information exchange system of the present invention, when it is desired to individually receive a status notification from each resource, it is possible to combine SUBSCRIBE requests to a plurality of resources into one, so SUBSCRIBE for starting a subscription It is possible to reduce the load on the network when sending a request and when sending a SUBSCRIBE request for updating a subscription.

  In the information exchange system according to the present invention, instead of sending one NOTIFY having a large content, a plurality of NOTIFYs having a small content are sent to reduce the network load. Furthermore, in the information exchange system according to the present invention, by reducing the contents of one NOTIFY, it is possible to reduce the processing load for the subscriber to interpret the contents of NOTIFY. Furthermore, in the information exchange system of the present invention, the load on the network can be reduced by distributing the NOTIFY transmission timing.

  The present invention has an arrangement and operation as described below, thereby obtaining an effect that the network load due to NOTIFY transmitted from the resource notifier to the subscriber can be reduced.

It is a block diagram which shows the structure of the information exchange system by this invention. It is a figure which shows the list table example of the list management part by the 1st Embodiment of this invention. It is a sequence chart which shows operation | movement of the information exchange system by the 1st Embodiment of this invention. It is a flowchart which shows the SUBSCRIBE reception process by the 1st Embodiment of this invention. It is a flowchart which shows the SUBSCRIBE reception process by the 1st Embodiment of this invention. It is a flowchart which shows the SUBSCRIBE reception process by the 1st Embodiment of this invention. It is a flowchart which shows the UNSUBSCRIBE reception process by the 1st Embodiment of this invention. It is a flowchart which shows the UNSUBSCRIBE reception process by the 1st Embodiment of this invention. It is a flowchart which shows NOTIFY reception processing by the 1st Embodiment of this invention. It is a block diagram which shows the structure of the subscriber by the 1st Embodiment of this invention. It is a flowchart which shows the operation example of the subscriber by the 1st Embodiment of this invention. It is a block diagram which shows the structure of the information exchange system by the 2nd Embodiment of this invention. It is a flowchart which shows the SUBSCRIBE reception process (update) by the 3rd Embodiment of this invention. It is a sequence chart which shows operation | movement of the information exchange system by a prior art example.

  Next, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing the configuration of an information exchange system according to the present invention. In FIG. 1, the information exchange system according to the present invention includes a subscriber 1, a resource list server 2, and a notifier 3. The subscriber 1 observes the state of the resource (the observation target that the subscriber 1 observes its state) for a certain period, and the notifier 3 notifies the subscriber 1 of the state of the resource.

  The resource list server 2 manages a list of resources whose status information is exchanged between the subscriber 1 and the notifier 3, and includes a SUBSCRIBE (registration / subscription) request reception unit 21 and a NOTIFY (notification) transmission unit 22. A SUBSCRIBE request transmission unit 25, a NOTIFY reception unit 26, a subscription control unit 24, and a list management unit 23. FIG. 1 shows only what is necessary for explaining the operation of the present invention.

  The subscription control unit 24 includes a subscription management unit 241, a list-subscriber related management unit 242, a back-end subscription-list related management unit 243, and a resource state management unit 244.

  The list management unit 23 manages the identifiers of resources included in each resource list. The SUBSCRIBE request receiving unit 21 and the NOTIFY transmitting unit 22 provide an interface with the subscriber 1. When the SUBSCRIBE request receiving unit 21 receives a SUBSCRIBE request or UNSUBSCRIBE request for the resource list managed by the list management unit 23 from the subscriber 1, the SUBSCRIBE request reception unit 21 notifies the subscription management unit 241 of this request. The NOTIFY transmission unit 22 transmits the status of the resource as the contents of NOTIFY to the subscriber 1 subscribed to the list including the resource.

  The SUBSCRIBE request transmission unit 25 and the NOTIFY reception unit 26 provide an interface with the resource notifier 3. The SUBSCRIBE request transmission unit 25 acts on behalf of the subscriber 1 and transmits a SUBSCRIBE request and UNSUBSCRIBE request for the resource from the resource list server 2. The NOTIFY receiving unit 26 receives the status of the resource from the notifier 3 of the resource as the content of NOTIFY.

  Note that the resource notifier 3 may be associated with each resource, or may be a group of a plurality of resources such as a presence server. Here, the presence server is a physical entity (function) and operates as a presence agent or a proxy server in response to a SUBSCRIBE request. When acting as a presence agent, the presence information of the presentity [the existence and state of everything (for example, status such as being present or going out)] is known, and when acting as a proxy server, the presence agent Forward the SUBSCRIBE request to other entities acting as

  The subscription control unit 24 generates a back-end subscription based on a SUBSCRIBE request for the list from the subscriber 1. The back-end subscription is a subscription for resources from the resource list server 2. Here, the subscription is a summary of the relationship between the subscriber 1 and the notifier 3 and the event package to be used.

  The subscription manager 241 manages subscriptions and backend subscriptions from the subscriber 1 to the list. When receiving a SUBSCRIBE request or UNSUBSCRIBE request from the subscriber 1, the subscription management unit 241 generates, updates, and terminates the subscription.

  The list-subscriber relation management unit 242 holds a subscriber group for each list. When the subscriber 1 is first associated with the list, the list-subscriber related management unit 242 requests the back-end subscription-list related management unit 243 to add a list, and when there is no subscriber associated with the list, the list-subscriber related management unit 242 The end subscription-list association management unit 243 is requested to delete the list.

  The back-end subscription-list association management unit 243 holds the association between the resource list server 2 with respect to the resource and the list that triggered the subscription. The resource state management unit 244 holds the resource state acquired by NOTIFY for the back-end subscription.

  A backend subscription is valid while there is one or more associated lists. The back-end subscription disappears when the list associated with the back-end subscription disappears, a SUBSCRIBE request transmission unit 25 sends an UNSUBSCRIBE request, and the resource state managed by the resource state management unit 244 becomes invalid.

  In FIG. 1, the resource list server 2 and the notifier 3 are illustrated separately. However, when the notifier 3 is a presence server, these may be implemented as one server.

  In the information exchange system according to the present invention, when the resource list server 2 receives a SUBSCRIBE request for the list, it issues a SUBSCRIBE request to each of the resources included in the list, and sends a NOTIFY of the resource status from the resource notifier 3. When received, NOTIFY is transmitted to the subscriber 1 having a subscription to the list including the resource.

  As a result, in the information exchange system according to the present invention, when it is desired to individually receive a status notification from each resource, it is possible to combine SUBSCRIBE requests to a plurality of resources into one, so SUBSCRIBE for starting a subscription It is possible to reduce the load on the network when sending a request and when sending a SUBSCRIBE request for updating a subscription.

  In the information exchange system according to the present invention, instead of sending one NOTIFY having a large content, a plurality of NOTIFYs having a small content can be sent to reduce the load on the network. Furthermore, in the information exchange system according to the present invention, by reducing the content of one NOTIFY, it is possible to reduce the processing load of the subscriber 1 interpreting the content of NOTIFY. Furthermore, in the information exchange system according to the present invention, the load on the network can be reduced by distributing the NOTIFY transmission timing.

  FIG. 2 is a diagram showing an example of a list table of the list management unit according to the first embodiment of the present invention. Here, the configuration of the information exchange system according to the first embodiment of the present invention is the same as that of the information exchange system according to the embodiment of the present invention shown in FIG. 1, and the list management unit shown in FIG. This shows the configuration of the list management unit 23 of the resource list server 2.

  In FIG. 2, the list management unit 23 stores list tables of lists A to N, and resource identifiers are registered in the list tables of lists A to N, respectively. For example, resource identifiers a to c are registered in the list table of list A.

  FIG. 3 is a sequence chart showing the operation of the information exchange system according to the first embodiment of the present invention, and FIGS. 4 to 6 are flowcharts showing SUBSCRIBE reception processing according to the first embodiment of the present invention. 7 and 8 are flowcharts showing UNSUBSCRIBE reception processing according to the first embodiment of the present invention, and FIG. 9 is a flowchart showing NOTIFY reception processing according to the first embodiment of the present invention. The operation of the information exchange system according to the first embodiment of the present invention will be described with reference to FIGS. The processing of the resource list server 2 shown in FIG. 1 can also be realized by executing a program by a computer (not shown), and the processing shown in FIGS. 4 to 9 is realized by executing the program by the computer. .

  When performing the SUBSCRIBE reception process, when the SUBSCRIBE request receiving unit 21 receives the SUBSCRIBE request from the subscriber 1 (step S1 in FIG. 4), it checks whether the specified list is a list managed by the list management unit 23 (FIG. 4). Step S2), if not managed by the list manager 23, an error is transmitted to the subscriber 1 (step S3 in FIG. 4). In addition, if the SUBSCRIBE request receiving unit 21 is a managed list, the SUBSCRIBE request receiving unit 21 passes the SUBSCRIBE request to the subscription management unit 241.

  The subscription management unit 241 checks whether there is a subscription for the list (step S4 in FIG. 4). If there is no subscription, it creates a new subscription (step S5 in FIG. 4) and responds normally to the subscriber 1. Is returned (step S6 in FIG. 4). When a new subscription is generated by the subscription management unit 241, the subscription control unit 24 acquires the identifier of the resource included in the list specified by the SUBSCRIBE request from the list management unit 23 (step S7 in FIG. 4). Repeat the following process for all the acquired resources.

  When there is no backend subscription (step S10 in FIG. 5), the backend subscription-list related management unit 242 creates a backend subscription (step S11 in FIG. 5), and a SUBSCRIBE request for the resource from the SUBSCRIBE request transmission unit 25. Is transmitted to the notifier 3 (step S12 in FIG. 5).

  If the backend subscription-list relation management unit 242 does not hold the relation between the backend subscription and the list for the resource of interest (step S13 in FIG. 5), the backend subscription-list relation management unit 242 determines the relation between the backend subscription and the list for the resource. This is added (step S14 in FIG. 5). When the association between the list and the subscriber is not held (step S15 in FIG. 5), the list-subscriber association management unit 242 adds the association between the list and the subscriber (step S16 in FIG. 5).

  The subscription control unit 24 acquires the resource state from the resource state management unit 244 based on the resource identifier acquired from the list management unit 23, and sends the individual NOTIFY included in these contents from the NOTIFY transmission unit 22 to the subscriber 1. (Step S17 in FIG. 5). The resource list server 2 repeats the above process until the processes for all the acquired resources are completed (steps S10 to S18 in FIG. 5).

  On the other hand, if there is already a subscription, the subscription management unit 241 updates the subscription (step S8 in FIG. 4) and returns a normal response to the subscriber 1 (step S9 in FIG. 4). When the subscription is updated, the subscription control unit 24 acquires the identifiers of the resources included in the list from the list management unit 23 (step S19 in FIG. 6), and sends the individual NOTIFY for these to the subscriber 1 from the NOTIFY transmission unit 22 It transmits to (steps S20 and S21 in FIG. 6). The NOTIFY to be transmitted is an empty NOTIFY. However, when the NOTIFY transmitted when the resource state is changed has not been reached (step S20 in FIG. 6), NOTIFY including the state of the resource is transmitted instead of the empty NOTIFY ( FIG. 6 step S22).

  When performing UNSUBSCRIBE reception processing, when the SUBSCRIBE request receiving unit 21 receives the UNSUBSCRIBE request from the subscriber 1 (step S31 in FIG. 7), it checks whether the specified list is a list managed by the list management unit 23 (FIG. 7). In step S32), if the list is not managed, error transmission is performed to subscriber 1 (step S33 in FIG. 7). In addition, if the SUBSCRIBE request receiving unit 21 is a managed list, the SUBSCRIBE request receiving unit 21 passes the SUBSCRIBE request to the subscription management unit 241.

  Upon receipt of the UNSUBSCRIBE request, the subscription management unit 241 terminates the subscription (step S35 in FIG. 7) and returns a normal response to the subscriber 1 (step S35 in FIG. 7). FIG. 7 step S36). When there is no subscription for the list (step S34 in FIG. 7), the subscription management unit 241 transmits an error to the subscriber 1 (step S33 in FIG. 7).

  When the subscription is terminated, the subscription control unit 24 acquires the identifier of the resource included in the list from the list management unit 23 (step S37 in FIG. 7), and acquires the status of each resource from the resource state management unit 244. (FIG. 7 step S38), the individual NOTIFY including these is transmitted from the NOTIFY transmitting unit 22 to the subscribe 1 (step S39 in FIG. 7). Further, the subscription control unit 24 deletes the association of the subscriber 1 with the list from the list-subscriber association management unit 242 (step S40 in FIG. 7).

  When there is no subscriber associated with the list (step S41 in FIG. 7), the subscription control unit 24 performs the following for the back-end subscription for each resource managed by the back-end subscription-list related management unit 243. Process.

  The subscription control unit 24 deletes the association between the back-end subscription for the resource and the list (step S42 in FIG. 8), and when there is no list associated with the back-end subscription for the resource (step S43 in FIG. 8). Then, the back-end subscription is terminated (step S44 in FIG. 8). Thereafter, the subscription control unit 24 transmits a UNSUBSCRIBE request to the resource from the SUBSCRIBE request transmission unit 25 (step S45 in FIG. 8).

  When the NOTIFY receiving process is performed, the NOTIFY receiving unit 26 receives NOTIFY including the state of the resource from the resource notifier (for example, presence server) 3 (step S51 in FIG. 9), and this NOTIFY is received by the subscription management unit 241. To pass. The subscription management unit 241 compares the received resource state with the resource state held in the resource state management unit 244 (step S52 in FIG. 9). If the comparison result is different (step S53 in FIG. 9), the following processing is performed. Repeat.

  The subscription management unit 241 updates the resource state managed by the resource state management unit 244 with the received resource state (step S54 in FIG. 9). The subscription manager 241 selects a list associated with the back-end subscription of the resource from the back-end subscription-list association manager 243 (step S55 in FIG. 9).

  The subscription management unit 241 determines the subscribers managed by the list-subscriber related management unit 242 for all the selected lists (step S56 in FIG. 9), and includes the resource status for the selected subscriber 1 in the contents. NOTIFY is transmitted from the NOTIFY transmitter 22 (step S57 in FIG. 9).

  FIG. 10 is a block diagram showing the configuration of the subscriber 1 according to the first embodiment of the present invention. In FIG. 10, a subscriber (terminal device) 1 uses a CPU (central processing unit) 11, a main memory 12 for storing a control program 12a executed by the CPU 11, and a work area when the CPU 11 executes the control program 12a. It comprises a storage device 13 and a communication control unit 14 that controls communication with the resource list server 2, and the CPU 11, main memory 12, storage device 13, and communication control unit 14 are connected to each other via an internal bus 110. Has been. In addition, the storage device 13 includes a resource list holding unit 131 that holds a resource list acquired from the resource list server 2.

  FIG. 11 is a flowchart showing an operation example of the subscriber 1 according to the first embodiment of the present invention. An example of the operation of the subscriber 1 will be described with reference to FIGS. The process shown in FIG. 11 is realized by the CPU 11 executing the control program 12a.

  When the subscriber 1 sends a SUBSCRIBE request including the list designation and the support notification to the resource list server 2 (step S61 in FIG. 11) and receives the resource list for the support notification from the resource list server 2 (step S62 in FIG. 11), the resource list Is held in the resource list holding unit 131 of the storage device 13 (step S63 in FIG. 11).

  Thereafter, when the subscriber 1 receives NOTIFY in response to the SUBSCRIBE request from the resource list server 2 (step S64 in FIG. 11), it compares the NOTIFY with the resource list held in the resource list holding unit 131 (step S65 in FIG. 11).

  When the subscriber 1 determines that it is a NOTIFY to be received by the collation (step S66 in FIG. 11), it interprets the contents of the NOTIFY (step S67 in FIG. 11). Further, if the subscriber 1 does not determine that it is a NOTIFY to be received in the collation (step S66 in FIG. 11), the subscriber 1 discards the NOTIFY (step S68 in FIG. 11). The subscriber 1 repeats the above processing until it receives all NOTIFYs (reception targets) for the resources included in the list designated by the SUBSCRIBE request (step S69 in FIG. 11).

  As described above, in the present embodiment, when it is desired to individually receive a status notification from each resource, SUBSCRIBE requests to a plurality of resources can be combined into one, so that when a SUBSCRIBE request for starting a subscription is transmitted and It is possible to reduce the load on the network when sending a SUBSCRIBE request for updating a subscription.

  In this embodiment, instead of sending one NOTIFY with a large content, a plurality of NOTIFYs with a small content can be sent to reduce the load on the network. Furthermore, in the present embodiment, by reducing the contents of one NOTIFY, it is possible to reduce the processing load for the subscriber 1 to interpret the contents of NOTIFY. In this embodiment, the SUBSCRIBE request from the subscriber 1 is processed by the resource list server 2 and passed to the notifier 3. However, by providing a list management unit in the notifier 3, the SUBSCRIBE request from the subscriber 1 is provided. Even if it is passed to the notifier 3 as it is, the same effect as described above can be obtained, and the present invention is not limited to this.

  FIG. 12 is a block diagram showing a configuration of an information exchange system according to the second embodiment of the present invention. 12, the information exchange system according to the second exemplary embodiment of the present invention is the same as the exemplary embodiment of the present invention illustrated in FIG. 1 except that a network load distribution unit 411 is provided in the NOTIFY transmission unit 41 of the resource list server 4. The configuration is the same as that of the information exchange system, and the same components are denoted by the same reference numerals. The operation of the same component is the same as that of the above-described embodiment of the present invention.

  The network load distribution unit 411 can reduce the network load by distributing the NOTIFY transmission timing to the subscriber 1. In this embodiment, the processing load on the subscriber 1 can be reduced.

  The network load distribution unit 411 (1) distributes NOTIFY transmission timing for the same subscriber, (2) distributes NOTIFY transmission timing among a plurality of subscribers (subscribers are selected, but for the same subscriber (NOTIFY is sent as it is), (3) There are those that disperse the transmission timing of NOTIFY without distinction of subscribers, and the like.

  As an example of the network load distribution unit 411, there is a method of waiting for “reference transmission waiting time × random number” period before transmitting each NOTIFY. The reference transmission waiting time may be a fixed value or a value that varies depending on the network load. When fluctuating according to the network load, the reference transmission waiting time becomes longer as the load is higher.

  As described above, in this embodiment, the network load distribution unit 411 is provided in the NOTIFY transmission unit 41 of the resource list server 4 to distribute the NOTIFY transmission timing, thereby reducing the network load.

  FIG. 13 is a flowchart showing SUBSCRIBE reception processing (update) according to the third embodiment of the present invention. The information exchange system according to the third embodiment of the present invention has the same configuration as the information exchange system according to the embodiment of the present invention shown in FIG. The operation of the information exchange system according to the third embodiment of the present invention will be described with reference to FIG. 1 and FIG. Note that the processing shown in FIG. 13 is realized by a computer executing a program in the same manner as in the first embodiment of the present invention. The information exchange system according to the third embodiment of the present invention may have the same configuration as the information exchange system according to the second embodiment of the present invention shown in FIG.

  This embodiment differs from the third embodiment of the present invention in that an empty NOTIFY transmitted from the NOTIFY transmitting unit 22 at the time of subscription update is not for each resource but for a list.

  When the SUBSCRIBE reception process (update) is performed, when the SUBSCRIBE request receiving unit 21 receives the SUBSCRIBE request from the subscriber 1 (step S71 in FIG. 13), it checks whether the specified list is a list managed by the list management unit 23. If it is not managed by the list management unit 23 (step S72 in FIG. 13), an error is transmitted to the subscriber 1 (step S73 in FIG. 13). In addition, if the SUBSCRIBE request receiving unit 21 is a managed list, the SUBSCRIBE request receiving unit 21 passes the SUBSCRIBE request to the subscription management unit 241.

  The subscription management unit 241 checks whether there is already a subscription for the list (step S74 in FIG. 13). If there is no subscription, it creates a new subscription (step S75 in FIG. 13) and responds normally to the subscriber 1. Is returned (step S76 in FIG. 13). When a new subscription is generated by the subscription management unit 241, the subscription control unit 24 obtains the identifier of the resource included in the list specified by the SUBSCRIBE request from the list management unit 23 (step S77 in FIG. 13). The processing from step S10 onward in the first embodiment of the present invention described above is repeated for all acquired resources.

  Upon receiving the SUBSCRIBE request, the subscription management unit 241 updates the subscription (step S78 in FIG. 13) and returns a normal response to the subscriber 1 (step S74 in FIG. 13) when there is already a subscription to the list (step S74 in FIG. 13). FIG. 13 step S79).

  When the subscription is updated, the subscription control unit 24 transmits one NOTIFY whose content is empty (steps S80 and S81 in FIG. 13). However, when the NOTIFY transmitted when the resource state is changed has not been reached (step S80 in FIG. 13), NOTIFY including the state of the resource is transmitted instead of the empty NOTIFY ( FIG. 13 step S82).

As described above, in the present embodiment, the network load can be reduced by combining the empty NOTIFYs transmitted to the subscriber 1 at the time of updating the subscription into one.
A part or all of the above embodiment can be described as in the following supplementary notes, but is not limited to the following description.

[Appendix 1]
Including a notifier including means for monitoring the state of one or more resources and a notifying means for notifying the resource list server of the state of the resource by NOTIFY, and designation information for designating a resource list including one or more resources A resource list server for managing a list of resources in an information exchange system comprising a subscriber including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request to a resource list server,
Resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier;
Means for issuing a SUBSCRIBE request for each of the resources included in the resource list when a SUBSCRIBE request for the resource list is received;
When NOTIFY of the state of the resource is received from the notifier, a plurality of NOTIFYs including the state of the resource included in the resource list are transmitted to a subscriber who has a subscription to the resource list including the resource. Means,
The resource list server, wherein the means for transmitting NOTIFY transmits the NOTIFY individually for each resource.

[Appendix 2]
The resource list server according to claim 1, further comprising means for distributing transmission timing of the NOTIFY to the subscriber.

[Appendix 3]
Including a notifier including means for monitoring the state of one or more resources and a notifying means for notifying the resource list server of the state of the resource by NOTIFY, and designation information for designating a resource list including one or more resources A resource list server for managing a list of resources in an information exchange system comprising a subscriber including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request to a resource list server,
Resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier;
Means for issuing a SUBSCRIBE request for each of the resources included in the resource list when a SUBSCRIBE request for the resource list is received;
When NOTIFY of the state of the resource is received from the notifier, a plurality of NOTIFYs including the state of the resource included in the resource list are transmitted to a subscriber who has a subscription to the resource list including the resource. Means,
A resource list server comprising means for distributing the transmission timing of the NOTIFY to the subscriber.

[Appendix 4]
Including a notifier including means for monitoring the state of one or more resources and a notifying means for notifying the resource list server of the state of the resource by NOTIFY, and designation information for designating a resource list including one or more resources In an information exchange system comprising subscribers including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request to a resource list server, a network load reducing method used for a resource list server for managing the list of resources,
The resource list server is provided with resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier,
When the resource list server receives a SUBSCRIBE request for the resource list, it receives a SUBSCRIBE request for each of the resources included in the resource list, and receives NOTIFY of the state of the resource from the notifier A plurality of NOTIFYs including the state of the resource included in the resource list to a subscriber who has a subscription to the resource list including the resource,
The network load reducing method, wherein the resource list server individually transmits the NOTIFY for each resource in the process of transmitting the NOTIFY.

[Appendix 5]
The network load reduction method according to appendix 4, wherein the resource list server executes a process of distributing the transmission timing of the NOTIFY to the subscriber.

[Appendix 6]
6. The network load reduction method according to appendix 4 or appendix 5, wherein the subscriber monitors the state of the resource until the SUBSCRIBE request is canceled.

[Appendix 7]
7. The network load mitigation method according to any one of appendix 4 to appendix 6, wherein the subscriber monitors the state of the resource for a predetermined period specified by the SUBSCRIBE request.

[Appendix 8]
The network load according to any one of appendix 4 to appendix 7, wherein the subscriber includes means for acquiring information on the resource list from the resource list server and means for interpreting the information on the resource list. Mitigation method.

[Appendix 9]
Including a notifier including means for monitoring the state of one or more resources and a notifying means for notifying the resource list server of the state of the resource by NOTIFY, and designation information for designating a resource list including one or more resources In an information exchange system comprising subscribers including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request to a resource list server, a network load reducing method used for a resource list server for managing the list of resources,
The resource list server is provided with resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier,
When the resource list server receives a SUBSCRIBE request for the resource list, it receives a SUBSCRIBE request for each of the resources included in the resource list, and receives NOTIFY of the state of the resource from the notifier A plurality of NOTIFYs including the state of the resource included in the resource list to a subscriber who has a subscription to the resource list including the resource,
The network load reduction method according to claim 1, wherein the resource list server executes a process of distributing the transmission timing of the NOTIFY to the subscriber.

[Appendix 10]
The network load reducing method according to appendix 9, wherein the subscriber monitors the state of the resource until the subscriber cancels the SUBSCRIBE request.

[Appendix 11]
11. The network load mitigation method according to appendix 9 or appendix 10, wherein the subscriber monitors the state of the resource for a predetermined period specified by the SUBSCRIBE request.

[Appendix 12]
12. The network load according to any one of appendix 9 to appendix 11, wherein the subscriber includes means for obtaining information on the resource list from the resource list server, and means for interpreting the information on the resource list. Mitigation method.

[Appendix 13]
Including a notifier including means for monitoring the state of one or more resources and a notifying means for notifying the resource list server of the state of the resource by NOTIFY, and designation information for designating a resource list including one or more resources In an information exchange system comprising subscribers including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request to a resource list server, a network load reducing method used for a resource list server for managing the list of resources,
The resource list server is provided with resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier,
When the resource list server receives a SUBSCRIBE request for the resource list, it receives a SUBSCRIBE request for each of the resources included in the resource list, and receives NOTIFY of the state of the resource from the notifier A plurality of NOTIFYs including the state of the resource included in the resource list to a subscriber who has a subscription to the resource list including the resource,
A network load reduction method characterized by monitoring the state of the resource until the subscriber cancels the SUBSCRIBE request.

[Appendix 14]
14. The network load mitigation method according to appendix 13, wherein the subscriber monitors the state of the resource for a predetermined period specified by the SUBSCRIBE request.

[Appendix 15]
15. The network load reduction method according to appendix 13 or appendix 14, wherein the subscriber performs a process of acquiring the resource list information from the resource list server and an interpreting process of the resource list information .

[Appendix 16]
Including a notifier including means for monitoring the state of one or more resources and a notifying means for notifying the resource list server of the state of the resource by NOTIFY, and designation information for designating a resource list including one or more resources In an information exchange system comprising subscribers including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request to a resource list server, a network load reducing method used for a resource list server for managing the list of resources,
The resource list server is provided with resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier,
When the resource list server receives a SUBSCRIBE request for the resource list, it receives a SUBSCRIBE request for each of the resources included in the resource list, and receives NOTIFY of the state of the resource from the notifier A plurality of NOTIFYs including the state of the resource included in the resource list to a subscriber who has a subscription to the resource list including the resource,
A network load mitigation method, wherein the subscriber monitors the state of the resource for a certain period of time specified by the SUBSCRIBE request.

[Appendix 17]
The network load reducing method according to supplementary note 16, wherein the subscriber performs a process of acquiring the resource list information from the resource list server and a process of interpreting the resource list information.

[Appendix 18]
Including a notifier including means for monitoring the state of one or more resources and a notifying means for notifying the resource list server of the state of the resource by NOTIFY, and designation information for designating a resource list including one or more resources In an information exchange system comprising subscribers including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request to a resource list server, a network load reducing method used for a resource list server for managing the list of resources,
The resource list server is provided with resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier,
When the resource list server receives a SUBSCRIBE request for the resource list, it receives a SUBSCRIBE request for each of the resources included in the resource list, and receives NOTIFY of the state of the resource from the notifier A plurality of NOTIFYs including the state of the resource included in the resource list to a subscriber who has a subscription to the resource list including the resource,
The network load reducing method, wherein the subscriber performs a process of acquiring the information of the resource list from the resource list server and a process of interpreting the information of the resource list.

  The present invention is not limited to the Internet, and can be applied to a presence service for notifying the presence and state (e.g., being in the office, going out, etc.) of all things, particularly a presence service in a mobile environment.

1 Subscriber 2, 4 Resource list server
3 Notifier 11 CPU
DESCRIPTION OF SYMBOLS 12 Main memory 12a Control program 13 Storage device 14 Communication control part 21 SUBSCRIBE request receiving part 22,41 NOTIFY transmitting part 23 List management part 24 Subscription control part 25 SUBSCRIBE request transmitting part 26 NOTIFY receiving part 110 Internal bus 241 Subscription management part 242 List-subscriber related management unit 243 Backend subscription-list related management unit 244 Resource state management unit 411 Network load balancing unit

Claims (9)

An information exchange system comprising a subscriber that observes a resource state for a certain period, a notifier that notifies the subscriber of the resource state, and a resource list server that manages the list of resources,
The notifier includes means for monitoring the state of one or more resources, and notification means for notifying the resource list server of the state of the resource by NOTIFY,
The subscriber has a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request including designation information for designating a resource list including one or more resources to the resource list server;
The resource list server is included in the resource list when it receives a resource status holding means for receiving and holding the status of the resource notified by the NOTIFY from the notifier and a SUBSCRIBE request for the resource list. A means for issuing a SUBSCRIBE request for each resource, and a NOTIFY of the status of the resource from the notifier is included in the resource list for a subscriber who has a subscription to the resource list containing the resource And a means for transmitting a plurality of NOTIFYs having the state of the resource to be stored.   2. The information exchange system according to claim 1, wherein the means for transmitting NOTIFY transmits the NOTIFY individually for each resource.   3. The information exchange system according to claim 1, wherein the resource list server includes means for distributing transmission timing of the NOTIFY to the subscriber.   4. The information exchange system according to claim 1, wherein the subscriber monitors the state of the resource until canceling the SUBSCRIBE request. 5.   5. The information exchange system according to claim 1, wherein the subscriber monitors the state of the resource for a predetermined period specified by the SUBSCRIBE request.   6. The information according to claim 1, wherein the subscriber includes means for acquiring information on the resource list from the resource list server and means for interpreting information on the resource list. Exchange system. Including a notifier including means for monitoring the state of one or more resources and a notifying means for notifying the resource list server of the state of the resource by NOTIFY, and designation information for designating a resource list including one or more resources A resource list server for managing a list of resources in an information exchange system comprising a subscriber including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request to a resource list server,
Resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier;
Means for issuing a SUBSCRIBE request for each of the resources included in the resource list when a SUBSCRIBE request for the resource list is received;
When NOTIFY of the state of the resource is received from the notifier, a plurality of NOTIFYs including the state of the resource included in the resource list are transmitted to a subscriber who has a subscription to the resource list including the resource. A resource list server. Including a notifier including means for monitoring the state of one or more resources and a notifying means for notifying the resource list server of the state of the resource by NOTIFY, and designation information for designating a resource list including one or more resources In an information exchange system comprising subscribers including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request to a resource list server, a network load reducing method used for a resource list server for managing the list of resources,
The resource list server is provided with resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier,
When the resource list server receives a SUBSCRIBE request for the resource list, it receives a SUBSCRIBE request for each of the resources included in the resource list, and receives NOTIFY of the state of the resource from the notifier Network load reduction characterized by executing a process of transmitting a plurality of NOTIFYs having contents of the resources included in the resource list to a subscriber who has a subscription to the resource list including the resource. Method. Including a notifier including means for monitoring the state of one or more resources and a notifying means for notifying the resource list server of the state of the resource by NOTIFY, and designation information for designating a resource list including one or more resources In an information exchange system comprising a subscriber including a SUBSCRIBE request transmitting means for transmitting a SUBSCRIBE request to a resource list server, a program executed by a computer in the resource list server that manages the list of resources,
The resource list server is provided with resource state holding means for receiving and holding the state of the resource notified by the NOTIFY from the notifier,
When a SUBSCRIBE request for the resource list is received, a process for issuing a SUBSCRIBE request to each of the resources included in the resource list, and when the NOTIFY of the state of the resource is received from the notifier, the resource is included And a process of transmitting a plurality of NOTIFYs containing the state of the resource included in the resource list to a subscriber who has a subscription to the resource list.

Images