FTTR forwarding method and device

Abstract

The invention discloses an FTTR forwarding method and device, and relates to the technical field of data forwarding, the FTTR forwarding method comprises the steps that a Gemport mapping table is maintained in a main gateway, the Gemport mapping table comprises a fem id, a gem id and a vlan id of a message, the fem id is id information of the Gemport received by the main gateway from an OLT, and the gem id is id information of the Gemport sent to a sub-gateway after being translated by the main gateway; and according to a message forwarding scene, setting a Gemport mapping rule, and according to the Gemport mapping rule and the Gemport mapping table, carrying out conversion between the fem id and the gem id in a downlink direction and an uplink direction so as to carry out message conversion. According to the invention, multi-level conversion of the message can be reduced, time delay is reduced, and forwarding efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data forwarding, in particular to an FTTR forwarding method and device. BACKGROUND

[0002] FTTR (Fiber to the Room) is a high-level deployment mode in the FTTx series. FTTR replaces the traditional gateway plus router wired networking mode by using the main sub-gateway fiber networking mode, and directly lays optical fibers to each room in a residence or building to provide better broadband access experience for users.

[0003] In the conventional FTTR forwarding model, data exchange is performed based on Ethernet frames inside the main sub-gateway. Since the main sub-gateway is connected by optical fibers, the messages received by the main sub-gateway are all gem frames, so the messages need to be converted into Ethernet frames before data exchange and forwarding. The main gateway needs to complete the conversion of gem frames -> Ethernet frames -> gem frames, and the sub-gateway needs to complete the conversion of gem frames -> Ethernet frames (the same as a general gateway). As shown in Figure 1 the main gateway Soc chip receives gem frames, converts them into Ethernet frames, adds a layer of vlan (gemport vlan) to the Ethernet frames, and then converts the layer of vlan (gemport vlan) into a gem frame header through the FPGA (Field Programmable Gate Array) chip, encapsulates the gem frame, and forwards it to the sub-gateway. The sub-gateway converts the gem frame -> Ethernet frame again to facilitate internal Ethernet frame exchange.

[0004] However, in the entire forwarding process, the messages are converted multiple times, especially the main gateway, which has a large number of conversion times, resulting in a large delay in the forwarding process and low efficiency. SUMMARY

[0005] The present application provides an FTTR forwarding method and device, which can improve the data forwarding efficiency of FTTR.

[0006] In a first aspect, an FTTR forwarding method is provided, which includes: maintaining a Gemport mapping table in the main gateway, the Gemport mapping table including a fem id, a gem id, and a vlan id of a message, the fem id being id information of a Gemport received by the main gateway from an OLT, the gem id being id information of a Gemport sent to a sub-gateway after translation by the main gateway; Based on the packet forwarding scenario, Gemport mapping rules are set. According to the Gemport mapping rules and Gemport mapping table, the fem id and gem id are converted in the downlink and uplink directions to perform packet conversion.

[0007] In conjunction with the first aspect, in one implementation, the step of setting Gemport mapping rules according to the packet forwarding scenario, and performing the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and the Gemport mapping table to perform packet conversion includes: If the scenario involves forwarding unicast packets between the master and sub-gateways, and each sub-gateway uses only one Gemport, the Gemport mapping rule should be set to independently map each fem ID to the gem ID of all sub-gateways. In the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the VLAN ID of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the gem ID and VLAN ID to find the mapped fem ID for packet conversion.

[0008] In conjunction with the first aspect, in one implementation, the step of setting Gemport mapping rules according to the packet forwarding scenario, and performing the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and the Gemport mapping table to perform packet conversion includes: If the scenario involves forwarding unicast packets between the master and sub-gateways, and the sub-gateways map different Gemports based on VLANs, the Gemport mapping rule should be set to map each fem ID to the gem ID of a different sub-gateway based on VLAN. In the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the VLAN ID of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the gem ID and VLAN ID to find the mapped fem ID for packet conversion.

[0009] In conjunction with the first aspect, in one implementation, the step of setting Gemport mapping rules according to the packet forwarding scenario, and performing the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and the Gemport mapping table to perform packet conversion includes: If it is a scenario of forwarding multicast packets between the master and sub-gateways, set the Gemport mapping rule to map the multicast fem id to a single multicast gem id and broadcast it to all sub-gateways; In the downlink direction, the multicast fem ID is parsed, converted into a shared multicast gem ID based on the Gemport mapping rules, and the VLAN ID of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the multicast gem ID and VLAN ID to find the mapped multicast fem ID for packet conversion.

[0010] In conjunction with the first aspect, in one implementation, when the OLT issues or deletes a Gemport configuration, the main gateway correspondingly adds or deletes information in the corresponding Gemport mapping table.

[0011] In conjunction with the first aspect, in one implementation, the Gemport mapping table further includes downstream PON port number information; When the main gateway has multiple downstream PON ports, different downstream PON ports are distinguished in the Gemport mapping table by the downstream PON port number information.

[0012] In conjunction with the first aspect, in one implementation, when the main gateway is a scenario with multiple downstream PON ports, distinguishing different downstream PON ports in the Gemport mapping table using downstream PON port number information includes: Add a "downlink pon No." field to the Gemport mapping table to distinguish different downlink pon ports based on the table entry number in the "downlink pon No." field.

[0013] In conjunction with the first aspect, in one implementation, the Gemport mapping table further includes upstream PON port number information; When the main gateway has multiple uplink PON ports, different uplink PON ports are distinguished in the Gemport mapping table by the uplink PON port number information.

[0014] In conjunction with the first aspect, in one implementation, when the main gateway is a multi-uplink PON scenario, distinguishing different uplink PON ports in the Gemport mapping table using uplink PON port number information includes: Add an uplink pon No. field to the Gemport mapping table to distinguish different uplink pon ports based on the table entry number in the uplink pon No. field.

[0015] In conjunction with the first aspect, in one implementation, the Gemport mapping table further includes aging time information, and the Gemport mapping table is deleted when the aging time is reached.

[0016] Secondly, embodiments of this application provide an FTTR forwarding device, characterized in that the FTTR forwarding device comprises: The maintenance module is used to maintain a Gemport mapping table in the main gateway. The Gemport mapping table includes femid, gem id and packet VLAN id. The fem id is the Gemport id information received by the main gateway from the OLT. The gem is the Gemport id information sent to the sub-gateway after being translated by the main gateway. The conversion module sets Gemport mapping rules according to the packet forwarding scenario, and performs the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and Gemport mapping table to convert the packets.

[0017] In conjunction with the second aspect, in one implementation, the conversion module sets Gemport mapping rules according to the packet forwarding scenario, and performs the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and the Gemport mapping table to perform packet conversion, including: If the scenario involves forwarding unicast packets between the master and sub-gateways, and each sub-gateway uses only one Gemport, the Gemport mapping rule should be set to independently map each fem ID to the gem ID of all sub-gateways. In the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the VLAN ID of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the gem ID and VLAN ID to find the mapped fem ID for packet conversion.

[0018] In conjunction with the second aspect, in one implementation, the conversion module sets Gemport mapping rules according to the packet forwarding scenario, and performs the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and the Gemport mapping table to perform packet conversion, including: If the scenario involves forwarding unicast packets between the master and sub-gateways, and the sub-gateways map different Gemports based on VLANs, the Gemport mapping rule should be set to map each fem ID to the gem ID of a different sub-gateway based on VLAN. In the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the VLAN ID of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the gem ID and VLAN ID to find the mapped fem ID for packet conversion.

[0019] The beneficial effects of the technical solutions provided in this application include at least the following: The FTTR forwarding method in this application maintains a Gemport mapping table within the main gateway. The Gemport mapping table includes fem id, gem id, and packet VLAN id. fem id is the Gemport id information received by the main gateway from the OLT, and gem is the Gemport id information sent to the sub-gateway after translation by the main gateway. According to the packet forwarding scenario, Gemport mapping rules are set, and according to the Gemport mapping rules and the Gemport mapping table, fem id and gem id are converted in the downlink and uplink directions to perform packet conversion.

[0020] This application maintains a Gemport mapping table within the main gateway. During packet forwarding, the fem id and gem id are looked up in the Gemport mapping table, and Gemport translation is performed to achieve gem frame switching. This reduces multi-level packet conversion, lowers latency, and improves forwarding efficiency. Attached Figure Description

[0021] Figure 1 This is a diagram illustrating traditional FTTR message forwarding. Figure 2 This is a flowchart of an embodiment of the FTTR forwarding method of this application; Figure 3 This is a schematic diagram of FTTR message forwarding in this application; Figure 4 This is the Gemport mapping table in this application; Figure 5 This is a schematic diagram illustrating the forwarding implementation of unicast packets between the master and sub-gateways under the N:1 sub-gateway model in this application. Figure 6 This is the Gemport mapping table for forwarding unicast packets between the master and sub-gateways under the N:1 sub-gateway model in this application. Figure 7 This is a schematic diagram illustrating the forwarding implementation of unicast packets between the master and sub-gateways under the N:P sub-gateway model in this application. Figure 8This is the Gemport mapping table for forwarding unicast packets between the master and sub-gateways under the N:P sub-gateway model in this application. Figure 9 This is a schematic diagram illustrating the implementation of multicast packet forwarding in the master-slave gateway in this application; Figure 10 This is the Gemport mapping table for forwarding multicast packets between the master and sub-gateways in this application; Figure 11 This is a schematic diagram illustrating the forwarding implementation of FMCI / OMCI messages in the master and sub-gateways of this application; Figure 12 This is the Gemport mapping table for FMCI / OMCI messages of the master and sub-gateways in this application; Figure 13 This is a schematic diagram illustrating the message forwarding implementation between different sub-gateways in this application; Figure 14 This is a Gemport mapping table for forwarding messages between different sub-gateways in this application. Figure 15 This is a schematic diagram illustrating the implementation of packet forwarding between the main and sub-gateways in a scenario where the main gateway has multiple downstream PON ports, as described in this application. Figure 16 This application provides a Gemport mapping table for message forwarding between the main and sub-gateways in scenarios where the main gateway has multiple downstream PON ports. Figure 17 This is a schematic diagram illustrating the implementation of packet forwarding between the main and sub-gateways in a scenario where the main gateway has multiple uplink PON ports. Figure 18 For the scenario of multiple uplink PON ports of the main gateway in this application, the Gemport mapping table for packet forwarding of the main and sub-gateways; Figure 19 This is a structural block diagram of an embodiment of the FTTR forwarding device of this application. Detailed Implementation

[0022] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0023] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0024] In a first aspect, embodiments of this application provide an FTTR forwarding method.

[0025] In one embodiment, reference is made toFigure 2 As shown, Figure 2 This is a flowchart illustrating an embodiment of the FTTR forwarding method of this application. Figure 2 As shown, the FTTR forwarding method includes: S1. Maintain a Gemport mapping table in the main gateway. The Gemport mapping table includes fem id, gem id and packet VLAN id. The fem id is the Gemport id information received by the main gateway from the OLT. The gem id is the Gemport id information sent to the sub-gateway after being translated by the main gateway. S2. Based on the packet forwarding scenario, set Gemport mapping rules, and based on the Gemport mapping rules and Gemport mapping table, perform the conversion of fem id and gem id in the downlink and uplink directions to convert packets.

[0026] It is worth noting that Gemport is a logical channel identifier used to carry and distinguish different service flows (such as data, voice, video, and management traffic), and the gem frame is the basic transmission unit that carries user data.

[0027] To address the issue of reduced forwarding efficiency caused by multiple gem and Ethernet frame conversions in the traditional FTTR forwarding model, where packets transition from OLT to MFU (Master Gateway) to SFU (Sub-Gateway), see [reference needed]. Figure 3 As shown, this application defines an optical switching processing module and unit based on gem frame switching. Within the main gateway, data exchange is directly based on gem frames, without performing gem frame -> Ethernet frame -> gem frame conversion. Gem frame conversion is achieved through Gemport translation. Reducing multi-level packet conversion within the main gateway better meets users' requirements for low-latency networks, improves forwarding efficiency, and reduces design costs.

[0028] To implement Gemport translation, the main gateway needs to maintain a Gemport mapping table. For example... Figure 4 As shown, the Gemport mapping table records information such as uplink pon No., fem id, downlink pon No., gem id, vlan id, and aging time.

[0029] Among them, uplink PON No. is the PON number of the main gateway uplink, and downlink PON No. is the PON number of the main gateway downlink; fem id is the Gemport ID information received by the main gateway from the OLT, and gem id is the Gemport ID information sent to the sub-gateway after being transformed by the main gateway; VLAN id is the VLAN ID information of the packet; aging time is the aging time of the table entry. Recording fem id and gem id facilitates the transformation of Gemport ID in uplink and downlink packet forwarding; recording VLAN id increases the accuracy of uplink Gemport reverse table lookup; recording uplink and downlink PON number information facilitates the implementation of forwarding in scenarios with multiple PON ports on the main gateway. The creation and deletion of Gemport mapping table information are mostly related to the Gemport configurations received by the main gateway from the OLT. Each time the main gateway receives a Gemport configuration from the OLT, it generates a corresponding Gemport translation rule for the sub-gateway and saves it to the Gemport mapping table. Conversely, when the OLT deletes a Gemport configuration, the main gateway also deletes the corresponding information in the Gemport mapping table. During the packet forwarding phase, in the downlink direction, the original Gemport ID is parsed, converted to a destination Gemport ID based on the Gemport mapping rules, and the packet VLAN information is recorded. In the uplink direction, the table is looked up in reverse based on the Gemport ID and VLAN information to find the translated Gemport ID, and the packet is then converted.

[0030] Based on the above scheme, the specific implementation schemes for forwarding unicast, multicast, OMCI, and other message scenarios in the master and sub-gateways are as follows: 1) Implementation of unicast packet forwarding between master and sub-gateways in the N:1 sub-gateway model: At this point, each sub-gateway uses only one Gemport, and the Gemport mapping rule is set to independently map each fem id to the gem id of all sub-gateways.

[0031] Specifically, such as Figure 5 As shown, Gemport x / Gemport y is translated into Gemport z_1 for sub-gateway 1, and into Gemport z_2 for sub-gateway 2. The main gateway configures one Gemport for each sub-gateway by default; when the OLT issues a Gemport configuration, it adds a Gemport translation rule to each sub-gateway and saves it to the Gemport mapping table. Conversely, when the OLT deletes the main gateway's Gemport configuration, the main gateway also deletes the corresponding information from its Gemport mapping table. The specific Gemport mapping relationship is as follows: Figure 6As shown. During packet forwarding, in the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the packet's VLAN id is recorded for packet conversion; in the uplink direction, the Gemport mapping table is looked up in reverse based on the gem id and VLAN id to find the mapped fem id for packet conversion.

[0032] 2) Implementation of unicast packet forwarding between master and sub-gateways under the N:P sub-gateway model: At this point, when the sub-gateway maps different Gemports according to VLAN, the Gemport mapping rule is set to map each femid to the gem id of a different sub-gateway according to VLAN.

[0033] Specifically, such as Figure 7 As shown, Gemport x is translated into Gemport x_1 and Gemport x_2 by the main gateway, and then forwards VLAN 30 packets to sub-gateways 1 and 2 respectively. Gemport y is translated into Gemport y_1 and Gemport y_2 by the main gateway, and then forwards VLAN 100 packets to sub-gateways 1 and 2 respectively.

[0034] Each time the OLT issues a Gemport configuration, the main gateway issues a Gemport configuration to each sub-gateway and saves it to the Gemport mapping table. Conversely, when the OLT deletes a Gemport configuration for the main gateway, the main gateway also deletes the corresponding information from the Gemport mapping table. The specific Gemport mapping relationship is as follows: Figure 8 As shown. During packet forwarding, in the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the packet's VLAN id is recorded for packet conversion; in the uplink direction, the Gemport mapping table is looked up in reverse based on the gem id and VLAN id to find the mapped fem id for packet conversion.

[0035] 3) Implementation of multicast packet forwarding in master and slave gateways: At this point, the Gemport mapping rule is set to map the multicast fem ID to a single multicast gem ID and broadcast it to all sub-gateways.

[0036] Specifically, such as Figure 9 As shown, when the OLT sends a multicast Gemport configuration to the main gateway, the main gateway will send a multicast Gemport configuration to the sub-gateways. Conversely, when a Gemport deletes a configuration from the main gateway, the main gateway will also delete the corresponding information from its Gemport mapping table. The specific Gemport mapping relationship is as follows: Figure 10As shown. During message forwarding, uplink multicast protocol messages use the unicast Gemport channel, which is implemented in the same way as uplink unicast message forwarding, as described in schemes 1) and 2). Downlink multicast data messages share a single multicast Gemport channel, and the Gemport mapping table is consulted for Gemport translation, converting fem id to gem id.

[0037] 4) Implementation of FMCI / OMCI message forwarding in master and slave gateways: like Figure 11 As shown, after a sub-gateway comes online normally, the main gateway assigns a Gemport channel to each sub-gateway for OMCI message exchange between the main and sub-gateways. In this scenario, the creation and forwarding of Gemport channels are independent of the OLT configuration, ensuring that sub-gateways can still be authorized normally even if the main gateway is not registered. When the main gateway assigns a Gemport to a sub-gateway, it creates Gemport mapping information in the Gemport mapping table; conversely, it deletes the corresponding information. The Gemport mapping relationship is as follows: Figure 12 As shown, it is worth noting that in this scenario, Gemport translation is not required. The Gemport channel is only used for forwarding fmci / omci messages between the master and sub-gateways, so there is no uplink PON port, fem ID, or other information.

[0038] 5) Packet forwarding between different sub-gateways: like Figure 13 As shown, within the main gateway, the Gemport mapping table is consulted for forwarding, allowing only packets from the same VLAN domain to communicate. The Gemport mapping relationship is as follows: Figure 14 As shown, the specific mapping relationship is the same as in scenarios 1) and 2).

[0039] 6) In scenarios where the main gateway has multiple downstream PON ports, the packet forwarding implementation for the main and sub-gateways is as follows: like Figure 15 As shown, sub-gateway 1 and sub-gateway 2 are connected to the main gateway's downstream PON 1 and downstream PON 2 ports, respectively. When the main gateway creates Gemport mapping information for the sub-gateways, it needs to distinguish between different PON ports. The remaining forwarding implementation is similar to the single downstream PON port scenario. The specific Gemport mapping relationship is as follows: Figure 16 As shown, both uplink and downlink packet forwarding are based on the Gemport mapping table to complete the Gemport translation of the packets.

[0040] 7) In scenarios where the main gateway has multiple uplink PON ports, the main and sub-gateway packet forwarding is implemented as follows: like Figure 17As shown, the main gateway has two uplink PON ports. The OLT sends different Gemport channels to the two PON ports of the main gateway. When the main gateway creates Gemport mapping information for the sub-gateways, it needs to distinguish between the different uplink PON ports. The rest of the forwarding implementation is similar to the single uplink PON port scenario. Taking the N:1 sub-gateway model as an example, the specific Gemport mapping relationship is as follows: Figure 18 As shown, both uplink and downlink packet forwarding are based on the Gemport mapping table to complete the Gemport translation of the packets.

[0041] In summary, the FTTR forwarding method in this application maintains a Gemport mapping table within the main gateway. This table includes fem id, gem id, and packet VLAN id. The fem id is the Gemport id information received by the main gateway from the OLT, and the gem id is the Gemport id information sent to the sub-gateway after translation by the main gateway. Based on the packet forwarding scenario, Gemport mapping rules are set. According to these rules and the Gemport mapping table, fem id and gem id are converted in both downlink and uplink directions to perform packet conversion.

[0042] This application maintains a Gemport mapping table within the main gateway. During packet forwarding, the fem id and gem id are looked up in the Gemport mapping table, and Gemport translation is performed to achieve gem frame switching. This reduces multi-level packet conversion, lowers latency, and improves forwarding efficiency.

[0043] Secondly, embodiments of this application provide an FTTR forwarding device.

[0044] In one embodiment, reference is made to Figure 19 As shown, Figure 19 This is a structural block diagram of an embodiment of the FTTR forwarding device of this application. Figure 19 As shown, the FTTR forwarding device includes: The maintenance module is used to maintain a Gemport mapping table in the main gateway. The Gemport mapping table includes femid, gem id and packet VLAN id. The fem id is the Gemport id information received by the main gateway from the OLT. The gem is the Gemport id information sent to the sub-gateway after being translated by the main gateway. The conversion module sets Gemport mapping rules according to the packet forwarding scenario, and performs the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and Gemport mapping table to convert the packets.

[0045] Further, in one embodiment, the conversion module sets Gemport mapping rules according to the packet forwarding scenario, and performs the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and the Gemport mapping table to perform packet conversion, including: If the scenario involves forwarding unicast packets between the master and sub-gateways, and each sub-gateway uses only one Gemport, the Gemport mapping rule should be set to independently map each fem ID to the gem ID of all sub-gateways. In the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the VLAN ID of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the gem ID and VLAN ID to find the mapped fem ID for packet conversion.

[0046] Further, in one embodiment, the conversion module sets Gemport mapping rules according to the packet forwarding scenario, and performs the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and the Gemport mapping table to perform packet conversion, including: If the scenario involves forwarding unicast packets between the master and sub-gateways, and the sub-gateways map different Gemports based on VLANs, the Gemport mapping rule should be set to map each fem ID to the gem ID of a different sub-gateway based on VLAN. In the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the VLAN ID of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the gem ID and VLAN ID to find the mapped fem ID for packet conversion.

[0047] Further, in one embodiment, the conversion module sets Gemport mapping rules according to the packet forwarding scenario, and performs the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and the Gemport mapping table to perform packet conversion, including: If it is a scenario of forwarding multicast packets between the master and sub-gateways, set the Gemport mapping rule to map the multicast fem id to a single multicast gem id and broadcast it to all sub-gateways; In the downlink direction, the multicast fem ID is parsed, converted into a shared multicast gem ID based on the Gemport mapping rules, and the VLAN ID of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the multicast gem ID and VLAN ID to find the mapped multicast fem ID for packet conversion.

[0048] Furthermore, in one embodiment, when the OLT issues or deletes a Gemport configuration, the main gateway correspondingly adds or deletes information in the corresponding Gemport mapping table.

[0049] Furthermore, in one embodiment, the Gemport mapping table also includes downstream PON port number information; When the main gateway has multiple downstream PON ports, different downstream PON ports are distinguished in the Gemport mapping table by the downstream PON port number information.

[0050] Furthermore, in one embodiment, when the main gateway is a scenario with multiple downstream PON ports, distinguishing different downstream PON ports in the Gemport mapping table using downstream PON port number information includes: Add a "downlink pon No." field to the Gemport mapping table to distinguish different downlink pon ports based on the table entry number in the "downlink pon No." field.

[0051] Furthermore, in one embodiment, the Gemport mapping table also includes upstream PON port number information; When the main gateway has multiple uplink PON ports, different uplink PON ports are distinguished in the Gemport mapping table by the uplink PON port number information.

[0052] Furthermore, in one embodiment, when the main gateway has multiple uplink PON ports, distinguishing different uplink PON ports in the Gemport mapping table using the uplink PON port number information includes: Add an uplink pon No. field to the Gemport mapping table to distinguish different uplink pon ports based on the table entry number in the uplink pon No. field.

[0053] Furthermore, in one embodiment, the Gemport mapping table also includes aging time information; when the aging time is reached, the Gemport mapping table is deleted.

[0054] The functions of each module in the FTTR forwarding device correspond to the steps in the FTTR forwarding method embodiment, and their functions and implementation processes will not be described in detail here.

[0055] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0056] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.

[0057] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.

[0058] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0059] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.

[0060] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.

[0061] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. An FTTR forwarding method, characterized in that, The FTTR forwarding method includes: The main gateway maintains a Gemport mapping table, which includes fem id, gem id and packet VLAN id. The fem id is the Gemport id information received by the main gateway from the OLT, and the gem id is the Gemport id information sent to the sub-gateway after being translated by the main gateway. Based on the packet forwarding scenario, Gemport mapping rules are set. According to the Gemport mapping rules and Gemport mapping table, the fem id and gem id are converted in the downlink and uplink directions to perform packet conversion.

2. The FTTR forwarding method as described in claim 1, characterized in that, The step of setting Gemport mapping rules according to the packet forwarding scenario, and converting the fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and the Gemport mapping table to perform packet conversion, includes: If the scenario involves forwarding unicast packets between the master and sub-gateways, and each sub-gateway uses only one Gemport, the Gemport mapping rule should be set to independently map each fem ID to the gem ID of all sub-gateways. In the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the VLAN id of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the gem ID and VLAN ID to find the mapped fem ID for packet conversion.

3. The FTTR forwarding method as described in claim 1, characterized in that, The step of setting Gemport mapping rules according to the packet forwarding scenario, and converting the fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and the Gemport mapping table to perform packet conversion, includes: If the scenario involves forwarding unicast packets between the master and sub-gateways, and the sub-gateways map different Gemports based on VLANs, the Gemport mapping rule should be set to map each fem ID to the gem ID of a different sub-gateway based on VLAN. In the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the VLAN id of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the gem ID and VLAN ID to find the mapped fem ID for packet conversion.

4. The FTTR forwarding method as described in claim 1, characterized in that, The step of setting Gemport mapping rules according to the packet forwarding scenario, and converting the fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and the Gemport mapping table to perform packet conversion, includes: If it is a scenario of forwarding multicast packets between the master and sub-gateways, set the Gemport mapping rule to map the multicast fem id to a single multicast gem id and broadcast it to all sub-gateways; In the downlink direction, the multicast fem ID is parsed, converted into a shared multicast gem ID based on the Gemport mapping rules, and the VLAN ID of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the multicast gem ID and VLAN ID to find the mapped multicast femid for packet conversion.

5. The FTTR forwarding method as described in any one of claims 1 to 4, characterized in that: When the OLT issues or deletes a Gemport configuration, the main gateway adds or deletes the corresponding information in the Gemport mapping table.

6. The FTTR forwarding method as described in any one of claims 1 to 4, characterized in that: The Gemport mapping table also includes downstream PON port number information; When the main gateway has multiple downstream PON ports, different downstream PON ports are distinguished in the Gemport mapping table by the downstream PON port number information.

7. The FTTR forwarding method as described in claim 6, characterized in that: When the main gateway has multiple downstream PON ports, the Gemport mapping table distinguishes different downstream PON ports by their downstream PON port numbers, including: Add a "downlink pon No." field to the Gemport mapping table to distinguish different downlink pon ports based on the table entry number in the "downlink pon No." field.

8. The FTTR forwarding method as described in any one of claims 1 to 4, characterized in that: The Gemport mapping table also includes the upstream PON port number information; When the main gateway has multiple uplink PON ports, different uplink PON ports are distinguished in the Gemport mapping table by the uplink PON port number information.

9. The FTTR forwarding method as described in claim 8, characterized in that: When the main gateway has multiple uplink PON ports, the Gemport mapping table distinguishes different uplink PON ports by their uplink PON port numbers, including: Add an uplink pon No. field to the Gemport mapping table to distinguish different uplink pon ports based on the table entry number in the uplink pon No. field.

10. The FTTR forwarding method as described in claim 1, characterized in that: The Gemport mapping table also includes aging time information. When the aging time is reached, the Gemport mapping table is deleted.

11. An FTTR forwarding device, characterized in that, The FTTR forwarding device includes: The maintenance module is used to maintain a Gemport mapping table in the main gateway. The Gemport mapping table includes fem id, gem id and packet VLAN id. The fem id is the Gemport id information received by the main gateway from the OLT. The gem id is the Gemport id information sent to the sub-gateway after being translated by the main gateway. The conversion module sets Gemport mapping rules according to the packet forwarding scenario, and performs the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and Gemport mapping table to convert the packets.

12. The FTTR forwarding device as claimed in claim 11, characterized in that, The conversion module sets Gemport mapping rules according to the packet forwarding scenario, and performs the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and Gemport mapping table to convert the packets, including: If the scenario involves forwarding unicast packets between the master and sub-gateways, and each sub-gateway uses only one Gemport, the Gemport mapping rule should be set to independently map each fem ID to the gem ID of all sub-gateways. In the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the VLAN id of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the gem ID and VLAN ID to find the mapped fem ID for packet conversion.

13. The FTTR forwarding device as described in claim 11, characterized in that, The conversion module sets Gemport mapping rules according to the packet forwarding scenario, and performs the conversion of fem id and gem id in the downlink and uplink directions according to the Gemport mapping rules and Gemport mapping table to convert the packets, including: If the scenario involves forwarding unicast packets between the master and sub-gateways, and the sub-gateways map different Gemports based on VLANs, the Gemport mapping rule should be set to map each fem ID to the gem ID of a different sub-gateway based on VLAN. In the downlink direction, the fem id is parsed, converted into a gem id based on the Gemport mapping rules, and the VLAN id of the packet is recorded for packet conversion. In the uplink direction, the Gemport mapping table is looked up in reverse based on the gem ID and VLAN ID to find the mapped fem ID for packet conversion.

Images