[go: up one dir, main page]

WO2007062566A1 - Procede et systeme pour la mise en oeuvre de l'abonnement de service - Google Patents

Procede et systeme pour la mise en oeuvre de l'abonnement de service Download PDF

Info

Publication number
WO2007062566A1
WO2007062566A1 PCT/CN2006/002588 CN2006002588W WO2007062566A1 WO 2007062566 A1 WO2007062566 A1 WO 2007062566A1 CN 2006002588 W CN2006002588 W CN 2006002588W WO 2007062566 A1 WO2007062566 A1 WO 2007062566A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
service
subscription
call
event
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2006/002588
Other languages
English (en)
Chinese (zh)
Inventor
Youzhu Shi
Xiao Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
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 WO2007062566A1 publication Critical patent/WO2007062566A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and system for implementing a service subscription.
  • Session Initiation Protocol a mechanism for subscription/notification (SUBSCRIBE/NOTIFY) is provided, and a subscriber can send a SIP SUBSCRIBE message (Session Initiation Protocol subscription message) to a subscriber (notifier).
  • the message carries an event package indicating the subscription information, and the subscriber sends a session initiation protocol notification (SIP NOTIFY message) to the subscriber, and the message carries the subscribed content.
  • SIP NOTIFY message session initiation protocol notification
  • the event packet indicating the subscription information is transmitted by the event header, and the event header can only be advertised through the SIP SUBSCRIBE message, the SIP NOTIFY message, and a session initiation protocol (SIP). PUBLISH message) The message is carried.
  • the subscription/notification mechanism of the SIP protocol provides users with a very flexible method of applying for a service. Users can apply for subscription to various services on their own terminals, such as the online status of a good friend, weather forecast, and A tracing call for a maliciously harassed call.
  • the user's subscription can only be implemented through the SIP SUBSCRIBE message, and the service subscribed to this type of service is not related to the call and does not need to be associated with a specific call.
  • Some services that apply for subscription are related to the call, that is, the application subscription for the service is only valid in a certain call. If the user initiates a call and wants to apply a certain service to the call, the user can temporarily apply for the service to be applied to the specific call. For example, the user initiates a call and wants to apply for an "Advice of Charge" temporarily.
  • the service allows the network to inform him/her of the cost of the call; for example, the user initiates a call and wants to temporarily apply for the "Calling Number Display Restriction" service, so that the network does not put him/her during the call setup process. The number is displayed to the called user.
  • the terminal will send a SIP INVITE message, and the Event header field of the event packet that delivers the user subscription information can only be transmitted in the SIP SUBSCRIBE message, so the current SIP protocol subscription mechanism cannot implement the user.
  • "Temporary" The requirement for a subscription service to act on a particular call.
  • the general method is to use a separate header in the SIP INVITE message to indicate the above-mentioned service information applied at the time of call initiation, such as TISPAN at the European Telecommunications Standards Institute ETSI (Telecommunications and Internet Converged Services and Protocols for Advanced Networking )
  • TISPAN at the European Telecommunications Standards Institute ETSI (Telecommunications and Internet Converged Services and Protocols for Advanced Networking )
  • ETSI Telecommunications and Internet Converged Services and Protocols for Advanced Networking
  • a P-AOC header field is used to indicate the application for the "billing notification" service when the call is initiated
  • a Privacy header field is used to indicate when the call is initiated. "Calling number display restriction" business application.
  • some services may be applied at the time of call initiation, or may not be applied when the call is initiated, such as the aforementioned "charge notification” service.
  • the user does not apply for the service when the call is initiated, but wants to query during the call. How much has already occurred, the user applies for a subscription to the "billing notification" service during the call. Obviously, the subscription at this time is still carried out by using the SIP SUBSCRIBE message carrying the event package.
  • the application for the service is indicated by a separate header field, and it is difficult to feed back the information of the service application success or failure to the user, because the purpose of the SIP INVITE message is to establish a call for a call, and its SIP session is established.
  • the process is for this purpose, there is no more consideration of the application status of such call-related services, obviously Even if the business application fails, the call cannot be established.
  • the above-mentioned "calling number display restriction" service the network succeeds or fails in this service application, according to the current standard process, the calling user who applies for the service is not known.
  • the prior art carries a separate header field through the SIP INVITE message to indicate the service information applied at the time of the call initiation.
  • the object of the present invention is to provide a method and system for implementing a service subscription.
  • the method for overcoming the service is to be carried out by the SIP INVITE message to indicate the service information applied at the time of the call initiation, so that the SIP protocol becomes uncontrollable and the implementation process is implemented.
  • the invention is inconsistent and brings waste of resources.
  • the present invention follows the existing mechanism of the SIP protocol, maintains the integrity of the existing mechanism of the SIP protocol, and makes the business application result transparent to the user, thereby improving user satisfaction.
  • a method for implementing a service subscription according to the present invention is applied to a network that provides a service by using a session initiation protocol, and the method includes:
  • the header field carries one or more event packets indicating subscription information related to the current session initiation protocol session;
  • the service control node of the service receives the event package, performs corresponding processing, and sends a notification message carrying the service application information to the service subscriber.
  • the header field is an event header field, which is carried by other session initiation protocol messages other than the subscription message and the notification message.
  • the event header field carries a plurality of the event packets.
  • the header field is a newly extended session initiation protocol header field, and the header field is carried by other session initiation protocol messages other than the subscription message and the notification message.
  • the newly extended session initiation protocol header field carries a plurality of the event packets.
  • the session initiation protocol session message of the non-subscription message is a call message, and includes a session initiation protocol invite message or a session initiation protocol instant message.
  • the user terminal initiates the call message carrying the event package, and the service control node receives the event package, and if the user terminal is allowed to subscribe to the service, when the notification condition is met, Sending a notification message including the service application related information to the user terminal.
  • the notification message is a session initiation protocol notification message, or a session initiation protocol release message, or a session initiation protocol response code message.
  • the service subscription is not applied, and when the service subscription is applied after the call is established, the application subscription is completed by the event header field in the session initiation protocol subscription message, and the service is performed.
  • the control node receives the event packet and performs corresponding service processing.
  • the user terminal initiates the call message that does not carry the event packet, and after receiving the call message, the first network element in the network inserts the event package in the call message according to the preset information of the service and the current session situation. , sent to the service control node; or,
  • the user terminal initiates the call message carrying the event packet, and sends the call message to the service control node via the second network element in the network.
  • the first network element or the second network element receives a notification message that includes information about the service application, and if the notification message is a session initiation protocol notification message, converting the notification message into a session initiation protocol release message. Or a session initiation protocol response code message, sent to the user terminal;
  • the notification message is a session initiation protocol release message
  • the message is forwarded to the user terminal, or converted into a session initiation protocol response code message and sent to the user terminal.
  • the first network element or the second network element creates a subscription instance for it.
  • the user terminal initiates the call message carrying the event package, after receiving After the notification message, a subscription instance is created for the event package carried in the notification message.
  • the event packet carried in the session initiation protocol response code message is delivered through a newly extended session initiation protocol header field or an event header field.
  • the user terminal, or the first network element, or the second network element initiates the call message carrying the event package, creates a dialog for the subscription corresponding to the event package, and creates a different dialog respectively.
  • the session parameters corresponding to the subscription are carried in the header field.
  • the user terminal initiates the call message carrying the event package to indicate whether the user terminal creates a subscription instance for the event package.
  • the call message indicates whether the user terminal creates a subscription instance for the event package by supporting the content of the header field.
  • a system for implementing a service subscription is provided, and the system is disposed in a network that provides services by using a session initiation protocol, including:
  • a subscriber configured to carry one or more event packets indicating subscription information related to the current call related service in a session initiation protocol session message of the non-subscribed message sent by the subscriber;
  • the notifier is configured to receive the event package, perform corresponding processing, and send a notification message carrying the service application information to the subscriber.
  • the event packet is carried by a session initiation protocol header field, which is an event header field or a new extension header field.
  • the session initiation protocol session message of the non-subscription message is a call message, and includes a session initiation protocol invite message or a session initiation protocol instant message.
  • the notification message is a session initiation protocol notification message, or a session initiation protocol release message, or a session initiation protocol response code message.
  • the session initiation protocol response code message carries the event package.
  • the session parameters corresponding to the subscription are carried in the header field.
  • the notification message is converted into a session initiation protocol.
  • a cloth message or a session initiation protocol response code message is sent to the originator of the call message.
  • the present invention provides a method for subscribing to a service at the time of call initiation, which is consistent with the current SIP subscription/notification mechanism, and may carry an event packet indicating the subscribed service information through the call message.
  • an event packet indicating the subscribed service information is transmitted through a fixed header field, and only one event package needs to be defined for a subscribed service, and no separate independent header fields need to be extended, and SIP is still used.
  • the existing mechanism of the protocol maintains the integrity of the existing mechanisms of the SIP protocol.
  • the event packet can also be transmitted in the SIP SUBSCRIBE message through the Event header field, that is, for those services that can be applied at the time of call initiation or not at the time of call initiation, the same event package can be defined in different application scenarios. Under the use, the process after the successful business application subscription is basically the same.
  • the service control node may notify the user terminal of the success or failure of the service application by using the SIP NOTIFY/PUBLISH message and the SIP response code that can carry the event package.
  • the present invention has wider applicability and versatility, makes the implementation of the business more compact, and makes the business application results transparent to the user and improves user satisfaction.
  • FIG. 1 is a flowchart of implementing a charging notification service subscription when a call is initiated according to an embodiment of the present invention
  • FIG. 2 is a flow chart showing an implementation of a charging notification service subscription during a call according to an embodiment of the present invention
  • FIG. 3 is a flowchart of another implementation of performing a charging notification service subscription when a call is initiated according to an embodiment of the present invention
  • FIG. 4 is a flowchart of an implementation of performing a charging notification service subscription when a call is initiated in a case where an event publishing agent is not in a service control node according to an embodiment of the present invention.
  • the prior art indicates that the method for applying for a service at the time of call initiation is not desirable through a separate header field. Based on this, the present invention will give a type and current SIP subscription/pass in the SIP protocol. The method for applying subscription to the service when the call is initiated is carried out, and the event packet indicating the subscribed service information is carried by the SIP INVITE message.
  • the problem to be solved by the present invention is that the application subscription method for the service at the time of call initiation still uses the current SIP subscription/notification mechanism, and still uses the event package to represent the information of the subscribed service.
  • the Event header field can be carried by the SIP INVITE message; or a new header field can be extended to also pass an event packet indicating the subscribed service information, the header field passing the SIP INVITE message. carry.
  • Event R m m needs to be modified to:
  • Event R o - - - m m means that the Event header field is mandatory for the SUBSCRIBE and NOTIFY messages, and optional for the INVITE message.
  • the present invention newly expands a header field that can be carried by SIP messages other than the SUBSCRIBE message, the NOTIFY message, and the PUBLISH message, and which conveys the event packet indicating the subscribed service information, for example, named P-SUB.
  • P-SUB the definition format of the Event header field in the SIP protocol
  • the definition format of P-SUB is as follows:
  • Event-template token-nodot
  • Token-nodot 1*( alphanum / / »! ⁇ / "%" /
  • event-param generic-param I ( "id” EQUAL token ) where sub-event indicates the pass in the P-SUB header field
  • event package indicating the subscribed service information, which includes the event package type event-type and the parameter event-param, and the definitions of the event-type and event-param are identical to those in the Event header field, and the present invention will not be explained in detail.
  • the difference from the definition format of P-SUB is that the P-SUB header field can pass multiple event packets indicating the subscribed service information, and only one event can be delivered in the Event header field. package. This is because the user may apply for subscription to multiple services when the call is initiated, such as applying for "billing notification” and "calling number display restriction” at the same time.
  • the following describes how the user applies for the subscription of the "charge notification” service when the call is initiated, and applies for the subscription of the "charge notification” service during the call, and explains how to use the SIP INVITE message and the SIP SUBSCRIBE.
  • the event packet is passed in the message to indicate the "accounting notification" service subscription information, so as to achieve the purpose of not extending a separate header field (P-AOC), a service subscription has only one corresponding event package.
  • the service to be subscribed for is provided by a logical network element such as a service control node to provide a service logic control and execution environment, which may exist in a network entity (such as an application server), or even exist in Among user terminals.
  • a logical network element such as a service control node to provide a service logic control and execution environment, which may exist in a network entity (such as an application server), or even exist in Among user terminals.
  • the user subscribes to the "Billing Notification" service subscription process when the call is initiated.
  • the SIP terminal user A calls the user B.
  • the application uses the charging notification service.
  • the SIP INVITE message sent by the terminal has the following contents:
  • INVITE sip mary@tele.com SIP/2.0
  • P-SUB aoc-message
  • the P-SUB header field is used to deliver an event packet aoc-message indicating "accounting notification" service subscription information.
  • the charging notification service event package aoc-message is an extension of the present invention
  • P- The value "aoc-message" of the event type (event-type) in the SUB header field and the Event header field described below is the event package name.
  • the scope of the Event header field is extended, and the Event header field can also be passed in the SIP INVITE message:
  • SIP terminal A as a subscriber for SIP-compliant subscription/notification mechanisms
  • the service control node receives the SIP INVITE message and sends it to the called party.
  • the service control node receives the 200 OK response code and sends it to the calling party.
  • the called party has already responded, and the service control node determines, according to the aoc-message event packet previously parsed from the P-SUB header field in the SIP INVITE message, that if the user A has the right to apply for the charging notification service, the service application Successfully, as a notifier, create a subscription instance of the event package, and carry the event package that the subscription is successfully accepted through the P-SUB header field or the Event header field in the 200 OK response code:
  • P-SUB aoc-message
  • the charging notification information of the current call can be carried in the 200 OK response code, and can generally be carried by the message body of the response code.
  • SIP terminal A receives the 200 OK response code and returns an ACK confirmation message.
  • SIP terminal A parses out the aoc-message event package from the 200 OK response code, and matches the event package of the created transaction to create a subscription instance of the event package.
  • the SIP terminal of the user A can also extract the charging notification information.
  • the service control node sends an ACK confirmation message to the SIP terminal of user B, the user The session between A and user B is established, and the two parties start talking.
  • the service control node calculates the rate of the current call, and may calculate the cost of the call in advance.
  • the message body carrying the SIP NOTIFY message carries the charging notification information to the SIP terminal of user A, which must be in the SIP NOTIFY message. Indicate the corresponding event package:
  • User A's SIP terminal receives the SIP NOTIFY message, extracts the rate or fee of the call from the message body, and returns a 200 OK response code.
  • the service control node receives the SIP BYE message and sends it to the calling party.
  • SIP terminal A receives the SIP BYE message, releases the call, and returns a 200 OK response code.
  • the service control node receives the 200 OK response code and sends it to the called party.
  • the service control node determines that the related information of the call is completely released, and the subscription notification service subscribed by the user also ends, and the call charge that has occurred is calculated, and the message body carrying the SIP NOTIFY message carries the charging notification information to the User A's SIP terminal, in the SIP NOTIFY message, must specify the corresponding event package, and indicate the end of the service application by the value of the Subscription-State header field, which is "terminated", and release the subscription instance:
  • the reason parameter can also be used to set the reason for the end of the business application. It can be seen that, in this embodiment, the validity period of the billing notification service starts when the call is established, and when the call is over, the release of the service subscription instance is determined by the service control node.
  • User A's SIP terminal receives the SIP NOTIFY message, extracts the cost of the call from the message body, releases the subscription instance, and returns a 200 OK response code.
  • the user response terminal and the service control node pass the SIP response code for the INVITE message (in the embodiment, the 200 OK response code, and may also be 183 Session Progress).
  • the event package carried in the response code indicates which event packets have been accepted by the service control node, and the user terminal only responds to the SIP.
  • the user terminal can create a transaction for the event package, that is, in step 5, the user terminal can transmit the event packet carried in the SIP response code and the transaction that has been created.
  • the event packets match, and the corresponding subscription instance can also be created according to the event package carried in the SIP response code.
  • the user terminal here creates an subscription instance of the event package according to the event package returned by the service control node and has agreed to subscribe, so that even if the SIP response code does not pass the extension to carry the event package (if necessary, The SIP response code can still carry the service application information, as shown in step 4 of FIG. 1 , and the user terminal can also directly send the NOTIFY message that the subscription request has been accepted according to the first one sent by the service control node.
  • the event package carried in (NOTIFY message sent in step 7 of Figure 1) is used to create a subscription instance of the event package.
  • the event packet returned by the service control node (through the SIP response code or NOTIFY message) will indicate that the event packet has been agreed to be subscribed by the service control node and the corresponding subscription instance is created, so the user terminal can return according to the service control node.
  • the event package to create the corresponding subscription instance will indicate that the event packet has been agreed to be subscribed by the service control node and the corresponding subscription instance is created, so the user terminal can return according to the service control node.
  • the subscription instance created on the user terminal can only be attached to the dialog. That is, the call and subscription will share a single dialog.
  • the service control node Since the dialog is established end-to-end, and the subscription instance exists only between the SIP terminal A and the service control node, the service control node will be a call established by the SIP INVITE message as a back-to-back user agent (B2BUA).
  • B2BUA back-to-back user agent
  • SIP terminal A and the service control node establish a dialog.
  • the service control node and the service control node establish another dialog, and the subscription instance uses SIP.
  • the subscription and the call share a dialog. If the subscription and the call do not share a dialog, that is, the subscription establishes a separate dialog, then the SIP terminal A needs to send the SIP INVITE message in step 1, indicating separately.
  • the subscribed dialog such as the extended P-SUB header field, carries the Call-ID parameter and the From-tag parameter necessary to create the dialog.
  • the message example is as follows: INVITE sip:mary@tele.com SIP/2.0
  • the service control node can carry the To-tag parameter in the returned P-SUB header field in step 4.
  • the message example is as follows:
  • the route set subscribed to the dialog reuses the route set established by the call between the SIP terminal A and the service control node, that is, the same signaling path, the subscription and the call respectively establish two dialogs, and the method is also applicable to the latter.
  • the route set subscribed to the dialog reuses the route set established by the call between the SIP terminal A and the service control node, that is, the same signaling path, the subscription and the call respectively establish two dialogs, and the method is also applicable to the latter. Example.
  • each event package has its own subscription instance, when the INVITE message carries more than one event package, if these event packages do not share the dialog of the call, you need to create one for each subscription instance corresponding to the event package. Dialog, that is, for the above P-SUB header field, each event packet must have its corresponding dialog parameter.
  • the subscription process for the "billing notification" service is specified in the call as follows: 1) SIP terminal user A calls user B to issue a SIP INVITE message.
  • the service control node receives the SIP INVITE message and sends it to the called party.
  • the service control node receives the 200 OK response code and sends it to the calling party.
  • User A's SIP terminal receives the 200 OK response code and returns an ACK confirmation message.
  • the service control node sends an ACK confirmation message to the SIP terminal of user B, and the session between user A and user B is established, and the two parties start a call.
  • SIP terminal A acts as a subscriber to create a transaction for the event package aoc-message.
  • the service control node receives the SIP SUBSCRIBE message, and parses the aoc-message event packet from the Event header field. If the user A has the right to apply for the charging notification service, the service application is successful, and the service control node creates the subscription instance as the notifier. , returns a 200 OK response code.
  • SIP terminal A receives the 200 OK response code that agrees to subscribe, and creates a subscription instance for the event package aoc-message.
  • the service control node calculates the cost of the current call.
  • the message body of the SIP NOTIFY message carries the SIP terminal sent to the user A, and may also carry the rate of the current call.
  • the corresponding event package must also be specified in the SIP NOTIFY message:
  • User A's SIP terminal receives the SIP NOTIFY message, extracts the cost or rate of the call from the message body, and returns a 200 OK response code.
  • the user actively carries an event packet indicating the subscribed service information in the INVITE message sent by the user, but the user may also initiate the method.
  • the INVITE message does not carry related things
  • the network After receiving the INVITE message sent by the user, the network inserts an event packet indicating the subscribed service information into the INVITE message according to the service subscription information of the user and the current call status, and then sends the event packet to the subsequent service.
  • the control node processes the subscription application for the subscribed service.
  • the called user subscribes to the CRBT service, and the calling user initiates a call.
  • the network element the first network element in the network receives the CRBT subscription information and the calling party number of the called user. If it is determined that the CRBT is applied to the call request, an event packet indicating that the subscription CRBT service is applied to the INVITE message is sent to the service control node that provides the CRBT.
  • the subscription instance of the event package indicating the subscription service is created on the network element (subscriber) and the service control node (notifier), and the user terminal does not have a subscription instance as the originator of the INVITE message, which is equivalent to the
  • the network element creates a subscription instance of the service for the user terminal.
  • the network element receives the SIP NOTIFY subscription notification message from the service control node, if the user needs to notify the application of the service, the message may be converted into a SIP PUBLISH message or a suitable response code, and sent to the network.
  • the user terminal of course, if the network element receives the SIP PUBLISH message carrying the service application information, it can forward it to the user terminal, or convert it into a suitable response code and send it to the user terminal.
  • the technical solution of the present invention is consistent with the current SIP subscription/notification mechanism.
  • the service control node sends a SIP NOTIFY subscription notification message to the user just like the SIP SUBSCRIBE message.
  • the service control node can notify the user of the success or failure of the service application by using the event packet indicating the subscription service and the SIP NOTIFY message carried in the SIP response code of the SIP INVITE message.
  • the existing SIP subscription/notification mechanism is used, and when the user initiates the call, the event packet carrying the subscribed service information is carried, and the subscription instance of the event package is created on the user terminal and the service control node, and the network
  • the user terminal sends a SIP NOTIFY subscription notification message to carry related application content of the subscribed service.
  • SIP protocol in addition to the SIP NOTIFY subscription notification message, there is also a SIP PUBLISH message that can also carry an event packet and indicate the relevant content of the event packet. Therefore, The user can also carry the event packet indicating the subscribed service information when the user initiates the call, and the network sends the SIP PUBLISH message to the user terminal to carry the related application content of the subscribed service. At this time, the user terminal does not need to create the subscription instance of the event package.
  • the application of the PUBLISH message is more to the user terminal transmitting to the network.
  • the SIP terminal is required to support the reception of the PUBLISH message and the maintenance of the PUBLISH state.
  • the SIP terminal user A calls the user B.
  • the application uses the charging notification service.
  • the SIP INVITE message sent by the terminal has the following contents:
  • P-SUB aoc-message
  • the service control node receives the SIP INVITE message and parses the aoc-message event packet from the P-SUB header field. If user A has the right to apply for the accounting notification service, the service application is successful.
  • the service control node receives the 200 OK response code and sends it to the calling party.
  • User A's SIP terminal receives the 200 OK response code and returns an ACK confirmation message.
  • the service control node sends an ACK confirmation message to the SIP terminal of user B, and the session between user A and user B is established, and the two parties start a call.
  • the service control node calculates the rate of the current call, and may calculate the cost of the call in advance.
  • the message body of the SIP PUBLISH message carries the SIP terminal sent to the user A, and the corresponding event must be specified in the SIP PUBLISH message.
  • the SIP terminal of user A receives the SIP PUBLISH message, extracts the rate or fee of the current call from the message body, and starts the maintenance of the PUBLISH state.
  • the monitoring duration of the maintenance state comes from the Expires header carried in the SIP PUBLISH message. Field value (3600 seconds), Returns the 200 OK response code.
  • SIP terminal B user hangs up and puts a call, and sends a SIP BYE message.
  • the service control node receives the SIP BYE message and sends it to the calling party.
  • SIP terminal A receives the SIP BYE message, releases the call, and returns a 200 OK response code.
  • the service control node receives the 200 OK response code and sends it to the called party.
  • the service control node determines that the related information of the call is completely released, and the charging notification service subscribed by the user also ends, and the call charge that has occurred is calculated, and the SIP body sends the SIP message sent to the user A through the message body of the SIP PUBLISH message.
  • the terminal must indicate the corresponding event packet in the SIP PUBLISH message, and indicate the end of the service application by taking the value of the Expires header field as "0":
  • the SIP terminal of user A receives the SIP PUBLISH message, extracts the cost of the call from the message body, stops the maintenance of the PUBLISH state, and returns a 200 OK response code.
  • the Event Publication Agent that issues the event by sending a SIP PUBLISH message is located on the service control node.
  • the event publishing agent may not be located on the service control node (ie, the service control node does not It has the ability to send SIP PUBLISH message publishing events, but is located on another independent network element (second network element).
  • Figure 4 The implementation process at this time is shown in Figure 4, which is described as follows:
  • the SIP terminal user A calls the user B.
  • the application uses the charging notification service.
  • the SIP INVITE message sent by the terminal has the following contents:
  • P-SUB aoc-message
  • the event publishing agent receives the SIP INVITE message, parses the aoc-message event package from the P-SUB header field, creates a transaction for the event package, and sends the SIP INVITE message to the service.
  • the control node sends.
  • the service control node receives the SIP INVITE message and sends it to the called party.
  • User B's SIP terminal receives the SIP INVITE message, User B picks up the phone and sends a 200 OK response code.
  • the event publishing agent receives the 200 OK response code and sends it to the calling party.
  • the service control node receives the 200 OK response code and sends it to the calling party.
  • User A's SIP terminal receives the 200 OK response code and returns an ACK confirmation message.
  • the event publishing agent receives the ACK confirmation message and sends it to the called party.
  • the service control node sends an ACK confirmation message to the SIP terminal of user B, and the session between user A and user B is established, and the two parties start a call.
  • the session is established, and the service control node determines, according to the aoc-message event packet parsed from the P-SUB header field, that if the user A has the right to apply for the charging notification service, the service application is successful, and the service control node creates the session. Subscription instance of the event package
  • the service control node calculates the rate of the call, and may calculate the cost of the call in advance.
  • the message body of the SIP NOTIFY message carries the message to the calling party. The corresponding event must be specified in the SIP NOTIFY message.
  • the event publishing agent receives the SIP NOTIFY message, parses the aoc-message event package from the P-SUB header field, and matches the created transaction to create a subscription instance of the event package.
  • the event publishing agent converts the SIP NOTIFY message into a SIP PUBLISH message carrying the rate and/or cost of the call.
  • the corresponding event packet must be indicated in the message, and the monitoring duration for maintaining the PUBLISH state is indicated by the Expires header field:
  • the SIP terminal of user A receives the SIP PUBLISH message, extracts the rate or fee of the current call from the message body, and starts the maintenance of the PUBLISH state.
  • the monitoring duration of the maintenance state comes from the Expires header carried in the SIP PUBLISH message.
  • the value of the field (3600 seconds) returns the 200 OK response code.
  • the event publishing agent receives a 200 OK response code for the SIP PUBLISH message, A 200 OK response code to the SIP NOTIFY message is sent to the service control node.
  • the event publishing node and the service control node can only create a subscription instance for the event package, and the service control node sends a SIP NOTIFY subscription notification message to the service control node.
  • the event issuance agent which converts the SIP NOTIFY message into a SIP PUBLISH message and sends it to the user. Of course, as described above, it can also be converted into an appropriate response code and sent to the user.
  • the event publishing agent has the event publishing capability, the SIP terminal of the user A and the event publishing agent constitute a pair of subscribers and notifiers, and maintain the PUBLISH state of the event package;
  • the event publishing agent is the subscriber to the event package, which creates a subscription instance for the event package for the subscriber and the notifier.
  • the event publishing agent similarly, similarly, the event publishing agent
  • a user applying for a service subscription when initiating a call may create a subscription instance for the event package (Example 1, as shown in FIG. 1 and FIG. 2), or may not create a subscription instance (
  • the second embodiment as shown in FIG. 3 and FIG. 4, when the entire network adopts the same technical solution, there is obviously no problem, but when the entire network is not using the same technical solution, there may be a problem of cooperation, such as a user terminal.
  • the technical solution of the second embodiment is adopted, and the network device adopts the technical solution 1 as described in Embodiment 1.
  • the user terminal After receiving the SIP response code carrying the event package, the user terminal does not create a subscription instance. It will not be able to receive SIP NOTIFY messages sent by subsequent networks. Obviously, the business application will fail due to an error.
  • the user terminal needs to indicate the technical solution supported by the user in the SIP INVITE message when initiating the call application service subscription, and indicate whether the user terminal supports the technical solution 1 or the technical solution by using the content of the Supported header field notifmg or publishing.
  • the network will handle the corresponding processing accordingly. For example, if the content of the Supported header field is publishing, the network will need to initiate the event publishing capability, route the call INVITE message to a network entity with the event publishing agent capability, and send the SIP.
  • the PUBLISH message is sent to the user terminal instead of the SIP NOTIFY message.
  • the call message of the present invention includes a SIP INVITE message and a SIP MESSAGE message. That is, the event packet indicating the subscribed service information can also be transmitted through a fixed header field in the SIP MESSAGE message. For example, user A sends an instant message to user B, and requests a "charge notification" service to learn the instant message.
  • the cost incurred, an example of the SIP message sent by User A is as follows:
  • P-SUB aoc-message
  • the user terminal described in the present invention may be a terminal device that supports the SIP protocol, such as a SIP phone, a SIP phone, or the like, or a SIP user agent that supports the SIP protocol and manages the legacy terminal device.
  • the device such as a SIP IAD (Integrated Access Device), can connect a legacy terminal device that does not support the SIP protocol to a network that provides services by using the SIP protocol.
  • the present invention is equally applicable to a network initiated call in which a subscription to a service is represented by an event package carried.
  • an event packet indicating the subscribed service information is transmitted through a fixed header field. Only one event package needs to be defined for a subscribed service, and there is no need to extend different independent header fields, and the existing SIP protocol is still used. The mechanism maintains the integrity of the existing mechanisms of the SIP protocol.
  • the event packet can also be transmitted in the SIP SUBSCRIBE message through the Event header field, that is, for those services that can be applied at the time of call initiation or not at the time of call initiation, the same event package can be defined in different application scenarios. Under the use, the process after the successful business application subscription is basically the same.
  • the service control node may
  • SIP NOTIFY/PUBLISH message and the SIP response code are used to notify the user of the success or failure of the service application, and the business application result is transparent to the user, and the user's service experience is good.
  • the present invention also provides a corresponding system for implementing a service subscription.
  • the network providing the service by the session initiation protocol includes: a subscriber, for carrying one or more representations in the session initiation protocol session message of the non-subscribed message sent by the subscriber An event package that is subscribed to the service related to the current call; the notifier is configured to receive the event package, and send a notification message carrying the service application information to the subscriber.
  • the working principle and method of the system are the same as those described above for the service subscription method when calling, and will not be described here.
  • the solution of the present invention has wider applicability and versatility, makes the implementation of the service more concise, and makes the business application result transparent to the user, thereby improving user satisfaction.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Procédé et système pour la mise en oeuvre de l'abonnement de service, dans le réseau de service établi par protocole SIP ; un en-tête dans le message de session SIP du message de non-abonnement lancé par le terminal utilisateur achemine l'information de module d'événement indiquant que le service associé à la session SIP en cours fait l'objet d'un abonnement; le noeud de contrôle de service correspondant reçoit ce module et accomplit l'opération de service, s'il accorde l'invitation d'abonnement du terminal utilisateur pour le service considéré, puis lorsque la condition de notification est satisfaite, le message de notification est envoyé avec l'information associée à l'application de service. On résout ainsi le problème actuel, qui réside dans le fait que l'indication de l'information d'invitation de service se fait par message SIP INVITE portant un en-tête de confidentialité lorsque l'appel est lancé, moyennant quoi le protocole SIP n'est pas contrôlé, ce qui entraîne la désunification du flux de réalisation et le gaspillage de ressources ; l'avantage consiste à permettre au flux d'abonnement de continuer à utiliser le mécanisme existant du protocole SIP et donc à rendre l'application de service transparente pour l'utilisateur, ce qui renforce l'expérience d'utilisation du service.
PCT/CN2006/002588 2005-11-29 2006-09-29 Procede et systeme pour la mise en oeuvre de l'abonnement de service Ceased WO2007062566A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510101952.3 2005-11-29
CN200510101952 2005-11-29

Publications (1)

Publication Number Publication Date
WO2007062566A1 true WO2007062566A1 (fr) 2007-06-07

Family

ID=38091861

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/002588 Ceased WO2007062566A1 (fr) 2005-11-29 2006-09-29 Procede et systeme pour la mise en oeuvre de l'abonnement de service

Country Status (1)

Country Link
WO (1) WO2007062566A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101399781B (zh) * 2007-09-26 2012-05-23 华为技术有限公司 一种消息发送方法、系统、消息发送装置及消息服务器
CN103999425A (zh) * 2012-07-06 2014-08-20 华为技术有限公司 呈现服务器发现非呈现用户业务能力的方法和相应装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040255302A1 (en) * 2003-06-10 2004-12-16 Nokia Corporation Systems and methods for content and service registration, query and subscription, and notification across local service discovery domains
WO2005025130A1 (fr) * 2003-09-03 2005-03-17 Siemens Aktiengesellschaft Procede d'information et systeme de communication
CN1663216A (zh) * 2002-06-14 2005-08-31 诺基亚公司 使用sip协议的事件订阅方法与系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1663216A (zh) * 2002-06-14 2005-08-31 诺基亚公司 使用sip协议的事件订阅方法与系统
US20040255302A1 (en) * 2003-06-10 2004-12-16 Nokia Corporation Systems and methods for content and service registration, query and subscription, and notification across local service discovery domains
WO2005025130A1 (fr) * 2003-09-03 2005-03-17 Siemens Aktiengesellschaft Procede d'information et systeme de communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"RFC 3265, Session Initiation Protocol (SIP-Specific Event Notification", IETF STANDARD, June 2002 (2002-06-01), pages 1 - 29, XP015009043 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101399781B (zh) * 2007-09-26 2012-05-23 华为技术有限公司 一种消息发送方法、系统、消息发送装置及消息服务器
CN103999425A (zh) * 2012-07-06 2014-08-20 华为技术有限公司 呈现服务器发现非呈现用户业务能力的方法和相应装置

Similar Documents

Publication Publication Date Title
US6512818B1 (en) Method and system for releasing a voice response unit from a protocol session
EP2055076B1 (fr) Mécanisme de facturation et de gestion de session prenant en charge le partage dynamique
CN101345845B (zh) 一种在ims环境中实现视频会议业务的方法
US8379544B2 (en) Communications
US20070153770A1 (en) System and method for feature-based services control using SIP
CN101394294B (zh) 网络多媒体会议接入方法、系统及装置
WO2007098706A1 (fr) Procédé permettant de transmettre des données de service et terminal de paquets utilisé dans ce procédé
CN101815067A (zh) 一种多媒体会议的实现方法和系统
JP5437257B2 (ja) パケット交換ベースのネットワークにおいてリアルタイムビリング情報を生成するための方法、およびネットワーク要素
WO2007112640A1 (fr) Procédé et appareil de remplacement de l'identification de session, serveur d'application et procédé de remplacement de session
CN102111415A (zh) 嵌入VoIP的交互式网络语音应答系统及其实现方法
WO2007093116A1 (fr) Procédé et système de fourniture de service de simulation et entité adaptative de signalisation d'accès
CN1901550B (zh) 基于会话发起协议的订阅方法及其系统和装置
WO2011153752A1 (fr) Procédé, système et serveur d'applications pour la mise en œuvre d'un transfert d'appel dans un service « click to dial »
US8160224B2 (en) Method, apparatus and system for implementing conference service
KR101009846B1 (ko) Ｓｉｐ 단말장치에서 서비스 이용 요금을 실시간으로제공하는 방법 및 그 ｓｉｐ 단말장치
CN101365157A (zh) 一种业务触发方法、系统及装置
KR100959019B1 (ko) ＳＩＰ 기반의 프락시 서버에서의 ＳＩＰ 메시지ｆｏｒｋｉｎｇ을 이용한 실시간 과금 데이터 수집 방법
WO2013040832A1 (fr) Procédé, dispositif et système permettant à l'opérateur d'insérer un appel dans un service de standard téléphonique
CN100563219C (zh) 实现点击拨号的系统及方法
WO2007062566A1 (fr) Procede et systeme pour la mise en oeuvre de l'abonnement de service
WO2007109950A1 (fr) Procédé et système pour réaliser une interaction vocale
CN100433751C (zh) 一种第三方控制业务的实现方法和应用服务器
WO2007028329A1 (fr) Procede de realisation d'operation d'activation de service et terminal utilisateur realisant ledit procede
CN101123524B (zh) 用于实现会议业务的方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06791174

Country of ref document: EP

Kind code of ref document: A1