CN113205302A - Data interaction method, device, equipment and storage medium - Google Patents
Data interaction method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113205302A CN113205302A CN202110363455.XA CN202110363455A CN113205302A CN 113205302 A CN113205302 A CN 113205302A CN 202110363455 A CN202110363455 A CN 202110363455A CN 113205302 A CN113205302 A CN 113205302A
- Authority
- CN
- China
- Prior art keywords
- financing
- request type
- data interaction
- bill
- state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000003993 interaction Effects 0.000 title claims abstract description 69
- 238000000034 method Methods 0.000 title claims abstract description 57
- 238000007726 management method Methods 0.000 claims description 71
- 238000012550 audit Methods 0.000 claims description 8
- 238000004891 communication Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 8
- 238000012545 processing Methods 0.000 claims description 4
- 238000012552 review Methods 0.000 claims description 3
- 230000006870 function Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/06—Asset management; Financial planning or analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- General Physics & Mathematics (AREA)
- Marketing (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Operations Research (AREA)
- General Business, Economics & Management (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Game Theory and Decision Science (AREA)
- Technology Law (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application relates to a data interaction method, a data interaction device, data interaction equipment and a storage medium, and relates to the field of finance. The data interaction method comprises the following steps: acquiring a financing list operation request sent by an enterprise management system, wherein the financing list operation request carries a user identifier and a request type identifier; acquiring a financing list operation authority corresponding to a user identifier, wherein the financing list operation authority comprises an interface address and a request type parameter corresponding to the interface address, and the request type parameter comprises a request type identifier and a state corresponding to the request type identifier; and if the state corresponding to the request type identifier is enabled, determining that the user identifier has the authority to access the interface address, and executing the data interaction operation with the enterprise management system corresponding to the request type identifier. The method and the device are used for solving the problem of multiple distribution of the interface access authority.
Description
Technical Field
The present application relates to the field of finance, and in particular, to a data interaction method, apparatus, device, and storage medium.
Background
The enterprise management system is a system for enterprise internal staff needing financing to perform operations such as creating financing lists, checking financing lists and the like. The remittance platform is a platform which can be accessed by various roles in financing such as enterprises, fund parties and banks needing financing and can perform information interaction. The enterprise management system needs to access the convergence platform through an interface of the convergence platform.
The convergence platform is provided with a plurality of interfaces, each interface corresponds to a function, such as pushing a financing sheet, obtaining the financing sheet and the like, if the functions are added, the interfaces are required to be added, and the authority for accessing the interfaces is distributed to required users.
Disclosure of Invention
The application provides a data interaction method, a data interaction device, data interaction equipment and a storage medium, which are used for solving the problem of multiple distribution of interface access authority.
In a first aspect, an embodiment of the present application provides a data interaction method, which is applied to a convergence platform, and includes:
acquiring a financing list operation request sent by an enterprise management system, wherein the financing list operation request carries a user identifier and a request type identifier;
acquiring a financing list operation authority corresponding to the user identifier, wherein the financing list operation authority comprises an interface address and a request type parameter corresponding to the interface address, and the request type parameter comprises a request type identifier and a state corresponding to the request type identifier;
and if the state corresponding to the request type identifier is enabled, determining that the user identifier has the right to access the interface address, and executing the data interaction operation between the user identifier and the enterprise management system corresponding to the request type identifier.
Optionally, before performing the operation of performing data interaction with the enterprise management system corresponding to the request type identifier, the method further includes:
acquiring a key corresponding to the user identifier, and sending the key to the enterprise management system;
obtaining a token sent by the enterprise management system;
obtaining the obtaining time of the token;
acquiring a preset moment corresponding to the token;
and determining that the acquisition time is not greater than the preset time.
Optionally, the request type corresponding to the request type identifier includes one of acquiring a financing order and pushing the financing order.
Optionally, when the request type corresponding to the request type identifier is the pushed financing bill, the executing of the operation of performing data interaction with the enterprise management system corresponding to the request type identifier includes:
acquiring encrypted data sent by the enterprise management system;
decrypting the encrypted data by using the secret key to obtain a first financing bill and an invoice corresponding to the first financing bill, wherein the pushing state of the first financing bill is not pushing, and the auditing state of the first financing bill is audited;
inquiring a second financing list corresponding to the identifier of the first financing list from a preset database, wherein the invalidation state of the second financing list is that the second financing list is not invalidated;
comparing the auditing time of the first financing bill with the auditing time of the second financing bill;
if the audit time of the first financing sheet is greater than the audit time of the second financing sheet, changing the invalidation state of the second financing sheet into invalidation, storing the first financing sheet to the preset database, and changing the pushing state of the first financing sheet into pushing;
and sending the changed push state of the first financing bill to the enterprise management system.
Optionally, when the request type corresponding to the request type identifier is the financing order acquisition, the performing of the operation of data interaction with the enterprise management system corresponding to the request type identifier includes:
acquiring a third financing bill, wherein the operation state of a fund side of the third financing bill is operated, and the updating state of the third financing bill is not updated;
obtaining fund party operation information in the third financing bill, wherein the fund party operation information comprises at least one of pre-review information, payment information and ticket refunding information;
sending the fund side operation information in the third financing bill to the enterprise management system;
and acquiring the updated state of the third financing order sent by the enterprise management system after the third financing order is changed, and changing the updated state of the third financing order into the updated state of the third financing order after the third financing order is changed.
In a second aspect, an embodiment of the present application provides a data interaction method, which is applied to an enterprise management system, and includes:
sending a financing sheet operation request to a convergence platform, wherein the financing sheet operation request carries a user identifier and a request type identifier;
acquiring a secret key sent by the convergence platform;
obtaining a token according to the user identification and the secret key;
and sending the token to the convergence platform.
Optionally, the request type corresponding to the request type identifier includes one of acquiring a financing order and pushing the financing order.
Optionally, when the request type corresponding to the request type identifier is the push financing sheet, after the token is sent to the convergence platform, the method further includes:
acquiring a first financing bill and an invoice corresponding to the first financing bill, wherein the pushing state of the first financing bill is not pushed, and the auditing state of the first financing bill is audited;
encrypting the first financing bill and the invoice corresponding to the first financing bill by using the secret key to obtain encrypted data;
sending the encrypted data to the convergence platform;
and acquiring the changed pushing state of the first financing order sent by the convergence platform, and changing the pushing state of the first financing order into the changed pushing state of the first financing order.
Optionally, when the request type corresponding to the request type identifier is the financing order acquisition, after the token is sent to the convergence platform, the method further includes:
obtaining fund party operation information in a third financing bill sent by the convergence platform;
updating the operation information of the fund party to the third financing bill, and changing the updating state of the third financing bill to be updated;
and sending the updated state after the third financing bill is changed to the convergence platform.
In a third aspect, an embodiment of the present application provides a data interaction device configured on a convergence platform, including:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a financing list operation request sent by an enterprise management system, and the financing list operation request carries a user identifier and a request type identifier;
a second obtaining module, configured to obtain a financing list operation permission corresponding to the user identifier, where the financing list operation permission includes an interface address and a request type parameter corresponding to the interface address, and the request type parameter includes the request type identifier and a state corresponding to the request type identifier;
and the processing module is used for determining that the user identifier has the permission to access the interface address and executing the data interaction operation between the user identifier and the enterprise management system corresponding to the request type identifier if the state corresponding to the request type identifier is enabled.
In a fourth aspect, an embodiment of the present application provides a data interaction device configured in an enterprise management system, including:
the system comprises a first sending module, a second sending module and a third sending module, wherein the first sending module is used for sending a financing list operation request to a convergence platform, and the financing list operation request carries a user identifier and a request type identifier;
the third acquisition module is used for acquiring the key sent by the convergence platform;
a fourth obtaining module, configured to obtain a token according to the user identifier and the secret key;
and the second sending module is used for sending the token to the convergence platform.
In a fifth aspect, an embodiment of the present application provides an electronic device, including: the system comprises a processor, a memory and a communication bus, wherein the processor and the memory are communicated with each other through the communication bus;
the memory for storing a computer program;
the processor is configured to execute the program stored in the memory to implement the data interaction method according to the first aspect, or to implement the data interaction method according to the second aspect.
In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the data interaction method according to the first aspect is implemented, or the data interaction method according to the second aspect is implemented.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages: according to the method provided by the embodiment of the application, the convergence platform acquires the financing list operation authority corresponding to the user identifier, wherein the financing list operation authority comprises an interface address and a request type parameter corresponding to the interface address, the request type parameter comprises a request type identifier and a state corresponding to the request type identifier, if the state corresponding to the request type identifier is enabled, it is determined that the user identifier has the authority to access the interface address, and the operation of data interaction with the enterprise management system corresponding to the request type identifier is executed. In the prior art, a convergence platform has a plurality of interfaces, each interface corresponds to a function, if a function is added, an interface needs to be added, and a right to access the interface is allocated to a user in need. In the method provided by the embodiment of the application, the financing list operation authority comprises an interface address and a request type parameter corresponding to the interface address, the request type parameter comprises a request type identifier and a state corresponding to the request type identifier, the request type parameter corresponding to the interface address is added into the financing list operation authority, only once financing list operation authority needs to be allocated, subsequently, multiple functions corresponding to one interface can be realized by modifying the request type parameter, when the functions are added, no interface needs to be added, the authority of accessing the interface is allocated to a needed user, and the problem of multiple allocation of interface access authority is solved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
FIG. 1 is a block diagram of a data interaction system according to an embodiment of the present disclosure;
FIG. 2 is a schematic flow chart illustrating a method for data interaction applied to a convergence platform in an embodiment of the present application;
FIG. 3 is a flowchart illustrating a method for data interaction applied to an enterprise management system according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating a method for data interaction between the convergence platform and the enterprise management system when the request type is pushing a financing order according to an embodiment of the present application;
FIG. 5 is a flowchart illustrating a method for data interaction between the convergence platform and the enterprise management system when the request type is to obtain a financing order according to an embodiment of the present application;
FIG. 6 is a schematic structural diagram of a data interaction device configured on a convergence platform according to an embodiment of the present disclosure;
FIG. 7 is a block diagram of a data interaction device configured in an enterprise management system according to an embodiment of the present disclosure;
fig. 8 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the embodiment of the present application, as shown in fig. 1, the data interaction system includes a convergence platform 101 and an enterprise management system 102. The data interaction method provided by the embodiment of the application is mainly a process of realizing data interaction by matching the convergence platform and the enterprise management system. The following embodiments describe data interaction methods from two different perspectives, a convergence platform and an enterprise management system.
In the embodiment of the present application, as shown in fig. 2, a flow of a method applied to data interaction of a convergence platform mainly includes:
The user identifier may be an account of the enterprise management system on the convergence platform, for example: the first letter of the name of the business.
In one embodiment, the request type corresponding to the request type identifier includes one of obtaining a financing order and pushing a financing order.
It should be noted that the parameters included in the request type corresponding to the request type identifier listed herein are only examples, and do not limit the scope of the present application, and other parameters may also be included in the request type corresponding to the request type identifier as needed, for example: and updating the financing bill.
The interface address refers to a URL (Uniform Resource Locator) corresponding to the interface.
The state corresponding to the request type identification comprises enabling and disabling.
For example: the user identifier wykj carried in the financing order operation request is hqrzd, the request type identifier is hqrzd, the request type corresponding to the request type identifier is to acquire the financing order, the financing order operation authority corresponding to the user identifier wykj includes request type parameters corresponding to the interface address 234.24.3.2 and the interface address 234.24.3.2, the request type parameters include request type identifiers hqrzd and tsrzd, the state corresponding to the request type identifier hqrzd is enabled, and the state corresponding to the request type identifier tsrzd is disabled, and because the state corresponding to the request type identifier hqrzd carried in the financing order operation request is enabled, it is determined that the user identifier wykj has the authority to access the interface address 234.24.3.2.
In a specific embodiment, if the state corresponding to the request type identifier is disabled, determining that the user identifier does not have the right to access the interface address, and sending a prompt message to the enterprise management system, where the prompt message is used to prompt the user identifier to have the no right to access the interface address.
In a specific embodiment, before performing an operation of performing data interaction with the enterprise management system corresponding to the request type identifier, a specific method flow further includes: acquiring a key corresponding to the user identifier, and sending the key to an enterprise management system; obtaining a token sent by an enterprise management system; obtaining the obtaining time of the token; acquiring a preset moment corresponding to the token; and determining that the acquisition time is not greater than the preset time.
The token (token) and the preset time corresponding to the token are stored in the database of the convergence platform, and the preset time corresponding to the token is the validity period of the token. And when the acquisition time is not more than the preset time, the token further determines that the user identification has the authority to operate the convergence platform in the valid period.
In the embodiment of the present application, as shown in fig. 3, a flow of a method applied to data interaction of an enterprise management system mainly includes:
In one embodiment, the request type corresponding to the request type identifier includes one of obtaining a financing order and pushing a financing order.
In a specific embodiment, as shown in fig. 4, after the convergence platform determines that the user identifier has the right to access the interface address, and when the request type is pushing the financing bill, the flow of the method for the convergence platform to perform data interaction with the enterprise management system mainly includes:
Specifically, the auditing time of the first financing order may be within a preset time period, for example: the preset time period may be from 7 days 3/2021 to 8 days 3/2021.
The first financing bill and the invoice corresponding to the first financing bill are encrypted by using the secret key, so that the transmission safety of the first financing bill and the invoice corresponding to the first financing bill between the enterprise management system and the convergence platform can be ensured.
Wherein the identification of the first financing order is consistent with the identification of the second financing order, the second financing order is already stored in the preset database, and the first financing order is not stored in the preset database.
In one embodiment, if the convergence platform cannot inquire the second financing sheet corresponding to the identifier of the first financing sheet from the preset database, the first financing sheet is stored in the preset database.
And step 408, if the audit time of the first financing order is greater than the audit time of the second financing order, the convergence platform changes the invalidation state of the second financing order into invalidation, stores the first financing order into a preset database, and changes the pushing state of the first financing order into pushing.
If the auditing time of the first financing order is greater than the auditing time of the second financing order, the first financing order is indicated to be reviewed and modified on the basis of the second financing order, and at the moment, the first financing order needs to be stored in a preset database, so that the financing order in the convergence platform is guaranteed to include the updated financing order which is reviewed and modified.
In one embodiment, if the audit time of the first financing order is equal to the audit time of the second financing order, the first financing order does not need to be saved in the preset database, and multiple identical financing orders are prevented from being saved.
The enterprise management system changes the pushing state of the first financing list into the pushing state after the first financing list is changed, and the situation that the same financing list is repeatedly pushed to the convergence platform can be avoided.
In a specific embodiment, as shown in fig. 5, after the convergence platform determines that the user identifier has the right to access the interface address, and when the request type is to acquire a financing order, the method flow of the convergence platform performing data interaction with the enterprise management system mainly includes:
And the updating state of the third financing bill is not updated, which indicates that the operation information of the fund side of the third financing bill is not updated to the enterprise management system.
And 505, the enterprise management system updates the operation information of the fund side to the third financing bill and changes the updating state of the third financing bill to be updated.
And 507, the convergence platform acquires the updated state of the third financing order sent by the enterprise management system after being changed, and changes the updated state of the third financing order into the updated state of the third financing order after being changed.
The convergence platform changes the update state of the third financing order into the update state after the third financing order is changed, so that the enterprise management system can be prevented from repeatedly acquiring the same financing order from the convergence platform.
In summary, in the embodiment of the present application, the convergence platform obtains a financing sheet operation permission corresponding to a user identifier, where the financing sheet operation permission includes an interface address and a request type parameter corresponding to the interface address, the request type parameter includes a request type identifier and a state corresponding to the request type identifier, and if the state corresponding to the request type identifier is enabled, it is determined that the user identifier has permission to access the interface address, and an operation of performing data interaction with an enterprise management system corresponding to the request type identifier is executed. In the prior art, a convergence platform has a plurality of interfaces, each interface corresponds to a function, if a function is added, an interface needs to be added, and a right to access the interface is allocated to a user in need. In the method provided by the embodiment of the application, the financing list operation authority comprises an interface address and a request type parameter corresponding to the interface address, the request type parameter comprises a request type identifier and a state corresponding to the request type identifier, the request type parameter corresponding to the interface address is added into the financing list operation authority, only once financing list operation authority needs to be allocated, subsequently, multiple functions corresponding to one interface can be realized by modifying the request type parameter, when the functions are added, no interface needs to be added, the authority of accessing the interface is allocated to a needed user, and the problem of multiple allocation of interface access authority is solved.
Based on the same concept, the present application provides a data interaction device configured on a convergence platform in an embodiment, and specific implementation of the device may refer to the description of the method embodiment, and repeated details are not repeated, as shown in fig. 6, the device mainly includes:
a first obtaining module 601, configured to obtain a financing order operation request sent by an enterprise management system, where the financing order operation request carries a user identifier and a request type identifier;
a second obtaining module 602, configured to obtain a financing list operation permission corresponding to the user identifier, where the financing list operation permission includes an interface address and a request type parameter corresponding to the interface address, and the request type parameter includes the request type identifier and a state corresponding to the request type identifier;
the processing module 603 is configured to determine that the user identifier has permission to access the interface address if the state corresponding to the request type identifier is enabled, and perform an operation of performing data interaction with the enterprise management system corresponding to the request type identifier.
Based on the same concept, the present application provides a data interaction device configured in an enterprise management system in an embodiment, and specific implementation of the device may refer to the description of the method embodiment, and repeated details are not repeated, as shown in fig. 7, the device mainly includes:
a first sending module 701, configured to send a financing order operation request to a convergence platform, where the financing order operation request carries a user identifier and a request type identifier;
a third obtaining module 702, configured to obtain a key sent by the convergence platform;
a fourth obtaining module 703, configured to obtain a token according to the user identifier and the key;
a second sending module 704, configured to send the token to the convergence platform.
Based on the same concept, an embodiment of the present application further provides an electronic device, as shown in fig. 8, the electronic device mainly includes: a processor 801, a memory 802, and a communication bus 803, wherein the processor 801 and the memory 802 communicate with each other via the communication bus 803. The memory 802 stores a program executable by the processor 801, and the processor 801 executes the program stored in the memory 802, so as to implement the following steps:
acquiring a financing list operation request sent by an enterprise management system, wherein the financing list operation request carries a user identifier and a request type identifier; acquiring a financing list operation authority corresponding to a user identifier, wherein the financing list operation authority comprises an interface address and a request type parameter corresponding to the interface address, and the request type parameter comprises a request type identifier and a state corresponding to the request type identifier; if the state corresponding to the request type identification is enabled, determining that the user identification has the authority to access the interface address, and executing the data interaction operation with the enterprise management system corresponding to the request type identification;
or,
sending a financing sheet operation request to a convergence platform, wherein the financing sheet operation request carries a user identifier and a request type identifier; acquiring a secret key sent by a convergence platform; obtaining a token according to the user identifier and the secret key; and sending the token to the convergence platform.
The communication bus 803 mentioned in the electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus 803 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus.
The Memory 802 may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Alternatively, the memory may be at least one memory device located remotely from the processor 801.
The Processor 801 may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc., and may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic devices, discrete gates or transistor logic devices, and discrete hardware components.
In yet another embodiment of the present application, there is also provided a computer-readable storage medium having a computer program stored therein, which, when run on a computer, causes the computer to perform the data interaction method described in the above embodiment.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wirelessly (e.g., infrared, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The available media may be magnetic media (e.g., floppy disks, hard disks, tapes, etc.), optical media (e.g., DVDs), or semiconductor media (e.g., solid state drives), among others.
It is noted that, in this document, 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 an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present invention, which enable those skilled in the art to understand or practice the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (13)
1. A data interaction method is applied to a convergence platform and comprises the following steps:
acquiring a financing list operation request sent by an enterprise management system, wherein the financing list operation request carries a user identifier and a request type identifier;
acquiring a financing list operation authority corresponding to the user identifier, wherein the financing list operation authority comprises an interface address and a request type parameter corresponding to the interface address, and the request type parameter comprises a request type identifier and a state corresponding to the request type identifier;
and if the state corresponding to the request type identifier is enabled, determining that the user identifier has the right to access the interface address, and executing the data interaction operation between the user identifier and the enterprise management system corresponding to the request type identifier.
2. The data interaction method of claim 1, wherein before performing the operation of data interaction with the enterprise management system corresponding to the request type identifier, the method further comprises:
acquiring a key corresponding to the user identifier, and sending the key to the enterprise management system;
obtaining a token sent by the enterprise management system;
obtaining the obtaining time of the token;
acquiring a preset moment corresponding to the token;
and determining that the acquisition time is not greater than the preset time.
3. The data interaction method of claim 2, wherein the request type identification of the corresponding request type comprises one of obtaining a financing order and pushing a financing order.
4. The data interaction method according to claim 3, wherein when the request type corresponding to the request type identifier is the push financing sheet, the performing of the data interaction operation with the enterprise management system corresponding to the request type identifier includes:
acquiring encrypted data sent by the enterprise management system;
decrypting the encrypted data by using the secret key to obtain a first financing bill and an invoice corresponding to the first financing bill, wherein the pushing state of the first financing bill is not pushing, and the auditing state of the first financing bill is audited;
inquiring a second financing list corresponding to the identifier of the first financing list from a preset database, wherein the invalidation state of the second financing list is that the second financing list is not invalidated;
comparing the auditing time of the first financing bill with the auditing time of the second financing bill;
if the audit time of the first financing sheet is greater than the audit time of the second financing sheet, changing the invalidation state of the second financing sheet into invalidation, storing the first financing sheet to the preset database, and changing the pushing state of the first financing sheet into pushing;
and sending the changed push state of the first financing bill to the enterprise management system.
5. The data interaction method according to claim 3, wherein when the request type corresponding to the request type identifier is the financing order acquisition, the performing of the data interaction operation with the enterprise management system corresponding to the request type identifier includes:
acquiring a third financing bill, wherein the operation state of a fund side of the third financing bill is operated, and the updating state of the third financing bill is not updated;
obtaining fund party operation information in the third financing bill, wherein the fund party operation information comprises at least one of pre-review information, payment information and ticket refunding information;
sending the fund side operation information in the third financing bill to the enterprise management system;
and acquiring the updated state of the third financing order sent by the enterprise management system after the third financing order is changed, and changing the updated state of the third financing order into the updated state of the third financing order after the third financing order is changed.
6. A data interaction method is applied to an enterprise management system and comprises the following steps:
sending a financing sheet operation request to a convergence platform, wherein the financing sheet operation request carries a user identifier and a request type identifier;
acquiring a secret key sent by the convergence platform;
obtaining a token according to the user identification and the secret key;
and sending the token to the convergence platform.
7. The data interaction method of claim 6, wherein the request type identification of the corresponding request type comprises one of obtaining a financing order and pushing a financing order.
8. The data interaction method according to claim 7, wherein when the request type corresponding to the request type identifier is the push financing sheet, after the token is sent to the convergence platform, the method further comprises:
acquiring a first financing bill and an invoice corresponding to the first financing bill, wherein the pushing state of the first financing bill is not pushed, and the auditing state of the first financing bill is audited;
encrypting the first financing bill and the invoice corresponding to the first financing bill by using the secret key to obtain encrypted data;
sending the encrypted data to the convergence platform;
and acquiring the changed pushing state of the first financing order sent by the convergence platform, and changing the pushing state of the first financing order into the changed pushing state of the first financing order.
9. The data interaction method according to claim 7, wherein when the request type corresponding to the request type identifier is the financing order acquisition, after the token is sent to the convergence platform, the method further comprises:
obtaining fund party operation information in a third financing bill sent by the convergence platform;
updating the operation information of the fund party to the third financing bill, and changing the updating state of the third financing bill to be updated;
and sending the updated state after the third financing bill is changed to the convergence platform.
10. A data interaction device, configured on a convergence platform, comprising:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a financing list operation request sent by an enterprise management system, and the financing list operation request carries a user identifier and a request type identifier;
a second obtaining module, configured to obtain a financing list operation permission corresponding to the user identifier, where the financing list operation permission includes an interface address and a request type parameter corresponding to the interface address, and the request type parameter includes the request type identifier and a state corresponding to the request type identifier;
and the processing module is used for determining that the user identifier has the permission to access the interface address and executing the data interaction operation between the user identifier and the enterprise management system corresponding to the request type identifier if the state corresponding to the request type identifier is enabled.
11. A data interaction device, configured in an enterprise management system, comprising:
the system comprises a first sending module, a second sending module and a third sending module, wherein the first sending module is used for sending a financing list operation request to a convergence platform, and the financing list operation request carries a user identifier and a request type identifier;
the third acquisition module is used for acquiring the key sent by the convergence platform;
a fourth obtaining module, configured to obtain a token according to the user identifier and the secret key;
and the second sending module is used for sending the token to the convergence platform.
12. An electronic device, comprising: the system comprises a processor, a memory and a communication bus, wherein the processor and the memory are communicated with each other through the communication bus;
the memory for storing a computer program;
the processor is configured to execute the program stored in the memory to implement the data interaction method of any one of claims 1 to 5, or to implement the data interaction method of any one of claims 6 to 9.
13. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, carries out the data interaction method of any one of claims 1 to 5, or carries out the data interaction method of any one of claims 6 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110363455.XA CN113205302A (en) | 2021-04-02 | 2021-04-02 | Data interaction method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110363455.XA CN113205302A (en) | 2021-04-02 | 2021-04-02 | Data interaction method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113205302A true CN113205302A (en) | 2021-08-03 |
Family
ID=77026171
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110363455.XA Pending CN113205302A (en) | 2021-04-02 | 2021-04-02 | Data interaction method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113205302A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117728954A (en) * | 2023-12-08 | 2024-03-19 | 中金金融认证中心有限公司 | Online authentication method, online data acquisition system and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101901458A (en) * | 2009-05-27 | 2010-12-01 | 中国工商银行股份有限公司 | Trade financing processing system and method for supporting various services |
| US20140149741A1 (en) * | 2012-11-27 | 2014-05-29 | Oracle International Corporation | Access management system using trusted partner tokens |
| CN109815013A (en) * | 2019-01-02 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Business data processing method, device, computer equipment and storage medium |
| CN110516454A (en) * | 2019-08-13 | 2019-11-29 | 苏州浪潮智能科技有限公司 | Exchange method, system, device and the computer readable storage medium of more equipment |
-
2021
- 2021-04-02 CN CN202110363455.XA patent/CN113205302A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101901458A (en) * | 2009-05-27 | 2010-12-01 | 中国工商银行股份有限公司 | Trade financing processing system and method for supporting various services |
| US20140149741A1 (en) * | 2012-11-27 | 2014-05-29 | Oracle International Corporation | Access management system using trusted partner tokens |
| CN109815013A (en) * | 2019-01-02 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Business data processing method, device, computer equipment and storage medium |
| CN110516454A (en) * | 2019-08-13 | 2019-11-29 | 苏州浪潮智能科技有限公司 | Exchange method, system, device and the computer readable storage medium of more equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117728954A (en) * | 2023-12-08 | 2024-03-19 | 中金金融认证中心有限公司 | Online authentication method, online data acquisition system and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109214197B (en) | Method, apparatus and storage medium for processing private data based on block chain | |
| CN109791591B (en) | Method and system for identity and credential protection and verification via blockchain | |
| CN107609848B (en) | Intellectual property licensing method and system based on Internet of things | |
| US11223482B2 (en) | Secure data exchange | |
| JP2022000757A5 (en) | ||
| US11855978B2 (en) | Sharing credentials | |
| US9350739B2 (en) | Recovery from rolling security token loss | |
| CN110598434B (en) | House information processing method and device based on blockchain network, electronic equipment and storage medium | |
| CN108289098B (en) | Authority management method and device of distributed file system, server and medium | |
| CN101443745A (en) | Method and apparatus for issuing rights object required to use digital content | |
| CN111769941B (en) | Business processing method and device and integrated business service system | |
| EP3839791B1 (en) | Identification and authorization of transactions via smart contracts | |
| CN107819743B (en) | Resource access control method and terminal equipment | |
| CN107832602B (en) | Unified electronic seal system based on identification | |
| KR100731491B1 (en) | Method for managing dispersion certificate revocation list | |
| CN110674531B (en) | Residential information management method, device, server and medium based on block chain | |
| WO2019175427A1 (en) | Method, device and medium for protecting work based on blockchain | |
| CN113642239B (en) | Federal learning modeling method and system | |
| CN112363997B (en) | Data version management method, device and storage medium | |
| CN113205302A (en) | Data interaction method, device, equipment and storage medium | |
| CN116438778A (en) | Persistent source value of assumed alternate identity | |
| CN108009794B (en) | Electronic credential state management method and device | |
| US20180157795A1 (en) | Multilevel object file storage | |
| WO2021160981A1 (en) | Methods and apparatus for controlling access to personal data | |
| CN117041959A (en) | Service processing method, device, electronic equipment and computer readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210803 |
|
| RJ01 | Rejection of invention patent application after publication |