Call connection method of relation call between networks and service broker system

Inter-network associated call connection method, service agent system

This application claims priority to Chinese Patent Application No. 200910140405.4, entitled "Inter-network Association Call Connection Method, Service Agent System", filed on May 6, 2009, the entire contents of which are incorporated by reference. In this application.

Technical field

The present invention relates to the field of communications, and in particular, to an inter-network associated call connection method and a service agent system.

Background technique

As a next-generation telecommunication network architecture, IMS (IP Multimedia Subsystem) is a multi-service application architecture. In the case of multi-service applications, it is inevitable that synergy and consistency between multiple services will occur. 3GPP (3rd Generation Partnership Project) introduces a new network element (SCIM) (Service Capability Interaction Manager service) in the IMS system in order to effectively control and handle the problem of service interaction in IMS. Interaction management) is responsible for coordinating business operations, namely Service Broker platform (business agent platform), in which the business agent platform is set up with a business agent system, which is responsible for processing related business in the business agent platform. The Service Broker platform addresses multi-business interactions and potential conflicts.

Service Broker is an important business platform of NGIN (Next General Intelligent Network), which provides services such as service configuration, service interaction, service composition, service bundling, and resolution of service feature conflicts. The provisioning model has brought about revolutionary changes. It can quickly combine services, shorten the service delivery cycle, and enrich the user's business experience. This makes the Service Broker business platform have broad market application prospects.

In the process of implementing the present invention, the inventor has found that at least the following problems exist in the prior art, the Service Broker platform cannot support the connection of multiple network-triggered associated calls, where multiple networks include multiple networks of the same type, including multiple Different types of networks, such as the Service Broker platform, cannot support the case where the calling and called parties are respectively two broadband network users, nor can the support party and the called party be broadband network users, and the other party is a narrowband network user. That is, the calling and called as the associated call triggered by multiple networks, the further promotion and application of Service Broker technology is greatly limited.

Summary of the invention

The embodiment of the invention provides an inter-network association call connection method and a service agent system, so as to solve the problem that the Service Broker platform cannot support the connection of multiple network-triggered associated calls.

In one aspect, an inter-network association call connection method is provided, where a service data unit is set in a service proxy system, where the method includes:

The first service execution system, when receiving the first call from the first network, stores feature information of the first call in the service data unit, and generates a routing signal, according to the route Transmitting a signal to the second network to trigger a second call on the second network; the first service execution system receiving the second service execution system according to the feature information of the first call stored by the service data unit a second call and subsequent processing of the first call and the second call.

In another aspect, a service agent system is provided, including a service data unit, and a first service execution system:

The first service execution system is configured to: when receiving the first call from the first network, store feature information of the first call in the service data unit; and generate a routing signal, the first The call is routed to the second network according to the routing signal to trigger a second call on the second network; and the received second service execution system is transferred according to the feature information of the first call stored by the service data unit. a second call, and processing the first call and the second call; the service data unit is configured to store feature information of the first call.

In still another aspect, a service agent system is provided, including a service data unit, and a second service execution system;

The service data unit is configured to store feature information of the first call from the first network, and the second service execution system is configured to: when receiving the second call from the second network, according to the service data unit Storing the feature information of the first call, transferring the second call to the first service execution system; the feature information of the first call is received by the first service execution system from the first network When a call is made, it is stored in the service data unit. The inter-network associated call connection method and the service agent system provided by the embodiments of the present invention provide service data units in a service agent system (ie, Service Broker platform), and according to feature information stored in the service data unit, The associated call is transferred to a service execution system for connection processing, thereby implementing the support of the Service Broker platform for the associated call triggered by multiple networks, which is more conducive to the further promotion and application of Service Broker technology. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings to be used in the embodiments or the description of the prior art will be briefly described below, and obviously, in the following description The drawings are only some of the embodiments of the present invention, and other drawings may be obtained from those skilled in the art without departing from the drawings.

FIG. 1 is a flowchart of a method for inter-network association call connection according to an embodiment of the present invention; FIG. 2 is a flowchart of another method for inter-network association call connection according to an embodiment of the present invention; a schematic diagram of the second service execution system transferring the second call to the first service execution system;

4 is a flowchart of a method for connecting a call between a narrowband network and a broadband network according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of networking of a method for connecting call between a narrowband network and a broadband network according to an embodiment of the present invention;

FIG. 6 is a flowchart of a method for connecting a call between networks according to an embodiment of the present invention; FIG. 7 is a schematic structural diagram of a service proxy system according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a service proxy system according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of a service proxy system according to an embodiment of the present disclosure;

FIG. 10 is a structural block diagram of a service execution system according to an embodiment of the present invention;

FIG. 11 is a structural block diagram of another service execution system according to an embodiment of the present invention;

FIG. 12 is a structural block diagram of another service proxy system according to an embodiment of the present invention; FIG. 13 is a structural block diagram of another service proxy system according to an embodiment of the present invention; FIG. 14 is another service proxy according to an embodiment of the present invention; System structure block diagram. 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. example. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without departing from the inventive scope are the scope of the present invention.

Referring to FIG. 1 , an inter-network association call connection method is provided in an embodiment of the present invention, where a service data unit is set in a service proxy system, where the method includes:

101: The first service execution system, when receiving the first call from the first network, storing feature information of the first call in the service data unit, and generating a routing signal, where the first call is based on Routing signals are routed to the second network, and the second call is triggered on the second network;

Step 102: The first service execution system receives a second call that is transferred by the second service execution system according to the feature information of the first call stored by the service data unit, and continues to process the first call and the second call. .

In the embodiment of the present invention, a service data unit is set in a service agent system (ie, a Service Broker platform), and multiple network-triggered associated calls are transferred to a service execution system for connection processing according to the feature information stored in the service data unit. This enables the Service Broker platform to support the associated calls triggered by multiple networks, which is more conducive to the further promotion and application of Service Broker technology. Referring to FIG. 2, another inter-network association call connection method according to an embodiment of the present invention first sets an SDU (Service Data Unit) in a service agent system (ie, a Service Broker platform). Preferably, the SDU set in the service proxy system is a global type, and the global type SDU can be accessed by any service execution system in the Service Broker platform.

The inter-network associated call connection method provided by the embodiment of the present invention includes the following steps:

201: The first service execution system, when receiving the first call from the first network, generates a routing signal, routing the first call according to the routing signal to a second network, and triggering on the second network Two calls.

It should be explained that the associated call refers to a call with an associated relationship, such as multiple calls triggered by a user. When the calling party is called, the calling party will first trigger an incoming call. When routing to the called party, Trigger an outgoing call, and then process the incoming call and the outgoing call to realize the dialogue between the calling party and the called party. Here, the incoming call and the outgoing call are two calls with an associated relationship. The association information between the at least two calls for identifying the associated relationship may be the same call information between at least two calls, such as a calling number, a called number, or the like, or information that can be associated by logical operations. For example, by adding a prefix, a suffix, etc., information that can be associated with some or some of the call information between the two calls through logical operations, for example, two calls, where the A information in the first call is advanced The agreed logical operation can obtain the B information in the second call, and the relationship between the first call and the second call is identified by the association relationship between the A information and the B information. .

Here, the first network and the second network are respectively two different networks, which may be the same type of network, or different types of networks, such as broadband networks or narrowband networks, or one Broadband network, one is a narrowband network, wherein the broadband network may be an IMS network, and the narrowband network may be a narrowband fixed network or a narrowband mobile network.

202: The first service execution system stores feature information of the first call in the service data unit.

Preferably, the feature information of the first call includes a session identification code of the first call, association information used to identify an association relationship between the first call and the second call, and session identifier code and associated information of the first call. Correspondence relationship.

Correspondingly, storing the feature information of the first call in the service data unit may be: storing a correspondence between the association information and a session identification code of the first call in the service data unit.

Each session creates a session ID (session ID), which is used to uniquely identify the service logic processing related information of the call. For example, the session ID can be used to identify the service logical interface information of the call, that is, the service logic of the call is Where it is processed, the session ID can also be used to identify the processing status information of the business logic of the call, and so on. For the service execution system, it generally includes three layers: The lowest layer is the protocol layer, and the protocol related to the service execution is defined and described in the protocol stack of the layer; the middle layer is the SCS (Service Capability Set) layer. This layer defines and describes the API (Pplication Programming Interface) related to business execution; the upper layer is the application layer, also called the business layer.

Generally, after the call is triggered to the service execution system, the protocol layer reaches the SCS layer for processing, and the SCS layer searches for the service logical interface information corresponding to the call according to the session ID of the call, and invokes the interface information, where the interface information corresponds. The business logic of the application session indicates that the call object is processed in succession.

The sequence of step 201 and step 202 is not limited to performing step 201 first, and then step 202 is performed; step 202 may be performed first, then step 201 may be performed, and may be performed in parallel.

203: The second service execution system, when receiving the second call from the second network, transfers the second call to the first service according to the feature information of the first call stored by the service data unit. Executing the system, performing the connection processing on the associated first call and the second call on the first service execution system.

Preferably, the step of transferring, by the second service execution system, the second call to the first service execution system according to the feature information of the first call stored by the service data unit may include the following sub-steps:

1 The second service execution system acquires the associated information from the second call;

The second service execution system searches for the session identification code of the first call in the service data unit by using the obtained association information as an index;

Here, when the association information is the same call information between the first call and the second call, such as the calling number, the called number, and the like, the second service execution system may directly use the acquired related information as an index. Querying, in the service data unit, a session identification code of the first call;

When the associated information is information that can be associated by logical operations, at this time, the second service execution system needs to first obtain the associated information through a predetermined logical operation to obtain the associated information after the operation, and the associated relationship after the operation. The information is the association information of the first call stored in the service data unit after the first service execution system receives the first call of the first network, and then the second service execution system uses the associated information as an index. The session identifier of the first call is queried in the service data unit.

The second service execution system modifies the session identification code of the second call to the queried session identification code of the first call, and transfers the service logic of the second call to the first service execution system. The business of the first call is logical.

In the prior art, the Service Broker platform cannot support the connection of multiple network-triggered associated calls. When multiple associated calls are triggered from multiple networks to the Service Broker platform, the multiple associated calls are assigned to different service execution systems for processing. Specifically, the first service execution system includes an SCS layer session 1 and an application session 1. After receiving the first call, the SCS layer session 1 of the first service execution system searches for the corresponding call according to the session identification code 1 of the first call. The business logic interface information, the business logic of the first call is transferred to the application session 1 for processing; correspondingly, the second service execution system includes the SCS layer 2 and the application module 2, and the second service execution system After receiving the second call, the SCS layer session 2 searches for the corresponding service logical interface information according to the session identification code 2 of the second call, and transfers the service logic of the second call to the application session 2 for processing, visible, for Two associated calls (first call and second call) from multiple networks are separately executed by the two services in the Service Broker platform System (a first service execution system and a second service execution system) for processing, and therefore can not support this time internet Service Broker for the subsequent treatment of the two associated calls.

In the embodiment of the present invention, the foregoing step 3 is described in detail in conjunction with FIG. 3. After the second service execution system modifies the session identification code 2 of the second call to the session identification code 1 of the first call, the SCS layer session of the second service execution system. 2, according to the session identification code 1 of the first call, find the corresponding business logic interface information, and transfer the business logic of the second call to the application session of the first service execution system.

Processing in 1 to implement the second service execution system to transfer the received business logic of the second call to the business logic of the first call in the first service execution system, so that the two networks are triggered to the Service Broker platform. The two associated calls can be uniformly processed by the first service execution system, thereby enabling the Service Broker platform to support the associated calls triggered by multiple networks.

Correspondingly, after the second service execution system transfers the second call to the first service execution system, the subsequent service of the second call also transfers the service logic to the first service execution system according to the modified session identification code 1. deal with. It can be seen that the service data unit is set in the service agent system (ie, the Service Broker platform), and the related call from multiple networks is transferred to a service execution system for connection processing according to the feature information stored in the service data unit, thereby realizing The support of the Service Broker platform for multiple network-triggered associated calls is more conducive to the further promotion and application of Service Broker technology.

The inter-network association call connection method provided by the embodiment of the present invention is not limited to the connection processing of the associated calls from the two networks, and is also applicable to the connection processing of multiple associated calls from multiple networks, and multiple associations from multiple networks. The call is triggered separately to different service execution systems (for example, multiple associated calls of the same user are triggered to different service execution systems), and any one of the service execution systems can be used as the first service execution system, that is, it can be received The feature information of the incoming call is stored in the SDU, and the other service execution system transfers the received call to the first service execution system according to the feature information stored in the SDU, so that the associated call from multiple networks can be in one The connection processing is implemented in the service execution system, so that centralized control of multiple related calls can be implemented in one service execution system, for example, centralized control of multiple calls of one user.

Further, the SDU is added to the service agent system (ie, the Service Broker platform), so that the operator can combine them to form a new service package, thereby enriching the user experience; no need to configure the existing network, nor need to The protocol is extended to add new Service Broker interaction logic to maximize the protection of the operator's investment. In addition, it can also be applied to multiple network combinations, such as narrowband network to narrowband network, broadband network to broadband network, and broadband network to narrowband network or narrowband network to broadband network. 4 is a schematic diagram of another narrowband network and broadband inter-network call association method according to another embodiment of the present invention; see FIG. 5, which is a narrowband network and a broadband inter-network call association network to which the method shown in FIG. 4 can be applied. Schematic diagram of the structure. The global SDU is set in the service agent system (that is, the Service Broker platform), wherein the narrowband network takes the GSM network as an example, and the broadband network uses the IMS network as an example.

Among them, the Service Broker platform is a distributed platform, divided into front-end and back-end. The front end generally refers to the access device. For the narrowband access, the front end generally refers to the USAU (Universal Signaling Access Unit). For broadband access, the front end generally refers to the FEP (Front End Processor). The front-end processor is a service execute environment (SEE). The service execution system in the service execution environment processes the call received by the front-end through the deployed service instance. The interaction between the instance and the front end follows the IDL ( interface description language) call specification.

In the networking of the embodiment of the present invention, the USAU is used as a narrowband access module, and the FEP is used as a broadband access module. The service execution system 1 and the service execution system 2 on the SEE1 and the SEE2 respectively have corresponding service instances deployed in the Service Broker. An SDU unit is added to the platform, and the business logic of the entire platform can be read and written. In this process, the narrowband user dials the broadband subscriber number, that is, the initial trigger is sent from the narrowband, and the service instance stores the characteristic information of the call into the SDU, and enters the waiting state. When the broadband call is triggered from the FEP to the Service Broker platform, the above-mentioned feature information is obtained by querying the SDU, and the call logic is transferred to the service execution system 1.

The method specifically includes the following steps:

401: The narrowband subscriber dials the broadband subscriber number, and the GSM core network triggers the call 1 to the USAU of the Service Broker platform.

402: The USAU triggers the call 1 to the service execution system 1 according to the information such as the subscription of the narrowband user.

403: The service execution system 1 creates a call object GSM Call, and stores the feature information of the call 1 into the SDU, where the specific relationship between the session ID1 and the calling number of the call 1 is stored in the SDU.

404: The GSM Call sends a Connect command to route the call 1 to the broadband called user. 405: The GSM core network routes the call 1 to the broadband IMS core network through the network management, and triggers the call 2 (usually an INVITE request).

406: The IMS core network triggers Call 2 to the FEP of the Service Broker platform.

407: FEP triggers call 2 to service execution system 2.

408: The service execution system 2 creates a call object IMS Call to process the call 2, obtains the calling number from the call 2, and obtains the calling number as an index to query the ID1 of the call 1 in the SDU, so as to learn the user. The narrowband portion is processed on the service execution system 1.

409: The service execution system 2 modifies the session ID2 of the call 2 to the session ID1, and transfers the service logic of the call 2 to the connection processing on the service execution system 1.

It can be seen that the service data unit is set in the service agent system (ie, the Service Broker platform), and the related call from multiple networks is transferred to a service execution system for connection processing according to the feature information stored in the service data unit, thereby realizing The support of the Service Broker platform for multiple network-triggered associated calls is more conducive to the further promotion and application of Service Broker technology.

Further, the SDU is added to the service agent system (ie, the Service Broker platform), so that the operator can combine them to form a new service package, thereby enriching the user experience; no need to configure the existing network, nor need to The protocol is extended to add new Service Broker interaction logic to maximize the protection of the operator's investment. Referring to Figure 6, an embodiment of another inter-network associated call connection method. In this embodiment, the first network is a GSM network, and the second network is an IMS network. Specifically, the calling party is an MSC (mobile switching centre) terminal in the GSM network, and the user subscribes to a VPN (Virtual Private Network), a PPS (Pre-paid service), and a PoC. ( Push to talk ) business. Poc is the intercom service provided in the mobile network. The called party is an IMS (IP Multimedia Subsystem) terminal, and this user subscribes to a VPN service.

Caller A calls called B, and the process is as follows:

601: The MSC terminal in the GSM network triggers the call 1 and sends an IDP (b, A) message to the service broker platform.

Where b is the short number of the called B, and A is the number of the calling party A.

602: The Service Broker platform invokes the VPN service to obtain the long number of the called B.

Including the Service Broker platform to forward the IDP (b, A) message to the VPN server. The VPN server finds the long number B of the called B in its database, and the short number a of the calling party A, using signaling RRBE, CONN ( B, a), feed the long number B of the called B and the short number a of the calling party A to the Service Broker platform.

603: The Service Broker platform invokes the PPS service for charging.

Including the Service Broker platform to send IDP (B, A) messages to the PPS server, the PPS server initiates charging logic, and feedback signaling SCI, RRBE, and CON to the Service Broker platform.

604: The Service Broker platform modifies the long number B of the called B into an IMS domain available number R-IMS according to the number range of the IMS domain, and sends a Connect command, that is, signaling CON (R-IMS, A) to the MSC of the GSM network. The terminal, the call 1 is routed by the MSC terminal to the IMS terminal.

605: Trigger another call 2 to the Service broker platform on the IMS core network, where call 2 is an INVITE request, that is, the IMS core network sends signaling INVITE (R-IMS, A) [SDP1] to the Service broker platform, and call 2 is SDP1 with the media gateway in call 2 triggered by the connect command generated by call 1 routing IMS.

606: Connect the associated call 1 and call 2 in the Service broker platform.

607: Call 2 obtains the source number of the called B (ie, the long number of the called B), and the service broker platform modifies the IMS routing number tel: R-IMS to the source number of B, and sends a PoC request to the PoC server, that is, Send signaling INVITE(B,A)[SDP2+list] to the PoC server to request intercom. SDP2 is converted from SDP1 according to the format required by the PoC server.

608: The PoC server routes the call 2 to the IMS core network through the service broker platform, that is, the PoC server sends the signaling INVITE (B, A) [SDP3] to the IMS core network through the service broker platform. SDP3 is generated by the PoC server.

609: The called B responds, the IMS core network sends a 200 OK [SDP4] message to the service broker platform, and the Service broker platform forwards the 200 OK [SDP4] message to the PoC server. SDP4 is generated by the IMS core network.

610: The Poc server sends a 200 OK [SDP5] message to the service broker platform, and the service broker platform forwards the 200 OK [SDP5] message to the IMS core network. SDP5 is generated by the PoC server.

611: After receiving the 200 OK [SDP5] message forwarded by the PoC server, the Service broker platform generates an Answer event, and reports the Answer event to the call 1. The Service broker platform sends an Answer event to the PPS server, that is, sends the ERB (ANS) signaling to The PPS server informs the billing start, the PPS server feeds back the signaling AC, RRBE, and CONT to the Service broker platform to initiate billing.

612: The Service broker platform forwards the ACK message sent by the IMS core network to the PoC server, and forwards the ACK message sent by the PoC server to the IMS core network. In the above step 606, the associated call 1 and the call 2 of the two networks are triggered to be connected. Specifically, the global type SDU is set in the service broker system (ie, the Service broker platform), and the service execution of the call 1 is received. The system 1 stores the feature information of the call 1 in the SDU, and the service execution system 2 that receives the call 2 queries the SDU, obtains the feature information of the call 1, transfers the call 2 to the service execution system 1, and performs the connection processing, thereby obtaining The source number of the called B, reporting the Answer event to call 1 and so on.

It can be seen that the service data unit is set in the service agent system (ie, the Service Broker platform), and the associated call from multiple networks is transferred to a service execution system for connection processing according to the feature information stored in the service data unit, thereby realizing The support of the Service Broker platform for multiple network-triggered associated calls is more conducive to the further promotion and application of Service Broker technology. Referring to FIG. 7, a service proxy system according to an embodiment of the present invention includes a service data unit 1, and at least one of the following two service execution systems:

a first service execution system 2, configured to store feature information of the first call in the service data unit 1 when receiving a first call from the first network; and generate a routing signal, the first The call is routed to the second network according to the routing signal to trigger a second call on the second network; and the feature of the first call stored by the second service execution system 3 according to the service data unit 1 is received. Transmitting a second call from the information, and subsequently processing the first call and the second call;

The service data unit 1 is configured to store feature information of the first call, so that the second service execution system 3 queries;

a second service execution system 3, configured to: when receiving the second call from the second network, according to the feature information of the first call stored by the service data unit 1, the second call Transfer to the first service execution system 2.

Preferably, the service data unit 1 is a global type.

Referring to FIG. 8, when the second service execution system 3 is two, that is, the Service Broker platform includes the second service execution system 3a and the second service execution system 3b, and the second service execution system 3a and the second service execution system 3b respectively. The received call is transferred to the first service execution system 2 by querying the service data unit 1. For the same reason, when the second service execution system 3 is plural, the plurality of second service execution systems 3 respectively transfer the received call to the first service execution system 2 by querying the service data unit 1.

Referring to FIG. 9, when the first service execution system 2 is two, that is, the Service Broker platform includes the first service execution system 2a and the first service execution system 2b, and the second service execution system 3 queries the service data unit 1, The received call is transferred to the first service execution system 2a and/or the first service execution system 2b. Similarly, when the first service execution system 2 is multiple, the second service execution system 3 transfers the received call to one or more first service execution systems 2 by querying the service data unit 1.

In practical applications, the service data unit 1 may also be multiple.

It can be seen that the service data unit is set in the service agent system (ie, the Service Broker platform), and the associated call from multiple networks is transferred to a service execution system for connection processing according to the feature information stored in the service data unit, thereby realizing The support of the Service Broker platform for multiple network-triggered associated calls is more conducive to the further promotion and application of Service Broker technology.

The foregoing service agent system shown in FIG. 7, 8 or 9 can perform the foregoing method shown in FIG. 2, 4 or 6 and its embodiments, and thus the workflow thereof will not be described herein. Referring to FIG. 10, an embodiment of the present invention provides a service execution system in the foregoing service agent system, that is, a first service execution system 2, including:

The receiving module 21 is configured to receive a first call from the first network;

The storage module 22 is configured to: when the receiving module 21 receives the first call, store feature information of the first call in a service data unit 1 of a service agent system;

The triggering module 23 is configured to: when the receiving module 21 receives the first call, generate a routing signal, and route the first call to the second network according to the routing signal, and trigger on the second network Second call

The connection module 24 is configured to receive a second call that is transferred by the second service execution system according to the feature information of the first call stored by the service data unit, and subsequently process the first call and the second call call. Further, the feature information of the first call includes a session identifier code of the first call, and associated information for identifying an association relationship between the first call and the second call, and the associated information and Corresponding relationship of the session identification code of the first call;

Further, the service execution system 2 further includes a transfer module, configured to transfer the second call according to the feature information stored by the service data unit 1 when receiving the second call from the second network. That is, in a practical application, in a service execution system, the feature information of the call received by the user can be stored in the SDU, and the other service execution system can transfer the call from other network to the service execution system by querying; You can transfer your received calls to other service execution systems by querying the SDU.

It can be seen that by setting a service data unit in a service agent system (for example, a Service Broker platform), the associated call from multiple networks is transferred to a service execution system for connection processing according to the feature information stored in the service data unit, thereby realizing The support of the Service Broker platform for multiple network-triggered associated calls is more conducive to the further promotion and application of Service Broker technology. Referring to FIG. 11, another service execution system, that is, the second service execution system 3, in the foregoing service agent system according to the embodiment of the present invention includes:

The obtaining module 31 is configured to acquire first call association information from the second call when receiving the second call from the second network;

The query module 32 is configured to query, by using the association information acquired by the acquiring module 31, the session identification code of the first call in the service data module 1 of the service agent system; and the transfer module 33, Modifying the session identifier of the second call to the session identifier of the first call that is queried by the query module 32, and transferring the service logic of the second call to the first service execution system 2 The business of the first call is logical.

The service execution system 3 provided by the embodiment of the present invention receives the second call from the second network, and the first service execution system 2 generates a routing signal when receiving the first call from the first network, according to the The routing signal routes the first call to the second network and triggers the generated second call on the second network.

Further, the service execution system 3 further includes a storage module, configured to store, when receiving the first call from the first network, feature information of the first call in the service data unit 1 of the service agent system. And a connection module, configured to receive a third call transferred by the third service execution system according to the feature information of the first call stored by the service data unit, and subsequently process the first call and the third call call. That is, in a practical application, in a service execution system, the feature information of the call received by the user can be stored in the SDU, and the other service execution system can transfer the call from the other network to the service execution system by querying; By querying the SDU, the call received by you is transferred to another service execution system.

It can be seen that by setting a service data unit in a service agent system (for example, a Service Broker platform), the associated call from multiple networks is transferred to a service execution system for connection processing according to the feature information stored in the service data unit, thereby realizing The support of the Service Broker platform for multiple network-triggered associated calls is more conducive to the further promotion and application of Service Broker technology.

The service execution system described in the foregoing FIGS. 10 and 11 and its embodiments can be applied to the method executed by the service execution system described in FIG. 2, 4 or 6 and its embodiments, and details are not described herein.

It should be noted that the service execution system 2 and the service execution system 3 in the foregoing service agent system may be implemented by hardware, may be implemented by software, or may be implemented by a combination of hardware and software. Of course, in an actual application, the service execution system 2 and the service execution system 3 may be distributed anywhere in the service agent system (ie, the Service Broker platform), wherein the service execution system 2 may also be software distributed in different locations of the service agent system. The function module, the hardware function module, and the functional modules combined with software and hardware are implemented together, and the business execution system 3 is also the same. Referring to FIG. 12, an embodiment of the present invention further provides a service proxy system, including a service data unit A1, and a first service execution system B1;

The first service execution system B1 is configured to: when receiving the first call from the first network, store feature information of the first call in the service data unit A1; and generate a routing signal, The first call is routed to the second network according to the routing signal to trigger a second call on the second network; and the receiving and connecting processing is performed by the second service execution system according to the service data unit A1 a second call transferred from the feature information of the first call;

The service data unit A1 is configured to store feature information of the first call, so that the second service performs system query.

The first service execution system B1 and the service data unit A1 may be one or more in an actual application.

It should be noted that the service execution system B1 in the embodiment of the present invention may perform the functions shown in the service execution system 2 in the foregoing embodiment, and thus the workflow thereof is not described herein.

It can be seen that by setting a service data unit in a service agent system (for example, a Service Broker platform), the associated call from multiple networks is transferred to a service execution system for connection processing according to the feature information stored in the service data unit, thereby realizing The support of the Service Broker platform for multiple network-triggered associated calls is more conducive to the further promotion and application of Service Broker technology. Referring to Figure 13, an embodiment of the present invention further provides a service proxy system, including a service data unit A2, and a first service execution system B2;

The first service execution system B2 is configured to: when receiving the first call from the first network, store feature information of the first call in the service data unit A2; and generate a routing signal, where the The first call is routed to the second network according to the routing signal to trigger a second call on the second network; and the first service stored by the second service execution system according to the service data unit A2 is received and connected a second call transferred from the feature information of a call;

The service data unit A2 is configured to store feature information of the first call, so that the second service performs system query.

The first service execution system B2 and the service data unit A2 may be one or more in an actual application.

The above service data unit A2 may be of a global type.

Further, the service proxy system further includes a second service execution system C, configured to: according to the first call stored by the service data unit A2, when receiving the second call from the second network Characteristic information, transferring the second call to the first service execution system B2.

The first service execution system B2 includes:

The receiving module B21 is configured to receive the first call from the first network, and the storage module B22 is configured to: when the receiving module B21 receives the first call, store feature information of the first call in the Business data unit A2;

The triggering module B23 is configured to: when the receiving module B21 receives the first call, generate a routing signal, and route the first call to the second network according to the routing signal, to be on the second network. Triggering a second call;

The connection module B24 is configured to receive a second call that is transferred by the second service execution system C according to the feature information of the first call stored by the service data unit A2, and subsequently process the first call and the Second call.

The feature information of the first call includes a session identification code of the first call, association information used to identify an association relationship between the first call and the second call, and the associated information and the first Correspondence of the session ID of the call.

The second business execution system C includes:

The acquiring module C1 is configured to acquire first call association information from the second call when receiving the second call from the second network;

The query module C2 is configured to query, by using the association information acquired by the acquiring module C1, the session identification code of the first call in the service data module A2;

The transfer module C3 is configured to modify the session identification code of the second call to the session identification code of the first call queried by the query module C2, and transfer the service logic of the second call to the first The business logic of the first call in a service execution system B2.

It should be noted that the service execution system B2 and the service execution system C in the embodiment of the present invention may perform the functions shown in the service execution system 2 and the service execution system 3 in the foregoing embodiments, and thus the workflow thereof is not described herein.

In practical applications, the second service execution system C can be used as one or more.

It can be seen that by setting a service data unit in a service agent system (for example, a Service Broker platform), the associated call from multiple networks is transferred to a service execution system for connection processing according to the feature information stored in the service data unit, thereby realizing The support of the Service Broker platform for multiple network-triggered associated calls is more conducive to the further promotion and application of Service Broker technology. Referring to Figure 14, an embodiment of the present invention further provides a service agent system, including a service data unit D, and a second service execution system S;

The service data unit D is configured to store feature information of the first call from the first network, and the second service execution system S is configured to: when receiving the second call from the second network, according to the service The feature information of the first call stored by the data unit D transfers the second call to the first service execution system; the feature information of the first call is received by the first service execution system from the first The first call of the network is stored in the service data unit D.

It can be seen that by setting a service data unit in a service agent system (for example, a Service Broker platform), the associated call from multiple networks is transferred to a service execution system for connection processing according to the feature information stored in the service data unit, thereby realizing The support of the Service Broker platform for multiple network-triggered associated calls is more conducive to the further promotion and application of Service Broker technology. It should be noted that, in this context, relational terms such as first and second, etc. are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities or operations. There is any such actual relationship or order between them. Furthermore, the terms "including", "comprising" or "comprising" or "includes" or "includes" or "includes" or "includes" or "includes" Other elements, or elements that are inherent to such a process, method, item, or device. In the absence of further limitation, an element defined by the phrase "comprising a ..." does not exclude the presence of additional the same element in the process, method, item, or device that comprises the element.

It will be understood by those skilled in the art that all or part of the steps of the foregoing embodiments may be implemented by a program to instruct related hardware, and the program may be stored in a computer readable storage medium. When executed, the method includes the following steps: (step of the method), the storage medium, such as: R0M/RAM, disk, optical disk, and the like.

The above is only the preferred embodiment 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 invention are intended to be included within the scope of the invention.