XML Document Management Server History Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current XDM Server history storage systems lack flexibility in selecting what information to store and when, leading to unnecessary data storage and inability to track specific events or time-based operations, which is inefficient and inflexible.
Innovation Solution
Implementing filter rules for history storage that allow users to define what information to store and when, enabling event-based and time-based storage, using XCAP PUT and SIP SUBSCRIBE methods to set and manage history preferences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If all history information is stored in the XDM Server, then complete history tracking is achieved, but storage space is wasted and data retrieval becomes inefficient
Solution Approach 1:
The patent extracts only the necessary history information from the complete set of operations. Filter rules are configured to select specific operations (e.g., only PUT operations, only operations on particular resources) to be stored as history, while other operations are not recorded. This extraction principle resolves the contradiction by storing only the essential history data needed for auditing and troubleshooting, eliminating waste of storage space on unnecessary information.
Solution Approach 2:
The patent applies different storage qualities to different types of history information based on filter rules. Certain operations are marked for storage while others are not, creating a non-uniform history storage strategy. This local quality approach allows the system to prioritize storage of important operations (like modifications) while skipping less important ones (like reads), thus maintaining information completeness for critical events while reducing overall storage volume.
2Quantity of substance
If filter rules are implemented for selective history storage, then storage efficiency is improved, but system complexity increases
Solution Approach 1:
The patent introduces filter rules as an intermediary layer between the history generation process and the actual storage process. These filter rules act as a configuration mechanism that mediates which operations should be stored. The filter rules are simple key-value pairs that can be easily configured and modified without changing the underlying system architecture, thus reducing the perceived complexity while still enabling selective storage.
Solution Approach 2:
The patent implements history storage control through parameter changes in the filter rules configuration. By modifying parameters such as operation type filters, resource path filters, and time range filters, the system can dynamically adjust what history is stored without structural changes. This parameter-based approach simplifies the system complexity as it relies on configurable parameters rather than complex conditional logic embedded in the core history management code.
3Adaptability or versatility
If event-based and time-based storage are enabled, then user flexibility is improved, but processing overhead increases
Solution Approach 1:
The patent applies preliminary action by pre-configuring filter rules that define event-based and time-based storage criteria before history operations occur. The filter rules are set up in advance with specific conditions (e.g., store only PUT events, store only events between certain times) so that when operations occur, the system can quickly evaluate them against the pre-defined rules without complex real-time decision-making. This preliminary configuration reduces processing overhead during actual history operations.
Solution Approach 2:
The patent introduces dynamics by making the history storage behavior adaptable through configurable filter rules. The system can dynamically adjust what history is stored based on the filter criteria without requiring architectural changes. The filter rules enable dynamic filtering of operations based on event type, resource, time, and other parameters, allowing the system to be flexible and adaptable to different user needs while maintaining efficient processing through rule-based evaluation.
Data Source
AI summary
A method for managing an Extensible Markup Language (XML) Document Management (XDM) Server history is provided. The method includes receiving, by the XDM Server, XML Documents and Filtering Rules within a filter body in an XCAP request from a first XDM Client Device, wherein the Filtering Rules define operation information performed on specific XML Documents to store as history information and further define when to store the history information of the XML Documents; storing the XML Documents and the Filtering Rules on the XDM Server; and when a second XDM Client Device has access to perform one or more operations on the XML Documents stored in the XDM Server, storing, by the XDM Server, the history information of the XML Documents according to the Filtering Rules by the XDM Server and the one or more operations performed.