CN102075644B - Implementation method and system for contact view in compressed address book - Google Patents

Implementation method and system for contact view in compressed address book Download PDF

Info

Publication number
CN102075644B
CN102075644B CN200910238234.9A CN200910238234A CN102075644B CN 102075644 B CN102075644 B CN 102075644B CN 200910238234 A CN200910238234 A CN 200910238234A CN 102075644 B CN102075644 B CN 102075644B
Authority
CN
China
Prior art keywords
cab
contact
xdms
pcc
view
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.)
Expired - Fee Related
Application number
CN200910238234.9A
Other languages
Chinese (zh)
Other versions
CN102075644A (en
Inventor
黄光平
糜正琨
徐名海
张鲁宁
彭荣群
邵伟翔
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN200910238234.9A priority Critical patent/CN102075644B/en
Publication of CN102075644A publication Critical patent/CN102075644A/en
Application granted granted Critical
Publication of CN102075644B publication Critical patent/CN102075644B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Information Transfer Between Computers (AREA)

Abstract

The invention discloses an implementation method for a contact view in a compressed address book, comprising the following steps of: representing a contact item in a PCC (Personal Contact Card) with an XML (Extensible Markup Language); setting an attribute value for the contact item; marking visual angle information of the contact item in the contact view and preference information of the contact item and information of strategy of the contact item; selecting a contact item from the PCC by the contact item in the contact view; sending an operation request of the contact view by a user to a CAB (Compressed Address Book) User Preference XDMS (Xml Data Management Server); acting on an XML document of the contact item in the PCC by the CAB User Preference XDMS according to the visual angle information, and/or the preference information of the contact item and/or the information of the strategy of the contact item to obtain the contact view of the operation request; and returning the contact view to the user. Meanwhile, the invention discloses an implementation system for the contact view in the compressed address book. The technical scheme disclosed by the invention is simple and practical.

Description

The implementation method of contact view and system in blend address book
Technical field
The present invention relates to the application technology of contact view in blend address book, relate in particular in a kind of IP network the implementation method of contact view and system in blend address book.
Background technology
Along with the evolution of communication network to complete IP network, there is the various new business of communicating by letter flexibly, as peer-to-peer communications is communicated by letter with colony etc.General each business all needs an address book to support, this just makes user face the problem of simultaneously processing a plurality of address books in a plurality of terminals.And because each terminal is to store independently data, when lost terminal or while breaking down, the address book information of loss will be difficult to recover.In order to improve user, experience, be necessary to develop a kind of address book system of fusion.
Blend address book (CAB, Converged Address Book) system provides a kind of like this mechanism, and it both can make user manage easily the address book information on local terminal, can make again the user's address book information of managed storage on network easily.The CAB system core is network side address book information memory.This memory not only will accomplish that user accesses easily and manages it, also to constantly keep and the synchronizeing of Data Update in various terminals, and when the address book information of network side storing changes, system also will be synchronized to the data that change each terminal of user simultaneously.
CAB system provides a kind of user the administrative mechanism to individual contact card (PCC, Personal Contact Card) simultaneously.User can be stored in all contact entry of oneself in the PCC on network.User can offer other people a subset of own PCC by the mode of definition contact view.By subscription/notifying mechanism, when the PCC data of oneself change, booking reader can obtain in time the renewal of data and notice, and has effectively solved the Problem of Failure of legacy data.
CAB system also provide authorized user to the search of CAB/PCC data between Nei Huo territory, territory, share and subscribe to function, and with the IWF of traditional address book system and other system.
Open Mobile Alliance (OMA, Open Mobile Alliance) is being formulated CAB V1.0 standard at present.In the requirement definition of CAB, for contact view Contact View, there is following requirement:
The territory that allows the contact view of its people's contact card of CAB user management (establishment, deletion, modification, name) and select to be associated with each contact view;
Allow CAB user that some specifying information in its people's contact card is linked in a plurality of contact views;
Allow CAB user to select view to offer the user of its PCC information of request.
Allow service provider that a series of contact views are provided, according to service provider's strategy, each view has one group of territory of the acquiescence being associated with it to be used for realizing each CAB user's personal needs.
Can generic connection information distribution give other users, these information only include the information in the individual contact card relevant to the contact view of user's request.
Can be with the data format of CAB system convention for asking to provide the individual contact card information defining in contact view.
CAB user arranges display name can to each contact view.
Although formulated relevant CAB V1.0 standard, because CAB technology is still in development, do not had relevant CAB application technology scheme at present.
Summary of the invention
In view of this, main purpose of the present invention is to provide implementation method and the system of contact view in a kind of blend address book, has facilitated user to the management of contact details in blend address book and has obtained.
For achieving the above object, technical scheme of the present invention is achieved in that
The implementation method of contact view in a kind of blend address book, contact entry in individual contact card PCC is represented with extending mark language XML, for described contact entry sets property, indicate the visual angle information of described contact entry in contact view and the information that indicates described contact entry preference information, affiliated strategy; Contact entry in described contact view is chosen the contact entry from described PCC; Described method also comprises:
User is to blend address book user preference XML document management server (CAB User Preference XDMS, CAB User Preference XML Document Management Server) send the operation requests of contact view, described CAB User Preference XDMS is according to the visual angle information of the contact view in described operation requests, and/or the preference information to described contact entry, and/or the policy information to described contact entry, act on the XML document of the contact entry in described PCC, obtain the contact view of described operation requests, and return to described user.
Preferably, described operation requests comprises at least one item of following request: subscribe request, sharing request, searching request.
Preferably, when described operation requests is subscribe request, obtain the contact view of described operation requests, comprising:
XML document management engine (XDM Enabler, XML Document Management Enabler) assembly receives after the subscribe request of described booking reader or fuse address book server CAB Server initiation, described subscribe request is routed to blend address book individual contact card XML document management server (CAB PCC XDMS), by described CAB PCC XDMS, to CAB User Preference XDMS, forward described subscribe request; The XML document of described CAB User Preference XDMS contact entry in PCC by the subscription view acting rules in described subscribe request, according to the attribute of the contact entry in PCC described in described subscription view rules modification, and will revise described PCC after contact entry attribute as described contact view, the assembly by described CAB PCC XDMS, described XML document management engine sends to described booking reader;
Or, receiving after the subscribe request of described booking reader or CAB Server, the assembly of described XDM Enabler sends subscribe request to described CAB User Preference XDMS; Described CAB User Preference XDMS produces subscribe request according to the subscription view rule in described subscribe request, and send to CAB PCC XDMS, CAB PCC XDMS returns to subscription response to described CAB User Preference XDMS, and described CAB User Preference XDMS notifies described booking reader to subscribe to successfully.
Preferably, the assembly of described XDM Enabler also comprises before described subscribe request is routed to described CAB PCC XDMS or described CAB User Preference XDMS:
The assembly of described XDM Enabler is inquired about subscribed user's preference information and policy information, when not defining view or there is no default view in the subscription strategy grouping booking reader described subscribed user, the assembly inquiry of described XDM Enabler notifies described subscribed user to specify described booking reader's grouping information.
Preferably, described method also comprises:
Described booking reader, after contact view is subscribed to successfully, writes described subscribed user's preference information and policy information in the subscription list of self.
Preferably, when described operation requests is searching request, the contact view of the described operation requests of described acquisition, comprising:
The assembly of XDM Enabler receives after the searching request of described search subscriber initiation, and described searching request is routed to CAB PCC XDMS, by described CAB PCC XDMS, to CAB User Preference XDMS, forwards described searching request; Or, receiving after the searching request of described search subscriber, the assembly of described XDM Enabler routes to CAB User Preference XDMS by described searching request;
Described CAB User Preference XDMS obtains the contact view of the search special use that described searched user arranges, and the assembly by described CAB PCC XDMS, described XML document management engine sends to described search subscriber; What in the special-purpose contact view of described search, comprise that described searched user sets comprises less contact entry in self PCC.
Preferably, when described operation requests is sharing request, the contact view of the described operation requests of described acquisition, comprising:
The assembly of XDM Enabler receives after the sharing request of described sharing users initiation, and described sharing request is routed to CAB PCC XDMS, by described CAB PCC XDMS, to CAB User Preference XDMS, forwards described sharing request;
Described in described CAB User Preference XDMS obtains, be shared the shared contact view that user arranges, the assembly by described CAB PCC XDMS, described XML document management engine sends to described sharing users; The shared recipient of described shared contact view comprises blend address book user or non-blend address book user, the contact entry in described shared contact view chooses in the PCC of sharing users or contact addresses book (AB, Address Book) in.
The system that realizes of contact view in blend address book, comprising:
Setting unit, for the contact entry of individual contact card PCC is represented with extending mark language XML, for described contact entry sets property, indicate the visual angle information of described contact entry in contact view and the information that indicates described contact entry preference information, affiliated strategy; Wherein, the contact entry in described contact view is chosen the contact entry from described PCC;
The first transmitting element, is arranged in user's terminal or CAB Server, for send the operation requests of contact view to CAB User Preference XDMS;
Receiving element, is arranged in described CAB User Preference XDMS, for receiving described operation requests;
Acquiring unit, be arranged in described CAB User Preference XDMS, be used for according to the visual angle information of the contact view of described operation requests and/or to the preference information of described contact entry and/or the policy information to described contact entry, act on the XML document of the contact entry in described PCC, obtain the contact view of described operation requests;
The second transmitting element, is arranged in described CAB User Preference XDMS, returns to the user of described operation requests for the contact view that described acquiring unit is obtained.
Preferably, described operation requests comprises at least one item of following request: subscribe request, sharing request, searching request.
Preferably, when described operation requests is subscribe request, described acquiring unit obtains the contact view of described operation requests, comprising:
The assembly of XDM Enabler receives after the subscribe request of described the first transmitting element initiation, described subscribe request is routed to blend address book individual contact card XML document management server (CAB PCC XDMS), by described CAB PCC XDMS, to CAB User Preference XDMS, forward described subscribe request; The XML document of described CAB User Preference XDMS contact entry in PCC by the subscription view acting rules in described subscribe request, according to the attribute of the contact entry in PCC described in described subscription view rules modification, and will revise described PCC after contact entry attribute as described contact view, the assembly by described CAB PCC XDMS, described XML document management engine sends to described booking reader;
Or, receiving after the subscribe request of described the first transmitting element, the assembly of described XDM Enabler sends subscribe request to described CAB User Preference XDMS; Described CAB User Preference XDMS produces subscribe request according to the subscription view rule in described subscribe request, and send to CAB PCC XDMS, CAB PCC XDMS returns to subscription response to described CAB User Preference XDMS, and described CAB User Preference XDMS notifies described booking reader to subscribe to successfully.
Preferably, described system also comprises:
Query unit, for before the assembly of XDM Enabler routes to described subscribe request described CAB PCC XDMS or described CAB User Preference XDMS, inquire about subscribed user's preference information and policy information, when not defining view or there is no default view in the subscription strategy grouping booking reader described subscribed user, the assembly inquiry of described XDM Enabler notifies described subscribed user to specify described booking reader's grouping information.
Preferably, described system also comprises:
Writing unit, is arranged in user's terminal, for described booking reader after contact view is subscribed to successfully, described subscribed user's preference information and policy information are write in the subscription list of self.
Preferably, when described operation requests is searching request, the contact view of the described operation requests of described acquisition, comprising:
Described the first transmitting element sends to the assembly of XDM Enabler the searching request that described search subscriber is initiated, the assembly of described XDM Enabler routes to CAB PCC XDMS by described searching request, by described CAB PCC XDMS, to described CAB User Preference XDMS, forwards described searching request; Or the assembly of described XDM Enabler receives after the searching request of the search subscriber that described the first transmitting element sends, and described searching request is routed to CAB User Preference XDMS;
Described CAB User Preference XDMS obtains the contact view of the search special use that described searched user arranges, and the assembly by described CAB PCC XDMS, described XML document management engine sends to described search subscriber; What in the special-purpose contact view of described search, comprise that described searched user sets comprises less contact entry in self PCC.
Preferably, when described operation requests is sharing request, the contact view of the described operation requests of described acquisition, comprising:
Described the first transmitting element sends to the assembly of XDM Enabler the sharing request that described sharing users is initiated, the assembly of described XDM Enabler routes to CAB PCC XDMS by described sharing request, by described CAB PCC XDMS, to described CAB User Preference XDMS, forwards described sharing request;
Described in described CAB User Preference XDMS obtains, be shared the shared contact view that user arranges, the assembly by described CAB PCC XDMS, described XML document management engine sends to described sharing users; The shared recipient of described shared contact view comprises blend address book user or non-blend address book user, and the contact entry in described shared contact view is chosen in the PCC of sharing users or contact addresses book AB(Address Book) in.
Technical scheme of the present invention is the conditions of demand to contact view for CAB user, have protected better the safety of user profile, make user process more neatly the personal information of oneself, thereby meet better the demand of CAB.
Accompanying drawing explanation
Fig. 1 is that CAB client of the present invention is initiatively initiated the flow chart to PCC data subscription mode one;
Fig. 2 is that CAB client of the present invention is initiatively initiated the flow chart to PCC data subscription mode two;
Fig. 3 is that server side of the present invention is initiated the flow chart to PCC data subscription mode one;
Fig. 4 is that server side of the present invention is initiated the flow chart to PCC data subscription mode two;
Fig. 5 is that server side of the present invention is initiated the flow chart to PCC data sharing operation;
Fig. 6 is that CAB client of the present invention is initiatively initiated the flow chart to PCC data search mode one;
Fig. 7 is that CAB client of the present invention is initiatively initiated the flow chart to PCC data search mode two;
Fig. 8 is the subscription realization flow figure of contact view in blend address book of the present invention;
Fig. 9 is the shared realization flow figure of contact view in blend address book of the present invention;
Figure 10 is the search realization flow figure of contact view in blend address book of the present invention;
Figure 11 is the composition structural representation of the system that realizes of contact view in blend address book of the present invention.
Embodiment
For making the object, technical solutions and advantages of the present invention clearer, by the following examples and with reference to accompanying drawing, the present invention is described in more detail.
In the present invention, the PCC in CAB system, contact view (Contact View) and other information are all to adopt XML document form to be stored on network, and these information can be positioned, access and manage (such as establishment, change and deletion etc.).Wherein, view (view) is to present to the PCC subset information that other CAB users see.For different contact persons, what CAB user wished that different users sees is own all subsets of the different visual angles of personal information, so there has been the concept of contact view.According to the difference at visual angle (different information categories, different functions etc.), can there is multiple view, as subscribed to view, search view, sharing view.
In the present invention, for the XML definition of contact view, basic ideas are as follows: the contact entry that contact view is just specified PCC on the one hand, does not have concrete contact details; Contact entry in contact view is the subset of the whole contact entry of PCC on the other hand.Therefore can design contact view XML according to the PCC XML document in CAB PCC XDMS.For contact view XML, using all contact entry in PCC as XML element, because view does not have the concrete contact details in PCC, the data format of its XML element is defined as boolean (Boolean) type without exception, in XML document, with True and two value representation contact views of False, whether comprises this contact entry in PCC.
Depending on map generalization: use in CAB User Preferences XDMS user preference XML document management server and rule (preference, strategy) corresponding to corresponding visual angle acts on PCC, as: subscribe to view acting rules and generate and subscribe to view in PCC; Search rule acts on PCC and generates search view; Sharing acting rules generates and shares view in PCC.
On technology realizes, contact view is as a part for user preference strategy, with the form of XML document, is stored in CAB User Preferences XDMS.When the operations such as user produces subscription, searches for or shares, corresponding functional entity is got required view XML document to CAB User Preferences XDMS.By the parsing to view XML document, system can access this and operate required contact entry, acts on PCC document and can produce concrete subscription, search or shared view and present to other CAB users.
In the present invention, contact view can also be set according to carrier policy, such as: the size of view file, quantity, classification etc., but be not limited to this, as spatial limitation of contact view etc. also can be set; CAB user is to the operating right of view file (reading and writing, control etc.), but is not limited to this, as the default view that also operator provides does not allow to revise and delete;
Below be given in the realization flow of contact view under various application scenarioss in CAB system.Contact view of the present invention can be applied to that Contact Subscription is subscribed in the contact of individual contact card, contact is shared in the scenes such as Contact Share and contact search Contact Search, below describes respectively.
Fig. 1 is that CAB client of the present invention is initiatively initiated the flow chart to PCC data subscription mode one, as shown in Figure 1, between CAB user, can keep upgrading in time of the other side's information by subscribing to the mode of PCC, when the ordered contact person's of user contact details change, its blend address book can be upgraded automatically accordingly.CAB user can formulate the difference subscription view of its PCC to other users, the information of part personal information rather than whole PCC is provided when other users subscribe to its PCC information, better protects privacy of user.The use of subscribing to view in the present invention comprises the following steps:
Step 1:CAB client is initiated subscribe request to CAB PCC XDMS, network agent etc. between assembly (SIP(Session Initiation the Protocol)/IP kernel heart net of this subscribe request by XDM Enabler, Aggregation Proxy, subscription agent, territory) forward.
The assembly of step 2:XDM Enabler (subscription agent) is received after user's subscribe request, and subscribe request is routed to CAB PCC XDMS.
Step 3:CAB PCC XDMS is to CAB User Preferences XDMS acquisition request user's subscription view.
Step 4:CAB User Preferences XDMS returns and subscribes to view to CAB PCC XDMS.
Step 5:CAB PCC XDMS generates to subscribe to and return according to subscription view rule and has subscribed to notice to the assembly of XDM Enabler.
The assembly of step 6:XDM Enabler returns to subscription and successfully notifies the client to CAB.
Fig. 2 is that CAB client of the present invention is initiatively initiated the flow chart to PCC data subscription mode two, and as shown in Figure 2, the use of subscribing to view in the present invention can also comprise the following steps:
Step 1:CAB client is initiated subscribe request to CAB PCC XDMS, and this request forwards by the assembly (network agent between SIP/IP core net, Aggregation Proxy, subscription agent, territory) of XDM Enabler.
Step 2: receive after user's request, the assembly of XDM Enabler is to CAB User Preferences XDMS acquisition request user's subscription view.
Step 3:CAB User Preferences XDMS returns and subscribes to view to the assembly of XDM Enabler.
The assembly of step 4:XDM Enabler generates subscribe request and routes to CAB PCC XDMS according to subscribing to view rule.
Step 5:CAB PCC XDMS returns and has subscribed to notice to subscription agent.
Step 6:XDM Enabler returns to subscription and successfully notifies the client to CAB.
The assembly of above-mentioned XDM Enabler can first be inquired about subscribed user's preference and strategy (subscriber in subscribed user-defined what group, the view that corresponding permission is subscribed to) before route subscribe request CAB PCC XDMS.If booking reader is not definition in the grouping of subscribed user's subscription strategy, and subscribed user do not define default view to booking reader, and subscription agent sends a request to the client of user B, C, requires the grouping of subscribed user's given subscription.
Subscriber's client can write subscribed user in the subscription list of own preference and strategy after subscribing to successfully.Subscription agent can be inquired about the registration situation of subscribed person's terminal and be produced subscribed notice.And the view rule of working as in subscribed person's preference changes, can realize and automatically reformulate and read by the subscription function in CAB server.
Fig. 3 is that server side of the present invention is initiated the flow chart to PCC data subscription mode one, and as shown in Figure 3, CAB server side of the present invention initiates the subscription of PCC data specifically to comprise the following steps:
The subscription function of step 1:CAB server is initiated subscribe request to CAB PCC XDMS, and this request forwards by the assembly (network agent between SIP/IP core net, Aggregation Proxy, subscription agent, territory) of XDM Enabler.
The assembly of step 2:XDM Enabler receives after subscribe request, and this asks the XDMS to CAB PCC subscription agent route.
Step 3:CAB PCC XDMS is to CAB User Preferences XDMS acquisition request user's subscription view.
Step 4:CAB User Preferences XDMS returns and subscribes to view to CAB PCC XDMS.
Step 5:CAB PCC XDMS generates to subscribe to and return according to subscription view rule and has subscribed to notice to subscription agent.
After step 5, follow-up subscription flow process will be carried out.
Fig. 4 is that server side of the present invention is initiated the flow chart to PCC data subscription mode two, and as shown in Figure 4, CAB server side of the present invention initiates the subscription of PCC data specifically to comprise the following steps:
The subscription function of step 1:CAB server is initiated subscribe request to CAB PCC XDMS, and this request forwards by the assembly (network agent between SIP/IP core net, Aggregation Proxy, subscription agent, territory) of XDM Enabler.
The assembly of step 2:XDM Enabler receives after user's request, and subscription agent is to CAB User Preferences XDMS acquisition request user's subscription view.
Step 3:CAB User Preferences XDMS returns and subscribes to view to subscription agent.
Step 4: subscription agent generates subscribe request and routes to CAB PCC XDMS according to subscribing to view rule.
Step 5:CAB PCC XDMS returns and has subscribed to notice to subscription agent.
After step 5, follow-up subscription flow process will be carried out.
In the contact of individual contact card, share in scene, CAB user can share by CAB system oneself contact person or PCC, receiving shared people can be that CAB user can be also non-CAB user, can also can be not in sharer's address book in sharer's address book.By sharing view, CAB user can share to and receive shared people according to the different view of different classes of selection that receives shared people; PCC also can produce and share data according to shared view XML document.
Fig. 5 is that server side of the present invention is initiated the flow chart to PCC data sharing operation, and as shown in Figure 5, to PCC, data sharing comprises the following steps in CAB client initiation of the present invention:
Step 1:CAB client is initiated sharing request to CAB PCC XDMS, and this request forwards by the assembly (network agent between SIP/IP core net, Aggregation Proxy, subscription agent, territory) of XDM Enabler.
The assembly of step 2:XDM Enabler receives after user's request, and this asks the XDMS to CAB PCC XDM Enabler route.
Step 3:CAB PCC XDMS is to CAB User Preferences XDMS acquisition request user's shared view.
Step 4:CAB User Preferences XDMS returns and shares view to CAB PCC XDMS
After step 4, will carry out the corresponding flow process of sharing.
In the search scene to contact person, CAB user can set a special-purpose view of search, wherein comprise less can disclosed personal information, when other user searchs are during to oneself PCC, system only provides the PCC information that this view is corresponding; PCC also can produce Search Results according to search view XML document;
Fig. 6 is that CAB client of the present invention is initiatively initiated the flow chart to PCC data search mode one, and as shown in Figure 6, to CAB/PCC, data search specifically comprises the following steps in CAB client initiation of the present invention:
Step 1:CAB client is to CAB AB/PCC XDMS(XML document management server) initiate searching request, this request forwards by the assembly (network agent between SIP/IP core net, Aggregation Proxy, search agent, territory) of XDM Enabler.
The assembly of step 2:XDM Enabler receives after user's request, and search agent is to CAB User Preferences XDMS acquisition request user's search view.
Step 3:CAB User Preferences XDMS returns to search view to search agent.
Step 4: search agent generates searching request and routes to CAB AB/PCC XDMS according to search view rule
Step 5:CAB AB/PCC XDMS returns to Search Results to search agent.
Step 6:XDM Enabler returns to Search Results to CAB client.
Fig. 7 is that CAB client of the present invention is initiatively initiated the flow chart to PCC data search mode two, and as shown in Figure 7, to CAB/PCC, data search specifically comprises the following steps in CAB client initiation of the present invention:
Step 1:CAB client is initiated searching request to CAB AB/PCC XDMS, and this request forwards by the assembly (network agent between SIP/IP core net, Aggregation Proxy, search agent, territory) of XDM Enabler.
The assembly of step 2:XDM Enabler receives after user's request, and this asks the XDMS to CAB AB/PCC search agent route.
Step 3:CAB AB/PCC XDMS is to CAB User Preferences XDMS acquisition request user's search view.
Step 4:CAB User Preferences XDMS returns to search view to CAB AB/PCC XDMS.
Step 5:CAB AB/PCC XDMS returns to Search Results to search agent.
Step 6:XDM Enabler returns to Search Results to CAB client.
Above-mentioned search agent can also be processed Search Results according to searched people's user preference, searched people's user preference mainly comprise whether allow searched etc.
Fig. 8 is the subscription realization flow figure of contact view in blend address book of the present invention, and in subscription, CAB client-side initiatively initiates to the embodiment of the subscription of PCC data as shown in Figure 8, specifically to comprise the following steps:
Step 1: XDM client and the SIP/IP core of user A complete two-way authentication, comprises complete authentication process (BSF(Bootstrapping Server Function)-KM(Key Management) generation distributing key);
Step 2: the XDM client of user A sends subscribe request to SIP/IP core, and wherein agreement is SIP, and subscribe message is to use Subscribe method, and Event defines event type; To field is subscribed logical address of putting; Also can in a subscribe message, subscribe to a plurality of people, that will comprise the dated all logical addresses of thinking the people of subscription of a list in message body, and the address that To Field Definition is subscription agent, for message body, include a plurality of subscribed people's situation, Required field will mark: recipient-list-subscribe.
Step 3:SIP/IP core is forwarded to subscription agent by subscribe request;
Step 4: subscription agent is inquired about preference and strategy (own what group in user B, C definition of subscribed user B, C, the view that corresponding permission is subscribed to), agreement is XML configuration access agreement (XCAP, XML Configuration Access Protocol), with the HTTP GET of XCAP agreement, remove to obtain user preference and strategy exactly;
Step 5: if user A does not have definition and B, C not to define default view to A in the grouping of the subscription strategy of user B, C, subscription agent sends a request to the client of user B, C, the grouping that requires user to specify A, this request goes to client by SIP/IP core;
Step 6: the client of user B, C is forwarded to subscription agent by grouping response by SIP/IP core;
Step 7: subscription agent produces man-to-man backstage subscribe request according to subscribed person's preference and strategy;
Step 8: subscription agent is sent to SIP/IP core by subscribe request; SIP/IP core is forwarded to PCC XDMS by subscribe request;
Step 9:PCC XDMS obtains subscription view to CAB User Preferences XDMS, and agreement is XCAP HTTP GET
Step 10:PCC XDMS produces and preserves subscribing relationship;
Step 11:PCC XDMS notice SUP subscription agent has been subscribed to
Step 12.1: subscription agent sends and subscribes to successfully notice to SIP/IP core;
Step 13.1:SIP/IP core is forwarded to client by subscribing notification;
The client of step 14.1:A writes contact person B, C in the subscription list of own preference and strategy, and agreement is XCAP, increases new user logic address in CAB UserPreferences XDMS subscription list exactly with the HTTP PUT of XCAP;
Step 12.2: the registration situation that subscription agent is inquired about subscribed person's terminal produces subscribed notice, agreement is SIP, can, by the Message method of SIP, add the text message such as " your good friend XXX has subscribed to your friend's view " in this message body.
Step 13.2: subscription agent is sent to SIP/IP core by subscribed notice;
Step 14.2:SIP/IP core is transmitted to subscribed person's terminal by subscribed notice;
Step 12.3: the subscribed view information of current B, C is sent in the network address book AB XDMS of A after subscribing to the processing of function in CAB server, agreement in change notice is SIP, method is SIP Notify method, has the change indication of XCAP document or even directly contain the content of change in message body;
Step 13.3: address book AB XDMS is synchronized to the information of subscription by synchronization server each terminal of user A;
Step 15: in subscribed person's individual contact card information, subscribed part is changed;
Step 16: changed information is sent in the network address book AB XDMS of A after subscribing to the processing of function in CAB server, agreement in change notice is SIP, method is SIP Notify method, has the change indication of XCAP document or even directly contain the content of change in message body;
Step 17: address book AB XDMS is synchronized to the information of subscription by synchronization server each terminal of user A.
Step 18: view rule open in subscribed person's preference and strategy changes;
Step 19: inquire about this view and by which user ordered;
Step 20: according to the result of inquiry, the change of subscribed person CAB User Preferences XDMS triggers the subscription function of CAB server;
The subscription function of step 21.a:CAB server is sent to SIP/IP core by view notice of change, and agreement is Session Initiation Protocol, adopts SIP Message method, and message body includes such as " your good friend XXX changes to your open view " text message;
Step 22.a:SIP/IP core is forwarded to subscribed person by notice;
The subscription function of step 21.b:CAB server resends subscribe request;
Step 22.b: subscribe request is sent to subscription agent by SIP/IP core;
Flow process is subscribed in the follow-up execution of step 22.b accordingly.
Fig. 9 is the shared realization flow figure of contact view in blend address book of the present invention, as shown in Figure 9, in the operation of sharing PCC, the application of contact view is specifically comprised the following steps:
Step 1: user A will share to user B, first authentication.
Step 2: the PCC that selection will be shared and shared recipient, send sharing request to the AP in XDM Enabler.
It is to share information that step 3:AP detects the information of receiving, forwards sharing request to CAB PCC XDMS.
Step 4:CAB PCC XDMS processes sharing request, to CAB User Preferences XDMS request, uses HTTP-get message to take the shared view XML document of family A oneself.
Step 5:CAB User Preferences XDMS returns and shares view XML document to CAB PCC XDMS.
Flow process is shared in the follow-up execution of step 5 accordingly.
Figure 10 is the search realization flow figure of contact view in blend address book of the present invention, and as shown in figure 10, the application to contact view in search operation specifically comprises the following steps:
Step 1:CAB user and AP complete two-way authentication.
Step 2: the CAB user who has authenticated sends a HTTP POST searching request to AP, and agreement is XDM-5i Xquery.
Step 3:AP forwards searching request to search agent (SEP, Search Proxy), and agreement is XDM-6i Xquery.
Step 4:SEP analysis protocol also converts HTTP GET request to HTTP POST request.
Step 5:SEP obtains user preference and search view, and PCC XDMS will inquire about each user's search view in when search, only searches for the contact entry comprising in the search view that CAB User Preferences XDMS returns in search operation.
Step 6:SEP produces searching request according to the UPP obtaining.
Step 7a:SEP forwards searching request to corresponding PCC, and agreement is XDM-7i Xquery.
Step 7b: if there is cross-domain search, forward searching request to Cross-Network Proxy, agreement is XDM-9i Xquery, carries out afterwards cross-domain search.Cross-domain search and the search in this territory are symmetrical, repeat no more herein.
Step 8:PCC carries out search operation and generates Search Results.
Step 9:PCC returns to SEP by Search Results.
Step 10: when SEP receives the Search Results that PCC sends, trigger the HTTP GET request that generates.
Step 11: the user preference of getting searched people.
Step 12a:SEP processes Search Results according to searched people's user preference, searched people's user preference mainly comprise whether allow searched etc.
Step 12b: if there is cross-domain search, the result of cross-domain search returns to the SEP in this territory by Cross-Network Proxy.
Step 13: if contain a plurality of Search Results, these Search Results of SEP polymerization.
Step 14:SEP is transmitted to AP by these Search Results.
Step 15:AP returns to CAB user by Search Results.
Figure 11 is the composition structural representation of the system that realizes of contact view in blend address book of the present invention, as shown in figure 11, in blend address book of the present invention, the system that realizes of contact view comprises setting unit 110, the first transmitting element 111, receiving element 112, acquiring unit 113 and the second transmitting element 114, wherein, setting unit 110 is for representing the contact entry of individual contact card PCC with extending mark language XML, for described contact entry sets property, indicate the visual angle information of described contact entry in contact view, and indicate described contact entry preference information, the information of affiliated strategy, wherein, the contact entry in described contact view is chosen the contact entry from described PCC, the first transmitting element 111 is arranged in user's terminal or CAB Server, for send the operation requests of contact view to CAB User Preference XDMS, receiving element 112 is arranged in described CAB User Preference XDMS, for receiving described operation requests, acquiring unit 113 is arranged in described CAB User Preference XDMS, be used for according to the visual angle information of the contact view of described operation requests and/or to the preference information of described contact entry and/or the policy information to described contact entry, act on the XML document of the contact entry in described PCC, obtain the contact view of described operation requests, the second transmitting element 114 is arranged in described CAB User Preference XDMS, returns to the user of described operation requests for the contact view that described acquiring unit is obtained.
Above-mentioned operation requests comprises at least one of following request: subscribe request, sharing request, searching request.
When operation requests is subscribe request, acquiring unit 113 obtains the contact view of described operation requests, comprise: the assembly of XDM Enabler receives after the subscribe request of the first transmitting element 111 initiations, described subscribe request is routed to CAB PCC XDMS, by described CAB PCC XDMS, to CAB User Preference XDMS, forward described subscribe request; The XML document of described CAB User Preference XDMS contact entry in PCC by the subscription view acting rules in described subscribe request, according to the attribute of the contact entry in PCC described in described subscription view rules modification, and will revise described PCC after contact entry attribute as described contact view, the assembly by described CAB PCC XDMS, described XML document management engine sends to described booking reader;
Or, receiving after the subscribe request of the first transmitting element 111, the assembly of described XDM Enabler sends subscribe request to described CAB User Preference XDMS; Described CAB User Preference XDMS produces subscribe request according to the subscription view rule in described subscribe request, and send to CAB PCC XDMS, CAB PCC XDMS returns to subscription response to described CAB User Preference XDMS, and described CAB User Preference XDMS notifies described booking reader to subscribe to successfully.
As shown in figure 11, in blend address book of the present invention, the system that realizes of contact view also comprises query unit 115, for before the assembly of XDM Enabler routes to described subscribe request described CAB PCC XDMS or described CAB User Preference XDMS, inquire about subscribed user's preference information and policy information, when not defining view or there is no default view in the subscription strategy grouping booking reader described subscribed user, the assembly inquiry of described XDM Enabler notifies described subscribed user to specify described booking reader's grouping information.
As shown in figure 11, in blend address book of the present invention, the system that realizes of contact view also comprises writing unit 116, be arranged in user's terminal, for described booking reader after contact view is subscribed to successfully, described subscribed user's preference information and policy information are write in the subscription list of self.
When operation requests is searching request, the contact view of the described operation requests of described acquisition, comprise: the first transmitting element 111 sends to the assembly of XDM Enabler the searching request that described search subscriber is initiated, the assembly of described XDM Enabler routes to CAB PCC XDMS by described searching request, by described CABPCC XDMS, to described CAB User Preference XDMS, forwards described searching request; Or the assembly of described XDM Enabler receives after the searching request of the search subscriber that described the first transmitting element sends, and described searching request is routed to CAB User Preference XDMS;
Described CAB User Preference XDMS obtains the contact view of the search special use that described searched user arranges, and the assembly by described CAB PCC XDMS, described XML document management engine sends to described search subscriber; What in the special-purpose contact view of described search, comprise that described searched user sets comprises less contact entry in self PCC.
When operation requests is sharing request, the contact view of the described operation requests of described acquisition, comprising:
The first transmitting element 111 sends to the assembly of XDM Enabler the sharing request that described sharing users is initiated, the assembly of described XDM Enabler routes to CAB PCC XDMS by described sharing request, by described CAB PCC XDMS, to described CAB User Preference XDMS, forwards described sharing request;
Described in described CAB User Preference XDMS obtains, be shared the shared contact view that user arranges, the assembly by described CAB PCC XDMS, described XML document management engine sends to described sharing users; The shared recipient of described shared contact view comprises blend address book user or non-blend address book user, the contact entry in described shared contact view choose in the PCC of sharing users or contact addresses book AB in.
Those skilled in the art are to be understood that, in blend address book shown in Figure 11, the system that realizes of contact view is to arrange for realizing the implementation method of contact view in aforesaid blend address book, in system shown in Figure 11, the function of each processing unit can be understood referring to figs. 1 through the description of method shown in Fig. 9, the function of each processing unit can realize by the program running on processor, also can realize by concrete logical circuit.It will be appreciated by those skilled in the art that the query unit 115 shown in Figure 11 and writing unit 116 not realize the essential features of basic technical scheme of the present invention.
The above, be only preferred embodiment of the present invention, is not intended to limit protection scope of the present invention.

Claims (12)

1. the implementation method of contact view in a blend address book, it is characterized in that, contact entry in individual contact card PCC is represented with extending mark language XML, for described contact entry sets property, indicate the visual angle information of described contact entry in contact view and the information that indicates described contact entry preference information, affiliated strategy; Contact entry in described contact view is chosen the contact entry from described PCC; Described method also comprises:
User sends the operation requests of contact view to blend address book user preference XML document management server (CAB User Preference XDMS), described CAB User Preference XDMS is according to the visual angle information of the contact view in described operation requests and/or to the preference information of described contact entry and/or the policy information to described contact entry, act on the XML document of the contact entry in described PCC, obtain the contact view of described operation requests, and return to described user;
Wherein, when described operation requests is subscribe request, the assembly of XML document management engine (XDM Enabler) receives after the subscribe request of described booking reader or fuse address book server CAB Server initiation, described subscribe request is routed to blend address book individual contact card XML document management server (CAB PCC XDMS), by described CAB PCC XDMS, to described CAB User Preference XDMS, forward described subscribe request; The XML document of described CAB User Preference XDMS contact entry in PCC by the subscription view acting rules in described subscribe request, according to the attribute of the contact entry in PCC described in described subscription view rules modification, and will revise described PCC after contact entry attribute as described subscription view, the assembly by described CAB PCC XDMS, described XML document management engine sends to described booking reader;
Or, receiving after the subscribe request of described booking reader or CAB Server, the assembly of described XDM Enabler sends subscribe request to described CAB User Preference XDMS; Described CAB User Preference XDMS produces subscribe request according to the subscription view rule in described subscribe request, and send to CAB PCC XDMS, CAB PCC XDMS returns to subscription response to described CAB User Preference XDMS, and described CAB User Preference XDMS notifies described booking reader to subscribe to successfully.
2. method according to claim 1, is characterized in that, described operation requests also comprises at least one of following request: sharing request, searching request.
3. method according to claim 1, is characterized in that, the assembly of described XDM Enabler also comprises before described subscribe request is routed to described CAB PCC XDMS or described CAB User Preference XDMS:
The assembly of described XDM Enabler is inquired about subscribed user's preference information and policy information, when not defining view or there is no default view in described subscribed user's subscription strategy grouping, the assembly inquiry of described XDM Enabler notifies described subscribed user to specify described booking reader's grouping information.
4. method according to claim 1, is characterized in that, described method also comprises:
Described booking reader, after contact view is subscribed to successfully, writes described subscribed user's preference information and policy information in the subscription list of self.
5. method according to claim 2, is characterized in that, when described operation requests is searching request, the contact view of the described operation requests of described acquisition, comprising:
The assembly of XDM Enabler receives after the searching request of described search subscriber initiation, and described searching request is routed to CAB PCC XDMS, by described CAB PCC XDMS, to CAB User Preference XDMS, forwards described searching request; Or, receiving after the searching request of described search subscriber, the assembly of described XDM Enabler routes to CAB User Preference XDMS by described searching request;
Described CAB User Preference XDMS obtains the contact view of the search special use that described searched user arranges, and the assembly by described CAB PCC XDMS, described XML document management engine sends to described search subscriber; What in the special-purpose contact view of described search, comprise that described searched user sets comprises less contact entry in self PCC.
6. method according to claim 2, is characterized in that, when described operation requests is sharing request, the contact view of the described operation requests of described acquisition, comprising:
The assembly of XDM Enabler receives after the sharing request of described sharing users initiation, and described sharing request is routed to CAB PCC XDMS, by described CAB PCC XDMS, to CAB User Preference XDMS, forwards described sharing request;
Described in described CAB User Preference XDMS obtains, be shared the shared contact view that user arranges, the assembly by described CAB PCC XDMS, described XML document management engine sends to described sharing users; The shared recipient of described shared contact view comprises blend address book user or non-blend address book user, the contact entry in described shared contact view choose in the PCC of sharing users or contact addresses book AB in.
7. the system that realizes of contact view in blend address book, is characterized in that, comprising:
Setting unit, for the contact entry of individual contact card PCC is represented with extending mark language XML, for described contact entry sets property, indicate the visual angle information of described contact entry in contact view and the information that indicates described contact entry preference information, affiliated strategy; Wherein, the contact entry in described contact view is chosen the contact entry from described PCC;
The first transmitting element, is arranged in user's terminal or CAB Server, for send the operation requests of contact view to CAB User Preference XDMS;
Receiving element, is arranged in described CAB User Preference XDMS, for receiving described operation requests;
Acquiring unit, be arranged in described CAB User Preference XDMS, be used for according to the visual angle information of the contact view of described operation requests and/or to the preference information of described contact entry and/or the policy information to described contact entry, act on the XML document of the contact entry in described PCC, obtain the contact view of described operation requests;
The second transmitting element, is arranged in described CAB User Preference XDMS, returns to the user of described operation requests for the contact view that described acquiring unit is obtained;
Wherein, when described operation requests is subscribe request, the assembly of XDM Enabler receives after the subscribe request of described the first transmitting element initiation, described subscribe request is routed to blend address book individual contact card XML document management server (CAB PCC XDMS), by described CAB PCC XDMS, to described CAB User Preference XDMS, forward described subscribe request; The XML document of described CAB User Preference XDMS contact entry in PCC by the subscription view acting rules in described subscribe request, according to the attribute of the contact entry in PCC described in described subscription view rules modification, and will revise described PCC after contact entry attribute as described subscription view, the assembly by described CAB PCC XDMS, described XML document management engine sends to described booking reader;
Or, receiving after the subscribe request of described the first transmitting element, the assembly of described XDM Enabler sends subscribe request to described CAB User Preference XDMS; Described CAB User Preference XDMS produces subscribe request according to the subscription view rule in described subscribe request, and send to CAB PCC XDMS, CAB PCC XDMS returns to subscription response to described CAB User Preference XDMS, and described CAB User Preference XDMS notifies described booking reader to subscribe to successfully.
8. system according to claim 7, is characterized in that, described operation requests also comprises at least one of following request: sharing request, searching request.
9. system according to claim 7, is characterized in that, described system also comprises:
Query unit, for before the assembly of XDM Enabler routes to described subscribe request described CAB PCC XDMS or described CAB User Preference XDMS, inquire about subscribed user's preference information and policy information, when not defining view or there is no default view in the subscription strategy grouping booking reader described subscribed user, the assembly inquiry of described XDM Enabler notifies described subscribed user to specify described booking reader's grouping information.
10. system according to claim 7, is characterized in that, described system also comprises:
Writing unit, is arranged in user's terminal, for described booking reader after contact view is subscribed to successfully, described subscribed user's preference information and policy information are write in the subscription list of self.
11. systems according to claim 8, is characterized in that, when described operation requests is searching request, the contact view of the described operation requests of described acquisition, comprising:
Described the first transmitting element sends to the assembly of XDM Enabler the searching request that described search subscriber is initiated, the assembly of described XDM Enabler routes to CAB PCC XDMS by described searching request, by described CAB PCC XDMS, to described CAB User Preference XDMS, forwards described searching request; Or the assembly of described XDM Enabler receives after the searching request of the search subscriber that described the first transmitting element sends, and described searching request is routed to CAB User Preference XDMS;
Described CAB User Preference XDMS obtains the contact view of the search special use that described searched user arranges, and the assembly by described CAB PCC XDMS, described XML document management engine sends to described search subscriber; What in the special-purpose contact view of described search, comprise that described searched user sets comprises less contact entry in self PCC.
12. systems according to claim 8, is characterized in that, when described operation requests is sharing request, the contact view of the described operation requests of described acquisition, comprising:
Described the first transmitting element sends to the assembly of XDM Enabler the sharing request that described sharing users is initiated, the assembly of described XDM Enabler routes to CAB PCC XDMS by described sharing request, by described CAB PCC XDMS, to described CAB User Preference XDMS, forwards described sharing request;
Described in described CAB User Preference XDMS obtains, be shared the shared contact view that user arranges, the assembly by described CAB PCC XDMS, described XML document management engine sends to described sharing users; The shared recipient of described shared contact view comprises blend address book user or non-blend address book user, the contact entry in described shared contact view choose in the PCC of sharing users or contact addresses book AB in.
CN200910238234.9A 2009-11-23 2009-11-23 Implementation method and system for contact view in compressed address book Expired - Fee Related CN102075644B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN200910238234.9A CN102075644B (en) 2009-11-23 2009-11-23 Implementation method and system for contact view in compressed address book

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN200910238234.9A CN102075644B (en) 2009-11-23 2009-11-23 Implementation method and system for contact view in compressed address book

Publications (2)

Publication Number Publication Date
CN102075644A CN102075644A (en) 2011-05-25
CN102075644B true CN102075644B (en) 2014-04-09

Family

ID=44033979

Family Applications (1)

Application Number Title Priority Date Filing Date
CN200910238234.9A Expired - Fee Related CN102075644B (en) 2009-11-23 2009-11-23 Implementation method and system for contact view in compressed address book

Country Status (1)

Country Link
CN (1) CN102075644B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101922985B1 (en) * 2011-12-08 2018-11-29 삼성전자주식회사 Apparatus and method for inviting subscription of contact information

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101335634A (en) * 2007-06-29 2008-12-31 华为技术有限公司 Method, system and network appliance providing contact information
EP2068534A1 (en) * 2007-12-07 2009-06-10 Research In Motion Limited System and method for managing multiple external identities of users with local or network based address book
CN101521861A (en) * 2008-02-26 2009-09-02 华为技术有限公司 A method for obtaining the Color Ring Back Tone service information of contacting persons

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101335634A (en) * 2007-06-29 2008-12-31 华为技术有限公司 Method, system and network appliance providing contact information
EP2068534A1 (en) * 2007-12-07 2009-06-10 Research In Motion Limited System and method for managing multiple external identities of users with local or network based address book
CN101521861A (en) * 2008-02-26 2009-09-02 华为技术有限公司 A method for obtaining the Color Ring Back Tone service information of contacting persons

Also Published As

Publication number Publication date
CN102075644A (en) 2011-05-25

Similar Documents

Publication Publication Date Title
CN100563196C (en) Communication system and in communication system the method for Query Information
US20140188802A1 (en) Pull and paste
WO2007068195A1 (en) A method and system for querying user information, and search agent, client and server
KR20150005708A (en) Information sharing method and device
CN101163117B (en) Packet management method, packet resource sharing method and instant communication equipment
EP3293925A1 (en) A network storage system and a control method for accessing the network storage content
CN103001926A (en) Method, device and system for subscription notification
CN102415067A (en) Subscription management for content-based presence service
CN102422609A (en) Content-based publication-subscription system for presence information
CN103119911A (en) System and method for synchronizing the profile of a user in social networks and the user's personal contact card (PCC)
CN101682648A (en) Managing entity data in case of multiple entity identities
CN104348848B (en) Manage method, terminal device and the server of picture
CN109314947A (en) Equipment and/or line events perception and intelligent synchronization
US10601799B2 (en) System and method for visualizing data sharing arrangements for an organization
EP2847931B1 (en) Method and apparatus for updating personal information in communication system
CN103139703B (en) A kind of method and terminal of the information processing based on RCS e systems
KR101175174B1 (en) Method and Apparatus for deliverying information using images taken from real things as an information agent
CN103460681B (en) The management method of the thin ability of fuse address
CN102075644B (en) Implementation method and system for contact view in compressed address book
CN109067905B (en) Method for realizing decentralized network application
US9760327B2 (en) Determining rendering systems utilizing printer locations and rendering system attributes
CN103457962B (en) Access method, microblogging client and the system of microblogging photograph album
CN101800657B (en) Combined address book system and relation view management method thereof
EP2891270B1 (en) Method and apparatus for updating personal information in communication system
CN102025697B (en) For the invitation subscription of CAB, subscription and subscription update notification method and device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20140409

Termination date: 20171123