WO2007124662A1 - Procédé, système, dispositif d'abonnement, dispositif d'information de commande centrale d'abonnement - Google Patents

Procédé, système, dispositif d'abonnement, dispositif d'information de commande centrale d'abonnement Download PDF

Info

Publication number
WO2007124662A1
WO2007124662A1 PCT/CN2007/001046 CN2007001046W WO2007124662A1 WO 2007124662 A1 WO2007124662 A1 WO 2007124662A1 CN 2007001046 W CN2007001046 W CN 2007001046W WO 2007124662 A1 WO2007124662 A1 WO 2007124662A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscription
subscriber
management set
message
identifier
Prior art date
Application number
PCT/CN2007/001046
Other languages
English (en)
Chinese (zh)
Inventor
Xiao Wang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007124662A1 publication Critical patent/WO2007124662A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present invention relates to network communication technologies, and in particular, to a method, system, subscription device, and notification device for controlling a subscription.
  • SIP Session Initiation Protocol
  • SIP implements the subscription/notification framework and introduces the SUBSCRIBE method and the NOTIFY method.
  • the SUBSCRIBE method is used by the subscriber to initiate a subscription to the notifier
  • the NOTIFY method is used to communicate a notification of any change in an event between the subscriber and the notifier.
  • a subscription notification is when a user or resource acts as a subscriber to initiate a subscription to the owner of another resource, the notifier, and then the subscriber receives notifications from the notifier about the status and any changes to the event.
  • Figure 1 is a flow diagram for implementing a subscription in the prior art. Referring to FIG. 1, in the prior art, a process in which a subscriber initiates a subscription to a notifier specifically includes the following steps:
  • Step 101 The subscriber sends a SUBSCRIBE message to the owner of the resource, that is, the notifier, requesting to subscribe to the resource status information of interest to the user.
  • Step 102 After the notifier receives the SUBSCRIBE message and determines to allow the subscription, Send a 200 OK response message to the subscriber.
  • Step 103 The subscriber and the notifier establish a dialog with the other party, and set up a subscription instance, record the identity of the subscription and the session, and record the subscription and related parameters.
  • Step 104 The notifier sends a NOTIFY message to the subscriber, and carries the subscribed resource status information in the message body of the NOTIFY message.
  • Step 105 After receiving the NOTIFY message, the subscriber sends a 200 OK response to the notifier, indicating that the NOTIFY message was successfully received.
  • each subscription of the subscriber to the user requires a different subscription to the notifier who owns the subscription resource.
  • the different subscriptions are separately controlled, that is, the sessions are respectively established and the different sessions are separately managed and maintained, the number of SIP sessions required to be maintained as the subscribers and the informants of the server is greatly increased. That is to increase the server-side business load, reducing the processing efficiency of the server. In addition, an increase in the number of conversations will excessively occupy the bandwidth resources of the network.
  • a main object of an embodiment of the present invention is to provide a method for centralized control of a subscription
  • a main object of another embodiment of the present invention is to provide a system for centralized control of a subscription, and another implementation of the present invention.
  • the main purpose of the example is to provide a subscription device.
  • the main purpose of another embodiment of the present invention is to provide a notification device, so as to reduce the number of sessions between the same subscriber and the notifier, thereby reducing the SIP required for maintenance on the server side. The number of sessions.
  • a method for centralized control of a subscription includes:
  • the subscriber and the notifier set a subscription management set and a corresponding session between the two; the notifier receives the current subscription related message on the session corresponding to the current subscription, and determines Whether the related message is sent by the subscriber, and if so,
  • the notifier records the identifier of the subscription instance corresponding to the current subscription in the subscription management set established by itself, releases the current subscription and its corresponding session, and the notifier triggers the subscriber to perform, and records the corresponding in the subscription management set established by the sender.
  • a system for centralized control of a subscription comprising: a subscription device and a notification device, wherein
  • a subscription device configured to establish, with the notification device, a subscription management set and a corresponding session between the two, and after receiving the trigger message sent by the notification device, record the subscription instance corresponding to the current subscription in the subscription management set established by the device Identifies and releases the current subscription and its corresponding session;
  • the notification device is configured to receive a related message of the current subscription on the session corresponding to the current subscription, and determine whether the related message is sent by the subscriber, and if yes, record the subscription management set established in the subscription corresponding to the current The identity of the subscribed subscription instance, releasing the current subscription and its corresponding session, and sending a trigger message to the subscribing device.
  • a subscription device includes: a subscription management set implementation unit and a transceiver unit, where
  • a subscription management set implementation unit configured to establish, with the notification device, a subscription management set and a corresponding session between the two, and after receiving the trigger message sent by the transceiver unit, record the subscription corresponding to the current subscription in the subscription management set established by the receiving device The identity of the subscription instance and release the current subscription and its corresponding session;
  • the transceiver unit is configured to send the currently subscribed related message to the notification device, and send the trigger message sent by the notification device to the subscription management set implementation unit.
  • a notification device comprising: a subscription management set setting unit and a transceiver unit, wherein a subscription management set setting unit, configured to set a subscription management set between the subscription device and the corresponding session, and after receiving the related message of the current subscription sent by the transceiver unit, determine whether the related message is the subscription If yes, the identity of the subscription instance corresponding to the current subscription is recorded in the subscription management set established by itself, the current subscription and its corresponding session are released, and the trigger message is sent to the transceiver unit;
  • the transceiver unit is configured to send a related message of the current subscription sent by the subscribing device to the session corresponding to the current subscription to the subscription management set setting unit, and send the received trigger message to the subscribing device.
  • the present invention proposes a specific implementation scheme for centrally controlling subscriptions between the same subscriber and the notifier.
  • the present invention performs subscriptions between the same subscriber and the notifier through the subscription management set. Management, and, between the same subscriber and the notifier, different subscriptions are associated with the same session corresponding to the subscription management set, rather than different subscriptions of the prior art associated with different sessions, thus reducing server rooms
  • the number of sessions greatly reduces the number of SIP transactions that need to be maintained on the server side as subscribers and notifiers, which reduces the server-side traffic load and improves the processing efficiency of the server.
  • the reduction in the number of conversations also reduces the occupation of network bandwidth resources.
  • the present invention adopts centralized control for the subscription between the same subscriber and the notifier, the batch refresh of the subsequent subscription and the batch sending of the notification message can be easily implemented, thereby reducing the traffic of the message on the network and further saving the network. bandwidth.
  • Figure 1 is a flow diagram for implementing a subscription in the prior art.
  • SMS subscription management set
  • Figure 3 is a subscription of subscriber 1 and notifier 1 joining an initial subscription in an embodiment of the invention.
  • FIG. 4 is a flow diagram of a first implementation in which Subscriber 1 and Notifier 1 join an existing subscription to a subscription management set in an embodiment of the present invention.
  • Figure 5 is a flow diagram of a second implementation of Subscriber 1 and Notifier 1 joining an initial subscription to a subscription management set in an embodiment of the present invention.
  • Figure 6 is a flow diagram of a second implementation of Subscriber 1 and Notifier 1 joining an existing subscription to a subscription management set in an embodiment of the present invention.
  • Figure 7 is a flow diagram of a third implementation of Subscriber 1 and Notifier 1 joining an initial subscription to a subscription management set in an embodiment of the present invention.
  • Figure 8 is a flow diagram of a third implementation in which subscriber 1 and notifier 1 join an existing subscription to a subscription management set in an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a system for centrally controlling subscriptions in an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a subscription device in an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a notification device in an embodiment of the present invention. Mode for carrying out the invention
  • the embodiment of the present invention proposes a method for centralized control of subscriptions between the same subscriber and the notifier: the subscriber and the notifier set a subscription management set (SMS) between the two and their corresponding sessions; Receiving a related message of the current subscription, determining whether the related message of the subscription is sent by the subscriber, and if yes, the notifier sets a subscription instance corresponding to the current subscription in the subscription management set established by itself, and records the current subscription. And the information associated with the corresponding session, and release the current subscription and its corresponding session; the notifier triggers the subscriber to set a subscription instance corresponding to the current subscription in the subscription management set established by the subscriber, and records the current subscription and its corresponding session. The associated information, and release the current subscription and its corresponding session.
  • SMS subscription management set
  • the subscriber and the notifier set the SMS and the corresponding session between the two to pass. W Once a subscription is called a first subscription.
  • the first subscription is simply the subscription name used for ease of description, and does not refer to the first subscription between the subscriber and the notifier.
  • the subscriber and the notifier may first negotiate whether to use the centralized control service between the two. If the negotiation is successful, the subsequent process of setting the SMS is continued.
  • the related SIP extension may be first defined, including:
  • SIP option tag as a centralized control service identifier, such as sms, for negotiation between the subscriber and the notifier to use the SMS mechanism;
  • a new parameter newid is defined in the Event header field for transmitting the information of the migration subscription
  • SMS-ID a SIP header field
  • the subscriber if the subscriber establishes an SMS by negotiating with the notifier, the subscriber carries sms in the Supported header field in the message when issuing the initial subscription message or refreshing the subscription message; the notifier receives the Supported header.
  • the domain contains the initial subscription message or refresh subscription message of sms. If the centralized control mechanism of the subscription is allowed between the two, the notifier carries sms in the Supported header field in the returned success response message, otherwise it does not carry sms. This completes the negotiation between the subscriber and the notifier for the use of a centralized control mechanism.
  • the negotiation success informer passes the sms in the Supported header field in the success response message, but returns if the negotiation fails. A failure response, which will cause the subscription being set or the existing subscription to fail.
  • FIG. 2 is a flow chart of setting an SMS through a subscription process in an embodiment of the present invention.
  • the subscription process is first required by the subscriber. 1
  • the process of setting up SMS includes the following steps:
  • Step 201 Subscriber 1 constructs an initial subscription message SUBSCRIBE message 1 for the first subscription, and sends the constructed initial subscription message SUBSCRIBE message 1 to Notifier 1 through a new session for the first subscription.
  • the SUBSCRIBE message 1 carries the preset centralized control service identifier in the SUBSCRIBE message 1, and the manner of carrying the method includes: the first mode: carrying the centralized control service identifier sms in the supported (Supported) header field of the SUBSCRIBE message 1; 2. Carrying the centralized control service identifier in the Require header field of the SUBSCRIBE message 1.
  • Step 202 After receiving the SUBSCRIBE message 1, the notifier 1 analyzes the centralized control service identifier from the message, and determines whether to allow centralized control on the first subscription. If yes, step 203 is performed; otherwise, the current process ends.
  • the mode 1 carries the centralized control service identifier sms in step 201, then in step 202, the notifier 1 parses the centralized control service identifier sms from the Supported header field of the SUBSCRIBE message 1, so that After judging that it is not allowed to use the centralized control of the current subscription, it can turn to the process of implementing the existing implementation subscription.
  • the notifier 1 parses the centralized control service identifier sms from the Require header field of the SUBSCRIBE message 1, so that after determining that centralized control is not allowed for the current subscription, the notifier 1 can subscribe to 1 returns a failure response and the current subscription fails.
  • a policy for allowing centralized control of the service may be set on the informant side, for example, allowing or disallowing centralized control services for some specific subscribers.
  • the notifier determines whether to allow centralized control of the current subscription according to a preset policy.
  • the preset policy is to allow some specific subscribers to allow centralized control of the service, so that the notifier determines to send the message. Whether the subscriber 1 of the SUBSCRIBE message 1 belongs to a specific subscriber set in advance, and if so, determines that centralized control is allowed for the current subscription, otherwise it is determined that centralized control of the current subscription is not allowed.
  • Step 203 The notifier 1 constructs a 200 OK response message, and carries the centralized control service identifier sms to the subscriber 1 in the Supported header field of the constructed 200 OK response message.
  • the notifier 1 indicates to the subscriber 1 that the centralized control service is supported by carrying the centralized control service identifier sms in the 200 OK response message.
  • Step 204 The notifier 1 accepts the subscription to the resource [email protected], the notifier 1 sets the SMS, sets an identifier for the SMS, and associates the set SMS with the session corresponding to the first subscription, and records the identifier of the first subscription and The first subscription corresponds to the information associated with the session into the SMS.
  • the identifier of the set SMS is smsid.
  • the information associated with the session corresponding to the first subscription includes: a Call-ID, a Route-set, and a remote target: of the first subscription corresponding session.
  • Step 205 The notifier 1 sends a NOTIFY message to the subscriber 1 for the first subscription.
  • the resource status information of the first subscription is carried.
  • the notifier 1 may also carry the set centralized control service identifier sms in the Supported header field of the NOTIFY message, and carry the identifier smsid of the set SMS in the SMS-ID header field in the NOTIFY message.
  • Step 206 The subscriber 1 receives the NOTIFY message, parses out that the Supported header field contains the centralized control service identifier sms, determines that the notifier 1 supports and allows the centralized control service, and extracts smsid from the SMS-ID header field of the NOTIFY message.
  • Step 207 Subscriber 1 sets the SMS locally, sets the extracted smsid as the identifier of the local SMS, and the subscriber 1 records the information associated with the first subscription and its corresponding session in the set SMS, and the association itself sets The SMS corresponds to the session of the first subscription.
  • the subscription between Subscriber 1 and Notifier 1 can be centrally controlled through the subscription management set.
  • the subscription management set is set through the process shown in Figure 2 above, the subscription between Subscriber 1 and Notifier 1 can be centrally controlled through the subscription management set.
  • three implementation methods for centralized control through the subscription management set are included.
  • FIG. 3 is a flow diagram of a first implementation in which Subscriber 1 and Notifier 1 join an initial subscription to a subscription management set in an embodiment of the present invention.
  • Subscriber 1 when an SMS and its corresponding session dialog are set between Subscriber 1 and Notifier 1, Subscriber 1 initiates a subscription to Notifier 1, for example.
  • the process of centrally controlling the subscription 2 between subscriber 1 and notifier 1 in the first manner includes the following steps:
  • Step 301 Subscriber 1 constructs an initial subscription message SUBSCRIBE message 2 for subscription 2, and sends the constructed initial subscription message SUBSCRIBE message 2 to notifier 1 through a new session corresponding to subscription 2.
  • the subscriber 1 needs to perform centralized control in order to notify the owner of the resource, that is, the informant 1.
  • the SUBSCRIBE message 2 carries the preset centralized control service identifier, and the manner of carrying the method includes: mode 1: carrying the centralized control service identifier sms in the Supported header field of the SUBSCRIBE message 2; and mode 2, the Require header field in the SUBSCRIBE message 2
  • the centralized control service identifier sms is carried in the middle.
  • Step 302 After receiving the SUBSCRIBE message 2, the notifier 1 parses the centralized control service identifier from the message, and determines whether to allow centralized control on the current subscription 2. If yes, step 303 is performed; otherwise, the existing Subscription process.
  • Step 303 The notifier 1 judges whether the SUBSCRIBE message 2 is sent by the subscriber 1, and if yes, performs step 304, otherwise, performs a process of creating an SMS for the current subscriber, and ends the current process.
  • the process in which the notifier 1 determines whether the SUBSCRIBE message 2 is sent by the subscriber 1 includes: the notifier 1 judges the remote target in the SMS set by itself and the contact in the SUBSCRIBE message 2 of the current subscription. Whether the address portion of the header field is the same, and if so, it is determined that the SUBSCRIBE message 2 is sent by subscriber 1, otherwise, it is determined that SUBSCRIBE message 2 is not sent by subscriber 1.
  • the notifier 1 can further determine the route set (Route-set) of the set SMS and the Route of the SUBSCRIBE message 2 of the current subscription. Whether the -set is the same, that is, whether the route from the subscriber 1 to the notifier 1 is the same, and if so, the subsequent subscription centralized control process is continued, that is, step 304 is performed, otherwise, the process of creating an SMS for the current subscriber is performed.
  • Step 304 The notifier 1 constructs a 200 OK response message, and carries the centralized control service identifier sms in the Supported header field of the constructed 200 OK response message to be sent to the subscriber.
  • the notifier 1 indicates to the subscriber 1 that the centralized control service is supported by carrying the centralized control service identifier sms in the 200 OK response message.
  • Step 305 Notifier 1 accepts subscription to resource [email protected] 2, Notifier 1 creates subscription instance sub2, records the relevant parameters of subscription 2 into sub2, and records the identity of sub2 into SMS.
  • the notifier 1 also needs to carry the set centralized control service identifier sms in the Supported header field of the NOTIFY message; and carry the identifier of the set SMS smsid in the SMS-ID header field in the NOTIFY message; the id of the subscription 2
  • rsl-xx is used as the value of the newid parameter in the Event header field of the NOTIFY message
  • the Subscription-State header field value in the NOTIFY message is set to terminated, and the reason parameter ⁇ value is set to migration.
  • Step 306 The notifier 1 records the ID of the subscription 2 and other related parameters into the subscription instance sub2 set in the SMS.
  • Step 307 Subscriber 1 receives the NOTIFY message, parses the Supported header field to include the sms identifier, and determines that the Notifier 1 supports and allows the use of the SMS mechanism.
  • Step 308 Subscriber 1 retrieves smsid from the SMS-ID header field of the NOTIFY message and matches locally to a subscription management set.
  • Step 309 The subscription-state header field value of the subscriber 1 parsing out the NOTIFY message is terminated, and the reason parameter value is migration, determining that the subscription has migrated on the side of the subscriber 1, and the subscriber 1 creates a subscription instance sub2, which will be from NOTIFY.
  • the value of the newid parameter obtained in the Event header field of the message is used as the identifier of sub2.
  • Step 310 Subscriber 1 records the identity of sub2 into the matched SMS, and releases Put the current subscription 2 and its corresponding session.
  • FIG. 4 is a flow diagram of a first implementation in which Subscriber 1 and Notifier 1 join an existing subscription to a subscription management set in an embodiment of the present invention.
  • the first method is used to implement the subscription for the subscription 3.
  • the process of control includes the following steps:
  • Step 401 Subscriber 1 sends a refresh subscription message SUBSCRIBE message 3 to the notifier 1 through the associated session of the subscription 3, wherein the Supported header field of the SUBSCRIBE message 3 carries the preset option tag, that is, the centralized control service identifier sms.
  • Step 402 After receiving the SUBSCRIBE message 3, the notifier 1 parses the centralized control service identifier from the message, and determines whether to allow centralized control on the current subscription 3. If yes, step 403 is performed; otherwise, the existing subscription is executed. Process.
  • Step 403 The notifier 1 accepts the refresh request for the subscription 3, determines whether the refresh subscription message SUBSCRIBE message 3 is sent by the subscriber 1, and if yes, performs step 404, otherwise, performs the process of creating an SMS for the current subscriber. , ends the current process.
  • the process by which the notifier 1 judges whether the refreshed SUBSCRIBE message 3 is sent by the subscriber 1 is exactly the same as the process of the judgment described in step 304 of FIG. Moreover, in this step, after determining that the refreshed SUBSCRIBE message 3 is sent by the subscriber 1, the route set corresponding to the refreshed SUBSCRIBE message 3 may be further determined. Whether the set of SMSs of the set SMS is the same, and after determining the same, continue to perform the subsequent centralized control process, that is, step 404 is performed, otherwise, the process of creating an SMS for the current subscriber is performed.
  • Step 404 The notifier 1 returns a 200 OK message to the subscriber 1 and carries sms in the Supported header field in the 200 OK message, indicating that the centralized control of the subscription is supported.
  • Step 405 The notifier 1 sets a subscription instance sub3 of the resource [email protected] according to the subscription instance of the existing subscription 3, records the relevant parameters of the subscription 3 into the sub3, and records the identifier of the sub3 into the SMS.
  • Step 406 The notifier 1 sends a NOTIFY message to the subscriber 1 to carry the resource status information of the subscription.
  • the notifier 1 also needs to carry the set option tag, that is, the centralized control service identifier sms, in the Supported header field of the NOTIFY message; and carry the identifier of the SMS matched by the subscription 3 in the SMS-ID header field in the NOTIFY message.
  • Smsid is the value of the newid parameter in the Event header field of the NOTIFY message; the value of the Subscription-State header field in the NOTIFY message is set to terminated, and the value of the reason parameter is set to migration.
  • Step 407 Subscriber 1 receives the NOTIFY message, and the Supported header field parsing the NOTIFY message carries the sms identifier to determine that the Notifier 1 supports and allows the use of the SMS mechanism.
  • Step 408 Subscriber 1 retrieves smsid from the SMS-ID header field of the NOTIFY message and matches it to SMS locally.
  • Step 409 The subscription-state header field value of the subscriber 1 parsing out the NOTIFY message is terminated, and the reason parameter value is migration, determining that the subscription 3 has migrated on the informant 1 side, and the subscriber 1 creates a subscription instance sub3, which will The value of the newid parameter obtained in the NOTIFY message is used as the identifier of sub3.
  • Step 410 Subscriber 1 records the identity of sub3 to the matched SMS, and releases Put the current subscription 3 and its corresponding session.
  • FIG. 5 is a flow diagram of a second implementation of Subscriber 1 and Notifier 1 joining an initial subscription to a subscription management set in an embodiment of the present invention.
  • Subscriber 1 initiates a subscription to Notifier 1, for example, for [email protected] resources.
  • Subscription 2 at this time, the second method of implementing centralized control of subscription 2 between subscriber 1 and notifier 1 includes the following steps:
  • Step 501 Subscriber 1 constructs an initial subscription message SUBSCRIBE message 2 for subscription 2, and sends the constructed initial subscription message SUBSCRIBE message 2 to notifier 1 through a new session corresponding to subscription 2.
  • the subscriber 1 needs to perform centralized control in order to notify the owner of the resource, that is, the subscriber 1 , and the subscriber 1 carries the preset centralized control service in the SUBSCRIBE message 2 when constructing the SUBSCRIBE message 2
  • the method for carrying the identifier includes: the method 1: carrying the centralized control service identifier sms in the Supported header field of the SUBSCRIBE message 2; and the second method, carrying the centralized control service identifier sms in the Require header field of the SUBSCRIBE message 2.
  • Step 502 After receiving the SUBSCRIBE message 2, the notifier 1 parses the centralized control service identifier from the message, and determines whether to allow centralized control on the current subscription 2. If yes, step 503 is performed; otherwise, the existing Subscription process.
  • Step 503 The notifier 1 judges whether the SUBSCRIBE message 2 is sent by the subscriber 1, and if yes, performs step 504, otherwise, performs the process of creating an SMS for the current subscriber, and ends the current process.
  • step 207 the process of creating an SMS for the current subscriber is the same as step 204 in FIG. 2 above.
  • the principle described in the process of step 207 is identical.
  • the process in which the notifier 1 determines whether the SUBSCRIBE message 2 is sent by the subscriber 1 includes: the notifier 1 judges the remote target in the SMS set by itself and the address of the Contact header field in the SUBSCRIBE message 2 of the current subscription. Whether the parts are the same, if yes, it is determined that SUBSCRIBE message 2 is sent by subscriber 1, otherwise, it is determined that SUBSCRIBE message 2 is not sent by subscriber 1.
  • the notifier 1 can further determine whether the set Route-set of the SMS is the same as the Route-set of the SUBSCRIBE message 2 of the current subscription. That is, it is judged whether the routes from the subscriber 1 to the notifier 1 are the same, and if so, the subsequent subscription centralized control process is continued, that is, step 504 is performed, otherwise, the process of creating an SMS for the current subscriber is performed.
  • Step 504 The notifier 1 carries the centralized control service identifier in the Supported header field of the failure response message, and carries the identifier of the subscription management set that is locally matched or the identifier of the session corresponding to the subscription management set in the SMS of the failure response message. The ID header field is then sent to subscriber 1 for the failure response message.
  • the failure response message may be a failure response message redefined in the embodiment of the present invention, or may be any failure response message of the existing 3XX-6XX.
  • Step 505 The subscriber 1 determines, according to the centralized control service identifier in the Supported header field, that the subscription adopts centralized control, and according to the subscription management set identifier or session carried in the SMS-ID header field of the failure response message. Identifies, locally associated to a session.
  • the subscriber 1 according to the subscription management set identifier or the identifier of the session carried in the SMS-ID header field of the failure response message, the session associated with the local is the subscription management created between the subscriber 1 and the notifier 1 Set the corresponding session.
  • Step 506 Subscriber 1 resends the initial subscription message SUBSCRIBE message 2 to Notifier 1 through the associated session.
  • Step 507 The notifier 1 receives the SUBSCRIBE message 2 on the session associated with the subscription management set, determines to allow the current subscription, and associates the current subscription with the subscription management set.
  • the operation of associating the current subscription with the subscription management set includes at least recording an identifier of the subscription instance corresponding to the current subscription to the subscription management set.
  • Step 508 The notifier 1 constructs a 200 OK response message, and carries the centralized control service identifier sms to the subscriber 1 in the Supported header field of the constructed 200 OK response message.
  • Step 509 After receiving the 200 OK response message, the subscriber 1 associates the subscription with the subscription management set.
  • FIG. 6 is a flow diagram of a second implementation of Subscriber 1 and Notifier 1 joining an existing subscription to a subscription management set in an embodiment of the present invention.
  • the second method is used to implement the subscription for the subscription 3.
  • the process of control includes the following steps:
  • Step 601 Subscriber 1 sends a refresh subscription message SUBSCRIBE message 3 to the notifier 1 through the associated session of the subscription 3, wherein the Supported header field of the SUBSCRIBE message 3 carries the preset option tag, that is, the centralized control service identifier sms.
  • Step 602 After receiving the SUBSCRIBE message 3, the notifier 1 parses the centralized control service identifier from the message, and determines whether to allow centralized control on the current subscription 3. If yes, step 603 is performed; otherwise, the existing subscription is executed. Process.
  • Step 603 The notifier 1 accepts the refresh request for the subscription 3, determines whether the refresh subscription message SUBSCRIBE message 3 is sent by the subscriber 1, and if yes, performs step 604, otherwise, performs the process of creating an SMS for the current subscriber. , ends the current process.
  • step 304 of FIG. 3 the process by which the notifier 1 judges whether the refreshed SUBSCRIBE message 3 is sent by the subscriber 1 is exactly the same as the process of the judgment described in step 304 of FIG.
  • step 604 the subsequent centralized control process is continued, that is, step 604 is performed, otherwise, the process of creating an SMS for the current subscriber is performed.
  • Step 604 The notifier 1 carries the centralized control service identifier in the Supported header field of the failure response message, and carries the identifier of the subscription management set that is locally matched or the identifier of the session corresponding to the subscription management set in the SMS of the failure response message. The ID header field is then sent to subscriber 1 for the failure response message.
  • the failure response message may be a failure response message redefined in the embodiment of the present invention, or may be any failure response message of the existing 3XX-6XX.
  • Step 605 The subscriber 1 determines, according to the centralized control service identifier in the Supported header field of the failure response message, that the subscription adopts centralized control, and only identifies the subscription management set identifier or the session identifier carried in the SMS-ID header field of the failure response message. , is associated locally to a session.
  • the subscriber 1 according to the subscription management set identifier or the identifier of the session carried in the SMS-ID header field of the failure response message, the session associated with the local is the subscription management created between the subscriber 1 and the notifier 1 Set the corresponding session.
  • Step 606 The subscriber 1 resends the subscription message SUBSCRIBE message 3 for the current subscription to the notifier 1 by the session associated with the local.
  • Step 607 The notifier 1 receives the SUBSCRIBE message 3 on the session associated with the subscription management set, determines to allow the current subscription, and associates the current subscription with the subscription management set.
  • Step 608 The notifier 1 constructs a 200 OK response message, and carries the centralized control service identifier sms to the subscriber 1 in the Supported header field of the constructed 200 OK response message.
  • Step 609 After receiving the 200 OK response message, the subscriber 1 associates the subscription with the subscription management set.
  • FIG. 7 is a flow diagram of a third implementation of Subscriber 1 and Notifier 1 joining an initial subscription to a subscription management set in an embodiment of the present invention.
  • Subscriber 1 initiates another subscription to Notifier 1, such as a subscription for B@exampl e.com resources. 2.
  • the process of centrally controlling the subscription 2 between the subscriber 1 and the notifier 1 in the third manner includes the following steps:
  • Step 701 Subscriber 1 constructs an initial subscription message SUBSCRIBE message 2 for subscription 2, and sends the constructed initial subscription message SUBSCRIBE message 2 to notifier 1 through a new session corresponding to subscription 2.
  • the subscriber 1 needs to perform centralized control in order to notify the owner of the resource, that is, the subscriber 1 , and the subscriber 1 carries the preset centralized control service in the SUBSCRIBE message 2 when constructing the SUBSCRIBE message 2
  • the method of carrying the identifier includes: the method 1: carrying the centralized control service identifier sms in the Supported header field of the SUBSCRIBE message 2; and the second, the Require header field in the SUBSCRIBE message 2
  • the centralized control service identifier sms is carried in the middle.
  • Step 702 After receiving the SUBSCRIBE message 2, the notifier 1 parses the centralized control service identifier from the message, and determines whether to allow centralized control on the current subscription 2. If yes, step 703 is performed, otherwise, the existing Subscription process.
  • Step 703 The notifier 1 judges whether the SUBSCRIBE message 2 is sent by the subscriber 1, and if yes, performs step 704, otherwise, performs the process of creating an SMS for the current subscriber, and ends the current process.
  • the process in which the notifier 1 determines whether the SUBSCRIBE message 2 is sent by the subscriber 1 includes: the notifier 1 judges the remote target in the SMS set by itself and the address of the Contact header field in the SUBSCRIBE message 2 of the current subscription. Whether the parts are the same, if yes, it is determined that SUBSCRIBE message 2 is sent by subscriber 1, otherwise, it is determined that SUBSCRIBE message 2 is not sent by subscriber 1.
  • the notifier 1 can further determine whether the set Route-set of the SMS is the same as the Route-set of the SUBSCRIBE message 2 of the current subscription. That is, it is judged whether the routes from the subscriber 1 to the notifier 1 are the same, and if so, the subsequent subscription centralized control process is continued, that is, step 704 is performed, otherwise, the process of creating an SMS for the current subscriber is performed.
  • Step 704 The notifier 1 constructs a 200 OK response message, and carries the centralized control service identifier sms to the subscriber 1 in the Supported header field of the constructed 200 OK response message.
  • Step 705 Notifier 1 will subscribe to the identity of the management set or the corresponding session of the subscription management set
  • the identifier is carried in the SMS-ID header field of the NOTIFY message, the Subscription-State header field value in the NOTIFY message is set to terminated, the value of the reason parameter is set to migration, and the NOTIFY message is sent to subscriber 1.
  • Step 706 After receiving the NOTIFY message, the subscriber 1 sends a 200 OK response message to the notifier 1.
  • subscriber 1 after receiving the NOTIFY message, subscriber 1 sets the value of the Subscription-State header field in the NOTIFY message to be terminated, and the value of the reason parameter is set to migration, and determines that the subscription should be moved to the subscription management set, and then released. A session created specifically for this subscription.
  • Step 707 Subscriber 1 is locally associated to a session according to the subscription management set identifier or the identity of the session carried in the SMS-ID header field of the NOTIFY message.
  • Step 708 Subscriber 1 resends the initial subscription message SUBSCRIBE message 2 to Notifier 1 through the associated session.
  • Step 709. ⁇ Notifier 1 receives the SUBSCRIBE message 2 on the session associated with the subscription management set, determines to allow this subscription, and associates this subscription with the subscription management set.
  • Step 710 The notifier 1 sends a 200 OK response message to subscriber 1.
  • Step 711 After receiving the 200 OK response message, the subscriber 1 associates the subscription with the subscription management set.
  • FIG. 8 is a flow diagram of a third implementation in which subscriber 1 and notifier 1 join an existing subscription to a subscription management set in an embodiment of the present invention.
  • the third method is used to implement the subscription for the subscription 3.
  • the process of control includes the following steps:
  • Step 801 Subscriber 1 sends a refresh subscription by subscribing to the 3 associated sessions.
  • the message SUBSCRIBE message 3 is sent to the informant 1, wherein the Supported header field of the SUBSCRIBE message 3 carries the preset option tag, that is, the centralized control service identifier sms.
  • Step 802 After receiving the SUBSCRIBE message 3, the notifier 1 parses the centralized control service identifier from the message, and determines whether to allow centralized control on the current subscription 3. If yes, step 803 is performed; otherwise, the existing subscription is executed. Process.
  • Step 803 The notifier 1 accepts the refresh request for the subscription 3, determines whether the refresh subscription message SUBSCRIBE message 3 is sent by the subscriber 1, and if yes, performs step 804, otherwise, performs the process of creating an SMS for the current subscriber. , ends the current process.
  • step 304 of FIG. 304 the process by which the notifier 1 judges whether the refreshed SUBSCRIBE message 3 is sent by the subscriber 1 is exactly the same as the process of the judgment described in step 304 of FIG.
  • step 804 the subsequent centralized control process is continued, that is, step 804 is performed, otherwise, the process of creating an SMS for the current subscriber is performed.
  • Step 804 The notifier 1 constructs a 200 OK response message, and carries the centralized control service identifier sms to the subscriber 1 in the Supported header field of the constructed 200 OK response message.
  • Step 805 The notifier 1 carries the identifier of the subscription management set or the identifier of the corresponding session of the subscription management set in the SMS-ID header field of the NOTIFY message, and sets the Subscription-State header field value in the NOTIFY message to the terminated, reason parameter. Value is set to Migration, then send the NOTIFY message to subscriber 1.
  • Step 806 After receiving the NOTIFY message, the subscriber 1 sends a 200 OK response message to the notifier 1.
  • subscriber 1 After receiving the NOTIFY message, subscriber 1 sets the value of the Subscription-State header field in the NOTIFY message to be terminated, and the value of the reason parameter is set to migration, and determines that the subscription should be moved to the subscription management set, then the version is released. Subscribe to the original associated session.
  • Step 807 Subscriber 1 is locally associated to a session according to the subscription management set identifier or the identity of the session carried in the SMS-ID header field of the NOTIFY message.
  • Step 808 Subscriber 1 resends the subscription message SUBSCRIBE message 3 for this subscription to Notifier 1 through the associated session.
  • Step 809 The notifier 1 receives the SUBSCRIBE message 3 on the session associated with the subscription management set, determines to allow the current subscription, and associates the current subscription with the subscription management set.
  • Step 810 Notifier 1 sends a 200 OK response message to subscriber 1.
  • Step 811 After receiving the 200 OK response message, the subscriber 1 associates the subscription with the subscription management set.
  • FIG. 9 is a schematic structural diagram of a system for centrally controlling subscriptions in an embodiment of the present invention.
  • the system provided by the embodiment of the present invention includes: a subscription device and a notification device, where
  • a subscription device configured to establish, with the notification device, a subscription management set and a corresponding session between the two, and after receiving the trigger message sent by the notification device, record the subscription instance corresponding to the current subscription in the subscription management set established by the device Identifies and releases the current subscription and its corresponding session;
  • the notification device is configured to receive the relevant subscription of the current subscription on the session corresponding to the current subscription. And determining whether the related message is sent by the subscriber, and if yes, recording the identifier of the subscription instance corresponding to the current subscription in the subscription management set established by itself, releasing the current subscription and its corresponding session, and A trigger message is sent to the subscribing device.
  • FIG. 10 is a block diagram showing the structure of a subscription device in the embodiment of the present invention.
  • a subscription device according to an embodiment of the present invention includes: a subscription management set implementation unit and a transceiver unit, where
  • a subscription management set implementation unit configured to establish, with the notification device, a subscription management set and a corresponding session between the two, and after receiving the trigger message sent by the transceiver unit, record the subscription corresponding to the current subscription in the subscription management set established by the receiving device The identity of the subscription instance and release the current subscription and its corresponding session;
  • the transceiver unit is configured to send the currently subscribed related message to the notification device, and send the trigger message sent by the notification device to the subscription management set implementation unit.
  • the subscription management set may be configured to carry the preset centralized control service identifier in a first subscription message for the first subscription to the transceiver unit, where After receiving the first notification message carrying the identifier of the subscription management set, the subscription management set is set, and the subscription management set identifier carried in the first notification message is set as the identifier of the subscription management set established by itself, and the established subscription management set is set. Associate with the session corresponding to the first subscription, and record the information associated with the session corresponding to the first subscription and the identifier of the first subscription instance in the established subscription management set;
  • the transceiver unit is further configured to send the first subscription message for the first subscription to the notification device, and send the first notification message that carries the subscription management set identifier sent by the notification device to the subscription management set implementation unit.
  • FIG. 11 is a schematic structural diagram of a notification device in an embodiment of the present invention.
  • the notification device provided by the embodiment of the present invention includes: a subscription management set setting unit and a transceiver unit, where a subscription management set setting unit, configured to set a subscription management set between the subscription device and the corresponding session, and after receiving the related message of the current subscription sent by the transceiver unit, determine whether the related message is the subscription If yes, the identity of the subscription instance corresponding to the current subscription is recorded in the subscription management set established by itself, the current subscription and its corresponding session are released, and the trigger message is sent to the transceiver unit;
  • the transceiver unit is configured to send a related message of the current subscription sent by the subscribing device to the session corresponding to the current subscription to the subscription management set setting unit, and send the received trigger message to the subscribing device.
  • the transceiver unit is further configured to send a first subscription message that carries the centralized control service identifier sent by the subscribing device to the subscription management set setting unit, and that the subscription is to be performed. Sending, by the management set setting unit, a first notification message carrying a subscription management set identifier to the subscription device;
  • a subscription management set setting unit configured to: after the centralized control service identifier is parsed from the first subscription message, establish a subscription management set, set a subscription management set identifier, and set a subscription management set established by itself with the first subscription The association is performed, and the information associated with the session corresponding to the first subscription and the identifier of the first subscription instance are recorded in the subscription management set, and the subscription management set identifier is carried in the first notification message and sent to the transceiver unit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Quality & Reliability (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Economics (AREA)
  • Databases & Information Systems (AREA)
  • Operations Research (AREA)
  • Data Mining & Analysis (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé, un système, un dispositif d'abonnement, dispositif d'information de commande centrale d'abonnement, selon lequel un abonné et un dispositif d'information établissent un ensemble de gestion d'abonnement, et la session correspondante entre eux; le dispositif d'information reçoit le message associé de l'abonnement en cours, et détermine si le message associé de l'abonnement a été envoyé par le dit abonné, si tel est le cas, le dispositif d'information enregistre l'indication correspondant à l'instance d'abonnement de l'abonnement en cours dans l'ensemble de gestion d'abonnement créé par lui-même, et émet l'abonnement en cours et la session y correspondant, et invite l'abonné à réaliser un enregistrement de l'indication correspondant à l'instance d'abonnement de l'abonnement en cours dans l'ensemble de gestion d'abonnement créé par l'abonné, et d'émettre l'abonnement en cours et la session y correspondant.
PCT/CN2007/001046 2006-04-29 2007-03-30 Procédé, système, dispositif d'abonnement, dispositif d'information de commande centrale d'abonnement WO2007124662A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2006100790890A CN101047691B (zh) 2006-04-29 2006-04-29 一种对订阅进行集中控制的方法
CN200610079089.0 2006-04-29

Publications (1)

Publication Number Publication Date
WO2007124662A1 true WO2007124662A1 (fr) 2007-11-08

Family

ID=38655058

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/001046 WO2007124662A1 (fr) 2006-04-29 2007-03-30 Procédé, système, dispositif d'abonnement, dispositif d'information de commande centrale d'abonnement

Country Status (2)

Country Link
CN (1) CN101047691B (fr)
WO (1) WO2007124662A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101562578B (zh) * 2008-04-16 2012-02-01 华为技术有限公司 一种用户数据订阅通知方法及装置
CN101867590B (zh) * 2009-04-14 2013-04-24 华为技术有限公司 基于会话初始化协议的订阅方法和装置
CN104618410B (zh) * 2013-11-04 2019-06-07 腾讯科技（北京）有限公司 资源推送方法和装置
CN104796417B (zh) * 2015-04-08 2018-05-01 大唐移动通信设备有限公司 一种创建订阅业务的方法及装置
CN105657018B (zh) * 2016-01-04 2019-08-16 上海斐讯数据通信技术有限公司 一种订阅远程消息的方法及***

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1638338A (zh) * 2003-12-22 2005-07-13 国际商业机器公司 会话共享的方法与***
EP1610528A2 (fr) * 2004-06-24 2005-12-28 Vodafone Group PLC Système et procédé d'assertion d'identités dans un réseau de télécommunications
US20050289097A1 (en) * 2004-06-23 2005-12-29 Nokia Corporation Method, system and computer program to enable querying of resources in a certain context by definition of sip event package

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100496043C (zh) * 2004-05-20 2009-06-03 华为技术有限公司 获取会话初始协议网络节点状态的方法及***

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1638338A (zh) * 2003-12-22 2005-07-13 国际商业机器公司 会话共享的方法与***
US20050289097A1 (en) * 2004-06-23 2005-12-29 Nokia Corporation Method, system and computer program to enable querying of resources in a certain context by definition of sip event package
EP1610528A2 (fr) * 2004-06-24 2005-12-28 Vodafone Group PLC Système et procédé d'assertion d'identités dans un réseau de télécommunications

Also Published As

Publication number Publication date
CN101047691B (zh) 2010-04-07
CN101047691A (zh) 2007-10-03

Similar Documents

Publication Publication Date Title
JP4391423B2 (ja) エンド・ポイント間のセッションを制御および管理すること
US10341443B2 (en) Multimodal conversation transfer
JP4215645B2 (ja) 通信ネットワークにおけるサービスアクセスと会議システムおよび方法
US20050213580A1 (en) System and method for enforcing policies directed to session-mode messaging
US8953583B2 (en) Method and system for selective call forwarding based on media attributes in telecommunication network
JP2006512855A (ja) エンド・ポイントをグループに加入させ、加入したエンド・ポイントに対して共通の通信性能を決定する方法
US8379544B2 (en) Communications
WO2009070989A1 (fr) Procédé, système et dispositif utiles pour effectuer une procédure de mise en mémoire et pour rechercher des enregistrements d'historiques de sessions
WO2007137485A1 (fr) Procédés et systèmes pour mise en oeuvre de transfert d'appel et réseau domestique de terminal d'utilisateur
WO2009015525A1 (fr) Procédé de commutation de voie de commande de session de service centralisé de sous-système réseau central multimédia ip
WO2009082945A1 (fr) Procédé, système et appareil de communication multiterminal
WO2007098714A1 (fr) Dispositif et procédé de contrôle de session
WO2007090347A1 (fr) Procédé, système et dispositif d'acheminement pour service de système multimédia ip
JP2010515311A (ja) パケット交換ドメインの状態を変化させるための方法、端末及びネットワークデバイス
WO2011017889A1 (fr) Procédé et système de mise en œuvre de conférence multimédia
WO2007124662A1 (fr) Procédé, système, dispositif d'abonnement, dispositif d'information de commande centrale d'abonnement
WO2010069176A1 (fr) Procédé de convocation d'une conférence lorsque des terminaux matériels ont été rattachés à des clients pc, à un serveur d'ouverture de session de ceux-ci, à un serveur de conférence de ceux-ci et à un client pc de ceux-ci
WO2006114059A1 (fr) Procédé et système de détermination du serveur de contrôle central
WO2014114088A1 (fr) Procédé et plate-forme de services pour mise en œuvre d'une fonction de services à haut débit dans un réseau de prochaine génération (ngn)
WO2008000134A1 (fr) Méthode et dispositif de transmission d'un message de demande dans un système multimédia
US20090327426A1 (en) Remote call control and conferencing using paired devices
EP2404434A1 (fr) Procédé et n ud pour des communications améliorées avec un partage temporaire des informations personnelles dans un réseau de communication
WO2010060359A1 (fr) Procédé, dispositif terminal et système de communication pour traitement de service de communication à média enrichi
WO2008011790A1 (fr) Procédé, système et appareil de réseau permettant d'établir une session
WO2008025216A1 (fr) Procédé et système de mise à jour de ressources

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07720620

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07720620

Country of ref document: EP

Kind code of ref document: A1