WO2012013033A1

WO2012013033A1 - Method and system for processing request message

Info

Publication number: WO2012013033A1
Application number: PCT/CN2011/071079
Authority: WO
Inventors: 卢艳
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-07-27
Filing date: 2011-02-18
Publication date: 2012-02-02
Also published as: CN101909019A

Abstract

The present invention discloses a method and system for processing a request message. When there are multiple reception side clients which registers by using the same user identifier, a selection for the reception side clients is performed. The method includes: before transmitting a request message, a service server obtains the reception rule configuration information for the multiple reception side clients, and performs a selection for the multiple reception side clients according to the reception rule configuration information respectively corresponding to the multiple reception side clients (410); selection result information including a third unique identifier of the reception side client is carried in the transmitted request message, in order to indicate whether the reception side client permits receiving the request message (420). In the method and system of the present invention, when the multiple clients used by the reception side are online simultaneously, the service system performs a selection for the clients according to the preset different reception rules for each reception side client, to determine a final reception side client, and thus the user experience is improved.

Description

Request message processing method and system

The present invention relates to the field of communications, and in particular to an instant messaging (including a Converged IP Messaging (CPM) service, and an IMS service, a Rich Communication Suite (RCS), etc.) Processing system and method for request messages within. Background technique

Instant messaging is becoming more and more widely used. The instant messaging system distinguishes users by assigning different user identities (or accounts or addresses) to them, and the user uses this user ID to log in and register with each other. To improve the user experience, more and more instant messaging services support the ability to log in to multiple terminals simultaneously. Taking the instant messaging service as an example, a user can have a user identity and log in to register online at multiple different terminals.

Converged IP Messaging (CPM) enables intercommunication of multiple messaging services, provides unified messaging services, and provides a consistent and convenient messaging service experience. CPM's business forms include: CPM based on pager-mode paging mode, Large Message Mode CPM Message based on session-mode session mode, and other CPM session services based on session (CPM Session service). Before users can use these services normally, they need to register to log in to the CPM system, which is commonly referred to as online.

The CPM Address is the identifier used by the CPM system (known as CPM Enabler, CPM Service Engine) to distinguish different users in the system. To improve the user experience, in a CPM system, a user can have multiple CPM addresses and can be registered on multiple terminal devices, that is, online at the same time, so that users can use multiple terminals in different scenarios. If some The user logs in to the CPM system on the different terminal using the same CPM address, and when the user is the receiver of the CPM message (CPM paging message, CPM big message request message, and CPM Session request message), the CPM system is transmitting. When the CPM message arrives at the receiver, if the receiver user can configure different receiving policies for different terminal devices, specifically, different receiving policies such as meeting, dining, work, and off-duty are set to receive and manage. For example, if the user can set different senders' blacklists or whitelists for different terminals, it is undoubtedly close to the user's psychology, but the related solutions in the prior art are not given.

The above description uses the instant message such as a CPM message as an example to illustrate the background of the present invention. Similarly, for other services (such as SIP-based services), the selection process before the request message is sent to the specific receiver terminal, in the prior art. The same solution is not given. Summary of the invention

The technical problem to be solved by the present invention is to provide a processing system and method for a service request message including an instant message, a CPM service, an IMS service, and an RCS converged communication service, etc., where the request message is sent to the same user. Before multiple clients identified by the user, according to different receiving rules set for each terminal in advance, the service system performs client selection according to the receiving rules of each client of the receiving party, determines the final receiving client, and increases the user experience.

In order to solve the above problems, the technical solution of the present invention is implemented as follows:

A method for processing a request message, when the number of recipient clients registered by using the same user identifier is multiple, is used for selecting a recipient client; the method includes:

The service server obtains the receiving rule configuration information of the multiple receiving client before sending the request message, and selects the multiple receiving client according to the receiving rule configuration information corresponding to the multiple receiving client respectively;

The request message sent carries the selection result information including the third unique identifier of the receiver client to indicate whether the recipient client is allowed to receive the request message. Further includes:

Before the service server performs message processing, any one of the multiple receiver clients sends a registration message to the SIP/IP core network, and carries the first unique identifier of the receiver client in the registration message.

Further includes:

Any one of the plurality of recipient clients sets the receiving rule configuration information for the own client and/or other recipient clients registered with the same user identifier, and the receiving rule configuration information of the different receiving client passes the The second unique identifier of the recipient client obtained by the service server is distinguished.

The service server obtains the second unique identifier of the recipient client by any one of the following methods:

(a) after receiving the registration message sent by the receiver client, the SIP/IP core network forwards the registration message to the service server, and carries the second unique identifier of the receiver client;

(b) The service server sends a subscription message to the SIP/IP core network, and the SIP/IP core network sends a subscription notification message to the service server, where the subscription notification message carries a second unique identifier of the recipient client.

The service server obtains a third unique identifier of the recipient client by any one of the following methods:

(a) after receiving the registration message carrying the first unique identifier sent by the receiving client, the SIP/IP core network generates a third unique identifier according to the first unique identifier, and forwards the registration message to the service server. Carrying a third unique identifier of the receiver CPM client;

(b) The service server sends a subscription message to the SIP/IP core network, and the SIP/IP core network sends a subscription notification message to the service server, where the subscription notification message carries a third unique identifier of the recipient client.

The first unique identifier of the recipient client, the second unique identifier of the receiver client, The relationship between the third unique identifier of the receiver client is: the three identifiers are the same identifier or are different but have an association relationship;

The receiver client first unique identifier, the receiver client second identifier, and the receiver client third unique identifier may include at least one of the following three types: a client proxy identifier instance-id, or a device Identity, or globally routable user agent global resource identifier GRUU.

The service server is a converged IP message CPM participates in a functional entity;

The request message is a request message of a CPM paging message, or a request message of a CPM big message, or a request message of a SIP session;

The recipient client is a receiver CPM client.

The request message sent by the CPM participating functional entity is a real-time received CPM request message from a sender, or a non-real-time CPM request message.

The first unique identifier is a client proxy identifier, or is a device identifier;

The second unique identifier is a client proxy identifier, or a device identifier, or a global routable user proxy global resource identifier;

The third unique identifier is a client proxy identifier, or a device identifier, or a global routable user proxy global resource identifier.

A processing system for requesting a message, comprising: a service server, a user configuration information storage server, and a plurality of receiver clients registered with the same user identifier; wherein

The service server is configured to: before receiving the request message, obtain the receiving rule configuration information of the plurality of receiver clients that are registered by using the same user identifier, and receive the different receiving according to different recipient clients. The rule configuration information is used by the receiver client to be selected; and is further configured to carry the selection result information including the third unique identifier of the receiver client in the sent request message, to indicate whether the receiver client is allowed to receive the request. Message

The user configuration information storage server is configured to store the receiving rule configuration information of the plurality of recipient clients registered by using the same user identifier. The system further includes a SIP/IP core network, configured to receive a SIP/IP core network registration message sent by any one of the multiple recipient clients before the service server performs message processing;

The SIP/IP core network registration message carries the first unique identifier of the receiver client. In summary, the present invention provides a processing system and method for a service request message including an instant message, a CPM service, an IMS service, and an RCS converged communication service, etc., when the receiver uses multiple clients simultaneously online. In this case, according to different receiving rules set for each terminal in advance, the service system performs client selection according to the receiving rule of each receiving client, determines the final receiving client, and increases the user experience.

The technical solution described in the present invention is applicable not only to an instant messaging system, a CPM system, an IMS-based service system, or an RCS converged communication service, but also to other SIP-based service systems. DRAWINGS

1 is a schematic diagram of receiving policy configuration information of a receiver of a request message according to an embodiment of the present invention; FIG. 2 is a flowchart of a message processing scheme 1 of a service server according to an embodiment of the present invention; FIG. 3 is a service server pair according to an embodiment of the present invention; Flowchart of message processing scheme 2; FIG. 4 is a schematic diagram of a processing flow of a request message according to an embodiment of the present invention. detailed description

The present invention provides a processing system and method for a service request message including an instant message, a CPM service, an IMS service, and an RCS converged communication service. When the receiver uses multiple clients to be online at the same time, the service system The client selects according to the receiving rule of each receiving client, determines the final receiving client, and increases the user experience.

In general, an entity that implements all business functions on the network side (relative to the client) can be considered as a business server. In a specific application, an instant messaging system is taken as an example, a business service Is an instant messaging server, which can be a business system consisting of one or more functional entities;

For example, the service server includes a participating function entity and a control function entity of the CPM system. For example, in the IMS system, the SIP/IP core network is the IMS core network, and the service server is in the IMS system. Application Server (AS).

The present invention is also applicable to other SIP-based service systems. The service system architecture of the present invention is based on a SIP/IP core network architecture. In some network environments, the SIP/IP core network may be integrated with a service server. Unit, the present invention is equally applicable to such networking situations.

The present invention is directed to a terminal selection method for multi-receiving terminal messages, which is not limited by a specific service form. For other services (such as SIP-based services), the request message is sent to a specific recipient client. The present invention is equally applicable to the selection process according to the user configuration.

2 and FIG. 3 are two schemes provided by the present invention. Before the service server sends a certain message request to the message client, if the receiver user has multiple clients at this time, it is obtained according to the slave user configuration information storage server. The receiving rule configuration information is used as one of the selection conditions to select a client that satisfies the receiving condition, and then carries the unique identification information of the selected client in the message sent by the client, in scheme 1 (FIG. 1), for each selected one. The client sends a request message, and the message carries the unique identifier information of the selected client. In scenario 2 (Fig. 2), regardless of the number of selected clients, only one request message is sent, and the request message carries the unique identifier of all selected clients (or carries the unique identifier of all clients that are not selected).

In the following, the technology of the present invention is described by taking only the IP messaging service (including the request message of the CPM paging message, the request message of the CPM big message, and the request message of the CPM Session) as an example, and the technical solutions for other service systems are as follows: The content has a similar principle.

In a specific application, the user configuration information is stored in an XDM (XML Document Management) server in the form of an XML (Extensible Markup Language) document. The receiver user can use a CPM address to register on different clients. The participating function entity that belongs to the receiver, that is, the Terminating Participating Function, when the CPM request message is sent, is based on the slave configuration information storage server. That is, the receiving rule of each receiving client is obtained from the XDM server, and one of the filtering conditions for screening the plurality of CPM clients of the receiving party, and selecting a CPM request message that satisfies the receiving condition from the plurality of CPM clients The CPM client is received, and then a CPM request message is sent for each selected receiving CPM client, where the filtered unique identifier of the client is carried in the message.

System embodiment

Embodiment 1

The embodiment provides a request message processing system for converging IP messages, including: a participating functional entity (service server), multiple receiver CPM clients, a SIP/IP core network, and a user configuration information storage server;

The participating functional entity is configured to obtain a receiving rule of each client from the user configuration information storage server (XDM server) before sending the CPM request message to the plurality of receiving CPM clients satisfying the receiving condition, and check each client receiving a rule, so that the unique identifier of the receiving CPM client is carried in the sent request message;

The CPM message sent by the participating functional entity is a real-time received CPM request message from the sender, or a non-real-time CPM request message.

The user configuration storage server (XDM server) stores the receiving rule configuration information of each client, and distinguishes the receiving rule corresponding to the client by the unique identifier of the client.

The CPM client is used to provide a unique identifier for the client when registering, and is also used to access the user-configured storage server to maintain configuration information.

Method embodiment

Embodiment 1 This embodiment is a multi-client selection method of the CPM. The method includes the following steps: Step S101: The user uses the same CPM address to register with different CPM clients, and the registration message carries the first unique identifier of each client, for example, instance-id Logo.

Step S102: Through the registration of step S101, the SIP/IP core network obtains the first unique identifier of each client, instance-id„

Step S103: The participating functional entity subscribes to the SIP/IP core network for the first unique identifier instance-id of each client of the user, and obtains the first unique identifier of each client. Or the SIP/IP core network forwards the first unique identifier instance-id of each client to the participating functional entity by using a third-party registration message.

Step S104: The user directly or indirectly accesses the user configuration information storage server (XDM server) through a certain CPM client, and sets the user to receive the rule configuration information, and the user can receive multiple rule configuration information. Protection.

Step S105: The unique identifier of each client acquired by the participating function entity through the method described in step S103, the user specifies different receiving rule configuration information for each client including the client itself through a certain CPM client; The second unique identifier is used to distinguish different receiving rule configuration information of each client.

The second unique identifier of the client may be the same as the first unique identifier, or may be extended by the first unique identifier and associated with the first identifier.

Step S106: Before the participating function entity needs to send the received CPM request message to the CPM client of the receiver, the participating function entity acquires the receiving rule of each client, and selects the receiving rule according to the receiving rule configuration information as one of the filtering conditions. Which of the CPM clients of the recipient of the condition is. For example, if the receiving rule corresponding to a receiving client is a blacklist member of the request message, the message will be prohibited from being sent to the client. The CPM request message sent by the participating function entity may be a real-time received CPM message (a request message of a paging message or a request message of a CPM big message) or a request message of a CPM Session, or may be a condition that the condition is satisfied. (If the receiver client becomes unreachable from reachable), send a non-real-time CPM message, that is, deferred CPM message.

Step S107: For each CPM client that meets the receiving condition, the participating functional entity carries the third unique identifier of the receiving CPM client in the sent CPM request message, and the request message is routed to each receiving CPM via the SIP/IP core network. Client.

Taking the request message of the CPM paging message or the CPM big message as an example, after the participating functional entity selects the receiving client, the requesting message may be sent to each selected client, and the request message carries the third unique identifier of the receiving client. Based on this information, the SIP/IP core network routes the messages to Client 1 and Client 2. This scheme corresponds to Figure 2.

Taking the CPM Session request message as an example, after the participating functional entity selects the recipient client, it may send only one request message regardless of the selected recipient client, and the request message carries permission (or does not allow) to receive the request message. Based on this information, the SIP/IP core network routes the message to Client 1 and Client 2. This scheme corresponds to Figure 3.

The invention is further illustrated by the following application examples.

In the following application examples, user A currently uses CPM terminal as Device-A, and Device-A built-in CPM client as CPM client A. Assume that CPM address Addr-A is a CPM address of user A, and the CPM address belongs to Participate in functional entity A (denoted as PF-A);

User B uses the same CPM address to register with the CPM system on two different terminals. These two CPM terminals are respectively recorded as Device-Bl and Device-B2, and the CPM client built in Device-Bl is recorded as CPM client. Bl, the built-in CPM client of Device-B2 is recorded as CPM client B2; the CPM address belongs to CPM participating functional entity B (denoted as PF-B).

Applications

In this example, user A sends a CPM request message to user B (including the request message for CPM search). For example, the request message SIP MESSAGE of the call message or the request message SIP INVITE of the CPM big message or the request message SIP INVITE of the SIP session is used as an example, and the CPM participating in the function entity of the receiving party sends the received CPM message to the client before the CPM message is sent. End selection processing, including the following steps:

Step S301: User B uses the same CPM address to register on different terminals Device-B1 and Device-B2 through two different CPM client B1 and CPM client B2, and the registration message carries a unique identifier of each client, for example, Instance-idl and instance-id2.

Step S302: Through the registration of step S101, the SIP/IP core network obtains the unique identifiers of each client B, instance-idl and instance-id2.

Step S303: The participating functional entity subscribes to the SIP/IP core network for the unique identifier of each client of the user B, obtains the unique identifier of each client B, the instance identifier instance-idl, instance-id2, and/or global routable User agent global resource identifiers GRUUl, GRUU2.

Or the SIP/IP core network forwards each client unique identifier instance-idl and instance-id2 ( instance-idl, instance-id2, and/or GRUUl, GRUU2) to the participating functional entity through a third-party registration message.

Step S304: The user B accesses the user configuration information storage server (XDM server) directly or indirectly through the CPM client B1, and sets the user to receive the rule configuration information, and the user can receive multiple configuration rules.

In this step, the direct access means that the CPM client (specifically the storage client agent) directly accesses the XDM document server. The indirect access means that the CPM client accesses the XDM document server through the participating functional entity.

Step S305: The participating function entity obtains the unique identifier instance-id of each client B of the user B through the method described in step S303, and the user specifies different receiving rule configuration information for the CPM client B1 and the CPM client B2 through the CPM client B1; The receiving rule configuration information of the client B1 is marked by the unique identifier instance-idl; the receiving of the CPM client B2 The rule configuration information is marked with a unique identifier instance-id2. The configuration of the receiving rule configuration information is stored on the storage server, that is, the XDM document server.

In this step, each client of user B, assuming that client B1, uses direct access XDM mode to set configuration information for each client, there are two options:

Solution 1: The client B1 first obtains the instance-id2 of the client B2 by accessing the participating functional entity, and the client B1 sets the receiving rule configuration information of the client B2; after that, the client B1 directly accesses the XDM server, for example, through the HTTP protocol. The configuration information is saved on the XDM server. The configuration information of client B2 contains the tag identifier instance-id2.

Solution 2: The participating functional entity obtains the instance-id of the client B1 and B2, and then saves the identifiers of the two clients, instance-idl and instance-id2, through the communication interface between the participating functional entity and the XDM (such as the HTTP protocol). On the user configuration information server.

The client B1 accesses the XDM server, sets the receiving rule configuration information of the client B2, and saves the configuration information on the XDM server. The configuration information of the client B2 includes the tag identifier instance-id2.

In this step, each client of user B, assuming that client B1, uses indirect access XDM mode to set configuration information for each client, the following scheme can be used:

The client B1 obtains the instance-id2 of the client B2 by accessing the participating function entity, and the client B1 sets the receiving rule configuration information of the client B2; after that, the participating functional entity communicates with the XDM server (such as the HTTP protocol), The configuration information is saved on the XDM server. The configuration information of client B2 contains the tag identifier instance-id2.

Step S306: User A sends a CPM request message to User B, and the request message may be a request message of a CPM paging message, a SIP MESSAGE or a request message of a CPM big message, a SIP INVITE or a SIP INVITE request message.

Specifically, user A sends a CPM request message to user B through CPM client A on the terminal Device-A using Addr-A, and the CPM request message is routed to PF-B via PF-A. Step S307: After receiving the CPM request message, the PF-B sends the request message of the received CPM message to the receiving party's CPM client, according to the receiving rule of each client from the user configuration information storage server, according to each The receiving rule of each client is one of the selection conditions to determine which of the CPM clients of the receiving party satisfying the receiving condition.

The terminal that is finally selected to meet the receiving condition is the CPM client B 1 and the CPM client B2;

Step S308: The request message delivered by the PF-B carries the unique identifier of the selected client, such as carrying the instance-idl and the instance-id2 or the globally routable user agent global resource identifiers GRUU1 and GRUU2 (the GRUU identifier includes the instance-id) , information, used to indicate the final recipient client to the SIP/IP core network.

Taking the CPM paging message or the CPM big message request message as an example, after the participating functional entity selects the receiving client, it can send a request message to each selected client, and the request message (Request-URI) carries the receiving client. At the end of the GRUU, the SIP/IP core network routes the message to Client 1 and Client 2 according to the Request-URI: GRUU information in each message. This scheme corresponds to Figure 2.

Taking the CPM Session request message as an example, after the participating functional entity selects the recipient client, it can send only one request message regardless of the selected recipient client. The request message carries the Accept-Request message through the Accept-Contact field. The instance-id of the receiver client or the instance-id of the receiver client that is not allowed to receive the request message through the Reject-Contact field. The SIP/IP core network routes the message to the client 1 and the client 2 according to this information. This scheme corresponds to Figure 3.

In this application example, when the destination end participating functional entity sends a delayed message, the same solution can be used for multiple receiving CPM clients.

The CPM request message in this embodiment refers to a request message SIP MESSAGE of a CPM paging message or a request message SIP INVITE of a CPM big message or a SIP Session. The request message SIP INVITE, the solution provided by the present invention is also applicable to the case where the SIP session is used as the signaling plane and the MSRP is used as the media plane to transmit other service requests.

As shown in the above, the processing of the request message of the present invention can represent the process shown in FIG. 4, and the process includes the following steps:

Step 410: The service server acquires the receiving rule configuration information of the multiple receiving client before sending the request message, and selects the multiple receiving client according to the receiving rule configuration information corresponding to the multiple receiving client respectively. .

Step 420: Carry the selection result information including the third unique identifier of the receiver client in the sent request message, to indicate whether the receiver client is allowed to receive the request message.

Although the above description is based on the CPM request message, the solution of the present invention is equally applicable to other SIP-based service systems.

In summary, by using the foregoing embodiment of the present invention, when a user logs in to a service system such as a CPM system on a different client by using a user identifier such as the same CPM address, the user can set a receiving rule for each client in advance and participate. When a service server such as a function entity sends a request message such as a CPM request message, the configuration rule configuration information of each client is obtained from the user configuration rule storage server, and the client selection is performed according to each receiving rule configuration information, thereby improving the user experience.

The terminal mentioned above refers to a physical entity running an instant messaging client. Generally, a physical entity can run an instant messaging client. Therefore, in the present invention, if not specified, sending to a terminal is also sent to An instant messaging client running on the terminal.

Claims

Claim

A method for processing a request message, wherein when the number of recipient clients registered by using the same user identifier is multiple, the method is used for selecting a recipient client; the method includes: before the service server sends the request message Obtaining the receiving rule configuration information of the multiple receiving client, and selecting the multiple receiving client according to the receiving rule configuration information corresponding to the multiple receiving client respectively;

The request message sent carries the selection result information including the third unique identifier of the receiver client to indicate whether the recipient client is allowed to receive the request message.

2. The method of claim 1, further comprising:

3. The method of claim 1, further comprising:

4. The method of claim 3 wherein:

(b) The service server sends a subscription message to the SIP/IP core network, and the SIP/IP core network sends a subscription notification message to the service server, where the subscription notification message carries the second unique identifier of the receiver client.

5. The method of claim 3 wherein:

6. A method according to any one of claims 3 to 5, characterized in that:

The relationship between the first unique identifier of the receiver client, the second unique identifier of the receiver client, and the third unique identifier of the receiver client is: the three are the same identifier or are different but have an associated relationship. Identification

7. The method of claim 6 wherein:

The recipient client is a receiver CPM client.

8. The method of claim 7 wherein:

9. The method of claim 7 wherein: The first unique identifier is a client proxy identifier, or is a device identifier; the second unique identifier is a client proxy identifier, or a device identifier, or a global routable user proxy global resource identifier;

A processing system for requesting a message, comprising: a service server, a user configuration information storage server, and a plurality of receiver clients registered with the same user identifier; wherein the service server is configured to send a request message The receiving rule configuration information of the plurality of receiving client clients registered with the same user identifier is obtained, and the receiving client configuration information is selected according to different receiving rule configuration information corresponding to the different receiving client clients; And the carrying the received request message carrying the selection result information including the third unique identifier of the receiving client, to indicate whether the receiving client is allowed to receive the request message;

The user configuration information storage server is configured to store the receiving rule configuration information of the plurality of recipient clients registered by using the same user identifier.

11. The system of claim 10, wherein:

The system further includes a SIP/IP core network, configured to receive a SIP/IP core network registration message sent by any one of the plurality of recipient clients before the service server performs message processing;

The SIP/IP core network registration message carries the first unique identifier of the receiver client.