WO2000033193A1 - Procede, dispositif et systeme de fourniture d'informations, et moyen d'enregistrement - Google Patents

Procede, dispositif et systeme de fourniture d'informations, et moyen d'enregistrement Download PDF

Info

Publication number
WO2000033193A1
WO2000033193A1 PCT/JP1998/005378 JP9805378W WO0033193A1 WO 2000033193 A1 WO2000033193 A1 WO 2000033193A1 JP 9805378 W JP9805378 W JP 9805378W WO 0033193 A1 WO0033193 A1 WO 0033193A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
configuration list
file
information file
machine
Prior art date
Application number
PCT/JP1998/005378
Other languages
English (en)
Japanese (ja)
Inventor
Yoshiko Sakanishi
Yukio Ooi
Mitsunori Itou
Original Assignee
Hitachi, Ltd.
Hitachi Software Engineering Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi, Ltd., Hitachi Software Engineering Co., Ltd. filed Critical Hitachi, Ltd.
Priority to JP2000585767A priority Critical patent/JP3811615B2/ja
Priority to PCT/JP1998/005378 priority patent/WO2000033193A1/fr
Publication of WO2000033193A1 publication Critical patent/WO2000033193A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
    • H04N21/4508—Management of client data or end-user data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G06F16/219—Managing data history or versioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/433—Content storage operation, e.g. storage operation in response to a pause request, caching operations
    • H04N21/4334—Recording operations

Definitions

  • the present invention relates to an apparatus, a system, a method, and a recording medium for distributing information to one or more machines through a transmission means such as a network.
  • the most widely known means of information distribution is "information sharing" and "information transmission” using Word 1d Wide Web (WWW).
  • WWW Word 1d Wide Web
  • Many home pages have been set up to provide information between companies, business partners or unspecified users.
  • the information distribution method adopted in the WWW is designed to avoid squeezing the disk of the receiving machine, and all the latest information is distributed every time a reception request is made.
  • the registration file is edited and managed as one file for ease of management.
  • the sender manages the generation of the information that has been sent to the receiver, and extracts and registers the update information from one or more generations beforehand, and the receiver matches the information generation that has already been received. Update information, or extract the update information between one generation and register it in order, and if the information of the received information is multiple generations earlier, the oldest generation update information The transfer efficiency is improved by using means for sequentially distributing the generation update information.
  • the WWW means When distributing information, considering how efficiently information can be distributed, the WWW means discards the information obtained by one access each time, so when accessing the second time In addition, all information will be downloaded. Even when distributing "information" that frequently changes a little, all the latest information is always distributed, placing a load on the sending machine and line, resulting in inefficient transfer volume and transfer There is a problem that billing occurs in proportion to time. In addition, information can be downloaded only when connected to the sender, and the information is not saved at the receiver. If it cannot connect to the other machine, there is a problem that the information cannot be referred to on the receiving side.
  • a means of a conventional software distribution product is a system capable of appropriately managing a reception state on a reception side on a transmission side.
  • a network such as the Internet
  • the better the frequency of all received machines access the transmission machine than the update frequency of the software Touea information such as programs and data to be delivered subject
  • the frequency of operation is too frequent, and it is rare that the generation of the information received on the receiving side is more than two generations older than the generation of the latest information.
  • the frequency of access to information depends on the situation of the receiving side, such as how much information the receiving side needs or how much information is used. Some types of information, such as forecasts and stock price information, may change every few hours or minutes depending on the type of information. Furthermore, it is conceivable to read information from a portable medium and replace the information on the receiving side.
  • the distribution information is updated frequently, and if there is a possibility that the information may be unilaterally updated on the receiving side, the receiving side will receive it
  • the generations of information that have already been received vary, and it is necessary for the transmitting side to realize efficient distribution in response to many different generations that have been received on the receiving side.
  • An object of the present invention is to minimize the load on a line and a machine on a transmitting side and a receiving side at the time of information distribution, and to reduce the load of an administrator or a receiver from any information receiving state even when updating information.
  • An object of the present invention is to provide an information distribution apparatus, a system, a method, and a recording medium that automatically obtain optimum update information and efficiently distribute information without bothering. Disclosure of the invention
  • the above object is an information distribution method in a transmitting machine that distributes information constituted by a file to a receiving machine, wherein the transmitting machine has a configuration list corresponding to a first information file and an update target. Comparing with the configuration list corresponding to the second information file, extracting update information for updating the second information file to the first information file from the comparison result, and extracting the updated information. This is achieved by transmitting information to the receiving machine.
  • the transmitting machine manages a configuration list group including a configuration list corresponding to a first information file, and searches the configuration list group for a configuration list corresponding to a first information file, This is achieved by comparing the configuration list corresponding to the first information file with the configuration list corresponding to the second information file to be updated.
  • the transmitting machine manages a configuration list for each attribute, receives attribute information of a second information file to be updated from a receiving machine, and receives a first information from a configuration list group according to the attribute information. This is achieved by searching the configuration list corresponding to the information file of the above. Further, the transmitting machine manages a configuration list group including a first information file and a configuration list corresponding to the first information file as an update history, and receives a second update target from the receiving machine. Receiving the information of the second information file from the group of configuration lists corresponding to the second information file, and searching the configuration list corresponding to the first information file and the second information file. This is achieved by comparing the configuration list with the corresponding configuration list.
  • the transmitting machine transmits the configuration list of the first information file to the receiving machine together with the update information. Further, the transmission side machine stores the extracted update information, and when receiving the same request from the reception machine, this is achieved by transmitting the stored update information. Further, the transmission side machine manages the content by associating the same file, and when there are a plurality of files having the same content in the update information, this is achieved by transmitting one of the files having the same content. . Further, the transmitting machine, if a third information file whose content matches the information file included in the extracted update information exists in the receiving machine, information whose content matches the third information file. This is achieved by sending update information excluding files.
  • An information distribution method for distributing information constituted by a file to a receiving machine wherein the transmitting machine corresponds to a configuration list corresponding to the first information file and a second information file to be updated
  • a configuration list is compared, update information for updating the second information file to the first information file is extracted from the comparison result, and the extracted update information is transmitted to the receiving machine.
  • the receiving side machine achieves this by updating the second information file to a first information file based on the received update information.
  • the receiving machine updates the second information file to the first information file based on the received update information, and deletes unnecessary files.
  • the receiving machine manages the receiving state of the update information, creates a configuration list indicating the information on the receiving state, and transmits the configuration list to the transmitting machine.
  • the receiving machine obtains the second information file from a machine other than the transmitting machine, the receiving machine creates a configuration list corresponding to a second information file on the receiving machine, and transmits the configuration list to the transmitting machine. Achieved by doing
  • An information distribution device that distributes information constituted by a file to a receiving device, wherein the information distribution device stores a configuration list corresponding to the first information file and a second information file to be updated. Comparing means for comparing a corresponding configuration list with the corresponding configuration list; extracting means for extracting update information for updating the second information file to the first information file from the comparison result; This is achieved by having transmitting means for transmitting to the receiving device. Further, the information distribution device manages a configuration list group including a configuration list corresponding to a first information file, and searches the configuration list corresponding to the first information file from the configuration list group Achieved by having search means.
  • the information distribution device includes: a management unit that manages a configuration list group including a first information file and a configuration list corresponding to the first information file as an update history; This is achieved by having a search means for receiving the information of the second information file and searching for a configuration list corresponding to the second information file from the configuration list group.
  • an information distribution system including a receiving device and a transmitting device that transmits information constituted by a file to the receiving device, wherein the transmitting device has a configuration list corresponding to a first information file.
  • Comparing means for comparing the second information file with the configuration list corresponding to the second information file to be updated; and updating the second information file to the first information file based on the comparison result by the comparing means.
  • Extracting means for extracting update information; and transmitting means for transmitting the update information extracted by the extracting means to the receiving device, wherein the receiving device receives the update information from the transmitting device. This is achieved by having receiving means for performing the above, and updating means for updating the second information file into a first information file based on the update information.
  • the recording medium stores an information distribution program in a transmission side machine that distributes information constituted by a file to a reception side machine, wherein the information distribution program includes a configuration list corresponding to a first information file and an update.
  • a configuration list corresponding to the target second information file is compared, update information for updating the second information file to the first information file is extracted from the comparison result, and the extracted information is extracted. This is achieved by sending update information to the receiving machine.
  • the present invention is achieved by managing a configuration list group including a configuration list corresponding to a first information file, and retrieving a configuration list corresponding to the first information file from the configuration list group.
  • a configuration list group including a first information file and a configuration list corresponding to the first information file is managed as an update history, and information on the second information file to be updated is received from the receiving machine. This is achieved by retrieving a configuration list corresponding to the second information file from the configuration list group.
  • FIG. 1 is a configuration diagram of an information distribution system for realizing information distribution of the present invention.
  • FIG. 2 is an example of a configuration list showing the configuration of the distribution information of the present invention.
  • FIG. 3 is a flowchart showing the flow of processing on the transmission side when the transmission side determines the necessity of distribution by the information distribution method of the present invention.
  • FIG. 4 is a flowchart showing the flow of processing on the receiving side when the transmitting side determines the necessity of distribution by the information distribution method of the present invention.
  • FIG. 5 is a flowchart showing the flow of processing when the receiving side determines the necessity of distribution by the information distribution method of the present invention.
  • Fig. 6 shows the information management status on the transmitting side in the information distribution method of the present invention. It is a state transition diagram.
  • FIG. 1 is a configuration diagram of an information distribution system for realizing information distribution of the present invention.
  • FIG. 2 is an example of a configuration list showing the configuration of the distribution information of the present invention.
  • FIG. 3
  • FIG. 7 is a flowchart when information is distributed to a receiving side for the first time by the information distribution method of the present invention.
  • FIG. 8 is a flow chart in a case where update information is distributed when the receiving side has already received information of a generation not managed by the transmitting side in the information distribution method of the present invention.
  • FIG. 9 is a flow chart in a case where update information is distributed when information of a generation managed by the transmission side has already been received by the reception side by the information distribution method of the present invention.
  • FIG. 10 is a flowchart in the case of distributing update information when a failure has occurred during information distribution in the information distribution method of the present invention.
  • FIG. 11 is a transition diagram of a management state in a case where information is managed for each attribute on the transmission side by the information distribution method of the present invention.
  • FIG. 12 is a transition diagram of a management state in the case where information is managed for each attribute on the transmission side by the information distribution method of the present invention.
  • FIG. 13 is a flowchart in the case where update information is distributed when the receiving side has already received information of a generation not managed by the transmitting side by the information distribution method of the present invention.
  • FIG. 14 is a flowchart in the case where information is read from a portable medium or the like on the receiving side and updated by the information distribution method of the present invention, and then the updated information is distributed from the transmitting side.
  • FIG. 12 is a transition diagram of a management state in the case where information is managed for each attribute on the transmission side by the information distribution method of the present invention.
  • FIG. 13 is a flowchart in the case where update information is distributed when the receiving side has already received information of a generation not managed by the
  • FIG. 15 is a flowchart in the case of distributing update information excluding duplicate files by the information distribution method of the present invention.
  • FIG. 16 is a flowchart in the case of distributing update information excluding files already distributed to the receiving side by the information distribution method of the present invention.
  • the present invention manages the registered latest information as a collection of files including directories, creates a configuration list, searches the corresponding configuration list from the generation information sent from the receiving side, and searches for the latest information. Compare the configuration list, or compare the configuration list sent from the receiver with the latest configuration list, or the latest generation sent from the sender or the generation of information whose configuration and receiver have been received Alternatively, only the changed information is extracted by comparing the configurations, and update information is created and distributed according to the reception status of the receiving machine. Also, based on a comparison of the old and new configuration lists managed on the transmitting side, the extracted update information is stored as the inter-generational update information on the transmitting side, and is extracted in response to subsequent similar information requests.
  • FIG. 1 is a configuration diagram of the information distribution system of the present invention.
  • reference numeral 11 denotes a Web browser capable of referring to management information.
  • Reference numeral 12 denotes a system for registering the latest information.
  • Each of the servers 13 and 14 may be considered as having a parent-child relationship.
  • 16 is a client that receives information from the server.
  • FIG. 2 is an example of a configuration list showing the configuration of an information file.
  • the configuration list includes at least information such as the file path (file name) (21), file update date and time (22), and file size (23). Based on the information in this list, You can determine whether the latest information has been updated.
  • FIGS. 3 and 4 show a processing flowchart of the transmitting side and FIG. 4 shows a processing flowchart of the receiving side when the transmitting side determines the necessity of distribution.
  • the transmitting side (Fig. 3)
  • the version (generation number) is set (S302), and if the configuration list does not exist, the configuration list is used.
  • Generate (S303).
  • the configuration list is created and registered by the information provider. Is also good. If the same content file is not to be duplicated, a file list is created for each registered file and added to the same file management information (S304).
  • S305 When the request is received from the receiving side (S305), it is determined whether or not a version is specified in the request message (S306).
  • the version is already generated. It is determined whether or not the updated information that has been cached has been cached (S315), and if it has been cached, a search is made for the same file from the extracted updated information and the latest configuration list (S309). If the same file is not checked as a result of the same file check (S310), the information is distributed as it is (S312), and if the same file exists, the distribution information is edited (S311). And distribute (S 3 1 2). The same file does not need to be in the information distributed at once, but may be in the information already received by the receiver. In this case, there is no file substance in the distribution information after editing, and link information to the distributed information is added.
  • the configuration list of one or more generations managed by the transmitting side is requested.
  • the configuration list corresponding to the version is searched from the data list (S316), and if it is determined that there is a corresponding configuration list (S316), the configuration list of the latest information and the corresponding configuration list are determined.
  • S320 update information is extracted (S321), the update information is cached (S322), and the extracted update information and the latest configuration list are searched for the same file.
  • the list of the latest information After comparing the data with the received configuration list (S320), extracting the update information (S321), and caching the update information (S322), the extracted update information and the latest configuration The list is searched for the presence or absence of the same file (S309), and as a result of checking the same file (S310), if the same file does not exist, the information is delivered as it is (S312) and the same file is sent. If there is, edit the distribution information (S311) and distribute (S312).
  • the specification in the request message from the receiving side is not the version specification and it is determined that there is no configuration list specification (S307), all the latest information and the latest configuration list are extracted (S300) 8) Then, the presence or absence of the same file is searched (S309), and if the same file is not found as a result of the same file check (S310), the information is delivered as is (S312) If there is the same file, the distribution information is edited (S311) and distributed (S312). If a configuration list has been specified, the latest configuration list is compared with the received configuration list (S313), update information is extracted (S314), and the extracted update information and the latest update list are compared.
  • the same list is searched for the presence or absence of the same file from the configuration list (S309), and if the same file is not found as a result of the same file check (S310), the information is delivered as it is (S312). If the same file exists, the distribution information is edited (S311) and distributed (S312).
  • the receiving side (Fig. 4) checks the reception status of the information to be received (S401), determines that there is no information already received (S402), and specifies only the name of the information.
  • An information reception request is transmitted (S403), and all the latest information and the latest configuration list are received (S404). If it is determined that there is already received information (S405), it is checked whether there was an error in the previous update (S405).
  • An information reception request is transmitted (S408), and if there is a configuration list request (S409), an information reception request (S408) is specified by specifying the received configuration list. ) I do.
  • There is already information received If it is determined that the previous update is in an error state (S405), a configuration list of the received information is generated (S406), and the generated configuration list is specified to request an information reception (S405). 407) is performed.
  • the update information of the requested information and the latest configuration list are received (S410), it is checked whether or not the received update information has been edited when the same file exists (S411).
  • FIG. 5 is a processing flowchart when the reception side determines whether or not reception is necessary.
  • the transmitting side accepts the request from the receiving side (S501), and if it is the latest information distribution request (S502), executes the latest information distribution processing described in FIG. 3 (S503). If a request for the latest version or information for discriminating between new and old information is made (S504), the latest version number or new and old identification information is transmitted (S505). If the request is for the latest configuration list (S506), the latest configuration list is transmitted (S507).
  • the receiving side checks the receiving status (S511), and judges that the received information has no version information (S512), and requests the transmitting side for a list of the latest information (S5).
  • FIG. 6 is a diagram showing changes in the information management state in the server at the time of information update.
  • the figure shows an example in which the number of generations to be managed is set to 2 for simplicity, but the number of generations to be managed can be arbitrarily determined in consideration of the update frequency of the information to be managed. It is possible to specify.
  • DB 61, 62
  • information is updated (61 to 64)
  • the latest information is registered in the server
  • a configuration list corresponding to the updated information is generated and added to the DB (66), and the information storage DB (66) is created. ) Is replaced with the latest information.
  • the latest information is registered in the server, a configuration list corresponding to the updated information is generated and added to the DB (69), and the information storage DB is added. Replace the information in (68) with the latest information.
  • the DB (69) that manages the configuration list the number of generations to be managed is larger than the specified number of generations to be managed (two generations), so that the oldest version is supported.
  • the configuration list has been deleted from the management DB. In this example, only the information part is registered at the time of registration. However, as shown in the example of FIG. 11, it is also possible to add and register a configuration list generated in advance.
  • FIG. 7 shows a sequence when the receiving side receives information for the first time. Since the receiving side has no received information, the name of the specified information is specified and the latest information is requested (72), and the transmitting side receives the information (75) in the information storage DB (73). The latest configuration list (76) in the configuration list storage DB (74) is stored. The information is extracted and distributed, and the receiving side stores the received information (77) and the latest configuration list (78) in the information storage DB (79).
  • FIG. 8 shows a sequence in a case where the receiving side has received the latest information when the version “00001” information has been received. Since the receiving side has received information (801), it requests the latest information (802) by specifying the name and version of the information, and the transmitting side checks the cache (805), Since there is no corresponding update information, the configuration list in the configuration list storage DB (804) is searched, and the configuration list of the corresponding version has already been deleted. A transmission request (806) is made. The receiving side extracts the configuration list (807) from the DB (810) storing the received information and transmits (808) to the transmitting side.
  • the transmitting side compares the received configuration list (809) with the latest configuration list (810), extracts update information (8111), and converts the version "00001" to "0101".
  • the update information to “00 03” is stored in the cache (8 12), and the update information (8 11) and the latest configuration list (8 10) are distributed (8 13) to the receiving side.
  • the receiving side adds the received update information (8 14) to the contents of the DB (801), and deletes the “A 1” file from the contents of the latest configuration list (8 15) as unnecessary. Then, it is stored in the information storage DB (8 16) together with the latest configuration list in the same way as the contents of the latest configuration file.
  • FIG. 9 shows a sequence in a case where the receiving side receives the latest information when the information of the version “00002” has been received. Since the receiving side has received information (901), it requests the latest information (902) by specifying the name and version of the information, and the transmitting side checks the cache (905). Since there is no corresponding update information, the configuration list in the configuration list storage DB (904) is searched, and the configuration list of the corresponding version exists, so the configuration of the corresponding version is found. List (900) and latest configuration list (907) And update information (990) is extracted and stored in the cache (909) as update information from version "00002" to "00003", and update information (990) ) And the latest configuration list (907) are distributed (910) to the receiving side.
  • the receiving side adds the received update information (911) to the contents of the DB (900 ⁇ ), and deletes the “ ⁇ 1” file from the contents of the latest configuration list (910 1) as it is unnecessary. Then, the same contents as the latest configuration file are stored in the information storage DB (913) together with the latest configuration list.
  • FIG. 10 shows a sequence in a case where the receiving side receives update information from an incomplete reception state when a failure occurs while receiving the information of the version “00001”. Since the receiving side has received information (1001), it requests the latest information (1002) by specifying the name and version of the information, and the transmitting side sends a cache (1005). ), And there is applicable update information, so update information “ ⁇ 3” and “ ⁇ 4” (100 6 ) And the latest configuration list (1007) are distributed (1008) to the receiving side.
  • the receiving side receives the update information (1 0 0 9) is added to the contents of D ((101), and the reception status is changed to “update error” (1012).
  • a configuration list (1013) indicating the latest configuration of the receiving side in the update error state is generated, and the configuration list is transmitted (101) at the time of the information request.
  • the transmitting side compares the received configuration list (101) with the latest information configuration list (101) to extract updated information (101) and distributes it to the receiving side. (1 0 18).
  • the receiving side receives the update information “A4” (0119) and the latest configuration list (0101) that could not be received last time, and stores the latest information in the DB.
  • FIGS. 11 and 12 are diagrams showing changes in the management state of information in the server when updating information having a plurality of attributes. Attributes are classified by business, such as sales or office work, to which the recipient belongs, or by job system, such as department manager or section manager, or by machine type, such as PC or WS, to which the receiving terminal belongs, or 0S type, such as Windows or OSZ2. Can be arbitrarily set.
  • the figure shows an example in which the number of generations to be managed is set to 2 for simplicity, but the number of generations to be managed is arbitrarily specified in consideration of the update frequency of the information to be managed.
  • the server DB (1108, 110) is registered with the latest information. 9) is updated.
  • the number of generations of the attribute C to be managed becomes larger than the specified number of generations of the management target (two generations), and the oldest version is supported.
  • the first 3 Figure c, which removes the configuration list from the management DB indicates a sequence when receiving the latest information when receiver information version attribute C "0 0 0 1" in the received already.
  • the receiving side On the receiving side Has received information (1222), requests the latest information (1203) by specifying the information name and attribute information (1221) and the version, and the sending side caches After confirming (1206), there is no relevant update information, so the configuration list in the configuration list storage DB (125) is searched, and the configuration list of the corresponding version has already been deleted. Therefore, a request for transmission of the configuration list is made to the receiving side (1207).
  • all attributes are sent from the receiving side.However, if the sending side manages information that associates one or more attributes with the receiving side, the management Information can also be used.
  • the receiving side extracts the configuration list (1208) from the DB (1202) storing the received information and transmits it to the transmitting side (1209).
  • the transmitting side compares the received configuration list (1 2 1 0) of attribute C with the latest configuration list (1 2 1 1), extracts update information (1 2 1 2), and checks the attribute C John Stores the update information from “00 1” to “0 0 3” in the cache (1 2 1 3) and receives the update information (1 2 1 2) and the latest configuration list (1 2 1 1) Delivery to the side (1 2 1 4).
  • the receiving side adds the received update information (1 2 1 5) to the contents of the DB (1 2 1 7), and judges that the "A 3" file is unnecessary from the contents of the latest configuration list (1 2 16). And delete it and store it in the information storage DB (1 2 1 7) together with the latest configuration list with the same contents as the latest configuration file.
  • the common configuration list in the description of FIG. 8 is replaced with a configuration list for each attribute, and it is possible to reduce the distribution information.
  • FIG. 14 shows a sequence in a case where information is read from a portable medium or the like on the receiving side and updated, and then the updated information is distributed from the transmitting side.
  • the information (1301) already received on the receiving side is transferred to the information file from the portable medium (1302).
  • a configuration list is generated when the file is updated, and stored as the latest information (1303).
  • the generated configuration list (1304) is specified and the latest information is requested (1305), and the transmission side receives the configuration list and the latest information configuration list (1304).
  • Update information (1310) is extracted based on 1309).
  • the extracted information (1311) and the configuration list (1309) of the latest information are transmitted to the receiving side (1311), and the receiving side updates the latest information based on the received information.
  • FIG. 15 shows a sequence in the case where the receiving side designates all the information management names that the user wants to receive at one time and makes an information update request.
  • the receiving side generates a list of information to be received at once (1401), specifies the request list and requests the latest information (1402), and the transmitting side generates the list based on the received information and the management information.
  • update information (1405, 1406) is extracted. If there is a matching file in the extracted information, the file entity is managed by unique information such as the serial number, and management information indicating the file entity is added to the configuration list information.
  • the "002" file matches the "Notices" information and the "Management / Business information” information.
  • the information "002" is redundantly added.
  • a file with a “1” in the file column indicates that the file has not changed from the received information.
  • the updated information (1407, 14008, 14009) after editing is distributed (14410) to the receiving side, and the receiving side receives the updated information based on the received information. Update information to the latest information.
  • Fig. 16 shows a system in which the receiver specifies all the information management names that he or she wants to receive at once and the information management name that has already been received, makes an information update request, and receives only files that do not exist on the receiver. Indicates one can.
  • the information (1501) to be newly distributed is registered in the server, the information is updated to the latest information (1503), and at the same time, the "type", Size ”and“ contents ”in the list (1504).
  • files classified by one or more types are further classified by one or more sizes, and files with the same content among the files of the same size are listed. It is managed (1504). Therefore, it is possible to manage one or more fireworks lists with different contents by combining "species" and "sizes”.
  • the matching file list includes at least information of “information management name”, “generation number (version number)”, and “file path”, and is a list that collects only information of files whose contents match. .
  • one file entity may be managed for each list of matching files.
  • the receiving side generates a list of information to be received at once and information already received (1505), specifies the request list, and requests the latest information (1406). Update information (1509) is extracted based on the management information.
  • the information is managed using unique information such as the management list, and information such as the management information indicating the file entity or the management name of the already delivered information ⁇ file path is added to the configuration list information.
  • the "002" file matches in the "communications” information and the "management and business information” information. Since the files “003” and “004” match the already distributed files, the file entities are excluded from distribution.
  • the edited update information (1511, 1512) is distributed to the receiving side (1513), and the receiving side updates the received information to the latest information based on the received information. .
  • the generation of the information already received by the receiving machine is 1 Even if the information is one or several generations earlier, or if the transmitting machine cannot identify the generation of the received information at the sending machine, it is possible to distribute the optimal update information or duplicate the same information By not distributing the information, it is possible to provide a device, a system, a method, and a recording medium that reduce the processing load and the line load on the transmission side and the reception side and perform efficient information distribution.
  • the present invention is useful for minimizing the load on the line and the transmitting and receiving machines at the time of information distribution and performing efficient information distribution. It is suitable for use in environments where reception conditions are not uniform.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Information Transfer Between Computers (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un procédé, un dispositif et un système permettant de fournir fréquemment à un client possédant des versions multiples des informations actualisées, de façon sure et efficace, ainsi qu'un moyen d'enregistrement. Une version de l'information déjà reçue par le client est transmise à un serveur. N'est communiquée que la partie mise à jour. A cette fin, on extrait la différence entre la liste qui compose l'information de la version gérée côté serveur, et l'information de la version la plus récente, ou bien l'information renseignant sur la composition de l'information en provenance du client est transmise et comparée à l'information la plus récente côté serveur et seule la partie mise à jour est transmise après extraction de la différence.
PCT/JP1998/005378 1998-11-30 1998-11-30 Procede, dispositif et systeme de fourniture d'informations, et moyen d'enregistrement WO2000033193A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2000585767A JP3811615B2 (ja) 1998-11-30 1998-11-30 情報配信システム、装置及び方法並びに記録媒体
PCT/JP1998/005378 WO2000033193A1 (fr) 1998-11-30 1998-11-30 Procede, dispositif et systeme de fourniture d'informations, et moyen d'enregistrement

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP1998/005378 WO2000033193A1 (fr) 1998-11-30 1998-11-30 Procede, dispositif et systeme de fourniture d'informations, et moyen d'enregistrement

Publications (1)

Publication Number Publication Date
WO2000033193A1 true WO2000033193A1 (fr) 2000-06-08

Family

ID=14209489

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP1998/005378 WO2000033193A1 (fr) 1998-11-30 1998-11-30 Procede, dispositif et systeme de fourniture d'informations, et moyen d'enregistrement

Country Status (2)

Country Link
JP (1) JP3811615B2 (fr)
WO (1) WO2000033193A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002116938A (ja) * 2000-10-11 2002-04-19 Id Gate Co Ltd 世代管理機能を備えたファイルバックアップ方法
JP2006260212A (ja) * 2005-03-17 2006-09-28 Nec Corp ファイル版管理システム、ファイル登録サーバ、ファイル版管理方法、およびプログラム
JP2011040107A (ja) * 2008-06-04 2011-02-24 Athena Telecom Lab Inc データベース並行編集方式
JP2011044181A (ja) * 2008-06-04 2011-03-03 Athena Telecom Lab Inc データベースのデータ項目の平行編集方式
JPWO2009147846A1 (ja) * 2008-06-04 2011-10-27 株式会社アテナテレコムラボ データベース並行編集の競合解消方式
US8050663B2 (en) 2005-04-15 2011-11-01 Kt Corporation System and method of providing contents for mobile communication terminal
US8145989B2 (en) 2005-04-15 2012-03-27 Kt Corporation System and method for providing continuous downloading service of large size contents through wireless network and computer readable medium for realizing the same
US10147081B2 (en) 2005-04-15 2018-12-04 Kt Corporation Method for providing contents

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS63262724A (ja) * 1987-04-02 1988-10-31 インターナシヨナル・ビジネス・マシーンズ・コーポレーション データ処理ネツトワーク

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS63262724A (ja) * 1987-04-02 1988-10-31 インターナシヨナル・ビジネス・マシーンズ・コーポレーション データ処理ネツトワーク

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002116938A (ja) * 2000-10-11 2002-04-19 Id Gate Co Ltd 世代管理機能を備えたファイルバックアップ方法
JP2006260212A (ja) * 2005-03-17 2006-09-28 Nec Corp ファイル版管理システム、ファイル登録サーバ、ファイル版管理方法、およびプログラム
US8050663B2 (en) 2005-04-15 2011-11-01 Kt Corporation System and method of providing contents for mobile communication terminal
US8145989B2 (en) 2005-04-15 2012-03-27 Kt Corporation System and method for providing continuous downloading service of large size contents through wireless network and computer readable medium for realizing the same
US10147081B2 (en) 2005-04-15 2018-12-04 Kt Corporation Method for providing contents
JP2011040107A (ja) * 2008-06-04 2011-02-24 Athena Telecom Lab Inc データベース並行編集方式
JP2011044181A (ja) * 2008-06-04 2011-03-03 Athena Telecom Lab Inc データベースのデータ項目の平行編集方式
JPWO2009147846A1 (ja) * 2008-06-04 2011-10-27 株式会社アテナテレコムラボ データベース並行編集の競合解消方式
JP5543918B2 (ja) * 2008-06-04 2014-07-09 株式会社アテナテレコムラボ データベース並行編集の競合解消方式

Also Published As

Publication number Publication date
JP3811615B2 (ja) 2006-08-23

Similar Documents

Publication Publication Date Title
JP3990115B2 (ja) サーバ側プロキシ装置及びプログラム
EP1739905B1 (fr) Procédé et système de gestion de messages électroniques
US9769278B2 (en) Providing local access to managed content
AU762283B2 (en) Content addressable information encapsulation, representation, and transfer
US7765228B2 (en) Method and system for data collection for alert delivery
US7415731B2 (en) Content addressable information encapsulation, representation, and transfer
USRE42051E1 (en) Peer-to-peer automated anonymous asynchronous file sharing
JP3885483B2 (ja) サービス実行方法および装置
CN101093497B (zh) 文档管理服务器、文档管理方法及管理文档使用的系统
US20030033283A1 (en) Data access
US8676855B2 (en) Distributed storage system, management apparatus, node apparatus, recording medium on which node program is recorded, page information acquisition method, recording medium on which page information sending program is recorded, and page information sending method
JP2009518757A (ja) 無線装置の最新データを維持するための方法及びシステム
US7584196B2 (en) Systems and methods for remote storage of electronic data
GB2321730A (en) Electronic conference system keeping consistency of messages between servers
US6999991B1 (en) Push service system and push service processing method
EP1225766A2 (fr) Système utilisant une historique de visualisation et appareil correspondant
JP3811615B2 (ja) 情報配信システム、装置及び方法並びに記録媒体
JP2004178121A (ja) ソフトウェア資産管理方法及びシステム
JP2009129195A (ja) バックアップサーバ、移動機、およびこれらを用いた通信システム、ならびにバックアップ方法
JP2001216184A (ja) 送信装置、受信装置、送受信システム、送信方法、および受信方法
CN111314407B (zh) 用于处理元数据的通信设备和通信方法
US8849920B2 (en) Management of broadcast-distributed data entities
JP2004280847A (ja) 情報中継装置及び記憶媒体
JPH11203321A (ja) メタ情報管理機能を備えた情報提供装置
JP2000156703A (ja) 交換用コンピュータ及び電子データ交換システム及び振り分け解析プログラムを記録したコンピュータ読み取り可能な記録媒体

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): CA CN JP KR SG US

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
ENP Entry into the national phase

Ref country code: JP

Ref document number: 2000 585767

Kind code of ref document: A

Format of ref document f/p: F

122 Ep: pct application non-entry in european phase