WO2012116592A1

WO2012116592A1 - Service triggering method and device

Info

Publication number: WO2012116592A1
Application number: PCT/CN2012/071024
Authority: WO
Inventors: 章璐
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-03-02
Filing date: 2012-02-10
Publication date: 2012-09-07
Also published as: CN102655613A

Abstract

The present invention provides a service triggering method and device. The service triggering method comprises: a serving-call session control function (S-CSCF) receiving a request message, acquiring service information of a user corresponding to the request message; the S-CSCF, according to a triggering rule in the service information, triggering one or more application servers (ASs) and/or triggering, through an IP multimedia service switching function (IM-SSF), one or more service controllers (SCP), so as to execute a service corresponding to the service information. The present invention solves the problem in the art that multiple services cannot be completed because a call cannot trigger multiple SCPs, thereby improving the user experience.

Description

The present invention relates to the field of communications, and in particular to a service triggering method and apparatus. BACKGROUND In a conventional telecommunication network, a Public Switched Telephone Network (PSTN) is used, and a Public Land Mobile Network (PLMN) is used as a Service Control Point (Service Control Point, SCP) is the core public service platform for users to realize telecom value-added services, such as caller prepaid, called party centralized payment, virtual private network and other services. The SCP is responsible for the implementation of the intelligent service logic and is the core of the intelligent service system. It interacts with the Service Switching Point (SSP) through the No.7 signaling network to instruct the SSP to perform call connection; the SSP is responsible for The smart call is monitored and triggered, the request information is sent to the SCP, and the connection is made according to the instructions received from the SCP. In the intelligent service system of the traditional telecommunication network, the calling or called user can only trigger one in one call.

The problem of SCP, which makes the caller or called party unable to complete multiple value-added services in the traditional telecommunication network, has imposed certain restrictions on the development of value-added services. SUMMARY OF THE INVENTION The present invention provides a service triggering method and apparatus to at least solve the above problems. According to an aspect of the present invention, a service triggering method is provided, including: a service call session control function S-CSCF receives a request message, and obtains service information of a user corresponding to the request message; The triggering rule in the service information triggers one or more application servers AS and/or triggers one or more service controllers SCP to perform the service corresponding to the service information via the IP multimedia service switching function IM-SSF. Preferably, the S-CSCF triggering one or more of the ASs according to the triggering rule and/or triggering one or more of the SCPs to perform the service corresponding to the service information by using the IM-SSF includes: The S-CSCF triggers one or more of the ASs in sequence according to the service triggering sequence relationship in the triggering rule, and/or triggers one or more of the SCPs to perform the service via the IM-SSF. Preferably, the S-CSCF acquiring the service information of the user corresponding to the request message includes: the S-CSCF acquiring the service information of the user on the home subscriber server HSS. Preferably, before the S-CSCF obtains the service information of the user on the HSS, the method further includes: setting, by the commercial operation support system BOSS, the service information of the user on the HSS, where The BOSS is used to manage user information of the user and the service information subscribed by the user. Preferably, before the S-CSCF receives the request message, the method further includes: the media gateway control function MGCF sends the request message to the S-CSCF via an interrogation call session control function I-CSCF, where The request message is further used to indicate the type of the service to the S-CSCF, where the type of the service is divided into a calling service and a called service. Preferably, before the MGCF sends the request message to the S-CSCF via the I-CSCF, the method further includes: a call request received by the mobile switching center MSC, sending a service trigger request to the anchor SCP; The anchoring SCP indicates that the MSC routes the call request to the MGCF; the MSC routes the call request to the MGCF, wherein the call request is further used to indicate the type of the service. Preferably, the MSC is instructed to route the call request to the MGCF by a prefix added to the calling number and/or the called number of the call request, and to indicate the type of the service to the MGCF. Preferably, after the S-CSCF triggers one or more of the ASs and/or triggers one or more of the SCPs to perform the service corresponding to the service information, the method further includes: The S-CSCF determines that the service is completed, and sends a request message to the MGCF when determining that the called user of the call corresponding to the request message is a traditional circuit domain user; the MGCF according to the received request The message sends a call request to the gateway mobile switching center GMSC. Preferably, the S-CSCF sends, to the MGCF, a request message carrying indication information, where the indication information is used to suppress secondary anchoring; and the MGCF sends, to the GMSC, the identifier that carries the indication information. a call request; the GMSC learns that the user corresponding to the call request subscribes to the service, and sends a service request message to the anchor SCP, where the service request message carries the indication information; the anchor SCP receives the bearer After the service request message with the indication information, the anchoring operation is not performed, and the GMSC is instructed to send the call request to the corresponding MSC. Preferably, the sending, by the S-CSCF, the request message carrying the indication information to the MGCF includes:

The S-CSCF initiates a request message to the redirecting AS, where the redirecting AS sets the indication information in the request message, and sends the indication information to the S-CSCF; the S-CSCF stops triggering according to the indication information. And sending a request message carrying the indication information to the MGCF. Preferably, the indication information is a prefix that is added to the calling number and/or the called number of the call request. According to another aspect of the present invention, a service triggering apparatus is further provided, which is located in the serving call session control function S-CSCF, and includes: a receiving module, configured to receive a request message; and an obtaining module, configured to obtain the request message corresponding to The service information of the user; the triggering module is configured to trigger one or more application servers AS according to the triggering rule in the service information and/or trigger one or more service controllers SCP via the IP multimedia service switching function IM-SSF Executing the service corresponding to the service information. The invention solves the problem that the multiple services cannot be completed due to the failure to trigger multiple SCPs in one call in the related art, and improves the user experience. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a flowchart of a service triggering method according to an embodiment of the present invention; FIG. 2 is a structural block diagram of a service triggering apparatus according to an embodiment of the present invention; and FIG. 3 is a schematic diagram of a system architecture according to a preferred embodiment of the present invention. 4 is a process flow diagram of a service setup in accordance with a preferred embodiment of the present invention; FIG. 5 is a flowchart of anchoring and service triggering in accordance with a preferred embodiment of the present invention; FIG. 6 is a conventional circuit user in accordance with a preferred embodiment of the present invention. Flowchart for processing two call side service SCPs; FIG. 7 is a flow chart showing the process of signing one called side service SCP and one called side IMS domain AS in a conventional circuit user according to a preferred embodiment of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. In the 3GPP R5 phase, a multimedia subsystem (IP Multimedia Subsystem, IMS for short) is introduced. In the IMS, a service interoperation network based on a trigger rule is proposed, which allows multiple application servers to simultaneously provide services for one user. Since the IMS service is richer than the service in the traditional telecommunication network, in this embodiment It is proposed to enable services in an IMS network to be used by conventional circuit domain users. There are two issues involved: (1) How do calls from traditional circuit domain users are routed to IMS? (2) How do the SCP services in the traditional circuit domain and the services in the IMS network work together for the traditional circuit domain users? For question (1), an anchoring solution is proposed in 3GPP TS 23.292 to route calls from legacy circuit domains to the IMS domain. With regard to the (2) problem, since the related art does not propose a service in which the legacy circuit domain user can use the IMS, there is no solution to the problem (2) in the related art. In the following embodiments, the convergence of the traditional intelligent service and the IMS service in the traditional telecommunication network and the next generation network with the IP multimedia subsystem as the core is proposed. In this embodiment, a service triggering method is provided. FIG. 1 is a flowchart of a service triggering method according to an embodiment of the present invention. As shown in FIG. 1, the process includes the following steps: Step S102, a service call session control function (Serving-CSCF, abbreviated as S-CSCF) receives the request message, and obtains the service information of the user corresponding to the request message. The service information of the user in this step may be the calling user service or the called user service, and may of course be the calling user service and the called user service. Step S104: The S-CSCF triggers one or more application servers (Application Servers, abbreviated as ASs) according to the triggering rules in the service information, and/or an IP Multimedia Service Switching Function (IM-SSF). The one or more SCPs are triggered to perform the service corresponding to the foregoing service information. Through the above steps, the SCP in the traditional circuit domain network and the IM-SSF in the IMS are combined, which effectively solves the defect that the calling or called party cannot trigger multiple SCPs in the traditional telecommunication network. In addition, through the above steps, the traditional telecommunication network user is allowed to use the traditional SCP service, and the service provided by the IMS application server can also be used, which enriches the user service experience and provides a way for the traditional telecommunication service to migrate to the IMS service. . Preferably, in implementation, the service triggering sequence may be set in the triggering rule, and the S-CSCF may trigger one or more ASs and/or trigger through the IM-SSF according to the service triggering sequence relationship in the triggering rule. One or more SCPs perform business. In this way, the user's business execution order can be flexibly configured, thereby further improving the service experience.

The S-CSCF can obtain the service information of the user in a plurality of manners, and the same manner can be achieved by any of the acquisition methods, that is, different acquisition methods do not affect the implementation of the embodiment, and are described below by way of example. For example, the S-CSCF can obtain service information on a Home Subscriber Server (HSS). The method of obtaining service information from the HSS has less modification to the existing IMS network element, and the implementation is relatively easy. More preferably, if there is a business operation support system in the system for managing user information and user-signed business information. In the case of the Business and Operation Support System (BOSS), the business information that the commercial operation support system BOSS sets on the HSS can be obtained before the S-CSCF obtains the service information on the HSS. As described above, the type of service can be divided into a calling service and a called service. In implementation, the Media Gateway Control Function (MGCF) can be used to control the session control function (Interrogating-CSCF, referred to as The I-CSCF indicates the service type to the S-CSCF (for example, a request message, which may carry indication information indicating the type of the service), so that the S-CSCF can distinguish. For example, before the MGCF sends a request message to the S-CSCF via the I-CSCF, the mobile switching center (Mobile Switching Center, referred to as MSC) receives the call request, sends a service trigger request to the anchor SCP, and the anchor SCP indicates that the MSC will The call request is routed to the MGCF, which is also used to indicate the type of service. Preferably, in the implementation, after the S-CSCF determines that the service is completed, the processing may be performed according to the type of the called user. For example, when determining that the called user of the call corresponding to the request message is a traditional circuit domain user, the MGCF may be sent to the MGCF. Sending a request message; The MGCF sends a call request to the gateway mobile switching center GMSC according to the received request message. After that, the GMSC can perform processing in the traditional circuit domain, and details are not described herein again. Of course, in the present embodiment, for some services, a secondary anchoring situation may occur, and a preferred processing method is provided in this embodiment. The request message carrying the indication information may be sent by the S-CSCF to the MGCF, where the indication information is used to suppress the secondary anchoring, and the MGCF sends a call request carrying the indication information to the GMSC; if the GMSC knows that the user corresponding to the call request signs the contract If the service sends a service request message to the anchor SCP, the indication information needs to be carried in the service request message, so that after the anchor SCP receives the service request message carrying the indication information, the anchor operation is not performed. And instructing the GMSC to send the call request to the corresponding MSC. Preferably, the method may be implemented by redirecting the AS. After the S-CSCF performs the service, the S-CSCF sends a request message to the redirecting AS, and the redirecting AS sets the indication information in the request message, and sends the indication information to the S-CSCF. The S-CSCF stops the trigger according to the indication information, and sends a request message carrying the indication information to the MGCF. There may be multiple ways to indicate information, for example, a prefix that may be added to the calling number and/or the called number in the call request. In this embodiment, a service triggering device is also provided, which is located in the S-CSCF, and implements the functions of the S-CSCF in the foregoing embodiment and its preferred embodiments. The module involved in the device is described. 2 is a structural block diagram of a service triggering apparatus according to an embodiment of the present invention. As shown in FIG. 2, the structure includes: a receiving module 22, an obtaining module 24, and a triggering module 26. The structure will be described below. The receiving module 22 is configured to receive the request message; the obtaining module 24 is connected to the receiving module 22, the module is configured to obtain the service information of the user corresponding to the request message; the triggering module 26 is connected to the obtaining module 24, and the module is configured to be The triggering rule in the service information triggers one or more application servers AS and/or triggers one or more service controllers SCP to perform services corresponding to the service information via the IP multimedia service switching function IM-SSF. The above embodiment solves the problem that a single user in a traditional circuit domain cannot trigger multiple SCPs, and the application server and the SCP in the IP multimedia subsystem simultaneously provide services for the user, and provides a traditional circuit domain service to the IMS evolution. The solution enables traditional circuit domain users to enjoy not only the services provided by traditional SCPs, but also the new services provided by the IMS domain, effectively enhancing the service experience of traditional users. A preferred embodiment will be described below by taking a conventional Global System for Mobile Communications (GSM) network as an example. In the preferred embodiment, by setting an anchor SCP in a conventional circuit domain, the circuit domain is The call is routed to the IMS. By signing multiple SCP or AS service information and triggering the sequence relationship on the HSS, the S-CSCF controls the IM-SSF to be triggered multiple times, and then the IM-SSF triggers the real service SCP, thereby implementing a single user trigger. The purpose of multiple service SCPs, as well as the application server and traditional SCP in the IMS domain serve the same user at the same time. 3 is a schematic diagram of a system architecture according to a preferred embodiment of the present invention. As shown in FIG. 3, the system includes:

BOSS301, the network element is responsible for managing user information and service subscription information in the IMS domain and the traditional circuit domain, through Simple Object Access Protocol (SOAP) or Man-Machine Language (MML). The method interacts with network elements such as SCP, AS, Home Location Register (HLR), and HSS to implement user information maintenance. In this embodiment, the function of the network element includes: setting information of anchoring SCP in the HLR; setting user service information in the service SCP; setting a trigger order relationship between the SCP and the AS in the HSS; setting a user in the IMS AS Business information. Anchoring SCP302, the network element performs the business logic of the SCP, and is responsible for redirecting the call of the traditional circuit domain to the IMS domain. Before performing the redirection operation, it is necessary to analyze whether the user has performed the redirection operation, if it has been executed. The redirect operation is no longer performed. In this embodiment, the anchor SCP is used as a specific functional entity, and may be used as an independent device or may be combined with other SCPs. The service SCP 303 is responsible for providing intelligent services for the traditional circuit domain users, and there is no special requirement in this embodiment. The HLR 304 is responsible for mobile user management, storing subscription data of the users under jurisdiction and location information of the mobile users, and providing routing information and the like for the call. In this embodiment, there is no special requirement for the network element.

The MSC 305 is responsible for completing call processing and exchange control, and implementing functions such as paging access, channel allocation, call connection, traffic control, charging, and base station management of mobile users. The network element may also have an SSP function, and send an intelligent service request to the SCP according to the subscription of the primary and the called user, and perform an interaction with the business logic. In this embodiment, the MSC has an SSF function.

MGCF306, the network element is responsible for implementing the interworking between the traditional circuit domain and the IMS domain, including protocol mapping and conversion between the traditional circuit domain and the IMS network, and controlling the media gateway to complete the conversion of the traditional circuit domain and the IMS network user media surface, etc. In this embodiment, the network element initiates the call p as a different role in the IMS domain according to the redirection number information. When the redirection is performed to perform the calling side service, the MGCF carries the calling service identifier in the initiated call. When the purpose of the redirection is to perform the called side service, the MGCF does not carry the calling service identifier in the initiated call.

I-CSCF307, the network element is responsible for allocating the S-CSCF to the IMS user, performing routing, and providing the network topology hiding function. In this embodiment, the network element has no special requirements. The S-CSCF 308 provides the UE with the session control, the registration service, the call authentication, and the service triggering function. In this embodiment, the network element has no special requirements.

AS309 of the IMS service, the network element provides service functions for the traditional circuit domain user and the IMS user. In this embodiment, there is no special requirement for the network element.

The redirection AS 310 of the IMS is a special network element in the embodiment. The network element provides the function of the IMS domain for the request of the user of the traditional circuit domain, and the call request in the IMS is performed by adding a prefix before the called number. Redirect back to the traditional circuit domain. The network element can be set independently or integrated in other IMS service ASs;

IM-SSF311, the network element serves as a special AS, and provides the function of triggering the call request of the IMS domain to the traditional SCP. In this embodiment, there is no special requirement for the network element.

The HSS 312 provides the user and service data management. In this embodiment, the network element has no special requirements. The preferred embodiment is described in three stages: service provisioning, anchoring and service triggering, anchor suppression, and call paging. Phase 1: Business Provisioning When the user subscribes to multiple traditional SCP services or IMS domain services, the following operations can be performed: The BOSS sends the command to the SCP and the IMS AS, and the service information is sent to the application servers of each SCP and IMS domain; the BOSS sends the command to the HLR. The trigger information of the user is associated with the anchor SCP on the HLR; the BOSS sends an instruction to the HSS, and sets a trigger sequence between multiple SCP services or IMS ASs on the HSS. Phase 2: When the anchor and the service trigger the traditional circuit domain terminal to initiate a call, the following operations may be performed: When the MSC receives the call request, it determines that the user has subscribed to the SCP service, and sends a service trigger request to the anchor SCP according to the subscription information; The anchor SCP analyzes the information of the primary and the called user, determines that the service user is triggered for the first time, performs a redirection operation, sets the call destination to the number corresponding to the MGCF, and sends a service message to the MSC; the MSC converts the message according to the message returned by the SCP into Calling the request, and routing the call to the MGCF through the other MSC; the MGCF determines whether the calling service identifier needs to be carried in the initiated IMS domain call request according to the special identifier of the primary and called numbers in the received call request, and the IMS call is performed. The request is sent to the I-CSCF; the I-CSCF queries the HSS, obtains the S-CSCF that provides the service for the user, and forwards the IMS call request to the S-CSCF; the S-CSCF queries the HSS to obtain the service trigger information of the user, according to the contract setting. The order is triggered to trigger the call request to the IM-SSF and the IMS AS to implement specific service logic; after the S-CSCF completes all service triggers, Called the number the call is routed to the MGCF. Phase 3: Anchoring Suppression and Call Paging This phase includes the following steps: The MGCF routes the call to the legacy circuit domain MSC according to the called number; the MSC determines that the SCP service needs to be executed according to the called user information, and sends a service request to the SCP; After the service request, the main and called number information is analyzed, and according to the special information such as the calling number prefix, it is determined that the user performs the anchoring operation, and no redirection operation is performed, and the service message is returned to the MSC; the MSC is based on the called user. The registration information sends a call request to the BSC, and the BSC sends the call to the mobile terminal to complete the call connection operation. Preferably, the redirection operation of the anchor SCP in the foregoing three phases may be implemented in multiple manners, and is not limited to adding a prefix before the called number, and the object is to implement routing of the request in the traditional circuit domain to the MGCF. The MGCF can determine that there are multiple conditions for carrying the calling call identity. It is not limited to the prefix mode. It can use a special called number. The goal is to determine the call by analyzing the primary and called information. Whether to carry the calling call identifier; the IMS application server can adopt multiple methods to suppress the secondary anchoring of the SCP, and is not limited to adding a prefix before the calling number; the IMS application server can route the call to the call in multiple ways. The MGCF is not limited to the method of adding a prefix before the called number. The anchoring SCP can determine the conditions for suppressing anchoring. It is not limited to the judgment based on the prefix of the calling number. The goal is to analyze the master and the peer. The information is called to determine whether the anchoring operation needs to be suppressed; the following description will be made by way of example with reference to the accompanying drawings. 4 is a process flow diagram of a service setting according to a preferred embodiment of the present invention. The flow shown in the figure is a processing flow of a traditional circuit domain user signing two call service SCPs, as shown in FIG. 4, and the process includes the following steps. Step S401: The BOSS sends a service opening instruction to the service SCP1. Step S402, the service SCP1 records the service subscription information of the user, and returns a service activation response to the BOSS. Step S403, the BOSS sends a service opening instruction to the service SCP2. Step S404, the service SCP2 Recording the service subscription information of the user, returning the service activation response to the BOSS; Step S405, the BOSS determines that the user has not signed the anchor SCP, and sends the service opening instruction to the anchor SCP. If the SCP service has been contracted, the opening instruction is not required to be sent; In step S406, the anchor service SCP records the service subscription information of the user, and returns a service activation response to the BOSS. Step S407, the BOSS sends a service activation command to the HLR, where the information triggered by the user's calling service is the anchor SCP; Step S408, HLR Recording the service user call trigger, and anchoring the SCP information, and returning the service activation response to the BOSS; Step S409 The BOSS sends a service provisioning command to the HSS, which includes the service identifiers of SCP1 and SCP2, and the sequence of triggering. Step S410, the HSS records the service trigger information, and returns a service activation response to the BOSS. At this point, the opening operation of the two calling SCP services ends. 5 is a flow chart of anchoring and service triggering according to a preferred embodiment of the present invention. FIG. 5 is a flowchart showing the processing flow of a traditional circuit domain user signing a called service SCP and a called IMS service AS. 5, the process includes the following steps: Step S501, the BOSS sends a service opening instruction to the called service SCP3; Step S502, the called service SCP3 records the service subscription information of the user, and returns a service opening response to the BOSS; Step S503, BOSS determines The user does not sign the anchor SCP, sends the service opening command to the anchor SCP; step S504, anchors the SCP to record the service user called trigger information, and returns the service opening response to the BOSS; Step S505, the BOSS sends a service opening command to the HLR, where the user subscription information is triggered by the called party, and the corresponding SCP is the anchor SCP address; Step S506, the HLR records the user called trigger, and anchors the SCP information, and returns the service opening. Responding to the BOSS; Step S507, the BOSS sends a service provisioning instruction to the IMS service AS; Step S508, the IMS service AS records the user service subscription information, and returns a service provisioning response to the BOSS; Step S509, the BOSS determines that the user has not subscribed to the redirected IMS AS, and sends The service is activated to redirect the IMS to the AS. In step S510, the IMS redirects the AS to record the service subscription information of the user, and returns a service activation response to the BOSS. Step S511, the BOSS sends a service activation command to the HSS, including the service identifier of the called SCP. And the sequence in which the IMS service AS and the IMS redirect AS are triggered by the port L] SCP, where the IMS redirect AS is set as the last trigger; in step S512, the HSS records the service trigger information, and returns the service activation response to the BOSS. At this point, the opening operation of the called service of the traditional circuit domain ends. FIG. 6 is a flowchart of a process for signing two call-side service SCPs by a conventional circuit user according to a preferred embodiment of the present invention. The figure illustrates an example in which a traditional circuit user subscribes to two calling-side service SCPs, and an SCP is used. The CAP protocol, the calling user A is a traditional circuit domain user, and has signed two calling side service SCPs in the traditional circuit domain: SCPa-1 (Virtual Private Mobile Network, VPMN for short) and P SCPa-2 (Call Prepaid) Fee business), and the anchor SCP set automatically; the AS is not signed in the IMS domain. The anchored SCP uses the prefix to route the call to the IMS domain. The prefix code is prefixl, which also serves as the calling service identifier in the IMS domain. The called user B is a traditional circuit domain user, and has not signed up for the SCP service and the IMS service. As shown in FIG. 6, the process includes the following steps: Step S601: The calling MSCa receives the request initiated by the A user, and triggers the calling side service according to the service subscription information 0_CSI of the A user, and sends a service request IDP (Initial DP). Anchoring the SCPa, the request contains the primary and called number information; Step S602, anchoring the SCPa to perform the anchoring operation according to the local service message, adding a prefix prefixl before the called number, and sending a CONNECT message to the MSCa; In step S603, the MSCa performs routing according to the prefix, and sends the call request to the GMSC (Gateway MSC) that can reach the MGCF, and the GMSC forwards the request to the MGCF. Step S604, the MGCF determines, according to the called prefix prefix1, that the calling side of the IMS domain needs to be executed. The service, the prefix of the called number is removed, the identifier orig of the calling call is carried in the route header of the INVITE request, and the request is sent to the I-CSCF; in step S605, the I-CSCF queries the HSS to allocate the S-CSCF to the calling user A, And the INVITE request is forwarded to the S-CSCF; Step S606, the S-CSCF queries the HSS to download the service data of the calling user A, and sends the INVITE request to the IM-SSF according to the service triggering condition; Step S607, the IM-SSF receives After the INVITE request, according to the service identification information in the request, converted into

The CAP message IDP is sent to the SCPa-1, where the primary and the called information are included. Step S608, the SCPa-1 executes the specific service logic, and after the completion, sends the CONNECT message to the IM-SSF. In step S609, the IM-SSF converts the CONNECT message. The INVITE request is sent to the S-CSCF; Step S610, the S-CSCF performs the triggering of the next service SCP according to the triggering rule, and sends the INVITE request to the IM-SSF again; Step S611, after receiving the INVITE request, the IM-SSF receives the request according to the request. The service identification information is converted into a CAP message IDP and sent to the SCPa, where the primary and the called information are included. Step S612, the SCPa-2 executes specific service logic, and sends a CONITNUE message to the IM-SSF after completion; Step S613, IM - SSF converts the CONTINUE message into an INVITE request and sends it to the S-CSCF; Step S614, the S-CSCF determines that the triggering rule is executed, performs route analysis, determines that the called user is a legacy CS user, and sends the request to the MGCF; Step S615, The MGCF performs route analysis according to the called number B, selects the GMSC to which the called user belongs, and sends a call request. At this point, the traditional circuit domain calling service is completed, and then the traditional network GMSC analyzes the called number B, sends a call request to the corresponding MSC, and finally pages to the terminal of the B user. FIG. 7 is a flowchart of processing a traditional circuit user signing a called side service SCP and a called side IMS domain AS according to a preferred embodiment of the present invention, wherein the calling user A is a traditional circuit domain user, and is not contracted. Traditional SCP services and IMS services. The called user B is a traditional circuit domain user. By the service setting method proposed in this embodiment, a called side service SCPb, a called side IMS service ASb, and an automatically set anchor are signed in the traditional circuit domain. The SCP and the IMS redirect the AS, and the service execution order is set to SCPb, IMS ASb, and IMS redirects the AS. The anchored SCP uses the prefix to route the call to the IMS domain. The prefix code is prefix2, which also serves as the called service identifier in the IMS domain. The IMS redirection AS routes the call out of the IMS domain by prefixing the called number. The prefix code is prefix3. The IMS redirects the AS to suppress the two redirects of the anchor SCP by prefixing the calling number. The prefix code is prefi _x 4. In the following implementation steps, the process of interaction between the I-CSCF and the S-CSCF and the HSS is omitted. As shown in FIG. 7, the process includes the following steps: Step S701: The calling MSCa receives a request initiated by the A user, and initiates an SRI (Send Routing Information) query to the HLRb. In step S702, the HLRb returns the service subscription information T_CSI of the B user. Terminating CAMEL Subsription Information) and anchoring the SCP address information; Step S703, MSCa performs the called side service trigger, and sends a service request IDP (Initial DP) to anchor

SCPb, the request contains the primary and called number information; Step S704, the anchoring SCPb performs the anchoring operation according to the local service message, adds the prefix prefix2 before the called number, and sends a CONNECT message to the MSCa; Step S705, the MSCa routes according to the prefix Sending the call request to the GMSC (Gateway MSC, Gateway MSC) of the MGCF, and forwarding the request to the MGCF by the GMSC; Step S706: The MGCF determines, according to the called prefix prefix2, that the IMS domain called side service needs to be performed, and the called party is removed. The prefix of the number, the INVITE request does not carry the calling call identifier, and the request is sent to the I-CSCF; Step S707, the I-CSCF queries the HSS to allocate the S-CSCF to the called user B, and forwards the INVITE request to the S-CSCF. Step S708, the S-CSCF queries the HSS to download the service data of the called user B, and sends an INVITE request to the IM-SSF according to the service triggering condition; Step S709, after receiving the INVITE request, the IM-SSF according to the requested service The identification information is converted into a CAP message IDP and sent to the SCPb, where the primary and the called information are included; Step S710, the SCPb executes specific service logic, and sends a CONITNUE message to the IM-SSF after completion; Step S711, the IM-SSF converts the CONTINUE message into an INVITE request and sends the message to the S-CSCF; Step S712, the S-CSCF performs the execution according to the trigger rule. The triggering of a service AS sends an INVITE request to the IMS ASb. Step S713, the IMS ASb executes specific service logic, and sends an INVITE request to the S-CSCF after completion. Step S714, the S-CSCF executes the next service AS according to the trigger rule. Triggering, sending an INVITE request to the IMS redirecting AS; Step S715, the IMS redirects the AS to execute the service logic, adding a prefix prefi _X 3 before the called number, and adding a prefix prefix4 before the calling number, and then forwarding the INVITE request to the S -CSCF; Step S716, the S-CSCF determines that the called number has changed, stops the triggering of the existing rule, analyzes the new called number, finds that the number is not an IMS user, performs route analysis according to prefi _X 3, and determines that The calling user is a traditional CS user, and sends a request to the MGCF. In step S717, the MGCF performs route analysis and transformation according to the called number prefix, and removes the called number prefix. Select the called user belongs GMSC (Gateway MSC), sends a call request; step S718, the traditional network GMSC queries HLRb known SCP called user B subscribes to services performed

T CSI, sending a CAP service request IDP message to the anchor SCP, wherein the calling information is prefix4+A, the called information is B; Step S719, anchoring the SCP to analyze the calling information, and finding the prefix carrying the suppressed secondary anchor Prefix4, the anchoring operation is not performed, the calling number prefix prefix4 is removed, and the CO NET service message is sent to the GMSC. In step S720, the GMSC analyzes the called number and sends a call request to the corresponding MSC. So far, the traditional circuit domain called service is completed, and then the traditional network MSC analyzes the called number B, and finally pages to the B user's terminal. In another embodiment, software is also provided for performing the technical solutions described in the above embodiments and preferred embodiments.

In another embodiment, a storage medium is provided, the software being stored, including but not limited to: an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like. In summary, with the above embodiment, the problem that a single user cannot trigger multiple SCPs and the nesting of the SCP and the IMS domain AS in the conventional circuit domain is solved. Moreover, the SCP service subscription of the HLR in the traditional circuit domain is simplified, and no matter how many different service SCPs the user has, only the information of anchoring the SCP needs to be signed. In addition, by controlling the service trigger sequence relationship on the HSS, the nesting problem between the traditional SCP and the IMS domain AS is effectively solved, and the original service is provided, and a method for the evolution of the traditional SCP to the IMS is provided. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device so that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, 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. A service triggering method, including:

The service call session control function receives the request message, and obtains the service information of the user corresponding to the request message;

The S-CSCF triggers one or more application servers AS according to a trigger rule in the service information, and/or triggers one or more service controllers SCP to perform the service information corresponding via an IP multimedia service switching function IM-SSF. Business.

2. The method according to claim 1, wherein the S-CSCF triggers one or more of the ASs according to the triggering rule and/or triggers one or more of the SCPs to execute via the IM-SSF The services corresponding to the service information include:

And the S-CSCF triggers one or more of the ASs in sequence according to the service triggering sequence relationship in the triggering rule, and/or triggers one or more of the SCPs to perform the service via the IM-SSF.

The method according to claim 1, wherein the acquiring, by the S-CSCF, the service information of the user corresponding to the request message includes:

The S-CSCF obtains service information of the user on the home subscriber server HSS.

The method according to claim 3, wherein, before the S-CSCF obtains the service information of the user on the HSS, the method further includes:

The business operation support system BOSS sets the service information of the user on the HSS, wherein the BOSS is used to manage the user information of the user and the service information subscribed by the user.

The method according to claim 1, wherein, before the S-CSCF receives the request message, the method further includes:

The media gateway control function MGCF sends the request message to the S-CSCF via an interrogation call session control function I-CSCF, where the request message is further used to indicate the type of the service to the S-CSCF, where The type of service is divided into a calling service and a called service.

The method according to claim 5, wherein, before the MGCF sends the request message to the S-CSCF via the I-CSCF, the method further includes:

The call request received by the mobile switching center MSC sends a service trigger request to the anchor SCP; The anchor SCP instructs the MSC to route the call request to the MGCF;

The MSC routes the call request to the MGCF, wherein the call request is further used to indicate the type of the service.

7. The method according to claim 6, wherein the MSC is instructed to route the call request to the MGCF by a prefix added by a calling number and/or a called number of the call request, and The MGCF indicates the type of the service.

8. The method according to claim 6, wherein the S-CSCF triggers one or more of the ASs and/or triggers one or more of the SCPs to perform corresponding to the service information via the IM-SSF. After the service, the method further includes:

The S-CSCF determines that the service is completed, and sends a request message to the MGCF when determining that the called user of the call corresponding to the request message is a traditional circuit domain user;

The MGCF sends a call request to the gateway mobile switching center GMSC according to the received request message.

9. The method according to claim 8, wherein

Sending, by the S-CSCF, a request message carrying indication information to the MGCF, where the indication information is used to suppress secondary anchoring;

The MGCF sends the call request carrying the indication information to the GMSC; the GMSC learns that the user corresponding to the call request subscribes to the service, and sends a service request message to the anchor SCP, where the service request The message carries the indication information;

After receiving the service request message carrying the indication information, the anchor SCP does not perform an anchor operation, and instructs the GMSC to send the call request to the corresponding MSC.

10. The method according to claim 9, wherein the sending, by the S-CSCF, the request message carrying the indication information to the MGCF includes:

The S-CSCF initiates a request message to the redirecting AS, and the redirecting AS sets the indication information in the request message, and sends the indication information to the S-CSCF;

The S-CSCF stops triggering according to the indication information, and sends a request message carrying the indication information to the MGCF.

The method according to any one of claims 8 to 10, wherein the indication information is a prefix added to a calling number and/or a called number of the call request.

A service triggering device, located in the service call session control function S-CSCF, comprising: a receiving module, configured to receive a request message;

The acquiring module is configured to obtain the service information of the user corresponding to the request message, and the triggering module is configured to trigger one or more application servers AS and/or the IP multimedia service switching function IM according to the triggering rule in the service information. The SSF triggers one or more service controllers SCP to perform the service corresponding to the service information.