CN114091424A - Outbound call data processing method, outbound call platform and computer readable storage medium - Google Patents
Outbound call data processing method, outbound call platform and computer readable storage medium Download PDFInfo
- Publication number
- CN114091424A CN114091424A CN202111437875.4A CN202111437875A CN114091424A CN 114091424 A CN114091424 A CN 114091424A CN 202111437875 A CN202111437875 A CN 202111437875A CN 114091424 A CN114091424 A CN 114091424A
- Authority
- CN
- China
- Prior art keywords
- data
- outbound
- outbound call
- field
- template
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003860 storage Methods 0.000 title claims abstract description 21
- 238000003672 processing method Methods 0.000 title description 5
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 79
- 238000000034 method Methods 0.000 claims abstract description 50
- 238000012795 verification Methods 0.000 claims abstract description 36
- 238000012545 processing Methods 0.000 claims abstract description 27
- 238000004458 analytical method Methods 0.000 claims abstract description 10
- 238000000586 desensitisation Methods 0.000 claims description 22
- 230000000694 effects Effects 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012216 screening Methods 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 10
- 238000013499 data model Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 210000001503 joint Anatomy 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000009795 derivation Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/186—Templates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Artificial Intelligence (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for processing outbound data in the field of intelligent service, 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, and comprise the following steps: creating a data batch for a plurality of original data files to be processed according to the upstream data system and the product; the original data file is generated according to an outbound data template provided by an outbound platform, common basic fields in each outbound data template 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 an upstream data system, and one outbound data template corresponds to one service scene; acquiring a current outbound data template of a product corresponding to a data batch from an outbound data template base, and performing content analysis and validity check on each original data file in the data batch according to the current outbound data template; and storing the original data record passing the verification into the outbound platform.
Description
Technical Field
The present invention relates to the field of intelligent services, and in particular, to a method for processing outbound data, an outbound platform, and a computer-readable storage medium.
Background
The telephone call-out is an important channel in the field of customer service, and can directly contact and reach customers by means of the telephone call-out, and directly communicate with the customers, facilitate on-line transaction, and develop the call-out service in various business scenes such as marketing, notification, customer care and the like.
For an enterprise or an organization comprising a plurality of branch companies and offices, the branch companies or the offices are not provided with the outbound service independently, but the outbound service is provided by an outbound platform of the enterprise or the organization uniformly, so that the outbound platform is required to continuously collect original data supporting the outbound service from systems of the branch companies and the offices.
Because the original data required by different service scenes are different, when the outbound platform collects the original data, the original data are usually collected according to the service scenes, different data models are designed for different service scenes, and the collected original data are processed into outbound data by using the data models and stored in corresponding databases. The disadvantage of this method is that when the data model and database are changed, the software code of the outbound platform needs to be rewritten and the rewritten software code needs to be reissued, and then the original data can be collected after the software code is re-interfaced with the software of each branch company and each office.
However, with the continuous change of the customer requirements, the business scenarios of the corresponding enterprises are also changing and are developing in a more diversified and rapidly changing trend, so that the outbound platform needs to continuously add new data models, modify existing data models, repeatedly modify software codes and rapidly update software versions in an iterative manner. Because the iterative update of the software version usually requires a long development period, the service requirement cannot be responded in time by quickly iterating the software version in practical application, and the frequent iterative update of the software version further causes a new system defect to appear in the software system of the outbound platform, which brings system risk and service risk.
Therefore, how to reduce the system risk and the business risk of the outbound platform becomes a technical problem to be solved urgently under the condition of quickly responding to the business requirement.
Disclosure of Invention
The invention provides a method for processing outbound data, an outbound platform and a computer readable storage medium, which are used for solving the technical problem that the outbound platform has higher system risk and service risk in the prior art.
In a first aspect, to solve the above technical problem, an outbound data processing method provided in an embodiment of the present invention is applied to an outbound platform, and a technical solution of the method is as follows:
creating a data batch for a plurality of original data files to be processed according to the upstream data system and the product; the original data file is generated according to outbound data templates provided by the outbound platform, common basic fields 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;
acquiring a current outbound data template of a product corresponding to the data batch from an outbound data template library; the outbound data template base is used for storing outbound data templates corresponding to all service scenes, and one service scene corresponds to one product;
according to the current outbound data template, performing content analysis and validity check on each original data file in the data batch;
and 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 the outbound platform.
In one possible embodiment, before creating a data batch from a plurality of raw data files to be processed according to the upstream data system and the product, the method further includes:
generating an outbound data template corresponding to a service scene according to information input by a user in a template configuration page; the target configuration page is used for configuring outbound data templates of different service scenes by a user;
and synchronizing each newly generated outbound data template to an upstream data system 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.
In one possible embodiment, the outbound data template includes:
field type and field attributes.
One possible implementation, the field type, includes:
the base field, the custom field, the secondary split field; the basic field is a basis for the data exported by the upstream data system, the custom field is a field added by the upstream data system for different service scenes when the data is exported, and the secondary split field is a field for screening the outbound data record from the outbound database when the outbound server executes the outbound service.
One possible implementation, the field attribute, includes:
whether desensitization, desensitization rules, whether padding is necessary, whether display is present, data type.
In a 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 way, creating a data batch by a plurality of original data files to be processed according to the upstream data system and the product, includes:
periodically scanning a plurality of original data files received from each upstream data system; the name of the original data file comprises an upstream data system and a product;
and classifying the original data files corresponding to the same product belonging to the same upstream data system into the newly created same data batch according to the names of the original data files.
One possible implementation manner, in which content analysis and validity check are performed on each original data file in the data batch according to the current outbound data template, includes:
acquiring header information of the original data file, wherein the header information comprises a field of the original data record;
acquiring a field position corresponding to a field consistent with a specified template field in the outbound data template from the header information;
according to the data recording rule of the specified template field, verifying whether the data of the corresponding field position in the original data record conforms to the data recording rule;
and if the data of the field position corresponding to each appointed template field in the original data record conforms to the data record rule, determining that the corresponding original data record passes verification, otherwise, determining that the corresponding original data record does not pass verification, and recording the reason why the corresponding original data record does not pass verification.
A possible implementation manner, after the original data record passing the verification in the original data file is taken as the outbound data record and stored in the outbound database of the outbound platform, further includes:
when one outbound data record is stored, the effective number of clients corresponding to the data batch is accumulated by one;
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 the outbound service.
In a second aspect, an embodiment of the present invention provides an outbound platform, including:
the creating unit is used for creating data batches from a plurality of original data files to be processed according to the upstream data systems and the products; the original data file is generated according to outbound data templates provided by the outbound platform, common basic fields 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;
the acquisition unit is used for acquiring the current outbound data template of the product corresponding to the data batch from the outbound data template base; the outbound data template base is used for storing outbound data templates corresponding to all service scenes, and one service scene corresponds to one product;
the verification unit is used for analyzing the content and verifying the validity of each original data file in the data batch according to the current outbound data template;
and the processing unit is used for recording the original data 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, wherein the outbound platform further comprises a configuration unit, and the configuration unit is configured to:
generating an outbound data template corresponding to a service scene according to information input by a user in a template configuration page; the target configuration page is used for configuring outbound data templates of different service scenes by a user;
and synchronizing each newly generated outbound data template to an upstream data system 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.
In one possible embodiment, the outbound data template includes:
field type and field attributes.
One possible implementation, the field type, includes:
the base field, the custom field, the secondary split field; the basic field is a basis for the data exported by the upstream data system, the custom field is a field added by the upstream data system for different service scenes when the data is exported, and the secondary split field is a field for screening the outbound data record from the outbound database when the outbound server executes the outbound service.
One possible implementation, the field attribute, includes:
whether desensitization, desensitization rules, whether padding is necessary, whether display is present, data type.
In a 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 is further configured to:
periodically scanning a plurality of original data files received from each upstream data system; the name of the original data file comprises an upstream data system and a product;
and classifying the original data files corresponding to the same product belonging to 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, the verification unit is further configured to:
acquiring header information of the original data file, wherein the header information comprises a field of the original data record;
acquiring a field position corresponding to a field consistent with a specified template field in the outbound data template from the header information;
according to the data recording rule of the specified template field, verifying whether the data of the corresponding field position in the original data record conforms to the data recording rule;
and if the data of the field position corresponding to each appointed template field in the original data record conforms to the data record rule, determining that the corresponding original data record passes verification, otherwise, determining that the corresponding original data record does not pass verification, and recording the reason why the corresponding original data record does not pass verification.
In one possible embodiment, the processing unit is further configured to:
when one outbound data record is stored, the effective number of clients corresponding to the data batch is accumulated by one;
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 the outbound service.
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, and the at least one processor performs the method according to the first aspect by executing the instructions stored by the memory.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, including:
a memory for storing a plurality of data to be transmitted,
the memory is for storing 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, the present invention further provides a computer program product containing computer-executable instructions for causing a computer to execute the method according to the first aspect.
Through the technical solutions in one or more of the above embodiments of the present invention, the embodiments of the present invention have at least the following technical effects:
in the embodiment provided by the invention, a data batch is created by a plurality of original data files to be processed according to the upstream data system and the product; acquiring a current outbound data template of a product corresponding to a data batch from an outbound data template base; according to the current outbound data template, analyzing the content and verifying the legality of each original data file in the data batch; and recording the original data passing 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. Because the processing process is completed by using the common basic field configured by the outbound platform and the outbound data template obtained by configuring the customized field specific to the service scene by the upstream data system, regardless of the data butt joint of the outbound platform and the upstream data system or the outbound data record obtained by processing the original data record by the outbound platform, when the service scene changes, the data butt joint of the two parties can be correctly completed only by adding or modifying the corresponding outbound data template, when the demand of the outbound service changes, the secondary split field in the outbound data template can be modified or added for the outbound service adjustment, and the whole process can be adapted to different demands of the service scene in time without modifying the program code of the outbound platform, thereby keeping the system of the outbound platform stable under the condition of quickly responding to the service demand, and further, the system risk and the service risk of the outbound platform are reduced.
Drawings
Fig. 1 is a flow chart of outbound data processing according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a relationship between an outbound platform of a bank a and each branch and branch bank according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of an outbound platform according to an embodiment of the present invention.
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 problem that the outbound platform has higher system risk and service risk in the prior art.
In order to better understand the technical solutions of the present invention, the following detailed descriptions of the technical solutions of the present invention are provided with the accompanying drawings and the specific embodiments, and it should be understood that the specific features in the embodiments and the examples of the present invention are the detailed descriptions of the technical solutions of the present invention, and are not limitations of the technical solutions of the present invention, and the technical features in the embodiments and the examples of the present invention may be combined with each other without conflict. According to the technical scheme, the data acquisition, storage, use, processing and the like meet 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.
Step 101: creating a data batch for a plurality of original data files to be processed according to the upstream data system and the product; the original data file is generated according to outbound data templates provided by an outbound platform, common basic fields 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 an upstream data system, and one outbound data template corresponds to one service scene.
The method comprises the following steps of creating a data batch by a plurality of original data files to be processed according to an upstream data system and a product, wherein the data batch can be created by the following modes:
fig. 2 is a schematic diagram of a relationship between an outbound platform of a bank a and each branch and branch bank according to an embodiment of the present invention.
The bank A comprises n branches in the whole country, each branch comprises a plurality of branches, for example, the branch 1 comprises a branch 1-branch m, the branch n comprises a branch 1-branch k, each branch and branch under the bank A need to provide an original data file for an outbound platform of the bank A, and data systems of the branches and branches are called as an upstream data system.
A user can configure a page through a template configuration page in the outbound platform, the outbound data templates of each service scene are configured, specifically, basic fields which are contained in each outbound data template can be configured, secondary splitting fields aiming at different outbound services can be configured, optional fields can be provided for an upstream data system for the custom fields, the total number of the custom fields can also be specified, after the outbound platform synchronizes the configured outbound data templates to the upstream data system, the outbound data platform can configure required fields aiming at different service scenes. If 10 basic fields and 6 secondary splitting fields are configured in the outbound platform, each outbound data template synchronized to the upstream data system should include 10 basic fields configured by the outbound platform, taking branch 1 and branch 3 as examples, branch 1 defines 3 custom fields for service scenario 1, and branch 3 defines 1 custom field for service scenario 5, then in the original data file provided by branch 1 to the outbound platform for service scenario 1, each original data record includes data of the 10 basic fields and 3 custom fields; the branch 3 provides the calling platform with the original data file for the service scenario 5, and each original data record contains the data of the 10 basic fields and 1 custom field. The original data files of other service scenes can be obtained by analogy.
Periodically scanning a plurality of original data files received from each upstream data system; the name of the original data file comprises an upstream data system and a product; and classifying the original data files corresponding to the same product belonging to 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 by the branch 1 to the outbound platform in fig. 2 include a raw data file 1A to a raw data file 1F, wherein the raw data file 1A, the raw data file 1C, and the raw data file 1E all belong to the product a, the raw data files provided by the branch 3 to the outbound platform include a raw data file 3A to a raw data file 3F, wherein the raw data file 3C, the raw data file 3D, and the raw data file 3E all belong to the product a, the raw data files belonging to the branch 1 and belonging to the product a are created into one data batch 1A (including the raw data file 1A, the raw data file 1C, and the raw data file 1E), the raw data files belonging to the branch 3 and belonging to the product a are created into another data batch 3A (including the raw data file 3C, b, C, Original data file 3D, original data file 3E).
In the embodiment provided by the invention, a 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 service 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 common basic field configured by the outbound platform and the customized field specific to the service scene configured by the upstream data system are butted between the outbound platform and the upstream data system, when the service scene changes, the data butting of the two parties can be correctly completed only by adding or modifying the corresponding outbound data template, and the whole process can be adapted to different requirements of the service scene in time without modifying the program code 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 a plurality of original data files to be processed are used for creating data batches according to the affiliated upstream data system and the affiliated product, an outbound data template for data docking between the upstream data system and an outbound platform needs to be configured, which can be realized by the following specific means:
generating an outbound data template corresponding to a service scene according to information input by a user in a template configuration page; the target configuration page is used for configuring outbound data templates of different service scenes by a user; and synchronizing each newly generated outbound data template to an upstream data system 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.
The outbound data template includes a field type and a field attribute.
The field types include: basic field, self-defined field and secondary split field; the basic field is the basis of the data exported by the upstream data system, the custom field is the field added by the upstream data system aiming at different service scenes when exporting the data, and the secondary split field is the field for screening the outbound data record from the outbound database when the outbound server executes the outbound service.
The field attributes include: whether desensitization, desensitization rules, whether padding is necessary, whether display is present, data type.
The template fields in the basic fields are usually included in the outbound data template of each service scenario, and the upstream data system can use this as a specification (i.e. basis) for data derivation, and the user can configure the chinese name and english name of each field in the configuration of the basic fields in 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 table 1 as configuration information of the basic field. After the basic fields are configured as shown in table 1, the basic fields in each outbound data template include the template fields in table 1, and the corresponding template fields in the generated original data file use the corresponding configured Chinese names or English names in table 1 as original data.
It should be noted that the template fields corresponding to the basic information and the custom information in table 1 are different, and the corresponding chinese and english names are also different, for example, the chinese name 1 and english name 1 corresponding to the basic information field 1 cannot be identical to the chinese name 1 and english name 1 corresponding to the custom information field 1.
For the self-defined field in the outbound data template, the upstream data system can self-define the corresponding Chinese name and English name according to the requirements of different service scenes, and configure the field attribute of the self-defined field. Please refer to table 2 for configuration information of field attributes of the custom fields provided in the embodiment of the present invention.
TABLE 2
In table 2, whether desensitization is performed or not is used to perform desensitization display on data in the custom field or not when performing subsequent data display, and if desensitization display is performed, a range corresponding to desensitization can be specified.
The desensitization rule is used for specifically specifying a desensitization rule, and the desensitization rule which can be supported includes desensitization on specified information, for example, desensitization on information 1 can be specified, desensitization on information 1 and information 3 can also be specified, and the desensitization rule can be freely set by a user of an upstream data system.
And whether the fields need to be filled or not is used for indicating whether the corresponding custom fields are the fields which need to be filled or not in the process of executing the outbound service transaction.
And whether to display or not is used for indicating whether the corresponding custom field is displayed or not in the process of executing the outbound service handling, and if the custom field is displayed, the range of the displayed object can be specified.
And 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 the outbound service 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, and in an upstream data system (a branch), for a new requirement of a service scenario of its product B, a chinese name of a custom field in the outbound data template defining the service scenario is a chinese name B and an english name is 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 by using corresponding values encoded in table 2, e.g., the desensitization rule of the custom field is configured as "information 3 encoding", and when the original data file is generated, the desensitization rule of the custom field desensitizes data containing information 3 in the field.
The outbound data template comprises basic fields which are required to be contained by each outbound data template which is predefined in the outbound data platform, custom fields which are defined in an upstream data system according to system requirements of different service scenes, and secondary splitting fields which are defined in the outbound platform according to different outbound services, wherein the required outbound data records can be split for different outbound services through different configurations of the secondary splitting fields and are used by outbound service personnel.
The field attribute of the secondary splitting field can comprise a splitting type besides the field attribute in the custom field, and different splitting types correspond to different splitting rules. Please refer to table 3 for configuration information of the split type provided in the embodiment of the present invention.
TABLE 3
Please refer to table 4 for configuration information of the customer care outbound data template provided by the embodiment of the present invention.
TABLE 4
Please refer to table 5 for a local data record in the upstream data system according to the embodiment of the present invention.
TABLE 5
| Serial number | Field 1 | Field 2 | Field 3 | Field 4 | Field 5 | Field 6 |
| 1 | Data 11 | Data 21 | Data 31 | Data 41 | Data 51 | Data 61 |
| 2 | Data 12 | Data 22 | Data 32 | Data 42 | Data 52 | Data 62 |
| 3 | Data 13 | Data 23 | Data 33 | Data 43 | Data 53 | Data 63 |
| … | … | … | … | … | … | … |
| q | Data 1q | Data 2q | Data 3q | Data 4q | Data 5q | Data 6q |
In an outbound data template, the basic fields include fields 3 to 5, the custom fields include field 1, and the upstream data system extracts data from the local data records (table 5) according to the outbound data template to form an original outbound data file, as shown in table 6, where table 6 is an original data record table of the outbound data file provided by the embodiment of the present invention.
TABLE 6
| Serial number | Field 1 | Field 3 | Field 4 | Field 5 |
| 1 | Data 11 | Data 31 | Data 41 | Data 51 |
| 2 | Data 12 | Data 32 | Data 42 | Data 52 |
| 3 | Data 13 | Data 33 | Data 43 | Data 53 |
| … | … | … | … | … |
| q | Data 1q | Data 3q | Data 4q | Data 5q |
After receiving the original data files provided by each upstream data system, the outbound platform can change the original data files to be processed into original data files to be processed at the designated position by scanning at regular time, and creates corresponding data batches according to the upstream data system to which the original data files belong and the product.
After the data batch is created, step 102 may be performed.
Step 102: acquiring a current outbound data template of a product corresponding to a data batch from an outbound data template base; the outbound data template base is used for storing outbound data templates corresponding to all service scenes, and one service scene corresponds to one product.
For example, the data batch comprises an original data file 1 to an original data file 3, the corresponding products of the original data files are a product A, and a corresponding current outbound data template is obtained from an outbound data template library of the outbound platform according to the product number of the product A.
After the current outbound data template corresponding to the data batch is obtained, steps 103-104 may be performed.
Step 103: and according to the current outbound data template, performing content analysis and validity check on each original data file in the data batch.
Step 104: and recording the original data passing 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.
According to the current outbound data template, each original data file in the data batch is subjected to content analysis and validity check, and the method can be realized in the following modes:
acquiring header information of an original data file, wherein the header information comprises a field of an original data record; acquiring a field position corresponding to a field consistent with a specified template field in the outbound data template from the header information; verifying whether the data of the corresponding field position in the original data record conforms to the data recording rule or not according to the data recording rule of the specified template field; and if the data of the field position corresponding to each appointed template field in the original data record conforms to the data record rule, determining that the corresponding original data record passes verification, otherwise, determining that the corresponding original data record does not pass verification, and recording the reason why the corresponding original data record does not pass verification.
After the original data record passing the verification in the original data file is taken as the outbound data record and stored in the outbound database of the outbound platform, the method also comprises the following steps:
when one outbound data record is stored, the effective number of clients corresponding to the data batch is accumulated by one; 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 the outbound service.
For example, taking table 6 as an example, the first row in table 6 is denoted as header information of the original data file, and each row after the header is an original data record, and each row of the original data record includes original data corresponding to each field of the header. Comparing each field in the header information with each field in the corresponding outbound data template, determining the field type of each field in the header information, if the field 1 in the table 6 is successfully compared with the field 1 in the outbound data template, and the field type of the field 1 in the outbound data template is a basic field, determining that a list of original data (number 11-data 1q) corresponding to the field 1 in the table 6 should accord with the data recording rule of the field 1 in the basic field, if the field 1 in the outbound data template does not accord with the data recording rule, determining that the original data record is illegal data, and if the original data record does not pass verification, failing to store the original data record in the outbound database of the outbound platform, and recording the reason of the verification failure; if each original data in a certain original data record accords with the data record rule of the corresponding template field, determining that the original data record accords with the data record rule, storing the original data record into an outbound database of an outbound platform for outbound service through verification, accumulating the effective customer number of the data batch by 1, and setting the state of the original data record to be effective when all the original data files in the data batch are verified.
In the embodiment provided by the invention, the original data file is analyzed through the outbound data template, and each original data record is verified, so that dirty data can be prevented from being stored in the outbound platform, reading in of invalid data during the execution of the outbound service is avoided, and the working efficiency is improved.
When the outbound platform processes the original data files in the data batch, it can also set the state for the data batch, for example, set the state as a cleaning state when the data batch is created, and set the state of the data batch as effective after the analysis and verification of all the original data files in the data batch are completed, so that the state of the data batch can be known in time.
In the embodiment provided by the invention, a data batch is created by a plurality of original data files to be processed according to the upstream data system and the product; acquiring a current outbound data template of a product corresponding to a data batch from an outbound data template base; according to the current outbound data template, analyzing the content and verifying the legality of each original data file in the data batch; and recording the original data passing 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. Because the processing process is completed by using the common basic field configured by the outbound platform and the outbound data template obtained by configuring the customized field specific to the service scene by the upstream data system, regardless of the data butt joint of the outbound platform and the upstream data system or the outbound data record obtained by processing the original data record by the outbound platform, when the service scene changes, the data butt joint of the two parties can be correctly completed only by adding or modifying the corresponding outbound data template, when the demand of the outbound service changes, the secondary split field in the outbound data template can be modified or added for the outbound service adjustment, and the whole process can be adapted to different demands of the service scene in time without modifying the program code of the outbound platform, thereby keeping the system of the outbound platform stable under the condition of quickly responding to the service demand, and further, the system risk and the service risk of the outbound platform are reduced.
Based on the same inventive concept, an embodiment of the present invention provides an outbound platform, where specific implementation manners of an outbound data processing method of the outbound platform may refer to descriptions in the method embodiment, and repeated descriptions are omitted, please refer to fig. 3, where the outbound platform includes:
the creating unit 301 is configured to create a data batch from a plurality of original data files to be processed according to the corresponding upstream data system and the corresponding product; the original data file is generated according to outbound data templates provided by the outbound platform, common basic fields 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;
an obtaining unit 302, configured to obtain a current outbound data template of a product corresponding to the data batch from an outbound data template library; the outbound data template base is used for storing outbound data templates corresponding to all service scenes, and one service scene corresponds to one product;
a processing unit 303, configured to perform content analysis and validity check on each original data file in the data batch according to the current outbound data template; and 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 the outbound platform.
A possible implementation method, the outbound platform further comprises a configuration unit 304, and the configuration unit 304 is configured to:
generating an outbound data template corresponding to a service scene according to information input by a user in a template configuration page; the target configuration page is used for configuring outbound data templates of different service scenes by a user;
and synchronizing each newly generated outbound data template to an upstream data system 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.
In one possible embodiment, the outbound data template includes:
field type and field attributes.
One possible implementation, the field type, includes:
the base field, the custom field, the secondary split field; the basic field is a basis for the data exported by the upstream data system, the custom field is a field added by the upstream data system for different service scenes when the data is exported, and the secondary split field is a field for screening the outbound data record from the outbound database when the outbound server executes the outbound service.
One possible implementation, the field attribute, includes:
whether desensitization, desensitization rules, whether padding is necessary, whether display is present, data type.
In a 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:
periodically scanning a plurality of original data files received from each upstream data system; the name of the original data file comprises an upstream data system and a product;
and classifying the original data files corresponding to the same product belonging to 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, the processing unit 303 is further configured to:
acquiring header information of the original data file, wherein the header information comprises a field of the original data record;
acquiring a field position corresponding to a field consistent with a specified template field in the outbound data template from the header information;
according to the data recording rule of the specified template field, verifying whether the data of the corresponding field position in the original data record conforms to the data recording rule;
and if the data of the field position corresponding to each appointed template field in the original data record conforms to the data record rule, determining that the corresponding original data record passes verification, otherwise, determining that the corresponding original data record does not pass verification, and recording the reason why the corresponding original data record does not pass verification.
In a possible implementation, the processing unit 303 is further configured to:
when one outbound data record is stored, the effective number of clients corresponding to the data batch is accumulated by one;
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 the outbound service.
It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
It should be noted that, the apparatus provided in the embodiment of the present invention can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.
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, and the at least one processor performs the method of outbound data processing as described above by executing the instructions stored by the memory.
Based on the same inventive concept, an embodiment of the present invention further provides a computer-readable storage medium, including:
a memory for storing a plurality of data to be transmitted,
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 outgoing 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 non-volatile memory, or may include both volatile and non-volatile memory. By way of example and not limitation, nonvolatile Memory may include Read-Only Memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash Memory, Solid State Disk (SSD), magnetic Memory (e.g., floppy Disk, hard Disk, magnetic tape, Magneto-Optical Disk (MO), etc.), Optical Memory (e.g., CD, BD, DVD, HVD, etc.), and so forth. Volatile Memory can include Random Access Memory (RAM), which can act as external cache Memory. By way of example and not limitation, RAM is available in many forms, such as Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchronous 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, an embodiment of the present invention provides a computer program product comprising program code for causing a computer device to perform the steps of the method for outgoing data processing according to various exemplary embodiments of the present application described above in this specification, when the program product is run on the computer device.
As will be appreciated by one skilled in the art, embodiments of the present 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. Furthermore, 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, and the like) 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (13)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111437875.4A CN114091424A (en) | 2021-11-30 | 2021-11-30 | Outbound call data processing method, outbound call platform and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111437875.4A CN114091424A (en) | 2021-11-30 | 2021-11-30 | Outbound call data processing method, outbound call platform and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114091424A true CN114091424A (en) | 2022-02-25 |
Family
ID=80305626
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111437875.4A Pending CN114091424A (en) | 2021-11-30 | 2021-11-30 | Outbound call data processing method, outbound call platform and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114091424A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115103076A (en) * | 2022-06-17 | 2022-09-23 | 中国平安财产保险股份有限公司 | Outbound method, device, computer equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1999013426A1 (en) * | 1997-09-11 | 1999-03-18 | Abb Power T & D Company Inc. | Automated meter reading system |
| CN107229466A (en) * | 2017-05-04 | 2017-10-03 | 中国建设银行股份有限公司 | Method, system and the storage medium of business development are carried out for enterprise branch office |
| CN109814856A (en) * | 2019-01-17 | 2019-05-28 | 平安科技（深圳）有限公司 | Data entry method, device, terminal and computer readable storage medium |
| CN110457312A (en) * | 2019-07-05 | 2019-11-15 | 中国平安财产保险股份有限公司 | Acquisition method, device, equipment and the readable storage medium storing program for executing of diversiform data |
| CN112148711A (en) * | 2020-09-21 | 2020-12-29 | 建信金融科技有限责任公司 | Processing method and device for batch processing tasks |
| CN112883029A (en) * | 2021-02-07 | 2021-06-01 | 中国工商银行股份有限公司 | Service processing method and device for real estate registration center |
-
2021
- 2021-11-30 CN CN202111437875.4A patent/CN114091424A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1999013426A1 (en) * | 1997-09-11 | 1999-03-18 | Abb Power T & D Company Inc. | Automated meter reading system |
| CN107229466A (en) * | 2017-05-04 | 2017-10-03 | 中国建设银行股份有限公司 | Method, system and the storage medium of business development are carried out for enterprise branch office |
| CN109814856A (en) * | 2019-01-17 | 2019-05-28 | 平安科技（深圳）有限公司 | Data entry method, device, terminal and computer readable storage medium |
| CN110457312A (en) * | 2019-07-05 | 2019-11-15 | 中国平安财产保险股份有限公司 | Acquisition method, device, equipment and the readable storage medium storing program for executing of diversiform data |
| CN112148711A (en) * | 2020-09-21 | 2020-12-29 | 建信金融科技有限责任公司 | Processing method and device for batch processing tasks |
| CN112883029A (en) * | 2021-02-07 | 2021-06-01 | 中国工商银行股份有限公司 | Service processing method and device for real estate registration center |
Non-Patent Citations (1)
| Title |
|---|
| 刘寒;孙晶;: "金融业大数据应用研究", 电信网技术, no. 02, 15 February 2015 (2015-02-15) * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115103076A (en) * | 2022-06-17 | 2022-09-23 | 中国平安财产保险股份有限公司 | Outbound method, device, computer equipment and storage medium |
| CN115103076B (en) * | 2022-06-17 | 2024-05-31 | 中国平安财产保险股份有限公司 | Outbound method, outbound device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112100052B (en) | A playback method and device for an interface test scene | |
| CN112612813A (en) | Test data generation method and device | |
| CN109871309A (en) | Method and system for generating test case for billing system | |
| CN109214785A (en) | Implementation method, server and the system of workflow | |
| CN112308727A (en) | Insurance claim settlement service processing method and device | |
| CN113037505B (en) | Method and system for realizing trusted Web application | |
| CN112307297B (en) | User identification unification method and system based on priority rule | |
| CN115049365B (en) | Application of production information processing method, device, and computer equipment | |
| CN114091424A (en) | Outbound call data processing method, outbound call platform and computer readable storage medium | |
| CN114756466A (en) | A test case acquisition method, device and storage medium | |
| WO2019019737A1 (en) | Product data processing system and method, server and storage medium | |
| CN118939635A (en) | Data migration method, device, terminal device and computer readable storage medium | |
| CN114138787B (en) | A barcode recognition method, device and medium | |
| CN114356848A (en) | Metadata management method, computer storage medium and electronic device | |
| CN113407456A (en) | Verification method, device, equipment and storage medium of reconstruction system | |
| CN112613988A (en) | Method and device for generating credit investigation index information | |
| CN111767343A (en) | Test data synchronization method and device based on message queue, equipment and medium | |
| CN114662007B (en) | Data recommendation method and device, computer equipment and storage medium | |
| CN118827818B (en) | A protocol configuration management method, system, terminal device and readable storage medium | |
| CN117827832B (en) | Data verification method, device, computer equipment and storage medium | |
| CN114490663B (en) | Data processing method and device | |
| CN113176943B (en) | Multi-environment consistency deployment method and device | |
| CN111209292A (en) | Bin data management method, device and system | |
| CN115509943A (en) | Interface modification test method and device, storage medium and equipment | |
| CN118820045A (en) | Resource calendar service testing method, device, electronic device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |