WO2008083582A1

WO2008083582A1 - A service trigger method, system and service trigger apparatus

Info

Publication number: WO2008083582A1
Application number: PCT/CN2007/071321
Authority: WO
Inventors: Youzhu Shi; Sang Wu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-01-11
Filing date: 2007-12-25
Publication date: 2008-07-17
Also published as: CN101222483A

Abstract

A service trigger method includes: monitoring the service trigger event; determining to trigger a plurality of service control point according to the service trigger event; triggering a plurality of service control point. A service trigger system and service trigger apparatus are provided based on said method, it invokes a plurality of service control point based on the same one service trigger event without returning back the initial request message based on the service control point after triggering one service control point, in order to trigger the next service control point, it can ensure the trigger of the subsequent service control point, and improve the efficiency of the trigger process.

Description

Service triggering method, system and service triggering device

The present invention relates to the field of communications technologies, and in particular, to a service triggering method, system, and service triggering apparatus. Background of the invention

The IP Multimedia Subsystem (IMS) is a Session Initiation Protocol (SIP) based system introduced in the 3rd Generation Mobile Communications Standards Partnership Project (3GPP) Release 5. The session layer of the IMS is separated from the service layer, and the session-layer service-call session control function (S-CSCF) triggers the service layer application server, including the SIP application server (AS), through preset initial filter rule (iFC) data. Open Service Access Service Capability Server (OSA SCS IP Multimedia Service Switching Function (IM-SSF).

In the existing 3GPP TS 29.288 standard, an iFC data may include 0 or 1 Trigger Point description, 1 Priority (Nority) number description, 1 Server Name description, and AS not available. Description of Default Handling when routing. The description of the above trigger point gives the conditions for the initial filter rule matching; the server name description gives the AS address corresponding to the iFC data, and only one server name is described in one iFC data; the priority number description gives the S-CSCF The processing order of the iFC data, and the same priority cannot be assigned to more than one iFC data usage.

According to the 3GPP TS 29.288 standard, in addition to the registration and deregistration messages, the S-CSCF triggers the AS as follows: After receiving the SIP initial request message, the S-CSCF first sends the SIP request message to the higher priority iFCl data. The described service triggering conditions are matched. If the matching is successful, the S-CSCF sends the SIP request message to the service control point AS1 corresponding to the iFCl, and invokes the AS1. The S-CSCF receives the SIP request returned by the AS 1 After the message, the S-CSCF uses the SIP request message returned by the AS1 to match the service trigger condition described in the lower priority iFC2 data. If the match is successful, the S-CSCF sends the SIP request message returned by the AS1 to the iFC2. The corresponding AS2, call AS2; execute sequentially, until the iFC data processing condition that meets the service trigger condition is completed. That is, the triggering of the subsequent AS in the prior art depends on the SIP initial request message sent by the previously triggered AS. In this flow, if the intermediate AS fails to return a message or the returned message is not a SIP initial request message, the S-CSCF will not be able to continue to call the next AS.

If the user subscribes to the combined service provided by multiple ASs, the SUBSCRIBE message sent by the user is routed to the first AS through the S-CSCF. After receiving the SUBSCRIBE message sent to itself, the AS returns the 200 OK response message after completing the subscription process. If the service trigger mode of the existing S-CSCF is used, the next AS cannot be called according to the 200 OK message of the non-SIP initial request message.

That is, the prior art adopts the foregoing serial service triggering mode, after triggering an AS, based on the SIP initial request message returned by the AS, continues to trigger the next AS, and the previously triggered AS fails to return a message, or returns The message type is not the SIP initial request message. Then, the existing service trigger mode cannot trigger the next service control point, so that the service trigger cannot be guaranteed.

In addition, the current S-CSCF adopts the serial trigger mode, and the triggering of the subsequent AS needs to wait for the previous AS trigger to complete, and the triggering efficiency is low.

In addition, in the prior art, after triggering an AS, the S-CSCF needs to continue to trigger the subsequent AS according to the SIP initial request message sent back by the AS, but since the AS may change the SIP message, this may cause a service interaction problem, that is, Causes subsequent business to not work or work abnormally. For example, the original SIP message received by the S-CSCF contains the +g.PoC.talkburst flag in the Accept-Contact header field, and one of the user's iFC rules is triggered according to the flag to provide wireless push-to-talk (PoC, Push to talk). Over Cellular) Business of AS Data. However, according to the service priority, the S-CSCF may first process other iFCs. At this time, the S-CSCF first triggers to AS1, and the AS1 works in the Back to Back User Agent (B2BUA) mode for service processing and SIP messages. After the modification, the flag is lost, so that the S-CSCF can no longer be triggered by the aforementioned iFC to the subsequent AS providing the PoC service after receiving the message again. Summary of the invention

In view of this, the embodiment of the present invention provides a service triggering method to ensure the implementation of service triggering.

A service triggering method, including:

Monitoring business trigger events;

Determining a plurality of service control points that need to be triggered according to the service triggering event;

Trigger the multiple service control points.

The embodiment of the invention further provides a service triggering device to ensure the implementation of the service trigger. A service triggering device includes:

a monitoring unit, a service control point information providing unit, and a triggering unit, where

a monitoring unit, configured to monitor a service trigger event, and transmit the monitored service trigger event information to the service control point information providing unit;

a service control point information providing unit, configured to receive service trigger event information from the monitoring unit, determine that a plurality of service control points need to be triggered according to the service triggering event, and transmit the multiple service control point information to the triggering unit;

The triggering unit is configured to receive multiple service control point information from the service control point information providing unit, and trigger the multiple service control points.

The embodiment of the invention further provides a service triggering system to ensure the implementation of the service trigger. A service triggering system includes: a service triggering device and multiple service control points, where The service triggering device is configured to monitor a service triggering event, determine that a plurality of service control points need to be triggered according to the service triggering event, and trigger the multiple service control points.

The foregoing service triggering method, system, and service triggering apparatus provided by the embodiment of the present invention trigger multiple service control points based on the same service triggering event, without triggering a service control point, and then returning based on the service control point. The message triggers the next service control point, which can ensure the triggering of the subsequent service control point, and can improve the trigger processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

1 is a schematic structural diagram of a service triggering system in an embodiment of the present invention;

2 is a flowchart of triggering two service control points in parallel in Embodiment 1 of the present invention; FIG. 3 is a flowchart of triggering a service control point in parallel in the embodiment of the present invention; FIG. 4 is a serial trigger in Embodiment 3 of the present invention; Flowchart of two service control points; Fig. 5 is a flow chart of serially triggering two service control points in Embodiment 4 of the present invention. Mode for carrying out the invention

In order to make the objects, technical solutions and advantages of the embodiments of the present invention more clear, the following description will be further described in conjunction with the accompanying drawings.

The embodiment of the present invention first provides a service triggering method, where the method includes: monitoring a service triggering event; determining that a plurality of service control points need to be triggered according to the service triggering event; and triggering the multiple service control points.

That is, the key of the embodiment of the present invention is to trigger multiple service control points according to the same service triggering event. For example, the service triggering device receives the message A, triggers the AS1 according to the message A, returns the message B after the AS1 processing, and triggers according to the same service. The event invoking multiple service control points includes at least one of the following: triggering subsequent multiple service control points according to message A, or triggering subsequent multiple service control points according to message B. That is, the same service trigger event may be a service trigger device. The original service trigger event received may also be a service trigger event received during the service trigger processing, for example, message B returned by AS 1.

The service triggering event mentioned in the embodiment of the present invention may include: a received service trigger message, or a migration of a call state.

The embodiment of the present invention further provides a service triggering system, where the system includes: a service triggering device and multiple service control points, where

The service triggering device is configured to monitor a service triggering event, determine that a plurality of service control points need to be triggered according to the service triggering event, and trigger the multiple service control points.

The service trigger device, that is, the service trigger point, includes:

Referring to FIG. 1, FIG. 1 is a schematic structural diagram of a service triggering system in an embodiment of the present invention. The service triggering system may further include: a service trigger data storage unit, configured to store the service trigger data, and transmit the service trigger data to the service triggering device; the service triggering apparatus may further include: a service trigger data acquiring unit, configured to: Obtaining service trigger data, and transmitting the service trigger data information to the service control point information providing unit; the service control point information providing unit is further configured to receive the service trigger data information from the service trigger data acquiring unit, and trigger according to the service The service trigger data corresponding to the event determines that multiple service control points need to be triggered according to the service trigger event. The service trigger data storage unit may be a User Home Server (HSS) or the like. The service triggering device may be: an S-CSCF or a Service Broker. The service control point can be: SIP AS, OSA SCS or IM-SSF. The interface between the service triggering device and the service trigger data storage unit is represented by E1, and the service triggering device obtains user subscription data, that is, service subscription data, from the service trigger data storage unit through the E1 interface. The protocols used by the E1 interface may include: Diameter protocol, SIP protocol, Universal User Profile (GUP) protocol, HTTP protocol, Mobile Application Part (MAP) protocol, and the like. The interface between the service triggering device and the service control point is represented by E2, and the service triggering device triggers the service triggering event to the service control point through the E2 interface. After the service is triggered, the service control point and the service triggering device pass the E2 interface. Interactive communication messages. The protocol used by the E2 interface can be: SIP protocol.

In the embodiment of the present invention, the method of triggering multiple service control points may be:

Triggering multiple service control points in parallel according to the same service trigger event, that is, triggering multiple service control points at the same time; or

According to the same service trigger event, multiple service control points are triggered serially, that is, multiple service control points are triggered one by one.

The method for triggering multiple service control points in parallel based on the same service trigger event in the embodiment of the present invention is described in detail. The method may be: expanding the existing service trigger data description, and triggering data according to the service corresponding to the service trigger event. , determine that multiple business control points need to be triggered in parallel based on the business trigger event. The extended service trigger data description includes: setting the priority of the multiple service trigger data corresponding to the service trigger event to be the same, or configuring the address information of the multiple service control points in a service trigger data corresponding to the service trigger event . The service triggering device triggers multiple service control points in parallel according to the extended service trigger data.

Determining that the service trigger data pair needs to be triggered according to the service triggering event according to the information of the same priority configuration in the multiple service trigger data corresponding to the service triggering event. Multiple business control points, such as:

Set the priority of the service trigger data iFCl and iFC2 to be the same, then the iFCl description can be:

<SPT>

<Method>INVITE</Method>

</SPT>

</TriggerPoint>

</ApplicationServer>

</InitialFilterCriteria> The description of iFC2 can be:

<SPT>

<Method>INVITE</Method> </SPT>

</TriggerPoint>

</ApplicationServer>

</InitialFilterCriteria>

It can be seen from the descriptions of the above iFCl and iFC2 that the priority of both iFCl and iFC2 is 10, and both are triggered according to the SIP INVITE message. When the service triggering device detects a service triggering event, for example, receives a service triggering message SIP INVITE message, and determines that the message matches the service triggering conditions described in the iFCl and the iFC2, the triggering of the service triggering device in the embodiment of the present invention The unit triggers AS1 and AS2 in parallel, that is, based on the service triggering event, and simultaneously triggers to the service control point AS1 corresponding to iFCl and the service control point AS2 corresponding to iFC2.

The service triggering device may invoke multiple service control points corresponding to the multiple service trigger data in parallel according to the service trigger data corresponding to the same service triggering event. The service triggering device may be: The service triggers the data priority, sorts the service trigger data, and finds the multiple service trigger data with the same priority after traversing all the service trigger data. The service trigger device has the same priority according to the multiple service trigger data. And in parallel calling a plurality of service control points corresponding to the plurality of service trigger data respectively.

The following describes the above-mentioned method of calling multiple service control points in parallel after setting the priorities of iFCl and iFC2 to be the same in combination with specific embodiments.

Referring to FIG. 2, FIG. 2 is a flowchart of triggering two service control points in parallel in Embodiment 1 of the present invention. The service trigger data storage unit is an HSS, and the service triggering device is an S-CSCF. The service control point may be any one of the SIP AS, the OSA SCS, or the IM-SSF. In this embodiment, the two service control points are all SIP ASs, which are AS1 and AS2, respectively. The process includes the following steps:

Step 201: The S-CSCF obtains service trigger data iFC data from the HSS.

In this step, the iFC data can be obtained from the HSS through the Cx interface defined by the 3GPP. Step 202: The S-CSCF receives the INVITE message sent by the user A.

Step 203: The S-CSCF finds two iFCls and iFC2s with the same priority from the iFC data of the user A.

In this step, the description of iFCl is:

<SPT>

<Method>INVITE</Method>

</SPT>

</TriggerPoint>

</ApplicationServer>

</InitialFilterCriteria> Let i2002 be described as:

<SPT>

<Method>INVITE</Method>

</SPT>

</TriggerPoint>

</ApplicationServer>

</InitialFilterCriteria>

The S-CSCF determines that there is no other iFC data of the same priority, and then processes the above iFCl and iFC2. The service trigger conditions described in iFCl and iFC2 above are <Method>INVITE</Method>. If the SIP request method is INVITE, it can be determined that the received INVITE message matches the service trigger conditions in iFCl and iFC2. That is, there are multiple service trigger data with the same priority level corresponding to the same service trigger event. Therefore, the S-CSCF calls multiple service control points corresponding to the multiple service trigger data in parallel.

In step 204, the S-CSCF sends an INVITE message to AS1 corresponding to iFCl and AS2 corresponding to iFC2. The addresses of AS1 and AS2 are respectively the server name described in iFCl and iFC2. sip: AS l @homedomain.com ,, , "sip:AS2@homedomain.com". The process ends.

In this embodiment, although two service control points are triggered based on the same INVITE message, in actual applications, the service triggering conditions described in the foregoing iFCl and iFC2 may not be For example, the service triggering device matches the received service trigger message according to the description of the different header fields or message body content of the same INVITE message according to the two iFCs, for example, the service triggering condition described in iFCl is in the INVITE message. The content of the From header field, the service trigger condition described in iFC2 is the content of the To header field in the INVITE message. After the matching is successful, the service control points corresponding to the two iFCs are triggered.

So far, the description of Embodiment 1 of the present invention has ended.

According to the address configuration information of the multiple service control points in the service trigger data corresponding to the service triggering event, it is determined that multiple service control points corresponding to the service trigger data are triggered according to the service triggering event, for example:

If multiple AS address descriptions are configured in iFCl, the extended iFCl description can be as follows:

</TriggerPoint>

</ApplicationServer>

</InitialFilterCriteria>

In this embodiment, it can be seen from the description of iFCl that there are two service controls in the iFCl. Address description items of AS1 and AS2:

The service triggering device triggers, according to the description of the iFCl, a service triggering event that matches the service triggering condition description in the iFCl, the service triggering device triggers to the two service control points AS1 and AS2 corresponding to the iFCl based on the service triggering event.

In addition, a trigger sequence mode indication, that is, a SequenceMode indication, is added in the iFC data description, and the indication may indicate: triggering the service control point in parallel, or serially triggering the service control point. Set Sequence Mode to 0 to indicate that AS1 and AS2 are triggered in parallel; Sequence Mode takes a value of 1, indicating serial triggering of AS1 and AS2. It can be set that when there is no Sequence Mode indication in the iFC data and there are multiple AS address descriptions, the trigger sequence mode can take a default value. For example, the default value is 0, that is, the multiple ASs are triggered in parallel, that is, the service trigger data is only When parallel triggering or serial triggering is supported, it is not necessary to add an explicit "trigger sequence mode indication" in the service trigger data. When multiple service control points are described in the service trigger data, either the parallel trigger or the serial trigger. When AS1 and AS2 are triggered in parallel, the service trigger event can be triggered to AS1 and AS2 simultaneously; if serial triggering of AS1 and AS2 is required, then one of the service control points of AS1 and AS2 can be triggered based on the service trigger event. Trigger another service control point. Whether it is parallel triggering or serial triggering, it is based on the same business trigger event implementation. In this embodiment, the value of the Sequence Mode is 0.

The following describes a method for triggering multiple service control points in parallel after configuring multiple AS addresses in iFCl according to a specific embodiment.

Referring to FIG. 3, FIG. 3 is a flowchart of triggering two service control points in parallel in Embodiment 2 of the present invention. The service trigger data storage unit is an HSS, the service triggering device is an S-CSCF, and the two service control points are AS1 and AS2. The process includes the following steps: Step 301: The S-CSCF obtains service trigger data iFC data from the HSS.

Step 302: The S-CSCF receives the INVITE request message sent by the user A.

Step 303: The S-CSCF checks the iFC data of the user, and determines that the INVITE request message needs to be sent to the two ASs specified by the iFC data: AS1 and AS2.

In this step, set the iFC data as follows:

<SPT>

<Method>INVITE</Method>

</SPT>

</TriggerPoint>

</ApplicationServer>

</InitialFilterCriteria>

The S-CSCF determines, according to the iFC data, that the received INVITE message matches the trigger condition <Method>INVITE</Method> described in the iFC data, and the S-CSCF further determines that the SequenceMode value is 0 according to the iFC data description. There are multiple descriptions of ServerName, which determines that AS1 and AS2 described by ServerName need to be called in parallel. That is, the service trigger data of the address information of the multiple service control points corresponding to the same service triggering event is present, so the S-CSCF calls multiple service control points corresponding to the multiple service trigger data in parallel.

Step 304 and step 305, the S-CSCF sends the INVITE message to AS1 and AS2 at the same time. The addresses of AS1 and AS2 are the server name described in iFC: "sip: AS l @homedomain.com", "sip:AS2@homedomain.com ". The 3⁄4! Cheng Jie bundle.

So far, the description of Embodiment 2 of the present invention has been completed.

In a practical application, if a service triggering process, such as a third-party registration process, does not need to strictly invoke the service control point according to the priority of the existing iFC, the above-mentioned parallel triggering multiple service control points according to the embodiment of the present invention may be used. The practice of business triggering, by calling multiple service control points in one trigger, can effectively improve the efficiency of business triggering.

At this point, the description of the parallel trigger ends.

The following is a detailed description of the method for triggering multiple service control points in series based on the same service trigger event in the embodiment of the present invention. The method may be: triggering multiple service control points in series by using mutually independent trigger modes. The adopting mutually independent triggering manners means that multiple service control points are triggered based on the same service triggering event, instead of being triggered based on the returned message of the last service control point that is triggered, that is, the next service control point. The trigger does not depend on the return message of the previous service control point.

Further, in the practice of triggering multiple service control points by using mutually independent triggering modes, the service triggering data description may be extended to determine that multiple service control points need to be triggered serially according to the service triggering event. For example, the scalable service trigger data description, adding a "trigger condition mode indication,", the indication may indicate whether to use the return message of the previous service control point for subsequent triggering. When the indication value indicates that the previous service control point is not used When the message is returned for subsequent triggering, the service triggering device is triggered to trigger the previous service control. After the point, the return message of the service control point is not used, and the service trigger event is continued to trigger the next service control point.

Further, in the method of triggering multiple service control points by using the mutually independent triggering manners, the service triggering data may not be extended. When the service triggering event is a specific service triggering message, the service triggering device determines whether the message needs to be local. Ending to implement the serial triggering, if yes, the service triggering device determines that the plurality of service control points described in the plurality of service triggering data corresponding to the service triggering event are serially triggered according to the service triggering event, where the specific service triggering message includes at least the following One: SIP REGISTER registration message, SIP SUBSCRIBE subscription message, SIP PUBLISH release message, SIP NOTIFY notification message.

Certainly, the method of triggering multiple service control points in series may also be: determining, by using the foregoing method for describing multiple service control points in one service trigger data, that multiple service control points need to be triggered serially according to the service trigger event, The serial trigger may be indicated by the aforementioned "trigger sequence mode indication", or the multiple service control points may be triggered serially by default as long as a plurality of service control points are described in one service trigger data.

The following describes the practice of serially triggering multiple service control points according to the same service triggering event in combination with Embodiment 3 to Embodiment 4 of the present invention.

When the service triggering event is a specific service triggering message, according to the service triggering message, the local termination decision is required, and multiple service control points are triggered independently of each other, for example:

The user subscribes to the combined service provided by multiple ASs, and the subscription message sent by the user is routed to a service trigger device Service Broker, the Service Broker terminates the message locally, and the SUBSCRIBE message is serially triggered to provide multiple services of the combined service. AS. Referring to FIG. 4, FIG. 4 is a flowchart of triggering two service control points in Embodiment 3 of the present invention. The process includes the following steps:

Step 401: The Service Broker obtains service trigger data from the HSS.

In this step, the service trigger data can be described in the form of filtering rules (FC) data. The specific method for the Service Broker to obtain the service trigger data from the HSS may be obtained through the Sh interface defined by the 3GPP.

Step 402: The Service Broker receives the SUBSCRIBE message sent by the user. In this step, the Request-URI in the SUBSCRIBE message is Service Broker's own address sbl @home.net.

Step 403: The Service Broker determines that the SUBSCRIBE message needs to be terminated locally, and the Service Broker checks the FC data to determine how to send the SUBSCRIBE message to the service control point corresponding to the FC data.

In this step, the Service Broker determines that the SUBSCRIBE message needs to be terminated locally according to the Request-URI in the SUBSCRIBE message. In this step, there are two service trigger data matching the SUBSCRIBE message, namely, FC1 and FC2, where

Let FC1 be described as follows:

</SPT>

<Method>SUBSCRIBE</Method>

</SPT> Pp </catoSeve>Aliinrr>>

Gg <eautadvo</eautad>DflHnlinDflHnlin

p <SeveNae>s:S@oedoa.co</SeveNae>rrmiA2hmminmrrm pp <catoSeve>Aliinrr>>

Gg </eot>TYirpin

Yypp <CodtoeCN>0</CodtoeCN>niinTFniinTF

Gg <eot>Trirpin-

Yy <ot> 5</ot>Priri 1Priri**

</teCtea>Filrriri

Pp </catoSeve>Aliinrr>>

Gg <eautadvo</eautad>DflHnlinDflHnlin

p <SeveNae>s:S @oedoa.co</SeveNae>rrmiAlhmminmrrm pp <catoSeve>Aliinrr>> gg </eot>TYirpin </FilterCriteria>

That is, the service triggering event is a specific service triggering message, and the service triggering device Service Broker determines that the service triggering message SUBSCRIBE needs to be locally terminated, and determines that the plurality of service triggering data FC1 and FC2 corresponding to the service triggering event are serially triggered according to the service triggering event. Described multiple service control points AS1, AS2. Service Broker serially triggers AS 1 and AS2 according to the priority of the filtering rules.

Step 404: The Service Broker triggers the SUBSCRIBE message to the AS1 corresponding to the FCl.

Step 405: The Service Broker triggers the SUBSCRIBE message to the AS2 corresponding to the FC2.

Step 406: The AS1 returns a 200 OK response to the Service Broker, and the AS2 returns a 200 OK response to the Service Broker. In the above steps 404 to 407, the Service Broker determines the priority of the two FC data according to the foregoing. The FC1 with the priority of 10 is processed first, and the SUBSCRIBE message is matched with the trigger condition of the FC1: <Method>SUBSCRIBE</Method>. After the matching is successful, the SUBSCRIBE message is sent according to the AS1 address item described in FC1. AS1. After AS1 is successfully invoked, it returns a 200 OK response message to Service Broker. However, Service Broker does not wait for AS 1 to return the 200 OK response message, but continues to process FC2 with priority 15 and the SUBSCRIBE message with the FC2. Trigger condition: <Method>SUBSCRIBE</Method> performs matching. After the matching is successful, the SUBSCRIBE message is sent to AS2 according to the AS2 address item described in FC2.

Step 408: After receiving the 200 OK response message returned by AS1 and AS2, the Service Broker returns a 200 OK response message to User A, and the process ends. So far, the description of the third embodiment of the present invention has been completed.

According to the "trigger condition mode indication", a plurality of service control points are triggered serially independently of each other. Referring to FIG. 5, FIG. 5 is a flowchart of serially triggering two service control points in Embodiment 4 of the present invention. The service triggering device is Service Broker, the service trigger data storage unit is HSS, and the two service control points are AS1 and AS2. The process includes the following steps:

Step 501: The Service Broker obtains service trigger data from the HSS, for example, the FC data described in the form of an XML-based filtering rule.

Step 502: The Service Broker receives an INVITE request message sent by User A to User B.

Step 503: After processing, the INVITE message is forwarded to user B.

Step 504: User B sends a 180 Ringing message to prompt the called party to ring.

In this step, the Service Broker start timer monitors whether the called user B answers. Step 505: After the timer expires, the Service Broker checks the FC data of the user A. In this step, User B fails to send a 200 OK response message before the timer started by Service Broker expires. Therefore, after the timer expires, Service Broker detects a service trigger event, and the call state transition processed by Service Broker is processed. To the origin _ no answer. User A's FC data has the following descriptions:

FC1 is described as follows:

<SessionState>0 NoAnswer</SessionState> t

</teCtea>Filrriri

Pp </catoSeve>Aliinrr>>

Gg <eautadvo</eautad>DflHnlinDflHnlin

Gggg <eCoddoode> </eCodtoode>TrirninMTrirniinM p <SeveNae>s:S@oedoa.co</SeveNae>rrmiA2hmminmrrm pp <catoSeve>Aliinrr>>

Gg </eot>TYirpin _ <sessostate>〇in ypyp <CodtoeCN>0</CodtoeCN>niinTFniinTF

Gg <eot>Trirpin- yy <ot></ot>Priri 2Priri**

</teCtea>Filrriri

Pp </catoSeve>Aliinrr>>

Gg <eautadvo</eautad>DflHnlinDflHnlin

Gggg <ecoddoodevo</ecodtoode>TrirninMTrirniinM p 5 <SeveNae>s:S @oedoa.co</SeveNae>rrmiAlhmminmrrm pp <catoSeve>Aliinrr>>

Gg </eot>TYirpin

</S>PT The service triggering conditions of FC1 and FC2 are both <SessionState>0_NoAnswer</SessionState>, that is, the call state is migrated to the originating_non-answering state. In this embodiment, a trigger condition mode indication (TriggerConditionMode) is added to both FC1 and FC2, and the TriggerConditionMode is used to indicate whether the service triggering device uses the return message of the previous service control point, and then continues to call. A business control point. Let TriggerConditionMode be 0 means not used; TriggerConditionMode is 1 means it needs to be used. In this embodiment, according to the description of FC1 <TriggerConditionMode>0</TriggerConditionMode>, after the Service Broker triggers the INVITE message to AS1, the message returned by AS1 is not used, and the INVITE message can be used to continue processing FC2; according to FC2 The description <TriggerConditionMode> 1 </TriggerConditionMode> , after the Service Broker triggers the INVITE message to AS2, it needs to wait for the AS2 to return a message to perform subsequent trigger processing according to the return message.

Step 506: The Service Broker sends an INVITE message to the AS1 according to the FC1. After this step is processed, because TriggerConditionMode in FC1 is 0, Service Broker can continue to process the next low-priority FC2 without waiting for AS 1 to return a message, so Service Broker continues to process FC2.

Step 507: The Service Broker sends an INVITE message to the AS2 according to the FC2. In this step, Service Broker according to the description of FC2, because TriggerConditionMode in FC2 is 1, Service Broker needs to wait for the return message of AS2 for subsequent trigger processing.

Step 508: AS1 returns a 200 OK message.

Step 509: The AS2 returns an INVITE message.

So far, the description of Embodiment 4 of the present invention has been completed.

At this point, the description of the serial trigger ends. Next, the service triggering apparatus in the present invention processes a response of a plurality of service control points triggered by a service triggering event, and the manner of processing the response includes at least one of the following: separately processing responses of each service control point, including each The response message and the unresponsive condition; or, the service triggering device only processes the first one of the multiple service control points; or, the service triggering device only processes the response of the specified service control point; or, as long as the multiple If one of the service control points does not return a response, the service triggering device only processes the unresponsive condition; or, as long as the service triggering device receives a specific response returned by any of the service control points, only the specific response is processed; or The service triggering device processes the response when the responses of the multiple service control points are consistent, and the consistent situation may include: all of the successful responses, or all of the failed responses, or none of the responses.

The processing of the service triggering device includes at least one of: sending a response message for a service trigger message, failing processing, performing a subsequent service trigger, and SIP dialog processing.

The sending a response message for the service trigger message, for example, the service trigger message is a user registration message, and the message may trigger a third party registration to be initiated for more than one AS. Correspondingly, the response message for the service trigger message refers to the response message of the registration message, such as a 200 OK message.

The failure processing refers to processing after the service triggering device fails to invoke the service control point, and the failure includes at least one of the following: the service control point is not responding, and the service control point returning message indicates that the call fails. For example, when the service triggering device triggers multiple service control points in parallel, when multiple service control points are not responding, the service triggering device performs failure processing, such as termination of the session or continued triggering according to DefaultHandling in the iFC data.

The subsequent service triggering refers to the service triggering device continuing the subsequent service triggering process after processing the response of the service control point. For example, when the service triggering device triggers multiple service control points in parallel, when receiving the first one of the multiple service control points, the service triggering device performs subsequent service trigger processing based on the message, for example, according to the return The reply message checks the subsequent iFC to trigger the subsequent service control point.

The SIP session processing means that the service triggering device processes the SIP session after receiving the response returned by the service control point, for example, migrating the conversation state. For example, the service triggering device serially sends the SUBSCRIBE message to the multiple service control points, when each service control point returns. After the 200 OK message, the service triggering device sets the corresponding multiple SIP dialogs to the established state.

In the manner of processing the response, when the service triggering device processes only one specific response, it indicates that the specific response is the response of all the service control points, for example, the service triggering device only receives one of the service control points returned by the service triggering device. When the response code is invalid, that is, the response code is processed as a response of all service control points, such as performing the above-described failure processing.

In the manner of processing the response, when the service triggering device only processes the response of the specified service control point, the specified manner may be: adding a description item of the specified processing to the service trigger data. For example, if the service triggering device needs to send a response message for the service trigger message, the description of the iFC may be:

<Method>SUBSCRIBE</Method>

</SPT>

</TriggerPoint>

<ApplicationServer> <ServerName>sip:AS2@homedomain.com</ServerName>

<NeedResponse>0</ NeedResponso

</ApplicationServer>

</InitialFilterCriteria>

In the iFC description, the NeedResponse item is used to indicate that the response message needs to be sent to the originating end of the service trigger message (ie, the SUBSCRIBE message), or does not need to be sent to the originating end of the service trigger message. A default value can be provided when the attribute item does not exist in the iFC data. For example, the response message does not need to be sent by default. When the service triggering device receives the response of the service control point described by the iFC, for example, if the service control point indicates that the call is successful, or the message indicating that the call fails, or the service control point does not respond, according to NeedResponse, it is determined whether the above need to be sent. In response to the message, setting the value of NeedResponse to 0 indicates that the above response message needs to be sent.

Specifically, the response message sent by the service triggering device to the originating end of the service triggering event may be:

When the service triggering device receives the SIP response code (response code) message returned by the service control point, the service triggering device forwards the SIP response message to the initiator of the service triggering event; when the service triggering device receives the SIP initial request message returned by the service control point Sending a 200 OK response message to the originating end of the service triggering event;

When the service control point is unresponsive, the service triggering device sends a response message to the originating end of the service triggering event, and the response message may be: 480 Temporarily unavailable, 408 Request Timeout or SIP 5XX series response message.

The processing of the response of the service triggering device to the plurality of service control points is applicable to the manner of triggering in parallel or serially triggering multiple service control points.

In summary, the foregoing service triggering method, system, and service provided by the embodiments of the present invention are provided. The triggering device, based on the same service triggering event, invokes multiple service control points without calling a service control point, and then calling the next service control point based on the message returned by the service control point, thereby ensuring Trigger of subsequent business control points. Moreover, in the embodiment of the present invention, the efficiency of the service triggering can be effectively improved by calling multiple service control points at a time.

Claims

Claim

A service triggering method, comprising:

Monitoring business trigger events;

Triggering the plurality of service control points.

The method according to claim 1, wherein the step of triggering the plurality of service control points comprises: parallel triggering, or serial triggering.

The method according to claim 1, wherein the determining the plurality of service control points that need to be triggered according to the service triggering event comprises:

Determining, according to the service trigger data corresponding to the service trigger event, multiple service control points that need to be triggered according to the service trigger event.

The method according to claim 3, wherein the determining the plurality of service control points that need to be triggered according to the service triggering event comprises:

And determining, according to the service triggering event, a plurality of service control points corresponding to the service triggering data, according to the multiple service control points described in a service triggering data corresponding to the service triggering event.

The method according to claim 4, wherein the step of triggering the plurality of service control points comprises: according to a trigger sequence mode indication configured in the service trigger data or a default trigger sequence mode indication, in parallel Or triggering the plurality of service control points in series.

Determining, according to the service control point that is respectively described in the multiple service trigger data corresponding to the service triggering event, that multiple service control points corresponding to the service trigger data are triggered according to the service triggering event.

The method according to claim 6, wherein the step of triggering the plurality of service control points comprises:

The service trigger data has the same priority configuration, and the multiple service control points are triggered in parallel;

Or triggering, by the trigger condition mode indication configured in the service trigger data, the plurality of service control points;

Or determining that the service triggering event is a specific service trigger message that needs to be locally terminated, and triggering the multiple service control points in series.

The method according to claim 1, wherein after the triggering the multiple service control points, the method further comprises: processing a response of the multiple service control points, where the processing of the multiple service control points The steps to respond include:

Handling the response of each service control point separately;

Or, processing only the response returned by the first one of the plurality of service control points;

Or, only handle the response of the specified service control point;

Or, as long as one of the plurality of service control points does not return a response, only the unresponsive condition is processed;

Or, only one specific response returned by any of the service control points is processed;

Or, when the responses of the multiple service control points are consistent, the response is processed.

The method according to claim 8, wherein the step of processing the response of the plurality of service control points further comprises:

Send a response message for a service trigger message, perform a failure process, perform a subsequent service trigger, or perform a SIP dialog process.

10. The method according to claim 8, wherein the step of processing the response of the specified service control point further comprises:

Determining whether a message needs to be triggered to the service according to the configuration in the service trigger data The originator sends a response message.

11. A service triggering device, comprising:

a monitoring unit, a service control point information providing unit, and a triggering unit, wherein the monitoring unit is configured to monitor a service triggering event, and transmit the monitored service triggering event information to the service control point information providing unit;

12. Apparatus according to claim 11 wherein said apparatus further comprises:

a service trigger data obtaining unit, configured to obtain service trigger data, and transmit the service trigger data information to the service control point information providing unit;

The service control point information providing unit is further configured to receive the service trigger data information from the service trigger data acquiring unit, and determine, according to the service trigger data corresponding to the service trigger event, that multiple service control points need to be triggered according to the service trigger event. .

The device according to claim 12, wherein the service control point information providing unit is further configured to: according to multiple service control points described in a service trigger data corresponding to the service trigger event, or And determining the multiple service control points according to the service control points respectively described in the multiple service trigger data corresponding to the service trigger event.

The device according to claim 11, wherein the triggering unit is further configured to receive a plurality of service control point information from the service control point information providing unit, and trigger the multiple service control points in parallel or serially. .