Communication methods and systems, electronic devices, computer-readable media

Abstract

The present application provides a communication method and system, electronic device, and computer-readable medium, the communication method including the steps of receiving an Ethernet frame transmitted by a first terminal, packaging a first port ID of a first slave gateway and the Ethernet frame as a first Gigabit Passive Optical Network Package Mode GEM frame, and transmitting the first GEM frame to a main gateway, where the first port ID is a port ID used when communicating between optical network units.

Description

Technical Field

[0004] , , , , ,

[0003] ,

[0001] Embodiments of the present application relate to the technical field of Passive Optical Network (PON) technology, and particularly relate to communication methods and systems, electronic devices, and computer-readable media.

Background Art

[0002] With the application and development of PON technology, it has gradually entered homes from the introduction of optical fibers to homes (FTTH, Fiber to the Home), and all domestic and international standards have started corresponding standardization and are gradually developing towards the reach of optical fibers to remote end nodes (FTTR, Fiber to the Room). FTTR can access the Internet through the access network and can also build a local area network to realize interconnection communication within the home.

Summary of the Invention

Problems to be Solved by the Invention

[0003] In actual applications, as shown in FIG. 1, a general FTTH Optical Network Unit (ONU) and an FTTR Optical Line Terminal (OLT) are integrated into one device, which can be called a main gateway. The main gateway has an upper optical port and a lower optical port. The main gateway is connected to the FTTH OLT through the upper optical port and operates according to the FTTH ONU. The main gateway is connected to the FTTR ONU through the lower optical port and operates according to the FTTR OLT.

[0004] The FTTR ONU and access point (AP) are integrated into a single device, which can be called a slave gateway. The slave gateway has an upper optical port and a wireless interface. The slave gateway is connected to the FTTR OLT via the upper optical port and operates according to the FTTR ONU, and the slave gateway is connected to the terminal via the wireless interface and operates according to the access point (AP). In conventional PON systems, there is a relatively large time lag during communication between FTTR ONUs. [Means for solving the problem]

[0005] Embodiments of the present application provide a communication method and system, electronic equipment, and a computer-readable medium.

[0006] In a first embodiment, an embodiment of the present application provides a communication method applicable to a first slave gateway, comprising the steps of: receiving an Ethernet® frame transmitted by a first terminal; packaging the first port ID of the first slave gateway and the Ethernet frame as a first Gigabit Passive Optical Network Package Mode GEM frame; and transmitting the first GEM frame to a main gateway, wherein the first port ID is a port ID used when communicating between optical network units.

[0007] In a second embodiment, an embodiment of the present application provides a communication method applicable to a main gateway, comprising the steps of: receiving a first gigabit passive optical network package mode GEM frame transmitted by a first slave gateway, wherein the first GEM frame includes a port ID; and, if it is determined that the port ID in the first GEM frame is a port ID used for communication between optical network units, transmitting the first GEM frame to all slave gateways.

[0008] In a third embodiment, an embodiment of the present application provides a communication method applicable to a third slave gateway, comprising the steps of: receiving a first gigabit passive optical network package mode GEM frame transmitted by a main gateway, wherein the first GEM frame includes a port ID; and determining whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame.

[0009] In a fourth embodiment, an embodiment of the present application provides an electronic device including at least one processor and a memory that stores at least one program and causes the at least one processor to implement any one of the above-described communication methods when the at least one program is executed by the at least one processor.

[0010] In a fifth embodiment, an embodiment of the present application provides a computer-readable medium on which a computer program is stored and which causes the processor to implement one of the above-described communication methods when the computer program is executed by the processor.

[0011] In a sixth embodiment, the embodiment of the present application provides a communication system comprising a first slave gateway, a main gateway, and a third slave gateway, wherein the first slave gateway is used to receive an Ethernet frame transmitted by a first terminal, packages the first port ID of the first slave gateway and the Ethernet frame as a first Gigabit Passive Optical Network Package Mode GEM frame, and transmits the first GEM frame to the main gateway, where the first port ID is a port ID used when communicating between optical network units; the main gateway is used to receive a first GEM frame transmitted by the first gateway, where the first GEM includes a port ID, and if it determines that the port ID in the first GEM frame is a port ID used when communicating between optical network units, it transmits the first GEM frame to all slave gateways; and the third slave gateway is used to receive a first GEM frame transmitted by the main gateway, where the first GEM frame includes a port ID, and determines whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame. [Effects of the Invention]

[0012] The communication method provided in the embodiment of the present invention performs communication between ONUs based on the port ID used when communicating between ONUs and OLTs, rather than based on the port ID used when communicating between ONUs and OLTs. This eliminates the need for the main gateway to parse the first GEM frame when forwarding, meaning that traffic forwarding between ONUs does not need to be implemented via the Ethernet or IP layer of the main gateway, and can be implemented only at the PON protocol layer of the main gateway, thereby reducing time lag. [Brief explanation of the drawing]

[0013] [Figure 1] This is a conceptual diagram of the PON system structure in related technologies. [Figure 2] This is a flowchart of a communication method applied to a first slave gateway provided by one embodiment of the present invention. [Figure 3] This is a conceptual diagram of the frame structure of the GEM frame according to the present embodiment. [Figure 4] This is a flowchart of a communication method applied to a main gateway provided by another embodiment of the present invention. [Figure 5] This is a flowchart of a communication method applied to a third slave gateway provided in another embodiment of the present invention. [Figure 6] This is a block diagram of a communication system provided by another embodiment of the present application. [Modes for carrying out the invention]

[0014] To enable those skilled in the art to better understand the technical proposal of this application, the communication methods and systems, electronic devices, and computer-readable media provided by this application will be described in detail below, accompanied by drawings.

[0015] The exemplary embodiments will be described in more detail below with reference to the drawings, but these exemplary embodiments should not be construed as being limited to the embodiments described herein and may be embodied in different forms. On the contrary, the purpose of providing these embodiments is to make the present application transparent and complete and to allow those skilled in the art to fully understand the scope of the present application.

[0016] Where there is no contradiction, each embodiment and each feature in the embodiment of this application may be combined with one another.

[0017] As used herein, the term "and / or" includes any and all combinations of at least one of the enumerated items relating to the subject.

[0018] The terms used in this specification are only used to describe specific embodiments and are not intended to limit the present application. Singular forms such as "one" and "said" used in this specification are also intended to include the plural form unless the context clearly indicates otherwise. Also, when the terms "comprising" and / or "consisting of" are used in this specification, they refer to the presence of such features, wholes, steps, operations, elements and / or assemblies, but it will also be understood that they do not exclude the presence or addition of at least one other feature, whole, step, operation, element, assembly and / or group thereof.

[0019] Unless otherwise specifically limited, the meanings of all terms (including technical and scientific terms) used in this specification are the same as those commonly understood by those skilled in the art. Also, terms defined in general dictionaries are construed to have meanings consistent with their meanings in the context of the related art and the background of the present application, and are not construed to have ideal or overly formal meanings, unless specifically limited in this specification.

[0020] In a conventional PON, FTTR ONUs can achieve interconnection communication through main gateway relay. A common implementation method is to arrange a Gigabit-Capable Passive Optical Network (GPON) Encapsulation Method (GEM) Port ID (Port-ID, Port Identification) between the FTTR OLT and the FTTR ONU to realize communication between the FTTR OLT and the FTTR ONU, and then transfer the communication between the FTTR ONUs by the FTTR OLT.

[0021] Currently, traffic transfer between FTTR ONUs via the Ethernet layer or Internet Protocol (IP) layer of the main gateway is required, which will result in a large time lag. For example, one way to realize communication between FTTR ONUs is that the FTTR OLT analyzes the Ethernet frame from the GEM frame, obtains the target Media Access Control (MAC) address from the Ethernet frame, maps the target MAC address to the target GEM Port-ID, repackages the Ethernet frame using the target GEM Port-ID to obtain a new GEM frame, and transmits the new GEM frame. In this process, in addition to the analysis of the GEM frame in the PON protocol layer and the repackaging of the Ethernet frame into the GEM frame, it is necessary to complete the analysis of the target MAC address and the mapping of the target MAC address and GEM Port-ID in the Ethernet layer, so a large time lag will occur. In some scenarios, it is necessary to further realize the mapping between the target IP address and the target GEM Port-ID, that is, it needs to be realized in the IP layer, and similarly, there is a large time lag in bandwidth.

[0022] Figure 2 is a flowchart of a communication method applied to the first slave gateway provided by an embodiment of the present application.

[0023] In the first aspect, referring to FIG. 2, in an embodiment of the present application, a communication method applied to the first slave gateway and including the following steps is provided.

[0024] Step 200, receive an Ethernet frame sent by the first terminal.

[0025] Step 201: The first port ID of the first slave gateway and the Ethernet frame are packaged as the first GEM frame, and the first GEM frame is sent to the main gateway. The first port ID is the port ID used when communicating between ONUs.

[0026] In some exemplary embodiments, as shown in Figure 3, the GEM frame includes a GEM frame header and a GEM frame payload region.

[0027] In some exemplary implementations, the GEM frame header includes a Payload Length Indication (PLI), Key Index, Port ID, Reserved Fields (Options), Last Fragment (LF), and Hybrid Error Correction (HEC).

[0028] In some exemplary embodiments, the port ID may be the first port ID of the slave gateway, or the second port ID of the slave gateway. Here, the first port ID is the port ID used when communicating between ONUs, and the second port ID is the port ID used when communicating between the ONU and the OLT.

[0029] In some exemplary cases, LF is used to indicate whether or not it is the last fragment.

[0030] In some exemplary embodiments, the step of packaging the first port ID of the first slave gateway and the Ethernet frame as a first GEM frame includes packaging the Ethernet frame in the payload area of ​​the first GEM frame and packaging the first port ID of the first slave gateway in the GEM frame header of the first GEM frame.

[0031] In some exemplary embodiments, the step of packaging the first port ID of the first slave gateway into the GEM frame header in the first GEM frame includes the step of packaging the first port ID of the first slave gateway into the port ID field in the GEM frame header.

[0032] In some exemplary embodiments, the step of packaging the first port ID of the first slave gateway and the Ethernet frame as a first GEM frame includes the step of packaging the first port ID of the first slave gateway, the first ID, and the Ethernet frame as a first GEM frame.

[0033] In some exemplary embodiments, the first ID may be the User Network Interface (UNI) node ID (Node ID, Node Identification) of the first slave gateway, or the UNI Node ID of the second slave gateway, where the second slave gateway is a slave gateway connected to the second terminal, and the second terminal is the terminal to which the target MAC address in the Ethernet frame belongs.

[0034] In some exemplary embodiments, the first ID may be the device ID of the second slave gateway.

[0035] In some exemplary implementations, the UNI Node ID is used to identify two communicating terminals. For example, ONU1 is represented by 1 and ONU2 by 0, thus representing the two communicating ONUs as 0 and 1.

[0036] In some exemplary embodiments, the step of packaging the first port ID, first ID, and Ethernet frame of the first slave gateway as a first GEM frame includes packaging the Ethernet frame in the payload area of ​​the first GEM frame and packaging the first port ID and first ID of the first slave gateway in the GEM frame header of the first GEM frame.

[0037] In some exemplary embodiments, the step of packaging the first port ID and first ID of the first slave gateway into the GEM frame header in the first GEM frame includes packaging the first port ID of the first slave gateway into the port ID field in the GEM frame header and packaging the first ID into the reserved field in the GEM frame header.

[0038] In some exemplary embodiments, if the first ID is the UNI Node ID of the first slave gateway, or if the first ID is the UNI Node ID of the second slave gateway, the step of packaging the first ID in a reserved field in the GEM frame header includes the step of packaging the first ID in any one bit in the reserved field.

[0039] In some exemplary embodiments, the step of packaging the first ID into any one bit in the reserved field includes the step of packaging the first ID into the most significant bit in the reserved field.

[0040] In some exemplary embodiments, if the first ID is the device ID of the second slave gateway, the step of packaging the first ID in the reserved field in the GEM frame header includes the step of packaging the first ID in at least one bit in the reserved field.

[0041] In some exemplary embodiments, the step of packaging the first port ID and first ID of the first slave gateway into the GEM frame header of the first GEM frame includes the step of packaging the first port ID, first ID, and second ID of the first slave gateway into the GEM header of the first GEM frame, the second ID being used to characterize whether the first GEM frame is a GEM frame for communication between ONUs or a GEM frame for communication between an ONU and an OLT.

[0042] In some exemplary embodiments, the step of packaging the first port ID, first ID, and second ID of the first slave gateway into the GEM frame header in the first GEM frame includes packaging the first port ID of the first slave gateway into the port ID field in the GEM frame header, and packaging the first ID and second ID into the reserved field in the GEM frame header.

[0043] In some exemplary embodiments, the first ID and the second ID are packaged in different bits in a reserved field in the GEM frame header.

[0044] In some exemplary embodiments, if the first ID is the UNI Node ID of the first slave gateway, or if the first ID is the UNI Node ID of the second slave gateway, the first ID is packaged in one of the bits in the reserved field, and the second ID is packaged in one of the bits in the reserved field other than the bit occupied by the first ID. For example, the first ID is packaged in the most significant bit in the reserved field, and the second ID is packaged in one of the bits in the reserved field other than the most significant bit.

[0045] In some exemplary embodiments, if the first ID is the device ID of the second slave gateway, the first ID is packaged in at least one bit in the reserved field, and the second ID is packaged in any one of the other bits in the reserved field, excluding the bit occupied by the first ID.

[0046] In some exemplary embodiments, if the second ID is not packaged in the first GEM frame, the first and second port IDs of the same slave gateway are different in order to distinguish whether the first GEM frame is a GEM frame communicated between ONUs or between an ONU and an OLT.

[0047] When the second ID is packaged in the first GEM frame, the values ​​of the first and second port IDs of the same slave gateway may be the same or different. The second ID distinguishes whether the first GEM frame is a GEM frame for communication between ONUs or a GEM frame for communication between an ONU and an OLT. If the values ​​of the first and second port IDs of the same gateway are the same, port ID resources are saved.

[0048] In some exemplary embodiments, if the first ID is not packaged in the first GEM frame, the method further includes the step of obtaining the first port ID of the first slave gateway after receiving the Ethernet frame transmitted by the first terminal and before packaging the Ethernet frame as the first GEM frame.

[0049] In some exemplary embodiments, the step of obtaining the first port ID of the first slave gateway includes the step of obtaining the device ID of the second slave gateway by the target MAC address in the Ethernet frame, wherein the second slave gateway is a slave gateway connected to the second terminal to which the target MAC address belongs, and the step of obtaining the first port ID of the first slave gateway by the device ID of the second slave gateway.

[0050] In some exemplary embodiments, the step of obtaining the first port ID of the first slave gateway using the device ID of the second slave gateway includes the steps of obtaining first configuration information that the peer device ID is the device ID of the second slave gateway, and obtaining the port ID in the first configuration information as the first port ID of the first slave gateway.

[0051] In some exemplary embodiments, where a first ID is packaged in a first GEM frame and the first ID is the UNI Node ID of a first slave gateway, or the first ID is the UNI Node ID of a second slave gateway, the method further includes, after the step of receiving an Ethernet frame transmitted by a first terminal, and before the step of packaging the Ethernet frame as a first GEM frame, the first port ID and first ID of the first slave gateway.

[0052] In some exemplary embodiments, the step of obtaining the first port ID and first ID of the first slave gateway includes the step of obtaining the device ID of the second slave gateway by the target MAC address in the Ethernet frame, wherein the second slave gateway is a slave gateway connected to the second terminal to which the target MAC address belongs, and the step of obtaining the first port ID and first ID of the first slave gateway by the device ID of the second slave gateway.

[0053] In some exemplary embodiments, the step of obtaining the device ID of the second slave gateway by the target MAC address in the Ethernet frame includes the step of searching for the device ID corresponding to the target media access control address in a first mapping relationship between the device ID and MAC address of a pre-stored slave gateway, and the device ID found is the device ID of the second slave gateway.

[0054] In some exemplary embodiments, the device ID of the slave gateway may be the ONU ID.

[0055] In some exemplary embodiments, with respect to each slave gateway, after a terminal connected to the slave gateway (e.g., the first and second terminals referred to in the embodiments of the present application) accesses the slave gateway, the slave gateway can learn the MAC address of the terminal and further store a first mapping relationship between the learned MAC address and the device ID of the slave gateway.

[0056] In some exemplary embodiments, prior to the step of finding a device ID corresponding to a target MAC address, the method further includes the step of obtaining a second mapping relationship shared by other slave gateways and using the second mapping relationship to store or update the first mapping relationship.

[0057] In some exemplary embodiments, the second mapping relationship is a mapping relationship between the MAC address of a terminal connected to another slave gateway, which is stored after the other slave gateway has learned the MAC address of that terminal, and the device ID of the other slave gateway.

[0058] In some exemplary embodiments, other slave gateways may share the second mapping relationship in multiple ways, for example, after learning the MAC address of a terminal connected to the other slave gateway, they may share the second mapping relationship, specifically with the main gateway, or they may share it with each other among different slave gateways.

[0059] In some exemplary embodiments, the step of obtaining the device ID of a second slave gateway by the target MAC address in an Ethernet frame includes the step of sending an acquisition request to a main gateway, the acquisition request being used to obtain a first mapping relationship corresponding to a target media access control address, the first mapping relationship being a mapping relationship between the device ID of the slave gateway and the media access control address, and the step of receiving the first mapping relationship corresponding to the target media access control address transmitted from the main gateway and obtaining the device ID in the first mapping relationship corresponding to the target media access control address.

[0060] In some exemplary cases, the acquisition request includes the target MAC address.

[0061] In some exemplary embodiments, the step of obtaining the device ID of a second slave gateway by the target MAC address in an Ethernet frame includes the steps of sending a request to another gateway, the request of which is used to obtain a first mapping relationship corresponding to a target media access control address, the first mapping relationship being a mapping relationship between the device ID of the slave gateway and the media access control address, and receiving the first mapping relationship corresponding to a target media access control address sent from the other gateway and obtaining the device ID in the first mapping relationship corresponding to the target media access control address.

[0062] In some exemplary embodiments, the step of obtaining the first port ID and first ID of the first slave gateway by the device ID of the second slave gateway includes the steps of: obtaining first configuration information that the peer device ID is the device ID of the second slave gateway; obtaining the port ID in the first configuration information as the first port ID of the first slave gateway; if the first ID is the UNI Node ID of the first slave gateway, obtaining the UNI Node ID in the first configuration information, and the obtained UNI Node ID being the first ID; and if the first ID is the UNI Node ID of the second slave gateway, obtaining the first ID by the UNI Node ID in the first configuration information.

[0063] For example, if we represent the two ONUs that communicate as 0 and 1, and assume that the UNI Node ID in the first configuration information is 0, then we can identify the first ID as 1, and if the UNI Node ID in the first configuration information is 1, then we can identify the first ID as 0.

[0064] In some exemplary embodiments, the peer device ID may be the peer ONU ID.

[0065] In some exemplary embodiments, communication between any two slave gateways corresponds to a single configuration piece of information: a GEM Port Network Connection Terminal Point (CTP) Maintenance Entity (ME), where the GEM Port Network CTP ME is associated with a Transmission Container (T-CONT) and a GEM IW TP ME.

[0066] In some exemplary implementations, the GEM Port Network CTP ME includes the following attributes:

[0067] This is the Managed Entity ID, and this attribute is just one example of how to uniquely identify a GEM Port Network CTP ME.

[0068] This is the Port ID, and this attribute is used to indicate the Port ID of the GEM port associated with the GEM Port Network CTP ME.

[0069] This is a T-CONT pointer, and this attribute points to an instance of T-CONT.

[0070] This attribute, Direction, describes whether the GEM port is used for UNI-to-ANNI, ANI-to-UNI, bidirectional connections, or bidirectional UNI-to-UNI connections. For example, a value of 1 indicates that the GEM port is used for UNI-to-ANN connections, a value of 2 indicates that the GEM port is used for ANI-to-UNI connections, a value of 3 indicates that the GEM port is used for bidirectional connections, and a value of 4 indicates that the GEM port is used for bidirectional UNI-to-UNI connections.

[0071] This is the peer device ID, and this attribute is used to identify the device ID of the other slave gateway with which it communicates.

[0072] Here, UNI-to-UNI is a new communication type added to the embodiments of the present invention, and represents communication between ONUs.

[0073] Here, the UNI Node ID is an attribute newly added to the embodiment of the present invention.

[0074] Here, the peer device ID is an attribute newly added to the embodiment of the present application.

[0075] In some exemplary embodiments, the GEM Port Network CTP ME further includes an associated port ID, which is used to describe the first port ID of the slave gateway to which the ONU communicating with the main gateway belongs.

[0076] In some exemplary cases, the GEM Port Network CTP ME further includes a UNI Node ID, which represents the two communicating terminals.

[0077] In some exemplary embodiments, if the first ID is the device ID of the second slave gateway, after the step of receiving an Ethernet frame transmitted by the first terminal, and before the step of packaging the Ethernet frame as a first GEM frame, the first port ID of the first slave gateway, the first ID, and the Ethernet frame, the method includes the steps of obtaining the device ID of the second slave gateway by the target MAC address and obtaining the first port ID of the first slave gateway by the device ID of the second slave gateway.

[0078] In some exemplary embodiments, the step of obtaining the first port ID of the first slave gateway using the device ID of the second slave gateway includes the steps of obtaining first configuration information that the peer device ID is the device ID of the second slave gateway, and obtaining the port ID in the first configuration information as the first port ID of the first slave gateway.

[0079] In some exemplary embodiments, if the device ID of the second slave gateway cannot be obtained, the method includes the step of packaging the port ID and Ethernet frame for uplink broadcast as a second GEM frame and sending the second GEM frame to the main gateway.

[0080] In some exemplary embodiments, the step of packaging the port ID for uplink broadcast and the Ethernet frame as a second GEM frame includes packaging the port ID for uplink broadcast in the port ID field in the GEM frame header of the second GEM frame and packaging the Ethernet frame in the payload area of ​​the second GEM frame.

[0081] The communication method provided in the embodiment of the present invention performs communication between ONUs based on the port ID used when communicating between ONUs and OLTs, rather than based on the port ID used when communicating between ONUs and OLTs. This eliminates the need for the main gateway to parse the first GEM frame when forwarding, meaning that traffic forwarding between ONUs does not need to be implemented via the Ethernet or IP layer of the main gateway, and can be implemented only at the PON protocol layer of the main gateway, thereby reducing time lag.

[0082] Figure 4 is a flowchart of a communication method applied to a main gateway provided in another embodiment of the present invention.

[0083] In a second embodiment, referring to Figure 4, another embodiment of the present application provides a communication method applied to a main gateway, which includes the following steps:

[0084] Step 400: The first GEM frame is received from the first slave gateway, and the first GEM frame contains the port ID.

[0085] In some exemplary embodiments, as shown in Figure 3, the first GEM frame includes a GEM frame header and a GEM frame payload region.

[0086] In some exemplary cases, the GEM frame header includes PLI, Key Index, Port ID, Options, LF, and HEC.

[0087] In some exemplary embodiments, the port ID may be the first port ID of the slave gateway, or the second port ID of the slave gateway. Here, the first port ID is the port ID used when communicating between ONUs, and the second port ID is the port ID used when communicating between the ONU and the OLT.

[0088] In some exemplary cases, LF is used to indicate whether or not it is the last fragment.

[0089] In some exemplary embodiments, the first GEM frame further includes a first ID.

[0090] In some exemplary embodiments, the first ID may be the UNI Node ID of the first slave gateway or the UNI Node ID of the second slave gateway. Here, the second slave gateway is a slave gateway connected to the second terminal, and the second terminal is the terminal to which the target MAC address in the Ethernet frame belongs.

[0091] In some exemplary embodiments, the first ID may be the device ID of the second slave gateway.

[0092] In some exemplary implementations, the UNI Node ID is used to identify two communicating terminals. For example, ONU1 is represented by 1 and ONU2 by 0, thus representing the two communicating ONUs as 0 and 1.

[0093] In some exemplary embodiments, the GEM frame header of the first GEM frame includes the port ID and the first ID.

[0094] In some exemplary embodiments, the Port ID field in the GEM frame header contains the Port ID, and the Reserved field in the GEM frame header contains the First ID.

[0095] In some exemplary embodiments, if the first ID is the device ID of the second slave gateway, then at least one bit of the reserved field in the GEM frame header contains the first ID.

[0096] In some exemplary embodiments, if the first ID is the UNI Node ID of the first slave gateway, or if the first ID is the UNI Node ID of the second slave gateway, then one bit in the reserved field of the GEM frame header contains the first ID.

[0097] In some exemplary embodiments, the most significant bit of the reserved field contains the first ID.

[0098] In some exemplary embodiments, the first GEM frame further includes a second ID used to characterize whether the first GEM frame is a GEM frame for communication between ONUs or a GEM frame for communication between an ONU and an OLT.

[0099] In some exemplary embodiments, the GEM frame header of the first GEM frame further includes a second ID.

[0100] In some exemplary implementations, the reserved field in the GEM frame header further includes a second ID.

[0101] In some exemplary embodiments, the second ID occupies the bits in the reserved field excluding the bits occupied by the first ID.

[0102] In some exemplary embodiments, if the first ID is the UNI Node ID of the first slave gateway, or if the first ID is the UNI Node ID of the second slave gateway, the second ID occupies the remaining bits in the reserved field, excluding the most significant bit.

[0103] Step 401: If it is determined that the port ID in the first GEM frame is the port ID used for communication between ONUs, the first GEM frame is sent to all slave gateways.

[0104] In some exemplary embodiments, the step of determining that the port ID in the first GEM frame is the port ID used when communicating between ONUs includes the step of obtaining second configuration information that the port ID is the port ID in the first GEM frame, and the step of determining that the peer device ID in the second configuration information is not a special value.

[0105] In some exemplary embodiments, if the peer device ID in the second configuration information is determined to be a special value, the port ID in the first GEM frame is determined to be the port ID used when communicating between the ONU and the OLT.

[0106] In some exemplary embodiments, communication between any two slave gateways is associated with a single configuration piece, namely, a GEM Port Network CTP ME, which is linked to a T-CONT and a GEM IW TP ME.

[0107] In some exemplary cases, the GEM Port Network CTP ME includes the following attributes.

[0108] This is the Managed Entity ID, and this attribute is just one example of how to uniquely identify a GEM Port Network CTP ME.

[0109] This is the Port ID, and this attribute is used to indicate the Port ID of the GEM port associated with the GEM Port Network CTP ME.

[0110] This is a T-CONT pointer, and this attribute points to an instance of T-CONT.

[0111] This attribute, Direction, describes whether the GEM port is used for UNI-to-ANNI, ANI-to-UNI, bidirectional connections, or bidirectional UNI-to-UNI connections. For example, a value of 1 indicates that the GEM port is used for UNI-to-ANN connections, a value of 2 indicates that the GEM port is used for ANI-to-UNI connections, a value of 3 indicates that the GEM port is used for bidirectional connections, and a value of 4 indicates that the GEM port is used for bidirectional UNI-to-UNI connections.

[0112] This is the peer device ID, and this attribute is used to indicate the device ID of the other slave gateway with which it communicates. If this attribute value is a special value, it indicates that communication will take place between the ONU and the OLT.

[0113] Here, UNI-to-UNI is a new communication type added to the embodiments of the present invention, and represents communication between ONUs.

[0114] Here, the peer device ID is an attribute newly added to the embodiment of the present application.

[0115] In some exemplary embodiments, the GEM Port Network CTP ME further includes the associated port ID, which is used to describe the first port ID of the slave gateway to which the ONU communicating with it belongs.

[0116] In some exemplary cases, the GEM Port Network CTP ME further includes a UNI Node ID, which represents the two communicating terminals.

[0117] Here, the UNI Node ID is an attribute newly added to the embodiment of the present invention.

[0118] In some exemplary embodiments, the step of determining that the port ID in the first GEM frame is the port ID used when communicating between ONUs includes the step of determining that there exists third configuration information in which the port ID is the port ID in the first GEM frame and the peer device ID is the first ID in the first GEM frame.

[0119] In some exemplary embodiments, if it is determined that the third configuration information does not exist, the port ID in the first GEM frame is determined to be the port ID used when communicating between the ONU and the OLT.

[0120] In some exemplary embodiments, the step of determining that the port ID in the first GEM frame is a port ID used when communicating between optical network units includes the steps of obtaining a second ID in the first GEM frame and determining that the second ID is used to characterize the first GEM frame as a GEM frame used for communication between ONUs.

[0121] In some exemplary embodiments, if the values ​​of the first port IDs assigned to the slave gateways where two communicating ONUs reside are different, the steps include, before sending the first GEM frame, obtaining the first port ID of the second slave gateway, and replacing the port ID in the first GEM frame with the first port ID of the second slave gateway obtained and updated in the first GEM frame, and accordingly, sending the first GEM frame to all slave gateways includes sending the updated first GEM frame to all slave gateways.

[0122] In some exemplary embodiments, if the values ​​of the first port IDs assigned to the slave gateways where the two communicating ONUs reside are different, the first GEM frame may be sent directly, and it is not necessary to replace the port ID in the first GEM frame with the first GEM frame obtained and updated by the first port ID of the second slave gateway.

[0123] In some exemplary embodiments, the step of obtaining the first port ID of the second slave gateway includes the step of obtaining second configuration information, which states that the port ID is the port ID in the first GEM frame, and the step of obtaining the associated port ID in the second configuration information, which states that the associated port ID is the first port ID of the second slave gateway.

[0124] In some exemplary embodiments, the step of obtaining the first port ID of the second slave gateway includes the step of obtaining third configuration information in which the port ID is the port ID in the first GEM frame and the peer device ID is the first ID in the first GEM frame, and the step of obtaining the associated port ID in the third configuration information, in which the associated port ID is the first port ID of the second slave gateway.

[0125] In some exemplary embodiments, prior to the step of receiving a first GEM frame transmitted by a first slave gateway, the method further includes the step of receiving a retrieval request transmitted by the first slave gateway, the retrieval request being used to retrieve a first mapping relationship corresponding to the target media access control address, the first mapping relationship being a mapping relationship between the device ID of the slave gateway and the media access control address; and the step of retrieving a first mapping relationship corresponding to the target MAC address from a pre-stored set of first mapping relationships and transmitting the first mapping relationship corresponding to the target MAC address to the first slave gateway.

[0126] In some exemplary cases, the acquisition request includes the target MAC address.

[0127] In some exemplary embodiments, prior to the step of receiving an acquisition request transmitted by the first slave gateway, the method further includes the step of receiving a second mapping relationship shared by the first slave gateway or other slave gateways, and storing or updating the first mapping relationship with the second mapping relationship.

[0128] In some exemplary embodiments, the second mapping relationship is a mapping relationship between the MAC address of a terminal connected to the slave gateway, which is stored after the slave gateway has learned the MAC address of that terminal, and the device ID of another slave gateway.

[0129] In some exemplary embodiments, prior to the step of receiving a first GEM frame transmitted by a first slave gateway, the method further includes the step of receiving a second mapping relationship shared by the first slave gateway or other slave gateways, and transmitting the second mapping relationship to all slave gateways or other slave gateways except those sharing the second mapping relationship.

[0130] In some exemplary embodiments, the method further includes receiving a second GEM frame transmitted by a first slave gateway, determining that the port ID in the second GEM frame is for uplink broadcasting, and broadcasting the second GEM frame to the FTTH OLT and all slave gateways.

[0131] Figure 5 is a flowchart of a communication method applied to a third slave gateway provided in another embodiment of the present application.

[0132] In a third embodiment, referring to Figure 5, another embodiment of the present application provides a communication method applied to a third gateway, which includes the following steps.

[0133] Step 500: The main gateway receives the first GEM frame, which includes the port ID.

[0134] In some exemplary embodiments, as shown in Figure 3, the GEM frame includes a GEM frame header and a GEM frame payload region.

[0135] In some exemplary cases, the GEM frame header includes PLI, Key Index, Port ID, Options, LF, and HEC.

[0136] In some exemplary embodiments, the port ID may be the first port ID of the slave gateway, or the second port ID of the slave gateway. Here, the first port ID is the port ID used when communicating between ONUs, and the second port ID is the port ID used when communicating between the ONU and the OLT.

[0137] In some exemplary cases, LF is used to indicate whether or not it is the last fragment.

[0138] In some exemplary embodiments, the first GEM frame further includes a first ID.

[0139] In some exemplary embodiments, the first ID may be the UNI Node ID of the first slave gateway or the UNI Node ID of the second slave gateway. Here, the second slave gateway is a slave gateway connected to the second terminal, and the second terminal is the terminal to which the target MAC address in the Ethernet frame belongs.

[0140] In some exemplary embodiments, the first ID may be the device ID of the second slave gateway.

[0141] In some exemplary implementations, the UNI Node ID is used to identify two communicating terminals. For example, ONU1 is represented by 1 and ONU2 by 0, thus representing the two communicating ONUs as 0 and 1.

[0142] In some exemplary embodiments, the GEM frame header of the first GEM frame includes the port ID and the first ID.

[0143] In some exemplary embodiments, the Port ID field in the GEM frame header contains the Port ID, and the Reserved field in the GEM frame header contains the First ID.

[0144] In some exemplary embodiments, if the first ID is the device ID of the second slave gateway, then at least one bit of the reserved field in the GEM frame header contains the first ID.

[0145] In some exemplary implementations, if the first ID is the UNI Node ID of the first slave gateway, or if the first ID is the UNI Node ID of the second slave gateway, then one bit of the reserved field in the GEM frame header contains the first ID. For example, the most significant bit of the reserved field contains the first ID.

[0146] In some exemplary embodiments, the first GEM frame further includes a second ID used to characterize whether the first GEM frame is a GEM frame for communication between ONUs or a GEM frame for communication between an ONU and an OLT.

[0147] In some exemplary embodiments, the GEM frame header of the first GEM frame further includes a second ID.

[0148] In some exemplary implementations, the reserved field in the GEM frame header further includes a second ID.

[0149] In some exemplary embodiments, the second ID occupies the bits in the reserved field excluding the bits occupied by the first ID.

[0150] In some exemplary embodiments, if the first ID is the UNI Node ID of the first slave gateway, or if the first ID is the UNI Node ID of the second slave gateway, the second ID occupies the remaining bits in the reserved field, excluding the most significant bit.

[0151] Step 501: Based on the port ID and the first ID in the first GEM frame, it is determined whether or not to perform appropriate processing on the first GEM frame.

[0152] In some exemplary embodiments, the port ID in the first GEM frame is used to determine whether or not to perform appropriate processing on the first GEM frame, and the port ID in the first GEM frame is used to determine whether or not to perform appropriate processing on the first GEM frame, depending on whether or not the port ID in the first GEM frame is the first port ID of the third slave gateway.

[0153] In some exemplary embodiments, the step of determining whether to perform appropriate processing on the first GEM frame based on whether the port ID in the first GEM frame is the first port ID of the third slave gateway is: If the port ID in the first GEM frame is the first port ID of the third slave gateway, the step of deciding to perform appropriate processing on the first GEM frame, The process includes at least one of the following steps: determining that if the port ID in the first GEM frame is not the first port ID of the third slave gateway, then no appropriate processing is performed on the first GEM frame.

[0154] In some exemplary embodiments, the step of determining whether to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame includes the step of determining whether to perform appropriate processing on the first GEM frame based on whether there is fourth configuration information indicating that the associated port ID is the port ID in the first GEM frame.

[0155] In some exemplary embodiments, the step of determining whether to perform appropriate processing on the first GEM frame based on whether or not there is fourth configuration information that the associated port ID is the port ID in the first GEM frame is: If a fourth configuration information exists, the step of deciding to perform appropriate processing on the first GEM frame, The process includes at least one of the following steps: determining that if no fourth configuration information exists, no corresponding processing should be performed on the first GEM frame.

[0156] In some exemplary embodiments, the step of determining whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame includes the step of determining whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame.

[0157] In some exemplary embodiments, if the first ID is the UNI Node ID of the first slave gateway or the UNI Node ID of the second slave gateway, the step of determining whether to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame includes the step of determining whether to perform appropriate processing on the first GEM frame based on whether the port ID in the first GEM frame is the first port ID of the third slave gateway and whether the first ID in the first GEM frame is the UNI Node ID of the third slave gateway.

[0158] In some exemplary embodiments, if the first ID is the UNI Node ID of the first slave gateway, the step of determining whether to perform appropriate processing on the first GEM frame based on whether the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether the first ID in the first GEM frame is the UNI Node ID of the third slave gateway, is as follows: If the port ID in the first GEM frame is the first port ID of the third slave gateway, and the first ID in the first GEM frame is not the UNI Node ID of the third slave gateway, then it is decided to perform appropriate processing on the first GEM frame. The process includes at least one of the following steps: determining that no appropriate processing should be performed on the first GEM frame if the port ID in the first GEM frame is not the first port ID of the third slave gateway, or if the first ID in the first GEM frame is the UNI Node ID of the third slave gateway.

[0159] In some exemplary embodiments, if the first ID is the UNI Node ID of the second slave gateway, the step of determining whether to perform appropriate processing on the first GEM frame based on whether the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether the first ID in the first GEM frame is the UNI Node ID of the third slave gateway, is as follows: If the port ID in the first GEM frame is the first port ID of the third slave gateway, and the first ID in the first GEM frame is the UNI Node ID of the third slave gateway, then it is decided to perform appropriate processing on the first GEM frame. The process includes at least one of the following steps: determining that no appropriate processing should be performed on the first GEM frame if the port ID in the first GEM frame is not the first port ID of the third slave gateway, or if the first ID in the first GEM frame is not the UNI Node ID of the third slave gateway.

[0160] In some exemplary embodiments, when the first ID is the device ID of the second slave gateway, the step of determining whether to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame includes the step of determining whether to perform appropriate processing on the first GEM frame based on whether the port ID in the first GEM frame is the first port ID of the third slave gateway and whether the first ID in the first GEM frame is the device ID of the third slave gateway.

[0161] In some exemplary embodiments, the step of determining whether to perform appropriate processing on the first GEM frame based on whether the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether the first ID in the first GEM frame is the device ID of the third slave gateway, is as follows: If the port ID in the first GEM frame is the first port ID of the third slave gateway, and the first ID in the first GEM frame is the device ID of the third slave gateway, then it is decided to perform appropriate processing on the first GEM frame. The process includes at least one of the following steps: determining that no appropriate processing should be performed on the first GEM frame if the port ID in the first GEM frame is not the first port ID of the third slave gateway, or if the first ID in the first GEM frame is not the device ID of the third slave gateway.

[0162] In some exemplary embodiments, when the first ID is the device ID of the second slave gateway, the step of determining whether to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame includes the step of determining whether to perform appropriate processing on the first GEM frame based on whether there is fourth configuration information that the associated port ID is the port ID in the first GEM frame, and whether the first ID in the first GEM frame is the device ID of the third slave gateway.

[0163] In some exemplary embodiments, the step of determining whether to perform appropriate processing on the first GEM frame based on whether there is fourth configuration information that the associated port ID is the port ID in the first GEM frame, and whether the first ID in the first GEM frame is the device ID of the third slave gateway, is as follows: If a fourth configuration information exists and the first ID in the first GEM frame is the device ID of the third slave gateway, the step of deciding to perform appropriate processing on the first GEM frame, The process includes at least one of the following steps: determining that no corresponding processing is performed on the first GEM frame if the fourth configuration information does not exist or the first ID in the first GEM frame is not the device ID of the third slave gateway;

[0164] In some exemplary embodiments, the corresponding processing performed on the first GEM frame may be any processing performed after the first GEM frame has been received. For example, the first GEM frame may be analyzed to obtain an Ethernet frame.

[0165] In some exemplary embodiments, failing to perform appropriate processing on the first GEM frame includes discarding the first GEM frame.

[0166] In some exemplary embodiments, prior to the step of receiving a first GEM frame transmitted by a main gateway, the method further includes the step of receiving a retrieval request transmitted by a first slave gateway, wherein the retrieval request is used to retrieve a first mapping relationship corresponding to the target MAC address, the first mapping relationship being a mapping relationship between the device ID and MAC address of the slave gateway, the method retrieving a first mapping relationship corresponding to the target MAC address from a pre-stored set of first mapping relationships, and transmitting the first mapping relationship corresponding to the target MAC address to the first slave gateway.

[0167] In some exemplary embodiments, prior to the step of receiving a first GEM frame transmitted by the main gateway, the method further includes the step of receiving a second mapping relationship shared by the first slave gateway or other slave gateways, and saving or updating the first mapping relationship with respect to the second mapping relationship.

[0168] In some exemplary embodiments, the second mapping relationship is a mapping relationship between the MAC address of a terminal connected to the slave gateway, which is stored after the slave gateway has learned the MAC address of that terminal, and the device ID of another slave gateway.

[0169] In some exemplary embodiments, the method further includes the step of receiving a second GEM frame broadcast by the main gateway.

[0170] To more clearly illustrate the communication method of the embodiment of this application, the following will describe the specific implementation process of the communication method of the embodiment of this application with several specific examples. The examples listed are not used to limit the scope of protection of the embodiment of this application.

[0171] Example 1 This example describes the process of achieving communication between ONUs when, at the start of ONU interaction, the slave gateway has not learned the MAC address of the terminal connected to the slave gateway, and the slave gateway connected to the transmitting terminal cannot obtain the device ID of the receiving terminal's slave gateway.

[0172] The main gateway sends configuration information to each slave gateway via GEM Port Network CTP ME. The port ID in the configuration information is the port ID for uplink broadcasting, and the communication type in the configuration information is UNI-to-ANI, meaning the value of the direction attribute is 1.

[0173] When the slave gateway receives an Ethernet frame transmitted by a terminal connected to the slave gateway, it packages the Ethernet frame into the payload area of ​​the second GEM frame, packages the slave gateway's uplink broadcast port ID into the port ID field of the GEM frame header of the second GEM frame, and sends the second GEM frame to the main gateway.

[0174] The main gateway receives the second GEM frame, determines that the port ID in the second GEM frame is for uplink broadcasting, and broadcasts the second GEM frame to the FTTH OLT and all slave gateways.

[0175] The slave gateway receives the second GEM frame.

[0176] Example 2 This example describes the process by which a slave gateway learns the MAC address of a terminal connected to it and shares the mapping relationship between the MAC address and the slave gateway's device ID with the main gateway.

[0177] Let's assume that the main gateway is connected to three slave gateways: slave gateway 1, slave gateway 2, and slave gateway 3. Slave gateway 1 is connected to two terminals: terminal 1 and terminal 2. Slave gateway 2 is connected to three terminals: terminal 3, terminal 4, and terminal 5. Slave gateway 3 is connected to two terminals: terminal 6 and terminal 7.

[0178] After terminals 1 and 2 access slave gateway 1, the MAC address of terminal 1 learned by slave gateway 1 is MAC address 1, and the MAC address of terminal 2 learned by slave gateway 1 is MAC address 2. Slave gateway 1 locally stores the mapping relationship between MAC address 1 and its device ID, and the mapping relationship between MAC address 2 and its device ID, and shares the stored mapping relationships with the main gateway as a second mapping relationship. The main gateway then stores or updates its local first mapping relationship based on the second mapping relationship shared by slave gateway 1.

[0179] After terminals 3, 4, and 5 access slave gateway 2, the MAC address of terminal 3 learned by slave gateway 2 is MAC address 3, the MAC address of terminal 4 learned by slave gateway 2 is MAC address 4, and the MAC address of terminal 5 learned by slave gateway 2 is MAC address 5. Slave gateway 2 locally stores the mapping relationships between MAC address 3 and its device ID, the mapping relationships between MAC address 4 and its device ID, and the mapping relationships between MAC address 5 and its device ID. It shares these stored mapping relationships with the main gateway as second mapping relationships, and the main gateway stores or updates its local first mapping relationships based on the second mapping relationships shared by slave gateway 2.

[0180] After terminals 6 and 7 access slave gateway 3, the MAC address of terminal 6 learned by slave gateway 3 is MAC address 6, and the MAC address of terminal 7 learned by slave gateway 3 is MAC address 7. Slave gateway 3 locally stores the mapping relationship between MAC address 6 and its device ID, and the mapping relationship between MAC address 7 and its device ID. It shares the stored mapping relationships with the main gateway as a second mapping relationship, and the main gateway stores or updates its local first mapping relationship based on the second mapping relationship shared by slave gateway 3.

[0181] Example 3 In this example, a first port ID is assigned to FTTR ONU1 and FTTR ONU2, which communicate with each other. The communication process between ONU1 and ONU2 is described when the value of the first port ID assigned to ONU1 is the same as the value of the first port ID assigned to ONU2.

[0182] In this example, the first port ID is the port ID used when communicating between ONUs. The value of the first port ID of ONU1 is different from the value of the second port ID of ONU1, and the value of the first port ID of ONU2 is different from the value of the second port ID of ONU2. The second port ID is the port ID used when communicating between the ONU and the OLT.

[0183] In this example, the main gateway sends configuration information to slave gateway 1 where ONU1 resides via GEM Port Network CTP ME. In the configuration information, the port ID is Port-ID1, which is the assigned first port ID. The communication type is ONU-to-ONU or UNI-to-UNI, meaning the value of the direction attribute is 4, the UNI Node ID is 0, and the peer device ID is the device ID of slave gateway 2 where ONU2 resides.

[0184] In this example, the main gateway sends configuration information to slave gateway 2 where ONU2 resides via GEM Port Network CTP ME. In the configuration information, the port ID is Port-ID1, which is the assigned first port ID. The communication type is ONU-to-ONU or UNI-to-UNI, meaning the value of the direction attribute is 4, the UNI Node ID is 1, and the peer device ID is the device ID of slave gateway 1 where ONU1 resides.

[0185] The process by which ONU1 initiates communication with ONU2 includes the following points:

[0186] The slave gateway 1, where ONU1 resides, receives Ethernet frames transmitted by terminal 1.

[0187] Slave gateway 1 sends a GET request to the main gateway, where the GET request includes the target MAC address in the Ethernet frame.

[0188] The main gateway searches for the first mapping relationship corresponding to the target MAC address in the pre-stored first mapping relationships and sends the first mapping relationship corresponding to the target MAC address to the slave gateway 1.

[0189] Slave Gateway 1 receives the first mapping relationship corresponding to the target MAC address transmitted by the main gateway, and obtains the device ID in the first mapping relationship corresponding to the target MAC address as the device ID for Slave Gateway 2.

[0190] Slave Gateway 1 obtains Port-ID1, which is the port ID in the configuration information where the peer device ID is the device ID of Slave Gateway 2, and sets it as the first port ID of Slave Gateway 1. It also obtains the UNI Node ID in the configuration information where the peer device ID is the device ID of Slave Gateway 2.

[0191] Slave Gateway 1 packages the Ethernet frame into the payload area of ​​the first GEM frame, packages the first port ID of Slave Gateway 1 into the port ID field in the GEM frame header of the first GEM frame, packages the UNI Node ID into the most significant bit in the Option field in the GEM frame header of the first GEM frame, and sends the packaged first GEM frame to the main gateway.

[0192] The main gateway receives the first GEM frame, obtains configuration information that the port ID is the port ID in the first GEM frame, determines that the peer device ID in the obtained configuration information is not a special value, identifies the port ID in the first GEM frame as the port ID used when communicating between ONUs, and broadcasts the first GEM frame to all slave gateways.

[0193] Slave Gateway 2 receives the first GEM frame. If the port ID in the first GEM frame is the first port ID of Slave Gateway 2, and the UNI Node ID in the first GEM frame is not the UNI Node ID of Slave Gateway 2, Slave Gateway 2 receives the first GEM frame, parses the first GEM frame to obtain an Ethernet frame, and sends the Ethernet frame to Terminal 2.

[0194] Example 4 In this example, we will describe the communication process between ONU1 and ONU2 when FTTR ONU1 and FTTR ONU2, which communicate with each other, are each assigned a first port ID, and the value of the first port ID assigned to ONU1 is not the same as the value of the first port ID assigned to ONU2.

[0195] In this example, the first port ID is the port ID used when communicating between ONUs. The value of the first port ID of ONU1 is different from the value of the second port ID of ONU1, and the value of the first port ID of ONU2 is different from the value of the second port ID of ONU2. The second port ID is the port ID used when communicating between the ONU and the OLT.

[0196] In this example, the main gateway sends configuration information to slave gateway 1 where ONU1 resides via GEM Port Network CTP ME. In the configuration information, the port ID is Port-ID1, which is the assigned first port ID. The communication type is ONU-to-ONU or UNI-to-UNI, meaning the value of the direction attribute is 4. The peer device ID is the device ID of slave gateway 2 where ONU2 resides, and the associated port ID is Port-ID2, which is the first port ID assigned by slave gateway 2 where ONU2 resides.

[0197] In this example, the main gateway sends configuration information to slave gateway 2 where ONU2 resides via GEM Port Network CTP ME. The port ID in the configuration information is Port-ID2, which is the assigned first port ID. The communication type is ONU-to-ONU or UNI-to-UNI, meaning the value of the direction attribute is 4. The peer device ID is the device ID of slave gateway 1 where ONU1 resides, and the associated port ID is Port-ID1, which is the first port ID assigned by slave gateway 1 where ONU1 resides.

[0198] The process by which ONU1 initiates communication with ONU2 includes the following points:

[0199] The slave gateway 1, where ONU1 resides, receives Ethernet frames transmitted by terminal 1.

[0200] Slave gateway 1 sends a GET request to the main gateway, where the GET request includes the target MAC address in the Ethernet frame.

[0201] The main gateway searches for the first mapping relationship corresponding to the target MAC address in the pre-stored first mapping relationships and sends the first mapping relationship corresponding to the target MAC address to the slave gateway 1.

[0202] Slave Gateway 1 receives the first mapping relationship corresponding to the target MAC address transmitted by the main gateway, and obtains the device ID in the first mapping relationship corresponding to the target MAC address as the device ID for Slave Gateway 2.

[0203] Slave Gateway 1 obtains Port-ID1, which is the port ID in the configuration information where the peer device ID is the device ID of Slave Gateway 2, and sets it as the first port ID of Slave Gateway 1.

[0204] Slave Gateway 1 packages the Ethernet frame into the payload area of ​​the first GEM frame, packages the first port ID of Slave Gateway 1 into the port ID field in the GEM frame header of the first GEM frame, packages the device ID of Slave Gateway 2 as the first ID into the Option field in the GEM frame header of the first GEM frame, and sends the packaged first GEM frame to the main gateway.

[0205] The main gateway receives the first GEM frame and determines that configuration information exists in which the port ID is the port ID in the first GEM frame and the peer device ID is the device ID of slave gateway 2. It then identifies the port ID in the first GEM frame as the port ID used when communicating between ONUs.

[0206] The main gateway obtains the relevant port ID from the configuration information, where the port ID is the port ID in the first GEM frame and the peer device ID is the device ID of slave gateway 2, as Port-ID2 of the first port ID of slave gateway 2. The main gateway then replaces the port ID in the first GEM frame with Port-ID2 of the first port ID of slave gateway 2 to obtain an updated first GEM frame, and broadcasts the updated first GEM frame to all slave gateways.

[0207] Slave Gateway 2 receives the updated first GEM frame. If the port ID in the updated first GEM frame is the first port ID of Slave Gateway 2, and the first ID in the first GEM frame is the device ID of Slave Gateway 2, Slave Gateway 2 receives the updated first GEM frame, analyzes the updated first GEM frame to obtain an Ethernet frame, and sends the Ethernet frame to Terminal 2.

[0208] Example 5 In this example, we will describe the communication process between ONU1 and ONU2 when FTTR ONU1 and FTTR ONU2, which communicate with each other, are each assigned a first port ID, and the value of the first port ID assigned to ONU1 is not the same as the value of the first port ID assigned to ONU2.

[0209] In this example, the first port ID is the port ID used when communicating between ONUs. The value of the first port ID of ONU1 is different from the value of the second port ID of ONU1, and the value of the first port ID of ONU2 is different from the value of the second port ID of ONU2. The second port ID is the port ID used when communicating between the ONU and the OLT.

[0210] In this example, the main gateway sends configuration information to slave gateway 1 where ONU1 resides via GEM Port Network CTP ME. In the configuration information, the port ID is Port-ID1, which is the assigned first port ID. The communication type is ONU-to-ONU or UNI-to-UNI, meaning the value of the direction attribute is 4. The peer device ID is the device ID of slave gateway 2 where ONU2 resides, and the associated port ID is Port-ID2, which is the first port ID assigned by slave gateway 2 where ONU2 resides.

[0211] In this example, the main gateway sends configuration information to slave gateway 2 where ONU2 resides via GEM Port Network CTP ME. The port ID in the configuration information is Port-ID2, which is the assigned first port ID. The communication type is ONU-to-ONU or UNI-to-UNI, meaning the value of the direction attribute is 4. The peer device ID is the device ID of slave gateway 1 where ONU1 resides, and the associated port ID is Port-ID1, which is the first port ID assigned by slave gateway 1 where ONU1 resides.

[0212] The process by which ONU1 initiates communication with ONU2 includes the following points:

[0213] The slave gateway 1, where ONU1 resides, receives Ethernet frames transmitted by terminal 1.

[0214] Slave gateway 1 sends a GET request to the main gateway, where the GET request includes the target MAC address in the Ethernet frame.

[0215] The main gateway searches for the first mapping relationship corresponding to the target MAC address in the pre-stored first mapping relationships and sends the first mapping relationship corresponding to the target MAC address to the slave gateway 1.

[0216] Slave Gateway 1 receives the first mapping relationship corresponding to the target MAC address transmitted by the main gateway, and obtains the device ID in the first mapping relationship corresponding to the target MAC address as the device ID for Slave Gateway 2.

[0217] Slave Gateway 1 obtains Port-ID1, which is the port ID in the configuration information where the peer device ID is the device ID of Slave Gateway 2, and sets it as the first port ID of Slave Gateway 1.

[0218] Slave Gateway 1 packages the Ethernet frame into the payload area of ​​the first GEM frame, packages the first port ID of Slave Gateway 1 into the port ID field in the GEM frame header of the first GEM frame, packages the device ID of Slave Gateway 2 as the first ID into the Option field in the GEM frame header of the first GEM frame, and sends the packaged first GEM frame to the main gateway.

[0219] The main gateway receives the first GEM frame, determines that the port ID is the port ID in the first GEM frame, and that configuration information exists indicating that the peer device ID is the device ID of slave gateway 2. It identifies the port ID in the first GEM frame as the port ID used for communication between ONUs and broadcasts the first GEM frame to all slave gateways.

[0220] Slave Gateway 2 receives the first GEM frame. If the port ID in the first GEM frame is the first port ID of Slave Gateway 2, and the first ID in the first GEM frame is the device ID of Slave Gateway 2, Slave Gateway 2 receives the first GEM frame, parses the first GEM frame to obtain an Ethernet frame, and sends the Ethernet frame to Terminal 2.

[0221] Example 6 In this example, we will describe the communication process between ONU1 and ONU2 when FTTR ONU1 and FTTR ONU2, which communicate with each other, are each assigned a first port ID, and the value of the first port ID assigned to ONU1 is not the same as the value of the first port ID assigned to ONU2.

[0222] In this example, the first port ID is the port ID used when communicating between ONUs. The value of the first port ID of ONU1 is the same as the value of the second port ID of ONU1, the value of the first port ID of ONU2 is the same as the value of the second port ID of ONU2, and the second port ID is the port ID used when communicating between the ONU and the OLT.

[0223] In this example, the main gateway sends configuration information to slave gateway 1 where ONU1 resides via GEM Port Network CTP ME. In the configuration information, the port ID is Port-ID1, which is the assigned first port ID. The communication type is ONU-to-ONU or UNI-to-UNI, meaning the value of the direction attribute is 4. The peer device ID is the device ID of slave gateway 2 where ONU2 resides, and the associated port ID is Port-ID2, which is the first port ID assigned by slave gateway 2 where ONU2 resides.

[0224] In this example, the main gateway sends configuration information to slave gateway 2 where ONU2 resides via GEM Port Network CTP ME. The port ID in the configuration information is Port-ID2, which is the assigned first port ID. The communication type is ONU-to-ONU or UNI-to-UNI, meaning the value of the direction attribute is 4. The peer device ID is the device ID of slave gateway 1 where ONU1 resides, and the associated port ID is Port-ID1, which is the first port ID assigned by slave gateway 1 where ONU1 resides.

[0225] The process by which ONU1 initiates communication with ONU2 includes the following points:

[0226] The slave gateway 1, where ONU1 resides, receives Ethernet frames transmitted by terminal 1.

[0227] Slave gateway 1 sends a GET request to the main gateway, where the GET request includes the target MAC address in the Ethernet frame.

[0228] The main gateway searches for the first mapping relationship corresponding to the target MAC address in the pre-stored first mapping relationships and sends the first mapping relationship corresponding to the target MAC address to the slave gateway 1.

[0229] Slave Gateway 1 receives the first mapping relationship corresponding to the target MAC address transmitted by the main gateway, and obtains the device ID in the first mapping relationship corresponding to the target MAC address as the device ID for Slave Gateway 2.

[0230] Slave Gateway 1 obtains Port-ID1, which is the port ID in the configuration information where the peer device ID is the device ID of Slave Gateway 2, and sets it as the first port ID of Slave Gateway 1.

[0231] Slave Gateway 1 packages the Ethernet frame into the payload area of ​​the first GEM frame, packages the first port ID of Slave Gateway 1 into the port ID field in the GEM frame header of the first GEM frame, packages the device ID of Slave Gateway 2 as the first ID into the Option field in the GEM frame header of the first GEM frame, packages the second ID into the second most significant bit in the Option field in the frame header of the first GEM frame, and sends the packaged first GEM frame to the main gateway. Here, the value of the second ID is 1 and is used to characterize the first GEM frame as communication between ONUs.

[0232] The main gateway receives the first GEM frame, obtains the second ID in the first GEM frame, determines that the second ID is used to characterize the first GEM frame as a GEM frame used for communication between ONUs, and identifies the port ID in the first GEM frame as the port ID used when communicating between ONUs.

[0233] The main gateway obtains the relevant port ID from the configuration information, where the port ID is the port ID in the first GEM frame and the peer device ID is the device ID of slave gateway 2, as Port-ID2 of the first port ID of slave gateway 2. The main gateway then replaces the port ID in the first GEM frame with Port-ID2 of the first port ID of slave gateway 2 to obtain an updated first GEM frame, and broadcasts the updated first GEM frame to all slave gateways.

[0234] Slave Gateway 2 receives the updated first GEM frame. If the port ID in the updated first GEM frame is the first port ID of Slave Gateway 2, and the first ID in the first GEM frame is the device ID of Slave Gateway 2, Slave Gateway 2 receives the updated first GEM frame, analyzes the updated first GEM frame to obtain an Ethernet frame, and sends the Ethernet frame to Terminal 2.

[0235] In a fourth embodiment, another embodiment of the present application provides an electronic device including at least one processor and a memory that stores at least one program and causes the at least one processor to implement any one of the above-described communication methods when at least one program is executed by the at least one processor.

[0236] Here, a processor is a device having data processing capabilities, including but not limited to a central processor (CPU). Memory is a device having data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH).

[0237] In some embodiments, the processor and memory are interconnected via a bus and further connected to other components of the computing device.

[0238] In a fifth embodiment, another embodiment of the present application provides a computer-readable medium on which a computer program is stored and which causes a processor to implement any one of the above-described communication methods when the computer program is executed by the processor.

[0239] Figure 6 is a block diagram of a communication system provided by another embodiment of the present application.

[0240] In a sixth embodiment, referring to Figure 6, another embodiment of the present application includes a first slave gateway 601, a main gateway 602, and a third slave gateway 603, wherein the first slave gateway 601 is used to receive Ethernet frames transmitted by a first terminal, packages the first port ID of the first slave gateway and the Ethernet frame as a first Gigabit Passive Optical Network Package Mode GEM frame, transmits the first GEM frame to the main gateway, the first port ID is a port ID used when communicating between optical network units, and the main gateway 602 transmits the first gateway The system provides a communication system in which a third slave gateway 603 is used to receive a first GEM frame, the first GEM frame includes a port ID and a first ID, and if it is determined that the port ID in the first GEM frame is the port ID used when communicating between optical network units, it sends the first GEM frame to all slave gateways, and the third slave gateway 603 is used to receive the first GEM frame sent by the main gateway, the first GEM frame includes a port ID and a first ID, and the third slave gateway 603 determines whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame.

[0241] In some exemplary embodiments, the step of packaging the first port ID of the first slave gateway and an Ethernet frame as a first Gigabit Passive Optical Network Package Mode GEM frame includes the step of packaging the first port ID of the first slave gateway, the first ID, and the Ethernet frame as a first GEM frame.

[0242] In some exemplary embodiments, the first ID is the user network interface node ID of the first slave gateway, or the first ID is the user network interface node ID of the second slave gateway, the second slave gateway is a slave gateway connected to the second terminal, and the second terminal is the terminal to which the target media access control address in the Ethernet frame belongs.

[0243] In some exemplary embodiments, the first slave gateway 601 is further used to obtain the first port ID and first ID of the first slave gateway.

[0244] In some exemplary embodiments, the first slave gateway 601 is specifically used to obtain the first port ID and first ID of the first slave gateway by employing a method that involves obtaining the device ID of the second slave gateway using the target media access control address in the Ethernet frame, and obtaining the first port ID and first ID of the first slave gateway using the device ID of the second slave gateway.

[0245] In some exemplary embodiments, the first slave gateway 601 is specifically used to obtain the device ID of the second slave gateway by the target media access control address in the Ethernet frame by employing a method in which the first slave gateway 601 searches for the device ID corresponding to the target media access control address in a first mapping relationship between the device ID of the slave gateway and the media access control address that has been stored in advance, and the device ID found is the device ID of the second slave gateway.

[0246] In some exemplary embodiments, the first slave gateway 601 is further used to acquire a second mapping relationship shared by other slave gateways and to store or update the first mapping relationship using the second mapping relationship.

[0247] In some exemplary embodiments, the first slave gateway 601 is specifically used to obtain the device ID of the second slave gateway by the target media access control address in the Ethernet frame by employing a method that includes the steps of: sending an acquisition request to the main gateway, the acquisition request being used to acquire a first mapping relationship corresponding to the target media access control address, the first mapping relationship being a mapping relationship between the device ID of the slave gateway and the media access control address; and receiving the first mapping relationship corresponding to the target media access control address transmitted from the main gateway and obtaining the device ID in the first mapping relationship corresponding to the target media access control address.

[0248] The main gateway 602 is further used to receive an acquisition request sent by the first slave gateway, retrieve the first mapping relationship corresponding to the target media access control address from the pre-stored first mapping relationships, and send the first mapping relationship corresponding to the target media access control address to the first slave gateway.

[0249] In some exemplary embodiments, the first slave gateway 601 employs a method that includes the steps of: sending an acquisition request to another gateway, the acquisition request being used to acquire a first mapping relationship corresponding to the target media access control address, the first mapping relationship being a mapping relationship between the device ID of the slave gateway and the media access control address; and receiving the first mapping relationship corresponding to the target media access control address transmitted from the other gateway and acquiring the device ID in the first mapping relationship corresponding to the target media access control address, thereby specifically achieving the acquisition of the device ID of the second slave gateway by the target media access control address in the Ethernet frame.

[0250] The third slave gateway 603 is further used to receive an acquisition request transmitted by the first slave gateway, retrieve the first mapping relationship corresponding to the target media access control address from the first mapping relationships stored in advance, and transmit the first mapping relationship corresponding to the target media access control address to the first slave gateway.

[0251] In some exemplary embodiments, the first slave gateway 601 is specifically used to obtain the first port ID and first ID of the first slave gateway using the device ID of the second slave gateway by employing a method that includes the steps of: obtaining first configuration information that the peer device ID is the device ID of the second slave gateway; obtaining the port ID in the first configuration information as the first port ID of the first slave gateway; and, if the first ID is the user network interface node ID of the first slave gateway, obtaining the user network interface node ID in the first configuration information; and if the first ID is the user network interface node ID of the second slave gateway, obtaining the first ID using the user network interface node ID in the first configuration information.

[0252] In some exemplary embodiments, the first ID is the device ID of the second slave gateway, the second slave gateway is a slave gateway connected to the second terminal, and the second terminal is the terminal to which the target media access control address in the Ethernet frame belongs.

[0253] In some exemplary embodiments, the first slave gateway 601 is further used to obtain the device ID of the second slave gateway by the target media access control address and to obtain the first port ID of the first slave gateway by the device ID of the second slave gateway.

[0254] In some exemplary embodiments, the first slave gateway 601 is specifically used to package the first port ID of the first slave gateway, the first ID, and the Ethernet frame as a first Gigabit Passive Optical Network Package Mode GEM frame by employing a method that involves packaging the Ethernet frame into the payload area of ​​the first GEM frame and packaging the first port ID and first ID of the first slave gateway into the GEM frame header of the first GEM frame.

[0255] In some exemplary embodiments, the first slave gateway 601 is specifically used to package the first port ID of the first slave gateway and the first ID into the GEM frame header of the first GEM frame by employing a method that involves packaging the first port ID of the first slave gateway into the port ID field in the GEM frame header and packaging the first ID into the reserved field in the GEM frame header.

[0256] In some exemplary embodiments, the first slave gateway 601 is specifically used to package the first ID into the reserved field in the GEM frame header by employing a method of packaging the first ID into any one bit in the reserved field.

[0257] In some exemplary embodiments, the first slave gateway 601 is specifically used to package the first ID into any one bit in the reserved field by employing a method of packaging the first ID into the most significant bit in the reserved field.

[0258] In some exemplary embodiments, the first slave gateway 601 is specifically used to package the first port ID, first ID, and second ID of the first slave gateway into the GEM frame header of the first GEM frame, wherein the second ID is used to characterize whether the first GEM frame is a GEM frame for communication between optical network units or a GEM frame for communication between an optical network unit and an optical line terminal.

[0259] In some exemplary embodiments, the first slave gateway 601 is specifically used to package the first port ID, first ID, and second ID of the first slave gateway into the GEM frame header of the first GEM frame by employing a method that involves packaging the first port ID of the first slave gateway into the port ID field in the GEM frame header, and packaging the first ID and second ID into the reserved field in the GEM frame header.

[0260] In some exemplary embodiments, the main gateway 602 is specifically used to determine that the port ID in the first GEM frame is the port ID used when communicating between optical network units, by employing a method that involves the steps of obtaining second configuration information that the port ID is the port ID in the first GEM frame, and determining that the peer device ID in the second configuration information is not a special value.

[0261] In some exemplary embodiments, the main gateway 602 employs a method that involves determining that there exists third configuration information, namely that the port ID is the port ID in the first GEM frame and the peer device ID is the first ID in the first GEM frame, thereby specifically enabling the determination that the port ID in the first GEM frame is the port ID used when communicating between optical network units.

[0262] In some exemplary embodiments, the first GEM frame further includes a second ID used to characterize whether the first GEM frame is a GEM frame for communication between optical network units or a GEM frame for communication between an optical network unit and an optical line terminal, and the main gateway 602 is specifically used to determine that the port ID in the first GEM frame is a port ID used when communicating between optical network units by employing a method that includes the steps of obtaining the second ID and determining that the preset ID is used to characterize the first GEM frame as a GEM frame for communication between optical network units.

[0263] In some exemplary embodiments, the main gateway 602 is further used to obtain the first port ID of the second slave gateway, replace the port ID in the first GEM frame with the first GEM frame obtained and updated by the first port ID of the second slave gateway, and transmit the updated first GEM frame.

[0264] In some exemplary embodiments, the main gateway 602 is specifically used to obtain the first port ID of the second slave gateway by employing a method that includes the steps of obtaining second configuration information, which is that the port ID is the port ID in the first GEM frame, and obtaining the associated port ID in the second configuration information, wherein the associated port ID is the first port ID of the second slave gateway.

[0265] In some exemplary embodiments, the third slave gateway 603 is specifically used to determine whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame, by employing a method that involves determining whether or not to perform appropriate processing on the first GEM frame based on whether or not the port ID in the first GEM frame is the first port ID of the third slave gateway.

[0266] In some exemplary embodiments, the third slave gateway 603 determines to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is the first port ID of the third slave gateway, This method is specifically used to determine whether or not to perform appropriate processing on the first GEM frame, depending on whether or not the port ID in the first GEM frame is the first port ID of the third slave gateway, by employing at least one of the following steps: determining whether or not to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is not the first port ID of the third slave gateway.

[0267] In some exemplary embodiments, the third slave gateway 603 is specifically used to determine whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame, by employing a method that involves determining whether or not to perform appropriate processing on the first GEM frame based on whether or not there is fourth configuration information that the associated port ID is the port ID in the first GEM frame.

[0268] In some exemplary embodiments, the third slave gateway 603 determines that if the fourth configuration information exists, it will perform the appropriate processing on the first GEM frame. This method employs at least one of the following steps: if the fourth configuration information does not exist, it is decided not to perform the appropriate processing on the first GEM frame; and it is specifically used to determine whether or not to perform the appropriate processing on the first GEM frame based on whether or not the fourth configuration information exists, which is that the associated port ID is the port ID in the first GEM frame.

[0269] In some exemplary embodiments, the third slave gateway 603 is specifically used to determine whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame, thereby enabling the determination of whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame.

[0270] In some exemplary embodiments, the third slave gateway 603 employs a method that involves determining whether or not to perform appropriate processing on the first GEM frame based on whether the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether or not the first ID in the first GEM frame is the user network interface node ID of the third slave gateway. This method is specifically used to realize the determination of whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame.

[0271] In some exemplary embodiments, the third slave gateway 603 determines to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is the first port ID of the third slave gateway and the first ID in the first GEM frame is not the user network interface node ID of the third slave gateway. This method is specifically used to determine whether or not to perform appropriate processing on the first GEM frame, based on whether or not the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether or not the first ID in the first GEM frame is the user network interface node ID of the third slave gateway, by employing at least one of the following methods: the step of deciding not to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is not the first port ID of the third slave gateway, or if the first ID in the first GEM frame is the user network interface node ID of the third slave gateway.

[0272] In some exemplary embodiments, the third slave gateway 603 employs a method that involves determining whether or not to perform appropriate processing on the first GEM frame based on whether the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether or not the first ID in the first GEM frame is the device ID of the third slave gateway. This method is specifically used to determine whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame.

[0273] In some exemplary embodiments, the third slave gateway 603 determines to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is the first port ID of the third slave gateway and the first ID in the first GEM frame is the device ID of the third slave gateway. This method is specifically used to determine whether or not to perform appropriate processing on the first GEM frame, based on whether or not the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether or not the first ID in the first GEM frame is the device ID of the third slave gateway, by employing at least one of the following methods: the step of deciding to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is not the first port ID of the third slave gateway, or if the first ID in the first GEM frame is not the device ID of the third slave gateway.

[0274] In some exemplary embodiments, the third slave gateway 603 determines to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is the first port ID of the third slave gateway and the first ID in the first GEM frame is the user network interface node ID of the third slave gateway. This method is specifically used to determine whether or not to perform appropriate processing on the first GEM frame, based on whether or not the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether or not the first ID in the first GEM frame is the device ID of the third slave gateway, by employing at least one of the following steps: deciding not to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is not the first port ID of the third slave gateway, or deciding not to perform appropriate processing on the first GEM frame if the first ID in the first GEM frame is not the user network interface node ID of the third slave gateway.

[0275] In some exemplary embodiments, the third slave gateway 603 employs a method that involves determining whether or not to perform appropriate processing on the first GEM frame based on whether or not there is fourth configuration information that the associated port ID is the port ID in the first GEM frame, and whether or not the first ID in the first GEM frame is the device ID of the third slave gateway. This method is specifically used to realize the determination of whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame.

[0276] The specific implementation process of the above communication system is the same as the specific implementation process of the communication method in the above-described embodiment, and will not be explained further here.

[0277] Those skilled in the art will understand that all or some steps, systems, and devices of the methods disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware embodiments, the distinctions between the functional modules / units described above do not necessarily correspond to distinctions between physical components; for example, one physical component may have multiple functions, and one function or step may be performed collaboratively by multiple physical components. Some or all physical components can be implemented as software executed by a processor such as a central processor, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit such as a dedicated integrated circuit. Such software can be distributed on computer-readable media, which may include computer storage media (or non-temporary media) and communication media (or temporary media). As is well known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technique for storing information (e.g., computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital multifunction disk (DVD) or other optical disk memory, magnetic cassette, magnetic tape, magnetic disk memory or other magnetic memory, or any other media used to store desired information and accessible by a computer. Furthermore, a person skilled in the art will know that communication media generally include computer-readable instructions, data structures, program modules or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information distribution media.

[0278] This specification discloses exemplary embodiments and uses specific terminology, which should be used and interpreted only in a general illustrative sense and not as limiting. In some examples, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in combination in certain embodiments may be used alone or in combination with other features, characteristics, and / or elements described in combination in other embodiments, unless otherwise specified. Thus, those skilled in the art will understand that various forms and detailed modifications are possible, as long as they do not deviate from the scope of this disclosure as set forth by the appended claims.

Claims

1. A communication method applicable to the first slave gateway, The steps include receiving an Ethernet frame transmitted by the first terminal, The process includes the steps of packaging the first port ID of the first slave gateway and the Ethernet frame as a first Gigabit Passive Optical Network Package Mode GEM frame, and transmitting the first GEM frame to the main gateway. A communication method in which the first port ID is a port ID used when communicating between optical network units.

2. The step of packaging the first port ID of the first slave gateway and the Ethernet frame as a first Gigabit Passive Optical Network Package Mode GEM frame is: The communication method according to claim 1, comprising the step of packaging the first port ID of the first slave gateway, the first ID, and the Ethernet frame as a first GEM frame.

3. The first ID is the user network interface node ID of the first slave gateway. Alternatively, the communication method according to claim 2, wherein the first ID is the user network interface node ID of the second slave gateway, the second slave gateway is a slave gateway connected to the second terminal, and the second terminal is the terminal to which the target media access control address in the Ethernet frame belongs.

4. After the step of receiving an Ethernet frame transmitted by the first terminal, and before the step of packaging the first port ID of the first slave gateway, the first ID, and the Ethernet frame as a first GEM frame, The communication method according to claim 3, further comprising the step of obtaining the first port ID and first ID of the first slave gateway.

5. The step of obtaining the first port ID and first ID of the first slave gateway is: A step of obtaining the device ID of the second slave gateway using the target media access control address, wherein the second slave gateway is a slave gateway connected to the second terminal, The communication method according to claim 4, comprising the step of obtaining the first port ID and first ID of the first slave gateway using the device ID of the second slave gateway.

6. The step of obtaining the device ID of the second slave gateway using the target media access control address is as follows: The communication method according to claim 5, comprising the step of searching for a device ID corresponding to the target media access control address in a first mapping relationship between a device ID of a slave gateway and a media access control address that has been stored in advance, and the device ID found is the device ID of the second slave gateway.

7. The communication method according to claim 6, further comprising the step of obtaining a second mapping relationship shared by another slave gateway, and storing or updating the first mapping relationship using the second mapping relationship, prior to the step of searching for a device ID corresponding to the target media access control address.

8. The step of obtaining the device ID of the second slave gateway using the target media access control address in the Ethernet frame is as follows: A step of sending an acquisition request to the main gateway, wherein the acquisition request is used to acquire a first mapping relationship corresponding to the target media access control address, and the first mapping relationship is a mapping relationship between the device ID of the slave gateway and the media access control address. The communication method according to claim 5, comprising the steps of receiving a first mapping relationship corresponding to the target media access control address transmitted from the main gateway and obtaining a device ID in the first mapping relationship corresponding to the target media access control address.

9. The step of obtaining the device ID of the second slave gateway using the target media access control address in the Ethernet frame is as follows: A step of sending an acquisition request to another gateway, wherein the acquisition request is used to acquire a first mapping relationship corresponding to the target media access control address, and the first mapping relationship is a mapping relationship between the device ID of the slave gateway and the media access control address. The communication method according to claim 5, comprising the steps of receiving a first mapping relationship corresponding to the target media access control address transmitted from the other gateway and obtaining a device ID in the first mapping relationship corresponding to the target media access control address.

10. The step of obtaining the first port ID and first ID of the first slave gateway using the device ID of the second slave gateway is as follows: A step of obtaining first configuration information that the peer device ID is the device ID of the second slave gateway, The steps include obtaining the port ID in the first configuration information as the first port ID of the first slave gateway, The communication method according to claim 5, comprising the steps of: obtaining the user network interface node ID in the first configuration information if the first ID is the user network interface node ID of the first slave gateway; and obtaining the first ID using the user network interface node ID in the first configuration information if the first ID is the user network interface node ID of the second slave gateway.

11. The communication method according to claim 2, wherein the first ID is the device ID of the second slave gateway, the second slave gateway is a slave gateway connected to the second terminal, and the second terminal is the terminal to which the target media access control address in the Ethernet frame belongs.

12. After the step of receiving an Ethernet frame transmitted by the first terminal, and before the step of packaging the first port ID of the first slave gateway, the first ID, and the Ethernet frame as a first GEM frame, The steps include obtaining the device ID of the second slave gateway using the target media access control address, The communication method according to claim 11, comprising the step of obtaining the first port ID of the first slave gateway using the device ID of the second slave gateway.

13. The step of packaging the first port ID of the first slave gateway, the first ID, and the Ethernet frame as a first GEM frame is: The communication method according to claim 2, comprising the steps of packaging the Ethernet frame into the payload area of ​​the first GEM frame, and packaging the first port ID of the first slave gateway and the first ID into the GEM frame header of the first GEM frame.

14. The step of packaging the first port ID of the first slave gateway and the first ID in the GEM frame header of the first GEM frame is: The communication method according to claim 13, comprising the steps of packaging the first port ID of the first slave gateway into the port ID field in the GEM frame header, and packaging the first ID into the reserved field in the GEM frame header.

15. The step of packaging the first ID into the reserved field in the GEM frame header is: The communication method according to claim 14, comprising the step of packaging the first ID into any one bit in the reserved field.

16. The step of packaging the first ID into any one bit in the reserved field is: The communication method according to claim 14, further comprising the step of packaging the first ID into the most significant bit in the reserved field.

17. The step of packaging the first port ID of the first slave gateway and the first ID in the GEM frame header of the first GEM frame is: The communication method according to claim 13, comprising the step of packaging the first port ID of the first slave gateway, the first ID, and the second ID in the GEM frame header of the first GEM frame, wherein the second ID is used to characterize whether the first GEM frame is a GEM frame for communication between optical network units or a GEM frame for communication between an optical network unit and an optical line terminal.

18. The step of packaging the first port ID, the first ID, and the second ID of the first slave gateway into the GEM frame header of the first GEM frame is: The communication method according to claim 17, comprising the steps of packaging the first port ID of the first slave gateway into the port ID field in the GEM frame header, and packaging the first ID and the second ID into the reserved field in the GEM frame header.

19. A communication method applied to the main gateway, The steps include receiving a first Gigabit Passive Optical Network Package Mode GEM frame transmitted by a first slave gateway, wherein the first GEM frame includes a port ID, A communication method comprising the step of sending the first GEM frame to all slave gateways if it is determined that the port ID in the first GEM frame is a port ID used when communicating between optical network units.

20. The step of determining that the port ID in the first GEM frame is a port ID used when communicating between optical network units is: The steps include obtaining second configuration information, which is that the port ID is the port ID in the first GEM frame, The communication method according to claim 19, comprising the step of determining that the peer device ID in the second configuration information is not a special value.

21. The first GEM frame further includes a first ID, The first ID is the user network interface node ID of the first slave gateway. Alternatively, the first ID is the user network interface node ID of the second slave gateway, the second slave gateway is a slave gateway connected to the second terminal, and the second terminal is the terminal to which the target media access control address in the Ethernet frame of the first GEM frame belongs. Alternatively, the communication method according to claim 19, wherein the first ID is the device ID of the second slave gateway.

22. The step of determining that the port ID in the first GEM frame is a port ID used when communicating between optical network units is: The communication method according to claim 21, further comprising the step of determining that there exists third configuration information in which the port ID is the port ID in the first GEM frame and the peer device ID is the first ID in the first GEM frame.

23. The first GEM frame further includes a second ID used to characterize whether the first GEM frame is a GEM frame communicated between optical network units or a GEM frame communicated between an optical network unit and an optical line terminal, The step of determining that the port ID in the first GEM frame is a port ID used when communicating between optical network units is: The steps of obtaining the aforementioned second ID and The communication method according to claim 19, comprising the step of determining that the second ID is used to characterize the first GEM frame as a GEM frame that communicates between optical network units.

24. Before the step of transmitting the first GEM frame, Steps to obtain the first port ID of the second slave gateway, The further step includes replacing the port ID in the first GEM frame with the first GEM frame obtained and updated by the first port ID of the second slave gateway, The communication method according to claim 19, wherein the step of transmitting the first GEM frame to all slave gateways includes the step of transmitting the updated first GEM frame to all slave gateways.

25. The step of obtaining the first port ID of the second slave gateway is: The steps include obtaining second configuration information, which is that the port ID is the port ID in the first GEM frame, The communication method according to claim 24, comprising the step of obtaining the associated port ID in the second configuration information, wherein the associated port ID is the first port ID of the second slave gateway.

26. A communication method applicable to a third slave gateway, The steps include receiving a first Gigabit Passive Optical Network Package Mode GEM frame transmitted by the main gateway, wherein the first GEM frame includes a port ID, A communication method comprising the step of determining whether or not to perform appropriate processing on the first GEM frame based on whether or not the port ID in the first GEM frame is the first port ID of the third slave gateway, wherein the first port ID is a port ID for communication between optical network units.

27. The step of determining whether or not to perform appropriate processing on the first GEM frame based on whether or not the port ID in the first GEM frame is the first port ID of the third slave gateway is as follows: If the port ID in the first GEM frame is the first port ID of the third slave gateway, the step of deciding to perform appropriate processing on the first GEM frame, The communication method according to claim 26, comprising at least one of the following steps: determining that no appropriate processing should be performed on the first GEM frame if the port ID in the first GEM frame is not the first port ID of the third slave gateway.

28. The step of determining whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame is: The communication method according to claim 26, further comprising the step of determining whether or not to perform appropriate processing on the first GEM frame based on whether or not there is fourth configuration information that the associated port ID is the port ID in the first GEM frame.

29. The step of determining whether or not to perform appropriate processing on the first GEM frame is based on whether or not there is fourth configuration information that the related port ID is the port ID in the first GEM frame. If the fourth configuration information exists, the step of deciding to perform appropriate processing on the first GEM frame, The communication method according to claim 28, comprising at least one of the following steps: determining that no appropriate processing is performed on the first GEM frame if the fourth configuration information does not exist.

30. The first GEM frame further includes a first ID, and the step of determining whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame is: The communication method according to claim 26, further comprising the step of determining whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame.

31. The aforementioned first ID is the user network interface node ID of the first slave gateway. Alternatively, the communication method according to claim 30, wherein the first ID is the user network interface node ID of the second slave gateway, the second slave gateway is a slave gateway connected to the second terminal, and the second terminal is the terminal to which the target media access control address in the Ethernet frame in the first GEM frame belongs.

32. The step of determining whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame is: The communication method according to claim 31, further comprising the step of determining whether or not to perform appropriate processing on the first GEM frame based on whether or not the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether or not the first ID in the first GEM frame is the user network interface node ID of the third slave gateway.

33. The first ID is the user network interface node ID of the first slave gateway, The step of determining whether to perform appropriate processing on the first GEM frame based on whether the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether the first ID in the first GEM frame is the user network interface node ID of the third slave gateway, is as follows: If the port ID in the first GEM frame is the first port ID of the third slave gateway, and the first ID in the first GEM frame is not the user network interface node ID of the third slave gateway, the step of deciding to perform appropriate processing on the first GEM frame, The communication method according to claim 32, comprising at least one of the following steps: determining not to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is not the first port ID of the third slave gateway, or if the first ID in the first GEM frame is the user network interface node ID of the third slave gateway.

34. The first ID is the user network interface node ID of the second slave gateway, The step of determining whether to perform appropriate processing on the first GEM frame based on whether the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether the first ID in the first GEM frame is the user network interface node ID of the third slave gateway, is as follows: The steps include determining to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is the first port ID of the third slave gateway and the first ID in the first GEM frame is the user network interface node ID of the third slave gateway, The communication method according to claim 31, comprising at least one of the following steps: determining that no appropriate processing is performed on the first GEM frame if the port ID in the first GEM frame is not the first port ID of the third slave gateway, or if the first ID in the first GEM frame is not the user network interface node ID of the third slave gateway.

35. The communication method according to claim 30, wherein the first ID is the device ID of the second slave gateway, the second slave gateway is a slave gateway connected to the second terminal, and the second terminal is the terminal to which the target media access control address in the Ethernet frame in the first GEM frame belongs.

36. The step of determining whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame is: The communication method according to claim 35, further comprising the step of determining whether or not to perform appropriate processing on the first GEM frame based on whether or not the port ID in the first GEM frame is the first port ID of the third slave gateway, and whether or not the first ID in the first GEM frame is the device ID of the third slave gateway.

37. The step of determining whether to perform appropriate processing on the first GEM frame based on whether the port ID in the first GEM frame is the first port ID of the third slave gateway and whether the first ID in the first GEM frame is the device ID of the third slave gateway is, The steps include determining to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is the first port ID of the third slave gateway and the first ID in the first GEM frame is the device ID of the third slave gateway, The communication method according to claim 36, comprising at least one of the steps of: determining not to perform appropriate processing on the first GEM frame if the port ID in the first GEM frame is not the first port ID of the third slave gateway, or if the first ID in the first GEM frame is not the device ID of the third slave gateway.

38. The step of determining whether or not to perform appropriate processing on the first GEM frame based on the port ID in the first GEM frame and the first ID in the first GEM frame is: The communication method according to claim 30, further comprising the step of determining whether or not to perform appropriate processing on the first GEM frame based on whether or not there is fourth configuration information that the associated port ID is the port ID in the first GEM frame, and whether or not the first ID in the first GEM frame is the device ID of the third slave gateway.

39. At least one processor, An electronic device comprising: a memory that stores at least one program, and when the at least one program is executed by the at least one processor, causes the at least one processor to implement the communication method described in any one of claims 1 to 38.

40. A computer-readable medium that stores a computer program and, when the computer program is executed by the processor, causes the processor to implement the communication method described in any one of claims 1 to 38.

41. It includes a first slave gateway, a main gateway, and a third slave gateway. The first slave gateway is used to receive Ethernet frames transmitted by the first terminal, packages the first port ID of the first slave gateway and the Ethernet frame as a first Gigabit Passive Optical Network Package Mode GEM frame, and transmits the first GEM frame to the main gateway. The first port ID is the port ID used when communicating between optical network units. The main gateway is used to receive the first GEM frame transmitted by the first gateway, and the first GEM frame includes a port ID. If the main gateway determines that the port ID in the first GEM frame is a port ID used for communication between optical network units, it transmits the first GEM frame to all slave gateways. A communication system in which the third slave gateway is used to receive a first GEM frame transmitted by the main gateway, the first GEM frame includes a port ID, and the port ID in the first GEM frame determines whether or not to perform appropriate processing on the first GEM frame.

Images