Outbound call data processing method, outbound call platform and computer-readable storage medium

Abstract

The present invention discloses a method for processing outbound call data in the field of intelligent services, an outbound call platform and a computer-readable storage medium, so as to solve the technical problem of high system risk and business risk of the outbound call platform in the prior art. The method comprises: creating a data batch for multiple original data files to be processed according to the upstream data system and the product to which they belong; the original data files are generated according to the outbound call data template provided by the outbound call platform, the basic fields shared by each outbound call data template and the secondary split fields for different outbound call services are configured in the outbound call platform, the custom fields related to different business scenarios are configured in the upstream data system, and one outbound call data template corresponds to one business scenario; the current outbound call data template of the product corresponding to the data batch is obtained from the outbound call data template library, and content parsing and legitimacy verification are performed on each original data file in the data batch based on the template; the original data records that pass the verification are stored in the outbound call platform.

Description

Technical Field

[0001] The present invention relates to the field of intelligent services, and in particular to a method for processing outbound call data, an outbound call platform, and a computer-readable storage medium. Background Art

[0002] Outbound calls are an important channel in the customer service field. Through outbound calls, we can directly reach customers, communicate with them directly, facilitate online transactions, and provide outbound services in various business scenarios such as marketing, notifications, and customer care.

[0003] For an enterprise or organization with many branches and offices, each branch or office does not provide outbound call services independently. Instead, an outbound call platform of the enterprise or organization provides outbound call services in a unified manner. This requires the outbound call platform to continuously collect original data supporting outbound call services from the systems of each branch and office.

[0004] Because different business scenarios require different raw data, outbound call platforms typically collect raw data based on business scenarios. They design different data models for each scenario, then use these models to process the collected raw data into outbound call data and store it in the corresponding database. The disadvantage of this approach is that changes to the data model or database require rewriting the outbound call platform's software code, republishing it, and then re-integrating it with the software in each branch and office before continuing to collect raw data.

[0005] However, as customer needs continue to evolve, the business scenarios of corresponding enterprises are also changing, becoming more diverse and rapidly evolving. This requires outbound call platforms to constantly add new data models, modify existing ones, repeatedly revise software code, and rapidly iterate and update software versions. Because software version updates typically require long development cycles, in practice, rapid software version iterations often fail to promptly respond to business needs. Furthermore, frequent software version updates can further lead to new system defects in the outbound call platform's software system, which in turn creates systemic and business risks.

[0006] Therefore, how to reduce the system risk and business risk of the outbound call platform while quickly responding to business needs has become a technical problem that needs to be solved urgently. Summary of the Invention

[0007] The present invention provides a method for processing outbound call data, an outbound call platform, and a computer-readable storage medium, which are used to solve the technical problem of high system risk and business risk of the outbound call platform in the prior art.

[0008] In the first aspect, to solve the above technical problems, an embodiment of the present invention provides a method for processing outbound call data, which is applied to an outbound call platform. The technical solution of the method is as follows:

[0009] Creating data batches from multiple raw data files to be processed according to their respective upstream data systems and products; wherein the raw data files are generated based on outbound call data templates provided by the outbound call platform, the basic fields common to each outbound call data template and the secondary split fields for different outbound call services are configured in the outbound call platform, and the custom fields related to different business scenarios are configured in the upstream data system, with one outbound call data template corresponding to one business scenario;

[0010] Obtaining the current outbound call data template of the product corresponding to the data batch from an outbound call data template library; wherein the outbound call data template library is used to store outbound call data templates corresponding to various business scenarios, and one business scenario corresponds to one product;

[0011] According to the current outbound call data template, each original data file in the data batch is parsed and verified for legitimacy;

[0012] The original data records that have passed the verification in the original data file are used as outbound call data records and stored in the outbound call database of the outbound call platform.

[0013] In one possible implementation, before creating data batches from the plurality of raw data files to be processed according to their respective upstream data systems and products, the method further includes:

[0014] Generate an outbound call data template corresponding to the business scenario based on the information entered by the user in the template configuration page; wherein the target configuration page is used for the user to configure the outbound call data template for different business scenarios;

[0015] Each newly generated outbound call data template is synchronized to the upstream data system that provides the original data file for the outbound call platform, so that the upstream data system exports data according to the data template of the corresponding business scenario to form the original data file.

[0016] In a possible implementation manner, the outbound call data template includes:

[0017] Field types and field properties.

[0018] In a possible implementation, the field type includes:

[0019] The basic fields, the custom fields, and the secondary split fields; the basic fields are the basis for the upstream data system to export data, the custom fields are the fields added by the upstream data system for different business scenarios when exporting data, and the secondary split fields are the fields used by outbound call operators to filter outbound call data records from the outbound call database when performing outbound call services.

[0020] In a possible implementation, the field attributes include:

[0021] Whether to desensitize, desensitization rules, whether required, whether to display, data type.

[0022] In a possible implementation manner, the field attributes of the secondary split field further include a split type, and different split types correspond to different split rules.

[0023] One possible implementation method is to create data batches for multiple raw data files to be processed according to their upstream data systems and products, including:

[0024] Periodically scanning a plurality of raw data files received from various upstream data systems; wherein the names of the raw data files include the upstream data systems and the products to which they belong;

[0025] According to the names of the original data files, the original data files corresponding to the same product under the same upstream data system are classified into the same newly created data batch.

[0026] A possible implementation method is to perform content parsing and legality verification on each original data file in the data batch according to the current outbound call data template, including:

[0027] Acquire header information of the original data file, wherein the header information includes fields of the original data record;

[0028] Acquire, from the header information, a field position corresponding to a field that is consistent with a specified template field in the outbound call data template;

[0029] Verifying, based on the data recording rule of the designated template field, whether the data at the corresponding field position in the original data record complies with the data recording rule;

[0030] If the data in the field position corresponding to each specified template field in the original data record complies with the data record rules, it is determined that the corresponding original data record has passed the verification; otherwise, it is determined that the corresponding original data record has failed the verification, and the reason for failure to pass the verification is recorded.

[0031] In a possible implementation manner, after the original data records in the original data file that have passed verification are stored as outbound call data records in the outbound call database of the outbound call platform, the method further includes:

[0032] Every time an outbound call data record is stored, the number of valid customers in the corresponding data batch is accumulated by one;

[0033] When all original data files in the data batch have been verified, the status of the corresponding data batch is set to be in effect for use by the outbound call service.

[0034] In a second aspect, an embodiment of the present invention provides an outbound calling platform, including:

[0035] a creation unit, configured to create data batches from a plurality of raw data files to be processed according to their respective upstream data systems and products; wherein the raw data files are generated based on an outbound call data template provided by the outbound call platform, wherein basic fields common to each outbound call data template and secondary split fields for different outbound call services are configured in the outbound call platform, and custom fields related to different business scenarios are configured in the upstream data system, with one outbound call data template corresponding to one business scenario;

[0036] an acquisition unit, configured to acquire the current outbound call data template of the product corresponding to the data batch from an outbound call data template library; wherein the outbound call data template library is configured to store outbound call data templates corresponding to various business scenarios, with one business scenario corresponding to one product;

[0037] A verification unit, configured to perform content analysis and legality verification on each original data file in the data batch according to the current outbound call data template;

[0038] The processing unit is used to store the original data records that have passed the verification in the original data file as outbound call data records in the outbound call database of the outbound call platform.

[0039] In a possible implementation method, the outbound calling platform further includes a configuration unit, wherein the configuration unit is configured to:

[0040] Generate an outbound call data template corresponding to the business scenario based on the information entered by the user in the template configuration page; wherein the target configuration page is used for the user to configure the outbound call data template for different business scenarios;

[0041] Each newly generated outbound call data template is synchronized to the upstream data system that provides the original data file for the outbound call platform, so that the upstream data system exports data according to the data template of the corresponding business scenario to form the original data file.

[0042] In a possible implementation manner, the outbound call data template includes:

[0043] Field types and field properties.

[0044] In a possible implementation, the field type includes:

[0045] The basic fields, the custom fields, and the secondary split fields; the basic fields are the basis for the upstream data system to export data, the custom fields are the fields added by the upstream data system for different business scenarios when exporting data, and the secondary split fields are the fields used by outbound call operators to filter outbound call data records from the outbound call database when performing outbound call services.

[0046] In a possible implementation, the field attributes include:

[0047] Whether to desensitize, desensitization rules, whether required, whether to display, data type.

[0048] In a possible implementation manner, the field attributes of the secondary split field further include a split type, and different split types correspond to different split rules.

[0049] In a possible implementation manner, the creation unit is further configured to:

[0050] Periodically scanning a plurality of raw data files received from various upstream data systems; wherein the names of the raw data files include the upstream data systems and the products to which they belong;

[0051] According to the names of the original data files, the original data files corresponding to the same product under the same upstream data system are classified into the same newly created data batch.

[0052] In one possible implementation manner, the verification unit is further configured to:

[0053] Acquire header information of the original data file, wherein the header information includes fields of the original data record;

[0054] Acquire, from the header information, a field position corresponding to a field that is consistent with a specified template field in the outbound call data template;

[0055] Verifying, based on the data recording rule of the designated template field, whether the data at the corresponding field position in the original data record complies with the data recording rule;

[0056] If the data in the field position corresponding to each specified template field in the original data record complies with the data record rules, it is determined that the corresponding original data record has passed the verification; otherwise, it is determined that the corresponding original data record has failed the verification, and the reason for failure to pass the verification is recorded.

[0057] In a possible implementation manner, the processing unit is further configured to:

[0058] Every time an outbound call data record is stored, the number of valid customers in the corresponding data batch is accumulated by one;

[0059] When all original data files in the data batch have been verified, the status of the corresponding data batch is set to be in effect for use by the outbound call service.

[0060] In a third aspect, an embodiment of the present invention further provides an outbound calling platform, including:

[0061] at least one processor, and

[0062] a memory coupled to the at least one processor;

[0063] The memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the method as described in the first aspect above by executing the instructions stored in the memory.

[0064] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, comprising:

[0065] Memory,

[0066] The memory is used to store instructions. When the instructions are executed by the processor, the device including the computer-readable storage medium performs the method as described in the first aspect above.

[0067] In a fifth aspect, an embodiment of the present invention further provides a computer program product comprising computer-executable instructions, wherein the computer-executable instructions are used to enable a computer to execute the method described in the first aspect.

[0068] Through the technical solutions in one or more of the above embodiments of the present invention, the embodiments of the present invention have at least the following technical effects:

[0069] In the embodiment provided by the present invention, a data batch is created by dividing the multiple original data files to be processed according to the upstream data system and the product to which they belong; the current outbound data template of the product corresponding to the data batch is obtained from the outbound data template library; based on the current outbound data template, each original data file in the data batch is subjected to content parsing and legality verification; the original data records that have passed the verification in the original data files are used as outbound data records and stored in the outbound database of the outbound call platform. Since the above-mentioned processing process, whether it is the data docking between the outbound call platform and the upstream data system, or the outbound call platform processing the original data records to obtain the outbound call data records, is completed using the outbound call data template obtained by the common basic fields configured by the outbound call platform and the custom fields specific to the business scenario configured by the upstream data system, when the business scenario changes, it is only necessary to add or modify the corresponding outbound call data template to correctly complete the data docking between the two parties. When the demand for the outbound call business changes, the secondary split fields in the outbound call data template can be modified or added to adjust the outbound call business. The entire process does not require modifying the program code of the outbound call platform, and can adapt to the different needs of the business scenario in a timely manner. Therefore, while quickly responding to business needs, the outbound call platform system remains stable, thereby reducing the system risk and business risk of the outbound call platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] Figure 1 A flowchart of outbound call data processing provided by an embodiment of the present invention;

[0071] Figure 2 A schematic diagram illustrating the relationship between Bank A's outbound call platform and its branches and sub-branches, provided in an embodiment of the present invention;

[0072] Figure 3 A schematic diagram of the structure of an outbound calling platform provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0073] The embodiments of the present invention provide a method for processing outbound call data, an outbound call platform, and a computer-readable storage medium to solve the technical problem of high system risk and business risk of the outbound call platform in the prior art.

[0074] In order to better understand the above technical solution, the technical solution of the present invention is described in detail below through the accompanying drawings and specific embodiments. It should be understood that the embodiments of the present invention and the specific features in the embodiments are detailed descriptions of the technical solution of the present invention, rather than limitations of the technical solution of the present invention. In the absence of conflict, the technical features in the embodiments of the present invention and the embodiments can be combined with each other. The acquisition, storage, use, and processing of data in the technical solution of this application comply with the relevant provisions of national laws and regulations.

[0075] Please refer to Figure 1, an embodiment of the present invention provides a method for processing outbound call data, which is applied to an outbound call platform. The processing process of the method is as follows.

[0076] Step 101: Create data batches for multiple raw data files to be processed according to their upstream data systems and products. The raw data files are generated based on the outbound call data template provided by the outbound call platform. The basic fields common to each outbound call data template and the secondary split fields for different outbound call services are configured in the outbound call platform. The custom fields related to different business scenarios are configured in the upstream data system. One outbound call data template corresponds to one business scenario.

[0077] Creating data batches based on the upstream data systems and products to which multiple raw data files to be processed can be achieved in the following ways:

[0078] See Figure 2 A schematic diagram illustrating the relationship between Bank A's outbound calling platform and its branches and sub-branches, provided in an embodiment of the present invention.

[0079] Bank A has n branches across the country, and each branch includes multiple sub-branches. For example, Branch 1 includes Sub-branches 1 to M, and Branch n includes Sub-branches 1 to K. Each branch and sub-branch under Bank A needs to provide original data files to Bank A's outbound call platform. The data systems of these branches and sub-branches are called upstream data systems.

[0080] Users can configure outbound call data templates for various business scenarios through the template configuration page in the outbound call platform. Specifically, they can configure the basic fields that each outbound call data template should include, as well as secondary split fields for different outbound call businesses. For custom fields, users can provide optional fields to upstream data systems and specify the total number of custom fields. After the outbound call platform synchronizes the configured outbound call data templates with the upstream data system, the outbound call platform can configure the required fields in the custom fields to meet the needs of different business scenarios. For example, if the outbound call platform is configured with 10 basic fields and 6 secondary split fields, each outbound call data template synchronized to the upstream data system should include the 10 basic fields configured by the outbound call platform. For example, Branch 1 and Branch 3 define 3 custom fields for Business Scenario 1, and Branch 3 defines 1 custom field for Business Scenario 5. In the raw data file provided by Branch 1 to the outbound call platform for Business Scenario 1, each raw data record contains data for the 10 basic fields and 3 custom fields. In the raw data file provided by Branch 3 to the outbound call platform for Business Scenario 5, each raw data record contains data for the 10 basic fields and 1 custom field. The raw data files for other business scenarios can be derived similarly.

[0081] Regularly scan multiple raw data files received from various upstream data systems; the names of the raw data files include the upstream data system and the product to which they belong; based on the names of the raw data files, the raw data files corresponding to the same product under the same upstream data system are classified into the same newly created data batch.

[0082] For example, Figure 2 The original data files provided by branch 1 to the outbound call platform include original data files 1A to 1F, among which original data files 1A, 1C and 1E all belong to product A; the original data files provided by branch 3 to the outbound call platform include original data files 3A to 3F, among which original data files 3C, 3D and 3E all belong to product A. The above original data files belonging to branch 1 and product A are created into a data batch 1A (including original data files 1A, 1C and 1E), and the above original data files belonging to branch 3 and product A are created into another data batch 3A (including original data files 3C, 3D and 3E).

[0083] In the embodiment provided by the present invention, by creating multiple original data files belonging to the same product in the same upstream data system into a data batch, it is convenient to batch process the original data files from the same business scenario in the same upstream data system, thereby improving work efficiency. And by using the common basic fields configured by the outbound call platform and the outbound call data template obtained by the custom fields unique to the business scenario configured by the upstream data system to connect data between the outbound call platform and the upstream data system, when there is a change in the business scenario, only the corresponding outbound call data template needs to be added or modified to correctly complete the data connection between the two parties. The entire process does not require modifying the program code of the outbound call platform, and can adapt to the different needs of the business scenario in a timely manner, thereby keeping the outbound call platform system stable while quickly responding to business needs, thereby reducing the system risk and business risk of the outbound call platform.

[0084] Before creating data batches for multiple raw data files to be processed according to their upstream data systems and products, you must first configure an outbound call data template for data connection between the upstream data system and the outbound call platform. This can be achieved in the following ways:

[0085] Based on the information entered by the user in the template configuration page, an outbound call data template corresponding to the business scenario is generated; wherein, the target configuration page is used for the user to configure the outbound call data template for different business scenarios; each newly generated outbound call data template is synchronized to the upstream data system that provides the original data file for the outbound call platform, so that the upstream data system exports data according to the data template corresponding to the business scenario to form the original data file.

[0086] The outbound call data template includes field types and field attributes.

[0087] Field types include: basic fields, custom fields, and secondary split fields. Basic fields serve as the basis for data export from upstream data systems. Custom fields are fields added by upstream data systems for different business scenarios when exporting data. Secondary split fields are fields used by outbound call operators to filter outbound call data records from the outbound call database when performing outbound call services.

[0088] Field attributes include: whether to desensitize, desensitization rules, whether required, whether to display, and data type.

[0089] Typically, template fields in the basic fields are included in the outbound call data template for each business scenario. Upstream data systems can use these as specifications (i.e., basis) for data export. Users can configure the Chinese and English names of each field in the basic field configuration on the template configuration page.

[0090] For example, basic fields can include basic information and custom information. Basic information can include multiple fields (denoted as basic information field 1 to basic information field n), and custom information can also include multiple fields (denoted as custom information field 1 to custom information field m). Please refer to Table 1 for basic field configuration information. After completing the configuration of basic fields as shown in Table 1, the basic fields in each outbound call data template will include the template fields in Table 1. In the generated raw data file, the corresponding template fields will use the corresponding Chinese or English names configured in Table 1 as the raw data.

[0091]

[0092] It should be noted that the corresponding template fields in the basic information and custom information in Table 1 are different, and the corresponding Chinese and English names are also different. For example, the Chinese name 1 and English name 1 corresponding to the basic information field 1 cannot be equated with the Chinese name 1 and English name 1 corresponding to the custom information field 1.

[0093] For custom fields in the outbound call data template, the upstream data system can customize the corresponding Chinese and English names according to the needs of different business scenarios and configure the field attributes of the custom fields. Please refer to Table 2 for the configuration information of the field attributes of the custom fields provided in this embodiment of the present invention.

[0094] Table 2

[0095]

[0096] In Table 2, whether to desensitize is used to determine whether to desensitize the data of the custom field when displaying data later. If the field is to be displayed desensitized, the range corresponding to the desensitization can be specified.

[0097] Desensitization rules are used to specify the desensitization rules. The supported desensitization rules include desensitizing specified information. For example, you can specify to desensitize information 1, or you can specify to desensitize information 1 and information 3. The specific settings can be freely set by the user of the upstream data system.

[0098] Whether it is required is used to indicate whether the corresponding custom field is required in the process of executing outbound call business processing.

[0099] Whether to display is used to indicate whether the corresponding custom field should be displayed during the outbound call processing process. If display is required, the scope of the display object can also be specified.

[0100] Data type is used to indicate the data type that the corresponding custom field can support, such as strings, numbers, dates, etc. In the process of executing outbound call business, the outbound call platform can verify the various data corresponding to the custom field according to the data type configured for the custom field to determine whether the data corresponding to the custom field is legal.

[0101] For example, an outbound call data template may include 10 custom fields. In an upstream data system (a branch), for a new requirement of the business scenario of its product B, a custom field in the outbound call data template of the business scenario is defined with the Chinese name being Chinese name B and the English name being English name B. The field attributes of the custom field include several field attributes shown in Table 2. The values of these field attributes can be represented using the values corresponding to the encoding in Table 2. For example, if the desensitization rule of this custom field is configured as "Information 3 Encoding", then when generating the original data file, the desensitization rule of this custom field is to desensitize the data containing Information 3 in this field.

[0102] In addition to the basic fields required by all outbound call data templates pre-defined in the outbound call platform, as well as custom fields defined in the upstream data system to meet the system requirements of different business scenarios, the outbound call data template also includes secondary split fields defined in the outbound call platform for different outbound call businesses. By configuring the secondary split fields differently, the required outbound call data records can be split for different outbound call businesses for use by outbound call business personnel.

[0103] In addition to the field attributes in the custom field, the field attributes of the secondary split field can also include the split type. Different split types correspond to different split rules. Please refer to Table 3 for the configuration information of the split type provided in the embodiment of the present invention.

[0104] Table 3

[0105]

[0106] Please refer to Table 4 for configuration information of the customer care outbound call data template provided in an embodiment of the present invention.

[0107] Table 4

[0108]

[0109]

[0110] Please refer to Table 5 for local data records in an upstream data system provided in an embodiment of the present invention.

[0111] Table 5

[0112] Serial number Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 1 Data 11 Data 21 Data 31 Data 41 Data 51 Data 61 2 Data 12 Data 22 Data 32 Data 42 Data 52 Data 62 3 Data 13 Data 23 Data 33 Data 43 Data 53 Data 63 … … … … … … … q Data 1q Data 2q Data 3q Data 4Q Data 5q Data 6q

[0113] In an outbound call data template, the basic fields include fields 3 to 5, and the custom fields include field 1. The upstream data system extracts data from the local data records (Table 5) based on this outbound call data template to form an original outbound call data file, as shown in Table 6. Table 6 is the original data record table of the outbound call data file provided in an embodiment of the present invention.

[0114] Table 6

[0115] Serial number Field 1 Field 3 Field 4 Field 5 1 Data 11 Data 31 Data 41 Data 51 2 Data 12 Data 32 Data 42 Data 52 3 Data 13 Data 33 Data 43 Data 53 … … … … … q Data 1q Data 3q Data 4Q Data 5q

[0116] After receiving the original data files provided by each upstream data system, the outbound call platform can be switched to a designated location, periodically scanning the original data files to be processed stored in the designated location, and creating corresponding data batches according to the upstream data system to which the original data files belong and the product.

[0117] After the data batch is created, step 102 may be executed.

[0118] Step 102: Obtain the current outbound call data template of the product corresponding to the data batch from the outbound call data template library; wherein the outbound call data template library is used to store the outbound call data template corresponding to each business scenario, and one business scenario corresponds to one product.

[0119] For example, the data batch includes original data files 1 to original data files 3, and the corresponding product is product A. According to the product number of product A, the corresponding current outbound call data template is obtained from the outbound call data template library of the outbound call platform.

[0120] After obtaining the current outbound call data template corresponding to the data batch, steps 103 and 104 may be executed.

[0121] Step 103: Based on the current outbound call data template, perform content analysis and legality verification on each original data file in the data batch.

[0122] Step 104: The original data records that have passed verification in the original data file are used as outbound call data records and stored in the outbound call database of the outbound call platform.

[0123] Based on the current outbound call data template, content parsing and legality verification are performed on each raw data file in the data batch. This can be achieved through the following methods:

[0124] Obtain the header information of the original data file, which includes the fields of the original data record; obtain the field position corresponding to the field consistent with the specified template field in the outbound call data template from the header information; verify whether the data at the corresponding field position in the original data record complies with the data recording rule according to the data recording rule of the specified template field; if the data at the field position corresponding to each specified template field in the original data record complies with the data recording rule, determine that the corresponding original data record has passed the verification; otherwise, determine that the corresponding original data record has failed the verification, and record the reason for failure to pass the verification.

[0125] After the original data records that have passed verification in the original data file are stored as outbound call data records in the outbound call database of the outbound call platform, the following is also included:

[0126] Each time an outbound call data record is stored, the number of valid customers in the corresponding data batch is increased by one; when all original data files in the data batch have been verified, the status of the corresponding data batch is set to "effective" for use by outbound call services.

[0127] For example, taking Table 6 as an example, the first row in Table 6 is recorded as the header information of the original data file, and each row after the header is an original data record. Each row of the original data record includes original data corresponding to each field in the header. By comparing each field in the header information with each field in the corresponding outbound call data template, the field type of each field in the header information can be determined. For example, if field 1 in Table 6 is successfully compared with field 1 in the outbound call data template, and the field type of field 1 in the outbound call data template is a basic field, it can be determined that a column of original data corresponding to field 1 in Table 6 (number 11 to data 1q) should comply with the data recording rules of field 1 in the basic field. If it does not comply, it is determined to be illegal data, and the corresponding original data record fails the verification and cannot be stored in the outbound call database of the outbound call platform, and the reason for the verification failure is recorded; if each original data in a certain original data record complies with the data recording rules of the corresponding template field, it is determined that this original data record complies with the data recording rules, passes the verification, and this original data record is stored in the outbound call database of the outbound call platform for use by the outbound call service, and the number of valid customers of this data batch is accumulated by 1. When all original data files in this data batch have completed the verification, its status is set to be effective.

[0128] In the embodiment provided by the present invention, the original data file is parsed through the outbound call data template and each original data record is verified, which can prevent dirty data from being stored in the outbound call platform, thereby avoiding the reading of invalid data when executing outbound call services and improving work efficiency.

[0129] When the outbound call platform processes the original data files in the data batch, it can also set the status of the data batch. For example, after creating the data batch, its status can be set to the cleaning status, and after completing the parsing and verification of all the original data files in the data batch, the status of the data batch can be set to be effective. In this way, the status of each data batch can be understood in a timely manner.

[0130] In the embodiment provided by the present invention, a data batch is created by dividing the multiple original data files to be processed according to the upstream data system and the product to which they belong; the current outbound data template of the product corresponding to the data batch is obtained from the outbound data template library; based on the current outbound data template, each original data file in the data batch is subjected to content parsing and legality verification; the original data records that have passed the verification in the original data files are used as outbound data records and stored in the outbound database of the outbound call platform. Since the above-mentioned processing process, whether it is the data docking between the outbound call platform and the upstream data system, or the outbound call platform processing the original data records to obtain the outbound call data records, is completed using the outbound call data template obtained by the common basic fields configured by the outbound call platform and the custom fields specific to the business scenario configured by the upstream data system, when the business scenario changes, it is only necessary to add or modify the corresponding outbound call data template to correctly complete the data docking between the two parties. When the demand for the outbound call business changes, the secondary split fields in the outbound call data template can be modified or added to adjust the outbound call business. The entire process does not require modifying the program code of the outbound call platform, and can adapt to the different needs of the business scenario in a timely manner. Therefore, while quickly responding to business needs, the outbound call platform system remains stable, thereby reducing the system risk and business risk of the outbound call platform.

[0131] Based on the same inventive concept, an embodiment of the present invention provides an outbound call platform. The specific implementation of the outbound call data processing method of the outbound call platform can be found in the description of the method embodiment part. The repeated parts will not be repeated. Figure 3 , the outbound calling platform includes:

[0132] A creation unit 301 is configured to create data batches from multiple raw data files to be processed according to their respective upstream data systems and products; wherein the raw data files are generated based on outbound call data templates provided by the outbound call platform, wherein the basic fields common to each outbound call data template and the secondary split fields for different outbound call services are configured in the outbound call platform, and the custom fields related to different business scenarios are configured in the upstream data system, with each outbound call data template corresponding to each business scenario;

[0133] The acquisition unit 302 is configured to acquire the current outbound call data template for the product corresponding to the data batch from an outbound call data template library; wherein the outbound call data template library is configured to store outbound call data templates corresponding to various business scenarios, with one business scenario corresponding to one product;

[0134] The processing unit 303 is used to perform content parsing and legality verification on each original data file in the data batch according to the current outbound call data template; and store the original data records that pass the verification in the original data file as outbound call data records in the outbound call database of the outbound call platform.

[0135] In a possible implementation method, the outbound call platform further includes a configuration unit 304, wherein the configuration unit 304 is configured to:

[0136] Generate an outbound call data template corresponding to the business scenario based on the information entered by the user in the template configuration page; wherein the target configuration page is used for the user to configure the outbound call data template for different business scenarios;

[0137] Each newly generated outbound call data template is synchronized to the upstream data system that provides the original data file for the outbound call platform, so that the upstream data system exports data according to the data template of the corresponding business scenario to form the original data file.

[0138] In a possible implementation manner, the outbound call data template includes:

[0139] Field types and field properties.

[0140] In a possible implementation, the field type includes:

[0141] The basic fields, the custom fields, and the secondary split fields; the basic fields are the basis for the upstream data system to export data, the custom fields are the fields added by the upstream data system for different business scenarios when exporting data, and the secondary split fields are the fields used by outbound call operators to filter outbound call data records from the outbound call database when performing outbound call services.

[0142] In a possible implementation, the field attributes include:

[0143] Whether to desensitize, desensitization rules, whether required, whether to display, data type.

[0144] In a possible implementation manner, the field attributes of the secondary split field further include a split type, and different split types correspond to different split rules.

[0145] In a possible implementation manner, the creating unit 301 is further configured to:

[0146] Periodically scanning a plurality of raw data files received from various upstream data systems; wherein the names of the raw data files include the upstream data systems and the products to which they belong;

[0147] According to the names of the original data files, the original data files corresponding to the same product under the same upstream data system are classified into the same newly created data batch.

[0148] In a possible implementation manner, the processing unit 303 is further configured to:

[0149] Acquire header information of the original data file, wherein the header information includes fields of the original data record;

[0150] Acquire, from the header information, a field position corresponding to a field that is consistent with a specified template field in the outbound call data template;

[0151] Verifying, based on the data recording rule of the designated template field, whether the data at the corresponding field position in the original data record complies with the data recording rule;

[0152] If the data in the field position corresponding to each specified template field in the original data record complies with the data record rules, it is determined that the corresponding original data record has passed the verification; otherwise, it is determined that the corresponding original data record has failed the verification, and the reason for failure to pass the verification is recorded.

[0153] In a possible implementation manner, the processing unit 303 is further configured to:

[0154] Every time an outbound call data record is stored, the number of valid customers in the corresponding data batch is accumulated by one;

[0155] When all original data files in the data batch have been verified, the status of the corresponding data batch is set to be in effect for use by the outbound call service.

[0156] It should be noted that the division of units in the embodiments of the present application is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0157] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0158] It should be noted here that the above-mentioned device provided by the embodiment of the present invention can implement all the method steps implemented by the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0159] Based on the same inventive concept, an embodiment of the present invention provides an outbound call platform, comprising: at least one processor, and

[0160] a memory coupled to the at least one processor;

[0161] The memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the method for processing outbound call data as described above by executing the instructions stored in the memory.

[0162] Based on the same inventive concept, an embodiment of the present invention further provides a computer-readable storage medium, comprising:

[0163] Memory,

[0164] The memory is used to store instructions. When the instructions are executed by the processor, the device including the computer-readable storage medium completes the outbound call data processing method as described above.

[0165] The readable storage medium can be any available medium or data storage device that the processor can access, including volatile memory or non-volatile memory, or can include both volatile memory and non-volatile memory. As an example and not limitation, non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory, solid state drive (SSD), magnetic storage (such as floppy disk, hard disk, tape, magneto-optical disc (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.). Volatile memory can include random access memory (RAM), which can act as external cache memory. By way of example and not limitation, RAM is available in various forms, such as dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), and synchronous link DRAM (SLDRAM). The memory devices of the disclosed aspects are intended to include, but are not limited to, these and other suitable types of memory.

[0166] Based on the same inventive concept, an embodiment of the present invention provides a computer program product, which includes program code. When the program product is run on a computer device, the program code is used to enable the computer device to execute the steps of the method for processing outbound call data according to various exemplary embodiments of the present application described above in this specification.

[0167] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or program products. Therefore, embodiments of the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, embodiments of the present invention may take the form of a machine program product implemented on one or more computer / processor-usable readable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing program code.

[0168] The embodiments of the present invention are described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the process in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0169] These program instructions may also be stored in a readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0170] These program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer / processor-implemented process, thereby providing instructions for executing on the computer / processor or other programmable device to implement the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

[0171] Obviously, those skilled in the art may make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if such changes and modifications fall within the scope of the claims and their equivalents, the present invention is intended to include such changes and modifications.

Claims

1. A method for processing outbound call data, applied to an outbound call platform, characterized in that: include: Create data batches for multiple raw data files to be processed according to their upstream data systems and products; wherein, the raw data files are generated based on the outbound call data template provided by the outbound call platform, the basic fields common to all outbound call data templates and the secondary split fields for different outbound call services are configured in the outbound call platform, and the custom fields related to different business scenarios are configured in the upstream data system, and one outbound call data template corresponds to one business scenario; the outbound call data template is a data template used for outbound call services in the outbound call platform, the basic fields are the fields common to all outbound call data templates, the secondary split fields are the fields used by outbound call operators to filter outbound call data records from the outbound call database when performing outbound call services, and the custom fields are fields defined according to corresponding business scenarios; Obtaining the current outbound call data template of the product corresponding to the data batch from an outbound call data template library; wherein the outbound call data template library is used to store outbound call data templates corresponding to various business scenarios, and one business scenario corresponds to one product; According to the current outbound call data template, each original data file in the data batch is parsed and verified for legitimacy; The original data records that have passed the verification in the original data file are used as outbound call data records and stored in the outbound call database of the outbound call platform.

2. The method according to claim 1, wherein Before creating data batches from the plurality of raw data files to be processed according to their upstream data systems and products, the method further includes: Generate an outbound call data template corresponding to the business scenario based on the information entered by the user in the template configuration page; wherein the template configuration page is used for the user to configure the outbound call data template for different business scenarios; Each newly generated outbound call data template is synchronized to the upstream data system that provides the original data file for the outbound call platform, so that the upstream data system exports data according to the data template of the corresponding business scenario to form the original data file.

3. The method according to claim 2, wherein The outbound call data template includes: Field types and field properties.

4. The method according to claim 3, wherein The field types include: The basic fields, the custom fields, and the secondary split fields; the basic fields are the basis for the upstream data system to export data, the custom fields are the fields added by the upstream data system for different business scenarios when exporting data, and the secondary split fields are the fields used by outbound call operators to filter outbound call data records from the outbound call database when performing outbound call services.

5. The method according to claim 3, wherein The field attributes include: Whether to desensitize, desensitization rules, whether required, whether to display, data type.

6. The method according to claim 5, wherein The field attributes of the secondary split field also include a split type, and different split types correspond to different split rules.

7. The method according to any one of claims 1 to 6, wherein: Create data batches for multiple raw data files to be processed according to their upstream data systems and products, including: Periodically scanning a plurality of raw data files received from various upstream data systems; wherein the names of the raw data files include the upstream data systems and the products to which they belong; According to the names of the original data files, the original data files corresponding to the same product under the same upstream data system are classified into the same newly created data batch.

8. The method according to claim 7, wherein According to the current outbound call data template, each original data file in the data batch is parsed and verified for legitimacy, including: Acquire header information of the original data file, wherein the header information includes fields of the original data record; Acquire, from the header information, a field position corresponding to a field that is consistent with a specified template field in the outbound call data template; Verifying, based on the data recording rule of the designated template field, whether the data at the corresponding field position in the original data record complies with the data recording rule; If the data in the field position corresponding to each specified template field in the original data record complies with the data record rules, it is determined that the corresponding original data record has passed the verification; otherwise, it is determined that the corresponding original data record has failed the verification, and the reason for failure to pass the verification is recorded.

9. The method according to claim 8, wherein After the original data records that have passed verification in the original data file are stored as outbound call data records in the outbound call database of the outbound call platform, the method further includes: Every time an outbound call data record is stored, the number of valid customers in the corresponding data batch is accumulated by one; When all original data files in the data batch have been verified, the status of the corresponding data batch is set to be in effect for use by the outbound call service.

10. An outbound calling platform, characterized in that: include: A creation unit is configured to create data batches for multiple raw data files to be processed according to their respective upstream data systems and products; wherein, the raw data files are generated according to the outbound call data template provided by the outbound call platform, the basic fields common to all outbound call data templates and the secondary split fields for different outbound call services are configured in the outbound call platform, the custom fields related to different business scenarios are configured in the upstream data system, and one outbound call data template corresponds to one business scenario; the outbound call data template is a data template used for outbound call services in the outbound call platform, the basic fields are the fields common to all outbound call data templates, the secondary split fields are the fields used by outbound call operators to filter outbound call data records from the outbound call database when performing outbound call services, and the custom fields are fields defined according to corresponding business scenarios; an acquisition unit, configured to acquire the current outbound call data template of the product corresponding to the data batch from an outbound call data template library; wherein the outbound call data template library is configured to store outbound call data templates corresponding to various business scenarios, with one business scenario corresponding to one product; The processing unit is used to parse the content and verify the legitimacy of each original data file in the data batch based on the current outbound call data template; the original data records that have passed the verification in the original data file are used as outbound call data records and stored in the outbound call database of the outbound call platform.

11. An outbound calling platform, characterized in that: include: at least one processor, and a memory coupled to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the method according to any one of claims 1 to 9 by executing the instructions stored in the memory.

12. A computer-readable storage medium, characterized in that: Including memory, The memory is used to store instructions, and when the instructions are executed by the processor, the device including the computer-readable storage medium performs the method according to any one of claims 1 to 9.

13. A computer program product, characterized in that The method comprises computer-executable instructions for causing a computer to execute the method according to any one of claims 1 to 9.

Images