Source: http://www.google.com/patents/US20040122851?dq=mirroring+data+in+a+remote+data+storage+system
Timestamp: 2017-08-22 11:27:25
Document Index: 749588123

Matched Legal Cases: ['art 2701', 'art 2702', 'art 2703', 'art 2705', 'art 2706', 'art 2703', 'art 1102', 'art 1103', 'art 1108', 'art 1109', 'art 1103', 'art 1104', 'art 1105', 'art 1106', 'art 1107', 'art 1701', 'art 1702', 'art 1702', 'art 1701', 'art 1102', 'art 1103', 'art 2102']

Patent US20040122851 - Identifier generating method, identity determining method, identifier ... - Google Patents
An identifier generating method according to the present invention has a canonicalization process step of subjecting document data to a canonicalization process to correct fluctuation of expression; and an identifier generating step of, based on all or part of document data having been subjected to the...http://www.google.com/patents/US20040122851?utm_source=gb-gplus-sharePatent US20040122851 - Identifier generating method, identity determining method, identifier transmitting method, identifier generating apparatus, identity determining apparatus, and identifier transmitting apparatus
Publication number US20040122851 A1
Application number US 10/659,308
Also published as CN1494018A, DE60330099D1, EP1398712A2, EP1398712A3, EP1398712B1, US7200585
Publication number 10659308, 659308, US 2004/0122851 A1, US 2004/122851 A1, US 20040122851 A1, US 20040122851A1, US 2004122851 A1, US 2004122851A1, US-A1-20040122851, US-A1-2004122851, US2004/0122851A1, US2004/122851A1, US20040122851 A1, US20040122851A1, US2004122851 A1, US2004122851A1
Inventors Akira Kinno, Minoru Etoh, Yoshifumi Yonemoto
US 20040122851 A1
a canonicalization process step of subjecting document data to a canonicalization process to correct fluctuation of expression; and
an identifier generating step of generating an identifier uniquely specifying the document data or part thereof, based on all or part of the document data having been subjected to the canonicalization process in the canonicalization process step.
a canonicalization process step of subjecting document data to a canonicalization process to correct fluctuation of expression;
an identity determining step of determining whether there is a common portion between one document data and another document data, based on the identifier having been generated in the identifier generating step.
3. An identity determining method comprising:
an identifier generating step of, based on all or part of encoded data of document data, generating an identifier uniquely specifying the document data or part thereof; and
an identity determining step of determining whether there exists a common portion between one document data and another document data, based on the identifier having been generated in the identifier generating step.
4. An identifier transmitting method comprising:
an identifier transmitting step of transmitting the identifier having been generated in the identifier generating step.
5. An identifier generating apparatus comprising:
canonicalization process means for subjecting document data to a canonicalization process to correct fluctuation of expression; and
identifier generating means for generating an identifier uniquely specifying the document data or part thereof, based on all or part of the document data having been subjected to the canonicalization process by the canonicalization process means.
6. The identifier generating apparatus according to claim 5, wherein the canonicalization process means comprises type standardization process means for, using a class definition file of the document data describing a definition of a type, standardizing a type of expression for a value described in the document data, in accordance with the type defined by the class definition file.
7. The identifier generating apparatus according to claim 6, wherein the type standardization process means is configured to standardize an accuracy of numerical data described in the document data, in accordance with a definition of a type for numerical data described in the class definition file of the document data.
8. The identifier generating apparatus according to claim 5, wherein the canonicalization process means comprises document data generating means for transforming first partial data and second partial data into document data in accordance with a predetermined transformation rule.
9. An identity determining apparatus comprising:
canonicalization process means for subjecting document data to a canonicalization process to correct fluctuation of expression;
identifier generating means for generating an identifier uniquely specifying the document data or part thereof, based on all or part of the document data having been subjected to the canonicalization process by the canonicalization process means; and
identity determining means for determining whether there is a common portion between one document data and another document data, based on the identifier having been generated by the identifier generating means.
10. The identity determining apparatus according to claim 9, wherein the canonicalization process means comprises type standardization process means for, using a class definition file of the document data describing a definition of a type, standardizing a type of expression for a value described in the document data, in accordance with the type defined by the class definition file.
11. The identity determining apparatus according to claim 10, wherein the type standardization process means is configured to standardize an accuracy of numerical data described in the document data, in accordance with a definition of a type for numerical data described in the class definition file of the document data.
12. The identity determining apparatus according to claim 9, wherein the canonicalization process means comprises document data generating means for transforming first partial data and second partial data into document data in accordance with a predetermined transformation rule.
13. The identity determining apparatus according to claim 9, further comprising a cache preliminarily storing the identifier having been generated by the identifier generating means, in correlation with the document data or a result of a predetermined process on the document data,
14. The identity determining apparatus according to claim 9, further comprising second identifier generating means for generating an identifier uniquely specifying the document data or part thereof, based on all or part of the document data, prior to execution of the canonicalization process by the canonicalization process means,
15. An identity determining apparatus comprising:
identifier generating means for, based on all or part of encoded data of document data, generating an identifier uniquely specifying the document data or part thereof; and
identity determining means for determining whether there exists a common portion between one document data and another document data, based on the identifier having been generated by the identifier generating means.
16. The identity determining apparatus according to claim 15, wherein an instruction to skip a process of decoding the encoded data of the document data is issued when the identity determining means determines that the two document data are identical.
17. An identifier transmitting apparatus comprising:
identifier transmitting means for transmitting the identifier having been generated by the identifier generating means.
18. The identifier transmitting apparatus according to claim 17, wherein the identifier transmitting means comprises transmitted data generating means for generating data obtained by replacing all or part of the document data by the identifier.
19. The identifier transmitting apparatus according to claim 18, wherein the transmitted data generating means is configured to generate transmitted data described by an identifier uniquely specifying partial data included in the document data, and difference data between the partial data and the document data.
[0037]FIG. 1 is a flowchart showing the operation of the identifier generating method according to an embodiment.
[0038]FIG. 2 is a flowchart showing the operation of the identifier generating method according to another embodiment.
[0039]FIG. 3 is a flowchart showing the details of the operation of type standardization process step S201.
[0040]FIG. 4 is a flowchart showing the operation of the identifier generating method according to another embodiment.
[0041]FIG. 5 is a flowchart showing the operation of the identity determining method according to another embodiment.
[0042]FIG. 6 is a flowchart showing the operation of the identity determining method according to another embodiment.
[0043]FIG. 7 is a flowchart showing the operation of the identity determining method according to another embodiment.
[0044]FIG. 8 is a flowchart showing the operation of the identity determining method according to another embodiment.
[0045]FIG. 9 is a flowchart showing the operation of the identity determining method according to another embodiment.
[0046]FIG. 10 is a block diagram showing the configuration of the identity determining apparatus according to another embodiment.
[0047]FIG. 11 is a diagram showing a case of an XML document as an example of input document data.
[0048]FIG. 12 is a diagram showing an example of data after the canonicalization of document data shown in FIG. 11, according to XML-Canonicalization Specification.
[0049]FIG. 13 is a diagram showing an example of document data identifiers and document data URIs stored in the cache.
[0050]FIGS. 14A to 14C are diagrams showing (A) document data 1 before the transformation of target document data, (B) document data 2 before the transformation of target document data, and (C) an example of the class definition file.
[0051]FIGS. 15A and 15B are diagrams showing examples of document data after the transformation of target document data.
[0052]FIG. 16 is a block diagram showing the configuration of the item rewriting process apparatus.
[0053]FIG. 17 is a flowchart showing the operation of the identifier transmitting method according to another embodiment.
[0054]FIGS. 18A and 18B are diagrams showing (A) an example of default data, and (B) an example of an RDF document as target document data.
[0055]FIG. 19 is a diagram showing document data after the transformation in document data generating step S401.
[0056]FIG. 20 is a block diagram showing the configuration of the identifier transmitting apparatus according to another embodiment.
[0057]FIG. 21 is a diagram showing an example of document data consisting of a plurality of constituent elements.
[0058]FIG. 22 is a diagram showing an example of document data transmitted by the identifier transmitting method according to another embodiment.
[0059]FIG. 23 is a diagram showing an example of the service system using the partly identifier-integrated document data transmitted by the identifier transmitting method according to another embodiment.
[0060]FIG. 24 is a flowchart showing the operation of the step-by-step identity determining method according to another embodiment.
[0061]FIG. 25 is a diagram for explaining encoded data.
[0062]FIG. 26 is a block diagram showing the configuration of the document data storing-acquiring system.
[0063]FIG. 27 is a diagram showing document data after rearrangement of the sequence of constituent elements in the alphabetical order.
[0067]FIG. 11 is a diagram showing a case of an XML document as an example of input document data. As shown in the figure, the input document data includes unnecessary white spaces and omission of a close tag. Canonicalization needs to be carried out prior to generation of the identifier, in order to prevent a different identifier from being generated because of the fluctuation of expression due to the describer.
[0068]FIG. 12 is an example of canonicalized data according to the XML-Canonicalization Specification from the document data shown in FIG. 11. As shown in the figure, the document data after the canonicalization process is free of the fluctuation of expression due to the describer, as a result of deletion of unnecessary white spaces and insertion of a close tag. An identifier is generated based on the document data shown in the figure.
[0070]FIG. 2 is a flowchart showing the operation of the identifier generating method in which the canonicalization process step S102 includes additional type standardization process step S201 of confirming a class definition file of the target document data and standardizing the type thereof.
[0071]FIG. 3 is a flowchart showing the details of the operation of type standardization process step S201. As shown in the figure, the type standardization process is comprised of step S301 of acquiring a class definition file of the target document data; data type confirming step S302 of confirming a type of every data described in the target document data, based on the class definition file; and document data transforming step S303 of transforming the target document data according to the class definition file.
[0073]FIG. 15A and FIG. 15B are examples of document data after the transformation of the target document data. As shown in these figures, the accuracy of the element values of “value” defined in the “double” type is made equivalent to the accuracy of “double,” whereby the element values, 12.0 and 12.00, of “value” in Document Data 1 and Document Data 2 shown in FIGS. 14A and 14B become equal to each other. This process standardizes the type and equalizes the documents in the form of sequences of characters as well.
[0074]FIG. 4 is a flowchart showing the operation of the identifier generating method in which, where the target document data is composed of default data and difference data, canonicalization process step S102 includes additional document data generating step S401 of generating the original document data from the default data and difference data.
[0075]FIG. 18A is a diagram showing an example of the default data. As shown in the figure, the following is defined as default (see lines 10 and 11).
<up:role>guest</up:role>
<up:age>16<up:age>
[0078]FIG. 18B is a diagram showing an example of an RDF document as target document data. As shown in the figure, the RDF document is doubly defined and includes the description of an URI of default data (<ccpp:defaults rdf:resource=“UserProfileDefault”></ccpp:defaults>) and the difference data (<up:role>vip<up:role>) (see lines 12 and 13). This RDF document is transformed into the original document data in the document data generating step S401. FIG. 19 is document data after the transformation in the document data generating step S401. The figure shows the case where the difference data was overwritten over the default data. As shown in the figure, the default data is acquired from the URI of the default data, and the difference data is overwritten to transform <up:role>guest</up:role> to <up:role>vip</up:role> (see line 12), thereby obtaining the original document data.
[0079]FIG. 26 is a block diagram showing a configuration of document data storing-acquiring system 2700 capable of storing target document data along with the identifier thereof into a cache by the identifier generating method of the present embodiment and acquiring the target document data later on from the cache, using the identifier. As shown in the figure, the document data storing-acquiring system 2700 is comprised of target document data acquiring part 2701 for acquiring target document data; identifier generating part 2702 with the identifier generating method of the present embodiment being mounted thereon; identifier storing part 2703 for storing the generated identifier with the target document data into cache 2704; identifier acquiring part 2705 for acquiring an identifier of document data desired to be acquired from the cache 2704; and document data acquiring part 2706 for acquiring the document data from the cache, using the identifier.
[0080]FIG. 13 shows an example of document data identifiers and document data URIs stored into cache 2704 by identifier storing part 2703. As shown in the figure, it becomes feasible to manage the input document data, using their identifiers. If an identifier is one already stored in the cache, it is also possible to discard the document data without storing it.
[0085]FIG. 11 and FIG. 12 show the examples of the document data before the canonicalization process and the document data after the canonicalization process. It is seen from these figures that the canonicalization process corrects the fluctuation of expression.
[0086]FIG. 6 is a flowchart showing the operation of the identity determining method in which the canonicalization process step S502 includes type standardization process step S601 of confirming the class definition file of the target document data and standardizing the type thereof.
[0087]FIG. 3 is a flowchart showing the details of the operation of type standardization process step S601. The details of the operation are the same as in the first embodiment.
[0088]FIGS. 14A and 14B are diagrams showing Document Data 1 and Document Data 2, respectively, before the type standardization process, FIG. 14C a diagram showing an example of the class definition file, and FIGS. 15A and 15B diagrams showing examples of Document Data 1 and Document Data 2, respectively, after the type standardization process. It is seen from these figures that the values in “value” expressed in different expressions are changed into one in the same expression by the type standardization step S601.
[0089]FIG. 7 is a flowchart showing the operation of the identity determining method in which, where the target document data consists of default data and difference data, the canonicalization process step S502 includes additional document data generating step S701 of generating the original document data from the default data and the difference data.
[0090]FIGS. 18A and 18B show the examples of the default data and target document data, and FIG. 19 the example of the document data after the transformation, which was generated in the document data generating step S701. The details of the operation are the same as in the first embodiment.
[0091]FIG. 8 is a flowchart showing the details of the operation of identity determining step S504. As shown in the figure, the identity determining step S504 is comprised of identifier acquiring step S801 of acquiring an identifier generated from target document data as a target for a determination on identity; identifier storing step S803 of storing the identifier into a cache; and identity determining step S802 of searching the cache for the identifier, determining with a success in the search that the same document data is present, and determining with a failure in the search that the same document data is absent. When the identifier is absent in the cache, the identifier is transferred to the identifier storing step S803 to be stored into the cache.
[0092]FIG. 10 is a block diagram showing a configuration of identity determining apparatus 1101 for determining whether input document data is one already processed, by the identity determining method according to the present embodiment. As shown in the figure, the identity determining apparatus 1101 is comprised of target document data acquiring part 1102 for acquiring target document data; identifier generating part 1103 for generating an identifier from the target document data; identity determining part 1108 for determining whether the data is one already processed, using the generated identifier and cache 1110; and identifier storing part 1109 for, when the identity determining part determines that the data is not one already processed, storing the identifier into the cache 1110, for the next identity determination. The identifier generating part 1103 is comprised of document data generating part 1104 for generating the original document data from the default data and difference data; canonicalization process part 1105 for carrying out the canonicalization process to correct the fluctuation of expression; type standardization process part 1106 for carrying out the type standardization process of data, using the class definition file; and identifier generation process part 1107 for generating a unique identifier from the target document data.
[0093]FIG. 16 is a block diagram showing a configuration of an item rewriting process apparatus for skipping an item rewriting process of document data if the input data is document data already processed, using the identity determining method according to the present embodiment. As shown in the figure, the apparatus is composed of identity determining part 1701 with the identity determining method of the present embodiment being mounted thereon; item rewriting part 1702 for rewriting items of document data in accordance with an item rewriting rule document; and transformed document data cache 1703 storing transformed document data generated by the item rewriting part 1702, along with the identifiers of the document data generated by the identity determining part 1701.
[0099]FIG. 25 is a diagram showing an example in which Document Data 1 and Document Data 2, which are documents identical in meaning but different in the sequence of characters, are encoded according to a byte code table to generate identical encoded data. As shown in the figure, the identical encoded data is obtained by encoding Document Data 1 and Document Data 2 with the same meaning, which are different only in insertion of line feeds. When an identifier is generated based on this encoded data, the same identifier can be generated for the multiple document data with the same meaning.
[0104]FIG. 20 is a block diagram showing a configuration of identifier transmitting apparatus 2101 for transmitting identifier-integrated document data, using the identifier transmitting method according to the present embodiment. As shown in the figure, the identifier transmitting apparatus 2101 is comprised of target document data acquiring part 1102 for acquiring target document data; identifier generating part 1103 for carrying out the canonicalization process and the type standardization process and generating an identifier; and identifier transmitting part 2102 for performing an identifier adding process for the target document and transmitting the document data.
[0106]FIG. 21 shows an example of target document data. As shown in the figure, three constituent elements of <ccpp:component> . . . </ccpp:component> are described in the target document data. When the target document data is processed in the identifier generating step S1802, identifiers are generated for the respective constituent elements.
[0107]FIG. 22 shows an example of partly identifier-integrated document data in which partial descriptions (constituent element 1 and constituent element 2) in the document data shown in FIG. 21 are replaced by their respective identifiers and in which constituent element 3 is described as additional data, as an example of document data transmitted by the identifier transmitting method according to the present embodiment. As seen from the figure, the replacement of constituent element 1 and constituent element 2 with the identifiers can decrease the data volume of the entire document data.
[0108]FIG. 23 is a diagram showing an example of a service system using the partly identifier-integrated document data transmitted by the identifier transmitting method according to the present embodiment. As shown in the figure, the service system is composed of terminal 2400 for transmitting the partly identifier-integrated document data transmitted by the identifier transmitting method of the present embodiment; proxy 2401 for receiving the partly identifier-integrated document data, performing an expansion to recover the original constituent elements from the partial identifiers to generate the original document data, and transmitting it; and server 2402 for receiving the document data and providing a service. The proxy 2401 is connected to database 2403 in which partial identifiers and original constituent elements are stored in correlation with each other. The terminal 2400 is allowed to transmit data after replacing each constituent element already having been transmitted through the proxy, in the document data originally to be transmitted to the server, with an identifier, and it thus becomes feasible to use the method of the present embodiment as a document data transmitting method with a lighter load on the network.
Cooperative Classification Y10S707/99932, Y10S707/99931, G06F17/2247, G06F17/3089
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KINNO, AKIRA;ETOH, MINORU;YONEMOTO, YOSHIFUMI;REEL/FRAME:014951/0991