CN102576361A - System and method for aggregating multiple contact information sources in a network-based address book system - Google Patents
System and method for aggregating multiple contact information sources in a network-based address book system Download PDFInfo
- Publication number
- CN102576361A CN102576361A CN2010800065186A CN201080006518A CN102576361A CN 102576361 A CN102576361 A CN 102576361A CN 2010800065186 A CN2010800065186 A CN 2010800065186A CN 201080006518 A CN201080006518 A CN 201080006518A CN 102576361 A CN102576361 A CN 102576361A
- Authority
- CN
- China
- Prior art keywords
- address book
- list
- request
- contact person
- searching request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
Abstract
Methods are provided for searching at least one directory that is external to an address book architecture including a client and a server. In one embodiment a client may communicate a contact search request that specifies an external directory which does not support a standard search format, the request causing the server to translate the request to an external search request in another format supported by the external directory. In another embodiment a server may translate a contact search request received from a client when the request specifies an external directory which does not support a standard search format. In yet another embodiment an interworking function, which is operable to import contact information from a legacy address book storage to a converged address book storage, of an address book server is adapted to query an external directory which does not support a standard search format.
Description
CROSS-REFERENCE TO RELATED PATENT
Present patent application requires in the U.S. Provisional Patent Application No.61/150 of submission on February 5th, 2009,208 right.
Technical field
The disclosure relates in general to communication facilities, the system and method that uses blend address book.More specifically, the disclosure relates to a plurality of associated person informations of search source in the blend address book system.
Background technology
Going up the electronic address book application of carrying out at electronic equipment (for example, smart phone, PDA, portable computer etc.) is useful for setting up and keeping interpersonal relation.Typical address book application is configured to visit in contacts local storage on the equipment that the executive address book is used or remote storage (for example, on server, database or other NEs).Each contacts comprises associated person information, for example: name, physical address, e-mail address, telephone number, Personal Identification Number, instant message identifier or the like.Correspondingly, contacts makes the user of equipment can get in touch other individualities that are associated with this contacts, or otherwise communication with it.
Created the mode that much associated person information is organized and managed in innovation growing aspect service field and the mobile device.In addition, existence is used for a lot of dissimilar contact management/address book application of managing liaison information and contacts, relevant data layout and agreement.That though the equipment user is enjoying is relevant with the contact management (the various selections of vis-à-vis), current available option caused the different address book use and the associated person information source between interoperability issue.In other words, on equipment, lack about the unification of address book application and consistent user experience, the function of particularly expecting to the equipment user that is easy to use and personal computer (PC) type wireless mobile apparatus.
Normal structure (Open Mobile Alliance (OMA) blend address book (CAB), open mobile-terminal platform (OMTP) and internet engineering duty group (IETF)) is being carried out through providing public address book system to improve some action of interoperability and user experience.About OMA CAB (after this also being referred to as CAB enabler (Enabler)), contact person's search is a kind of function that is described below:
The CAB enabler is intended to provide the mechanism of searched for contact information or contacts.The user of CAB enabler can be from host C AB system, long-range CAB system and/or the available external source of service provider (for example, Yellow Page
TM(Yellow Pages
TM), 411 Catalogue assistants etc.) searched for contact information.Can receive CAB user's authorization rule (for example,, limiting associated person information) and service provider's domination of strategies through the obtainable associated person information of search operation by user-defined contact person's view based on order.
A kind of mode that contact person's function of search is provided of proposal use equipment and web-based system (for example, the simple HTTP interface between CAB), this interface is responsible for CAB user's searching request is mail to based on network address book (NAB) system.Use simple HTTP interface keyword search to be provided with general fashion.In addition, the HTTP interface also provides XQuery has been embedded into the mechanism in the searching request.
Though the solution that comprises aforementioned HTTP interface that is proposed has made things convenient for contact person's function of search; (for example be used to search for a plurality of external relation people information sources; Comprise data source based on non-XCAP/XDM), and can be progress useful in this area to the new fuse address book function of concentrating from the Search Results of multiple source alternatively.
Summary of the invention
Description of drawings
Fig. 1 shows the block diagram of conventional address book system;
Fig. 2 is the block diagram of the illustrated functional blocks of address book server shown in Figure 1;
Fig. 3 shows the block diagram of another conventional address book system;
Fig. 4 shows the exemplary plot that is used to search for a plurality of external relation people information sources;
Fig. 5 shows the not illustration in the associated person information source that is used to search for XDM type and non-XDM type;
Fig. 6 shows the process flow diagram of the exemplary method in a plurality of associated person informations of search source;
Fig. 7 shows the process flow diagram of another exemplary method in a plurality of associated person informations of search source;
Fig. 8 show data source externally and the standard x ML data layout that can be used for searching between the sample data mapping.
Embodiment
The disclosure provides the method and system that is used for a plurality of associated person informations of search source in based on network address book (NAB) system (for example, like the framework by OMA CAB definition).More specifically; The disclosure provide be used to make the user except the source of search XML data management (XDM) type (for example; Individual's contacts cards (PCC) XDM server, address book XDM server etc.) outside; Can also search for the system and method in external source (source that for example, is used for the non-XDM type of contacts and/or associated person information).Though among this paper this system is called the address book system of " Network Based ", the employed one or more equipment of the user of this system also can comprise the contacts and/or the associated person information of local storage.That is, equipment can comprise contacts and/or associated person information in fixing or removable storer (for example, SIM, SD card, flash memory etc.).Turn to accompanying drawing now, example system and method are described.
Fig. 1 shows sample address book system 100.As shown in the figure, use network side 110 and equipment side 120 to come configuration-system 100.Network side 110 and equipment side 120 can comprise one or more entities, assembly or the module that goes out as shown in the figure, and this entity, assembly or module can be implemented as the combination of hardware, software or hardware and software.Can equipment side 120 partly be configured to can use on any suitable equipment 126 of public address book.Example apparatus comprises Wireless Telecom Equipment; For example; Cell phone, personal digital assistant, bidirection pager, smart phone, portable computer or other are this to comprise that processing module (for example; Microprocessor, CPU etc.), the equipment of memory module (for example, RAM, ROM or other storeies) and communication module (for example, radio receiving-transmitting unit etc.).Can equipment side 120 be configured at least in part on wireline equipment, for example personal computer, laptop computer, STB or the like.Though, can one or more equipment side assemblies (for example, the address book client 122) alternatively be embodied as the part of network side 110 not shown in Fig. 1.
Can use HTTP(Hypertext Transport Protocol) to be implemented in the underlying protocol of the interface 128 between address book client 122 and the address book server 140.In addition, the main body of agreement and Payload can comprise the necessary grammer of transmission request.Yet the communication of carrying on the interface 128 can have the various forms and the agreement of the message that comprises the SIP type.
Another functional block of equipment side 120 is Open Mobile Alliance (OMA) data sync (DS) client 124.Can OMADS client 124 be configured to and 122 cooperations of address book client, with simultaneous user's between equipment side 120 and network side 100 individual associated person information and address-book data.That is, OMADS client 124 can assist to be known as the synchronous OMACAB function of contact person.Can use OMA data sync (DS) server 130 to realize contact person's synchronizing function; OMA data sync (DS) server 130 is configured to communicate by letter with OMA DS client 124 with OMA DS-2 interface 134 via OMA DS-1 interface 132, perhaps with 124 cooperations of OMADS client.
In one embodiment, being used for synchronous underlying protocol can be that HTTP or wireless application protocol (wap) push.Can use the defined notification message framework of OMADS, as the mechanism that is used for to CAB user's (CAB user can be to use the individual of the equipment 126 with client 122) notice CAB information.For example, in notice, can use the renewal that causes ordering the associated person information that is produced, the change in user's individual contacts cards information, the CAB state etc. by the contact person.Can also transmit notice through other mechanism; For example; Short Message Service (SMS), Multimedia Message service (MMS), Email, instant message, SIP order (Subscribe)/(for example notify (Notify); According to IETF RFC 3265), SIP pushes (PUSH) (for example, according to OMA " Push Architecture, " OMA-AD-Push-V2.2) etc.
Further illustrate like Fig. 1, the network side 110 of system 100 also comprise address book storer 142, XDM enabler 144 (for example, OMA XDM standard is specified) and can with the assist architecture of address book server 140 interfaces.As shown in the figure, assist architecture can comprise traditional address book system 150, outside enabler 160 framework of the defined client-server type of OMA that is used for information receiving and transmitting, existence etc. (for example, by) and remote address book server 170.Can there be (for example, at equipment side 120 as other data structures in the storer of database or equipment 126) in the local address book storer.This local address book storer can be included in the contacts of storage in the network side 110 or the copy of associated person information.Can the contact person of the contact person of this locality storage and the network storage is synchronous.In addition, the local address book storer can comprise one or more traditional, proprietary perhaps measured local address books etc.In addition, can one or more companies (for example, based on enterprise) address book be stored in the local address book storer.Can be for example following situation: owing to lack voucher, can not conduct interviews and search for from 110 pairs of one or more CompanyAddresses of network side book.
With reference to figure 2; Address book server 200 (can be similar or different with the address book server 140 of Fig. 1) can comprise to address book system 100 provides the one or more modules by the function of OMA CAB definition, and the function of OMA CAB definition comprises: contact person's search, contact person share, the contact person orders etc.Address book server 200 can be the hardware device (for example, server computer) with processing module, and this processing module is carried out address book server software, firmware or the instruction that is used to provide aforementioned functional.Though among Fig. 2 module 210-270 is depicted as a part that is configured as address book server 200, yet one or more module 210-270 can be configured in other positions in the system 100.To describe module 210-270 in detail now.
User accounts manager and authentication proxy's module 210: this module is in charge of authentification of user and accounts information; Comprise User Preferences and customization aspect; For example with only from server to relevant configurations such as the reception notifications of client (for example, client 122) sync section address-book data, reception/not.
Informing function module 220: use the renewal of this module in the ordered contact person of client (for example, client 122) notice.This function can be used DS notice framework or other mechanism, for example, and Email, SMS, instant message (IM), SIP order/notice etc.
XML document administrative client (XDMC) module 270: this module is responsible for and the cooperation of XML document management server (XDMS) module, with the management (for example, visit and processing) that is used for address-book data.This address-book data can be (for example to be stored in individual contacts cards (PCC) XDM server; Information the frame 146 among Fig. 1) or that be associated with PCC XDM server; And be stored in the address book XDM server (for example, the frame among Fig. 1 148) or the information that is associated with address book XDM server.For this reason, XDMC module 270 can with contact person's function of search module 250 or interactive module 260 be communicated by letter or cooperation.
Further illustrate like Fig. 2; Use contact person's ordering function module 230, contact person's sharing functionality module 240 and interaction function module 260 that address book server 200 is configured to carry out the function about CAB, comprise that respectively the contact person orders, the contact person shares and communicate by letter with traditional address book.
Refer again to Fig. 1, network side 110 also comprises XML document management (XDM) enabler 144.XDM enabler 144 comprises: individual contacts cards (PCC) XML document management server (XDMS) 146, PCC XDMS 146 can comprise the PCC of system 100.In addition, XDM enabler 144 comprises address book XDMS 148, and address book XDMS 148 can comprise contacts or to the link of the contacts of system 100/quote.
Can the address book storer 142 shown in Fig. 1 be configured to server or database that each user's addresses book on the network is stored.Address book client 122 on the use equipment can conduct interviews to this storer 160, revises, synchronous etc.
Because additional address book server can provide (host) or provided by other Virtual network operators in other network domains, another assembly on the network side 110 can be a remote address book server 170.Remote address book server interface can allow the interaction between the credible address book system in one or more network domains.
Another assembly of network side 110 can be based on traditional address book system 150 of network.The tradition address book system is the address book system that possibly exist.For example, Facebook
TM, Outlook
TM TMContact persons etc. are Already on the network side.These legacy systems are used to manage individual contact person and address book information, and they are based on network.
Turn to Fig. 3 now, another sample address book system 300 is provided.As shown in the figure, use network side 310 and equipment side 320 to come configuration-system 300.Can equipment side 320 be configured on any suitable equipment 321 that possibly use the public address book at least in part.Example apparatus comprises Wireless Telecom Equipment, for example, and cell phone, personal digital assistant, bidirection pager, smart phone, portable computer or other this equipment.Can equipment side 320 be configured at least in part on wireline equipment, for example personal computer, laptop computer or the like.Alternatively, can one or more equipment side assemblies (for example, the CAB client 322) be embodied as the part of network side 310.If the equipment side assembly is embodied as the part of the address book system client in the network, then can uses the interface between equipment and equipment side assembly to dispose this system.In with the realization of client configuration in network; Can the passage that use one or more agreements (this agreement defines this interface between equipment and the based on network client) be optimized; To reduce the tediously long of request; And the expense that is associated of reduction and specific protocol (for example, SIP order/notice).This optimization can improve the battery life of equipment.If there is channel selecting, the agency on the equipment (for example, channel selecting agency or mechanism) and said based on network client/equipment side assembly can provide the means of consulting passage.Between equipment side 320 and network side 310, can also there be different passages.Similarly, if there is channel selecting, the assembly on assembly on the equipment side 320 and the network side 310 can provide the means of consulting passage.Simple HTTP interface is the example of passage.
With reference to figure 3, XDM enabler 344 can provide the function in search contact source.XDM enabler 344 provides the interface XDM-5 based on limited XQuery, and being stored in search perhaps can be by the XML document of XDMS 346 visits among the XDMS346.XQuery by the W3C definition is the standard mechanism of search XML document.
Especially, use interface XDM-5 and XDM-7 to carry out contact person's function of search, wherein; On XDM-5, send client-requested to XDM enabler 344; And XDM enabler 344 uses XDM-7 to communicate by letter with interaction function module 342, externally to search on catalogue or the source.At the search agent place of XDM enabler 344, the result from inner (for example, CAB XDMS346) and external source/catalogue (for example, using interaction function module 342) is concentrated.
Though aforementioned system and method (for example are stored in internal data memory for search; CABXDMS) information in is useful; Yet it does not provide searching request (for example is addressed to out-list; Third party's network directory is like Yellow Page TM, 411 Catalogue assistants etc.) and manage mode from the data (that is, suppose to operate out-list and discern searching request) of these out-lists from address book system.
XQuery is the powerful solution that is used at the enterprising line search of XML document.Yet in order in the background of for example inquiring about a plurality of associated person informations source, to let XQuery work good, XQuery requestor (for example, client or for example other any entities of web service) will be appreciated that the employed data layout of target source.In addition, the XQuery requestor will be appreciated that whether can be the XML form with the data representation that returns from the source.In some cases, requirement will be from the data representation of target source for the XML form be used for the purpose of Xquery, possibly not be efficiently or difficulty.
Among this paper; Provide to associated person information or contacts and (for example searched for multiple source; Comprise the CAB server and by the out-list that the service provider provided, this CAB server has according to CAB user's general public information and according to the private information of " friend " of search subscriber) method.Under a situation, " friend " can be so that the different contacts details can obtain for the requestor with common features (for example, exclusive club member).Under another situation, based on requestor's voucher, " friend " can be so that the different contacts details can obtain for the requestor.Under another situation, " friend " can so that with before the contact details in obtainable past compare, can obtain the different contacts details.Right that can the memory access contact details has perhaps been stored actual contact details itself, and perhaps friend makes and can use another accessible different contacts details.In an embodiment of native system and method, use other resources the standard x ML document that must adhere to.In another embodiment, use with the interface based on HTTP of standard x ML document as target.In another embodiment, native system and method are kept the copy of selecting public information and pointer or the URI that points to this resource.Be selected with the information that is used for keeping this locality and can be based on trial method (heuristics).Can upgrade these copies of selecting public information regularly.From the keyword that search string, uses or for example HTTP interface provide based on the mapping of the searching request of XQuery to address date; Can be based on trial method; Wherein, can keep trial method according to the user in the following manner: make search operation more effective; If perhaps multilingual is mixed in the search string, the result from user's angle see be still desired.In certain embodiments, can be based on some characteristics to sort result and/or filtration.For example, can be based on coming address sort such as distance to customer location.In another example, can friend's address information be risen to the most significant point (for example, the top of tabulation) in the address list.Can with the user's addresses item with a plurality of telephone numbers be placed as make that the contact person who does not more expect can the address entries of " in the network " be risen to other is alternative more than.
Though OMA CAB document has been specified four kinds of functions, provide the disclosure with main concern contact person function of search.Particularly, the disclosure provides and has been used for supporting search out-list (for example, Yellow Page
TM, 411 Catalogue assistants etc.) system and method.Through with the address book searches formal definition of standard for search is addressed to out-list, can measured XQuery request and/or keyword character string mechanism carry out the search out-list.Though the example that this paper illustrated and described is (for example, HTTP) to provide, and do not mean that the disclosure is restricted to the agreement based on the IP agreement about the agreement of internet protocol-based (IP).In fact, in other embodiments, can for use such as SIP or the agreement the proprietary protocol.In addition, though provide about extend markup language (XML) in the example of this signal and description, and do not mean that the disclosure is restricted to XML.In fact, can use other language, for example, broad sense SGML (GML), HTML(Hypertext Markup Language), extensible HyperText Markup Language (XHTML) etc.
When using the XML language, also can relevant mime type and XML pattern (schema) be defined as and be used for (for example, HTTP) transmitting XML document or fragment through host-host protocol.A kind of protocol method that is used to ask like this is HTTP POST.
Address book enabler (for example, the specified CAB framework of OMA) provides the mechanism of searched for contact information.It is intended to provide from the interior searched for contact information of main frame public address book system, long-range public address book system and/or the available external data base of service provider (for example, Yellow Page TM) to public address book user.The associated person information that can be used for search operation receives public address book user's authorization rule and service provider's domination of strategies.
With reference now to Fig. 4,, the exemplary search method is described about AS/Organization Chart.As shown in Figure 4, search client/requestor 410 (for example, the client shown in Fig. 1 122) makes request via interface 415 to application server 420.Application server 420 can be the agency's who is configured to address book server 340 shown in the address book server shown in Fig. 1 140 or Fig. 3 an XDM enabler 344 for example.Searching request can comprise XQuery and/or keyword character string expression, and it is based on by the defined standard x ML search data form of application server 420 ((host) that for example, provided by the interaction function in the application server or contact person's function of search).After in the alternative realization that will describe with reference to figure 5; This standard format can also be provided by search agent; This search agent can be taken on the concentrating of central point and Search Results of all searching request, then with the concentrated client that sends it back of this Search Results.
The standard x ML form of application server 420 can be with application server 420 employed or data source 430 compatibilities that can visit through other modes.Data source/catalogue 430 can comprise with the next item down or multinomial: PCC XDMS, address book XDMS and external data source.Standard x ML form can minimize the native format of data source and the data conversion process between the standard search form, thereby has promoted harmless in fact data conversion.Can address book server and/or XDM enabler implemented or be configured to application server at least in part, perhaps implement or be configured on address book server and/or the XDM enabler.Interface 425 definition shown in Fig. 4 or made things convenient for mutual between application server 420 (for example, the search agent in interaction function or contact person's function of search or the XDM enabler) and the data source/catalogue 430.
The common interface or the API that can be supported based on the entity that out-list is provided (for example, service provider) alternately between out-list that comprises in data source/catalogue 430 and the application server 420.In order to make that data can will be the standard x ML search form that defines in the application server from the data conversion of external source by the Xquery visit from search requestor.In an example, before searching request, can be the standard search form to carry out preformatting or conversion (for example, with non real-time mode) from the data of external source.In another instance,, can carry out in real time format or conversion from the data of external source through native data formats and the one or more mappings between the standard search form of definition out-list (or approaching real-time).In this case, maybe based on this mapping will be original Xquery request (that is, from search client/requestor 410 to application server 420) convert the specific inquiry of out-list in real time into (perhaps near real-time).In specific realization, the perhaps approaching in real time real-time format or the conversion of data can be more effective, because it searches for provider to the third party who operates and/or keep out-list greater flexibility is provided.For example, with opposite, be provided at standard x ML form and out-list and use the mapping between the native format just enough carrying out conversion from all data of out-list.
Turn to Fig. 5 now, described another exemplary search method.As shown in Figure 5, search client/requestor 510 (for example, the client shown in Fig. 1 122) makes request via interface 515 to application server 520 (for example, the address book server 140 shown in Fig. 1).Searching request can comprise the Xquery and/or the keyword character string expression of the standard x ML search data form that defines or use based on application server 520.As shown in Figure 5, application server 520 comprises search agent 522 and XDMS 524, and XDMS 524 provides (host) standard search XML form and can operate the form with application standard search XML.XDMS 524 and aforesaid CAB XDMS 346 (Fig. 3) can be similar or different.XDMS 524 can be through two-way mode application standard search XML form.That is, XDMS 524 can: 1) Xquery that receives (from search client/requestor 510) is mapped to the specific inquiry of outside external source; And 2) will be mapped to standard format from the result that external source receives, and can search for and/or report back client 510 through it with it.XDMS 524 can be a logic function.In addition, XDMS 524 can be an assembly independently, perhaps can be provided by the interaction function module in the application server (for example, the frame 342 of the frame 260 of Fig. 2 or Fig. 3) or contact person's function of search (for example, the frame 250 of Fig. 2).Can search agent 522 be configured to the concentrating of central point and Search Results of searching request, then with the concentrated client that sends it back of Search Results.
When application server 520 receives searching request; Search agent 522 can be with the request direct repeating system to compatible data source 530; This compatible data source 530 is inner, believable or known, under the situation that need not carry out reformatting or conversion, correctly to explain and to respond searching request.As shown in the figure, compatible data source 530 can comprise PCC XDMS 532 and address book XDMS 534, yet, other associated person information/data sources can be provided.Comprise (promptly in searching request " incompatible "; The data or the associated person information source of the data that are not configured to accept, explain and/or respond the request of XML form or return the XML form) the situation of inquiry of outside or third party's data source/catalogue 536 under; Search agent 522 can be cooperated (for example, being provided by interaction function) to communicate by letter with data source/catalogue 536 with XDMS 524.
XDMS 524 can carry out the native format of outside or third party's data source 536 and the data conversion process between the standard XML search form, thereby promotes harmless in fact data conversion.Can carry out this conversion process (for example, the frame 520 of the frame 420 of Fig. 4 or Fig. 5) by the mapping function in the application server.In addition, can both carry out this conversion by the interaction function in the address book server, contact person's function of search or its, this address book server can utilize interface or the API that is provided by the external search data system that out-list is provided.After execution is carried out data conversion or reformatting to the data that receive from external source 536; XDMS 524 can send the data of conversion/reformatting to search agent 522; Then; Search agent 522 can be concentrated the data from each associated person information source (for example, shown source 532,534,536).At conversion or reformatting and after execution is concentrated alternatively, search agent 522 can be to the result of client 510 search reports request/inquiry.
In order to let the contact person in address book client executing address book server and other associated person information sources search for slave unit side direction network side transmission requests.Various requests possibly known by those skilled in the art that two examples have comprised simple keyword search and complicated XQuery search.
Simple keyword search model allows the address book user to come the requester network address book through utilizing simple keyword.Typical searching request form is:
<ContactSearch>
<--------------data of----searching request or response are placed on here
</ContactSearch>
Use the exemplary search requests of simple keyword to be:
Exemplary search requests based on the XML form of XQuery is:
In above example, < Contact Search>is the root node of searching documents, is public for the searching request from the client to the server with from the search response that server is got back to client.< ContactSearch>unit can comprise < Request>perhaps < Response>unit.
< Request>comprises the searching request container of data unit with XML form.Request (Request) unit can comprise perhaps < XQuery>unit of < Keyword>unit.
< Keyword>is the unit of carrying the actual search data.In other words, through this parameter the keyword of search from the unit of network address book system described.The data type of this yuan is " character string ".This yuan can comprise attribute " caseSensitive ", and it indicates whether and search for the case sensitive mode.Type is a Boolean type, has following enumerated value { " true ", " false " }.In one embodiment, default value is " false ".In addition, this yuan can comprise attribute " maxResults ", and it has defined the maximum number of outcomes that can return, and it is an integer.If do not specify this attribute, can Use Defaults.In above example, maximum result is defined as 50, indication can be returned 50 results at most at the some place that search stops, and abandons or ignores remaining response.
< XQuery>is the unit of carrying the searching request data that meet W3C Xquery form.Use this yuan to inquire about based on network address book system, to have the complex query of specified criteria.This yuan comprises attribute " maxResults ", its pointer to XQuery search the maximum number of outcomes that should return.Alternatively, this attribute can have default value (for example, 10 results).Type is " integer ".
Also (for example to local address book storer or another; Company or enterprise) under at least one situation of searching for and finding to mate in the address book storer; Can this coupling be incorporated among the result who receives, as a part the response of XQuery searching request (the perhaps searching request of other passages response).If will present to the maxresults of search subscriber or assembly; Promptly maximum number as a result; (hereinafter; The maximum number of outcomes that will present to search subscriber or assembly is also referred to as maxresults) be set to a value, and the number sum of the number of local coupling and the coupling returned as the response (the perhaps searching request of other passages response) of XQuery searching request is higher than maxresults, then needs special consideration how to handle numerous result.The sum that perhaps presents coupling, the sum that perhaps presents coupling does not surpass the value of maxresults.If demonstrate the value that does not surpass maxresults, the searching request of XQuery or other passages can be indicated desired result in the initial maximum number or first response.Follow-up XQuery searching request response can comprise the result of maxresults number.In another embodiment, the equipment side assembly is incorporated Search Results into, and only presents maxresults coupling.
< dataSource>is the unit of indication or definition (inner and/or outside) data source, and wherein, this data source should be employed searching request.Correspondingly, dataSource unit is used to launch (at least in part) searched for also in a plurality of associated person informations source concentrate a characteristic from the matched data in these associated person information sources.Data source (data Source) unit can assign or define one or more data sources (for example, a plurality of XDMS, AUID or a plurality of out-lists), to be used for the associated person information search operation.DataSource unit can indicate the data source that be included in the search.Alternatively, also can the indicate data source that from search, is excluded of the text-string after the dataSource unit.
The keyword of just being searched for indicated in word in the above keyword search " example ".Thereby for example, if the user is searching for All Contacts in the Dallas (perhaps have to the link of Dallas or quote), keyword search can be based on word " Dallas " so.For this reason, can be to the address book client feedback result's relevant tabulation with Dallas.As the result of searching request, receive response from application server at the client place.The tabulation that will produce possible outcome from the result of application server or response is other data structures perhaps.Example response is:
Wherein, < Response>is container unit, comprises the searching request result who gets back to client from server.Response (response) unit can comprise one or more < Result>unit.
< Result>is the unit that comprises based on the single result of searching request.For a plurality of results, by server bear results (Result) unit sequence.This yuan comprises " userId " attribute, unique identifier of the contact person among its indication result.This result can also comprise < dataSource>unit.
< dataSource>is the unit that the data source of Search Results is returned in indication.Can use data source information to allow the user to get in the territory of external search provider, further mutual to carry out.
In some instances, can be to the ordering of the unit of the result (Result) in the response with server configures.For example, compare, can in response, earlier present also the people's who is complementary with some adeditive attribute associated person information (for example, address) with the people's of not mating adeditive attribute associated person information.For example; Have identical native place or the people/resource in the same area in native place or adjacent postcode; In the address book of search subscriber, come to light can in list of matches, receive different with people/resource that the people/resource with same name of in the public address book, finding is not inconsistent or a preferred position (for example; Higher to lower, perhaps opposite).
Owing to can return a limited number of result elemenet (for example, first), can perhaps alternatively, carry out the unit (for example, application server) of search in the network and carry out certain ordering/filtration by client according to maxResults acquiescence or appointment.Filtration can Use Defaults, for example, and native place, other shared attribute.Yet searching request can also comprise the value that some are used to filter.In addition; Can utilize user profiles/preference to come the search data of being returned is sorted/filters; The part that this user profile/preference for example can be stored in the address book server (for example; User account/profile 210 of Fig. 2) or in the part (for example, User Preferences XDMS) of XDM enabler (for example, the frame 144 of Fig. 1).The priority of this filter value can be set in addition.The default setting of user profiles/priority can be different for each user, and can confirm (for example, based on past searching request) through trial method.
With reference now to Fig. 6,, the example message transmitting-receiving figure that is used for describing the exemplary method of searching for a plurality of associated person informations sources (for example, shown source 606 and 608) is provided.In Fig. 6; To corresponding application server 604 (for example; Can with server 140,340 (collaborative), 420 and 520 similar address book servers with XDM enabler 344), can carry out authentication and authorization to search client 602 (can be similar with 510 or different) with client 122,322,410.In addition, to the corresponding address book server, can be XDMS (its can be included in application server 520 similar application servers 604 in) have been carried out authentication and authorization.
Shown in the arrow among Fig. 6 610, the searching request that client 602 is sent to associated person information or contacts to application server 604.Can recognize in some instances, can arrow 610 indicated searching request communication or message directly be sent to the address book server according to the exemplary architecture of anticipating shown in Fig. 1.Yet, in other instances, can arrow 610 indicated searching request communication or message be sent to the address book server indirectly.That is, can searching request communication or message be directed to XDMS (agency who takes on the address book server) according to the exemplary architecture of illustrating among Fig. 3, thereafter, XDMS can send or be relayed to the address book server with this searching request communication or message.No matter which entity receives searching request; In response to receiving searching request; Application server 604 can will send to application server data source 608 (for example, PCC XDMS, address book XDMS) and external data source 606 respectively by arrow 620 and 640 indicated searching request in fact simultaneously.Based on the searching request of being sent 620,640, application server 604 receives search response 630 and 650.To respond 630 and turn back to application server 604, turn back to application server 604 from external data source 606 and will respond 650 from application server data source 608.Can recognize that when external data source 606 did not provide the data of XML form standard or desired, the reception of response 650 can relate to real-time or approaching real-time data conversion.As communicate by letter shown in the arrow 660, application server can be concentrated the search response from each source 606 and 608, can be with the response of Search Results merging to form.As communicate by letter shown in the arrow 670, application server 604 sends the response that (for example, via the interface 415 of Fig. 4 or the interface 515 of Fig. 5) comprises Search Results to client 602.Can recognize, can indicated by arrow 660 result is concentrated before, afterwards or during, the result from each source is sorted/filters.
With reference now to Fig. 7,, another information receiving and transmitting figure that is used to describe another exemplary method of searching for a plurality of associated person informations source is provided.In the figure of Fig. 7, should be appreciated that with non real-time mode and carry out searching request external data source.That is, it is received to be employed server 704 from the data of external data source/catalogue 706, by conversion, be mapped to standard format, perhaps before the searching request from client 702, is processed and stores.Like this, having prevented or minimized in fact maybe be owing to the operating lag that the data reformatting/data conversion from external relation people information source is produced.
Shown in the arrow among Fig. 7 710, before application server 704 receives searching request from client 702, receive from external data source 706 and to have off-gauge or data of expectation (for example, non-XML) form.Through before searching request, receiving data from external data source 706; Application server 704 can be standard or desired XML search form with data conversion; This form by application server data source 708 (for example meets also; PCC XDMS, address book XDMS etc.) employed form/type, so that can be easily and visit data apace from each source from search client 702 or requestor's Xquery.As previously mentioned, can use the native data formats of out-list and the mapping between the standard search form, data are carried out conversion.The example criteria search form of operable XML form is:
Though aforesaid XML relates to basic or typically can be included in the associated person information/attribute in the standard search form, other XML standard search forms can comprise additional associated person information/attribute.For example, the standard search form can be or can use the subclass by employed identical XML form of the contacts of PCC or address book contacts item or XML form.In application server, use standard format will allow client executing from the Xquery request of client to this form; And (for example will allow outside perhaps third-party associated person information/metadata provider; Yellow Page TM etc.) its local data is transformed to standard format; Thereby make in response to the searching request of client, let its data be easier to visit, search and use.
With reference now to Fig. 8,, illustrated sample data conversion/mapping between first data structure format (by external data source output) and second data structure format (can store before the searching request and search for) to it.As shown in Figure 8, be configured to provide contact data or information (for example, vCard form etc.) with external data source with first data structure 820.First data structure 820 comprises: contact name; Tissue, address, telephone number (voice and fax), e-mail address (work and individual); And the website (for example, URL).Yet external data source can provide the data layout of the data with different pieces of information or different ordering/configurations.For example, first data structure from another external data source can comprise still less or additional information field.Like what scheme further to illustrate, second data structure 840 comprises: surname, name, telephone number, address, website (URL), geographic position, display Name, tissue and e-mail address.Second data structure 840 can be the example criteria search form of aforementioned XML form.
As shown in Figure 8, mapping 830 can be discerned the information field (for example, through keyword or data layout) of first data structure 820, and uses the information of first data structure 820 to fill the field of second data structure 840.For example, as shown in Figure 8, use mapping 830 to fill the surname and the file-name field of second data structure 840, mapping 830 can parse surname and name from the name field of first data structure 820.Can use similar or different techniques to fill other fields of second data structure 840.
Turn to Fig. 7 once more, indicated like arrow 720, the searching request that client 702 is sent to associated person information or contacts to application server 704.Can recognize in some instances, can arrow 720 indicated searching request communication or message directly be sent to the address book server according to the exemplary architecture of anticipating shown in Fig. 1.Yet, in other instances, can arrow 720 indicated searching request communication or message be sent to the address book server indirectly.That is, can searching request communication or message be directed to XDMS (agency who takes on the address book server) according to the exemplary architecture of illustrating among Fig. 3, thereafter, XDMS can send or be relayed to the address book server with this searching request communication or message.No matter which entity receives searching request, in response to receiving searching request, application server 704 can send to application server data source 708 (for example, PCC XDMS, address book XDMS) with arrow 730 indicated searching request.Based on the searching request of being sent 730, application server 704 receives search response 740 from application server data source 708.As communicate by letter shown in the arrow 750, application server 750 can be to concentrating from the search response of each source 706 and 708, to form the response that will merge from the Search Results in source 706,708.As communicate by letter shown in the arrow 760, application server sends the response that (for example, via the interface 415 of Fig. 4 or the interface 515 of Fig. 5) comprises Search Results to client 702.Can recognize, can arrow 750 indicated the result is concentrated before, afterwards or during, the result from each source is sorted/filters.
This paper has described each embodiment.Yet these embodiment are nonrestrictive, and provide from illustrative purpose.Thus, only if should be appreciated that indication or very clearly inconsistent in this article, all modifications and the equivalence of the theme that the disclosure is intended to cover in the claim to be stated with context.
Claims (30)
1. method by the performed searched for contact information of the server of address book framework, said method comprises:
Receive contact person's searching request from the client that is associated with said server or agency, said contact person's searching request specify to associated person information the catalogue that will search for, said catalogue is in the outside of said address book framework; And
Convert said contact person's searching request into external search request, said external search request has the form of being supported by this out-list.
2. method according to claim 1, wherein, said contact person's searching request comprises XML unit < dataSource >, said XML unit < dataSource>be used to discern to associated person information the catalogue that will search for.
3. method according to claim 1 also comprises:
After said conversion, send said external search request to said out-list;
Receive response, said response comprises the result relevant with said external search request; And
Said result is sent to said client or said agency.
4. method according to claim 3, wherein, said response also comprises XML unit < dataSource >, said XML unit < dataSource>is used to discern the catalogue that is associated with said result.
5. method according to claim 1, wherein, searching request specify to associated person information first out-list and second out-list that will search for, and said conversion comprises:
Convert said contact person's searching request into first external search request, said first external search request has first form of being supported by said first out-list;
Convert said contact person's searching request into second external search request, said second external search request has second form of being supported by said second out-list; And
Said first external search request and said second external search request are sent to said first out-list and said second out-list.
6. method according to claim 5 also comprises:
Receive first response from said first out-list, said first response comprises first result relevant with said first external search request;
Receive second response from said second out-list, said second response comprises second result relevant with said second external search request; And
Concentrate said first result and said second result.
7. method according to claim 6 also comprises: according to characteristic or attribute, among said first result and said second result at least one sorted, classifies or one of filter.
8. method according to claim 1, wherein, said contact person's searching request has the XQuery form, and based on standard x ML form.
9. method according to claim 8 wherein, provides said standard x ML form by the interaction function of said address book framework.
10. method according to claim 8, wherein, said standard x ML form is one of following:
Form by the contacts of the individual contacts cards of said address book framework management or address book; And
Subclass by the form of the contacts of the individual contacts cards of said address book framework management or address book.
11. method according to claim 1, wherein, said address book framework, said server, said client and said agency meet Open Mobile Alliance (OMA) blend address book (CAB) standard.
12. the method by the performed searched for contact information of the client of address book framework, said method comprises:
Create contact person's searching request, said contact person's searching request specify to associated person information the catalogue that will search for, said catalogue is in the outside of said address book framework; And
Send said contact person's searching request to server that is associated with said client or agency,
Wherein, said contact person's searching request makes said server convert said contact person's searching request into external search request, and said external search request has the form of being supported by this out-list.
13. method according to claim 12, wherein, said contact person's searching request comprises XML unit < dataSource >, said XML unit < dataSource>be used to discern to associated person information the catalogue that will search for.
14. method according to claim 12 also comprises:
Receive response from said server or said agency, said response comprises and the relevant result of said contact person's searching request.
15. method according to claim 14, wherein, said response also comprises XML unit < dataSource >, and said XML unit < dataSource>is used to discern the catalogue that is associated with said result.
16. method according to claim 12, wherein, searching request specify to associated person information first out-list and second out-list that will search for, and said contact person's searching request makes said server:
Convert said contact person's searching request into first external search request, said first external search request has first form of being supported by said first out-list;
Convert said contact person's searching request into second external search request, said second external search request has second form of being supported by said second out-list; And
Said first external search request and said second external search request are sent to said first out-list and said second out-list.
17. method according to claim 16, wherein, said contact person's searching request also makes said server:
Receive first response from said first out-list, said first response comprises first result relevant with said first external search request;
Receive second response from said second out-list, said second response comprises second result relevant with said second external search request; And
In said first result and said second result set, to be sent to said client.
18. method according to claim 17, wherein, said contact person's searching request also makes said server that in said first result, said second result and said first result and said second result's the centralized list at least one sorted.
19. method according to claim 12, wherein, said contact person's searching request has the XQuery form, and based on standard x ML form.
20. method according to claim 19 wherein, provides said standard x ML form by the interaction function of said address book framework.
21. method according to claim 19, wherein, said standard x ML form is one of following:
Form by the contacts of the individual contacts cards of said address book framework management or address book; And
Subclass by the form of the contacts of the individual contacts cards of said address book framework management or address book.
22. method according to claim 12, wherein, said address book framework, said server, said client and said agency meet Open Mobile Alliance (OMA) blend address book (CAB) standard.
23. the method for a searched for contact information, said method comprises:
Make the interaction function of address book server be suitable for inquiring about second out-list of not supporting standard x ML form, said interaction function can be operating as associated person information is imported the blend address book storer from first out-list; And
Use said interaction function, will convert external search request into from the contact person's searching request based on said standard x ML form of address book client with form of supporting by said second out-list.
24. method according to claim 23 also comprises:
Dispose said interaction function, to concentrate result from a plurality of out-lists.
25. method according to claim 23, wherein, said contact person's searching request comprises XML unit < dataSource >, said XML unit < dataSource>be used to discern to associated person information second catalogue that will search for.
26. method according to claim 23, wherein, said contact person's searching request has the XQuery form.
27. method according to claim 23, wherein, said standard x ML form is one of following:
The form of the individual contacts cards in the said blend address book storer or the contacts of address book; And
The subclass of the form of the individual contacts cards in the said blend address book storer or the contacts of address book.
28. method according to claim 23, wherein, said interaction function, said blend address book storer, said address book server and said address book client meet Open Mobile Alliance (OMA) blend address book (CAB) standard.
29. method according to claim 23, wherein, said interaction function is configured to: receive data from said second out-list, and the said data of conversion are to carry out and the relevant search of said contact person's searching request.
30. method according to claim 29, wherein, said interaction function is configured to: when receiving said contact person's searching request, perhaps before receiving said contact person's searching request, the data from second out-list are carried out conversion.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US15020809P | 2009-02-05 | 2009-02-05 | |
| US61/150,208 | 2009-02-05 | ||
| PCT/US2010/022877 WO2010091012A1 (en) | 2009-02-05 | 2010-02-02 | System and method for aggregating multiple contact information sources in a network-based address book system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102576361A true CN102576361A (en) | 2012-07-11 |
Family
ID=42138967
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010800065186A Pending CN102576361A (en) | 2009-02-05 | 2010-02-02 | System and method for aggregating multiple contact information sources in a network-based address book system |
Country Status (6)
| Country | Link |
|---|---|
| US (1) | US20100198854A1 (en) |
| EP (1) | EP2394227A1 (en) |
| KR (1) | KR20110122834A (en) |
| CN (1) | CN102576361A (en) |
| CA (1) | CA2750960A1 (en) |
| WO (1) | WO2010091012A1 (en) |
Families Citing this family (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7958266B1 (en) * | 2003-07-30 | 2011-06-07 | Chen Sun | Multiple URL identity syntaxes and identities |
| US8489768B2 (en) * | 1999-12-31 | 2013-07-16 | Chen Sun | Associated URLVS in exchanges |
| WO2010148116A2 (en) * | 2009-06-19 | 2010-12-23 | Research In Motion Limited | System and method for remote management of dynamic address book application |
| US8626137B1 (en) | 2010-08-20 | 2014-01-07 | WhitePages, Inc. | Providing caller identification to mobile devices |
| ES2388389B1 (en) * | 2011-01-14 | 2013-09-03 | Telefonica Sa | PROCEDURE FOR MANAGING THE CONVERGENT ADDRESS BOOK CAPACITY. |
| KR20120085559A (en) * | 2011-01-24 | 2012-08-01 | 삼성전자주식회사 | Apparatus and method for search address book information |
| US20130047089A1 (en) * | 2011-08-21 | 2013-02-21 | Murali S. Kulathungam | System and Method to Consolidate and Update Digital Address Books |
| US8856101B2 (en) * | 2011-10-14 | 2014-10-07 | Normand Pigeon | Interactive media card |
| KR101922985B1 (en) * | 2011-12-08 | 2018-11-29 | 삼성전자주식회사 | Apparatus and method for inviting subscription of contact information |
| US9471682B1 (en) * | 2012-08-28 | 2016-10-18 | Google Inc. | Providing information associated with a profile owner in a social network system |
| US9406081B2 (en) * | 2012-10-26 | 2016-08-02 | Facebook, Inc. | Methods and systems for contact importing using a mobile device |
| US10080112B2 (en) | 2013-05-13 | 2018-09-18 | Hiya, Inc. | Unwanted caller and message sender identification for restricted communication devices |
| US10977677B2 (en) | 2013-07-15 | 2021-04-13 | Dropbox, Inc. | Contact importer |
| US9877185B2 (en) | 2013-09-13 | 2018-01-23 | Facebook, Inc. | Techniques for phone number and data management |
| US9253302B2 (en) | 2014-06-04 | 2016-02-02 | Google Inc. | Populating user contact entries |
| US9705993B1 (en) * | 2014-07-18 | 2017-07-11 | Sprint Communications Company L.P. | Information exchange between a directory assistance application server and a web-RTC engine |
| US9491288B1 (en) | 2015-06-03 | 2016-11-08 | Hiya, Inc. | Caller identification for restricted mobile devices |
| US10826986B2 (en) * | 2017-03-14 | 2020-11-03 | Ricoh Company, Ltd. | Information processing apparatus, merge method, and computer program product |
| JP6960819B2 (en) * | 2017-10-05 | 2021-11-05 | キヤノン株式会社 | Communication equipment, its control method, and programs |
| CN109257386B (en) * | 2018-11-19 | 2021-08-13 | 北京锐安科技有限公司 | Processing method, device, equipment and medium for broadcast television program list protocol |
| US20200193056A1 (en) * | 2018-12-12 | 2020-06-18 | Apple Inc. | On Device Personalization of Content to Protect User Privacy |
| US11586690B2 (en) | 2020-02-05 | 2023-02-21 | Apple Inc. | Client-side personalization of search results |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050149552A1 (en) * | 2003-12-23 | 2005-07-07 | Canon Kabushiki Kaisha | Method of generating data servers for heterogeneous data sources |
| CN1648900A (en) * | 2004-01-30 | 2005-08-03 | 株式会社东芝 | Content management apparatus and content management method |
| US20070041571A1 (en) * | 2003-07-14 | 2007-02-22 | Saurav Chatterjee | Directory integration in mobile systems |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5228116A (en) * | 1988-07-15 | 1993-07-13 | Aicorp., Inc. | Knowledge base management system |
| US5634053A (en) * | 1995-08-29 | 1997-05-27 | Hughes Aircraft Company | Federated information management (FIM) system and method for providing data site filtering and translation for heterogeneous databases |
| US5913214A (en) * | 1996-05-30 | 1999-06-15 | Massachusetts Inst Technology | Data extraction from world wide web pages |
| US7349907B2 (en) * | 1998-10-01 | 2008-03-25 | Onepin, Inc. | Method and apparatus for storing and retrieving business contact information in a computer system |
| US6496833B1 (en) * | 1999-11-01 | 2002-12-17 | Sun Microsystems, Inc. | System and method for generating code for query object interfacing |
| US6956942B2 (en) * | 2002-09-18 | 2005-10-18 | Sbc Properties, L.P. | Multi-modal address book |
| US20070276911A1 (en) * | 2003-07-11 | 2007-11-29 | Soujanya Bhumkar | Method and System for Transferring Contact Information and Calendar Events to a Wireless Device Via E-Mail |
| US7698307B2 (en) * | 2004-05-01 | 2010-04-13 | Microsoft Corporation | System and method for synchronizing between a file system and presence of contacts on a network |
| US8116444B2 (en) * | 2006-02-01 | 2012-02-14 | At&T Intellectual Property, L.P. | System and method of publishing contact information |
| US20070266156A1 (en) * | 2006-05-09 | 2007-11-15 | Wilkins John T | Contact management system and method |
| US20080235186A1 (en) * | 2007-03-23 | 2008-09-25 | Antti Laurila | Lawful Interception of Search Functionalities |
| KR20110044250A (en) * | 2008-07-23 | 2011-04-28 | 노키아 코포레이션 | Method and apparatus for address book updates |
-
2010
- 2010-02-02 CN CN2010800065186A patent/CN102576361A/en active Pending
- 2010-02-02 CA CA2750960A patent/CA2750960A1/en not_active Abandoned
- 2010-02-02 KR KR1020117020617A patent/KR20110122834A/en not_active Application Discontinuation
- 2010-02-02 EP EP10703745A patent/EP2394227A1/en not_active Withdrawn
- 2010-02-02 US US12/698,680 patent/US20100198854A1/en not_active Abandoned
- 2010-02-02 WO PCT/US2010/022877 patent/WO2010091012A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070041571A1 (en) * | 2003-07-14 | 2007-02-22 | Saurav Chatterjee | Directory integration in mobile systems |
| US20050149552A1 (en) * | 2003-12-23 | 2005-07-07 | Canon Kabushiki Kaisha | Method of generating data servers for heterogeneous data sources |
| CN1648900A (en) * | 2004-01-30 | 2005-08-03 | 株式会社东芝 | Content management apparatus and content management method |
Non-Patent Citations (1)
| Title |
|---|
| 无: "Converged Address Book Architecture"，Draft Version 1.0", 《CONVERGED ADDRESS BOOK ARCHITECTURE"，DRAFT VERSION 1.0》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CA2750960A1 (en) | 2010-08-12 |
| US20100198854A1 (en) | 2010-08-05 |
| WO2010091012A1 (en) | 2010-08-12 |
| KR20110122834A (en) | 2011-11-11 |
| EP2394227A1 (en) | 2011-12-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102576361A (en) | System and method for aggregating multiple contact information sources in a network-based address book system | |
| KR101098696B1 (en) | Sharing information between devices | |
| Wilde | Putting things to REST | |
| US20080141136A1 (en) | Clipping Synchronization and Sharing | |
| RU2337398C2 (en) | Method and device for data storage synchronisation in different data storages | |
| CN101277472B (en) | Method, equipment and system of synchronization of blog contents | |
| US20050160088A1 (en) | System and method for metadata-based distribution of content | |
| WO2018150244A1 (en) | Registering, auto generating and accessing unique word(s) including unique geotags | |
| KR20110008334A (en) | System and method for a converged network-based address book | |
| JP2009532785A (en) | System and method for searching different data stores via a remote device | |
| AU1394199A (en) | Method and apparatus for automatically disseminating information over a network | |
| CA2336836A1 (en) | Requirements matching | |
| CN102171690A (en) | System and method for implementing personalization and mapping in a network-based address book | |
| CN101253757A (en) | Communication system and communication terminal | |
| CN103119911A (en) | System and method for synchronizing the profile of a user in social networks and the user's personal contact card (PCC) | |
| KR100759186B1 (en) | System and method to provide web service that delivers information from semi structured web document and database | |
| López-de-Ipiña et al. | A context-aware mobile mash-up platform for ubiquitous web | |
| KR100570504B1 (en) | System And Method For Remote Management Of Personal Contents | |
| CN101179550B (en) | Personal homepage implementing method and system | |
| EP1715647B1 (en) | System and Method for Generic Data Mapping Between Wireless Component Applications and Application Data Sources | |
| Liu | Federating heterogeneous digital libraries by metadata harvesting | |
| Ilik et al. | InformationSharing Pipeline | |
| Alliance | White Paper on Mobile Social Network Work Item Investigation | |
| KR100368534B1 (en) | System and method of Electronic Data Interchanging and automatic explanatory file attaching through network | |
| WO2008023376A2 (en) | Live web pages system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20120711 |