WO2020224251A1 - 区块链事务的处理方法、装置、设备及存储介质 - Google Patents
区块链事务的处理方法、装置、设备及存储介质 Download PDFInfo
- Publication number
- WO2020224251A1 WO2020224251A1 PCT/CN2019/122054 CN2019122054W WO2020224251A1 WO 2020224251 A1 WO2020224251 A1 WO 2020224251A1 CN 2019122054 W CN2019122054 W CN 2019122054W WO 2020224251 A1 WO2020224251 A1 WO 2020224251A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- transaction block
- transaction
- processing
- block
- mutex
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
- G06F9/526—Mutual exclusion algorithms
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Definitions
- This application relates to the field of blockchain technology, and in particular to a method, device, equipment and computer-readable storage medium for processing blockchain transactions.
- Blockchain is generally understood as a distributed ledger, and its essence is also a distributed database.
- One of the fundamental differences between the alliance blockchain and the ordinary blockchain is the need to provide a privacy protection mechanism. Normally, this mechanism is implemented through signature encryption and signature verification in cryptography.
- blockchain transactions are packaged into blocks and sent to blockchain nodes. The node unlocks the block and obtains the transactions in it, then verifies each transaction and executes the commit process of the corresponding transaction in order. Since the submission of existing blockchain transactions is executed in a sequential manner, when the system is busy and there are many transactions, the transaction submission speed often lags behind the transaction generation speed, which reduces the transaction processing efficiency.
- the main purpose of this application is to provide a blockchain transaction processing method, device, equipment, and computer-readable storage medium, aiming to solve the technical problem of low transaction processing efficiency of existing blockchain transactions.
- this application provides a method for processing blockchain transactions, and the method for processing blockchain transactions includes the following steps:
- the second transaction block in the transaction block processing queue is verified and signed, multi-version checked, and persisted through the second pipeline thread, wherein the occurrence time of the preset event is not It is greater than the end time of the verification signature of the first transaction block to process the transaction block in parallel.
- the present application also provides a block chain transaction processing device, the block chain transaction processing device includes:
- the transaction block adding module is used to obtain the transaction blocks packaged in the blockchain ordering node when receiving the transaction processing instruction, and add each transaction block to the transaction block processing queue in turn;
- the first processing module is configured to perform signature verification, multi-version checking, and persistence processing on the first transaction block in the transaction block processing queue through the first pipeline thread;
- the second processing module is used to perform signature verification, multi-version checking, and persistence processing on the second transaction block in the transaction block processing queue through the second pipeline thread when a preset event is detected.
- the occurrence time of the preset event is not greater than the end time of the verification signature of the first transaction block, so that the transaction block is processed in parallel.
- this application also provides a blockchain transaction processing device.
- the blockchain transaction processing device includes a processor, a memory, and stored on the memory and can be used by the processor.
- the executed computer-readable instructions wherein when the computer-readable instructions are executed by the processor, the steps of the above-mentioned blockchain transaction processing method are realized.
- the present application also provides a computer-readable storage medium having computer-readable instructions stored on the computer-readable storage medium, and when the computer-readable instructions are executed by a processor, the implementation is as described above The steps of the blockchain transaction processing method.
- This application provides a method for processing blockchain transactions. This application allocates each transaction block in the blockchain to multiple pipeline threads to process transaction blocks in parallel through multiple pipeline threads, which not only increases the throughput of the blockchain It reduces transaction processing delay, improves resource utilization and transaction processing efficiency, and solves the technical problem of low transaction processing efficiency of existing blockchain transactions.
- FIG. 1 is a schematic diagram of the hardware structure of a blockchain transaction processing device involved in the solution of the embodiment of the application;
- FIG. 2 is a schematic flowchart of a first embodiment of a method for processing a blockchain transaction in this application
- FIG. 3 is a schematic flowchart of a second embodiment of a method for processing blockchain transactions in this application.
- FIG. 4 is a schematic flowchart of a third embodiment of a method for processing blockchain transactions in this application.
- the blockchain transaction processing method involved in the embodiments of the present application is mainly applied to the processing equipment of the blockchain transaction.
- the processing equipment of the blockchain transaction may be a device with display and processing functions such as a PC, a portable computer, and a mobile terminal.
- FIG. 1 is a schematic diagram of the hardware structure of a blockchain transaction processing device involved in the solution of an embodiment of the application.
- the device for processing blockchain transactions may include a processor 1001 (for example, a CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005.
- the communication bus 1002 is used to realize the connection and communication between these components;
- the user interface 1003 may include a display (Display), an input unit such as a keyboard (Keyboard);
- the network interface 1004 may optionally include a standard wired interface, a wireless interface (Such as WI-FI interface);
- the memory 1005 can be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory.
- the memory 1005 may optionally be a storage device independent of the aforementioned processor 1001.
- FIG. 1 does not constitute a limitation on the processing equipment of blockchain transactions, and may include more or less components than shown in the figure, or combine some components, or different The layout of the components.
- the memory 1005 as a computer-readable storage medium in FIG. 1 may include an operating system, a network communication module, and computer-readable instructions.
- the network communication module is mainly used to connect to the server and perform data communication with the server; and the processor 1001 can call the computer-readable instructions stored in the memory 1005 and execute the blockchain transaction processing provided by the embodiment of the application method.
- the embodiment of the application provides a method for processing blockchain transactions.
- FIG. 2 is a schematic flowchart of a first embodiment of a method for processing a blockchain transaction in this application.
- the blockchain transaction processing method includes the following steps:
- Step S10 when the transaction processing instruction is received, the transaction blocks packaged in the blockchain ordering node are obtained, and each transaction block is sequentially added to the transaction block processing queue;
- a method for processing blockchain transactions is provided, which is based on pipeline technology (Pipeline), that is, transaction blocks are processed through multiple pipeline threads. Parallel processing, thereby improving resource utilization and improving the transaction processing efficiency of blockchain transactions.
- Pipeline technology repeatedly performs the same operation on the data set for each thread, and passes the result of the operation to other threads in the next step, where the "data element" stream is executed serially.
- the transaction block includes three transaction processing stages, namely, signature verification, multi-version checking, and persistence processing.
- the processing time of verifying signatures is generally much higher than the processing time of multi-version checking and persistence.
- the time occupied by verifying signatures is generally more than 50% of the processing time of the entire transaction block, and the transaction block
- the multi-version check depends on the multi-version check result of the previous transaction block. Therefore, two transaction blocks can be processed in parallel based on at least two pipeline threads. Specifically, when transaction processing needs to be performed, the packaged transaction block to be processed is obtained in the blockchain ordering node, and the transaction block is added to the preset transaction block processing queue. Wherein, the transaction blocks in the transaction block processing queue are arranged in sequence according to the processing order.
- Step S20 Perform signature verification, multi-version checking and persistence processing on the first transaction block in the transaction block processing queue through the first pipeline thread;
- the verification signature operation of each transaction block can be performed at the same time. Therefore, the first transaction block to be processed in the transaction block processing queue is determined, and the first transaction block is verified and signed by the first pipeline thread.
- step S20 may include:
- the first transaction block is verified and signed by the first pipeline thread, and when the completion instruction of the verification signature of the first transaction block is detected, the first phase mutex of the first transaction block is locked Unlock
- the second-stage mutex is added to the first transaction block through the first pipeline thread, and the first transaction block is passed through The pipeline thread performs multi-version checking and persistence processing on the first transaction block.
- the first pipeline thread when the conditional expression, that is, whether the verification signature of the first transaction block is completed, is not satisfied, the first pipeline thread will still be blocked on the first transaction block and verify the first transaction block signature.
- the specific process is as follows: when the first transaction block is verified and signed by the first pipeline thread, the first mutex lock needs to be set on the first transaction block to declare that the first pipeline thread is The first transaction block performs a signature verification operation, and the first transaction block is currently in a locked state and cannot be processed by other threads.
- the first pipeline thread completes the verification signature of the first transaction block, unlock the first mutex, and generate a first unlock signal corresponding to the first mutex.
- the first unlock signal When the first unlock signal is detected, continue to add a second mutex lock to the first transaction block through the first pipeline thread to declare that the first pipeline thread is performing multiple versions of the first transaction block Check operation, and the first transaction block is currently locked and cannot be processed by other threads.
- the first pipeline thread completes the multi-version check of the first transaction block, unlock the second mutex, and generate a second unlock signal corresponding to the second mutex.
- step S20 may also include:
- Parse the first transaction block obtain each transaction in the first transaction block, and obtain the transaction request second flow rate, current load status information and preset processing value of each transaction;
- the transaction block is parsed to obtain each transaction in the transaction block, the current transaction request traffic per second, the current load status information of the server's CPU and the preset processing values are obtained based on the current The transaction request traffic per second, the load status information and the preset processing value establish multiple threads. Based on the established multiple threads, the transaction is allocated to the CPU for dynamic parallel verification and signature, and then the verification and signature are completed Then, collect the transactions after the verification and signature in the multiple threads, and perform multi-version check and transaction persistence processing on the transactions after the verification and signature.
- the blockchain ordering node packs each transaction with the processing sequence pre-identified into the form of transaction block, and then sends the transaction block to the blockchain data node.
- the blockchain data node verifies and signs each transaction block.
- Transactions are, for example, operations related to data in the database, including data modification operations, data deletion operations, etc., of course, it can also be other operations.
- the processing sequence corresponding to each transaction identifier for example, can identify transactions in the order of numbers "1, 2, 3 --, or identify transactions in the order of letters "a, b, c --, etc.
- each transaction is obtained.
- the current load status information of the CPU includes the CPU working time ratio (of course, it can also be the CPU idle time ratio).
- the preset processing values include preset processing values for testing The maximum number of CPUs for signing and signing, the preset time for signing and verifying, the preset maximum number of CPUs for signing, for example, 16, and the preset time for signing, for example, 10 seconds.
- 5 threads can be established for signature verification Signature, based on the 5 threads, the transaction is allocated to 5 CPUs for parallel verification and signature. In the actual process of signature verification and signature performed by the CPU, other factors may affect the verification and signature time. In order to make the verification and signature time not greater than the preset verification and signature time, this embodiment can also dynamically adjust the number of threads, for example, In the case that the signature verification time is greater than the preset signature verification time due to other factors, if the current transaction request second flow is large, the current CPU working time ratio is small, and the number of current threads does not exceed the preset time. When setting the maximum value of the CPU used for signature verification, the number of threads can be increased.
- a thread allocates transactions to a CPU for signature verification. Therefore, as the number of threads increases, it is also equivalent to adjusting the number of CPUs currently used for signature verification. Since each transaction identifier has a processing sequence, after completing the verification and signature, collect the transactions after verification and signature in the multiple threads, and sort them according to the processing order of the transaction identifier, and sort based on the standard processing method of the database The latter transaction is checked for multiple versions, and then the checked transaction is processed for transaction persistence.
- Step S30 when the occurrence of a preset event is detected, the second transaction block in the transaction block processing queue is subjected to signature verification, multi-version checking and persistence processing through the second pipeline thread, wherein the preset event The occurrence time is not greater than the end time of the verification signature of the first transaction block, so that the transaction block is processed in parallel.
- the second pipeline thread starts processing the second transaction block in the transaction block processing queue.
- the verification signature of the second transaction block is completed through the second pipeline thread
- the time required to verify the signature far exceeds the time required for the other two stages
- the first pipeline thread has completed the multi-version check and persistence of the first transaction block. ⁇ .
- the multi-version check of the second transaction block needs to use the result of the multi-version check of the first transaction block
- the multi-version check of the second transaction block needs to start after the multi-version check of the second transaction block.
- the multi-version check of the first transaction block needs to be completed before the multi-version check of the second transaction block starts.
- the second transaction block can be verified and signed by the second pipeline thread.
- the occurrence time of the preset event is not greater than the end time of the verification signature of the first transaction block, that is, the ideal state is: the completion time of the verification signature of the second transaction block and the time point of the first transaction block
- the multi-version check is completed at the same time.
- the preset time occurrence may be the detection of the first unlock signal of the verification signature of the first transaction block, and when the first unlock information is detected, The second pipeline thread verifies the signature of the second transaction block in the transaction block processing queue, so that the parallel processing of the transaction block can be realized, the processing time of the transaction block is reduced, and the processing efficiency of the transaction block is improved.
- This embodiment provides a method for processing blockchain transactions, that is, when a transaction processing instruction is received, the transaction blocks packaged in the blockchain ordering node are obtained, and each transaction block is sequentially added to the transaction block processing queue;
- the first-rate pipeline thread performs signature verification, multi-version checking, and persistence processing on the first transaction block in the transaction block processing queue; when a preset event is detected, the second pipeline thread processes the transaction block in the queue Perform signature verification, multi-version checking, and persistence processing on the second transaction block of the transaction block, wherein the occurrence time of the preset event is not greater than the end time of the signature verification of the first transaction block, so that the transaction block is processed in parallel.
- the present invention allocates each transaction block in the blockchain to multiple pipeline threads to process the transaction blocks in parallel through multiple pipeline threads, which not only increases the throughput of the blockchain, but also reduces the transaction processing delay. It also improves resource utilization and transaction processing efficiency, and solves the technical problem of low transaction processing efficiency of existing blockchain transactions.
- FIG. 3 is a schematic flowchart of a second embodiment of a method for processing blockchain transactions in this application.
- the step S30 specifically includes:
- Step S31 When the unlock signal of the first stage mutex of the first transaction block is detected, the second pipeline thread adds the first stage mutex to the second transaction block in the transaction processing queue to Adding a verification signature identifier to the second transaction block;
- the verification signature of the second transaction block is started by the second pipeline thread. That is, when the unlock signal of the first phase mutex lock of the first transaction block is detected, the verification signature of the second transaction block is started.
- the multi-version check of the second transaction block needs to be started after the multi-version check of the first transaction block. Since the verification signature time is much longer than the multi-version check and persistence time, the second transaction block starts to verify the signature when the first transaction block starts the multi-version check, and when the verification signature of the second transaction block ends, the first transaction block The multi-version check and persistence of one transaction block have also been completed, and the second transaction block can continue the multi-version check and persistence processing. Therefore, it is possible to start the second pipeline thread to add the first-stage mutex to the second transaction block in the transaction processing queue by detecting whether the first-stage mutex of the first transaction block generates an unlock signal. Add a verification signature identifier to the second transaction block.
- Step S32 verify the signature of the second transaction block through the second pipeline thread, and when the completion of the verification signature of the second transaction block is detected, mutually exclusive the first stage of the second transaction block Lock to unlock;
- the first-stage processing that is, signature verification
- the first phase mutex lock of the second transaction block is unlocked.
- Step S33 When the unlock signal of the first-stage mutex of the second transaction block is detected, the second-stage mutex is added to the second transaction block through the second pipeline thread, so as to The second transaction block performs multi-version checking and persistent identification;
- the second pipeline thread when the unlock signal of the first stage of the second transaction block is detected, the second pipeline thread continues to add the second stage mutex to the second transaction block to declare the second transaction block.
- the pipeline thread is performing a multi-version check operation on the second transaction block, and the second transaction block is currently locked and cannot be processed by other threads.
- Step S34 Perform multi-version check and persistence identification on the second transaction block through the second pipeline thread, and when the multi-version check and persistence completion instruction of the second transaction block are detected, all The second phase mutex lock of the second transaction block is unlocked.
- the second pipeline thread can perform multi-version checking and persistent identification on the second transaction block.
- the second pipeline thread completes the multi-version check and persistence processing of the second transaction block, unlock the second-stage mutex, and generate an unlock signal corresponding to the second-stage mutex.
- FIG. 4 is a schematic flowchart of a third embodiment of a method for processing blockchain transactions in this application.
- the step S30 specifically includes:
- Step S35 when the lock signal of the first phase mutex lock of the first transaction block is detected, verify the signature of the second transaction block in the transaction block processing queue through the second pipeline thread;
- the second-stage mutex is added to the first transaction block through the first pipeline thread
- the specific steps of performing multi-version check and persistent identification on the first transaction block are: when the unlock signal of the first-stage mutex lock of the first transaction block is detected, pass the first pipeline thread Add a second-stage mutex lock to the first transaction block to add a multi-version check identifier to the first transaction block; perform multi-version check on the first transaction block through the first pipeline thread, and When the completion instruction of the multi-version check of the first transaction block is detected, unlock the second phase mutex of the first transaction block; when the second phase mutex of the first transaction block is detected When the lock is unlocked, the third-stage mutex lock is added to the first transaction block through the first pipeline thread to add a persistent identifier to the first transaction block; and the first pipeline thread pairs The first transaction block performs persistence processing, and when a completion instruction of the persistence processing of the first transaction block
- the verification signature of the transaction block is much longer than the time of multi-version checking and persistence processing, and the verification signature of the transaction block is not related.
- the verification corresponding to each transaction block is processed in parallel Sign, and then collect the verification signature results of each transaction block, and perform the multi-version check and persistence processing of each transaction in turn according to the verification signature results and the transaction processing sequence. That is, when the lock signal of the first phase mutex of the first transaction block is detected, the verification signature of the second transaction block is started.
- Step S36 When the unlock signal of the second-stage mutex lock of the first transaction block is detected, perform multi-version checking and persistence processing on the second transaction block through the second pipeline thread.
- the steps of performing signature verification, multi-version checking, and persistence processing on the second transaction block in the transaction block processing queue through the second pipeline thread may also be:
- the processing time of the verification signature of the first transaction block is taken as the first processing time. Then, the processing time for verifying the signature of the second transaction block is estimated as the second processing time.
- the first processing time for controlling the first pipeline thread to process the first transaction block is the same as the second processing time for the second pipeline thread to process the second transaction block, that is, the first transaction block is processed by the first pipeline thread
- the second pipeline thread has just processed the verification signatures of the second transaction block, so that the second transaction can be performed when the multi-version check of the first transaction block has just ended Multi-version checking of blocks.
- the verification signature of the first transaction block and the first processing time required for multi-version checking are determined, the second processing time required for the verification signature of the second transaction block is determined, and the first transaction block is calculated.
- the embodiment of the present application also provides a blockchain transaction processing device.
- the device for processing blockchain transactions includes:
- the transaction block adding module is used to obtain the transaction blocks packaged in the blockchain ordering node when receiving the transaction processing instruction, and add each transaction block to the transaction block processing queue in turn;
- the first processing module is configured to perform signature verification, multi-version checking, and persistence processing on the first transaction block in the transaction block processing queue through the first pipeline thread;
- the second processing module is used to perform signature verification, multi-version checking, and persistence processing on the second transaction block in the transaction block processing queue through the second pipeline thread when a preset event is detected.
- the occurrence time of the preset event is not greater than the end time of the verification signature of the first transaction block, so that the transaction block is processed in parallel.
- the first processing module is also used for:
- the first transaction block is verified and signed by the first pipeline thread, and when the completion instruction of the verification signature of the first transaction block is detected, the first phase mutex of the first transaction block is locked Unlock
- the second-stage mutex is added to the first transaction block through the first pipeline thread, and the first transaction block is passed through The pipeline thread performs multi-version checking and persistence processing on the first transaction block.
- the first processing module is also used for:
- Parse the first transaction block obtain each transaction in the first transaction block, and obtain the transaction request second flow rate, current load status information and preset processing value of each transaction;
- the second processing module specifically includes:
- the first-stage locking unit is used to add a first transaction block to the second transaction block in the transaction processing queue through the second pipeline thread when the unlock signal of the first-stage mutex lock of the first transaction block is detected.
- Phase mutex lock to add a verification signature identifier to the second transaction block;
- the first-stage unlocking unit is used to verify the signature of the second transaction block through the second pipeline thread, and when the completion of the second transaction block verification signature is detected, the second transaction block The first phase of the mutex is unlocked;
- the second-stage locking unit is configured to add a second-stage mutual exclusion lock to the second transaction block through the second pipeline thread when the unlock signal of the first-stage mutex of the second transaction block is detected.
- Exclusion lock to perform multi-version checking and persistent identification of the second transaction block;
- the second-stage processing unit is configured to perform multi-version check and persistence identification on the second transaction block through the second pipeline thread, and to detect the completion of the multi-version check and persistence of the second transaction block When instructing, unlock the second phase mutex lock of the second transaction block.
- the second processing module specifically further includes:
- the first parallel processing unit is configured to process the second transaction block in the transaction block queue through the second pipeline thread when the lock signal of the first phase mutex lock of the first transaction block is detected Perform verification signature;
- the second parallel processing unit is configured to perform multi-version checking and persistence on the second transaction block through the second pipeline thread when the unlock signal of the second phase mutex lock of the first transaction block is detected deal with.
- the second processing module is also used for:
- the second transaction block in the transaction block processing queue is subjected to verification signature, multi-version check, and persistence processing through a second pipeline thread.
- each module in the above-mentioned block chain transaction processing device corresponds to each step in the above-mentioned block chain transaction processing method embodiment, and its functions and implementation processes are not repeated here.
- the embodiments of the present application also provide a computer-readable storage medium, and the computer-readable storage medium may be a non-volatile readable storage medium.
- the computer-readable storage medium of the present application stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the steps of the above-mentioned blockchain transaction processing method are realized.
- the method implemented when the computer readable instruction is executed can refer to the various embodiments of the blockchain transaction processing method of the present application, which will not be repeated here.
Abstract
Description
Claims (20)
- 一种区块链事务的处理方法,其中,所述区块链事务的处理方法包括以下步骤:在接收到事务处理指令时,获取区块链排序节点中打包的事务块,并将各个事务块依次添加至事务块处理队列;通过第一流水线线程对所述事务块处理队列中的第一事务块进行验证签名、多版本检查以及持久化处理;在检测到预设事件发生时,通过第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名、多版本检查以及持久化处理,其中,所述预设事件的发生时间不大于所述第一事务块的验证签名的结束时间,以将事务块进行并行处理。
- 如权利要求1所述的区块链事务的处理方法,其中,所述通过第一流水线线程对所述事务块处理队列中的第一事务块进行验证签名、多版本检查以及持久化处理的步骤具体包括:通过所述第一流水线线程对所述事务处理队列中的第一事务块添加第一阶段互斥锁,以对所述第一事务块添加验证签名标识;通过所述第一流水线线程对所述第一事务块进行验证签名,并在检测到所述第一事务块的验证签名的完成指令时,将所述第一事务块的第一阶段互斥锁进行解锁;在检测到所述第一事务块的第一阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第二阶段互斥锁,并通过所述第一流水线线程对所述第一事务块进行多版本检查以及持久化处理。
- 如权利要求2所述的区块链事务的处理方法,其中,所述在检测到预设事件发生时,通过第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名、多版本检查以及持久化处理的步骤具体包括:在检测到第一事务块的第一阶段互斥锁的解锁信号时,通过所述第二流水线线程对所述事务处理队列中的第二事务块添加第一阶段互斥锁,以对所述第二事务块添加验证签名标识;通过所述第二流水线线程对所述第二事务块进行验证签名,并在检测到所述第二事务块验证签名的完成时,将所述第二事务块的第一阶段互斥锁进行解锁;在检测到所述第二事务块的第一阶段互斥锁的解锁信号时,通过所述第二流水线线程的对所述第二事务块添加第二阶段互斥锁,以对所述第二事务块进行多版本检查以及持久化标识;通过所述第二流水线线程对所述第二事务块进行多版本检查以及持久化标识,并在检测到所述第二事务块的多版本检查以及持久化的完成指令时,将所述第二事务块的第二阶段互斥锁进行解锁。
- 如权利要求2所述的区块链事务的处理方法,其中,所述在检测到所述第一事务块的第一阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第二阶段互斥锁,以对所述第一事务块进行多版本检查以及持久化标识的步骤具体包括:在检测到所述第一事务块的第一阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第二阶段互斥锁,以对所述第一事务块添加多版本检查标识;通过所述第一流水线线程对所述第一事务块进行多版本检查,并在检测到所述第一事务块的多版本检查的完成指令时,将所述第一事务块的第二阶段互斥锁进行解锁;在检测到所述第一事务块的第二阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第三阶段互斥锁,以对所述第一事务块添加持久化标识;通过所述第一流水线线程对所述第一事务块进行持久化处理,并在检测到所述第一事务块的持久化处理的完成指令时,将所述第一事务块的第三阶段互斥锁进行解锁。
- 如权利要求4所述的区块链事务的处理方法,其中,所述在检测到预设事件发生时,通过第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名、多版本检查以及持久化处理的步骤具体包括:在检测到所述第一事务块的第一阶段互斥锁的加锁信号时,通过所述第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名;在检测到所述第一事务块的第二阶段互斥锁的解锁信号时,通过所述第二流水线线程对所述第二事务块进行多版本检查以及持久化处理。
- 如权利要求4所述的区块链事务的处理方法,其中,所述在检测到预设事件发生时,通过第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名、多版本检查以及持久化处理的步骤包括:确定所述第一事务块的验证签名以及多版本检查所需的第一处理时间,确定所述第二事务块的验证签名所需的第二处理时间,并计算出所述第一处理时间以及第二处理时间的时间差值;在检测到所述第一事务块的处理时间达到所述时间差值时,通过第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名、多版本检查以及持久化处理。
- 如权利要求1所述的区块链事务的处理方法,其中,所述通过第一流水线线程对所述事务块处理队列中的第一事务块进行验证签名、多版本检查以及持久化处理的步骤具体包括:对所述第一事务块进行解析,获取所述第一事务块中的各个事务,并获取各个事务的事务请求秒流量、当前负载状况信息及预设的处理值;基于所述事务请求秒流量、当前负载状况信息及预设的处理值,建立多个线程,并通过所述多个线程对所述各个事务进行并行验签签名;在完成所述各个事务的并行验签签名时,收集所述多个线程中的各个验签签名结果,并根据所述各个验签签名结果以及事务处理顺序,依次对各个事务依次执行多版本检查和事务持久化处理。
- 一种区块链事务的处理装置,其中,所述区块链事务的处理装置包括:事务块添加模块,用于在接收到事务处理指令时,获取区块链排序节点中打包的事务块,并将各个事务块依次添加至事务块处理队列;第一处理模块,用于通过第一流水线线程对所述事务块处理队列中的第一事务块进行验证签名、多版本检查以及持久化处理;第二处理模块,用于在检测到预设事件发生时,通过第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名、多版本检查以及持久化处理,其中,所述预设事件的发生时间不大于所述第一事务块的验证签名的结束时间,以将事务块进行并行处理。
- 如权利要求8所述的区块链事务的处理装置,其中,所述第一处理模块还用于:通过所述第一流水线线程对所述事务处理队列中的第一事务块添加第一阶段互斥锁,以对所述第一事务块添加验证签名标识;通过所述第一流水线线程对所述第一事务块进行验证签名,并在检测到所述第一事务块的验证签名的完成指令时,将所述第一事务块的第一阶段互斥锁进行解锁;在检测到所述第一事务块的第一阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第二阶段互斥锁,并通过所述第一流水线线程对所述第一事务块进行多版本检查以及持久化处理。
- 如权利要求8所述的区块链事务的处理装置,其中,所述第一处理模块还用于:对所述第一事务块进行解析,获取所述第一事务块中的各个事务,并获取各个事务的事务请求秒流量、当前负载状况信息及预设的处理值;基于所述事务请求秒流量、当前负载状况信息及预设的处理值,建立多个线程,并通过所述多个线程对所述各个事务进行并行验签签名;在完成所述各个事务的并行验签签名时,收集所述多个线程中的各个验签签名结果,并根据所述各个验签签名结果以及事务处理顺序,依次对各个事务依次执行多版本检查和事务持久化处理。
- 如权利要求8所述的区块链事务的处理装置,其中,所述第二处理模块具体还包括:第一并行处理单元,用于在检测到所述第一事务块的第一阶段互斥锁的加锁信号时,通过所述第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名;第二并行处理单元,用于在检测到所述第一事务块的第二阶段互斥锁的解锁信号时,通过所述第二流水线线程对所述第二事务块进行多版本检查以及持久化处理。
- 如权利要求8所述的区块链事务的处理装置,其中,所述第二处理模块还用于:确定所述第一事务块的验证签名以及多版本检查所需的第一处理时间,确定所述第二事务块的验证签名所需的第二处理时间,并计算出所述第一处理时间以及第二处理时间的时间差值;在检测到所述第一事务块的处理时间达到所述时间差值时,通过第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名、多版本检查以及持久化处理。
- 一种区块链事务的处理设备,其中,所述区块链事务的处理设备包括处理器、存储器、以及存储在所述存储器上并可被所述处理器执行的计算机可读指令,其中所述计算机可读指令被所述处理器执行时,实现如下步骤在接收到事务处理指令时,获取区块链排序节点中打包的事务块,并将各个事务块依次添加至事务块处理队列;通过第一流水线线程对所述事务块处理队列中的第一事务块进行验证签名、多版本检查以及持久化处理;在检测到预设事件发生时,通过第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名、多版本检查以及持久化处理,其中,所述预设事件的发生时间不大于所述第一事务块的验证签名的结束时间,以将事务块进行并行处理。
- 如权利要求13所述的区块链事务的处理设备,其中,所述通过第一流水线线程对所述事务块处理队列中的第一事务块进行验证签名、多版本检查以及持久化处理的步骤具体包括:通过所述第一流水线线程对所述事务处理队列中的第一事务块添加第一阶段互斥锁,以对所述第一事务块添加验证签名标识;通过所述第一流水线线程对所述第一事务块进行验证签名,并在检测到所述第一事务块的验证签名的完成指令时,将所述第一事务块的第一阶段互斥锁进行解锁;在检测到所述第一事务块的第一阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第二阶段互斥锁,并通过所述第一流水线线程对所述第一事务块进行多版本检查以及持久化处理。
- 如权利要求14所述的区块链事务的处理设备,其中,所述在检测到预设事件发生时,通过第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名、多版本检查以及持久化处理的步骤具体包括:在检测到第一事务块的第一阶段互斥锁的解锁信号时,通过所述第二流水线线程对所述事务处理队列中的第二事务块添加第一阶段互斥锁,以对所述第二事务块添加验证签名标识;通过所述第二流水线线程对所述第二事务块进行验证签名,并在检测到所述第二事务块验证签名的完成时,将所述第二事务块的第一阶段互斥锁进行解锁;在检测到所述第二事务块的第一阶段互斥锁的解锁信号时,通过所述第二流水线线程的对所述第二事务块添加第二阶段互斥锁,以对所述第二事务块进行多版本检查以及持久化标识;通过所述第二流水线线程对所述第二事务块进行多版本检查以及持久化标识,并在检测到所述第二事务块的多版本检查以及持久化的完成指令时,将所述第二事务块的第二阶段互斥锁进行解锁。
- 如权利要求14所述的区块链事务的处理设备,其中,所述在检测到所述第一事务块的第一阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第二阶段互斥锁,以对所述第一事务块进行多版本检查以及持久化标识的步骤具体包括:在检测到所述第一事务块的第一阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第二阶段互斥锁,以对所述第一事务块添加多版本检查标识;通过所述第一流水线线程对所述第一事务块进行多版本检查,并在检测到所述第一事务块的多版本检查的完成指令时,将所述第一事务块的第二阶段互斥锁进行解锁;在检测到所述第一事务块的第二阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第三阶段互斥锁,以对所述第一事务块添加持久化标识;通过所述第一流水线线程对所述第一事务块进行持久化处理,并在检测到所述第一事务块的持久化处理的完成指令时,将所述第一事务块的第三阶段互斥锁进行解锁。
- 一种计算机可读存储介质,其中,所述计算机可读存储介质上存储有计算机可读指令,其中所述计算机可读指令被处理器执行时,实现如下步骤:在接收到事务处理指令时,获取区块链排序节点中打包的事务块,并将各个事务块依次添加至事务块处理队列;通过第一流水线线程对所述事务块处理队列中的第一事务块进行验证签名、多版本检查以及持久化处理;在检测到预设事件发生时,通过第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名、多版本检查以及持久化处理,其中,所述预设事件的发生时间不大于所述第一事务块的验证签名的结束时间,以将事务块进行并行处理。
- 如权利要求17所述的计算机可读存储介质,其中,所述通过第一流水线线程对所述事务块处理队列中的第一事务块进行验证签名、多版本检查以及持久化处理的步骤具体包括:通过所述第一流水线线程对所述事务处理队列中的第一事务块添加第一阶段互斥锁,以对所述第一事务块添加验证签名标识;通过所述第一流水线线程对所述第一事务块进行验证签名,并在检测到所述第一事务块的验证签名的完成指令时,将所述第一事务块的第一阶段互斥锁进行解锁;在检测到所述第一事务块的第一阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第二阶段互斥锁,并通过所述第一流水线线程对所述第一事务块进行多版本检查以及持久化处理。
- 如权利要求18所述的计算机可读存储介质,其中,所述在检测到预设事件发生时,通过第二流水线线程对所述事务块处理队列中的第二事务块进行验证签名、多版本检查以及持久化处理的步骤具体包括:在检测到第一事务块的第一阶段互斥锁的解锁信号时,通过所述第二流水线线程对所述事务处理队列中的第二事务块添加第一阶段互斥锁,以对所述第二事务块添加验证签名标识;通过所述第二流水线线程对所述第二事务块进行验证签名,并在检测到所述第二事务块验证签名的完成时,将所述第二事务块的第一阶段互斥锁进行解锁;在检测到所述第二事务块的第一阶段互斥锁的解锁信号时,通过所述第二流水线线程的对所述第二事务块添加第二阶段互斥锁,以对所述第二事务块进行多版本检查以及持久化标识;通过所述第二流水线线程对所述第二事务块进行多版本检查以及持久化标识,并在检测到所述第二事务块的多版本检查以及持久化的完成指令时,将所述第二事务块的第二阶段互斥锁进行解锁。
- 如权利要求17所述的计算机可读存储介质,其中,所述在检测到所述第一事务块的第一阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第二阶段互斥锁,以对所述第一事务块进行多版本检查以及持久化标识的步骤具体包括:在检测到所述第一事务块的第一阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第二阶段互斥锁,以对所述第一事务块添加多版本检查标识;通过所述第一流水线线程对所述第一事务块进行多版本检查,并在检测到所述第一事务块的多版本检查的完成指令时,将所述第一事务块的第二阶段互斥锁进行解锁;在检测到所述第一事务块的第二阶段互斥锁的解锁信号时,通过所述第一流水线线程的对所述第一事务块添加第三阶段互斥锁,以对所述第一事务块添加持久化标识;通过所述第一流水线线程对所述第一事务块进行持久化处理,并在检测到所述第一事务块的持久化处理的完成指令时,将所述第一事务块的第三阶段互斥锁进行解锁。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910375885.6A CN110245006B (zh) | 2019-05-07 | 2019-05-07 | 区块链事务的处理方法、装置、设备及存储介质 |
CN201910375885.6 | 2019-05-07 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020224251A1 true WO2020224251A1 (zh) | 2020-11-12 |
Family
ID=67883744
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/122054 WO2020224251A1 (zh) | 2019-05-07 | 2019-11-29 | 区块链事务的处理方法、装置、设备及存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110245006B (zh) |
WO (1) | WO2020224251A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112636915A (zh) * | 2020-11-27 | 2021-04-09 | 杭州趣链科技有限公司 | 基于国密sm2算法的批量签名验证方法、装置、设备及介质 |
CN113518384A (zh) * | 2021-07-29 | 2021-10-19 | 中移(杭州)信息技术有限公司 | 分布式事务处理方法、装置、设备及计算机可读存储介质 |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110245006B (zh) * | 2019-05-07 | 2023-05-02 | 深圳壹账通智能科技有限公司 | 区块链事务的处理方法、装置、设备及存储介质 |
US11095431B2 (en) * | 2019-12-13 | 2021-08-17 | DLT Global, Inc. | Blockchain transaction manager |
CN111984421B (zh) * | 2020-09-03 | 2022-09-16 | 深圳壹账通智能科技有限公司 | 数据处理方法、装置及存储介质 |
CN111985928A (zh) * | 2020-09-03 | 2020-11-24 | 深圳壹账通智能科技有限公司 | 一种验证方法、装置、电子设备和存储介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140365597A1 (en) * | 2013-06-07 | 2014-12-11 | International Business Machines Corporation | Processing Element Data Sharing |
CN109271245A (zh) * | 2018-09-13 | 2019-01-25 | 腾讯科技(深圳)有限公司 | 一种区块处理任务的控制方法和装置 |
CN109344172A (zh) * | 2018-08-31 | 2019-02-15 | 深圳市元征科技股份有限公司 | 一种高并发数据处理方法、装置及客户端服务器 |
CN110245006A (zh) * | 2019-05-07 | 2019-09-17 | 深圳壹账通智能科技有限公司 | 区块链事务的处理方法、装置、设备及存储介质 |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102880507A (zh) * | 2012-09-12 | 2013-01-16 | 科立讯通信股份有限公司 | 一种链式结构消息申请及分发的方法 |
CN102945278B (zh) * | 2012-11-09 | 2015-12-09 | 华为技术有限公司 | 一种数据库记录重做日志的方法和装置 |
US10437630B2 (en) * | 2016-04-10 | 2019-10-08 | Bank Of America Corporation | System for transforming large scale electronic processing using application block chain and multi-structured data stores |
CN107766127B (zh) * | 2016-08-23 | 2021-07-06 | 阿里巴巴集团控股有限公司 | 事务消息处理方法、装置、设备及系统 |
US10445302B2 (en) * | 2017-01-03 | 2019-10-15 | International Business Machines Corporation | Limiting blockchain size to optimize performance |
CN107360206B (zh) * | 2017-03-29 | 2020-03-27 | 创新先进技术有限公司 | 一种区块链共识方法、设备及系统 |
CN106980544B (zh) * | 2017-03-31 | 2020-03-03 | 北京奇艺世纪科技有限公司 | 一种线程同步方法及线程同步系统 |
CN108805561B (zh) * | 2017-04-27 | 2023-06-02 | 中思博安科技(北京)有限公司 | 可访问多个区块链的智能合约的执行方法和系统 |
US10896169B2 (en) * | 2017-05-12 | 2021-01-19 | International Business Machines Corporation | Distributed system, computer program product and method |
US10289456B2 (en) * | 2017-06-01 | 2019-05-14 | International Business Machines Corporation | Software bot conflict-resolution service agent |
JP7212266B2 (ja) * | 2017-06-05 | 2023-01-25 | バランスド メディア テクノロジー エルエルシー | タスクを共同処理するためのプラットフォーム |
CN107729137B (zh) * | 2017-09-04 | 2021-06-22 | 深圳壹账通智能科技有限公司 | 服务器、区块链验签解密的方法及存储介质 |
CN107992356B (zh) * | 2017-12-13 | 2021-09-14 | 深圳壹账通智能科技有限公司 | 区块链事务区块处理方法、电子装置及可读存储介质 |
CN108376106A (zh) * | 2018-02-01 | 2018-08-07 | 中国工商银行股份有限公司 | 一种区块链消息反馈方法及系统 |
CN109034802A (zh) * | 2018-08-03 | 2018-12-18 | 克洛斯比尔有限公司 | 用于区块链的权益证明创建方法、设备及可读存储介质 |
CN109522314B (zh) * | 2018-10-16 | 2023-04-14 | 平安科技(深圳)有限公司 | 基于区块链的数据归档方法及终端设备 |
CN109493044A (zh) * | 2018-11-08 | 2019-03-19 | 深圳壹账通智能科技有限公司 | 区块链区块删除方法、装置以及终端设备 |
CN109684091B (zh) * | 2018-12-24 | 2021-04-27 | 杭州迪普科技股份有限公司 | 一种任务处理方法及装置 |
-
2019
- 2019-05-07 CN CN201910375885.6A patent/CN110245006B/zh active Active
- 2019-11-29 WO PCT/CN2019/122054 patent/WO2020224251A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140365597A1 (en) * | 2013-06-07 | 2014-12-11 | International Business Machines Corporation | Processing Element Data Sharing |
CN109344172A (zh) * | 2018-08-31 | 2019-02-15 | 深圳市元征科技股份有限公司 | 一种高并发数据处理方法、装置及客户端服务器 |
CN109271245A (zh) * | 2018-09-13 | 2019-01-25 | 腾讯科技(深圳)有限公司 | 一种区块处理任务的控制方法和装置 |
CN110245006A (zh) * | 2019-05-07 | 2019-09-17 | 深圳壹账通智能科技有限公司 | 区块链事务的处理方法、装置、设备及存储介质 |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112636915A (zh) * | 2020-11-27 | 2021-04-09 | 杭州趣链科技有限公司 | 基于国密sm2算法的批量签名验证方法、装置、设备及介质 |
CN112636915B (zh) * | 2020-11-27 | 2024-03-22 | 杭州趣链科技有限公司 | 基于国密sm2算法的批量签名验证方法、装置、设备及介质 |
CN113518384A (zh) * | 2021-07-29 | 2021-10-19 | 中移(杭州)信息技术有限公司 | 分布式事务处理方法、装置、设备及计算机可读存储介质 |
CN113518384B (zh) * | 2021-07-29 | 2023-12-01 | 中移(杭州)信息技术有限公司 | 分布式事务处理方法、装置、设备及计算机可读存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN110245006A (zh) | 2019-09-17 |
CN110245006B (zh) | 2023-05-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020224251A1 (zh) | 区块链事务的处理方法、装置、设备及存储介质 | |
WO2021003975A1 (zh) | 网关接口测试方法、终端设备、存储介质及装置 | |
WO2016137304A1 (en) | Trust-zone-based end-to-end security | |
WO2019093574A1 (ko) | 해시 기반 서명 기법을 적용한 블록체인 시스템 및 방법 | |
WO2018036167A1 (zh) | 测试任务执行机分配方法、装置、服务器和存储介质 | |
WO2020029585A1 (zh) | 基于迁移学习的神经网络联邦建模方法、设备及存储介质 | |
WO2020224249A1 (zh) | 基于区块链的事务处理方法、装置、设备及存储介质 | |
WO2020220413A1 (zh) | 个人信息的零知识证明方法、系统及存储介质 | |
WO2020119115A1 (zh) | 数据审核方法、装置、设备及存储介质 | |
WO2020253116A1 (zh) | 数据跑批方法、装置、存储介质及集群中的成员主机 | |
WO2020224246A1 (zh) | 基于区块链的数据管理方法、装置、设备和存储介质 | |
WO2019109957A1 (zh) | 基于esb的服务提供方法、装置、设备及可读存储介质 | |
WO2019132272A1 (ko) | 블록체인 기반의 서비스로서의 아이디 | |
WO2018035929A1 (zh) | 一种验证码的处理方法及装置 | |
WO2020224250A1 (zh) | 智能合约的触发方法、装置、设备及存储介质 | |
WO2018036168A1 (zh) | 数据处理任务执行方法、装置、执行服务器和存储介质 | |
WO2020042464A1 (zh) | 数据交互方法、装置、设备及可读存储介质 | |
WO2020233089A1 (zh) | 测试用例生成方法、装置、终端及计算机可读存储介质 | |
WO2020233057A1 (zh) | 文件打包方法、装置、设备及存储介质 | |
WO2020233073A1 (zh) | 区块链环境检测方法、设备、装置及存储介质 | |
WO2020062661A1 (zh) | 合同数据一致性的核实方法、装置、设备及存储介质 | |
WO2020119369A1 (zh) | 智能it运维故障定位方法、装置、设备及可读存储介质 | |
WO2011065660A4 (ko) | 계산 시뮬레이션 모사 시스템 및 그 방법 | |
WO2020019405A1 (zh) | 数据库监控方法、装置、设备及可读存储介质 | |
WO2020062658A1 (zh) | 合同生成方法、装置、设备及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19927995 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19927995 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 18/03/2022) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19927995 Country of ref document: EP Kind code of ref document: A1 |