Verification full-process tracking method and system for multi-end users

Abstract

The present invention relates to the technical field of verification management. Disclosed are a verification full-process tracking method and system for multi-end users. The method comprises: acquiring port information, and performing identification to determine merchant information; on the basis of the port information and the merchant information, locating data storage information, and invoking a merchant verification record sub-library; acquiring a verification tracking request, performing information decomposition on the verification tracking request, and determining an order identification factor; on the basis of account information, using the order identification factor to traverse the merchant verification record sub-library to obtain matched verification information; and determining a full-process tracking permission on the basis of the account information, screening the matched verification information, and matching a tracking and localization result for feedback. The present invention solves the technical problem of being unable to accurately grasp the verification statuses of various orders due to the inability to intelligently and automatically perform tracking query and localization on real-time order information in existing verification full-process tracking.

Description

Multi-terminal user-oriented whole-process tracking method and system for verification TECHNICAL FIELD

[0001] The present application relates to the technical field of verification management, in particular to a multi-terminal user-oriented whole-process tracking method and system for verification. BACKGROUND

[0002] With the continuous expansion of the scale of enterprises and the increasing complexity of business, verification management has become a crucial part of enterprise management and operation. A whole-process verification tracking system aims to achieve real-time monitoring and data tracing of the verification process by integrating data information from multiple departments and systems of an enterprise. Through the whole-process verification tracking system, enterprises can achieve cross-department collaboration and share data resources. At the same time, risks and problems in the verification process can be discovered and solved in a timely manner. However, traditional whole-process verification tracking relies on offline manual processing, which is time-consuming and inefficient, and cannot meet the rapidly changing market demands and diversified business. When facing multi-terminal users, it cannot accurately query and locate the verification status of orders, and cannot guarantee the efficiency and accuracy of enterprise verification management.

[0003] Therefore, in the current whole-process verification tracking technology, there is a technical problem that when facing multi-terminal users, real-time order information cannot be tracked and located intelligently and automatically, which leads to an inability to accurately grasp the verification status of various orders. TECHNICAL PROBLEM

[0004] The existing whole-process verification tracking has the technical problem that when facing multi-terminal users, real-time order information cannot be tracked and located intelligently and automatically, which leads to an inability to accurately grasp the verification status of various orders. TECHNICAL SOLUTION

[0005] The present application provides a multi-terminal user-oriented whole-process tracking method and system for verification, which uses information acquisition, record library retrieval, information decomposition, and permission management techniques to solve the technical problem of existing whole-process verification tracking that cannot intelligently and automatically track and locate real-time order information when facing multi-terminal users, which leads to an inability to accurately grasp the verification status of various orders. The technical effect of automatically and intelligently accurately querying and locating the verification status of orders is achieved, thereby improving the efficiency and accuracy of enterprise verification management.

[0006] The application provides a multi-end user-oriented verification whole-process tracking method, which comprises the following steps: acquiring port information, identifying a merchant based on the port information, determining merchant information, and uniquely corresponding the port information and the merchant information; positioning data storage information according to the port information and the merchant information, and calling a merchant verification record sub-library; acquiring a verification tracking request, wherein the verification tracking request comprises account information of a sending request, performing information decomposition in the verification tracking request, determining an order identification factor, and the order identification factor comprises one or more of an order state, an order generation time and a verification code information; based on the account information, traversing the merchant verification record sub-library by using the order identification factor to obtain matching verification information, wherein the matching verification information comprises whole-process record data of a related verification order in the verification tracking request; determining a whole-process tracking permission according to the account information, screening the matching verification information based on the whole-process tracking permission, and feeding back a matching tracking positioning result.

[0007] In a possible implementation, before the acquiring port information, the following processing is performed: performing port authorization according to the merchant information and the port information, generating a port identification rule; acquiring an external verification code service creation rule, including a service type, a verification mode, a verification period, establishing a mapping relationship between the port identification rule and the external verification code service creation rule; receiving verification request information, including a verification time, a service type, account information, a verification code and a sending port; based on the port identification rule, the sending port is checked, when the checking is passed, the business verification information is generated according to the verification time, the service type, the account information and the verification code; according to the business verification information, the verification tracking is performed, and the transaction batch of the verification information generated in the transaction is generated; after the batch audit of the transaction batch, the verification code order is generated based on the verification code, the merchant fund account deduction instruction is sent to the merchant through the port information, and the log record is performed; according to the verification code order and the merchant fund account deduction instruction, the local verification settlement sheet is generated and stored locally, wherein the local storage position comprises a local verification record master library and a merchant verification record sub-library, the local verification record master library and the merchant verification record sub-library have a mapping relationship according to the verification code order, and the merchant verification record sub-library node is matched and stored according to the merchant information, the verification time and the verification code.

[0008] In a possible implementation, before the matching and storing of the merchant verification record sub-library node according to the merchant information, the verification time, and the verification code, the following processing is performed: performing verification business analysis on the merchant information to determine a verification business category of the merchant, a merchant cooperation period, and a verification business quantity; performing sub-library node division based on the verification business category of the merchant, the merchant cooperation period, and the verification business quantity, each sub-library node corresponding to one verification business category, the number of nodes corresponding to the verification business quantity, and the sub-library node including a time sequence chain that matches the merchant cooperation period; and connecting the sub-library nodes in a normal order according to the time sequence relationship of the merchant cooperation period, and identifying the sub-library nodes based on the identification code corresponding to the verification business category, the merchant cooperation period, and the verification business quantity.

[0009] In a possible implementation, the feedback of the matching and tracking positioning result further performs the following processing: locating the local verification record master library according to the matching verification information to obtain master record positioning information and record information; generating and storing a master library query log according to the master record positioning information and the record information; performing request quantity analysis according to the verification tracking request to determine a quantity requirement; when the quantity requirement is 1 and the quantity of the matching verification information does not meet the requirement, performing differential analysis according to the matching verification information to determine a differential factor, and generating and feeding back request supplement information based on the differential factor, the differential factor being used for precision matching of the matching verification information, the quantity requirement judgment and the differential factor matching being repeatedly performed until the quantity requirement of the verification tracking request is met, and the matching verification information meeting the requirement being fed back.

[0010] In a possible implementation, after the generation and storage of the master library query log, the following processing is further performed: respectively performing port query log and query business content clustering according to the master library query log to obtain each port query data set and query business content cluster; performing verification business evaluation of each merchant according to the each port query data set; performing business content evaluation according to the query business content cluster; locating a verification process according to the verification business evaluation information and the business content evaluation information, and performing abnormal analysis based on the verification business evaluation information and the business content evaluation information to optimize the verification process corresponding to the abnormal analysis result.

[0011] In a possible implementation, the merchant information is subjected to a cancellation service analysis to determine a cancellation service category of the merchant, a merchant cooperation period, and a cancellation service quantity, and the following processing is further performed: the cancellation service analysis is performed on all merchant cancellation record sub-libraries and sub-library nodes to determine a cancellation order proportion; based on the cancellation order proportion of all merchants, a cancellation matrix is constructed, and horizontal and vertical analyses are performed to determine a merchant cancellation service evaluation value and a cancellation service periodicity evaluation value; and based on the merchant cancellation service evaluation value and the cancellation service periodicity evaluation value, the cancellation service is subjected to quantity matching, and a cancellation service cooperation relationship is set.

[0012] In a possible implementation, the sending port is subjected to verification based on the port identification rule, and when the verification is passed, the business cancellation information is generated according to the cancellation time, the service category, the account information, and the cancellation code, and the following processing is further performed: based on a cancellation whole process, a cancellation process list is constructed, including a cancellation process, a process record, and a result requirement; based on the cancellation process list, a process constraint condition is set, the process constraint condition is a necessary condition for a normal state of the cancellation process, the process constraint condition is added to the cancellation process; and the cancellation process record is monitored, and when the cancellation process record triggers the process constraint condition, a reminder information is sent.

[0013] The application further provides a cancellation whole process tracking system for multiple end users, including:

[0014] A merchant information acquisition module, which is configured to acquire port information, identify a merchant based on the port information, and determine merchant information, the port information being uniquely corresponding to the merchant information;

[0015] A merchant cancellation record library calling module, which is configured to locate data storage information according to the port information and the merchant information, and call a merchant cancellation record sub-library;

[0016] An order identification factor determination module, which is configured to acquire a cancellation tracking request including account information of a sending request, perform description information decomposition in the cancellation tracking request, and determine an order identification factor including one or more of an order state, an order generation time, and cancellation code information;

[0017] A matched cancellation information obtaining module, which is configured to perform iteration in the merchant cancellation record sub-library based on the account information and the order identification factor, and obtain matched cancellation information including whole process record data of a relevant cancellation order in the cancellation tracking request;

[0018] The tracking positioning result matching module is configured to determine a full-process tracking permission according to the account information, filter the matching cancellation information based on the full-process tracking permission, and match and feed back the tracking positioning result.

[0019] The multi-terminal user-oriented cancellation full-process tracking method and system provided in the present application obtains port information and identifies the same, and determines merchant information; locates data storage information according to the port information and the merchant information, and calls a merchant cancellation record sub-database; obtains a cancellation tracking request and decomposes information, and determines an order identification factor; based on account information, the order identification factor is used to traverse the merchant cancellation record sub-database, and matching cancellation information is obtained; the full-process tracking permission is determined according to the account information, the matching cancellation information is filtered, and the tracking positioning result is matched and fed back, thereby solving the technical problem that the existing cancellation full-process tracking cannot intelligently and automatically track and locate real-time order information when facing multi-terminal users, and thus cannot accurately grasp the cancellation status of various orders, achieving accurate query and positioning of the order cancellation status in an automated and intelligent manner, and thereby improving the efficiency and accuracy of enterprise cancellation management. Beneficial effects

[0020] The technical problem that the existing cancellation full-process tracking cannot intelligently and automatically track and locate real-time order information when facing multi-terminal users, and thus cannot accurately grasp the cancellation status of various orders is solved, accurate query and positioning of the order cancellation status in an automated and intelligent manner are achieved, and thereby the efficiency and accuracy of enterprise cancellation management are improved. BRIEF DESCRIPTION OF DRAWINGS

[0021] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments of the present disclosure will be briefly introduced below, and the flowcharts are used to illustrate the operations performed by the system according to the embodiments of the present application. It should be understood that the foregoing or the following operations are not necessarily performed in sequence. On the contrary, various steps can be processed in reverse order or simultaneously according to needs. At the same time, other operations can be added to these processes, or one or more steps can be removed from these processes.

[0022] FIG. 1 is a flowchart of a multi-terminal user-oriented cancellation full-process tracking method according to an embodiment of the present application;

[0023] FIG. 2 is a structural diagram of a multi-terminal user-oriented cancellation full-process tracking system according to an embodiment of the present application.

[0024] Port information acquisition module 10, merchant cancellation record word library calling module 20, order identification factor determination module 30, matching cancellation information obtaining module 40, tracking positioning result matching module 50. DETAILED DESCRIPTION

[0025] The above description is only a summary of the technical scheme of the present application. In order to make the technical means of the present application more clearly understood, and to be implemented according to the content of the specification, and in order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the following specific embodiments of the present application are described.

[0026] In order to make the purposes, technical schemes and advantages of the present application more clear, the following will further describe the present application with reference to the accompanying drawings. The described embodiments should not be regarded as limiting the present application. All other embodiments obtained by those skilled in the art without making creative labor are within the scope of protection of the present application.

[0027] In the following description, "some embodiments" are related to a subset of all possible embodiments, but it can be understood that "some embodiments" can be the same subset or different subset of all possible embodiments, and can be combined with each other without conflict. The term "first\second" is only to distinguish similar objects, and does not represent the specific order of the objects. The terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or server including a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or modules not clearly listed or inherent to these processes, methods, products or devices. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as understood by those skilled in the art to which the present application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application.

[0028] The embodiments of the present application provide a multi-end user-oriented cancellation whole process tracking method, as shown in FIG. 1, the method comprises:

[0029] In step S100, port information is acquired, and based on the port information, a merchant is identified, and merchant information is determined, the port information uniquely corresponding to the merchant information. Specifically, port information of multiple different user terminals (such as PC terminals, mobile terminals, and tablet terminals) is acquired from a certain data source (such as a database or an API interface), which can include a port number, an IP address, a protocol type, and the like, the acquired port information is analyzed and processed, for example, the port information is matched and queried with merchant information, a merchant associated therewith is identified, and detailed information of the merchant, such as a merchant name and an address, is further determined, each port information corresponds to a unique and specific merchant information, to help accurately identify merchant-related information subsequently.

[0030] In a possible implementation, before the step S100 of acquiring port information, the method further includes the following steps. In step S90, port authorization is performed according to the merchant information and the port information, and a port identification rule is generated. Based on the merchant information and the port information and the corresponding relationship, a rule is formulated to authorize or restrict access of a specific merchant to a specific port, which indicates which merchants are authorized to access which ports. For example, merchant A can access port 66 but cannot access port 3306. Access restrictions, access time restrictions, and the like are set for specific ports or merchants. The port identification rule is used to identify and verify the identity information of a merchant requesting to access a specific port. In step S91, an external verification code service creation rule is acquired, including a service type, a verification mode, and a verification period, and a mapping relationship between the port identification rule and the external verification code service creation rule is established. Specifically, the external verification code service creation rule is acquired, and a mapping relationship between the port identification rule and the external verification code service creation rule is established. The verification code service includes a service type, a verification mode, and a verification period. The service type of the external verification code service can include a coupon, a discount card, and the like. The verification mode specifies the verification method, such as offline code scanning verification, online input of a verification code for verification, and the like. The verification period refers to the validity period of the verification code, which can be one-time verification, verification by a number of times, or specific time-limited verification. In step S92, a verification request information is received, including a verification time, a service type, account information, a verification code, and a sending port. The verification time is a timestamp recording the verification request. The service type refers to the specific service of the verification request. The account information refers to the account information of the verification request, which is used to identify the source of the verification request and includes an account name and an account type. The verification code is used for verification and recording. The sending port is the port information of the sending of the verification request. In step S94, the sending port is verified based on the port identification rule. When the verification is passed, service verification information is generated according to the verification time, the service type, the account information, and the verification code. The sending port is verified based on the port identification rule to verify the access authority of the port, so that the merchant corresponding to the sending port can access the port, and unauthorized port access is prevented. After the verification is passed, the service verification information is generated according to the verification time, the service type, the account information, and the verification code. Specifically, the above verification-related information and verification status, verification result, and the like are integrated into a complete service verification information for recording. For example, the store name, the product name, and the purchase amount are verified one by one, and a file verification result is generated for the verification result. In step S95, the service verification information is used for verification tracking, and a transaction batch is generated for the verification information of a transaction. Specifically, the verification tracking refers to monitoring the status and changes of the service verification information, realizing tracking and management of the verification operation, integrating the related verification records into a transaction batch according to the verification information of the transaction, and facilitating subsequent continuous processing.Also included is step S96, after the batch of transactions is audited, a cancellation code order is generated based on the cancellation code, a merchant fund account deduction instruction is sent to the merchant through the port information, and a log record is made. Specifically, the generated transaction batch is audited to ensure that the cancellation information and transaction information in the batch are accurate, such as verification of the cancellation information, reconciliation, and other operations, a cancellation order is generated based on the cancellation code, including the cancellation code, transaction amount, transaction content, merchant information, transaction time, and other information, then a merchant fund account deduction instruction is sent to the merchant through the port, the deduction operation is completed, and during the deduction instruction sending process, relevant information is recorded, including the deduction instruction content, the deduction time, the sending time, the receiving status, and the like. Also included is step S97, according to the cancellation code order and the merchant fund account deduction instruction, a local cancellation settlement sheet is generated and stored locally, wherein the local storage location includes a local cancellation record master library and a merchant cancellation record sub-library, the local cancellation record master library and the merchant cancellation record sub-library have a mapping relationship according to the cancellation code order, and the merchant cancellation record sub-library node is matched and stored according to the merchant information, the cancellation time, and the cancellation code. Specifically, the local cancellation record master library is a main database that stores all cancellation records, containing cancellation information of all merchants; the merchant cancellation record sub-library is a subset of the master library, which is stored according to different merchant information, and the corresponding node is matched in the merchant cancellation record sub-library according to the merchant information of the cancellation order, and the cancellation information is stored in the node.

[0031] In a possible implementation, before the step S97 of storing the merchant verification record sub-database node matched according to the merchant information, the verification time and the verification code, the step S10 of performing verification business analysis on the merchant information to determine the verification business category of the merchant, the merchant cooperation period and the verification business quantity is further included. Specifically, the verification business category refers to analyzing the user verification behavior and transaction mode to determine the verification business category of the merchant, for example, car washing, maintenance, driving, annual inspection and other automobile service businesses; the merchant cooperation period is determined by analyzing the historical verification data and transaction of the merchant, and is evaluated according to the transaction frequency and stability of the merchant and other factors; the verification business quantity refers to evaluating and counting the verification business quantity of the merchant according to the historical verification information, including the verification of each transaction. The step S20 of dividing the sub-database node based on the verification business category of the merchant, the merchant cooperation period and the verification business quantity is further included, each sub-database node corresponds to a verification business category, the number of nodes corresponds to the verification business quantity, and the sub-database node includes a time sequence chain that matches the merchant cooperation period. Specifically, the merchant verification record database is divided into different sub-database nodes according to the verification business category of the merchant, each node corresponds to a verification business category, the number of nodes corresponds to the verification business quantity, each node contains verification records of the corresponding verification business category, and the time sequence chain of the sub-database node is the order of recording verification information according to time, which is used for subsequent tracking of the verification business process. The verification information is sorted and managed according to the cooperation period of the merchant, which facilitates monitoring of the verification process. The step S30 of sequentially connecting the sub-database nodes according to the time sequence relationship of the merchant cooperation period and identifying the sub-database nodes based on the generated identification code corresponding to the verification business category, the merchant cooperation period and the verification business quantity is further included. Specifically, the sub-database nodes divided according to the verification business category are sequentially connected according to the time sequence relationship of the merchant cooperation period to form a continuous data stream, and an identification code is generated to identify and distinguish the sub-database nodes. The identification code can be generated in a unique and easily identifiable coding manner, for example, by combining the abbreviation of the verification business category, the timestamp of the merchant cooperation period and the serial number of the verification business quantity. The generated identification code is applied to each sub-database node to uniquely identify and distinguish the verification business category, the merchant cooperation period and the verification business quantity represented by the node. Through the steps S10 to S30, one port commodity can include multiple business types, different verification codes and different activity contents, and different nodes are divided according to the business content and verification rules of the merchant in different periods, for example, the verification rules include fixed time period for timed task verification time, limited verification order with earlier completion time in the order to be verified, verification according to the transaction batch ID number of the system when the order verification time is the same, etc., to realize positioning and tracking of the entire cooperation process of the merchant, and to track the whole process of each activity or service period respectively.

[0032] In a possible implementation, the step S10 further includes a step S11 of performing a business analysis on the all-merchant cancellation record sub-database and sub-database nodes to determine a cancellation order proportion. The cancellation order proportion refers to a proportion of cancellation orders of each cancellation business category to a total number of cancellation orders, to determine the contribution of each category. The step S10 further includes a step S12 of constructing a cancellation matrix based on all cancellation order proportions, performing horizontal and vertical analyses, and determining a merchant cancellation business evaluation value and a cancellation business periodic evaluation value. Specifically, a matrix is constructed according to the proportion data of all cancellation orders, rows represent different cancellation business categories, and columns represent different merchant cooperation periods. The cancellation matrix is analyzed horizontally and vertically, the performance of different merchants in each cancellation business category is compared, and the performance of merchants in different cancellation business categories in the same period is compared, to determine the merchant cancellation business evaluation value and the cancellation business periodic evaluation value. The step S10 further includes a step S13 of performing quantity matching on the cancellation business based on the merchant cancellation business evaluation value and the cancellation business periodic evaluation value, and setting a cancellation business cooperation relationship. Specifically, the cancellation business quantities between merchants are matched according to the cancellation business and demand of the merchants. When a new cancellation business is needed, merchants are matched and the quantities are allocated based on the cancellation capabilities of different merchants. The allocation proportion of a merchant with a strong cancellation capability is high, to ensure that the cancellation business quantities between cooperating merchants are reasonably matched, and to avoid resource waste or supply-demand imbalance.

[0033] In a possible implementation, the step S97 further includes a step S40 of constructing a cancellation process list based on the cancellation whole process, including a cancellation process, a process record, and a result requirement. The cancellation whole process tracking is performed to clearly understand each link and process record in the cancellation process, to ensure smooth progress of the cancellation process and effective tracking of the result. Specifically, the cancellation process list includes the cancellation process, the process record, and the result requirement, such as order generation and distribution, cancellation information confirmation, cancellation operation, cancellation information uploading, fund settlement, and cancellation result review. The step S97 further includes a step S50 of setting a process constraint condition based on the cancellation process list, the process constraint condition being a necessary condition for a normal state of the cancellation process, and the process constraint condition being added to the cancellation process. The step S97 further includes a step S60 of monitoring the cancellation process record, and sending a reminder information when the cancellation process record triggers the process constraint condition. Through the steps S40 to S60, the important nodes and contents in the whole process are set as constraint conditions for real-time monitoring. If the constraint conditions are not met, triggering is performed, and timely reminders are given, to ensure smooth progress of the cancellation business, to avoid incomplete tracking, and to avoid occurrence of situations such as order state or cancellation exception and no fund arrival. For example, when fund data needs to be exported according to a condition query, the data of the imported fund file is arranged in reverse chronological order, a unique identifier is automatically generated by the system as a batch number, the system verifies the information of the fund file after receiving the import application of the fund file, and the import is successful.

[0034] After obtaining the port information and the merchant information, step S200 is performed to locate data storage information according to the port information and the merchant information, and to call a merchant cancellation record sub-library. Specifically, according to the obtained port information and the merchant information, relevant data storage information is located in a database, and according to the merchant information and the identification of the cancellation record, the merchant cancellation record sub-library is called, so as to ensure that the extracted cancellation record contains the required cancellation time, cancellation code, cancellation state and other information.

[0035] After calling the merchant cancellation record sub-library, step S300 is performed to obtain a cancellation tracking request, the cancellation tracking request including account information of a sending request, and performing information decomposition described in the cancellation tracking request to determine an order identification factor, the order identification factor including one or more of an order state, an order generation time, and a cancellation code information. Specifically, the cancellation tracking request is obtained, the account information of the sending cancellation tracking request is confirmed, the description information in the cancellation tracking request is parsed, including the specific content of the cancellation request, the order identification factor is determined from the cancellation tracking request, which can include one or more combinations of the order state, the order generation time, or the cancellation code information, the order factor is used to query the corresponding cancellation order information in the system, and the accuracy and integrity of the order are ensured.

[0036] After obtaining the cancellation tracking request, step S400 is performed to perform traversal in the merchant cancellation record sub-library based on the account information and the order identification factor to obtain matching cancellation information, the matching cancellation information including full-process record data of a relevant cancellation order in the cancellation tracking request, such as data in a cancellation transaction file and data in a cancellation fund file, and being displayed with a merchant name and a project number respectively. The account information and the order identification factor are used to perform traversal in the merchant cancellation record sub-library to obtain matching cancellation information corresponding to the order identification factor, wherein the matching cancellation information includes full-process record data of a relevant cancellation order in the cancellation tracking request, such as order creation information, payment settlement state, cancellation state record, cancellation code operation record, batch state, audit state, operation verification record, and the like, wherein the audit state includes to be audited, to be passed, and to be rejected, and the cancellation state record includes cancelled amount and to be cancelled amount, so as to realize full-process tracking and positioning of the cancellation order.

[0037] After obtaining the matched cancellation information, step S500 is performed to determine the full-process tracking authority according to the account information, filter the matched cancellation information based on the full-process tracking authority, and feed back the matching tracking positioning result. The full-process tracking authority is determined according to the obtained account information, the full-process of the account is tracked and verified to ensure that the account has access to relevant cancellation information, the scope of cancellation information that the account can access and operate is determined according to the authority level of the account, including the data in the cancellation record sub-library, the matched cancellation information is filtered based on the full-process tracking authority, specifically, according to the filtered cancellation information, tracking positioning is performed to view the cancellation order state, cancellation state change and operation record, etc., complete tracking positioning results are obtained and fed back to the corresponding account, thereby realizing effective management and tracking of the cancellation process.

[0038] In a possible implementation, step S500 further includes step S510 of generating and storing a parent library query log according to the parent library record positioning information and the record information. Specifically, when the parent library record positioning is performed, the relevant positioning information is recorded, such as query time, query condition, query result, etc., the parent library query log is generated according to the recorded positioning information, including query timestamp, query condition (order identification factor), query result quantity, query operation type (query, update, deletion, etc.), query operation performer information (account information, etc.) and other related information, the generated cancellation order query log is stored in a proper position, and access authority control is added to ensure data security. Step S520 of performing request quantity analysis according to the cancellation tracking request to determine the quantity requirement is further included. Specifically, the request quantity analysis is performed on the cancellation tracking request, the quantity requirement of the cancellation tracking request is determined according to the analysis result, in combination with the processing capacity and resource condition of the system, such as the average request quantity, peak request quantity, etc. per hour or per day. Step S530 of, when the quantity requirement is 1 and the quantity of the matched cancellation information does not meet the requirement, performing differential analysis according to the matched cancellation information to determine a differential factor, generating and feeding back request supplement information based on the differential factor, and the differential factor is used for precision matching of the matched cancellation information, the quantity requirement judgment and differential factor matching are repeatedly performed until the quantity requirement of the cancellation tracking request is met, and the matched cancellation information meeting the requirement is fed back.

[0039] In a possible implementation, after the step S520 of generating and storing the mother query log, the method further includes a step S521 of performing port query log and query business content clustering based on the mother query log to obtain each port query data set and query business content cluster. Based on the mother query log, the port query log and the query business content are obtained, and clustering analysis is performed on the port query log and the query business content. The query log data is classified and grouped according to different ports to obtain each port query data set. The query business content is clustered (such as K-means clustering) according to the extracted business content information, and similar query contents are classified into the same category to obtain the query business content cluster. The method further includes a step S522 of performing verification business evaluation on each merchant based on the each port query data set. The method further includes a step S523 of performing business content evaluation based on the query business content cluster. The method further includes a step S524 of locating the verification process based on the verification business evaluation information and the business content evaluation information, and performing abnormality analysis based on the verification business evaluation information and the business content evaluation information to optimize the verification process corresponding to the abnormality analysis result. Specifically, each process of the verification process, including request submission, information verification, verification processing, and result feedback, is determined based on the verification business evaluation information and the business content evaluation information, abnormality analysis is performed, abnormal conditions such as system errors, inconsistent information, and delayed processing are identified, the causes of the abnormality are analyzed, corresponding optimization schemes are formulated based on the analysis result, the verification process is optimized, the effect is monitored and feedback is collected, so as to improve the efficiency and accuracy of the verification process.

[0040] In the foregoing, the multi-terminal user-oriented verification full-process tracking method according to the embodiment of the application is described in detail with reference to FIG. 1. Next, the multi-terminal user-oriented verification full-process tracking system according to the embodiment of the application will be described with reference to FIG. 2.

[0041] The multi-terminal user-oriented verification full-process tracking system according to the embodiment of the application is used to solve the technical problem that the existing verification full-process tracking cannot intelligently and automatically track and locate real-time order information when facing multi-terminal users, and thus cannot accurately grasp the verification state of various orders, so as to achieve the technical effect of automatically and intelligently accurately tracking and locating the order verification state, and thus improve the efficiency and accuracy of enterprise verification management. The multi-terminal user-oriented verification full-process tracking system includes a port information acquisition module 10, a merchant verification record library calling module 20, an order identification factor determination module 30, a matching verification information obtaining module 40, and a tracking and positioning result matching module 50.

[0042] A port information acquisition module 10 is configured to acquire port information, identify a merchant based on the port information, and determine merchant information, wherein the port information corresponds to the merchant information uniquely.

[0043] A merchant verification record dictionary calling module 20 is configured to locate data storage information according to the port information and the merchant information, and call a merchant verification record sub-dictionary.

[0044] An order identification factor determination module 30 is configured to acquire a verification tracking request, perform information decomposition described in the verification tracking request, and determine an order identification factor, wherein the verification tracking request includes account information of a sending request, and the order identification factor includes one or more of an order state, an order generation time, and verification code information.

[0045] A matching verification information obtaining module 40 is configured to perform iteration in the merchant verification record sub-dictionary based on the account information and the order identification factor, and obtain matching verification information, wherein the matching verification information includes full-process record data of a relevant verification order in the verification tracking request.

[0046] A tracking positioning result matching module 50 is configured to determine a full-process tracking authority according to the account information, filter the matching verification information based on the full-process tracking authority, and match a tracking positioning result for feedback.

[0047] In the following, the specific configuration of the port information acquisition module 10 will be described in detail. As described above, the port information is acquired, the merchant is identified based on the port information, the merchant information is determined, the port information uniquely corresponds to the merchant information, and the port information acquisition module 10 can further include: generating a port identification rule based on the merchant information and the port information; acquiring an external verification code service creation rule, including service type, verification mode, verification period, establishing a mapping relationship between the port identification rule and the external verification code service creation rule; receiving a verification request information, including verification time, service type, account information, verification code, sending port; based on the port identification rule, the sending port is checked, when the check is passed, the business verification information is generated according to the verification time, service type, account information and verification code; according to the business verification information, the verification tracking is carried out, and the transaction batch of the transaction verification information is generated; after the batch audit of the transaction batch, the verification code order is generated based on the verification code, the merchant fund account deduction instruction is sent to the merchant through the port information, and the log record is recorded; according to the verification code order and the merchant fund account deduction instruction, a local verification settlement sheet is generated and stored locally, wherein the local storage location includes a local verification record mother library and a merchant verification record sub-library, the local verification record mother library and the merchant verification record sub-library have a mapping relationship according to the verification code order, and the merchant verification record sub-library node is matched and stored according to the merchant information, verification time and verification code.

[0048] In the following, the specific configuration of the port information acquisition module 10 will be described in detail. As described above, before the merchant verification record sub-library node is matched and stored according to the merchant information, verification time and verification code, the port information acquisition module 10 further includes: performing verification business analysis on the merchant information to determine the verification business category of the merchant, the merchant cooperation period and the verification business quantity; based on the verification business category of the merchant, the merchant cooperation period and the verification business quantity, the sub-library node is divided, each sub-library node corresponds to a verification business category, the node quantity corresponds to the verification business quantity, and the sub-library node includes a time sequence chain which matches the merchant cooperation period; according to the time sequence relationship of the merchant cooperation period, the sub-library nodes are connected in sequence, and the sub-library nodes are identified based on the identification code corresponding to the verification business category, the merchant cooperation period and the verification business quantity.

[0049] Below, the specific configuration of the tracking positioning result matching module 50 will be described in detail. As described above, the matching tracking positioning result feedback, the tracking positioning result matching module 50 can further include: according to the matching cancellation information, positioning the local cancellation record mother library, obtaining the mother record positioning information and record information; according to the mother record positioning information and record information, generate the mother query log for storage; according to the number of requests for the cancellation tracking request, determine the quantity requirement; when the quantity requirement is 1, and the number of the matching cancellation information does not meet, according to the matching cancellation information, differential analysis is performed to determine the difference factor, and request supplement information is generated based on the difference factor for feedback, the difference factor is used for precision matching of the matching cancellation information, the quantity requirement judgment and the difference factor matching are repeated until the quantity requirement of the cancellation tracking request is met, and the matching cancellation information that meets the requirement is fed back.

[0050] Below, the specific configuration of the tracking positioning result matching module 50 will be described in detail. As described above, the matching tracking positioning result feedback, the tracking positioning result matching module 50 can further include: according to the matching cancellation information, positioning the local cancellation record mother library, obtaining the mother record positioning information and record information; according to the mother record positioning information and record information, generate the mother query log for storage; according to the number of requests for the cancellation tracking request, determine the quantity requirement; when the quantity requirement is 1, and the number of the matching cancellation information does not meet, according to the matching cancellation information, differential analysis is performed to determine the difference factor, and request supplement information is generated based on the difference factor for feedback, the difference factor is used for precision matching of the matching cancellation information, the quantity requirement judgment and the difference factor matching are repeated until the quantity requirement of the cancellation tracking request is met, and the matching cancellation information that meets the requirement is fed back.

[0051] Below, the specific configuration of the port information acquisition module 10 will be described in detail. The port information acquisition module 10 further includes: performing cancellation business analysis on all merchant cancellation record sub-libraries and sub-library nodes to determine the cancellation order proportion; based on all cancellation order proportions, constructing a cancellation matrix for horizontal and vertical analysis to determine the merchant cancellation business evaluation value and the cancellation business periodic evaluation value; based on the merchant cancellation business evaluation value and the cancellation business periodic evaluation value, performing quantity matching on the cancellation business, and setting the cancellation business cooperation relationship.

[0052] Below, the specific configuration of the port information acquisition module 10 will be described in detail. The port information acquisition module 10 can further include: based on the cancellation whole process, constructing a cancellation process list including the cancellation process, the process record, and the result requirement; according to the cancellation process list, setting the process constraint condition which is the necessary condition for the normal state of the cancellation process, and adding the process constraint condition to the cancellation process; monitoring the cancellation process record, and sending a reminder information when the cancellation process record triggers the process constraint condition.

[0053] The multi-terminal user-oriented whole-process tracking system provided by the embodiments of the present application can execute the multi-terminal user-oriented whole-process tracking method provided by any of the embodiments of the present application, and has the corresponding function modules and beneficial effects of the execution method.

[0054] Although the present application makes various references to certain modules in the system according to the embodiments of the present application, however, any number of different modules can be used and run on the user terminal and / or server, and the various units and modules are only divided according to the functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of the functional units are only for the convenience of mutual differentiation, and are not used to limit the protection scope of the present application.

[0055] The above specific embodiments do not constitute a limitation on the protection scope of the present application. Those skilled in the art should understand that various modifications, combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A method for tracking the entire write-off process for multiple users, characterized by: The method comprises: Acquire port information, identify a merchant based on the port information, and determine merchant information, wherein the port information uniquely corresponds to the merchant information; According to the port information and merchant information, locate the data storage information and retrieve the merchant verification record sub-library; Obtaining a write-off tracking request, the write-off tracking request including information about the account that sent the request, decomposing information described in the write-off tracking request, and determining order identification factors, the order identification factors including one or more of order status, order generation time, and write-off code information; Based on the account information, using the order identification factor, traverse the merchant verification record sub-library to obtain matching verification information, wherein the matching verification information includes full-process record data of the verification order related to the verification tracking request; The full-process tracking authority is determined according to the account information, the matching verification information is screened based on the full-process tracking authority, and the matching tracking positioning result is fed back.

2. The method for tracking the entire verification process for multiple users according to claim 1, characterized in that: Before obtaining the port information, the method further includes: Perform port authorization based on the merchant information and port information, and generate port identification rules; Obtaining external verification code service creation rules, including service type, verification mode, and verification period, and establishing a mapping relationship between the port identification rules and the external verification code service creation rules; Receive verification request information, including verification time, service type, account information, verification code, and sending port; Verifying the sending port based on the port identification rule, and when the verification is passed, generating service verification information according to the verification time, service type, account information, and verification code; Based on the business write-off information, write-off tracking is performed and transaction batches are generated for the write-off information of the transactions that have occurred; After batch review of the transaction batch, a verification code order is generated based on the verification code, a merchant fund account deduction instruction is sent to the merchant through the port information, and a log record is made; Based on the verification code order and the merchant fund account deduction instruction, a local verification settlement statement is generated and stored locally, wherein the local storage location includes a local verification record parent database and a merchant verification record sub-database. The local verification record parent database and the merchant verification record sub-database have a mapping relationship based on the verification code order, and the merchant verification record sub-database node matching storage is performed based on the merchant information, verification time, and verification code.

3. The method for tracking the entire verification process for multiple users according to claim 2, characterized in that: Before performing matching and storing of merchant verification record sub-library nodes according to the merchant information, verification time, and verification code, the method further includes: Conduct write-off business analysis on the merchant information to determine the merchant's write-off business category, merchant cooperation cycle, and write-off business volume; Based on the merchant's write-off business category, merchant cooperation cycle, and write-off business volume, sub-database nodes are divided. Each sub-database node corresponds to a write-off business category, and the number of nodes corresponds to the number of write-off businesses. The sub-database nodes include a time sequence chain that matches the merchant cooperation cycle. According to the time sequence relationship of the merchant cooperation cycle, the sub-database nodes are connected in positive order, and identification codes are generated based on the write-off business category, merchant cooperation cycle, and write-off business quantity to identify the sub-database nodes.

4. The method for tracking the entire verification process for multiple users according to claim 3, characterized in that: Feedback of the matching tracking and positioning results includes: Locating the local write-off record master database based on the matching write-off information, and obtaining master database record location information and record information; Generate a parent database query log based on the parent database record location information and record information for storage; Analyze the requested quantity based on the verification tracking request and determine the quantity requirement; When the quantity requirement is 1 and the quantity of the matching write-off information is not met, a differential analysis is performed based on the matching write-off information to determine the difference factor, and a request for supplementary information is generated based on the difference factor for feedback. The difference factor is used to accurately match the matching write-off information. The quantity requirement judgment and difference factor matching are repeated until the quantity requirement of the write-off tracking request is met, and the matching write-off information that meets the requirements is fed back.

5. The method for tracking the entire verification process for multiple users according to claim 4, characterized in that: After generating and storing the parent database query log, the method further includes: According to the mother database query log, the port query log and the query business content are clustered respectively to obtain the query data set and query business content cluster of each port; Conducting write-off business evaluation on each merchant based on the query data sets of each port; Performing business content evaluation based on the query business content cluster; The write-off process is located according to the write-off business evaluation information and the business content evaluation information, and an abnormality analysis is performed based on the write-off business evaluation information and the business content evaluation information, and the write-off process corresponding to the abnormality analysis result is optimized.

6. The method for tracking the entire verification process for multiple users according to claim 3, characterized in that: The method further comprises: Conduct write-off business analysis on all merchant write-off record sub-databases and sub-database nodes to determine the write-off order ratio; Based on the proportion of all written-off orders, a write-off matrix is ​​constructed to conduct horizontal and vertical analysis to determine the merchant's write-off business evaluation value and the write-off business periodicity evaluation value; Based on the merchant's write-off business evaluation value and the write-off business periodic evaluation value, the write-off business is matched in quantity and a write-off business cooperation relationship is established.

7. The method for tracking the entire verification process for multiple users according to claim 2, characterized in that: The method further comprises: Based on the entire write-off process, a write-off process list is constructed, including the write-off process, process records, and result requirements; According to the write-off process list, set process constraints, which are necessary conditions for the normal state of the write-off process, and add the process constraints to the write-off process; Monitor the write-off process record, and send a reminder message when the write-off process record triggers the process constraint condition.

8. The full-process verification tracking system for multiple users is characterized by: The system is used to implement the method for tracking the entire write-off process for multiple users according to any one of claims 1 to 7, and the system includes: A merchant information acquisition module, the merchant information acquisition module is used to obtain port information, identify the merchant based on the port information, and determine the merchant information, the port information uniquely corresponding to the merchant information; A merchant write-off record word library retrieval module is used to locate data storage information based on the port information and merchant information, and retrieve the merchant write-off record sub-library; an order identification factor determination module, the order identification factor determination module being configured to obtain a write-off tracking request, the write-off tracking request including information about the account sending the request, decompose information described in the write-off tracking request, and determine an order identification factor, the order identification factor including one or more of order status, order generation time, and write-off code information; a matching write-off information acquisition module, configured to traverse the merchant write-off record sub-library based on the account information and the order identification factor to obtain matching write-off information, the matching write-off information including full-process record data of the relevant write-off order in the write-off tracking request; The tracking and positioning result matching module is used to determine the full-process tracking authority based on the account information, screen the matching verification information based on the full-process tracking authority, and provide feedback on the matching tracking and positioning results.

Images