Language selection

Search

Patent 3175939 Summary

Third-party information liability

Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.

Claims and Abstract availability

Any discrepancies in the text and image of the Claims and Abstract are due to differing posting times. Text of the Claims and Abstract are posted:

  • At the time the application is open to public inspection;
  • At the time of issue of the patent (grant).
(12) Patent: (11) CA 3175939
(54) English Title: BLACKLIST DATA SHARING METHOD AND SYSTEM BASED ON BLOCKCHAIN
(54) French Title: PROCEDE ET SYSTEME DE PARTAGE DE DONNEES DE LISTE NOIRE A BASE DE CHAINE DE BLOCS
Status: Granted and Issued
Bibliographic Data
(51) International Patent Classification (IPC):
  • G06F 16/176 (2019.01)
(72) Inventors :
  • SHENG, WEI (China)
  • ZHENG, ZHITAN (China)
(73) Owners :
  • 10353744 CANADA LTD.
(71) Applicants :
  • 10353744 CANADA LTD. (Canada)
(74) Agent: JAMES W. HINTONHINTON, JAMES W.
(74) Associate agent:
(45) Issued: 2024-06-25
(86) PCT Filing Date: 2019-09-30
(87) Open to Public Inspection: 2020-09-24
Examination requested: 2022-09-19
Availability of licence: N/A
Dedicated to the Public: N/A
(25) Language of filing: English

Patent Cooperation Treaty (PCT): Yes
(86) PCT Filing Number: PCT/CN2019/109349
(87) International Publication Number: WO 2020186726
(85) National Entry: 2022-09-19

(30) Application Priority Data:
Application No. Country/Territory Date
201910203937.1 (China) 2019-03-18

Abstracts

English Abstract

Provided are a block chain-based blacklist data sharing method and system, which relates to the field of block chain technology, the convenience and effectiveness of blacklist data acquisition can be ensured by introducing block chain technology into the application scenarios of blacklist data, and the sharing value of blacklist data is improved. The method includes: member institutions build their own network nodes, the network nodes to which each member institution belongs are networked sequentially to construct the block chain, the network nodes include business nodes and token nodes; initiating blacklist data upload request via any business node, using the generated symmetric key to encrypt the blacklist data while using the random public key to encrypt the symmetric key, packing the encrypted blacklist data and the encrypted symmetric key onto the chain, and when the account is received onto the chain, the associated token node requests to transfer the token to the specified token address; the system includes the method mentioned in the above solution.


French Abstract

L'invention concerne un procédé et un système de partage de données de liste noire à base de chaîne de blocs, qui se rapportent au domaine de la technologie des chaînes de blocs. La commodité et l'efficacité de l'acquisition de données de liste noire peuvent être assurées par l'introduction d'une technologie de chaîne de blocs dans les scénarios d'application de données de liste noire, et la valeur de partage de données de liste noire est améliorée. Le procédé comprend les étapes suivantes : des institutions membres construisent leurs propres nuds de réseau, les nuds de réseau auxquels appartient chaque institution membre sont mis en réseau de manière séquentielle pour construire la chaîne de blocs, les nuds de réseau comprennent des nuds commerciaux et des nuds de jeton ; le lancement d'une demande de téléchargement de données de liste noire par l'intermédiaire d'un quelconque nud commercial, l'utilisation de la clé symétrique générée pour chiffrer les données de liste noire tout en utilisant la clé publique aléatoire pour chiffrer la clé symétrique, l'empaquetage des données de liste noire chiffrées et de la clé symétrique chiffrée sur la chaîne, et lorsque le compte est reçu sur la chaîne, le nud de jeton associé demande de transférer le jeton à l'adresse de jeton spécifiée. Le système comprend le procédé mentionné dans la solution ci-dessus.

Claims

Note: Claims are shown in the official language in which they were submitted.


Claims:
1. A blacklist data sharing system based on a blockchain, the system
comprising:
a blockchain constructing unit, for:
constructing respective network nodes by member organizations; and
sequentially networking the network nodes belonging to the various member
organizations
to construct a blockchain, wherein the network nodes include business nodes
and
accumulated point nodes, and wherein the blockchain includes a business
alliance chain
and an accumulated point alliance chain, of which the business alliance chain
includes
plural business nodes networked together, and the accumulated point alliance
chain
includes plural accumulated point nodes networked together;
a blacklist data uploading unit including:
an upload requesting module, for initiating a blacklist data uploading request
to the
business alliance chain by a member organization through a business node
belonging
thereto, and simultaneously designating an accumulated point address for
receiving
accumulated points;
a duplicate-checking module, for calculating a key value of blacklist data to
be
uploaded, and judging through the key value whether the blacklist data to be
uploaded
has been stored in the business alliance chain;
a first executing module, for:
in the case a judging result is negative, employing a randomly generated
symmetric key to encrypt the blacklist data and using a random public key to
encrypt the symmetric key and executing packaging and up-chaining operations;
associatively marking the blacklist data, the accumulated point address, and
the
random public key, wherein the blacklist data includes names, IDs, and
detailed
data;
Date Recue/Date Received 202402-12

using the randomly generated symmetric key to encrypt the detailed data, and
storing the names, the IDs, and the encrypted detailed data in the same file
folder;
and
using the random public key to encrypt the symmetric key for a second time,
and thereafter packaging the symmetric key encrypted for the second time and
the file folder and uploading the same to the business alliance chain; and
in the case the judging result is positive, terminating the current operation
of
uploading the blacklist data; and
an accumulated point transacting module, for requesting the accumulated point
alliance chain by the associated accumulated point node to transfer
accumulated
points to the designated accumulated point address, when it is monitored that
the up-
chaining operation and down-accounting of the blacklist data are triggered;
and
a blacklist data enquiring unit, for:
initiating a blacklist data enquiring request via any one business node, in
the case target
blacklist data is not uploaded by an enquiring organization;
paying accumulated points to an accumulated point address of an organization
holding the
target blacklist data through an associated accumulated point node;
using a private key that matches the random public key to decrypt the packaged
target
blacklist data after the holding organization has monitored entry into the
account of the
accumulated points; and
simultaneously invoking a public key of the enquiring organization to
reversely encrypt
the decrypted target blacklist data for return to the enquiring organization
for decryption
and enquiry; and
a blacklist data deleting unit, for:
26
Date Recue/Date Received 202402-12

initiating a blacklist data deleting request via a business node of the
blacklist data holding
organization itself; and
deleting the target blacklist data after signature verification has been
passed and deducting
accumulated points in the associated accumulated point address.
2. The system of claim 1 wherein business nodes are used for initiating a
business request and
storing blacklist data and accumulated point nodes are used for executing
corresponding
accumulated point transactions and recording accumulated point information.
3. The system of claim 1 wherein the blockchain further includes an API
server with enclosed
sdk kits and external service frameworks of the business alliance chain and
the accumulated
point alliance chain.
4. The system of claim 3 wherein the API server is configured to connect
the business alliance
chain with the accumulated point alliance chain and to provide an externally
servicing
interface.
5. The system of claim 3 wherein the business alliance chain includes a
business alliance chain
body and an event monitoring server, wherein the business alliance chain body
is employed
to run a smart contract and provide blacklist data storing and sharing
services, and wherein
the event monitoring server is employed to monitor events sent from the
business alliance
chain body and simultaneously initiate accumulated point transferring
requests.
6. The system of claim 1 wherein names and IDs are desensitized before
being uploaded.
7. The system of claim 1 wherein the blacklist data to be uploaded is
judged against the blacklist
data already stored to determine if the data already exists in the business
alliance chain by
comparing the key values of the already stored blacklist data with the
blacklist data to be
uploaded.
8. The system of claim 7 wherein when the judging result is negative the
blacklist data to be
uploaded is encrypted using the randomly generated symmetric key.
27
Date Recue/Date Received 202402-12

9. The system of claim 7 wherein when the judging result is positive
the operation of uploading
the blacklist data is terminated and a request is sent to the accumulated
point alliance chain to
obtain accumulated points.
10. The system according to claim 1, wherein the blacklist data enquiring unit
includes:
an enquiry requesting module, for initiating a blacklist data enquiring
request to the business
alliance chain by a member organization through a business node belong
thereto, and judging
whether uploading is performed by the enquiring organization according to the
accumulated
point address associated with the blacklist data to be enquired; and
a second executing module, for, in the case a judging result is positive,
invoking a private key
associated with the accumulated point address to decrypt the encrypted
symmetric key and
extract a plaintext symmetric key, and thereafter employing the plaintext
symmetric key to
decrypt detailed data in the file folder; in the case the judging result is
negative, requesting
the accumulated point alliance chain through the associated accumulated point
node to pay
accumulated points to the accumulated point address of the target blacklist
data holding
organization, using a private key that matches the associated accumulated
point address to
decrypt the encrypted symmetric key after the holding organization has
monitored entry into
the account of the accumulated points, invoking a public key of the enquiring
organization to
reversely encrypt the plaintext symmetric key after extracting the plaintext
symmetric key,
and thereafter packaging the reversely encrypted symmetric key and the
undecrypted detailed
data and returning the sane to the enquiring organization for decryption and
obtainment.
11. The system according to claim 10, wherein the accumulated point node
includes plural
accumulated point addresses, and that the enquiring organization can select
any one
accumulated point address with ample accumulated points to pay accumulated
points to the
accumulated point address of the target blacklist data holding organization.
12. The system according to claim 1, wherein a process of enquiring blacklist
data further includes:
initiating a basic information enquiring request of the blacklist data via any
one business node,
inputting a name and an ID of the target blacklist data as key values in the
business alliance
chain, and returning basic information of the target blacklist data by
invoking a smart contract.
28
Date Recue/Date Received 202402-12

13. The system according to claim 1, wherein the blacklist data deleting unit
includes:
a deletion requesting module, for initiating a blacklist data deleting request
via a business
node of the blacklist data holding organization itself, and judging through
the business
alliance chain whether the accumulated point address associated therewith has
ample
accumulated points; and
a third executing module, for, in the case a judging result is positive, using
a private key that
matches the random public key to sign the target blacklist data, sending
signature information
together with the blacklist data deleting request to the business alliance
chain, and deleting
the target blacklist data after verification has been passed by the business
alliance chain and
deducting accumulated points in the associated accumulated point address,
otherwise
terminating the current operation of deleting the blacklist data; and in the
case the judging
result is negative, directly terminating the current operation of deleting the
blacklist data.
14. A blacklist data sharing method based on a blockchain, the method
comprising:
constructing respective network nodes by member organizations, and
sequentially networking
the network nodes belonging to the various member organizations to construct a
blockchain,
wherein the network nodes include business nodes and accumulated point nodes,
wherein the
blockchain includes a business alliance chain and an accumulated point
alliance chain, of
which the business alliance chain includes plural business nodes networked
together, and the
accumulated point alliance chain includes plural accumulated point nodes
networked together;
initiating a blacklist data uploading request to the business alliance chain
by a member
organization through a business node belonging thereto, and simultaneously
designating an
accumulated point address for receiving accumulated points;
calculating a key value of blacklist data to be uploaded, and judging through
the key value
whether the blacklist data to be uploaded has been stored in the business
alliance chain;
in the case a judging result is negative:
29
Date Recue/Date Received 202402-12

employing a randomly generated symmetric key to encrypt the blacklist data and
using a
random public key to encrypt the symmetric key and executing packaging and up-
chaining operations;
associatively marking the blacklist data, the accumulated point address, and
the random
public key, wherein the blacklist data includes names, IDs, and detailed data;
using the randomly generated symmetric key to encrypt the detailed data, and
storing the
names, the Ds, and the encrypted detailed data in the same file folder; and
using the random public key to encrypt the symmetric key for a second time,
and
thereafter packaging the symmetric key encrypted for the second time and the
file folder
and uploading the same to the business alliance chain; and
in the case the judging result is positive, telininating the current operation
of uploading the
blacklist data;
requesting the accumulated point alliance chain by the associated accumulated
point node to
transfer accumulated points to the designated accumulated point address, when
it is
monitored that the up-chaining operation and down-accounting of the blacklist
data are
triggered; and
initiating a blacklist data enquiring request via any one business node, in
the case target
blacklist data is not uploaded by an enquiring organization, paying
accumulated points to an
accumulated point address of an organization holding the target blacklist data
through an
associated accumulated point node, using a private key that matches the random
public key
to decrypt the packaged target blacklist data after the holding organization
has monitored
entry into the account of the accumulated points, and simultaneously invoking
a public key
of the enquiring organization to reversely encrypt the decrypted target
blacklist data for return
to the enquiring organization for decryption and enquiry; or
initiating a blacklist data deleting request via a business node of the
blacklist data holding
organization itself, and deleting the target blacklist data after signature
verification has been
passed and deducting accumulated points in the associated accumulated point
address.
3 0
Date Recue/Date Received 202402-12

15. The method of claim 14 wherein business nodes are used for initiating a
business request and
storing blacklist data and accumulated point nodes are used for executing
corresponding
accumulated point transactions and recording accumulated point information.
16. The method of claim 14 wherein the blockchain further includes an API
server with enclosed
sdk kits and external service frameworks of the business alliance chain and
the accumulated
point alliance chain.
17. The method of claim 16 wherein the API server is configured to connect the
business alliance
chain with the accumulated point alliance chain and to provide an externally
servicing
interface.
18. The method of claim14 wherein the business alliance chain includes a
business alliance chain
body and an event monitoring server, wherein the business alliance chain body
is employed
to run a smart contract and provide blacklist data storing and sharing
services, and wherein
the event monitoring server is employed to monitor events sent from the
business alliance
chain body and simultaneously initiate accumulated point transferring
requests.
19. The method of claim 14 wherein names and IDs are desensitized before being
uploaded.
20. The method of claim 14 wherein the blacklist data to be uploaded is judged
against the
blacklist data already stored to determine if the data already exists in the
business alliance
chain by comparing the key values of the already stored blacklist data with
the blacklist data
to be uploaded.
21. The method of claim 20 wherein when the judging result is negative the
blacklist data to be
uploaded is encrypted using the randomly generated symmetric key.
22. The method of claim 20 wherein when the judging result is positive the
operation of uploading
the blacklist data is terminated and a request is sent to the accumulated
point alliance chain to
obtain accumulated points.
31
Date Recue/Date Received 202402-12

23. The method according to claim 14, wherein the step of initiating a
blacklist data enquiring
request via any one business node, in the case target blacklist data is not
uploaded by an
enquiring organization, transferring accumulated points to an accumulated
point address of
an organization holding the target blacklist data through an associated
accumulated point node,
using a private key that matches the random public key to decrypt the packaged
target blacklist
data after the holding organization has monitored entry into the account of
the accumulated
points, and simultaneously invoking a public key of the enquiring organization
to reversely
encrypt the decrypted target blacklist data for return to the enquiring
organization for
decryption and enquiry includes:
initiating a blacklist data enquiring request to the business alliance chain
by a member
organization through a business node belong thereto, and judging whether
uploading is
performed by the enquiring organization according to the accumulated point
address
associated with the blacklist data to be enquired;
in the case a judging result is positive, invoking a private key associated
with the accumulated
point address to decrypt the encrypted symmetric key and extract a plaintext
symmetric key,
and thereafter employing the plaintext symmetric key to decrypt detailed data
in the file folder;
and
in the case the judging result is negative, requesting the accumulated point
alliance chain
through the associated accumulated point node to pay accumulated points to the
accumulated
point address of the target blacklist data holding organization, using a
private key that matches
the associated accumulated point address to decrypt the encrypted symmetric
key after the
holding organization has monitored entry into the account of the accumulated
points, invoking
a public key of the enquiring organization to reversely encrypt the plaintext
symmetric key
after extracting the plaintext symmetric key, and thereafter packaging the
reversely encrypted
symmetric key and the undecrypted detailed data and returning the same to the
enquiring
organization for decryption and obtainment.
32
Date Recue/Date Received 202402-12

24. The method according to claim 23, wherein the accumulated point node
includes plural
accumulated point addresses, and that the enquiring organization can select
any one
accumulated point address with ample accumulated points to pay accumulated
points to the
accumulated point address of the target blacklist data holding organization.
25. The method according to claim 14, wherein a process of enquiring blacklist
data further
includes:
initiating a basic infoimati on enquiring request of the blacklist data via
any one business node,
inputting a name and an ID of the target blacklist data as key values in the
business alliance
chain, and returning basic information of the target blacklist data by
invoking a smart contract.
26. The method according to claim 14, wherein the step of initiating a
blacklist data deleting
request via a business node of the blacklist data holding organization itself,
and deleting the
target blacklist data after signature verification has been passed and
deducting accumulated
points in the associated accumulated point address includes:
initiating a blacklist data deleting request via a business node of the
blacklist data holding
organization itself, and judging through the business alliance chain whether
the accumulated
point address associated therewith has ample accumulated points;
in the case a judging result is positive, using a private key that matches the
random public key
to sign the target blacklist data, sending signature information together with
the blacklist data
deleting request to the business alliance chain, and deleting the target
blacklist data after
verification has been passed by the business alliance chain and deducting
accumulated points
in the associated accumulated point address, otherwise terminating the current
operation of
deleting the blacklist data; and
in the case the judging result is negative, directly terminating the current
operation of deleting
the blacklist data.
27. A computer equipment comprising:
a computer readable physical memory;
33
Date Recue/Date Received 202402-12

a processor communicatively coupled to the memory,
a computer program stored on the memory and operable on the processor, wherein
the
processor executes the computer program configured to:
construct respective network nodes by member organizations, and sequentially
network the
network nodes belonging to the various member organizations to construct a
blockchain,
wherein the network nodes include business nodes and accumulated point nodes,
wherein the
blockchain includes a business alliance chain and an accumulated point
alliance chain, of
which the business alliance chain includes plural business nodes networked
together, and the
accumulated point alliance chain includes plural accumulated point nodes
networked together;
initiate a blacklist data uploading request to the business alliance chain by
a member
organization through a business node belonging thereto, and simultaneously
designate an
accumulated point address for receiving accumulated points;
calculate a key value of blacklist data to be uploaded, and judging through
the key value
whether the blacklist data to be uploaded has been stored in the business
alliance chain;
in the case a judging result is negative, employ a randomly generated
symmetric key to
encrypt the blacklist data and use a random public key to encrypt the
symmetric key and
execute packaging and up-chaining operations by:
associatively marking the blacklist data, the accumulated point address, and
the random
public key, wherein the blacklist data includes names, IDs, and detailed data;
using the randomly generated symmetric key to encrypt the detailed data, and
store the
names, the IDs, and the encrypted detailed data in the same file folder; and
using the random public key to encrypt the symmetric key for a second time,
and
thereafter package the symmetric key encrypted for the second time and the
file folder
and upload the same to the business alliance chain
in the case the judging result is positive, terminating the current operation
of uploading the
blacklist data; and
34
Date Recue/Date Received 202402-12

request the accumulated point alliance chain by the associated accumulated
point node to
transfer accumulated points to the designated accumulated point address, when
it is monitored
that the up-chaining operation and down-accounting of the blacklist data are
triggered; or
initiate a blacklist data enquiring request via any one business node, in the
case target blacklist
data is not uploaded by an enquiring organization, pay accumulated points to
an accumulated
point address of an organization holding the target blacklist data through an
associated
accumulated point node, use a private key that matches the random public key
to decrypt the
packaged target blacklist data after the holding organization has monitored
entry into the
account of the accumulated points, and simultaneously invoke a public key of
the enquiring
organization to reversely encrypt the decrypted target blacklist data for
return to the enquiring
organization for decryption and enquiry; or
initiate a blacklist data deleting request via a business node of the
blacklist data holding
organization itself, and delete the target blacklist data after signature
verification has been
passed and deducting accumulated points in the associated accumulated point
address.
28. The equipment of claim 27 wherein business nodes are used for initiating a
business request
and storing blacklist data and accumulated point nodes are used for executing
corresponding
accumulated point transactions and recording accumulated point information.
29. The equipment of claim 27 wherein the blockchain further includes an API
server with
enclosed sdk kits and external service frameworks of the business alliance
chain and the
accumulated point alliance chain.
30. The equipment of claim 29 wherein the API server is configured to connect
the business
alliance chain with the accumulated point alliance chain and to provide an
externally servicing
interface.
31. The equipment of claim 27 wherein the business alliance chain includes a
business alliance
chain body and an event monitoring server, wherein the business alliance chain
body is
employed to run a smart contract and provide blacklist data storing and
sharing services, and
wherein the event monitoring server is employed to monitor events sent from
the business
alliance chain body and simultaneously initiate accumulated point transferring
requests.
Date Recue/Date Received 202402-12

32. The equipment of claim 27, wherein names and IDs are desensitized before
being uploaded.
33. The equipment of claim 27, wherein the blacklist data to be uploaded is
judged against the
blacklist data already stored to determine if the data already exists in the
business alliance
chain by comparing the key values of the already stored blacklist data with
the blacklist data
to be uploaded.
34. The equipment of claim 33 wherein when the judging result is negative the
blacklist data to
be uploaded is encrypted using the randomly generated symmetric key.
35. The equipment of claim 33 wherein when the judging result is positive the
operation of
uploading the blacklist data is terminated and a request is sent to the
accumulated point
alliance chain to obtain accumulated points.
36. The equipment according to claim 27, wherein the program is further
configured to:
initiate a blacklist data enquiring request to the business alliance chain by
a member
organization through a business node belong thereto, and judge whether
uploading is
performed by the enquiring organization according to the accumulated point
address
associated with the blacklist data to be enquired;
in the case a judging result is positive, invoke a private key associated with
the accumulated
point address to decrypt the encrypted symmetric key and extract a plaintext
symmetric key,
and thereafter employ the plaintext symmetric key to decrypt detailed data in
the file folder;
and
36
Date Recue/Date Received 202402-12

in the case the judging result is negative, request the accumulated point
alliance chain through
the associated accumulated point node to pay accumulated points to the
accumulated point
address of the target blacklist data holding organization, using a private key
that matches the
associated accumulated point address to decrypt the encrypted symmetric key
after the
holding organization has monitored entry into the account of the accumulated
points, invoke
a public key of the enquiring organization to reversely encrypt the plaintext
symmetric key
after extracting the plaintext symmetric key, and thereafter package the
reversely encrypted
symmetric key and the undecrypted detailed data and return the same to the
enquiring
organization for decryption and obtainment.
37. The equipment according to claim 36, wherein the accumulated point node
includes plural
accumulated point addresses, and that the enquiring organization can select
any one
accumulated point address with ample accumulated points to pay accumulated
points to the
accumulated point address of the target blacklist data holding organization.
38. The equipment according to claim 27, wherein a process of enquiring
blacklist data further
includes:
initiating a basic information enquiring request of the blacklist data via any
one business node,
inputting a name and an ID of the target blacklist data as key values in the
business alliance
chain, and returning basic information of the target blacklist data by
invoking a smart contract.
39. The equipment according to claim 27, wherein the program is further
configured to:
initiate a blacklist data deleting request via a business node of the
blacklist data holding
organization itself, and judge through the business alliance chain whether the
accumulated
point address associated therewith has ample accumulated points;
in the case a judging result is positive, use a private key that matches the
random public key
to sign the target blacklist data, send signature information together with
the blacklist data
deleting request to the business alliance chain, and delete the target
blacklist data after
verification has been passed by the business alliance chain and deduct
accumulated points in
the associated accumulated point address, otherwise terminate the current
operation of
deleting the blacklist data; and
37
Date Recue/Date Received 202402-12

in the case the judging result is negative, directly terminate the current
operation of deleting
the blacklist data.
40. A computer readable physical memory having recorded thereon statements and
instructions
for execution by a computer, said statements and instructions comprising code
means for
performing::
construct respective network nodes by member organizations, and sequentially
network the
network nodes belonging to the various member organizations to construct a
blockchain,
wherein the network nodes include business nodes and accumulated point nodes,
wherein the
blockchain includes a business alliance chain and an accumulated point
alliance chain, of
which the business alliance chain includes plural business nodes networked
together, and the
accumulated point alliance chain includes plural accumulated point nodes
networked together;
initiate a blacklist data uploading request via any one business node, using a
random public
key to encrypt a generated symmetric key while employing the generated
symmetric key to
encrypt blacklist data, and request by an associated accumulated point node to
transfer
accumulated points to a designated accumulated point address during up-
chaining and down-
accounting by packaging and up-chaining the encrypted blacklist data and the
encrypted
symmetric key; or
initiate a blacklist data uploading request to the business alliance chain by
a member
organization through a business node belonging thereto, and simultaneously
designate an
accumulated point address for receiving accumulated points;
calculate a key value of blacklist data to be uploaded, and judging through
the key value
whether the blacklist data to be uploaded has been stored in the business
alliance chain;
in the case a judging result is negative, employ a randomly generated
symmetric key to
encrypt the blacklist data and use a random public key to encrypt the
symmetric key and
execute packaging and up-chaining operations by:
associatively marking the blacklist data, the accumulated point address, and
the random
public key, wherein the blacklist data includes names, IDs, and detailed data;
38
Date Recue/Date Received 202402-12

using the randomly generated symmetric key to encrypt the detailed data, and
store the
names, the Ds, and the encrypted detailed data in the same file folder; and
using the random public key to encrypt the symmetric key for a second time,
and
thereafter package the symmetric key encrypted for the second time and the
file folder
and upload the same to the business alliance chain
in the case the judging result is positive, terminating the current operation
of uploading the
blacklist data; and
request the accumulated point alliance chain by the associated accumulated
point node to
transfer accumulated points to the designated accumulated point address, when
it is monitored
that the up-chaining operation and down-accounting of the blacklist data are
ITiggered; or
initiate a blacklist data deleting request via a business node of the
blacklist data holding
organization itself, and delete the target blacklist data after signature
verification has been
passed and deducting accumulated points in the associated accumulated point
address.
41. The memory of claim 40 wherein business nodes are used for initiating a
business request and
storing blacklist data and accumulated point nodes are used for executing
corresponding
accumulated point transactions and recording accumulated point information.
42. The memory of claim 40 wherein the blockchain further includes an API
server with enclosed
sdk kits and external service frameworks of the business alliance chain and
the accumulated
point alliance chain.
43. The memory of claim 42 wherein the API server is configured to connect the
business alliance
chain with the accumulated point alliance chain and to provide an externally
servicing
interface.
44. The memory of claim 40 wherein the business alliance chain includes a
business alliance
chain body and an event monitoring server, wherein the business alliance chain
body is
employed to run a smart contract and provide blacklist data storing and
sharing services, and
wherein the event monitoring server is employed to monitor events sent from
the business
alliance chain body and simultaneously initiate accumulated point transferring
requests.
39
Date Recue/Date Received 202402-12

45. The memory of claim 40, wherein names and IDs are desensitized before
being uploaded.
46. The memory of claim 40, wherein the blacklist data to be uploaded is
judged against the
blacklist data already stored to determine if the data already exists in the
business alliance
chain by comparing the key values of the already stored blacklist data with
the blacklist data
to be uploaded.
47. The memory of claim 46 wherein when the judging result is negative the
blacklist data to be
uploaded is encrypted using the randomly generated symmetric key.
48. The memory of claim 46 wherein when the judging result is positive the
operation of
uploading the blacklist data is terminated and a request is sent to the
accumulated point
alliance chain to obtain accumulated points.
49. The memory according to claim 40, wherein the program is further
configured to:
initiate a blacklist data enquiring request to the business alliance chain by
a member
organization through a business node belong thereto, and judge whether
uploading is
performed by the enquiring organization according to the accumulated point
address
associated with the blacklist data to be enquired;
in the case a judging result is positive, invoke a private key associated with
the accumulated
point address to decrypt the encrypted symmetric key and extract a plaintext
symmetric key,
and thereafter employ the plaintext symmetric key to decrypt detailed data in
the file folder;
and
Date Recue/Date Received 202402-12

in the case the judging result is negative, request the accumulated point
alliance chain through
the associated accumulated point node to pay accumulated points to the
accumulated point
address of the target blacklist data holding organization, using a private key
that matches the
associated accumulated point address to decrypt the encrypted symmetric key
after the
holding organization has monitored entry into the account of the accumulated
points, invoke
a public key of the enquiring organization to reversely encrypt the plaintext
symmetric key
after extracting the plaintext symmetric key, and thereafter package the
reversely encrypted
symmetric key and the undecrypted detailed data and return the same to the
enquiring
organization for decryption and obtainment.
50. The memory according to claim 49, wherein the accumulated point node
includes plural
accumulated point addresses, and that the enquiring organization can select
any one
accumulated point address with ample accumulated points to pay accumulated
points to the
accumulated point address of the target blacklist data holding organization.
51. The memory according to claim 40, wherein a process of enquiring blacklist
data further
includes:
initiating a basic information enquiring request of the blacklist data via any
one business node,
inputting a name and an ID of the target blacklist data as key values in the
business alliance
chain, and returning basic information of the target blacklist data by
invoking a smart contract.
52. The memory according to claim 40, wherein the program is further
configured to:
initiate a blacklist data deleting request via a business node of the
blacklist data holding
organization itself, and judge through the business alliance chain whether the
accumulated
point address associated therewith has ample accumulated points;
in the case a judging result is positive, use a private key that matches the
random public key
to sign the target blacklist data, send signature information together with
the blacklist data
deleting request to the business alliance chain, and delete the target
blacklist data after
verification has been passed by the business alliance chain and deduct
accumulated points in
the associated accumulated point address, otherwise terminate the current
operation of
deleting the blacklist data; and
41
Date Recue/Date Received 202402-12

in the case the judging result is negative, directly terminate the current
operation of deleting
the blacklist data.
42
Date Recue/Date Received 202402-12

Description

Note: Descriptions are shown in the official language in which they were submitted.


CA 03175939 2022-09-19
BLACKLIST DATA SHARING METHOD AND SYSTEM BASED ON BLOCKCHAIN
BACKGROUND OF THE INVENTION
Technical Field
[0001] The present invention relates to the field of blockchain technology,
and more particularly
to blacklist data sharing method and system based on a blockchain.
Description of Related Art
[0002] The blacklist is a list that records actors or legal representatives
with severely negative
credits, once an actor is listed in the blacklist, this indicates that the
actor is problematic
in terms of credit, and cooperation with any actor or legal representative
appearing in the
blacklist necessitates an increased risk; currently available blacklist data
originates from
many approaches, such as financial organizations, credit card issuing
organizations,
courts, and telecommunication enterprises, etc.; since the origins of
blacklist data include
governmental functional organizations and large- and medium-sized enterprises,
and due
to characteristics of the dispersed origins, it is very hard in the
operational process to
effectively integrate and share the blacklist data originating from the above
units, so there
comes into a lot of private institutions that are dedicated to collecting
blacklist data from
various units and thereafter selling the data for profit, so that enterprises
acquire the
required blacklist data through paid purchase; nevertheless, due to
characteristics that the
blacklist data is dispersedly publicized and not transparently publicized, the
blacklist data
obtained by different private institutions differs from one another both in
terms of
quantity and quality, accordingly, even if enterprises would like to buy the
blacklist data
with a high price, it is still impossible to ensure completeness and
effectiveness of the
blacklist data.
1
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
SUMMARY OF THE INVENTION
[0003] An objective of the present invention is to provide blacklist data
sharing method and
system based on a blockchain, by introducing the blockchain technology into
the
application scenario of blacklist data, it is made possible to ensure
conveniency and
effectiveness in obtaining blacklist data, and enhance sharing value of the
blacklist data.
[0004] In order to achieve the above objective, according to the first aspect,
the present invention
provides a blacklist data sharing method based on a blockchain, and the method
comprises:
[0005] constructing respective network nodes by member organizations, and
sequentially
networking the network nodes belonging to the various member organizations to
construct a blockchain, wherein the network nodes include business nodes and
accumulated point nodes;
[0006] initiating a blacklist data uploading request via any one business
node, using a random
public key to encrypt a generated symmetric key while employing the generated
symmetric key to encrypt blacklist data, and requesting by an associated
accumulated
point node to transfer accumulated points to a designated accumulated point
address
during up-chaining and down-accounting by packaging and up-chaining the
encrypted
blacklist data and the encrypted symmetric key; or
[0007] initiating a blacklist data enquiring request via any one business
node, in the case target
blacklist data is not uploaded by an enquiring organization, paying
accumulated points to
an accumulated point address of an organization holding the target blacklist
data through
an associated accumulated point node, using a private key that matches the
random public
key to decrypt the packaged target blacklist data after the holding
organization has
monitored entry into the account of the accumulated points, and simultaneously
invoking
a public key of the enquiring organization to reversely encrypt the decrypted
target
blacklist data for return to the enquiring organization for decryption and
enquiry; or
[0008] initiating a blacklist data deleting request via a business node of the
blacklist data holding
2
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
organization itself, and deleting the target blacklist data after signature
verification has
been passed and deducting accumulated points in the associated accumulated
point
address.
[0009] Specifically, the blockchain includes a business alliance chain and an
accumulated point
alliance chain, of which the business alliance chain consists of plural
business nodes
networked together, and the accumulated point alliance chain consists of
plural
accumulated point nodes networked together.
[0010] Preferably, the step of initiating a blacklist data uploading request
via any one business
node, using a random public key to encrypt a generated symmetric key while
employing
the generated symmetric key to encrypt blacklist data, and requesting by an
associated
accumulated point node to transfer accumulated points to a designated
accumulated point
address during up-chaining and down-accounting by packaging and up-chaining
the
encrypted blacklist data and the encrypted symmetric key includes:
[0011] initiating a blacklist data uploading request to the business alliance
chain by a member
organization through a business node belonging thereto, and simultaneously
designating
an accumulated point address for receiving accumulated points;
[0012] calculating a key value of blacklist data to be uploaded, and judging
through the key value
whether the blacklist data to be uploaded has been stored in the business
alliance chain;
[0013] in the case a judging result is negative, employing a randomly
generated symmetric key
to encrypt the blacklist data and using a random public key to encrypt the
symmetric key
and executing packaging and up-chaining operations, in the case the judging
result is
positive, terminating the current operation of uploading the blacklist data;
and
[0014] requesting the accumulated point alliance chain by the associated
accumulated point node
to transfer accumulated points to the designated accumulated point address,
when it is
monitored that the up-chaining operation and down-accounting of the blacklist
data are
triggered.
3
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
[0015] Preferably, the step of employing a randomly generated symmetric key to
encrypt the
blacklist data and using a random public key to encrypt the symmetric key and
executing
packaging and up-chaining operations includes:
[0016] associatively marking the blacklist data, the accumulated point
address, and the random
public key, wherein the blacklist data includes names, IDs, and detailed data;
[0017] using the randomly generated symmetric key to encrypt the detailed
data, and storing the
names, the IDs, and the encrypted detailed data in the same file folder; and
[0018] using the random public key to encrypt the symmetric key for a second
time, and
thereafter packaging the symmetric key encrypted for the second time and the
file folder
and uploading the same to the business alliance chain.
[0019] Preferably, the step of initiating a blacklist data enquiring request
via any one business
node, in the case target blacklist data is not uploaded by an enquiring
organization,
transferring accumulated points to an accumulated point address of an
organization
holding the target blacklist data through an associated accumulated point
node, using a
private key that matches the random public key to decrypt the packaged target
blacklist
data after the holding organization has monitored entry into the account of
the
accumulated points, and simultaneously invoking a public key of the enquiring
organization to reversely encrypt the decrypted target blacklist data for
return to the
enquiring organization for decryption and enquiry includes:
[0020] initiating a blacklist data enquiring request to the business alliance
chain by a member
organization through a business node belong thereto, and judging whether
uploading is
performed by the enquiring organization according to the accumulated point
address
associated with the blacklist data to be enquired;
[0021] in the case a judging result is positive, invoking a private key
associated with the
accumulated point address to decrypt the encrypted symmetric key and extract a
plaintext
symmetric key, and thereafter employing the plaintext symmetric key to decrypt
detailed
data in the file folder; and
[0022] in the case the judging result is negative, requesting the accumulated
point alliance chain
4
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
through the associated accumulated point node to pay accumulated points to the
accumulated point address of the target blacklist data holding organization,
using a
private key that matches the associated accumulated point address to decrypt
the
encrypted symmetric key after the holding organization has monitored entry
into the
account of the accumulated points, invoking a public key of the enquiring
organization
to reversely encrypt the plaintext symmetric key after extracting the
plaintext symmetric
key, and thereafter packaging the reversely encrypted symmetric key and the
undecrypted
detailed data and returning the same to the enquiring organization for
decryption and
obtainment.
[0023] Preferably, the accumulated point node includes plural accumulated
point addresses, and
the enquiring organization can select any one accumulated point address with
ample
accumulated points to pay accumulated points to the accumulated point address
of the
target blacklist data holding organization.
[0024] Optionally, a process of enquiring blacklist data further includes:
[0025] initiating a basic information enquiring request of the blacklist data
via any one business
node, inputting a name and an ID of the target blacklist data as key values in
the business
alliance chain, and returning basic information of the target blacklist data
by invoking a
smart contract.
[0026] Preferably, the step of initiating a blacklist data deleting request
via a business node of
the blacklist data holding organization itself, and deleting the target
blacklist data after
signature verification has been passed and deducting accumulated points in the
associated
accumulated point address includes:
[0027] initiating a blacklist data deleting request via a business node of the
blacklist data holding
organization itself, and judging through the business alliance chain whether
the
accumulated point address associated therewith has ample accumulated points;
[0028] in the case a judging result is positive, using a private key that
matches the random public
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
key to sign the target blacklist data, sending signature information together
with the
blacklist data deleting request to the business alliance chain, and deleting
the target
blacklist data after verification has been passed by the business alliance
chain and
deducting accumulated points in the associated accumulated point address,
otherwise
terminating the current operation of deleting the blacklist data; and
[0029] in the case the judging result is negative, directly terminating the
current operation of
deleting the blacklist data.
[0030] In comparison with prior-art technology, the blacklist data sharing
method based on a
blockchain provided by the present invention achieves the following
advantageous effects.
[0031] In the blacklist data sharing method based on a blockchain provided by
the present
invention, a blockchain is constructed by sequentially accessing network nodes
to which
various member organizations correspond to a network, and each network node
includes
mutually associated business nodes and accumulated point nodes, of which the
business
node is used for initiating a business request and storing blacklist data, and
the
accumulated point node is used for executing corresponding accumulated point
transaction and recording accumulated point information when down-accounting
of the
business request is triggered; exemplarily, any member organization can
initiate a
blacklist data uploading request via a corresponding business node, uses a
random public
key to encrypt a generated symmetric key while employing the generated
symmetric key
to encrypt blacklist data, and requests by an associated accumulated point
node to transfer
accumulated points to a designated accumulated point address during up-
chaining and
down-accounting by packaging and up-chaining the encrypted blacklist data and
the
encrypted symmetric key; alternatively, any member organization can initiate a
blacklist
data enquiring request via a corresponding business node, in the case target
blacklist data
is not uploaded by an enquiring organization, pays accumulated points to an
accumulated
point address of an organization holding the target blacklist data through an
associated
accumulated point node, uses a private key that matches the random public key
to decrypt
6
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
the packaged target blacklist data after the holding organization has
monitored entry into
the account of the accumulated points, and simultaneously invokes a public key
of the
enquiring organization to reversely encrypt the decrypted target blacklist
data for return
to the enquiring organization for decryption and enquiry; alternatively, any
member
organization can initiate a blacklist data deleting request via a
corresponding business
node, and deletes the target blacklist data after signature verification has
been passed and
deducts accumulated points in the associated accumulated point address.
[0032] Seen as such, when any member organization broadcasts the business
request via its
respective business node to the business alliance chain, the corresponding
business
request operation can be executed in the business alliance chain according to
consensus
results, if the business request executed is any one selected from a blacklist
data uploading
request, a blacklist data enquiring request, and a blacklist data deleting
request, the
relevant party that executes the current operation is bestowed with certain
accumulated
point award or deduction through the accumulated point alliance chain, thus
creating a
"paid" pattern of using shared blacklist data in exchange for accumulated
points, so that
the various member organizations are urged to timely and proactively share
blacklist data
in the business alliance chain on the basis of the above accumulated point
incentive policy,
and sharing scale and sharing value of the blacklist data are enhanced; in
addition, due to
the decentralized characteristic of the blockchain, use of the blacklist data
sharing method
based on a blockchain provided by the present invention requires no
centralized operating
organization, and possesses the characteristic of low operational cost, by
encrypted
storage of essential data, it is further possible to effectively protect
privacy of customers,
and achieve characteristics of safety and reliability.
[0033] According to another aspect, the present invention provides a blacklist
data sharing
system based on a blockchain, the system is applied to the blacklist data
sharing method
based on a blockchain as recited in the foregoing technical solution, and
comprises:
[0034] a blockchain constructing unit, for constructing respective network
nodes by member
7
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
organizations, and sequentially networking the network nodes belonging to the
various
member organizations to construct a blockchain, wherein the network nodes
include
business nodes and accumulated point nodes;
[0035] a blacklist data uploading unit, for initiating a blacklist data
uploading request via any
one business node, using a random public key to encrypt a generated symmetric
key while
employing the generated symmetric key to encrypt blacklist data, and
requesting by an
associated accumulated point node to transfer accumulated points to a
designated
accumulated point address during up-chaining and down-accounting by packaging
and
up-chaining the encrypted blacklist data and the encrypted symmetric key;
[0036] a blacklist data enquiring unit, for initiating a blacklist data
enquiring request via any one
business node, in the case target blacklist data is not uploaded by an
enquiring
organization, paying accumulated points to an accumulated point address of an
organization holding the target blacklist data through an associated
accumulated point
node, using a private key that matches the random public key to decrypt the
packaged
target blacklist data after the holding organization has monitored entry into
the account
of the accumulated points, and simultaneously invoking a public key of the
enquiring
organization to reversely encrypt the decrypted target blacklist data for
return to the
enquiring organization for decryption and enquiry; and
[0037] a blacklist data deleting unit, for initiating a blacklist data
deleting request via a business
node of the blacklist data holding organization itself, and deleting the
target blacklist data
after signature verification has been passed and deducting accumulated points
in the
associated accumulated point address.
[0038] Preferably, the blacklist data uploading unit includes:
[0039] an upload requesting module, for initiating a blacklist data uploading
request to the
business alliance chain by a member organization through a business node
belonging
thereto, and simultaneously designating an accumulated point address for
receiving
accumulated points;
[0040] a duplicate-checking module, for calculating a key value of blacklist
data to be uploaded,
8
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
and judging through the key value whether the blacklist data to be uploaded
has been
stored in the business alliance chain;
[0041] a first executing module, for, in the case a judging result is
negative, employing a
randomly generated symmetric key to encrypt the blacklist data and using a
random
public key to encrypt the symmetric key and executing packaging and up-
chaining
operations, in the case the judging result is positive, terminating the
current operation of
uploading the blacklist data; and
[0042] an accumulated point transacting module, for requesting the accumulated
point alliance
chain by the associated accumulated point node to transfer accumulated points
to the
designated accumulated point address, when it is monitored that the up-
chaining
operation and down-accounting of the blacklist data are triggered.
[0043] Preferably, the blacklist data enquiring unit includes:
[0044] an enquiry requesting module, for initiating a blacklist data enquiring
request to the
business alliance chain by a member organization through a business node
belong thereto,
and judging whether uploading is performed by the enquiring organization
according to
the accumulated point address associated with the blacklist data to be
enquired; and
[0045] a second executing module, for, in the case a judging result is
positive, invoking a private
key associated with the accumulated point address to decrypt the encrypted
symmetric
key and extract a plaintext symmetric key, and thereafter employing the
plaintext
symmetric key to decrypt detailed data in the file folder; in the case the
judging result is
negative, requesting the accumulated point alliance chain through the
associated
accumulated point node to pay accumulated points to the accumulated point
address of
the target blacklist data holding organization, using a private key that
matches the
associated accumulated point address to decrypt the encrypted symmetric key
after the
holding organization has monitored entry into the account of the accumulated
points,
invoking a public key of the enquiring organization to reversely encrypt the
plaintext
symmetric key after extracting the plaintext symmetric key, and thereafter
packaging the
reversely encrypted symmetric key and the undecrypted detailed data and
returning the
9
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
same to the enquiring organization for decryption and obtainment.
[0046] Preferably, the blacklist data deleting unit includes:
[0047] a deletion requesting module, for initiating a blacklist data deleting
request via a business
node of the blacklist data holding organization itself, and judging through
the business
alliance chain whether the accumulated point address associated therewith has
ample
accumulated points; and
[0048] a third executing module, for, in the case a judging result is
positive, using a private key
that matches the random public key to sign the target blacklist data, sending
signature
information together with the blacklist data deleting request to the business
alliance chain,
and deleting the target blacklist data after verification has been passed by
the business
alliance chain and deducting accumulated points in the associated accumulated
point
address, otherwise terminating the current operation of deleting the blacklist
data; and in
the case the judging result is negative, directly terminating the current
operation of
deleting the blacklist data.
[0049] In comparison with prior-art technology, the advantageous effects
achieved by the
blacklist data sharing system based on a blockchain provided by the present
invention are
identical with the advantageous effects achievable by the blacklist data
sharing method
based on a blockchain provided by the foregoing technical solution, so these
are not
redundantly described in this context.
BRIEF DESCRIPTION OF THE DRAWINGS
[0050] The drawings described here are meant to provide further understanding
of the present
invention, and constitute part of the present invention. The exemplary
embodiments of
the present invention and the descriptions thereof are meant to explain the
present
invention, rather than to constitute any improper restriction to the present
invention. In
the drawings:
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
[0051] Fig. 1 is a flowchart schematically illustrating the blacklist data
sharing method based on
a blockchain in Embodiment 1 of the present invention;
[0052] Fig. 2 is a view schematically illustrating the framework of a business
alliance chain and
an accumulated point alliance chain;
[0053] Fig. 3 is a flowchart schematically illustrating uploading blacklist
data via any one
business node to obtain accumulated points in Fig. 1;
[0054] Fig. 4 is a flowchart schematically illustrating enquiring blacklist
data via any one
business node to pay accumulated points in Fig. 1;
[0055] Fig. 5 is a flowchart schematically illustrating deleting blacklist
data via any one business
node to deduct accumulated points in Fig. 1; and
[0056] Fig. 6 is a block diagram illustrating the structure of the blacklist
data sharing system
based on a blockchain in Embodiment 2 of the present invention.
[0057] Reference Numerals:
[0058] 1 ¨ blockchain constructing unit 2¨ blacklist data uploading unit
[0059] 3 ¨ blacklist data enquiring unit 4¨ blacklist data deleting unit
[0060] 21 ¨ upload requesting module 22¨ duplicate-checking module
[0061] 23 ¨ first executing module 24 ¨ accumulated point transacting
module
[0062] 31 ¨ enquiry requesting module 32¨ second executing module
[0063] 41 ¨ deletion requesting module 42 ¨ third executing module
DETAILED DESCRIPTION OF THE INVENTION
[0064] To make more lucid and clear the objectives, features and advantages of
the present
invention, the technical solutions in the embodiments of the present invention
are clearly
and comprehensively described below with reference to the accompanying
drawings in
11
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
the embodiments of the present invention. Apparently, the embodiments as
described are
merely partial, rather than the entire, embodiments of the present invention.
All other
embodiments obtainable by persons ordinarily skilled in the art on the basis
of the
embodiments in the present invention without spending creative effort shall
all fall within
the protection scope of the present invention.
[0065] Embodiment 1
[0066] Please refer to Fig. 1, this embodiment provides a blacklist data
sharing method based on
a blockchain, and the method comprises:
[0067] constructing respective network nodes by member organizations, and
sequentially
networking the network nodes belonging to the various member organizations to
construct a blockchain, wherein the network nodes include business nodes and
accumulated point nodes; initiating a blacklist data uploading request via any
one
business node, using a random public key to encrypt a generated symmetric key
while
employing the generated symmetric key to encrypt blacklist data, and
requesting by an
associated accumulated point node to transfer accumulated points to a
designated
accumulated point address during up-chaining and down-accounting by packaging
and
up-chaining the encrypted blacklist data and the encrypted symmetric key; or
initiating a
blacklist data enquiring request via any one business node, in the case target
blacklist data
is not uploaded by an enquiring organization, paying accumulated points to an
accumulated point address of an organization holding the target blacklist data
through an
associated accumulated point node, using a private key that matches the random
public
key to decrypt the packaged target blacklist data after the holding
organization has
monitored entry into the account of the accumulated points, and simultaneously
invoking
a public key of the enquiring organization to reversely encrypt the decrypted
target
blacklist data for return to the enquiring organization for decryption and
enquiry; or
initiating a blacklist data deleting request via a business node of the
blacklist data holding
organization itself, and deleting the target blacklist data after signature
verification has
12
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
been passed and deducting accumulated points in the associated accumulated
point
address.
[0068] During specific implementation, in the blacklist data sharing method
based on a
blockchain provided by the present invention, a blockchain is constructed by
sequentially
accessing network nodes to which various member organizations correspond to a
network,
and each network node includes mutually associated business nodes and
accumulated
point nodes, of which the business node is used for initiating a business
request and
storing blacklist data, and the accumulated point node is used for executing
corresponding
accumulated point transaction and recording accumulated point information when
down-
accounting of the business request is triggered; exemplarily, any member
organization
can initiate a blacklist data uploading request via a corresponding business
node, uses a
random public key to encrypt a generated symmetric key while employing the
generated
symmetric key to encrypt blacklist data, and requests by an associated
accumulated point
node to transfer accumulated points to a designated accumulated point address
during up-
chaining and down-accounting by packaging and up-chaining the encrypted
blacklist data
and the encrypted symmetric key; alternatively, any member organization can
initiate a
blacklist data enquiring request via a corresponding business node, in the
case target
blacklist data is not uploaded by an enquiring organization, pays accumulated
points to
an accumulated point address of an organization holding the target blacklist
data through
an associated accumulated point node, uses a private key that matches the
random public
key to decrypt the packaged target blacklist data after the holding
organization has
monitored entry into the account of the accumulated points, and simultaneously
invokes
a public key of the enquiring organization to reversely encrypt the decrypted
target
blacklist data for return to the enquiring organization for decryption and
enquiry;
alternatively, any member organization can initiate a blacklist data deleting
request via a
corresponding business node, and deletes the target blacklist data after
signature
verification has been passed and deducts accumulated points in the associated
accumulated point address.
13
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
[0069] Seen as such, when any member organization broadcasts the business
request via its
respective business node to the business alliance chain, the corresponding
business
request operation can be executed in the business alliance chain according to
consensus
results, if the business request executed is any one selected from a blacklist
data uploading
request, a blacklist data enquiring request, and a blacklist data deleting
request, the
relevant party that executes the current operation is bestowed with certain
accumulated
point award or deduction through the accumulated point alliance chain, thus
creating a
"paid" pattern of using shared blacklist data in exchange for accumulated
points, so that
the various member organizations are urged to timely and proactively share
blacklist data
in the business alliance chain on the basis of the above accumulated point
incentive policy,
and sharing scale and sharing value of the blacklist data are enhanced; in
addition, due to
the decentralized characteristic of the blockchain, use of the blacklist data
sharing method
based on a blockchain provided by the present invention requires no
centralized operating
organization, and possesses the characteristic of low operational cost, by
encrypted
storage of essential data, it is further possible to effectively protect
privacy of customers,
and achieve characteristics of safety and reliability.
[0070] As should be understood by persons skilled in the art, the blacklist
business request in
this embodiment is not limited to the above three modes as the blacklist data
uploading
request, the blacklist data enquiring request, and the blacklist data deleting
request, as
other realizable business requests can be further included, such as a
blacklist data
downloading request, a blacklist data modifying request, etc.
[0071] Understandably, please refer to Fig. 2, the blockchain in this
embodiment includes a
business alliance chain, an accumulated point alliance chain, and an API
server, of which
the business alliance chain consists of plural business nodes networked
together, the
accumulated point alliance chain consists of plural accumulated point nodes
networked
together, the API server has enclosed sdk kits and external service frameworks
of the
14
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
business alliance chain and the accumulated point alliance chain, and the
function of the
API server is to connect the business alliance chain with the accumulated
point alliance
chain and to provide an externally servicing interface; the business alliance
chain includes
a business alliance chain body and an event monitoring server, of which the
business
alliance chain body is employed for the running of a smart contract and
providing
blacklist data storing and sharing services, and the event monitoring server
is employed
for monitoring events sent out of the business alliance chain body, and
simultaneously
initiating an accumulated point transferring request to the accumulated point
alliance
chain.
[0072] Specifically, please refer to Fig. 3, in this embodiment, the step of
initiating a blacklist
data uploading request via any one business node, using a random public key to
encrypt
a generated symmetric key while generated employing the symmetric key to
encrypt
blacklist data, and requesting by an associated accumulated point node to
transfer
accumulated points to a designated accumulated point address during up-
chaining and
down-accounting by packaging and up-chaining the encrypted blacklist data and
the
encrypted symmetric key includes:
[0073] initiating a blacklist data uploading request to the business alliance
chain by a member
organization through a business node belonging thereto, and simultaneously
designating
an accumulated point address for receiving accumulated points; calculating a
key value
of blacklist data to be uploaded, and judging through the key value whether
the blacklist
data to be uploaded has been stored in the business alliance chain; in the
case a judging
result is negative, employing a randomly generated symmetric key to encrypt
the blacklist
data and using a random public key to encrypt the symmetric key and executing
packaging and up-chaining operations, in the case the judging result is
positive,
terminating the current operation of uploading the blacklist data; and
requesting the
accumulated point alliance chain by the associated accumulated point node to
transfer
accumulated points to the designated accumulated point address, when it is
monitored
that the up-chaining operation and down-accounting of the blacklist data are
triggered.
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
[0074] Further, the step of employing a randomly generated symmetric key to
encrypt the
blacklist data and using a random public key to encrypt the symmetric key and
executing
packaging and up-chaining operations includes:
[0075] associatively marking the blacklist data, the accumulated point
address, and the random
public key, wherein the blacklist data includes names, IDs, and detailed data;
using the
randomly generated symmetric key to encrypt the detailed data, and storing the
names,
the IDs, and the encrypted detailed data in the same file folder; and using
the random
public key to encrypt the symmetric key for a second time, and thereafter
packaging the
symmetric key encrypted for the second time and the file folder and uploading
the same
to the business alliance chain.
[0076] During specific implementation, when it is required for a certain
member organization to
upload the blacklist data it possesses to the business alliance chain, the
name and the ID
of the blacklist data are firstly desensitized, an accumulated point address
and a random
public key are designated to be associatively marked with the blacklist data
to be
uploaded, the key value of the blacklist data to be uploaded is thereafter
calculated on the
basis of the name, ID and detailed data of the blacklist data to be uploaded,
and it is
judged whether the blacklist data to be uploaded has already existed in the
business
alliance chain by comparison with key values of blacklist data already stored
in the
business alliance chain, in the case the judging result is negative, the
detailed data is
encrypted by means of a randomly generated symmetric key, the name, ID and the
encrypted detailed data are stored in the same file folder, the random public
key associated
above is thereafter used to encrypt the symmetric key for a second time, and
the
symmetric key encrypted for the second time and the file folder are finally
packaged and
uploaded to the business alliance chain; in the case the judging result is
positive, the
current operation of uploading the blacklist data is terminated, and a request
is sent to the
accumulated point alliance chain to obtain accumulated points until the event
monitoring
server monitors that the up-chaining operation and down-accounting of the
blacklist data
16
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
are triggered.
[0077] As can be known from the above specific implementation process, since
the storage fields
of the packaged and up-chained blacklist data contain the symmetric key and
the file
folder encrypted with the symmetric key, in order to ensure safety of the
symmetric key,
it is required to use a random public key associated with the uploading
organization
address to separately encrypt the symmetric key for the second time, through
such mode
of encrypting for the second time the encrypted symmetric key and the
encrypted file
folder are stored together in the business alliance chain, whereby it is not
required for the
member organization to maintain the symmetric key used for each piece of
blacklist data,
and utilization complexity of the system is reduced at the same time of
ensuring safety;
in addition, by storing the encrypted symmetric key on the business alliance
chain, it is
made possible to make full use of bookkeeping characteristics of each business
node, and
to prevent the symmetric key from being lost.
[0078] With respect to enquiry of the blacklist data, this embodiment provides
two enquiring
patterns, namely a paid enquiring pattern and a free-of-charge enquiring
pattern, whose
specific realization steps are described in this embodiment as follows.
[0079] As regards basic information enquiring pattern, a basic information
enquiring request of
the blacklist data is initiated via any one business node, a name and an ID of
the target
blacklist data are input as key values in the business alliance chain, and
basic information
of the target blacklist data is returned by invoking a smart contract.
[0080] As regards detailed information enquiring pattern, please refer to Fig.
4, a blacklist data
enquiring request is initiated to the business alliance chain by a member
organization
through a business node belong thereto, and it is judged whether uploading is
performed
by the enquiring organization according to the accumulated point address
associated with
the blacklist data to be enquired; in the case a judging result is positive, a
private key
17
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
associated with the accumulated point address is invoked to decrypt the
encrypted
symmetric key and extract a plaintext symmetric key, and thereafter the
plaintext
symmetric key is employed to decrypt detailed data in the file folder; in the
case the
judging result is negative, the accumulated point alliance chain is requested
through the
associated accumulated point node to pay accumulated points to the accumulated
point
address of the target blacklist data holding organization, a private key that
matches the
associated accumulated point address is used to decrypt the encrypted
symmetric key
after the holding organization has monitored entry into the account of the
accumulated
points, the plaintext symmetric key is extracted and then a public key of the
enquiring
organization is invoked to reversely encrypt the plaintext symmetric key, and
thereafter
the reversely encrypted symmetric key and the undecrypted detailed data are
packaged
and returned to the enquiring organization for decryption and obtainment.
[0081] The accumulated point node includes plural accumulated point addresses,
and the
enquiring organization can select any one accumulated point address with ample
accumulated points to pay accumulated points to the accumulated point address
of the
target blacklist data holding organization.
[0082] Through the above settings of two blacklist data enquiring patterns,
the enquiring
organization can make free selections of enquiring requirements of the
blacklist data, so
that the application of the blacklist data sharing method based on a
blockchain is rendered
more flexible.
[0083] Please refer to Fig. 5, in this embodiment, the step of initiating a
blacklist data deleting
request via a business node of the blacklist data holding organization itself,
and deleting
the target blacklist data after signature verification has been passed and
deducting
accumulated points in the associated accumulated point address includes:
[0084] initiating a blacklist data deleting request via a business node of the
blacklist data holding
organization itself, and judging through the business alliance chain whether
the
18
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
accumulated point address associated therewith has ample accumulated points;
in the case
a judging result is positive, using a private key that matches the random
public key to
sign the target blacklist data, sending signature information together with
the blacklist
data deleting request to the business alliance chain, and deleting the target
blacklist data
after verification has been passed by the business alliance chain and
deducting
accumulated points in the associated accumulated point address, otherwise
terminating
the current operation of deleting the blacklist data; and in the case the
judging result is
negative, directly terminating the current operation of deleting the blacklist
data.
[0085] During specific implementation, when it is required for the blacklist
data holding
organization to delete a certain piece of blacklist data, a blacklist data
deleting request is
firstly initiated via a business node of its own, and it is thereafter judged
whether the
accumulated point address associated with the blacklist data has ample
accumulated
points; when the associated accumulated point address has ample accumulated
points, a
private key that matches the encrypting random public key is used to sign the
target
blacklist data, the signature information is sent together with the blacklist
data deleting
request to the business alliance chain, and the target blacklist data is
deleted after
verification has been passed by the business alliance chain and accumulated
points in the
associated accumulated point address are deducted, otherwise the current
operation of
deleting the blacklist data is terminated; when the associated accumulated
point address
has insufficient accumulated points, any other accumulated point address of
the holding
organization having ample accumulated points can be selected to deduct
corresponding
accumulated points, and the operation of deleting the blacklist data is
subsequently
executed; if none of the accumulated point addresses of the holding
organization has
ample accumulated points, the current operation of deleting the blacklist data
is directly
terminated.
[0086] As can be known from the above specific implementation process, when
the holding
organization deletes any blacklist data, it is firstly required to verify its
identification,
19
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
namely to verify whether it is the uploading organization of this piece of
blacklist data,
and this piece of blacklist data can be deleted only after the verification
has been passed,
so that safety of blacklist data in the business alliance chain is guaranteed.
[0087] Embodiment 2
[0088] Please refer to Fig. 1 and Fig. 6, this embodiment provides a blacklist
data sharing system
based on a blockchain, and the system comprises:
[0089] a blockchain constructing unit 1, for constructing respective network
nodes by member
organizations, and sequentially networking the network nodes belonging to the
various
member organizations to construct a blockchain, wherein the network nodes
include
business nodes and accumulated point nodes;
[0090] a blacklist data uploading unit 2, for initiating a blacklist data
uploading request via any
one business node, using a random public key to encrypt a generated symmetric
key while
employing the generated symmetric key to encrypt blacklist data, and
requesting by an
associated accumulated point node to transfer accumulated points to a
designated
accumulated point address during up-chaining and down-accounting by packaging
and
up-chaining the encrypted blacklist data and the encrypted symmetric key;
[0091] a blacklist data enquiring unit 3, for initiating a blacklist data
enquiring request via any
one business node, in the case target blacklist data is not uploaded by an
enquiring
organization, paying accumulated points to an accumulated point address of an
organization holding the target blacklist data through an associated
accumulated point
node, using a private key that matches the random public key to decrypt the
packaged
target blacklist data after the holding organization has monitored entry into
the account
of the accumulated points, and simultaneously invoking a public key of the
enquiring
organization to reversely encrypt the decrypted target blacklist data for
return to the
enquiring organization for decryption and enquiry; and
[0092] a blacklist data deleting unit 4, for initiating a blacklist data
deleting request via a business
node of the blacklist data holding organization itself, and deleting the
target blacklist data
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
after signature verification has been passed and deducting accumulated points
in the
associated accumulated point address.
[0093] Preferably, the blacklist data uploading unit 2 includes:
[0094] an upload requesting module 21, for initiating a blacklist data
uploading request to the
business alliance chain by a member organization through a business node
belonging
thereto, and simultaneously designating an accumulated point address for
receiving
accumulated points;
[0095] a duplicate-checking module 22, for calculating a key value of
blacklist data to be
uploaded, and judging through the key value whether the blacklist data to be
uploaded
has been stored in the business alliance chain;
[0096] a first executing module 23, for, in the case a judging result is
negative, employing a
randomly generated symmetric key to encrypt the blacklist data and using a
random
public key to encrypt the symmetric key and executing packaging and up-
chaining
operations, in the case the judging result is positive, terminating the
current operation of
uploading the blacklist data; and
[0097] an accumulated point transacting module 24, for requesting the
accumulated point
alliance chain by the associated accumulated point node to transfer
accumulated points
to the designated accumulated point address, when it is monitored that the up-
chaining
operation and down-accounting of the blacklist data are triggered.
[0098] Preferably, the blacklist data enquiring unit 3 includes:
[0099] an enquiry requesting module 31, for initiating a blacklist data
enquiring request to the
business alliance chain by a member organization through a business node
belong thereto,
and judging whether uploading is performed by the enquiring organization
according to
the accumulated point address associated with the blacklist data to be
enquired; and
[0100] a second executing module 32, for, in the case a judging result is
positive, invoking a
private key associated with the accumulated point address to decrypt the
encrypted
symmetric key and extract a plaintext symmetric key, and thereafter employing
the
21
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
plaintext symmetric key to decrypt detailed data in the file folder; in the
case the judging
result is negative, requesting the accumulated point alliance chain through
the associated
accumulated point node to pay accumulated points to the accumulated point
address of
the target blacklist data holding organization, using a private key that
matches the
associated accumulated point address to decrypt the encrypted symmetric key
after the
holding organization has monitored entry into the account of the accumulated
points,
invoking a public key of the enquiring organization to reversely encrypt the
plaintext
symmetric key after extracting the plaintext symmetric key, and thereafter
packaging the
reversely encrypted symmetric key and the undecrypted detailed data and
returning the
same to the enquiring organization for decryption and obtainment.
[0101] Preferably, the blacklist data enquiring unit 3 includes:
[0102] an enquiry requesting module 31, for initiating a blacklist data
enquiring request to the
business alliance chain by a member organization through a business node
belong thereto,
and judging whether uploading is performed by the enquiring organization
according to
the accumulated point address associated with the blacklist data to be
enquired; and
[0103] a second executing module 32, for, in the case a judging result is
positive, invoking a
private key associated with the accumulated point address to decrypt the
encrypted
symmetric key and extract a plaintext symmetric key, and thereafter employing
the
plaintext symmetric key to decrypt detailed data in the file folder; in the
case the judging
result is negative, requesting the accumulated point alliance chain through
the associated
accumulated point node to pay accumulated points to the accumulated point
address of
the target blacklist data holding organization, using a private key that
matches the
associated accumulated point address to decrypt the encrypted symmetric key
after the
holding organization has monitored entry into the account of the accumulated
points,
invoking a public key of the enquiring organization to reversely encrypt the
plaintext
symmetric key after extracting the plaintext symmetric key, and thereafter
packaging the
reversely encrypted symmetric key and the undecrypted detailed data and
returning the
same to the enquiring organization for decryption and obtainment.
22
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
[0104] Preferably, the blacklist data deleting unit 4 includes:
[0105] a deletion requesting module 41, for initiating a blacklist data
deleting request via a
business node of the blacklist data holding organization itself, and judging
through the
business alliance chain whether the accumulated point address associated
therewith has
ample accumulated points; and
[0106] a third executing module 42, for, in the case a judging result is
positive, using a private
key that matches the random public key to sign the target blacklist data,
sending signature
information together with the blacklist data deleting request to the business
alliance chain,
and deleting the target blacklist data after verification has been passed by
the business
alliance chain and deducting accumulated points in the associated accumulated
point
address, otherwise terminating the current operation of deleting the blacklist
data; and in
the case the judging result is negative, directly terminating the current
operation of
deleting the blacklist data.
[0107] In comparison with prior-art technology, the advantageous effects
achieved by the
blacklist data sharing system based on a blockchain provided by this
embodiment of the
present invention are identical with the advantageous effects achievable by
the blacklist
data sharing method based on a blockchain provided by Embodiment 1, so these
are not
redundantly described in this context.
[0108] As understandable to persons ordinarily skilled in the art, the entire
or partial steps
realizing the method of the present invention can be completed via a program
that
instructs relevant hardware, the program can be stored in a computer-readable
storage
medium, and subsumes the various steps of the method in the foregoing
embodiment
when it is executed, while the storage medium can be an ROM/RAM, a magnetic
disk,
an optical disk, or a memory card, etc.
[0109] What the above describes is merely directed to specific modes of
execution of the present
23
Date Regue/Date Received 2022-09-19

CA 03175939 2022-09-19
invention, but the protection scope of the present invention is not restricted
thereby. Any
change or replacement easily conceivable to persons skilled in the art within
the technical
range disclosed by the present invention shall be covered by the protection
scope of the
present invention. Accordingly, the protection scope of the present invention
shall be
based on the protection scope as claimed in the Claims.
24
Date Regue/Date Received 2022-09-19

Representative Drawing
A single figure which represents the drawing illustrating the invention.
Administrative Status

2024-08-01:As part of the Next Generation Patents (NGP) transition, the Canadian Patents Database (CPD) now contains a more detailed Event History, which replicates the Event Log of our new back-office solution.

Please note that "Inactive:" events refers to events no longer in use in our new back-office solution.

For a clearer understanding of the status of the application/patent presented on this page, the site Disclaimer , as well as the definitions for Patent , Event History , Maintenance Fee  and Payment History  should be consulted.

Event History

Description Date
Inactive: Grant downloaded 2024-06-27
Inactive: Grant downloaded 2024-06-27
Letter Sent 2024-06-25
Grant by Issuance 2024-06-25
Inactive: Cover page published 2024-06-24
Inactive: Final fee received 2024-05-14
Pre-grant 2024-05-14
Letter Sent 2024-04-24
Notice of Allowance is Issued 2024-04-24
Inactive: Approved for allowance (AFA) 2024-04-22
Inactive: Q2 passed 2024-04-22
Amendment Received - Voluntary Amendment 2024-02-12
Amendment Received - Response to Examiner's Requisition 2024-02-12
Examiner's Report 2023-10-11
Inactive: Report - No QC 2023-10-10
Letter sent 2023-09-29
Advanced Examination Determined Compliant - paragraph 84(1)(a) of the Patent Rules 2023-09-29
Amendment Received - Voluntary Amendment 2023-09-22
Inactive: Advanced examination (SO) fee processed 2023-09-22
Amendment Received - Voluntary Amendment 2023-09-22
Inactive: Advanced examination (SO) 2023-09-22
Letter sent 2022-10-19
Application Received - PCT 2022-10-18
Inactive: First IPC assigned 2022-10-18
Letter Sent 2022-10-18
Priority Claim Requirements Determined Compliant 2022-10-18
Request for Priority Received 2022-10-18
Inactive: IPC assigned 2022-10-18
National Entry Requirements Determined Compliant 2022-09-19
Request for Examination Requirements Determined Compliant 2022-09-19
All Requirements for Examination Determined Compliant 2022-09-19
Application Published (Open to Public Inspection) 2020-09-24

Abandonment History

There is no abandonment history.

Maintenance Fee

The last payment was received on 2023-12-15

Note : If the full payment has not been received on or before the date indicated, a further fee may be required which may be one of the following

  • the reinstatement fee;
  • the late payment fee; or
  • additional fee to reverse deemed expiry.

Please refer to the CIPO Patent Fees web page to see all current fee amounts.

Fee History

Fee Type Anniversary Year Due Date Paid Date
MF (application, 3rd anniv.) - standard 03 2022-10-03 2022-09-19
Request for examination - standard 2024-10-01 2022-09-19
MF (application, 2nd anniv.) - standard 02 2021-10-01 2022-09-19
Reinstatement (national entry) 2022-09-20 2022-09-19
Basic national fee - standard 2022-09-20 2022-09-19
MF (application, 4th anniv.) - standard 04 2023-10-03 2023-06-15
Advanced Examination 2023-09-22
MF (application, 5th anniv.) - standard 05 2024-10-01 2023-12-15
Final fee - standard 2024-05-14
Owners on Record

Note: Records showing the ownership history in alphabetical order.

Current Owners on Record
10353744 CANADA LTD.
Past Owners on Record
WEI SHENG
ZHITAN ZHENG
Past Owners that do not appear in the "Owners on Record" listing will appear in other documentation within the application.
Documents

To view selected files, please enter reCAPTCHA code :



To view images, click a link in the Document Description column. To download the documents, select one or more checkboxes in the first column and then click the "Download Selected in PDF format (Zip Archive)" or the "Download Selected as Single PDF" button.

List of published and non-published patent-specific documents on the CPD .

If you have any difficulty accessing content, you can call the Client Service Centre at 1-866-997-1936 or send them an e-mail at CIPO Client Service Centre.


Document
Description 
Date
(yyyy-mm-dd) 
Number of pages   Size of Image (KB) 
Claims 2024-02-12 18 1,140
Cover Page 2024-05-27 1 72
Representative drawing 2024-05-27 1 36
Claims 2023-09-22 24 1,578
Representative drawing 2023-02-25 1 33
Claims 2022-09-19 7 355
Description 2022-09-19 24 1,208
Abstract 2022-09-19 1 25
Drawings 2022-09-19 5 198
Cover Page 2023-02-25 2 81
Electronic Grant Certificate 2024-06-25 1 2,527
Amendment / response to report 2024-02-12 58 2,717
Final fee 2024-05-14 3 62
Commissioner's Notice - Application Found Allowable 2024-04-24 1 576
Courtesy - Letter Acknowledging PCT National Phase Entry 2022-10-19 1 594
Courtesy - Acknowledgement of Request for Examination 2022-10-18 1 423
Advanced examination (SO) / Amendment / response to report 2023-09-22 30 1,275
Courtesy - Advanced Examination Request - Compliant (SO) 2023-09-29 1 176
Examiner requisition 2023-10-11 7 342
National entry request 2022-09-19 13 1,297
International search report 2022-09-19 7 278
Amendment - Abstract 2022-09-19 2 125