WO2009010004A1

WO2009010004A1 - Search system, search method and presence server

Info

Publication number: WO2009010004A1
Application number: PCT/CN2008/071637
Authority: WO
Inventors: Fang Ji
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-07-16
Filing date: 2008-07-14
Publication date: 2009-01-22
Also published as: CN101075266A; CN101075266B

Abstract

A search system, a search method and a presence server are provided. The search system includes search proxy, which is used to transmit search request to presence server; presence server, which is used to store presence information including personal information and perform search in user presence information according to received search request and return search result. The search method includes: according to search conditions in the received search request, performing search in presence information including personal information stored in presence server, then returning information meeting the search conditions. In the embodiment, because of storing all presence information in presence server, interaction between search proxy and presence server and XML document management server is avoided, and interface complexity degree is reduced, and search efficiency is improved, and system structure becomes simple and user data needn't repetition.

Description

Search system, search method and rendering server

Embodiments of the present invention relate to the field of mobile communications, and more particularly to a search system, a search method, and a presentation server. Background technique

Currently, the user information of the network user includes the user's willingness to communicate, communication capability, communication device information, and user personal information. The user needs to search for qualified users according to certain information of other users (part of the user information).

The search proxy (Search Proxy, SP) is mainly to complete the document search function, that is, the following functions need to be implemented in the implementation: Receive the extension markup language (XML) document management client (XDMC) search request ; parse the request and forward the request to the XML Document Management Server (XDMS) of the domain, or forward the request to the XDMS processing of other networks; collect all the response messages of the XDMS, and then send them to the UE after combined filtering. In addition, the SP searches for user information as follows: XDMC sends a search request to the Aggregation Proxy (AP) to search for user personal information and online information (Search with User Profile & Online), and the AP forwards the received search request to the SP; SP First, the search condition is extracted, and then the XDMS is searched for the qualified user personal information; the XDMS returns the search result, and the SP receives the returned result and saves it to the local, and extracts the Uniform Resource Identifier (URI) of the user; The PS subscribes to the online information of these users; the PS returns the result; after all the user's subscriptions are completed, the SP combines the two results; the SP returns the combined result to the XDMC. Summary of the invention

An embodiment of the present invention provides a search system, a search method, and a presence server, which are used for searching. When the user information is used, the interaction between the search agent and the presence server and the XML document management server is not required, thereby reducing the interface complexity, improving the search efficiency, and making the architecture simple and the user data not repeated.

An embodiment of the present invention provides a search system, including:

a search agent for forwarding search requests to the presence server;

a presentation server, configured to store presence information including personal information, and perform a search in the presence information of the user according to the received search request to return a search result.

The embodiment of the invention further provides a search method, including:

Performing a search in the presence information including the personal information in the presence server according to the search condition carried by the received search request;

Returns information that matches the search criteria.

An embodiment of the present invention provides a presence server, including:

a database for storing presence information of the user including personal information;

Presenting a search agent, configured to perform a search in the presence information of the user stored in the database according to the received search request;

A server module is provided for maintaining the presence information.

Therefore, the search system and the search method of the embodiment of the present invention store the presence information in the presence server, so that the interaction between the search agent and the presence server and the XML document management server is not required, the interface complexity is reduced, and the search is improved. Efficiency, while making the architecture simple, user data is no longer duplicated. DRAWINGS

1 is a schematic diagram of a context of a search system according to an embodiment of the present invention;

2 is a schematic structural diagram of a search system according to an embodiment of the present invention;

3 is a flowchart of a search method according to an embodiment of the present invention;

FIG. 4 is a flowchart of presenting a user agent to publish user presence information in a search method according to an embodiment of the present invention; Figure. detailed description

In the embodiment of the present invention, the personal information of the user is maintained by the presence server (Presence Server), and all the information available for searching by the user is saved on the Presence Server. Therefore, as shown in FIG. 1 , it is a schematic diagram of the context of the search system according to an embodiment of the present invention. As can be seen from the figure, the XDMC 11 only needs to pass through the Session Initiation Protocol Core (SIP Core ) 12 and the Presence Server 13 . The interactive completion information is released. XDMC11 only needs to perform search request through AP14 and Search Proxyl5. In the background, Search Proxyl5 only needs to search in the presence information stored in Presence Serverl3, and the search result is directly returned to XDMC11, which makes the signaling simple. The architecture is simple and the search performance will be greatly improved.

Table 1 is a Schema (shared-profile Schema) of personal information defined in the prior art, in which content contained in the user's personal information can be seen.

Table 1

<?xml version:"1.0" encoding= ⁿ UTF-8"?>

<xs:schema

targetNamespace="um:oma:params:xml:ns:shared-profile"

Xmlns= ⁿ um:oma:params:xml:ns:shared-profile"

Xmlns:xs="http:〃 www.w3.org/2001/XMLSchema"

<!-- The root "shared-profile" element ~>

<xs: element name="shared-profile">

<xs: complexType>

<xs: sequence maxOccurs=,, 1,,>

<xs: element name="shared-profile" type="shared-profileType"/> </xs:sequence>

</ xs: complexType>

</xs:element>

<xs:complexType name="shared-profileType"> <xs:sequence>

<xs: element name= "user-information" type= ⁿ user-informationType"minOccurs='"/>

<xs: element name: "alias" type="aliasType" minOccurs="0"/>

<xs: element name= "display-name" type="display-nameType" minOccurs="0"/〉

<xs: element name= "allow-publication" type="xs:boolean />

<xs: element name= "allow-anonymity" type="xs:boolean />

</xs:sequence>

<xs: attribute name="uri" type="xs:anyURJ" use="required">

<xs:anyAttribute namespace=,,##other" processContents="lax" minOccurs=,,0,, maxOccurs="unbounded"/>

</xs :complexType>

<xs:complexType name ¹ ="user-informationType">

<xs:sequence>

<xs: element name= "name" type="nameType" minOccurs="0" maxOccurs=" l"/>

<xs: element name= "age" type="ageType" minOccurs="0" maxOccurs=" 1 "/>

<xs: element name= "address" type="addressType" minOccurs="0" maxOccurs=" 1,,/>

<xs: element name= "city" type="cityType" minOccurs=,,0" maxOccurs="l"/>

<xs: element name= "country"type="countryType" minOccurs= ⁿ 0"maxOccurs="1,,/>

<xs:element name= "email" type="emailType" minOccurs="0" maxOccurs="l"/>

<xs: element name= "gender" type="genderType" minOccurs="0"

maxOccurs=" 1,,/>

<xs: element name= "intention" type= ⁿ intentionType" minOccurs= ⁿ 0"maxOccurs="1,,/>

<xs: element name= "freetext"type="freetextType"minOccurs='O" maxOccurs= ^M 1 >

<xs: element name= "communication-type" type="communication-typeType" minOccurs=' " maxOccurs="l, />

<xs: element name= "hobbies" type="hobbiesType" minOccurs=' " maxOccurs=" 1,,/>

<xs: element name= "links"type="linksType" minOccurs ^=, "maxOccurs=" 1 "/> <xs: anyAttribute namespace=,,##other,, processContents="lax"minOccurs='maxOccurs="unbounded"/>

</xs: complexType>

<xs:complexType name="aliasType"><xs:simpleContent><xs:extensionbase="xs:string ⁿ ><xs: attribute ref="xml:lang"/></xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:complexType name="display-nameType"> <xs: simpleC ontent>

<xs:extension base="xs:string ⁿ ><xs: attribute ref="xml:lang"/></xs:extension></xs:simpleContent>

</xs:complexType>

</xs:schema> The Presence information can contain user information. As shown in Table 2, the user data model table defined for the prior art, that is, the Schema for Presence information, refers to the Schema definition of RFC 4479:

Table 2

<?xml version:" 1.0" encoding="UTF-8 " ?>

<xs: schema targetNamespace="um:ietf:params:xml:ns:pidf:data-moder'

Xmlns:xs="http://www.w3.org/200 l XMLSchema"

Xmlns="um:ietf:params:xml:ns:pidf:data-moder'

elementFormDefault="qualified" attributeFormDefault="unqualified">

<xs: include schemaLocation="common-schema.xsd"/>

<xs: element name="deviceID" type="deviceID_t">

<xs:annotation>

<xs:documentation>Device ID, a U N</xs:documentation>

</ xs: annotation

</xs:element>

<xs: element name="device">

<xs:annotation>

<xs: documentation>C ontains information about

The device</xs:documentation> </ xs: annotation

<xs: complexType>

<xs:sequence>

<xs:any namespace=,,##other,,processContents="lax"

minOccurs=,,0,, maxOccurs="unbounded"/>

<xs: element ref="deviceID"/>

<xs: element name="note" type="Note_t" minOccurs=' "/>

<xs: element name="timestamp" type="Timestamp_t" minOccurs=,,0"/> </xs:sequence>

<xs: attribute name="id" type="xs:ID" use="required"/>

</xs: complexType>

</xs:element>

<xs: element name="person">

<xs:annotation>

<xs: documentation>C ontains information about the

Human user</xs:documentation>

</ xs: annotation

<xs: complexType>

<xs:sequence>

<xs:any namespace=,,##other,,processContents="lax"

minOccurs=,,0,, maxOccurs="unbounded">

<xs:annotation>

<xs:documentation>Characteristic and status

Information</xs: documentation

</ xs: annotation

</xs:any>

<xs: element name="note" type="Note_t" minOccurs=' "/>

<xs: attribute name="id" type="xs:ID" use="required"/>

</xs: complexType>

</xs:element>

</xs:schema> The user's business information (including willingness information and capability information), device information and personal information are defined in the Data-Model. The personal information can refer to personal information belonging to any namespace, which justifies the personal information into the Presence information. Provided for convenience, and personal information can be modified and queried under the "person" node in the presence information, and can also be modified and queried, and thus the user information, including capability information, willingness information, device information And the personal information is stored in the user's Presnece information, so that the function of Search Proxy is added without changing the function of the existing Presence Server, the implementation is simple, the architecture is simple and clear, the signaling is simple, and the interaction with the XDMS is not required. Will greatly improve the search performance.

As shown in FIG. 2, it is a schematic structural diagram of a search system according to an embodiment of the present invention, which includes an Aggregation Proxy (AP) 2, which is used for authentication and routing of search requests, and a search proxy (Search Proxy) 3 for using an aggregation proxy. The routed search request is forwarded to the presence server; the presence server (Presence Server, PS) 4 is configured to store the presence information including the personal information, and search in the user's presence information according to the received search request, and return the search result.

As shown in FIG. 2, the presentation server 4 includes a database 40 for storing presence information of the user including personal information. A presence search proxy (Presence Search Proxy) 41 is configured to store in the database 40 according to the received search request. The user's presence information is searched; the presence server module 42 is used to maintain the presence information.

The search request is sent by the XML Document Management Client (XDMC).

Therefore, the search system of the embodiment of the present invention does not have any influence on the capabilities of the existing presence server. The search agent is presented as a logically independent module, but has the characteristics of common data with the PS, so it is called Presence Search Proxy.

The search method of the embodiment of the present invention includes performing a search in the presence information according to the search condition carried by the received search request, and returning the information that meets the search condition.

As shown in FIG. 3, it is a flowchart of a search method according to an embodiment of the present invention, and the detailed steps are as follows: Step 501: The XDMC sends a search request to the AP.

Step 502: The AP performs a permission check, and returns the check result to the XDMC. If the search request is the authorization information, step 503 is performed; otherwise, the process ends;

Step 503: After receiving the authorization information, the XDMC re-initiates the request to the AP.

Step 504: The AP routes the search request to a Presence Search Proxy. Step 505: The search agent searches in the Presence information of the user that the search agent carries according to the search condition carried by the search request, where the user searches for the search. Privilege control, in the User-Profile defined by the OMA, the "allow-publication" user controls whether the user's personal information is allowed to search, and the user's personal information that the user controls the search permission is not allowed to be searched;

Step 506, the rendering search agent returns the search result to the AP;

In step 507, the AP returns the search result to the XDMC.

Before performing the search, the user presentation information needs to be published. As shown in FIG. 4, it is a flow chart for presenting the user agent to publish the user presentation information in the search method according to the embodiment of the present invention. The detailed steps are as follows:

Step 401: Presenting a Presence User Agent (PUA) to issue Presence information of the user;

The PUA may be located on the user's terminal device, or on the application server, or in the network;

Step 402: The Proxy-Call/Session Control Function (P-CSCF) in the IMS core network sends the publishing request to the Serving-Call/Session Control Function (S-). CSCF );

Step 403: The S-CSCF checks the initial filter criteria (IFC) of the user, and determines a trigger rule.

Step 404, the S-CSCF delivers the publishing request to the PS according to the triggering rule;

Step 405, the PS checks the user's authority, passes the permission check; otherwise ends

Step 406, the PS stores Presence information including personal information, and returns a 200 OK response; Step 407, the S-CSCF sends the response message to the P-CSCF; Step 408, the P-CSCF delivers the response message to the PUA;

After the PS stores the Presence information, the PS can notify the user who sent the search request of the new Presence information including the personal information.

The above gives how to obtain the user's personal information on the PS. It is published to the PS through the user's publishing agent (which can be the user's terminal device or an application server, which can publish its information on behalf of the user).

E.g:

1. The presentation publishing agent of user A issues the user's presence information to the presence server, including the user's capability information, willingness information, device information, and personal information. Of course, the information can also be released separately, for example, only one capability is released in one release. Information and willingness information as well as device information, and at other times the device even publishes the user's personal information. In other words, the published information can be a piece of all the information.

2. After user B goes online, initiates a search request, and hopes to search for the city where the city is "Shenzhen", and the current "online" user is routed to the presence search agent, and the agent only needs to check the presence information of the current user. The city is "Shenzhen", and the current "online" is OK, and the qualified user information is returned to User B.

If you use the existing architecture, you need to go to the Profile XDMS to search for the user whose current city is "Shenzhen". After returning the eligible users, go to the presence server to subscribe to the presentation information of these users, and then find out the current The "online" user then returns the user who meets the two conditions to user B. This performance is clearly poor, resulting in slow search results, and regardless of which of the existing solutions, the Profile XDMS and the presence server endure a large amount of data and signaling interactions.

Therefore, embodiments of the present invention have the following advantages:

1. The rendering search agent no longer interacts with both Presence Server and XDMS at the same time, greatly improving performance;

2. According to the prior art, the user saves a personal information in the XDMS, and the Presence information The user's personal information can also be saved, resulting in data duplication, and the user experience is complicated. In the embodiment of the present invention, the XDMS is no longer used to maintain personal information, but the user's personal information is maintained on the Presence Server and embedded in the data-model definition. Under the "person" node, the data is not duplicated, which is convenient for user management and the user experience is more reasonable.

3. Searching only one piece of data can satisfy the user's search needs (you can search the user's personal information, ability information, willingness information and device information), which is simple and performance-enhancing;

4. The emergence of Presence Search Proxy based on Presence Server reduces network complexity;

5. The search scheme provided by the embodiment of the present invention is simple in structure and greatly improved in performance, without prejudice to the specification, in response to the user's search for the personal information and the presence information of the other users.

Therefore, the search system and the search method of the embodiment of the present invention do not require interaction between the search agent and the presence server and the XML document management server, thereby reducing interface complexity, improving search efficiency, and making the architecture simple, and user data is no longer repeat. The embodiments of the present invention are described in detail with reference to the preferred embodiments, and those skilled in the art should understand that the technical solutions of the embodiments of the present invention may be modified or equivalently substituted without departing from the technical solutions of the embodiments of the present invention. Spirit and scope.

Claims

Rights request

A search system, comprising:

a search agent for forwarding search requests to the presence server;

2. The search system according to claim 1, further comprising:

An aggregation proxy, configured to receive and authenticate a search request, and route the search request to the search agent;

The search system according to claim 1, wherein the presentation server comprises: a database, configured to store presence information of the user including personal information;

A server module is provided for maintaining the presence information.

4. A search method, characterized in that it comprises:

Returns information that matches the search criteria.

The search method according to claim 4, wherein the searching in the presence information including the personal information in the presence server according to the search condition carried in the search request includes:

After receiving the search request, the search request is checked for permission, if the search request is authorized information, the search request is re-initiated, and then the search is performed in the presence information including the personal information in the presence server.

The search method according to claim 4, characterized in that the personal information of the user who controls the search authority by the user is not allowed to be searched.

7. The search method according to claim 4, wherein before receiving the search request The method includes: storing the presented information of the released user including personal information.

The search method according to claim 7, wherein before the storing the presence information of the user including the personal information, the method further includes: checking the permission information, and storing the personal information including the personal information by the permission check Presentation information.

The search method according to claim 7, wherein the storing the presence information of the user including the personal information further comprises: notifying the user who sent the search request of the new presence information.

10. A presence server, comprising:

A server module is provided for maintaining the presence information.