CN112115518A - Service data checking method and device - Google Patents
Service data checking method and device Download PDFInfo
- Publication number
- CN112115518A CN112115518A CN202011043716.1A CN202011043716A CN112115518A CN 112115518 A CN112115518 A CN 112115518A CN 202011043716 A CN202011043716 A CN 202011043716A CN 112115518 A CN112115518 A CN 112115518A
- Authority
- CN
- China
- Prior art keywords
- service
- context
- data
- current user
- context information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 89
- 238000012795 verification Methods 0.000 claims abstract description 43
- 238000013524 data verification Methods 0.000 claims abstract description 23
- 238000013479 data entry Methods 0.000 claims abstract description 18
- 230000002688 persistence Effects 0.000 claims description 16
- 230000002085 persistent effect Effects 0.000 claims description 11
- 230000008569 process Effects 0.000 description 27
- 238000012545 processing Methods 0.000 description 25
- 238000007726 management method Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 16
- 238000004590 computer program Methods 0.000 description 13
- 230000010365 information processing Effects 0.000 description 13
- 230000006870 function Effects 0.000 description 12
- 238000004891 communication Methods 0.000 description 9
- 230000005540 biological transmission Effects 0.000 description 5
- 230000015572 biosynthetic process Effects 0.000 description 5
- 238000000605 extraction Methods 0.000 description 5
- 238000003786 synthesis reaction Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 238000012546 transfer Methods 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 239000000284 extract Substances 0.000 description 3
- 238000007781 pre-processing Methods 0.000 description 3
- 238000012550 audit Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 239000000047 product Substances 0.000 description 2
- 230000000750 progressive effect Effects 0.000 description 2
- 238000012797 qualification Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 108010001267 Protein Subunits Proteins 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000007795 chemical reaction product Substances 0.000 description 1
- 238000013136 deep learning model Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000002372 labelling Methods 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- 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/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application provides a service data checking method and a device, wherein the method comprises the following steps: acquiring data recorded in the current column; checking the data input in the current column through the context information of the current user; if the verification is passed, switching to the next column for continuing data entry; and if the verification fails, highlighting the data entered by the current field. By the scheme, the technical problems that the existing service data verification is large in limitation and inaccurate in verification result are solved, and the purpose of performing data verification more accurately and efficiently is achieved.
Description
Technical Field
The application belongs to the technical field of business handling, and particularly relates to a business data verification method and device.
Background
Generally, when a business action transaction occurs, a front-end operation interface or a back-end application service verifies business data according to preset rules, for example, in a scenario where a user applies for a loan, it is necessary to verify whether a filled data format meets requirements, whether the user exists, whether an account number is valid, whether the user meets loan qualifications, whether the user is in a business blacklist, and the like. These are passive check methods that intercept interface events or transaction events at the time of transaction, i.e. check each field in the event payload if there is an event trigger.
That is, the check rule for checking the data validity is generally limited to the constraint condition of the current scene, the check process focuses on the current stage of the service, but not on the global process of the service, especially on the incidence relation between the service initiation and each stage, so that misjudgment is made on the data validity in some scenes, and thus the risk potential exists.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The application aims to provide a service data checking method and a service data checking device, which can be used for checking service data more accurately.
The application provides a service data checking method and a device, which are realized as follows:
a service data verification method, the method comprising:
acquiring data recorded in the current column;
checking the data input in the current column through the context information of the current user;
if the verification is passed, switching to the next column for continuing data entry;
and if the verification fails, highlighting the data entered by the current field.
In one embodiment, the above method further comprises:
generating the context information of the current user as follows:
acquiring basic data information and historical service handling information of a current user;
and generating context information of the current user according to the association relation among the basic data information, the historical service handling information and the services.
In one embodiment, generating context information for the current user includes:
receiving a queuing request of the current user;
responding to the queuing request to generate a global tracking number for the current user, wherein the global tracking number is used for associating and uniquely identifying each business transaction of the current counter of the current user;
and taking the global tracking number as a queuing number, adding the current user into a service handling waiting queue and starting to assemble the context information of the current user.
In one embodiment, further comprising:
under the condition that the current user is determined to be arranged in the service transaction waiting queue, extracting the global tracking number of the current user from queuing information;
determining whether the context information corresponding to the global tracking number is assembled;
and if the assembly is finished, sequentially acquiring the context information from the buffer module and the persistence module, and loading, wherein the loaded context information is used for verifying the data input in the column.
In one embodiment, assembling the context information of the current user comprises:
acquiring the service type of the service requested to be transacted by the current user;
acquiring a context assembly rule corresponding to the service type;
acquiring data information required by context assembly according to the context assembly rule;
assembling the acquired data information according to the context assembly rule to obtain context information;
and putting the context information into a cache and persisting the context information into a database.
In another aspect, a service data checking apparatus is provided, including:
the acquisition module is used for acquiring data recorded in the current column;
the verification module is used for verifying the data input in the current column through the context information of the current user;
the switching module is used for switching to the next column for continuing data entry under the condition that the verification is passed;
and the display module is used for highlighting the data input by the current column under the condition that the verification fails.
In one embodiment, the above apparatus further comprises:
a generating module, configured to generate the context information of the current user as follows:
acquiring basic data information and historical service handling information of a current user;
and generating context information of the current user according to the association relation among the basic data information, the historical service handling information and the services.
In one embodiment, the generating module comprises:
the receiving unit is used for receiving the queuing request of the current user;
the first generation unit is used for responding to the queuing request to generate a global tracking number for the current user, wherein the global tracking number is used for associating and uniquely identifying each business transaction of the current counter of the current user;
and the assembling unit is used for adding the current user into a service handling waiting queue and starting to assemble the context information of the current user by taking the global tracking number as a queuing number.
In one embodiment, the above apparatus further comprises:
the extracting module is used for extracting the global tracking number of the current user from the queuing information under the condition that the current user is determined to be queued in the service transaction waiting queue;
the determining module is used for determining whether the context information corresponding to the global tracking number is assembled;
and the obtaining module is used for obtaining the context information from the caching module and the persistence module in sequence and loading the context information under the condition that the assembly is determined to be completed, wherein the loaded context information is used for verifying the data input in the column.
In one embodiment, the assembly unit comprises:
the first acquiring subunit is used for acquiring the service type of the service requested to be transacted by the current user;
a second obtaining subunit, configured to obtain a context assembly rule corresponding to the service type;
the third obtaining subunit is configured to obtain data information required for context assembly according to the context assembly rule;
the assembling unit is used for assembling the acquired data information according to the context assembling rule to obtain context information;
and the cache persistence unit is used for putting the context information into a cache and persisting the context information into a database.
In yet another aspect, a terminal device is provided, comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor implementing the steps of the method:
acquiring data recorded in the current column;
checking the data input in the current column through the context information of the current user;
if the verification is passed, switching to the next column for continuing data entry;
and if the verification fails, highlighting the data entered by the current field.
In yet another aspect, a computer-readable storage medium is provided having computer instructions stored thereon which, when executed, implement the steps of the method of:
acquiring data recorded in the current column;
checking the data input in the current column through the context information of the current user;
if the verification is passed, switching to the next column for continuing data entry;
and if the verification fails, highlighting the data entered by the current field.
According to the business data verification method and device, the data input in the current column is verified through the context information of the current user, if the verification is passed, the next column is switched to continue data input, and if the verification is not passed, the data input in the current column is highlighted. Namely, when the service data is verified, the context information of the current user is used, instead of being limited to the current service scene, and the context information is the global process of the service, so that the verification is more comprehensive and accurate, the technical problems that the existing service data verification is more limited and the verification result is inaccurate are solved, and the aim of performing data verification more accurately and efficiently is fulfilled.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.
Fig. 1 is a flowchart of a method according to an embodiment of a service data verification method provided in the present application;
FIG. 2 is an architecture diagram of a service interaction system provided herein;
FIG. 3 is a block diagram of the structure of a number taking subsystem provided in the present application;
FIG. 4 is a flowchart of a method of the number taking step provided herein;
FIG. 5 is a block diagram of the architecture of a business context management subsystem provided herein;
FIG. 6 is a flowchart of a method for verifying business data via context information according to the present application;
FIG. 7 is a block diagram of the architecture of a context engine subsystem provided herein;
FIG. 8 is a flow diagram of a method for context assembly by a business context engine subsystem as provided herein;
FIG. 9 is an architecture diagram of a computer terminal provided herein;
fig. 10 is a block diagram of a structure of a service data verification apparatus provided in the present application.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
For the existing service data verification, when a service action transaction occurs, a front-end operation interface or a back-end application service verifies the service data according to preset rules, for example, in a scenario where a user applies for a loan, it is necessary to verify whether a filled data format meets requirements, it is necessary to verify whether the user exists, whether an account number is valid, whether the user meets loan qualification, whether the user is in a service blacklist, and the like. These are passive check methods that intercept interface events or transaction events at the time of transaction, i.e. check each field in the event payload if there is an event trigger. That is, the check rule for checking the data validity is generally limited to the constraint condition of the current scene, the check process focuses on the current stage of the service, but not on the global process of the service, especially on the incidence relation between the service initiation and each stage, so that misjudgment is made on the data validity in some scenes, and thus the risk potential exists.
In this example, a service data verification method is provided, as shown in fig. 1, the method includes:
step 101: acquiring data recorded in the current column;
step 102: checking the data input in the current column through the context information of the current user;
step 103: if the verification is passed, switching to the next column for continuing data entry;
step 104: and if the verification fails, highlighting the data entered by the current field.
In the above example, the data entered in the current field is checked through the context information of the current user, if the check is passed, the next field is switched to continue data entry, and if the check is not passed, the data entered in the current field is highlighted. Namely, when the service data is verified, the context information of the current user is used, instead of being limited to the current service scene, and the context information is the global process of the service, so that the verification is more comprehensive and accurate, the technical problems that the existing service data verification is more limited and the verification result is inaccurate are solved, and the aim of performing data verification more accurately and efficiently is fulfilled.
Specifically, the context information may be generated according to basic data information (e.g., name, sex, telephone, address, etc.) and historical business transaction information (e.g., type of business transacted before, business data of business transacted before, etc.) of the user, and an association relationship between businesses (e.g., relationship between current counter business and previous business, relationship between multiple businesses requested to be transacted at this time). That is, the context information of the current user may be generated as follows: acquiring basic data information and historical service handling information of a current user; and generating context information of the current user according to the association relation among the basic data information, the historical service handling information and the services.
When the method is realized, the number taking subsystem can generate a service global tracking number corresponding to the service context of the user in the process of waiting for the number taking of the user, all subsequent services handled by the user can acquire the service context information of the user through the service global tracking number, and the uniqueness and consistency of the service context of the user in the whole service handling process can be ensured through the method. Meanwhile, the service context information required by the user to handle the service is prepared in advance, the consumed time of the information acquisition process required by the whole service processing is dispersed in two stages of pre-processing and processing, which is equivalent to the fact that the service to be handled by the user starts to be preprocessed in the process of waiting for calling, the handling efficiency of the user when the user really handles the service can be improved by the method, and the user experience is also improved.
For this purpose, when generating the context information of the current user, a queuing request of the current user may be received; responding to the queuing request to generate a global tracking number for the current user, wherein the global tracking number is used for associating and uniquely identifying each business transaction of the current counter of the current user; and taking the global tracking number as a queuing number, adding the current user into a service handling waiting queue and starting to assemble the context information of the current user. That is, the service global tracking number generated for the user is used as the queuing number for the user service transaction. Correspondingly, when extracting the context information of the user, the context information may also be extracted based on the global tracking number of the service, for example, when it is determined that the current user is queued in the service transaction waiting queue, the global tracking number of the current user may be extracted from the queuing information; determining whether the context information corresponding to the global tracking number is assembled; and if the assembly is finished, sequentially acquiring the context information from the buffer module and the persistence module, and loading, wherein the loaded context information is used for verifying the data input in the column. If the context information is successfully obtained in the caching module, it is not necessary to obtain the context information from the persistence module.
For the context information of the current user, the assembly can be performed as follows, and the caching and the persistence are performed: acquiring the service type of the service requested to be transacted by the current user; acquiring a context assembly rule corresponding to the service type; acquiring data information required by context assembly according to the context assembly rule; assembling the acquired data information according to the context assembly rule to obtain context information; and putting the context information into a cache and persisting the context information into a database.
Further, if the verification fails, when highlighting the data entered in the current field, highlighting may be performed in a highlight mode or in a labeling mode, so that the business handling personnel can see and collate the information that the verification fails.
The above method is described below with reference to a specific example, however, it should be noted that the specific example is only for better describing the present application and is not to be construed as limiting the present application.
In this example, an interactive system is provided, as shown in fig. 2, which may include: three interacting subsystems: a number fetching subsystem, a service context management subsystem and a context engine subsystem.
Considering that the number taking of the current counter service is completed through a number taking machine, when the number is received, a user selects the service to be handled through an interface, a number taking module selects a corresponding service queue for the user and generates a queue number, and after a service operator handles the service of the current user, the service operator finds the foremost number in the queue and calls the number to wait for the user to handle the number before going to the queue.
The number taking subsystem generates a service global tracking number corresponding to the service context of the user in the process of waiting for the number taking of the user, and all subsequent services handled by the user acquire the service context information of the user through the service global tracking number. Meanwhile, the service context information required by the user to handle the service is prepared in advance, the consumed time of the information acquisition process required by the whole service processing is dispersed in two stages of pre-processing and processing, which is equivalent to the fact that the service to be handled by the user starts to be preprocessed in the process of waiting for calling, the handling efficiency of the user when the user really handles the service can be improved by the method, and the user experience is also improved.
As shown in fig. 3, the number taking subsystem may include: the system comprises a number taking control module, an identity information reading module, a global service tracking number generating module, a user queuing module and a service context information queuing processing module.
Specifically, the number-taking step may be as shown in fig. 4, and includes:
step 1: after the user selects the service type to be handled by the number taking control module, clicking 'number taking';
step 2: the number taking control module informs the identity information reading module to read and return the identity information;
and step 3: the number taking control module requests the global service tracking number generation module to generate and return a service global tracking number;
the business global tracking number is used for associating a plurality of sub-businesses possibly involved in the process of handling counter business once, the sub-businesses are identified to be triggered by the same source, and the associated consistent business context information can be obtained when different sub-businesses are handled through the business global tracking number.
And 4, step 4: the number taking control module sends service queuing information containing the service global tracking number to the user queuing module, and prompts a queuing fault and returns if the queuing fails;
and 5: if the enqueue is successful, the number-taking control module continues to send queuing information of the assembled service context containing the service global tracking number to the service context information processing queuing module, and waits for the context engine module to asynchronously process the information;
step 6: the number taking control module prompts that the number taking is successful and asks the user to wait for the number calling.
As shown in fig. 5, the business context management subsystem may include: the system comprises a service context management main control module, a number calling module, a service processing module, a service context caching module, a service checking module, a service context persistence module, a service context information processing queuing module, a user queuing module and an auditing module.
For the context switching of the service master control subsystem, the following steps can be included:
s1: the service personnel clicks the 'context switch', and the service context management main control module starts to execute the context switch;
s2: the service context management main control module informs the number calling module to call the number;
s3: the service context management main control module acquires the next user queuing information to be processed from the user queuing module;
s4: the service context management main control module extracts a service global tracking number from the obtained queuing information;
s5: the service context management main control module cooperates with the service context information processing queuing module to check whether the context corresponding to the service global tracking number is assembled;
s6: if the service context information processing queuing module finishes the context assembly of the service, sequentially trying to acquire corresponding context information from the service context caching module and the service context persistence module in sequence, and loading after acquiring the context information;
the service context is a special data when handling services, and its data is not limited to specific services, but a data set integrating various service data is a data background for handling services, for example: the business context may include, for example, "currently selectable business transaction identity information", "commonly used business transaction type", "commonly used business transaction geographic information", and the like.
S7: if the service context information processing queuing module does not finish the context assembly of the service, judging whether the service is being processed, if the service context information processing queuing module is in the service context processing, slightly waiting for processing, and trying to read corresponding context information from the service context caching module and the service context persistence module again after the processing is finished;
s8: if the service context information processing queuing module does not process the service, the service context management main control module informs the service context queuing processing module to process immediately, and tries to read corresponding context information from the service context cache module and the service context persistence module again after the processing is finished;
s9: the service context management main control module reads the context information and carries out context loading;
s10: and finishing the loading of the context information of the service context management main control module and finishing the switching.
For the context information of the service master control subsystem, the service data may be checked through the context information in the manner shown in fig. 6:
step 1: the service context management main control module waits for loading context information;
step 2: when the business transaction is started, a business clerk inputs data, and a page onChange event triggers a business verification module to check whether the input data passes through business verification;
and step 3: if the service check module fails to check, service error information is prompted;
and 4, step 4: if the service checking module passes the checking, checking the context information;
and 5: if the context check of the service context management main control module passes, finishing the data entry of the column, and continuing waiting for the entry of the next column;
step 6: if the context check of the service context management main control module is not passed, popping a frame to request to confirm whether abnormal data (namely data outside the context) is input or not;
and 7: if the input is confirmed, highlighting abnormal data;
and 8: informing an auditing module to audit and leave a trace for the action of confirming the entry of the abnormal data;
and step 9: if the entry is abandoned, return to waiting for the onChange event to be re-entered.
As shown in fig. 7, the context engine subsystem may include: the system comprises a service context engine module, a service context management main control module, a service context caching module, a service context persistence module, a service context information processing queuing module, a service context rule configuration module, a service context extraction module and a service context synthesis module.
For the context engine subsystem, context assembly may be performed according to the steps shown in FIG. 8:
step 1: the service context engine module informs the service context information processing queuing module to return the next task to be processed in the queue to be processed;
step 2: the service context engine module informs the service context information processing queuing module to transfer the acquired task to be processed to a processing queue;
and step 3: the business context engine module acquires the corresponding business type of the task;
and 4, step 4: the service context engine module acquires a context assembly rule of the service type from the service context rule configuration module;
and 5: the service context engine module informs the service context extraction module to respectively extract original information from each module according to the obtained rule;
step 6: the service context engine module informs the service context synthesis module to carry out context synthesis according to the acquired rule;
and 7: the service context engine module caches the synthesized context information through the service context caching module;
and 8: the service context engine module writes the synthesized context information into a database in a persistent mode through the service context persistent module;
and step 9: and the business context engine module informs the business context information processing queuing module to transfer the task from the queue in processing to the completed queue, and returns to continue to pick up the next task to be processed.
Specifically, the method can further comprise the following steps:
s1: the real-time processing thread of the business context engine module receives a task to be immediately processed and stops sleeping;
s2: the service context engine module informs the service context information processing queuing module to transfer the task to the real-time queue;
s3: the business context engine module acquires a corresponding business type;
s4: the business context engine module acquires the context assembly rule of the business type from the business context rule configuration module, because the rules of different types of business scenes are different, the business contexts corresponding to the businesses are naturally different, and the context assembly rule is a function of providing flexible context assembly for different business scenes in a preset mode;
s5: the service context engine module informs the service context extraction module to respectively extract original information from each module according to the obtained rule; the business context extraction module is a collection of modules including, for example: the module for acquiring the existing context persistent data, the module for acquiring the business data according to the business rule, the module for butting the artificial intelligence deep learning model data and the like so as to acquire various different data.
S6: the business context engine module informs the business context synthesis module to carry out context synthesis according to the rules, and because the data provided by the business context extraction module is various, the subsequent use can be facilitated only after the data are assembled and processed according to certain rules;
s7: the service context engine module caches the synthesized context information through the service context caching module;
s8: the service context engine module writes the synthesized context information into a database in a persistent mode through the service context persistent module;
s9: the business context engine module informs the business context information processing queuing module to transfer the task from the processing queue to the completed queue;
s10: the service context engine module informs the service context management service main control module of the completion of the task;
s11: and the business context engine module processes the thread to continuously sleep in real time.
Namely, in the above example, a risk checking system based on a service context is provided, which is used to perform a global data check in a process of handling a plurality of associated services triggered at one time, obtain consistent context data at different stages of each associated service through a global service tracking number to perform the check, and perform highlighting display and audit trace retention on data entry which does not pass the check, so as to remind the entered service personnel and the subsequent approval personnel of paying attention. Furthermore, a context information preprocessing method is added in the number fetching process to disperse the time consumed by data reading during service handling, so that the service handling efficiency and the user experience are effectively improved. And the method of linking number calling by switching service context by service personnel not only finishes the loading of the service context but also triggers the start of the next service to be processed, thereby ensuring that the service context is consistent with the real service, namely ensuring that the context is the corresponding service context when a new service is handled, and one service context only acts on the current service, and also setting the method of acquiring original data to synthesize the service context by a preset rule.
The method embodiments provided in the above embodiments of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking the example of running on a computer terminal, fig. 9 is a hardware structure block diagram of a computer terminal of a service data verification method according to an embodiment of the present invention. As shown in fig. 9, the computer terminal 10 may include one or more (only one shown) processors 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 9 is only an illustration and is not intended to limit the structure of the electronic device. For example, the computer terminal 10 may also include more or fewer components than shown in FIG. 9, or have a different configuration than shown in FIG. 9.
The memory 104 may be configured to store software programs and modules of application software, such as program instructions/modules corresponding to the business data checking method in the embodiment of the present invention, and the processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implements the business data checking method of the application program. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission module 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 106 includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission module 106 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
On the software level, the above apparatus may be as shown in fig. 10, and may include:
an obtaining module 1001, configured to obtain data entered in a current field;
the checking module 1002 is configured to check data entered in the current field according to context information of the current user;
the switching module 1003 is configured to switch to a next field to continue data entry when the verification passes;
and a display module 1004, configured to highlight the data currently entered in the field if the verification fails.
In an embodiment, the service data checking apparatus may further include: a generating module, configured to generate the context information of the current user as follows: acquiring basic data information and historical service handling information of a current user; and generating context information of the current user according to the association relation among the basic data information, the historical service handling information and the services.
In one embodiment, the generating module may include: the receiving unit is used for receiving the queuing request of the current user; the first generation unit is used for responding to the queuing request to generate a global tracking number for the current user, wherein the global tracking number is used for associating and uniquely identifying each business transaction of the current counter of the current user; and the assembling unit is used for adding the current user into a service handling waiting queue and starting to assemble the context information of the current user by taking the global tracking number as a queuing number.
In an embodiment, the service data checking apparatus may further include: the extracting module is used for extracting the global tracking number of the current user from the queuing information under the condition that the current user is determined to be queued in the service transaction waiting queue; the determining module is used for determining whether the context information corresponding to the global tracking number is assembled; and the obtaining module is used for obtaining the context information from the caching module and the persistence module in sequence and loading the context information under the condition that the assembly is determined to be completed, wherein the loaded context information is used for verifying the data input in the column.
In one embodiment, the assembly unit may include: the first acquiring subunit is used for acquiring the service type of the service requested to be transacted by the current user; a second obtaining subunit, configured to obtain a context assembly rule corresponding to the service type; the third obtaining subunit is configured to obtain data information required for context assembly according to the context assembly rule; the assembling unit is used for assembling the acquired data information according to the context assembling rule to obtain context information; and the cache persistence unit is used for putting the context information into a cache and persisting the context information into a database.
An embodiment of the present application further provides a specific implementation manner of an electronic device, which is capable of implementing all steps in the service data verification method in the foregoing embodiment, where the electronic device specifically includes the following contents: a processor (processor), a memory (memory), a communication Interface (Communications Interface), and a bus; the processor, the memory and the communication interface complete mutual communication through the bus; the processor is configured to call a computer program in the memory, and when the processor executes the computer program, all steps in the service data checking method in the foregoing embodiment are implemented, for example, when the processor executes the computer program, the following steps are implemented:
step 1: acquiring data recorded in the current column;
step 2: checking the data input in the current column through the context information of the current user;
and step 3: if the verification is passed, switching to the next column for continuing data entry;
and 4, step 4: and if the verification fails, highlighting the data entered by the current field.
As can be seen from the above description, in the embodiment of the present application, the data entered in the current field is checked through the context information of the current user, if the check is passed, the field is switched to the next field for continuing data entry, and if the check is not passed, the data entered in the current field is highlighted. Namely, when the service data is verified, the context information of the current user is used, instead of being limited to the current service scene, and the context information is the global process of the service, so that the verification is more comprehensive and accurate, the technical problems that the existing service data verification is more limited and the verification result is inaccurate are solved, and the aim of performing data verification more accurately and efficiently is fulfilled.
An embodiment of the present application further provides a computer-readable storage medium capable of implementing all steps in the service data verification method in the foregoing embodiment, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, implements all steps of the service data verification method in the foregoing embodiment, for example, when the processor executes the computer program, implements the following steps:
step 1: acquiring data recorded in the current column;
step 2: checking the data input in the current column through the context information of the current user;
and step 3: if the verification is passed, switching to the next column for continuing data entry;
and 4, step 4: and if the verification fails, highlighting the data entered by the current field.
As can be seen from the above description, in the embodiment of the present application, the data entered in the current field is checked through the context information of the current user, if the check is passed, the field is switched to the next field for continuing data entry, and if the check is not passed, the data entered in the current field is highlighted. Namely, when the service data is verified, the context information of the current user is used, instead of being limited to the current service scene, and the context information is the global process of the service, so that the verification is more comprehensive and accurate, the technical problems that the existing service data verification is more limited and the verification result is inaccurate are solved, and the aim of performing data verification more accurately and efficiently is fulfilled.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the hardware + program class embodiment, since it is substantially similar to the method embodiment, the description is simple, and the relevant points can be referred to the partial description of the method embodiment.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Although the present application provides method steps as described in an embodiment or flowchart, additional or fewer steps may be included based on conventional or non-inventive efforts. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or client product executes, it may execute sequentially or in parallel (e.g., in the context of parallel processors or multi-threaded processing) according to the embodiments or methods shown in the figures.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Although embodiments of the present description provide method steps as described in embodiments or flowcharts, more or fewer steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded.
For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, in implementing the embodiments of the present description, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, and the like. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may therefore be considered as a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The present invention is 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 computer 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 computer program instructions may also be stored in a computer-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 computer-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 computer 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 implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description 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 present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The described embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of an embodiment of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
The above description is only an example of the embodiments of the present disclosure, and is not intended to limit the embodiments of the present disclosure. Various modifications and variations to the embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present specification should be included in the scope of the claims of the embodiments of the present specification.
Claims (12)
1. A service data verification method is characterized by comprising the following steps:
acquiring data recorded in the current column;
checking the data input in the current column through the context information of the current user;
if the verification is passed, switching to the next column for continuing data entry;
and if the verification fails, highlighting the data entered by the current field.
2. The method of claim 1, further comprising:
generating the context information of the current user as follows:
acquiring basic data information and historical service handling information of a current user;
and generating context information of the current user according to the association relation among the basic data information, the historical service handling information and the services.
3. The method of claim 2, wherein generating context information for the current user comprises:
receiving a queuing request of the current user;
responding to the queuing request to generate a global tracking number for the current user, wherein the global tracking number is used for associating and uniquely identifying each business transaction of the current counter of the current user;
and taking the global tracking number as a queuing number, adding the current user into a service handling waiting queue and starting to assemble the context information of the current user.
4. The method of claim 3, further comprising:
under the condition that the current user is determined to be arranged in the service transaction waiting queue, extracting the global tracking number of the current user from queuing information;
determining whether the context information corresponding to the global tracking number is assembled;
and if the assembly is finished, sequentially acquiring the context information from the buffer module and the persistence module, and loading, wherein the loaded context information is used for verifying the data input in the column.
5. The method of claim 3, wherein assembling the context information of the current user comprises:
acquiring the service type of the service requested to be transacted by the current user;
acquiring a context assembly rule corresponding to the service type;
acquiring data information required by context assembly according to the context assembly rule;
assembling the acquired data information according to the context assembly rule to obtain context information;
and putting the context information into a cache and persisting the context information into a database.
6. A service data verification apparatus, comprising:
the acquisition module is used for acquiring data recorded in the current column;
the verification module is used for verifying the data input in the current column through the context information of the current user;
the switching module is used for switching to the next column for continuing data entry under the condition that the verification is passed;
and the display module is used for highlighting the data input by the current column under the condition that the verification fails.
7. The apparatus of claim 6, further comprising:
a generating module, configured to generate the context information of the current user as follows:
acquiring basic data information and historical service handling information of a current user;
and generating context information of the current user according to the association relation among the basic data information, the historical service handling information and the services.
8. The apparatus of claim 7, wherein the generating module comprises:
the receiving unit is used for receiving the queuing request of the current user;
the first generation unit is used for responding to the queuing request to generate a global tracking number for the current user, wherein the global tracking number is used for associating and uniquely identifying each business transaction of the current counter of the current user;
and the assembling unit is used for adding the current user into a service handling waiting queue and starting to assemble the context information of the current user by taking the global tracking number as a queuing number.
9. The apparatus of claim 8, further comprising:
the extracting module is used for extracting the global tracking number of the current user from the queuing information under the condition that the current user is determined to be queued in the service transaction waiting queue;
the determining module is used for determining whether the context information corresponding to the global tracking number is assembled;
and the obtaining module is used for obtaining the context information from the caching module and the persistence module in sequence and loading the context information under the condition that the assembly is determined to be completed, wherein the loaded context information is used for verifying the data input in the column.
10. The apparatus of claim 8, wherein the assembly unit comprises:
the first acquiring subunit is used for acquiring the service type of the service requested to be transacted by the current user;
a second obtaining subunit, configured to obtain a context assembly rule corresponding to the service type;
the third obtaining subunit is configured to obtain data information required for context assembly according to the context assembly rule;
the assembling unit is used for assembling the acquired data information according to the context assembling rule to obtain context information;
and the cache persistence unit is used for putting the context information into a cache and persisting the context information into a database.
11. A terminal device comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor implementing the steps of the method of:
acquiring data recorded in the current column;
checking the data input in the current column through the context information of the current user;
if the verification is passed, switching to the next column for continuing data entry;
and if the verification fails, highlighting the data entered by the current field.
12. A computer readable storage medium having stored thereon computer instructions which, when executed, implement the steps of a method comprising:
acquiring data recorded in the current column;
checking the data input in the current column through the context information of the current user;
if the verification is passed, switching to the next column for continuing data entry;
and if the verification fails, highlighting the data entered by the current field.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011043716.1A CN112115518A (en) | 2020-09-28 | 2020-09-28 | Service data checking method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011043716.1A CN112115518A (en) | 2020-09-28 | 2020-09-28 | Service data checking method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112115518A true CN112115518A (en) | 2020-12-22 |
Family
ID=73797298
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011043716.1A Pending CN112115518A (en) | 2020-09-28 | 2020-09-28 | Service data checking method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112115518A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115185616A (en) * | 2022-09-14 | 2022-10-14 | 深圳依时货拉拉科技有限公司 | Business rule engine and processing method thereof |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050187368A1 (en) * | 2004-02-19 | 2005-08-25 | International Business Machines Corporation | Methods and apparatus for complementing user entries associated with events of interest through context |
| US20070162456A1 (en) * | 2005-12-30 | 2007-07-12 | Shai Agassi | Method and system for providing context based content for computer applications |
| US20120102002A1 (en) * | 2010-10-25 | 2012-04-26 | Vinaya Sathyanarayana | Automatic data validation and correction |
| CN104360901A (en) * | 2014-11-04 | 2015-02-18 | 中国建设银行股份有限公司 | Processing method and device for access request of terminal equipment and queuing machine |
| US20160267082A1 (en) * | 2015-03-10 | 2016-09-15 | Royal Bank Of Canada | Systems and methods for managing data |
| CN109815013A (en) * | 2019-01-02 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Business data processing method, device, computer equipment and storage medium |
| CN110955464A (en) * | 2019-12-10 | 2020-04-03 | 深圳前海环融联易信息科技服务有限公司 | Service processing method and device, computer equipment and storage medium |
| CN111562965A (en) * | 2020-04-27 | 2020-08-21 | 深圳木成林科技有限公司 | Page data verification method and device based on decision tree |
-
2020
- 2020-09-28 CN CN202011043716.1A patent/CN112115518A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050187368A1 (en) * | 2004-02-19 | 2005-08-25 | International Business Machines Corporation | Methods and apparatus for complementing user entries associated with events of interest through context |
| US20070162456A1 (en) * | 2005-12-30 | 2007-07-12 | Shai Agassi | Method and system for providing context based content for computer applications |
| US20120102002A1 (en) * | 2010-10-25 | 2012-04-26 | Vinaya Sathyanarayana | Automatic data validation and correction |
| CN104360901A (en) * | 2014-11-04 | 2015-02-18 | 中国建设银行股份有限公司 | Processing method and device for access request of terminal equipment and queuing machine |
| US20160267082A1 (en) * | 2015-03-10 | 2016-09-15 | Royal Bank Of Canada | Systems and methods for managing data |
| CN109815013A (en) * | 2019-01-02 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Business data processing method, device, computer equipment and storage medium |
| CN110955464A (en) * | 2019-12-10 | 2020-04-03 | 深圳前海环融联易信息科技服务有限公司 | Service processing method and device, computer equipment and storage medium |
| CN111562965A (en) * | 2020-04-27 | 2020-08-21 | 深圳木成林科技有限公司 | Page data verification method and device based on decision tree |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115185616A (en) * | 2022-09-14 | 2022-10-14 | 深圳依时货拉拉科技有限公司 | Business rule engine and processing method thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2015088853A1 (en) | Launching a client application based on a message | |
| CN109298926B (en) | Method and device for entering resource transfer party into resource transfer platform and electronic equipment | |
| CN109615384B (en) | Method, device and server for generating timeliness check rule | |
| CN109003071B (en) | Payment method, device and equipment | |
| CN112579321A (en) | Method, device and equipment for downloading service data | |
| CN113256426B (en) | Data processing method, device, equipment and medium | |
| CN115691004A (en) | Cargo access method, system and device | |
| CN110135815A (en) | Travel order monitoring method, device, computer equipment and storage medium | |
| CN111415146A (en) | Resource data processing method, device and equipment | |
| CN112115518A (en) | Service data checking method and device | |
| CN108647102B (en) | Service request processing method and device of heterogeneous system and electronic equipment | |
| CN113760242A (en) | Data processing method, device, server and medium | |
| CN109120509B (en) | Information collection method and device | |
| CN113111078B (en) | Resource data processing method and device, computer equipment and storage medium | |
| CN111966892A (en) | Data processing method and device, computer storage medium and electronic equipment | |
| CN109992614B (en) | Data acquisition method, device and server | |
| CN113468886A (en) | Work order processing method and device and computer equipment | |
| CN112163879A (en) | User rights pushing method, device, server and storage medium | |
| CN111784346A (en) | User interception method and device based on unmanned selling equipment and server | |
| CN114428723A (en) | Test system, system test method, related device and storage medium | |
| CN110750563A (en) | Multi-model data processing method, system, device, electronic equipment and storage medium | |
| CN109542609A (en) | A kind of method, apparatus withholding refund, computer equipment and storage medium | |
| CN115689555A (en) | Order payment system, method and device, storage medium and electronic equipment | |
| CN115599968A (en) | Transaction data processing method and device, computer equipment and storage medium | |
| CN114416585A (en) | Automatic testing method and device |
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 |