WO2009121281A1 - A method for invoking a service in ims network, system and device thereof - Google Patents

Abstract

A method for invoking a service in IMS network, system and device thereof. The method for invoking a service in IMS network includes: a service triggering unit receives the first communication message; the service triggering unit matches with a preset service invoking rule according to the first communication message content; if the match is successful, it generates a service invoking request message which is independent of a session of the first communication message, and it sends the service invoking request message to a service control unit which is described in successfully matched service invoking rule then apprizes to implement a service invoking, so that the invention realizes service invoking according to actual requirement, avoids routing a signal to a needless service control unit, reduces route redundance, shortens the time of call continue, realizes thorough separating between the service invoking and the session control.

Description

 Method, system and device for calling a service in an IMS network, the application is filed on March 29, 2008, the Chinese Patent Office, the application number is 200810066218.1, and the invention is entitled "Method, system and device for calling a service in an IMS network, Priority of the Chinese Patent Application, the entire contents of which is incorporated herein by reference.

Technical field

 The present invention relates to the field of communications technologies, and in particular, to a method, system, and apparatus for service invocation in an IMS network.

Background technique

 The SIP protocol is an application layer control protocol for establishing, changing, and terminating multimedia sessions or calls. These multimedia sessions include multimedia conferencing, distance learning, Internet telephony, etc., and its core is composed of the Internet Engineering Task Force (IETF). Standard organization definition.

 Currently, an IP multimedia subsystem (IMS) system defined by the 3GPP (3rd Generation Partnership Project) standard is a 3G (3rd Generation) mobile network that implements packet voice and packet data. A target network for providing unified multimedia services and applications, which uses an IP packet domain as a bearer channel for its control signaling and media transmission, and uses SIP protocol as call control signaling to implement service management, session control, and bearer connection. The three entered are separated.

 In the IMS network, the application server (Application Server AS) provides value-added multimedia services, and an AS can provide a service for users. Currently, the calling service in the IMS network can be triggered according to the initial filtering rule (iFC).

The initial filtering rules of multiple priorities are included in the iFC. The existing iFC triggering mechanism is to perform iFC matching and matching according to the priority of the user subscription information according to the priority of the user, when the call session control function entity S-CSCF receives the SIP session initial request (such as INVITE) message. After the success, the SIP session initial request message is sent to the corresponding AS, and each AS is added to the SIP session signaling path, so that the service of the AS can be called. Due to the routing mechanism of SIP itself It is determined that subsequent messages cannot be serialized into a new SIP entity. As a result, the current service trigger needs to pre-integrate the ASs that may be applied to the signaling path to ensure the implementation of each service, but the AS is not immediately after the serialization. The service is executed, or some ASs have never called the corresponding service because they do not meet the conditions triggered by the service. In this way, when the S-CSCF performs the iFC trigger, sending the SIP session initial request message to each AS causes routing redundancy, thereby prolonging the call connection time.

Summary of the invention

 The embodiments of the present invention provide a method, a system, and a device for invoking a service in an IMS network, so as to implement a service call according to actual needs, and solve the problem of routing redundancy caused by iFC triggering in the prior art.

 The embodiment of the invention provides a method for calling a service in an IMS network, including:

 The service triggering unit receives the first communication message;

 And the service triggering unit matches the preset service invocation rule according to the content of the first communication message, and after the matching is successful, generates a service invocation request message that is unrelated to the session to which the first communication message belongs, and the service is The call request message is sent to the service control unit described in the successfully matched service invocation rule to perform a service call, where the service invocation rule includes a combination of conditions required for a service call matching the content of the first communication message and an execution corresponding The business control unit of the service describes the information.

 An embodiment of the present invention provides a system for calling a service in an IMS network, where the system includes a service triggering unit and a service control unit.

 The service triggering unit is configured to receive the first communication message, and match the preset service invocation rule according to the content of the first communication message. After the matching is successful, generate a service invocation request message that is not related to the session to which the first communication message belongs. And sending the service call request message to the service control unit described in the matching successful service invocation rule;

The service control unit is configured to receive the service call request message, and perform a service call according to the call request message. The service invocation rule includes a combination of conditions required for a service call that matches the content of the first communication message and a service control unit description information that performs a corresponding service.

 An embodiment of the present invention provides a service triggering unit in an IMS network, including a receiving module, a storage module, a triggering module, and a sending module, where

 a receiving module, configured to receive a first communication message;

 a storage module, configured to store a service invocation rule, where the service invocation rule includes a combination of conditions required for the service invocation and a description of the service control unit that executes the corresponding service;

 a triggering module, configured to match, according to the first communication message received from the receiving module, a service invocation rule stored by the storage module, and after the matching is successful, generate a service invocation request message that is not related to the session to which the first communication message belongs;

 And a sending module, configured to send a service call request message generated by the triggering module to the service control unit described in the service matching rule that is successfully matched.

 The technical solution of the embodiment of the present invention, after receiving the first communication message by the service triggering unit, matching the content of the first communication message with a preset service calling rule, and after the matching is successful, generating the first communication message The session inactivity-free service invocation request message is sent to the service control unit described in the matching successful service invocation rule to perform a service call. Since the service invocation rule includes a combination of conditions required for the service invocation, when the conditional combination is satisfied, the service is invoked. The request message is sent to the corresponding service control unit, thereby ensuring that the service control unit immediately performs the service call after receiving the service call request message, thereby avoiding routing the signaling to the unnecessary service control unit, thereby reducing Routing redundancy reduces the time for call connection. In addition, since the service call request message generated by the service triggering unit is independent of the session to which the first communication message belongs, the service control unit that receives the service call request message is not added to the original SIP session signaling route, and the service call is implemented. Complete separation of session control.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art description will be briefly described below, obviously, the following The drawings in the description are only some of the embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any inventive labor.

 1 is a structural diagram of a service invocation system in an IMS network according to an embodiment of the present invention;

 2 is a schematic structural diagram of a service triggering unit according to an embodiment of the present invention;

 3 is a flowchart of a method for calling a service according to an embodiment of the present invention;

 4 is a schematic flowchart of a specific embodiment of a service invocation method according to the present invention;

 FIG. 5 is a schematic flowchart diagram of another specific embodiment of a service invoking method according to the present invention;

 FIG. 6 is a schematic flowchart diagram of another specific embodiment of a service invocation method according to the present invention.

detailed description

 The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

 As shown in FIG. 1 , it is an architecture diagram of a service invoking system in an IMS network according to an embodiment of the present invention. The service invoking system includes a service triggering unit 11 and a service control unit 13, and the service triggering unit 11 and the service control unit 13 pass through an E1 interface. connection.

 The service triggering unit 11 is configured to receive the first communication message, and match the preset service invocation rule according to the content of the first communication message. After the matching is successful, generate a service invocation request that is not related to the session to which the first communication message belongs. a message, and the service call request message is sent to the service control unit 13 described in the matching successful call rule;

 The service control unit 13 is configured to receive the service call request message, and perform a service call according to the service call request message to provide a logical control function of the service, which is a host execution environment of various services.

The service invocation rule includes a combination of conditions required for a service call that matches the content of the first communication message and a service control unit description information that performs a corresponding service. In the system, the first communication message received by the service triggering unit 11 may be a SIP message, and may be a request message, such as an initial session request INVITE message, or a response message, such as various SIP response messages, such as 200, 486, etc. When the SIP message is a request message, the first communication message content may include one or any combination of the following: a request URI, a request method, a message header field, a message body content; when the SIP message is a response message The content of the first communication message includes one or any combination of the following: a message header field, a message body content, and a status code.

 The preset service invocation rules may be stored in the service triggering unit or stored in a separate storage entity, and the service triggering unit 11 obtains from the storage entity when needed. The service invocation rule may be configured by the operator, the user, or both, and may be dynamically updated. The service invocation rule may be generally composed of a service triggering rule and a corresponding service control unit description information, where the service triggering rule description A combination of conditions required for a service call matching the content of the first communication message, the condition combination defining a condition that the service call must satisfy, and taking the busy forwarding service as an example, the condition combination of the service call may be Received a 486 busy response message. The service triggering unit may invoke the corresponding service control unit to perform a service call only when the received first communication message content matches the condition combination described in the service triggering rule. When the condition is empty, the service triggering unit may invoke the service unconditionally.

The service triggering unit 11 matches the received content of the first communication message with the service triggering rule. If the matching is successful, the service triggering request may be generated according to the received content of the first communication message and the corresponding service control unit description information, and the service control is performed. The unit description information includes the address information of the service control unit, and the service triggering unit 11 may send the generated service call request to the corresponding service control unit 13 according to the address information therein. Further, the service control unit description information may further include The service identification information, the service identification information may be used to distinguish the case where the multiple service is available on the single service control unit 13, and the service triggering unit 11 may carry the service identification information in the generated service call request. The service invocation rule may further include a service invocation request type information, and is used to instruct the service triggering unit 11 to generate a corresponding type of service invoking request, and the specific type may include a SIP message type and The HTTP message type, when it is an HTTP message type, may be specifically a SOAP request message, and the service call request generated by the service triggering unit 11 is a SOAP service call request message.

 When the service call request generated by the service triggering unit 11 is a SIP message type, the service call request of the SIP message type has a different session identifier than the received first communication message, that is, the two SIP sessions are independent of each other, when the service trigger unit When the generated service call request is of the HTTP message type, the request belongs to a new HTTP transaction, and is also independent of the session to which the first communication message belongs.

 The E1 interface between the service triggering unit 11 and the service control unit 13 may be a SIP protocol interface, and the E1 interface may be a direct interface or an indirect interface. The indirect interface refers to other interfaces between the service triggering unit 11 and the service control unit 13. Intermediate node.

 In an actual application, the service triggering unit 11 may be located in a network element such as a call session control function entity S-CSCF, a service agent Service Broker, etc., and the service control unit 13 may be a unit that provides telecommunication services, such as an application server AS in an IMS network. It can also be a unit that provides Web services, such as a WEB server, which is a server that uses a standard Web protocol (such as HTTP) interface, and can be located in the Internet (Internet) or Intranet (Local Area Network).

 The service triggering unit 11 can further refer to the description of the following embodiments.

The service invoking system in the IMS network, after receiving the first communication message by the service triggering unit, matches the content of the first communication message with a preset service calling rule, and after the matching is successful, generating the first The session-independent service call request message of the communication message is sent to the service control unit described in the successfully matched service call rule to perform a service call. Since the service call rule includes a combination of conditions required for the service call, when the condition combination is met, The service call request message is sent to the corresponding service control unit, thereby ensuring that the service control unit immediately performs the service call after receiving the service call request message, thereby avoiding routing the signaling to the unnecessary service control unit. , reducing routing redundancy and shortening call connection time. In addition, since the service call request message generated by the service triggering unit is independent of the session to which the first communication message belongs, the service control unit that receives the service call request message is not added to the original SIP session signaling route, and the service call is implemented. Complete separation of session control. As shown in FIG. 2, it is a schematic structural diagram of a service triggering unit in an IMS network according to an embodiment of the present invention. The service triggering unit is applicable to the service calling system in the foregoing embodiment, where the service triggering unit may include a receiving module 21, a storage module 23, The triggering module 25 and the sending module 27, wherein the receiving module 21 is configured to receive the first communication message, where the first communication message may be a SIP message, and may be a request message, such as an initial session request INVITE message, or a response message, such as various SIP response messages, such as 200, 486, etc.;

 The storage module 23 is configured to store a service invocation rule, where the service invocation rule may include a combination of conditions required for the service invocation (ie, a service triggering rule) and a service control unit description information of the corresponding service, where the service invocation rule may be specifically determined by the operator. The user, or both, can be set up dynamically or dynamically. The service triggering rule describes a combination of conditions required for a service call matching the content of the communication message, the condition combination defines a condition that the service call must satisfy, and the service control unit description information includes the address information of the service control unit. Further, The service control unit description information may further include service identification information, where the service identification information may be used to distinguish between a plurality of services on a single service control unit, and the service invocation rule may further include a service call request type information, which is used to indicate corresponding generation. A type of service call request, the specific type may include a SIP message type and an HTTP message type. When it is an HTTP message type, it may be specifically a SOAP request message.

 The triggering module 25 is configured to match the content of the first communication message received from the receiving module 21 with the service calling rule stored by the storage module 23, and after the matching is successful, generate a service calling request that is not related to the session to which the first communication message belongs. The message, when the first communication message is a SIP message, and the SIP message is a request message, the first communication message content may include one or any combination of the following: a request URI, a request method, a message header field, a message body Content: When the SIP message is a response message, the first communication message content includes one or any combination of the following: a message header field, a message body content, and a status code.

The triggering module 25 may generate a service call request according to the content of the first communication message received by the receiving module 21 and the service control unit description information in the successfully matched service calling rule; When the service invocation request generated by the triggering module 25 is a SIP message type, the service invoking request of the SIP message type has a different session identifier from the received first communication message, that is, the two SIP sessions are independent of each other, and the triggering module 25 generates When the service call request is of the HTTP message type, the request belongs to the new HTTP transaction and is also independent of the session to which the first communication message belongs.

 The sending module 27 is configured to send the service call request message generated by the triggering module 25 to the service control unit described in the successfully matched service invocation rule.

 Further, the triggering module 25 may further include a matching submodule 252 and a service invoking request message generating submodule 254, where

 The matching sub-module 252 is configured to match the content of the first communication message received from the receiving module 21 with the service calling rule stored by the storage module 23, and notify the service calling request message generating sub-module 254 of the matching result;

 The service call request message generation sub-module 254 is configured to generate, when the matching sub-module 252 matches successfully, a service call request message that is unrelated to the session to which the first communication message belongs.

 Further, the triggering module 25 may further include a message type determining sub-module 256, configured to determine a service call request message type according to the service call request type information described in the successfully matched service invocation rule, after the matching sub-module 252 is successfully matched. And outputting to the service call request message generation sub-module 254, the service call request message generation sub-module 254 generates a corresponding service call request message according to the service call request message type, and the specific type may include a SIP message type and an HTTP message type. When it is an HTTP message type, it can be specifically a SOAP request message.

 Further, the triggering module 25 may further include a service identifier obtaining sub-module 258, configured to obtain a service identifier according to the service identification information in the service invocation rule that is successfully matched, and output the service identifier to the service after the matching sub-module 252 is successfully matched. The call request message generation sub-module 254, the service call request message generation sub-module 254 carries the service identifier in the generated service call request message.

Further, the service invocation request message generating sub-module 254 may further include a mapping encapsulation processing sub-module 2542, configured to perform mapping or encapsulation processing between the SIP message and the HTTP message, specifically, when the message type determining sub-module 256 determines When the message type is an HTTP message type, the service The call request message generation sub-module 254 can encapsulate or map the first communication message content into a SOAP service call request message.

 In an actual application, the service triggering unit may be a call session control function entity S-CSCF or a service agent Service Broker.

 The service triggering unit in the IMS network, after receiving the first communication message, matches the content of the first communication message with a preset service calling rule, and after the matching is successful, generates a message with the first communication message. The session-independent service invocation request message is sent to the service control unit described in the matching successful service invocation rule to perform a service invocation. Since the service invocation rule includes a combination of conditions required for the service invocation, when the conditional combination is satisfied, the service invocation request is performed. The message is sent to the corresponding service control unit, so that the service control unit immediately performs the service call after receiving the service call request message, thereby avoiding routing the signaling to the unnecessary service control unit, thereby reducing the number of Route redundancy reduces the time for call connection. In addition, since the service call request message generated by the service triggering unit is independent of the session to which the first communication message belongs, the service control unit that receives the service call request message is not added to the original SIP session signaling route, and the service call is implemented. Complete separation of session control.

 Further, in this embodiment, the service triggering unit may further generate a service invocation request message including the service identification information according to the service identification information in the service invocation rule, so that the service control unit may perform a service call according to the service identification information. Thereby, the call of executing multiple services in the same service control unit can be realized.

 As shown in FIG. 3, it is a flowchart of a service invocation method in an IMS network according to an embodiment of the present invention, where the method includes:

 301. The service triggering unit receives the first communication message.

 The first communication message received by the service triggering unit in the 301 may be a SIP message, and may be an initial session request INVITE message, or various SIP response messages, such as 200, 486, and the like.

303. The service triggering unit matches the preset service invocation rule according to the content of the first communication message, and after the matching is successful, generating a session that is independent of the session to which the first communication message belongs. The service invokes the request message, and sends the service call request message to the service control unit described in the successfully matched service call rule to perform a service call, where the service call rule includes matching with the content of the first communication message. The combination of conditions required for the service call and the description of the service control unit that executes the corresponding service.

 The pre-set service invocation rule may be stored in the service triggering unit or stored in an independent storage entity, and the service triggering unit obtains the storage entity from the storage entity when needed. The service invocation rules may be specifically set by the operator, the user, or both, or may be dynamically updated. The service invocation rule may be generally composed of a service triggering rule and a corresponding service control unit description information, where the service triggering rule describes a combination of conditions required for a service call matching the content of the first communication message, and the condition combination defines The condition that must be met by the service call is taken as an example of the busy forwarding service, and the condition combination of the service call may be the received 486 busy response message. Only when the received first communication message content matches the condition combination described in the service triggering rule, the corresponding service control unit is invoked to perform a service call. When the condition is empty, the service triggering unit can call the service unconditionally.

 303, the service triggering unit may generate a service call request according to the received first communication message content and the corresponding service control unit description information, and send the service call request message to the service control described in the service success matching rule. The unit makes a business call.

 The service control unit description information may include address information of the service control unit, and the service triggering unit may send the service call request message to the service control unit according to the address information of the service control unit.

The service control unit description information may further include service identification information, where the service call request message generated by the service triggering unit may further include the service identification information, where the service control unit receives the service call request message. Then, the corresponding service is invoked according to the service identification information, and the service identification information is mainly used to distinguish the situation in which multiple services are owned by the single service control unit. In addition, the service invocation rule may further include a service call request type information, and the service triggering unit may further generate a corresponding service call request message according to the service call request type information, and the specific type may include a SIP message type and HTTP. The message type, when it is an HTTP message type, can be specifically a SOAP request message.

 When the service invocation request generated by the service triggering unit is a SIP message, the service invoking request has a different session identifier from the first communication message.

 When the service call request generated by the service triggering unit is an HTTP message, the HTTP request belongs to a new HTTP transaction, and is not related to the session to which the first communication message belongs. In this case, the service call request may be a SOAP service call request message.

 When the service call request generated by the service triggering unit is an HTTP message, the service triggering unit may generate the service call request as follows:

 The service triggering unit encapsulates or maps the received content of the first communication message into a SOAP service call request message.

 The first communication message content for matching, when the SIP message is a request message, the first communication message content may include one or any combination of the following: a request URI, a request method, a message header field, a message body Content: When the SIP message is a response message, the first communication message content includes one or any combination of the following: a message header field, a message body content, and a status code.

 When the service call request generated by the service triggering unit is a SIP message, in order to implement the separation of the service call and the session control, the embodiment of the present invention may extend a SIP message for performing a service call, such as the INVOKE method, where the method only represents one. A call request, which is independent of the original session, has a session identifier different from the original session, and the original session is the session to which the first communication request message belongs.

 Specifically, the process that the service triggering unit generates the INVOKE service call request may include: the service triggering unit replaces the method name of the received SIP message (the first communication request message) with the INVOKE, and the original SIP message method name is placed in the service call request. Other locations, such as the Request-URI, for example, the Request-Line example of the received SIP message is as follows:

INVITE sip:bob@biloxi.com SIP/2.0 The Request-Line example of the generated INVOKE service call request is as follows:

 INVOKE sip:bob@biloxi.com SIP/2.0; method=INVITE

 Alternatively, the process of generating the INVOKE service call request may be: changing the original SIP message method name, and placing the INVOKE method name in another location of the service call request, such as the Request-URI, still using the SIP message received above. The Request-Line example, the Request-Line example of the generated INVOKE service call request is as follows:

 INVITE message sip:bob@biloxi.com SIP/2.0; method=INVOKE In 303, the manner in which the service triggering unit generates a service call request may include: a default mode, or a service call request type in a service call rule that matches a successful match The information in the default mode is that the service call request of the HTTP type or the SIP type is always generated. The service call request type information according to the service matching rule that matches the successful service refers to the service call request generated depending on the successful service call. The service in the rule invokes the request type information, such as the type information describing the service call request for generating SOAP or INVOKE.

 305. The service control unit receives the service call request, performs a service call, and returns a service call response.

 In this step, if the service control unit receives an HTTP type service call request, such as a SOAP service call request, the returned service call response is also an HTTP type service call response, such as a SOAP service call response, and the response includes the encapsulated Or the mapped SIP message content; or, if the service control unit receives a SIP type service call request, such as an INVOKE service call request, the returned service call response is also a SIP type service call response, such as an INVOKE service call response. Specifically, the INVOKE service call response may be a SIP method, such as INVOKE-RSP, or a SIP response code.

The technical solution of the embodiment of the present invention, after receiving the first communication message by the service triggering unit, matching the content of the first communication message with a preset service calling rule, and after the matching is successful, generating the first communication message The session inactivity-free service call request message is sent to the service control unit described in the matching successful service invocation rule to perform a service call, because the service invocation rule The combination of conditions required for the service call is included, and when the condition combination is met, the service call request message is sent to the corresponding service control unit, thereby ensuring that the service control unit immediately after receiving the service call request message The service is invoked, thereby avoiding routing signaling to unnecessary service control units, reducing routing redundancy and shortening call connection time. In addition, since the service call request message generated by the service triggering unit is independent of the session to which the first communication message belongs, the service control unit that receives the service call request message is not added to the SIP session signaling route, and the service call and session are implemented. The complete separation of the control is performed by sending the service invocation request message to the WEB server through the HTTP bearer, thereby introducing the WEB resource into the IMS network, further realizing the fusion of the IMS network and the WEB network.

 Specific embodiments in which the above method is applied are given below.

 As shown in FIG. 4, it is a schematic flowchart of a specific embodiment of the service invocation method of the present invention. In this embodiment, the S-CSCF is a service triggering unit, and the busy forwarding AS is a service control unit. The called party signed a contract and forwarded the business. When the called party was busy, the incoming call was forwarded. The specific process of the method is as follows:

 Step 1-4) The calling UE-A calls the UE-B, after the media negotiation and the resource reservation is completed, ringing; Step 5) the called UE-B is busy, responding to the 486 busy indication message;

 Step 6-8) The S-CSCF matches the service invocation rule according to the received 486 message, generates a service invocation request independent of the original session, and sends the service invocation request to the service control unit in the successfully matched service invocation rule, as in this example. In the busy forward AS, the 486 response is forwarded to the calling UE-A;

 The above service invocation rules include service triggering rules and service control unit description information. Examples of the fragments are as follows:

 <ServiceFilterCriteria>

 <TriggerPoint>

 <SPT>

 <Response>486 </ Response >

 </SPT>

 </TriggerPoint>

<ApplicationServer> < S erverName>http: //ims . example . com</ ServerName >

 </ApplicationServer>

 </ServiceFilterCriteria>

 The TriggerPoint describes that the service triggering rule of the embodiment triggers the service when the service triggering unit receives the 486 response message; the ApplicationServer describes the service control unit description information, where the service control unit description information includes the address information of the service control unit. Further, the ApplicationServer may further include the called service identification information, such as 000 for busy service, and examples are as follows:

 <ApplicationServer>

 < S erverName>htt : //ims . example . com</ ServerName >

 <ServiceId>000</ Serviceld>

 </ApplicationServer> ,

 Where Serviceld describes the service identifier of the called call as 000;

 Further, the service invocation rule may further include a service invocation request type information, and the business call request type sub-element is included in the service call rule element, and the fragment example is as follows:

 <ServiceFilterCriteria>

 <TriggerPoint> ... </TriggerPoint>

 <ApplicationServer> ... </ApplicationServer>

 <Method> HTTP</ Method>

 </ServiceFilterCriteria>

 In the above example, the method is the service call request type information, and the service call request type is an HTTP message type, and the service call request generated by the service control unit is a service call request carried by the HTTP message, such as a SOAP request, if the method value is SIP, the service control unit generates a SIP-based service call request, such as an extended SIP message for performing a service call in the embodiment of the present invention: the INVOKE method. When the service invocation rule does not include the service invocation request type information, the service control unit may generate the service invocation request in a default manner.

Step 9) The busy AS forwards the service call request and returns a response; If the AS accepts the request, it returns a successful response, such as 200 OK in this embodiment; if the service is refused, a failure response is returned.

 Step 10-11) Busy Forward AS performs the corresponding service logic according to the service call request, and generates a Refer request.

 Among them, Referi Qing asks the Refer-To header field to carry the forwarded number registered by the called party.

 Step 12-13) The caller accepts the Refer request and issues an INVITE request based on the URI in the Refer-To header field.

 In the above steps, when the S-CSCF receives the INVITE request, the 180 response and the 200 OK (HTTP) of the service call request, the S-CSCF also performs the matching of the service calling rule, but the matching is unsuccessful and there is no service to be called, so there is no Generate any business call requests.

 In this embodiment, only the busy forwarding service is taken as an example. Step 11 is the execution result of the busy forwarding AS service logic, and may not be a Refer request for other services, which is related to a specific service, and is determined by the AS itself logic.

 Obviously, in this embodiment, the busy forwarding AS is not serialized in the initial INVITE request, but the service call request is sent to the busy forwarding AS when the service execution condition is met, and the service calling process is independent of the session control. After the service control unit receives the service call request message, the service call is immediately performed, thereby avoiding routing the signaling to unnecessary service control units, reducing routing redundancy, and shortening the call connection time. In addition, since the service call request message generated by the service triggering unit is independent of the original session, the service control unit that receives the service call request message is not added to the original SIP session signaling route, and the service call and session control are completely implemented. Separation.

 As shown in FIG. 5, it is a schematic flowchart of another specific embodiment of the service invocation method of the present invention. In this embodiment, the S-CSCF is a service triggering unit, and the missed call prompting AS is a service control unit. The called party signs the missed call alert service. When the called party cannot answer the call due to shutdown, busy or no network coverage, the missed call prompts the AS to send the missed call information to the called user by means of a short message. , remind the user of the missed call. The specific process of this method is as follows:

Step 1-4) The calling UE-A calls the UE-B, and rings after the media negotiation and the resource reservation are completed; Step 5) The called UE-B is busy, and responds to the 486 busy indication message;

 Step 6-8: The S-CSCF matches the service invocation rule according to the received 486 message, generates a service invocation request independent of the original session, and sends the service invocation request to the service control unit in the successfully matched service invocation rule, as in this implementation. The missed call in the example prompts the AS, and forwards the 486 response to the calling UE-A;

 The above service invocation request may be an HTTP SOAP request or an extended new SIP method request, and the service invocation request includes information required for service execution, such as a calling identity and a calling time.

 Step 9) Missing call prompt The AS receives the service call request and returns a response;

 If the AS accepts the request, it returns a successful response, such as 200 OK in this embodiment; if the service is refused, a failure response is returned.

 Step 10-12) The missed call prompts the AS to execute the corresponding service logic according to the service call request, generate a Message message and send it to the called UE-B, prompting the UE-B to miss the incoming call information, such as: "136XXXXXXXX at 10/ 01/2008 16:15 Give you a call once".

 In this embodiment, the missed call of the called party indicates that the AS does not enter the signaling path when the INVITE request is performed, but invokes the service AS when the trigger condition (such as busy) of the missed call service is satisfied. After the service control unit receives the service call request message, the service call is immediately performed, thereby avoiding routing the signaling to unnecessary service control units, reducing routing redundancy, and shortening the call connection time. The missed call indicates that the service call does not affect the original session, and the original session continues. The missed call prompts the AS to send the request to the called party to miss the call prompt message after receiving the corresponding logic, and receives the service control request message. The unit will not be added to the SIP session signaling route, which completely separates the service call from the session control.

 As shown in FIG. 6 , it is a schematic flowchart of another specific embodiment of the service invocation method of the present invention. In this embodiment, the S-CSCF is a service triggering unit, and the AoC AS is a service control unit. The calling user UE-A subscribes to the AoC service. When the UE-A makes a call, the AoC AS notifies the user of the rate, balance and other cost information of the current communication. The specific process of this method is as follows:

Step 1) The calling UE-A issues an INVITE request; Step 2-4: The S-CSCF matches the service invocation rule according to the received INVITE request, generates a service invocation request independent of the original session, and sends the service invocation request to the service control unit in the successfully matched service invocation rule, as in this example. AoC AS in , and forward the INVITE request to the called party;

 Step 5) The AoC AS receives the service call request and responds;

 Step 6-8) The AoC AS executes the corresponding service logic according to the service call request, and generates an INFO message carrying the fee information and returns it to the UE-A;

 Step 9-10) The calling UE-A responds after receiving the INFO message;

 Step 11-12) The call is established, and the called UE-B responds to the INVITE request of the calling UE-A.

 In this embodiment, the AoC service is invoked and executed when the S-CSCF receives the INVITE request, and the service calling process is independent of the original session, where steps 7, 8, 9, and 10 may occur during the original session establishment process or after the original session ends. That is, there is no time limit between steps 7, 8, 9, 10 and steps 11, 12.

 In this embodiment, the S-CSCF matches the service invocation rule according to the received INVITE request, generates a service invocation request independent of the original session, implements the AoC service call, and does not serialize the AoC AS into the original session. In the path, routing redundancy is reduced and call connection time is reduced. The call of the AoC service does not affect the original session. The original session continues. After the corresponding logic is executed, the AoC AS generates an INFO message carrying the fee information and returns it to the UE-A, thereby completely separating the service call from the session control.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. the way. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a readable storage medium, such as a floppy disk of a computer. A hard disk or optical disk or the like includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention. A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. In execution, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

 In summary, the above description is only a preferred embodiment of the technical solution of the present invention, and is not intended to limit the scope of the present invention. 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

 1. An IP multimedia subsystem A method for calling a service in an IMS network, characterized in that the method comprises:

 The service triggering unit receives the first communication message;

 The service triggering unit matches the preset service invocation rule according to the content of the first communication message, generates a service invocation request message that is unrelated to the session to which the first communication message belongs, and sends the service invocation request message The service control unit described in the matching service invocation rule performs a service call, where the service invocation rule includes a combination of conditions required for a service call matching the content of the first communication message and a service control for executing the corresponding service Unit description information.

 The method for invoking a service according to claim 1, wherein the service triggering unit sends the service call request message to the service control unit:

 The service control unit description information includes address information of the service control unit, and the service triggering unit sends the service call request message to the service control unit according to the address information of the service control unit.

 The method for calling a service according to claim 1, wherein the service control unit description information further includes service identification information, and the service triggering unit generates a service call request message including the service identification information, After being sent to the service control unit, the service control unit, after receiving the service call request message, invokes the corresponding service according to the service identification information.

 The method for invoking a service according to claim 1, wherein the service invocation rule further includes service invocation request type information, and the service triggering unit generates a corresponding service invocation according to the service invocation request type information. Request message.

 The method for calling a service according to claim 4, wherein the service call request type information comprises a hypertext transfer protocol HTTP message type or a session initiation protocol SIP message type.

 The method for calling a service according to any one of claims 1 to 5, wherein, when the service call request message generated by the service triggering unit is a SIP message, the service call request message and the first Communication messages have different session IDs.

7. A method of calling a service according to any of claims 1 to 5, characterized in that When the service call request message generated by the service triggering unit is an HTTP message, the service call request message is a simple object access protocol SOAP service call request message carried by the HTTP message, and the service triggering unit generates the service call request message, which specifically includes :

 The service triggering unit encapsulates or maps the received content of the first communication message into a SOAP service call request message.

 The method for calling a service according to any one of claims 1 to 5, wherein the first communication message comprises a SIP message, and when the SIP message is a request message, the first communication message The content includes one or any combination of the following: a request URI, a request method, a message header field, and a message body content; when the SIP message is a response message, the first communication message content includes one or any combination of the following: Domain, message body content, status code.

 9. A service invocation system in an IMS network, characterized in that the system comprises a service triggering unit and a service control unit,

 The service triggering unit is configured to receive the first communication message, and match the preset service invocation rule according to the content of the first communication message. After the matching is successful, generate a service invocation request message that is unrelated to the session to which the first communication message belongs. And sending the service call request message to the service control unit described in the matching successful service invocation rule;

 The service control unit is configured to receive the service call request message, and perform a service call according to the service call request message;

 The service invocation rule includes a combination of conditions required for a service call matching the content of the first communication message and a service control unit description information for executing the corresponding service.

 The service invoking system according to claim 9, wherein the service triggering unit is located in a call session control function entity S-CSCF or a service agent Service Broker, and the service control unit is located in an application server AS or a WEB server. in.

 A service triggering unit in an IMS network, comprising: a receiving module, a storage module, a triggering module, and a sending module, wherein

a receiving module, configured to receive a first communication message; a storage module, configured to store a service invocation rule, where the service invocation rule includes a combination of conditions required for the service invocation and a description of the service control unit that executes the corresponding service;

 And a triggering module, configured to match, according to the first communication message received from the receiving module, a service invocation rule stored by the storage module, and after the matching succeeds, generate a service invocation request message that is not related to the session to which the first communication message belongs;

 And a sending module, configured to send, by the service control unit described in the successfully matched service invocation rule, the service invocation request message generated by the triggering module.

 The service triggering unit of claim 11, wherein the triggering module further comprises a matching submodule and a service invocation request message generating submodule,

 a matching submodule, configured to match, according to the first communication message content received from the receiving module, a service invocation rule stored by the storage module, and notify the service invocation request message generating submodule of the matching result; the service invoking request message generating submodule, And configured to generate, when the matching submodule matches successfully, a service call request message that is not related to the session to which the first communication message belongs.

 The service triggering unit according to claim 12, wherein the triggering module further comprises a message type determining sub-module, configured to: after the matching sub-module is successfully matched, according to a service call in a service matching rule that is successfully matched The request message type information determines a service call request message type, and outputs the message to the service call request message generation sub-module, and the service call request message generation sub-module generates a corresponding service call request message according to the service call request message type.

 The service triggering unit according to claim 12 or 13, wherein the triggering module further comprises a service identifier obtaining submodule, configured to: after the matching submodule is successfully matched, according to the service matching rule in the matching success The service identifier information obtains the service identifier, and is output to the service call request message generation sub-module, where the service call request message generation sub-module carries the service identifier in the generated service call request message.

The service triggering unit according to claim 12 or 13, wherein the service invocation request message generating submodule further comprises a mapping encapsulation processing submodule, configured to perform mapping or encapsulation between the SIP message and the HTTP message. deal with.

The service triggering unit according to claim 12, wherein the service triggering unit is located in a call session control function entity S-CSCF or a service agent Service Broker.