Outbound call data processing method, device, equipment and medium

Abstract

The present application relates to the field of intelligent service technology, and specifically to an outbound call data processing method, apparatus, device, and medium, which are used to solve the problem of high workload and low efficiency of existing outbound call data processing methods. The method comprises: obtaining an outbound call data set from a target data source, wherein the outbound call data set comprises a version number and a plurality of outbound call data, wherein the outbound call data comprises content corresponding to different attributes; determining the rule information of each attribute corresponding to the version number based on the correspondence between the pre-set version number and the rule information of each attribute; for any outbound call data, if the content corresponding to each attribute in the any outbound call data satisfies the rule information of the attribute, then determining that the outbound call data has passed verification.

Description

Technical Field

[0001] The present disclosure relates to the field of intelligent service technology, and in particular to an outbound call data processing method, device, equipment, and medium. Background Art

[0002] With the development of artificial intelligence (AI), outbound calling has become a key customer engagement channel. While maintaining the traditional manual outbound calling model, intelligent outbound calling is rapidly gaining momentum. As a system supporting the growth of outbound calling, efficiently processing outbound call data from different business types is crucial to the development of this business.

[0003] There are two main methods currently available: The first is to develop an information expression method for the outbound call data set of each type of telephone outbound call service, along with a corresponding verification and processing method. For example, when adding an outbound call data set of a new service type, a whole set of corresponding information expression methods is rewritten, and based on the information expression method, a corresponding method for verifying each outbound call data of the outbound call data set is determined. However, this outbound call data processing method is labor-intensive and has low flexibility. The second is to use a custom method, for example, using a domain-specific language (DSL) to write a processing engine to process outbound call data of different service types. However, this outbound call data processing method is highly complex and places high demands on users, requiring an understanding of the syntax and semantics of DSL, making it difficult to promote. Summary of the Invention

[0004] The embodiments of the present application provide an outbound call data processing method, apparatus, device, and medium for reducing workload and improving outbound call data processing efficiency.

[0005] In a first aspect, the present application provides a method for processing outbound call data, the method comprising:

[0006] Obtain an outbound call data set from a target data source, the outbound call data set including a version number and multiple outbound call data, the outbound call data including content corresponding to different attributes;

[0007] Determine the rule information of each attribute corresponding to the version number according to the preset correspondence between the version number and the rule information of each attribute;

[0008] For any piece of outbound call data, if the content corresponding to each attribute in the any piece of outbound call data satisfies the rule information of the attribute, it is determined that the outbound call data has passed the verification.

[0009] The technical solution provided by the embodiments of this application can determine the rule information corresponding to each attribute based on the version number in the outbound call data set from different data sources, and verify the content corresponding to each attribute in each piece of outbound call data based on the rule information of the attribute. This can support different types of business information in each piece of outbound call data, thereby reducing workload and improving outbound call data processing efficiency. In addition, the technical solution provided by the embodiments of this application is text-based, which is easy to promote.

[0010] In a possible embodiment, the method further includes:

[0011] If the content corresponding to each attribute in any of the outbound call data does not satisfy the rule information of the attribute, it is determined that the outbound call data verification has failed, and the corresponding verification failure result is obtained and displayed, wherein the verification failure result includes part or all of the following information: the reason for verification failure, the outbound call data sequence number and the attribute identifier corresponding to the attribute that failed verification determined according to the rule information of each attribute.

[0012] The technical solution provided by the embodiment of the present application can display the verification failure result to the user when the outbound call data verification fails, so that the user can take corresponding measures.

[0013] In a possible embodiment, determining the rule information of each attribute corresponding to the version number according to a preset correspondence between the version number and the rule information of each attribute includes:

[0014] Determine the rule information to be verified for each attribute corresponding to the version number according to the preset correspondence between the version number and the rule information of each attribute;

[0015] Determine whether the to-be-verified rule information of each attribute satisfies the set verification conditions;

[0016] If so, the rule information to be verified for each attribute is used as the rule information for each attribute.

[0017] The technical solution provided by the embodiment of the present application can verify the rule information to be verified of each attribute determined based on the version number according to the set verification conditions, and obtain the rule information of each attribute to ensure the accuracy of the rule information of each attribute.

[0018] In a possible embodiment, determining whether the to-be-verified rule information of each attribute satisfies a set verification condition includes:

[0019] If the attribute's to-be-verified rule information includes a version number, and the version number is within a set range, determining that the attribute's to-be-verified rule information meets the set verification condition;

[0020] If the attribute's rule information to be verified includes the number of basic information fields, and the number of basic information fields is not greater than a set threshold, then determining that the attribute's rule information to be verified meets the set verification condition;

[0021] If the attribute's to-be-verified rule information includes the number of contact information groups and the number of fields in each contact information group, and the number of contact information groups is not greater than a set first threshold, and the number of fields in each contact information group is not greater than a set first field threshold, then determining that the attribute's to-be-verified rule information meets the set verification condition;

[0022] If the attribute's rule information to be verified includes the number of business information groups and the number of fields in each business information group, and the number of business information groups is not greater than a set second threshold, and the number of fields in each business information group is not greater than a set second field threshold, then it is determined that the attribute's rule information to be verified meets the set verification condition, wherein the second threshold is greater than the first threshold, and the second field threshold is greater than the first field threshold;

[0023] If the attribute's rule information to be verified includes attribute identifiers and attribute identifier fields corresponding to each attribute, the number of attribute identifier fields is equal to the sum of the number of basic information fields, the number of contact information fields, and the number of business information fields, and the attribute identifier corresponding to each attribute is not empty, then it is determined that the attribute's rule information to be verified meets the set verification condition; wherein the number of contact information fields is obtained by the number of contact information groups and the number of fields in each contact information group, and the number of business information fields is obtained by the number of business information groups and the number of fields in each business information group.

[0024] The technical solution provided by the embodiments of the present application can verify the rule information to be verified of each attribute according to the verification conditions of the attribute, and obtain the rule information of each attribute to ensure the accuracy of the rule information of each attribute.

[0025] In a possible embodiment, whether the content corresponding to each attribute in any one piece of outbound call data satisfies the rule information of the attribute is determined by the following method:

[0026] If the content corresponding to any attribute in the outbound call data includes multiple groups of data, and the number of groups of the content corresponding to the attribute is not greater than the number of groups in the rule information of the attribute, and the number of fields in each group of data is not greater than the number of fields in the corresponding group in the rule information of the attribute, then it is determined that the content corresponding to the attribute in the outbound call data satisfies the rule information of the attribute;

[0027] If the content corresponding to any attribute in the outbound call data includes a group of data, and the number of fields in the group of data is not greater than the number of fields in the rule information of the attribute, it is determined that the content corresponding to the attribute in the outbound call data meets the rule information of the attribute.

[0028] The technical solution provided by the embodiments of the present application can verify the content corresponding to each attribute in any outbound call data using the rule information of the attribute to determine whether the outbound call data passes the verification, so as to ensure the accuracy of the content corresponding to each attribute in each outbound call data.

[0029] In a second aspect, the present application provides an outbound call data processing device, the device comprising:

[0030] An acquisition module, configured to acquire an outbound call data set from a target data source, wherein the outbound call data set includes a version number and multiple pieces of outbound call data, and the outbound call data includes content corresponding to different attributes;

[0031] A determination module, configured to determine the rule information of each attribute corresponding to the version number according to a preset correspondence between the version number and the rule information of each attribute;

[0032] The verification module is configured to determine, for any piece of outbound call data, that the outbound call data has passed verification if the content corresponding to each attribute in the piece of outbound call data satisfies the rule information of the attribute.

[0033] In a possible embodiment, the device further includes:

[0034] A display module is used to determine that the outbound call data verification has failed if the content corresponding to each attribute in any of the outbound call data does not satisfy the rule information of the attribute, and obtain and display the corresponding verification failure result, wherein the verification failure result includes part or all of the following information: the reason for the verification failure, the outbound call data sequence number and the attribute identifier corresponding to the attribute that failed the verification determined according to the rule information of each attribute.

[0035] In a possible embodiment, the determining module is configured to determine the rule information of each attribute corresponding to the version number based on a preset correspondence between the version number and the rule information of each attribute, including:

[0036] Determine the rule information to be verified for each attribute corresponding to the version number according to the preset correspondence between the version number and the rule information of each attribute;

[0037] Determine whether the to-be-verified rule information of each attribute satisfies the set verification conditions;

[0038] If so, the rule information to be verified for each attribute is used as the rule information for each attribute.

[0039] In a possible embodiment, the determining module is configured to determine whether the to-be-verified rule information of each attribute satisfies a set verification condition, including:

[0040] If the attribute's to-be-verified rule information includes a version number, and the version number is within a set range, determining that the attribute's to-be-verified rule information meets the set verification condition;

[0041] If the attribute's rule information to be verified includes the number of basic information fields, and the number of basic information fields is not greater than a set threshold, then determining that the attribute's rule information to be verified meets the set verification condition;

[0042] If the attribute's to-be-verified rule information includes the number of contact information groups and the number of fields in each contact information group, and the number of contact information groups is not greater than a set first threshold, and the number of fields in each contact information group is not greater than a set first field threshold, then determining that the attribute's to-be-verified rule information meets the set verification condition;

[0043] If the attribute's rule information to be verified includes the number of business information groups and the number of fields in each business information group, and the number of business information groups is not greater than a set second threshold, and the number of fields in each business information group is not greater than a set second field threshold, then it is determined that the attribute's rule information to be verified meets the set verification condition, wherein the second threshold is greater than the first threshold, and the second field threshold is greater than the first field threshold;

[0044] If the attribute's rule information to be verified includes attribute identifiers and attribute identifier fields corresponding to each attribute, the number of attribute identifier fields is equal to the sum of the number of basic information fields, the number of contact information fields, and the number of business information fields, and the attribute identifier corresponding to each attribute is not empty, then it is determined that the attribute's rule information to be verified meets the set verification condition; wherein the number of contact information fields is obtained by the number of contact information groups and the number of fields in each contact information group, and the number of business information fields is obtained by the number of business information groups and the number of fields in each business information group.

[0045] In a possible embodiment, the verification module is configured to determine whether the content corresponding to each attribute in any one of the outbound call data satisfies the attribute rule information by:

[0046] If the content corresponding to any attribute in the outbound call data includes multiple groups of data, and the number of groups of the content corresponding to the attribute is not greater than the number of groups in the rule information of the attribute, and the number of fields in each group of data is not greater than the number of fields in the corresponding group in the rule information of the attribute, then it is determined that the content corresponding to the attribute in the outbound call data satisfies the rule information of the attribute;

[0047] If the content corresponding to any attribute in the outbound call data includes a group of data, and the number of fields in the group of data is not greater than the number of fields in the rule information of the attribute, it is determined that the content corresponding to the attribute in the outbound call data meets the rule information of the attribute.

[0048] In a third aspect, the present application provides an electronic device, comprising:

[0049] a memory for storing program instructions;

[0050] The processor is configured to call the program instructions stored in the memory and execute the steps included in any one of the methods of the first aspect according to the obtained program instructions.

[0051] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes any one of the methods according to the first aspect.

[0052] In a fifth aspect, the present application provides a computer program product, comprising: a computer program code, which, when executed on a computer, enables the computer to execute any one of the methods described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0054] Figure 1 is a schematic diagram of an application scenario according to an exemplary embodiment;

[0055] Figure 2 is a flow chart showing a method for processing outbound call data according to an exemplary embodiment;

[0056] Figure 3 is a specific flow chart of a method for processing outbound call data according to an exemplary embodiment;

[0057] Figure 4 is a schematic diagram showing an outbound call data set according to an exemplary embodiment;

[0058] Figure 5 is a module diagram illustrating outbound call data processing according to an exemplary embodiment;

[0059] Figure 6 is a schematic diagram showing rule information of various attributes according to an exemplary embodiment;

[0060] Figure 7 is a schematic diagram of an outbound call data processing device according to an exemplary embodiment;

[0061] Figure 8 is a schematic diagram of an electronic device showing a method for processing outbound call data according to an exemplary embodiment;

[0062] Figure 9 The diagram is a program product diagram showing a method for processing outbound call data according to an exemplary embodiment. DETAILED DESCRIPTION

[0063] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application. Unless there is a conflict, the embodiments in the present application and the features in the embodiments can be combined with each other in any way. In addition, although a logical order is shown in the flowchart, in some cases, the steps shown or described can be performed in an order different from that here.

[0064] The terms "first" and "second" in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of its variations are intended to cover non-exclusive protection. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. "Multiple" in this application can mean at least two, for example, two, three or more, and the embodiments of this application are not limited thereto.

[0065] In the technical solution of this application, the collection, dissemination, and use of data comply with the requirements of relevant national laws and regulations.

[0066] Before introducing the outbound call data processing method provided by the embodiment of the present application, in order to facilitate understanding, the technical background of the embodiment of the present application is first introduced in detail below.

[0067] Currently, there are two main methods for processing outbound call data. The first is to develop an information expression method for the outbound call data set of each type of telephone outbound call service, along with a corresponding verification and processing method. For example, when adding an outbound call data set for a new service type, a complete set of corresponding information expression methods is rewritten, and based on this information expression method, a corresponding method for verifying each outbound call data in that outbound call data set is determined. However, this outbound call data processing method is labor-intensive and has low flexibility. The second is to use a custom method, for example, using DSL to write a processing engine to process outbound call data of different service types. However, this outbound call data processing method is highly complex and requires high user experience, as it requires an understanding of the syntax and semantics of DSL, making it difficult to promote.

[0068] Therefore, in order to solve the above problems, the present disclosure provides an outbound call data processing method, device, equipment and medium for reducing workload and improving outbound call data processing efficiency.

[0069] First reference Figure 1 , which is a schematic diagram of an application scenario of an embodiment of the present disclosure, including a target data source 11, a server 12, and a database 13. Specifically, the target data source 11 is used to collect an outbound call dataset; the server 12 is used to verify the outbound call dataset obtained from the target data source 11; and the database 13 is used to store the verified outbound call data obtained from the server 12.

[0070] In the embodiment of the present disclosure, the server 12 obtains an outbound call data set from the target data source 11, wherein the outbound call data set includes a version number and multiple outbound call data, and the outbound call data includes content corresponding to different attributes; based on the correspondence between the preset version number and the rule information of each attribute, the rule information of each attribute corresponding to the version number is determined; for any outbound call data, if the content corresponding to each attribute in any outbound call data satisfies the rule information of the attribute, it is determined that the outbound call data verification has passed.

[0071] In an embodiment of the present disclosure, a method for processing outbound call data is provided. Based on the same concept, the present disclosure also provides an outbound call data processing device, an electronic device, a computer-readable storage medium, and a computer program product.

[0072] In some embodiments, the following describes an outbound call data processing method provided by the present disclosure through specific embodiments. Figure 2 Shown, including:

[0073] Step 201: Obtain an outbound call data set from a target data source. The outbound call data set includes a version number and multiple outbound call data. The outbound call data includes content corresponding to different attributes.

[0074] The version numbers in the outbound call datasets from different data sources are different.

[0075] Step 202: Determine the rule information for each attribute corresponding to the version number based on the preset correspondence between the version number and the rule information for each attribute.

[0076] The specific process is as follows:

[0077] Determine the rule information to be verified for each attribute corresponding to the version number according to the preset correspondence between the version number and the rule information of each attribute;

[0078] Determine whether the to-be-verified rule information of each attribute satisfies the set verification conditions;

[0079] If so, the rule information to be verified for each attribute is used as the rule information for each attribute.

[0080] If not, a verification failure result is obtained and displayed.

[0081] Step 203: For any piece of outbound call data, if the content corresponding to each attribute in the any piece of outbound call data satisfies the rule information of the attribute, it is determined that the outbound call data has passed verification.

[0082] If the content corresponding to each attribute in any of the outbound call data does not satisfy the rule information of the attribute, it is determined that the outbound call data verification fails, and a corresponding verification failure result is obtained and displayed.

[0083] The technical solution provided by the embodiments of the present application can determine the rule information corresponding to each attribute based on the version number in the outbound call data set from different data sources, and verify the content corresponding to each attribute in each piece of outbound call data based on the rule information of the attribute. This can support different types of business information in each piece of outbound call data, thereby reducing the workload and improving the efficiency of outbound call data processing. In addition, the technical solution provided by the embodiments of the present application is text-based, with low user requirements and easy promotion.

[0084] The following describes the specific steps of an outbound call data processing method provided by the present disclosure. Figure 3 Shown, including:

[0085] Step 301: Obtain an outbound call dataset from a target data source;

[0086] The outbound call data set includes a version number and multiple outbound call data items. The outbound call data items include content corresponding to different attributes. For example, content corresponding to basic attributes, contact attributes, and service attributes. Basic attributes include basic data, such as name and gender; contact attributes include multiple groups of contact data, such as the user's phone number, company phone number, contact person's phone number, and contact person's name; and service attributes include multiple groups of service data, each group of service data including a detailed description of the service in that group. Each group of service information can be of the same or different types, and the service information includes a detailed description of the service.

[0087] The outbound call datasets from different data sources have different version numbers and formats. Therefore, you can use the converter corresponding to the data source to convert the format, and get the following: Figure 4 The standard format outbound call data set shown in the figure includes version number A1 and 3 outbound call data. Among them, F1[0] in the first outbound call data is the content corresponding to this attribute.

[0088] Step 302: Determine the rule information to be verified for each attribute corresponding to the version number based on the preset correspondence between the version number and the rule information of each attribute.

[0089] like Figure 5 As shown, the outbound call dataset 1 of data source 1 is format-converted using converter 1, and based on the correspondence between the preset version number and the rule information of each attribute, the rule information to be verified for each attribute corresponding to version number 1 in the outbound call dataset 1 is determined; the outbound call dataset 2 of data source 2 is format-converted using converter 2 to obtain an outbound call dataset 2 in a standard format, and based on the correspondence between the preset version number and the rule information of each attribute, the rule information to be verified for each attribute corresponding to version number 2 in the outbound call dataset 2 is determined.

[0090] The information to be verified for each of the aforementioned attributes includes: version number, number of basic information fields, number of contact information groups, number of fields per contact information group, number of business information groups, number of fields per business information group, attribute identifiers corresponding to each attribute, and attribute identifier fields. The number of fields per contact information group can be the same or different, and the number of fields per business information group can be the same or different.

[0091] like Figure 6 As shown, after obtaining the version number A1 of the outbound call data set, the corresponding number of basic information fields B1, the number of contact information groups C1, the number of fields in each contact information group C2, the number of service information groups d, and the number of fields in each service information group D1, D2, ..., D d, attribute identifier E corresponding to each attribute i And attribute identification field E.

[0092] Step 303: determine whether the to-be-verified rule information of each attribute satisfies the set verification conditions. If so, execute step 304; otherwise, execute step 305.

[0093] like Figure 5 As shown, the to-be-verified rule information of each attribute is verified by the validator to see whether it meets the set verification conditions.

[0094] The following methods are used to determine whether the to-be-verified rule information of each attribute satisfies the set verification conditions:

[0095] If the attribute's to-be-verified rule information includes a version number, and the version number is within a set range, determining that the attribute's to-be-verified rule information meets the set verification condition;

[0096] The above setting range is the version number range allowed by the system. For example, if the attribute's pending rule information includes version number 001 and the setting range is 000-003, and the version number is within the setting range and is a positive integer, then it is determined that the attribute's pending rule information meets the set verification condition.

[0097] If the attribute's rule information to be verified includes the number of basic information fields, and the number of basic information fields is not greater than a set threshold, then determining that the attribute's rule information to be verified meets the set verification condition;

[0098] The above thresholds can be set based on actual conditions.

[0099] For example, if the number of basic information fields is 20, the set threshold is 25, and the number of basic information fields is not greater than the set threshold and is a positive integer, it is determined that the rule information to be verified of the attribute meets the set verification condition.

[0100] If the attribute's to-be-verified rule information includes the number of contact information groups and the number of fields in each contact information group, and the number of contact information groups is not greater than a set first threshold, and the number of fields in each contact information group is not greater than a set first field threshold, then determining that the attribute's to-be-verified rule information meets the set verification condition;

[0101] The first threshold value may be 20 or other values. The first field threshold value may be set based on actual conditions.

[0102] For example, the first threshold is set to 20 and the first field threshold is set to 40. If the number of contact information groups is 20 and the number of fields in each group of contact information is 35, the number of contact information groups is not greater than the first threshold and is a positive integer, and the number of fields in each group of contact information is not greater than the first field threshold and is a positive integer, then it is determined that the to-be-verified rule information of the attribute meets the set verification condition.

[0103] If the attribute's rule information to be verified includes the number of business information groups and the number of fields in each business information group, and the number of business information groups is not greater than a set second threshold, and the number of fields in each business information group is not greater than a set second field threshold, then it is determined that the attribute's rule information to be verified meets the set verification condition, wherein the second threshold is greater than the first threshold, and the second field threshold is greater than the first field threshold;

[0104] The second threshold value may be 50 or other values. The second field threshold value may be 80 or other values.

[0105] For example, the second threshold is set to 50 and the second field threshold is set to 80. If the number of business information groups is 50 and the number of fields in each business information group is 60, the number of business information groups is not greater than the second threshold and is a positive integer, and the number of fields in each business information group is not greater than the second field threshold and is a positive integer, then it is determined that the to-be-verified rule information of the attribute meets the set verification condition.

[0106] If the attribute's rule information to be verified includes attribute identifiers and attribute identifier fields corresponding to each attribute, the number of attribute identifier fields is equal to the sum of the number of basic information fields, the number of contact information fields, and the number of business information fields, and the attribute identifier corresponding to each attribute is not empty, then it is determined that the attribute's rule information to be verified meets the set verification condition; wherein the number of contact information fields is obtained by the number of contact information groups and the number of fields in each contact information group, and the number of business information fields is obtained by the number of business information groups and the number of fields in each business information group.

[0107] The number of attribute identifier fields mentioned above must be a positive integer. The attribute verification rule information mentioned above is primarily used to display the attribute identifiers corresponding to each attribute to the user. For example, if an outbound call data entry is "1, Zhang San, Male, 18, 00000000000, Need to process service A," the outbound call data displayed to the user based on the attribute verification rule information is "Serial number: 1, Name: Zhang San, Gender: Male, Age: 18, Contact information: 00000000000, Service: Need to process service A."

[0108] like Figure 6As shown, the number of basic information fields B1, the number of contact information groups C1, the number of fields in each contact information group C2, the number of business information groups d, the number of fields in each business information group D1, D2, ..., D d , then the attribute identification field E = B1 + C + D, wherein the number of contact information fields C = C1 * C2, the number of business information fields

[0109] The following methods are used to determine whether the to-be-verified rule information of each attribute satisfies the set verification condition, including:

[0110] If the attribute's to-be-verified rule information includes a version number, and the version number is not within a set range, or the version number is a non-positive integer, it is determined that the attribute's to-be-verified rule information does not meet the set verification condition;

[0111] For example, if the version number included in the attribute's pending rule information is 004, the setting range is 000-003, and the version number is not within the setting range, then it is determined that the attribute's pending rule information does not meet the set verification condition. If the version number included in the attribute's pending rule information is -000, the setting range is 000-003, and the version number is a non-positive integer, then it is determined that the attribute's pending rule information does not meet the set verification condition.

[0112] If the attribute's rule information to be verified includes the number of basic information fields, and the number of basic information fields is greater than a set threshold, or the number of basic information fields is a non-positive integer, it is determined that the attribute's rule information to be verified does not meet the set verification condition;

[0113] For example, if the number of basic information fields is 30 and the threshold is set to 25, and the number of basic information fields is greater than the threshold, it is determined that the attribute's rule information to be verified does not meet the set verification condition. If the number of basic information fields is 20.13, it is determined that the attribute's rule information to be verified does not meet the set verification condition.

[0114] If the attribute's rule information to be verified includes the number of contact information groups and the number of fields in each contact information group, and the number of contact information groups is greater than a set first threshold, or the number of fields in each contact information group is greater than a set first field threshold, or the number of contact information groups is a non-positive integer, or the number of fields in each contact information group is a non-positive integer, then it is determined that the attribute's rule information to be verified does not meet the set verification condition;

[0115] For example, the first threshold is set to 20 and the first field threshold is set to 40. If the number of contact information groups is 21 and the number of fields in each contact information group is 35, and the number of contact information groups is greater than the first threshold, then it is determined that the rule information to be verified for the attribute does not meet the set verification conditions. If the number of contact information groups is 18 and the number of fields in each contact information group is 45, and the number of fields in each contact information group is greater than the first field threshold, then it is determined that the rule information to be verified for the attribute does not meet the set verification conditions. If the number of contact information groups is 18.5 and the number of fields in each contact information group is 35, and the number of contact information groups is a non-positive integer, then it is determined that the rule information to be verified for the attribute does not meet the set verification conditions. If the number of contact information groups is 18 and the number of fields in each contact information group is 35.67, and the number of fields in each contact information group is a non-positive integer, then it is determined that the rule information to be verified for the attribute does not meet the set verification conditions.

[0116] If the attribute's rule information to be verified includes the number of business information groups and the number of fields in each business information group, and the number of business information groups is greater than a set second threshold, or the number of fields in each business information group is greater than a set second field threshold, or the number of business information groups is a non-positive integer, or the number of fields in each business information group is a non-positive integer, then it is determined that the attribute's rule information to be verified does not meet the set verification condition, wherein the second threshold is greater than the first threshold, and the second field threshold is greater than the first field threshold;

[0117] For example, set the second threshold to 50 and the second field threshold to 80. If the number of business information groups is 55, and the number of fields in each business information group is 60, and the number of business information groups is greater than the second threshold, it is determined that the rule information to be verified for the attribute does not meet the set verification conditions. If the number of business information groups is 40, and the number of fields in each business information group is 90, and the number of fields in each business information group is greater than the second field threshold, it is determined that the rule information to be verified for the attribute does not meet the set verification conditions. If the number of contact information groups is 45.8, and the number of fields in each business information group is 60, and the number of business information groups is a non-positive integer, it is determined that the rule information to be verified for the attribute does not meet the set verification conditions. If the number of business information groups is 40, and the number of fields in each business information group is 60.89, and the number of fields in each business information group is a non-positive integer, it is determined that the rule information to be verified for the attribute does not meet the set verification conditions.

[0118] If the attribute's rule information to be verified includes attribute identifiers and attribute identifier fields corresponding to each attribute, the number of attribute identifier fields is not equal to the sum of the number of basic information fields, the number of contact information fields, and the number of business information fields, or the attribute identifier corresponding to at least one attribute is empty, or the number of attribute identifier fields is a non-positive integer, then it is determined that the attribute's rule information to be verified does not meet the set verification conditions.

[0119] For example, if an outbound call data entry is "1, Zhang San, Male, 18, 00000000000, Service A Required," the outbound call data displayed to the user based on the pending verification rule information for the attribute is "Serial Number: 1, Zhang San, Gender: Male, Age: 18, Contact Information: 00000000000, Service: Service A Required." Since the attribute identifier "Name" corresponding to one of the attributes is empty, it is determined that the pending verification rule information for the attribute does not meet the set verification conditions.

[0120] For example, if the number of basic information fields is B1, the number of contact information groups is C1, the number of fields in each contact information group is C2, the number of business information groups is d, and the number of fields in each business information group is D1, D2, ..., D d , attribute identification field E≠B1+C+D, wherein the number of contact information fields C=C1*C2, the number of business information fields Therefore, it is determined that the to-be-verified rule information of the attribute does not meet the set verification condition.

[0121] Step 304: using the to-be-verified rule information of each attribute as the rule information of each attribute;

[0122] When the rule information to be verified of each attribute satisfies the set verification conditions, the rule information to be verified of each attribute is used as the rule information of each attribute.

[0123] Step 305: Obtain and display the verification failure result;

[0124] When the to-be-verified rule information of any of the above attributes does not meet the set verification conditions, the verification program is terminated and a verification failure result is obtained. The verification failure result includes information such as the reason for the verification failure and is saved in the corresponding verification file for display to the user.

[0125] Step 306: Determine whether the content corresponding to each attribute in any outbound call data satisfies the attribute rule information. If so, execute step 307; otherwise, execute step 308.

[0126] like Figure 5 As shown, for each outbound call data, a validator is used to gradually verify whether the basic information, contact information and business information meet the corresponding rule information.

[0127] Determine whether the content corresponding to each attribute in any one of the outbound call data satisfies the rule information of the attribute by the following method:

[0128] If the content corresponding to any attribute in the outbound call data includes multiple groups of data, and the number of groups of the content corresponding to the attribute is not greater than the number of groups in the rule information of the attribute, and the number of fields in each group of data is not greater than the number of fields in the corresponding group in the rule information of the attribute, then it is determined that the content corresponding to the attribute in the outbound call data satisfies the rule information of the attribute;

[0129] Specifically, the content corresponding to any attribute in the outbound call data may be contact information and business information.

[0130] For example, when it is contact information, if the number of contact information groups in the rule information of the attribute is 10, the number of fields of the corresponding group in the rule information of the attribute is 20, the number of groups of content corresponding to the attribute is 5, the number of fields of each group of data is 20, the number of groups of content corresponding to the attribute is not greater than the number of contact information groups in the rule information of the attribute, the number of fields of each group of data is not greater than the number of fields of the corresponding group in the rule information of the attribute, and the unused 10-5=5 groups need to be left blank, then it is determined that the content corresponding to the attribute in the outbound call data meets the rule information of the attribute.

[0131] For example, when it is business information, if the number of business information groups in the rule information of the attribute is 40, the number of fields of the corresponding group in the rule information of the attribute is 60, the number of groups of content corresponding to the attribute is 35, the number of fields of each group of data is 50, the number of groups of content corresponding to the attribute is not greater than the number of business information groups in the rule information of the attribute, the number of fields of each group of data is not greater than the number of fields of the corresponding group in the rule information of the attribute, and the unused 40-35=5 groups need to be left blank, then it is determined that the content corresponding to the attribute in the outbound call data meets the rule information of the attribute.

[0132] If the content corresponding to any attribute in the outbound call data includes a group of data, and the number of fields in the group of data is not greater than the number of fields in the rule information of the attribute, it is determined that the content corresponding to the attribute in the outbound call data meets the rule information of the attribute.

[0133] Specifically, the content corresponding to any attribute in the outbound call data may be basic information. The fields of the group of data include fields of actual data and unused fields.

[0134] If the number of basic information fields in the rule information of the attribute is 30, the number of fields of the group of data is 30, and the number of fields of the group of data is not greater than the number of basic information fields in the rule information of the attribute, then it is determined that the content corresponding to the attribute in the outbound call data meets the rule information of the attribute.

[0135] Determine whether the content corresponding to each attribute in any of the outbound call data satisfies the attribute rule information by the following method:

[0136] If the content corresponding to any attribute in the outbound call data includes multiple groups of data, and the number of groups of the content corresponding to the attribute is greater than the number of groups in the rule information of the attribute, or the number of fields in each group of data is greater than the number of fields in the corresponding group in the rule information of the attribute, then it is determined that the content corresponding to the attribute in the outbound call data does not satisfy the rule information of the attribute;

[0137] Specifically, the content corresponding to any attribute in the outbound call data may be contact information and business information.

[0138] For example, in the case of contact information, if the number of contact information groups in the attribute's rule information is 10, the number of fields in the corresponding group in the attribute's rule information is 20, the number of content groups corresponding to the attribute is 12, and the number of fields in each data group is 20, and the number of content groups corresponding to the attribute is greater than the number of contact information groups in the attribute's rule information, then it is determined that the content corresponding to the attribute in the outbound call data does not satisfy the attribute's rule information. If the number of contact information groups in the attribute's rule information is 10, the number of fields in the corresponding group in the attribute's rule information is 20, the number of content groups corresponding to the attribute is 10, and the number of fields in each data group is 25, and the number of fields in each data group is greater than the number of fields in the corresponding group in the attribute's rule information, then it is determined that the content corresponding to the attribute in the outbound call data does not satisfy the attribute's rule information.

[0139] For example, in the case of service information, if the number of service information groups in the rule information of the attribute is 40, the number of fields of the corresponding group in the rule information of the attribute is 60, the number of content groups corresponding to the attribute is 45, the number of fields of each data group is 50, and the number of content groups corresponding to the attribute is greater than the number of service information groups in the rule information of the attribute, then it is determined that the content corresponding to the attribute in the outbound call data does not satisfy the rule information of the attribute. If the number of service information groups in the rule information of the attribute is 40, the number of fields of the corresponding group in the rule information of the attribute is 60, the number of content groups corresponding to the attribute is 35, the number of fields of each data group is 70, and the number of fields of each data group is not greater than the number of fields of the corresponding group in the rule information of the attribute, then it is determined that the content corresponding to the attribute in the outbound call data does not satisfy the rule information of the attribute.

[0140] If the content corresponding to any attribute in the outbound call data includes a group of data, and the number of fields in the group of data is greater than the number of fields in the rule information of the attribute, it is determined that the content corresponding to the attribute in the outbound call data does not satisfy the rule information of the attribute.

[0141] Specifically, the content corresponding to any attribute in the outbound call data may be basic information.

[0142] If the number of basic information fields in the rule information of the attribute is 30, and the number of fields of the group of data is 40, and the number of fields of the group of data is greater than the number of basic information fields in the rule information of the attribute, it is determined that the content corresponding to the attribute in the outbound call data does not meet the rule information of the attribute.

[0143] Step 307: Determine whether the outbound call data verification has passed;

[0144] like Figure 5 As shown, after determining that the outbound call data has passed the verification, the outbound call data is stored in a storage medium. Thereafter, based on the outbound call data in the storage medium, an outbound call service can be carried out manually or intelligently, or other processing can be performed.

[0145] Step 308: Determine that the outbound call data verification fails, obtain and display a verification failure result corresponding to the outbound call data.

[0146] The verification failure result includes part or all of the following information: the verification failure reason, the outbound call data sequence number, and the attribute identifier corresponding to the attribute for which verification failed, determined according to the rule information of each attribute.

[0147] The specific method for determining the attribute identifier corresponding to the attribute that failed verification based on the rule information of each attribute is as follows:

[0148] The attribute identifier corresponding to the attribute that failed verification is determined according to the attribute identifier corresponding to each attribute included in the attribute's to-be-verified rule information.

[0149] Based on the same inventive concept, the embodiment of the present application provides a device for processing outbound call customer information, please refer to Figure 7 , the device comprises:

[0150] An acquisition module 701 is configured to acquire an outbound call data set from a target data source, wherein the outbound call data set includes a version number and multiple pieces of outbound call data, and the outbound call data includes content corresponding to different attributes;

[0151] Determining module 702, for determining the rule information of each attribute corresponding to the version number according to the preset correspondence between the version number and the rule information of each attribute;

[0152] The verification module 703 is configured to determine, for any piece of outbound call data, that the outbound call data has passed verification if the content corresponding to each attribute in the piece of outbound call data satisfies the rule information of the attribute.

[0153] As an optional implementation, the device further includes:

[0154] A display module is used to determine that the outbound call data verification has failed if the content corresponding to each attribute in any of the outbound call data does not satisfy the rule information of the attribute, and obtain and display the corresponding verification failure result, wherein the verification failure result includes part or all of the following information: the reason for the verification failure, the outbound call data sequence number and the attribute identifier corresponding to the attribute that failed the verification determined according to the rule information of each attribute.

[0155] As an optional implementation manner, the determining module is configured to determine the rule information of each attribute corresponding to the version number based on a preset correspondence between the version number and the rule information of each attribute, including:

[0156] Determine the rule information to be verified for each attribute corresponding to the version number according to the preset correspondence between the version number and the rule information of each attribute;

[0157] Determine whether the to-be-verified rule information of each attribute satisfies the set verification conditions;

[0158] If so, the rule information to be verified for each attribute is used as the rule information for each attribute.

[0159] As an optional implementation manner, the determination module is configured to determine whether the to-be-verified rule information of each attribute satisfies a set verification condition, including:

[0160] If the attribute's to-be-verified rule information includes a version number, and the version number is within a set range, determining that the attribute's to-be-verified rule information meets the set verification condition;

[0161] If the attribute's rule information to be verified includes the number of basic information fields, and the number of basic information fields is not greater than a set threshold, then determining that the attribute's rule information to be verified meets the set verification condition;

[0162] If the attribute's to-be-verified rule information includes the number of contact information groups and the number of fields in each contact information group, and the number of contact information groups is not greater than a set first threshold, and the number of fields in each contact information group is not greater than a set first field threshold, then determining that the attribute's to-be-verified rule information meets the set verification condition;

[0163] If the attribute's rule information to be verified includes the number of business information groups and the number of fields in each business information group, and the number of business information groups is not greater than a set second threshold, and the number of fields in each business information group is not greater than a set second field threshold, then it is determined that the attribute's rule information to be verified meets the set verification condition, wherein the second threshold is greater than the first threshold, and the second field threshold is greater than the first field threshold;

[0164] If the attribute's rule information to be verified includes attribute identifiers and attribute identifier fields corresponding to each attribute, the number of attribute identifier fields is equal to the sum of the number of basic information fields, the number of contact information fields, and the number of business information fields, and the attribute identifier corresponding to each attribute is not empty, then it is determined that the attribute's rule information to be verified meets the set verification condition; wherein the number of contact information fields is obtained by the number of contact information groups and the number of fields in each contact information group, and the number of business information fields is obtained by the number of business information groups and the number of fields in each business information group.

[0165] As an optional implementation manner, the verification module is configured to determine whether the content corresponding to each attribute in any one of the outbound call data satisfies the rule information of the attribute by:

[0166] If the content corresponding to any attribute in the outbound call data includes multiple groups of data, and the number of groups of the content corresponding to the attribute is not greater than the number of groups in the rule information of the attribute, and the number of fields in each group of data is not greater than the number of fields in the corresponding group in the rule information of the attribute, then it is determined that the content corresponding to the attribute in the outbound call data satisfies the rule information of the attribute;

[0167] If the content corresponding to any attribute in the outbound call data includes a group of data, and the number of fields in the group of data is not greater than the number of fields in the rule information of the attribute, it is determined that the content corresponding to the attribute in the outbound call data meets the rule information of the attribute.

[0168] Based on the same inventive concept, the embodiment of the present application provides an electronic device that can implement the outbound call data processing function discussed above. Please refer to Figure 8 , the device includes a processor 801 and a memory 802, wherein the memory 802 is used to store program instructions;

[0169] The processor 801 calls the program instructions stored in the memory and executes the program instructions to implement the following steps:

[0170] Obtain an outbound call data set from a target data source, the outbound call data set including a version number and multiple outbound call data, the outbound call data including content corresponding to different attributes;

[0171] Determine the rule information of each attribute corresponding to the version number according to the preset correspondence between the version number and the rule information of each attribute;

[0172] For any piece of outbound call data, if the content corresponding to each attribute in the any piece of outbound call data satisfies the rule information of the attribute, it is determined that the outbound call data has passed the verification.

[0173] As an optional implementation, the processor further executes:

[0174] If the content corresponding to each attribute in any of the outbound call data does not satisfy the rule information of the attribute, it is determined that the outbound call data verification has failed, and the corresponding verification failure result is obtained and displayed, wherein the verification failure result includes part or all of the following information: the reason for verification failure, the outbound call data sequence number and the attribute identifier corresponding to the attribute that failed verification determined according to the rule information of each attribute.

[0175] As an optional implementation manner, determining the rule information of each attribute corresponding to the version number according to the preset correspondence between the version number and the rule information of each attribute includes:

[0176] Determine the rule information to be verified for each attribute corresponding to the version number according to the preset correspondence between the version number and the rule information of each attribute;

[0177] Determine whether the to-be-verified rule information of each attribute satisfies the set verification conditions;

[0178] If so, the rule information to be verified for each attribute is used as the rule information for each attribute.

[0179] As an optional implementation manner, determining whether the to-be-verified rule information of each attribute satisfies a set verification condition includes:

[0180] If the attribute's to-be-verified rule information includes a version number, and the version number is within a set range, determining that the attribute's to-be-verified rule information meets the set verification condition;

[0181] If the attribute's rule information to be verified includes the number of basic information fields, and the number of basic information fields is not greater than a set threshold, then determining that the attribute's rule information to be verified meets the set verification condition;

[0182] If the attribute's to-be-verified rule information includes the number of contact information groups and the number of fields in each contact information group, and the number of contact information groups is not greater than a set first threshold, and the number of fields in each contact information group is not greater than a set first field threshold, then determining that the attribute's to-be-verified rule information meets the set verification condition;

[0183] If the attribute's rule information to be verified includes the number of business information groups and the number of fields in each business information group, and the number of business information groups is not greater than a set second threshold, and the number of fields in each business information group is not greater than a set second field threshold, then it is determined that the attribute's rule information to be verified meets the set verification condition, wherein the second threshold is greater than the first threshold, and the second field threshold is greater than the first field threshold;

[0184] If the attribute's rule information to be verified includes attribute identifiers and attribute identifier fields corresponding to each attribute, the number of attribute identifier fields is equal to the sum of the number of basic information fields, the number of contact information fields, and the number of business information fields, and the attribute identifier corresponding to each attribute is not empty, then it is determined that the attribute's rule information to be verified meets the set verification condition; wherein the number of contact information fields is obtained by the number of contact information groups and the number of fields in each contact information group, and the number of business information fields is obtained by the number of business information groups and the number of fields in each business information group.

[0185] As an optional implementation manner, whether the content corresponding to each attribute in any one of the outbound call data satisfies the rule information of the attribute is determined by the following method:

[0186] If the content corresponding to any attribute in the outbound call data includes multiple groups of data, and the number of groups of the content corresponding to the attribute is not greater than the number of groups in the rule information of the attribute, and the number of fields in each group of data is not greater than the number of fields in the corresponding group in the rule information of the attribute, then it is determined that the content corresponding to the attribute in the outbound call data satisfies the rule information of the attribute;

[0187] If the content corresponding to any attribute in the outbound call data includes a group of data, and the number of fields in the group of data is not greater than the number of fields in the rule information of the attribute, it is determined that the content corresponding to the attribute in the outbound call data meets the rule information of the attribute.

[0188] Based on the same inventive concept, embodiments of the present application provide a computer-readable storage medium, a computer program product comprising: computer program code. When the computer program code is executed on a computer, it causes the computer to execute any of the outbound call data processing methods discussed above. Because the principles underlying the problems solved by the computer-readable storage medium are similar to those of the outbound call data processing methods, the implementation of the computer-readable storage medium can be referenced to the implementation of the methods, and any repetitions will be omitted.

[0189] Based on the same inventive concept, the present application also provides a computer program product, such as Figure 9 As shown, the computer program product 90 includes computer program code. When executed on a computer, the computer executes any of the outbound call data processing methods discussed above. Because the principles underlying the problems solved by the computer program products are similar to those of the outbound call data processing methods, the implementation of the computer program products can be referenced to the implementation of the methods, and any repetitive details will not be repeated.

[0190] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0191] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. 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 computer 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 processes 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.

[0192] These computer program instructions may also be stored in a computer 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 computer readable memory produce an article of manufacture comprising 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.

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

[0194] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A method for processing outbound call data, characterized in that: The method includes: Obtain an outbound call data set from a target data source, the outbound call data set including a version number and multiple outbound call data, the outbound call data including content corresponding to different attributes; Determine the rule information to be verified for each attribute corresponding to the version number based on the pre-set correspondence between the version number and the rule information of each attribute; determine whether the rule information to be verified for each attribute satisfies the set verification conditions; if so, use the rule information to be verified for each attribute as the rule information for each attribute corresponding to the version number; For any outbound call data, if the content corresponding to each attribute in the outbound call data satisfies the rule information of the attribute, it is determined that the outbound call data has passed the verification; The step of determining whether the to-be-verified rule information of each attribute satisfies a set verification condition includes: If the attribute's to-be-verified rule information includes a version number, and the version number is within a set range, determining that the attribute's to-be-verified rule information meets the set verification condition; If the attribute's rule information to be verified includes the number of basic information fields, and the number of basic information fields is not greater than a set threshold, then determining that the attribute's rule information to be verified meets the set verification condition; If the attribute's to-be-verified rule information includes the number of contact information groups and the number of fields in each contact information group, and the number of contact information groups is not greater than a set first threshold, and the number of fields in each contact information group is not greater than a set first field threshold, then determining that the attribute's to-be-verified rule information meets the set verification condition; If the attribute's rule information to be verified includes the number of business information groups and the number of fields in each business information group, and the number of business information groups is not greater than a set second threshold, and the number of fields in each business information group is not greater than a set second field threshold, then it is determined that the attribute's rule information to be verified meets the set verification condition, wherein the second threshold is greater than the first threshold, and the second field threshold is greater than the first field threshold; If the attribute's rule information to be verified includes attribute identifiers and attribute identifier fields corresponding to each attribute, the number of attribute identifier fields is equal to the sum of the number of basic information fields, the number of contact information fields, and the number of business information fields, and the attribute identifier corresponding to each attribute is not empty, then it is determined that the attribute's rule information to be verified meets the set verification condition; wherein the number of contact information fields is obtained by the number of contact information groups and the number of fields in each contact information group, and the number of business information fields is obtained by the number of business information groups and the number of fields in each business information group.

2. The method according to claim 1, wherein The method further comprises: If the content corresponding to each attribute in any of the outbound call data does not satisfy the rule information of the attribute, it is determined that the outbound call data verification has failed, and the corresponding verification failure result is obtained and displayed, wherein the verification failure result includes part or all of the following information: the reason for verification failure, the outbound call data sequence number and the attribute identifier corresponding to the attribute that failed verification determined according to the rule information of each attribute.

3. The method according to any one of claims 1 to 2, characterized in that Determine whether the content corresponding to each attribute in any one of the outbound call data satisfies the rule information of the attribute by the following method: If the content corresponding to any attribute in the outbound call data includes multiple groups of data, and the number of groups of the content corresponding to the attribute is not greater than the number of groups in the rule information of the attribute, and the number of fields in each group of data is not greater than the number of fields in the corresponding group in the rule information of the attribute, then it is determined that the content corresponding to the attribute in the outbound call data satisfies the rule information of the attribute; If the content corresponding to any attribute in the outbound call data includes a group of data, and the number of fields in the group of data is not greater than the number of fields in the rule information of the attribute, it is determined that the content corresponding to the attribute in the outbound call data meets the rule information of the attribute.

4. An outbound call data processing device, characterized in that: The device includes: An acquisition module, configured to acquire an outbound call data set from a target data source, wherein the outbound call data set includes a version number and multiple pieces of outbound call data, and the outbound call data includes content corresponding to different attributes; a determination module, configured to determine, based on a preset correspondence between a version number and rule information for each attribute, rule information to be verified for each attribute corresponding to the version number; determine whether the rule information to be verified for each attribute satisfies a set verification condition; and if so, use the rule information to be verified for each attribute as the rule information for each attribute corresponding to the version number; a verification module configured to determine, for any piece of outbound call data, that the outbound call data passes verification if the content corresponding to each attribute in the piece of outbound call data satisfies the rule information of the attribute; The determination module is used to determine whether the to-be-verified rule information of each attribute satisfies the set verification conditions, including: If the attribute's to-be-verified rule information includes a version number, and the version number is within a set range, determining that the attribute's to-be-verified rule information meets the set verification condition; If the attribute's rule information to be verified includes the number of basic information fields, and the number of basic information fields is not greater than a set threshold, then determining that the attribute's rule information to be verified meets the set verification condition; If the attribute's to-be-verified rule information includes the number of contact information groups and the number of fields in each contact information group, and the number of contact information groups is not greater than a set first threshold, and the number of fields in each contact information group is not greater than a set first field threshold, then determining that the attribute's to-be-verified rule information meets the set verification condition; If the attribute's rule information to be verified includes the number of business information groups and the number of fields in each business information group, and the number of business information groups is not greater than a set second threshold, and the number of fields in each business information group is not greater than a set second field threshold, then it is determined that the attribute's rule information to be verified meets the set verification condition, wherein the second threshold is greater than the first threshold, and the second field threshold is greater than the first field threshold; If the attribute's rule information to be verified includes attribute identifiers and attribute identifier fields corresponding to each attribute, the number of attribute identifier fields is equal to the sum of the number of basic information fields, the number of contact information fields, and the number of business information fields, and the attribute identifier corresponding to each attribute is not empty, then it is determined that the attribute's rule information to be verified meets the set verification condition; wherein the number of contact information fields is obtained by the number of contact information groups and the number of fields in each contact information group, and the number of business information fields is obtained by the number of business information groups and the number of fields in each business information group.

5. The device according to claim 4, characterized in that The device further comprises: A display module is used to determine that the outbound call data verification has failed if the content corresponding to each attribute in any of the outbound call data does not satisfy the rule information of the attribute, and obtain and display the corresponding verification failure result, wherein the verification failure result includes part or all of the following information: the reason for the verification failure, the outbound call data sequence number and the attribute identifier corresponding to the attribute that failed the verification determined according to the rule information of each attribute.

6. The device according to any one of claims 4 to 5, characterized in that: The verification module is configured to determine whether the content corresponding to each attribute in any of the outbound call data satisfies the rule information of the attribute by: If the content corresponding to any attribute in the outbound call data includes multiple groups of data, and the number of groups of the content corresponding to the attribute is not greater than the number of groups in the rule information of the attribute, and the number of fields in each group of data is not greater than the number of fields in the corresponding group in the rule information of the attribute, then it is determined that the content corresponding to the attribute in the outbound call data satisfies the rule information of the attribute; If the content corresponding to any attribute in the outbound call data includes a group of data, and the number of fields in the group of data is not greater than the number of fields in the rule information of the attribute, it is determined that the content corresponding to the attribute in the outbound call data meets the rule information of the attribute.

7. An electronic device, characterized in that: include: a memory for storing program instructions; A processor is configured to call program instructions stored in the memory and execute the steps of the method according to any one of claims 1 to 3 according to the obtained program instructions.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions. When the program instructions are executed by a computer, the computer is caused to perform the method according to any one of claims 1 to 3.

9. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 3.

Images