# US 2021/0083902 A1 · Method for Managing Virtual Private Network, and Device > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0083902 A1 - Document ID: US20210083902A1 - Status: Published application - Kind: A1 - Application number: 17/106,931 - Filed: 2020-11-30 - Published: 2021-03-18 - Earliest claimed: 2018-06-01 - Assignees: Huawei Technologies Co., Ltd. - Applicants: Huawei Technologies Co., Ltd. - Inventors: Shunwan Zhuang; Haibo Wang; Penghui Mi; Yunan Gu; Gang Yan; Zhenbin Li - Web page: https://patentgrep.com/patent/US20210083902A1 ## CPC - H04L 45/04: {Interdomain routing, e.g. hierarchical routing} - H04L 12/4641: {Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272)} - H04L 12/4675: {Dynamic sharing of VLAN information amongst network nodes (configuration of the network or of network elements H04L41/08)} - H04L 45/033: by updating distance vector protocols - H04L 45/34: {Source routing} - H04L 45/50: using label swapping, e.g. multi-protocol label switch [MPLS] - H04L 45/507: {Label distribution} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract In a method for managing a VPN, a routing device establishes a BMP session with a BMP server. The routing device allocates a VPN label associated with a VPN instance, wherein the VPN instance is used for communication between the routing device and another routing device. Then, the routing device sends, to the BMP server, a BMP message that carries the VPN label. Because the routing device sends the VPN label through the BMP message, the routing device does not need to establish a BGP peer relationship with the BMP server to send the VPN label. ## Claims ### Claim 1 A method for managing a virtual private network (VPN), implemented by a first routing device, and comprising: establishing a BGP Monitoring Protocol (BMP) session with a BMP server; allocating a VPN label associated with a VPN instance for communication between the first routing device and a second routing device; and sending, to the BMP server, a BMP message comprising the VPN label. ### Claim 2 (depends on 1) The method of claim 1, wherein the BMP message is an extended peer up notification message comprising a type-length-value (TLV), and wherein the TLV comprises the VPN label. ### Claim 3 (depends on 1) The method of claim 1, wherein the BMP message is a newly-defined BMP message comprising a protocol data unit (PDU), and wherein the PDU comprises the VPN label. ### Claim 4 (depends on 3) The method of claim 3, wherein the PDU comprises an identifier of the VPN instance and a corresponding relationship between the VPN label and an Internet Protocol (IP) address segment to which an IP address of a user equipment (UE) belongs. ### Claim 5 (depends on 1) The method of claim 1, wherein the VPN label is a multi-protocol label switching (MPLS) label or a Segment Routing over IPv6 (SRv6) segment identifier (SID). ### Claim 6 (depends on 1) The method of claim 1, further comprising: receiving, from the second routing device, a data packet whose destination is a user equipment (UE) and which comprises the VPN label; deleting the VPN label in the data packet to obtain a processed data packet; and sending the processed data packet to the UE based on the VPN label. ### Claim 7 A method for managing a virtual private network (VPN), implemented by a BMP Monitoring Protocol (BMP) server, and comprising: establishing a BMP session with a first routing device; receiving, from the first routing device, a BMP message comprising a VPN label; obtaining routing information based on the VPN label, wherein the routing information comprises the VPN label, a destination address segment, a VPN instance identifier, and a next hop; and sending the routing information to a second routing device. ### Claim 8 (depends on 7) The method of claim 7, wherein the BMP message is an extended peer up notification message comprising a type-length-value (TLV), and wherein the TLV comprises the VPN label. ### Claim 9 (depends on 7) The method of claim 7, wherein the BMP message is a newly-defined BMP message comprising a protocol data unit (PDU), and wherein the PDU comprises the VPN label. ### Claim 10 (depends on 9) The method of claim 9, wherein the PDU comprises the routing information. ### Claim 11 (depends on 7) The method of claim 7, wherein the destination address segment comprises a first Internet Protocol (IP) address of a user equipment (UE), wherein the VPN instance identifier identifies a VPN instance that is on the first routing device and that is for communicating with the second routing device, and wherein the next hop is a second IP address of the first routing device. ### Claim 12 A first routing device comprising: a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to: establish a BGP Monitoring Protocol (BMP) session with a BMP server; allocate a virtual private network (VPN) label associated with a VPN instance for communication between the first routing device and a second routing device; and send, to the BMP server, a BMP message comprising the VPN label. ### Claim 13 (depends on 12) The first routing device of claim 12, wherein the BMP message is an extended peer up notification message comprising a type-length-value (TLV), and wherein the TLV comprises the VPN label. ### Claim 14 (depends on 12) The first routing device of claim 12, wherein the BMP message is a newly-defined BMP message comprising a protocol data unit (PDU), and wherein the PDU comprises the VPN label. ### Claim 15 (depends on 14) The first routing device of claim 14, wherein the PDU comprises an identifier of the VPN instance and a corresponding relationship between the VPN label and an Internet Protocol (IP) address segment to which an IP address of a user equipment (UE) belongs. ### Claim 16 (depends on 12) The first routing device of claim 12, wherein the VPN label is a multi-protocol label switching (MPLS) label or a Segment Routing over IPv6 (SRv6) segment identifier (SID). ### Claim 17 (depends on 12) The first routing device of claim 12, wherein the processor is further configured to: receive, from the second routing device, a data packet whose destination is a user equipment (UE) and which comprises the VPN label; delete the VPN label in the data packet to obtain a processed data packet; and send the processed data packet to the UE based on the VPN label. ### Claim 18 A BGP Monitoring Protocol (BMP) server comprising: a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to: establish a BMP session with a first routing device; receive, from the first routing device, a BMP message comprising a virtual private network (VPN) label; obtain routing information based on the VPN label, wherein the routing information comprises the VPN label, a destination address segment, a VPN instance identifier, and a next hop; and send the routing information to a second routing device. ### Claim 19 (depends on 18) The BMP server of claim 18, wherein the BMP message is an extended peer up notification message comprising a type-length-value (TLV) and wherein the TLV comprises the VPN label. ### Claim 20 (depends on 18) The BMP server of claim 18, wherein the BMP message is a newly-defined BMP message, comprising a protocol data unit (PDU), and wherein the PDU comprises the VPN label. ### Claim 21 (depends on 20) The BMP server of claim 20, wherein the PDU comprises the routing information. ### Claim 22 (depends on 18) The BMP server of claim 18, wherein the destination address segment comprises a first Internet Protocol (IP) address of a user equipment (UE), wherein the VPN instance identifier identifies a VPN instance that is on the first routing device and that is for communicating with the second routing device, and wherein the next hop is a second IP address of the first routing device.