Disclosure of Invention
The invention provides an outbound data processing method, an outbound platform and a computer readable storage medium, which are used for solving the technical problems of higher system risk and service risk of the outbound platform in the prior art.
In order to solve the above technical problems, a method for processing outbound data according to an embodiment of the present invention is applied to an outbound platform, and the technical scheme of the method is as follows:
creating a data batch according to an upstream data system and products, wherein the data batch is generated according to outbound data templates provided by the outbound platform, basic fields shared by the outbound data templates and secondary split fields aiming at different outbound services are configured in the outbound platform, custom fields related to different service scenes are configured in the upstream data system, and one outbound data template corresponds to one service scene;
the method comprises the steps of obtaining a current outbound data template of a product corresponding to the data batch from an outbound data template library, wherein the outbound data template library is used for storing outbound data templates corresponding to various business scenes, and one business scene corresponds to one product;
According to the current outbound data template, carrying out content analysis and validity verification on each original data file in the data batch;
and taking the verified original data record in the original data file as an outbound data record and storing the outbound data record into an outbound database of the outbound platform.
In one possible embodiment, before creating a data batch of the plurality of raw data files to be processed according to the associated upstream data system and the associated product, the method further comprises:
generating outbound data templates corresponding to service scenes according to information input by a user in a template configuration page, wherein the target configuration page is used for the user to configure outbound data templates of different service scenes;
and synchronizing each newly generated outbound data template to an upstream data system for providing an original data file for the outbound platform, so that the upstream data system exports data according to the data template of the corresponding service scene to form the original data file.
A possible implementation, the outbound data template includes:
a field type and a field attribute.
A possible implementation, the field type includes:
The base field is the basis for the upstream data system to export data, the custom field is the field added for different service scenes when the upstream data system exports data, and the secondary split field is the field for the outbound operator to screen outbound data records from the outbound database when executing outbound service.
A possible implementation, the field attribute includes:
Whether desensitized, rules for desensitization, whether to fill, whether to display, data type.
In one possible implementation manner, the field attribute of the secondary split field further includes a split type, and different split types correspond to different split rules.
One possible implementation, creating a data batch of a plurality of raw data files to be processed according to an upstream data system and a product, includes:
the method comprises the steps of regularly scanning a plurality of original data files received from each upstream data system, wherein the names of the original data files comprise the upstream data system and the product;
And classifying the original data files corresponding to the same product under the same upstream data system into the newly created same data batch according to the names of the original data files.
According to a possible implementation manner, according to the current outbound data template, content analysis and validity verification are performed on each original data file in the data batch, including:
Acquiring header information of the original data file, wherein the header information comprises fields of the original data record;
Acquiring a field position corresponding to a field consistent with a template field specified in the outbound data template from the header information;
verifying whether the data of the corresponding field position in the original data record accords with the data record rule according to the data record rule of the specified template field;
And if the data in the field positions corresponding to each specified template field in the original data record accords with the data record rule, determining that the corresponding original data record passes the verification, otherwise, determining that the corresponding original data record fails the verification, and recording the reason of the failure.
In one possible implementation manner, after the original data record passing through verification in the original data file is used as an outbound data record and stored in an outbound database of the outbound platform, the method further includes:
accumulating one for each valid client number of the corresponding data batch when storing one outbound data record;
And when all the original data files in the data batch are verified, setting the state of the corresponding data batch to be in effect for use by outbound business.
In a second aspect, an embodiment of the present invention provides an outbound platform, including:
The system comprises a creation unit, a service creation unit and a service analysis unit, wherein the creation unit is used for creating a data batch of a plurality of original data files to be processed according to an upstream data system and products, wherein the original data files are generated according to outbound data templates provided by an outbound platform, basic fields shared by the outbound data templates and secondary split fields aiming at different outbound services are configured in the outbound platform, custom fields related to different service scenes are configured in the upstream data system, and one outbound data template corresponds to one service scene;
The system comprises an acquisition unit, a service scene generation unit and a data batch generation unit, wherein the acquisition unit is used for acquiring a current outbound data template of a product corresponding to the data batch from an outbound data template base, and the outbound data template base is used for storing outbound data templates corresponding to various service scenes, wherein one service scene corresponds to one product;
The verification unit is used for carrying out content analysis and validity verification on each original data file in the data batch according to the current outbound data template;
the processing unit is used for taking the original data record which passes the verification in the original data file as an outbound data record and storing the outbound data record into an outbound database of the outbound platform.
A possible implementation method, the outbound platform further includes a configuration unit, where the configuration unit is configured to:
generating outbound data templates corresponding to service scenes according to information input by a user in a template configuration page, wherein the target configuration page is used for the user to configure outbound data templates of different service scenes;
and synchronizing each newly generated outbound data template to an upstream data system for providing an original data file for the outbound platform, so that the upstream data system exports data according to the data template of the corresponding service scene to form the original data file.
A possible implementation, the outbound data template includes:
a field type and a field attribute.
A possible implementation, the field type includes:
The base field is the basis for the upstream data system to export data, the custom field is the field added for different service scenes when the upstream data system exports data, and the secondary split field is the field for the outbound operator to screen outbound data records from the outbound database when executing outbound service.
A possible implementation, the field attribute includes:
Whether desensitized, rules for desensitization, whether to fill, whether to display, data type.
In one possible implementation manner, the field attribute of the secondary split field further includes a split type, and different split types correspond to different split rules.
In a possible embodiment, the creating unit is further configured to:
the method comprises the steps of regularly scanning a plurality of original data files received from each upstream data system, wherein the names of the original data files comprise the upstream data system and the product;
And classifying the original data files corresponding to the same product under the same upstream data system into the newly created same data batch according to the names of the original data files.
In a possible embodiment, the verification unit is further configured to:
Acquiring header information of the original data file, wherein the header information comprises fields of the original data record;
Acquiring a field position corresponding to a field consistent with a template field specified in the outbound data template from the header information;
verifying whether the data of the corresponding field position in the original data record accords with the data record rule according to the data record rule of the specified template field;
And if the data in the field positions corresponding to each specified template field in the original data record accords with the data record rule, determining that the corresponding original data record passes the verification, otherwise, determining that the corresponding original data record fails the verification, and recording the reason of the failure.
In a possible embodiment, the processing unit is further configured to:
accumulating one for each valid client number of the corresponding data batch when storing one outbound data record;
And when all the original data files in the data batch are verified, setting the state of the corresponding data batch to be in effect for use by outbound business.
In a third aspect, an embodiment of the present invention further provides an outbound platform, including:
At least one processor, and
A memory coupled to the at least one processor;
Wherein the memory stores instructions executable by the at least one processor, the at least one processor performing the method of the first aspect described above by executing the instructions stored by the memory.
In a fourth aspect, embodiments of the present invention also provide a computer-readable storage medium, including:
The memory device is used for storing the data,
The memory is configured to store instructions that, when executed by the processor, cause an apparatus comprising the computer-readable storage medium to perform the method as described in the first aspect above.
In a fifth aspect, embodiments of the present invention also provide a computer program product comprising computer executable instructions for causing a computer to perform the method according to the first aspect.
Through the technical scheme in the one or more embodiments of the present invention, the embodiments of the present invention have at least the following technical effects:
In the embodiment provided by the invention, a data batch is created according to an upstream data system and a product to be processed, a current outbound data template of the product corresponding to the data batch is obtained from an outbound data template base, content analysis and validity verification are carried out on each original data file in the data batch according to the current outbound data template, and the original data records verified in the original data files are used as outbound data records and stored in an outbound database of an outbound platform. Because the above-mentioned processing procedure is that the outbound platform is in data butt joint with upstream data system, or the outbound platform processes the original data record to obtain the outbound data record, it is accomplished by using the shared basic field configured by the outbound platform and the outbound data template obtained by the custom field of the upstream data system configuration service scene, when the service scene changes, only the corresponding outbound data template needs to be added or modified, so that the data butt joint of both parties can be completed correctly, when the demand of outbound service changes, the secondary split field in the outbound data template can be modified or added to adjust outbound service, the whole procedure does not need to modify the program code of the outbound platform, so as to adapt to different demands of the service scene in time, thereby keeping the system of the outbound platform stable under the condition of quick response to the service demand, and further reducing the system risk and service risk of the outbound platform.
Detailed Description
The embodiment of the invention provides an outbound data processing method, an outbound platform and a computer readable storage medium, which are used for solving the technical problems of higher system risk and service risk of the outbound platform in the prior art.
In order to better understand the above technical solutions, the following detailed description of the technical solutions of the present application is made by using the accompanying drawings and specific embodiments, and it should be understood that the specific features of the embodiments and the embodiments of the present application are detailed descriptions of the technical solutions of the present application, and not limiting the technical solutions of the present application, and the technical features of the embodiments and the embodiments of the present application may be combined with each other without conflict. The technical scheme of the application obtains, stores, uses, processes and the like the data, which all meet the relevant regulations of national laws and regulations.
Referring to fig. 1, an embodiment of the present invention provides a method for processing outbound data, which is applied to an outbound platform, and the processing procedure of the method is as follows.
And 101, creating a data batch of a plurality of original data files to be processed according to an upstream data system and products, wherein the original data files are generated according to outbound data templates provided by an outbound platform, basic fields shared in the outbound data templates and secondary split fields aiming at different outbound services are configured in the outbound platform, custom fields related to different service scenes are configured in the upstream data system, and one outbound data template corresponds to one service scene.
Creating a data batch of a plurality of original data files to be processed according to the upstream data system and the products, wherein the data batch can be realized by the following modes:
Fig. 2 is a schematic diagram showing the relationship between the outbound platform and each branch line and the branch line of the bank a according to the embodiment of the present invention.
The bank A comprises n branches in the whole country, each branch comprises a plurality of branches, for example, branch 1-branch m are included under branch 1, branch 1-branch k are included under branch n, each branch and branch under the bank A need to provide an original data file for an outbound platform of the bank A, and the data systems of the branches and branches are called as upstream data systems.
A user can configure outbound data templates of each service scene through a template configuration page in an outbound platform, specifically can configure basic fields which each outbound data template should contain and secondary split fields aiming at different outbound services, can provide optional fields for an upstream data system for custom fields, can also prescribe the total number of custom fields, and can configure required fields in the custom fields according to the requirements of different service scenes after the outbound platform synchronizes the configured outbound data templates to the upstream data system. If 10 basic fields and 6 secondary split fields are configured in the outbound platform, 10 basic fields configured by the outbound platform should be contained in each outbound data template synchronized to the upstream data system, taking line 1 and line 3 as examples, line 1 defines 3 custom fields for service scene 1, line 3 defines 1 custom field for service scene 5, then in the original data file provided to the outbound platform for service scene 1 in line 1, each original data record contains data of the 10 basic fields and 3 custom fields, and line 3 provides the original data file provided to the outbound platform for service scene 5, each original data record contains data of the 10 basic fields and 1 custom field. The original data files of other business scenarios can be obtained by analogy.
The method comprises the steps of periodically scanning a plurality of original data files received from each upstream data system, wherein the names of the original data files comprise the upstream data system and the product, and classifying the original data files corresponding to the same product under the same upstream data system into the newly created same data batch according to the names of the original data files.
For example, the raw data files provided to the outbound platform by the line 1 in fig. 2 include raw data files 1A-1F, wherein the raw data files 1A, 1C and 1E all belong to the product a, the raw data files provided to the outbound platform by the line 3 include raw data files 3A-3F, wherein the raw data files 3C, 3D and 3E all belong to the product a, the raw data files belonging to the line 1 and the product a are created as one data batch 1A (including the raw data file 1A, 1C and 1E), and the raw data files belonging to the line 3 and the product a are created as another data batch 3A (including the raw data file 3C, 3D and 3E).
In the embodiment provided by the invention, the plurality of original data files belonging to the same product in the same upstream data system are created into one data batch, so that the batch processing of the original data files from the same business scene in the same upstream data system is facilitated, and the working efficiency is improved. The data of the outbound data template obtained by the shared basic field configured by the outbound platform and the customized field unique to the service scene configured by the upstream data system is butted between the outbound platform and the upstream data system, when the service scene is changed, the data of the two parties can be correctly butted by only adding or modifying the corresponding outbound data template, and the whole process can be timely adapted to different requirements of the service scene without modifying the program codes of the outbound platform, so that the system of the outbound platform is kept stable under the condition of quickly responding to the service requirement, and further the system risk and the service risk of the outbound platform are reduced.
Before creating a data batch according to the upstream data system and the products, the upstream data system and the outbound platform are configured to carry out data docking on the outbound data templates, which can be realized by the following modes:
Generating outbound data templates corresponding to service scenes according to information input by a user in a template configuration page, wherein a target configuration page is used for the user to configure outbound data templates of different service scenes, synchronizing each newly generated outbound data template to an upstream data system for providing an original data file for the outbound platform, and enabling the upstream data system to export data according to the data templates corresponding to the service scenes so as to form the original data file.
The outbound data template includes a field type and a field attribute.
The field types comprise a basic field, a custom field and a secondary split field, wherein the basic field is the basis for the upstream data system to export data, the custom field is the field added for different service scenes when the upstream data system exports data, and the secondary split field is the field for the outbound service personnel to screen outbound data records from an outbound database when the outbound service personnel executes outbound service.
The field attributes include whether to desensitize, desensitize rules, whether to fill, whether to display, data type.
The template field in the basic field is usually contained in the outbound data template of each business scenario, and the upstream data system can be used as a data-derived specification (i.e. basis), and the user can configure the Chinese name and English name of each field in the configuration of the basic field of the template configuration page.
For example, the field type of the basic field may include basic information and custom information, the basic information may include a plurality of fields (denoted as basic information field 1 to basic information field n), and the custom information may also include a plurality of fields (denoted as custom information field 1 to custom information field m), please refer to the configuration information of the basic field in table 1. After the configuration of the basic fields as shown in table 1 is completed, the basic fields in each outbound data template include template fields in table 1, and the corresponding template fields in the generated original data file use the corresponding configured chinese name or english name in table 1 as the original data.
It should be noted that, in table 1, the template fields corresponding to the basic information and the custom information are different, and the corresponding chinese and english names are also different, for example, chinese name 1 and english name 1 corresponding to the basic information field 1 cannot be equated with chinese name 1 and english name 1 corresponding to the custom information field 1.
For the custom field in the outbound data template, the upstream data system can customize the corresponding Chinese name and English name according to the requirements of different service scenes, and configure the field attribute of the custom field. Please refer to table 2 for configuration information of field attributes of custom fields provided in an embodiment of the present invention.
TABLE 2
In table 2, whether to desensitize is used for carrying out desensitization display on the data of the custom field in the subsequent data display, if so, the corresponding range of desensitization can be specified.
The desensitization rule is used for specifically designating desensitization, and the desensitization rule which can be supported comprises desensitization of designated information, such as desensitization of designated information 1, desensitization of designated information 1 and desensitization of designated information 3, and can be specifically set by users of an upstream data system.
Whether filling is necessary or not is used for indicating whether the corresponding custom field is a filling necessary field or not in the flow of executing the outbound business transaction.
Whether the display is used for indicating whether the corresponding custom field is displayed or not in the process of executing the outbound business handling, and if the display is needed, the range of the display object can be specified.
The data type is used for indicating the supportable data type of the corresponding custom field, for example, the supportable data type comprises character strings, numbers, dates and the like, and in the process of executing outbound business handling, the outbound platform can check each data corresponding to the custom field according to the data type configured for the custom field so as to determine whether the data corresponding to the custom field is legal or not.
For example, 10 custom fields may be included in the outbound data template, in an upstream data system (a branch line), for a new requirement of a service scenario of its product B, a chinese name of a custom field in the outbound data template of the service scenario is defined as a chinese name B, an english name is defined as an english name B, field attributes of the custom field include several field attributes shown in table 2, values of the field attributes may be represented using corresponding values encoded in table 2, for example, a desensitization rule of the custom field is configured as "information 3 encoding", and then when generating an original data file, the desensitization rule of the custom field desensitizes data containing information 3 in the field.
Besides basic fields which are required to be contained in each pre-defined outbound data template in the outbound platform and custom fields which are defined in an upstream data system according to system requirements of different service scenes, the outbound data templates also comprise secondary splitting fields which are defined in the outbound platform according to different outbound services, and the required outbound data records can be split according to different outbound services through different configurations of the secondary splitting fields for use by outbound service personnel.
The field attributes of the secondary split field may include a split type in addition to the field attributes in the custom field, where different split types correspond to different split rules. Please refer to table 3 for configuration information of split type provided in the embodiment of the present invention.
TABLE 3 Table 3
Please refer to table 4 for configuration information of the customer care outbound data template provided in the embodiment of the present invention.
TABLE 4 Table 4
Please refer to table 5 for a local data record in an upstream data system according to an embodiment of the present invention.
TABLE 5
| Sequence 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 |
The basic field in an outbound data template comprises field 3-field 5, the custom field comprises field 1, the upstream data system extracts data from the local data record (table 5) according to the outbound data template to form an original outbound data file, as shown in table 6, and table 6 is an original data record table of the outbound data file provided by the embodiment of the invention.
TABLE 6
| Sequence 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 |
After receiving the original data files provided by each upstream data system, the outbound platform can be replaced by scanning the original data files to be processed stored in the appointed position at fixed time, and creating corresponding data batches according to the upstream data system to which the original data files belong and the products.
After the data batch is created, step 102 may be performed.
Step 102, obtaining a current outbound data template of a product corresponding to the data batch from an outbound data template library, wherein the outbound data template library is used for storing outbound data templates corresponding to various business scenes, and one business scene corresponds to one product.
For example, the data batch includes original data files 1 to 3, the corresponding products are product a, and the corresponding current outbound data template is obtained from the outbound data template base of the outbound platform according to the product number of the product a.
After the current outbound data template corresponding to the data lot is obtained, steps 103-104 may be performed.
And 103, carrying out content analysis and validity verification on each original data file in the data batch according to the current outbound data template.
And 104, taking the original data record passing the verification in the original data file as an outbound data record and storing the outbound data record into an outbound database of an outbound platform.
According to the current outbound data template, content analysis and validity verification are carried out on each original data file in the data batch, and the method can be realized by the following steps:
The method comprises the steps of obtaining header information of an original data file, wherein the header information comprises fields of original data records, obtaining field positions corresponding to fields consistent with specified template fields in an outbound data template from the header information, verifying whether data corresponding to the field positions in the original data records accord with data record rules according to the data record rules of the specified template fields, if the data corresponding to the field positions of each specified template field in the original data records accord with the data record rules, determining that the corresponding original data records pass verification, otherwise, determining that the corresponding original data records fail verification, and recording reasons of the fail verification.
After the original data records passing the verification in the original data file are used as outbound data records and stored in an outbound database of an outbound platform, the method further comprises the following steps:
and if all the original data files in the data batch are checked, setting the state of the corresponding data batch to be in effect for use by outbound business.
For example, taking table 6 as an example, the first row in table 6 is recorded as header information of an original data file, and each row of original data records after the header includes original data corresponding to each field of the header. By comparing each field in the header information with each field in the corresponding outbound data template, the field type of each field in the header information can be determined, if the field type of the field 1 in the outbound data template is the basic field, the list of the original data (11-1 q) corresponding to the field 1 in the table 6 can be determined to be in accordance with the data record rule of the field 1 in the basic field, if the list of the original data does not accord with the data record rule, the corresponding original data record does not pass the verification, the list of the original data record cannot be stored in the outbound database of the outbound platform, and the reason of the verification failure is recorded, if each original data in a certain original data record accords with the data record rule of the corresponding template field, the list of the original data record accords with the data record rule, and through the verification, the list of the original data record is stored in the outbound database of the outbound platform for use of the outbound service, and the valid client number 1 of the data batch is determined, and when all the original data files in the data batch are finished, the verification state is set as the accumulated valid verification state.
In the embodiment provided by the invention, the original data file is analyzed through the outbound data template, and each original data record is checked, so that dirty data can be prevented from being stored in the outbound platform, the reading of invalid data when outbound service is executed is avoided, and the working efficiency is improved.
When the outbound platform processes the original data files in the data batch, the data batch can be set to be in a state, for example, the data batch is set to be in a cleaning state when the data batch is created, and the data batch is set to be in effect after all the original data files in the data batch are analyzed and verified, so that the data batch can be known in time.
In the embodiment provided by the invention, a data batch is created according to an upstream data system and a product to be processed, a current outbound data template of the product corresponding to the data batch is obtained from an outbound data template base, content analysis and validity verification are carried out on each original data file in the data batch according to the current outbound data template, and the original data records verified in the original data files are used as outbound data records and stored in an outbound database of an outbound platform. Because the above-mentioned processing procedure is that the outbound platform is in data butt joint with upstream data system, or the outbound platform processes the original data record to obtain the outbound data record, it is accomplished by using the shared basic field configured by the outbound platform and the outbound data template obtained by the custom field of the upstream data system configuration service scene, when the service scene changes, only the corresponding outbound data template needs to be added or modified, so that the data butt joint of both parties can be completed correctly, when the demand of outbound service changes, the secondary split field in the outbound data template can be modified or added to adjust outbound service, the whole procedure does not need to modify the program code of the outbound platform, so as to adapt to different demands of the service scene in time, thereby keeping the system of the outbound platform stable under the condition of quick response to the service demand, and further reducing the system risk and service risk of the outbound platform.
Based on the same inventive concept, in an embodiment of the present invention, an outbound platform is provided, and a specific implementation of an outbound data processing method of the outbound platform may refer to a description of an embodiment part of the method, and details are not repeated, and please refer to fig. 3, where the outbound platform includes:
A creating unit 301, configured to create a data batch from a plurality of original data files to be processed according to an upstream data system and a product to which the original data files belong, where the original data files are generated according to outbound data templates provided by the outbound platform, a base field shared in each outbound data template and a secondary split field for different outbound services are configured in the outbound platform, custom fields related to different service scenarios are configured in the upstream data system, and one outbound data template corresponds to one service scenario;
The obtaining unit 302 is configured to obtain a current outbound data template of a product corresponding to the data batch from an outbound data template library, where the outbound data template library is configured to store outbound data templates corresponding to various service scenarios, and one service scenario corresponds to one product;
And the processing unit 303 is configured to perform content analysis and validity verification on each original data file in the data batch according to the current outbound data template, and store the original data record verified in the original data file as an outbound data record in an outbound database of the outbound platform.
A possible implementation method, the outbound platform further includes a configuration unit 304, where the configuration unit 304 is configured to:
generating outbound data templates corresponding to service scenes according to information input by a user in a template configuration page, wherein the target configuration page is used for the user to configure outbound data templates of different service scenes;
and synchronizing each newly generated outbound data template to an upstream data system for providing an original data file for the outbound platform, so that the upstream data system exports data according to the data template of the corresponding service scene to form the original data file.
A possible implementation, the outbound data template includes:
a field type and a field attribute.
A possible implementation, the field type includes:
The base field is the basis for the upstream data system to export data, the custom field is the field added for different service scenes when the upstream data system exports data, and the secondary split field is the field for the outbound operator to screen outbound data records from the outbound database when executing outbound service.
A possible implementation, the field attribute includes:
Whether desensitized, rules for desensitization, whether to fill, whether to display, data type.
In one possible implementation manner, the field attribute of the secondary split field further includes a split type, and different split types correspond to different split rules.
In a possible implementation, the creating unit 301 is further configured to:
the method comprises the steps of regularly scanning a plurality of original data files received from each upstream data system, wherein the names of the original data files comprise the upstream data system and the product;
And classifying the original data files corresponding to the same product under the same upstream data system into the newly created same data batch according to the names of the original data files.
In a possible implementation manner, the processing unit 303 is further configured to:
Acquiring header information of the original data file, wherein the header information comprises fields of the original data record;
Acquiring a field position corresponding to a field consistent with a template field specified in the outbound data template from the header information;
verifying whether the data of the corresponding field position in the original data record accords with the data record rule according to the data record rule of the specified template field;
And if the data in the field positions corresponding to each specified template field in the original data record accords with the data record rule, determining that the corresponding original data record passes the verification, otherwise, determining that the corresponding original data record fails the verification, and recording the reason of the failure.
In a possible implementation manner, the processing unit 303 is further configured to:
accumulating one for each valid client number of the corresponding data batch when storing one outbound data record;
And when all the original data files in the data batch are verified, setting the state of the corresponding data batch to be in effect for use by outbound business.
It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a processor-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. The storage medium includes a U disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.
It should be noted that, the above device provided in the embodiment of the present invention can implement all the method steps implemented in the method embodiment and achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those in the method embodiment in this embodiment are omitted.
Based on the same inventive concept, the embodiment of the invention provides an outbound platform, which comprises at least one processor, and
A memory coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor, the at least one processor performing the outbound data processing method as described above by executing the instructions stored by the memory.
Based on the same inventive concept, an embodiment of the present invention also provides a computer readable storage medium, including:
The memory device is used for storing the data,
The memory is for storing instructions that, when executed by the processor, cause an apparatus comprising the computer readable storage medium to perform a method of outbound data processing as described above.
The readable storage medium may be any available medium or data storage device that can be accessed by a processor, including volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. By way of example, and not limitation, nonvolatile Memory can include Read-Only Memory (ROM), programmable ROM (Programmable Read-Only Memory, PROM), electrically programmable ROM (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable ROM (ELECTRICALLY ERASABLE PROGRAMMABLE READ ONLY MEMORY, EEPROM) or flash Memory, solid state disk (Solid state STATE DISK or Solid state STATE DRIVE, SSD), magnetic Memory (e.g., floppy disk, hard disk, magnetic tape, magnetic-Optical disk (MO), etc.), optical Memory (e.g., CD, DVD, BD, HVD, etc.). Volatile memory can include random access memory (Random Access Memory, RAM), which can act as external cache memory. By way of example, and not limitation, RAM is available in a variety of forms, such as dynamic RAM (Dynamic Random Access Memory, DRAM), synchronous DRAM (Synchronous Dynamic Random-Access Memory, SDRAM), double data rate SDRAM (Double DATA RATE SDRAM, DDR SDRAM), enhanced SDRAM (Enhanced Synchronous DRAM, ESDRAM), synchronous link DRAM (SYNC LINK DRAM, SLDRAM). The storage devices of the disclosed aspects are intended to comprise, without being limited to, these and other suitable types of memory.
Based on the same inventive concept, a computer program product is provided in an embodiment of the present application, which comprises program code for causing a computer device to carry out the steps of the method of outbound data processing according to the various exemplary embodiments of the application described in the present specification when the program product is run on the computer device.
It will be appreciated by those skilled in the art that embodiments of the invention may be provided as a method, system, or program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Moreover, embodiments of the invention may take the form of a computer program product embodied on one or more readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer/processor-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These program instructions may also be stored in a readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer/processor implemented process such that the instructions which execute on the computer/processor or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.