# US 2021/0344567 A1 · Connectivity detection session creation method, network device, and system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0344567 A1
- Document ID: US20210344567A1
- Status: Published application
- Kind: A1
- Application number: 17/375,348
- Filed: 2021-07-14
- Published: 2021-11-04
- Earliest claimed: 2019-01-16
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Huawei Technologies Co., Ltd.
- Inventors: Xiaojing LI
- Web page: https://patentgrep.com/patent/US20210344567A1

## CPC

- 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/1877: {Measures taken prior to transmission}
- H04L 45/66: {Layer 2 routing, e.g. in Ethernet based MAN's}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A connectivity detection session creation method, a network device, and a system, to create a connectivity detection session in an EVPN. The method includes: receiving, by the first network device, a creation message of a connectivity detection session from the second network device, where the creation message of the connectivity detection session carries an inclusive multicast route of the second network device and session information of the second network device; determining, by the first network device, that a local inclusive multicast routing table includes the inclusive multicast route of the second network device; and creating, by the first network device, the connectivity detection session with the second network device based on the session information of the second network device.

## Claims

### Claim 1

A connectivity detection session creation method, wherein the method is applied to an Ethernet virtual private network (EVPN), the EVPN comprises a first network device and a second network device, and the method comprises:
receiving, by the first network device, a creation message of a connectivity detection session from the second network device, wherein the creation message of the connectivity detection session carries an inclusive multicast route of the second network device and session information of the second network device;
determining, by the first network device, that a local inclusive multicast routing table comprises the inclusive multicast route of the second network device; and
creating, by the first network device, the connectivity detection session with the second network device based on the session information of the second network device.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the receiving, by the first network device, of a creation message of a connectivity detection session from the second network device comprises:
receiving, by the first network device, the creation message of the connectivity detection session that is sent by the second network device in a broadcast or multicast manner.

### Claim 3 (depends on 1)

The method according to claim 1, wherein before the receiving, by the first network device, of a creation message of a connectivity detection session from the second network device, the method further comprises:
obtaining, by the first network device, the inclusive multicast routing table, wherein the inclusive multicast routing table comprises the inclusive multicast route of the second network device.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the connectivity detection session comprises a connectivity fault management (CFM) session.

### Claim 5 (depends on 1)

The method according to claim 1, wherein a type-length-value (TLV) field in the creation message of the connectivity detection session comprises the inclusive multicast route of the second network device, the TLV field comprises a type, a length, and a value, the type is used to indicate that a type of the TLV field is the inclusive multicast route, the length is used to indicate a length of the TLV field, and the value is the inclusive multicast route of the second network device.

### Claim 6 (depends on 1)

The method according to claim 1, wherein the session information of the second network device comprises a maintenance association end point identifier (MEP ID) or a session identifier (Session ID) of the second network device.

### Claim 7 (depends on 6)

The method according to claim 6, further comprising:
obtaining, by the first network device, an MEP ID range or a session ID range, wherein the MEP ID range comprises the MEP ID of the second network device, or the session ID range comprises the session ID of the second network device; and
before the creating, by the first network device, of the connectivity detection session with the second network device based on the session information of the second network device, the method further comprises:
determining, by the first network device, that the MEP ID of the second network device is within the MEP ID range; or
determining, by the first network device, that the session ID of the second network device is within the session ID range.

### Claim 8

A connectivity detection session creation method, wherein the method is applied to an Ethernet virtual private network (EVPN), the EVPN comprises a first network device and a second network device, and the method comprises:
obtaining, by the second network device, an inclusive multicast route of the second network device; and
sending, by the second network device, a creation message of a connectivity detection session to the first network device, wherein the creation message of the connectivity detection session carries the inclusive multicast route and session information of the second network device, and the session information is used to create the connectivity detection session.

### Claim 9 (depends on 8)

The method according to claim 8, wherein the sending, by the second network device, of a creation message of a connectivity detection session to the first network device comprises:
sending, by the second network device, the creation message of the connectivity detection session to each network device in the EVPN in a broadcast or multicast manner.

### Claim 10 (depends on 8)

The method according to claim 8, wherein the connectivity detection session comprises a connectivity fault management (CFM) session.

### Claim 11 (depends on 8)

The method according to claim 8, wherein a type-length-value (TLV) field in the creation message of the connectivity detection session comprises the inclusive multicast route of the second network device, the TLV field comprises a type, a length, and a value, the type is used to indicate that a type of the TLV field is the inclusive multicast route, the length is used to indicate a length of the TLV field, and the value is the inclusive multicast route of the second network device.

### Claim 12 (depends on 8)

The method according to claim 8, wherein the session information of the second network device comprises a maintenance association end point identifier (MEP ID) or a session identifier (session ID) of the second network device.

### Claim 13

A network device serving as a first network device, comprising:
a transceiver, a memory, and a processor, wherein
the processor is configured to execute a computer-readable instruction in the memory to cause the network device to perform the following operations:
receiving a creation message of a connectivity detection session from a second network device, wherein the creation message of the connectivity detection session carries an inclusive multicast route of the second network device and session information of the second network device;
determining that a local inclusive multicast routing table comprises the inclusive multicast route of the second network device; and
creating the connectivity detection session with the second network device based on the session information of the second network device.

### Claim 14 (depends on 13)

The first network device according to claim 13, wherein the processor is configured to execute the instruction to cause the network device to:
receive the creation message of the connectivity detection session that is sent by the second network device in a broadcast or multicast manner.

### Claim 15 (depends on 13)

The first network device according to claim 13, wherein the processor is further configured to:
obtain the inclusive multicast routing table, wherein the inclusive multicast routing table comprises the inclusive multicast route of the second network device.

### Claim 16 (depends on 13)

The first network device according to claim 13, wherein the connectivity detection session comprises a connectivity fault management (CFM) session.

### Claim 17 (depends on 13)

The first network device according to claim 13, wherein a type-length-value (TLV) field in the creation message of the connectivity detection session comprises the inclusive multicast route of the second network device, the TLV field comprises a type, a length, and a value, the type is used to indicate that a type of the TLV field is the inclusive multicast route, the length is used to indicate a length of the TLV field, and the value is the inclusive multicast route of the second network device.

### Claim 18 (depends on 13)

The first network device according to claim 13, wherein the session information of the second network device comprises a MEP ID or a session ID of the second network device.

### Claim 19 (depends on 13)

The first network device according to claim 13, wherein the processor is further configured to:
obtain a maintenance association end point identifier (MEP ID) range or a session identifier (session ID) range, wherein the MEP ID range comprises the MEP ID of the second network device, or the session ID range comprises the session ID of the second network device; and
the processor is further configured to:
determine that the MEP ID of the second network device is within the MEP ID range before the first network device receives the creation message of the connectivity detection session from the second network device; or
determine that the session ID of the second network device is within the session ID range before the first network device receives the creation message of the connectivity detection session from the second network device.
