Patent SG-11201903572Y-A (SG)
Title: Managing communications among consensus nodes and client nodes
Inventor: PAN DONG
Filed: 2018-11-07
Abstract: WO 19/07 2267 A2 (12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT) (19) World Intellectual Property Organization International Bureau (43) International Publication Date 18 April 2019 (18.04.2019) WIPO I PCT 11111111111111011111111111111110111110100111111111110111011111111111111111011110111111 (10) International Publication Number WO 2019/072267 A2 Camerae men 306a Determining CAs (51) International Patent Classification: Not classified (21) International Application Number: PCT/CN2018/114417 (22) International Filing Date: 07 November 2018 (07.11.2018) (25) Filing Language: English (26) Publication Language: English (71) Applicant: ALIBABA GROUP HOLDING LIMITED [—/CN]; Fourth Floor, One Capital Place, P.O. Box 847, George Town, Grand Cayman (KY). (72) Inventors: PAN, Dong; Alibaba Group Legal Department 5/F, Building 3, No. 969 West Wen Yi Road, Yuhang Dis- trict, Hangzhou, Zhejiang 311121 (CN). YAN, Xuebing; Alibaba Group Legal Department 5/F, Building 3, No. 969 West Wen Yi Road, Yuhang District, Hangzhou, Zhejiang 311121 (CN). CHEN, Shenglong; Alibaba Group Legal Department 5/F, Building 3, No. 969 West Wen Yi Road, Yuhang District, Hangzhou, Zhejiang 311121 (CN). (74) Agent: BEIJING BESTIPR INTELLECTUAL PROP- ERTY LAW CORPORATION; Room 409, Tower B, Ka Wah Building, No. 9 Shangdi 3rd Street, Haidian District, Beijing 100085 (CN). (81) Designated States (unless otherwise indicated, for every kind of national protection available): AE, AG, AL, AM, AO, AT, AU, AZ, BA, BB, BG, BH, BN, BR, BW, BY, BZ, CA, CH, CL, CN, CO, CR, CU, CZ, DE, DJ, DK, DM, DO, DZ, EC, EE, EG, ES, FI, GB, GD, GE, GH, GM, GT, HN, HR, HU, ID, IL, IN, IR, IS, JO, JP, KE, KG, KH, KN, KP, KR, KW, KZ, LA, LC, LK, LR, LS, LU, LY, MA, MD, ME, MG, MK, MN, MW, MX, MY, MZ, NA, NG, NI, NO, NZ, OM, PA, PE, PG, PH, PL, PT, QA, RO, RS, RU, RW, SA, SC, SD, SE, SG, SK, SL, SM, ST, SV, SY, TH, TJ, TM, TN, TR, TT, TZ, UA, UG, US, UZ, VC, VN, ZA, ZM, ZW. (84) Designated States (unless otherwise indicated, for every kind of regional protection available): ARIPO (BW, GH, GM, KE, LR, LS, MW, MZ, NA, RW, SD, SL, ST, SZ, TZ, UG, ZM, ZW), Eurasian (AM, AZ, BY, KG, KZ, RU, TJ, TM), European (AL, AT, BE, BG, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GR, HR, HU, 1E, IS, IT, LT, LU, LV, MC, MK, MT, NL, NO, PL, PT, RO, RS, SE, SI, SK, SM, TR), OAPI (BF, BJ, CF, CG, CI, CM, GA, GN, GQ, GW, KM, ML, MR, NE, SN, TD, TG). (54) Title: MANAGING COMMUNICATIONS AMONG CONSENSUS NODES AND CLIENT NODES (57) : Implementations of the present disclosure include generating, 3008 by a consensus node, a certificate signing request (CSR); sending the CSR to a first certificate authority (CA); receiving a first public key certificate of the consensus node from the first CA, and a first one or more public key certifi- _,-302a 3 GAs cates issued by a first one or more CAs. The consensus nodes also sends the CSR to a second CA, receives a second public key certificate of the consensus node from the second CA, and a second one or more public key certificates issued by a second one or more CAs. The consensus node further configures a 308a first tmststore including the first public key certificate and the first one or more ye a loll public key certificates, and a second tmststore including the second public key and selkigned catificales certificate and the second one or more public key certificates. 310a Sending sekigned cerdadel 312a Genering CS& 314a Sending dighly signed CSRelo CAs 316a Goosing NW: dig 318a WIN pubic key mates t comma nodes 320a Configwing tustStae, Ova imp, end selfaiped certificates bycomensus nodes FIG. 3A [Continued on next page] WO 2019/072267 x2111111 IIIIIIII 0 DOI 11111 ME 0 III 1101 0 01 110111111111111111111111111111111011110 HIE Published: upon request of the applicant, before the expiration of the time limit referred to in Article 21(2)(a) without international search report and to be republished upon receipt of that report (Rule 48.2(g))