WO2008034358A1 - A handling method, device and system for service control unit - Google Patents

Abstract

A handling method includes firstly excuting service filter criteria, determining the invoked service control unit and corresponding subsequent filter criteria, and then handling the proceeding communication according to the determined subsequent filter criteria in the service excuting process. A handling device and system for service control unit are also disclosed. By using the present invention, the signal path can be adjusted in the subsequent communication process, so as to resolve the problem of service interaction and conflict, improve the call setup efficiency and shorten the call connection time.

Description

 Service control unit processing method, device and system

 The present invention relates to a service invocation technology of an Internet multimedia subsystem, and in particular, to a method, apparatus and system for processing a service control unit. Background of the invention

 The Internet Protocol Multimedia Subsystem (IMS) is an IP Multimedia Subsystem defined by the 3rd Generation Partnership Project (3GPP). The IMS network uses the Session Initiation Protocol (SIP) as the call control signaling, which is the target network for the 3G mobile communication network to provide unified multimedia services and applications.

 In the IMS network, the session layer is separated from the service layer, and IMS provides the necessary method for the call of the service. The host execution environment for various services is called the Service Control Unit and provides a variety of business logic control functions. The service control unit includes an IMS application server, a traditional intelligent network service control function entity (SCF, Service Control Function), and the like. Taking the IMS application server as an example, the process of providing services in an IMS network includes the following three basic steps:

 Step 1: Define a possible business or business collection;

 Step 2: When the user orders/modifies the service subscription relationship, the user-specific service data is created in the form of an initial filter rule (iFC, Initial Filter Criteria);

Specifically, the iFC includes a service call condition and its corresponding application server (AS, Application Server), and the service call condition is described by a service point trigger (SPT, Service Point Trigger), and the content of the SPT includes: a request-uniform resource identifier (Request-URI), identifying the resource pointed to by the SIP initial request; a SIP method (Method) indicating the type of the SIP initial request; a SIP header field (Header) containing information related to the SIP initial request, Can be any SIP header field and its header field content; Session Case, there are three possible values, ie start, terminate or terminate unregistered; Session Description, any session description within the SIP method SDP (Session Description Protocol) field content.

 Step 3: When the service-call session control function (S-CSCF) receives the SIP initial request, according to the current session situation and the received SIP initial request message, the iFC is executed to determine the current session situation and the SIP initial request. Corresponding application server, and the received SIP initial request is delivered to the determined application server.

 In general, different services may be provided by different application servers. However, the inventors of the present application found in the process of implementing the present invention that different services may have mutual influence and conflict in the application process.

 For example, the S-CSCF receives a SIP Invite message (INVITE), and according to the execution of the iFC, sequentially calls the three application servers AS1, AS2, and AS3, and sends the INVITE message to the called user; Bell, suppose the called user has opened the no-answer forwarding voice mailbox service. After the ringing timeout, the call is forwarded to the voice mailbox; the voice mailbox answers, and the S-CSCF receives the response message from the voice mailbox (200 OK) . According to the prior art, the 200 OK message will be sent to AS3, AS2 and AS1 according to the established signaling path. When AS2 receives the 200 OK message, it considers that this is the 200 OK message returned by the user, and the voice message will be played to it. The 200 OK message in this example is actually returned by the voice mailbox. Obviously, AS2 cannot receive the 200 OK message.

Moreover, according to the IMS standard, the application server can only be triggered by the SIP initial request message, such as: can only be triggered by INVITE message, instant message (MESSAGE), subscription message (SUBSCRIBE) and reference message (REFER), ie iFC Only SIP initial request messages are processed; however, some application servers actually need to be triggered only in certain scenarios during communication. For example, handle busy call forwarding (CFB, Call Forwarding) The application server CFB AS of Busy needs to be triggered only when the called user is busy. However, since the prior art needs to establish a signaling path in the initial SIP request, the CFB AS must be Triggered, and if the called user is currently idle, the CFB AS will be useless in the signaling path. Obviously, this reduces the efficiency of call setup and prolongs the call connection time.

 In addition, according to the IMS standard, a complete, normal call setup procedure will pass through the INVITE message, the 183 response code message, the temporary acknowledgement message (PRACK), the 200 response code message, the update message (UPDATE), the 200 response code message, and the 180-vibration. The bell response message, the PRACK message, the 200 response code message, the 200 response response code message, and the acknowledgement message (ACK) have a total of 11 messages. When the S-CSCF receives the INVITE message, according to the execution of the iFC, after calling the AS 1 and sending the INVITE message thereto, the 10 subsequent call setup messages received by the S-CSCF will be sent according to the established signaling path. To AS1; but in fact, AS1 only needs to receive 4 messages of INVITE message, 180 ringing response message, 200 response response message, and ACK message to implement business logic control, and S-CSCF sends all messages to AS1. Reduce the efficiency of call setup and extend the call duration.

 It can be seen from the above analysis by the inventor of the present application that since the signaling path of the application server in the prior art is fixed at the initial SIP request, it cannot be adjusted in the subsequent process of the communication, and the SIP initial request message cannot be used according to the service filtering rule. Subsequent messages are processed. Therefore, the service interaction and conflict problems after the service control unit is invoked cannot be solved, and the message cannot be sent to the service control unit as needed, and the call setup efficiency is low and the call connection time is long. Summary of the invention

In view of this, the embodiment of the present invention provides a service control unit processing method, so that the signaling path of the service control unit can be adjusted in the subsequent process of communication, thereby solving the service. Interaction and conflict issues.

 The embodiment of the invention further provides a service control unit processing device, so that the signaling path of the service control unit can be adjusted in the subsequent process of communication, thereby solving the business interaction and conflict problem.

 The embodiment of the present invention further provides a service control unit processing system, so that the signaling path of the service control unit can be adjusted in the subsequent process of communication, thereby solving the business interaction and conflict problem.

 To achieve the above objective, the technical solution of the embodiment of the present invention is specifically implemented as follows: A service control unit processing method, where the method includes the following steps: executing a service filtering rule, determining a called service control unit and a phase thereof Corresponding subsequent filtering rules;

 During the execution of the service, the current communication is processed according to the determined subsequent filtering rules.

 A service control unit processing device, comprising: a subsequent filtering rule obtaining module, configured to execute a service filtering rule, and determine a called service control unit and a corresponding subsequent filtering rule;

 The subsequent processing mode execution module is configured to process the current communication according to the subsequent filtering rule during the execution of the service.

 A service control unit processing system, the system comprising: a service control unit processing device, configured to execute a service filtering rule, determine a subsequent filtering rule corresponding to the service control unit, and perform current according to the subsequent filtering rule Communication processing;

 The service control unit is configured to provide various service logic control functions according to the processing of the service control unit processing device.

It can be seen from the above technical solution that the embodiment of the present invention firstly is based on the called service control unit. The processing conditions that may occur during the execution of the service, setting a subsequent filtering rule corresponding to the called service control unit in the service filtering rule; then executing the service filtering rule to determine the service control unit and its corresponding subsequent filtering rule; After the service execution process, the current communication is processed according to the determined subsequent filtering rule, so that the signaling path of the service control unit can be adjusted in the subsequent process of the communication, and the service interaction and conflict problem after the service control unit is invoked are solved. And improve call setup efficiency and shorten call connection time. BRIEF DESCRIPTION OF THE DRAWINGS

 FIG. 1 is a schematic flowchart diagram of a method for processing a service control unit according to a preferred embodiment of the present invention. The flowchart of the service control unit processing method in the specific embodiments 1 to 3 of the present invention is shown.

 FIG. 3 is a schematic structural diagram of a service control unit processing apparatus according to an embodiment of the present invention. FIG. 4 is a schematic structural diagram of a service control unit processing system according to an embodiment of the present invention. Mode for carrying out the invention

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

 FIG. 1 is a schematic flowchart diagram of a method for processing a service control unit according to a preferred embodiment of the present invention. Referring to Figure 1, the method includes the following steps:

 Step 101: Perform a service filtering rule to determine the called service control unit and its corresponding subsequent filtering rules.

 Step 102: During the service execution process, the current communication is processed according to the determined subsequent filtering rule.

In this step, when the subsequent triggering conditions in the subsequent filtering rules are met, the corresponding processing is performed according to the subsequent processing manner in the subsequent filtering rules. So far, the service control unit processing method in the preferred embodiment of the present invention has been completed.

 In the above step 101, the service filtering rule is executed based on the service triggering message. Here, the service trigger message may be a SIP initial request message or the like. Typically, the service trigger message will be sent to the called service control unit to enable the call to the service control unit.

 In this embodiment, a subsequent filtering rule corresponding to the called service control unit is set in the service filtering rule according to the processing situation that may be occurred in the service execution process of the called service control unit. The subsequent filtering rule is a concept introduced by the present invention with respect to the initial filtering rule (iFC), indicating that the filtering rule is a service filtering rule set according to a processing situation that may be occurred in the service execution process of the called service control unit.

 Subsequent filtering rules include subsequent trigger conditions and their corresponding subsequent processing methods. The subsequent triggering conditions include at least one of a subsequent message, a call state, a service control unit call failure, and a service control unit call success; the subsequent processing manner includes sending a message, rejecting the message, calling the specified service control unit, continuing the communication, and stopping. Perform at least one of a service filtering rule, a release service control unit, and a communication release.

 Here, the subsequent message in the subsequent trigger condition refers to all messages after the service control unit is called (that is, after receiving the service trigger message) until the current communication is released, and also includes the release message. For example, it may be a response code message of a SIP initial request message, or any SIP method or the like. The message name, message content and any combination of the subsequent messages can be used as subsequent trigger conditions; one or more subsequent messages may be included in the subsequent trigger conditions.

 Further, the source of the subsequent message can also be distinguished in subsequent trigger conditions. For example, depending on the source information, subsequent messages can be divided into the following two categories:

One is a message returned by the called service control unit, including a SIP initial request message, a SIP response code message (the message is a response code message of a SIP initial request message invoking the service control unit), and other subsequent SIP method messages (eg, SIP PRACK message, SIP A BYE message, etc., that is, a subsequent SIP method message that invokes the SIP initial request message of the service control unit).

 The other is a message sent to the called service control unit, including a SIP initial request message (unlike the SIP initial request message that invokes the current service filtering rule to invoke the service control unit), and a SIP response code message (the message is generally called) The response code message of the SIP initial request message returned by the service control unit) and other subsequent SIP method messages (ie, subsequent SIP method messages of the SIP initial request message returned by the called service control unit).

 It can be seen that the source information can indicate: the subsequent message is the same message as the SIP initial request message that invokes the service control unit, or the message that is the same as the SIP initial request message returned after the service control unit is called. , or a new SIP initial request message. The homology may be further represented as being located in the same call, session, or conversation.

 The call state in the subsequent trigger condition includes all process states of the current communication and any combination thereof. Taking the 3GPP TS 23.278 standard as an example, the call status includes: collecting information, analyzing information, routing failure, originating_busy, originating_non-answering, originating_responding, originating_disconnection, originating_abandonment, terminal attempting authentication, Terminal_Busy, Terminal_No Answer, Terminal_Answer, Terminal_Remove, Terminal_Abandon. One or more of the above call states may be included in the subsequent trigger conditions; for a detailed explanation of each of the above call states, see 3GPP TS 23.278, and no further details are provided herein. In addition, the call status in subsequent trigger conditions may also employ a SIP timer, such as timers T1, T2, Timer A, Timer B, etc., as defined in 3GPP TS 24.229. For a detailed explanation of the above SIP timer, refer to 3GPP TS 23.278 and 3GPP TS 24.229, which are not described here. Further, the timeout waiting time of the call state may also be described in the subsequent filtering rule.

The failure of the service control unit call in the subsequent trigger condition means that the called service control unit does not respond, or the service logic call in the called service control unit fails. The latter indicates that the service control unit is called normally, and the response is returned, but the user is not on schedule. Provide the corresponding business. The reason for the failure of the business logic call may be that the user has no permission or no data to use the service, a function failure in the service control unit, and the like. The business logic call failure is different from the case where the business logic in the service control unit is normally called but the communication fails. For example, if the call restriction service is called, it is a communication failure. The related protocol may be extended such that when the business logic call fails, the service control unit may return a message indicating that the business logic call failed, for example, return a SIP response code indicating that the business logic call failed or a SIP message carrying a service logic call failure indication. Wait. In the subsequent triggering conditions, the failure of the various service control unit calls may be separately described, for example, the service control unit does not respond or the service logic fails to be invoked, and the failure of the various service control unit calls may be uniformly described. In an actual application, the returned failure message may be used as a subsequent message in the subsequent trigger condition to indicate that the service logic call fails, and the call state in the subsequent trigger condition may also be used to indicate that the service control unit does not respond.

 The successful call of the service control unit in the subsequent trigger condition means that the invoked service control unit is successfully invoked, and the service control unit returns a message indicating that the service logic call is successful, for example, returning a SIP response code indicating that the service logic call is successful or carrying the business logic. Call the SIP message indicating the success. If the message returned by the service control unit does not explicitly indicate whether the service logic is successfully invoked, such as receiving an initial SIP request message, and returning an initial SIP request message that does not carry the service logic call success indication, the default may also be considered. The service control unit was successfully called.

 The sending message in the subsequent processing mode is: Send the specified message. In the subsequent processing mode, only the name of the specified message may be described, and the content of the specified message may be described. Further, the source and/or destination of the sent message may be distinguished in the subsequent processing manner. Specifically, depending on the source information, sending messages can be divided into the following three types:

The first type is the message returned by the called service control unit. For the description of the source information, please refer to the corresponding description of the subsequent source information in the subsequent trigger conditions as described above. The second type is a message sent to the called service control unit. For a description of the source information, refer to the corresponding description of the source information of the subsequent message in the subsequent trigger condition as described above.

 The third is to call the SIP initial request message of the service control unit, that is, the service trigger message.

 Wherein, as a special case of the first type and the second type, the sending message may be a subsequent message in the subsequent triggering condition.

 The destination information of the sent message may be: sending a message to the called service control unit, sending a message to the called service control unit (ie, starting direction of the current communication, such as sending a message to the calling party), to the called service The control unit sends a message backward (ie, the end direction of the current communication, such as sending a message to the called party).

 The reject message in the subsequent processing mode is: It is forbidden to send subsequent messages in subsequent trigger conditions. Further, the destination of the reject message may also be distinguished in a subsequent processing manner to indicate that the subsequent message is prohibited from being sent to the destination. Specifically, the destination information of the reject message may be: refusing to send a message to the called service control unit, rejecting the forward sending message to the called service control unit (such as the calling direction), or refusing to the called service control unit. The message is sent backwards (such as the direction of the called party).

 The call in the subsequent processing mode specifies that the service control unit is: Sends an invocation message to the specified service control unit. The address of the service control unit may be directly specified, or may be specified indirectly, for example, the identifier of the service filtering rule corresponding to the specified service control unit is described in the subsequent filtering rule (the address of the specified service control unit is described in the service filtering rule) At this point, the call to the specified service control unit will be implemented by the execution of the business filter rule. In general, calling the specified service control unit is divided into the following three cases:

The first case is to re-invoke the service control unit, and the subsequent processing mode can be used to process the subsequent trigger condition that the service control unit fails to be called, that is, the call message is resent to the service control unit that failed the call; Used to process subsequent triggers The condition is that the service control unit is successfully invoked, that is, the call message is sent again to the service control unit that successfully invokes. At this time, the call message sent again may not be the call message of the previous successful call of the service control unit.

 In the second case, the homogeneous service control unit is called, that is, the call message is sent to the homogeneous service control unit. This subsequent processing mode can be used to process the subsequent trigger condition as the service control unit call fails. Here, the homogeneous service control unit refers to a service control unit that can provide the same service as the service control unit that has failed the current call. If the AS7 call fails, and the AS8 can provide the same service as the AS7, the AS8 is called and a message is sent to the AS8. The address of the homogeneous service control unit can be set in the service filtering rule together with the address of the called service control unit, so that when the service filtering rule is executed, the address of the homogeneous service control unit corresponding to a certain service control unit can be obtained. .

 The third case is to call a new service control unit, which specifies the address of the new service control unit, and sends a call message to the designated new service control unit.

 The communication in the subsequent processing mode continues to: Continue processing the current communication. Specifically, if there is a subsequent service filtering rule, the subsequent service filtering rule is executed, otherwise the current communication process continues to be processed, for example, continuing to the called route, or sending the currently processed communication message to the calling party. In the subsequent processing manner of invoking the new service control unit, when the new service control unit corresponds to the subsequent service filtering rule, the method may also be implemented in this manner.

 The execution of the service filtering rule in the subsequent processing mode is: If there is a subsequent service filtering rule, the subsequent service filtering rule is stopped, and the current communication is continued, for example, continuing to the called route.

The release service control unit in the subsequent processing mode is: releasing the service control unit that has been called. In general, the sending message in the subsequent processing mode may also be set as a release message, such as a SIP BYE message, a SIP CANCEL message, etc., to indicate that the service control unit that has been called is released. The communication in the subsequent processing mode is released as: Release the current communication.

 It can be seen from the above technical solution that the method provided by the preferred embodiment of the present invention enables the service filtering rule to process subsequent messages in the communication process in addition to the SIP initial request message, that is, to provide a communication according to the subsequent filtering rule. Methods. The subsequent filtering rules in the embodiment of the present invention may be set by extending the existing iFC, or may be separately set.

 In the following embodiments, the existing iFC is extended to describe the subsequent filtering rules in the iFC, so that the initial filtering rule iFC that can only process the SIP initial request message is expanded to have the capability of processing subsequent messages. Business filtering rules. To this end, it is necessary to set a subsequent filtering rule corresponding to the called service control unit in the service filtering rule in advance, and for the sake of the cylinder, only the service filtering rules related to the embodiment are listed in the following embodiments. Piece.

 As mentioned earlier, the Service Control Unit is the host execution environment for a variety of services and provides a variety of business logic control functions. The service control unit can be an IMS application server, SCF, or the like. In the following embodiments, an IMS application server is taken as an example for description.

 Embodiment 1:

 In this embodiment, it is assumed that a SIP INVITE message is received, and the IMS application server AS1 is invoked. Thereafter, when the called user does not answer, the call is forwarded to the voice mailbox, the voice mailbox responds, and a 200 OK response message is returned. AS1 does not want to receive the 200 OK message automatically answered by the system. Therefore, the 200 OK message should be masked to AS1.

 The service filtering rule fragments set in this embodiment are as follows:

<TriggerPoint>

 <SPT>

 <Method>INVITE</Method>

</SPT> </TriggerPoint >

 <ApplicationServer>

 <ServerName>sip:asl @ims.example.com</ServerName>

 < SubsequentFilterCriteria>

 <SubsequentTriggerPoint>

 <SubsequentMessageToApplicationServer>

 <MessageName>200</MessageName>

 <SIPHeader>

 <Header>Contact</Header>

 <Content>automata</ Content>

 </SIPHeader>

 </SubsequentMessageToApplicationServer> </SubsequentTriggerPoint>

 <SubsequentHandlingMode>

 <Mode>RejectMessage</Mode>

 <Destination>ApplicationServer</Destionation>

 </SubsequentHandlingMode>

 </SubsequentFilterCriteria>

 </ApplicationServer> For convenience of description, the above-mentioned service filtering rule segment is referred to as a service filtering rule one in this embodiment. The following description of the method of processing the service control unit in this embodiment also focuses on the portion related to the segment of the service filtering rule.

 The flowchart of the service control unit processing method in the specific embodiments 1 to 3 of the present invention is shown. Referring to Figure 2, the method includes the following steps:

 Step 201: Perform a service filtering rule according to the service trigger message INVITE, and determine the called application server and its corresponding subsequent filtering rule.

The service filtering rules executed in this step are as shown in the service filtering rule one, where The content between <13⁄4886 01111> and </ 886 01111> is the trigger point information, indicating the trigger condition of the service filtering rule. In this embodiment, the trigger condition of the service filtering rule is a method (Method) service point trigger (SPT) with a value of INVITE.

 In this step, after the service filtering rule 1 is executed according to the INVITE message, the called application server name (ServerName) and its corresponding subsequent filtering rule (Subsequent FilterCriteria) are obtained, that is, <ApplicationServer> and < as shown in the service filtering rule one. Content between /ApplicationServer>.

The ServerName indicates the address of the called application server. In this embodiment, the value is sip:asl @ims.example.com, which represents the address of AS1. If there is a service control unit of the same quality as AS1, the address of the homogeneous service control unit of AS1 can be set here. Indicates the subsequent filtering rules corresponding to AS1. This part is the extended description of iFC in this embodiment. Subsequent filtering rules include subsequent trigger conditions and their corresponding subsequent processing methods. The same service control unit may have different subsequent filtering rules in different situations. In the present invention, a <SubsequentFilterCriteriax/SubsequentFilter Criteria> may be used to describe all subsequent processing modes and their corresponding subsequent triggering conditions, or multiple <SubsequentFilterCriteria may be used. ></SubsequentFilterCriteria> min ¹ J another embodiment described in the subsequent processing and follow-up corresponding to the trigger condition.

In the subsequent filter rule ¹ J, the content between <SubsequentTriggerPoint> and </SubsequentTrigger Point> indicates the subsequent trigger condition. There may be multiple Subsequent TriggerPoint></SubsequentTriggerPoint> indicating multiple subsequent trigger conditions, or multiple subsequent trigger conditions may be described between one <SubsequentTriggerPoint></SubsequentTriggerPoint>.

In the subsequent filtering rule, the content between <SubsequentHandlingMode> and </Subsequent HandlingMode> represents the subsequent processing party corresponding to the subsequent trigger condition. Style.

 In the subsequent trigger condition shown in the business filter rule 1, the content between <SubsequentMessage To ApplicationServer> ^ </SubsequentMessageToApplicationServer> -^. indicates that the source is a subsequent message sent to the called service control unit, and the content can be any subsequent The message's message name, the message content, and the source information of the message. Specifically, the message name ( MessageName ), the source ( Origination ), the SIP header field ( SIPHeader ), the header field ( Header ), and the content of the header field ( Content ). In addition, the description of the subsequent source may not be reflected in the <SubsequentMessageToApplicationServer> tag, and subsequent messages in subsequent trigger conditions may be described as follows:

<SubsequentMessage>

 <MessageName>200</MessageName>

 <Origination>ToApplicationServer</Origination>

 <SIPHeader>

 <Header>Contact</Header>

 <Content>automata</Content>

 </SIPHeader>

 </SubsequentMessage> The content between <SubsequentMessage>"^ </SubsequentMessage>-^ represents the subsequent message, where the source of the subsequent message is represented by Origination. In the above example, the value of Origination is ToApplicationServer, indicating the source of subsequent messages. Is the message sent to the called service control unit.

In the foregoing triggering condition, MessageName indicates the name of the subsequent message. In this embodiment, the value is 200; <81?11⁄2&(the content between 161 and </SIPHeader^ indicates the SIP header field content of the subsequent message, in this embodiment , set the Header to the contact header field ( Contact ), the Content header i or the content is set to auto-operate ( automata ). The mode (Mode) in the subsequent processing mode indicates a subsequent processing mode corresponding to the subsequent triggering condition. In this embodiment, the subsequent processing mode indicating the reject message (RejectMessage) is set. The destination indicates the destination of the reject message. In this embodiment, it is set as the service control unit (ApplicationServer), indicating that the message is refused to be sent to the called service control unit.

 Step 202: Record a subsequent filtering rule of the called application server, and send an INVITE message to the called application server, that is, the application server is initially called.

 In this step, according to the service filtering rule 1 executed in step 201, the called application server AS1 and its corresponding subsequent filtering rules are obtained, the subsequent filtering rules of AS1 are recorded, and the INVITE message is sent to AS1.

 Step 203: According to the subsequent message received during the execution of the service, the current call state, and the call failure of the service control unit, determine whether the subsequent trigger condition is satisfied according to the recorded subsequent filtering rule. When the subsequent trigger condition is met, the subsequent use is performed. The corresponding subsequent processing in the filtering rule processes the current communication.

 In this step, when receiving the 200 OK response message from the voice mailbox, the 200 OK response response message is matched with the recorded subsequent trigger condition: since the 200 OK message is a response from the voice mailbox, The "automata" is set in the Contact header field of the message, indicating that this is an automatic response from the system; moreover, the destination of the 200 OK message is AS1, and therefore, the subsequent trigger condition recorded in step 202 is successfully matched. After the matching is successful, the corresponding service control unit is processed in a subsequent processing manner corresponding to the subsequent triggering condition in the subsequent filtering rule. In this embodiment, the subsequent processing mode is a processing manner indicating the rejection message, that is, the 200 OK response is not received. The response message is sent to AS1.

Similarly, the subsequent call setup message that is used by the service control unit to process the service logic control is used as a follow-up message in the subsequent trigger condition, and the subsequent processing manner corresponding to the 183, the PRACK message, the UPDATE message, and the like is set as the reject message. Can be achieved The message is sent to the service control unit as needed, and the subsequent call setup message that is used by the service control unit to process the service logic control is shielded from the service control unit, thereby simplifying the call processing, improving the call setup efficiency, and shortening the call connection time. An example is as follows:

<ApplicationServer>

 <ServerName>sip:asl @ims.example.com</ServerName>

 < SubsequentFilterCriteria>

 <SubsequentTriggerPoint>

 <SubsequentMessageToApplicationServer>

 <MessageName>200</MessageName>

 <SIPHeader>

 <Header>Contact</Header>

 <Content>automata</ Content>

 </SIPHeader>

 </SubsequentMessageToApplicationServer>

<SubsequentMessageToApplicationServer>

 <MessageName>183</MessageName>

 </SubsequentMessageToApplicationServer>

<SubsequentMessageToApplicationServer>

 <MessageName>AllMessage</MessageName>

 <SIPHeader>

 <Header>CSeq</Header>

 <Content>PRACK</Content>

 </SIPHeader>

</SubsequentMessageToApplicationServer></SubsequentTriggerPoint> <SubsequentHandlingMode>

 <Mode>RejectMessage</Mode>

 <Destination>ApplicationServer</Destionation> </SubsequentHandlingMode>

 </SubsequentFilterCriteria>

</ApplicationServer> in the above-mentioned subsequent filtering rules, at <81^869116111; 13⁄4 6 0 1 and </81^869116111;

Three subsequent trigger conditions are described. The three subsequent trigger conditions are subsequent messages, which are: 200 messages sent to AS1, the Contact header field contains content automata; 183 messages sent to AS1; all messages sent to AS1, Cseq header field containing content PRACK (Various SIP response code messages including PRACK messages and PARCK messages). The three subsequent trigger conditions have the same subsequent processing mode: the corresponding subsequent message is rejected from being sent to AS1. In this embodiment, the wildcard description is allowed to be used in the subsequent filtering rule, for example, AllMessage means all messages, and 1XX means all SIP 1XX response code messages. In addition, in this embodiment, any combination of a plurality of subsequent trigger conditions is allowed to be described in a subsequent filtering rule, such as an "and", "or", "non" combination relationship, and any multiple combination relationship based on the three, etc., in the above In the subsequent filtering rules, the default combination relationship is "or", that is, as long as one of the three subsequent trigger conditions meets, the subsequent processing mode is executed.

 So far, the processing method of the service control unit of this embodiment is ended.

It can be seen from the foregoing embodiment that the present embodiment sets a subsequent filtering rule corresponding to AS1 in the service filtering rule one according to the processing situation that may be occurred in the service execution process of the called application server AS1. Then, according to the service trigger message INVITE After the service filtering rule 1 is executed, the subsequent filtering rule corresponding to the AS 1 is obtained. In the subsequent service execution process, the AS1 is processed according to the determined subsequent filtering rule, so that the signaling path of the called service control unit is adjusted according to requirements. , to solve business interactions and conflicts, in addition, Improve call setup efficiency and shorten call connection time.

 In the above embodiment, the technical solution of the present invention is described in detail by taking the case that the subsequent trigger condition is the subsequent message and the subsequent processing mode is the rejection. In actual applications, when the call state is migrated, subsequent trigger conditions may also be met; for the service control unit, there are other subsequent processing methods, such as the manner in which the message is sent. How the invention is carried out in these cases will be described in detail in the second embodiment below.

 Embodiment 2:

 In this embodiment, it is assumed that a SIP INVITE message is received, and the IMS application server AS2 is invoked. Thereafter, when the called user does not answer, AS2 wishes to quit the current communication, and therefore, a new call message should be sent to AS2.

 The service filtering rule fragments set in this embodiment are as follows:

<TriggerPoint>

 <SPT>

 <Method>INVITE</Method>

 </SPT>

 </TriggerPoint >

 <ApplicationServer>

 <ServerName>sip:as2@ims.example.com</ServerName>

 <SubsequentFilterCriteria>

 <SubsequentTriggerPoint>

 <CallState>

 <StateName>Terminating_NoAnswer</StateName>

<StateValue>20000</StateValue>

 </CallState>

 </SubsequentTriggerPoint>

<SubsequentHandlingMode> <Mode>SendingMessage</Mode>

 <MessageName>BYE</MessageName>

 <Origination>ToApplicationServer</Origination>

 <Destination>ApplicationServer</Destionation> </SubsequentHandlingMode>

 </SubsequentFilterCriteria>

 </ApplicationServer> For convenience of description, the above-mentioned service filtering rule segment is referred to as service filtering rule 2 in this embodiment. The following description of the method of processing the service control unit in this embodiment also focuses on the portion related to the segment of the service filtering rule.

 The flowchart of the service control unit processing method in this embodiment is the same as that in FIG. 2 in the first embodiment, and FIG. 2 is shown. In this embodiment, the service control unit processing method includes the following steps: In step 201, the service filtering rule is executed according to the service trigger message INVITE, and the called application server and its corresponding subsequent filtering rule are determined.

 The service filtering rule executed in this step is as shown in the service filtering rule 2. The content between <13⁄4886 011«> and </1 886 011«> is the trigger point information, which is the same as the first embodiment. The trigger condition for the filter rule is the method (Method) of the INVITE, which is the business point trigger (SPT).

 In this step, after the service filtering rule 2 is executed according to the INVITE message, similar to the first embodiment, the called application server name (ServerName) and its corresponding subsequent filtering rule 'J (SubsequentFilterCriteria) are obtained, that is, the service filtering rule is as follows: In the second example, ServerName represents the address of the called application server. In this embodiment, the value is sip: as2@ims.example.com, which represents the address of AS2.

among them, The content represents a subsequent filtering rule corresponding to AS2, and this part is an extended description of the iFC in this embodiment.

In the subsequent filter rule ¹ J, the content between <SubsequentTriggerPoint> and </ SubsequentTrigger Point> indicates the subsequent trigger condition. In the subsequent trigger condition of this embodiment, the content between <〇&1181&16> and </CallState> indicates the call status, and the part of the content may be the name of any call state and any related content thereof; <SubsequentHandling Mode> and < The content between /SubsequentHandling Mode> represents the subsequent processing method corresponding to the subsequent trigger condition.

 In the subsequent trigger condition shown in the service filtering rule 2, the state name (StateName) indicates the name of the call state. In this embodiment, the value is Terminal_No Answer (Noin Answer), and the State Value indicates the call state. The timeout period is long. In this embodiment, the value is 20000 milliseconds.

 The mode (Mode) in the subsequent processing mode of the service filtering rule 2 indicates the subsequent processing mode corresponding to the subsequent trigger condition. In this embodiment, it is set to indicate a subsequent processing manner of sending a message (SendingMessage), and the message is specified as a goodbye message (BYE) in the message name (MessageName), and the Origination of the message is set to ToApplicationServer, indicating the source of the BYE message. It is a subsequent SIP method message sent to AS2, that is, it is the same as the SIP initial request message returned after AS2 is called. The Destination of the message is set to ApplicationServer, indicating that the message is sent to AS2.

 In step 202, the subsequent filtering rule obtained in step 201 is recorded, and an INVITE message is sent to AS2, that is, AS2 is initially called.

In step 203, according to the subsequent message received during the execution of the service, the current call state, and the call failure of the service control unit, it is determined whether the subsequent trigger condition is satisfied according to the recorded subsequent filtering rule. When the subsequent trigger condition is met, The current communication is processed using the corresponding subsequent processing in the subsequent filtering rules. In this step, when the call state of the user is migrated to the terminal_no answer, the call state is matched with the recorded subsequent trigger condition, and the matching is successful, and the subsequent processing manner corresponding to the subsequent triggering condition in the subsequent filtering rule is used. Process the corresponding application server. In this embodiment, the corresponding subsequent processing mode is sent according to the call state and the subsequent filtering rule, and the specified message name is BYE, and the SIP BYE message is sent to AS2, so that AS2 quits the current communication, and the SIP BYE message and AS2 are The SIP initial request message returned after the call (the SIP INVITE message returned after the AS2 receives the call message SIP INVITE message) is the same.

 The timeout period of the user's call state transition to the terminal_non-answering may be specified in the subsequent filtering rule. For example, it is specified as 20000 milliseconds in this embodiment, or may be preset in the program, or may be set in other manners.

 So far, the processing method of the service control unit of this embodiment is ended.

 It can be seen from the foregoing embodiment that the present embodiment sets a subsequent filtering rule corresponding to AS2 in the service filtering rule 2 according to the processing situation that may occur in the service execution process of the invoked application server AS2. Then, according to the service trigger message INVITE The service filtering rule 2 is executed to obtain the subsequent filtering rule corresponding to the AS2. In the subsequent service execution process, the AS2 is processed according to the determined subsequent filtering rule, thereby implementing the signaling path of the called service control unit according to the need. , solve business interaction and conflict issues.

In the above embodiment, an example is given in which the called service control unit is adjusted in the same communication process, that is, the initial call and the subsequent trigger condition described are that when the user is in the same communication process, the pair is Call the relevant processing of the business control unit. In practical applications, the processing described by the initial call and subsequent trigger conditions of the called service control unit may also be related processing of the user in different communication processes. For example, the called service control unit is already in a communication process, when the user When another communication is initiated or received, it will cause the adjustment of the called service control unit. In the following third embodiment, how will these cases be implemented? The invention is described.

 Embodiment 3:

 In this embodiment, it is assumed that a SIP INVITE1 message is received, an IP television (IPTV) AS is invoked, and an IPTV service is provided to the user. Thereafter, when the user receives an incoming SIP INVITE2 message, the IPTV AS should pause. The user plays the video streaming media so that the user can accept the incoming incoming call and establish a call with the calling party that newly incoming the incoming call; thereafter, when the incoming incoming call is released, the IPTV AS should resume the call to the user. Play video streaming. Therefore, there are two communication processes in this embodiment, one is communication between the user and the IPTV, and the other is communication between the user and the incoming caller of the new incoming call.

 In order to implement the IPTV AS suspension service when the user receives a new incoming call, and implement the IPTV AS recovery service when the new incoming call is released, the embodiment sets the interaction in the service filtering rule for the INVITE1 message. Subsequent filtering rules corresponding to the IPTV AS, the subsequent filtering rule fragments related to the IPTV AS set in this embodiment are as follows:

<SubsequentFilterCriteria>

 <SubsequentTriggerPoint>

 <SubsequentMessageToApplicationServer>

 <MessageName>INVITE</MessageName>

 </SubsequentMessageToApplicationServer>

</SubsequentTriggerPoint>

 <SubsequentHandlingMode>

 <Mode>SendingMessage</Mode>

<MessageName>SameWithSubsequentMessage</MessageName>

 <Destination>ApplicationServer</Destionation>

</SubsequentHandlingModex/SubsequentFilterCriteria> For convenience of description, the above-mentioned subsequent filtering rule segment is referred to as a subsequent filtering rule three in this embodiment. The following description of the processing method of the service control unit in this embodiment also focuses on the part related to the subsequent filtering rule segment.

 The flowchart of the service control unit processing method in this embodiment is the same as that in FIG. 2 in the first embodiment, and FIG. 2 is shown. In this embodiment, the service control unit processing method includes the following steps: In step 201, according to the service trigger message INVITE1, the service filtering rule is executed, and the called application server and its corresponding subsequent filtering rule are determined.

 After the service filtering rule is executed according to the service trigger message INVITE1, the subsequent filtering rules corresponding to the IPTV AS are obtained, as shown in the following filtering rule three:

 The content of <SubsequentTriggerPoint>"^ </SubsequentTriggerPoint> -^. indicates that the subsequent trigger condition for the new incoming call is the subsequent message to the IPTV AS (SubsequentMessageToApplicationServer). The MessageName is set to the INVITE message, that is, the subsequent message. It is a new SIP initial request message sent to the IPTV AS. In the subsequent processing mode (SubsequentHandlingMode), the Mode is set to SendendingMessage, and the MessageName is set to SameWithSubsequentMessage, indicating that the subsequent processing mode is to send subsequent messages in the subsequent trigger condition (ie, new incoming call) Incoming INVITE message), so there is no need to set the message name here. The Destination of the message is set to ApplicationServer, indicating that the message is sent to the IPTV AS.

 In step 202, the subsequent filtering rules of the IPTV AS obtained in step 201 are recorded, and the IPTV AS is initially invoked.

 In step 203, according to the subsequent message received during the execution of the service, the current call state, and the call failure of the service control unit, it is determined whether the subsequent trigger condition is satisfied according to the recorded subsequent filtering rule. When the subsequent trigger condition is met, The current communication is processed using the corresponding subsequent processing in the subsequent filtering rules.

In this step, when a new incoming call INVITE2 message is received, according to the determined follow-up Filtering the rule, sending the INVITE2 message to the IPTV AS; the IPTV AS receives the INVITE2 message, and after determining that it is a new incoming call for establishing a call, the IPTV AS suspends the service to the user; thereafter, the new call The incoming call is released. Since the IPTV AS is already in the signaling path established by the INVITE2 message, it will receive the BYE release message for the INVITE2 message. After parsing, it is determined that this is the release of the incoming call, and the IPTV AS is restored. Service to users.

 So far, the processing method of the service control unit of this embodiment is ended.

 In this embodiment, subsequent filtering rules may also be set as follows:

 The subsequent trigger conditions and subsequent processing modes for the IPTV AS are set in the service filtering rule in advance. The subsequent processing manner for the subsequent trigger condition INVITE2 message is to send a new INVITE3 message to the IPTV AS, and specify the content of the INVITE3 message as: Set the media direction of the INVITE1 message establishment session to "inactive". That is, the INVITE3 message is a re-INVITE message (re-INVITE1). Correspondingly, the release of the BYE message to the INVITE2 message is also set to a subsequent trigger condition. The corresponding subsequent processing mode is to send an INVITE4 message to the IPTV AS, and the message is also a re-INVITE1 message whose media direction is set to "active". (active ),, and set the Originaltion of the above INVITE3 message and INVITE4 message to SameDialogWith InvokingMessage, indicating that INVITE3 and INVITE4 are in the same conversation with the invocation message, that is, the service trigger message INVITE1, that is, the same dialog (Dialog) identifier as INVITE1. .

 Then, the service filtering rule is executed according to the service trigger message INVITE1, and subsequent filtering rules corresponding to the IPTV AS are obtained.

Thereafter, during the service execution process, when the INVITE2 message is received, the INVITE3 message is sent to the IPTV AS according to the determined subsequent filtering rule. The IPTV AS receives the INVITE3 message, and sets the media direction of the INVITE1 message establishment session to deactivate, that is, does not send media to the user. When the new incoming call is released, that is, when the BYE message is received, to the IPTV AS The INVITE4 message is sent, the media direction of the INVITE1 message establishing session is set to be activated, and the IPTVAS resumes service.

 The above is the description of the third embodiment of the present invention. The following describes the specific implementation method of the subsequent processing mode as the communication continues by the fourth embodiment.

 Embodiment 4:

 In this embodiment, it is assumed that the user initiates an INVITE message, and the protocol extension is described in the request header field (Require) of the INVITE message or a certain media type is described in the INVITE message body. After the service filtering rule is executed, one is invoked. The ring back tone service AS of the CRBT service is provided; when the called CRBT service AS does not support the protocol described by the Require header field

When the AS does not support the media type described in the message body, it will return an Unsupported Media Type that is not supported by 415. In this embodiment, it is assumed that after the CRBT service AS is invoked, there is also a service filtering rule for the application server AS4. According to the prior art, AS4 is only called when the SIP initial request is received, and when the CRBT service AS returns a 420 response code or a 415 response code. When AS4 will not be called, AS4 will not be able to join the call signaling path of the user. However, since the CRBT service is not a necessary service in the call setup process, the user hopes that the CRBT service can still be provided normally, so that the call success rate can be improved.

 In order to realize that the AS4 can be normally called when the CRBT service AS cannot provide services normally, this embodiment presets the following filtering rules in the service filtering rule as follows:

<Sub sequentFilterCriteria>

 <SubsequentTriggerPoint>

 <SubsequentMessageFromApplicationServer>

<Mes sageName>420</Mes sageNamo <MessageName>415 </Mes sageNamo

 </SubsequentMessageFromApplicationServer>

</SubsequentTriggerPoint>

 <SubsequentHandlingMode>

 <Mode>CallContinued</Mode>

 </SubsequentHandlingMode>

 </SubsequentFilterCriteria> In the above subsequent filtering rules, the subsequent trigger condition is set to follow-up messages. Subsequent MessageFromApplicationServer indicates that the subsequent message is from the message returned by the called service control unit. The names of subsequent messages are 420 messages and 415 messages. As mentioned before, the subsequent trigger condition can also be set to the subsequent message SubsequentMessage, and the source information of the subsequent message is set by the label Origination; and, here, two subsequent trigger conditions (420 messages and 415 messages) are provided, indicating these Subsequent messages have the same subsequent processing mode. As mentioned above, the combination of these two subsequent trigger conditions defaults to "or";

 Subsequent processing SubsequentHandlingMode , Mode is set to CallContinued , indicating communication continues.

 In this way, during the service execution process, when the subsequent triggering conditions are met, the service filtering rule of AS4 will be executed, and AS4 will be added to the call signaling path of the user, thereby realizing the adjustment of the signaling path of the service control unit. Business interaction and conflict issues, and improved call setup efficiency.

Generally, the service triggering message INVITE of the color ring service AS can be used to perform the service filtering rule of the AS4. Of course, the execution basis of the subsequent service filtering rule can be further specified here. For example, in the subsequent processing mode, a combination of "send message," and "communicate continuation" is used, and "send message" is set to send a SIP initial request message for calling the CRBT service AS to the "backward of the called service control unit". In the above fourth embodiment, the specific implementation manner of the present invention is described in detail in the following example, in which the subsequent triggering condition is a subsequent message, and the subsequent processing mode is the continuation of the communication. The subsequent processing method is a detailed description of the case where the execution of the service filtering rule is stopped.

 Embodiment 5:

 In this embodiment, it is assumed that the user initiates an INVITE message, and after executing the service filtering rule, the application server AS5 is invoked; AS5 detects that the call is an emergency call, so an emergency flag is set in the returned INVITE message; When you stop using other services, continue to route the call to the called party. To this end, the embodiment sets a subsequent filtering rule as shown in the following in the service filtering rule:

<Sub sequentFilterCriteria>

 <SubsequentTriggerPoint>

 <SubsequentMessageFromApplicationServer>

 <MessageName>INVITE</MessageName>

 <SIPHeader>

 <Header>Priority</Header>

 <Content>urgent</ Content>

 </SIPHeader>

 </SubsequentMessageFromApplicationServer>

 </SubsequentTriggerPoint>

 <SubsequentHandlingMode>

 <Mode>StopNextFilterCriteria</Mode>

 </SubsequentHandlingMode>

</SubsequentFilterCriteria> In the above subsequent filtering rules, the subsequent trigger condition is set to follow-up messages. Subsequent MessageFromApplicationServer indicates that the subsequent message comes from the called service control list. The message returned by the element, the name of the subsequent message is the INVITE message; the Header is set to the Priority header field, and the Content is set to urgent, indicating that this is an emergency call.

 Subsequent processing SubsequentHandlingMode , Mode is set to StopNextFilter Criteria, which means that the business filtering rule is stopped.

 In this way, during the service execution process, if the subsequent triggering conditions are met, if the subsequent service filtering rule exists after the service filtering rule of the AS5, the subsequent service filtering rule will be stopped, that is, the service control unit corresponding to the subsequent service filtering rule is excluded. Outside the user's call signalling path, and continue to route the call to the called party. In this way, the adjustment of the signaling path of the service control unit is realized, the conflict between the emergency service and other services is solved, the call establishment efficiency is improved, and the call connection time is shortened.

 The following describes the specific implementation manner of the present invention, in which the subsequent triggering condition is a follow-up message, and the subsequent processing mode is to stop performing subsequent service filtering. The following describes how to implement the call according to actual needs when the service control unit fails to be invoked. The new business control unit is a follow-up treatment.

 Example 6:

 In this embodiment, it is assumed that the user initiates an INVITE message, and after executing the service filtering rule, the application server AS6 is invoked; and the current state of the AS6 is "busy", and the service logic control cannot be processed. Therefore, the busy response code (Busy) is returned 486. Here ), Call Forwarding Busy (CFB) AS should be called at this time. In order to implement the CFB AS according to actual needs, the subsequent filtering rules set in the service filtering rule in this embodiment are as follows:

<Sub sequentFilterCriteria>

 <SubsequentTriggerPoint>

 <SubsequentMessageFromApplicationServer>

<MessageName>486</MessageName> </SubsequentMessageFromApplicationServer>

 </SubsequentTriggerPoint>

 <SubsequentHandlingMode>

 <Mode>InvokingNewApplicationServer</Mode>

 <ServerName>sip:cfb-as@ims.example.com</ServerName>

</SubsequentHandlingMode>

 </SubsequentFilterCriteria> In the above subsequent filtering rules, the name of the subsequent message in the subsequent trigger condition is 486 message. In the subsequent processing mode, Mode is set to InvokingNewApplicationServer, which means that the new service control unit is called, and the name of the new service control unit is set in ServerName. For example, in this embodiment, it is set to sip:cfb-as@ims.example.com, which is the address of the CFB AS.

 In this way, during the service execution process, when the subsequent trigger condition is met, the call will be sent to the address of the CFB AS, that is, the service control unit is called only when the trigger condition of the service control unit is satisfied, and the service is invoked according to actual needs. The control unit solves the problem of business interaction and conflict, and improves call setup efficiency and shortens call connection time.

 In general, the CFB AS can be invoked using AS6's Service Trigger Message INVITE, although the call message to the new Service Control Unit can be further specified here. For example, in the subsequent processing mode, a combination of "send message" and "communicate continuation" is used, and "send message" is set to send a SIP initial request message calling AS6 to "backward of the called service control unit".

So far, the description of the processing method of the service control unit in the sixth embodiment of the present invention is completed. In the above embodiment, it has been pointed out that the present invention allows one or more subsequent processing modes to be set between <SubsequentHandling ^10(16> and </81^691161«11⁄211(11113⁄4^10(16>, the following seventh embodiment will Describe in detail how to use the combined subsequent processing. Example 7:

 In this embodiment, the user initiates a SUBSCRIBE message to subscribe to the change notification of the user data, that is, notify the user when the user data in the network changes. The above-mentioned CRBT service AS and CFB AS both store user data, so the SUBSCRIBE message needs to be sent to the CRBT service AS and CFB AS. According to the service filtering rule, the CRBT service AS is first invoked. After receiving the SUBSCRIBE message, the processing user subscription is successful, and the subscription success message 200 message is returned. At this time, the SUBSCRIBE message needs to be used to call the CFB AS, and the 200 message is returned to the user. In this embodiment, the service filtering rule for the color ring back tone service AS is set in the embodiment to enable the CFB AS to be invoked according to actual needs, as follows:

<TriggerPoint>

 <SPT>

 <Method>SUBSCRIBE</Method>

 </SPT>

 </TriggerPoint >

 <ApplicationServer>

 <ServerName>sip:colored-ring-as@ims.example.com</ServerName> <SubsequentFilterCriteria>

 <SubsequentTriggerPoint>

 <SubsequentMessageFromApplicationServer>

 <MessageName>AllMessage</MessageName>

 </SubsequentMessageFromApplicationServer> </SubsequentTriggerPoint>

 <SubsequentHandlingMode>

 <Mode>SendingMessage</Mode>

<MessageName>SameWithSubsequentMessage</MessageName><Destination>Front_ApplicationServer</Destionation><Mode>SendingMessage</Mode> <MessageName>SameWithInvokingMessage</MessageName><Destination>Back_ApplicationServer</Destionation>

 <Mode>InvokingNewApplicationServer</Mode>

 <ApplicationServerID> 10</ApplicationServerFilterID> </SubsequentHandlingMode>

 </SubsequentFilterCriteria>

 </ApplicationServer> In the foregoing service filtering rule, the content between <886 01111> and </13⁄4886 01111> is the trigger point information, and the trigger condition of the service filtering rule in this embodiment is the method (Method) with the value of SUBSCRIBE. The service point trigger (SPT), correspondingly, the called application server name ( ServerName ) takes the value sip:colored -ring-as @ims. example.com , which is the call address of the CRBT service AS.

 In the subsequent filtering rule corresponding to the CRBT service AS, the name of the subsequent message as the subsequent trigger condition is AllMessage, indicating that the subsequent trigger condition is all messages returned from the called service control unit.

 /^<SubsequentHandlingMode>^</SubsequentHandlingMode> -^., three post-processing methods are set:

 The first mode is that Mode is set to SendingMessage, and the name of the sent message is Same WithSubsequentMessage, that is, the subsequent message of the subsequent trigger condition, that is, the message returned by the ring back tone service AS after being called. The destination Destination is set to Front-Application Server, indicating forward delivery to the called service control unit.

In the second mode, Mode is set to SendingMessage, and the name of the sent message is Same WithlnvokingMessage, that is, the CR initial request message (SUBSCRIBE message) is called by the CRBT service AS, and the destination destination is set to Back_Application Server, indicating to the called service control unit. Send backwards. The third mode is that Mode is set to InvokingNewApplicationServer, which means that the new service control unit is called. In the sixth embodiment, the implementation of the subsequent processing mode of invoking the new service control unit is indicated by setting the name of the new service control unit. In this embodiment, another implementation manner of invoking the new service control unit is provided. : Set the service filtering rule identifier corresponding to the new service control unit itself. The application server Filter1D indicates that the new service control unit itself corresponds to the corresponding service filtering rule identifier, that is, the corresponding service filtering rule identifier corresponding to the new service control unit (CFB AS) is set to 10, and the iFC is taken as an example. The rule ID can be the priority of the iFC.

 In this way, the CRBT service AS is first invoked according to the execution of the service filtering rule. In the service execution process, when the subsequent triggering condition is satisfied, the CRBT service AS returns a message, and then sends a message returned by the CRBT service AS to the CR ring service AS. If the CRBT service AS returns a message indicating that the subscription is successful, the message will be forwarded to the user, that is, sent to the user, and then sent to the CRBT service AS in the backward direction of the CRBT service AS, that is, the SUBSCRIBE message, the message The service triggering message to be used as the iFC of the priority level 10, that is, the service filtering rule corresponding to the CFB AS, that is, the iFC with the priority of 10.

 In the embodiments provided by the present invention, subsequent processing manners using a plurality of arbitrary combinations are allowed, such as a combination of "simultaneous execution", "sequential execution", and any multiple combination relationship based on the two. In this embodiment, by default, the combination of the three subsequent processing modes is "sequential execution". In this way, when the previous service control unit is called instead of the SIP initial request message, the latter service control unit can be called according to actual needs, thereby solving the business interaction and conflict problem.

So far, the description of the processing method of the service control unit in the seventh embodiment of the present invention is ended. In the above embodiment, a specific implementation manner for describing a subsequent filtering rule related to a called service control unit in a service filtering rule is given, that is, a subsequent filtering is performed on a called service control unit in a service filtering rule. The rules are processed. In addition to this In addition, the present invention also supports processing one or more called service control units in accordance with subsequent filtering rules in one service filtering rule. At this time, there are two cases. The first case is: the call of the one or more called service control units comes from a service filter rule, and the second case is: the call of the one or more called service control units From more than one business filter rule.

 In the following embodiment 8, how to implement the present invention in the first case above will be introduced.

4 knife

 Example 8:

 In this embodiment, it is assumed that the service filtering rule is executed and the IMS application servers AS1 and AS2 are called. Thereafter, when both AS1 and AS2 fail to call, the communication is released, and when only one of the AS1 and AS2 calls fails, the communication continues. In this embodiment, the service filtering rules shown below are set in advance for AS1 and AS2:

<TriggerPoint>

 <SPT>

 <Method>INVITE</Method>

 </SPT>

 </TriggerPoint >

 <ApplicationServer>

 <ServerName>sip:asl @ims.example.com</ServerName>

 <ServerName>sip:as2@ims.example.com</ServerName>

 <Sub sequentFilterCriteria>

 <SubsequentTriggerPoint>

 <InvokingFailure>

 <ConditionTypeCNF> 1 </ConditionTypeCNF>

 <Source> sip: as 1 @ ims.example.com </Source>

<Source> sip: as2@ims.example.com </Source> </InvokingFailure>

 </SubsequentTriggerPoint>

 <SubsequentHandlingMode>

 <Mode>CallRelease</Mode>

 </SubsequentHandlingMode>

<SubsequentTriggerPoint>

 <InvokingFailure>

 <ConditionTypeCNF>0</ConditionTypeCNF>

 <Source> sip: as 1 @ ims.example.com </Source>

 <Source> sip: as2@ims.example.com </Source>

 </InvokingFailure>

 </SubsequentTriggerPoint>

 <SubsequentHandlingMode>

 <Mode>CallContinued</Mode>

 </SubsequentHandlingMode>

 </SubsequentFilterCriteria>

 </ApplicationServer> In the above business filter rule, the content between < 1 311011860^1 and </ 1 31^011860^1 indicates that the application server is called. In this embodiment, two called application server names sip: as l @ims.example.com sip: as2@ims.example.com are given, indicating that the service filtering rule is applied to the two application servers AS1. Both are valid with AS2. After the service filtering rule is executed, AS1 and AS2 will be called. Generally, AS1 and AS2 can be called in order, or other calling methods can be specified in the service filtering rule, such as simultaneous calling.

 Two subsequent trigger conditions and corresponding subsequent processing methods are respectively described in the subsequent filtering rules.

Where two subsequent trigger conditions are failed by the service control unit call (InvokingFailure), /^<InvokingFailure>^</InvokingFailure>-^|s] is the description of the failure of the service control unit call. Where Source indicates the source of the failure of the service control unit call. In this example, two sources AS1 and AS2 are given. ConditionTypeCNF represents a combination of conditions using a regular expression. A value of 1 in the first subsequent trigger condition indicates that the combination type of the two sources AS1 and AS2 is "AND", that is, the subsequent trigger condition is that the AS1 and AS2 calls fail. The corresponding subsequent processing method is communication release (CallRelease); in the second subsequent trigger condition, ConditionTypeCNF takes a value of 0, indicating that the combination type of the two sources AS1 and AS2 is "OR (OR)", that is, the subsequent trigger condition is The AS1 or AS2 call fails, and the corresponding subsequent processing method is CallContinued.

 Thus, during the execution of the service, when the subsequent trigger condition is satisfied, the communication release or communication continues.

 As described above, in this embodiment, the subsequent trigger condition may be set to the call state to indicate that the service control unit fails to be called, for example, the call state name is set to “the service control unit invokes no response”, and may also be triggered subsequently. The timeout waiting time for the call state is further set in the condition.

 The technical solution provided by the embodiment of the present invention, when describing the subsequent triggering condition, may indicate which service control unit is associated with the subsequent triggering condition, such as indicating the subsequent message, the call state, and the source service control unit that the service control unit fails to call, for example, The service control unit described in this embodiment calls the failed source service control unit. Similarly, when describing the subsequent processing mode, it may indicate which service control unit is associated with the subsequent processing mode. For example, when describing the source information of the sent message, the source service control unit may be specified, and the destination service control unit that sends the message may be specified. It may also indicate the destination service control unit of the reject message, and may also indicate the destination service control unit that releases the service control unit, and may even indicate the destination service control unit that invokes the specified service control unit.

Embodiments of the present invention also support the implementation of the second case described above, that is, in a service filtering When more than one called service control unit performs subsequent filtering rule processing in the rule, the calls of the one or more called service control units are respectively from more than one service filtering rule, for example: 3⁄4:

<TriggerPoint>

 <SPT>

 <Method>INVITE</Method>

 </SPT>

 </TriggerPoint >

 <ApplicationServer>

 <ServerName>sip:asl @ims.example.com</ServerName>

 <Sub sequentFilterCriteria>

 <SubsequentTriggerPoint>

 <InvokingFailure>

 <ConditionTypeCNF> 1 </ConditionTypeCNF>

 <Source> sip: as 1 @ ims.example.com </Source>

 <Source> sip: as2@ims.example.com </Source>

 <ApplicationServerID> 10</ApplicationServerFilterID> </InvokingFailure>

 </SubsequentTriggerPoint>

 <SubsequentHandlingMode>

 <Mode>CallRelease</Mode>

 </SubsequentHandlingMode>

 </SubsequentFilterCriteria>

</ApplicationServer> In the above service filtering rule, the corresponding called application server has only one AS1, and the name is sip:asl @ims.example.com. In the subsequent filtering rules of AS1, in addition to AS1, there is another AS2 named sip:as2@ ims. example .com, corresponding The ApplicationServer1D label is set to 10, which indicates that the AS2 itself corresponds to the attribute of the service filtering rule, that is, the application server corresponding to the service filtering rule is AS2. In this way, in the subsequent filtering rules in a service filtering rule, the subsequent filtering rules of the service control unit invoked by other service filtering rules may be described.

 In this way, during the execution of the service, when both AS1 and AS2 fail to call, the communication is released.

 In the embodiment of the present invention, a method for performing subsequent filtering processing on multiple called service control units in a service filtering rule may, on the one hand, describe and execute the description and execution of the service filtering rule; on the other hand, it may also combine more Subsequent processing application.

 So far, the description of the processing method of the service control unit in the eighth embodiment of the present invention is completed. In addition, it should be noted that, in the embodiment of the present invention, when the subsequent processing mode is to invoke the specified service control unit or the communication continues, the subsequent communication processing may be the execution of a specified service filtering rule, that is, the subsequent processing manner. The corresponding subsequent trigger condition is a trigger execution prerequisite of the specified service filtering rule. Obviously, such a service filtering rule is a special type of service filtering rule. The present invention allows a special identifier to be set in such a service filtering rule so that such a service filtering rule is only used when a specific subsequent triggering condition is met. Trigger execution. For example, if a SIP initial request message is received, the service filtering rule is executed in sequence. If the special identifier is set in a service filtering rule, the corresponding subsequent triggering condition is checked. If not, the service is not executed. Filter rules.

 In addition, the present invention also provides a way to allow subsequent trigger conditions to be directly set in such service filtering rules so that such service filtering rules are not triggered when certain subsequent triggering conditions are not met. . The following embodiment IX will explain in detail how the invention is implemented in this case.

 Example 9:

In this embodiment, there are service interactions between AS1 and AS2, and service filtering of AS1. Rule 1 is executed, and the call message INVITE1 message is sent to AS1, and the AS1 call succeeds; thereafter, the service filter rule 2 of AS2 is executed, and the call message INVITE2 message is sent to AS2, and the AS2 call is successful. In order to implement the service interaction between AS1 and AS2, AS 1 needs to be aware of the call of AS2. That is, the call message INVITE2 message needs to be sent to AS1. The example of service filter rule 3 of AS1 is as follows:

<TriggerPoint>

 <SPT>

 <Method>INVITE</Method>

 </SPT>

 <SPT>

 <SubsequentTriggerPoint>

 <InvokingSuccess>

 <ConditionTypeCNF> 1 </ConditionTypeCNF>

 <Source> sip: as 1 @ ims.example.com </Source>

 <ApplicationServerID> 10</ApplicationServerFilterID> <Source> sip: as2@ims.example.com </Source>

 <ApplicationServerID>20</ApplicationServerFilterID> </InvokingSuccess>

 </SubsequentTriggerPoint>

 </SPT>

 </TriggerPoint >

 <ApplicationServer>

 <ServerName>sip:asl @ims.example.com</ServerName>

</ApplicationServer> In the service filtering rule 3 of the foregoing AS1, the INVITE2 message is set to an SPT, and the subsequent triggering condition is also set to SPT, that is, the filtering matching condition of the service filtering rule 3 is directly set, and the subsequent triggering condition is the service control. The unit call succeeds (InvokingSuccess), The ID of Service Filtering Rule 1 of AS1 is 10, the ID of Service Filtering Rule 1 of AS2 is 20, and the ConditionTypeCNF is set to "1", indicating that both AS 1 and AS2 are successfully invoked.

 In this way, the service filtering rule 3 is executed, and the subsequent trigger condition of the called service control unit AS1 and the corresponding other service filtering rule is obtained, and the subsequent trigger condition is used as the SPT. When the two SPTs are satisfied, the current communication is performed. Processing, sending a call message INVITE2 message to the service control unit AS1, that is, the subsequent process is to invoke the specified service control unit, so that AS1 processes the corresponding service interaction.

 It can be seen that the subsequent triggering conditions of the service filtering rule 1 and the service filtering rule 2 are set in the service filtering rule 3, so that it becomes the execution matching condition of the service filtering rule 3. As a matter of course, as described above, the subsequent triggering condition may be set to the subsequent filtering rule of the service filtering rule 2, and the corresponding subsequent processing is to execute the specified service filtering rule 3. In this case, in the service filtering rule 3 Set the special label above. In this way, when the INVITE2 message is received, if the subsequent trigger condition is not met, the INVITE2 message will not be matched to perform the service filtering rule 3.

 So far, the description of the processing method of the service control unit in the ninth embodiment of the present invention is completed. In the above embodiment, as long as the service filtering rule is executed, the called service control unit and its corresponding subsequent filtering rule can be determined. As a special case, the present invention also allows the "called service control unit" to be empty. This is because the subsequent filtering rule describes the situation that occurs after the called service control unit is called at the initial request, that is, the subsequent filtering rule relies on first obtaining the called service control unit, and if the user only signs one AS. And the call of the AS itself is described in the subsequent filtering rule, then no service control unit is called at the initial request, so that the subsequent filtering rule will not be dependent on the called service control unit, the following embodiment Ten will explain in detail how to implement the invention in this case.

Example 10: In this embodiment, it is assumed that the user initiates an INVITE message, and the CFB AS is invoked when the called user is busy. The subsequent filtering rules set in the service filtering rule in this embodiment are as follows:

<TriggerPoint>

 <SPT>

 <Method>INVITE</Method>

 </SPT>

 </TriggerPoint >

 <ApplicationServer>

 <ServerName>NULL</ServerName>

 <Sub sequentFilterCriteria>

 <SubsequentTriggerPoint>

 <SubsequentMessageFromBack>

 <MessageName>486</MessageName>

 </SubsequentMessageFromBack>

 </SubsequentTriggerPoint>

 <SubsequentHandlingMode>

 <Mode>InvokingNewApplicationServer</Mode>

<ServerName>sip:cfb-as@ims.example.com</ServerName>

 </SubsequentHandlingMode>

 </SubsequentFilterCriteria>

</ApplicationServer>

In the above service filtering rule, the matched application server name (ServerName) is "NULL" (empty). In the corresponding subsequent filtering rule, the label of the subsequent message in the subsequent triggering condition is SubsequentMessageFromBack, indicating that the source information of the subsequent message is From the backward direction, since there is no specified application server, there is no label SubsequentMessageToApplicationServer that uses the subsequent message used in the previous embodiment (of course It can also be used, but another way to express the source information of subsequent messages. It should be noted that the expression of the source information may also be used in the foregoing embodiment, and may represent further subdivision of the source information, that is, whether the distinction is forward or backward.

 In the subsequent filtering rule, the name of the subsequent message in the subsequent trigger condition is 486 message. In the subsequent processing mode, the Mode is set to InvokingNewApplicationServer, indicating that the new service control unit is invoked, and the name of the new service control unit is set in the ServerName. In this embodiment, it is set to sip:cfb-as@ims.example.com, which is the address of the CFB AS.

 In this way, during the service execution process, when the SIP initial request INVITE message is matched with the service filtering rule, the corresponding called service control unit is not obtained, but the subsequent filtering rule is still obtained. When the called party is busy, the 486 message is received. After the subsequent trigger condition is met, the call will be sent to the address of the CFB AS. By default, the SIP initial request INVITE message can be used to invoke the CFB AS, and the call message to the CFB AS can also be set in the subsequent processing mode.

 So far, the description of the processing method of the service control unit in the tenth embodiment of the present invention is ended. In order to implement subsequent filtering rule processing on the service control unit, the present invention provides a service control unit processing apparatus, which is configured to execute a service filtering rule, determine a called service control unit and a corresponding subsequent filtering rule, and During the service execution process, the service control unit is processed according to the determined subsequent filtering rules. The service control unit processing apparatus of the present invention will now be described with reference to an apparatus embodiment.

 FIG. 3 is a schematic structural diagram of a service control unit processing apparatus according to an embodiment of the present invention. Referring to FIG. 3, the apparatus includes a subsequent filtering rule obtaining module 301, a subsequent trigger condition matching module 302, and a subsequent processing mode executing module 303.

The subsequent filtering rule obtaining module 301 is configured to execute a service filtering rule, and determine a subsequent filtering rule that includes a subsequent triggering condition and a corresponding subsequent processing mode, and is used to provide a subsequent triggering condition to the subsequent triggering condition matching module 302, and to perform subsequent processing. Mode execution mode Block 303 provides a subsequent processing method;

 The subsequent trigger condition matching module 302 is configured to determine whether the trigger condition and the subsequent trigger condition provided by the subsequent filter rule obtaining module 301 are satisfied during the execution of the service, and notify the subsequent processing mode execution module 303 when the subsequent trigger condition is met. ;

 The subsequent processing mode execution module 303 is configured to perform a subsequent processing manner provided by the subsequent filtering rule obtaining module 301 according to the notification of the subsequent triggering condition matching module 302.

 Next, a system embodiment will be described to explain how the apparatus shown in Fig. 3 is applied to the service control unit processing system of the present invention. FIG. 4 is a schematic structural diagram of a service control unit processing system according to an embodiment of the present invention. Referring to FIG. 4, the system includes a service filtering rule base 410, a service control unit processing unit 420, and a service control unit 430. The service control unit processing unit 420 further includes a subsequent filtering rule obtaining module 421, a subsequent trigger condition matching module 422, and The subsequent processing mode executes the module 423.

 In the system shown in FIG. 4, the service filtering rule base 410 is configured to save or generate a service filtering rule of the user, and is configured to provide a service filtering rule to the subsequent filtering rule obtaining module 421 in the service control unit processing device 420;

 The subsequent filtering rule obtaining module 421 is configured to receive and execute the service filtering rule from the service filtering rule base 410, and provide a subsequent triggering condition to the subsequent triggering condition matching module 422, and provide a subsequent processing manner to the subsequent processing mode execution module 423.

 The subsequent trigger condition matching module 422 is configured to determine whether the trigger condition is met during the execution of the service, and notify the subsequent processing mode execution module 423 to perform a subsequent processing mode, the service control unit 430, and the current communication, when the subsequent trigger condition is met. Carry out corresponding processing;

 The service control unit 430 is configured to provide various service logic control functions according to the processing of the subsequent processing mode execution module 423 in the service control unit processing device 420.

Further, the service control unit may further include a first communication module, configured to be used in When the service filtering rule is generated in the process of the service, the generated service filtering rule is sent to the service filtering rule base 410.

 Correspondingly, the service filtering rule base 410 may further include a second communication module for receiving the service filtering rule from the service control unit 430, and a storage module for saving the service filtering rule.

 In the system shown in FIG. 4, there may be one or more service filtering rule bases 410, and the service filtering rule base 410 in the system may be an independent user subscription database, such as a home subscriber server (HSS, Home Subscriber Server), The filtering rule is stored as the user subscription data, such as the aforementioned iFC; the service filtering rule base 410 in the system may also be located in the service control unit processing device 420, such as the service filtering rule exists as a piece of program or configuration data in the service control unit. In the device 420, the service filtering rule base 410 in the system may also be located in the service control unit 430, for example, the service control unit 430 generates a service filtering rule in the service processing process.

 In the system shown in FIG. 4, the service control unit processing apparatus 420 may be an S-CSCF, a Service Broker, or a Service Capability Interaction Manager (SCIM) defined in the 3GPP IMS standard. ;

 The service control unit 430 is a host execution environment of various services, and may be an IMS application server, a traditional intelligent network SCF entity, or the like;

 The interface between the service filtering rule base 410 and the service control unit processing device 420 may be a Diameter protocol or an internal interface protocol, etc.; the interface between the service filtering rule base 410 and the service control unit 430 may be a Diameter protocol or an internal interface protocol; The interface between the service control unit processing device 420 and the service control unit 430 may be a SIP protocol, an intelligent service protocol (such as an Intelligent Network Application Protocol: INAP, an internal interface protocol, etc.).

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

Claims

Claim

A method for processing a service control unit, the method comprising the steps of:

 Performing a service filtering rule to determine the called service control unit and its corresponding subsequent filtering rules;

 During the execution of the service, the current communication is processed according to the determined subsequent filtering rules.

 2. The method according to claim 1, wherein the subsequent filtering rule includes a subsequent triggering condition and a corresponding subsequent processing manner;

 The processing of the current communication is: when the subsequent trigger condition is met, performing a subsequent processing manner corresponding to the subsequent trigger condition.

 The method according to claim 2, wherein the subsequent triggering condition comprises at least one of a subsequent message, a call state, a service control unit call failure, and a service control unit call success;

 The subsequent processing manner includes at least one of sending a message, rejecting a message, invoking a specified service control unit, continuing communication, stopping execution of a service filtering rule, releasing a service control unit, and releasing a communication.

 4. The method according to claim 3, wherein the subsequent message comprises at least one of all messages including a release message after the called service control unit is invoked until the current communication is released. ;

 The call state includes at least one of all process states of the current communication; the service control unit call failure includes at least the called service control unit not responding or the service logic call in the invoked service control unit fails;

Successfully invoking the service control unit includes at least the called service control unit The business logic is called successfully.

 The method according to claim 4, wherein before the performing the service filtering rule, the method further comprises: describing, in the subsequent filtering rule, a timeout waiting time of the call state.

 The method according to claim 4, wherein the service logic call in the called service control unit fails: the called service control unit returns a SIP message indicating that the service logic call failed or carries a service The SIP message indicating the failure of the logic call; the success of the service logic in the called service control unit is: returning a SIP message indicating that the service logic is successfully invoked or a SIP message carrying the success indication of the service logic call

The method according to claim 3, wherein the sending the message in the subsequent processing mode is: sending the specified message.

 8. The method according to claim 7, wherein the specified message is: a message further specifying message source information and/or message destination information;

 Determining, according to the source information, the specified message is a message returned from the called service control unit, a message sent to the called service control unit, and a SIP initial request message invoking the called service control unit. , or a subsequent message in the subsequent trigger condition.

 The method according to claim 3, wherein the reject message in the subsequent processing manner is: prohibiting sending a subsequent message in the subsequent trigger condition.

 10. The method of claim 3, wherein

 The invoking the specified service control unit is: when the subsequent triggering condition is met, sending an invocation message to the specified service control unit or performing a service filtering rule corresponding to the specified service control unit.

11. The method according to claim 3, wherein the subsequent processing manner The communication in the continuation is: If there is a subsequent service filtering rule, the subsequent service filtering rule is continued to be executed; otherwise, the current communication process is continued.

 The method according to claim 3, wherein the stopping the execution of the service filtering rule in the subsequent processing mode is: if there is a subsequent service filtering rule, stopping the execution of the subsequent service filtering rule, and continuing the current communication process.

 The method according to claim 3, wherein the subsequent triggering condition is one of matching conditions of a subsequent service filtering rule, and the subsequent processing mode is to perform communication to the subsequent service filtering rule to continue or stop executing. The subsequent service filtering rule.

 The method according to any one of claims 2 to 13, wherein before the performing the service filtering rule, the method further includes: describing the source service control unit information in the subsequent triggering condition, and/or The source service control unit information and/or the destination service control unit information are described in the subsequent processing manner.

 The method according to any one of claims 2 to 13, wherein before the performing the service filtering rule, the method further includes: describing, in the subsequent triggering condition, at least one of the multiple service control units The service filtering rule identifier corresponding to the control unit.

 The method according to any one of claims 2 to 13, wherein before the performing the service filtering rule, the method further includes: describing, in the subsequent filtering rule, any combination of a plurality of subsequent triggering conditions, and/ Or any combination of multiple subsequent processing methods is described in the subsequent filtering rules.

 The method according to any one of claims 1 to 13, wherein the processing the current communication is to execute a specified service filtering rule;

 The specified service filtering rule is provided with a special identifier indicating that the specified service filtering rule is triggered to be executed only when the corresponding subsequent triggering condition is met.

18. A service control unit processing apparatus, the apparatus comprising: a subsequent filtering rule obtaining module, configured to execute a service filtering rule, and determine a called service control unit and a corresponding subsequent filtering rule;

 The subsequent processing mode execution module is configured to process the current communication according to the subsequent filtering rule during the execution of the service.

 The device according to claim 18, wherein the subsequent filtering rule includes a subsequent triggering condition and a corresponding subsequent processing manner;

 The device further includes a subsequent trigger condition matching module, configured to determine, according to the subsequent trigger condition provided by the subsequent filter rule acquiring module, whether the subsequent trigger condition is satisfied, when the subsequent trigger condition is satisfied. When the method is satisfied, the subsequent processing mode execution module is notified, and the subsequent processing manner provided by the subsequent filtering rule obtaining module is executed.

 A service control unit processing system, comprising: a service control unit processing device, configured to execute a service filtering rule, determine a subsequent filtering rule corresponding to the service control unit, and according to the subsequent filtering rule Processing the current communication;

 The service control unit is configured to provide various service logic control functions according to the processing of the service control unit processing device.

 The system according to claim 20, wherein the apparatus further comprises: a service filtering rule base, configured to save or generate a service filtering rule of the user, and configured to provide the service to the service control unit processing device Filter rules.