WO2012119407A1 - 文档更新方法和装置 - Google Patents

文档更新方法和装置 Download PDF

Info

Publication number
WO2012119407A1
WO2012119407A1 PCT/CN2011/078761 CN2011078761W WO2012119407A1 WO 2012119407 A1 WO2012119407 A1 WO 2012119407A1 CN 2011078761 W CN2011078761 W CN 2011078761W WO 2012119407 A1 WO2012119407 A1 WO 2012119407A1
Authority
WO
WIPO (PCT)
Prior art keywords
package
navigation
document
update
source
Prior art date
Application number
PCT/CN2011/078761
Other languages
English (en)
French (fr)
Inventor
王凯
宋磊
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2011/078761 priority Critical patent/WO2012119407A1/zh
Priority to CN2011800015139A priority patent/CN102356394B/zh
Publication of WO2012119407A1 publication Critical patent/WO2012119407A1/zh
Priority to US14/086,469 priority patent/US20140081910A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23Updating
    • G06F16/2358Change logging, detection, and notification

Definitions

  • Embodiments of the present invention relate to document updating techniques, and in particular, to a document updating method and apparatus. Background technique
  • documents need to be deployed on each device.
  • the documents can be various instructions, help files, and so on. Due to the rapid update and upgrade of products in the telecommunications field, the documentation of each product needs to be updated frequently, and how to effectively update the documents becomes an important part of document management in the telecom field.
  • the same set of telecommunication equipment may involve multiple products, multiple versions, multiple network management, and multiple network elements, which may be related to document maintenance of different products, coexistence of documents of different versions, use of documents by different network management, and different network elements.
  • documents of the same set of telecommunication devices are usually provided in a file format, which includes various required document contents, and the user needs to update the documents, for example, when modifying, deleting, or expanding the documents, The entire document content is updated, such as the current Compiled Help Manual (CHM), and the Office series of Doc documents, Docx documents, and so on.
  • CHM Compiled Help Manual
  • the embodiment of the invention provides a document updating method and device, which are used to solve the defects of complicated document updating in the prior art and improve the convenience of document updating.
  • An embodiment of the present invention provides a document update method, including:
  • the update document package includes updating navigation information and an update file, where each navigation node in the update navigation information is associated with a corresponding update file;
  • the source document package includes updated navigation information and a source file, and each navigation node in the updated navigation information is associated with a corresponding source file.
  • An embodiment of the present invention provides a document updating apparatus, including:
  • An update document obtaining module configured to obtain an update document package, where the update document package includes an update navigation information and an update file, where each navigation node in the update navigation information is associated with a corresponding update file;
  • a document update module configured to merge the update document package into the source document package according to the updated navigation information and source navigation information of the source document package, to update the source document package;
  • the source document package includes updated navigation information and a source file, and each navigation node in the updated navigation information is associated with a corresponding source file.
  • the document updating method and apparatus by making an updated document package into a document package including navigation information, so that when the source document package having the navigation information is updated, the updated document package may be merged according to the navigation information.
  • the update of the source document package is implemented.
  • the update document package only needs to include the file to be updated, the update document package is small, and the update file is also very simple to make; at the same time, the source document package is updated only when The file to be updated needs to be merged into the source document package, which makes the document update process simple and convenient, and is particularly suitable for updating and processing large documents, which can effectively improve the convenience of document update.
  • FIG. 1 is a schematic flowchart of a document updating method according to Embodiment 1 of the present invention.
  • FIG. 2 is a schematic flowchart of a document updating method according to Embodiment 2 of the present invention.
  • FIG. 3 is a schematic flowchart of a document updating method according to Embodiment 3 of the present invention.
  • FIG. 4 is a schematic flowchart of a document updating method according to Embodiment 4 of the present invention.
  • FIG. 5 is a schematic structural diagram of a document updating apparatus according to Embodiment 5 of the present invention.
  • FIG. 6 is a schematic structural diagram of a document updating apparatus according to Embodiment 6 of the present invention.
  • FIG. 7 is a schematic structural diagram of a document updating apparatus according to Embodiment 7 of the present invention.
  • FIG. 8 is a schematic structural diagram of a document updating apparatus according to Embodiment 8 of the present invention. detailed description
  • the technical solution of the embodiment of the present invention provides a document updating method and apparatus.
  • the document can be divided into three types: a basic document package, a patch document package, and an extended document package.
  • the document is made into a basic document package and a patch document package, or a basic document package and an extension package, or a basic document package, an extended document package, and a patch document package.
  • various types of document packages can be composed of a plurality of files of different formats, including The navigation information of the navigation and display, and each navigation node in the navigation information is associated with a file for display, so that when the document is displayed, each file can be displayed according to the navigation information.
  • the document updating method of the present invention will be described below by way of specific examples.
  • FIG. 1 is a schematic flowchart diagram of a document updating method according to Embodiment 1 of the present invention.
  • the method may include the following steps: Step 101: Acquire an update document package, where the update document package may include updating navigation information and an update file, where each navigation node in the update navigation information is associated with a corresponding update file respectively; 102.
  • the update document package is merged into the source document package to update the source document package, where the source document package may include source navigation information and source files, and source navigation information.
  • Each navigation node is associated with a corresponding source file.
  • This embodiment can be applied to document update, and is particularly suitable for document update that requires a large number of documents and needs to be updated frequently.
  • the source document package and the update document package are all in the form of separate document packages, and the document package may be produced by integrating multiple source files or update files, including navigation information, and navigation nodes with navigation information.
  • the associated source or update file is produced by integrating multiple source files or update files, including navigation information, and navigation nodes with navigation information.
  • the associated source or update file In this way, when the source document package is updated, such as a patch update or an extended update, the update file can be merged into the source document package according to the navigation information, and the source document package is updated.
  • the source document package can display the file based on the navigation information, and the user can view the corresponding document file by selecting each navigation node, and the document viewing is very convenient, wherein the files associated with each navigation node can be written in different formats.
  • the file as long as the document package is created, associate the file with the navigation node.
  • the document updating method provided in this embodiment, by making the updated document package into a document package including navigation information, so that when the source document package having the navigation information is updated, the updated document package may be merged into the source document according to the navigation information.
  • FIG. 2 is a schematic flowchart diagram of a document updating method according to Embodiment 2 of the present invention.
  • the update document package in this embodiment is a patch package.
  • the document update method in this embodiment may perform patch update on a base package or an extension package as a parent package. Specifically, as shown in FIG. 2, the document updating method in this embodiment may include the following steps:
  • Step 201 Obtain a patch package, where the patch package may include updating navigation information and a patch file, where a navigation node different from the source document package is associated with a corresponding patch file;
  • Step 202 Compare the source navigation information and the updated navigation information, obtain a navigation node that is added to the navigation information, the deleted navigation node, and the modified navigation node in the updated navigation information.
  • Step 203 Delete the navigation node deleted from the source navigation information and modify the navigation node. The navigation node adds the navigation node added in the navigation information and the modified navigation node to the source navigation information to update the source document package.
  • the patch package only the newly modified patch file is included in the patch package, and other unmodified files in the source document package are not carried in the patch package, so that only the creation of the patch package is required.
  • the modified patch file and the corresponding navigation information are very simple to make, and the patch package is small, which facilitates the production and upload of the patch package, and makes the update of the document package very convenient.
  • the source document package is a basic package as a parent package, and those skilled in the art may understand that the source document package may also be an extension package or other patch package.
  • the patch package may include the patch package information, where the patch package information includes source document package information indicating that the patch package needs to be updated, and may be determined according to the patch package information before being updated.
  • the source document package that needs to be updated to update the determined source document package, so that with multiple source document packages, the document package that needs to be updated can be effectively updated.
  • the source document package information may specifically include a source document package identifier to be updated, that is, a parent package identifier, so that the parent package identifier may be used to determine which document package belongs to the update.
  • the navigation information of the patch package is a guide that the parent package should include after the parent package is updated.
  • the navigation information, and only the modified navigation node in the patch package is associated with the patch file, and the unmodified navigation node may not associate any file.
  • both the patch package and the parent package carry the basic information of the identifier document, for example, the identifier of the document package type. For details, refer to the description of the composition and production of the document package. In this way, during the document update process, it is possible to determine which type of document package the document belongs to based on the basic information of each document package, to determine the document that needs to be updated, and to use the document package for the update.
  • the patch update of the document can be implemented.
  • the patch package only needs to include the patch file to be modified, and does not need to include the source.
  • the other files in the document package make the patch package very simple, the patch package is small, and it is easy to upload the patch package.
  • the source document package is very convenient to update.
  • FIG. 3 is a schematic flowchart diagram of a document updating method according to Embodiment 3 of the present invention.
  • the document updating method in this embodiment may include the following steps:
  • Step 301 Obtain a patch package, where the patch package may include updating navigation information and a patch file, where a navigation node different from the source document package is associated with a corresponding patch file;
  • Step 302 Compare the source navigation information and the update navigation information, obtain a navigation node that is added to the navigation information, the deleted navigation node, and the modified navigation node in the updated navigation information.
  • Step 303 Update the navigation node added in the navigation information, and The modified navigation node is added to the source navigation information to implement update of the source document package.
  • Step 304 Add a new modification flag to the added navigation node in the updated source navigation information, add a modification flag to the modified navigation node and the navigation node before the modification, and add a deletion modification flag to the deleted navigation node, so as to Add edit tags, edit tags, and delete edit tags Check out the updates.
  • the modification mark of the source document package may be distinguished, so that when the document package is displayed, the modification may be displayed according to the modification mark, for example,
  • the color, such as the newly added navigation node and its corresponding patch file, can be displayed in red.
  • the deleted navigation node and its source file can be displayed in gray.
  • the specific display form is not limited, as long as the user can distinguish it. .
  • FIG. 4 is a schematic flowchart diagram of a document updating method according to Embodiment 4 of the present invention.
  • the update document in this embodiment is an extension package.
  • the document update method in this embodiment may be extended to a base package, a patch package, or other extension package as a parent package.
  • the parent package described in this embodiment is a base package.
  • the document updating method of this embodiment may include the following steps:
  • Step 401 Obtain an extended package, where the extended package may include updating navigation information and an extended file, where the extended package may include target node information, and each navigation node in the navigation information of the extended package is associated with an extended file as an update file.
  • Step 402 Search for the extended node corresponding to the target node information in the source navigation information according to the target node information in the extended package.
  • Step 403 merge the updated navigation information to a location corresponding to the extended node, and merge the extended package into the source document package. in.
  • the parent package that needs to be extended may be updated.
  • the navigation information in the extended package may be merged into the parent package to be extended according to the target node information carried in the extended package, so as to implement the expansion of the parent package.
  • Update In this way, when the document is expanded, only the file of the extended part needs to be edited, and the extended package can be formed, without editing on the basis of the source document package, and the expansion package is convenient to manufacture, which can effectively improve the expansion of the document package. Convenience makes the expansion of the document package very convenient. At the same time, it also facilitates the management and uploading of documents. At the same time, when the expansion package is created, it does not need to be Can effectively improve the convenience of document production.
  • the extended package also carries the basic information of the identification document, to identify the type of the document package, and carries the identification information of the parent package that needs to be extended.
  • the basic information of the identification document to identify the type of the document package
  • carries the identification information of the parent package that needs to be extended For details, refer to the following: Description.
  • the embodiment of the present invention proposes an update of the document package suitable for the equipment in the telecommunication field.
  • the document package is divided into a basic document package, an extended document package, and an update document package, so that each document can be produced based on the three types of document package types, and the documents can be managed and updated based on the types of the three types of document packages.
  • Each type of document package may be a combination of multiple files and a document package, for example, a document package that can be integrated into XML, HtmlHelp, JavaHelp, Office, PDF, etc., and each document package.
  • Basic information for identifying a document such as a product model, a product version, a document version, a document package type, a document package identifier, etc.
  • the identifier may also include a location of the attachment.
  • Target node information when the document package is a patch package, may include patch package information, such as a parent package identifier, to identify a parent package to which the patch package applies;
  • navigation information for navigation presentation which may be composed of navigation nodes.
  • Each navigation node may have a Universal Resource Locator (URL) for pointing to the associated file, where each file may have a unique identifier, so that each navigation node can pass the unique identifier and file.
  • URL Universal Resource Locator
  • index information for searching can be used for quick search, in document package production Indexing may be made for the displayed content;
  • file information for display that is, a file for making a document package, which is associated with the corresponding navigation node by the node URL;
  • summary information for recording the navigation node such as a message digest
  • MD5 file The fifth version of the algorithm MD5 file, to determine whether the node and its associated files have been modified, in addition to other supporting files.
  • the base document package is a completely separate document package that can be displayed independently without relying on other document packages.
  • the production process is as follows:
  • the navigation nodes and their associated source files may be displayed to the user based on the navigation information. Specifically, when the presentation is performed, the navigation information may be presented to the user in a tree manner, and the user may be based on the tree shape. The selection of each navigation node to view the source file associated with the navigation node.
  • An extension package is a document package that can be attached to a base package or other extension package. It can exist and be displayed as a separate document package.
  • the attached base package or other extension package can also be a parent package.
  • the production process is as follows:
  • the priority of the attached current package can also be selected according to the attributes of the attached parent package, so that the expansion package with higher priority can be attached when there are two expansion packages with the same mount position. Displayed in front and in front.
  • the extension package can merge the extension package into the parent package according to the target node and display it together with the parent package.
  • the extension package can also be displayed as a separate document package, which is displayed in the same way as the base package. .
  • the patch package, extension package or other patch package is updated to form a new base package, extension package or fix package.
  • the base package, extension package or other fix package for update can also be the parent package. Production process as follows:
  • the modification information such as adding, modifying, and deleting is recorded in the patch package node resource file to obtain the node resource file of the patch package;
  • the node resource file of the patch package is merged into the patch package, and the newly modified source file is incorporated into the patch package;
  • the newly created index is merged into the patch package to obtain a patch package that can be used for the update, and the patch package also includes the patch information.
  • the patch package When in use, the patch package can be published to the document package to be updated to update the parent package.
  • each document package may be composed of files of different formats, and the navigation node in the document package is associated with the combined file, so that when the document is updated, only the document package that needs to be updated is needed.
  • the navigation information can be updated, which makes the update of the document very convenient, and the preparation of each update document package is very convenient, and it is convenient to update the production and upload of the document package, and improve the convenience of document update, especially suitable for the production and management of large documents. And updates.
  • the document package is divided into a basic package, an extended package, and a patch package.
  • targeted publishing can be performed for different networking modes of the communication device. The following describes how different document combinations are published:
  • product documents that one can independently complete can be released in the form of basic packages and fix packs. In this way, the document written for the first time can be made into a separate basic package.
  • the patch package and the patch package of the basic package can be released.
  • the patch package only needs to include the incremental part. , takes up less disk space, is easy to download, and is also very convenient for updating the base package.
  • the product has network management and network elements
  • it can be supported by the model of the extension package of the base package and the base package.
  • the network management document can be included in the basic package, and each expansion package belongs to an independent network.
  • the meta-documents are respectively attached to the target location of the main navigation.
  • the document is distributed in the form of a basic package and a plurality of expansion packages.
  • the basic package can be allocated to the network management device, and the extended package can be allocated to the corresponding network element device.
  • the network element device can be dynamically added and deleted. You can customize the effective document for the user. The user can only see the help of the NE device that he uses.
  • the network management device For the documents of other NEs or network management devices, the user will not see it, which can avoid the interference of unwanted documents.
  • the network management device The document exists separately from the NE device. In the case where the interface between the NMS and the NE is unchanged, the NMS and NE maintain their own documents without the need to merge each version. When the document is updated, only Update the network management document or network element document to be updated, which makes the update of the document very convenient.
  • the basic package, the extended package, and the service package can be used for the release of the document.
  • the basic package can correspond to the network management device
  • the expansion package corresponds to the network element device.
  • the network management document can effectively reduce the coupling of network management and network element documents, and the patch is small, which is convenient for users to download and update.
  • the document can be modularized as needed, so that the documents required for the corresponding product can be released to the corresponding
  • the product does not need to include the entire device's documentation.
  • the document can reduce the development scope and maintenance scope, and reduce the development, maintenance and upgrade cost of the document by allowing the same module's documents to share multiple products.
  • FIG. 5 is a schematic structural diagram of a document updating apparatus according to Embodiment 5 of the present invention. As shown in FIG.
  • the apparatus of this embodiment includes an update document obtaining module 1 and a document update module 2, wherein: an update document obtaining module 1 is configured to obtain an update document package, where the update document package includes updating navigation information and an update file, where Each of the navigation nodes in the update navigation information is associated with a corresponding update file; the document update module 2 is configured to merge the update document package into the source document package according to the updated navigation information and the source navigation information of the source document package, to The document package is updated, wherein the source document package includes update navigation information and a source file, and each navigation node in the update navigation information is associated with a corresponding source file.
  • the embodiment of the present invention can be applied to the document update to implement the update of the document.
  • reference may be made to the description of the method embodiment of the present invention, and details are not described herein.
  • FIG. 6 is a schematic structural diagram of a document updating apparatus according to Embodiment 6 of the present invention.
  • the updated document package obtained by the update document is the patch package
  • the navigation node different from the source document package in the service package is associated with the patch file as the update file
  • the document update module 2 may include a first comparison unit 21 and a first update unit 22, where: the first comparison unit 21 is configured to compare the source navigation information and update the navigation information, and obtain an increase in the updated navigation information relative to the source navigation information.
  • the first comparison unit 21 is configured to compare the source navigation information and update the navigation information, and obtain an increase in the updated navigation information relative to the source navigation information.
  • the first updating unit 22 is configured to delete the navigation node deleted in the source navigation information and the modified navigation node, and add the added navigation node and the modified navigation node in the updated navigation information to the source navigation information, to implement Update of the source document package.
  • the document package may be updated in the form of a patch package.
  • FIG. 7 is a schematic structural diagram of a document updating apparatus according to Embodiment 7 of the present invention. Different from the technical solution of the embodiment shown in FIG. 6 above, in this embodiment, the patch file is merged into the source document package. When the modified document is modified, the difference is made so that the user can easily know the modification made by the parent package. Specifically, as shown in FIG.
  • the document update module 2 in the apparatus of this embodiment may include a second comparison unit 23, a second update unit 24, and a second identification unit 25, where: the second comparison unit 23 is used for comparison Deriving the source navigation information and updating the navigation information, obtaining a navigation node that is added to the updated navigation information, the deleted navigation node, and the modified navigation node; and a second update unit 24, configured to: The navigation node added to the information and the modified navigation node are added to the source navigation information to implement the update of the source document package.
  • the second identifier unit 25 is configured to add a new navigation node added to the updated source navigation information.
  • the document package may be updated in the form of a patch package, and the updated content may be identified in the updated document package.
  • FIG. 8 is a schematic structural diagram of a document updating apparatus according to Embodiment 8 of the present invention.
  • the update document package obtained by the update document acquisition module 1 is an extension package
  • the extension package may include target node information
  • each navigation node in the navigation information of the extension package is associated with the update file.
  • the file update module 2 may include a third search unit 26 and a third update unit 27, wherein: the third search unit 26 is configured to search for and target node information in the source navigation information according to the target node information in the extended package.
  • the third updating unit 27 is configured to merge the updated navigation information to a location corresponding to the extended node, and merge the extended package into the source document package.
  • the document package may be extended and updated based on the form of the extended package, and the specific implementation thereof
  • the document package may be extended and updated based on the form of the extended package, and the specific implementation thereof

Description

文档更新方法和装置
技术领域
本发明实施例涉及文档更新技术, 尤其涉及一种文档更新方法和装 置。 背景技术
电信领域中, 各设备上均需要部署有文档, 该文档可以是各种说明、 帮 助等文件。 由于电信领域产品的更新、 升级较快, 相应地, 各产品的文档也 需要经常进行更新, 而如何有效对文档进行更新, 则成为电信领域中文档管 理的重要内容。
目前, 同一套电信设备可能会涉及到多产品、 多版本、 多网管和多网元, 而这会关系到不同产品的文档维护、 不同版本的文档并存、 不同网管的文档 使用, 以及不同网元的文档动态扩展等, 同时, 这些文档本身都较庞大, 且 文档通常需要不同的编写人员编制而成, 使得文档的管理和更新非常复杂。 现有技术中, 同一套电信设备的文档通常是以一种文件格式提供, 该文档包 括所需的各种文档内容, 用户需要对文档进行更新, 例如修改、 删减或扩展 文档时, 需要对整个文档内容进行更新, 例如目前的已编译帮助文件 ( Compiled Help Manual, CHM ) , 以及 Office系列的 Doc文档、 Docx文档 等。
综上, 现有电信设备文档进行更新时, 需要全文替换, 导致文档更新 复杂, 对文档进行修改时, 需要对所有的文档进行处理, 特别是对大批量 文档进行处理时, 更新过程复杂, 更新时间较长, 且更新文件制作也非常 麻烦。 发明内容
本发明实施例提供一种文档更新方法和装置, 用以解决现有技术中文档 更新复杂的缺陷, 提高文档更新的便利性。 本发明实施例提供一种文档更新方法, 包括:
获取更新文档包, 所述更新文档包包括更新导航信息和更新文件, 所述 更新导航信息中各导航节点分别与相应的更新文件关联;
根据所述更新导航信息和源文档包的源导航信息, 将所述更新文档包合 并到所述源文档包, 以对所述源文档包进行更新;
其中, 所述源文档包包括更新导航信息和源文件, 所述更新导航信息中 各导航节点分别与相应的源文件关联。
本发明实施例提供一种文档更新装置, 包括:
更新文档获取模块, 用于获取更新文档包, 所述更新文档包包括更新导 航信息和更新文件, 所述更新导航信息中各导航节点分别与相应的更新文件 关联;
文档更新模块, 用于根据所述更新导航信息和源文档包的源导航信息, 将所述更新文档包合并到所述源文档包, 以对所述源文档包进行更新;
其中, 所述源文档包包括更新导航信息和源文件, 所述更新导航信息中 各导航节点分别与相应的源文件关联。
本发明实施例提供的文档更新方法和装置, 通过将更新文档包制作成 包括导航信息的文档包, 使得对具有导航信息的源文档包进行更新时, 可 根据导航信息,将更新文档包合并到源文档包中,实现对源文档包的更新, 在文档更新时, 更新文档包只需要包含待更新文件, 更新文档包较小, 更 新文件的制作也非常简单; 同时, 源文档包更新时只需要将待更新文件合 并到源文档包即可, 使得文档更新过程简单、 便利, 特别适用于大型文档 的更新处理, 可有效提高文档更新的便利性。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实 施例中所需要使用的附图作简单地介绍, 显而易见地, 下面描述中的附图仅 仅是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性 劳动性的前提下, 还可以根据这些附图获得其他的附图。
图 1为本发明实施例一提供的文档更新方法的流程示意图;
图 2为本发明实施例二提供的文档更新方法的流程示意图;
图 3为本发明实施例三提供的文档更新方法的流程示意图;
图 4为本发明实施例四提供的文档更新方法的流程示意图;
图 5为本发明实施例五提供的文档更新装置的结构示意图;
图 6为本发明实施例六提供的文档更新装置的结构示意图;
图 7为本发明实施例七提供的文档更新装置的结构示意图;
图 8为本发明实施例八提供的文档更新装置的结构示意图。 具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本发 明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描述, 显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于 本发明中的实施例, 本领域普通技术人员在没有做出创造性劳动前提下所获 得的所有其他实施例, 都属于本发明保护的范围。
本发明实施例技术方案提出了一种文档更新方法和装置, 根据该文档更 新方法和装置, 可将文档分成基础文档包、 补丁文档包和扩展文档包三种类 型, 在文档制作时可根据需要, 将文档制作成基础文档包和补丁文档包, 或 者基础文档包和扩展包, 或者基础文档包、 扩展文档包和补丁文档包等形式。 其中, 各种类型的文档包均可由多个不同格式的文件组合而成, 包括用于导 航和展示的导航信息,且导航信息中的各导航节点均关联有用于展示的文件, 这样, 在文档展示时, 可根据导航信息进行各文件的展示。 下面以具体实例 对本发明文档更新方法进行说明。
图 1为本发明实施例一提供的文档更新方法的流程示意图。如图 1所示, 该方法可包括以下步骤: 步骤 101、 获取更新文档包, 该更新文档包可包括更新导航信息和更新 文件, 更新导航信息中各导航节点分别与相应的更新文件关联; 步骤 102、 根据更新导航信息和源文档包的源导航信息, 将更新文档包 合并到源文档包, 以对源文档包进行更新, 其中, 源文档包可包括源导航信 息和源文件, 源导航信息中各导航节点分别与相应的源文件关联。 本实施例可应用于文档更新中, 特别适用于文档较大, 需要频繁进行更 新的文档更新中。 其中, 源文档包和更新文档包均以独立的文档包形式存在, 且文档包可以是由多个源文件或更新文件整合而制作得到的, 包括有导航信 息, 以及与导航信息的各导航节点关联的源文件或更新文件。 这样, 在对源 文档包进行更新, 例如补丁更新或扩展更新时, 就可以根据导航信息, 将更 新文件合并到源文档包中, 对源文档包进行更新。 本实施例中, 源文档包可基于导航信息对文件进行展示, 用户可通过选 择各导航节点来查看相应的文档文件, 文档查看非常方便, 其中, 各导航节 点关联的文件可以是具有不同格式编写的文件, 只要在文档包制作时, 将文 件与导航节点关联即可。 本实施例中提供的文档更新方法, 通过将更新文档包制作成包括导航信 息的文档包, 使得对具有导航信息的源文档包进行更新时, 可根据导航信息, 将更新文档包合并到源文档包中, 在文档更新时, 更新文档包只需要包含待 更新文件, 更新文档包较小, 更新文件的制作也非常简单; 同时, 源文档包 更新时只需要将待更新文件合并到源文档包即可, 使得文档更新过程简单、 便利, 特别适用于大型文档的更新处理, 可有效提高文档更新的便利性。 图 2为本发明实施例二提供的文档更新方法的流程示意图。 本实施例中 的更新文档包为补丁包, 本实施例文档更新方法可以对作为父包的基础包或 扩展包进行补丁更新。 具体地, 如图 2所示, 本实施例文档更新方法可包括 以下步骤:
步骤 201、 获取补丁包, 该补丁包可包括更新导航信息和补丁文件, 该 补丁包中与源文档包不同的导航节点关联有相应的补丁文件;
步骤 202、 对比源导航信息和更新导航信息, 获得更新导航信息中相对 源导航信息增加的导航节点、 删除的导航节点以及修改的导航节点; 步骤 203、 删除源导航信息中删除的导航节点以及修改的导航节点, 并 将更新导航信息中增加的导航节点以及修改后的导航节点加入到源导航信息 中, 实现对源文档包的更新。
本实施例中, 补丁包中仅包括新增修改的补丁文件, 对于源文档包中的 其它未作修改的文件并未携带在补丁包中, 这样, 在补丁包制作时, 只需要 制作新增修改的补丁文件以及相应的导航信息, 补丁包的制作非常简单, 且 补丁包较小, 便于补丁包的制作和上载, 使得文档包的更新非常便利。
本实施例中, 所述的源文档包为作为父包的基础包, 本领域技术人员可 以理解, 源文档包也可以是扩展包或其它补丁包。 本实施例中, 补丁包中可包括有补丁包信息, 该补丁包信息包括有表明 该补丁包需要更新的源文档包的源文档包信息, 在进行更新前, 可根据该补 丁包信息, 确定需要进行更新的源文档包, 以便对确定的源文档包进行更新, 这样, 在具有多个源文档包的情况下, 可有效对需要进行更新的文档包进行 更新。 实际应用中, 该源文档包信息具体可包括待更新的源文档包标识, 即 父包标识, 从而可^^据父包标识确定其属于对哪个文档包的更新。 本实施例中, 补丁包的导航信息是对父包进行更新后, 父包应包括的导 航信息, 且补丁包中只有修改的导航节点才关联有补丁文件, 未作修改的导 航节点可不关联任何文件。 这样, 在对源文档进行更新时, 只需要将修改的 导航节点合并到源文档包相应的导航节点处, 以及将原导航信息中修改的导 航节点删除即可。 本实施例中, 补丁包和父包中均携带有标识文档的基本信息, 例如标识 文档包类型的标识等, 具体可参见下文文档包的构成、 制作中的说明。 这样, 在文档更新过程中, 即可根据各文档包的基本信息确定文档属于哪种类型的 文档包, 以确定需要更新的文档, 以及用作更新的文档包。
可以看出, 本实施例利用补丁包对文档包进行更新时, 可实现文档的补 丁更新, 该补丁更新过程中, 补丁包制作时只需要包含待 ^ίι爹改的补丁文件, 不需要包含源文档包中的其它文件, 使得补丁包的制作非常简单, 补丁包较 小, 便于补丁包的上载, 源文档包的更新非常便利。
图 3为本发明实施例三提供的文档更新方法的流程示意图。 与上述图 2 所示实施例不同的是, 本实施例中, 在将补丁包合并到父包时, 可对更新内 容进行区分, 以便用户可方便的了解父包所做的修改。 具体地, 如图 3所示, 本实施例文档更新方法可包括以下步骤:
步骤 301、 获取补丁包, 该补丁包可包括更新导航信息和补丁文件, 该 补丁包中与源文档包不同的导航节点关联有相应的补丁文件;
步骤 302、 对比源导航信息和更新导航信息, 获得更新导航信息中相对 源导航信息增加的导航节点、 删除的导航节点以及修改的导航节点; 步骤 303、 将更新导航信息中增加的导航节点、 以及修改的导航节点加 入到源导航信息中, 实现对源文档包的更新;
步骤 304、 为更新后的源导航信息中增加的导航节点添加新增修改标记, 为修改后的导航节点和修改前的导航节点添加修改标记, 以及为删除的导航 节点添加删除修改标记, 以便根据新增修改标记、 修改标记和删除修改标记 查看更新内容。
本实施例中, 在对作为父包的基础包进行补丁更新时, 可将源文档包以 的修改标记进行区分, 使得对文档包进行展示时, 可根据修改标记进行区分 显示, 例如, 可以通过颜色, 如新增加导航节点及其对应的补丁文件的可以 显示为红色, 删除的导航节点及其源文件可显示为灰色等, 其具体展示形式 并不做特别限定, 只要便于用户进行区分即可。
可以看出, 通过为更新的导航节点添加修改标记, 可便于用户对文档更 新内容进行识别, 便于用户查看文档内容。
图 4为本发明实施例四提供的文档更新方法的流程示意图。 本实施例中 的更新文档为扩展包, 本实施例文档更新方法可以对作为父包的基础包、 补 丁包或其它扩展包进行扩展, 本实施例中所述的父包为基础包。 具体地, 如 图 4所示, 本实施例文档更新方法可包括以下步骤:
步骤 401、 获取扩展包, 该扩展包可包括更新导航信息和扩展文件, 该 扩展包可包括有目标节点信息, 该扩展包的导航信息中的各导航节点关联有 作为更新文件的扩展文件。
步骤 402、 根据扩展包中的目标节点信息, 在源导航信息中查找与目标 节点信息对应的扩展节点; 步骤 403、 将更新导航信息合并到扩展节点对应的位置, 将扩展包合并 到源文档包中。
本实施例可对仅需要进行扩展的父包进行更新, 更新时, 可根据扩展包 中携带的目标节点信息, 将扩展包中的导航信息合并到待扩展的父包, 实现 对父包的扩展更新。 这样, 在对文档进行扩展时, 仅需要编辑扩展部分的文 件, 并形成扩展包即可, 而不需要在源文档包的基础上进行编辑, 扩展包的 制作方便, 可有效提高文档包扩展的便利性, 使得文档包的扩展非常方便, 同时, 也利于文档的管理和上载; 同时, 扩展包制作时, 可不需要对其中的 可有效提高文档制作的便利性。
本实施例中, 扩展包中也携带有标识文档的基本信息, 以标识文档包所 属的类型, 且携带有需要扩展的父包的标识信息, 具体可参见下文对文档包 的构成、 制作中的说明。
为便于对上述本发明各实施例的理解, 下面对本发明实施例中各类型的 文档包的构成、 制作、 展示等进行说明。
为适应电信领域中同一套设备的多产品、 多版本、 多网管以及多网元中 文档的制作、 管理和更新, 本发明实施例中提出一种适用于电信领域设备的 文档包的更新, 可将文档包分成基础文档包、 扩展文档包和更新文档包, 使 得各文档可基于这三种文档包类型进行制作, 并可基于这三种文档包的类型 对文档进行管理和更新。 其中, 各类型的文档包均可以是将多个文件合成并 制作得到一个文档包, 例如可以将 XML、 HtmlHelp, JavaHelp, Office, Pdf 等格式文件整合并制作得到的一个文档包, 且各文档包可包括以下内容: (1) 用于标识文档的基本信息, 例如产品型号、 产品版本、 文档版本、 文档包类 型、 文档包标识等, 文档包为扩展包时, 还可包括标识挂接位置的目标节点 信息, 文档包为补丁包时, 可包括补丁包信息, 如父包标识等, 以标识该补 丁包适用的父包; (2 )用于导航展现的导航信息, 可由各导航节点组成, 各 导航节点可具有节点统一资源定位符 ( Universal Resource Locator, URL ) , 以用于指向关联的文件, 其中, 各文件可具有一个唯一的标识, 使得各导航 节点均可通过该唯一的标识与文件关联在一起; (3 )用于搜索的索引信息, 可用于快速搜索, 在文档包制作时可针对展示内容制作索引; ( 4 )用于展示 的文件信息,也即制作文档包的文件,通过节点 URL关联到相应的导航节点; ( 5 )用于记录导航节点的摘要信息, 例如消息摘要算法第五版 MD5文件, 以确定节点及其关联的文件是否有做修改, 此外还可包括其它支撑文件。 下 面对各类型文档包的制作和适用分别进行说明: 1. 基础文档包
基础文档包是完全独立的文档包,可不依赖其它文档包而进行独立展示。 其制作过程如下:
首先, 根据源文件生成导航、 索引以及节点资源文件;
其次, 将源文件、 导航、 索引、 节点资源文件等制作成一个文档包。 在使用时, 可基于导航信息, 将各导航节点及其关联的源文件展示给用 户, 具体地, 在进行展示时, 可将导航信息以树形的方式展现给用户, 用户 可基于对树形中各导航节点的选择来查看导航节点所关联的源文件。
2. 扩展包
扩展包是指可以挂接在基础包或其它扩展包上的文档包, 其可以作为独 立的文档包存在和展示, 其中, 挂接的基础包或其它扩展包也可成为父包。 其制作过程如下:
首先, 根据扩展文件生成导航、 索引、 节点资源文件以及待扩展的父包 的目标节点;
然后, 将扩展文件、 导航、 索引、 节点资源文件以及目标节点等制作成 文档包。
此外, 也可根据挂接的父包的属性, 选择挂接的当前包的优先级, 这样, 在具有相同挂接位置的两个扩展包时, 可将具有较高优先级的扩展包挂接在 前面并在前面进行显示。
使用时, 扩展包可根据目标节点, 将扩展包合并到父包中, 并与父包一 起进行展示; 此外, 该扩展包也可作为独立的文档包进行展示, 其具体展示 方式与基础包相同。
3. 补丁包 包、 扩展包或其它补丁包进行更新, 以形成新的基础包、 扩展包或补丁包, 其中, 用于更新的基础包、 扩展包或其它补丁包也可成为父包。 其制作过程 如下:
首先, 将补丁包的补丁文件与父包中的节点摘要文件进行对比, 根据对 比结果, 将新增、 修改、 删除等修改信息记录到补丁包节点资源文件中, 得 到补丁包的节点资源文件;
其次, 将补丁包的节点资源文件合入到补丁包中, 并将新增修改的源文 件合入到补丁包中;
最后, 制作新增修改的索引合入到补丁包中, 从而得到可用于更新的补 丁包, 且补丁包中还包括补丁信息。
使用时, 可将补丁包发布到待更新的文档包中, 对父包进行更新。
本实施例中, 各文档包均可以由不同格式的文件组合而成, 且文档包中 的导航节点与组合的文件分别关联, 这样, 在对文档进行更新时, 只需要对 需要更新的文档包的导航信息进行更新即可, 使得文档的更新非常方便, 且 各更新文档包的制作非常方便, 便于更新文档包的制作和上载, 提高文档更 新的便利性, 特别适用于大型文档的制作、 管理和更新。
本实施例中, 通过将文档包分成基础包、 扩展包和补丁包的形式, 在进 行文档发布时, 可针对通信设备的不同组网方式, 进行针对性的发布。 下面 对不同的文档组合发布方式进行说明:
1. 基础包和补丁包
对于文档内容较少且产品单一, 一个人可以独立完成的产品文档, 可以 基础包和补丁包的形式进行发布。 这样, 首次编写的文档可制作成一个独立 的基础包发布, 后期变更及修改较小的情况下可以发布基础包的补丁包及补 丁包的补丁包形式, 其中, 补丁包只需包含增量部分, 占用磁盘空间小, 易 于下载, 且对基础包的更新也非常方便。
2. 基础包和扩展包
针对产品具有网管和网元的情况, 可以用基础包和基础包的扩展包的模 型支撑, 例如, 可以在基础包中包含网管文档, 每个扩展包则属于独立的网 元文档, 分别挂接的到主导航的目标位置, 文档发布时以基础包和多个扩展 包的形式, 基础包可分配到网管设备上, 扩展包则可分配到相应的网元设备 上。 这样, 网元设备可以动态增加和删除。 可以为用户定制有效的文档, 用 户只能看到他使用的网元设备的帮助, 对于其它网元或网管设备的文档, 用 户不会看到, 可避免不想干文档的干扰; 同时, 网管设备和网元设备之间的 文档独立存在, 在网管与网元设别的接口不变的情况下, 网管、 网元维护自 己的文档无需每个版本都合并到一起发布, 文档更新时, 仅需要对要更新的 网管文档或网元文档进行更新即可, 使得文档的更新非常便利。
3. 基础包、 扩展包和补丁包
对于需要经常进行补丁更新的文档, 则可采用基础包、 扩展包和补丁包 的方式进行文档的发布, 基础包可对应于网管设备, 扩展包对应于网元设备, 对于需要进行补丁更新时, 可针对不同的网元文档或网管文档, 制定单独的 补丁包, 并下发到相应的网元或网管, 对文档进行补丁更新, 这样, 各网元 或网管的文档更新不会影响其它网元或网管的文档, 可有效降低网管、 网元 文档的耦合性, 补丁较小, 便于用户下载和更新。
可以看出, 通过将文档包分成基础包、 补丁包和扩展包, 在进行电信设 备的产品开过时, 可根据需要对文档进行模块化制作, 这样, 可将相应产品 所需的文档发布给相应的产品, 而不需要每个产品均包括整个设备的文档, 在文档制作时, 可通过降低开发范围、 维护范围, 通过允许相同模块的文档 多产品共用, 实现降低文档的开发、 维护、 升级成本; 通过允许动态增删文 档模块, 实现不同的定制化交付; 通过允许动态增删文档模块, 实现客户增 删功能时, 最小化的动态增删文档; 在模块的基础上制作补丁, 最小化补丁 范围, 避免大文档替换, 造成资源的浪费。
本领域技术人员可以理解, 本实施例文档更新方法除了可适用于电信领 域中文档的更新外, 还可适用于其它需要进行类似更新的文档更新中, 在此 并不做限制。 图 5为本发明实施例五提供的文档更新装置的结构示意图。如图 5所示, 本实施例装置包括更新文档获取模块 1和文档更新模块 2, 其中: 更新文档获取模块 1 , 用于获取更新文档包, 该更新文档包包括更新导 航信息和更新文件, 该更新导航信息中各导航节点分别与相应的更新文件关 联; 文档更新模块 2 , 用于根据更新导航信息和源文档包的源导航信息, 将 更新文档包合并到所述源文档包, 以对源文档包进行更新, 其中, 源文档包 包括更新导航信息和源文件, 更新导航信息中各导航节点分别与相应的源文 件关联。
本发明实施例可应用于文档更新中, 实现对文档的更新, 其具体实现过 程可参考上述本发明方法实施例的说明, 在此不再赘述。
图 6为本发明实施例六提供的文档更新装置的结构示意图。如图 6所示, 本实施例中更新文档获耳 莫块 1获取的更新文档包为补丁包, 且补丁包中与 源文档包不同的导航节点关联有作为更新文件的补丁文件; 文档更新模块 2 可包括第一对比单元 21和第一更新单元 22, 其中: 第一对比单元 21 , 用于对比所述源导航信息和更新导航信息, 获得所述 更新导航信息中相对所述源导航信息增加的导航节点、 删除的导航节点以及 修改的导航节点;
第一更新单元 22, 用于删除源导航信息中删除的导航节点以及修改的导 航节点 , 并将所述更新导航信息中增加的导航节点以及修改后的导航节点加 入到源导航信息中, 实现对源文档包的更新。
本实施例可以对基于补丁包的形式对文档包进行补丁更新, 其具体实现 方式可参见上述本发明方法实施例二的说明, 在此不再赘述。 图 7为本发明实施例七提供的文档更新装置的结构示意图。 与上述图 6 所示实施例技术方案不同的是, 本实施例中, 在将补丁文件合并到源文档包 时, 可修改的文档修改之处进行区别, 以便用户可以方便的知道父包所作出 的修改。 具体地, 如图 7所示, 本实施例装置中文档更新模块 2可包括第二 对比单元 23、 第二更新单元 24和第二标识单元 25 , 其中: 第二对比单元 23 , 用于对比所述源导航信息和更新导航信息, 获得所述 更新导航信息中相对所述源导航信息增加的导航节点、 删除的导航节点以及 修改的导航节点; 第二更新单元 24, 用于将所述更新导航信息中增加的导航节点、 以及修 改后的导航节点加入到源导航信息中, 实现对源文档包的更新; 第二标识单元 25 , 用于为更新后的源导航信息中增加的导航节点添加新 增修改标记, 为修改后的导航节点和修改前的导航节点添加修改标记, 以及 为删除的导航节点添加删除修改标记, 以便根据所述新增修改标记、 修改标 记和删除修改标记查看更新内容。 本实施例可以对基于补丁包的形式对文档包进行补丁更新, 并可在更新 后的文档包中对更新内容进行标识, 其具体实现方式可参见上述本发明方法 实施例三的说明, 在此不再赞述。
图 8为本发明实施例八提供的文档更新装置的结构示意图。如图 8所示, 本实施例中更新文档获取模块 1获取的更新文档包为扩展包, 扩展包可包括 有目标节点信息, 该扩展包的导航信息中的各导航节点关联有作为更新文件 的扩展文件; 文档更新模块 2可包括第三查找单元 26和第三更新单元 27, 其中: 第三查找单元 26, 用于根据扩展包中的目标节点信息, 在源导航信息中 查找与目标节点信息对应的扩展节点; 第三更新单元 27, 用于将更新导航信息合并到扩展节点对应的位置, 将 扩展包合并到源文档包中。
本实施例可以对基于扩展包的形式对文档包进行扩展更新, 其具体实现 方式可参见上述本发明方法实施例四的说明, 在此不再赘述。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读 取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述 的存储介质包括: ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介 质。
最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对 其限制; 尽管参照前述实施例对本发明进行了详细的说明, 本领域的普通 技术人员应当理解: 其依然可以对前述各实施例所记载的技术方案进行修 改, 或者对其中部分技术特征进行等同替换; 而这些修改或者替换, 并不 使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权 利 要 求
1、 一种文档更新方法, 其特征在于, 包括: 获取更新文档包, 所述更新文档包包括更新导航信息和更新文件, 所述 更新导航信息中各导航节点分别与相应的更新文件关联; 根据所述更新导航信息和源文档包的源导航信息, 将所述更新文档包合 并到所述源文档包, 以对所述源文档包进行更新; 其中, 所述源文档包包括源导航信息和源文件, 所述源导航信息中各导 航节点分别与相应的源文件关联。
2、 根据权利要求 1所述的文档更新方法, 其特征在于, 所述更新文档包 为补丁包, 所述补丁包中与所述源文档包不同的导航节点关联有作为更新文 件的补丁文件;
所述根据所述更新导航信息和源文档包的源导航信息, 将所述更新文档 包合并到所述源文档包包括:
对比所述源导航信息和更新导航信息, 获得所述更新导航信息中相对所 述源导航信息增加的导航节点、 删除的导航节点以及修改的导航节点; 删除源导航信息中删除的导航节点以及修改的导航节点, 并将所述更新 导航信息中增加的导航节点以及修改后的导航节点加入到源导航信息中, 实 现对所述源文档包的更新。
3、 根据权利要求 1所述的文档更新方法, 其特征在于, 所述更新文档包 为补丁包, 所述补丁包中与所述源文档包不同的导航节点关联有作为更新文 件的补丁文件;
所述根据所述更新导航信息和源文档包的源导航信息, 将所述更新文档 包合并到所述源文档包包括: 对比所述源导航信息和更新导航信息, 获得所述更新导航信息中相对所 述源导航信息增加的导航节点、 删除的导航节点以及修改的导航节点; 将所述更新导航信息中增加的导航节点、 以及修改的导航节点加入到源 导航信息中, 实现对源文档包的更新; 为更新后的源导航信息中增加的导航节点添加新增修改标记, 为修改后 的导航节点和修改前的导航节点添加修改标记, 以及为删除的导航节点添加 删除修改标记, 以便根据所述新增修改标记、 修改标记和删除修改标记查看 更新内容。
4、 根据权利要求 2或 3所述的文档更新方法, 其特征在于, 所述补丁包 还包括有源文档包信息, 用于表明所述补丁包更新的源文档包; 所述根据所述更新导航信息和源文档包的源导航信息, 将所述更新文档 包合并到所述源文档包之前还包括: 根据所述补丁包中的源文档包信息, 确定需要进行更新的源文档包, 以 便利用所述补丁包对源文档包进行更新。
5、 根据权利要求 1所述的文档更新方法, 其特征在于, 所述更新文档包 为扩展包, 所述扩展包包括有目标节点信息, 所述扩展包的导航信息中的各 导航节点关联有作为更新文件的扩展文件; 所述根据所述更新导航信息和源文档包的源导航信息, 将所述更新文档 包合并到所述源文档包包括: 根据所述扩展包中的目标节点信息, 在所述源导航信息中查找与所述目 标节点信息对应的扩展节点; 将所述更新导航信息合并到所述扩展节点对应的位置, 实现对所述源文 档包的更新。
6、 一种文档更新装置, 其特征在于, 包括: 更新文档获取模块, 用于获取更新文档包, 所述更新文档包包括更新导 航信息和更新文件, 所述更新导航信息中各导航节点分别与相应的更新文件 关联;
文档更新模块, 用于根据所述更新导航信息和源文档包的源导航信息, 将所述更新文档包合并到所述源文档包, 以对所述源文档包进行更新;
其中, 所述源文档包包括更新导航信息和源文件, 所述更新导航信息中 各导航节点分别与相应的源文件关联。
7、 根据权利要求 6所述的文档更新装置, 其特征在于, 所述更新文档包 为补丁包, 所述补丁包中与所述源文档包不同的导航节点关联有作为更新文 件的补丁文件; 所述文档更新模块包括:
第一对比单元, 用于对比所述源导航信息和更新导航信息, 获得所述更 新导航信息中相对所述源导航信息增加的导航节点、 删除的导航节点以及修 改的导航节点; 第一更新单元, 用于删除源导航信息中删除的导航节点以及修改的导航 节点, 并将所述更新导航信息中增加的导航节点以及修改后的导航节点加入 到源导航信息中, 实现对源文档包的更新。
8、 根据权利要求 6所述的文档更新装置, 其特征在于, 所述更新文档包 为补丁包, 所述补丁包中与所述源文档包不同的导航节点关联有作为更新文 件的补丁文件; 所述文档更新模块包括:
第二对比单元, 用于对比所述源导航信息和更新导航信息, 获得所述更 新导航信息中相对所述源导航信息增加的导航节点、 删除的导航节点以及修 改的导航节点; 第二更新单元, 用于将所述更新导航信息中增加的导航节点、 以及修改 的导航节点加入到源导航信息中, 实现对源文档包的更新;
第二标识单元, 用于为更新后的源导航信息中增加的导航节点添加新增 修改标记, 为修改后的导航节点和修改前的导航节点添加修改标记, 以及为 删除的导航节点添加删除修改标记, 以便根据所述新增修改标记、 修改标记 和删除修改标记查看更新内容。
9、 根据权利要求 6所述的文档更新方法, 其特征在于, 所述更新文档包 为扩展包, 所述扩展包包括有目标节点信息, 所述扩展包的导航信息中的各 导航节点关联有作为更新文件的扩展文件; 所述文档更新模块包括:
第三查找单元, 用于根据所述扩展包中的目标节点信息, 在所述源导航 信息中查找与所述目标节点信息对应的扩展节点;
第三更新单元, 用于将所述更新导航信息合并到所述扩展节点对应的位 置, 实现对所述源文档包的更新。
PCT/CN2011/078761 2011-08-23 2011-08-23 文档更新方法和装置 WO2012119407A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2011/078761 WO2012119407A1 (zh) 2011-08-23 2011-08-23 文档更新方法和装置
CN2011800015139A CN102356394B (zh) 2011-08-23 2011-08-23 文档更新方法和装置
US14/086,469 US20140081910A1 (en) 2011-08-23 2013-11-21 Method and apparatus for document updating

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/078761 WO2012119407A1 (zh) 2011-08-23 2011-08-23 文档更新方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/086,469 Continuation US20140081910A1 (en) 2011-08-23 2013-11-21 Method and apparatus for document updating

Publications (1)

Publication Number Publication Date
WO2012119407A1 true WO2012119407A1 (zh) 2012-09-13

Family

ID=45579278

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/078761 WO2012119407A1 (zh) 2011-08-23 2011-08-23 文档更新方法和装置

Country Status (3)

Country Link
US (1) US20140081910A1 (zh)
CN (1) CN102356394B (zh)
WO (1) WO2012119407A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110442359A (zh) * 2018-05-03 2019-11-12 大唐移动通信设备有限公司 一种对mib文档进行归并的方法及装置
CN109408778A (zh) * 2018-10-19 2019-03-01 成都信息工程大学 一种基于可视化配置的文档生成控制系统及方法
CN110442553B (zh) * 2019-07-05 2021-02-26 深圳赛安特技术服务有限公司 文件管理方法、装置、计算机设备和存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101420324A (zh) * 2008-10-10 2009-04-29 中兴通讯股份有限公司 一种网管系统及其代理软件的版本更新方法
CN101931944A (zh) * 2010-07-23 2010-12-29 华为终端有限公司 在线升级终端补丁的方法、装置与系统
US20110202541A1 (en) * 2010-02-12 2011-08-18 Microsoft Corporation Rapid update of index metadata

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7689901B2 (en) * 2001-03-01 2010-03-30 Sony Corporation Multiple updates to content descriptions using a single command
US7231394B2 (en) * 2001-07-17 2007-06-12 Sony Corporation Incremental bottom-up construction of data documents
US6925467B2 (en) * 2002-05-13 2005-08-02 Innopath Software, Inc. Byte-level file differencing and updating algorithms
US7584466B1 (en) * 2003-06-16 2009-09-01 Hewlett-Packard Development Company, L.P. Management tree management in a mobile handset
US7089270B2 (en) * 2003-06-20 2006-08-08 Innopath Software Processing software images for use in generating difference files
US8694620B2 (en) * 2003-09-08 2014-04-08 Microsoft Corporation System and method for an OMA DM extension to manage mobile device configuration settings
US7694293B2 (en) * 2003-09-26 2010-04-06 Hewlett-Packard Development Company, L.P. Update package catalog for update package transfer between generator and content server in a network
US7568195B2 (en) * 2003-12-16 2009-07-28 Microsoft Corporation Determining a maximal set of dependent software updates valid for installation
US8117293B1 (en) * 2005-01-05 2012-02-14 Smith Micro Software, Inc. Method of receiving, storing, and providing device management parameters and firmware updates to application programs within a mobile device
US7873959B2 (en) * 2005-02-01 2011-01-18 Microsoft Corporation Publishing the status of and updating firmware components
DE602006004384D1 (de) * 2005-03-21 2009-02-05 Hewlett Packard Development Co Mobiles Klientgerät und System mit Unterstützung von Fernverwaltungsgeräten
WO2007148899A1 (en) * 2006-06-19 2007-12-27 Samsung Electronics Co., Ltd. Information upgrade system and method for ota-capable device
US8307095B2 (en) * 2010-06-21 2012-11-06 Research In Motion Limited Firmware upgrade system and method in a device management architecture
US9069641B2 (en) * 2013-09-17 2015-06-30 Blackberry Limited Updating firmware on mobile devices

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101420324A (zh) * 2008-10-10 2009-04-29 中兴通讯股份有限公司 一种网管系统及其代理软件的版本更新方法
US20110202541A1 (en) * 2010-02-12 2011-08-18 Microsoft Corporation Rapid update of index metadata
CN101931944A (zh) * 2010-07-23 2010-12-29 华为终端有限公司 在线升级终端补丁的方法、装置与系统

Also Published As

Publication number Publication date
CN102356394A (zh) 2012-02-15
US20140081910A1 (en) 2014-03-20
CN102356394B (zh) 2013-09-11

Similar Documents

Publication Publication Date Title
US10776104B2 (en) Systems and methods for tracking configuration file changes
JP5282324B2 (ja) ユーザーインターフェースデータのためのデータコンテナ
KR100866076B1 (ko) 트리 데이터 교환의 관리를 위한 방법 및 장치
US8146100B2 (en) System and method for event-based information flow in software development processes
CN109376121B (zh) 一种基于ElasticSearch全文检索的文件索引系统及方法
JP2008257317A (ja) 情報処理装置、情報処理システム及びプログラム
US20100198874A1 (en) Data management method and apparatus
EP2356580A2 (en) Common configuration application programming interface
US9659023B2 (en) Maintaining and using a cache of child-to-parent mappings in a content-addressable storage system
WO2010059444A2 (en) Unified interface for configuring multiple networking technologies
US20100131622A1 (en) Unified storage for configuring multiple networking technologies
KR100737043B1 (ko) 화일 관리 방법, 콘텐츠 재생 방법, 콘텐츠 기록/재생 장치, 컴퓨터 실행 가능한 프로그램을 기록한 기록 매체, 및 컴퓨터 실행 가능한 콘텐츠 재생 프로그램을 기록한 기록 매체
WO2010059442A2 (en) Creating cross-technology configuration settings
US11487707B2 (en) Efficient file path indexing for a content repository
WO2012119407A1 (zh) 文档更新方法和装置
US8244688B2 (en) Managing apparatus, recording medium in which managing program is recorded, and expiration date determining method
CN109947739B (zh) 数据源管理方法及装置
WO2011085573A1 (zh) 管理实体文件的建立、更新方法以及管理装置
CN107463618B (zh) 一种索引创建方法和装置
TW201448544A (zh) 經由通用類型長度值產生器及剖析器之訊息交換
CN114328031A (zh) 元数据组织方法、系统、存储介质及备份方法、检索方法
KR101095423B1 (ko) 단말기 및 룩앤필 관리 방법
KR20170125665A (ko) M2M/IoT 플랫폼에서의 시맨틱 정보 관리 방법
WO2020116014A1 (ja) ドキュメント作成支援システム
JP5402066B2 (ja) 情報検索システム、情報検索装置、情報検索プログラム及び情報検索方法

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180001513.9

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11860378

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11860378

Country of ref document: EP

Kind code of ref document: A1