CN110175845B - Cross-contract data calling method, device and storage medium - Google Patents
Cross-contract data calling method, device and storage medium Download PDFInfo
- Publication number
- CN110175845B CN110175845B CN201910442121.4A CN201910442121A CN110175845B CN 110175845 B CN110175845 B CN 110175845B CN 201910442121 A CN201910442121 A CN 201910442121A CN 110175845 B CN110175845 B CN 110175845B
- Authority
- CN
- China
- Prior art keywords
- contract
- combined
- shareability
- shared
- command
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a cross-contract data calling method, cross-contract data calling equipment and a storage medium, wherein the method comprises the following steps: configuring a combined contract of a plurality of contracts according to a pre-configured combined contract configuration rule; the method comprises the steps that a combined contract of a plurality of contracts is configured, wherein the combined contract comprises a first sharability for configuring methods of the combined contract and a second sharability for configuring execution results generated and stored by executing the methods, and the combined contract configuration rule comprises that when the first sharability of the methods is configured to be shared, the second sharability of the execution results generated by the executing methods is also configured to be shared; and calling the second shareability as the shared execution result by calling the first method for sharing the first shareability. The method and the system realize the interoperation of different contracts and the asset intercommunication among different contracts.
Description
Technical Field
The application relates to the technical field of block chains, in particular to a cross-contract data calling method, cross-contract data calling equipment and a storage medium.
Background
The existing contract issuing modes are all issued in a single contract issuing mode, different contracts cannot be operated mutually, and assets among different contracts are not universal.
Disclosure of Invention
In view of the above-described deficiencies or inadequacies in the prior art, it would be desirable to provide an interoperable, asset-generic, cross-contract data invocation method, apparatus, and storage medium.
In a first aspect, the present invention provides a cross-contract data calling method, including:
configuring a combined contract of a plurality of contracts according to a pre-configured combined contract configuration rule; the method comprises the steps that a combined contract of a plurality of contracts is configured, wherein the combined contract comprises a first sharability for configuring methods of the combined contract and a second sharability for configuring execution results generated and stored by executing the methods, and the combined contract configuration rule comprises that when the first sharability of the methods is configured to be shared, the second sharability of the execution results generated by the executing methods is also configured to be shared;
and calling the second shareability as the shared execution result by calling the first method for sharing the first shareability.
In a second aspect, the present invention also provides an apparatus comprising one or more processors and memory, wherein the memory contains instructions executable by the one or more processors to cause the one or more processors to perform a cross contract data call method provided in accordance with embodiments of the present invention.
In a third aspect, the present invention also provides a storage medium storing a computer program that causes a computer to execute the cross-contract data call method provided according to the embodiments of the present invention.
The cross-contract data calling method, the device and the storage medium provided by the embodiments of the invention configure a combined contract of a plurality of contracts according to the pre-configured combined contract configuration rule; the method comprises the steps that a combined contract of a plurality of contracts is configured, wherein the combined contract comprises a first sharability for configuring methods of the combined contract and a second sharability for configuring execution results generated and stored by executing the methods, and the combined contract configuration rule comprises that when the first sharability of the methods is configured to be shared, the second sharability of the execution results generated by the executing methods is also configured to be shared; and calling a first method with the first sharing property as the sharing property and calling a method with the second sharing property as the shared execution result to realize the interoperation of different contracts and the asset intercommunication among different contracts.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
fig. 1 is a flowchart of a cross-contract data call method according to an embodiment of the present invention.
Fig. 2 is a flowchart of step S14 in a preferred embodiment of the method shown in fig. 1.
Fig. 3 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 is a flowchart of a cross-contract data call method according to an embodiment of the present invention. As shown in FIG. 1, in this embodiment, the present invention provides a cross-contract data calling method, including:
s12: configuring a combined contract of a plurality of contracts according to a pre-configured combined contract configuration rule; the method comprises the steps that a combined contract of a plurality of contracts is configured, wherein the combined contract comprises a first sharability for configuring methods of the combined contract and a second sharability for configuring execution results generated and stored by executing the methods, and the combined contract configuration rule comprises that when the first sharability of the methods is configured to be shared, the second sharability of the execution results generated by the executing methods is also configured to be shared;
s14: and calling the second shareability as the shared execution result by calling the first method for sharing the first shareability.
Specifically, the second shareability configuration mode is, for example, when the first shareability configuration of a method in the combined contract is shared, a key for generating an execution result by using the name of the combined contract as a prefix, and when the first shareability configuration of a method in the combined contract is not shared, a key for generating an execution result by using the name of the original contract to which the method belongs as a prefix; assuming that a contract A and a contract B are provided, methods a1 and a2 are provided in the contract A, methods B1 and B2 are provided in the contract B, and when a combined contract AB of the contract A and the contract B is configured according to a pre-configured combined contract configuration rule, first shareability of a1, a2, B1 and B2 is configured to be shared;
in step S12, the node configures a combined contract AB according to the preconfigured combined contract configuration rule; the first sharing of the node configurations a1, a2, b1, b2 is shared public; when a1, a2, b1 and b2 in the combined contract AB are called, the AB is used as a prefix to generate a key of an execution result;
in step S14, the node calls the data of the key generating the execution result with AB as the prefix by calling a1, a2, B1, B2 in the combined contract AB, so that the execution result generated by the method B1, B2 of the original B contract can be called by the method a1 or a2 of the original a contract, or the execution result generated by the method a1, a2 of the original a contract can be called by the method B1 or B2 of the original B contract, thereby realizing data calling and asset intercommunication across contracts.
Preferably, part of methods in the combined contract may be configured to be unshared, assuming that there are methods a1, a2 and a3 in the contract a and methods B1, B2 and B3 in the contract B, when the combined contract AB of the contract a and the contract B is configured according to the pre-configured combined contract configuration rule, the first shareability of a1, a2, B1 and B2 is configured to be shared, and the first shareability of a3 and B3 is configured to be unshared; the node configures the first sharing property of a3 and b3 as an unshared private; when a3 in the combined contract AB is called, a is taken as a prefix to generate a key of an execution result, and when B3 in the combined contract AB is called, B is taken as a prefix to generate a key of an execution result.
The above embodiment describes the method exemplarily by taking the first shareability of a1, a2, B1, B2 as shared and the first shareability of a3, B3 as non-shared as examples when there are methods a1, a2, a3 in the contract a, methods B1, B2, B3 in the contract B, and a combined contract AB of the contract a and the contract B in the contract B, and in more embodiments, the method may be applied to any number of contract composition contract transactions, for example, a combined contract ABC of configuration contracts a, B, and C is described in detail, wherein the principle of configuring the combined contract ABC is the same as the above examples, and is not repeated here, as long as the first shareability of the method in the composed combined contract is configured to be shared, the same technical effect can be achieved.
The cross-contract data calling method, the device and the storage medium provided by the above embodiments configure a combined contract of a plurality of contracts according to a pre-configured combined contract configuration rule; the method comprises the steps that a combined contract of a plurality of contracts is configured, wherein the combined contract comprises a first sharability for configuring methods of the combined contract and a second sharability for configuring execution results generated and stored by executing the methods, and the combined contract configuration rule comprises that when the first sharability of the methods is configured to be shared, the second sharability of the execution results generated by the executing methods is also configured to be shared; and calling a first method with the first sharing property as the sharing property and calling a method with the second sharing property as the shared execution result to realize the interoperation of different contracts and the asset intercommunication among different contracts.
In a preferred embodiment, configuring a combined contract of a number of contracts further includes configuring a method of identifying a command of the combined contract.
Assuming that the command of the combined contract includes a combined contract prefix, a method of the combined contract, and command information, the combined contract command received by the node is ab.a.a1.(info), where AB is the combined contract prefix and a.a1 is the method of the combined contract and (info) is the command information.
In further embodiments, the combined contract prefix in the command of the combined contract may be configured as a prefix in other formats such as a-B, A _ B, and the same technical effect can be achieved as long as whether the received command is a command of the combined contract can be determined according to the prefix.
In further embodiments, the method of combining contracts in the command of the combined contract may be configured as a method of combining contracts in other formats such as a-a1, a _ a1, and the like, and the same technical effect can be achieved as long as the name of the original contract to which the method belongs can be judged according to the method of the combined contract (assuming that there are method a1 in contract a and method a1 in contract B, and therefore a distinction is required).
In a preferred embodiment, the commands of the combined contract include a combined contract prefix, a method of the combined contract, and command information.
The cross-contract data calling principle of the above embodiments may refer to methods shown in some embodiments in the specification, and details are not described here.
In a preferred embodiment, the second sharing configuration is as follows:
generating a key of an execution result by using a name of the combined contract as a prefix when the first shareability of the method is configured to be shared;
when the first shareability configuration of the method is unshared, a key of an execution result is generated by using a name of an original contract to which the method belongs as a prefix.
The cross contract data call principle of the above embodiment may refer to the method shown in fig. 1, and is not described herein again.
In this embodiment, since the database is configured with the prefix of the key as the data barrier of the different contract, the second shareability is configured by configuring the prefix of the key of the execution result;
in further embodiments, when the data barriers are configured in different ways in different databases, the second shareability should be configured in a corresponding way.
Fig. 2 is a flowchart of step S14 in a preferred embodiment of the method shown in fig. 1. As shown in fig. 2, in a preferred embodiment, step S14 includes:
s141: receiving a first command, and judging whether the first command is combined with a contract command according to whether a first prefix of the first command is consistent with the name of the combined contract:
if yes, go to step S142: executing the first command according to the first method of the first command, the shareability of the preconfigured first method and the first command information of the first command to generate a first execution result:
if the first sharing configuration of the first method is sharing, step S143 is executed: generating a first key of an execution result by taking the name of the combined contract as a prefix, and storing the first key and a corresponding first value;
if the first sharing configuration of the first method is non-sharing, step S144 is executed: and generating a second key of the execution result by taking the name of the original contract to which the method belongs as a prefix, and storing the second key and a corresponding second value.
Assuming that a contract C and a contract D are provided, methods C1 and C2 are provided in the contract C, and a method D1 is provided in the contract D, when a combined contract CD of the contract C and the contract D is configured according to a pre-configured combined contract configuration rule, a first sharing property of C1 and D1 is shared, and a first sharing property of C2 is non-shared;
the first command is cd.c.c1.(info1), where CD is a first prefix of the combined contract CD, c.c1 is a first method of the combined contract CD, (info1) is first command information of the combined contract CD, and the first sharing of c1 is shared public;
in step S141, the node receives the first command cd.c.c. 1.(info1), and determines whether the first command is a combined contract command according to whether the first prefix CD coincides with the name of the combined contract:
since the name of the combined contract is CD, which is the same as the first prefix, step S142 is executed: generating a first execution result according to the c.c.c.c 1, the preconfigured c.c1 shareability, and (info1) executing the cd.c.c.c 1.(info 1):
since the shareability of c.c1 is shared public, step S143 is executed: generating a first key of a first execution result by using the CD as a prefix, and storing the first key and a corresponding first value (assuming that the execution result is v1, the first key is constructed by the first execution result and the first prefix, and the first value is the execution result v1, the first key value pair (CDv1, v1)) is stored.
Assuming that the first command is cd.c.c2.(info2), where CD is a first prefix of the combined contract CD, c.c2 is a first method of the combined contract CD, (info2) is first command information of the combined contract CD, and the first shareability of c2 is an unshared private;
in step S141, the node receives the first command cd.c.c. 2.(info2), and determines whether the first command is a combined contract command according to whether the first prefix CD coincides with the name of the combined contract:
since the name of the combined contract is CD, which is the same as the first prefix, step S142 is executed: generating a first execution result according to the c.c.c.c 2, the preconfigured c.c2 shareability, and (info2) executing the cd.c.c.c 1.(info 2):
since the shareability of c.c2 is the unshared private, step S144 is executed: c is used as a prefix to generate a second key of the first execution result, and the second key and a corresponding second value are stored (assuming that the execution result is v2, the second key is constructed by the first execution result and the name of the original contract to which the method belongs as a prefix, and the second value is the first execution result v2, a second key-value pair (Cv2, v2) is stored).
Assume that the first command is d.d1.info3, the first prefix is null;
in step S141, the node receives the first command d.d1.info3, and determines whether the first command is a combined contract command according to whether the first prefix is consistent with the name of the combined contract:
since the name of the combined contract is CD, different from the first prefix (null), a first execution result is generated according to d.d1 and info3, a third key of the first execution result is generated by prefixing D, and the third key and a corresponding third value are stored (assuming that the execution result is v3, the third key is constructed by prefixing the name of the original contract to which the first execution result and method belong, and the third value is v3, a third key value pair (Dv3, v3) is stored).
Preferably, in step S142, it is first determined whether a first method of the first command exists in a combined contract composed of contracts declared in the first prefix, and if the received first command is cd.c.e1.info4 and there is no method c.e1 in the combined contract CD, the subsequent step is not executed, and the error information is directly returned.
Fig. 3 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
As shown in fig. 3, as another aspect, the present application also provides an apparatus 300 including one or more Central Processing Units (CPUs) 301 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)302 or a program loaded from a storage section 308 into a Random Access Memory (RAM) 303. In the RAM303, various programs and data necessary for the operation of the apparatus 300 are also stored. The CPU301, ROM302, and RAM303 are connected to each other via a bus 304. An input/output (I/O) interface 305 is also connected to bus 304.
The following components are connected to the I/O interface 305: an input portion 306 including a keyboard, a mouse, and the like; an output section 307 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 308 including a hard disk and the like; and a communication section 309 including a network interface card such as a LAN card, a modem, or the like. The communication section 309 performs communication processing via a network such as the internet. A drive 310 is also connected to the I/O interface 305 as needed. A removable medium 311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 310 as necessary, so that a computer program read out therefrom is mounted into the storage section 308 as necessary.
In particular, according to an embodiment of the present disclosure, the cross contract data call method described in any of the above embodiments may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for executing a cross-contract data call method. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 309, and/or installed from the removable medium 311.
As yet another aspect, the present application also provides a computer-readable storage medium, which may be the computer-readable storage medium included in the apparatus of the above-described embodiment; or it may be a separate computer readable storage medium not incorporated into the device. The computer-readable storage medium stores one or more programs for use by one or more processors in performing the cross-contract data call methods described herein.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted 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-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules described in the embodiments of the present application may be implemented by software or hardware. The described units or modules may also be provided in a processor, for example, each of the described units may be a software program provided in a computer or a mobile intelligent device, or may be a separately configured hardware device. Wherein the designation of a unit or module does not in some way constitute a limitation of the unit or module itself.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the present application. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (7)
1. A cross-contract data invocation method, comprising:
configuring a combined contract of a plurality of contracts according to a pre-configured combined contract configuration rule; wherein the configuring of the combined contract of the plurality of contracts comprises configuring a first shareability of methods of the combined contract and configuring a second shareability of execution results generated and stored by executing the methods, the combined contract configuration rule comprises that when the first shareability of the methods is configured to be shared, the second shareability of the execution results generated by executing the methods is also configured to be shared, the plurality of contracts comprises a first contract and a second contract, the first shareability of the first method and the second method in the combined contract is configured to be shared, the first method is derived from the first contract, and the second method is derived from the second contract;
and calling an execution result of a second method with shared second sharing by calling the first method with shared first sharing.
2. The method of claim 1, wherein configuring a combined contract of a number of contracts further comprises configuring an identification method of a command of the combined contract.
3. The method of claim 2, wherein the commands for the combined contract comprise a combined contract prefix, a method for the combined contract, and command information.
4. The method according to any of claims 1-3, wherein the second shareability is configured by:
generating a key of the execution result prefixed by a name of the combined contract when the first shareability of the method is configured for sharing;
generating a key of the execution result prefixed by a name of an original contract to which the method belongs when the first shareability configuration of the method is unshared.
5. The method of claim 4, wherein invoking the execution result of the second shareability as shared by invoking the first method of the first shareability as shared comprises:
receiving a first command, and judging whether the first command is combined with a contract command according to whether a first prefix of the first command is consistent with a name of the combined contract:
if yes, executing the first command according to the first method of the first command, the shareability of the preconfigured first method and the first command information of the first command to generate a first execution result:
if the first sharability configuration of the first method is shared, generating a first key of the execution result by using the name of the combined contract as a prefix, and storing the first key and a corresponding first value;
and if the first sharability configuration of the first method is non-shared, generating a second key of the execution result by taking the name of the original contract to which the method belongs as a prefix, and storing the second key and a corresponding second value.
6. An apparatus for cross contract data invocation, the apparatus comprising:
one or more processors;
a memory for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method recited in any of claims 1-5.
7. A storage medium storing a computer program, characterized in that the program, when executed by a processor, implements the method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910442121.4A CN110175845B (en) | 2019-05-24 | 2019-05-24 | Cross-contract data calling method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910442121.4A CN110175845B (en) | 2019-05-24 | 2019-05-24 | Cross-contract data calling method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110175845A CN110175845A (en) | 2019-08-27 |
| CN110175845B true CN110175845B (en) | 2021-05-11 |
Family
ID=67695713
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910442121.4A Active CN110175845B (en) | 2019-05-24 | 2019-05-24 | Cross-contract data calling method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110175845B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2017146842A (en) * | 2016-02-18 | 2017-08-24 | 株式会社三井住友銀行 | Loan office management system and method |
| CN107767265A (en) * | 2017-11-07 | 2018-03-06 | 中积有限公司 | A kind of data sharing method and server |
| CN108989389A (en) * | 2018-06-11 | 2018-12-11 | 北京航空航天大学 | A method of establishing intelligent contract micro services |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7870060B2 (en) * | 2007-07-31 | 2011-01-11 | Chicago Mercantile Exchange, Inc. | Bundled financial instruments |
| CN107945021A (en) * | 2017-12-07 | 2018-04-20 | 杭州趣链科技有限公司 | A kind of digital asset management method based on block chain intelligence contract |
| CN108876618A (en) * | 2018-06-15 | 2018-11-23 | 浙江华信区块链科技服务有限公司 | A kind of exchange block catenary system and corresponding universal block chain mutual operation method and network |
| CN109543457B (en) * | 2018-11-07 | 2021-07-09 | 泰康保险集团股份有限公司 | Method and device for controlling calling between intelligent contracts |
-
2019
- 2019-05-24 CN CN201910442121.4A patent/CN110175845B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2017146842A (en) * | 2016-02-18 | 2017-08-24 | 株式会社三井住友銀行 | Loan office management system and method |
| CN107767265A (en) * | 2017-11-07 | 2018-03-06 | 中积有限公司 | A kind of data sharing method and server |
| CN108989389A (en) * | 2018-06-11 | 2018-12-11 | 北京航空航天大学 | A method of establishing intelligent contract micro services |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110175845A (en) | 2019-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102121159B1 (en) | Event-driven blockchain workflow processing | |
| US20210248605A1 (en) | Cross-chain right usage systems, methods, apparatuses, electronic devices, and storage media | |
| CN111782668B (en) | Data structure reading and updating method and device and electronic equipment | |
| CN108846753B (en) | Method and apparatus for processing data | |
| CN109885786B (en) | Data caching processing method and device, electronic equipment and readable storage medium | |
| CN109522751B (en) | Access right control method and device, electronic equipment and computer readable medium | |
| CN109639598A (en) | Request processing method, server, storage medium and device based on micro services | |
| CN111639123A (en) | Data processing method and device based on block chain, terminal and storage medium | |
| WO2020224100A1 (en) | Blockchain configuration file processing apparatus, system, and method, and storage medium | |
| CN112817600B (en) | Program annotation compilation method and corresponding device, equipment and medium | |
| CN114816393A (en) | Information generation method, apparatus, device, and storage medium | |
| CN113010115B (en) | Data processing method in block chain node and related equipment | |
| CN114723394A (en) | Credit granting flow configuration method based on artificial intelligence and related equipment | |
| CN115545639B (en) | Financial business processing method, device, electronic equipment and storage medium | |
| CN114637969A (en) | Authentication method and device for target object | |
| CN110175845B (en) | Cross-contract data calling method, device and storage medium | |
| CN113077241B (en) | Approval processing method, device, equipment and storage medium | |
| CN116737662A (en) | Method, device, electronic equipment and storage medium for processing business data | |
| CN114546475A (en) | Service system management method and device | |
| CN114546705A (en) | Operation response method, operation response device, electronic device, and storage medium | |
| US11960469B2 (en) | Heterogeneous integration with distributed ledger blockchain services | |
| CN114553930B (en) | System integration method, device, computer equipment and storage medium | |
| US10423475B2 (en) | Stateful tokens for communicating with external services | |
| CN111274051B (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN118394761A (en) | Data processing method and device based on object storage cluster and electronic equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |