WO2007147321A1

WO2007147321A1 - Method and device for subscribing to user event

Info

Publication number: WO2007147321A1
Application number: PCT/CN2007/001674
Authority: WO
Inventors: Hui Li
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-06-15
Filing date: 2007-05-23
Publication date: 2007-12-27
Also published as: CN101043396A; CN100471150C

Abstract

A method and device for subscribing to a user event. The method includes: a subscription server receives a subscription request initiated by a subscription network element for subscribing to the related event of the network element user, the request address of the subscription request being the address of the subscription server; the subscription server responds to the subscription request and establishes a subscription session between the subscription network element and the subscription server; the subscription server notifies the user event related to the subscription network element to the subscription network element through the subscription session. The device includes a subscription session creation unit (301), for establishing the subscription session between the network element and the subscription server; a send unit (302), for sending the user event related to the subscription network element to the subscription network element through the subscription session; the device also includes a judge unit (303), and an authentication unit (304). The method and device realize the event notify for all of the subscription users of the network element through establishing the network element-based subscription session between the subscription network element and the subscription server, therefore the spending of the network system and flux is decreased.

Description

Method and apparatus for subscribing to a user event This application claims priority to a Chinese patent application filed on June 15, 2006 by the Chinese Patent Office, application number 200610061154.7, and entitled "Method of Establishing a Subscription Session and Method of Subscribing to a User Event" The entire contents of which are incorporated herein by reference. Technical field

The present invention relates to the field of communications technologies, and in particular, to a method and apparatus for subscribing to user events. Background technique

The Session Initiation Protocol (SIP) is a protocol defined by IETF RFC3261 for establishing a multimedia session. Currently, the SIP protocol is widely used in packet networks including Internet networks and IMS networks. For example, the IMS network is a service network in which 3GPP R5 and R6 use SIP architecture as a variety of access technologies such as 3G/2G GPRS and WLAN.

In order to obtain the location information of the user, SIP creates a binding relationship for the location service of the specific domain through the registration service, and the registration service binds the contact address of the Contact header field and the record address in the To header field. A record address can be bound to one or more contact addresses. When the proxy server in the domain receives a SIP request, it finds the contact address registered by the user according to the record matching between the Request-U I and the record address in the request, wherein the Request-URI is used to indicate which one to subscribe to. User registration status information. Then forward the request to this contact address.

The SIP registration service includes a registration request REGISTER request to add, delete, refresh, and query binding information. A REGISTER request can add a binding between a record address and one or more contact addresses. The client can also delete the content bound to the front and the current binding address of the record address.

SIP's subscription mechanism is defined in RFC3265 (SIP-Specific Event Notification) and RFC3680 (A SIP Event Package for Registrations), and a method for subscribing to user registration events through a subscription mechanism. The main process is shown in Figure 1:

1. The application server sends a message to the registration server requesting to subscribe to the registration event of the user terminal.

2. The registration server returns a response message, accepts the subscription request, and at this point, the subscription session is established. 3. After the subscription session is established, the registration server sends a notification message to the application server to notify the registration status of the currently subscribed user terminal.

4. The user terminal initiates registration with the registration server. After the registration is successful, the registration server sends a notification message to the application server to notify the registration event of the user terminal.

The registration event of obtaining the subscribed user by the user-based subscription method is applied to

In networks such as IMS. In the MS network, the network elements that can subscribe to the user registration event include the user terminal, the proxy call session control function entity P-CSCF, and the third party registered application server AS. The foregoing network element can obtain information such as an implicit registration set of the subscribed user, a registration status of the user identifier, and the like by subscribing to the registration event. By subscribing to notification messages, the network can force user authentication, log off users, or have users initiate re-registration when needed.

However, in the above-mentioned user-based subscription method, the subscription network element such as the P-CSCF and the AS needs to periodically send a subscription request during the registration lifetime of the user to maintain the validity of the subscription, thereby increasing the overhead of the network device. For example, if a device supports 100,000 users, and each user has three ASs providing services, then each user needs 5 subscription instances, the subscription period is 30 minutes, and the entire device requires 500,000 subscription instances, which need to be processed every second. 28 subscription transactions. This has very high requirements on the memory and performance of communication devices. In addition, the subscription mechanism needs to maintain the validity of the subscription session through periodic redefinition. Since the SIP protocol is a text protocol, it will greatly occupy the network transmission bandwidth and increase the network traffic. Summary of the invention

Embodiments of the present invention provide a method and apparatus for subscribing to a user event, which can reduce memory and performance requirements of a communication device, and reduce network traffic and occupied network transmission bandwidth.

An embodiment of the present invention provides a method for subscribing to a user event, including:

The subscriber receives the subscription request initiated by the subscription network element to subscribe to the related event of the user of the network element, and the request address of the subscription request is the address of the subscription server;

And the subscriber responds to the subscription request, and establishes a subscription conversation between the subscription network element and the subscription server;

The subscriber server notifies the subscribed network element of the user event related to the subscribed network element through the subscription session. An embodiment of the present invention provides an apparatus for subscribing to a user event, including:

a subscription session creation unit, configured to establish a subscription session between the network element and the subscription server; and a sending unit, configured to send the user event related to the subscription network element to the subscription network element by using the subscription session;

The sending unit notifies the subscribed network element related user event notification to the network element through the established subscription session.

In the technical solution provided by the embodiment of the present invention, the user-based subscription mode is replaced by the network element-based subscription mode, that is, all users of the subscription network element proxying the network element establish a subscription dialogue with the registration/subscription server, based on the subscription dialogue. Complete the event notification for all subscribers that subscribe to the NE. Therefore, the network element-based subscription conversation is established between the subscription network element and the subscription server, and the event notification of all subscribers of the network element is completed through the dialogue, thereby reducing the network system and traffic overhead. DRAWINGS

1 is a flow chart of a method for subscribing to a user registration event in the prior art;

2 is a flowchart of a method implemented in a SIP network according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a device structure for subscribing user events in an embodiment of the present invention. detailed description

The present invention will be further described in detail below with reference to the drawings and specific embodiments.

In the following embodiments of the present invention, in the case where the registration server and the subscription server are unified, the subscription-based network element-based subscription method is used instead of the user-based subscription method, that is, the subscription network element and the subscription server establish a subscription session. Event notifications for all subscribers of the subscribed network element are completed based on this subscription session.

The event includes at least one or more of a registration event, a presence list, a message wait, a conversation event, an observer information, and the like.

The specific implementation steps of the method provided by the embodiment of the present invention are as follows:

S101. The subscriber server saves an address letter of the subscription network element that subscribes to the subscribed user event. The subscriber server can obtain the address information of the subscribed network element by using the information of the registration request message (for example, the path header field) of the subscribed user, the subscription data of the user, the static configuration, and the like.

5102. Before the subscribing network element subscribes the user event to the subscribing server, check whether the network element-based subscription conversation has been established between the subscribing network element and the subscription server.

If not established, the subscribing network element initiates a subscription request to the subscribing server to subscribe to the events of all users of the subscription network element. If it is already established, use the subscription dialog directly.

5103. After receiving the subscription request, the subscriber determines that the subscription request is a network element-based subscription, and establishes a subscription session according to the subscription request information and the subscribed network element of the known subscription user event (see step 1).

After the subscription server establishes the network element-based subscription dialog, the event of the user to be subscribed is notified to the subscribed network element through the subscription dialog; when the event of the subscribed user occurs, the new event is passed through The subscription dialog described is a notification of the subscribed network element.

The subscriber can determine whether the subscribed network element can subscribe by checking the path header field carried by the user registration request, the subscription data of the user, and the like.

If the subscribing server cannot judge whether the subscribing network element can subscribe, the authentication network can perform authentication judgment on the subscription network element.

5105. The subscriber sends a notification message to the subscribing network element according to the method described in RFC3680, and notifies the subscribed user event.

S106. When receiving the event notification, the subscribing network element updates the corresponding user data by notifying the user record address in the message body.

The implementation in the SIP network is described in detail in the following embodiments. The proxy server in this embodiment is a subscription network element, and the registration server is a subscription server for registration events. The process is shown in Figure 2:

S201. The user Joe initiates a registration request to the registration server. When the registration request message passes through the proxy server, the proxy server places its own address information in the path header field and carries it to the registration server.

S202. After receiving the registration request message of the user Joe, the registration server saves the information such as the path header field, and then sends a response registration message to the user Joe. The registration response message passes through the proxy At the time of the server, the proxy server saves the registration information of the user Joe in the registration response message.

5203. The proxy server initiates a subscription request to the registration server to obtain a registration event of the subscription user in order to obtain the registration status of all users registered by the proxy server.

In order to support network element-based registration event subscriptions, subscription request messages and response messages can be extended. Supported methods include adding header fields, adding parameters, tags, and the like. In this embodiment, the Request-URI in the subscription request is used to specify the network element address of the registered registration server; the To header field is used to carry the network element address of the subscribed registration server, and the rest is described in RFC3680. The specific message content is as follows:

SUBSCRIBE sip:registar.example.com SIP/2.0

Via: SIP/2.0/UDP app.example.com;branch=z9hG4bKnas ds7

From: sip:app.example.com;tag=123aa9

To: sip:registar.example.com

Call-ID: 9987@app.example.com

CSeq: 9887 SUBSCRIBE

Contact: sip:app.example.com

Event: reg

Max- Forwards: 70

Accept: application/reginfo+xml

After the registration server receives the subscription request, if the Request-URI carries its own network element address, it determines that the subscription request is a network element-based subscription. The registration server determines whether the proxy server can subscribe according to the saved path header field information. If the address of the proxy server carried in the From header field in the subscription request is the same as the address of the saved proxy server, the subscription request is accepted, and a response message is returned. a proxy server, and a subscription dialog is established between the proxy server and the registration server. The contents of the response message are as follows:

SIP/2.0 200 OK

Via: SIP/2.0/UDP app.example.com;branch=z9hG4bKnashds7

; received=192.0.2.1

From: sip: ap . example . com;tag= 123 aa9 To: si : registar.example.com;tag=xyzygg

Call-ID: 9987@app.example.com

CSeq: 9987 SUBSCRIBE

Contact: sip: registar.example.com

Expires: 3600

S205. After establishing a network element-based subscription session, the registration server checks whether an event of the registered user needs to be notified by the subscribed network element. If it is (user Joe), the registration server sends the subscription server to the proxy server. The notification message carries the registration information of the user Joe. The content of the notification message is as follows:

NOTIFY sip:app.example.com SIP/2.0

Via: SIP/2.0/UDP registar.example.com;branch=z9hG4bKnasaij From: sip: registar.example.com^ag^xyzygg

To: sip :app. example. com;tag= 123 aa9

Call-ID: 9987@app.example.com

CSeq: 1289 NOTIFY

Contact: sip: registar.example.com

Event: reg

Max-Forwards: 70

Content-Type: application/reginfo+xml

Content-Length: ...

<?xml version^" 1.0"?>

<reginfo xmlns="urn:ietf:params:xml:ns:reginfo"

Version-" 1 " state="partial">

Registration aor="sip:joe@example.com" id="a7" state="active"> <contact id="76" state=" active" event="registered"

Duration-registered="0">

<uri>sip: j oe@pc34. example . com</uri>

</contact> </registration>

</reginfo>

If more than one registered user's registration event is sent to the same subscription network element through the same subscription session, the registration server can put multiple notification message content into a notification message by means of multiple message bodies.

5206. The proxy server answers the notification message.

5207. The user Bob initiates a registration request to the registration server. When the registration request message passes through the proxy server, the proxy server carries its own address information in the path header field and carries it to the registration server.

5208. After receiving the registration request message of the user Bob, the registration server saves the information such as the path header field, and then sends a response registration message to the user Bob. When the registration response message passes through the proxy server, the proxy server saves the registration information of the user Bob in the registration response message. The proxy server checks if a subscription session has been established with the registration server, and if so, the subscription request is no longer initiated.

5209. After the registration server responds to the registration request of the user Bob, check the proxy server address in the path header field carried in the user registration request, and determine whether the registered user has been subscribed by the proxy server. If yes, the registration server passes the proxy server and the registration server. A subscription message has been established between the two, and a notification message is sent to the proxy server, and the notification message carries the registration letter of the user Bob.

NOTIFY sip:app.example.com SIP/2.0

Via: SIP/2.0 UDP registar.example.com;branch=z9hG4bKnasdfdk

From: sip: registar . example . com;tag=xyzygg

To: sip: app.example.com;tag= 123 aa9

Call-ID: 9987@app.example.com

CSeq: 1290 NOTIFY

Contact: sip: registar.example.com

Event: reg

Max-Forwards: 70

Content-Type: application/reginfo+xml

Content-Length: ... <?xml version="1.0"?>

<reginfo xmlns^'^rniietfiparamsixmlinsireginfo"

Version^" 1 " state="partial">

Registration aor="sip:bob@example.com" id="a8"

State="active">

<contact id— '78" state="active" event="registered"

Duration-registered=" 0">

<uri>sip :bob@pc38.example.com</uri>

</contact>

</registration>

</reginfo>

S210. The proxy server answers the notification message.

The foregoing process is a general SIP entity process. In the IMS network, the proxy server is a P-CSCF, and the subscriber server is an S-CSCF. The specific implementation process is similar, and details are not described herein.

Referring to FIG. 3, an embodiment of the present invention further provides a device 300 for subscribing to a user event, including: a subscription session creation unit 301, configured to establish a subscription session between a network element and a subscription server; and a subscription session creation unit 301 is generally disposed at Subscribe to the network element.

The sending unit 302 is configured to send, in the subscription server, a user event related to the subscription network element to the subscription network element by using the subscription session; and the sending unit notifies the user event related to the subscription network element by using the established subscription session. Subscribe to an NE.

The device further includes a determining unit 303, configured to determine whether the subscribed network element has established a subscription dialogue with the subscription server;

Before the user event is subscribed, the determining unit determines whether the subscribed network element has established a subscription dialogue with the subscription server;

If the judging unit determines that no subscription conversation is established between the network element and the subscribing server, the subscription conversation creation unit establishes a corresponding subscription conversation.

The device further includes an authentication unit 304, configured to authenticate the subscribed network element that initiates the subscription request; the authentication unit 304 can be configured in the registration server or other network management entity. When the subscription network element address in the subscription request message received by the subscriber is different from the saved subscription network element address, the authentication unit authenticates the subscription network element, and after the authentication is passed, the The subscription dialog creation unit establishes a corresponding subscription conversation between the subscription network element and the subscription server.

Those skilled in the art can understand that all or part of the steps in the above embodiments can be implemented by instructing related hardware through a program, and the program can be stored in a computer readable storage medium.

The storage medium, such as a ROM/RAM, a magnetic disk, a optical disk, or the like.

According to the foregoing embodiment, the embodiment of the present invention replaces the user-based subscription mode by using a network element-based subscription method, that is, all users of the subscription network element proxying the network element establish a subscription dialogue with the registration/subscription server, based on the subscription dialogue. The event notification of all subscribers of the subscription network is completed, thereby reducing the overhead of the network system and traffic.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

A method for subscribing to a user event, comprising:

The subscriber server subscribes the user event related to the subscription network element to the network element through the subscription conversation interface.

2. The method according to claim 1, further comprising the step of: obtaining, by the subscriber, a network element address of the subscription network element before the subscription server receives the subscription request initiated by the subscription network element.

3. The method according to claim 2, further comprising:

The subscriber obtains the network element address of the subscribed network element according to the registration request message of the user, the subscription data of the user, or the static configuration data.

The method according to any one of claims 1 to 3, wherein the establishing a subscription session between the subscription network element and the subscription server comprises:

The subscriber receives the subscription request. If the subscription network element address in the subscription request message is the saved subscription network element address, a network element-based subscription session is established between the subscription network element and the subscription server.

Receiving, by the subscriber, the subscription request, if the subscription network element address in the subscription request message is different from the saved subscription network element address, initiating authentication of the subscription network element, and authenticating, on the subscription network A meta-based subscription session is established between the meta and the subscriber.

6. The method according to claim 1, further comprising the steps of: subscribing the network element to determine whether it has established a subscription session with the subscription server before subscribing to the user event;

If the subscription dialog is not established, a subscription dialog is established, if the subscription has been established The conversation uses the subscription conversation to subscribe to user events.

The method according to claim 1, wherein the step of the subscription server notifying the subscribed network element related user event to the subscribed network element through the subscription session comprises: the subscriber server after the user event changes Determining whether the user is subscribed by the subscribed network element; if yes, notifying the subscribed network element of the event of the subscribed user through the subscription session.

The method according to claim 1, wherein the step of the subscription server notifying the subscribed network element related user event to the subscribed network element through the subscription session comprises: the event that the subscription server is to be subscribed to the user The information carried in the notification message is sent to the subscription network element through the subscription session.

The method according to claim 7, wherein the subscription server determines, according to the user's registration request message, the user's subscription data, or the static configuration data, whether the user can be subscribed by the subscription network element.

The method according to claim 8, wherein the subscription server notifies the subscribed network element of the user event related to the subscription network element, specifically:

The subscriber server sends the event of the multiple subscribed users to the subscribed network element in the message body of the notification message, and the message body of the notification message is a multi-message body or an extended event notification script. .

11. A device for subscribing to a user event, comprising:

The sending unit notifies the subscribed network element of the user event related to the subscription network element by using the subscription session established by the subscription session creation unit.

12. The device according to claim 11, further comprising:

a judging unit, configured to determine whether the subscribing network element has established a subscription conversation with the subscribing server; before establishing a subscription conversation between the network element and the subscribing server, the determining unit determines whether the subscribing network element has established a subscription conversation with the subscribing server; If the judging unit determines that no subscription conversation is established between the network element and the subscribing server, the subscription conversation creation unit establishes a corresponding subscription conversation.

The device according to claim 11 or 12, further comprising: an authentication unit, configured to authenticate a subscription network element that initiates the subscription request;

When the subscription network element address in the subscription request message received by the subscriber is different from the saved subscription network element address, the authentication unit authenticates the subscription network element, and after the authentication is passed, the The subscription dialog creation unit establishes a corresponding subscription conversation between the subscription network element and the subscription server.