JP4577803B2 - COMMUNICATION METHOD AND TRANSMITTER - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
  The present invention relates to a method for determining a communication method for performing data communication between devices connected by a data communication path.
[0002]
  In the present invention, information includes various types of files shared by a plurality of devices, user status, news, messages, and the like. The communication side device and the receiving side device share logically the same information. However, the information possession form may be different between the information on the receiving device and the information on the transmitting device. For example, the transmitting device has the text data itself on the hard disk, but the receiving device may simply display the corresponding image on the screen. Further, the information on the receiving device need not have all the information on the transmitting device.
[0003]
  The data communication path may be a virtual communication path such as packet communication, and does not need to be always connected. A relay device may exist in the middle of the data communication path.
[0004]
  The communication side device and the reception side device do not need to have a fixed role. For example, in some cases, the device that is the transmitting side may be the receiving side in other cases. The same device may play the roles of the transmitting side and the receiving side at the same time.
[0005]
[Prior art]
  In recent years, networking of society as a whole has progressed, and communication between users, news distribution, advertisement distribution, and the like have been performed using data communication paths such as computer networks and telephone lines. In these network communications, information on a plurality of information devices connected to a data communication path is generally synchronized.
[0006]
  In order to synchronize information among a plurality of devices, the latest information is transmitted / received between the information devices, or the latest information is distributed from the server to the terminal device. Communication methods for transmitting and receiving information between devices connected via a data communication path are roughly classified into the following methods.
[0007]
  (1) Push method
  The receiving device is registered in advance with the transmitting device. When the information on the transmission side device is updated, the transmission side device transmits the update information to the reception side device via the data communication path. When the receiving device receives the update information, it updates the information stored in itself. Note that the transmission-side device may transmit a plurality of pieces of update information to the reception-side device collectively without transmitting communication information immediately after the transmission-side information is updated.
[0008]
  The advantages and disadvantages of this method are as follows.
[0009]
  Advantage: Information on the receiving side always reflects information updates promptly, and communication for acquiring information is not required when the user refers to the information, so that the waiting time at the time of reference is short.
[0010]
  Disadvantage: When the update frequency is greater than the reference frequency, useless communication occurs. Therefore, the load on the communication path increases, the load on the communication side and the receiving side device increases, and the communication fee increases.
[0011]
  (2) Pull method
  First, the information on the transmission side device is updated. Thereafter, the receiving device transmits a pull request to the transmitting device according to an event such as a user instruction or the passage of time. Upon receiving the pull request, the transmitting device transmits update information to the receiving device. The receiving device receives the update information and updates the information stored in itself. The update of information on the transmission side device may be executed a plurality of times before the update information is transmitted to the reception side device. In the present invention, a method in which the receiving device periodically issues a pull request is also classified as a pull method.
[0012]
  The advantages and disadvantages of this method are as follows.
[0013]
  Advantage: In the method of issuing a pull request for the first time when referring to information, useless communication is unlikely to occur when the update frequency is higher than the reference frequency. Therefore, the load on the communication path is reduced, the load on the transmitting side and the receiving side device is reduced, and the communication fee is reduced.
[0014]
  Disadvantages: In the method of issuing a pull request for the first time when referring to information, communication is performed at the time of reference, and update information is acquired, so the waiting time becomes long. Further, when the update frequency is smaller than the reference frequency, useless communication occurs. For this reason, the load on the communication path, the load on the transmission side and the reception side devices are increased, and the communication fee is increased. In addition, it is impossible to promptly notify the user that the information has been updated. When a pull request is periodically issued, an excessive pull request is generally required, and wasteful communication is likely to occur.
[0015]
  (3) Notify method
  The receiving device is registered in advance with the transmitting device. When the information on the transmitting device is updated, the transmitting device transmits an update notification to the receiving device. The update notification is not the updated information itself but the fact that the information has been updated and the identifier of the update information. When receiving the update notification, the receiving device adds an update mark indicating that the information has been updated to the corresponding information. Thereafter, in the receiving device, information is updated by an event such as a user instruction or the passage of time.
[0016]
  Information update is performed as follows. The receiving-side device transmits a pull request only for those with an update mark. The transmitting device transmits the update information to the receiving device. Based on the received update information, the receiving device updates the information with the update mark and deletes the update mark. There is also a method of transmitting a pull request immediately after receiving an update notification without using an update stamp or the like. In addition, an update notification may not be sent every time information is updated in the transmission side device, and an update notification may be transmitted to the reception side device after collecting a plurality of information updates.
[0017]
  This method has intermediate advantages and disadvantages between the push method and the pull method.
[0018]
  In addition to the advantages and disadvantages of the various communication methods described above, the push method may not be used depending on the communication environment. For example, on the Internet, there are many cases where information cannot be sent from the outside to the inside of the firewall by a push method. Furthermore, there are communication systems in which combinations or details of the above communication systems are changed.
[0019]
[Problems to be solved by the invention]
  2. Description of the Related Art Conventionally, a communication method according to needs is set for a device by setting of a user or a system administrator. A combination of certain information, a user, a receiving device, and a communication method is determined when the device is activated or when a setting is changed.
[0020]
  However, the relationship and degree of advantages and disadvantages of each communication method described above vary due to various factors. For example, when the reference frequency is higher than the update frequency, the communication fee is cheaper using the push method. On the contrary, when the reference frequency is low and the update frequency is low, the communication fee is reduced by using the pull method. Further, when the communication time is short, the disadvantage that the waiting time of the pull method is long is reduced. Many of these factors dynamically change, but conventionally, the set communication method is not changed according to the situation, so that it is difficult to perform optimal communication according to the change of the factors. Therefore, for example, the following problems occur.
[0021]
  (1) The push method is set on the assumption that a certain information item has a high reference frequency. As a result, unnecessary communication charges are incurred.
[0022]
  (2) The push method is set on the assumption that a certain information item has a high reference frequency, but the amount of information that is not referred to is large, and a wasteful communication fee is required.
[0023]
  (3) The notify method was set on the assumption that the communication speed was sufficiently fast, but it happened that the communication path was congested and took time.
[0024]
  (4) The push method was set on the assumption that the update frequency was low, but the update frequency was high for a certain period and the communication charge was high.
[0025]
  In addition to the above problems, it is not possible to perform a flexible operation that copes with various factors that change dynamically only by setting a communication method. For example, 1) The push method is usually used with priority on the reference time, and the notify method is used when the communication fee is increased. It is difficult to switch the communication method depending on the situation, such as using the notify method.
[0026]
  The present invention solves the aforementioned problems, improves the utilization efficiency of the data communication path, reduces the burden and cost of the data communication path, reduces the burden and cost of the user terminal, and enhances the convenience for the user. For the purpose.
[0027]
[Means for Solving the Problems]
  In order to solve the above problems, the first invention of the present application is:A communication method executed by the transmission apparatus when performing communication of information between a transmission apparatus and a reception apparatus connected by a data communication path by any one of a push, notify, or pull communication system. ,
・When the information is updated, the communication method of the information is determined based on the state information of the transmitting device and the state information of the receiving device provided from the receiving device,
・If the determined communication method is a push method, the updated information is transmitted to the receiving device,
・If the determined communication method is a notify method, an update notification is sent to the receiving device,
・When the determined communication method is a notify method or a pull method, based on the information acquisition request from the receiving device, the updated information is transmitted to the receiving device.
  communicationProvide a method.
[0028]
  The second invention of the present application isA transmission device used in a communication system that communicates information in a communication method of push, notify, or pull method between a transmission device and a reception device connected by a data communication path,
A method determination unit that determines a communication method of the information based on the state information of the transmission device and the state information of the reception device provided from the reception device when the information is updated;
When the determined communication method is a push method, the updated information is transmitted to the receiving device. When the determined communication method is a notify method, an update notification is transmitted to the receiving device, and the determined communication method is In the case of the notify method or the pull method, an information transmission unit that transmits the updated information to the receiving device based on an information acquisition request from the receiving device;
A transmission apparatus comprising:I will provide a.
[0029]
  The third invention of the present application isIn the second invention,
The method determination unit includes a history storage unit that records the determined communication method;
・A determination method notifying unit for notifying the receiving device of the determined communication method when the previous communication method recorded in the history storage unit is different from the determined communication method;
  Is further provided.
[0030]
  The fourth invention of the present application is the second or third invention, wherein
・The state information of the transmission device includes at least one of the capability of the transmission device, the load status of the transmission device, or information indicating the update frequency of the information,
・The status information of the receiving device includes at least one of the capability of the receiving device, the load status of the receiving device, the reference frequency of the information, and information indicating a communication method set in the receiving device. I will provide a.
[0031]
DETAILED DESCRIPTION OF THE INVENTION
  <Outline of the invention>
  The present invention switches the communication method to the optimum one according to various factors that change dynamically. This makes it possible to effectively use the network and computer resources, reduce the cost of communication, and improve the convenience for the user. In most cases, the optimum communication method is different between the transmitting device and the receiving device. In this case, the communication method that is considered to be optimal for the entire system is determined, or the communication method used on both sides is finally determined by prioritizing the determination on either the transmission side or the reception side.
[0032]
  In the following first and second exemplary embodiments, an example will be described in which the communication method is determined by increasing the priority of the transmitting device. In the third embodiment, an example will be described in which the communication method is determined by increasing the priority of the receiving device.
[0033]
  <First embodiment>
  [Constitution]
  Next, the case where the communication system switching method of the present invention is applied to an awareness system will be specifically described as an example. FIG. 1 shows the overall configuration of an awareness system according to the first embodiment. In this system, an awareness server 1 and a client 2 are connected via a network 3. Although only one client 2 is shown in the figure, a plurality of clients are normally connected to the network 3.
[0034]
  The awareness server 1 manages the awareness information of users on the network 3 and distributes the awareness information of other users to the client 2. The awareness information is general personal information of the user such as the user status, which communication means the user can use, address, telephone number, mail address, and the like. In this example, when any of the awareness information managed by the awareness server 1 is updated, an example is given for switching the communication method for synchronizing the updated information with the awareness information on the client 2. I will explain.
[0035]
  (1) Awareness server
  The awareness server 1 includes an awareness service module 11, a method determination module 12, a user DB 13, a setting DB 14, and a method DB 15. The awareness service module 11 receives an update of awareness information from the client and stores it in the user DB 13. The awareness service module 11 stores which user's awareness information refers to which user, that is, a buddy list of each user, in the user DB 13. Further, when the awareness information in the user DB 13 is updated, the awareness service module 11 distributes the updated information to the user who is referring to the updated awareness information. The method determination module 12 is a communication method between the server 1 and the client 2 based on dynamically changing factors such as server load, network 3 load, information update frequency, and the communication method designated by the client 2. Switch dynamically.
[0036]
  FIG. 2 is a conceptual explanatory diagram of awareness information stored in the user DB 13. In this example, whether or not “user ID”, “status” and “message” of the user can be received, whether or not “telephone” can be received, and “e-mail” can be received as awareness information. Are stored for each user. The user DB 13 stores a buddy list for each user (not shown). This buddy list defines who is referring to who's awareness.
[0037]
  FIG. 3 is a conceptual explanatory diagram of information stored in the setting DB 14 of the awareness server 1. The setting DB 14 stores (a) an administrator setting data table, (b) a user setting data table, and (c) a reference data table. FIG. 4A is a conceptual explanatory diagram of the administrator setting data table (a). In this table, whether to give priority to throughput or priority to response time is set as a server priority. This setting is performed by the administrator of the awareness server 1.
[0038]
  FIG. (B) is a conceptual explanatory diagram of the user setting data table (b). In this table, “user ID”, “priority”, and “charge target” are accumulated. In other words, in this table, whether the reference time is given priority or the communication fee is given priority, and the target amount of the communication fee for January is accumulated for each user. This setting is made by the user.
[0039]
  FIG. 3C is a conceptual explanatory diagram of the reference data table. In this table, the contents of each user's buddy list are described. Specifically, “user ID”, “buddy ID”, “reference item”, and “notification item” are accumulated. The “user ID” is the owner of the buddy list, and the “buddy ID” is the ID of the user registered as a reference destination in each user's buddy list. In the “reference item”, an item of awareness information referred to by the user is stored. “Notification item” is information that should be promptly notified among the awareness information to be referred to.
[0040]
  4 and 5 are conceptual explanatory diagrams of information stored in the method DB 15 of the awareness server 1. The method DB 15 stores (a) a communication history table, (b) a client capability table, (c) a reference information data table, (d) a past method table, and (e) a server capability table. FIG. 4A is a conceptual explanatory diagram of the communication history table (a). In this table, “user ID”, “communication amount”, “communication time (seconds)”, and “charge (yen)” are accumulated. That is, in this table, past communication history is accumulated for each user.
[0041]
  FIG. 4B is a conceptual explanatory diagram accumulated in the client capability table (b). In this table, “communication path load”, “client capability”, and “communication path capability” are stored for each user ID. The client capability is determined based on, for example, processing speed and memory capacity. The channel capacity is determined from, for example, the communication capacity and the communication speed.
[0042]
  FIG. 4C is a conceptual explanatory diagram of information stored in the reference information data table (c). In this figure, “information item”, “update frequency (times / hour)”, and “information amount (Bytes)” are accumulated for each user ID. In the information item, an item of awareness information is described, and an update frequency and an information amount are stored for each awareness information item of each user.
[0043]
  FIG. 5D is a conceptual explanatory diagram of information accumulated in the past method table (d). This table stores, for each item of the awareness information, the past communication method used for transmitting the awareness information from the awareness server 1 to the client 2. Specifically, this table stores “buddy ID”, “information item”, “client-side determination method”, “reason”, and “previous method” for each “user ID”. The user is the owner of the buddy list. The client-side determination method is a communication method determined by the user client 2. The previous method is a communication method used for the previous communication between the awareness server 1 and the user client 2.
[0044]
  FIG. 5E is a conceptual explanatory diagram of information stored in the server capability table (e). In this table, the load of the awareness server and the capacity of the server are recorded. The server capability is determined in the same manner as the client capability.
[0045]
  (2) Client
  The client 2 includes an awareness client module 21, a method specifying module 22, a setting DB 23, and a method DB 24. The awareness client module 21 accepts setting and updating of awareness information from the user, and transmits it to the awareness server 1. Further, the awareness client module 21 accepts setting and updating of the buddy list and registers them in the awareness server 1. Furthermore, the awareness client module 21 acquires the awareness information of other users registered in the buddy list from the awareness server 1 in response to the occurrence of a predetermined event. The predetermined event is, for example, a user operation or an update of awareness information every predetermined time.
[0046]
  The method designating module 22 determines the optimum communication method for the client 2 based on dynamically changing factors such as the load on the client 2 and the network load.
[0047]
  FIG. 6 is a conceptual explanatory diagram of information stored in the setting DB 23 of the client 2. In this setting DB 23, (a) a user setting data table and (b) a reference setting table are stored.
[0048]
  FIG. 4A is a user setting data table. In this table, “priority” and “charge target” are accumulated. The contents set in this table are registered in the user setting data table (b) of the server side setting DB 14.
[0049]
  FIG. 7B is a conceptual explanatory diagram of information stored in the reference setting table. In this table, IDs of other users registered by the user in the buddy list, that is, buddy IDs, “reference items”, and “notification items” are accumulated. The contents set in this table are accumulated in the reference data table (c) of the setting DB 14 of the awareness server 1.
[0050]
  FIG. 7 is a conceptual explanatory diagram of information stored in the method DB 24 of the client 2. In this method DB, (a) a communication history table, (b) a capability table, and (c) a reference information table are stored.
[0051]
  FIG. 4A is a conceptual explanatory diagram of information accumulated in the communication history table. In this table, the communication history of the client 2, specifically, “communication amount (Kbytes / min)”, “communication time (seconds)”, and “charge (yen)” are associated and stored. The contents accumulated in this table are registered in the communication history table (a) in the method DB 15 of the awareness server 1.
[0052]
  FIG. 2B is a conceptual explanatory diagram of information stored in the capability table. In this table, “communication path load”, “client load”, “client capability”, and “communication path capability” are accumulated. The contents of this table are registered in the client capability table (b) of the method DB 15.
[0053]
  FIG. 3C is a conceptual explanatory diagram of information stored in the reference information table. This table stores “reference frequency (times / degrees)”, “determination method”, and “determination reason” that determines the communication method for each information item to be referenced for buddies registered in the buddy list by the user. Has been.
[0054]
  [Process flow]
  Next, the flow of processing performed by the method determination module 12 of the awareness server 1 and the method specification module 22 of the client 2 will be specifically described. For ease of explanation, when the awareness information stored in the user DB 13 is updated, a communication method for notifying the user who refers to the updated information of new update information is described below. Whether to determine will be described ((1) Determination of communication method). Accordingly, the awareness server 1 is a transmission side and the client 2 is a reception side device. Next, processing in which the awareness server 1 and the client 2 switch the communication method according to the determination of the communication method will be described ((2) communication processing).
[0055]
  (1) Determination of communication method
  In this example, the client 2 first designates a communication method convenient for the client 2. The awareness server 1 determines the communication method based on the communication method designated by the client 2 and the overall communication status. For simplicity, the communication method is determined from push, pull, or notify.
[0056]
  (1-1) Flow of processing on the awareness server side
  (1-1-1) Server-side determination process
  The awareness server 1 performs the following processing by the method determination module 12 to determine the communication method with the client 2. When the awareness information in the user DB 13 is updated, the awareness server 1 starts the following processing.
[0057]
  Steps S1, S2, S3: The awareness server 1 refers to the reference information data table (c) of the server side method DB 15, and whether or not the client 2 referring to the updated awareness information specifies the communication method. Is determined (S1). If there is an already designated communication method, the awareness server 1 adds 100 points to the method designated by the client 2 among the three methods of push, pull, and notify. If there is no designation method, an addition subroutine described later is executed (S3).
[0058]
  Steps S4, S5, S6: The awareness server 1 adds 100 points to the notify method (S5) when the designation method of the client 2 is the push method and the load of the server 1 is high (S4). Otherwise, 30 points are added to the designation method of the client 2 (S6).
[0059]
  Steps S7, S8, S9: The awareness server 1 determines whether or not the updated awareness information is a notification item, and in the case of the notification item, communicates using the higher point of push or notify. (S8). If it is not a notification item, it is decided to communicate using the method with the highest point among the three methods (S9).
[0060]
  Steps S10 and S11: The awareness server 1 determines whether or not it is necessary to notify the client 2 of the determined communication method (S10). The case where it is necessary is a case where the previous time is a push or notify and this time is a pull. When the current communication method is push or notify, update information or update notification is transmitted to the client 2, so that notification is not necessary. In the case of pulling the previous time and this time as well, there is no need for notification because there is no change in the communication method. If it is determined that it is necessary, the awareness server 1 notifies the client 2 of a new communication method (S11). The client 2 that has received this notification sets a new communication method with the awareness server 1.
[0061]
  By this processing, a communication method based on the situation of the client 2 and the entire system can be set according to the dynamically changing situation.
[0062]
  (1-1-2) Addition process
  9 and 10 are flowcharts showing the flow of processing of the addition processing subroutine performed by the awareness server 1 by the method determination module 12 when the processing proceeds to step S3. In this process, the awareness server 1 determines an optimal communication method based on the situation of the entire system such as its own load, client load, and network load.
[0063]
  Step S401: The awareness server 1 determines whether or not a push method has been used in the past with the client 2 that distributes updated awareness information (S401). This determination is made by referring to the past method table (d) of the server side method DB 15.
[0064]
  If the determination is “Yes”, the awareness server 1 uses the communication charge CC and the charge target CD up to now and adds points to the pull method and the notify method as follows. The communication charge CC and the charge target CD are read from the server side system DB 15 and the setting DB 14, respectively.
When T = (CD-CC) / CD and T <0, 200 points are added to the pull method and 100 points are added to the notify method (S403). When T ≧ 0, (T × 200) points are added to the pull method and (T × 100) points are added to the notify method (S404).
[0065]
  Step S405: When the amount to be communicated is 10 Kbytes or more and the communication path capability is medium or less, the awareness server 1 proceeds to step S406. Otherwise, the process proceeds to step S409 described later.
[0066]
  Steps S406, S407, and S408: The awareness server 1 refers to the user setting data table (b) in the server side setting DB 14, and determines whether the delivery destination client 2 prioritizes the reference time or the communication fee. (S406). If priority is given to the reference time, 30 points are added to the push method (S407). If the communication fee is given priority, 50 points are added to the pull method and 30 points are added to the notify method (S408).
[0067]
  Steps S409 and S410: The awareness server 1 adds 50 points to the pull method and 30 points to the notify method when the server load is high and the amount of communication is 10 Kbytes or more (S410). ). Otherwise, the process proceeds to S411 in FIG.
[0068]
  Steps S411 and S412: The awareness server 1 determines whether or not the client capability is low and the amount to be communicated is 10 Kbytes or more based on the server side method DB 15 (S411). If “Yes” is determined, 50 points are added to the pull method and 30 points are added to the notify method (S412).
[0069]
  Steps S413 and S414: The awareness server 1 determines whether or not the load on the communication path is high and the update frequency of the awareness information is greater than or equal to a predetermined value (S413). The level of update frequency is performed based on the reference information data table (c) of the server side method DB 15. If "Yes" is determined, 30 points are added to the notify system (S414). In other cases, the process proceeds to step 415.
[0070]
  Steps S415 and S416: If the communication path capability is low and the priority of the distribution destination client 2 is the reference time (S415), the awareness server 1 adds 30 points to the push method (S416).
[0071]
  Steps S417 and S418: If the updated information is important information, the awareness server 1 adds 50 points to the push method (S417) and returns to the determination process. Otherwise, the process returns to the determination process.
[0072]
  (1-2) Client side method designation processing
  FIG. 11 is a flowchart showing a flow of communication method designation processing performed by the client 2. The client 2 determines the optimum communication method for itself by the following processing and notifies the awareness server 1 of it. The awareness server 1 that has received this notification finally determines the communication method by the method described above.
[0073]
  Step S21: The method designation module 22 of the client 2 waits for the occurrence of a predetermined event, and when the predetermined event occurs, the process proceeds to step S22. The predetermined event is an instruction to acquire buddy awareness information from the user, elapse of a predetermined time, a change in the status of the client 2, or the like.
[0074]
  Steps S22 and S23: The client 2 determines whether the communication method is set by the user (S22). If it is set, it is decided to designate the method (S23). If not, the process proceeds to step S26 described later.
[0075]
  Steps S24, S25, S26: The client 2 determines whether or not the designated communication method is to change the designated communication method so far (S24). It is determined whether or not it is necessary to notify 1 (S25). The case where it is necessary is a case where the push or notify method is changed to the pull method or vice versa. If it is determined that there is no change, the process returns to step S21 again to wait for the next event to occur.
[0076]
  If it is determined in step S25 that “notification is required”, the client 2 notifies the awareness server 1 of the designated method. If it is determined that “no need”, the process returns to step S21 again to wait for the next event to occur.
[0077]
  Step S27: When the communication method is not set by the user, the client 2 designates the push method based on the method DB 24 when the frequency of referring to the buddy awareness information is greater than or equal to a predetermined value (S27). If not, it is determined based on the method DB 24 whether the load on the client 2 is high (S29). If the load on the client 2 is high, the notify method is selected (S210), and if the load on the client 2 is not high. The determination method of the awareness server 1 is designated (S211).
[0078]
  (2) Communication processing
  (2-1) Awareness server side communication processing
  FIG. 12 is a flowchart showing the flow of communication processing performed by the awareness server 1 by the method determination module 12. By this processing, the awareness server 1 switches the communication method with the client 2 to the determined one. The awareness server 1 starts the following process when the awareness information is updated.
[0079]
  Steps S31 and S32: When the communication method is the push method (S31), the awareness server 1 transmits updated awareness information (hereinafter referred to as update information) to the distribution destination client 2 (S32).
[0080]
  Steps S33 and S34: When the communication method is the notify method (S33), the awareness server 1 transmits an update notification to the distribution destination client 2 (S34).
[0081]
  Steps S35, S36, S37: When the communication method is the pull method, the awareness server 1 waits for a pull request from the distribution destination client 2 (S36), and waits for this to transmit update information (S37).
[0082]
  (2-2) Client side communication processing
  FIG. 13 is a flowchart showing the flow of communication processing performed by the client 2 using the method designation module 22. By this processing, the client 2 switches the communication method with the awareness server 1 to the determined one. The client 2 starts the following processing in response to a reference instruction for awareness information from the user.
[0083]
  Steps S41, S42, S43, S44: When the communication method is the pull method (S41), the client 2 transmits a pull request to the awareness server 1 (S42). Next, the server waits for update information from the server 1 (S43). When this information is received, the old awareness information is updated (S44).
[0084]
  Steps S45, S46, S47, S48, S49: When the communication method is other than the pull method, the client 2 determines whether there is an update mark in the buddy's awareness information (S45). Since it is the latest information, the process is terminated. If there is, the same processing as in steps S42 to S44 is performed (S46 to 48), and the update mark of the updated awareness information is deleted (S49).
[0085]
  As described above, the awareness server 1 and the client 2 communicate using the switched communication method.
[0086]
  <Second Embodiment>
  [Constitution]
  Next, a case where the method of the present invention is applied to a news system that distributes news on a network will be described. FIG. 14 is an overall configuration diagram of a news system according to the second embodiment. The news system is configured by connecting a news server 10 and a client 20 via a network 30.
[0087]
  The news server 10 has a news DB 103 instead of the user DB 13 and a news distribution module 101 instead of the awareness service module 11. Other components are the same as those of the awareness server 1. The news distribution module 101 distributes to the client 2 when the news stored in the server-side news DB 103 is updated. Which news is distributed to which client is determined by referring to a table set in advance by the user.
[0088]
  The client 20 has a receiving module 201 for receiving news instead of the awareness client module 21. Furthermore, it has news DB205 which accumulate | stores the received news. Other components are the same as those in the first embodiment.
[0089]
  FIG. 15 is a conceptual explanatory diagram of information stored in the server-side setting DB 104. As in the first embodiment, the setting DB 104 stores (a) an administrator setting data table, (b) a user setting data table, and (c) a reference data table. Information stored in the administrator setting data table (a) and the user setting data table (b) is the same as in the first embodiment.
[0090]
  In the content stored in the reference data table (c), “reference news” is stored instead of “buddy ID” and “reference item”, and “notification news” is stored instead of “notification item”.
[0091]
  16 and 17 are conceptual explanatory diagrams of information stored in the method DB 105 of the news server 10. In this DB, (a) a communication history table, (b) a client capability table, (c) a reference information data table, (d) a past method table, and (e) a server capability table are accumulated. Except for the reference information data table (c) and the past method table (d), the same information as in the first embodiment is stored.
[0092]
  In the reference information data table (c), the same information as in the first embodiment is stored except that “news” is stored instead of “user ID” and “information item”.
[0093]
  In the past method table (d), the same information as in the first embodiment is stored except that “news” is stored instead of “buddy ID” and “information item”.
[0094]
  FIG. 18 is a conceptual explanatory diagram of information stored in the news DB 205 of the client 20. In this DB, the category of “news” designated by the user and its “content” are stored.
[0095]
  FIG. 19 is a conceptual explanatory diagram of information stored in the setting DB 203 of the client 20. In this DB, (a) a user setting data table and (b) a reference setting data table are stored. The user setting data table (a) stores the same information as in the first embodiment. The reference setting table (b) stores “reference news” instead of “buddy ID” and “reference item”, and “notification news” instead of “notification item”. Information similar to that in the embodiment is accumulated.
[0096]
  FIG. 20 is a conceptual explanatory diagram of information stored in the method DB 204 of the client 20. In this DB, (a) a communication history table, (b) a capability table, and (c) a reference information table are stored. Information stored in the communication history table (a) and the capability table (b) is the same as in the first embodiment. The information stored in the reference information table stores the same information as in the first embodiment except that “reference news” is described instead of “buddy ID” and “information item”.
[0097]
  [Process flow]
  In the present embodiment example, the processing performed by the news server 10 and the client 20 by the method determining module 102 and the method specifying module 202 is the same as in the first embodiment example.
[0098]
  <Third Embodiment>
  In the first and second embodiments, the transmission side is preferentially determined as a method for communication between the transmission side and the reception side devices. However, it is also possible to give priority to the receiving side as follows.
[0099]
  [Constitution]
  FIG. 21 is a configuration diagram of an awareness system according to the third embodiment. This system is configured by connecting a plurality of awareness clients 120a, b. In this system, a user's awareness information is temporarily held in the user's client. After that, the awareness information is synchronized with clients of other users who designate the user as a buddy.
[0100]
  For ease of explanation, it is assumed that user A and user B have registered their opponents in their buddy lists. The client 120a indicates the client of the user A, and the client 120b indicates the client of the user B. Further, a case where the client 120a is the transmission side and the client 120b is the reception side will be described. However, the client on the transmission side is also provided with the function and database on the reception side, and vice versa.
[0101]
  Both the sending client 120a and the receiving client 120b have an awareness client module 121, a setting DB 123, and a system DB 124. In addition, the transmission side client 120 a has a method designation module 126 and a user information DB 125, and the reception side client 120 b has a method determination module 122. The method designation module 126 designates the optimum communication method for the transmitting client 120a and notifies the receiving client 120b. The method determination module 122 determines a communication method based on a transmission-side designation method and the convenience of the reception-side client 120b.
[0102]
  FIG. 22 is a conceptual explanatory diagram of user A's own awareness information stored in the user information DB 125 of the transmitting client 120a. This DB information is transmitted to the receiving client 120b. In this example, this DB stores whether “user status”, “message” can be received, “phone” can be received, and “e-mail” can be received. . As the “user status”, data representing the status of the user such as being present, absent, busy, etc. is stored.
[0103]
  FIG. 23 is a conceptual explanatory diagram of information stored in the setting DB 123 of the transmission-side client 120a. This DB stores which awareness information of the user A is distributed to the users B, C,. These pieces of information are assumed to have been sent from the receiving client 120b in advance.
[0104]
  Here, the setting DB stores “referencer ID”, “reference item”, and “notification item”. The referrer ID is an ID of a user who refers to the sender user A's awareness information. In the reference item, an item of awareness information that is referred to by the referrer is stored. In the notification item, awareness information that is desired to be notified promptly among the reference items is stored.
[0105]
  FIG. 24 is a conceptual explanatory diagram of information stored in the method DB 124 of the transmission client 120a. In this DB, (a) a communication history table, (b) a reference information data table, (c) a past method table, and (d) a communication information table are stored. Of these, the communication history table (a) corresponds to the communication history table of FIG. 4, the reference information data table (b) corresponds to the reference information data table of FIG. 4, and the past method table (c) corresponds to the past method table of FIG. .
[0106]
  However, in the communication history table (a), only information about the user who has registered the user A as a buddy is stored. Further, only information related to the user A is stored in the reference information data table (b). Furthermore, the past method table (c) stores only information about other users who have registered user A as buddies.
[0107]
  The communication information table (d) stores a communication path load, a communication client load and capacity, and a communication path capacity.
[0108]
  FIG. 25 is a conceptual explanatory diagram of information stored in the setting DB 123 of the receiving client 120b. This DB stores (a) a user setting data table and (b) a reference setting table. These tables store the same contents as the user setting data table and the reference setting data table of FIG.
[0109]
  FIG. 26 is a conceptual explanatory diagram of information stored in the method DB 124 of the receiving client 120b. In this DB, (a) a communication history table, (b) a capability table, and (c) a reference information table are stored. These tables store the same contents as the tables stored in the client side method DB of FIG.
[0110]
  [Process flow]
  Next, processing for determining a communication method in the present embodiment will be described. As described above, in this system, the transmission side device designates a communication method, and the reception side device determines a method for actual communication. Thereafter, the communication process based on the determined communication method is the same as the communication process described above. In the following, (1) a communication method designating method performed by the transmitting client and (2) a communication method determining process performed by the receiving client will be described.
[0111]
  (1) Communication method designation processing (transmission side)
  27 and 28 are flowcharts showing the flow of the communication method designation process performed by the transmission side client. The sending client 120a uses the method designation module 126 to perform the following processing. The transmission-side client 120a starts the following process when the user's awareness information is updated.
[0112]
  Steps S51 and S52: The sending client 120a refers to the method DB 124, and if the previous communication amount with the client 120b is less than 100 bytes / minute (S51), adds 20 points to the push method (S52).
[0113]
  Steps S53 and S54: The sending client 120a refers to the method DB 124, and if the previous communication time with the client 120b is less than 2 seconds on average (S53), 10 points are added to the push method (S54).
[0114]
  Steps S55 and S56: The sending client 120a refers to the method DB 124, and when the amount to be communicated is 10 Kbytes or more and the communication path capacity is medium or less (S55), 10 points are added to the push method (S56). .
[0115]
  Steps S57 and S58: The transmitting client 120a refers to the method DB 124, and when the transmitting side has a high load and the amount of communication is 10 Kbytes or more (S57), the pull method has 20 points and the notify method has 10 points. Are respectively added (S58).
[0116]
  Steps S59 and S510: The transmission side client 120a refers to the method DB 124, and when its own capability is low and the amount to be communicated is 10 Kbytes or more (S59), 20 points for the pull method and 10 points for the notify method Are respectively added (S510).
[0117]
  Steps S511 and S512: The transmission-side client 120a refers to the method DB 124 and determines whether the load on the communication path is high and the update frequency of the awareness information to be transmitted is equal to or higher than a predetermined value. Here, if the update frequency is 100 times or more per hour (S511), 30 points are added to the notify method (S512).
[0118]
  Steps S513 and S514: If the updated awareness information of the user A is important information (S513), the transmission-side client 120a adds 30 points to the push method (S514).
[0119]
  Steps S515, S516, S517: The transmitting client 120a determines whether or not the updated awareness information is specified in the notification item of the receiving user B (S515). In the case of the notification item, the sending client 120a uses the push method or the notify method with the higher point as the designation method (S516). If it is not a notification item, the designation method is the one with the highest point among the push, notify, and pull methods (S517).
[0120]
  Steps S518 and S519: The transmission-side client 120a refers to the method DB 124, and determines whether or not the designated method or its decision reason is different from the previous time (S518). If they are different, an inquiry is transmitted to the receiving client 120b (S519). This inquiry describes the communication method designated by the sending client 120a.
[0121]
  Steps S520 and S521: The transmitting client 120a waits for a communication method response from the receiving client 120b (S520), and determines the communication method notified by the answer as the final communication method (S521).
[0122]
  (2) Communication method decision processing
  FIG. 29 and FIG. 30 are flowcharts showing the flow of communication method determination processing performed by the receiving client. The receiving client 120b uses the method determining module 122 to determine the communication method based on the communication method designated by the transmitting client 120a and its own situation. The receiving client 120b starts the following process when a predetermined event occurs. The predetermined event is when there is an inquiry about a communication method from the sending client 120a, or when its own situation changes every predetermined time.
[0123]
  Steps S61 and S62: The receiving client 120b determines whether or not there is a designated method of the transmitting client 120a (S61), and if there is, adds 100 points to the communication method (S62).
[0124]
  Step S63: The receiving client 120b adds 50 points to the communication method designated by the transmitting client 120a.
[0125]
  Steps S64, S65, S66: The receiving client 120b determines whether or not the previous communication with the transmitting client 120a is a push method (S64). In the case of the push method, the following processing is performed depending on whether T <0 (S65). Here, T is expressed as follows using the communication charge CC and the charge target CD up to now. The communication charge CC and the charge target CD are read from the setting DB 123 and the system DB 124.
[0126]
  T = (CD-CC) / CD
  When T <0, the receiving client 120b adds 200 points to the pull method and 100 points to the notify method (S66). When T ≧ 0, the receiving client 120b adds (T × 200) points to the pull method and (T × 100) points to the notify method (S67).
[0127]
  Steps S68, S69, S610: The receiving client 120b refers to the setting DB 123 and determines whether or not the reference time has priority (S68). If the reference time is given priority, the receiving client 120b adds 30 points to the push method (S69). Otherwise, 50 points are added to the pull method and 30 points are added to the notify method (S610).
[0128]
  Steps S611 and S612: The receiving client 120b refers to the method DB 124 and determines whether or not its own load is high (S611). When the load is high, 20 points are added to the pull method and 10 points are added to the notify method (S612).
[0129]
  Steps S613 and S614: The receiving client 120b refers to the method DB 124 and determines whether or not its capability is low (S613). If the ability is low, 10 points are added to the pull method and 5 points are added to the notify method (S614).
[0130]
  Steps S615 and S616: The receiving client 120b refers to the method DB 124 and determines whether or not the reference frequency for referring to the awareness information of the user A is not less than a predetermined value, for example, 20 (times / hour) (S615). If it is equal to or greater than the predetermined value, the receiving client 120b adds 30 points to the push method and 20 points to the notify method (S616).
[0131]
  Steps S617 and S618: The receiving client 120b refers to the method DB 124 and the setting DB 123, and determines whether or not the communication path capability is low and the receiving user B prioritizes the reference time (S617). If so, the receiving client 120b adds 10 points to the push method (S618).
[0132]
  Steps S619, S620, S621: The receiving client 120b determines whether or not the user B has designated the updated awareness information of the user A as a notification item based on the setting DB 123 (S619). In the case of the notification item, the receiving client 120b determines the higher communication point of the push method or the notify method as the final communication method (S620). If it is not a notification item, the push method, notify method, or pull method having the highest point is determined as the final communication method (S621).
[0133]
  Step S622: The receiving client 120b notifies the transmitting client 120a of the determined final communication method, and ends the process.
[0134]
  After the communication method is determined as described above, the receiving client 120b and the transmitting client 120a switch the communication method to the determined method. This process is the same as the communication process on the server side and the client side in the first embodiment.
[0135]
  <Other embodiment examples>
  (A) There are various factors that affect communication other than those described in the above embodiment. By taking these into consideration and modifying the above-described determination process, various communication method determination methods are possible.
[0136]
  (B) A recording medium on which a program for executing the above-described method of the present invention is recorded is included in the present invention. Examples of the recording medium include a computer readable / writable floppy disk, hard disk, semiconductor memory, CD-ROM, DVD, magneto-optical disk (MO), and others.
[0137]
  <Appendix>
    (Appendix 1)
  A communication method switching method for transmitting and receiving information between a plurality of devices connected by a data communication path,
  When a predetermined event occurs in the first device, the first communication method is dynamically determined based on the communication environment of the first device,
  When a predetermined event occurs in the second device, the second communication method is dynamically determined based on the communication environment of the second device,
  Switching the communication method for transmitting information from one device to the other device to either the first communication method or the second communication method;
  Switching method of communication method.
[0138]
    (Appendix 2)
  The switching of the communication method according to appendix 1, wherein when the first device is an information transmission side, the communication method for transmitting information from one device to the other device is switched to the communication method determined by the first device. Method.
[0139]
  In this method, priority is given to the determination on the transmission side. However, as in the case where the transmission side is a server, the transmission side may be able to determine the communication method in consideration of the communication environment of the reception side to some extent.
[0140]
    (Appendix 3)
  The switching of the communication method according to appendix 1, wherein when the first device is an information receiving side, the communication method for transmitting information from one device to the other device is switched to the communication method determined by the first device. Method.
[0141]
  In this method, priority is given to the determination on the receiving side. For example, in a serverless system, since communication between clients is performed, there may be a case where priority is given to determination on the receiving side.
[0142]
    (Appendix 4)
  The communication method switching method according to appendix 1, wherein the first and second devices determine the first and second communication methods from any one of push, notify, and pull communication methods.
[0143]
    (Appendix 5)
  A communication method switching method for transmitting and receiving information between a plurality of devices connected by a data communication path,
  When a predetermined event occurs, the first device dynamically determines a first communication method for communicating with the predetermined second device based on the communication environment of the first device,
  The first device notifies the determined first communication method to the second device,
  The second device determines a second communication method for communicating with the first device based on a communication environment of the second device and the first communication method when a predetermined event occurs,
  Switching the communication method for transmitting information from one device to the other device to the second communication method;
  Switching method of communication method.
[0144]
    (Appendix 6)
  A communication method switching device used for a second device connected to a data communication path and transmitting / receiving information to / from the first device,
  Means for dynamically determining a communication method based on a communication environment of the second device when a predetermined event occurs in the second device;
  Means for negotiating with the first device to determine a communication method with the first device;
  Means for switching a communication method for communicating with the first device according to the result of the negotiation with the first device;
  A communication system switching device comprising:
[0145]
    (Appendix 7)
  A communication method switching device used for a second device connected to a data communication path and transmitting / receiving information to / from the first device,
  Means for receiving a notification of a first communication method determined by the first device based on a communication environment of the first device when a predetermined event occurs in the first device;
  Means for determining a communication method with the first device based on a communication environment of the second device and the first communication method;
  Means for switching a communication method for communicating with the first device according to the determination;
  A communication system switching device comprising:
[0146]
【The invention's effect】
  By using the present invention, it is possible to dynamically switch communication methods according to changes in various factors, effectively use network and computer resources, and reduce communication costs.
[Brief description of the drawings]
FIG. 1 is an overall configuration of an awareness system according to a first embodiment.
FIG. 2 is a conceptual explanatory diagram of information stored in a user DB.
FIG. 3 is a conceptual explanatory diagram of information stored in a server-side setting DB.
FIG. 4 is a conceptual explanatory diagram (1) of information stored in a server-side method DB.
FIG. 5 is a conceptual explanatory diagram (2) of information stored in a server-side method DB.
FIG. 6 is a conceptual explanatory diagram of information stored in a client-side setting DB.
FIG. 7 is a conceptual explanatory diagram of information stored in a client side method DB.
FIG. 8 is a flowchart showing a flow of determination processing (server side).
FIG. 9 is a flowchart (1) showing a flow of addition processing (server side).
FIG. 10 is a flowchart (2) showing the flow of addition processing (server side).
FIG. 11 is a flowchart showing a flow of designation processing (client side).
FIG. 12 is a flowchart showing a flow of communication processing (server side).
FIG. 13 is a flowchart showing a flow of communication processing (client side).
FIG. 14 is an overall configuration of an awareness system according to a second embodiment.
FIG. 15 is a conceptual explanatory diagram of information stored in a server-side setting DB.
FIG. 16 is a conceptual explanatory diagram (1) of information stored in a server-side method DB.
FIG. 17 is a conceptual explanatory diagram (2) of information stored in a server-side method DB.
FIG. 18 is a conceptual explanatory diagram of information accumulated in a client-side news DB.
FIG. 19 is a conceptual explanatory diagram of information stored in a client-side setting DB.
FIG. 20 is a conceptual explanatory diagram of information stored in a client side method DB.
FIG. 21 is an overall configuration of an awareness system according to a third embodiment.
FIG. 22 is a conceptual explanatory diagram of information stored in a user information DB on the transmission side.
FIG. 23 is a conceptual explanatory diagram of information stored in a transmission side setting DB.
FIG. 24 is a conceptual explanatory diagram of information stored in a transmission-side method DB.
FIG. 25 is a conceptual explanatory diagram of information stored in a receiving side setting DB.
FIG. 26 is a conceptual explanatory diagram of information stored in a reception-side method DB.
FIG. 27 is a flowchart (1) showing a flow of designation processing (transmission side).
FIG. 28 is a flowchart (2) showing the flow of the designation process (transmission side).
FIG. 29 is a flowchart (1) showing a flow of determination processing (reception side).
FIG. 30 is a flowchart (2) showing a flow of determination processing (reception side).
[Explanation of symbols]
  1: Awareness server
  2; Client
  3; Network

Claims (4)

A communication method executed by the transmission apparatus when performing communication of information between a transmission apparatus and a reception apparatus connected by a data communication path by any one of a push, notify, or pull communication system. ,
  When the information is updated, the communication method of the information is determined based on the state information of the transmitting device and the state information of the receiving device provided from the receiving device,
  If the determined communication method is a push method, the updated information is transmitted to the receiving device,
  If the determined communication method is a notify method, an update notification is sent to the receiving device,
  A communication method for transmitting the updated information to the receiving device based on an information acquisition request from the receiving device when the determined communication method is a notify method or a pull method. A transmission device used in a communication system that communicates information in a communication method of push, notify, or pull method between a transmission device and a reception device connected by a data communication path,
  When the information is updated, a method determination unit that determines a communication method of the information based on the state information of the transmission device and the state information of the reception device provided from the reception device;
  When the determined communication method is a push method, the updated information is transmitted to the receiving device. When the determined communication method is a notify method, an update notification is transmitted to the receiving device. In the case of the phi method or the pull method, an information transmitting unit that transmits the updated information to the receiving device based on an information acquisition request from the receiving device;
  A transmission apparatus comprising: The method determination unit includes a history storage unit that records the determined communication method;
A determination method notifying unit for notifying the receiving device of the determined communication method when the previous communication method recorded in the history storage unit is different from the determined communication method;
The transmission device according to claim 2, further comprising: The state information of the transmission device includes at least one of the capability of the transmission device, the load status of the transmission device, or information indicating the update frequency of the information,
  The status information of the receiving device includes at least one of the capability of the receiving device, a load status of the receiving device, a reference frequency of the information, and information indicating a communication method set by the receiving device. Item 4. The transmission device according to Item 2-3.

Images