CN101800657B - Combined address book system and relation view management method thereof - Google Patents

Abstract

The invention discloses a relation view management method in a combined address book system thereof, comprising: a relation view management extensible markup language document management server XDMS which operates and manages the relation view is arranged in a combined address book CAB system; a CAB user initiates an operation request to the relation view by a CAB client side; the CAB client sidesends the operation request to the relation view management XDMS; after performing the corresponding operation, the relation view management XDMS feeds back an operation result to the CAB client side. The invention also discloses a combined address book system. The invention can satisfy the management requirements on relation view of CAB and can conveniently and flexibly operate and manage the relation view.

Description

Converged address book system and contact view management method thereof

Technical Field

The invention relates to a converged address book technology, in particular to a converged address book system and a contact view management method thereof.

Background

With the evolution of telecommunication networks towards Internet Protocol (IP) networks, various flexible new services for communication have emerged, such as: peer-to-peer communication and group communication, etc. Generally, each service requires an address book for support, which causes a user to be inconvenienced by handling multiple address books on multiple terminals at the same time. Furthermore, since each terminal stores data independently, when a certain terminal is lost or malfunctions, the lost address book information is difficult to recover. In order to meet the requirements of new communication environments and new services and improve user experience, a Converged Address Book (CAB) system is developed.

The CAB system provides such a mechanism: it is possible to allow a user to conveniently manage address book information on a local terminal and also to allow a user to conveniently manage address book information stored on a network. The core of the CAB system is a network-side address book information storage that not only allows users to conveniently access and manage it, but also maintains synchronization with data updates on various terminals at all times. Also, when the address book information stored on the network side changes, the CAB system is also required to synchronize the changed data to the respective terminals of the users at the same time.

The CAB system also provides a user-to-Personal Contact Card (PCC) management mechanism, and the user can store all the contact items of the user in the PCC on the network. Also, the user may provide some subset of his PCC to others for use by defining a contact view. Through a subscription/notification mechanism, when the PCC data of a user is changed, the subscription user can obtain the update notification of the data in time, and the problem of the failure of the original data is effectively solved.

In the CAB system, a search, sharing and subscription function of an authorized user to CAB/PCC data within or between operator network domains is also provided, as well as an interworking function with a conventional address book system such as vCard, other systems.

In the prior art, PCC, contact view and other information in CAB system are stored in the form of XML document on the network side, and it is required that these information can be located, accessed and managed, for example: create, change, delete, etc., the Open Mobile Alliance (OMA) organization determined to use an extensible markup language Document Management Server (XDMS, XML Document Management Server) to manage these XML documents. The XML Document Management (XDM) architecture document [ AD-XDM ] describes the architecture and characteristics of an OMA XDM Enabler (Enabler), while the XDM Core specification [ XDM Core ] defines a common protocol that authorizes users to access and manage these documents.

Among other things, XDM Enabler defines a generic mechanism that enables service Enabler to access user-specific service-related information. The XDM Enabler architecture mainly comprises: an XDM Client (Client), a Shared XDMs (Shared XDMs), a Search Proxy (Search Proxy), an aggregation Proxy (aggregation Proxy), a Subscription Proxy (Subscription Proxy), a Network interworking Proxy (Cross-Network Proxy), etc., wherein the Shared XDMs further includes a Shared Group (Shared Group) XDMs, a Shared Policy (Shared Policy) XDMs, a Shared List (Shared List) XDMs, and a Shared summary (Shared profile) XDMs.

The XDM core specification specifies how service-related information is defined in well-structured XML documents, and the general protocols for accessing and managing these XML documents. The XDM Core specification [ XDM Core ] defines various characteristics of XDM Enabler, including specifically:

● XML Configuration and Access Protocol (XCAP): the specification reuses the XCAP protocol, by which participating Principals (principls) can store and manage service-related data stored on the network side in the form of XML documents using the methods of HTTP GET, PUT, and DELETE;

● SIP subscribe/notify mechanism: the specification reuses the SIP event package mechanism defined by IETF, through which the body can be notified of these file changes;

● search mechanism: through the mechanism body, the HTTP POST method can be used, and limited XQuery expressions are adopted to search service related data stored on the network side in the form of XML documents.

Wherein documents accessed and managed by XCAP are stored in logical repositories, called XDMS, on the network side, each associated with a functional entity implementing the respective function. Each document stored in the XDMS is described as an XCAP Application method (Application Usage), by which an Application can use the document through XCAP. XDM Enabler describes an application method that can be reused by multiple enablers and stored in a shared XDMs, including four types, respectively: shared list XDMS, shared group XDMS, shared policy XDMS, and shared summary XDMS. The document types supported by these XDMSs are: URI list and group method list documents in shared list XDMS; sharing group documents in a group XDMS; sharing a user access policy document in a policy XDMS; user profile in shared profile XDMS. In addition to the above documents, XDM Enabler also defines extended multicast documents.

Currently, the OMA organization is making the CAB V1.0 specification, and in the requirements definition of CAB, there are the following requirements for the contact view:

(ii) allowing CAB users to manage contact views of their personal contact cards and select the domain associated with each contact view; wherein, the management includes but is not limited to creating, deleting, modifying, naming;

allowing CAB users to link certain specific information in their personal contact cards into multiple contact views;

allowing CAB user to select contact view to provide for user requesting PCC information;

allowing the service provider to provide a series of contact views, wherein each contact view has a default group of domains associated with the contact view according to the use strategy of the service provider for the contact views, and is used for realizing the personalized needs of each CAB user;

generating contact information to be distributed to other users, wherein the generated information only comprises information in a personal contact card related to the contact view requested by the user;

sixthly, the conventional data format of the CAB system can be used for providing the personal contact card information defined in the contact view for the request;

the CAB user may set a display name for each contact view.

The above points are requirements on the contact view given in the CAB specification, but no specific implementation scheme has been proposed in the prior art specifically how to implement management on the contact view.

Disclosure of Invention

In view of the above, the main objective of the present invention is to provide a converged address book system and a contact view management method thereof, which can meet the requirement of CAB on management of contact views.

In order to achieve the purpose, the technical scheme of the invention is realized as follows:

the invention provides a contact view management method in a converged address book system, which comprises the following steps:

setting a contact view management extensible markup language document management server XDMS for operating and managing a contact view in a fusion address book CAB system;

the CAB user initiates an operation request for the contact view through the CAB client, and the CAB client sends the operation request to the contact view management XDMS; and after the XDMS executes corresponding operation, feeding back an operation result to the CAB client.

Wherein, the sending, by the CAB client, the operation request to the contact view management XDMS is: the CAB client directly sends the operation request to the contact view management XDMS or sends the operation request to the contact view management XDMS through the CAB server; correspondingly, the step of feeding back the operation result to the CAB client by the contact view management XDMS is: and the XDMS directly feeds back the operation result to the CAB client or feeds back the operation result to the CAB client through the CAB server.

Before the CAB client sends the operation request to the CAB server or the contact view management XDMS, the method further includes: the CAB client performs bidirectional authentication with a CAB server or a contact view management XDMS.

In the above scheme, the operation request is to query, create, add, update, modify, or delete the contact view. The operation authority of the user is set according to the operator strategy.

The method further comprises a using process of the contact view, which specifically comprises the following steps: the method comprises the steps that a personal contact card XDMS acquires user preference and user strategy information, and acquires a required contact view from a contact view management XDMS; and then combining the user preference and the user policy information with the view obtained from the contact view management XDMS according to a preset corresponding rule, and applying and operating the contact view.

Wherein the corresponding rule is set according to operator policy, or according to user preference setting information, or according to a filtering rule, or according to sensitive information.

The invention also provides a system for fusing the address book, which comprises a CAB client and an extensible markup language document management (XDM) server, wherein the CAB client is connected with the XDM server; the XDM server comprises a contact view management XDMS; wherein,

the CAB client is used for sending an operation request initiated by a CAB user to the contact view management XDMS;

a contact view management XDMS for managing a contact view; and receiving an operation request sent by the CAB client, and returning an operation result to the CAB client after executing corresponding operation.

Wherein the CAB client directly sends the operation request to a contact view management XDMS; correspondingly, the XDMS directly feeds back the operation result to the CAB client;

or, the system further comprises a CAB server for forwarding the operation request sent by the CAB client to the contact view management XDMS and forwarding the operation result fed back by the contact view management XDMS to the CAB client.

In the above scheme, the XDM server further comprises a personal contact card XDMs interconnected with the contact view management XDMs; the personal contact card XDMS is used for storing all contact items of the user and realizing the operation and the use of the contact information of the user.

In the above scheme, the CAB client includes part or all of an XDM client, a DS client, and a WEB client;

the XDM server comprises a CAB XDMS server, an OMA shared XDMS server, PCCXDMS, a CAB user preference setting XDMS, a CAB user strategy XDMS and part or all of a contact view management XDMS;

the contact view management XDMS is a component of any one network element or equipment in a CAB XDM server, a shared XDMS server, OMAXDM and an XDM enabler; or as a stand-alone XDM server.

The fusion address book system and the contact view management method thereof provided by the invention have the advantages that the contact view management XDMS is added in the CAB system architecture, the contact view information defined by each CAB user can be stored through the contact view management XDMS, the mapping relation between the personal contact card of the user and each contact view is established and maintained, the operation of inquiring, creating, adding, updating, modifying, deleting and the like on the contact view by an authorized CAB user is supported, and the fusion address book system and the contact view management method thereof can be applied to scenes such as contact view display, contact subscription, contact sharing, contact searching and the like of the personal contact card. Therefore, the management requirement of CAB on the contact view can be met, and the universality is strong.

In the invention, the CAB user can send the operation request for the contact view initiated by the CAB client to the contact view management XDMS directly or through the CAB server, and after the contact view management XDMS executes corresponding operation, the operation result is fed back to the CAB client directly or through the CAB server. Therefore, the CAB user can operate the contact view conveniently and flexibly; the integrated address book system is convenient to manage the contact view.

Drawings

FIG. 1 is a schematic diagram of a converged address book system according to the present invention;

FIG. 2 is a schematic flow chart of a method for managing contact views according to the present invention;

FIG. 3 is a schematic diagram of a flow chart of another method for managing contact views according to the present invention;

fig. 4 is a schematic flow chart illustrating an implementation of a contact view using method according to the present invention.

Detailed Description

The basic idea of the invention is: setting a special contact view management XDMS for operating and managing a contact view in a converged address book system, sending an operation request for the contact view, initiated by a CAB client, to the contact view management XDMS by a CAB user directly or through a CAB server, and feeding back an operation result to the CAB client directly or through the CAB server after the contact view management XDMS executes corresponding operation. Therefore, the contact view can be conveniently and flexibly operated and managed.

Fig. 1 shows a converged address book system proposed by the present invention, and as shown in fig. 1, the converged address book system 10 includes a CAB client 11, an XDM server 13; the CAB client 11 is connected with the XDM server 13; the XDM server 13 further comprises a personal contact card XDMs 131 and a contact view management XDMs 132, wherein the personal contact card XDMs 131 is interconnected with the contact view management XDMs 132. The converged address book system 10 further includes a CAB server 12, the CAB client 11 being connected to the CAB server 12; in particular, the method comprises the following steps of,

a CAB client 11 for sending an operation request for the contact view, which is initiated by a CAB user, to the CAB server 12 or the contact view management XDMS 132; the system is also used for carrying out bidirectional authentication with the CAB server 12 or the XDMS 132 for contact view management and establishing communication connection;

the CAB client 11 may include part or all of an XDM client, a DS client, a WEB client, and the like.

The CAB server 12 is configured to forward the operation request sent by the CAB client 11 to the contact view management XDMS 132, and forward the operation result fed back by the contact view management XDMS 132 to the CAB client 11;

the CAB server 12 may contain some or all of a subscription agent, an aggregation agent, a search agent, a network interworking agent, a DS server, a sharing server, an XDM client, and the like.

An XDM server 13 for storing user-specific service-related information on the network, which can be located, accessed and managed, the information being defined in XML documents;

the XDM server 13 may include some or all of a CAB XDMs server, an OMA shared XDMs server, a PCC XDMs, a CAB user preference setting XDMs, a CAB user policy XDMs, a contact view management XDMs, and the like.

A personal contact card XDMS 131 for storing all contact items of the user and supporting the management and operation of PCC; and also for acquiring a contact view from the contact view management XDMS 132, applying the contact view.

A contact view management XDMS 132 for managing a contact view; receiving an operation request sent by the CAB client, and returning an operation result to the CAB client directly or through the CAB server after executing corresponding operation; but also to provide the required contact view to the personal contact card XDMS 131.

The contact view management XDMS is extended based on a sharing summary XDMS and can be a CABAC DM server, a sharing XDMS server, OMAXDM and an XDM Enable, wherein the shared summary XDMS is any network element or equipment part; or may be a separate XDM server.

The contact view management XDMS may work with other network elements or devices in the converged address book system, including but not limited to: a CAB client, a CAB terminal, a CAB server, an XDM server, a CAB XDMs server, an OMA shared XDMs server, a PCCXDMS, a CAB user preference setting XDMs, a CAB user policy XDMs, a subscription agent, an aggregation agent, a search agent, a network interworking agent, an XDM client, a DS server, a DS client, a shared server, a WEB client, etc.

The CAB terminal may include a CAB client, an XDM client, a DS client, a WEB client, or some or all of them.

The invention can store the contact view information defined by each CAB user through the contact view management XDMS, and can realize the operations of inquiring, creating, adding, updating, modifying, deleting and the like of the contact view by an authorized CAB user through establishing and maintaining the mapping relation between the personal contact card of the user and each contact view, such as establishing a mapping table. For example, after an authorized CAB user initiates an operation request for a contact view through a CAB client, for example: and deleting the contact view, sending the operation request to the contact view management XDMS by the CAB client directly or through a CAB server, finding the corresponding contact view in the established mapping table by the contact view management XDMS according to CAB user information carried in the request, deleting the found contact view, and then successfully deleting the contact view and returning the deleted contact view to the CAB client.

The method and the device can be applied to scenes such as contact view display, contact subscription, contact sharing, contact searching and the like of the personal contact card.

The functions that the contact view management XDMS of the present invention can implement also include: and establishing and maintaining a mapping relation between a user personal contact card and each contact view, wherein the PCC XDMS acquires the user view and can be realized through an XDM-4XCAP interface between the PCCXDMS and the contact view management XDMS.

The functions that the contact view management XDMS of the present invention can implement also include: when the PCC XDMS needs to obtain the user preference and the strategy information of CAB user preference setting XDMS and CAB user strategy XDMS, the user preference and the strategy information can be realized through interfaces of XDM-4XCAP, XDM-3XCAP and the like; the PCC is combined and applied to scenes such as contact view showing, contact subscribing, contact sharing, contact searching and the like according to user preference and strategy information and a contact view obtained from a contact view management XDMS.

The functions that the contact view management XDMS of the present invention can implement also include: when the method is applied to a contact view display scene of PCC, the XDMS is managed through the contact view, and CAB users can select different contact views to display;

further, the functions that can be implemented by the contact view management XDMS of the present invention further include: when the method is applied to a PCC contact subscription scene, CAB users can keep timely updating of opposite side information in a PCC subscription mode. When the contact information of the contact subscribed by the CAB user changes, the fused address book of the CAB user can be automatically updated correspondingly. By managing XDMS through the contact view, CAB users can formulate different contact views of PCC to other users, and when other users subscribe PCC information, partial personal information is provided instead of all PCC information, so that user privacy can be better protected; the PCC may also generate a subscription relationship based on user preferences and policy information, as well as the contact view from the contact view management XDMS.

Further, the functions that can be implemented by the contact view management XDMS of the present invention further include: when the CAB user sharing method is applied to a PCC (policy and charging management system) contact sharing scene, CAB users can share own contacts or PCC through a CAB system, and the CAB users or non-CAB users can receive and share the contacts or the PCC; the address book may or may not be the merged address book of the sharer. By contacting view management XDMS, CAB users can select different views to share to the receiving sharer according to different categories of the receiving sharer; the PCC may also generate shared data based on user preferences and policy information, and the contact view obtained from the contact view management XDMS.

Further, the functions that can be implemented by the contact view management XDMS of the present invention further include: when the method is applied to scenes such as contact search of PCC (policy and charging management), XDMS (enhanced data management system) is managed through a contact view, a CAB user can set a special contact view for search, wherein the special contact view contains less personal information which can be disclosed, and when other users search the PCC of the CAB user, the CAB system only provides the PCC information corresponding to the special contact view; the PCC may also search for data based on user preferences and policy information, as well as the contact view obtained from the contact view management XDMS.

Further, the functions that can be implemented by the contact view management XDMS of the present invention further include: the operation of the CAB user on the contact view XML document specifically comprises inquiry, creation, addition, update, modification, deletion and the like, and can be realized through methods and interfaces of XDM-3XCAP, XDM-4XCAP, OMA DS SyncML, HTTP, HTTPS and the like, singly or in combination. For example: the CAB client can access the XDMS by the XDM-3 XCAP; the CAB user can access a DS server in the CAB server through the DS client in the CAB client by adopting SyncML; the CAB server accessing the contact view management XDMS can adopt XDM-3 XCAP; the CAB client may also access the contact view management XDMs through an aggregation proxy based on a combination of XDM-3XCAP and XDM-4 XCAP.

Further, the functions that can be implemented by the contact view management XDMS of the present invention further include: and the CAB user operates the XML document of the contact view, and the operation authority of the CAB user can be set according to the strategy of an operator. The CAB user's operation authority for the contact view file includes but is not limited to reading, writing, controlling, etc., such as setting up default contact view provided by the operator not to allow modification and deletion.

Based on the converged address book system shown in fig. 1, the present invention can adopt two contact view management methods: one is that the CAB client sends an operation request to the contact view management XDMS via the CAB server, and the contact view management XDMS performs the corresponding operation; the other is that the CAB client directly sends an operation request to the contact view management XDMS, and the contact view management XDMS performs a corresponding operation.

Specifically, the first contact view management method includes the steps of:

step A1: establishing bidirectional authentication between the CAB client and the CAB server;

here, the bidirectional authentication includes a complete authentication process, and a general authentication process may be adopted, such as: the CAB client sends an authentication request carrying self authentication information to the CAB server; after receiving the information, the CAB server authenticates the corresponding information of the CAB client; after the authentication is passed, the CAB server returns an authentication success message to the CAB and sends the authentication information of the CAB server; and after receiving the information, the CAB client authenticates the corresponding information of the CAB server, and after passing the authentication, returns an authentication passing message to the CAB.

The CAB client and the CAB server establish bidirectional authentication, and the authentication can be completed in the modes of IKEv2, IPSec, HTTP digest, Generic Authentication Architecture (GAA), early IMS authentication, Transport Layer Security (TLS) and the like.

Step B1: the CAB client sends the operation requirement on the contact view management XDMS to the CAB server, and the CAB server sends the operation requirement on the contact view management XDMS to the contact view management XDMS;

step C1: and the contact view management XDMS executes corresponding operation after receiving the message.

Step D1: and the contact view management XDMS returns the operation result to the CAB server, and the CAB server returns the operation result to the CAB client.

The second contact view management method includes the steps of:

step A2: establishing bidirectional authentication between the CAB client and the contact view management XDMS;

here, the bidirectional authentication includes a complete authentication process, and a general authentication process may be used.

The CAB client establishes bidirectional authentication with the contact view management XDMS, and the authentication can be completed in the modes of IKEv2, IPSec, HTTP digest, general authentication architecture, early IMS authentication, transport layer security and the like.

Step B2: the CAB client transmits an operation requirement for the contact view management XDMS to the contact view management XDMS.

Step C2: and the contact view management XDMS executes corresponding operation after receiving the message.

Step D2: and the contact view management XDMS returns the operation result to the CAB client.

The present invention can further use and operate the contact view with respect to the contact view managed in the contact view management XDMS. Such as: the personal contact card XDMS can combine the user preference and the strategy information and the contact view obtained from the contact view management XDMS according to a preset rule, and is applied to the scenes of contact view display, contact subscription, contact sharing, contact searching and the like of a converged address book.

The following describes the implementation of the technical solution of the present invention in further detail with reference to the accompanying drawings and specific embodiments.

The contact view management XDMS described in the following embodiments is disposed in an XDM server, and thus, specific implementations relate to functional entities such as a CAB client, a CAB server, and an XDM server, and corresponding interfaces thereof. Without loss of generality, the following embodiments use the XCAP protocol as a protocol interface between the CAB client, CAB server, and XDM server.

The first embodiment is as follows:

in this embodiment, the CAB user needs to modify and delete the contact view data of the CAB user, and the CAB client sends an operation requirement to the contact view management XDMS via the CAB server. The contact view management method of this embodiment is shown in fig. 2, and specifically includes:

step 201: establishing bidirectional authentication between the CAB client and the CAB server;

wherein the bidirectional authentication comprises a complete authentication procedure.

Step 202: the CAB user initiates a request for acquiring the contact view data to the CAB server through the CAB client and requires to acquire the contact view data of the CAB user;

step 203: the CAB server initiates a request for acquiring contact view data to the contact view management XDMS, and requires to acquire the contact view data of the current user;

step 204: the XDMS finds out the contact view data of the user initiating the request through inquiry and returns the found contact view data to the CAB server;

step 205: the CAB server returns the contact view data of the user who initiates the request to the CAB client;

step 206: the CAB user modifies the contact view data of the CAB user through the CAB client on the CAB client;

step 207: the CAB user initiates a request for writing in the contact view data to the CAB server through the CAB client and requires to write in the modified contact view data; wherein, the request carries the contact view data modified by the user who initiates the request CAB;

step 208: the CAB server initiates a request for writing contact view data to the contact view management XDMS, and requests to write the contact view data modified by the current user; wherein, the request carries the contact view data modified by the user who initiates the request CAB;

step 209: after receiving the request, the XDMS modifies the corresponding contact view of the initiating request user;

step 210: the CAB user initiates a request for deleting the contact view to the CAB server through the CAB client and requires to delete part of the contact view of the CAB user;

step 211: the CAB server initiates a request for deleting the contact view to the contact view management XDMS, and requires to delete part of the contact view of a user initiating the request;

step 212: after receiving the information, the contact view management XDMS finds and deletes the corresponding contact view of the user.

Example two:

in this embodiment, the CAB user needs to modify and delete the contact view data of the CAB user, and the CAB client directly sends the operation requirement to the contact view management XDMS. The contact view management method of this embodiment is shown in fig. 3, and specifically includes:

step 301: establishing bidirectional authentication between the CAB client and the contact view management XDMS;

wherein the bidirectional authentication comprises a complete authentication procedure.

Step 302: a CAB user initiates a request for acquiring contact view data to a contact view management XDMS through a CAB client, and requires to acquire the contact view data of the CAB user;

step 303: the XDMS finds out the contact view data of the user initiating the request through inquiry, and returns the found contact view data to the CAB client;

step 304: the CAB user modifies the contact view data of the CAB user through the CAB client on the CAB client;

step 305: a CAB user initiates a request for writing contact view data to a contact view management XDMS through a CAB client, and requests to write the modified contact view data; wherein, the request carries the contact view data modified by the user who initiates the request CAB;

step 306: after receiving the request, the XDMS modifies the corresponding contact view of the initiating request user;

step 307: a CAB user initiates a request for deleting a contact view to a contact view management XDMS through a CAB client, and requires to delete part of the contact view of the CAB user;

step 308: after receiving the information, the contact view management XDMS finds and deletes the corresponding contact view of the user.

Example three:

in this embodiment, a method for using a contact view is provided, where when a CAB user subscribes, shares, or searches data of a personal contact card, a process of using the contact view is shown in fig. 4, and specifically includes:

step 401: the PCC XDMS acquires user strategies and preference data from the user strategy XDMS and the user preference XDMS;

here, the user policy XDMS and the user preference XDMS are both located in an XDM server;

step 402: the PCC XDMS acquires a contact view of a corresponding user through the contact view management XDMS;

step 403: and the PCC XDMS combines the user preference and the user strategy information with the contact view obtained from the contact view management XDMS according to the preset corresponding rule, and applies and operates the contact view.

Here, the application includes presenting a contact view, or generating a subscription relationship, or generating shared data, or searching data, and may be respectively used in a scenario of presenting a contact view, subscribing to a contact, sharing a contact, and searching a contact in a converged address book.

In this embodiment, the corresponding rule may be set according to an operator policy, for example: setting the size, the number, the category and the like of the contact view files, and limiting the space of the contact view;

the corresponding rule may also be set according to user preference setting information, for example: setting different contact views such as contact views of shopping, sports and the like according to user preferences;

the corresponding rule may also be set according to a filtering rule, for example: different rule conditions can be set to set different contact views; different contact views can be set according to different contacts (such as family, colleagues, classmates, friends, social relations and blacklists), or partial contents can be provided, or the contact views can be refused to be provided;

the corresponding rule may also be set according to sensitive information, for example: sensitive attributes may include, but are not limited to, keep-prohibited, forward-prohibited, etc., such as: limiting the number of readings, etc.

The invention is suitable for any mobile terminal, wired terminal or WEB client. The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.

Claims (6)

1. A method for contact view management in a converged address book system, the method comprising:

setting a contact view management extensible markup language document management server XDMS for operating and managing a contact view in a fusion address book CAB system;

the CAB user initiates an operation request for the contact view through the CAB client, and the CAB client sends the operation request to the contact view management XDMS; after the XDMS executes corresponding operation, feeding back an operation result to the CAB client;

the CAB client sends an operation request to the contact view management XDMS: the CAB client directly sends the operation request to the contact view management XDMS or sends the operation request to the contact view management XDMS through the CAB server;

correspondingly, the step of feeding back the operation result to the CAB client by the contact view management XDMS is: the XDMS directly feeds back the operation result to the CAB client side or feeds back the operation result to the CAB client side through a CAB server;

before the CAB client sends the operation request to the CAB server or the contact view management XDMS, the method further includes: the CAB client performs bidirectional authentication with a CAB server or a contact view management XDMS;

the method further comprises a using process of the contact view, which specifically comprises the following steps:

the method comprises the steps that a personal contact card XDMS acquires user preference and user strategy information, and acquires a required contact view from a contact view management XDMS;

and then combining the user preference and the user policy information with the view obtained from the contact view management XDMS according to a preset corresponding rule, and applying and operating the contact view.

2. The contact view management method according to claim 1, wherein the operation request is to query, create, add, update, modify, or delete a contact view.

3. The contact view management method according to claim 2, wherein the operation authority of the user is set according to an operator policy.

4. The contact view management method of claim 1, wherein the corresponding rule is set according to an operator policy, or according to user preference setting information, or according to a filtering rule, or according to sensitive information.

5. A kind of system of integrated address book, including CAB customer end, extensible markup language document management XDM server, CAB customer end couples to XDM server; the method is characterized in that the XDM server comprises a contact view management XDMS; wherein,

the CAB client is used for sending an operation request initiated by a CAB user to the contact view management XDMS; and is also used for performing bidirectional authentication with the contact view management XDMS;

a contact view management XDMS for managing a contact view; receiving an operation request sent by the CAB client, and returning an operation result to the CAB client after executing corresponding operation; the CAB client is also used for bidirectional authentication with the CAB client;

the CAB client directly sends the operation request to a contact view management XDMS; correspondingly, the XDMS directly feeds back the operation result to the CAB client;

or, the system further comprises a CAB server, configured to forward an operation request sent by the CAB client to the contact view management XDMS, and forward an operation result fed back by the contact view management XDMS to the CAB client; the CAB client is also used for bidirectional authentication with the CAB client;

correspondingly, the CAB client is also used for carrying out bidirectional authentication with the CAB server;

the XDM server further comprises a personal contact card XDMS interconnected with the contact view management XDMS; the personal contact card XDMS is used for storing all contact items of the user and realizing the operation and the use of the contact information of the user.

6. The converged address book system of claim 5, wherein the CAB client includes some or all of an XDM client, a DS client, a WEB client;

the XDM server comprises a CAB XDMS server, an OMA shared XDMS server, PCCXDMS, a CAB user preference setting XDMS, a CAB user strategy XDMS and part or all of a contact view management XDMS;

the contact view management XDMS is a component of any one network element or equipment in a CAB XDM server, a shared XDMS server, OMAXDM and an XDM enabler; or as a stand-alone XDM server.

Images