WO2008049348A1 - Method and system, client, server of managing xml document - Google Patents

Method and system, client, server of managing xml document Download PDF

Info

Publication number
WO2008049348A1
WO2008049348A1 PCT/CN2007/070275 CN2007070275W WO2008049348A1 WO 2008049348 A1 WO2008049348 A1 WO 2008049348A1 CN 2007070275 W CN2007070275 W CN 2007070275W WO 2008049348 A1 WO2008049348 A1 WO 2008049348A1
Authority
WO
WIPO (PCT)
Prior art keywords
document
xml document
xml
document management
operation request
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2007/070275
Other languages
English (en)
French (fr)
Inventor
Hongqing Bao
Qian Sun
Yang Zhao
Linyi Tian
Chenghui Peng
Xuefei Song
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP07764203A priority Critical patent/EP2045725A4/en
Publication of WO2008049348A1 publication Critical patent/WO2008049348A1/zh
Priority to US12/357,690 priority patent/US20090125803A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
    • G06F16/81—Indexing, e.g. XML tags; Data structures therefor; Storage structures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
    • G06F16/83—Querying
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/93—Document management systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2105—Dual mode as a secondary aspect

Definitions

  • the present invention relates to Extensible Markup Language (XML) technology, and more particularly to XML document management methods, systems, clients, and servers. Background of the invention
  • the XML Document Management (XDM, XQuery Data Model) system is a general-purpose engine for a variety of communication services, capable of storing and managing data for various services.
  • OMA Open Mobile Alliance
  • XCAP XML Configuration Access Protocol
  • XCAP resources contain elements or attributes in an XML document or XML document.
  • the XCAP resource is identified by the XCAP Uniform Resource Identifier (URI), which corresponds to an XML document, an element in an XML document, or an attribute in an XML document.
  • URI Uniform Resource Identifier
  • the ordinary data of an XML document includes the elements and attributes of the XML document.
  • the XDM client (XDMC, XDM Client) uses the XCAP operation to use the XML document of the XML server (XMLS, XML Server).
  • the XDMC should construct the URI of the resource requesting the operation based on the usage of the application.
  • XDMC can perform the following general operations on XMLS XML documents: create or replace a document; delete a document; get a document; create or replace an element; delete an element; get an element; create or replace an attribute; An attribute; gets an attribute.
  • XCAP refer to the "The Extensible Markup Language (XML) Configuration Access Protocol" specification of the Internet Engineering Task Force (IETF).
  • XDMS also provides operational authentication of XML documents, management of XML documents, and Features such as change notifications for XML documents.
  • the shared XDMC stores a URI list document shared by the user, and the URI list includes a group that is reused by different service engines, an accept list, a reject list, and the like.
  • the embodiment of the invention provides an XML document management method, which enables the XDMC to manage the XML document flexibly and completely effectively.
  • the embodiment of the invention provides an XML document management system, which enables the XDMC to flexibly and completely manage XML documents.
  • the embodiment of the invention provides an XML document management client, which enables the XDMC to flexibly and completely manage XML documents.
  • the embodiment of the invention provides an XML document management server, which enables the XDMC to flexibly and completely manage XML documents.
  • An XML document management method including:
  • the XDMS receives an XML document management operation request sent by the XDMC, and the request carries the document identifier and status information;
  • the XDMS modifies the state of the document corresponding to the document identification to a state corresponding to the status information.
  • An XML document management system comprising: an XDMC and an XDMS; the XDMC, configured to send an XML document management operation request to the XDMS, where the request carries a document identifier and status information;
  • the XDMS is configured to change the state of the document corresponding to the document identifier to The status corresponding to the status information.
  • An XML document management client comprising: a message construction unit, a message sending unit; the message construction unit, configured to construct an XML document management operation request, wherein the request carries a document identifier and status information;
  • the message sending unit is configured to send the XML document management operation request to the XDMS.
  • An XML document management server comprising a receiving unit and a processing unit;
  • the receiving unit is configured to receive an XML document management operation request sent by the XDMC, where the request message carries document identification status information;
  • the processing unit is configured to receive the XML document management operation request sent by the receiving unit, and modify a state of the document corresponding to the document identifier to a state corresponding to the state information.
  • the XDMC carries the status information of the document in the document management request sent to the XDMS, so that the XDMS can change the state of the document, so that the state of the document reaches the management requirement of the XDMC.
  • FIG. 1 is a flowchart of an XML document management method according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of obtaining document status information according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of an XML document management system according to an embodiment of the present invention. Mode for carrying out the invention
  • Step 101 An XDMC sends an XML document management operation request to an XDMS, where the request carries a document identifier and status information.
  • Step 102 The XDMS obtains the current state information of the document corresponding to the document identifier, and determines whether the current state information is consistent with the state information carried in the request. If yes, the process ends; otherwise, step 103 is performed. This step is optional.
  • Step 103 The XDMS modifies current state information of the document according to the state information carried in the request.
  • the state information according to the embodiment of the present invention includes a suspended state and a restored state, and other states set by the XML document management system.
  • the XML document management of the embodiment of the present invention is performed only by using the state information as the suspended state and the restored state. The method is explained.
  • the status information of the document belongs to the attribute information of the document, that is, the additional information of the document, which is the metadata of the document, and the metadata of the document is highly correlated with the document itself (for example, the creation time of the document, etc.).
  • a document includes the metadata of the document and the normal data of the document.
  • the metadata of a document is some data that describes additional information about the document.
  • a document can have several kinds of metadata, such as when the document was created, the owner of the document, etc., as metadata for the document.
  • the difference between the metadata of the document and the normal data of the document is mainly:
  • the metadata of the document describes the attributes of the document.
  • the metadata of the document is often maintained by the XDMS and cannot be changed by the XDMC at will, and the normal data of the document can be changed by the XDMC. .
  • a common implementation of storing XML documents in XDMS is: Recording XML documents with tables in the database.
  • the records in the table generally include the following fields: User ID (used to identify the owner of the XML document), document name, creation time, version label of the document (E Tag) and other fields.
  • a field describing the state of the document is added to the record.
  • setting the value of this field to "inactive” indicates that the document is pending; when restoring the document, set the value of this field to "active” to indicate this The document is active.
  • the identifier of the document metadata also referred to as an accessor
  • the information in the document to control the state of the document, such as the suspension or recovery of the document.
  • the XDMC When an operation is to be performed on a document, the XDMC sends an XCAP message containing the identifier Request-URI of the document metadata to specify the XCAP resource to be accessed, ie the metadata information of the XML document to be accessed.
  • the value of a Request-URI parameter can be: http : ⁇ xcap. example.com/resource-lists/users/sip :joe@ example.com/ind ex
  • This Request-URI consists of the following parts:
  • XCAP Root The context of the document that is managed by the XCAP server and contains all applications for all users. For example, http: ⁇ xcap.example.com in the above example.
  • Document selector Consists of a series of path segments, each path segment is separated by a "symbol, and the document selector specifies an XML document in the root of the XCAP.
  • Metadata selector separator In order to distinguish it from the node selector in the XCAP protocol, the symbol " ⁇ @" is used in the embodiment of the present invention, and other suitable symbols may of course be selected.
  • Metadata selector Specify specific metadata for the selected document, such as selecting the document status. Use "state" as the metadata selector.
  • the Request-URI that accesses the metadata of the XML document may also include the following additional parts:
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • Document status information can be stored in a separate XCAP resource document.
  • the relationship between the XCAP URI identifier of an XML document and the XCAP URI identifier of its document status information is as follows:
  • the XCAP URI of the document status information consists of a suffix ".state” appended to the XCAP URI of the corresponding XML document.
  • XCAP URI of an XML document is identified as:
  • Http ⁇ xcap. example.com/resource-lists/users/sip :joe@ example.com/ind ex
  • Http ⁇ xcap. example.com/resource-lists/users/sip :joe@ example.com/ind ex.state
  • the status information of the document described in step 101 is inactive.
  • step 103 the XDMS changes the status information of the document to inactive according to the status information of the document acquired in step 102, if the current status information of the document is active, and returns a message indicating successful operation to the XDMC; The status information is inactive. The current state information of the document is maintained, and a message that the operation failed is returned to the XDMC. Similarly, to implement the recovery operation of the document, the status information of the document in step 101 is active.
  • step 103 the XDMS maintains the current state information of the document according to the state information of the document acquired in step 102, if the current state information of the document is active, and returns an invalid operation message to the XDMC; If the current status information is inactive, the status information of the document is changed to active, and a message indicating that the operation is successful is returned to the XDMC.
  • the XDMC When performing a suspend and resume operation on a document, when an XDMC suspends a document, the XDMC sends an XML document suspend operation request to the XDMS. If the XDMS returns a success response message, the document on the XDMS is originally active. , and is currently in the suspended state, if the XDMS returns an error message indicating that the document on the XDMS is in a suspended state and is still in a suspended state. When an XDMC performs a recovery operation on a document, the situation is similar to the above situation. When the XDMS returns a success response message, it indicates that the XDMS document is in a suspended state and is currently active. Otherwise, the XDMS document is originally active. , and is currently active.
  • the current state value of the document can also be given in the body of the error message or in the header field of the contract. This is because a return message is made up of several parts, one is the message type, and some are called the header field.
  • the message type is a number, and each header field field includes a header domain name and a header field value. You can specify a number of message types to represent the current state of the document, or you can use a header field to represent different document states with different header fields.
  • XDMC can obtain status information about a document before initiating a suspend or resume operation on the document.
  • the current state information of the acquired document is consistent with the state required by the XDMC, there is no need to initiate an operation on the document state information. If the metadata containing the document status information is stored in a separate XML document,
  • Step 201 The XDMC initiates a request for acquiring document status information to the separate XML document; the request is: according to an access character of the document whose state is to be obtained, the XDMC constructs an access symbol of the document storing the document status information. Specifically: Add a ".state" suffix after the accessor of the document whose status you want to get.
  • Step 202 The XDMS returns current status information of the document to the XDMC according to the request message.
  • the XDMC obtains the current state of the document in advance, and if the current state of the document is the state required by the XDMC, it is not necessary to initiate a suspension or recovery request for the document, thereby making the process more simple.
  • XDMC sends a suspend request: XDMC first sends a suspend request message to the XDMS, here is a message of XCAP protocol, the Request-URI parameter in the message is as described in the previous section. Using the example of the Request-URI given at the end of the previous section, the pending request message is given as follows:
  • User-Agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; )
  • the pending request message is as follows: PUT Http://xcap.example om/resource-lists/users/sip:joe@example.com/index.sta te HTTP/1.1
  • the PUT method can be used to modify only the status information, as follows:
  • User-Agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; )
  • XDMS In the process of checking the Request-URI, XDMS first finds the XML document corresponding to this parameter. After checking the metadata selector separator, according to the metadata selector, the storage location of the metadata is first checked, and the current element is checked first.
  • the data content here is the status information of the document, ⁇ according to the status information of the document as follows:
  • XDMS looks at the message body part of the above request message. If the content of the message body is "inactive”, the status of the document is changed to "inactive”, and the operation success prompt message is as follows :
  • XDMC sends a recovery request: XDMC first sends a suspend recovery message to the XDMS, here is a message of XCAP protocol, the Request-URI parameter in the message is as described in the previous section. Using the example of the Request-URI given at the end of the previous section, the recovery request message is given as follows:
  • User-Agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; )
  • the XDMS processes the recovery request: After receiving the above request, the XDMS first finds the XML document corresponding to the parameter in the process of checking the Request-URI, and after checking the metadata selector separator, according to the metadata selector positioning
  • the storage location of the metadata, first check the current metadata content, here is the status information of the document, at this time:
  • the XDMC manages the status information of the document in the XML document management request sent by the XDMS, so that the XDMS can change the state of the document, so that the state of the document meets the management needs of the XDMC.
  • XDMC and XDMS cannot perform general operations on the document, thereby enabling XDMC to fully control the document and manage the document more conveniently.
  • the XDMC can also obtain the current state of the document in advance. If the current state of the document is the state required by the XDMC, it is not necessary to initiate a suspend or resume request for the document, thereby making the process more simple.
  • FIG. 3 it is a schematic structural diagram of an XML document management system according to an embodiment of the present invention, where the system includes an XDMC and an XDMS.
  • the XDMC is configured to send an XML document management operation request to the XDMS, where the request carries a document identifier and status information.
  • the XDMC includes a message construction unit and a message sending unit, a message construction unit, configured to construct an XML document management operation request carrying the document identification and status information, and a message sending unit, configured to send the XML document management operation request to the XDMS.
  • the XDMS is configured to change a state of the document corresponding to the document identifier to a state corresponding to the state information.
  • the XDMS includes a receiving unit, a processing unit, an obtaining unit, and a determining unit.
  • the receiving unit is configured to receive an XML document management operation request transmitted by the XDMC, where the request carries a document identifier and status information.
  • the document identifies the current state information of the corresponding document, and transmits the current state information to the determining unit.
  • the determining unit is configured to determine whether the current state information is consistent with the state information in the XML document management operation request. Sending a startup instruction to the processing unit when the content is inconsistent; the processing unit is configured to receive the XML document management operation request transmitted by the receiving unit, and modify a state of the document corresponding to the document identifier to the status information Corresponding ⁇ state.
  • the XDMC carries the state information of the XML document in the XML document management request sent to the XDMS, so that the XDMS can change the state of the XML document, so that the state of the document reaches the XDMC.
  • Management needs. Due to changes in the state of the XML document, such as when the document state is suspended, XDMC and XDMS cannot perform general operations on the XML document, thereby making XDMC flexible and completely effective in controlling the XML document, and it is more convenient to manage the XML document. It is within the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and the modifications of the invention

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Software Systems (AREA)
  • Information Transfer Between Computers (AREA)

Description

可扩展标记语言文档管理方法、 系统、 客户端及服务器 技术领域
本发明涉及可扩展标记语言 （ XML, Extensible Markup Language ) 技术， 尤其涉及 XML文档管理方法、 系统、 客户端及服务器。 发明背景
XML文档管理 (XDM, XQuery Data Model )系统是多种通信业务的 通用引擎， 能够存储和管理各种业务的数据。 开放移动联盟 （OMA, Open Mobile Alliance ) 已经对 XML文档的管理制定了初步的规范， 通过 XML配置访问协议（XCAP， XML Configuration Access Protocol ) 实现 对 XML文档的管理。
XCAP资源包含 XML文档或 XML文档中的元素或属性。 XCAP资源 通过 XCAP通用资源标志符（URI, Uniform Resource Identifier )来识别， 一个 XCAP URI对应着一个 XML文档、 XML文档中的一个元素或 XML 文档中的一个属性。 XML文档的普通数据包括该 XML文档的元素和属 性。 XDM客户端 (XDMC, XDM Client)通过 XCAP操作来使用 XML服务 器（XMLS, XML Server ) 的 XML文档， XDMC应该基于应用的使用方 法来构造请求操作的资源的 URI。 目前， XDMC可以对 XMLS 的 XML文 档进行如下的一般操作： 创建或取代一个文档； 删除一个文档； 获取一 个文档； 创建或取代一个元素； 删除一个元素； 获取一个元素； 创建或 取代一个属性； 删除一个属性； 获取一个属性。 关于 XCAP具体可以参 见互联网工程组 （IETF , Internet Engineering Task Force ) 的 "The Extensible Markup Language (XML) Configuration Access Protocol" 规范。
XDMS还提供对 XML文档的操作鉴权、 对 XML文档的管理和对 XML文档的改变通知等功能。 如共享 XDMC存储用户共享的 URI列表文 档， URI列表包括被不同业务引擎重用的群组、 接受列表、 拒绝列表等。
现有技术中， XML系统只提供了对 XML文档本身的一般操作， 因 此 XDMC只能对 XML文档本身进行一般操作。而在实际运用中， XDMC 需要对 XML文档进行灵活的完全的控制。 发明内容
本发明实施例提供一种 XML文档管理方法， 该方法能够使 XDMC 对 XML文档进行灵活而完全有效的管理。
本发明实施例提供一种 XML文档管理系统， 该系统能够使 XDMC 对 XML文档进行灵活而完全有效的管理。
本发明实施例提供一种 XML 文档管理客户端， 该客户端能够使 XDMC对 XML文档进行灵活而完全有效的管理。
本发明实施例提供一种 XML 文档管理服务器， 该服务器能够使 XDMC对 XML文档进行灵活而完全有效的管理。
一种 XML文档管理方法， 包括：
XDMS接收由 XDMC发送的 XML文档管理操作请求， 所述请求中携 带文档标识和状态信息；
XDMS将与所述文档标识对应的文档的状态修改为与所述状态信息 对应的 态。 一种 XML文档管理系统， 包括 XDMC和 XDMS； 所述 XDMC, 用于向所述 XDMS发送 XML文档管理操作请求， 所述 请求中携带文档标识和状态信息；
所述 XDMS , 用于将与所述文档标识对应的文档的状态^ ίι爹改为与所 述状态信息对应的状态。
一种 XML文档管理客户端， 包括： 消息构造单元、 消息发送单元； 所述消息构造单元， 用于构造 XML文档管理操作请求， 所述请求中 携带文档标识和状态信息；
所述消息发送单元，用于将所述 XML文档管理操作请求发送给所述 XDMS。
一种 XML文档管理服务器， 包括接收单元、 处理单元；
所述接收单元， 用于接收 XDMC传送的 XML文档管理操作请求， 所 述请求消息中携带文档标识状态信息；
所述处理单元，用于接收所述接收单元传送的所述 XML文档管理操 作请求， 将与所述文档标识对应的文档的状态修改为与所述状态信息对 应的^ 态。
本发明实施例的有效益效果如下：
1 ) XDMC通过在向 XDMS发送的文档管理请求中携带所述文档的 状态信息， 以使 XDMS能够改变所述文档的状态，从而使文档的状态达 到 XDMC的管理需要。
2 ) 由于文档状态的改变， 如文档状态为挂起状态时， XDMC 及 XDMS就不能对所述文档进行一般操作， 从而使 XDMC能够完全的控 制 XML文档， 更为方便管理 XML文档。 附图简要说明
图 1为本发明实施例 XML文档管理方法的流程图；
图 2为本发明实施例获取文档状态信息的流程图； 图 3为本发明实施例 XML文档管理系统的结构示意图。 实施本发明的方式
如图 1所示， 为本发明实施例 XML文档管理方法的流程图， 该方法 包括如下步骤： 步骤 101、 XDMC向 XDMS发送 XML文档管理操作请求， 所述 请求中携带文档标识和状态信息。
步骤 102、 XDMS获取与所述文档标识对应的文档的当前状态信息， 判断所述当前状态信息与所述请求中携带的状态信息是否一致， 若一 致， 则结束流程； 否则， 执行步骤 103。 本步骤可选。
步骤 103、 XDMS根据所述请求中携带的状态信息修改所述文档的 当前状态信息。
本发明实施例所述的状态信息包括挂起状态和恢复状态， 以及由 XML文档管理系统设置的其它状态， 下面仅以所述的状态信息为挂起 状态和恢复状态对本发明实施例 XML文档管理方法进行说明。
文档的状态信息属于文档的属性信息， 也即文档的附加信息， 是文 档的元数据，文档的元数据是与文档本身高度关联的 (例如文档的创建时 间等)。 引入文档的元数据之后， 一个文档包括该文档的元数据和该文档 的普通数据。 文档的元数据是描述文档附加信息的一些数据。 一个文档 可以有若干种元数据， 例如文档的创建时间， 文档的拥有者等都可以作 为文档的元数据。 文档的元数据与文档的普通数据之间的区别主要是： 文档的元数据描述文档的属性，文档的元数据往往由 XDMS维护， 不能 由 XDMC随意更改， 而文档的普通数据可以由 XDMC进行更改。
XDMS中存储 XML文档的常见实现方案是： 用数据库中的表记录 XML文档， 表中的记录一般包括如下字段： 用户标识 (用于标识 XML文档的拥有者）， 文档名称， 创建时间， 文 档的版本标签 （E Tag)等字段。
为实现文档的挂起 /恢复操作，本发明实施例中在所述记录中增加一 个描述文档的状态的字段。 当对文档进行挂起操作时， 将此字段的值设 置为 "inactive" ，表示此文档处于挂起状态； 当对文档进行恢复操作时， 将此字段的值设置为为 "active" , 表示此文档处于活动状态。 而采用 XCAP协议实现文档的挂 ¾/恢复操作， 需要确定文档元数据的标识 （也 可称为访问符)， 以通过该标识访问所述文档的元数据， 并通过 ^ίι爹改文档 元数据中的信息来实现文档状态的控制， 如实现文档的挂起或恢复。 当 要对文档实施某种操作时， XDMC发送一个 XCAP消息， 消息中包含文 档元数据的标识 Request-URI, 来指定要访问的 XCAP资源， 即所要访 问的 XML文档的元数据信息。 例如一个 Request-URI参数的值可以是： http :〃xcap. example.com/resource-lists/users/sip :joe@ example.com/ind ex
下面列举两种表示文档元数据的方法的实施例。
实施例一
设定规定格式的 Request-URI来指定所要访问的 XML文档的元数 据位置信息。 此 Request-URI由以下部分组成：
XCAP根： 是由 XCAP服务器管理的包含所有用户的所有应用的 文档的上下文。 例如上面例子中的 http:〃xcap.example.com。
文档选择符： 由一系列的路径片断组成， 每个路径片断由一个 " 符号分隔， 文档选择符指定 XCAP根中的一个 XML文档。
元数据选择符分隔符： 为区别于 XCAP协议中的节点选择符， 本发 明实施例中采用符号 "一 @" , 当然也可以选择其他合适的符号。
元数据选择符： 指定选择文档的特定元数据， 例如选择文档状态可 以使用 "state"作为元数据选择符。
由于元数据信息可能是筒单的数据格式， 也可能是复杂的 XML格 式， 因此， 访问 XML文档元数据的 Request-URI还可以包含如下附加 部分：
现在， 我们可以给出上述例子中名称为 index的文档的元数据文档 状态的 Request-URI参数：
http://xcap.example.eom/resource-lists/resource-lists/users/sip:joe@exa mple.com/index/ ~~ @ /state
实施例二：
文档状态信息可以用一个单独的 XCAP资源文档存储。 一个 XML 文档的 XCAP URI标识与其文档状态信息的 XCAP URI标识的关系如 下：
文档状态信息的 XCAP URI由相应的 XML文档的 XCAP URI附加 一个后缀 ".state"构成。
例如一个 XML文档的 XCAP URI标识为：
http :〃xcap. example.com/resource-lists/users/sip :joe@ example.com/ind ex
那么这个文档的文档状态信息的 XCAP URI为
http :〃xcap. example.com/resource-lists/users/sip :joe@ example.com/ind ex.state
要实现文档的挂起操作， 步骤 101 中所述文档的状态信息为 inactive。
步骤 103中， XDMS根据其在步骤 102中所获取的文档的状态信息， 如果文档的当前状态信息为 active,则更改文档的状态信息为 inactive,并 向 XDMC返回操作成功的消息； 如果文档的当前状态信息为 inactive , 则保持所述文档的当前状态信息， 并向 XDMC返回操作失败的消息。 同理， 要实现文档的恢复操除， 步骤 101中所述文档的状态信息为 active.
步骤 103中， XDMS根据其在步骤 102中所获取的文档的状态信息， 如果文档的当前状态信息为 active, 则保持所述文档的当前状态信息.并 向 XDMC返回操作无效的消息； 如果文档的当前状态信息为 inactive, 则更改文档的状态信息为 active, 并向 XDMC返回操作成功的消息。
在执行对文档的挂起、 恢复操作时， 当一个 XDMC对一个文档实 施挂起操作， XDMC发送 XML文档挂起操作请求给 XDMS , 若 XDMS 返回成功响应消息，说明 XDMS上的文档原处于活动状态， 并且当前处 于挂起状态， 若 XDMS返回错误提示消息， 说明 XDMS上的文档原处 于挂起状态， 并且当前仍处于挂起状态。 当一个 XDMC对一个文档实 施恢复操作时的情形与上述情形类似， 当 XDMS返回成功响应消息时， 说明 XDMS的文档原处于挂起状态， 并且当前处于活动状态， 否则说明 XDMS的文档原处于活动状态， 并且当前处于活动状态。
除了上述利用操作时返回消息的类型来获得文档的当前状态外， 还 可以在错误提示消息的消息体或约定的头域字段中给出文档的当前状 态值。 这是因为一条返回消息是由若干部分组成的， 一个是消息类型， 还有一些叫做头域字段。 消息类型是一个数字， 每个头域字段又包括头 域名和头域值两部分。 可以约定消息类型的某个数字用来表示文档的 当前状态， 也可以使用一个头域字段， 用不同的头域值表示不同的文档 状态。
此外， XDMC还可以在发起对文档进行挂起或恢复操作之前， 获取 文档的状态信息。 当所获取的文档的当前状态信息与 XDMC所需要的 状态一致， 则无需再发起对文档状态信息的操作。 如果包含文档状态信息的元数据存储于一个单独的 XML文档中，
XDMC获取文档状态的方法如图 2所示， 具体流程如下：
步骤 201、 XDMC向所述单独的 XML文档发起获取文档状态信息 的请求； 所述请求为： 根据要获取其状态的文档的访问符， XDMC构造 存储此文档状态信息的文档的访问符。 具体是： 在要获取其状态的文档 的访问符后添加" .state"后缀。
步骤 202、 XDMS根据所述请求消息， 将所述文档的当前状态信息 返回给 XDMC。
由此可以看出， XDMC通过预先获取所述文档的当前状态， 如果文 档的当前状态为 XDMC所需的状态， 则不必在发起对文档的挂起或恢 复请求， 从而使流程更为筒单。
对于实现文档的挂起操作， 具体实施例如下：
1. XDMC发送挂起请求： XDMC首先向 XDMS发送挂起请求消 息， 这里是一个 XCAP协议的消息， 消息中的 Request-URI参数如上节 所述。 利用上节最后给出的 Request-URI的例子， 给出挂起请求消息如 下：
PUT
http://xcap.example.eom/resource-lists/resource-lists/users/sip:joe@example. com/index/— ©/state HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; )
Host: xcap.example.com
Inactive
该挂起请求消息中的 "Inactive" 为消息体。
如果状态信息单独放在一个 XML文档内， 则挂起请求消息如下： PUT http://xcap.example om/resource-lists/users/sip:joe@example.com/index.sta te HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; ) Host: xcap.example.com
<?xml version="1.0" encodings "UTF- 8 "?>
<state>inactive</ state>
如果该单独文档还包括除状态信息 <state〉之外其他内容如授权规则 Access信息， 则可以用 PUT方法只修改状态信息， 如下：
PUT
http://xcap.example om/resource-lists/users/sip:joe@example.com/index.sta te/~~/state HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; )
Host: xcap.example.com inactive
2. XDMS在检查 Request-URI的过程中， 首先查找到此参数对应的 XML文档， 在检查到元数据选择符分隔符后， 根据元数据选择符定位 元数据的存储位置， 首先检查当前的元数据内容， 在这里是文档的状态 信息， ^^据文档的状态信息作如下处理：
- 若文档的状态值为 "active" , XDMS 查看上述请求消息中的 消息体部分， 若消息体的内容为 "inactive" , 则将文档的状态修改为 "inactive" , 并返回操作成功提示消息如下：
HTTP/1.1 200 OK
Connection: close
- 若文档的状态值为 "inactive" ，则请求操作无效， XDMS 返回 失败消息： HTTP/1.1 403 Forbidden
Connection: close
对于实现文档的恢复操作， 具体实施例如下：
1. XDMC发送恢复请求： XDMC首先向 XDMS发送挂起恢复消 息， 这里是一个 XCAP协议的消息， 消息中的 Request-URI参数如上节 所述。 利用上节最后给出的 Request-URI的例子， 给出恢复请求消息如 下：
PUT
http://xcap.example.eom/resource-lists/resource-lists/users/sip:joe@example. com/index/— ©/state HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; )
Host: xcap.example.com
Active
2. XDMS 处理恢复请求： XDMS 收到上述请求后， 在检查 Request-URI的过程中， 首先查找到此参数对应的 XML文档， 在检查到 元数据选择符分隔符后， 根据元数据选择符定位元数据的存储位置， 首 先检查当前的元数据内容， 在这里是文档的状态信息， 此时：
- 若得到文档的状态为 "active" , 则此恢复请求无效， XDMS发 送合适的相应消息如下， 例如可以发送：
HTTP/1.1 403 Forbidden
Connection: close
- 若得到文档的状态为 "inactive" , 则此恢复请求有效， XDMS 将文档状态修改为 "active" ，并返回操作成功提示消息：
HTTP/1.1 200 OK
Connection: close。 由以上方案可以看出， XDMC通过在向 XDMS发送的 XML文档管 理请求中携带的文档的状态信息， 以使 XDMS 能够改变所述文档的状 态， 从而使文档的状态达到 XDMC 的管理需要。 此外， 由于文档状态 的改变， 如文档状态为挂起状态时， XDMC及 XDMS就不能对所述文 档进行一般操作， 从而使 XDMC 能够完全的控制文档， 更为方便的管 理文档。 此外， XDMC还可以预先获取所述文档的当前状态， 如果文档 的当前状态为 XDMC所需的状态， 则不必在发起对文档的挂起或恢复 请求， 从而使流程更为筒单。
参见图 3, 为本发明实施例 XML文档管理系统的结构示意图， 该 系统包括 XDMC和 XDMS。
所述 XDMC, 用于向所述 XDMS发送 XML文档管理操作请求， 所述 请求中携带文档标识和状态信息。 XDMC包括消息构造单元和消息发送 单元； 消息构造单元， 用于构造携带文档标识和状态信息的 XML文档管 理操作请求； 消息发送单元， 用于发送所述 XML文档管理操作请求给 XDMS。 所述 XDMS , 用于将与所述文档标识对应的文档的状态^ ίι爹改为与所 述状态信息对应的状态。 XDMS包括接收单元、 处理单元、 获取单元和 判断单元； 所述接收单元用于接收 XDMC传送的 XML文档管理操作请 求， 所述请求中携带文档标识和状态信息； 所述获取单元用于获取与所 述文档标识对应的文档的当前状态信息， 将所述当前状态信息传送给所 述判断单元； 判断单元， 用于判断出所述当前状态信息是否与所述 XML 文档管理操作请求中的状态信息一致， 当不一致时向处理单元发送启动 指令；所述处理单元用于接收所述接收单元传送的所述 XML文档管理操 作请求， 将与所述文档标识对应的文档的状态修改为与所述状态信息对 应的^ 态。 本发明实施例 XML文档管理的方案中， XDMC通过在向 XDMS发 送的 XML文档管理请求中携带 XML文档的状态信息， 以使 XDMS能 够改变所述 XML文档的状态，从而使文档的状态达到 XDMC的管理需 要。 由于 XML文档状态的改变， 如文档状态为挂起状态时， XDMC及 XDMS就不能对所述 XML文档进行一般操作，从而使 XDMC灵活而且 完全有效的控制 XML文档， 更为方便管理 XML文档。 离本发明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发 明权利要求及其等同技术的范围之内， 则本发明也意图包含这些改动和 变型在内。

Claims

权利要求书
1. 一种可扩展标记语言 XML文档管理方法， 其特征在于， 所述方 法包括：
XML文档管理服务器 XDMS接收由 XML文档管理客户端 XDMC发 送的 XML文档管理操作请求， 所述请求中携带文档标识和状态信息；
XDMS将与所述文档标识对应的文档的状态修改为与所述状态信息 对应的 态。
2.如权利要求 1所述的方法， 其特征在于， 所述 XML文档管理操作 请求为挂起操作请求时， 所述状态信息为挂起状态；
所述 XML文档管理操作请求为恢复操作请求时，所述状态信息为活 动^ 态。
3. 如权利要求 1所述的方法， 其特征在于， 所述 XML文档管理操作 请求通过 XML配置访问协议的消息实现。
4. 如权利要求 1所述的方法， 其特征在于， XML文档管理操作请求 携带的所述文档标识设置在 XML配置访问协议的消息的 Request-URI参 数中， XML文档管理操作请求携带的所述状态信息设置在 XML配置访问 协议的消息的消息体中。
5. 如权利要求 1至 4任一项所述的方法， 其特征在于， 与所述文档 的状态对应的状态信息存储在所述文档的元数据中或者单独的文档中。
6.如权利要求 1所述的方法，其特征在于，所述 XDMS接收由 XDMC 发送的 XML文档管理操作请求之前， 该方法包括：
XDMC获取与所述文档标识对应的文档的状态， 所述获取的文档的 状态与 XDMC所需要的状态不一致。
7.—种 XML文档管理系统， 其特征在于， 该系统包括 XML文档管理 客户端 XDMC和 XML文档管理服务器 XDMS; 所述 XDMC, 用于向所述 XDMS发送 XML文档管理操作请求， 所述 请求中携带文档标识和状态信息； 所述 XDMS , 用于将与所述文档标识对应的文档的状态^ ίι爹改为与所 述状态信息对应的状态。
8.如权利要求 7所述的系统， 其特征在于， 所述 XDMC包括消息构造 单元和消息发送单元； 所述消息构造单元，用于构造携带文档标识和状态信息的所述 XML 文档管理操作请求； 所述消息发送单元，用于将所述 XML文档管理操作请求发送给所述 XDMSo
9.如权利要求 7所述的系统， 其特征在于， 所述 XDMS包括接收单元 和处理单元； 所述接收单元， 用于接收 XDMC传送的携带文档标识和状态信息的 所述 XML文档管理操作请求； 所述处理单元，用于接收所述接收单元传送的所述 XML文档管理操 作请求， 将与所述文档标识对应的文档的状态修改为与所述状态信息对 应的^ 态。
10.如权利要求 9所述的系统， 其特征在于， 所述 XDMS包括获取单 元和判断单元； 所述获取单元，用于获取与 XML文档管理操作请求携带的所述文档 标识对应的文档的当前状态信息， 将所述当前状态信息传送给所述判断 单元； 所述判断单元，用于判断出所述当前状态信息与 XML文档管理操作 请求中携带的状态信息不一致时， 向所述处理单元发送启动指令。
11.一种 XML文档管理客户端 XDMC,其特征在于，该 XDMC包括消 息构造单元和消息发送单元； 所述消息构造单元， 用于构造 XML文档管理操作请求， 所述请求中 携带文档标识和状态信息； 所述消息发送单元，用于将所述 XML文档管理操作请求发送给所述 XDMS。
12.—种 XML文档管理服务器 XDMS, 其特征在于， 该 XDMS包括接 收单元和处理单元； 所述接收单元， 用于接收 XDMC传送的 XML文档管理操作请求， 所 述请求中携带文档标识和状态信息； 所述处理单元，用于接收所述接收单元传送的所述 XML文档管理操 作请求， 将与所述文档标识对应的文档的状态修改为与所述状态信息对 应的^ 态。
13.如权利要求 12所述的 XDMS, 其特征在于， 所述 XDMS包括获取 单元和判断单元； 所述获取单元，用于获取与 XML文档管理操作请求携带的所述文档 标识对应的文档的当前状态信息， 将所述当前状态信息传送给所述判断 单元； 所述判断单元，用于判断出所述当前状态信息与 XML文档管理操作 请求中携带的状态信息不一致时， 向所述处理模块发送启动指令。
PCT/CN2007/070275 2006-10-24 2007-07-11 Method and system, client, server of managing xml document Ceased WO2008049348A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP07764203A EP2045725A4 (en) 2006-10-24 2007-07-11 PROCESS AND SYSTEM, CLIENT, SERVER FOR MANAGING AN XML DOCUMENT
US12/357,690 US20090125803A1 (en) 2006-10-24 2009-01-22 Method, system, client and server for managing xml document

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610063281.0 2006-10-24
CNA2006100632810A CN101170540A (zh) 2006-10-24 2006-10-24 一种xml文档管理方法和客户端、服务器

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/357,690 Continuation US20090125803A1 (en) 2006-10-24 2009-01-22 Method, system, client and server for managing xml document

Publications (1)

Publication Number Publication Date
WO2008049348A1 true WO2008049348A1 (en) 2008-05-02

Family

ID=39324139

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/070275 Ceased WO2008049348A1 (en) 2006-10-24 2007-07-11 Method and system, client, server of managing xml document

Country Status (4)

Country Link
US (1) US20090125803A1 (zh)
EP (1) EP2045725A4 (zh)
CN (1) CN101170540A (zh)
WO (1) WO2008049348A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010026023A1 (de) * 2008-09-02 2010-03-11 Infineon Technologies Ag Verfahren zur ermittlung aktiver kommunikationssitzungen, kommunikationssitzungs-informationsserver, verfahren zum bereitstellen einer information über aktive kommunikationssitzungen und dokumentenmanagement-server

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100514968C (zh) 2005-10-11 2009-07-15 华为技术有限公司 离线消息的处理方法和即时消息服务器
CN101808073A (zh) * 2009-02-13 2010-08-18 华为技术有限公司 一种获取节点信息的方法、服务器以及系统
EP2480989A4 (en) * 2009-09-22 2013-03-27 Ericsson Telefon Ab L M METHOD AND ARRANGEMENTS FOR MODIFYING XML DOCUMENTS
CN102726030B (zh) * 2010-02-02 2016-01-20 瑞典爱立信有限公司 用于路由xcap请求的方法和设备
CN102882844B (zh) * 2012-07-20 2015-05-13 广东电网公司电力科学研究院 一种基于xml文件的多屏互动展现的实现方法
US8825828B2 (en) * 2012-10-10 2014-09-02 Ca, Inc. Method and system for implementing notifications
CN113674818A (zh) * 2021-08-23 2021-11-19 苏州优炫智能科技有限公司 一种医药电子试验主文档的管理方法及管理系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1296251A1 (en) * 2001-09-19 2003-03-26 Kreter, Martin Document creation system
US20040019630A1 (en) * 2002-07-24 2004-01-29 International Business Machines Corporation Method and apparatus for processing workflow through a gateway
US20050138132A1 (en) * 2003-12-22 2005-06-23 International Business Machines Corporation Method and system for instant messaging bots specification using state transition methodology and XML
CN1794692A (zh) * 2005-11-25 2006-06-28 华为技术有限公司 通信系统和在通信系统中查询信息的方法

Family Cites Families (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US473162A (en) * 1892-04-19 Rail-joint
JP3794659B2 (ja) * 1997-07-23 2006-07-05 シャープ株式会社 通信機
US6298122B1 (en) * 1998-12-07 2001-10-02 Gregory L. Horne Caller ID system
US6721059B1 (en) * 1999-07-30 2004-04-13 Hewlett-Packard Develpoment Company, L.P. Method and apparatus for automatically handling faxes
US6941510B1 (en) * 2000-06-06 2005-09-06 Groove Networks, Inc. Method and apparatus for efficient management of XML documents
US6883168B1 (en) * 2000-06-21 2005-04-19 Microsoft Corporation Methods, systems, architectures and data structures for delivering software via a network
US20040131164A1 (en) * 2002-12-20 2004-07-08 Gould Mark Wendell Method and apparatus for automated telephone call screening
US7644361B2 (en) * 2002-12-23 2010-01-05 Canon Kabushiki Kaisha Method of using recommendations to visually create new views of data across heterogeneous sources
US20050012966A1 (en) * 2003-07-14 2005-01-20 Mitchell Shirley F. Method for blocking unwanted facsimile transmissions
US7698398B1 (en) * 2003-08-18 2010-04-13 Sun Microsystems, Inc. System and method for generating Web Service architectures using a Web Services structured methodology
US7831693B2 (en) * 2003-08-18 2010-11-09 Oracle America, Inc. Structured methodology and design patterns for web services
US7526563B2 (en) * 2004-02-27 2009-04-28 Nokia Corporation Interworking gateway and method
US7706401B2 (en) * 2004-08-13 2010-04-27 Verizon Business Global Llc Method and system for providing interdomain traversal in support of packetized voice transmissions
US7415284B2 (en) * 2004-09-02 2008-08-19 Sonim Technologies, Inc. Methods of transmitting a message to a message server in a push-to-talk network
US20060046758A1 (en) * 2004-09-02 2006-03-02 Mohsen Emami-Nouri Methods of retrieving a message from a message server in a push-to-talk network
FI20050092A0 (fi) * 2004-09-08 2005-01-28 Nokia Corp Ryhmäpalveluiden ryhmätiedot
US7558286B2 (en) * 2004-10-22 2009-07-07 Sonim Technologies, Inc. Method of scheduling data and signaling packets for push-to-talk over cellular networks
KR101061373B1 (ko) * 2005-04-11 2011-09-02 삼성전자주식회사 푸쉬투토크 오버 셀룰러 망의 미디어 저장 서비스 수행 방법과 ＰｏＣ 서버 및 ＰｏＣ 클라이언트
ZA200708898B (en) * 2005-04-26 2009-03-25 Ericsson Telefon Ab L M A method and arrangement for providing context information
EP1905256B1 (en) * 2005-07-15 2013-05-15 Research In Motion Limited Methods and apparatus for providing ptt data buffering support indications from mobile devices and ptt data buffering control by wireless networks
CN101223755B (zh) * 2005-07-19 2014-11-05 艾利森电话股份有限公司 在ims中分配应用服务器的方法和装置
CN100488176C (zh) * 2005-08-09 2009-05-13 华为技术有限公司 即时消息系统间的搜索方法
WO2007028122A2 (en) * 2005-09-02 2007-03-08 Nortel Networks Limited Sip header reduction
DE102005049077B4 (de) * 2005-10-13 2009-02-12 Infineon Technologies Ag Verfahren zum Übertragen von Mediendaten, Kommunikationsnetzwerk-Einheit und Computerprogrammelement
US7664742B2 (en) * 2005-11-14 2010-02-16 Pettovello Primo M Index data structure for a peer-to-peer network
KR101232434B1 (ko) * 2005-11-15 2013-02-13 삼성전자주식회사 ＰｏＣ 시스템에서 동시 다중 세션 ＰｏＣ 멀티미디어서비스 제공 방법과 단말기 및 그 시스템
US20070118660A1 (en) * 2005-11-24 2007-05-24 Nokia Corporation Recording session contents in a network
BRPI0520719B1 (pt) * 2005-12-16 2018-02-14 Telefonaktiebolaget Lm Ericsson Publ “método e aparelho de rede para fornecer uma função de servidor de gerenciador de documento de xml para um cliente de gerenciador de documento de xml, e, entidade de rede para fornecer pelo menos parte de uma função de servidor de gerenciador de documento de xml para um cliente de gerenciador de documento de xml”
US7743985B2 (en) * 2005-12-29 2010-06-29 Motorola, Inc. Method and apparatus for an up-to-date transportation notification system
US20070255714A1 (en) * 2006-05-01 2007-11-01 Nokia Corporation XML document permission control with delegation and multiple user identifications
KR100823289B1 (ko) * 2006-08-28 2008-04-17 한국과학기술정보연구원 유알아이 기반 성과 정보 관리 시스템 및 그 방법
WO2008034450A1 (en) * 2006-09-19 2008-03-27 Telecom Italia S.P.A. Remote monitoring of phone calls
US7702644B2 (en) * 2007-01-25 2010-04-20 Ludi Labs, Inc. Data management system and method to host applications and manage storage, finding and retrieval of typed items with support for tagging, connections, and situated queries
US7864716B1 (en) * 2007-02-15 2011-01-04 Nextel Communications Inc. Talk group management architecture

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1296251A1 (en) * 2001-09-19 2003-03-26 Kreter, Martin Document creation system
US20040019630A1 (en) * 2002-07-24 2004-01-29 International Business Machines Corporation Method and apparatus for processing workflow through a gateway
US20050138132A1 (en) * 2003-12-22 2005-06-23 International Business Machines Corporation Method and system for instant messaging bots specification using state transition methodology and XML
CN1794692A (zh) * 2005-11-25 2006-06-28 华为技术有限公司 通信系统和在通信系统中查询信息的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2045725A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010026023A1 (de) * 2008-09-02 2010-03-11 Infineon Technologies Ag Verfahren zur ermittlung aktiver kommunikationssitzungen, kommunikationssitzungs-informationsserver, verfahren zum bereitstellen einer information über aktive kommunikationssitzungen und dokumentenmanagement-server
US9356791B2 (en) 2008-09-02 2016-05-31 Intel Deutschland Gmbh Method for determining active communication sessions, communication session information servers, method for providing information about active communication sessions and document management servers

Also Published As

Publication number Publication date
EP2045725A1 (en) 2009-04-08
US20090125803A1 (en) 2009-05-14
CN101170540A (zh) 2008-04-30
EP2045725A4 (en) 2009-08-19

Similar Documents

Publication Publication Date Title
US8250102B2 (en) Remote storage and management of binary object data
US8965958B2 (en) File fetch from a remote client device
US8051186B2 (en) Method for device capability negotiation, method, system and device for synchronization
WO2002079921A2 (en) Messaging infrastructure for identity-centric data access
US20200311028A1 (en) Recent file synchronization and aggregation methods and systems
JPH10312350A (ja) リソース命名方法及び機構
US20060248181A1 (en) Formatted and/or tunable QOS data publication, subscription, and/or distribution servers and clients
CN104580085A (zh) 业务数据更新方法、系统、客户端及服务器
WO2011029025A1 (en) Methods and apparatus to subscribe for change notifications in a document management system
CN101557409A (zh) 一种地址簿信息融合管理的方法及装置
EP2224661A1 (en) A method, system and apparatus of affair control
EP2045725A1 (en) Method and system, client, server of managing xml document
EP2275944B1 (en) Method and apparatus for managing binding information about a bundle installed remotely in an osgi service platform
US20120179959A1 (en) Method and arrangements for enabling modifications of xml documents
JP2009151560A (ja) リソースの管理方法、情報処理システム、情報処理装置、及びプログラム
CA2768805A1 (en) Methods and apparatus to use a network repository as a proxy to exchange converged address book service requests and responses
CN101296201A (zh) 网络信息共享方法、系统及即时通信装置
EP2764675A1 (en) System for contact subscription invitations in a cross-domain converged address book system
KR20170125665A (ko) M2M/IoT 플랫폼에서의 시맨틱 정보 관리 방법
TW200538950A (en) Defining nodes in device management system
CN114202297A (zh) 业务集成系统及方法
JP2007156546A (ja) コンテンツリスト提供装置およびコンテンツリスト提供方法
JP3845070B2 (ja) エレメント管理システム、エレメント管理方法及びエレメント管理プログラム
CN102812690B (zh) 获取数据类型定义的方法和装置
CN101771731B (zh) 获取网络地址本的方法和实现网络地址本的装置

Legal Events

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

Ref document number: 07764203

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2007764203

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE