Abstract

ABSTRACT Disclosed herein are methods, systems, and apparatus, including computer programs encoded on computer storage media, for performing allocation of M resources among N users into K pools by solving a knapsack problem (KP) using a distributed computing systern that includes a number of individual solvers. The method includes: receiving data representing K global constraints and L local constraints of the KP; decomposing the KP into N sub-problems using K dual multipliers, each of the N sub-problems corresponding to a respective one of the N users and subject to the L local constraints w.r.t. the corresponding user, wherein N is in an order of billions or larger; determining the number of individual solvers for solving the N sub- problems; distributing the N sub-problems among the number of individual solvers; and solving the KP by the distributed computing systern by performing two or more iterations. Date Recue/Date Received 2020-12-03

IPC Classes  ?

• G06F 17/11 - Complex mathematical operations for solving equations
• G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs

Abstract

Disclosed is an electronic certificate-based interaction method, comprising: a client outputs, in response to an interaction operation initiated by a first user, a list of users having social relationships with the first user and holding electronic certificates; the client determines a second user selected by the first user from the list of users, and sends an electronic certificate acquisition request to a server; wherein the electronic certificate acquisition request comprises a user identifier of the second user; the server selects, in response to the electronic certificate acquisition request, a first electronic certificate from the electronic certificates held by the second user, generates a second electronic certificate of which the category is the same as that of the first electronic certificate, and issues to the client the second electronic certificate generated; the client acquirers the second electronic certificate issued by the server and locally stores the second electronic certificate; wherein when the number of categories of the electronic certificates acquired by the client reaches a preset threshold, the first user acquires permission for distributing virtual objects in a preset virtual object set.

IPC Classes  ?

• G06Q 20/38 - Payment architectures, schemes or protocols - Details thereof

Abstract

Disclosed herein are methods, systems, and apparatus, including computer programs encoded on computer storage media, for performing counterfactual regret minimization (CFR) for strategy searching in strategic interaction between parties. One of the methods includes: identifying N1 possible actions of a first party in a first state of the first party; sampling a possible action out of the N1 possible actions in the first state of the first party with a first sampling probability; identifying N2 possible actions of the first party in a second state of the first party, wherein the first state of the first party is closer to a beginning state of the IIG than the second state of the first party; sampling a possible action out of the N2 possible actions in the second state of the first party with a second sampling probability, wherein the first sampling probability is less than the second sampling probability.

IPC Classes  ?

• G06N 20/00 - Machine learning

Abstract

Disclosed herein are methods, systems, and apparatus, including computer programs encoded on computer storage media, for performing counterfactual regret minimization (CFR) for strategy searching in strategic interaction between two or more parties. One of the methods includes: storing multiple regret samples in a first data store, wherein the multiple regret samples are obtained in two or more iterations of a CFR algorithm in strategy searching in strategic interaction between two or more parties; storing multiple strategy samples in a second data store; updating parameters of a first neural network for predicting a regret value of a possible action in a state of a party based on the multiple regret samples in the first data store; and updating parameters of a second neural network for predicting a strategy value of a possible action in a state of the party based on the multiple strategy samples in the second data store.

IPC Classes  ?

• G06N 3/02 - Neural networks
• G06F 16/903 - Querying

Abstract

A computer-implemented method includes obtaining a trained convolutional neural network comprising one or more convolutional layers, each of the one or more convolutional layers comprising a plurality of filters with known filter parameters; pre- computing a reusable factor for each of the one or more convolutional layers based on the known filter parameters of the trained convolutional neural network; receiving input data to the trained convolutional neural network; computing an output of the each of the one or more convolutional layers using a Winograd convolutional operator based on the pre-computed reusable factor and the input data; and determining output data of the trained convolutional network based on the output of the each of the one or more convolutional layers.

Abstract

An item rating and recommendation platform identifies rating data comprising respective ratings of multiple items with respect to multiple users, identifies user- feature data comprising multiple user features contributing to the respective ratings of the multiple items with respect to the multiple users, and receives, from a social network platform via a secret sharing scheme with a trusted initializer, manipulated social network data computed based on social network data and first input data from the trusted initializer. The social network data indicate social relationships between any two of the multiple users. In the secret sharing scheme with the trusted initializer, the social network platform shares with the item rating and recommendation platform the manipulated social network data without disclosing the social network data. The item rating and recommendation platform updates the user-feature data based on the rating data and the manipulated social network data.

IPC Classes  ?

• G06Q 50/00 - Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism

Abstract

A computer-implemented method for information protection comprises: determining one or more data inputs and one or more data outputs for a transaction, wherein the data inputs are associated with input data types respectively, and the data outputs are associated with output data types respectively; encrypting the input data types and the output data types; committing each of the encrypted input data types and the encrypted output data types with a commitment scheme to obtain corresponding commitment values; obtaining at least a parameter R based at least on the commitment values; and submitting the transaction to one or more nodes in a blockchain network with disclosure of the parameter R and without disclosure of the input data types and output data types for the nodes to verify consistency between the input data types and the output data types.

IPC Classes  ?

• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

An item rating and recommendation platform identifies rating data including respective ratings of multiple items with respect to multiple users; identifies user- feature data including user features contributing to the respective ratings of the multiple items with respect to the multiple users; and receives, from a social network platform via a secret sharing scheme without a trusted initializer, manipulated social network data computed based on social network data and a first number of random variables. The social network data indicate social relationships between any two of the number of users. In the secret sharing scheme without the trust initializer, the social network platform shares with the item rating and recommendation platform manipulated social network data without disclosing the social network data. The item rating and recommendation platform updates the user-feature data based on the rating data and the manipulated social network data.

IPC Classes  ?

• G06Q 50/00 - Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism

Abstract

Disclosed herein are methods, systems, and apparatus, including computer programs encoded on computer storage media for secure collaborative computation of a matrix product of a first matrix including private data of a first party and a second matrix including private data of the second party by secret sharing without a trusted initializer. One method includes obtaining a first matrix including private data of the first party; generating a first random matrix; identifying a first sub-matrix and a second sub-matrix of the first random matrix; computing first scrambled private data of the first party based on the first matrix, the first random matrix, the first sub-matrix, and the second sub-matrix; receiving second scrambled private data of the second party; computing a first addend of the matrix product; receiving a second addend of the matrix product; and computing the matrix product by summing the first addend and the second addend.

IPC Classes  ?

• G06F 21/60 - Protecting data
• G06F 17/16 - Matrix or vector computation

Abstract

A threshold determining and identity verification method to achieve a balance between user experience and risk control. Weak identity verification demands of inactive users can be satisfied, and the users who need strong identity verification can be identified from the inactive users. The threshold determining method includes obtaining predetermined target values respectively corresponding to multiple identification models for identity verification, where the predetermined target values are used to indicate expected target identification capabilities of the identification models for identity verification; and determining user service variable values and identity verification thresholds respectively corresponding to the multiple identification models for identity verification based on the predetermined target values, where the user service variable values are used for classification of active users and inactive users, and the identity verification thresholds are used by the identification models for identity verification to exclude users who need strong verification from the inactive users.

IPC Classes  ?

• G06F 21/31 - User authentication

Abstract

A target transaction comprising invocation data used to initiate the invocation of the smart contract based on a blockchain is received, where at least a part of the invocation data comprises a data digest of target data stored in a third-party storage system interconnected with the blockchain. The target data corresponding to the data digest from the third-party storage system is queried. A query result comprising encrypted target data returned by the third-party storage system is received. A key used to decrypt the encrypted target data is obtained and the encrypted target data is decrypted based on the key. Content verification on decrypted target data is performed. If the verification succeeds, the smart contract is invoked to perform smart contract computation on the invocation data. A computation result is stored in a distributed database of the blockchain after the smart contract computation is completed.

IPC Classes  ?

• G06F 16/24 - Querying
• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• G06F 16/22 - Indexing; Data structures therefor; Storage structures
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G06F 16/903 - Querying

Abstract

One or more implementations of the present specification provide a blockchain- based data processing method and device that are applied to a data center connected to the blockchain. The method includes: synchronizing block data in the blockchain to a local database; receiving a data use request sent by a target application; and in response to the data use request, querying the local database for requested data corresponding to the data use request, and returning the requested data to the target application.

IPC Classes  ?

• G06F 16/90 - Information retrieval; Database structures therefor; File system structures therefor - Details of database functions independent of the retrieved data types

Abstract

Implementations of the present specification disclose blockchain-based smart contract invocation processing. In an implementation, a target transaction comprising invocation data used to initiate invocation of a smart contract is received, and wherein at least a part of the invocation data comprises a data digest of target data stored in a third-party storage system interconnected with a blockchain. The target data corresponding to the data digest is queried from the third-party storage system. A verification of a content on the target data is performed by determining whether an execution condition is satisfied. In response to determining that the verification on the target data succeeds, the smart contract is invoked to perform smart contract computation on the invocation data in the target transaction. A computation result is stored in a distributed database of the blockchain after the smart contract computation is completed.

IPC Classes  ?

• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system
• H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• H04L 67/52 - Network services specially adapted for the location of the user terminal

Abstract

One or more implementations of the present specification relate to the blockchain field, and in particular, to data verification methods and apparatuses, and electronic devices. The method can include: obtaining a data identifier of target data published by a data provider in a blockchain, where the data identifier indicates a storage location of the target data in the blockchain; determining whether the target data has been stored in the blockchain based on the data identifier; if the target data has been stored in the blockchain, obtaining the target data from the storage location indicated by the data identifier, where the target data stored in the blockchain carries verification information used to verify authenticity of the target data; and verifying authenticity of the obtained target data based on the verification information, and outputting a verification result to a data verifier.

IPC Classes  ?

• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system
• G06Q 40/04 - Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

Implementations of the present disclosure provide a service processing method, device, and system associated with unified resource locator (URL)-based two- dimensional (code). In an implementation, a URL is received from a first service institution. The URL is obtained by a mobile device from scanning a 2D code provided by a service provider and sent to the first service institution. The URL is then parsed to identify one or more data elements including a service network identifier, a service institution identifier, and a payload including a service object identifier. The one or more data elements is sent to the second service institution based on the service institution identifier. Service information associated with the service object is received from the second service institution based on the service object identifier, and the service information is sent to the first service institution for presenting on the mobile device.

IPC Classes  ?

• H04W 4/18 - Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]

Abstract

One or more implementations of the present specification provide a financing method and apparatus, applied to a blockchain-based supply chain financial system, where the supply chain financial system includes a light node and a core node. The method includes: publishing, by the light node, a target transaction for financing to the blockchain, where the target transaction includes account receivable information; obtaining, by the core node from the blockchain, a target transaction initiated by the light node for financing; determining, by the core node, a grant limit, a repayment period, and a loan interest rate of financing based on the account receivable information; publishing, by the core node, a smart contract for financing management to the blockchain, where the smart contract specifies the determined grant limit, repayment period, and loan interest rate of the financing; and invoking, by the light node, the smart contract.

Abstract

One or more implementations of the present specification provide a blockchain-based transaction processing method and apparatus, and an electronic device. A target transaction initiated by a member node device in a blockchain is received, where the target transaction includes a reference time parameter, and where the target transaction indicates a transfer of an asset and associated data released by the member node device to the blockchain for transfer to a candidate block. Based on the reference time parameter, a determination is performed as to whether the target transaction is a valid transaction within a transaction validity period. The target transaction is recorded to the candidate block in response to determining that the target transaction is a valid transaction within the transaction validity period.

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
• G06Q 20/38 - Payment architectures, schemes or protocols - Details thereof

Abstract

One or more implementations of the present application provide a blockchain-based transaction processing method and apparatus, and an electronic device. The method can include the following: receiving a target transaction initiated by a member node device in a blockchain, where the target transaction comprises a unique identifier of the target transaction. Whether a transaction idempotent table stores a transaction idempotent record corresponding to the unique identifier of the target transaction is queried. The target transaction is recorded in a candidate block if the transaction idempotent table has not stored the transaction idempotent record corresponding to the unique identifier of the target transaction.

IPC Classes  ?

• G06Q 20/38 - Payment architectures, schemes or protocols - Details thereof
• G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists

Abstract

One or more implementations of the present specification provide a parking fee collection method, apparatus, and an electronic device, applied to a parking fee collection system. The method includes the following: obtaining vehicle information of a parked vehicle in a parking space, where the vehicle information has a corresponding user account on a payment platform; and initiating a payment collection request for the vehicle information to the payment platform each time a parking time period of the parked vehicle in the parking space reaches a first predetermined time period, to collect an asset corresponding to the first predetermined time period.

IPC Classes  ?

• G07B 15/02 - Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points taking into account a variable factor such as distance or time, e.g. for passenger transport, parking systems or car rental systems

Abstract

One or more implementations of the present specification provide a parking charging method, apparatus, and electronic device, applied to a parking charging system. The method includes the following: obtaining vehicle information of a parked vehicle in a parking space, where the vehicle information has a corresponding user account on a payment platform; publishing a vehicle parking record to a blockchain network by using a first blockchain node corresponding to the parking charging system in the blockchain network, where the vehicle parking record includes parking duration of the parked vehicle in the parking space; and performing an asset transfer operation related to the payment platform based on the vehicle parking record each time the parking duration reaches first predetermined duration, so as to charge an asset corresponding to the first predetermined duration.

IPC Classes  ?

• G07B 15/02 - Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points taking into account a variable factor such as distance or time, e.g. for passenger transport, parking systems or car rental systems
• G08G 1/01 - Detecting movement of traffic to be counted or controlled

Abstract

One or more implementations of the present specification provide an open road tolling method, apparatus, and electronic device, applied to a tolling system. The method can include the following: obtaining vehicle information of a driving vehicle on a toll road, where the vehicle information has a corresponding user account on a payment platform; publishing a vehicle travel history to a blockchain network by using a first blockchain node corresponding to the tolling system in the blockchain network, where the vehicle travel history includes a travelled distance of the driving vehicle on the toll road; and performing an asset transfer operation related to the payment platform based on the vehicle travel history each time the travelled distance of the driving vehicle on the toll road reaches a predetermined distance, so as to charge an asset corresponding to the predetermined distance.

IPC Classes  ?

• G07B 15/06 - Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems
• G07B 15/02 - Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points taking into account a variable factor such as distance or time, e.g. for passenger transport, parking systems or car rental systems
• G08G 1/01 - Detecting movement of traffic to be counted or controlled

Abstract

One or more implementations of the present specification provide an asset transfer method and apparatus and an electronic device, which are applied to a blockchain node. The method includes the following: An asset transfer request related to a blockchain member is detected, where the asset transfer request involves transferring an asset of a specified asset type to an asset held by the blockchain member, and the asset to be transferred is issued by a specified anchor in a blockchain. A determination is performed as to whether there is a maximum trusted asset limit that is configured by the blockchain member for the specified anchor and that corresponds to the specified asset type. The asset transfer request is prohibited when the determination is that the maximum trusted asset limit does not exist.

IPC Classes  ?

• G06F 17/00 - Digital computing or data processing equipment or methods, specially adapted for specific functions
• G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

One or more implementations of the present specification provide a blockchain- based commodity claim method and apparatus, and an electronic device. The method can include: collecting appearance data of a target commodity, where the appearance data of the target commodity is registered with a distributed database of a blockchain in advance. Whether a damage event occurred on the target commodity is determined based on the appearance data of the target commodity and the appearance data of the target commodity that is registered with the distributed database in advance. If the determination is yes a smart contract corresponding to the target commodity is invoked. Commodity damage claim logic stated in the smart contract is executed to complete the commodity damage claim for the target commodity.

IPC Classes  ?

• G06Q 40/08 - Insurance
• G06F 16/24 - Querying
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

One or more implementations of the present specification provide blockchain asset issuing and redemption methods and apparatuses, and an electronic device therefor. The method can include the following: determining, by a blockchain anchor, that an off-chain asset of a specified amount is in a frozen state indicating that the off-chain asset is isolated and protected from a plurality of factors. The blockchain anchor issues the blockchain asset on a blockchain, where an amount of the blockchain asset is not greater than the specified amount. The blockchain anchor publishes a transaction record of the blockchain asset in a blockchain ledger containing a freeze certificate for the off-chain asset.

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme

Abstract

One or more implementations of the present specification provide a blockchain transaction reconciliation method and apparatus, and an electronic device. The method can include: obtaining, by a blockchain member, a blockchain transaction record that is selected from a blockchain and satisfies a specified condition. The blockchain member compares the blockchain transaction record with an off-chain transaction record maintained by the blockchain member. Whether the off-chain transaction record is inconsistent with the blockchain transaction record is determined. In response to a determination that the off-chain transaction record is inconsistent with the blockchain transaction record, the blockchain member updates the off-chain transaction record based on the blockchain transaction record.

IPC Classes  ?

• G06F 16/21 - Design, administration or maintenance of databases
• G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

Blockchain-based virtual resource delivery and crowdfunding methods and devices are disclosed. In a blockchain network, a delivery node can obtain a category identifier and a resource amount specified by a user, and then initiate a transaction based on the category identifier and the resource amount. After the transaction passes consensus verification performed by a plurality of nodes, the plurality of nodes establish a first correspondence between the category identifier and virtual resources of the resource amount, and store the first correspondence in a shared ledger of the nodes. For each project category, the virtual resources corresponding to the project category can be converted into assets for funding the crowdfunding project corresponding to the project category.

IPC Classes  ?

• G06Q 40/04 - Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
• G06Q 40/06 - Asset management; Financial planning or analysis

Abstract

One or more implementations of the present specification provide a blockchain- based copyright revenue allocation method and apparatus. The method includes; receiving a target transaction initiated by a member node device in a blockchain, where the target transaction corresponds to a copyright usage event of a target work; and invoking a smart contract corresponding to copyright revenue allocation of the target work, executing copyright revenue allocation logic that is declared in the smart contract and that corresponds to the copyright usage event, and allocating copyright revenue to a copyright beneficiary of the target work in the form of a transaction, where the smart contract is generated based on copyright status information that is associated with the target work and that is issued to the blockchain.

IPC Classes  ?

• G06Q 40/04 - Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

Information data released on a blockchain network is obtained, where the information data is released on the blockchain network by a plurality of device nodes provided with sensors, where the information data comprises a parameter related to a resource value, where the blockchain network comprises the plurality of device nodes provided with the sensors, and where the sensors are configured to perceive or collect the parameter related to the resource value. Whether a parameter value in the information data exceeds a predetermined threshold or a threshold range is determined. In response to determining that the parameter value in the information data exceeds the predetermined threshold or the threshold range, the resource value is calculated using resource value evaluation logic.

IPC Classes  ?

• G06F 17/00 - Digital computing or data processing equipment or methods, specially adapted for specific functions
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G06Q 40/03 - Credit; Loans; Processing thereof
• G06N 20/00 - Machine learning
• G16Y 40/10 - Detection; Monitoring

Abstract

One or more implementations of the present specification provide a blockchain-based music originality analysis method and apparatus. In an implementation, a music file published on a blockchain network comprising a music library node and a music analyzer node is obtained by the music library node. An originality analysis is performed by the music library node on the music file based on a local music library to obtain a first originality and analysis digest that is used to indicate an originality and analysis result. The music library node publishes the first originality and analysis digest to the blockchain network to record and authenticate the originality and analysis result. The music analyzer node obtains and summarizes the first originality and analysis digest to obtain a second originality and analysis digest and performs processing of a service related to originality of the music file based on the second originality and analysis digest.

IPC Classes  ?

• G06F 21/10 - Protecting distributed programs or content, e.g. vending or licensing of copyrighted material
• G10L 25/54 - Speech or voice analysis techniques not restricted to a single one of groups specially adapted for particular use for comparison or discrimination for retrieval
• G06F 16/65 - Clustering; Classification
• G10G 1/00 - Means for the representation of music

Abstract

The present application discloses a resource transfer method, a fund payment method, and an electronic device. The resource transfer method includes: obtaining a face image of a resource transferor, where the face image is used to authenticate an identity of the resource transferor, and obtaining resource transfer identification information of the resource transferor, where the resource transfer identification information corresponds to a transferor account of the resource transferor; determining, based on the resource transfer identification information, information about the transferor account and a reference image corresponding to the transferor account; and transferring a resource of the resource transferor based on the information about the transferor account when the face image matches the reference image.

IPC Classes  ?

• G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists
• G06Q 20/10 - Payment architectures specially adapted for home banking systems

Abstract

The present specification discloses a method and an apparatus for offline payment, service processing, and payment processing. When both a collection device and a payment device are in an offline state, the collection device can send payment data to the payment device through a communication connection established to the payment device, so that the payment device can perform payment processing based on the payment data, to obtain a payment result, and return the payment result to the collection device, and the collection device can perform collection processing based on the payment result and obtained account information of the payment device, to obtain a collection result.

IPC Classes  ?

• G06Q 20/22 - Payment schemes or models

Abstract

One or more implementations of the present specification provide cross- blockchain authentication. A subscribing client corresponding to a first blockchain and included in a system for cross-chain interaction obtains a public key of an oracle engine that is used as an authentication data source. By using a cross-chain interaction end, data to be authenticated in a second blockchain and is published by a publishing client corresponding to the second blockchain is obtained, where the data to be authenticated is signed by the oracle engine connected to the second blockchain based on a private key held by the oracle engine. Based on the authentication data source and a signature of the data to be authenticated, data authentication is performed on the data to be authenticated.

IPC Classes  ?

• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system

Abstract

One or more implementations of the present application provide for cross-blockchain interaction. A message generated by a second contract in a second blockchain is determined by a blockchain node in a first blockchain using a cross-blockchain interaction end between the first blockchain and the second blockchain and by using a subscribing client corresponding to the blockchain node, where the subscribing client is configured to maintain a plurality of message queues that are in a one-to-one correspondence with a plurality of blockchain nodes to perform mapping to a corresponding blockchain node by using a message queue. A first contract in the first blockchain is called by the blockchain node to trigger a corresponding contract operation when the message generated by the second contract satisfies a subscription condition of the blockchain node.

IPC Classes  ?

• G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures

Abstract

Implementations of the present specification provide for cross-blockchain authentication. A subscribing client, using a cross-blockchain interaction system cross-chain client, obtains data from a second blockchain published by a publishing client, to use the data as an authentication data source, the cross-blockchain interaction system comprises the subscribing client, the publishing client, and a cross-chain client, the subscribing client corresponds to a first blockchain, the publishing client corresponds to the second blockchain, the cross-chain client is separately interconnected with the subscribing client and the publishing client and the first blockchain are used as a sidechain that is anchored to the second blockchain that is used as a main chain. Data to be authenticated is received from the second blockchain. Data authentication is performed on the data to be authenticated based on the authentication data source and a data authentication rule configured on the first blockchain.

IPC Classes  ?

• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system
• G06Q 20/02 - Payment architectures, schemes or protocols involving a neutral third party, e.g. certification authority, notary or trusted third party [TTP]
• G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
• G06Q 20/38 - Payment architectures, schemes or protocols - Details thereof
• G06F 21/57 - Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures

Abstract

Appearance data of a target entity is collected as appearance data, where the target entity comprises a physical entity capable of accessing, as a member, a blockchain. The appearance data is registered in a distributed database associated with the blockchain as an identity of the target entity. A target transaction initiated by a member node device in the blockchain is received, where the target transaction comprises the appearance data of the target entity that is collected by the member node device and a service event that is related to the target entity and that is detected by the member node device. A smart contract that corresponds to the service event is invoked. Based on the identity indicated by the appearance data of the target entity, a service logic stated in the smart contract is executed.

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G06F 16/23 - Updating

Abstract

A first node of a blockchain receives service data, and first consensus verification is performed on the service data. Whether the first consensus verification on the service data succeeds is determined. In response to determining that the first consensus verification on the service data succeeds, the service data is added to a service queue to be validated, so that a second node selects service data from the service queue to be validated to generate a block, and performs the second consensus verification on the block. In response to determining that the first consensus verification on the service data fails, whether the service data satisfies a predetermined retry condition is determined. If YES, the service data is stored as service data to be retried. The first consensus verification is performed on the service data to be retried when it is determined that a predetermined retry execution condition is triggered.

IPC Classes  ?

• G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists

Abstract

A node device of a blockchain receives a target transaction including transaction content, where at least a part of the transaction content comprises a content summary of target content stored in a third-party storage system connected to the blockchain. The target content corresponding to the content summary is queried from the third-party storage system. The target content is verified based on the content summary of the target content in the target transaction. If the verification of the target content succeeds, the target transaction is executed based on the transaction content in the target transaction. After the target transaction is executed, the target transaction is stored in a distributed database of the blockchain.

IPC Classes  ?

• G06Q 20/02 - Payment architectures, schemes or protocols involving a neutral third party, e.g. certification authority, notary or trusted third party [TTP]
• G06Q 20/38 - Payment architectures, schemes or protocols - Details thereof

Abstract

A blockchain node in a first blockchain initiates a subscription request to a cross-chain interaction end between the first blockchain and a second blockchain. The blockchain node obtains a message from the second blockchain based on the subscription request. The blockchain node executes an operation related to the message.

IPC Classes  ?

• G06Q 40/04 - Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

A node device in a blockchain receives a status update request initiated by a target user for a target asset object. In response to the status update request, a verification is performed as to whether the target user is a member user with update permission for the target asset object in a smart contract object that is published in the blockchain and corresponds to an asset type of the target asset object, where the target asset object is created by invoking the smart contract object. A status update is performed on the target asset object by invoking the smart contract object if the target user is a member user with update permission for the target asset object in the smart contract object.

IPC Classes  ?

• G06F 16/21 - Design, administration or maintenance of databases
• G06F 21/30 - Authentication, i.e. establishing the identity or authorisation of security principals
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

A network node of a blockchain network receives an asset object creation request. In response to the asset object creation request, invoking a smart contract object is invoked, where the smart contract object is deployed in the blockchain network and corresponds to an asset type of an asset object to create the asset object. Address information of the asset object is added to a target object that holds the asset object.

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

A blockchain node in a blockchain network creates an asset container to record field information of an asset object registered on a blockchain ledger. The blockchain node divides corresponding asset containers into at least one asset container group based on an association relationship between asset objects, where an association relationship exists between each asset container in the asset container group and at least one another asset container in the asset container group.

IPC Classes  ?

• G06F 21/00 - Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity

Abstract

One or more implementations of the present specification provide for asset management. One implementation can include receiving, by a node device in a blockchain, an asset object transfer request, where the asset object transfer request comprises a plurality of asset objects to be transferred. In response to the asset object transfer request, combining the plurality of asset objects into a target asset object. Address information of the plurality of asset objects are removed from target objects holding the plurality of asset objects, and address information of the target asset object is added to asset receiving objects corresponding to the plurality of asset objects.

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• H04L 9/30 - Public key, i.e. encryption algorithm being computationally infeasible to invert and users' encryption keys not requiring secrecy

Abstract

A node device in a blockchain receives an asset object conversion request, where the asset object conversion request comprises an asset object of a first asset type to be converted and a second asset type to be obtained after conversion. Upon the asset object conversion request, invoking a contract object published on the blockchain and corresponding to the second asset type is invoked, and the asset object of the first asset type is converted into the asset object of the second asset type. The asset object of the second asset type obtained after conversion is added to a target object that holds the asset object of the first asset type.

IPC Classes  ?

• G06F 21/00 - Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity

Abstract

An asset object transfer request is received y a node device in a blockchain, where the asset object transfer request includes an asset object to be transferred. In response to the asset object transfer request, a contract object that corresponds to an asset type of the asset object to be transferred and that is deployed in the blockchain is invoked. The asset object to be transferred is split into a plurality of target asset objects. Address information of the asset object to be transferred is removed from a target object holding the asset object to be transferred. Address information of the plurality of target asset objects is added to asset receiving objects corresponding to the plurality of target asset objects.

IPC Classes  ?

• H04L 9/14 - Arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms

Abstract

A first member of a blockchain receives a fund flow request for a specified amount between a payer and a payee. The first member determines a fund flow route between the first member and a second member corresponding to the payee in the blockchain, where the fund flow route includes the first member, the second member, and several relay members from the blockchain. A compliance check request is initiated by the first member to at least two other members in the fund flow route, so that the at least two members concurrently perform a compliance check on a fund flow event corresponding to the fund flow request. The first member initiates a fund flow contract operation to complete the fund flow event based on the fund flow route when all compliance check results of the fund flow event of all members in the fund flow route are qualified.

IPC Classes  ?

• G06Q 20/00 - Payment architectures, schemes or protocols

Abstract

A first member of a blockchain receives a request for fund flow of a specified amount between a payer and a payee. The first member determines a fund flow route between the first member and a second member corresponding to the payee in the blockchain, where the fund flow route includes the first member, the second member, and several relay members, and blockchain balances deposited by all members of the fund flow route at all anchor points of the blockchain are registered in a blockchain ledger of the blockchain. The first member initiates a fund flow contract operation, where, after the fund flow contract operation takes effect, the blockchain balances of all the members of the fund flow route registered in the blockchain ledger uniformly change, so that the second member pays funds of the specified amount to the payee.

IPC Classes  ?

• G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
• G06Q 20/10 - Payment architectures specially adapted for home banking systems
• G06Q 20/22 - Payment schemes or models
• G06Q 20/38 - Payment architectures, schemes or protocols - Details thereof
• G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists

Abstract

A regulatory member receives a fund flow report generation request from a target member in a blockchain. Fund flow data of the target member is obtained from the blockchain. Based on a parameter in a specified report template, data corresponding to the parameter in the obtained fund flow data through matching is determined. The matched data is written to the report template to generate a fund flow report of the target member. The fund flow report is pushed to the target member.

Abstract

At least one member of a blockchain queries a blockchain balance deposited on at least one anchor point in the blockchain by the at least one member and changes caused by transactions of blockchain balances deposited on the at least one anchor point by different members. The at least one member initiates a balance adjusting contract operation when a changed amount of the queried blockchain balance reaches a predetermined change threshold, to enable the changed amount to be less than the predetermined change threshold by adjusting the blockchain balance deposited on the at least one anchor point by the at least one member.

IPC Classes  ?

• G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
• G06Q 20/22 - Payment schemes or models
• G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists

Abstract

A supervising member obtains a remittance link involved in a remittance to be inspected from a blockchain, where the remittance link corresponds to members of the remittance to be inspected. The supervising member obtains, from the blockchain, a first inspection result of a compliance inspection performed by at least one member in the remittance link on an inspection document that corresponds to the remittance to be inspected. The supervising member performs a compliance inspection on the inspection document to obtain a second inspection result. The supervising member determines a member whose compliance inspection is abnormal based on the second inspection result and the first inspection result.

IPC Classes  ?

• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• H04L 12/22 - Arrangements for preventing the taking of data from a data transmission channel without authorisation

IPC Classes  ?

• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system
• G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
• G06F 21/57 - Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• H04L 9/14 - Arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms
• H04L 12/16 - Arrangements for providing special services to substations

IPC Classes  ?

• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
• G06F 16/21 - Design, administration or maintenance of databases
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G06F 17/00 - Digital computing or data processing equipment or methods, specially adapted for specific functions
• G06Q 20/00 - Payment architectures, schemes or protocols

IPC Classes  ?

• G06F 40/279 - Recognition of textual entities
• G16H 10/60 - ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records

IPC Classes  ?

• G06F 16/23 - Updating
• G06F 16/22 - Indexing; Data structures therefor; Storage structures
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• G06F 21/32 - User authentication using biometric data, e.g. fingerprints, iris scans or voiceprints
• G06F 21/72 - Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information in cryptographic circuits
• H04L 9/14 - Arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms
• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system

IPC Classes  ?

• G06F 21/60 - Protecting data
• H04L 9/06 - Arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
• H04L 9/08 - Key distribution
• H04L 9/30 - Public key, i.e. encryption algorithm being computationally infeasible to invert and users' encryption keys not requiring secrecy
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• G06F 17/00 - Digital computing or data processing equipment or methods, specially adapted for specific functions
• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• G06F 21/76 - Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information in application-specific integrated circuits [ASIC] or field-programmable devices, e.g. field-programmable gate arrays [FPGA] or programmable logic devices [PLD]
• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• G06F 17/00 - Digital computing or data processing equipment or methods, specially adapted for specific functions
• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
• H04L 9/30 - Public key, i.e. encryption algorithm being computationally infeasible to invert and users' encryption keys not requiring secrecy
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• H04L 12/16 - Arrangements for providing special services to substations

Abstract

)isclosed herein are methods, systems, and apparatus, including computer programs encoded on computer storage media, for product promotion using a smart contract in a blockchain network. The method includes: receiving, by a node of a blockchain network, a creation request to create a promotion event, wherein: the promotion event is associated with multiple promotion codes and a pair of a private key and a public key, and the creation request includes the public key and a digital signature generated using the private key; determining, by the node and based on the public key and the digital signature, validity of the creation request; and in response to determining that the creation request is valid, registering, by the node, the promotion event in the blockchain network using a smart contract without storing the multiple promotion codes in the blockchain network.

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

Disclosed herein are methods, systems, and apparatus, including computer programs encoded on computer storage media, for blockchain network digital ticket transfer. One of the methods includes receiving a request from a client device to transfer a digital ticket from a blockchain network to a target server by a blockchain network node. The blockchain network node determines whether the client device is authorized to transfer the digital ticket based on a digital signature in the request, and transmits a notification message to the target server if the digital signature is valid. The blockchain network node receives a confirmation message from the target server indicating validity of the client device, and transfers the digital ticket to the target server.

IPC Classes  ?

• G06Q 20/38 - Payment architectures, schemes or protocols - Details thereof

IPC Classes  ?

• G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system
• G06F 21/32 - User authentication using biometric data, e.g. fingerprints, iris scans or voiceprints
• G06F 21/56 - Computer malware detection or handling, e.g. anti-virus arrangements

IPC Classes  ?

• H04L 9/14 - Arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms
• G06F 21/31 - User authentication
• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• H04L 9/30 - Public key, i.e. encryption algorithm being computationally infeasible to invert and users' encryption keys not requiring secrecy

IPC Classes  ?

• H04L 9/14 - Arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms
• G06F 21/32 - User authentication using biometric data, e.g. fingerprints, iris scans or voiceprints
• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• H04L 9/06 - Arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system

Abstract

Disclosed herein are methods, systems, and apparatus for performing parallel execution of transactions in a blockchain network. One method includes receiving multiple transactions; determining whether each transaction is a first-type or a second-type transaction; for a first-type transaction, determining accounts affected by the first-type transaction; for a second-type transaction, pre-executing the second-type transaction; and determining accounts affected by the pre-executing the second-type transaction; performing a consensus process of the multiple transactions and the accounts affected by the pre-executing the second-type transaction; dividing the multiple transactions into groups; executing groups of transactions in parallel; committing the executing each first-type transaction; if the each of the accounts affected by the executing a second-type transaction are the same as accounts affected by the pre-executing of the second-type transaction and the accounts affected by the executing the second-type transaction are not affected by any previously

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G06F 17/00 - Digital computing or data processing equipment or methods, specially adapted for specific functions
• G06Q 20/22 - Payment schemes or models

IPC Classes  ?

• G06F 12/0802 - Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G06F 16/21 - Design, administration or maintenance of databases

IPC Classes  ?

• G06F 16/23 - Updating
• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• G06F 16/22 - Indexing; Data structures therefor; Storage structures
• G06F 16/23 - Updating
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for consensus system downtime recovery. One of the methods includes: multicasting a pre-prepare message to at least some of the backup nodes; obtaining (Q-1) or more prepare messages respectively from (Q-1) or more of the backup nodes, wherein the prepare messages each indicate an acceptance of the pre-prepare message by the corresponding backup node; storing the pre-prepare message and the (Q-1) or more prepare messages; multicasting a commit message to at least some of the backup nodes, the commit message indicating that the primary node agrees to the (Q-1) or more prepare messages; and obtaining, respectively from Q or more nodes among the primary node and the backup nodes, Q or more commit messages each indicating that the corresponding node agrees to (Q-1) or more prepare messages received by the corresponding node.

IPC Classes  ?

• H04L 41/0663 - Performing the actions predefined by failover planning, e.g. switching to standby network elements

IPC Classes  ?

• G06F 21/60 - Protecting data
• G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G06F 16/21 - Design, administration or maintenance of databases
• H04L 12/16 - Arrangements for providing special services to substations

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G07C 9/00 - Individual registration on entry or exit

IPC Classes  ?

• G06F 16/22 - Indexing; Data structures therefor; Storage structures
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules

Abstract

Implementations of this specification include receiving a synchronization request from a light-weight node of the blockchain network including an identity of the light-weight node; identifying one or more permissions associated with the identity of the light-weight node; determining an original world state structure associated with the block height and including a plurality of account records; identifying based on the one or more permissions, a subset of the plurality of account records that are authorized for access by the light-weight node; generating an isolated world state structure based on the original world state data structure including only the subset of the plurality of account records that are authorized for access by the light-weight node; sending a response to the light-weight node that includes the isolated world state data structure.

IPC Classes  ?

• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules

Abstract

Disclosed in the present application are a method and apparatus for verifying documents and identity. The method comprises: first, acquiring an image of an identity document of a subject to be verified; then verifying whether the image of the identity document comes from the same capture scene as a first background image pre-acquired on-site and/or whether the image of the identity document comes from a physical document, and obtaining a first verification result; simultaneously verifying the authenticity of identity information in the image of the identity document, and obtaining a second verification result; and finally determining an identity verification result for the subject to be verified on the basis of the first verification result and the second verification result.

IPC Classes  ?

• G06V 20/00 - Scenes; Scene-specific elements
• G06V 10/74 - Image or video pattern matching; Proximity measures in feature spaces
• G06V 40/10 - Human or animal bodies, e.g. vehicle occupants or pedestrians; Body parts, e.g. hands
• G06V 40/40 - Spoof detection, e.g. liveness detection

IPC Classes  ?

• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• H04L 9/06 - Arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems

IPC Classes  ?

• H04L 9/06 - Arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems

Abstract

A computer-implemented method comprises: committing a transaction amount t of a transaction with a commitment scheme to obtain a transaction commitment value T, the commitment scheme comprising at least a transaction blinding factor r_t; encrypting a combination of the transaction blinding factor r_t and the transaction amount t with a second public key PK_2_B of a recipient of the transaction, wherein: the recipient is further associated with a first public key PK_1_B as an address for receiving the transaction amount t; and transmitting the transaction commitment value T and the encrypted combination to a recipient node associated with the recipient for the recipient node to verify the transaction.

IPC Classes  ?

• G06Q 20/10 - Payment architectures specially adapted for home banking systems

IPC Classes  ?

• G06Q 20/38 - Payment architectures, schemes or protocols - Details thereof

IPC Classes  ?

• H04L 61/30 - Managing network names, e.g. use of aliases or nicknames
• H04L 67/1087 - Peer-to-peer [P2P] networks using cross-functional networking aspects

Abstract

Implementations of the present disclosure include receiving, by a contract updates management system, an update request indicating a change to a smart contract, the change being a proposed update to the smart contract, determining, by executing an updates smart contract within the contract updates management system, whether conditions are met for updating the smart contract to incorporate the change, the updates smart contract defining the conditions, and upon determining, by the contract updates management system, that the conditions are met, updating, by the contract updates management system, the smart contract, and recording the change to one or more blocks in a blockchain of a blockchain network.

IPC Classes  ?

• G06F 16/23 - Updating
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• H04L 61/30 - Managing network names, e.g. use of aliases or nicknames
• H04L 61/4535 - Network directories; Name-to-address mapping using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers

IPC Classes  ?

• H04L 61/4535 - Network directories; Name-to-address mapping using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• H04L 61/30 - Managing network names, e.g. use of aliases or nicknames
• H04L 67/1087 - Peer-to-peer [P2P] networks using cross-functional networking aspects

Abstract

Implementations of the present disclosure include initializing a nonce table comprising a plurality of nonce slots, each nonce slot being associated with a nonce index and a status, and storing a respective nonce value; receiving a request for a nonce value from an application, and in response, requesting a nonce value from the nonce table; receiving a nonce value in response to the request, a status of a nonce slot corresponding to the nonce value being set to occupied; and in response to a transaction using the nonce value being one of successful and failed, executing one of: releasing the nonce value within the nonce slot and setting the status to unoccupied, if the transaction is successful, and setting the status to unoccupied, if the transaction failed.

IPC Classes  ?

• G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists

Abstract

Implementations of the present specification provide for management of service keys for consortium blockchain networks within a blockchain-as-a-service (BaaS) platform. Implementations include actions of receiving a request for a service key from a participant in a consortium blockchain network provisioned within the BaaS platform, determining that the participant is authorized for the service key based on a service authorization table that records participant privileges within the consortium blockchain network, providing a key package including an encrypted private key of the service key, and a public key of the service key, and sending the key package to the participant, the participant decrypting the private key of the service key using a private key associated with the participant.

IPC Classes  ?

• H04L 9/08 - Key distribution

Abstract

Implementations of the present specification include receiving, from a smart contract, and by a function controller executing within the blockchain network, a function call to execute a function, the function call including data for execution of the function, transmitting, by the function controller, the data of the function call to a function component, the function component executing the function based on the data of the function call, receiving, by the function controller, a function result from the function component, and providing, by the function controller, the function result to the smart contract.

IPC Classes  ?

• G06Q 20/38 - Payment architectures, schemes or protocols - Details thereof

IPC Classes  ?

• G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists

IPC Classes  ?

• H04L 9/28 - Arrangements for secret or secure communications; Network security protocols using particular encryption algorithm

IPC Classes  ?

• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system

IPC Classes  ?

• G06F 16/9038 - Presentation of query results

IPC Classes  ?

• G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system
• G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

IPC Classes  ?

• H04L 9/06 - Arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems

Abstract

Implementations of the present disclosure include receiving, by a consensus node of a blockchain, transaction data and a digital signature of the transaction data. The transaction data includes a commitment value, a random number, and a transaction amount to be transferred from one of a public account or a private account of the first user node to one of a public account or a private account of a second user node. The consensus node verifies the digital signature of the transaction data using a public key of the first user node. It then determines that the transaction amount is valid, if the commitment value is correct based on the random number and the commitment scheme, and the transaction amount is less than or equal to a balance of the one of the public account or the private account of the first user node before transfer of the transaction amount.

IPC Classes  ?

• G06Q 20/10 - Payment architectures specially adapted for home banking systems

IPC Classes  ?

• H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system

IPC Classes  ?

• G06Q 20/38 - Payment architectures, schemes or protocols - Details thereof