Business processing method and device
By converting business data into interface data and determining the validation logic based on the matching type field, the problems of long development cycles and large workloads in existing technologies are solved, and flexible business data validation processing is achieved.
Patent Information
- Application Number
- CN202511400315.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-09-28
- Publication Date
- 2025-12-19
AI Technical Summary
In existing technologies, the verification and processing logic for different business data needs to be hard-coded separately, resulting in long development cycles and a heavy workload for technical personnel.
By using a general interface to convert business data into interface data and determining the validation logic based on the value of the matching type field, validation processing for different types of business data can be achieved without writing dedicated validation code for each type of business data.
It shortens the development cycle, reduces the workload of technical personnel, and enables flexible verification and processing of different business data, making it suitable for various verification scenarios.
Smart Images
Figure CN121166801A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of computer, and in particular, to a service processing method and device. BACKGROUND
[0002] Before service data is processed, data verification is usually needed. Therefore, different verification processing logic needs to be provided for different service data. At present, the verification processing logic for different service data is mainly realized by means of hard coding. The hard coding method needs to write verification codes for different service data respectively, which is time-consuming and requires a large amount of work of technical personnel. SUMMARY
[0003] Therefore, the embodiments of the present application provide a service processing method and device, which can shorten the development period and reduce the workload of technical personnel without writing verification codes for different service data.
[0004] In a first aspect, the embodiments of the present application provide a service processing method, comprising:
[0005] receiving service data;
[0006] converting the service data into interface data by using a general interface; wherein the interface data comprises the values of at least one type field and the values of at least one service field;
[0007] determining at least one matching type field from the at least one type field according to a verification scenario corresponding to the service data;
[0008] determining verification logic according to the values of the matching type fields in the interface data;
[0009] performing verification processing on the values of the service fields in the interface data by using the verification logic, and performing service processing on the service data according to the verification result.
[0010] Optionally, determining the verification logic according to the values of the matching type fields in the interface data comprises:
[0011] setting the matching values of the non-matching fields to default values in response to the existence of the non-matching fields in the at least one type field;
[0012] matching at least one configuration record corresponding to the service data from a configuration table according to the values of the matching type fields in the interface data and the matching values of the non-matching fields;
[0013] generating the verification logic according to the at least one configuration record.
[0014] Optionally, generating the verification logic according to the at least one configuration record comprises:
[0015] According to the check service field, the check type and the check operation in the configuration record, a check sub-logic corresponding to the configuration record is generated;
[0016] The check sub-logics corresponding to the configuration records are combined to generate a check logic.
[0017] Optionally, after the value of each unmatched service field is set to a default value, the method further comprises:
[0018] In response to the fact that the configuration record corresponding to the service data does not exist in the configuration table, it is determined that the service data fails to pass the check, and alarm information corresponding to the service data is generated and sent.
[0019] Optionally, according to the check result, the service data is processed, comprising:
[0020] In response to the fact that the check result indicates that the check is passed, service processing logic corresponding to the service data is determined; and the service processing logic is executed on the service data.
[0021] In response to the fact that the check result indicates that the check is failed, alarm information corresponding to the check result is generated and sent.
[0022] Optionally, according to the check result, the service data is processed, comprising:
[0023] In response to the fact that the check result indicates that the check is passed, filling logic corresponding to the interface data is determined;
[0024] The filling fields in the service data are filled by using the filling logic.
[0025] In a second aspect, an embodiment of the present application provides a service processing device, comprising:
[0026] A data receiving module is configured to receive service data.
[0027] A data conversion module is configured to convert the service data into interface data by using a general interface; wherein the interface data comprises the value of at least one type field and the value of at least one service field.
[0028] A field determining module is configured to determine at least one matching type field from the at least one type field according to a check scenario corresponding to the service data.
[0029] A logic determining module is configured to determine a check logic according to the value of each matching type field in the interface data.
[0030] A service processing module is configured to perform check processing on the value of the service field in the interface data by using the check logic, and to perform service processing on the service data according to the check result.
[0031] In a third aspect, an embodiment of the present application provides an electronic device, comprising:
[0032] one or more processors;
[0033] a storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the method of any of the above embodiments.
[0034] In a fourth aspect, an embodiment of the present application provides a computer readable medium, having stored thereon a computer program, the program being executed by a processor to implement the method of any of the above embodiments.
[0035] In a fifth aspect, an embodiment of the present application provides a computer program product, comprising a computer program, the computer program being executed by a processor to implement the method of any of the above embodiments.
[0036] An embodiment of the above application has the following advantages or beneficial effects: the business data is converted into interface data by using a general interface. The checking logic is determined according to the values of the matching type fields corresponding to the checking scenarios in the interface data. The values of the business fields in the interface data are checked by using the checking logic, and the business data is processed accordingly.
[0037] By using the general interface, the business data from different source systems can be converted into interface data with a unified data structure. By configuring multiple checking scenarios, matching type fields corresponding to the checking scenarios and checking logic, the checking processing of different business data can be implemented. There is no need to write checking codes for different business data, which can shorten the development cycle and reduce the workload of technical personnel.
[0038] The further effects of the above non-conventional optional mode will be described in the following combined with the specific embodiments. BRIEF DESCRIPTION OF DRAWINGS
[0039] The accompanying drawings are used to better understand the present application, and do not constitute an improper limitation on the present application. Among them:
[0040] Figure 1 is a schematic diagram of a flow of a business processing method provided by an embodiment of the present application;
[0041] Figure 2 is a schematic diagram of a flow of a business processing method provided by another embodiment of the present application;
[0042] Figure 3 is a schematic diagram of a flow of a business processing method provided by another embodiment of the present application;
[0043] Figure 4 is a schematic diagram of an architecture of a service processing system provided by an embodiment of the present application;
[0044] Figure 5 is a schematic diagram of a structure of a service processing device provided by an embodiment of the present application;
[0045] Figure 6 is a schematic diagram of a structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present application. DETAILED DESCRIPTION
[0046] Exemplary embodiments of the present application are described herein with reference to the accompanying drawings, which are meant to be exemplary and not limiting. Therefore, it should be recognized that many modifications and variations of the exemplary embodiments described herein can be made by those of ordinary skill in the art without departing from the scope and spirit of the application. Also, for the purpose of clarity and the brevity, the description below omits the description of well-known functions and structures.
[0047] It should be noted that the acquisition, storage, use, processing, etc. of data in the technical solutions of the embodiments of the present application comply with the relevant provisions of national laws and regulations.
[0048] Figure 1 is a schematic diagram of a flow of a service processing method provided by an embodiment of the present application. As shown in Figure 1 , the method comprises:
[0049] Step 101: receiving service data.
[0050] Step 102: converting the service data into interface data by using a universal interface; wherein the interface data comprises the value of at least one type field and the value of at least one service field.
[0051] The universal interface is used for standardizing the service data. The universal interface converts the service data of different source systems or service types into interface data having the same data structure. Conversion rules are set in the universal interface for different source systems and / or service types. The service data is converted into interface data by the conversion rules.
[0052] For example, the type field comprises a source system. The service field comprises a total sales amount. The service data comprises a product unit price and a sales quantity. Conversion rule 1 and conversion rule 2 are preset in the system. Conversion rule 1 is used to determine the value of the source system in the type field as the source system corresponding to the service data. Conversion rule 2 is used to calculate the product of the product unit price and the sales quantity in the service data, and determine the obtained product as the value of the total sales amount in the service field.
[0053] Step 103: Based on the validation scenario corresponding to the business data, determine at least one matching type field from at least one type field.
[0054] Based on the business requirements and / or scenario rules of the business data, determine the corresponding verification scenario for the business data. For example, if the business requirement of the business data is requirement 1, then the business data corresponds to verification scenario 1. If the business type of the business data is 2, then the business data corresponds to verification scenario 3, and so on. If the business requirement of the business data is requirement 2, and the business type of the business data is 2, then the business data corresponds to verification scenario 5.
[0055] The system pre-defines the scenario mapping relationship between each validation scenario and the matching type field. Based on the scenario mapping relationship, at least one matching type field is determined for the business data. The matching type field is a type field.
[0056] Step 104: Determine the validation logic based on the values of each matching type field in the interface data.
[0057] The system predefines the logical mapping relationship between the values of each matching type field and the predetermined validation logic. Based on this logical mapping relationship, the validation logic corresponding to the interface data is determined. The validation logic is used to validate the values of the business fields in the interface data. The validation logic can be described using validation rules or implemented by calling validation code.
[0058] Step 105: Use validation logic to validate the values of business fields in the interface data, and perform business processing on the business data based on the validation results.
[0059] In this embodiment of the invention, a general interface is used to convert business data into interface data. Based on the values of each matching type field corresponding to the verification scenario in the interface data, verification logic is determined. Using the verification logic, the values of the business fields in the interface data are verified, and corresponding business processing is performed on the business data. If the verification result indicates that the verification passes, the business processing logic corresponding to the business data is determined, and the business processing logic is executed on the business data.
[0060] By utilizing a universal interface, business data from different source systems can be transformed into interface data with a unified data structure. Configuring the matching type fields and validation logic corresponding to the validation scenarios enables validation processing for different business data. This eliminates the need to write separate validation code for different business data, shortening the development cycle and reducing the workload of technical personnel.
[0061] Figure 2 This is a schematic diagram of a business processing method provided in another embodiment of the present invention. Figure 2 As shown, the method includes:
[0062] Step 201: receiving service data.
[0063] Step 202: converting the service data into interface data by using a general interface; wherein the interface data comprises: a value of at least one type field and a value of at least one service field.
[0064] Step 203: determining at least one matched type field from the at least one type field according to a verification scenario corresponding to the service data.
[0065] Step 204: determining verification logic according to the value of each matched type field in the interface data.
[0066] Step 205: performing verification processing on the value of the service field in the interface data by using the verification logic.
[0067] Step 206: determining service processing logic corresponding to the service data in response to the verification result representing passing the verification; and executing the service processing logic on the service data.
[0068] Step 207: generating and sending alarm information corresponding to the verification result in response to the verification result representing failing the verification.
[0069] In the scheme of the embodiment of the application, if the verification result represents passing the verification, the service processing logic corresponding to the service data is determined; and the service processing logic is executed on the service data. The service processing logic can be determined according to the service type and service demand of the service data, etc. The service processing logic can include: saving the service data to a data sink, notifying other systems, sending the service data to a downstream system, etc. If the verification result represents failing the verification, alarm information corresponding to the verification result is generated and sent to remind the business system to promptly troubleshoot related problems.
[0070] Figure 3 is a schematic diagram of a flow of a service processing method according to another embodiment of the application. As shown in the figure, the method comprises: Figure 3
[0071] Step 301: receiving service data.
[0072] Step 302: converting the service data into interface data by using a general interface; wherein the interface data comprises: a value of at least one type field and a value of at least one service field.
[0073] Step 303: determining at least one matched type field from the at least one type field according to a verification scenario corresponding to the service data.
[0074] Step 304: setting a matched value of each non-matched field to a default value in response to the at least one type field having the non-matched field.
[0075] The non-matching type field is a type field that is not a matching type field. For example, the type fields include field 1, field 2, and field 3. Among them, field 1 is a matching type field, and field 2 and field 3 are non-matching type fields.
[0076] Step 305: According to the values of the matching type fields in the interface data and the matching values of the non-matching type fields, at least one configuration record corresponding to the service data is matched from the configuration table.
[0077] The configuration table includes a plurality of configuration records. Each configuration record includes the value of at least one type field, the related field of the verification logic, and the related field of the filling logic. Among them, the type field corresponding to the configuration record is the same as the type field corresponding to the interface data. The related field of the verification logic can include a verification service field, a verification type, a verification operation, etc. The related field of the filling logic can include a filling type and a filling operation, etc.
[0078] According to the verification service field, the verification type, and the verification operation in the configuration record, a verification sub-logic corresponding to the configuration record is generated. The verification service field is a service field for verification processing. The verification type can be an expression type. The expression type can include a spel expression type, an mvel2 expression type, and a custom type, etc. The verification operation can be an expression, an expression name, etc.
[0079] The verification sub-logic can include determining the field value of the verification service field in the interface data, calling the execution engine corresponding to the verification type to determine whether the field value satisfies the verification processing of the expression corresponding to the verification operation, and if so, determining that the verification result represents passing the verification, otherwise, determining that the verification result represents failing the verification.
[0080] In an embodiment of the present application, after setting the value of each non-matching service field to a default value, it further includes: in response to the configuration table not having a configuration record corresponding to the service data, determining that the service data fails the verification, and generating and sending alarm information corresponding to the service data. In the case that the configuration table does not have a configuration record corresponding to the service data, it is directly determined that the service data fails the verification.
[0081] Step 306: According to at least one configuration record, a verification logic is generated.
[0082] For each configuration record, according to the verification service field, the verification type, and the verification operation in the configuration record, a verification sub-logic corresponding to the configuration record is generated. In a preset combination manner, the verification sub-logics corresponding to each configuration record are combined to generate a verification logic. The preset combination can be a union set manner or an intersection set manner.
[0083] In a union manner, the check sub-logic corresponding to each configuration record is combined to generate the check logic. If the interface data conforms to any check sub-logic, it is determined that the check result represents passing the check.
[0084] In a union manner, the check sub-logic corresponding to each configuration record is combined to generate the check logic. If the interface data conforms to any check sub-logic, it is determined that the check result represents passing the check.
[0085] Step 307: The value of the service field in the interface data is checked by using the check logic, and the service data is processed according to the check result.
[0086] A specific example is listed below to illustrate how to match the configuration record, generate the check logic and perform the verification processing on the interface data.
[0087] Table 1: Data structure example of interface data
[0088]
[0089] Three pieces of interface data are shown in Table 1. As can be seen from Table 1, the interface data includes multiple type fields and multiple service fields. The type fields include source_sys, biz_type and expense_type. The service fields include ou, ouName and supplierId.
[0090] Table 2: Data structure example of configuration record
[0091]
[0092] Three pieces of configuration record are shown in Table 2. As can be seen from Table 2, the configuration record includes multiple type fields, service fields, check type, check operation, fill type and fill operation. The type fields include source_sys, biz_type and expense_type. The type fields in the configuration record are the same as the type fields in the interface data. The service field in the configuration record is the service field for check processing, i.e., the check service field.
[0093] The first piece of interface data is taken as the interface data to be processed to explain the scheme of the embodiment of the application.
[0094] Example one, if it is determined that the first piece of business data corresponds to the verification scenario 1. The matching type field corresponding to the verification scenario 1 is source_sys. It is determined that source_sys ='source 1'. The unmatched business fields are biz_type and expense_type, and the default values are -1. It is determined that biz_type = '-1' and expense_type = '-1'. According to source_sys ='source 1', biz_type = '-1', and expense_type = '-1', the third configuration record is matched from table 2 as the matching record.
[0095] According to the third configuration record, it is determined that the verification logic includes: determining that the field value of the verification business field ou in the interface data is 81; calling the execution engine corresponding to the verification type 2 to determine whether 81 satisfies the verification processing of , and obtaining a verification result. The verification result represents that the verification is passed.
[0096] Example two, if it is determined that the first piece of business data corresponds to the verification scenario 2. The matching type field corresponding to the verification scenario 2 is source_sys and biz_type. It is determined that source_sys ='source 1' and biz_type = '4'. The unmatched business field is expense_type, and the default value is -1. It is determined that expense_type = '-1'. According to source_sys ='source 1', biz_type = '4', and expense_type = '-1', the first configuration record and the second configuration record are matched from table 2 as the matching records.
[0097] It is determined that the verification sub-logic corresponding to the first configuration record includes: determining that the field value of the verification business field ou in the interface data is 81; calling the execution engine corresponding to the verification type 1 to determine whether 81 satisfies the verification processing of , and obtaining a first verification result. The first verification result represents that the verification sub-logic corresponding to the first configuration record is passed.
[0098] It is determined that the verification sub-logic corresponding to the second configuration record includes: determining that the field value of the verification business field ou in the interface data is 81; calling the execution engine corresponding to the verification type 2 to determine whether 81 satisfies the verification processing of , and obtaining a second verification result. The second verification result represents that the verification sub-logic corresponding to the second configuration record is passed.
[0099] The verification sub-logics corresponding to the configuration records are combined in an intersection manner to generate the verification logic. Since the interface data meets the verification sub-logics corresponding to the first configuration record and the second configuration record at the same time, it is determined that the verification result represents that the verification is passed.
[0100] In the scheme of the embodiment of the present application, at least one matching type field is determined according to the verification scene corresponding to the service data, and at least one configuration record corresponding to the service data is matched according to the value of each matching type field in the interface data and the matching value of each non-matching field, and verification logic is generated according to the at least one configuration record to verify the service data. The scheme of the embodiment of the present application can be flexibly applied to various verification scenes through the general interface and the configuration table, and the workload and labor cost required for demand change and system operation and maintenance are reduced.
[0101] In an embodiment of the present application, if the verification result represents passing the verification, the filling logic corresponding to the interface data is determined, and the filling field in the service data is filled by using the filling logic.
[0102] The filling type and the filling operation corresponding to the interface data are determined. The filling type and the filling operation can be stored in the configuration record. The filling type can adopt an enumeration value, such as enumeration value 1 representing filling by code, enumeration value 2 representing filling by mapping value, and enumeration value 3 representing filling by calculation model. The filling operation can be a filling code name, a mapping relationship name, and a calculation model name, etc.
[0103] The filling logic corresponding to the configuration record is generated according to the filling type and the filling operation in the configuration record. The filling logic can be: calling an execution engine corresponding to the filling type, executing a processing logic corresponding to the filling operation, and obtaining a filling value. The filling value is determined as the value of the filling field in the service data.
[0104] Figure 4 is a schematic diagram of an architecture of a service processing system provided by an embodiment of the present application. As shown in Figure 4 The service processing system includes an upstream part, an open interface part, a rule definition part, a rule matching part, and an execution rule part.
[0105] The upstream part is used to receive service data sent by an upstream source system. There can be multiple source systems. Each source system can send service data of multiple business types.
[0106] The open interface part provides a general interface, and the service data is converted into interface data by using the general interface. The interface data includes the value of at least one type field and the value of at least one service field.
[0107] The rule definition part is used to configure different verification scenes, matching type fields corresponding to the verification scenes, verification logic, and verification rules corresponding to the verification logic, etc. for service data of various types of businesses.
[0108] The rule matching part is configured to determine at least one matching type field from the at least one type field according to a corresponding verification scenario of the service data, and determine at least one verification rule according to the value of each matching type field in the interface data, and further determine the verification logic according to the determined verification rule.
[0109] The execution rule part is configured to perform verification processing on the value of the service field in the interface data by using the verification logic, and perform service processing on the service data according to the verification result.
[0110] The embodiment of the present application provides a general data verification solution. For service data sent by multiple source systems, a general interface and verification logic are called to implement a personalized, configured, online operation-free, and real-time effective rule configuration and data verification solution.
[0111] Figure 5 is a structural schematic diagram of a service processing device provided by an embodiment of the present application. As shown in Figure 5 , the device comprises:
[0112] The data receiving module 501 is configured to receive service data.
[0113] The data conversion module 502 is configured to convert the service data into interface data by using a general interface, wherein the interface data comprises the value of at least one type field and the value of at least one service field.
[0114] The field determination module 503 is configured to determine at least one matching type field from the at least one type field according to a corresponding verification scenario of the service data.
[0115] The logic determination module 504 is configured to determine the verification logic according to the value of each matching type field in the interface data.
[0116] The service processing module 505 is configured to perform verification processing on the value of the service field in the interface data by using the verification logic, and perform service processing on the service data according to the verification result.
[0117] Optionally, the logic determination module 504 is specifically configured to:
[0118] in response to the existence of at least one non-matching field in the at least one type field, set the matching value of each non-matching field as a default value;
[0119] according to the value of each matching type field in the interface data and the matching value of each non-matching field, match at least one configuration record corresponding to the service data from a configuration table;
[0120] generate the verification logic according to the at least one configuration record.
[0121] Optionally, the logic determination module 504 is specifically configured to:
[0122] For each configuration record, a verification sub-logic corresponding to the configuration record is generated according to the verification service field, the verification type, and the verification operation in the configuration record;
[0123] The verification sub-logics corresponding to the configuration records are combined to generate the verification logic.
[0124] Optionally, the service processing module 505 is further configured to:
[0125] In response to the fact that the configuration record corresponding to the service data does not exist in the configuration table, it is determined that the service data does not pass the verification, and the alarm information corresponding to the service data is generated and sent.
[0126] Optionally, the service processing module 505 is specifically configured to:
[0127] In response to the fact that the verification result indicates that the verification is passed, the service processing logic corresponding to the service data is determined; and the service processing logic is executed on the service data.
[0128] In response to the fact that the verification result indicates that the verification is not passed, the alarm information corresponding to the verification result is generated and sent.
[0129] Optionally, the service processing module 505 is specifically configured to:
[0130] In response to the fact that the verification result indicates that the verification is passed, the filling logic corresponding to the interface data is determined.
[0131] The filling field in the service data is filled by using the filling logic.
[0132] Embodiments of the present application provide an electronic device, comprising:
[0133] One or more processors;
[0134] A storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the method of any of the above embodiments.
[0135] Embodiments of the present application provide a computer program product comprising a computer program, the computer program implements the method of any of the above embodiments when executed by a processor.
[0136] Reference will be made to the following description Figure 6 which shows a structural schematic diagram of a computer system 600 of a terminal device suitable for implementing embodiments of the present application. Figure 6 The terminal device shown is only an example, and should not bring any limitation to the functions and use range of embodiments of the present application.
[0137] AsFigure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601 which can perform various appropriate actions and processes in accordance with programs stored in a read only memory (ROM) 602 or programs loaded from the storage section 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the system 600 are also stored. The CPU 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.
[0138] Connected to the I / O interface 605 are an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as necessary. A removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is attached to the drive 610 as necessary, so that a computer program read therefrom is installed into the storage section 608 as necessary.
[0139] In particular, the processes described above with reference to the flowcharts can be implemented as a computer software program in accordance with the embodiments disclosed herein. For example, the embodiments disclosed herein include a computer program product comprising a computer program carried on a computer readable medium, the computer program comprising program code for performing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via the communication section 609 and / or installed from the removable media 611. When the computer program is executed by the central processing unit (CPU) 601, the above-described functions defined in the system of the present invention are performed.
[0140] It should be noted that the computer-readable medium shown in the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or component. In the present application, the computer-readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to an electromagnetic signal, an optical signal or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate or transmit a program for use by or in conjunction with an instruction execution system, device or component. The program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, optical cable, RF, etc., or any suitable combination of the above.
[0141] The flowcharts and block diagrams in the drawings illustrate the possible implementation architectures, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowcharts or block diagrams can represent a module, a program segment, or a portion of code that contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in different orders than that shown in the figures. For example, two blocks that are shown in succession can actually be executed substantially concurrently, or they can sometimes be executed in reverse order, depending on the functionality involved. It should also be noted that each block in the block diagrams or flowcharts, and combinations of blocks in the block diagrams or flowcharts, can be implemented by a dedicated hardware-based system that performs specified functions or operations, or can be implemented by a combination of special-purpose hardware and computer instructions.
[0142] The modules described in the embodiments of the present application can be implemented in the form of software or hardware. The modules described can be arranged in a processor, for example, can be described as a data receiving module, a data converting module, a field determining module, a logic determining module and a service processing module. In some cases, the names of these modules do not limit the modules themselves, for example, the data receiving module can also be described as a module for receiving service data.
[0143] As another aspect, the present application also provides a computer readable medium, which can be included in the device described in the above embodiments, or can exist independently without being assembled into the device. The computer readable medium carries one or more programs, which, when executed by the device, cause the device to include:
[0144] receiving service data;
[0145] converting the service data into interface data using a general interface, wherein the interface data includes the value of at least one type field and the value of at least one service field;
[0146] determining at least one matching type field from the at least one type field according to a verification scenario corresponding to the service data;
[0147] determining verification logic according to the value of each matching type field in the interface data;
[0148] performing verification processing on the value of the service field in the interface data using the verification logic, and performing service processing on the service data according to the verification result.
[0149] According to the technical solution of the embodiments of the present application, the service data is converted into interface data using a general interface. The verification logic is determined according to the value of each matching type field in the interface data corresponding to the verification scenario. The value of the service field in the interface data is verified using the verification logic, and the service data is processed accordingly.
[0150] Using a general interface, the service data from different source systems can be converted into interface data with a unified data structure. The matching type field and the verification logic corresponding to the verification scenario are configured to implement verification processing on different service data. There is no need to write verification codes for different service data, which can shorten the development cycle and reduce the workload of technical personnel.
[0151] The foregoing detailed description has set forth various embodiments of the devices and / or processes via the use of specific terminology. However, embodiments thereof can be practiced with the exact description not being presented in detail. The term "device" should be understood to encompass devices operating in various modes, such as active mode, sleep mode, hibernate mode, and the like. The terms "coupled" and "connected," along with their derivatives, can be used. It should be understood that these terms are not intended as synonyms for each other. Rather, particular circuitry that can be said to be coupled or connected can be coupled and connected via some transmission medium.
Claims
1. A business processing method, characterized in that, include: Receive business data; The business data is converted into interface data using a general interface; wherein the interface data includes: the value of at least one type field and the value of at least one business field; Based on the verification scenario corresponding to the business data, at least one matching type field is determined from the at least one type field; The validation logic is determined based on the values of each of the matching type fields in the interface data; The verification logic is used to verify the values of the business fields in the interface data, and the business data is processed according to the verification results.
2. The method according to claim 1, characterized in that, The step of determining the verification logic based on the values of each of the matching type fields in the interface data includes: In response to the presence of a non-matching field in the at least one type field, the matching value of each non-matching field is set to a default value; Based on the values of each of the matching type fields in the interface data and the matching values of each of the non-matching fields, at least one configuration record corresponding to the business data is matched from the configuration table; The verification logic is generated based on at least one configuration record.
3. The method according to claim 2, characterized in that, The step of generating the verification logic based on the at least one configuration record includes: For each configuration record, a corresponding verification sub-logic is generated based on the verification business field, verification type, and verification operation in the configuration record. The verification logic is generated by combining the verification sub-logic corresponding to each of the configuration records.
4. The method according to claim 2, characterized in that, After setting the values of each of the unmatched business fields to their default values, the method further includes: If the configuration record corresponding to the business data does not exist in the configuration table, it is determined that the business data has failed the verification, and an alarm message corresponding to the business data is generated and sent.
5. The method according to claim 1, characterized in that, Based on the verification results, the business data is processed, including: In response to the verification result indicating that the verification is passed, the business processing logic corresponding to the business data is determined; the business processing logic is executed on the business data. In response to the verification result indicating that the verification failed, an alarm message corresponding to the verification result is generated and sent.
6. The method according to claim 1, characterized in that, Based on the verification results, the business data is processed, including: In response to the verification result indicating that the verification has passed, the padding logic corresponding to the interface data is determined; The filling logic is used to fill the fields in the business data.
7. A business processing device, characterized in that, include: The data receiving module is used to receive business data; A data conversion module is used to convert the business data into interface data using a general interface; wherein the interface data includes: the value of at least one type field and the value of at least one business field; The field determination module is used to determine at least one matching type field from the at least one type field according to the verification scenario corresponding to the business data; The logic determination module is used to determine the verification logic based on the values of each of the matching type fields in the interface data; The business processing module is used to perform validation processing on the values of business fields in the interface data using the validation logic, and to perform business processing on the business data based on the validation results.
8. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-6.
9. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-6.
10. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-6.