CN115878733A

CN115878733A - Data uploading method, device, equipment and computer storage medium

Info

Publication number: CN115878733A
Application number: CN202211619971.5A
Authority: CN
Inventors: 叶小强
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Priority date: 2022-12-15
Filing date: 2022-12-15
Publication date: 2023-03-31

Abstract

The application discloses a data uploading method, a device, equipment and a computer storage medium, wherein the method comprises the following steps: acquiring abnormal transaction data and a business mechanism identifier corresponding to a business mechanism; determining a tenant label corresponding to the abnormal transaction data according to a preset tenant mechanism mapping table and a service mechanism identifier to obtain the abnormal transaction data marked with the tenant label; processing the abnormal transaction data marked with the tenant label aiming at each tenant label, and determining the data to be uploaded corresponding to the tenant label; and uploading the data to be uploaded corresponding to the tenant label to a target mechanism. According to the embodiment of the application, the data uploading method can be realized no matter the initial data of the data providing mechanism needs to be processed independently and uploaded to the target mechanism or the initial data of the data providing mechanism needs to be processed together with the initial data of other data providing mechanisms and uploaded to the target mechanism, so that the data uploading efficiency is improved, and the cost is reduced.

Description

Data uploading method, device, equipment and computer storage medium

Technical Field

The present application belongs to the field of data processing technologies, and in particular, to a data uploading method, apparatus, device, and computer storage medium.

Background

In order to comply with regulatory requirements, financial institutions need to process and upload user's anomalous transaction data to relevant institutions.

In general, different financial institutions have different development modes, some financial institutions have a plurality of subsidiaries, some financial institutions have a plurality of subordinate institutions, and some financial institutions have a plurality of subsidiaries. The subsidiary companies usually need to process and upload the held abnormal transaction data, and the subordinate companies usually need to integrate the held abnormal transaction data with the abnormal transaction data held by other subordinate companies and then process and upload the integrated abnormal transaction data.

Therefore, a financial institution owning multiple sub-companies needs to deploy the upload system at each sub-company, and then owns multiple sub-companies and financial institutions owning multiple subordinate companies, that is, needs to deploy the upload system at each sub-company, and also needs to deploy a joint upload system to upload data of multiple subordinate companies. Therefore, when the financial institution uploads data, a plurality of uploading systems are required to be deployed, so that the cost is high and the efficiency is low.

Disclosure of Invention

The embodiment of the application provides a data uploading method, a data uploading device and a computer storage medium, which can meet the requirements that initial data of a data providing mechanism needs to be processed independently and uploaded to a target mechanism, and can also meet the requirements that the initial data of other data providing mechanisms are processed together and uploaded to the target mechanism, so that the data uploading efficiency is improved, and the cost is reduced.

In a first aspect, an embodiment of the present application provides a data uploading method, where the method includes:

acquiring abnormal transaction data and a business mechanism identifier corresponding to a business mechanism;

determining a tenant label corresponding to the abnormal transaction data according to a preset tenant mechanism mapping table and a service mechanism identifier to obtain the abnormal transaction data marked with the tenant label;

processing the abnormal transaction data marked with the tenant label aiming at each tenant label, and determining the data to be uploaded corresponding to the tenant label;

and uploading the data to be uploaded corresponding to the tenant label to a target mechanism.

Optionally, the uploading the data to be uploaded corresponding to the tenant label to a target entity specifically includes:

auditing data to be uploaded corresponding to the tenant label;

and when the data to be uploaded pass the audit, uploading the data to be uploaded to a target organization.

Optionally, when it is determined that the data to be uploaded passes the audit, before the data to be uploaded is uploaded to the target organization, the method further includes:

when the data to be uploaded is determined not to pass the auditing, determining a tenant label corresponding to the data to be uploaded;

determining a service mechanism corresponding to the tenant label according to the tenant mechanism mapping table and the tenant label;

and returning the abnormal transaction data and the service organization identification corresponding to the acquired service organization for the service organization until the data to be uploaded corresponding to the tenant label passes the audit.

Optionally, the auditing the data to be uploaded corresponding to the tenant label specifically includes:

determining a verification user corresponding to the data to be uploaded according to a preset verification user mechanism mapping table and the tenant mechanism mapping table;

when a first operation instruction executed after the data to be uploaded is audited by the auditing user is received, responding to the first operation instruction, and determining that the data to be uploaded passes the audit;

and when a second operation instruction executed after the data to be uploaded is audited by the auditing user is received, responding to the second operation instruction, and determining that the data to be uploaded does not pass the audit.

Optionally, determining the audit user corresponding to the data to be uploaded according to a preset audit user mechanism mapping table and the tenant mechanism mapping table, specifically including:

determining a first corresponding relation between the tenant and the service mechanism according to the tenant mechanism mapping table;

determining a business mechanism corresponding to the data to be uploaded according to the tenant label corresponding to the data to be uploaded and the first corresponding relation;

determining a second corresponding relation between the audit user and the service organization according to a preset audit user organization mapping table;

and determining an auditing user corresponding to the data to be uploaded according to the second corresponding relation and the business mechanism corresponding to the data to be uploaded.

Optionally, determining an audit user corresponding to the data to be uploaded according to a preset audit user mechanism mapping table and the tenant mechanism mapping table specifically includes:

determining a business mechanism corresponding to at least one piece of to-be-audited data included in the to-be-uploaded data according to the tenant label corresponding to the to-be-uploaded data and the first corresponding relation;

and determining an auditing user corresponding to at least one piece of to-be-audited data included in the to-be-uploaded data according to the business mechanism corresponding to the to-be-audited data and the second corresponding relation.

Optionally, before determining the tenant label corresponding to the abnormal transaction data according to a preset tenant mechanism mapping table and the service mechanism identifier, the method further includes:

creating a tenant in response to an operation of a user;

and responding to the operation of the user, and determining the corresponding relation between the tenant and the business mechanism, wherein at least one business mechanism corresponding to the tenant needs to perform joint processing on abnormal transaction data and joint uploading.

In a second aspect, an embodiment of the present application provides a data uploading apparatus, where the apparatus includes:

the acquisition module is used for acquiring abnormal transaction data and a business mechanism identifier corresponding to a business mechanism;

the determining module is used for determining a tenant label corresponding to the abnormal transaction data according to a preset tenant mechanism mapping table and a service mechanism identifier to obtain the abnormal transaction data marked with the tenant label;

the processing module is used for processing the abnormal transaction data marked with the tenant label aiming at each tenant label and determining the data to be uploaded corresponding to the tenant label;

and the uploading module is used for uploading the data to be uploaded corresponding to the tenant label to a target mechanism.

In a third aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory storing computer program instructions;

a processor, when executing the computer program instructions, implements a data upload method as described in any of the first aspects.

In a fourth aspect, an embodiment of the present application provides a computer storage medium, where the computer storage medium has stored thereon computer program instructions, and when executed by a processor, the computer program instructions implement the data uploading method according to any one of the first aspect.

In a fifth aspect, the present application provides a computer program product, where when instructions in the computer program product are executed by a processor of an electronic device, the electronic device is capable of executing the data uploading method of any one of the first aspects.

The data uploading method, the data uploading device, the data uploading equipment and the computer storage medium of the embodiment of the application acquire abnormal transaction data and business organization identification corresponding to a business organization, determine a tenant label corresponding to the abnormal transaction data based on the abnormal transaction data, acquire the abnormal transaction data marked with the tenant label, process the abnormal transaction data marked with the tenant label for each tenant label, and determine data to be uploaded corresponding to the tenant label, so that initial data of a data providing organization can be uploaded to a target organization after being processed. In the process, no matter the initial data of the data providing mechanism needs to be processed independently and uploaded to the target mechanism, or the initial data of the data providing mechanism needs to be processed together with the initial data of other data providing mechanisms and uploaded to the target mechanism, the data uploading method provided by the embodiment of the application can be realized, so that the data uploading efficiency is improved, and the cost is reduced.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly described below, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic flowchart of a data uploading method according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a tenant creating method according to an embodiment of the present application;

fig. 3 is a schematic flowchart of another data uploading method provided in an embodiment of the present application;

FIG. 4 is a flowchart illustrating an embodiment of S304;

fig. 5 is a flowchart of a specific implementation of S3041;

FIG. 6 is a flowchart illustrating another specific implementation of S3041;

fig. 7 is a schematic structural diagram of a data uploading system according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a data uploading device provided in an embodiment of the present application;

fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

Features and exemplary embodiments of various aspects of the present application will be described in detail below, and in order to make objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are intended to be illustrative only and are not intended to be limiting. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present application by illustrating examples thereof.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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, an element defined by the phrase "comprising … …" does not exclude the presence of another like element in a process, method, article, or apparatus that comprises the element.

In order to comply with regulatory requirements, financial institutions need to process and upload user's anomalous transaction data to relevant institutions. In general, different financial institutions have different development modes, some financial institutions have a plurality of subsidiaries, some financial institutions have a plurality of subordinate institutions, and some financial institutions have a plurality of subsidiaries.

In the process of processing and uploading data to the related institutions, the subsidiary companies usually need to process and upload the held abnormal transaction data, and the subordinate institutions usually need to integrate the held abnormal transaction data with the abnormal transaction data held by other subordinate institutions, and then process and upload the integrated abnormal transaction data. However, the existing uploading system or processing mechanism of the financial institution is only suitable for a scenario of independent delivery and service processing of multiple subsidiaries or subordinate organizations, and is not suitable for a scenario of combined delivery of multiple subsidiaries or a mixed mode of independent delivery and combined delivery, so that the financial institution often needs to deploy multiple uploading systems when uploading data, which is high in cost and low in efficiency.

In order to solve the prior art problems, embodiments of the present application provide a data uploading method, apparatus, device, and computer storage medium. First, a data uploading method provided by the embodiment of the present application is described below.

Fig. 1 shows a flowchart of a data uploading method provided in an embodiment of the present application. As shown in fig. 1, the method specifically includes the following steps:

s101, acquiring abnormal transaction data and a business mechanism identifier corresponding to a business mechanism;

s102, according to a preset tenant mechanism mapping table and a service mechanism identifier, determining a tenant label corresponding to abnormal transaction data, and obtaining the abnormal transaction data marked with the tenant label;

s103, processing the abnormal transaction data marked with the tenant label aiming at each tenant label, and determining the data to be uploaded corresponding to the tenant label;

and S104, uploading the data to be uploaded corresponding to the tenant label to a target mechanism.

Therefore, according to the data uploading method provided by the embodiment of the application, the initial data of the data providing mechanism can be processed and uploaded to the target mechanism. The method can be realized no matter the initial data of the data providing mechanism needs to be processed independently and uploaded to the target mechanism, or the initial data of the data providing mechanism needs to be processed together with the initial data of other data providing mechanisms and uploaded to the target mechanism, so that the efficiency is improved, and the cost is reduced.

In some embodiments, in S101, the abnormal transaction data corresponding to each business organization is accessed through the data aggregation tool, and the business organization identifier is obtained.

In some embodiments, as shown in fig. 2, before S102, the method further comprises the steps of:

s201, responding to the operation of a user, and creating a tenant;

s202, responding to the operation of a user, and determining the corresponding relation between the tenant and the business mechanisms, wherein at least one business mechanism corresponding to the tenant needs to perform combined processing on abnormal transaction data and upload the abnormal transaction data jointly.

As an example, there may be multiple subsidiaries or subordinate companies for different financial institutions, or both. According to the business requirement and the reporting mode, a plurality of subsidiaries or subordinate organizations are divided into a plurality of groups, and the subsidiaries or subordinate organizations of each group adopt the same business processing mode and carry out combined reporting. And at least one business mechanism is used for performing joint processing on abnormal transaction data and jointly uploading the abnormal transaction data.

Therefore, the tenant corresponding to the business mechanism which performs combined processing and combined uploading on the abnormal data is created, so that the tenant label is marked on the abnormal transaction data based on the tenant mechanism mapping table and the business mechanism identification.

In some embodiments, in S102, the tenant authority mapping table may be generated according to the correspondence between the tenant and the business authority, and the source data is marked according to the tenant authority mapping table, and the business authority identifier is combined, so as to determine the tenant label corresponding to the abnormal transaction data. Therefore, data processing and processing of abnormal transaction data marked with the tenant label are facilitated.

In some embodiments, in S103, each tenant label is different, that is, the user authority range of each tenant under the user configuration of the tenant is also different. The user permission range is mainly that a user can configure the mapping relation between a mechanism used by the user for processing data and a mechanism used by the user for processing the data, so that the data to be uploaded corresponding to the tenant label is determined. Each tenant can configure the user processing authority range of the tenant in a differentiated mode, so that different data to be uploaded corresponding to the tenant label can be determined for each tenant label.

In some embodiments, in S104, the electronic device may upload data to be uploaded to the target institution.

Therefore, based on the tenant organization mapping table, the service identification and the tenant label, the acquired abnormal transaction data corresponding to the service organization is processed, the data to be uploaded is determined and is uploaded to the target organization, and therefore the data uploading task is efficiently and accurately completed.

Fig. 3 illustrates another data uploading method provided in the embodiment of the present application, and as shown in fig. 3, the method may specifically include the following steps:

s301, acquiring abnormal transaction data and a business mechanism identifier corresponding to a business mechanism;

s302, according to a preset tenant mechanism mapping table and a service mechanism identifier, determining a tenant label corresponding to abnormal transaction data to obtain the abnormal transaction data marked with the tenant label;

s303, processing the abnormal transaction data marked with the tenant label aiming at each tenant label, and determining the data to be uploaded corresponding to the tenant label;

s304, auditing data to be uploaded corresponding to the tenant label;

s305, judging whether the data to be uploaded pass the audit;

s306, uploading the data to be uploaded to a target mechanism when the data to be uploaded pass the audit;

s307, when the data to be uploaded is determined not to pass the verification, determining a tenant label corresponding to the data to be uploaded;

s308, according to the tenant organization mapping table and the tenant label, determining a service organization corresponding to the tenant label, and returning to obtain abnormal transaction data and a service organization identifier corresponding to the service organization until the data to be uploaded corresponding to the tenant label passes the verification.

Therefore, the data to be uploaded corresponding to the tenant label is audited, the data to be uploaded is uploaded to the target organization under the condition that the audit is passed, if the data to be uploaded does not pass the audit, the tenant label corresponding to the data to be uploaded and the business organization corresponding to the tenant label are determined again, and the abnormal transaction data and the business organization identification corresponding to the business organization are returned to be obtained until the data to be uploaded corresponding to the tenant label passes the audit. Based on the method, the corresponding processing mode is adopted by judging whether the data to be uploaded passes the audit, so that the data uploading efficiency is improved.

Since S301 to S303 are the same as those described in S101 to S103, they are not described again.

In some embodiments, the data to be uploaded corresponding to the tenant label can be uploaded to the target institution only when the data to be uploaded passes the audit. As shown in fig. 4, the step S304 may include the following steps:

s3041, determining a verification user corresponding to the data to be uploaded according to a preset verification user mechanism mapping table and a tenant mechanism mapping table;

s3042, when a first operation instruction executed after the data to be uploaded is audited by the auditing user is received, responding to the first operation instruction, and determining that the data to be uploaded passes the audit;

s3043, when a second operation instruction executed after the audit user audits the data to be uploaded is received, determining that the data to be uploaded does not pass the audit in response to the second operation instruction.

As an example, determining whether the data to be uploaded passes the audit, first determining an audit user corresponding to the data to be uploaded according to a preset audit user mechanism mapping table and a tenant mechanism mapping table, so as to determine whether the data to be uploaded passes the audit when receiving an operation instruction of the audit user.

In some embodiments, as shown in fig. 5, the above S3041 may include the following steps:

s501, determining a first corresponding relation between a tenant and a service mechanism according to a tenant mechanism mapping table;

s502, determining a business mechanism corresponding to the data to be uploaded according to the tenant label corresponding to the data to be uploaded and the first corresponding relation;

s503, determining a second corresponding relation between the audit user and the service organization according to a preset audit user organization mapping table;

s504, according to the second corresponding relation and the business mechanism corresponding to the data to be uploaded, the auditing user corresponding to the data to be uploaded is determined.

As an example, the auditing user corresponding to the data to be uploaded may be determined through a tenant organization mapping table, a first corresponding relationship between a tenant and a service organization, a preset auditing user organization mapping table, and a second corresponding relationship between an auditing user and a service organization.

Illustratively, a first corresponding relation between a tenant and a service mechanism is determined according to a tenant mechanism mapping table, a service mechanism corresponding to data to be uploaded is determined by combining a tenant label, then a second corresponding relation between an audit user and the service mechanism is determined through a preset audit user mechanism mapping table, and an audit user corresponding to the data to be uploaded is determined according to the second corresponding relation and the service mechanism corresponding to the data to be uploaded.

In some embodiments, to determine an audit user corresponding to data to be uploaded, as shown in fig. 6, the above S3041 may further include the following steps:

s601, determining a first corresponding relation between a tenant and a service mechanism according to a tenant mechanism mapping table;

s602, determining a business mechanism corresponding to at least one piece of to-be-audited data included in the to-be-uploaded data according to the tenant label corresponding to the to-be-uploaded data and the first corresponding relation;

s603, determining a second corresponding relation between the audit user and the service organization according to a preset audit user organization mapping table;

s604, according to the business mechanism corresponding to the data to be audited and the second corresponding relation, the auditing user corresponding to at least one piece of data to be audited included in the data to be uploaded is determined.

As an example, the business mechanism corresponding to the data to be uploaded may also be a business mechanism corresponding to at least one piece of to-be-audited data included in the data to be uploaded, and correspondingly, the auditing user corresponding to the data to be uploaded may also be an auditing user corresponding to at least one piece of to-be-audited data included in the data to be uploaded.

In some embodiments, in S307, if the data to be uploaded does not pass the audit, the tenant label corresponding to the data to be uploaded and the service mechanism corresponding to the tenant label are re-determined, and the abnormal data and the service mechanism identifier corresponding to the re-determined service mechanism are obtained until the data to be uploaded corresponding to the tenant label passes the audit.

Therefore, when the auditing user corresponding to the data to be uploaded is determined, the data to be uploaded is audited through the auditing user, and when the data to be uploaded is determined to pass the auditing, the data to be uploaded is uploaded to the target mechanism. Based on the method, the data of the business mechanism can be processed independently and uploaded to the target mechanism, or processed together with the data of other business mechanisms and uploaded to the target mechanism, the method can be realized, repeated uploading of the data is avoided, the data uploading efficiency is improved, and the cost is reduced.

Fig. 7 is a schematic structural diagram of a data uploading system according to an embodiment of the present application, and as shown in fig. 7, the data uploading processing system includes a data acquiring and processing device, a data uploading and submitting device, a business organization processing device, and an audit user processing device. In combination with the data uploading method and the data uploading processing system provided by the embodiment of the application, the data acquiring and processing device acquires abnormal transaction data and a service organization identifier corresponding to a service organization, processes the abnormal transaction data, and determines data to be uploaded, the service organization processing device determines a tenant organization mapping table based on the corresponding relationship between multiple organizations and multiple tenants, the auditing user processing device determines an auditing user based on the tenant organization mapping table and the auditing user organization mapping table, and the data uploading and reporting device generates a message to be reported for the data to be uploaded and uploads the message to a target organization under the condition that the data to be uploaded is determined to pass auditing.

Therefore, based on the data uploading method and the data uploading processing system of the embodiment of the application, the requirement of independent data reporting of multiple mechanisms and the requirement of joint data reporting can be met, and a mixed scene of the two situations is supported, namely, the differentiated configuration of tenants is supported, so that the expandability and the flexibility of the system are improved. In addition, in the data uploading process, the data to be uploaded is audited, the problems of repeated data uploading and uploading failure are solved, and the uploading system does not need to be repeatedly established by multiple mechanisms and multiple tenants, so that the uploading efficiency is improved, and the cost is saved.

It should be noted that the application scenario described in the embodiment of the present application is for more clearly explaining the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided in the embodiment of the present application. As can be known to those skilled in the art, with the advent of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

Based on the same inventive concept, the present application provides a data uploading apparatus, which is specifically described in detail with reference to fig. 8.

Fig. 8 illustrates a data uploading apparatus provided by an embodiment of the present application, and as shown in fig. 8, the data uploading apparatus 800 may include:

an obtaining module 801, configured to obtain abnormal transaction data and a service organization identifier corresponding to a service organization;

the determining module 802 is configured to determine, according to a preset tenant institution mapping table and a service institution identifier, a tenant label corresponding to the abnormal transaction data, so as to obtain the abnormal transaction data marked with the tenant label;

the processing module 803 is configured to, for each tenant label, process the abnormal transaction data marked with the tenant label, and determine data to be uploaded corresponding to the tenant label;

and an uploading module 804, configured to upload the data to be uploaded corresponding to the tenant label to a target organization.

Therefore, according to the data uploading device provided by the embodiment of the application, the initial data of the data providing mechanism can be processed and uploaded to the target mechanism. The method can be realized no matter the initial data of the data providing mechanism needs to be processed independently and uploaded to the target mechanism, or the initial data of the data providing mechanism needs to be processed together with the initial data of other data providing mechanisms and uploaded to the target mechanism, so that the efficiency is improved, and the cost is reduced.

In some embodiments, in order to create a tenant and determine a corresponding relationship between the tenant and a business entity, the determining module 802 may include the following sub-modules:

the creating submodule is used for responding to the operation of a user and creating the tenant;

and the determining submodule is used for responding to the operation of a user and determining the corresponding relation between the tenant and the business mechanism, wherein at least one business mechanism corresponding to the tenant needs to perform combined processing on the abnormal transaction data and upload the abnormal transaction data in a combined mode.

In some embodiments, in order to determine whether the data to be uploaded passes the audit, the data uploading apparatus 800 may further include the following sub-modules:

the auditing submodule is used for auditing the data to be uploaded corresponding to the tenant label;

the judging submodule is used for judging whether the data to be uploaded passes the audit;

the uploading sub-module is used for uploading the data to be uploaded to a target mechanism when the data to be uploaded is confirmed to pass the audit;

the first determining submodule is used for determining a tenant label corresponding to the data to be uploaded when the data to be uploaded is determined to be not approved;

and the second determining submodule is used for determining the service mechanism corresponding to the tenant label according to the tenant mechanism mapping table and the tenant label, and returning and acquiring the abnormal transaction data and the service mechanism identification corresponding to the service mechanism until the data to be uploaded corresponding to the tenant label passes the audit.

In some embodiments, to determine whether the data to be uploaded passes the audit, the audit sub-module may include the following units:

the first determining unit is used for determining an audit user corresponding to the data to be uploaded according to a preset audit user mechanism mapping table and a tenant mechanism mapping table;

the second determining unit is used for responding to the first operating instruction and determining that the data to be uploaded passes the audit when the first operating instruction executed after the data to be uploaded is audited by the audit user is received;

and the third determining unit is used for responding to the second operating instruction and determining that the data to be uploaded does not pass the audit when the second operating instruction executed after the audit user audits the data to be uploaded is received.

In some embodiments, in order to determine an audit user corresponding to data to be uploaded, the first determining unit may include the following sub-units:

the first determining subunit is used for determining a first corresponding relation between the tenant and the service institution according to the tenant institution mapping table;

the second determining subunit is used for determining the business mechanism corresponding to the data to be uploaded according to the tenant label corresponding to the data to be uploaded and the first corresponding relation;

a third determining subunit, configured to determine, according to a preset mapping table of the audit user mechanism, a second correspondence between the audit user and the service mechanism;

the fourth determining subunit is configured to determine, according to the second correspondence and the service organization corresponding to the data to be uploaded, an audit user corresponding to the data to be uploaded;

the fifth determining subunit is configured to determine, according to the tenant label corresponding to the data to be uploaded and the first correspondence, a business mechanism corresponding to at least one piece of to-be-audited data included in the data to be uploaded;

and the sixth determining subunit is configured to determine, according to the business organization corresponding to the data to be audited and the second corresponding relationship, an auditing user corresponding to at least one piece of data to be audited included in the data to be uploaded.

Fig. 9 shows a hardware structure diagram of an electronic device according to an embodiment of the present application.

The electronic device 900 may include a processor 901 and a memory 902 that stores computer program instructions.

Specifically, the processor 901 may include a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or may be configured to implement one or more Integrated circuits of the embodiments of the present Application.

Memory 902 may include a mass storage for data or instructions. By way of example, and not limitation, memory 902 may include a Hard Disk Drive (HDD), floppy Disk Drive, flash memory, optical Disk, magneto-optical Disk, tape, or Universal Serial Bus (USB) Drive or a combination of two or more of these. Memory 902 may include removable or non-removable (or fixed) media, where appropriate. The memory 902 may be internal or external to the integrated gateway disaster recovery device, where appropriate. In a particular embodiment, the memory 902 is non-volatile solid-state memory.

The memory 902 may include Read Only Memory (ROM), random access memory (RA M), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical/tangible memory storage devices. Thus, in general, the memory 902 comprises one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the data upload method according to the first aspect of the present application.

The processor 901 reads and executes the computer program instructions stored in the memory 902 to implement any one of the data uploading methods in the above embodiments.

In one example, electronic device 900 can also include a communication interface 903 and a bus 904. As shown in fig. 9, the processor 901, the memory 902, and the communication interface 903 are connected via a bus 904 to complete communication with each other.

The communication interface 903 is mainly used for implementing communication between modules, apparatuses, units and/or devices in this embodiment of the application.

The bus 904 comprises hardware, software, or both that couple the components of the electronic device 900 to one another. By way of example, and not limitation, the bus 904 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an infiniband interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a video electronics standards association local (VLB) bus, or other suitable bus, or a combination of two or more of these. Bus 904 may include one or more buses, where appropriate. Although specific buses are described and shown in the embodiments of the application, any suitable buses or interconnects are contemplated by the application.

The electronic device 900 may implement the data uploading method and apparatus described in conjunction with fig. 1 and 8.

In addition, in combination with the data uploading method in the foregoing embodiments, the embodiments of the present application may provide a computer storage medium to implement. The computer storage medium having computer program instructions stored thereon; the computer program instructions, when executed by a processor, implement any of the data upload methods in the above embodiments.

It is to be understood that the present application is not limited to the particular arrangements and instrumentalities described above and shown in the attached drawings. A detailed description of known methods is omitted herein for the sake of brevity. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications, and additions or change the order between the steps after comprehending the spirit of the present application.

The functional blocks shown in the above-described structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, plug-in, function card, or the like. When implemented in software, the elements of the present application are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine-readable medium or transmitted by a data signal carried in a carrier wave over a transmission medium or a communication link. A "machine-readable medium" may include any medium that can store or transfer information. Examples of a machine-readable medium include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio Frequency (RF) links, and so forth. The code segments may be downloaded via computer networks such as the internet, intranet, etc.

It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, may be performed in an order different from the order in the embodiments, or may be performed simultaneously.

Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus, and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations 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, 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, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware for performing the specified functions or acts, or combinations of special purpose hardware and computer instructions.

As described above, only the specific embodiments of the present application are provided, and it can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the module and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. It should be understood that the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present application, and these modifications or substitutions should be covered within the scope of the present application.

Claims

1. A data uploading method, comprising:

determining a tenant label corresponding to the abnormal transaction data according to a preset tenant mechanism mapping table and the service mechanism identification to obtain the abnormal transaction data marked with the tenant label;

2. The method according to claim 1, wherein the uploading the data to be uploaded corresponding to the tenant label to a target institution specifically comprises:

auditing data to be uploaded corresponding to the tenant label;

and when the data to be uploaded passes the audit, uploading the data to be uploaded to a target mechanism.

3. The method of claim 2, wherein when it is determined that the data to be uploaded passes the audit, before uploading the data to be uploaded to a target institution, the method further comprises:

when the data to be uploaded is determined to be not approved, determining a tenant label corresponding to the data to be uploaded;

determining a business mechanism corresponding to the tenant label according to the tenant mechanism mapping table and the tenant label;

and returning the abnormal transaction data and the service organization identification corresponding to the obtained service organization aiming at the service organization until the data to be uploaded corresponding to the tenant label passes the verification.

4. The method according to claim 2, wherein auditing the data to be uploaded corresponding to the tenant label specifically includes:

5. The method according to claim 4, wherein determining the audit user corresponding to the data to be uploaded according to a preset audit user authority mapping table and the tenant authority mapping table specifically includes:

6. The method according to claim 4, wherein determining the audit user corresponding to the data to be uploaded according to a preset audit user authority mapping table and the tenant authority mapping table specifically includes:

7. The method according to claim 1, wherein before determining the tenant label corresponding to the abnormal transaction data according to a preset tenant institution mapping table and the service institution identification, the method further comprises:

creating a tenant in response to an operation of a user;

8. A data uploading apparatus, comprising:

the acquisition module is used for acquiring abnormal transaction data and business mechanism identification corresponding to the business mechanism;

the determining module is used for determining a tenant label corresponding to the abnormal transaction data according to a preset tenant mechanism mapping table and the service mechanism identifier to obtain the abnormal transaction data marked with the tenant label;

9. An electronic device, characterized in that the device comprises: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements a data upload method as claimed in any of claims 1-7.

10. A computer-readable storage medium, having computer program instructions stored thereon, which, when executed by a processor, implement the data upload method of any of claims 1-7.

11. A computer program product, wherein instructions in the computer program product, when executed by a processor of an electronic device, enable the electronic device to perform the data upload method of any of claims 1-7.