Message forwarding method, OLT, ONU and computer readable storage medium

Abstract

The application relates to the communication technical field, and provides a message forwarding method, an OLT, an ONU and a computer readable storage medium. The method is applied to the OLT, any OLT port corresponds to each ONU connected with the OLT port and a non-unicast GemPort ID of a non-unicast type, the non-unicast type is at least two of multicast, broadcast and unknown unicast. If the message type of a received target message is any one of the non-unicast types, a target OLT port used for forwarding the target message is determined; the target message is encapsulated based on the target non-unicast GemPort ID corresponding to the target OLT port, a target message carrying the target non-unicast GemPort ID is obtained, and the target message is sent to each ONU connected with the target OLT port; and each ONU forwards the target message according to the target non-unicast GemPort ID. The message does not need to be copied to different ONUs of a single OLT port, so as to reduce message redundancy.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to message forwarding methods, OLT, ONU and computer-readable storage media. Background Technology

[0002] Passive Optical Network (PON) is a fiber optic access technology that uses a point-to-multipoint topology. It consists of three parts: an Optical Line Terminal (OLT), an Optical Distribution Network (ODN), and Optical Network Units (ONUs). The OLT, as the central office equipment, connects multiple ONUs through a single optical fiber via a splitter to provide broadband access services to end users.

[0003] Currently, PON can use GEM (GPON Encapsulation Method) to carry upper-layer service data. GEM frames identify different service flows through GemPort. GemPort is the logical connection channel or "port" between ONU and OLT that carries these GEM frames.

[0004] The service traffic carried by the PON system is divided into unicast traffic and non-unicast traffic according to the destination address type. Non-unicast traffic includes unknown unicast traffic, broadcast traffic, or multicast traffic.

[0005] Currently, it is necessary to create an independent non-unicast GemPort for each ONU connected to any OLT port, and the non-unicast GemPorts of different ONUs are different. When the OLT sends non-unicast traffic, since the non-unicast GemPorts of different ONUs are different, it is necessary to make a copy for each ONU that needs to receive the traffic and send it through the GemPort corresponding to that ONU.

[0006] It is evident that when multiple ONUs on an OLT port receive the same non-unicast traffic, multiple copies of the non-unicast traffic need to be replicated, resulting in traffic redundancy. Summary of the Invention

[0007] This application provides a message forwarding method, an OLT, an ONU, and a computer-readable storage medium to solve the problem of traffic redundancy in the prior art.

[0008] Firstly, this application provides a message forwarding method applied to an optical line terminal (OLT). Each OLT port corresponds to a non-unicast gigabit passive optical network encapsulation mode (GemPort ID). The non-unicast GemPort ID corresponding to any OLT port is associated with each optical network unit (ONU) connected to that OLT port and with a non-unicast type, wherein the non-unicast type is at least two of multicast, broadcast, and unknown unicast. The method includes: If the received target message is of any non-unicast type, determine the target OLT port used to forward the target message; Based on the target non-unicast GemPort ID corresponding to the target OLT port, the target packet is encapsulated to obtain the target packet carrying the target non-unicast GemPort ID; The target packet carrying the target non-unicast GemPort ID is sent to each ONU connected to the target OLT port, so that each ONU forwards the target packet according to the target non-unicast GemPort ID.

[0009] Secondly, this application provides a message forwarding method applied to an optical network unit (ONU), where the ONU connects to a target OLT port of an optical line terminal (OLT). The target OLT port is assigned a target non-unicast gigabit passive optical network encapsulation mode (GemPort ID), which is associated with each ONU connected to the target OLT port and represents a non-unicast type. The non-unicast type is at least two of multicast, broadcast, and unknown unicast. The method includes: Receive the target packet carrying the target non-unicast GemPort ID sent by the OLT through the target OLT port. The target OLT port is any OLT port that the OLT determines to forward the target packet when the packet type of the target packet is any of the non-unicast types. Forward the target packet based on the target non-unicast GemPort ID.

[0010] Thirdly, embodiments of this application provide an optical line terminal (OLT), wherein each OLT port corresponds to a non-unicast gigabit passive optical network encapsulation mode port identifier (GemPort ID), and the non-unicast GemPort ID corresponding to each OLT port is associated with each optical network unit (ONU) connected to that OLT port and the non-unicast type, wherein the non-unicast type is at least two of multicast, broadcast, and unknown unicast; the OLT includes: The port determination module is used to determine the target OLT port used to forward the target packet when the packet type of the received target packet is any of the non-unicast types. The encapsulation module is used to encapsulate the target packet based on the target non-unicast GemPort ID corresponding to the target OLT port, so as to obtain the target packet carrying the target non-unicast GemPort ID; The sending module is used to send the target packet carrying the target non-unicast GemPort ID to each ONU connected to the target OLT port, so that each ONU forwards the target packet according to the target non-unicast GemPort ID.

[0011] Fourthly, embodiments of this application provide an optical network unit (ONU) that connects to a target OLT port of an optical line terminal (OLT). The target OLT port is assigned a target non-unicast gigabit passive optical network encapsulation mode (GemPort ID). The target non-unicast GemPort ID is associated with each ONU connected to the target OLT port and with a non-unicast type, wherein the non-unicast type is at least two of multicast, broadcast, and unknown unicast. The ONU includes: The receiving module is used to receive the target packet carrying the target non-unicast GemPort ID sent by the OLT through the target OLT port. The target OLT port is any OLT port that the OLT determines to forward the target packet when the packet type of the target packet is any of the non-unicast types. The forwarding module is used to forward target packets based on the target non-unicast GemPort ID.

[0012] Fifthly, embodiments of this application provide an optical line terminal (OLT), the OLT comprising: Memory, used to store program instructions; A processor is configured to invoke program instructions stored in memory and execute the steps of the method described in any of the first aspects above, according to the obtained program instructions.

[0013] Sixthly, embodiments of this application provide an optical network unit (ONU), the ONU comprising: Memory, used to store program instructions; A processor is configured to invoke program instructions stored in memory and execute the steps of any of the methods described in the second aspect above, according to the obtained program instructions.

[0014] In a seventh aspect, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the steps of any one of the methods described in the first or second aspect above.

[0015] In summary, the message forwarding method provided in this application is applied to an Optical Line Terminal (OLT). Each OLT port corresponds to a non-unicast GemPort ID. The non-unicast GemPort ID associated with each OLT port is linked to each Optical Network Unit (ONU) connected to that OLT port and is a non-unicast type, where the non-unicast type is at least two of multicast, broadcast, and unknown unicast. The method first determines the target OLT port used to forward the target message if the received target message's message type is any of the non-unicast types. Then, based on the target non-unicast GemPort ID corresponding to the target OLT port, the target message is encapsulated to obtain a target message carrying the target non-unicast GemPort ID. Next, the target message carrying the target non-unicast GemPort ID is sent to each ONU connected to the target OLT port. Finally, each ONU forwards the target message according to the target non-unicast GemPort ID.

[0016] Using the message forwarding method provided in this application, each OLT port corresponds to a non-unicast GemPortID. This non-unicast GemPortID is associated with a non-unicast type (at least two of multicast, broadcast, and unknown unicast) and each ONU connected to the OLT port. In this way, for non-unicast type messages that need to be forwarded using this OLT port, the message is encapsulated based on the non-unicast GemPortID corresponding to the OLT port and sent directly to each ONU connected to the OLT port. There is no need to copy the encapsulated message on a single OLT port, thereby reducing the probability of message redundancy. In addition, the mapping of non-unicast type messages and each ONU connected to a single OLT port to the same non-unicast GemPortID can save GemPortID resources. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments of this application or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings of the embodiments of this application.

[0018] Figure 1 A detailed flowchart of a message forwarding method provided for an embodiment of this application; Figure 2 A schematic diagram illustrating a message forwarding scenario provided in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of an OLT provided in an embodiment of this application; Figure 4This is a schematic diagram of the structure of an ONU provided in an embodiment of this application; Figure 5 This is a schematic diagram of a message forwarding device provided in an embodiment of this application. Detailed Implementation

[0019] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “the,” and “the” as used in this application and claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to any and all possible combinations comprising one or more of the associated listed items.

[0020] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" may also be interpreted as "when," "when," or "in response to a determination."

[0021] Passive Optical Network (PON) is a fiber optic access technology that uses a point-to-multipoint topology. It consists of three parts: Optical Line Terminal (OLT), Optical Distribution Network (ODN), and Optical Network Units (ONUs). The OLT, as the central office equipment, connects multiple ONUs through a single optical fiber via a splitter to provide broadband access services to end users.

[0022] Currently, the mainstream PON technologies include GPON (ITU-T G.984 series), XGSPON (ITU-T G.9807 series), and EPON (IEEE 802.3ah). GPON and XGSPON use GEM (GPON Encapsulation Method) encapsulation to carry upper-layer service data. GEM frames identify different service flows through GemPort. GemPort is the basic channel unit for carrying data services in a GPON / XGSPON system; it is the logical connection channel or "port" between the ONU and OLT that carries these GEM frames.

[0023] The OLT device internally consists of two main parts: the Host CPU and the FPGA, which work together. The FPGA, as the PON chip, undertakes the core processing functions of the TC (Transmission Convergence) layer in the PON protocol stack, mainly including the following five functions: (1) GEM frame encapsulation / decapsulation: encapsulate uplink service data into GEM frames, decapsulate downlink GEM frames and extract service data; (2) GemPort multiplexing / demultiplexing: Distribute downlink GEM frames according to GemPort ID to ensure that each ONU only receives its own GEM frames; (3) Downlink data scheduling and replication: The FPGA downlink scheduler is responsible for encapsulating the data frames sent by the Host CPU according to the GemPort ID and sending them to the fiber optic link. For non-unicast traffic, it is necessary to replicate and send them one by one according to the GemPort. (4) DBA (Dynamic Bandwidth Allocation) scheduling: manages uplink bandwidth allocation and schedules the uplink transmission time slots of each ONU according to T-CONT (Transmission Container) and AllocId (allocation identifier); (5) FPGA register configuration: The Host CPU configures parameters such as GemPort entries, T-CONT bandwidth, and alarm threshold by reading and writing FPGA registers.

[0024] Therefore, the processing power of the FPGA directly determines the number of GEM frames that the OLT downlink can carry. When non-unicast traffic needs to be copied independently for each ONU, the FPGA downlink scheduler needs to perform N GEM frame encapsulations (N being the number of ONUs), and the processing load increases linearly with the number of ONUs.

[0025] Each ONU can be assigned multiple T-CONTs, and each T-CONT is bound to an AllocId. The uplink bandwidth is allocated by the DBA scheduler. Each T-CONT can carry multiple GemPorts, and each GemPort has a unique GemPort ID for GEM frame multiplexing / demultiplexing.

[0026] The GemPort ID of the current OLT device is assigned using a linear mapping formula based on the ONU ID. The linear mapping formula is GemPort ID = GEMPORT_ID_MIN + OnuId × SUBIF_PORT_MAX + SubIfPort – 1.

[0027] Wherein, GEMPORT_ID_MIN=256 is the starting value of GemPort ID; OnuId is the ONU number (0~127 for GPON, 0~255 for XGSPON); SUBIF_PORT_MAX is the maximum number of subports supported by each ONU (current value is 8); SubIfPort is the subport sequence number (1~8 are service subports).

[0028] This allocation method ensures that each ONU has its own dedicated GemPort ID space, and the GemPort IDs of different ONUs will not conflict.

[0029] The service traffic carried by a PON system is divided into unicast traffic and non-unicast traffic based on the destination address type. Unicast traffic is traffic destined for a specific ONU and is transmitted through the GemPort corresponding to that ONU. Non-unicast traffic includes unknown unicast traffic, broadcast traffic, or multicast traffic. For downlink traffic, the OLT needs to copy and send non-unicast traffic to all or multiple ONUs.

[0030] In related technologies, the OLT allocates an independent unicast GemPort (ID range 256~) to each ONU to carry the unicast traffic of that ONU.

[0031] For non-unicast traffic, in the PON downlink direction, the physical link from any OLT port to an ONU is shared (broadcast topology), and all downlink GEM frames will reach all ONUs. However, the GEM protocol stipulates that an ONU only receives GEM frames that match its own GemPortID and discards the rest. Therefore, an independent non-unicast GemPort needs to be created for each ONU connected to any OLT port. That is, the non-unicast GemPorts of different ONUs connected to any OLT port are different, even if the non-unicast traffic received by different ONUs is exactly the same. Correspondingly, when the OLT sends non-unicast traffic through any OLT port, it needs to make a copy for each ONU that needs to receive the traffic and send it through the GemPort corresponding to that ONU.

[0032] However, the above scheme assigns a non-unicast GemPort ID to each ONU connected to any OLT port independently. For non-unicast traffic such as multicast / broadcast / unknown unicast, a copy still needs to be made for each ONU, resulting in wasted GemPort resources and redundant traffic copying.

[0033] To address the technical issues of GemPort resource waste and redundant traffic replication, this application provides a packet forwarding method. The core idea of ​​this method is as follows: For any OLT port, non-unicast packets and all ONUs under that OLT port that need to receive non-unicast packets are mapped to the same non-unicast GemPort ID. This non-unicast GemPort ID is configured for that OLT port. The non-unicast type can be designed according to requirements and can be at least two of multicast, broadcast, and unknown unicast. Thus, for any OLT port, a non-unicast packet is encapsulated using the non-unicast GemPort ID corresponding to that OLT port, and this packet is forwarded to each ONU connected to that OLT port. Each ONU receives the packet carrying the non-unicast GemPort ID and forwards it, thereby saving GemPort resources and avoiding packet redundancy.

[0034] It should be noted that the non-unicast GemPort ID is independent of the unicast GemPort ID space and uses a dedicated numbering range (e.g., 0x4000). Furthermore, each OLT port is assigned only one non-unicast GemPort ID, which is shared by all ONUs under that OLT port. This means that all non-unicast packets from all ONUs under that OLT port can be forwarded via this non-unicast GemPort ID.

[0035] For example, see Figure 1 The diagram shown is a flowchart illustrating a message forwarding method provided in an embodiment of this application.

[0036] like Figure 1 As shown, in step 100, the OLT receives the target message and, if the message type of the target message is any of the non-unicast types, determines the target OLT port used to forward the target message.

[0037] An OLT includes at least one OLT port. Each OLT port corresponds to a non-unicast GemPort ID. The non-unicast GemPort ID corresponding to each OLT port is associated with each optical network unit (ONU) connected to that OLT port and the non-unicast type. The non-unicast type is at least two of multicast, broadcast, and unknown unicast.

[0038] It should be noted that the non-unicast GemPort IDs associated with each OLT port can be of the same or different non-unicast types. The non-unicast GemPort IDs associated with each OLT port can also be the same or different, depending on the specific circumstances. For example, any OLT port can have the same non-unicast GemPort ID, and all OLT ports can have the same non-unicast GemPort ID associated with the same non-unicast type, thus conserving GemPort ID resources.

[0039] In some embodiments, if the destination IP address of the received target packet is a multicast address, the OLT determines that the packet type of the target packet is multicast; if the destination IP address of the received target packet is a broadcast address, the OLT determines that the packet type of the target packet is broadcast; if the destination IP address of the received target packet is a unicast address and the MAC address table does not include the destination media access control address MAC address of the target packet, the OLT determines that the packet type of the target packet is unknown unicast.

[0040] In one example, the destination address of the target message includes the destination IP address. Broadcast addresses can be the restricted broadcast address 255.255.255.255 or subnet-directed broadcast addresses (such as 10.1.1.255 / 24); unicast addresses can be Class A IP address ranges (1.0.0.0 to 126.255.255.255), Class B IP address ranges (128.0.0.0 to 191.255.255.255), or Class C IP address ranges (192.0.0.0 to 223.255.255.255); multicast addresses can be Class D IP address ranges (224.0.0.0–239.255.255.255). Correspondingly, if the destination IP address of the target message belongs to any of the Class A, Class B, or Class C IP address ranges, then the message type of the target message is unicast. If the destination IP address is a restricted broadcast address (255.255.255.255) or a subnet-directed broadcast address (such as 10.1.1.255 / 24), then the message type of the destination packet is broadcast; if the destination IP address is a Class D IP address range (224.0.0.0–239.255.255.255), then the message type of the destination packet is multicast.

[0041] Furthermore, the destination address of the target packet also includes the destination MAC address. If the destination IP address is a unicast address and the MAC address table does not include the destination MAC address, the packet type of the target packet is determined to be unknown unicast.

[0042] For example, when the OLT receives a non-unicast type (broadcast, unknown unicast, or multicast) message, it identifies whether the destination IP address of the message is a multicast address, a broadcast address, or a unicast address. If the destination IP address is identified as a multicast address, the message type of the target message is determined to be multicast. If the destination IP address is identified as a broadcast address, the message type of the target message is determined to be broadcast. If the destination IP address is identified as a unicast address, it further identifies whether the destination MAC address of the message is in the MAC address table. If it is not in the table, the message type of the target message is determined to be non-unicast. If it is in the table, the message type of the target message is determined to be unicast.

[0043] In some embodiments, the OLT can identify the Virtual Local Area Network (VLAN) of the target packet; any OLT port configured with the VLAN of the target packet is designated as the target OLT port. The VLAN of the target packet can be represented by a VLAN identifier, which can be a VLAN identifier carried in the target packet or a VLAN identifier in a table entry matching the destination address of the target packet. This table entry is used to record the mapping relationship between the destination address and the VLAN identifier.

[0044] In some optional implementations, if the target packet is a broadcast or an unknown unicast, the OLT can determine the target VLAN identifier carried by the target packet and use any OLT port configured with the target VLAN identifier as the target OLT port.

[0045] In some optional implementations, the OLT includes a default mapping table that contains the mapping relationship between multicast addresses and VLAN identifiers. The default mapping table includes multiple entries, each containing a multicast address and a VLAN identifier. The multicast address can be a MAC address or an IP address.

[0046] In some possible scenarios, if the target packet's packet type is multicast, and there is no entry in the default mapping table matching the target packet's destination address (i.e., none of the entries in the default mapping table include a multicast address matching the target packet's destination address), the matching method can be exact matching. This requires the target packet's destination address (IP address and / or MAC address) to be exactly the same as the multicast address in the entry. Exact matching is merely an example and does not constitute a specific limitation; the matching method can be designed according to actual needs. In one example, the OLT discards the target packet; in another example, the OLT determines the target VLAN identifier carried by the target packet and uses any OLT port configured with the target VLAN identifier as the target OLT port.

[0047] In other possible scenarios, if the target packet's packet type is multicast, and the preset mapping table contains a target entry that matches the target packet's destination address (i.e., the target entry includes a multicast address matching the target packet's destination address), then the OLT will use any OLT port configured with the VLAN identifier from the target entry as the target OLT port.

[0048] In step 110, the OLT encapsulates the target packet based on the target non-unicast GemPort ID corresponding to the target OLT port to obtain a target packet carrying the target non-unicast GemPort ID.

[0049] In this embodiment, the OLT encapsulates the target packet into a GEM frame using the target non-unicast GemPort ID. The target non-unicast GemPort ID is a non-unicast GemPort ID corresponding to the target OLT port.

[0050] In some embodiments, the non-unicast GemPort IDs corresponding to each OLT port of the OLT are the same. In this way, each ONU connected to each OLT port of the OLT and the non-unicast type packets share the non-unicast GemPort ID, and the non-unicast GemPort ID is directly used as the target non-unicast GemPort ID.

[0051] In step 120, the OLT sends a target message carrying the target non-unicast GemPort ID to each ONU connected to the target OLT port.

[0052] The target OLT port is connected to multiple ONUs through a shared fiber optic link. After the OLT encapsulates the target message into a GEM frame using the target non-unicast GemPort ID, it is sent to the shared fiber optic link connected to the target OLT port. Regardless of how many ONUs are connected to the target OLT port, the GEM frame only needs to be sent once.

[0053] In step 130, each ONU connected to the target OLT port forwards the target packet according to the target non-unicast GemPort ID.

[0054] In some embodiments, if the ONU determines that the allowed GemPort IDs include the target non-unicast GemPort ID, it determines the packet type of the target packet. If the target packet type is broadcast or non-unicast, the target packet is forwarded to each ONU port. If the target packet type is multicast, a mapping relationship between multicast features and ONU ports can be pre-set. The target packet is matched with each preset multicast feature. If a preset multicast feature is matched, the target packet is forwarded to each ONU port corresponding to the matched preset multicast feature. The preset multicast feature can be a multicast VLAN or a multicast address. Correspondingly, if the target packet feature matches a multicast feature, it means the target packet matches the preset multicast feature, and the target packet is forwarded to each ONU port corresponding to the preset multicast feature. Among them, the matching method between the target packet feature and the multicast feature can be exact matching, that is, the target packet feature and the multicast feature must be completely consistent. For example, if the target packet feature is the destination IP address and the multicast feature is the multicast address, then the destination IP address and the multicast address must be completely consistent. Exact matching is only an example and does not constitute a specific limitation. The matching method can be designed according to the actual needs.

[0055] For example, the ONU includes a GemPort table, which records the allowed GemPort IDs and the message types associated with those GemPort IDs. Correspondingly, the ONU matches the target non-unicast GemPort ID with the GemPort IDs in the GemPort table. If a match is found with any GemPort ID in the GemPort table, it is determined that the allowed GemPort IDs include the target non-unicast GemPort ID.

[0056] For example, after receiving a GEM frame (a target message carrying a non-unicast GemPort ID), the ONU directly forwards broadcast and unknown unicast messages to its respective ONU ports. For multicast messages, the ONU must match them against local multicast rules before deciding whether to forward them to the corresponding ONU port. Messages that do not match a multicast rule are discarded and not forwarded to any ONU port. Multicast rules include the mapping relationship between ONU ports and multicast features, which can be multicast addresses and / or multicast VLANs.

[0057] In this scheme, one OLT port corresponds to one non-unicast GemPort ID. This non-unicast GemPort ID is associated with a non-unicast type (at least two of multicast, broadcast, and unknown unicast) and each ONU connected to the OLT port. In this way, for non-unicast type packets that need to be forwarded using this OLT port, the packet is encapsulated based on the non-unicast GemPort ID corresponding to the OLT port, and the encapsulated packet is directly sent to each ONU connected to the OLT port. There is no need to copy the encapsulated packet on a single OLT port, thereby reducing the probability of packet redundancy. In addition, the mapping of non-unicast type packets and each ONU connected to a single OLT port to the same non-unicast GemPort ID can save GemPort ID resources.

[0058] It should be noted that there can be multiple target OLT ports. For each target OLT port, the OLT can encapsulate the target packet based on the target non-unicast GemPort ID corresponding to the target OLT port to obtain a target packet carrying the target non-unicast GemPort ID, and send the target packet carrying the target non-unicast GemPort ID to each ONU connected to the target OLT port.

[0059] If the target non-unicast GemPort IDs corresponding to each target OLT port are the same, the OLT can encapsulate the target packet based on the target non-unicast GemPort ID shared by each target OLT port to obtain a target packet carrying the target non-unicast GemPort ID; and send the target packet carrying the target non-unicast GemPort ID to each ONU connected to each target OLT port.

[0060] In related technologies, the ONU needs to upload its Management Information Base (MIB) during the registration process. This MIB upload includes the ONU reporting MIB information to the OLT. The OLT audits the MIB information reported by the ONU, comparing it with pre-configured templates or business rules. If the audit passes, the ONU is considered successfully registered and can run online. The MIB can be understood as the ONU's "configuration database" or "capability description file," defining various parameters, functions, performance, and supported business types—like a detailed device resume.

[0061] After the MIB Upload is complete, upon receiving the multicast service trigger command configured by the user, the OLT sends the corresponding GemPort ID to the ONU, and the ONU begins processing the multicast packets. Broadcast and unicast are similar and will not be described further.

[0062] As can be seen, the creation process of GemPort is: ONU registration → MIB Upload → Online operation → [Waiting for multicast / broadcast service trigger] → Creating multicast / broadcast GemPort → Multicast / broadcast available. Here, " / " represents AND or OR.

[0063] The embodiments of this application improve the creation process of GemPort. The improved creation process is ONU registration → MIBUpload → [Immediately bind non-unicast GemPort ID] → Online operation (broadcast / multicast / unknown unicast is ready), thereby advancing the creation time of non-unicast GemPort from "when the service is triggered" to "after the MIB Upload is completed", shortening the readiness time of non-unicast services.

[0064] Correspondingly, in some embodiments, for any ONU (which can be referred to as the target ONU for ease of description and distinction) connected to any OLT port, after the OLT receives the local configuration information sent by the target ONU during the registration process, it sends GemPort configuration information to the target ONU. The GemPort configuration information includes the non-unicast GemPort ID corresponding to the OLT port connected to the target ONU and its corresponding non-unicast type. Subsequently, the target ONU records the received GemPort configuration information in the GemPort table. Thus, the non-unicast GemPort ID is the GemPort ID that the ONU is allowed to receive.

[0065] In some implementations, the ONU registration process may include: First, the ONU sends a registration request to the OLT. Then, the OLT initiates an information reporting request to the ONU, requesting the ONU to upload its local configuration information, such as the MIB. Next, the ONU reports its local configuration information, such as the MIB. For example, the ONU reports a series of "ME (Managed Entity)" instances from its MIB, describing the device's capabilities and configuration status, to the OLT. For instance, it might tell the OLT: "I have four Ethernet ports, support VLAN pass-through, and port 1 is currently connected." Finally, the OLT audits the local configuration information, such as the MIB, reported by the ONU. If the audit is successful, the OLT sends the GemPort configuration information to the ONU. Thus, through this implementation, the OLT sends the GemPort configuration information to the ONU after the MIBUpload is completed.

[0066] In this solution, after receiving the local configuration information of the ONU, the OLT binds the ONU and the non-unicast GemPort ID, instead of creating the binding GemPort ID when the service is triggered, thus shortening the time window from ONU registration to being able to receive broadcast / multicast / unknown unicast traffic.

[0067] The message forwarding method provided in this application embodiment will be described in detail below with reference to specific application scenarios.

[0068] The application scenario is as follows: any OLT port in the OLT corresponds to a non-unicast GemPort ID. The non-unicast GemPort ID is associated with all ONUs connected to all OLT ports and non-unicast types. The non-unicast types are multicast, broadcast, and unknown unicast.

[0069] Figure 2 This is a schematic diagram illustrating a message forwarding scenario provided in an embodiment of this application. For example... Figure 2 As shown, the OLT maps multicast, broadcast, and unknown unicast packets to non-unicast GemPort IDs, obtaining a shared non-unicast GemPort ID for multicast, broadcast, and unknown unicast packets. Then, for any of these packets, the OLT port configured with the shared non-unicast GemPort ID is determined. The packet is then encapsulated using the shared non-unicast GemPort ID and sent to each ONU connected to the corresponding OLT port. The OLT port can be determined by the VLAN corresponding to the packet. If the packet does not correspond to a VLAN, each OLT port corresponding to the shared non-unicast GemPort ID is directly used as the OLT port corresponding to the packet. The method of forwarding this message is merely an example and does not constitute a specific limitation. In other implementations, for any message among multicast messages, broadcast messages, and unknown unicast messages, the message is encapsulated with the shared non-unicast GemPort ID and sent to each ONU connected to each OLT port configured with the shared non-unicast GemPort ID.

[0070] The following is combined with Figure 2 This paper provides a detailed introduction to the message forwarding methods in this application scenario.

[0071] Step S1: Non-unicast message arrives. The OLT receives a non-unicast message, identifies the destination IP address in the message as a multicast address or a broadcast address, determines the message type as multicast or broadcast, that is, the message is a multicast message or a broadcast message, or although the destination IP address is a unicast address, the destination MAC is not in its MAC address table, determines the message type as unknown unicast, that is, the message is an unknown unicast message, and proceeds to step S2.

[0072] Step S2: Locate the target OLT ports used for forwarding non-unicast packets. The OLT ports determine the VLAN identifier corresponding to the non-unicast packets and designate each OLT port configured with the VLAN identifier as a target OLT port. For example, if the non-unicast packet is a broadcast packet or an unknown unicast packet, the VLAN identifier corresponding to the non-unicast packet is the VLAN identifier carried by the non-unicast packet. The OLT includes a preset mapping table representing the mapping relationship between multicast addresses and VLAN identifiers. If the non-unicast packet is a multicast packet, and there is a target entry in the preset mapping table that matches the destination address of the multicast packet, then the VLAN identifier corresponding to the non-unicast packet is the VLAN identifier in the target entry. If the non-unicast packet is a multicast packet, and there is no entry in the preset mapping table that matches the destination address of the multicast packet, then the VLAN identifier corresponding to the non-unicast packet is the VLAN identifier carried by the non-unicast packet.

[0073] Step S3: Find the target non-unicast GemPort ID corresponding to each target OLT port. For each target OLT port, find the corresponding non-unicast GemPort ID based on the port's identifier (e.g., its number) and use it as the target non-unicast GemPort ID. If all OLT ports have the same non-unicast GemPort ID, then there is only one target non-unicast GemPort ID. In this case, you can find the corresponding non-unicast GemPort ID based on any target OLT port's identifier (e.g., its number) and use it as the target non-unicast GemPort ID.

[0074] Step S4: Single Data Transmission. In some implementations, for any target OLT port, the OLT encapsulates a non-unicast message into a GEM frame using the target non-unicast GemPort ID corresponding to that target OLT port, and sends the GEM frame to the shared fiber link of that target OLT port. Thus, regardless of the number of ONUs under that OLT port, the GEM frame only needs to be sent once. In other implementations, if all OLT ports have the same non-unicast GemPort ID, the OLT encapsulates the non-unicast message into a GEM frame using the target non-unicast GemPort ID; for any target OLT port, the GEM frame is sent to the shared fiber link of that target OLT port. Since the target non-unicast GemPort IDs are the same for all OLT ports, the non-unicast message only needs to be encapsulated once. If the number of target OLT ports is greater than two, the GEM frame is directly copied to other target OLT ports.

[0075] Step S5: ONU-side reception processing. When any ONU receives a GEM frame, it parses the GemPortID in the GEM frame and matches it with each allowed GemPort ID in the GemPort ID table. If a non-unicast GemPort ID is matched, it is processed according to the message type. If the message type is broadcast or unknown unicast, it is directly forwarded to each ONU port. If the message type is multicast, it is forwarded to the ONU port corresponding to the local multicast rule after matching the local multicast rule. If no local multicast rule is matched, it is discarded. The multicast rule describes the mapping relationship between multicast characteristics and ONU ports. The multicast characteristics are multicast VLAN and / or multicast address.

[0076] For example, see Figure 3 The diagram shown is a structural schematic of an OLT provided in an embodiment of this application. Each OLT port corresponds to a non-unicast GemPort ID. The non-unicast GemPort ID corresponding to any OLT port is associated with each optical network unit (ONU) connected to that OLT port and the non-unicast type. The non-unicast type is at least two of multicast, broadcast, and unknown unicast. The OLT includes a port determination module 300, an encapsulation module 310, and a transmission module 320. The port determination module 300 is used to determine the target OLT port used to forward the target packet when the packet type of the received target packet is any of the non-unicast types. The encapsulation module 310 is used to encapsulate the target packet based on the target non-unicast GemPort ID corresponding to the target OLT port to obtain a target packet carrying the target non-unicast GemPort ID. The sending module 320 is used to send the target packet carrying the target non-unicast GemPort ID to each ONU connected to the target OLT port, so that each ONU forwards the target packet according to the target non-unicast GemPort ID.

[0077] In some embodiments, the non-unicast GemPort IDs corresponding to each OLT port are the same.

[0078] In some embodiments, the port determination module 300 is used to determine the target virtual local area network (VLAN) identifier carried by the target packet if the packet type of the target packet is broadcast or unknown unicast, and to use any OLT port configured with the target VLAN identifier as the target OLT port. If the target packet is of multicast type and there is no entry in the preset mapping table that matches the destination address of the target packet, then the target packet is discarded; or, the target VLAN identifier carried by the target packet is determined, and any OLT port configured with the target VLAN identifier is used as the target OLT port; wherein, the preset mapping table includes the mapping relationship between multicast address and VLAN identifier. If the target packet is of multicast type and there is a target entry in the preset mapping table that matches the destination address of the target packet, then any OLT port configured with the VLAN identifier in the target entry will be used as the target OLT port.

[0079] In some embodiments, the OLT further includes a non-unicast configuration module. The non-unicast configuration module is used to send non-unicast configuration information to the target ONU when it receives the local configuration information sent by the target ONU during the registration process. The non-unicast configuration information includes the non-unicast GemPort ID and non-unicast type corresponding to the OLT port connected to the target ONU. The target ONU is any ONU connected to any OLT port.

[0080] In some embodiments, the OLT further includes a type recognition module. The type identification module is used to determine whether the message type of the received target message is multicast when the destination IP address of the target message is a multicast address. If the destination IP address of the received target message is a broadcast address, then the message type of the target message is determined to be broadcast. If the destination IP address of the received target packet is a unicast address and the MAC address table does not include the destination media access control address MAC address of the target packet, the packet type of the target packet is determined to be unknown unicast.

[0081] For example, see Figure 4 As shown, this application provides an ONU that connects to the target OLT port of the OLT. The target OLT port is assigned a target non-unicast GemPort ID, which is associated with each ONU and non-unicast type connected to the target OLT port. The non-unicast type is at least two of multicast, broadcast, and unknown unicast.

[0082] The ONU includes a receiving module 400 and a forwarding module 410. The receiving module 400 is used to receive a target packet carrying a target non-unicast GemPort ID sent by the OLT through the target OLT port. The target OLT port is any OLT port used by the OLT to forward the target packet when the packet type of the target packet is any of the non-unicast types. Forwarding module 410 is used to forward target packets based on the target non-unicast GemPort ID.

[0083] In some embodiments, the forwarding module 410 is configured to determine the message type of the target message if the GemPort IDs that the ONU is allowed to receive include the target non-unicast GemPort ID; If the target message is of broadcast or non-unicast type, forward the target message to each ONU port of the ONU; If the target message is of multicast type, the message characteristics of the target message are matched with the preset multicast message characteristics. If a preset multicast characteristic is matched, the target message is forwarded to the ONU port corresponding to the matched preset multicast characteristic.

[0084] These units can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more digital signal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, when one of these units is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these units can be integrated together to form a system-on-a-chip (SOC).

[0085] Furthermore, the message forwarding apparatus provided in this application embodiment. From a hardware perspective, a schematic diagram of the hardware architecture of the message forwarding apparatus can be found in [reference needed]. Figure 5 As shown, the message forwarding device can be an OLT or an ONU. The message forwarding device may include: a memory 500 and a processor 510. The memory 500 is used to store program instructions; the processor 510 calls the program instructions stored in the memory 500 and executes the above method embodiment according to the obtained program instructions. The specific implementation method and technical effect are similar, and will not be described again here.

[0086] Optionally, this application also provides a distributed communication device, including at least one processing element (or chip) for performing the above method embodiments.

[0087] Optionally, this application also provides a program product, such as a computer-readable storage medium storing computer-executable instructions for causing the computer to perform the above-described method embodiments.

[0088] Here, a machine-readable storage medium can be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, etc. For example, a machine-readable storage medium can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drives (such as hard disk drives), solid-state drives, any type of storage disk (such as optical discs, DVDs, etc.), or similar storage media, or combinations thereof.

[0089] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0090] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0091] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0092] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0093] Furthermore, these computer program instructions can also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in the process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0094] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0095] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A message forwarding method, characterized in that, Applied to an optical line terminal (OLT), wherein each OLT port corresponds to a non-unicast gigabit passive optical network encapsulation mode port identifier (GemPort ID), and the non-unicast GemPort ID corresponding to any OLT port is associated with each optical network unit (ONU) connected to that OLT port and the non-unicast type, wherein the non-unicast type is at least two of multicast, broadcast, and unknown unicast, the method comprising: If the message type of the received target message is any of the non-unicast types, determine the target OLT port used to forward the target message; Based on the target non-unicast GemPort ID corresponding to the target OLT port, the target packet is encapsulated to obtain a target packet carrying the target non-unicast GemPort ID; The target packet carrying the target non-unicast GemPort ID is sent to each ONU connected to the target OLT port, so that each ONU forwards the target packet according to the target non-unicast GemPort ID.

2. The method as described in claim 1, characterized in that, The non-unicast GemPort IDs corresponding to each OLT port of the OLT are the same.

3. The method as described in claim 1, characterized in that, Determining the target OLT port used to forward the target packet includes: If the message type of the target message is broadcast or unknown unicast, then the target virtual local area network (VLAN) identifier carried by the target message is determined, and any OLT port configured with the target VLAN identifier is used as the target OLT port. If the target packet is of multicast type and there is no entry in the preset mapping table that matches the destination address of the target packet, then the target packet is discarded; or, the target VLAN identifier carried by the target packet is determined, and any OLT port configured with the target VLAN identifier is used as the target OLT port; wherein, the preset mapping table includes the mapping relationship between multicast address and VLAN identifier; If the target packet is of multicast type and there is a target entry in the preset mapping table that matches the destination address of the target packet, then any OLT port configured with the VLAN identifier in the target entry will be used as the target OLT port.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Upon receiving local configuration information sent by the target ONU during the registration process, non-unicast configuration information is sent to the target ONU. The non-unicast configuration information includes the non-unicast GemPortID corresponding to the OLT port connected to the target ONU and the non-unicast type. The target ONU is any ONU connected to any OLT port.

5. The method according to any one of claims 1 to 3, characterized in that, The method further includes: If the destination IP address of the received target message is a multicast address, then the message type of the target message is determined to be multicast. If the destination IP address of the received target message is a broadcast address, then the message type of the target message is determined to be broadcast; If the destination IP address of the received target packet is a unicast address and the MAC address table does not include the destination media access control address (MAC address) of the target packet, then the packet type of the target packet is determined to be unknown unicast.

6. A message forwarding method, characterized in that, The method is applied to an optical network unit (ONU) connected to a target OLT port of an optical line terminal (OLT). The target OLT port is assigned a target non-unicast gigabit passive optical network encapsulation mode (GemPort ID). The target non-unicast GemPort ID is associated with each ONU connected to the target OLT port and represents a non-unicast type, wherein the non-unicast type is at least two of multicast, broadcast, and unknown unicast. Receive the target packet carrying the target non-unicast GemPort ID sent by the OLT through the target OLT port, wherein the target OLT port is any OLT port used by the OLT to forward the target packet when the packet type of the target packet is any of the non-unicast types; Based on the target non-unicast GemPort ID, forward the target packet.

7. The method according to claim 6, characterized in that, The forwarding of the target packet based on the target non-unicast GemPort ID includes: If the target non-unicast GemPort ID is included among the GemPort IDs that the ONU is allowed to receive, determine the message type of the target message; If the message type of the target message is broadcast or non-unicast, the target message is forwarded to each ONU port of the ONU. If the target message is of multicast type, the message characteristics of the target message are matched with each preset multicast message characteristic. If a preset multicast characteristic is matched, the target message is forwarded to each ONU port corresponding to the matched preset multicast characteristic.

8. An optical line terminal (OLT), characterized in that, Each OLT port in the OLT corresponds to a non-unicast Gigabit Passive Optical Network Encapsulation Mode Port Identifier (GemPort ID). The non-unicast GemPort ID corresponding to any OLT port is associated with each Optical Network Unit (ONU) connected to that OLT port and the non-unicast type, wherein the non-unicast type is at least two of multicast, broadcast, and unknown unicast. The OLT includes: The port determination module is used to determine the target OLT port used to forward the target packet when the packet type of the received target packet is any of the non-unicast types. The encapsulation module is used to encapsulate the target packet based on the target non-unicast GemPort ID corresponding to the target OLT port to obtain a target packet carrying the target non-unicast GemPort ID; The sending module is used to send a target packet carrying the target non-unicast GemPort ID to each ONU connected to the target OLT port, so that each ONU forwards the target packet according to the target non-unicast GemPort ID.

9. An optical network unit (ONU), characterized in that, The ONU connects to the target OLT port of the Optical Line Terminal (OLT). The target OLT port is assigned a target non-unicast gigabit passive optical network encapsulation mode port identifier (GemPort ID). The target non-unicast GemPort ID is associated with each ONU connected to the target OLT port and represents a non-unicast type. The non-unicast type is at least two of multicast, broadcast, and unknown unicast. The ONUs include: The receiving module is used to receive a target packet carrying a target non-unicast GemPort ID sent by the OLT through the target OLT port. The target OLT port is any OLT port used by the OLT to forward the target packet when the packet type of the target packet is any of the non-unicast types. The forwarding module is used to forward the target packet based on the target non-unicast GemPort ID.

10. An optical line terminal (OLT), characterized in that, include: Memory, used to store program instructions; A processor is configured to invoke program instructions stored in the memory and execute the method of any one of claims 1-5 according to the obtained program instructions.

11. An optical network unit (ONU), characterized in that, include: Memory, used to store program instructions; A processor is configured to invoke program instructions stored in the memory and execute the method of claim 6 or 7 according to the obtained program instructions.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1-7.

Images