WO2025185376A1 - Communication method, apparatus and system - Google Patents

Abstract

The present application relates to the field of communication, and provides a communication method, apparatus and system. The method comprises: an NERG sending a prefix synchronization message to a first ONT, so as to instruct the first ONT to send an IPv6 address prefix of the NERG to a first terminal device, such that the first terminal device acquires a first GUA on the basis of the IPv6 address prefix of the NERG, wherein an IPv6 address prefix of the first GUA is the same as an IPv6 address prefix of a second GUA, and the second GUA is acquired by a second terminal device on the basis of the IPv6 address prefix of the NERG; and the first ONT generating a first network segment route entry, wherein a destination IP address of the first network segment route entry is a network bridge interface address of the NERG. Thus, an NERG is used as an IPv6 network control point, such that an ONT and a terminal device under the NERG have the same prefix, and can directly learn each other's neighbor tables, thereby realizing layer 2 intercommunication, and reducing the complexity of layer 2 network intercommunication.

Description

Communication method, device and system

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on March 8, 2024, with application number 202410269946.1 and application name “Communication Methods, Devices and Systems”, the entire contents of which are incorporated by reference into this application.

Technical Field

The present application relates to the field of communications, and in particular to a communication method, device, and system.

Background Art

Based on the differences in logical topology, network structures are divided into Layer 2 and Layer 3 networks. A Layer 2 network consists of a core layer and an access layer. Its workflow can be summarized as switches forwarding packets based on the media access control (MAC) address table. A Layer 3 network differs from a Layer 2 network in the addition of a convergence layer, which acts as an intermediary between the access layer and the core layer. While Layer 2 networks rely solely on MAC addressing for communication, Layer 3 networks require Internet Protocol (IP) routing for cross-segment communication, including across multiple collision domains.

Because the architecture of the Layer 2 network is simpler and technologies such as Dynamic Host Configuration Protocol (DHCP) are often used in Layer 2 networks, users can interconnect based on the Layer 2 network, for example, multiple families can be networked based on the Layer 2 network.

In Internet Protocol version 6 (IPv6) networks, multi-home IPv6 Layer 2 networking typically uses Layer 2 tunneling technologies, such as virtual extensible local area network (VxLAN), to achieve interoperability. However, Layer 2 tunneling technology is complex and requires operators to deploy and configure special resources in the upper layer network.

Summary of the Invention

The present application provides a communication method, device and system, thereby reducing the complexity of users' Layer 2 network intercommunication.

In a first aspect, the present application provides a communication method, which is applied to a first optical network terminal (ONT), wherein the first ONT is connected to a network enhanced residential gateway (NERG), the first ONT is connected to a first terminal device, and the NERG is connected to a second terminal device. In the process of the communication method, when the first ONT receives a prefix synchronization message sent by the NERG, it sends the IPv6 address prefix of the NERG contained in the prefix synchronization message to the first terminal device, so that the first terminal device obtains a first global unicast address (GUA) based on the IPv6 address prefix of the NERG. The IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of the second GUA, and the second GUA is obtained by the second terminal device based on the IPv6 address prefix of the NERG. Then, the first ONT generates a first network segment routing item, and the destination IP address of the first network segment routing item is the bridge interface address of the NERG.

The first GUA and the second GUA may also be referred to as IPv6 public network addresses.

Based on the above communication method, using NERG as the IPv6 network control point, the first terminal device connected to the first ONT and the second terminal device connected to the NERG uniformly use the NERG's IPv6 address prefix to obtain the GUA. This ensures that the GUAs of the terminal device connected to the first ONT and the terminal device connected to the NERG have the same IPv6 address prefix and belong to the same network segment. Therefore, the terminal device connected to the first ONT and the terminal device connected to the NERG can directly learn each other's neighbor table, achieving Layer 2 network interoperability. This reduces the complexity of Layer 2 network interoperability compared to traditional Layer 2 network solutions that require operators to deploy and configure special resources in the upper layer network.

As one possible implementation, the NERG's IPv6 address prefix is the IPv6 address prefix of the NERG's Point-to-Point Protocol over Ethernet (PPPoE) wide area network (WAN) interface. This allows the first and second terminal devices to synchronize their IPv6 address prefixes with the IPv6 address prefix of the NERG's default Internet interface, the PPPoE WAN interface, facilitating Internet access for the first and second terminal devices.

As a possible implementation manner, when forwarding the first Internet uplink message through its own PPPoE WAN interface, the first ONT performs IPv6-to-IPv6 network prefix translation (NPTv6) or IPv6-to-IPv6 network address translation (NAT66) on the first Internet uplink message.

Optionally, the first ONT enables an NPTv6 function or a NAT66 function on a PPPoE WAN interface connected to the Internet. When the first Internet uplink packet is forwarded through the PPPoE WAN interface of the first ONT, an NPTv6 conversion or a NAT66 conversion is required. Otherwise, the first Internet downlink packet corresponding to the first Internet uplink packet cannot reach the first ONT because there is no routing entry corresponding to the IPv6 address prefix to the first ONT.

Optionally, the Internet uplink message of the second terminal device connected to the NERG is forwarded by the PPPoE WAN interface of the NERG connected to the Internet, and the Internet can be accessed normally without special processing.

Based on the above implementation, while the terminal device connected to the first ONT and the terminal device connected to the NERG can achieve Layer 2 network intercommunication, the NPTv6 function or NAT66 function is enabled on the PPPoE WAN interface of the first ONT connected to the Internet, allowing the terminal device to access the Internet through a normal channel.

As one possible implementation, the first ONT forwards the first application access uplink message to the NERG based on the first static route. The NERG performs NPTv6 or NAT66 on the first application access uplink message and then sends it to the application. The outbound port of the first static route is the bridge interface of the first ONT, and the next hop address is the bridge interface address of the NERG. In this way, the first application access uplink message from the first terminal device can reach the designated application based on the static route configuration, enabling user access to the application on the first ONT.

Optionally, the first ONT updates the MAC address of the first application's uplink access message to the MAC address of the ERG's bridge interface. This allows the first application's uplink access message to be forwarded on the first ONT over the Layer 2 network. This resolves the issue of communication interruption caused by issues with the Transmission Control Protocol (TCP) state and MAC learning entries when the first application's uplink access message from the first ONT to the application is forwarded over the Layer 3 network and the corresponding downlink message is forwarded over the Layer 2 network.

As one possible implementation, when the first ONT's PPPoE WAN interface fails, it sends a first failure state synchronization message to the NERG, instructing the NERG to send a first route advertisement message to the first terminal device. The first route advertisement message instructs the first terminal device to update its gateway to the gateway of the second terminal device. The first ONT then forwards the first terminal device's second Internet uplink message to the NERG, which then forwards the second Internet uplink message via the PPPoE WAN interface. This allows the first terminal device connected to the first ONT to use the NERG's Internet link as a backup link when the first ONT loses Internet access, ensuring network stability.

Optionally, the domain name system server of the first terminal device is proxied by the domain name system server of the second terminal device.

As one possible implementation, the first ONT receives a second fault state synchronization message sent by the NERG and, in response to the second fault state synchronization message, sends a second route advertisement message to the second terminal device. The second route advertisement message instructs the second terminal device to update its gateway to the gateway of the first terminal device. In this way, if the NERG loses internet access, the second terminal device connected to the NERG can use the first ONT's internet link as a backup link and access the internet through the first ONT, thereby ensuring network stability.

Optionally, the second route advertisement message includes a second route deletion advertisement message and a second route creation advertisement message. The source IP address of the second route deletion advertisement message is the bridge interface address of the first NERG. The source IP address of the second route creation advertisement message is the bridge interface address of the ONT.

In a second aspect, the present application provides a communication method, applied to a NERG, wherein the NERG is connected to a first ONT, the first ONT is connected to a first terminal device, and the NERG is connected to a second terminal device. In the process of the communication method, the NERG sends a prefix synchronization message to the first ONT. In response to the prefix synchronization message, the first ONT sends the NERG's IPv6 address prefix to the first terminal device and generates a first network segment routing entry. The first terminal device obtains a first GUA based on the NERG's IPv6 address prefix. The IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of the second GUA. The second GUA is obtained by the second terminal device based on the NERG's IPv6 address prefix. The destination address of the first network segment routing entry is the bridge interface address of the NERG.

As a possible implementation, the NERG is also connected to a second ONT, and the second ONT is connected to a third terminal device. In this communication method, the NERG sends a prefix synchronization message to the second ONT. The second ONT responds to the prefix synchronization message by sending the NERG's IPv6 address prefix to the third terminal device. The third terminal device obtains a third GUA based on the NERG's IPv6 address prefix and generates a second network segment routing entry. The IPv6 address prefix of the third GUA is the same as the IPv6 address prefix of the second GUA. The second GUA is obtained by the second terminal device based on the NERG's IPv6 address prefix. The destination address of the second network segment routing entry is the bridge interface address of the NERG. In this way, terminal devices under multiple ONTs connected to the NERG can uniformly use the NERG's IPv6 address prefix to obtain the GUA. This ensures that the GUAs of terminal devices connected to the first ONT, the second ONT, and the NERG have the same IPv6 address prefix and belong to the same network segment. They can directly learn each other's neighbor tables, thus achieving large-scale Layer 2 network interoperability among multiple home terminal devices.

As a possible implementation, the IPv6 address prefix of NERG is the IPv6 address prefix of NERG's PPPoE WAN interface.

As a possible implementation, the NERG receives a first application access uplink message sent by the first ONT based on the first static route, performs NPTv6 or NAT66 on the first application access uplink message, and then sends it to the application. The outbound port of the first static route is the bridge interface of the first ONT, and the next hop address is the bridge interface address of the NERG.

As one possible implementation, upon receiving a first application access uplink message from the first ONT, the NERG adds a tag to the first application access uplink message. Upon receiving a first application access downlink message returned by the application containing the tag, the NERG sets the outbound port of the first application access downlink message to the NERG's bridge interface and the next hop address to the address of the first ONT's bridge interface. This allows the first application access uplink message from the first terminal device to reach the designated application based on the static routing configuration, and the first application access downlink message returned by the application can also be sent to the first ONT, enabling users on the first ONT to access the application.

As one possible implementation, the NERG receives a first fault status synchronization message from the first ONT and, in response to the first fault status synchronization message, sends a first route advertisement message to the first terminal device. The first route advertisement message is used to instruct the first terminal device to update its gateway to the gateway of the second terminal device. The NERG then receives a second Internet uplink message from the first ONT for the first terminal device and forwards the second Internet uplink message via the PPPoE WAN interface.

Optionally, the first route advertisement message includes a first route deletion advertisement message and a first route creation advertisement message. The source IP address of the first route deletion advertisement message is the bridge interface address of the first ONT. The source IP address of the second route creation advertisement message is the bridge interface address of the NERG.

As one possible implementation, when the NERG's PPPoE WAN interface is in a faulty state, the NERG sends a second fault state synchronization message to the first ONT, causing the first ONT to send a second route advertisement message to the second terminal device. The second route advertisement message instructs the second terminal device to update its gateway to the gateway of the first terminal device. The NERG then forwards a third Internet uplink message from the second terminal device to the first ONT, causing the first ONT to forward the third Internet uplink message via the PPPoE WAN interface.

Optionally, the NERG sends the second application access uplink message based on a second static route. The outbound port of the second static route is the NERG's PPPoE WAN interface, and the next hop address is the application address.

Optionally, when NERG sends the second application access uplink message through the PPPoE WAN interface of NERG, NERG performs NPTv6 or NAT66 on the second application access uplink message.

The second aspect differs from the first aspect in that the execution entity is different. The second aspect can be combined with any possible implementation method described in the first aspect, which will not be repeated here.

In a third aspect, the present application provides a communication device, comprising a receiving module, a sending module, and a processing module. The receiving module is used to receive a prefix synchronization message sent by NERG; the prefix synchronization message includes the IPv6 address prefix of NERG. The sending module is used to send the IPv6 address prefix of NERG to a first terminal device, so that the first terminal device obtains a first global unicast address GUA based on the IPv6 address prefix of NERG; the IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of the second GUA, and the second GUA is obtained by the second terminal device based on the IPv6 address prefix of NERG. The processing module is used to generate a first network segment routing item; the destination IP address of the first network segment routing item is the bridge interface address of NERG.

As a possible implementation manner, the communication device may further include other modules that execute the operation steps of the communication method of the first aspect.

In a fourth aspect, the present application provides a communication device, comprising a sending module. The sending module is configured to send a prefix synchronization message to a first ONT and generate a first network segment routing entry; the prefix synchronization message includes the IPv6 address prefix of the NERG, causing the first ONT to send the IPv6 address prefix of the NERG to a first terminal device; the first terminal device obtains a first GUA based on the IPv6 address prefix of the NERG, the IPv6 address prefix of the first GUA being the same as the IPv6 address prefix of a second GUA, the second GUA being obtained by the second terminal device based on the IPv6 address prefix of the NERG; and the destination address of the first network segment routing entry being the bridge interface address of the NERG.

As a possible implementation manner, the communication device may further include other modules for executing the operation steps of the communication method described in the second aspect.

In a fifth aspect, the present application provides a communication system, comprising a first ONT and a NERG, wherein the first ONT is connected to the NERG, the first ONT is connected to a first terminal device, and the NERG is connected to a second terminal device. The NERG is used to send a prefix synchronization message to the first ONT, wherein the prefix synchronization message includes the IPv6 address prefix of the NERG. The first ONT is used to receive the prefix synchronization message sent by the NERG. The first ONT is also used to send the IPv6 address prefix of the NERG to the first terminal device, so that the first terminal device obtains a first global unicast address GUA based on the IPv6 address prefix of the NERG, wherein the IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of the second GUA, and the second GUA is obtained by the second terminal device based on the IPv6 address prefix of the NERG. The first ONT is also used to generate a first network segment routing item, wherein the destination IP address of the first network segment routing item is the bridge interface address of the NERG.

Regarding the technical principles and beneficial effects of the second, third, fourth and fifth aspects, please refer to the relevant description of the first aspect mentioned above and will not be repeated here.

In a sixth aspect, a computing device is provided, comprising a processor and a memory. The processor is configured to execute instructions stored in the memory of the computing device, so that the computing device executes the communication method described in any possible implementation of the first aspect.

In a seventh aspect, a computing device cluster is provided, comprising at least one computing device, each computing device including a processor and a memory. The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster performs the communication method described in any possible implementation of the second aspect.

In an eighth aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are executed on a computing device, causes the computing device to execute the communication method described in any possible implementation of the first aspect.

In a ninth aspect, a computer program product is provided, comprising a computer program or instructions, which, when executed on a computing device cluster, causes the computing device cluster to execute the communication method described in any possible implementation of the second aspect.

In a tenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes a computer program or instructions that, when executed on a computing device, causes the computing device to execute the communication method described in any possible implementation of the first aspect.

In an eleventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes a computer program or instructions that, when executed on a computing device cluster, causes the computing device cluster to execute the communication method described in any possible implementation of the second aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the architecture of a communication system provided by the present application;

FIG2 is a flow chart of a communication method provided by the present application;

FIG3 is a second flow chart of a communication method provided by the present application;

FIG4 is a third flow chart of a communication method provided by the present application;

FIG5 is a fourth flow chart of a communication method provided by the present application;

FIG6 is a flow chart of a communication method provided by the present application;

FIG7 is a sixth flow chart of a communication method provided by the present application;

FIG8 is a flow chart of a communication method provided by the present application;

FIG9 is a schematic structural diagram of a communication device provided by the present application;

FIG10 is a schematic structural diagram of another communication device provided by the present application;

FIG11 is a schematic diagram of the structure of a computing device provided by the present application;

FIG12 is a schematic diagram of the structure of a computing device cluster provided by this application;

FIG13 is a schematic diagram of a structure of a network connection between computing devices provided by the present application.

DETAILED DESCRIPTION

The communication method provided in the embodiment of the present application can be applied to optical network terminal networking scenarios in the field of communications. The following is a brief introduction to the technologies that may be involved in this application.

(1) Internet Protocol Version 6

Internet Protocol version 6, abbreviated as IPv6, not only expands the address space but also offers additional features and improvements over Internet Protocol version 4 (IPv4). These include improved security, reliability, and longevity, simpler address allocation, faster routing, and better support for mobile devices. IPv6 also supports flow labels and quality of service, making network traffic management more flexible and efficient.

An IPv6 address is 128 bits long and consists of eight 16-bit fields, with adjacent fields separated by colons. Each field in an IPv6 address must contain a hexadecimal number. An IPv6 address consists of an IPv6 address prefix and an interface identifier. The IPv6 address prefix is the portion of the address with a fixed value or the portion of the address that identifies the network. The IPv6 notation for subnet identifiers, routers, and address range prefixes is the same as the Classless Inter-Domain Routing (CIDR) notation used by IPv4. The prefix can be written as: address/prefix length. For example, 21DA:D3::/48 is a router prefix, while 21DA:D3:0:2F3B::/64 is a subnet prefix. If multiple devices have the same IPv6 address prefix, they can directly learn each other's neighbor tables, enabling Layer 2 network interoperability.

An IPv6 address is an identifier for a single interface. All IPv6 addresses are assigned to interfaces, not nodes. Since each interface belongs to a specific node, any interface address of a node can be used to identify a node. IPv6 has three types of addresses: unicast, anycast, and multicast. Unicast is used to identify an address on a single interface. Packets sent to a unicast address are sent to the interface identified by that address. Based on packet reachability, unicast supports global unicast addresses, site-local unicast addresses, and link-local unicast addresses. A GUA is an address that can be reached and identified globally. Its IPv6 address prefix consists of a global routing prefix and a subnet ID, and the interface identifier is an interface ID (identify). The other unicast addresses mentioned above, as well as the specific address types of anycast and multicast, are not discussed here.

(2) Optical Network Terminal

An optical network terminal, also known as an ONT or optical modem, is a device that provides access to the internet for home users, offering services such as high-speed internet access, IPTV, voice, and Wi-Fi. An ONT can be understood as an optical network unit (ONU), and can be considered a part of the ONU.

The difference between ONT and ONU is that ONT is an optical network terminal, which is directly located at the user end; ONU is an optical network unit, which may have other networks between it and the user. For example, the ONU can be connected to an x digital subscriber line (xDSL) or Ethernet access point gateway device, which can then be connected to the ONU.

An ONU is a user-side device in a passive optical network (PON), typically located at the user's end. The ONU converts received optical signals into electrical signals and transmits them to user devices such as computers, televisions, or phones.

The ONT is a component of the ONU, providing additional functionality such as voice, data, or video services. The ONT can connect directly to user terminals to provide network services or function as a home gateway.

(3) Edge Cloud

Edge cloud is a small-scale cloud data center distributed at the edge of the network that provides real-time data processing, analysis and decision-making. Both private cloud and public cloud rely on a large-scale cloud server to operate.

The core of the edge cloud is cloud computing, primarily relying on edge computing capabilities. It's a platform built on edge infrastructure. Forming a triangular architecture with the central cloud and IoT terminals, it offloads network dispatch, storage, computing, and intelligent data analysis tasks to edge cloud processors, reducing response latency, alleviating overall cloud pressure, and lowering network costs. It also provides cloud services such as computer resource distribution and scheduling.

(4) Spine-Leaf

With the widespread adoption of cloud computing technology in data centers, the traditional three-tier data center network architecture is no longer able to meet the network carrying requirements of new services. The physical network architecture of cloud data centers needs to evolve from the traditional three-tier architecture to a two-tier spine-leaf network based on a non-blocking multi-stage switching network. This architecture, routing organization, and automated management and control must meet the requirements of elastic scalability, efficient forwarding, and high reliability for large-scale networking.

In the Spine-Leaf architecture, the Spine is the core network node, providing high-speed IP forwarding capabilities and connecting to various functional Leaf nodes via high-speed interfaces. Leaf nodes are network function access nodes, providing access to various network devices. Spine and Leaf switches are interconnected using Layer 3 routing interfaces, with the choice of Open Shortest Path First (OSPF) or External Border Gateway Protocol (EBGP) for Layer 3 underlay network interconnection. Cross-device link aggregation technology and equal-cost multipath routing (ECMP) enable multipath forwarding and fast link switching, supporting non-blocking forwarding, horizontal elastic expansion, and network reliability.

The present application provides a communication method, in particular, a "communication method for synchronizing IPv6 address prefixes using NERG as a control center." First, NERG sends a prefix synchronization message containing NERG's IPv6 address prefix to the first ONT to instruct the first ONT to send NERG's IPv6 address prefix to the first terminal device connected to itself, so that the first terminal device obtains a first GUA based on NERG's IPv6 address prefix. The IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of the second GUA, and the second GUA is obtained by the second terminal device connected to NERG based on NERG's IPv6 address prefix. Then, the first ONT generates a first network segment routing item, and the destination IP address of the first network segment routing item is the bridge interface address of NERG.

In this way, using NERG as the IPv6 network control point, the first terminal device connected to the first ONT and the second terminal device connected to the NERG uniformly use the NERG's IPv6 address prefix to obtain the GUA. This ensures that the GUAs of the terminal device connected to the first ONT and the terminal device connected to the NERG have the same IPv6 address prefix and belong to the same network segment. Therefore, the terminal device connected to the first ONT and the terminal device connected to the NERG can directly learn each other's neighbor table, achieving Layer 2 network interoperability. This reduces the complexity of Layer 2 network interoperability compared to traditional Layer 2 network solutions that require operators to deploy and configure special resources in the upper layer network.

The implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Figure 1 is a schematic diagram of the architecture of a communication system provided by this application. As shown in Figure 1, communication system 100 includes a first ONT 101, a second ONT 102, a switch 103, a NERG 104, a switch 110, a switch 105, and an edge cloud 106. The first ONT 101 and the second ONT 102 are connected to the NERG 104 via the switch 103. The first ONT 101 and the second ONT 102 are also connected to the Internet via the switch 110. The NERG 104 is connected to the edge cloud 106 via the switch 105.

First, the structure of NERG 104 and how NERG 104 connects to the first ONT 101 , the second ONT 102 , and the edge cloud 106 are described.

NERG 104 can be a virtual gateway on an edge cloud gateway (ECGW). NERG 104 can have DHCP server functions, domain name system (DNS) proxy functions, and PPPoE client functions.

As a possible implementation method, ECGW is virtualized into the U-plane and the C-plane. The C-plane is responsible for establishing and managing channels for forwarding service data, and the U-plane is responsible for forwarding user service data.

The C-plane of the ECGW includes NERG 104, which includes an L2 control plane and an L3 control plane. The L2 control plane includes a first local area network interface (LAN1) and a second local area network interface (LAN2). The L3 control plane includes a second wide area network interface (WAN2) and a third wide area network interface (WAN3). NERG 104 may also include a first wide area network interface (WAN1).

Optionally, the NERG 104 may be a virtual device implemented based on Kubernetes (k8s) containerization and may be managed by a Kubernetes client.

The LAN 1 of the NERG 104 is connected to the switch 103 via a U-plane, thereby being bridged to the first ONT 101 .

For example, LAN 1 of NERG 104 is connected to switch 103 via Ethernet virtual private network (EVPN) SRv6 (segment routing IPv6), thereby connecting to the bridge interface of first ONT 101. LAN 1 may utilize QinQ (802.1Q-in-802.1Q) technology based on a virtual local area network (VLAN).

The LAN 2 of the NERG 104 is connected to the switch 103 via the U-plane, thereby being bridged to the second ONT 102 .

For example, LAN2 of NERG 104 is connected to switch 103 via EVPN SRv6, and is thus connected to the bridge interface of the second ONT 102. LAN2 can use QinQ VLAN technology.

In the preceding scenario, switch 103 can be considered an A-Leaf node in the spine-leaf architecture. Switch 103 connects to LAN 1 using EVPN SRv6 in TAG mode, and connects to LAN 2 using EVPN SRv6 in RAW mode.

WAN1 of NERG 104 is connected to switch 110 via the U interface, thereby connecting to the Internet.

For example, WAN1 of NERG104 is connected to switch 110 through EVPN SRv6, thereby accessing the Internet through switch 110. WAN1 can use QinQ VLAN technology.

In the preceding scenario, switch 110 can be considered an S-Leaf in the Spine-Leaf architecture. Switch 110 connects to WAN1 using EVPN SRv6 in TAG mode.

NERG 104 is connected to the switch 105 via the U-plane, and thus connected to the edge cloud 106 .

For example, WAN2 of NERG 104 is connected to switch 105 through virtual routing and forwarding (VRF), thereby connecting to edge cloud 106. WAN2 can use Smart VLAN technology.

For example, WAN3 of NERG 104 is connected to switch 105 through EVPN VxLAN, thereby connecting to edge cloud 106. WAN3 can use QinQ VLAN technology.

In the above scenario, switch 105 can be a TOR (top of rack) switch. Switch 105 is connected to WAN2 through EVPN VxLAN RAW mode.

In a possible embodiment of the present application, the NERG 104 may isolate the first ONT 101 and the second ONT 102 according to users, or the ECGW may virtualize a NERG for each user.

Next, a specific connection method of the first ONT 101 and the second ONT 102 is described.

The first ONT 101 is connected to the switch 103 via a bridge interface, thereby being bridged to the NERG 104 .

For example, the first ONT 101 is connected to the switch 103 via the bridge interface BR0 , and is thus connected to the LAN 1 of the NERG 104 via the switch 103 .

The first ONT 101 is connected to the switch 103 through the PPPoE interface, and is then connected to the switch 110 through the switch 103 , and accesses the Internet through the switch 110 .

For example, the first ONT 101 is connected to the switch 103 through the PPPoE interface, and is thereby connected to the switch 110 in the TAG mode of EVPN SRv6, and the switch 110 is connected to the Internet.

The second ONT 102 is connected to the switch 103 via a bridge interface, thereby being bridged to the NERG 104 .

For example, the second ONT 102 is connected to the switch 103 via the bridge interface BR0 , and is thus connected to the LAN 2 of the NERG 104 via the switch 103 .

The second ONT 102 is connected to the switch 103 through the PPPoE interface, and is thereby connected to the switch 110 through the switch 103 , and is accessed to the Internet through the switch 110 .

For example, the second ONT 102 is connected to the switch 103 through the PPPoE interface, and is thereby connected to the switch 110 in the TAG mode of EVPN SRv6, and the switch 110 is connected to the Internet.

In the above scenario, first ONT 101 and second ONT 102 can provide access functions for two households respectively. Devices connected to first ONT 101 include first terminal device 107, such as a TV with an address of 192.168.16.3 and a computer with an address of 192.168.16.2. Devices connected to second ONT 102 include third terminal device 108, such as a TV with an address of 192.168.17.2 and a computer with an address of 192.168.17.5.

Next, the edge cloud 106 will be described.

The edge cloud 106 may include one or more edge cloud services. The edge cloud services may be virtualized from the host machine, and the edge cloud services may be considered as the second terminal device 109 connected to the NERG 104 .

The edge cloud 106 may include edge cloud-specific services, such as an edge cloud business instance (network attached storage (NAS) with an address of 192.168.31.8). The edge cloud-specific services are connected to WAN2 of NERG104 through the switch 105, thereby forming a large Layer 2 network with the home.

The edge cloud 106 may include edge cloud shared services, such as intelligent computing with an address of 29.18.7.8. The edge cloud proprietary services are connected to WAN3 of NERG104 through the switch 105. The WAN3 address is 29.18.7.7, thereby supporting three-layer network access.

It should be noted that FIG1 is merely a schematic diagram and should not be construed as limiting the present application. The communication system 100 may also include other modules not shown in FIG1. For example, the switch 103 (or switch 110, or switch 105) is a network device, or may be formed by connecting one or more network devices (switches, routers, gateways, etc.).

The communication method provided by this embodiment will be described in detail below with reference to the accompanying drawings.

The steps of the communication method provided in the present application are executed by multiple devices in the communication system 100, such as the first ONT 101, the second ONT 102, the NERG 104 and the edge cloud 106. Next, the communication method provided in the embodiment of the present application is described with reference to FIG2.

Please refer to Figure 2, which is a flow chart of a communication method provided by this application. The communication method may include the following steps 201 to 205. In Figure 2 above and in the subsequent embodiments of this application, dotted lines are used to indicate communication paths.

Step 201 : NERG 104 sends prefix synchronization information to the first ONT 101 .

NERG 104, as the control point, sends prefix synchronization information to first ONT 101, synchronizing NERG 104's IPv6 address prefix to first ONT 101 through the prefix synchronization information. The prefix synchronization information includes NERG 104's IPv6 address prefix, i.e., the IPv6 address prefix of the PPPoE WAN.

For example, the IPv6 address prefix of NERG104's PPPoE WAN is 2005::/56, and the interface identifier is 2004::1. The IPv6 address prefix of the above NERG104 is 2005::/56.

As a possible implementation, NERG 104 is connected to the new city network (such as switch 103) through bridge interface BR0, and thus connected to bridge interface BR0 of the first ONT 101 through the cloud LAN interface (CloudLAN). The local link address of bridge interface BR0 of NERG 104 can be fe80::101, and the local link address of bridge interface bro of the first ONT 101 can be fe80::1.

Step 202: The first ONT 101 receives prefix synchronization information.

Step 203 : The first ONT 101 sends the IPv6 address prefix of the NERG 104 to the first terminal device 107 .

After receiving the prefix synchronization information, the first ONT 101 sends the IPv6 address prefix synchronized by the NERG 104 to the first terminal device 107 .

Step 204: The first terminal device 107 obtains a first GUA based on the IPv6 address prefix of the NERG.

The IPv6 address prefix of the first GPU is the same as the IPv6 address prefix of the second GUA. The second GUA is acquired by the second terminal device 109 based on the IPv6 address prefix of the NERG.

As a possible implementation manner, GUA may also be referred to as an IPv6 public network address in the embodiments of this application.

For example, the first GUA is 2005::111, that is, the IPv6 public network address of the first terminal device 107 is 2005::111.

Step 205: The first ONT 101 generates a first network segment routing entry.

The first network segment routing entry is used to implement routing between the first ONT 101 and the NERG 104. The destination IP address of the first network segment routing entry is the bridge interface address of the NERG 104. For example, the first network segment routing entry is 2005::/56dev BR0.

In a possible embodiment of the present application, the above-mentioned other interface configurations and connection modes of the first ONT 101, NERG 104 and terminal devices do not affect the Layer 2 intercommunication between the terminal device connected to the first ONT 101 and the terminal device connected to the NERG 104, and are therefore only illustrative.

The IPv6 address prefix of the PPPoE WAN interface of the first ONT 101 is 2003::/56, and the interface identifier is 2002::1.

The DNS server address of the first terminal device 107 is fe80::1, and the gateway address is fe80::1.

The IPv6 address prefix of NERG104's IPoE WAN interface is 2007::/56, and the interface identifier is 2006::1.

The bridge interface BR0 of NERG104 is connected to the second terminal device 109 through a data center gateway (DC-GW).

The IPv6 address of the second terminal device 109 is 2005::/101, the DNS server address is fe80::1, and the gateway address is fe80::1.

NERG104 is connected to the first ONT101 through Newtown Network's EVPN SRv6.

In this way, with NERG04 as the IPv6 network control point, first terminal device 107 connected to first ONT 101 and second terminal device 109 connected to NERG 104 uniformly use NERG 104's IPv6 address prefix to obtain the GUA. This ensures that the GUAs of terminal devices connected to first ONT 101 and NERG 104 have the same IPv6 address prefix and belong to the same network segment. Therefore, terminal devices connected to first ONT 101 and NERG 104 can directly learn each other's neighbor tables, achieving Layer 2 network interoperability. This reduces the complexity of Layer 2 network interoperability compared to traditional Layer 2 network solutions that require operators to deploy and configure special resources in the upper layer network.

Based on the communication method shown in FIG. 2 provided in the embodiment of the present application, NERG04 may also be connected to the second ONT 102 to implement Layer 2 intercommunication among multiple households.

Please refer to Figure 3, which is a second flow chart of a communication method provided by the present application. The communication method may include the following steps 301 to 310.

Step 301 : NERG 104 sends prefix synchronization information to the first ONT 101 .

Step 302: The first ONT 101 receives prefix synchronization information.

Step 303 : The first ONT 101 sends the IPv6 address prefix of the NERG 104 to the first terminal device 107 .

Step 304 : The first terminal device 107 obtains a first GUA based on the IPv6 address prefix of the NERG 104 .

Step 305: The first ONT 101 generates a first network segment routing entry.

Step 306 : NERG 104 sends prefix synchronization information to the second ONT 102 .

Step 307: The second ONT 102 receives prefix synchronization information.

Step 308 : The second ONT 102 sends the IPv6 address prefix of the NERG 104 to the third terminal device 108 .

Step 309: The third terminal device 108 obtains a third GUA based on the IPv6 address prefix of the NERG.

Step 310: The first ONT 101 generates a second network segment routing entry.

The second network segment routing entry is used to implement routing between the second ONT 102 and NERG 104. The destination IP address of the second network segment routing entry is the bridge interface address of NERG 104. For example, the second network segment routing entry is 2005::/56dev BR0.

The above steps 301 to 305 are the same as steps 201 to 205 shown in FIG. 2 . The above steps 306 to 310 differ from steps 201 to 205 shown in FIG. 2 in that the interaction objects are different, which will not be repeated here.

In a possible embodiment of the present application, the other interface configurations and connection modes of the second ONT 102 and the terminal device do not affect the Layer 2 intercommunication between the terminal device connected to the second ONT 102, the terminal device connected to the first ONT 101, and the terminal device connected to the NERG 104, and are therefore only illustrative.

The IPv6 address prefix of the PPPoE WAN interface of the second ONT 102 is 2013::/56, the interface identifier is 2012::1, and the link-local address of the bridge interface BR0 is fe80::111.

The IPv6 address of the third terminal device 108 is 2005::222, the DNS server address is fe80::101, and the gateway address is fe80::101.

NERG104 is connected to the second ONT102 via EVPN SRv6 of New Town Networks.

In this way, NERG 104, as a control point, synchronizes the IPv6 address prefix of NERG 104 to the first ONT 101 and the second ONT 102, so that the terminal devices connected to the first ONT 101 and the second ONT 102 use the same IPv6 address prefix to obtain the GUA. That is, the terminal devices connected to the first ONT 101 and the second ONT 102 obtain the GUA of 2005::X, so that the terminal devices connected to the first ONT 101 and the second ONT 102 can achieve Layer 2 intercommunication at the GUA level.

Based on the communication method shown in FIG. 2 provided in the embodiment of the present application, the first ONT 101 and the first terminal device 107 and the second terminal device 109 under the NERG 104 can access the Internet normally.

Please refer to Figure 4, which is a flow chart of a communication method provided by the present application. The communication method may include the following steps 401 to 406.

Step 401 : NERG 104 sends prefix synchronization information to the first ONT 101 .

Step 402: The first ONT 101 receives prefix synchronization information.

Step 403 : The first ONT 101 sends the IPv6 address prefix of the NERG 104 to the first terminal device 107 .

Step 404 : The first terminal device 107 obtains a first GUA based on the IPv6 address prefix of the NERG 104 .

Step 405: The first ONT 101 generates a first network segment routing entry.

The above steps 401 to 405 are the same as steps 201 to 205 shown in FIG. 2 , and are not described in detail here.

Step 406: When forwarding the first Internet uplink message through the PPPoE WAN interface, the first ONT 101 performs NPTv6 or NAT66 on the first Internet uplink message.

The first ONT 101 receives the first Internet uplink message sent by the first terminal device 107, and performs NPTv6 or NAT66 on the first Internet uplink message.

For example, the first ONT 101 performs NPTv6 on the first Internet uplink message, and transforms the source IP address of the first Internet uplink message into the IPv6 address prefix of the first ONT 101, such as 2003::X.

For another example, the first ONT 101 performs NAT66 on the first Internet uplink message, and transforms the source IP address of the first Internet uplink message into the interface identifier of the first ONT 101, such as 2002::1.

In a possible embodiment of the present application, the Internet uplink message of the second terminal device 109 under NERG104 is directly forwarded by the PPPoE WAN interface of NERG104 without the need for special processing.

NAT66 is an address translation technology based on IPv6 networks, used to translate the IPv6 address prefix in IPv6 packets into another IPv6 address prefix. NAT66 includes two address translation methods: NPTv6 and static NAT66. NPTv6 is one of the NAT66 address translation methods. After the source IPv6 address is translated through NPTv6, the IPv6 network prefix is replaced with the new network prefix. Based on the change in prefix before and after translation, a compensation value is added to the interface ID. This technology is generally applicable in scenarios with a high volume of IPv6 traffic and low sensitivity to the translated IP address.

This solves the problem that the downlink message corresponding to the Internet uplink message of the terminal device connected to the ONT cannot reach the ONT because there is no routing entry corresponding to the IPv6 address prefix to the ONT, allowing the terminal device connected to the ONT to access the Internet normally.

Based on the communication method shown in FIG2 provided in the embodiment of the present application, the second terminal device 109 under the NERG 104 can access applications, wherein the applications may be specific applications such as paid videos and network cloud disks.

Please refer to Figure 5, which is a fourth flow chart of a communication method provided by the present application. The communication method may include the following steps 501 to 505.

Step 501: NERG 104 configures a second static route.

When accessing an application based on IP, configure a second static route. The second static route is used to indicate the forwarding path for uplink packets from the second application accessing the application. For example, the second static route is 3003::/64dev WAN2.

When accessing applications based on domain names, configure the DNS resolution path for the specific domain name corresponding to IPoE WAN2. After resolving the IP address, configure the second static route.

Step 502 : NERG 104 sends the IPv6 address prefix of NERG 104 to the second terminal device 109 .

Step 503: The second terminal device 109 obtains a second GUA based on the IPv6 address prefix of the NERG.

For the above steps 502 and 503 , please refer to steps 203 and 204 shown in FIG. 2 , which will not be described in detail here.

Step 504 : The second terminal device 109 sends a second application access uplink message to the NERG 104 .

Step 505 : NERG 104 sends the second application access uplink message based on the second static route, and performs NPTv6 or NAT66 on the second application access uplink message.

For example, after the second application performs NPTv6 on the uplink packet, the source IP address when it leaves the IPoE WAN2 interface is changed to 2007::X. For another example, after the second application performs NAT66 on the uplink packet, the source IP address when it leaves the IPoE WAN2 interface is changed to 2006::1.

In this way, the problem that the downlink message corresponding to the uplink message of the application of the terminal device under NERG104 cannot be transmitted due to the inability to query the routing entry 2007::/56 is solved, and the terminal device under NERG104 can access the specific application.

Based on the communication method shown in FIG. 2 provided in the embodiment of the present application, if the IPv6 network of the first ONT 101 fails, the terminal device under the first ONT 101 can achieve backup Internet access through the network of NERG 104, thereby ensuring the stability of the terminal device's access to the Internet.

Please refer to Figure 6, which is a flowchart diagram 5 of a communication method provided by this application. The communication method may include the following steps 601 to 610.

Step 601 : NERG 104 sends prefix synchronization information to the first ONT 101 .

Step 602: The first ONT 101 receives prefix synchronization information.

Step 603 : The first ONT 101 sends the IPv6 address prefix of the NERG 104 to the first terminal device 107 .

Step 604 : The first terminal device 107 obtains a first GUA based on the IPv6 address prefix of the NERG 104 .

Step 605: The first ONT 101 generates a first network segment routing entry.

The above steps 601 to 605 are the same as steps 201 to 205 shown in FIG. 2 , and are not described in detail here.

Step 606: When the PPPoE WAN interface is in a fault state, the first ONT 101 sends a first fault state synchronization message to NERG 104.

When the PPPoE WAN interface of the first ONT 101 is in the down state, it is determined that the PPPoE WAN interface is in a fault state.

Step 607 : NERG 104 sends a first routing advertisement message to the first terminal device 107 .

The first routing advertisement message is used to instruct the first terminal device 107 to update the gateway to the gateway of the second terminal device 109 .

As a possible implementation manner, the first route advertisement message includes a first route deletion advertisement message and a first route creation advertisement message.

Optionally, NERG 104 first sends a first route deletion notification message to first terminal device 107 to instruct first terminal device 107 to delete the expired routing table entry. For example, the lifetime of the first route deletion notification message is 0, and the source IP address is fe80::1. NERG 104 then sends a first route creation notification message to first terminal device 107 to instruct first terminal device 107 to create a new routing table entry. For example, the lifetime of the first route creation notification message is not 0, and the source IP address is fe80::101.

Step 608: The first terminal device 107 updates the gateway based on the first routing advertisement message.

For example, the first terminal device 107 updates the gateway to fe80::101 based on the first routing advertisement message.

Step 609 : The first terminal device 107 sends a second Internet uplink message to the NERG 104 .

Step 610, NERG104 forwards the second Internet uplink message through the PPPoE WAN interface.

In a possible embodiment of the present application, the DNS server of the first terminal device 107 is still fe80::1, and the initiated DNS resolution is sent to the next-level DNS server fe80::101 for resolution through the fe80::1 proxy.

In this way, when the first ONT 101 cannot connect to the Internet, the terminal device connected to the first ONT 101 can use the Internet link of NERG 104 as a backup link and access the Internet through NERG 104 to ensure network stability.

Based on the communication method shown in FIG2 provided in the embodiment of the present application, if the IPv6 network of NERG 104 fails, the terminal device under NERG 104 can achieve backup Internet access through the network of the first ONT 101, thereby ensuring the stability of the terminal device's access to the Internet.

Please refer to Figure 7, which is a sixth flow chart of a communication method provided by the present application. The communication method may include the following steps 701 to 710.

Step 701 : The first ONT 101 synchronizes the gateway to the NERG 104 .

For example, the first ONT 101 synchronizes the gateway fe80::1 to NERG 104 .

Step 702: The first ONT 101 generates a second network segment routing entry.

The second network segment routing entry is used to indicate the forwarding path from the first ONT 101 to the NERG 104. For example, the second network segment routing entry is 2005::/64dev BR0.

Step 703 : NERG 104 sends the IPv6 address prefix of NERG 104 to the second terminal device 109 .

Step 704 : The second terminal device 109 obtains a second GUA based on the IPv6 address prefix of the NERG 104 .

For the above steps 703 and 704, please refer to steps 203 and 204 shown in FIG. 2 , which will not be described in detail here.

Step 705: When the PPPoE WAN interface is in a fault state, NERG 104 sends a second fault state synchronization message to the first ONT 101.

NERG104 determines that the PPPoE WAN interface is in a faulty state when the PPPoE WAN interface is in the down state.

Step 706 : The first ONT 101 sends a second notification message to the second terminal device 109 .

The second routing advertisement message is used to instruct the second terminal device 109 to update the gateway to the gateway of the first terminal device 107 .

As a possible implementation manner, the second route advertisement message includes a second route deletion advertisement message and a second route creation advertisement message.

Optionally, first ONT 101 first sends a second route deletion notification message to second terminal device 109, instructing second terminal device 109 to delete the expired route table entry. For example, the lifetime of the second route deletion notification message is 0, and the source IP address is fe80::101. First ONT 101 then sends a second route creation notification message to second terminal device 109, instructing second terminal device 109 to create a new route table entry. For example, the lifetime of the second route creation notification message is not 0, and the source IP address is fe80::1.

Step 707: The second terminal device 109 updates the gateway based on the second routing advertisement message.

For example, the second terminal device 109 updates the gateway to fe80::1 based on the first routing advertisement message.

Step 708 : The second terminal device 109 sends a third Internet uplink message to the first ONT 101 .

Step 709: The first ONT 101 forwards the third Internet uplink message through the PPPoE WAN interface.

In a possible embodiment of the present application, the DNS server of the second terminal device 109 is still fe80::101, and the initiated DNS resolution is sent to the next-level DNS server fe80::1 for resolution through the fe80::101 proxy.

Step 710: The first ONT 101 performs NPTv6 or NAT66 on the third Internet uplink message.

For example, the first ONT 101 performs NPTv6 on the third Internet uplink message, and changes the source IP address of the third Internet uplink message to 2003::X.

For another example, the first ONT 101 performs NAT66 on the third Internet uplink message, and changes the source IP address of the third Internet uplink message to 2002::1.

In this way, when NERG 104 cannot connect to the Internet, the terminal device connected to NERG 104 via NAT66 can use the Internet link of the first ONT 101 as a backup link and access the Internet through the first ONT 101, thereby ensuring network stability.

Based on the communication method shown in FIG2 provided in the embodiment of the present application, if the IPv6 network of NERG 104 fails, the terminal device under NERG 104 can achieve backup Internet access through the network of the first ONT 101, thereby ensuring the stability of the terminal device's access to the Internet.

Based on the communication method shown in FIG2 provided in the embodiment of the present application, the first terminal device 107 under the first ONT 101 can access applications, which may be specific applications such as paid videos and network cloud disks.

Please refer to Figure 8, which is a flow chart of a communication method provided by the present application. The communication method may include the following steps 801 to 808.

Step 801: The first ONT 101 configures a first static route.

The outbound port of the first static route is the bridge interface of the first ONT 101 , and the next hop address is the bridge interface address of the NERG 104 .

Step 802 : The first ONT 101 receives a first application access uplink message from the first terminal device 107 .

Step 803: The first ONT 101 sends a first application access uplink message to the NERG 104 based on the second static route.

As a possible implementation, first ONT 101 performs special processing on uplink packets from the first application with a destination IP address of 3003::/64. The packet's destination MAC address is modified to the MAC address of bridge interface BR0 on NERG 104, so that the packet is forwarded at Layer 2 in first ONT 101. This prevents communication interruption caused by TCP status and MAC learning table errors due to uplink and downlink packets being forwarded at Layer 2 and 3003, respectively.

Step 804 : NERG 104 forwards the first application access uplink message to the application.

When NERG104 forwards the first application access uplink message through IPoE WAN2, it performs NPTv6 or NAT66 on the first application access uplink message.

Step 805: NERG 104 receives the first application access downlink message.

Step 806 : NERG 104 forwards the first application access downlink message to the first ONT 101 .

As a possible implementation, NERG 104 adds a tag to the first application's uplink access message. When receiving a first application's downlink access message sent by an application that includes the tag, NERG 104 sets the outbound port of the first application's downlink access message to the bridge interface of NERG 104 and the next hop address to the address of the bridge interface of first ONT 101. This prevents communication interruption caused by issues with TCP status and MAC learning entries due to uplink and downlink messages being forwarded at Layer 3 and Layer 2, respectively.

If the destination MAC address of the first application access uplink message has been modified in step 803, then in step 806, there is no need to perform special processing on the first application access downlink message according to the tag.

Step 807: The first ONT 101 receives the first application access downlink message.

Step 808 : The first ONT 101 forwards the first application access downlink message to the first terminal device 107 .

In this way, the problem that the downlink message corresponding to the uplink message of the application of the terminal device under the first ONT 101 cannot be transmitted due to the inability to query the routing entry of the first ONT 101 is solved, and the terminal device under the first ONT 101 can access the specific application.

To support the communication method provided in any embodiment of the present application, the present application further provides a communication device 900, which can be used to implement the ONT functions in the above communication method. As shown in Figure 9, the communication device 900 includes a receiving module 910, a sending module 920, and a processing module 930.

Receiving module 910, configured to receive a prefix synchronization message sent by a NERG; the prefix synchronization message includes the IPv6 address prefix of the NERG;

a sending module 920 configured to send the IPv6 address prefix of the NERG to the first terminal device, so that the first terminal device obtains a first GUA based on the IPv6 address prefix of the NERG; the IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of the second GUA, and the second GUA is obtained by the second terminal device based on the IPv6 address prefix of the NERG;

The processing module 930 is configured to generate a first network segment routing entry; the destination IP address of the first network segment routing entry is the bridge interface address of NERG.

As a possible implementation, the IPv6 address prefix of the NERG is the IPv6 address prefix of the PPPoE WAN interface of the NERG.

As a possible implementation, the processing module 930 is further configured to: when forwarding the first Internet uplink message through the PPPoE wide area network interface, perform IPv6-to-IPv6 network prefix translation NPTv6 or IPv6-to-IPv6 network address translation NAT66 on the first Internet uplink message, so that the source IP address of the first Internet uplink message is the address of the first ONT.

As a possible implementation method, the sending module 920 is also used to: forward the first application access uplink message to the NERG based on the first static route, so that the NERG performs NPTv6 or NAT66 on the first application access uplink message and sends it to the application, the outbound port of the first static route is the bridge interface of the first ONT, and the next hop address is the bridge interface address of the NERG.

As a possible implementation manner, the processing module 930 is further configured to update the destination media access control MAC address of the uplink message accessed by the first application to the MAC address of the bridge interface of the NERG.

As a possible implementation method, the sending module 920 is also used to: when the PPPoE wide area network interface of the first ONT is in a fault state, send a first fault state synchronization message to the NERG, so that the NERG sends a first route announcement message to the first terminal device, and the first route announcement message is used to instruct the first terminal device to update the gateway to the gateway of the second terminal device; forward the second Internet uplink message of the first terminal device to the NERG, so that the NERG forwards the second Internet uplink message through the PPPoE wide area network interface.

As a possible implementation manner, the DNS server of the first terminal device is proxied by the DNS server of the second terminal device.

As a possible implementation, receiving module 910 is further configured to receive a second fault state synchronization message sent by the NERG. Sending module 920 is further configured to, in response to the second fault state synchronization message, send a second route advertisement message to the second terminal device, the second route advertisement message being configured to instruct the second terminal device to update its gateway to the gateway of the first terminal device. Receiving module 910 is further configured to receive a third Internet uplink message from the second terminal device sent by the NERG. Sending module 920 is further configured to forward the third Internet uplink message via the PPPoE WAN interface.

As a possible implementation, the second route announcement message includes a second route deletion announcement message and a second route creation announcement message, the source IP address of the second route deletion announcement message is the bridge interface address of the first NERG, and the source IP address of the second route creation announcement message is the bridge interface address of the ONT.

The receiving module 910, the sending module 920, and the processing module 930 can all be implemented in software or hardware. For example, the implementation of the receiving module 910 will be described below using the receiving module 910 as an example. Similarly, the implementation of the sending module 920 and the processing module 930 can refer to the implementation of the receiving module 910.

As an example of a software functional unit, the receiving module 910 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Furthermore, the computing instance may be one or more. For example, the receiving module 910 may include code running on multiple hosts/virtual machines/containers. It should be noted that the multiple hosts/virtual machines/containers used to run the code may be distributed in the same region or in different regions. Furthermore, the multiple hosts/virtual machines/containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one data center or multiple geographically close data centers. Typically, a region may include multiple AZs.

Similarly, multiple hosts/virtual machines/containers running the code can be distributed within the same virtual private cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Inter-region communication between two VPCs within the same region, or between VPCs in different regions, requires a communication gateway within each VPC to interconnect the VPCs.

As an example of a hardware functional unit, receiving module 910 may include at least one computing device, such as a server. Alternatively, receiving module 910 may be implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

The multiple computing devices included in the receiving module 910 can be distributed in the same region or in different regions. The multiple computing devices included in the receiving module 910 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the receiving module 910 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of servers, ASICs, PLDs, CPLDs, FPGAs, GALs, and other computing devices.

It should be noted that, in other embodiments, any one of the receiving module 910, the sending module 920, and the processing module 930 can be used to execute any step in the communication method, and the steps that the receiving module 910, the sending module 920, and the processing module 930 are responsible for implementing can be specified as needed. The full functions of the communication device 900 are realized by respectively implementing different steps in the communication method through the receiving module 910, the sending module 920, and the processing module 930.

In order to cooperate with the communication method provided in any embodiment of the present application, the present application further provides a communication device 1000 , which can be used to implement the NERG function in the above communication method.

A sending module 1010 is configured to send a prefix synchronization message to the first ONT, where the prefix synchronization message includes the IPv6 address prefix of the NERG. The prefix synchronization message is used to instruct the first ONT to send the IPv6 address prefix to the first terminal device and generate a first network segment routing entry. The first terminal device obtains a first GUA based on the IPv6 address prefix of the NERG. The IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of the second GUA. The second GUA is obtained by the second terminal device based on the IPv6 address prefix of the NERG. The destination address of the first network segment routing entry is the bridge interface address of the NERG.

As a possible implementation manner, the sending module 1010 is further used to: send a prefix synchronization message to the second ONT; the prefix synchronization message includes the IPv6 address prefix of the NERG, the prefix synchronization message is used to instruct the second ONT to send the IPv6 address prefix to the third terminal device, and generate a second network segment routing item, the third terminal device obtains a third GUA based on the IPv6 address prefix of the NERG, the IPv6 address prefix of the third GUA is the same as the IPv6 address prefix of the second GUA, the second GUA is obtained by the second terminal device based on the IPv6 address prefix of the NERG, and the destination address of the second network segment routing item is the bridge interface address of the NERG.

As a possible implementation, the IPv6 address prefix of the NERG is the IPv6 address prefix of the PPPoE WAN interface of the NERG.

As a possible implementation, communication device 1000 further includes a receiving module 1020 configured to receive a first application access uplink message sent by a first ONT based on a first static route, where the outbound port of the first static route is the bridge interface of the first ONT and the next hop address is the bridge interface address of the NERG. Transmitting module 1010 is further configured to perform NPTv6 or NAT66 on the first application access uplink message and then transmit it to the application.

As a possible implementation method, the communication device 1000 also includes a processing module 1030, which is used to: add a mark to the first application access uplink message; when the first application access downlink message sent by the receiving application includes a mark, the outbound port of the first application access downlink message is set to the bridge interface of the NERG, and the next hop address is set to the address of the bridge interface of the first ONT.

As a possible implementation, the receiving module 1020 is further configured to receive a first fault state synchronization message sent by the first ONT. The sending module 1010 is further configured to, in response to the first fault state synchronization message, send a first route advertisement message to the first terminal device, the first route advertisement message being used to instruct the first terminal device to update its gateway to the gateway of the second terminal device. The receiving module 1020 is further configured to receive a second Internet uplink message from the first ONT for the first terminal device. The sending module 1010 is further configured to forward the second Internet uplink message via the PPPoE WAN interface.

As a possible implementation, the first route announcement message includes a first route deletion announcement message and a first route creation announcement message, the source IP address of the first route deletion announcement message is the bridge interface address of the first ONT, and the source IP address of the second route creation announcement message is the bridge interface address of the NERG.

As a possible implementation method, the sending module 1010 is further used to: when the PPPoE WAN interface of the NERG is in a fault state, send a second fault state synchronization message to the first ONT, so that the first ONT sends a second route announcement message to the second terminal device, and the second route announcement message is used to instruct the second terminal device to update the gateway to the gateway of the first terminal device; forward a third Internet uplink message of the second terminal device to the first ONT, so that the first ONT forwards the third Internet uplink message through the PPPoE WAN interface.

As a possible implementation, the sending module 1010 is further configured to: send a second application access uplink message based on a second static route; the egress port of the second static route is the PPPoE WAN interface of the NERG, and the next hop address is the application address.

As a possible implementation manner, the processing module 1030 is further configured to: when sending the second application access uplink message through the PPPoE WAN interface of the NERG, perform NPTv6 or NAT66 on the second application access uplink message.

The sending module 1010, the receiving module 1020, and the processing module 1030 can all be implemented by software or hardware. For example, the implementation of the sending module 1010 is described below. Similarly, the implementation of the receiving module 1020 and the processing module 1030 can refer to the implementation of the sending module 1010.

As an example of a software functional unit, the sending module 1010 may include code running on a computing instance. The computing instance may be at least one of a physical host (computing device), a virtual machine, a container, and other computing devices. Furthermore, the above-mentioned computing device may be one or more. For example, the sending module 1010 may include code running on multiple hosts/virtual machines/containers. It should be noted that the multiple hosts/virtual machines/containers used to run the application may be distributed in the same region or in different regions. The multiple hosts/virtual machines/containers used to run the code may be distributed in the same AZ or in different AZs, and each AZ includes one data center or multiple data centers with close geographical locations. Generally, a region may include multiple AZs.

Similarly, the multiple hosts/virtual machines/containers running the code can be distributed within the same VPC or across multiple VPCs. Typically, a VPC is located within a region. Cross-region communication between two VPCs within the same region, or between VPCs in different regions, requires a communication gateway within each VPC to interconnect the VPCs.

As an example of a hardware functional unit, the sending module 1010 may include at least one computing device, such as a server. Alternatively, the sending module 1010 may be implemented using an ASIC or a PLD. The PLD may be implemented using a CPLD, an FPGA, a GAL, or any combination thereof.

The multiple computing devices included in the sending module 1010 can be distributed in the same region or in different regions. The multiple computing devices included in the sending module 1010 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the sending module 1010 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

This application also provides a computing device 1100. As shown in Figure 11, computing device 1100 includes a bus 1102, a processor 1104, a memory 1106, and a communication interface 1108. Processor 1104, memory 1106, and communication interface 1108 communicate with each other via bus 1102. Computing device 1100 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in computing device 1100.

Bus 1102 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Buses can be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG11 shows only one line, but this does not imply a single bus or type of bus. Bus 1102 may include a path for transmitting information between various components of computing device 1100 (e.g., memory 1106, processor 1104, and communication interface 1108).

Processor 1104 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

The memory 1106 may include volatile memory, such as random access memory (RAM). The processor 1104 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

The memory 1106 stores executable program code, and the processor 1104 executes the executable program code to respectively implement the functions of each module included in the aforementioned communication device 900 or communication device 1000, thereby implementing the communication method. In other words, the memory 1106 stores instructions for executing the communication method.

Alternatively, the memory 1106 stores executable codes, and the processor 1104 executes the executable codes to implement the functions of the aforementioned ONT or NERG, thereby implementing the communication method. That is, the memory 1106 stores instructions for executing the communication method.

The communication interface 1108 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 1100 and other devices or a communication network.

Considering that the communication method provided in this application is applied to the communication system 100, the infrastructure of the communication system 100, such as the ECGW, typically includes multiple computing devices. Therefore, this application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

As shown in Figure 12, the computing device cluster includes at least one computing device 1100. The memory 1106 of one or more computing devices 1100 in the computing device cluster may store the same instructions for executing the communication method.

In some possible implementations, the memory 1106 of one or more computing devices 1100 in the computing device cluster may also store partial instructions for executing the communication method. In other words, the combination of one or more computing devices 1100 can jointly execute the instructions for executing the communication method.

It should be noted that the memory 1106 in different computing devices 1100 in the computing device cluster may store different instructions, each for executing part of the functions of the communication device 900 or the communication device 1000. In other words, the instructions stored in the memory 1106 in different computing devices 1100 may implement the functions of one or more modules included in the communication device 900 or the communication device 1000.

In some possible implementations, one or more computing devices in a computing device cluster may be connected via a network. The network may be a wide area network (WAN) or a local area network (LAN), among others. FIG13 illustrates one possible implementation. As shown in FIG13 , two computing devices 1100A and 1100B are connected via a network. Specifically, the connection to the network is achieved via a communication interface in each computing device. In this type of possible implementation, the memory 1106 in the computing device 1100A stores instructions for executing the functions of one or more of the receiving module 910, the sending module 920, and the processing module 930. FIG13 illustrates an example of the memory 1106 in the computing device 1100A storing instructions for executing the functions of the receiving module 910. Simultaneously, the memory 1106 in the computing device 1100B stores instructions for executing the functions of one or more of the receiving module 910, the sending module 920, and the processing module 930. FIG13 illustrates an example of the memory 1106 in the computing device 1100B storing instructions for executing the functions of the sending module 920 and the processing module 930.

It should be understood that the functionality of the computing device 1100A shown in FIG13 may also be implemented by multiple computing devices 1100. Similarly, the functionality of the computing device 1100B may also be implemented by multiple computing devices 1100.

Embodiments of the present application also provide a computer program product comprising instructions. The computer program product may be software or a program product comprising instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, it causes the at least one computing device to perform the communication method provided in any embodiment of the present application, or the steps performed by an ONT or NERG in the communication method.

The embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the communication method provided in any embodiment of the present application, or the steps performed by the ONT or NERG in the communication method.

The above embodiments can be implemented in whole or in part by software, hardware (such as circuits), firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (such as infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.

Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

In this application, "at least one" means one or more, and "more" means two or more. "And/or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character "/" generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b and c can be single or multiple.

It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the various embodiments of the present invention.

Claims (26)

A communication method, characterized in that it is applied to a first optical network terminal (ONT), the first ONT is connected to a network enhanced residential gateway (NERG), the first ONT is connected to a first terminal device, and the NERG is connected to a second terminal device, the method comprising: receiving a prefix synchronization message sent by the NERG, wherein the prefix synchronization message includes an Internet Protocol version 6 (IPv6) address prefix of the NERG; Sending the IPv6 address prefix of the NERG to the first terminal device, so that the first terminal device obtains a first global unicast address (GUA) based on the IPv6 address prefix of the NERG, where the IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of a second GUA, and the second GUA is obtained by the second terminal device based on the IPv6 address prefix of the NERG; A first network segment routing entry is generated, where the destination IP address of the first network segment routing entry is the bridge interface address of the NERG. The method according to claim 1, wherein the IPv6 address prefix of the NERG is the IPv6 address prefix of the NERG's Point-to-Point Protocol over Ethernet (PPPoE) wide area network interface. The method according to claim 1 or 2, characterized in that the method further comprises: When forwarding the first Internet uplink message through the PPPoE wide area network interface, IPv6-to-IPv6 network prefix translation (NPTv6) or IPv6-to-IPv6 network address translation (NAT66) is performed on the first Internet uplink message, so that the source IP address of the first Internet uplink message is the address of the first ONT. The method according to any one of claims 1 to 3, further comprising: The first application access uplink message is forwarded to the NERG based on the first static route, so that the NERG performs NPTv6 or NAT66 on the first application access uplink message and sends it to the application, the outbound port of the first static route is the bridge interface of the first ONT, and the next hop address is the bridge interface address of the NERG. The method according to claim 4, wherein the destination IP address of the uplink message accessed by the first application is the address of the application, and the method further comprises: The destination media access control (MAC) address of the first application access uplink message is updated to the MAC address of the bridge interface of the NERG. The method according to any one of claims 1 to 5, further comprising: When the PPPoE WAN interface of the first ONT is in a fault state, sending a first fault state synchronization message to the NERG, so that the NERG sends a first route advertisement message to the first terminal device, where the first route advertisement message is used to instruct the first terminal device to update the gateway to the gateway of the second terminal device; The second Internet uplink message of the first terminal device is forwarded to the NERG, so that the NERG forwards the second Internet uplink message through the PPPoE wide area network interface. The method according to claim 6 is characterized in that the domain name system server of the first terminal device is proxied by the domain name system server of the second terminal device. The method according to any one of claims 1 to 7, further comprising: receiving a second fault state synchronization message sent by the NERG; In response to the second fault state synchronization message, sending a second route advertisement message to the second terminal device, where the second route advertisement message is used to instruct the second terminal device to update the gateway to the gateway of the first terminal device; receiving a third Internet uplink message from the second terminal device sent by the NERG; The third Internet uplink message is forwarded through the PPPoE wide area network interface. The method according to claim 8, characterized in that the second route announcement message includes a second route deletion announcement message and a second route creation announcement message, the source IP address of the second route deletion announcement message is the bridge interface address of the first NERG, and the source IP address of the second route creation announcement message is the bridge interface address of the ONT. A communication method, characterized in that it is applied to a NERG, the NERG is connected to a first ONT, the first ONT is connected to a first terminal device, and the NERG is connected to a second terminal device, the method comprising: Send a prefix synchronization message to the first ONT, where the prefix synchronization message includes the IPv6 address prefix of the NERG. The prefix synchronization message is used to instruct the first ONT to send the IPv6 address prefix of the NERG to the first terminal device, and to generate a first network segment routing entry. The IPv6 address prefix of the NERG is used to instruct the first terminal device to obtain a first GUA based on the IPv6 address prefix of the NERG. The IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of the second GUA. The second GUA is obtained by the second terminal device based on the IPv6 address prefix of the NERG. The destination address of the first network segment routing entry is the bridge interface address of the NERG. The method according to claim 10, wherein the NERG is connected to a second ONT, and the second ONT is connected to a third terminal device, and the method further comprises: Sending a prefix synchronization message to the second ONT; the prefix synchronization message includes the IPv6 address prefix of the NERG, the prefix synchronization message is used to instruct the second ONT to send the IPv6 address prefix of the NERG to the third terminal device, and generate a second network segment routing item, the third terminal device obtains a third GUA based on the IPv6 address prefix of the NERG, the IPv6 address prefix of the third GUA is the same as the IPv6 address prefix of the second GUA, the second GUA is obtained by the second terminal device based on the IPv6 address prefix of the NERG, and the destination address of the second network segment routing item is the bridge interface address of the NERG. The method according to claim 10 or 11, characterized in that the IPv6 address prefix of the NERG is the IPv6 address prefix of the PPPoE wide area network interface of the NERG. The method according to any one of claims 10 to 12, further comprising: receiving a first application access uplink message sent by the first ONT based on a first static route, where the outbound port of the first static route is the bridge interface of the first ONT, and the next hop address is the bridge interface address of the NERG; The first application access uplink message is NPTv6 or NAT66 performed and then sent to the application. The method according to claim 13, further comprising: Adding a mark to the uplink message accessed by the first application; When receiving a first application access downlink message sent by the application including the tag, the outbound port of the first application access downlink message is set to the bridge interface of the NERG, and the next hop address is set to the address of the bridge interface of the first ONT. The method according to any one of claims 10 to 14, further comprising: Receiving a first fault status synchronization message sent by the first ONT; In response to the first fault state synchronization message, sending a first routing advertisement message to the first terminal device, where the first routing advertisement message is used to instruct the first terminal device to update the gateway to the gateway of the second terminal device; receiving a second Internet uplink message of the first terminal device sent by the first ONT; The second Internet uplink message is forwarded through the PPPoE wide area network interface. The method according to claim 15, characterized in that the first route announcement message includes a first route deletion announcement message and a first route creation announcement message, the source IP address of the first route deletion announcement message is the bridge interface address of the first ONT, and the source IP address of the second route creation announcement message is the bridge interface address of the NERG. The method according to any one of claims 10 to 16, further comprising: When the PPPoE WAN interface of the NERG is in a fault state, sending a second fault state synchronization message to the first ONT, so that the first ONT sends a second route advertisement message to the second terminal device, where the second route advertisement message is used to instruct the second terminal device to update the gateway to the gateway of the first terminal device; Forward a third Internet uplink message of the second terminal device to the first ONT, so that the first ONT forwards the third Internet uplink message through the PPPoE wide area network interface. The method according to any one of claims 10 to 17, further comprising: A second application access uplink message is sent based on a second static route; the egress port of the second static route is the PPPoE WAN interface of the NERG, and the next hop address is the address of the application. The method according to claim 18, further comprising: When the second application access uplink message is sent through the PPPoE WAN interface of the NERG, the second application access uplink message is subjected to NPTv6 or NAT66. A communication device, characterized in that the device comprises: A receiving module, configured to receive a prefix synchronization message sent by the NERG; the prefix synchronization message includes the IPv6 address prefix of the NERG; a sending module, configured to send the IPv6 address prefix of the NERG to the first terminal device, so that the first terminal device obtains a first GUA based on the IPv6 address prefix of the NERG; the IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of a second GUA, and the second GUA is obtained by the second terminal device based on the IPv6 address prefix of the NERG; The processing module is used to generate a first network segment routing item; the destination IP address of the first network segment routing item is the bridge interface address of the NERG. A communication device, characterized in that the device comprises: a sending module, configured to send a prefix synchronization message to the first ONT; the prefix synchronization message includes the IPv6 address prefix of the NERG, so that the first ONT sends the IPv6 address prefix of the NERG to the first terminal device, and the first terminal device obtains a first GUA based on the IPv6 address prefix of the NERG and generates a first network segment routing entry, where the IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of a second GUA, the second GUA is obtained by the second terminal device based on the IPv6 address prefix of the NERG, and the destination address of the first network segment routing entry is the bridge interface address of the NERG. A communication system, characterized in that the system includes a first ONT and a NERG, wherein the first ONT is connected to the NERG, the first ONT is connected to a first terminal device, and the NERG is connected to a second terminal device; The NERG is configured to send a prefix synchronization message to the first ONT, where the prefix synchronization message includes an Internet Protocol version 6 (IPv6) address prefix of the NERG; The first ONT is configured to receive a prefix synchronization message sent by the NERG; The first ONT is further configured to send the IPv6 address prefix to the first terminal device, so that the first terminal device obtains a first global unicast address GUA based on the IPv6 address prefix of the NERG, where the IPv6 address prefix of the first GUA is the same as the IPv6 address prefix of a second GUA, and the second GUA is obtained by the second terminal device based on the IPv6 address prefix of the NERG; The first ONT is further configured to generate a first network segment routing entry, where the destination IP address of the first network segment routing entry is the bridge interface address of the NERG. A computer program product comprising instructions, wherein when the instructions are executed by a computing device, the computing device is caused to perform the method according to any one of claims 1 to 9. A computer program product comprising instructions, wherein when the instructions are executed by a computing device cluster, the computing device cluster is caused to perform the method according to any one of claims 10 to 19. A computer-readable storage medium, characterized in that it includes computer program instructions, when the computer program instructions are executed by a computing device, the computing device executes the method according to any one of claims 1 to 9. A computer-readable storage medium, characterized in that it includes computer program instructions, and when the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method according to any one of claims 10 to 19.