WO2008083595A1

WO2008083595A1 - A method and a call controller for triggering the user service under the controlling of the application server

Info

Publication number: WO2008083595A1
Application number: PCT/CN2007/071361
Authority: WO
Inventors: Weiqiang Zhou
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-12-31
Filing date: 2007-12-28
Publication date: 2008-07-17
Also published as: CN101001250B; CN101001250A

Abstract

A method and a call controller for triggering the user service under the controlling of the application server are provided. The method includes the following steps: the trigger conditions are divided to several trigger groups; after the call arrives the call controller, in the call, the call controller matches each condition of each trigger group according to the call information, after this group of conditions all have been matched, the next trigger group will be matched.

Description

Method for triggering user service under control of service server and call controller This application claims to be submitted to China Patent Office on December 31, 2006, application number is 200610063769.3, and the invention name is "method of triggering users under the control of business server" Priority of the patent application, the entire contents of which is incorporated herein by reference.

Technical field

The present invention relates to the field of communications, and in particular, to a method for triggering user services under the control of a service server and a call controller.

Background technique

A method of service implementation is defined in the IP Multimedia Subsystem (IMS). The various messages of the SIP (Session Initiation Protocol) user are transmitted to the S-CSCF (Service-Call Session Control Function), and the S-CSCF triggers according to the session initialization protocol message itself. The condition is matched. If the match is successful, a call is initiated to the service server (AS), and the AS completes the service control of the user according to the triggered call. The above process is repeated multiple times until all the rules match.

Please refer to Figure 1. In the IMS system, certain rules are defined for SIP users.

The session control for the calling SIP user mainly includes the following steps:

a) according to the content of the SIP session message from the IMS calling user, the IMS multiple AS trigger conditions (ie, the conditions triggered to the AS) signed by the calling SIP user are matched in the order of priority, if the matching is successful, The SIP session is routed to the AS service platform specified by the matching trigger condition to trigger the execution of the IMS user-related value-added service logic, and jumps to step b); if the match is unsuccessful or the remaining trigger condition is empty, then jump to step c ) ;

b) Waiting for the SIP^ tongue returned from the AS service platform, according to the content of the SIP session message (possibly modified), the other AS signing trigger conditions remaining for the calling SIP user are not matched, and the matching is continued in the order of priority. If the match is successful, the SIP session is routed to the AS service platform specified by the matching trigger condition, and jumps to step b); if the match is unsuccessful or the remaining trigger condition is empty, then jump to c);

c) The tongue is routed to the called side, and the called SIP user side is processed. The control of the called SIP user mainly includes the following steps:

a) Determine whether the called user is registered. If not registered, download the relevant IMS basic subscription data directly from the HSS (Home Subsciber Server, Home User Server) through the Diameter protocol (upgraded version of the RADIUS protocol);

b) According to the content of the SIP session message from the destination network, the IMS multiple AS trigger conditions signed by the called SIP user are matched in the order of priority, and if the matching is successful, the SIP session is routed to the matching successful contracting rule. The specified AS service platform address or BGCF (Breakout Gateway Control Function) address to trigger the execution of the IMS user-related value-added service logic, and jump to step c); if the match is unsuccessful or the remaining trigger condition is empty In case, then jump to step d);

c) Waiting for the SIP session returned from the AS service platform, determining whether the Request URL address of the SIP message content has been modified, and if not modified, the other unmatched AS subscription trigger conditions remaining for the called SIP user continue to be prioritized. The order of the levels is matched. If the matching is successful, the SIP session is routed to the AS service platform address or BGCF address specified by the contracting rule, and jumps to step c); if the matching is unsuccessful or the remaining trigger condition is empty , then go to step d). If it is modified, it jumps to step c) of the calling SIP user session control flow, and proceeds to the called network I-CSCF (Interrogating-CSCF according to the new called URL (Uniform Resource Location) address. Query the addressing of CSCF, referred to as "I-CSCF" for short;

d) According to the P-CSCF (Proxy-CSCF, Proxy CSCF) address recorded in the S-CSCF during the registration process of the called IMS user, the session route to the P-CSCF where the called user roams is performed.

In the process of implementing the present invention, the inventor has found that the implementation method of the above existing trigger service is too simple to meet the increasingly diverse business requirements.

Summary of the invention

The embodiment of the present invention provides a method for triggering user service under the control of a service server and a call controller, which can provide a more flexible service trigger mode for the user.

An embodiment of the present invention provides a method for triggering user service under the control of a service server, and the trigger condition is divided into a plurality of trigger groups in advance, and the method includes: after the call arrives at the call controller, in the call, the call controller is configured according to the call controller The information of the call triggers conditions for each of the trigger groups Matching is performed until the triggering conditions of the trigger group are all matched, and the matching of the next trigger group is performed.

The embodiment of the present invention further provides a method for triggering user service under the control of a service server, and pre-associating an AS trigger condition into a plurality of trigger groups, the method comprising: the call controller is configured to each of the ASs according to the received call information. Each trigger condition of the triggering group is matched. After all the triggering conditions of the current triggering group are all matched, the matching result of the current triggering group is used to determine whether to trigger the call to the service server AS, and the next triggering group is performed. Match.

An embodiment of the present invention further provides a call controller, including: a unit for dividing a service server AS trigger condition into a plurality of trigger groups; and triggering each trigger of each of the AS trigger groups according to the received call information The unit that matches the condition; after all the trigger conditions of the current trigger group are all matched, the unit determines whether to trigger the call according to the matching result of the current trigger group.

AS, and the matching of the next trigger group.

Compared with the prior art, the technical solution provided by the embodiment of the present invention solves the problem of triggering by group, and triggers only when a set of trigger conditions are matched. The introduction of this mechanism makes the business processing mechanism of the entire network more flexible and can meet increasingly diverse business needs.

DRAWINGS

1 is a flow chart of a prior art SIP^ tongue process;

2 is a flowchart of a method for triggering a user service under a service server according to an embodiment of the present invention.

detailed description

The implementation process of the present invention will be described below in conjunction with specific embodiments.

In one embodiment of the invention, the trigger condition is divided into a number of trigger groups, assuming that the trigger group 1, group 2, group 3, up to group n. The grouping rules can be freely set, such as dividing the triggering conditions into a number of triggering groups according to the attributes of the triggering conditions.

The content of the trigger condition is not limited to the SIP message itself, and may be any information in the call process, for example, at least one of call attribute including caller attribute, called attribute, relay attribute, inbound and outbound IP route attribute, and number analysis result. . This determines that the trigger condition is not limited to SIP users and relays. It can also be applied to other users and relays, such as ordinary POTS ( PLAIN OLD TELEPHONE SERVICE) users (including H248, MGCP (Media). Gateway Control Protocol, User, etc.), H323 User, H323 Relay, ISUP (ISDN User Part) Relay, TUP (Telephone User Part) Relay, PRA (Packet Routing address, routing address, etc. relay.

Referring to FIG. 2, after the call arrives at the call controller, within the call, the call controller performs the following processing on each trigger group according to the information of the call: matching and recording each trigger condition in the trigger group Matching result, after all the triggering conditions of the group are matched, if only one or more triggering conditions are successfully matched in the matching result record, the call controller routes the call to the AS, and carries the indication that the triggering conditions match successfully. AS; If the trigger conditions of this group do not match at all, the matching of the following trigger group is performed, that is, the matching of the trigger group 2 is performed.

After the call is triggered to be routed to the AS, the AS performs subsequent processing according to the satisfied trigger condition. After the processing ends, the call is routed back to the call controller, and the call controller performs matching processing on the next trigger group.

The above process for each trigger group starts from the first trigger condition and continues until the trigger conditions of all trigger groups are matched.

Suppose there are three trigger groups, group 1 contains trigger condition 1, trigger condition 2, trigger condition 3, trigger condition 4, referred to as FC1, FC2, FC3, FC4; group 2 contains trigger condition 5, referred to as FC5; group 3 Contains trigger condition 6, trigger condition 7, referred to as FC6, FC7; then the triggering of the calling user or relay side is as follows:

1) The call controller first matches all trigger conditions in trigger group 1, for FC1, FC2, FC3,

FC4 matches one by one, and whether it is successful or not, all matching is required;

If no trigger condition matches successfully, it will not trigger and jump directly to step 3);

If at least one trigger condition is successfully matched, ϋ殳FC2, and FC3 match successfully, the call controller triggers the call to the AS, and needs to indicate that FC2, FC3 is matched in the interface triggered to the AS, and continues to step 2);

2) The AS accepts the trigger and completes the relevant processing, routes the call back to the call controller, continues the matching of the trigger group 2, and continues to perform step 3);

3) The call controller matches the trigger condition of the trigger group 2, and the matching process is similar to the step 1). If the I setting does not match successfully, the jump jumps directly to 4); 4) Match the trigger conditions of trigger group 3, the process is similar to step 1). Assume that there is no matching success, then directly follow the process, that is, jump directly to step 5); if the FC6 match is successful, the call is routed to the AS, and the interface indicates that the FC6 is matched;

5) Match all the trigger conditions as described above; until the match is over, then the called route can be made.

The process of the called user or the relay side is the same as above.

The method for controlling user service under the trigger service server of the present invention implements group triggering, and triggers only when a set of trigger conditions are matched, and then one or more trigger conditions in a trigger group match. In the case of success, only one trigger can be performed. In addition, all conditions of a successful match in a trigger group can be simultaneously notified to the AS in the trigger interface. The introduction of this mechanism makes the business processing mechanism of the entire network more flexible; the content and scope of the matching conditions are independent of the specific user types.

A person skilled in the art may understand that all or part of the steps in implementing the above method embodiments may be completed by a program instructing related hardware, and the program may be stored in a computer readable storage medium, the storage medium Such as: ROM / RAM, disk, CD, etc.

The invention also discloses an embodiment of a call controller, the call controller comprising: a unit for dividing an AS trigger condition into a plurality of trigger groups; and a triggering group for each of the ASs according to the received call information The unit that matches each trigger condition. The unit for matching each trigger condition of each AS trigger group, after all the trigger conditions of the current trigger group are all matched, determining whether to trigger the call according to the matching result of the current trigger group. AS, and the matching of the next trigger group.

The above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any technical person skilled in the art can disclose the technical scope of the present invention and the technical idea of the present invention. Variations or substitutions that are conceivable within the scope of the invention are intended to be included within the scope of the invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

Rights request

A method for triggering a user service under the control of a service server, and the triggering condition is divided into a plurality of trigger groups in advance, wherein the method includes:

After the call arrives at the call controller, within the call, the call controller matches each trigger condition in each trigger group according to the information of the call, until the trigger conditions of the trigger group are all matched, and the next trigger group is performed. Match.

The method according to claim 1, wherein the call controller records the matching result information together when matching each trigger condition in each trigger group according to the call information.

The method according to claim 2, wherein, after all the triggering conditions of the triggering group are matched, if the one or more conditions in the matching result record are successfully matched, the call controller routes the call to The service server AS carries the indication that the trigger condition matches successfully to the AS; after the AS completes the trigger processing, the call is routed back to the call controller, and the call controller performs the matching of the next trigger group; if the trigger condition of the trigger group If all do not match, the next trigger group is matched.

A method for triggering a user service under the control of a service server, which is characterized in that the service server AS triggering condition is divided into a plurality of trigger groups in advance, and the method includes:

The call controller matches each trigger condition of each of the AS trigger groups according to the received call information. After all the trigger conditions of the current trigger group are all matched, the call controller determines whether the current trigger group matches the result of the current trigger group. The call is triggered to the service server AS and the next trigger group is matched.

5. The method according to claim 4, wherein the content of the trigger condition comprises a SIP message and information during a call.

The method according to claim 5, wherein the information in the calling process comprises at least one of a calling attribute, a called attribute, a relay attribute, an inbound and outbound IP routing attribute, and a call identity attribute.

The method according to claim 4, wherein the pre-setting the trigger condition into the plurality of trigger groups comprises: dividing the trigger condition into a plurality of trigger groups according to the attribute in advance.

The method according to any one of claims 4 to 7, wherein the according to the current The matching result of the trigger group determines whether the call is triggered to the AS and the matching of the next trigger group includes:

If the matching result of the current trigger group is that at least one of all trigger conditions of the trigger group is successfully matched, the call controller routes the call to the AS; and when the call is processed by the AS, it is routed back to the call controller. The call controller performs matching of the next trigger group;

If the matching result of the current trigger group is that all the trigger conditions of the trigger group do not match, the matching of the next trigger group is performed.

The method according to claim 8, wherein when the call controller routes the call to the AS, it also indicates to the AS the trigger condition that the matching is successful in the current trigger group.

10. A call controller, comprising:

A unit for dividing a service server AS trigger condition into a plurality of trigger groups;

a unit for matching each trigger condition of each AS trigger group according to the received call information; after all the trigger conditions of the current trigger group are all matched, the unit determines whether the current trigger group matches the result according to the matching result of the current trigger group. The call is triggered to the AS and the next trigger group is matched.

11. The call controller according to claim 10, wherein the content of the AS trigger condition comprises a SIP message and information during a call.

The call controller according to claim 11, wherein the information in the calling process includes at least one of a calling attribute, a called attribute, a relay attribute, an inbound and outbound IP routing attribute, and a call itself attribute. .

The call controller according to claim 10, wherein the unit determines whether to trigger the call to the AS according to the matching result of the current trigger group after all the triggering conditions of the current trigger group are all matched. And the matching of the next trigger group specifically includes:

After the matching condition of the current triggering group is all matched, if the matching result of the current triggering group is that at least one of all the triggering conditions of the triggering group is successfully matched, the call is routed to the AS; When the AS is processed and returned to the call controller, the matching of the next trigger group is performed; if the matching result of the current trigger group is that all the trigger conditions of the trigger group do not match, the matching of the next trigger group is performed. .

The call controller according to any one of claims 10 to 13, characterized by, further comprising: indicating to the AS, a unit that triggers a successful trigger condition in the current trigger group.