Intelligent gateway system and interaction method

Abstract

The invention relates to the technical field of new-generation information, and discloses an intelligent gateway system, which comprises an outbound data receiving module used for receiving outbound data transmitted by an outbound task initiator in a message queue mode; the outbound database is used for storing outbound data existing in a message queue mode; the storage module is used for analyzing the outbound data; the timing scanning module is used for performing timing scanning on the outbound data in the database; the service configuration module is used for carrying out outbound task matching on the acquired outbound data; the routing module is used for distributing the matched outbound task to a corresponding outbound system for outbound; and the gateway background is used for data transmission management and scheduling among the modules, data transmission is carried out on an outbound task through a uniform interface in combination with the steps of the interaction method, and an outbound data initiator can communicate with multiple outbound systems only by connecting an outbound system once.

Description

Technical Field

[0001] The present invention relates to the field of new generation information technology, and in particular to an intelligent gateway system and an interaction method. Background Art

[0002] In the process of financial business development, we seek cooperation methods through telephone contacts. Due to the large volume of outbound calls, manual outbound calls alone can no longer meet the needs of the business. Therefore, intelligent outbound calls are now used for phone dialing, and multiple outbound call systems are used to adjust the outbound call rhythm and judge the outbound call efficiency.

[0003] Since each outbound call system has different connection capacity and business, each outbound call system adopts different internal logic, communication protocol and data connection interface. It is time-consuming and labor-intensive for the outbound call requester to access different outbound call systems. It is necessary to design a docking method for the outbound call requester and each outbound call system separately, resulting in repeated matching and confirmation processes for the outbound call requester to connect to the outbound call system. In particular, the communication access method between multiple outbound call requesters and multiple outbound call systems requires a communication docking method to be designed for each communication structure, resulting in a decentralized and complex communication docking system. During communication matching, they need to be compared one by one, resulting in reduced data exchange effectiveness. Summary of the invention

[0004] The present invention aims to provide an intelligent gateway system and an interaction method to solve the problem that the outbound call requesting party has different outbound call purposes and needs to connect to multiple outbound call systems. The connection method with the outbound call system must be designed separately, which reduces the effectiveness of data exchange.

[0005] In order to solve the above problems, the technical solution adopted by the present invention is: an intelligent gateway system for processing outbound call data, comprising:

[0006] An outbound call data receiving module, used to receive the outbound call data transmitted by the outbound call task initiator in the form of a message queue;

[0007] Outbound call database, used to store outbound call data in the form of message queues;

[0008] The storage module is used to parse the outbound call data and store it in the outbound call database in a unified data format;

[0009] The timed scanning module is used to perform timed scanning on the outbound call data in the database to obtain the outbound call data required for outbound calls at a specified time;

[0010] The business configuration module matches the acquired outbound call data with outbound call tasks and assigns an identification code to the matched outbound call data;

[0011] The routing module is used to assign the matched outbound call tasks to the corresponding outbound call system for outbound calls;

[0012] The gateway backend is used for data transmission management and scheduling between modules.

[0013] The principle and effect of this method are as follows: outbound call data is transmitted in the form of message queues, and outbound call initiation and outbound call execution can be processed asynchronously during the outbound call process. After obtaining the outbound call data from the outbound call data initiator, the outbound call data is first stored in the outbound call database, and then the outbound call data is retrieved from the outbound call database according to the outbound call period of the outbound call data according to the timing scanning module; then, through the setting of outbound call rules, the outbound call data is distributed to the matching outbound call system through the routing module. This process can shield the differences in manufacturer protocols internally, and through the routing module with a unified entrance, the outbound call data initiator only needs to connect to the system once to access the capabilities of multiple outbound call systems.

[0014] Furthermore, it also includes a callback module, which is used to receive the outbound call response volume of the outbound call system. The callback module sends the outbound call response volume of each outbound call system to the gateway background, sets matching rules in the gateway background, and the service configuration module allocates outbound call data to each outbound call system according to the matching rules in the gateway background, and the routing module distributes the outbound call data to each outbound call system. The outbound call response volume of the outbound call system is first collected by the callback module, so as to avoid the problem of insufficient outbound call response volume and outbound call matching errors when matching outbound call data.

[0015] Furthermore, the callback module also receives the outbound call data of the completed outbound call in the outbound call system, and transmits the outbound call data to the gateway background. The gateway background clears the outbound call data of the completed outbound call in the outbound call database, and updates the version number of the outbound call database. The callback module also calls back the situation after the outbound call is completed, and through the identification of the gateway background, it is more convenient to clear the data in the outbound call database in a targeted manner, so as to avoid the data in the outbound call database being mistakenly cleared.

[0016] An interactive method of an intelligent gateway, for processing an outbound call task, comprises the following steps:

[0017] Step 1: The outbound call data sent by the outbound call task initiator is continuously received through the routing module, and the outbound call data is sent in the form of a message queue;

[0018] Step 2: After the outbound call data is uniformly transmitted to the gateway background, the format of the outbound call data is converted through the warehousing module and stored in the outbound call database.

[0019] Step 3: The gateway backend issues an instruction to let the timing scanning module regularly scan the outbound call data that needs to be completed within a specified time; extract the outbound call data;

[0020] Step 4: Match the outbound call data with the outbound call system according to the preset outbound call rules in the gateway background.

[0021] Step 5: Distribute the matched outbound call data to the corresponding outbound call system through the routing module for outbound calling;

[0022] Step 6: The callback module obtains the outbound call task status after the outbound call system completes the outbound call;

[0023] Step 7: After the outbound call task status is set, the storage location occupied by the outbound call data is cleared through the gateway background so that the outbound call data can be stored again in the storage location after the outbound call database is cleared.

[0024] Through the above steps, reasonable matching of multiple outbound call initiators and outbound call tasks in multiple outbound call systems is completed.

[0025] Furthermore, between step 1 and step 2, an outbound call data receiving module is set between the routing module and the gateway background, and a unique identifier is added to each outbound call data through the outbound call data receiving module, and the identifier is combined with the outbound call data and stored in the outbound call database. The unique identifier can help each module to quickly identify the outbound call data.

[0026] Furthermore, the outbound call data received by the routing module is in the form of a message queue, which facilitates asynchronous processing in subsequent outbound call processes.

[0027] Furthermore, the outbound call rules in step 4 are implemented by setting a rule engine in the gateway backend, and the rule engine configures the outbound call deadline, outbound call cost, and outbound call success rate of the outbound call data, and configures the outbound call data to the outbound call system that best meets the parameter range. By configuring the outbound call data through the rule engine, the outbound call success rate can be improved and the outbound call cost can be reduced.

[0028] Furthermore, after the outbound call data of the outbound call database is cleared in step 7, the outbound call database is updated, and the subsequent outbound call data is matched with the current outbound call database version number and then stored in the database. It is easier to determine whether the outbound call is successful by identifying the version number of the outbound call database than to obtain data directly in the outbound call system. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 It is a schematic diagram of the structure of the intelligent gateway system based on outbound call task processing;

[0030] Figure 2 The figure is a flow chart of the interaction method of the intelligent gateway for outbound call tasks. DETAILED DESCRIPTION

[0031] Example 1

[0032] The following is further described in detail by specific implementations, but the implementations of the present invention are not limited thereto. Unless otherwise specified, the technical means used in the following implementations are conventional means well known to those skilled in the art.

[0033] like Figure 1 An intelligent gateway system is shown, which is used for processing outbound call data, and includes:

[0034] The outbound call data receiving module 4 is used to receive the outbound call data transmitted by the outbound call task initiator 1 in the form of a message queue;

[0035] Outbound call database 8, used to store outbound call data in the form of message queues;

[0036] The storage module 6 is used to parse the outbound call data and store it in the outbound call database in a unified data format;

[0037] The timing scanning module 7 is used to perform timing scanning on the outbound call data in the database to obtain the outbound call data required for outbound calls at a specified time;

[0038] The service configuration module 9 performs outbound call task matching on the acquired outbound call data and assigns an identification code to the matched outbound call data;

[0039] Routing module 3, used to distribute the matched outbound call tasks to the corresponding outbound call system 2 for outbound calling;

[0040] The gateway backend 5 is used for data transmission management and scheduling between modules.

[0041] It also includes a callback module 10, which is used to receive the outbound call response volume issued by the outbound call system 2. The callback module 10 sends the outbound call response volume of each outbound call system 2 to the gateway background 5, sets matching rules in the gateway background 5, and the business configuration module 9 allocates outbound call data to each outbound call system 2 according to the matching rules in the gateway background 5, and the routing module 3 distributes the outbound call data to each outbound call system 2.

[0042] The callback module 10 also receives the outbound call data of the completed outbound call in the outbound call system 2 and transmits the outbound call data to the gateway background 5 . The gateway background 5 clears the outbound call data of the completed outbound call in the outbound call database 8 and updates the version number of the outbound call database 8 .

[0043] like Figure 2 The interactive method of an intelligent gateway shown in the figure, for processing an outbound call task, includes the following steps:

[0044] Step 1 S1: Continuously receive the outbound call data sent by the outbound call task initiator through the routing module, and the outbound call data is sent in the form of a message queue.

[0045] Step 2 S2: After the outbound call data is uniformly transmitted to the gateway backend, the format of the outbound call data is converted through the storage module and stored in the outbound call database.

[0046] Step 3 S3: The gateway backend issues an instruction to let the timing scanning module regularly scan the outbound call data that needs to be completed within a specified time; and extract the outbound call data.

[0047] Step 4 S4: Match the outbound call data and the outbound call system according to the preset outbound call rules in the gateway background. The setting rule engine of the gateway background is implemented. The rule engine configures the parameters of the outbound call period, outbound call cost, and outbound call success rate of the outbound call data, and configures the outbound call data to the outbound call system that best meets the parameter range.

[0048] Step 5 S5: The matched outbound call data is distributed to the corresponding outbound call system through the routing module for outbound calling.

[0049] Step 6 S6: The callback module obtains the outbound call task status after the outbound call system completes the outbound call.

[0050] Step 7 S7: After the outbound call task status is changed, the storage location occupied by the outbound call data is cleared through the gateway background so that the outbound call database can store the outbound call data again after the storage location is cleared; the outbound call database is updated, and the subsequent outbound call data is matched with the current outbound call database version number before being stored in the database.

[0051] Between step 1 S1 and step 2 S2, an outbound call data receiving module is set between the routing module and the gateway background, and a unique identifier is added to each outbound call data through the outbound call data receiving module, and the identifier is combined with the outbound call data and stored in the outbound call database. The unique identifier can help each module to quickly identify the outbound call data.

[0052] The outbound call data received by the routing module exists in the form of a message queue, which facilitates asynchronous processing in subsequent outbound calls.

[0053] The above is only an embodiment of the present invention, and the common knowledge such as the known specific technical solutions and / or characteristics in the solution is not described in detail here. It should be pointed out that for those skilled in the art, without departing from the technical solution of the present invention, several modifications and improvements can be made, which should also be regarded as the protection scope of the present invention, and these will not affect the effect of the implementation of the present invention and the practicality of the patent. The scope of protection required by this application shall be based on the content of its claims, and the specific implementation methods and other records in the specification can be used to interpret the content of the claims.

Claims

1. An intelligent gateway system for processing outbound call data, characterized in that: include: An outbound call data receiving module, used to receive the outbound call data transmitted by the outbound call task initiator in the form of a message queue; Outbound call database, used to store outbound call data in the form of message queues; The storage module is used to parse the outbound call data and store it in the outbound call database in a unified data format; The timed scanning module is used to perform timed scanning on the outbound call data in the database to obtain the outbound call data required for outbound calls at a specified time; The business configuration module matches the acquired outbound call data with outbound call tasks and assigns an identification code to the matched outbound call data; The routing module is used to assign the matched outbound call tasks to the corresponding outbound call system for outbound calls; The gateway backend is used for data transmission management and scheduling between modules.

2. The intelligent gateway system according to claim 1, characterized in that , also includes a callback module, which is used to receive the outbound call response volume issued by the outbound call system. The callback module sends the outbound call response volume of each outbound call system to the gateway background, sets matching rules in the gateway background, and the business configuration module allocates outbound call data to each outbound call system according to the matching rules in the gateway background, and the routing module distributes the outbound call data to each outbound call system.

3. The intelligent gateway system according to claim 2, characterized in that: The callback module also receives the outbound call data of the completed outbound call in the outbound call system, and transmits the outbound call data to the gateway background. The gateway background clears the outbound call data of the completed outbound call in the outbound call database and updates the version number of the outbound call database.

4. An interactive method of an intelligent gateway, for processing outbound call tasks, and based on the intelligent gateway system of claim 2, characterized in that: The specific steps are as follows: Step 1: Continuously receive the outbound call data sent by the outbound call task initiator through the routing module, and the outbound call data is sent in the form of a message queue; Step 2: After the outbound call data is uniformly transmitted to the gateway background, the format of the outbound call data is converted through the storage module and stored in the outbound call database. Step 3: The gateway backend issues an instruction to let the timing scanning module regularly scan the outbound call data that needs to be completed within a specified time; extract the outbound call data; Step 4: Match the outbound call data with the outbound call system according to the preset outbound call rules in the gateway background. Step 5: Distribute the matched outbound call data to the corresponding outbound call system through the routing module for outbound calling; Step 6: The callback module obtains the outbound call task status after the outbound call is completed by the outbound call system; Step 7: After the outbound call task status is set, the storage location occupied by the outbound call data is cleared through the gateway background so that the outbound call data can be stored again in the storage location after the outbound call database is cleared.

5. The interaction method of the intelligent gateway according to claim 4, characterized in that: Between step 1 and step 2, an outbound call data receiving module is set between the routing module and the gateway background, and a unique identifier is added to each outbound call data through the outbound call data receiving module, and the identifier is combined with the outbound call data and stored in the outbound call database.

6. The intelligent gateway interaction method according to claim 5, characterized in that: The outbound call rules in step 4 are implemented by setting a rule engine in the gateway background. The rule engine configures the outbound call deadline, outbound call cost, and outbound call success rate of the outbound call data, and configures the outbound call data to the outbound call system that best meets the parameter range.

7. The intelligent gateway interaction method according to claim 6, characterized in that: After the outbound call data of the outbound call database is cleared in step seven, the outbound call database is updated, and the subsequent outbound call data is matched with the current outbound call database version number and then stored in the database.

Images