Global Patent Index - EP 4027598 A4

EP 4027598 A4 20221026 - VIRTUAL PRIVATE CLOUD COMMUNICATION METHOD, VIRTUAL PRIVATE CLOUD COMMUNICATION CONFIGURATION METHOD, AND RELATED APPARATUSES

Title (en)

VIRTUAL PRIVATE CLOUD COMMUNICATION METHOD, VIRTUAL PRIVATE CLOUD COMMUNICATION CONFIGURATION METHOD, AND RELATED APPARATUSES

Title (de)

VERFAHREN ZUR KOMMUNIKATION MIT EINER VIRTUELLEN PRIVATEN CLOUD, KONFIGURATIONSVERFAHREN FÜR DIE KOMMUNIKATION MIT EINER VIRTUELLEN PRIVATEN CLOUD UND ZUGEHÖRIGE GERÄTE

Title (fr)

PROCÉDÉ DE COMMUNICATION EN NUAGE PRIVÉ VIRTUEL, PROCÉDÉ DE CONFIGURATION DE COMMUNICATION EN NUAGE PRIVÉ VIRTUEL ET APPAREILS ASSOCIÉS

Publication

EP 4027598 A4 20221026 (EN)

Application

EP 20909186 A 20200904

Priority

  • CN 201911424858 A 20191231
  • CN 2020113379 W 20200904
  • CN 201910389727 A 20190510

Abstract (en)

[origin: EP4027598A1] Embodiments of the present invention provide a virtual private cloud communication and configuration method, and a related apparatus and system. The configuration method includes: binding a private network address in a first VPC with a first address, where the first address is an address that belongs to a private network address segment of a third VPC; binding a private network address in a second VPC with a second address, where the second address is an address that belongs to the private network address segment of the third VPC, and the first address is different from the second address; configuring a source address of a packet sent by the first VPC to the second VPC, as the first address; and configuring a destination address of the packet sent by the first VPC to the second VPC, as the second address. Through bridging of the third VPC, the first VPC accesses the second VPC by accessing the second address bound with the second VPC, and the second VPC accesses the first VPC by accessing the first address bound with the first VPC. In this way, communication between the first VPC and the second VPC can be implemented when a private network address segment of the first VPC overlaps with a private network address segment of the second VPC, and a technical problem that VPCs on a cloud cannot communicate with each other due to overlapping private network addresses can be effectively resolved.

IPC 8 full level

H04L 45/74 (2022.01); H04L 12/46 (2006.01); H04L 41/0895 (2022.01); H04L 61/2514 (2022.01); H04L 61/2521 (2022.01); H04L 41/22 (2022.01)

CPC (source: CN EP KR US)

H04L 12/4633 (2013.01 - CN EP); H04L 12/4641 (2013.01 - CN EP); H04L 41/0895 (2022.05 - CN EP KR); H04L 45/74 (2013.01 - CN EP KR US); H04L 61/2514 (2013.01 - CN EP KR); H04L 61/2528 (2013.01 - US); H04L 61/2535 (2013.01 - CN EP KR); H04L 61/2553 (2013.01 - KR); H04L 61/50 (2022.05 - KR); H04L 41/22 (2013.01 - CN EP)

Citation (search report)

Designated contracting state (EPC)

AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

Designated extension state (EPC)

BA ME

Designated validation state (EPC)

KH MA MD TN

DOCDB simple family (publication)

EP 4027598 A1 20220713; EP 4027598 A4 20221026; CN 111917649 A 20201110; CN 111917649 B 20220628; CN 111917893 A 20201110; CN 111917893 B 20220712; CN 115699699 A 20230203; CN 115699699 B 20230512; CN 116057910 A 20230502; CN 116057910 B 20231103; CN 116800712 A 20230922; CN 117692334 A 20240312; EP 4084438 A1 20221102; EP 4084438 A4 20221207; JP 2022546802 A 20221109; KR 20220134554 A 20221005; KR 20220134555 A 20221005; US 2022337545 A1 20221020; WO 2021135344 A1 20210708; WO 2021135345 A1 20210708

DOCDB simple family (application)

EP 20909186 A 20200904; CN 201911424828 A 20191231; CN 201911424858 A 20191231; CN 2020113370 W 20200904; CN 2020113379 W 20200904; CN 202080097771 A 20200904; CN 202080097806 A 20200904; CN 202310745229 A 20200904; CN 202311654518 A 20200904; EP 20908562 A 20200904; JP 2022507499 A 20200904; KR 20227026455 A 20200904; KR 20227026456 A 20200904; US 202217855531 A 20220630