CN101997899A

CN101997899A - CBUS-based user selection method and device

Info

Publication number: CN101997899A
Application number: CN2009101671182A
Authority: CN
Inventors: 李小娟; 刘海涛; 宋悦
Original assignee: Huawei Device Co Ltd
Current assignee: Huawei Device Co Ltd
Priority date: 2009-08-20
Filing date: 2009-08-20
Publication date: 2011-03-30

Abstract

The embodiment of the invention provides a control bus (CBUS)-based user selection method and a CBUS-based user selection device. The method comprises the following steps of: receiving user uniform resource identifier (URI) selection request information transmitted by a CBUS client; acquiring list name information in the user URI selection request information; acquiring a selection condition from the user URI selection request information or acquiring a selection condition from the list; acquiring a user uniform resource identifier (URI) from the corresponding list according to the list name information; acquiring user URI related information according to the user URI and the selection condition; and matching the user URI related information with the selection condition, and returning the user URI in accordance with the selection condition to the CBUS client. In the embodiment of the invention, by adding the list name information into the user URI selection request information, a CBUS server can perform user selection in Shared List XDMS.

Description

CBUS-based user selection method and device

Technical Field

The present invention relates to the field of communications, and in particular, to a CBUS-based user selection method and apparatus.

Background

With the development of telecommunication technology, services in the future are rich and varied, and in the session establishment phase of many services, a user who needs to join a session needs to be selected according to certain conditions, and the conditions are based on various information owned by the user, such as Presence information, Location information, and interests and hobbies information of the user.

Condition-Based user Selection (CBUS) techniques determine whether a user is the subject of a search by making a user Selection of various information that a requester can provide Based on certain conditions. The selection range of the users can be a group of users set by the requester or not, and the CBUS Server must use a search operation to find all users meeting the conditions.

The CBUS Server acquires information of a List user, a Group user, and a description (Profile) from a Shared Extensible Markup Language Document Management Server (Shared XDMS) including a Shared Group xml Document Server (Shared Group XDMS), a Shared policy xml Document Server (Shared policy XDMS), a Shared description xml Document Server (Shared Profile XDMS), and a Shared List xml Document Server (Shared List XDMS). In a Shared list (Shared list) document of a user, uniform resource identifier Lists (URI Lists) of the user have two types, one is a list reserved for a system, and the other is a list customized by the user.

Currently, in the CBUS technology, a requester can only include a single User address (User URI) and a Group identifier (Group URI) in a User selection range of a request message, where the Group URI is stored in a Shared Group XDMS, and the selection range cannot be limited to a User List under a List name in the Shared List XDMS.

Disclosure of Invention

The embodiment of the invention provides a CBUS-based user selection method and device, which are used for selecting a user URI in a Shared List XDMS.

The embodiment of the invention provides a method for selecting a user URI, which comprises the following steps:

receiving user URI selection request information sent by a CBUS client; obtaining list name information in the user URI selection request information; acquiring a selection condition in the user URI selection request information or acquiring a selection condition in a list corresponding to the list name information; acquiring a user Uniform Resource Identifier (URI) in a corresponding list according to the list name information; acquiring relevant information of the user URI according to the user URI and a selection condition; and matching the relevant information of the user URI with the selection condition, and returning the user URI meeting the selection condition to the CBUS client.

The embodiment of the invention also provides a method for sending the user URI selection request information, which comprises the following steps:

generating user URI selection request information, wherein the user URI selection request information comprises list name information; user URI selection request information is sent.

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

the receiving unit is used for receiving user URI selection request information sent by the CBUS client;

a list name acquisition unit, configured to acquire list name information in the user URI selection request information;

a selection condition obtaining unit, configured to obtain a selection condition in the user URI selection request information or obtain a selection condition in a list corresponding to the list name information;

a user list obtaining unit, configured to obtain a user URI in a corresponding list according to the list name information;

a user related information obtaining unit, configured to obtain related information of the user URI according to the user URI and the selection condition;

the matching unit is used for matching the relevant information of the user URI and the selection condition to obtain the user URI meeting the selection condition;

and the sending unit is used for returning the user URI meeting the selection condition to the CBUS client.

An embodiment of the present invention further provides a CBUS client, including:

a generating unit configured to generate user URI selection request information, where the user URI selection request information includes a list name;

a transmitting unit for transmitting the user URI selection request information.

By the embodiment of the invention, the List name (List name) is included in the user URI selection request information sent by the client, the CBUS Server can directly access the Shared List XDMS, accurately acquire the user URI under each List name, and also can acquire the selection condition of the user URI, thereby realizing the user selection based on the List.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a flow chart illustrating a CBUS-based information transmission method according to an embodiment of the present invention;

fig. 2 is a schematic structural diagram of a CBUS client according to an embodiment of the present invention;

FIG. 3 is a flow chart of a CBUS user selection method according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a CBUS server according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of another CBUS server according to an embodiment of the present invention;

FIG. 6 is another data flow diagram based on CBUS user selection according to an embodiment of the present invention;

FIG. 7 is another data flow diagram based on CBUS user selection according to an embodiment of the present invention;

FIG. 8 is another data flow diagram based on CBUS user selection according to an embodiment of the present invention;

FIG. 9 is another data flow diagram based on CBUS user selection according to an embodiment of the present invention;

FIG. 10 is another data flow diagram based on CBUS user selection according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Fig. 1 is a flowchart of a CBUS-based information sending method according to an embodiment of the present invention, including:

step 101, generating user URI selection request information, wherein the user URI selection request information includes list name information.

Step 102, sending user URI selection request information.

As an embodiment of the present invention, the user URI selection request information further includes selection condition information.

As an embodiment of the present invention, the user URI selection request information further includes a group URI and/or a user URI.

As an embodiment of the present invention, the user URI selection request information further includes at least any one of the following:

condition information, a group URI, or a user URI is selected.

Through the embodiment, list name information can be added into the user URI selection request information, so that the user can be selected in the shared list xml document server.

FIG. 2 is a schematic structural diagram of a CBUS client according to an embodiment of the present invention, which includes

A generating unit 201, configured to generate user URI selection request information, where the user URI selection request information includes a list name.

A sending unit 202, configured to send user URI selection request information.

Through the embodiment, the CBUS client can add listname information into the user URI selection request information, so that the user selection in the shared list xml document server is realized.

Fig. 3 is a flowchart of a CBUS-based user URI selection method according to an embodiment of the present invention.

Step 301, receiving user URI selection request information sent by the CBUS client.

Step 302, obtaining list name information in the user URI selection request information.

Step 303, obtaining a selection condition in the user URI selection request information or obtaining a selection condition in a list corresponding to the list name information.

And step 304, acquiring the user URI in the corresponding list according to the list name information.

And 305, acquiring related information of the user URI according to the user URI and the selection condition.

And step 306, matching the relevant information of the user URI and the selection condition, and returning the user URI meeting the selection condition to the CBUS client.

As an embodiment of the present invention, in step 303, obtaining a selection condition in the user URI selection request information includes: acquiring selection condition information in the user URI selection request information; acquiring a selection condition in a list corresponding to the list name information includes: and storing a selection condition in a list corresponding to the list name information, and acquiring the selection condition in the corresponding list according to the list name information. The selection condition information includes information indicating that the presentation information and/or the description information meet a certain condition, for example, the selection condition is online or offline, a certain preference, the presentation information includes online, offline, and the like, and the description information includes a preference, age, and the like.

As an embodiment of the present invention, step 302 further includes obtaining a group URI in the user URI selection request information;

or,

when list name information in the user URI selection request information is obtained, a group URI in the user URI selection request information is also obtained, and the user URI is obtained in a corresponding group according to the group URI;

or,

and when the list name information in the user URI selection request information is obtained, the user URI in the user URI selection request information is also obtained.

In step 305, the information related to the user URI at least includes any one of the following: presence information, description information, or location information of a user; the presence information includes, for example, whether the user is online or not, and the description information includes the preference, age, and the like of the user.

Through the embodiment of the invention, the user selection can be realized in the shared list xml document server according to the list name information sent by the CBUS client.

Fig. 4 is a schematic structural diagram of a CBUS server according to an embodiment of the present invention, where the CBUS server includes:

a receiving unit 401, configured to receive user URI selection request information sent by the CBUS client.

A list name obtaining unit 402, configured to obtain list name information in the user URI selection request information.

A selection condition obtaining unit 403, configured to obtain a selection condition in the user URI selection request information or obtain a selection condition in a list corresponding to the list name information.

A user list obtaining unit 404, configured to obtain the user URI in the corresponding list according to the list name information.

A user-related information obtaining unit 405, configured to obtain, according to the user URI and the selection condition, related information of the user URI.

A matching unit 406, configured to match the relevant information of the user URI with the selection condition, and obtain a user URI meeting the selection condition.

A sending unit 407, configured to return the user URI information meeting the selection condition to the CBUS client.

Through the above embodiment of the present invention, the CBUS server can perform user selection in the list according to the list name sent by the CBUS client.

Fig. 5 is another schematic structural diagram of a CBUS server according to an embodiment of the present invention, where the CBUS client includes:

like the receiving unit 401, the list name acquiring unit 402, the selection condition acquiring unit 403, the user list acquiring unit 404, the user-related information acquiring unit 405, the matching unit 406, the transmitting unit 407, described in fig. 4, further include:

a group identifier obtaining unit 408, configured to obtain the group URI and the selection condition in the user URI selection request information, obtain the user URI in the corresponding group according to the group URI, and send the user URI to the user related information obtaining unit 405.

A user identifier obtaining unit 409, configured to obtain the user URI and the selection condition in the user URI selection request information, and send the user URI to the user related information obtaining unit 405.

A selection condition obtaining unit 403, configured to obtain a selection condition in the user URI selection request information, and send the selection condition to the user related information obtaining unit 405; the selection condition acquisition unit 403 is required to acquire a selection condition from the list corresponding to the list name information if the user URI and the selection condition are stored in the list corresponding to the list name information. The group identifier obtaining unit 408 and the user identifier obtaining unit 409 respectively send the user URI to the user-related information obtaining unit 405, and the selection condition obtaining unit 403 sends the selection condition to the user-related information obtaining unit 405 to obtain the related information of the user URI.

As an embodiment of the present invention, the receiving unit 401, the list name obtaining unit 402, the selection condition obtaining unit 403, the matching unit 406, the sending unit 407, and the selection condition obtaining unit 409 are all integrated in a CBUS server;

the user list acquisition unit 404 is integrated with a shared list xml document server;

the user-related information obtaining unit 405 is integrated with a presence server and/or a shared description xml document server;

the group identification acquisition unit 408 is integrated with the shared group xml document server.

Fig. 6 is a data flow diagram based on CBUS user selection according to an embodiment of the present invention.

In this embodiment, the application scenario is that the requester Alice sends a request message to a CBUS Server (Server) through a CBUS client, and selects oma _ buddy, which is a user whose presence status is online. The user selection range in the request message is "oma _ buddy", and the selection condition is: the presence status is online.

Step 601: and a generating unit of the CBUS client generates user URI selection request information according to the requirement of a requester Alice, wherein the user URI selection request information comprises a list name and a selection condition.

The sending unit of the CBUS client sends user URI selection request information, wherein the user URI selection request information comprises a selection condition and a user selection range, and the user selection range is as follows: the list name is oma _ buddy, and the user selects the condition: the presence status is online.

Step 602: the CBUS Server receives the user URI selection request information through a receiving unit, and analyzes the user URI selection request information by using a list name acquisition unit and a selection condition acquisition unit, wherein the user selection range is as follows: and (3) analyzing the List name as "oma _ buddy", wherein the user range is stored in the Shared List XDMS, and the user selection condition is as follows: the presence status is online.

Step 603: the CBUS Server sends the List name to a Shared List XDMS, and the sending command adopts an HTTP GET request;

GET/resource-lists/users/sip:alice@example.com//resource-lists/list@name＝″oma_buddylist″/HTTP/1.1

Host：xcap.example.com

step 604: after receiving the request of step 603, the Shared List XDMS uses the user List obtaining unit to obtain the user URI under the List name, and then returns the user List to the CBUS Server;

HTTP/1.12000K

Etag：”eti87”

......

Content-Type：application/resource-lists+xml；charset＝”utf-8”

<？xml version＝”1.0”encoding＝”UTF-8”？>

<resource-lists xmlns＝”urn:ietf:params:xml:ns:resource-lists”

xmlns:oau＝”urn:oma:xml:xdm:resource-list:appusage”>

<display-name>Hermione</display-name>

<entrv>

</list>

</resource list>

step 605: the CBUS Server transmits the user URI ═ sip: hermone. blossom @ instance. com "and the user URI: + 43012349999" to the Presence Server (Presence Server).

Step 606: the Presence Server (Presence Server) acquires the online states of the two users by using the user-related information acquisition unit, and returns the online state information of the two users to the CBUS Server, wherein uri is status of "sip: Hermione.

Step 607: and the CBUS Server evaluates the received online information of the two users by using a matching unit, and analyzes to obtain that the online information of Hermione meets the user selection condition.

Step 608: the CBUS Server returns the URI of Hermione to the CBUS client of the requester Alice using the sending unit.

Fig. 7 is another data flow diagram based on CBUS user selection according to an embodiment of the present invention.

In this embodiment, the application scenario is that the requester Alice sends user URI selection request information to the CBUS Server, and selects a user who likes football from list name-a, URI-Bob @ example. The user selection range in the user URI selection request information is list name ═ list-a, the user URI ═ sip: Bob @ instance. com, the group URI ═ sip: mygroup _ Alice @ instance. com, and the selection conditions are as follows: the profile information is hobby football.

Step 701: and a generating unit of the CBUS client generates user URI selection request information according to the requirement of a requester Alice, wherein the user URI selection request information comprises a list name and a selection condition.

And the sending unit of the CBUS client sends the user URI selection request information.

The user URI selection request information comprises selection conditions and a user selection range. Wherein, the user selection range is as follows: list name ═ list-a ", user URI ═ Bob @ instance.com", and group URI ═ mygroup _ Alice @ instance.com "(mygroup _ Alice @ instance.com is a group URI, so this identification is tagged with a group identification in the user URI selection request information), the user selection condition is: the profile information is hobby football.

Step 702: the CBUS Server receives the user URI selection request information through a receiving unit, and analyzes the user URI selection request information by using a list name acquisition unit and a selection condition acquisition unit, wherein in a user selection range: the List name is analyzed to be stored in the Shared List XDMS, the URI is analyzed from the user URI selection request information to be a Group identifier, the Group identifier is stored in the Shared Group XDMS, and the user selection condition is as follows: the profile information is hobby football.

Step 703: the CBUS Server sends the List name to a Shared List XDMS, and the sending command adopts an HTTP GET request;

GET/resource-lists/users/sip:alice@example.com//resource-lists/list@name＝″list-a″/HTTP/1.1

Host：xcap.example.com

step 704: after receiving the request of step 703, the Shared List XDMS uses the user List obtaining unit to obtain the user URI under the List name, and then returns the user List to the CBUS Server;

HTTP/1.12000K

Etag：”est65”

......

Content-Type：application/resource-lists+xml；charset＝”utf-8”

<？xml version＝”1.0”encoding＝”UTF-8”？>

<resource-lists xmlns＝”urn:ietf:params:xml:ns:resource-lists”

xmlns:oau＝”urn:oma:xml:xdm:resource-list:appusage”>

<display-name>my closed friends</display-name>

<display-name>Joe</display-name>

<entry>

<display-name>Bert</display-name>

</entry>

</list>

</resource list>

step 705: the CBUS Server sends uri ═ sip: mygroup _ Alice @ example.com' to Shared Group XDMS to obtain the user list.

Step 706: the Shared Group XDMS acquires the user URI in the Group URI Group by using a user list acquisition unit, and then returns the Group URI user in the Group URI to the CBUS Server: lily @ example.com, rose @ example.com.

Step 707: the CBUS Server sends user URIs of Bob, Joe, Bert, Lily and Rose to Shared Profile XDMS to acquire preference information of the user URIs.

Step 708: the Shared description xml document Server (Shared Profile XDMS) uses the user-related information acquisition unit to acquire the preference information of the user URI, and then returns the information of Bob, Joe, and Lily hobbies for football, Bert hobbies for basketball, and Rose hobbies for volleyball to the CBUS Server.

Step 709: the CBUS Server evaluates the preference information of the user URIs by using a matching unit to obtain that Bob, Lily and Joe meet the user selection condition.

Step 710: the CBUS Server returns the user URIs of Bob, Lily and Joe to the CBUS client of the requester by using the sending unit.

Fig. 8 is another data flow diagram based on CBUS user selection according to an embodiment of the present invention.

In this embodiment, the application scenario is that the requester Alice sends user URI selection request information to the CBUS Server, and selects a user whose geographic location is in beijing and who likes football in list name "list-b" and list name "oma _ gradedcontacts". The user selection range in the user URI selection request information is list name ═ list-b ═ list name ═ oma _ grantecontacts ″, and the selection conditions are as follows: the presence information is: geographic location in Beijing; the profile information is hobby football.

Step 801: and a generating unit of the CBUS client generates user URI selection request information according to the requirement of a requester Alice, wherein the user URI selection request information comprises a list name and a selection condition.

The user URI selection request information comprises selection conditions and a user selection range. Wherein, the user selection range is as follows: the list name is "list-b", and the list name is "oma _ gradecontacts", and the selection conditions are as follows: the presence information is: geographic location in Beijing; the profile information is hobby football.

Step 802: the CBUS Server receives the user URI selection request information through a receiving unit, and analyzes the user URI selection request information by using a list name acquisition unit and a selection condition acquisition unit, wherein in a user selection range: both the List name-b and the List name-oma _ gradecontacts are located in the Shared List XDMS, and the selection conditions are as follows: the presence information is: geographic location in Beijing; the profile information is hobby football.

Step 803: the CBUS Server firstly sends a List name to a Shared List XDMS, namely 'List-a', acquires a user URI List under the List-a, and sends a command to adopt an HTTP GET request;

GET/resource-lists/users/sip:alice@example.com//resource-lists/list@name＝″list-b″/HTTP/1.1

Host：xcap.example.com

step 804: after receiving the request of step 803, the Shared List XDMS uses the user List obtaining unit to obtain the user URI under the List name, and then returns the user List under the List name to the CBUS Server;

HTTP/1.12000K

Etag：”est65”

......

Content-Type：application/resource-lists+xml；charset＝”utf-8”

<？xml version＝”1.0”encoding＝”UTF-8”？>

<resource-lists xmlns＝”urn:ietf:params:xml:ns:resource-lists”

xmlns:oau＝”urn:oma:xml:xdm:resource-list:appusage”>

<display-name>my closed friends</display-name>

<display-name>Joe</display-name>

<entry>

<display-name>Bert</display-name>

</entry>

</list>

</resource list>

step 805: the CBUS Server sends the List name ═ oma _ grantecontacts' to Shared List XDMS to obtain a corresponding user URI List, and also adopts HTTP GET request;

GET/resource-lists/users/sip:alice@example.com//resource-lists/list@name＝″oma_grantcontacts″/HTTP/1.1

Host：xcap.example.com

step 806: after receiving the request of step 805, the Shared List XDMS uses the user List obtaining unit to obtain the user URI under the List name, and then returns to the CBUS Server that the List name satisfying user oma _ granditcontacts is: lily @ example.com, Rose @ example.com;

HTTP/1.12000K

Etag：”bdj50”

......

Content-Type：application/resource-lists+xml；charset＝”utf-8”

<？xml version＝”1.0”encoding＝”UTF-8”？>

<resource-lists xmlns＝”urn:ietf:params:xml:ns:resource-lists”

xmlns:oau＝”urn:oma:xml:xdm:resource-list:appusage”>

<display-name>my closed friends</display-name>

<display-name>Lily</display-name>

<entry>

<display-name>Rose</display-name>

</entry>

</list>

</resource list>

step 807: the CBUS Server sends user URIs of Bob, Joe, Bert, Lily and Rose to Shared Profile XDMS to acquire preference information of the user URIs.

Step 808: and the Shared Profile XDMS acquires the preference information of the user URI by using the user related information acquisition unit, and then returns the information of Bob, Joe and Lily hobby football, Bert hobby basketball and Rose hobby volleyball to the CBUS Server.

Step 809: the CBUS Server sends user URIs of Bob, Joe, Bert, Lily and Rose to the Presence Server to acquire the position information of the user URIs.

Step 810: the Presence Server acquires the position information of the user URI by using the user related information acquisition unit, and then returns the information of Joe and Lily in Beijing, Bob in Shanghai, and Bert and Rose in Shenzhen to the CBUS Server.

Step 811: the CBUS Server evaluates the preference information and the position information of the user URIs by using a matching unit to obtain that Lily and Joe meet the user selection condition.

Step 812: the CBUS Server returns Lily and Joe's URI to the requester's CBUS client using a sending unit.

Fig. 9 is another data flow diagram based on CBUS user selection according to an embodiment of the present invention.

In this embodiment, an application scenario is that a requester Alice sends user URI selection request information to a CBUS Server, where the user URI selection request information is: the list name is "list-a", the user URI selection request information does not include a selection condition, the selection condition is already stored in the list-a, and the selection condition is as follows: hobby football. The storage format of the selection condition in the Shared List XDMS is as follows:

<display-name>my closed friends</display-name>

<display-name>Joe</display-name>

<entry>

<display-name>Bert</display-name>

</entry>

<oau:uriusages>

<hobbies>football</hobbies>

</profile>

</conditions>

</oau:urisages>

</list>

step 901: and a generating unit of the CBUS client generates user URI selection request information according to the requirement of a requester Alice, wherein the user URI selection request information is a list name.

The user URI selection request information is list name ═ list-a. The selection condition is stored in a list name ═ list-a', and specific information of the selection condition is as follows: hobby football.

Step 902: the CBUS Server receives the user URI selection request information through the receiving unit, analyzes the user URI selection request information by using the list name acquiring unit, and obtains that a list name is stored in a SharedList XDMS as a list-a, and if the user URI selection request information only comprises the list name and does not comprise a selection condition, the selection condition is stored in a list. Alternatively, it may be indicated that the selection condition is stored in the list by transmitting a specific character.

Step 903: the CBUS Server sends the List name to a Shared List XDMS, and the sending command adopts an HTTP GET request;

Host：xcap.example.com

step 904: after receiving the request of step 903, the Shared List XDMS obtains the user URI under the List name by using the user List obtaining unit, and then returns the user List under the List name and the selection condition thereof to the CBUS Server, and the selection condition obtaining unit of the CBUS Server obtains the selection condition information at the same time;

HTTP/1.12000K

Etag：”est65”

......

Content-Type：application/resource-lists+xml；charset＝”utf-8”

<？xml version＝”1.0”encoding＝”UTF-8”？>

<resource-lists xmlns＝”urn:ietf:params:xml:ns:resource-lists”

xmlns:ou＝”urn:oma:xml:xdm:resource-list:oma-uriusages”>

<display-name>my closed friends</display-name>

<display-name>Joe</display-name>

<entry>

<display-name>Bert</display-name>

</entry>

<oau:uriusages>

<hobbies>football</hobbies>

</profile>

</conditions>

</oau:urisages>

</list>

</resource list>

step 905: the CBUS Server sends the user URI of the user list to the Shared Profile XDMS to acquire the preference information of the user in the user list, wherein the user list comprises Joe and Bert in the example.

Step 906: and the Shared Profile XDMS acquires the preference information of the user URI by using the user related information acquisition unit, and then returns the information that Joe likes football and Bert likes basketball to the CBUS Server.

Step 907: the CBUS Server evaluates the preference information of the user URIs by using a matching unit to obtain that Joe meets the user selection condition.

And step 908, the CBUS Server returns the user URI of Joe to the CBUS client of the requester by using the sending unit.

In this embodiment, the application scenario is that a requester Alice sends user URI selection request information to a CBUS Server, where the user URI selection request information is: list name is "list-a" (selection condition 1 in list-a is: hobby football), user URI is David @ example.com, and selection condition 2 is that user status is: online.

For the processing of the above situation, when the requester sends the user URI selection request information, a tag is added to the reference of different selection conditions, for example, tag ═ 0 "indicates the selection condition already existing in the reference list; tag-1 indicates a selection condition in referring to the user URI selection request information.

Step 1001: and a generating unit of the CBUS client generates user URI selection request information according to the requirement of a requester Alice, wherein the user URI selection request information comprises a list name and a selection condition.

The user selection range in the user URI selection request information is: list name is "list-a", user URI is David @ example, com, and selection condition 2 in the user URI selection request information is: the user state is online. Here, the list name "list-a" has the selection condition 1: hobby football. The selection condition 1 is referred to as "list-a" for the list name, so the flag bit is 0, and the selection condition 2 is referred to as "David @ example" com for the user URI, and the data format is as follows:

SUBSCRIBE sip:cbuss@example.com SIP/2.0

Via：SIP/2.0/TCP alice.example.com；branch＝z9hG4bKwYb6QREiCL

Max-Forwards：70

To：CBUSS<sip:cbuss@example.com>

From：<sip:alice@example.com>；tag＝ie4hbb8t

Call-ID：cdB34qLToC@terminal.example.com

CSeq：1 SUBSCRIBE

Contact：<sip:alice.example.com>

Event：cbus

Expires：7200

Require：recipient-list-subscribe

Supported：eventlist

Accept：application/cpim-pidf+xml

Accept：application/rlmi+xml

Accept：multipart/related

Accept：multipart/signed

Accept：multipart/encrypted

Content-Type：application/rls-service+xml；type＝″application/rlmi+xml″；

Content-Disposition：recipient-list

Content-Length：247

<？xml version＝″1.0″encoding＝″UTF-8″？>

<rls-services xmlns＝″urn:ietf:params:xml:ns:rls-services″

xmlns:xsi＝″http://www.w3.org/2001/XMLSchema-instance″>

</inputlist>

</presence>

</conditions>

</rls-services>

step 1002: the CBUS Server receives the user URI selection request information through the receiving unit, analyzes the user URI selection request information by using the List name obtaining unit, obtains that a List name is stored in a Shared List XDMS as a List-a, and obtains that a selection condition 1 is adopted without referring to a selection condition 2 in the user URI selection request information if a corresponding List comprises the selection condition according to a flag bit tag of the List being 0.

Steps 1003, 1004, 1005 are the same as steps 903, 904, 905 in the embodiment shown in fig. 9.

Step 1006: and the CBUS Server sends the user URI david @ example to the Presence Server to acquire the online state information of the user.

Step 1007: and the Shared Profile XDMS acquires the preference information of the user URI by using the user related information acquisition unit, and then returns Joe hobby football and Bert hobby basketball to the CBUS Server.

Step 1008: the Presence Server acquires the state information of the user URI by using the user related information acquisition unit, and then returns the information that the David state is online to the CBUS Server.

Step 1009: the CBUS Server evaluates the preference information and the state information of the user URIs by using a matching unit to obtain that Joe and David meet the user selection condition.

In step 1010, the CBUS Server returns the user URIs of Joe and David to the CBUS client of the requester by using the sending unit.

In the embodiment of the invention, the CBUS client and the system can adopt a signaling control protocol (SIP) of an application layer or an XML Configuration Access Protocol (XCAP) to communicate.

The embodiment of the invention has the advantages that the list name is included in the user selection range, and the elements under the list name support the extension, so that the selection condition can be stored in the list name. By including List names in the user selection range, the CBUS Server can directly access the Shared List XDMS, accurately acquire the user List under each List name, and also can acquire the selection conditions in the user List or acquire the selection conditions in the user URI selection request, thereby realizing the user selection based on the List.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the computer program is executed. The storage medium may be a magnetic disk, an optical disk, a Read-On1y Memory (ROM), a Random Access Memory (RAM), or the like.

The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are merely exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims

1. A method for user URI selection, comprising:

receiving user URI selection request information sent by a CBUS client;

obtaining list name information in the user URI selection request information;

acquiring a selection condition in the user URI selection request information or acquiring a selection condition in a list corresponding to the list name information;

acquiring a user Uniform Resource Identifier (URI) in a corresponding list according to the list name information;

acquiring relevant information of the user URI according to the user URI and a selection condition;

and matching the relevant information of the user URI with the selection condition, and returning the user URI meeting the selection condition to the CBUS client.

2. The method according to claim 1, wherein obtaining selection conditions in the user URI selection request information comprises: when list name information in the user URI selection request information is obtained, selection condition information in the user URI selection request information is also obtained;

acquiring a selection condition in a list corresponding to the list name information includes: and storing the selection condition in a list corresponding to the list name information, and acquiring the selection condition in the corresponding list according to the list name information.

3. The method of claim 1,

when list name information in the user URI selection request information is obtained, a group URI in the user URI selection request information is also obtained;

or,

4. The method according to any of claims 1 to 3, wherein the information related to the user URI comprises at least any one of presence information, description information or location information of the user.

5. A method for sending user URI selection request information is characterized by comprising the following steps:

generating user URI selection request information, wherein the user URI selection request information comprises list name information;

user URI selection request information is sent.

6. The method according to claim 5, wherein the user URI selection request information further includes at least any one of:

selecting condition information, a group uniform resource identifier URI or a user URI.

7. A CBUS server, comprising:

8. The server according to claim 7, further comprising a group identifier obtaining unit, configured to obtain a group URI in the user URI selection request information, obtain a user URI in a corresponding group according to the group URI, and send the user URI to the user-related information obtaining unit.

9. The server according to claim 7, further comprising a user identifier obtaining unit, configured to obtain a user URI in the user URI selection request information, and send the user URI to the user-related information obtaining unit.

10. A CBUS client, comprising: