XML Document Management Server Indirect Creation via XCAP URI
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing XDM service enablers face inefficiencies due to redundant information exchange and signaling overhead when creating XML documents, particularly in wireless environments, as they require transmitting and re-storing existing XML documents, leading to resource waste and processing delays.
Innovation Solution
The system and method for indirectly creating XML documents in an XDMS using the URL of an XCAP document, where the XDM Client sends an XCAP PUT request with a URI that identifies the source and destination storage positions, allowing the XDMS to retrieve and store the document without redundant data transfer, utilizing 'message/external-body' MIME type or a new XML application MIME type to describe the document's location instead of its content.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If the XDMC retrieves an XML document and stores it again in the XDMS using existing XDM creation function, then the XML document can be created in the XDMS, but redundant information is exchanged causing signaling overhead
Solution Approach 1:
The patent extracts only the necessary information (XML document content) from the source and transfers it directly to the destination storage position in the XDMS, eliminating the need to re-store the same content. The system uses GET request to retrieve the XML document and then directly places it at the target location, removing redundant storage operations.
Solution Approach 2:
The patent introduces an intermediary mechanism where the XDMS acts as a mediator between the source XML document and the destination storage position. Instead of the XDMC directly storing the document, the XDMS retrieves it from the source URI and automatically places it at the specified destination, streamlining the transfer process.
2Adaptability or versatility
If the XDMC retrieves and re-stores XML documents using existing XDM functions, then XML document management is achieved, but processing time is delayed due to redundant operations
Solution Approach 1:
The patent performs preliminary action by having the XDMC specify the complete destination storage position (including URI and storage location) in advance within the PUT request. This allows the XDMS to directly create the XML document at the target location without requiring subsequent storage operations, reducing processing time.
Solution Approach 2:
The patent makes the XDM creation function universal by allowing it to handle both creation of new documents and copying of existing documents through a single unified mechanism. The same PUT request can specify either a new document content or a source URI for copying, eliminating the need for separate operations.
3Adaptability or versatility
If redundant XML document transfer occurs over wireless channel, then XML document copying is achieved, but resource waste occurs
Solution Approach 1:
The patent extracts only the essential XML document content for copying, separating it from redundant metadata and control information. By using GET request to retrieve only the XML content and then directly placing it at the destination, the system minimizes the data transfer volume while achieving the copying function.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
A method for indirectly creating an XML (eXtensible Markup Language) document in an XDMS (XML Document Management Server) by using a URL (Uniform Resource Locator), which indicates the position of an XCAP (XML Configuration Access Protocol) document, in an XDM (XML Document Management) system including an XDMC (XDM Client) and an XDMS. The method includes transmitting an XCAP PUT request message, which contains an XCAP URI (Uniform Resource Identifier) and a storage position of an XML document to be created, to a corresponding XDMS by the XDMC; and receiving the XCAP PUT request message by the XDMS, retrieving an XML document corresponding to the XCAP URI contained in the XCAP PUT request message, and storing the XML document in the storage position.