Management control message transmission method and master device

Abstract

The embodiment of the invention provides a management control message transmission method and master equipment, and the method comprises the steps: receiving a first message carrying a management control message and a first port identifier from first equipment, and determining a second port identifier according to the first port identifier, and sending a second message carrying the second port identifier and the management control message to the second device. According to the embodiment of the invention, relay forwarding of the management control message between the optical line terminal and the FTTR slave equipment can be realized at the master equipment, so that the problem that the FTTH OLT cannot directly manage or transparently manage the FTTR SFU in the related technology is solved.

Description

Technical Field

[0001] This application relates to the fields of passive optical networks and fiber in-premise networks (FINs), and more specifically, to a method for transmitting management and control messages and a master device thereof. Background Technology

[0002] With the continuous development of communication technology, Fiber to the Room (FTTR) is gradually entering the stage of large-scale deployment, and standardization is also maturing. FTTR is similar to Fiber to the Home (FTTH) in that it adopts a point-to-multipoint network topology, consisting of a main Fibre Unit (MFU) connected to multiple sub-fibre units (SFU) through an indoor optical distribution network (IFDN). FTTH, on the other hand, consists of an optical line terminal (OLT) connected to multiple optical network units (ONUs) through an optical distribution network (ODN). Figure 1 The diagram illustrates the architecture of FTTH and FTTR networks, as shown below. Figure 1 As shown, when FTTH and FTTR networks are networked together, the FTTH ONU is replaced as the master device, and logically the master device consists of an ONU and an MFU.

[0003] In current network applications, FTTR and FTTH networks are logically two independent networks. FTTH OLT and FTTH ONU manage each other through ONU Management and Control Interface (OMCI) messages, and FTTR SFU and FTTR SFU also manage each other through a similar Fiber Management and Control Interface (FMCI). However, OMCI and FMCI are independent of each other. Therefore, seamless collaboration between FTTH and FTTR networks cannot be achieved in network management, nor can FTTH OLT achieve transparent or direct management of FTTR SFU, which is not conducive to unified management by operators.

[0004] In summary, there is still no good solution to the above-mentioned technical problems. Summary of the Invention

[0005] This application provides a method for transmitting management control messages and a master device to at least solve the problem in related technologies that FTTH OLTs cannot directly or transparently manage FTTR SFUs.

[0006] According to one embodiment of this application, a method for transmitting management control messages is provided, applied to a master device. The method includes: receiving a first message carrying a management control message and a first port identifier from a first device; determining a second port identifier based on the first port identifier; and sending a second message carrying the second port identifier and the management control message to a second device; wherein the first device is an optical line terminal and the second device is an FTTR slave device; or, the first device is an FTTR slave device and the second device is an optical line terminal.

[0007] According to another embodiment of this application, a method for transmitting management control messages is provided, applied to an optical line terminal (OLT). The method includes: sending a third message carrying a management control message and a third port identifier to a master device, so that the master device sends a fourth message carrying a management control message and a fourth port identifier to an FTTR slave device, wherein the fourth port identifier is determined based on the third port identifier; or receiving a third message from the master device, wherein the third message is determined by the master device based on the fourth message received from the FTTR slave device.

[0008] According to another embodiment of this application, a master device is provided, including: an optical network relay module, configured to receive a first message carrying a management control message and a first port identifier from a first device, determine a second port identifier based on the first port identifier, and send a second message carrying the second port identifier and management control message to a second device; wherein, the first device is an optical line terminal and the second device is an FTTR slave device; or, the first device is an FTTR slave device and the second device is an optical line terminal.

[0009] According to yet another embodiment of this application, a computer-readable storage medium is also provided, which stores a computer program, wherein the computer program is executed by a processor to perform the steps in any of the above method embodiments.

[0010] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0011] According to yet another embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0012] In this embodiment, the master device establishes a transparent forwarding channel between the optical line terminal and the FTTR slave device, enabling the relay forwarding of management and control messages between the master device and the FTTR slave device. This solves the problem in related technologies where the FTTH OLT cannot directly or transparently manage the FTTR SFU, thus integrating the FTTR network and the FTTH network into a single entity. This achieves a logically integrated network of FTTH and FTTR. Logically, the slave device and the master device belong to the ONU under the OLT. The FTTR is an extension of the FTTH. The FTTH OLT can directly manage the FTTR slave device, and the FTTR slave device can also directly report information to the FTTH OLT, logically forming a passive optical network where FTTH and FTTR cooperate with each other. Attached Figure Description

[0013] Figure 1 This is a schematic diagram of the architecture of FTTH and FTTR networks;

[0014] Figure 2 This is a flowchart of a method for transmitting management control messages according to an embodiment of this application;

[0015] Figure 3 This is a flowchart of a method for transmitting management and control messages of an optical line terminal according to an embodiment of this application;

[0016] Figure 4 This is a flowchart of a method for transmitting management and control messages of an optical line terminal in another embodiment of this application;

[0017] Figure 5 This is a schematic diagram illustrating the process of allocating ONU-ID and SFU-ID from a device in one embodiment of this application;

[0018] Figure 6 This is a schematic diagram illustrating the process of allocating ONU-ID and SFU-ID from the device in another embodiment of this application;

[0019] Figure 7 This is a schematic diagram of the encapsulation format of the XGEM frame in the XG-PON standard of the FTTH segment in this application embodiment;

[0020] Figure 8 This is a schematic diagram of the encapsulation format of the G.fin FEM frame in the FTTR segment of this application embodiment;

[0021] Figure 9 This is a schematic diagram of the structure of the message type field in the embodiments of this application;

[0022] Figure 10 This is a schematic diagram of the main device in one embodiment of this application (I);

[0023] Figure 11 This is a schematic diagram (II) of the main device in one embodiment of this application;

[0024] Figure 12 This is a schematic diagram (iii) of the main device in one embodiment of this application;

[0025] Figure 13 This is a schematic diagram (four) of the main device in one embodiment of this application. Detailed Implementation

[0026] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0028] In FTTH systems, when assigning an Optical Network Unit (ONU-ID) to an Optical Network Unit (ONU), the Optical Line Terminal (OLT) automatically assigns a GEM Port-ID, which is equivalent to the ONU-ID, to the ONU. This GEM Port-ID carries OMCI messages between the OLT and the ONU, forming a GEM frame. Simultaneously, the GEM Port-ID also indicates the management and control channel between the OLT and the ONU used to transmit OMCI messages. On the receiving side, both the OLT and the ONU identify the port-ID in the GEM frame to determine if it is an OMCI message and whether the OMCI message has been received or from which ONU. Alternatively, GEM can also be a 10-Gigabit Passive Optical Network (XG-PON) Encapsulation Method (XGEM).

[0029] In an FTTR system, when assigning a SFU-ID to a slave device, the master device automatically assigns a FEM Port-ID (Fiber In-premises Network, FIN Encapsulation Method, or FEM) port identifier, equivalent to the SFU-ID, to the slave device. This FEM Port-ID carries FMCI messages between the master and slave devices, forming FEM frames. Simultaneously, this FEM Port-ID also indicates the management and control channel used for transmitting FMCI messages between the master and slave devices. As the receiving side, both the master and slave devices identify this port identifier in the FEM frame to determine if it is an FMCI message and whether the FMCI message has been received, or from which slave device it originated. The FTTR system also supports wireless collaboration between the MFU and SFU via the Wireless Management and Control Interface (WMCI). The FEM Port-ID carrying the WMCI can be the same as the FMCI FEM Port-ID or other FEM Port-IDs.

[0030] Since FTTH and FTTR are logically two independent systems, the allocation of ONU-ID and SFU-ID is independent of each other. This leads to possible overlap or duplication of the values ​​of ONU-ID and SFU-ID. Consequently, the GEM / FEM Port-ID carrying OMCI or FMCI / WMCI also overlaps or duplicates. This makes it impossible for the receiving side to determine whether an OMCI or FMCI / WMCI message has been received, or to determine where the OMCI / FMCI / WMCI message came from. Therefore, transparent forwarding of OMCI / FMCI / WMCI messages cannot be achieved.

[0031] In this embodiment, the master device establishes a transparent forwarding channel between the optical line terminal and the FTTR slave device, enabling the relay forwarding of management and control messages between the master device and the FTTR slave device. This solves the problem in related technologies where the FTTH OLT cannot directly or transparently manage the FTTR SFU, thus integrating the FTTR network and the FTTH network into a single entity. This achieves a logically integrated network of FTTH and FTTR. Logically, the slave device and the master device belong to the ONU under the OLT. The FTTR is an extension of the FTTH. The FTTH OLT can directly manage the FTTR slave device, and the FTTR slave device can also directly report information to the FTTH OLT, logically forming a passive optical network where FTTH and FTTR cooperate with each other.

[0032] According to one embodiment of this application, a method for transmitting management control messages is provided, applied to a master device.

[0033] Figure 2 This is a flowchart of a method for transmitting management control messages according to an embodiment of this application, as shown below. Figure 2 As shown, the method includes the following steps:

[0034] Step S202: Receive a first message from the first device carrying a management control message and a first port identifier;

[0035] Step S204: Determine the second port identifier based on the first port identifier;

[0036] Step S206: Send a second message carrying a second port identifier and management control messages to the second device.

[0037] In this embodiment, the first port identifier is used to indicate the first management control channel between the first device and the master device for transmitting the first message, and the second port identifier is used to indicate the second management control channel between the second device and the master device for transmitting the second message.

[0038] In this embodiment, management control messages are transmitted directly / transparently between the FTTH OLT and the FTTR SFU. In the downlink direction, the first device is an optical line terminal (FTTH OLT), and the second device is an FTTR slave device; in the uplink direction, the first device is an FTTR slave device, and the second device is an optical line terminal. In the FTTH segment, the FTTH OLT can determine which master device (processed or transparently forwarded by it) the management control message is sent to, and also which master device (sent or transparently forwarded by it) the management control message originates from, by using the first / second port identifier. In the FTTR segment, the master device can determine which FTTR SFU the management control message is sent to, and also which FTTR SFU the management control message originates from, by using the first / second port identifier.

[0039] In this embodiment of the application, through the above steps S202 to S206, the master device can directly forward the management and control messages of the FTTR network to the FTTH network, and can also directly forward the management and control messages of the FTTH network to the FTTR network. This solves the problem in the related technology that the FTTH OLT cannot directly manage or transparently manage the FTTR SFU, and integrates the FTTR network and the FTTH network into a whole, realizing the logical integration of FTTH and FTTR networking.

[0040] In this embodiment, the passive optical network architecture consists of an FTTH network and an FTTR network. The network can contain multiple optical line terminals (OLTs), each OLT connected to multiple FTTR master devices, and each FTTR master device connected to multiple FTTR slave devices. The master device also determines whether the management and control message is destined for or originates from its connected slave devices based on the port identifier of the message. If not, the message is discarded; if so, the corresponding relay forwarding process is executed.

[0041] In some embodiments, management and control messages include at least one of the following: Optical Network Unit Management and Control Interface (OMCI) messages, Fiber Management and Control Interface (FMCI) messages, and Wireless Management and Control Interface (WMCI) messages. Other types of messages can also be transparently forwarded between FTTH and FTTR using the methods in the embodiments of this application, and this application does not impose any limitations on this.

[0042] In one exemplary embodiment, the channel between the optical line terminal and the master device is an FTTH segment OMCI channel. The channel between the master device and the FTTR slave device is an FTTR segment FMCI channel or an FTTR segment WMCI channel.

[0043] In some embodiments, the first port identifier is assigned along with the optical network unit identifier, the second port identifier is assigned along with the slave device identifier, the first port identifier is equivalent to the ONU-ID, and the second port identifier is equivalent to the SFU-ID; in other embodiments, the first port identifier is assigned along with the slave device identifier, the second port identifier is assigned along with the optical network unit identifier, the first port identifier is equivalent to the SFU-ID, and the second port identifier is equivalent to the ONU-ID.

[0044] In other embodiments, the first port identifier can be assigned independently, without relying on the optical network unit identifier or SFU-ID, and the second port identifier can also be assigned independently, without relying on the optical network unit identifier or SFU-ID.

[0045] In some embodiments, the first port identifier is the same as the second port identifier; or, the first port identifier is different from the second port identifier, but there is a preset port identifier mapping relationship between them. Furthermore, the port identifier mapping relationship can be configured by the OLT, through PLOAM messages or OMCI, and each master gateway has a corresponding mapping relationship.

[0046] In some embodiments, step S204 may specifically include: using the first port identifier as the second port identifier, or in other words, the second port identifier being equivalent to the first port identifier; or, determining the second port identifier based on the first port identifier and a pre-established identifier mapping relationship, wherein the identifier mapping relationship is a mapping relationship between the first port identifier and the second port identifier.

[0047] Specifically, the identifier mapping relationship can be a mapping relationship between optical network unit identifier and slave device identifier. If the first port identifier is equal to the optical network unit identifier, the corresponding slave device identifier can be determined according to the identifier mapping relationship, and then the second port identifier, which is equal to the slave device identifier, can be determined.

[0048] In one exemplary embodiment, the same Port-ID can be used to identify the FTTH segment OMCI channel and the FTTR segment FMCI channel in an integrated FTTH+FTTR system. The FTTR MFU, FTTR SFU, and FTTH ONU share the ONU-ID value field of the FTTH PON port / OLT for allocating ONU-ID and SFU-ID. That is, the ONU-ID of each FTTR MFU, the SFU-ID of each FTTR SFU, and the ONU-ID of each FTTH ONU are unique and distinct from each other in the FTTH+FTTR system. Correspondingly, according to the standard, the GEM / FEM Port-ID / XGEMPort-ID used to carry OMCI / FMCI, which are equivalent to the ONU-ID / SFU-ID, are also unique and distinct from each other.

[0049] In the downlink direction, the FTTH OLT encapsulates and sends the OMCI message using the port-ID of the FTTR SFU. The downlink broadcast is sent to the FTTR MFU, and the FTTR MFU connected to the FTTR SFU will forward the OMCI message. The forwarding principle is that the FTTR MFU checks that the SFU corresponding to the port-ID carrying the OMCI is connected to the FTTR MFU.

[0050] In the uplink direction, the FTTR SFU encapsulates the FMCI message with the Port-ID and sends it to the FTTR MFU. The FTTR MFU forwards the FMCI message to the FTTH OLT. The forwarding principle is that the FTTH OLT is configured to forward the uplink FMCI message of the SFU to the uplink instead of processing it locally.

[0051] In one exemplary embodiment, different Port-IDs can be used to identify the OMCI channel in the FTTH segment and the FMCI channel in the FTTR segment within an integrated FTTH+FTTR system. Because the SFU-ID value range in the FTTR segment is relatively small, it may not be possible to assign a unique ONU-ID to an SFU under the entire OLTPON port. Therefore, based on the previous exemplary embodiment, the master device can obtain the ONU-ID assigned to the SFU by the OLT and assign a different SFU-ID locally to the SFU, associating the ONU-ID and SFU-ID for the master device to perform uplink and downlink conversion.

[0052] In another exemplary embodiment, the same Port-ID can also be used to identify the FTTH segment OMCI channel and the FTTR segment WMCI channel in the integrated FTTH+FTTR system. The WMCI uses the same Port-ID for transmission as the FMCI, and the method is the same as when the OMCI channel and the FMCI channel use the same Port-ID.

[0053] In another exemplary embodiment, different Port-IDs can be used to identify the OMCI channel in the FTTH segment and the WMCI channel in the FTTR segment within the integrated FTTH+FTTR system. Different Port-IDs are assigned to the FTTH and FTTR segments, an association is established between the two Port-IDs at the master device, and the conversion is performed when forwarding WMCI messages.

[0054] In some embodiments, the method further includes the following steps:

[0055] Step S2002: Determine the optical network unit identifier of the FTTR slave device, wherein the FTTR slave device has a unique slave device serial number;

[0056] Step S2004: Assign the slave device identifier to the FTTR slave device, wherein the optical network unit identifier is the same as or different from the slave device identifier;

[0057] Step S2006: If the optical network unit identifier and the slave device identifier are different, establish the identifier mapping relationship between the optical network unit identifier and the slave device identifier corresponding to the same slave device serial number.

[0058] In some embodiments, the slave device identifier or optical network unit identifier of the slave device can be assigned by the master device or directly by the optical line terminal.

[0059] Specifically, step S2002, which determines the optical network unit identifier of the FTTR slave device, may include: obtaining the optical network unit identifier assigned to the FTTR slave device by the optical line terminal; or, obtaining a pre-assigned optical network unit identifier from the optical line terminal and assigning the optical network unit identifier to the FTTR slave device from the pre-assigned optical network unit identifier.

[0060] In this embodiment, the pre-assigned optical network unit identifier can be understood as an optional range of identifier allocation. The pre-assigned optical network unit identifier and the FTTR slave device do not have a corresponding relationship. The master device still needs to assign the identifier to a certain FTTR slave device to establish a corresponding relationship. The FTTR slave device is indicated by a unique slave device serial number.

[0061] In some embodiments, if the optical network unit identifier is assigned by an optical line terminal (OLT), obtaining the optical network unit identifier assigned by the OLT to the FTTR slave device can be achieved through the following steps:

[0062] Step S2002A: Send the slave device serial number to the optical line terminal and receive the optical network unit identifier from the optical line terminal, wherein the optical network unit identifier is assigned by the optical line terminal to the FTTR slave device corresponding to the slave device serial number.

[0063] In some embodiments, the optical line terminal (OLT) can directly assign an ONU-ID to the FTTR slave device, or it can assign an ONU-ID based on an unassigned ONU-ID reported by the master device. Specifically, if the assignment is based on an unassigned ONU-ID, step S2002A may further include: sending the slave device serial number and an unassigned optical network unit identifier to the OLT, and receiving the optical network unit identifier from the OLT, wherein the optical network unit identifier is assigned by the OLT to the FTTR slave device corresponding to the slave device serial number from the unassigned optical network unit identifiers.

[0064] In some embodiments, if the optical network unit identifier is assigned by the master device, obtaining a pre-assigned optical network unit identifier from the optical line terminal and assigning the optical network unit identifier to the FTTR slave device from the pre-assigned optical network unit identifier can be achieved through the following steps:

[0065] Step S2002B: Obtain the pre-allocated optical network unit identifier from the optical line terminal, and allocate the optical network unit identifier to the FTTR slave device corresponding to the slave device serial number from the pre-allocated optical network unit identifier.

[0066] In some embodiments, if the optical network unit identifier is assigned by the master device, then after obtaining the pre-assigned optical network unit identifier from the optical line terminal and assigning the optical network unit identifier to the FTTR slave device from the pre-assigned optical network unit identifier, the method further includes: sending the correspondence between the slave device serial number and the optical network unit identifier to the optical line terminal.

[0067] In some embodiments, after assigning the slave device identifier to the FTTR slave device in step S2004, the method further includes the following step: step S2005, sending the slave device identifier to the FTTR slave device corresponding to the slave device serial number.

[0068] In some embodiments, before assigning the slave device identifier to the FTTR slave device in step S2004, the method further includes the following steps:

[0069] Step S2003-2: Send a serial number request to the FTTR slave device;

[0070] Step S2003-4: Receive a serial number response carrying the serial number of the slave device from the FTTR slave device.

[0071] In this embodiment, the master device first needs to obtain the slave device serial number from the FTTR slave device, and then assign a slave device identifier to the FTTR slave device corresponding to the slave device serial number. The slave device serial number can be obtained through a serial number request and the corresponding serial number response.

[0072] In some embodiments, the first message is a service encapsulation frame encapsulated according to a preset first standard, and the second message is a service encapsulation frame encapsulated according to a preset second standard, wherein the first port identifier or the second port identifier is located in the port identifier field of the service encapsulation frame, and the management control message is located in the payload of the service encapsulation frame.

[0073] In this embodiment, the master device does not need to parse the specific content of the management control message. It only needs to obtain the port identifier in the first message, and convert the port identifiers of the FTTR segment and FTTH segment according to the identifier mapping relationship. The converted port identifier and management control message are then re-encapsulated into the second message, thereby realizing transparent forwarding of the management control message.

[0074] In some embodiments, the preset first standard or the preset second standard includes at least one of the following: GPON standard, symmetrical GPON standard, XG-PON standard, XGS-PON standard, 50G-PON standard, G.fin standard, and FTTR standard, wherein the FTTR standard can be the FTTR standard specified by the China Communications Standards Association (CCSA). Correspondingly, the service encapsulation frame can include GEM frames, XGEM frames, FEM frames, etc.

[0075] In this embodiment, the master device establishes an OMCI / FMCI forwarding channel for the OLT and the slave device. This enables the OLT of FTTH to directly manage the slave device of FTTR through OMCI. FMCI can reuse the original OMCI and be extended on the basis of OMCI as needed. There are no restrictions on the FTTH and FTTR standards. Whether FTTH and FTTR are of the same standard or different standards, the OLT can directly or transparently manage the slave device or FTTR SFU through OMCI.

[0076] In some embodiments, the method further includes the following steps:

[0077] Step S203: Determine whether the management control message is a relay message between the FTTH network and the FTTR network based on the message type field carried in the management control message and / or based on the managed entity (ME) attribute field; wherein the message type field includes a relay enable field (RE), and / or the managed entity attribute field includes an optical network unit management and control channel (OMCC) relay attribute field.

[0078] In this embodiment, the master device can selectively control whether to relay management control messages and whether the master device needs to process management control messages locally. This allows for integrated control of FTTR and FTTH, as well as separate control of FTTR or FTTH, enabling more flexible management control in passive optical network architectures. While the data encapsulation formats of different standards may vary, enabling and controlling the relay and transparent forwarding functions of management control messages can be achieved by adding or extending reserved fields.

[0079] In this embodiment, the master device establishes a transparent forwarding channel between the optical line terminal and the FTTR slave device, enabling the relay forwarding of management and control messages between the master device and the FTTR slave device. This solves the problem in related technologies where the FTTH OLT cannot directly or transparently manage the FTTR SFU, thus integrating the FTTR network and the FTTH network into a single entity. This achieves a logically integrated network of FTTH and FTTR. Logically, the slave device and the master device belong to the ONU under the OLT. The FTTR is an extension of the FTTH. The FTTH OLT can directly manage the FTTR slave device, and the FTTR slave device can also directly report information to the FTTH OLT, logically forming a passive optical network where FTTH and FTTR cooperate with each other.

[0080] According to another embodiment of this application, a method for transmitting management control messages is provided, which is applied to an optical line terminal.

[0081] Figure 3 This is a flowchart of a method for transmitting management and control messages of an optical line terminal according to an embodiment of this application, as follows: Figure 3 As shown, the process includes the following steps:

[0082] Step S302A: Send a third message carrying a management control message and a third port identifier to the master device, so that the master device sends a fourth message carrying the management control message and a fourth port identifier to the FTTR slave device.

[0083] In this embodiment, in the downlink direction, the fourth port identifier is determined based on the third port identifier.

[0084] In this embodiment, the third port identifier is used to indicate the third management and control channel between the optical line terminal and the master device for transmitting the third message, and the fourth port identifier is used to indicate the fourth management and control channel between the master device and the FTTR slave device for transmitting the fourth message.

[0085] In this embodiment, the third port identifier is assigned along with the optical network unit identifier, and the third port identifier is equal to the optical network unit identifier, or it can be assigned independently. The fourth port identifier is assigned along with the slave device identifier, and the fourth port identifier is equal to the slave device identifier, or it can be assigned independently.

[0086] Through the embodiments of this application, the optical line terminal can send management and control messages to the master device, and then the master device can pass the management and control messages through to the FTTR slave device, thereby realizing the direct control of the FTTR slave device by the optical line terminal.

[0087] Figure 4This is a flowchart of a method for transmitting management and control messages of an optical line terminal in another embodiment of this application, as shown below. Figure 4 As shown, the process includes the following steps:

[0088] Step S302B: Receive a third message from the master device carrying management control messages and a third port identifier.

[0089] In this embodiment, in the uplink direction, the third message is determined by the master device based on the fourth message received from the FTTR slave device. The fourth message carries the management control message and the fourth port identifier, and the third port identifier is determined based on the fourth port identifier.

[0090] In this embodiment, the third port identifier is used for the third management and control channel between the optical line terminal and the master device, and the fourth port identifier is used for the fourth management and control channel between the master device and the FTTR slave device.

[0091] In this embodiment, the third port identifier is assigned along with the optical network unit identifier, and the third port identifier is equal to the optical network unit identifier, or it can be assigned independently. The fourth port identifier is assigned along with the slave device identifier, and the fourth port identifier is equal to the slave device identifier, or it can be assigned independently.

[0092] In this embodiment, if the optical network unit identifier of the FTTH segment and the slave device identifier of the FTTR segment are the same, then in the uplink direction, the master device can directly encapsulate the fourth port identifier as the third port identifier into the third message; in the downlink direction, the master device can directly encapsulate the third port identifier as the fourth port identifier into the fourth message. If the optical network unit identifier of the FTTH segment and the slave device identifier of the FTTR segment are different, then the master device needs to convert the port identifier according to the pre-established identifier mapping relationship, and the optical line terminal will also store this identifier mapping relationship.

[0093] Through the embodiments of this application, the optical line terminal can receive management and control messages sent by the FTTR slave device through the master device, and the master device can transparently transmit the management and control messages of the FTTR slave device to the optical line terminal, thereby enabling the FTTR slave device to directly report management and control messages to the optical line terminal.

[0094] In some embodiments, the optical network unit identifier of the FTTR slave device is assigned by the optical line terminal or the master device.

[0095] If the optical network unit identifier is assigned by the optical line terminal, the method further includes the following steps:

[0096] Step S3002: Obtain the slave device serial number of the FTTR slave device;

[0097] Step S3004: Assign the optical network unit identifier to the FTTR slave device, and send the slave device serial number and the optical network unit identifier to the master device.

[0098] If the optical network unit identifier is assigned by the master device, the method further includes the following steps:

[0099] Step S3006: Assign a pre-allocated optical network unit identifier to the FTTR slave device and send the pre-allocated optical network unit identifier to the master device, so that the master device assigns the optical network unit identifier to the FTTR slave device from the pre-allocated optical network unit identifier;

[0100] Step S3008: Receive from the master device the correspondence between the slave device serial number of the FTTR slave device and the optical network unit identifier.

[0101] In some embodiments, prior to step S3004, the method may further include: step S3003, obtaining an unassigned optical network unit identifier from the master device. In this case, step S3004 involves assigning the optical network unit identifier to the FTTR slave device from the unassigned optical network unit identifiers.

[0102] In some embodiments, the management control message carries a message type field, wherein the message type field includes a relay enable field; and / or, the management control message carries a managed entity attribute field, wherein the managed entity attribute field includes an optical network unit management control channel relay attribute field; wherein the message type field and / or the managed entity attribute field are used to indicate whether the management control message is a relay message between the FTTH network and the FTTR network.

[0103] In this embodiment, the optical line terminal can configure the relay forwarding function of the master device, and indicate whether the management control message supports relay forwarding by reserving or adding fields, which is compatible with the existing message transmission mode and realizes flexible control over the transmission of management control messages between the FTTR network and the FTTH network.

[0104] In some embodiments, the ONU-ID of the slave device is assigned by the optical line terminal. Figure 5 This is a schematic diagram illustrating the process of assigning ONU-ID and SFU-ID to a slave device in one embodiment of this application, as shown below. Figure 5 As shown, the process includes the following steps:

[0105] Step S501: The master device sends a serial number request (SN request) to the slave device;

[0106] Step S502: The slave device sends a serial number response to the master device, carrying the slave device serial number (SFU SN);

[0107] Step S503: The master device reports the SFU-SN to the optical line terminal;

[0108] Step S504: The optical line terminal assigns an optical network unit (ONU-ID) to the slave device and sends it to the master device;

[0109] Step S505: The master device assigns a slave device identifier (SFU-ID) to the slave device.

[0110] In some embodiments, the activation process of the FTTR slave device may include the following steps in addition to steps S501 to S505 described above:

[0111] Step S506: The master device sends a ranging request to the slave device;

[0112] Step S507: The slave device sends a ranging response to the master device;

[0113] Step S508: The master device sends the ranging time (ranging_Time) to the slave device.

[0114] The identifier allocation method in this application embodiment can be improved based on existing standards (such as ITU-T G.9942).

[0115] In some embodiments, in step S503, after the master device obtains the serial number of the slave device, the master device (i.e., the ONU of the FTTH segment) reports the SFU SN to the OLT. The master device can report the serial number of the slave device to the OLT by modifying the message format of the optical network unit serial number (Serial_Number_ONU) message.

[0116] The modification of the Serial_Number_ONU message format includes: changing the ONU-ID field in the message from an unassigned ONU-ID to the ONU-ID of the master device ONU. The OLT can determine whether the message is used to report the SFU SN based on the ONU-ID field of the Serial_Number_ONU message being the ONU-ID of the master device ONU.

[0117] In some embodiments, in step S504, after receiving the SFN SN, the OLT allocates an ONU-ID to the SFU via the FTTH segment. The new ONU-ID can be allocated to the SFU SN by modifying the message format of the FTTH optical network unit identifier allocation (Assign_ONU-ID) message and placing it in the message content field.

[0118] The modification to the Assign_ONU-ID message format includes: changing the target ONU-ID field in the message from the broadcast ONU-ID to the ONU-ID of the master device ONU. The master device determines that the message is being sent to itself based on the ONU-ID field in the Assign_ONU-ID message, but since the SN in the Message Content belongs to the downstream SFU, the message needs to be forwarded. Therefore, it continues to send the message to the SFU via the slave device identifier allocation (Assign_SFU-ID) message in the broadcast FTTR segment.

[0119] In some embodiments, in step S503, the master device can also report via an unmodified Serial_Number_ONU message, in which the ONU-ID field is still an unassigned ONU-ID, and the OLT parses the Serial_Number_ONU message from the burst sent by the master device.

[0120] In other embodiments, the master device may also convert and map the ONU-ID to an SFU-ID with another value.

[0121] In some embodiments, in step S504, the OLT can also assign a new ONU-ID to the SFU by placing the unmodified Assign_ONU-ID in the FTTH segment in the Message Content field. The target ONU-ID of the message is still the broadcast ONU-ID. The master device determines that the SN in it belongs to the SFU connected to it and continues to send the Assign_SFU-ID message in the broadcast FTTR segment to the SFU.

[0122] In other embodiments, steps S503 (reporting the SFU SN) and S504 (assigning an ONU-ID to the SFU) can also be implemented via OMCI messages. For example, a table attribute containing the downstream SFU SN and its ONU-ID can be added to the managed entity (ME) of the ONU2-G message. When the SFU SN needs to be reported, the master device reports a table attribute carrying the SFU SN and an unassigned ONU-ID, indicating that the OLT needs to assign an ONU-ID. The OLT sends the assigned ONU-ID to the master device by setting this table attribute, thus assigning an ONU-ID to the SFU.

[0123] In some embodiments, the ONU-ID is first pre-assigned by the optical line terminal and then assigned to the slave device by the master device. Figure 6 This is a schematic diagram illustrating the process of allocating ONU-ID and SFU-ID from a device in another embodiment of this application, as shown below. Figure 6 As shown, the process includes the following steps:

[0124] Step S601: The optical line terminal sends the pre-assigned ONU-ID to the master device;

[0125] Step S602: The master device sends a serial number request (SN request) to the slave device;

[0126] Step S603: The slave device sends a serial number response to the master device, carrying the slave device serial number (SFU SN);

[0127] Step S604: The master device assigns an ONU-ID / SFU-ID to the slave device;

[0128] Step S605: The master device reports the correspondence between SFU-SN and ONU-ID to the optical line terminal.

[0129] In some embodiments, the activation process of the FTTR slave device may include the following steps in addition to steps S601 to S605 described above:

[0130] Step S606: The master device sends a ranging request to the slave device;

[0131] Step S607: The slave device sends a ranging response to the master device;

[0132] Step S608: The master device sends the ranging time (ranging_Time) to the slave device.

[0133] The identifier allocation method in this application embodiment can be improved based on existing standards (such as ITU-T G.9942).

[0134] In this embodiment, the OLT distributes the ONU-ID to the master device in advance. The master device assigns the ONU-ID as the SFU-ID to the SFU as needed (of course, the master device can also convert and map the ONU-ID to another SFU-ID value), and reports the correspondence between the SFU SN and the ONU-ID / SFU-ID to the OLT.

[0135] In some embodiments, the OLT can pre-assign ONU-IDs to the master device. After discovering the SFU SN, the master device uses the pre-assigned ONU-ID as the SFU-ID and assigns it to the SFU via the Assign_SFU-ID message in the broadcast FTTR segment, and reports the correspondence between the SFU SN and ONU-ID to the OLT. The OLT can pre-assign ONU-IDs to the master device through the Physical Layer Operations, Administration and Maintenance (PLOAM) channel or the OMCI channel, and the master device can also report the correspondence between the SFU SN and ONU-ID to the OLT.

[0136] In one exemplary embodiment, taking the PLOAM message as an example, the FTTH OLT can send a pre-assigned ONU-ID / SFU-ID to the master device by modifying the message format of the Assign_ONU-ID message. The ONU-ID field in the Assign_ONU-ID message is changed from the broadcast ONU-ID field to the ONU-ID of the master device ONU, and the Vendor Identifier (Verdor-ID) and Vendor Specific Serial Number (VSSN) fields in the Assign_ONU-ID message are changed to all 0s, indicating that it is a pre-assigned ONU-ID.

[0137] In an exemplary embodiment, taking the PLOAM message as an example, the master device can report the correspondence between the SFU SN and ONU-ID to the OLT by modifying the message format of the Serial_Number_ONU message. The ONU-ID field in the Serial_Number_ONU message is modified from an unassigned ONU-ID to the ONU-ID of the master device's ONU. Bytes 13-16 of the Serial_Number_ONU message are filled with 0, and bytes 17-18 are filled with the SFU-ID of the SFU, indicating that the master device is reporting the correspondence between the SFU SN and ONU-ID / SFU-ID.

[0138] In an exemplary embodiment, taking the OMCI message as an example, a table attribute containing the downstream SFU SN and the corresponding ONU-ID can be added to the ONU2-G ME. The OLT sends the pre-allocated ONU-ID to the master device by setting this table attribute, where SFUSN is all 0s, thus achieving the pre-allocation of ONU-ID. After the master device assigns the ONU-ID as an SFU-ID, when reporting the correspondence between the SFU SN and ONU-ID, the master device reports a table attribute carrying the SFU SN and ONU-ID, reporting the correspondence between the SFU SN and ONU-ID.

[0139] This application does not limit the standard of FTTH and FTTR. Whether FTTH and FTTR are of the same standard or different standards, the OLT can directly or transparently manage the slave device or FTTR SFU through OMCI. The following will use XG-PON standard for FTTH and G.fin standard for FTTR as an example to describe the message format in detail.

[0140] Table 1 shows the message format of the Assign_ONU-ID message in the XG-PON standard of the FTTH segment.

[0141] Table 1

[0142]

[0143] As shown in Table 1, the Assign_ONU-ID message contains a sequence number (SN, consisting of a 7-10 byte Vendor-ID and an 11-14 byte VSSN) field and a 5-6 byte ONU-ID field. By setting the values ​​of these two fields, the ONU-ID can be assigned or pre-assigned.

[0144] In one exemplary embodiment, the target ONU-ID field (bytes 1-2) in the Assign_ONU-ID message is modified from the broadcast ONU-ID to the ONU-ID of the master device ONU, while bytes 7-14, Vendor-ID+VSSN, are set to the sequence number of the downstream SFU, indicating that the ONU-ID is assigned to the slave device corresponding to the sequence number.

[0145] In one exemplary embodiment, the ONU-ID field (1-2 bytes) in the Assign_ONU-ID message is modified from the broadcast ONU-ID to the ONU-ID of the master device ONU, and the Verdor-ID and VSSN fields in the Assign_ONU-ID message are changed to all 0, indicating that the ONU-ID is a pre-assigned ONU-ID.

[0146] Table 2 shows the message format of the Assign_SFU-ID message in G.fin format for the FTTR segment.

[0147] Table 2

[0148] octet content describe 1 11111111 Broadcast message to all S-FTRs 2 00000011 The message was identified as "Assign_SFU-ID" 3 pppppppp From the device identifier (SFU-ID) 4 abcdefgh Serial number byte 1 5-10 …… …… 11 stuvwxyz Serial number byte 8 12 Unspecified

[0149] As shown in Table 2, the Assign_SFU-ID message is sent to the slave transceiver of SFU (S-FTR) and assigns a slave device identifier (SFU-ID) to the SFU. Subsequently, based on the SFU-ID of a specific S-FTR, an Alloc-ID is assigned to each of its transmission containers (T-CONTs). This message allows the SFU-ID to be assigned to a specified slave device.

[0150] Table 3 shows the message format of the Serial_Number_ONU message in the XG-PON standard of the FTTH segment.

[0151] Table 3

[0152]

[0153] As shown in Table 3, the Serial_Number_ONU message can report only the SFU SN, or it can report the correspondence between the SFU SN and the ONU-ID.

[0154] In one exemplary embodiment, the SFU SN can be reported directly to the optical line terminal (OLT) via an unmodified Serial_Number_ONU message. Alternatively, the ONU-ID field in the Serial_Number_ONU message can be modified from an unassigned ONU-ID to the ONU-ID of the master ONU. Upon receiving the Serial_Number_ONU message, the OLT recognizes the ONU-ID field as belonging to the master ONU and thus determines that the message is intended for reporting the SFU SN.

[0155] In one exemplary embodiment, the ONU-ID field in the Serial_Number_ONU message is modified from an unassigned ONU-ID to the ONU-ID of the master device ONU. Bytes 13-16 of the Serial_Number_ONU message are filled with 0, and bytes 17-18 are filled with the SFU-ID of the SFU. This indicates that the master device reports the correspondence between the SFU SN and ONU-ID / SFU-ID to the optical line terminal.

[0156] Figure 7This is a schematic diagram of the encapsulation format of the XGEM frame in the XG-PON standard of the FTTH segment in this application embodiment, as shown below. Figure 7 As shown, in XG-PON, the XGEM Port-ID is defined as 16 bits, and the XGEM Port-ID value range is 0-0x3FF, which is equivalent to the ONU-ID.

[0157] Figure 8 This is a schematic diagram of the encapsulation format of the G.fin FEM frame in the FTTR segment of this application embodiment, as shown below. Figure 8 As shown, in G.fin, the FEM Port-ID is defined as 12 bits, and the FEM Port-ID value range is 0-0xFF, which is equivalent to the SFU-ID.

[0158] Therefore, based on the value ranges of ONU-ID and SFU-ID, the optical line terminal can preferentially allocate part or all of the 0-0xFF value range to the SFU for the FEM Port-ID of the FTTR segment, and then allocate the other values ​​in the 0-0x3FF range to the ONU or MFU for the XGEM Port-ID of the FTTH segment.

[0159] In some embodiments, management control messages can be WMCI messages. For example, when transmitting WMCI messages, the FTTH segment still uses the OMCI channel, or the corresponding Port-ID is configured through the Connection Termination Point (Managed Entity, CTPME) of the GEM port network to carry management information related to WMCI for the FTTH segment. The FTTR segment WMCI management messages still use the FMCI channel, or the corresponding Port-ID is configured through the CTPME of the GEM port network to carry management information related to WMCI for the FTTR segment.

[0160] In some embodiments, the forwarding configuration of uplink and downlink OMCI / FMCI and OMCI / WMCI messages on the master device can be implemented using any one of the following methods or a combination of two of them:

[0161] Method 1: Add the managed entity (ME) feature.

[0162] For example, an OMCC relay attribute can be added to the ONU2-G ME. This attribute is 1 byte long, with a value of 0 indicating that OMCC relay is not performed, and a value of 1 indicating that OMCC relay is performed, which will relay OMCI / FMCI / WMCI messages between FTTH OLT and FTTRSFU in the uplink and downlink directions.

[0163] Method 2: Modify the OMCI / FMCI message format.

[0164] Table 4 shows the message format of the Baseline OMCI message. As shown in Table 4, the Baseline OMCI message carries a Message type field.

[0165] Table 4

[0166] Byte number size use 1..2 2 Transaction association identifier 3 1 Message Type 4 1 Device Identifier 5..8 4 Managed Entity Identifier 9..40 32 Message content 41..48 8 OMCI tail

[0167] Table 5 shows the message format of Extended OMCI messages. As shown in Table 5, Extended OMCI messages also carry a message type field.

[0168] Table 5

[0169] Byte number size use 1..2 2 Transaction association identifier 3 1 Device Identifier 4 1 Device Identifier 5..8 4 Managed Entity Identifier 9..10 2 Message content length 11..(N-4) - Message content (N-3)..N 4 Message Integrity Check

[0170] Figure 9 This is a schematic diagram of the structure of the message type field in an embodiment of this application, as shown below. Figure 9 As shown, the 8th bit reserved in the message type field can be redefined as the Relay Enable (RE) field. If the RE value is 0, it is consistent with the traditional OMCI meaning that the message will not be relayed. If the RE value is 1, it indicates that the message is an FTTH+FTTR relay message type, that is, the message is exchanged between FTTH OLT and FTTR SFU, and the master device needs to relay the message in the uplink or downlink direction.

[0171] Embodiments of this application also provide a master device that can be used to execute the steps in the method embodiments on the master device side.

[0172] Figure 10 This is a schematic diagram (a) of the main device in one embodiment of this application, as shown below. Figure 10 As shown, the main device includes an optical network relay module 10.

[0173] In this embodiment, the Optical Network Relay (ONR) module is used to receive a first message carrying a management control message and a first port identifier from a first device, determine a second port identifier based on the first port identifier, and send a second message carrying the second port identifier and the management control message to a second device. The first port identifier is used for a first management control channel between the first device and the master device, and the second port identifier is used for a second management control channel between the second device and the master device. The first device is an optical line terminal (OLT), and the second device is an FTTR slave device; or, the first device is the FTTR slave device, and the second device is the OLT.

[0174] In this embodiment, the optical network relay module integrates FTTH ONU and FTTR MFU functions. The FTTH ONU function can be the transmission convergence (TC) layer function of the ONU in FTTH, and the FTTR MFU function can be the TC / DLL layer function of the MFU in FTTR.

[0175] Furthermore, in the downlink direction, this module can encapsulate the OMCI message and Port-ID into an FEM frame and send it to the SFU if the Port-ID in the GEM frame is equal to the downstream SFU-ID. In the uplink direction, upon receiving an FEM frame encapsulated with an FMCI message, this module encapsulates the Port-ID and FMCI message into a GEM frame containing an OMCI message and sends it to the FTTH OLT.

[0176] In this embodiment, the Port-ID of the FTTR segment and the Port-ID of the FTTH segment can be the same or different. If the port identifiers of the two networks are different, the optical network relay module needs to convert the Port-ID according to the preset port identifier mapping relationship before encapsulation. The identifier allocation process can be referred to the description in the above method embodiment, and will not be repeated here.

[0177] In this embodiment of the application, the relay / forwarding function of the optical network relay module can be enabled or disabled according to the configuration information. For example, the optical line terminal can inform the optical network relay module whether the corresponding management control message needs to be forwarded between FTTR and FTTH by adding ME features or modifying the OMCI / FMCI message format. When the relay function is enabled, the optical network relay module will relay and forward the management control message.

[0178] In this embodiment, a master device can connect to multiple slave devices, and the master device can interact with the downstream slave devices through the downstream optical port. A master device can also connect to only one optical line terminal (OLT), and the master device can interact with that OLT through the upstream optical port.

[0179] Figure 11 This is a schematic diagram (II) of the main device in one embodiment of this application, as shown below. Figure 11 As shown, the main equipment includes an optical network relay module 10, wherein the optical network relay module 10 includes an optical network unit module 11 and an optical line terminal module 12.

[0180] In this embodiment, the optical network unit module is used to receive the first message from the optical line terminal in the downlink direction, parse the first message, and obtain the management control message and the first port identifier, wherein the first port identifier is allocated along with the optical network unit identifier or allocated independently.

[0181] In this embodiment, the optical line terminal module is used to, in the downlink direction, use the first port identifier as the second port identifier, encapsulate the second port identifier and the management control message into the second message, and send the second message to the FTTR slave device, wherein the second port identifier is assigned along with the slave device identifier or is assigned independently.

[0182] In this embodiment, the optical line terminal module is further configured to receive the first message from the FTTR slave device in the uplink direction, parse the first message to obtain the management control message and the first port identifier, wherein the first port identifier is allocated along with the slave device identifier or allocated independently.

[0183] In this embodiment, the optical network unit module is further configured to, in the uplink direction, use the first port identifier as the second port identifier, encapsulate the second port identifier and the management control message into the second message, and send the second message to the optical line terminal, wherein the second port identifier is allocated along with the optical network unit identifier or allocated independently.

[0184] In this embodiment, the optical network unit module is used to implement the FTTH ONU function, and the optical line terminal module is used to implement the FTTR MFU function. The FTTH ONU function can be an FTTH ONU TC layer function, and the FTTR MFU function can be an FTTR MFU TC / DLL layer function.

[0185] In some embodiments, the optical network unit module and the optical line terminal module interact through a specific interface. This specific interface is determined by the specific implementation and generally uses an interface between chips or modules, such as an internal Ethernet interface or a bus interface, which will not be elaborated upon here.

[0186] In an exemplary embodiment, the specific interface may be an internal channel. The internal channel is used to send the management control message parsed by the optical network unit module and the first port identifier to the optical line terminal module in the downlink direction; the internal channel is also used to send the management control message parsed by the optical line terminal module and the first port identifier to the optical network unit module in the uplink direction.

[0187] In this embodiment, the Port-ID of the FTTR segment and the Port-ID of the FTTH segment can be the same or different. If the port identifiers of the two networks are different, the optical network relay module needs to convert the Port-ID according to the preset port identifier mapping relationship before encapsulation. The identifier allocation process can be referred to the description in the above method embodiment, and will not be repeated here.

[0188] In this embodiment of the application, the relay / forwarding function of the optical network relay module can be enabled or disabled according to the configuration information. For example, the optical line terminal can inform the optical network relay module whether the corresponding management control message needs to be forwarded between FTTR and FTTH by adding ME features or modifying the OMCI / FMCI message format. When the relay function is enabled, the optical network relay module will relay and forward the management control message.

[0189] Figure 12 This is a schematic diagram (iii) of the main device in one embodiment of this application, as shown. Figure 12 As shown, the main device includes an optical network relay module 10.

[0190] The optical network relay module 10 includes: an optical network unit module 11, an optical line terminal module 12, an optical network unit Ethernet module 13, and an optical line terminal Ethernet module 14.

[0191] In this embodiment, the optical network unit Ethernet module is configured to receive, in the downlink direction, the management and control message encapsulated into an Ethernet frame and the first port identifier from the optical network unit module, and exchange the Ethernet frame with the optical line terminal Ethernet module. The optical line terminal Ethernet module is further configured to receive, in the uplink direction, the management and control message encapsulated into an Ethernet frame and the first port identifier from the optical line terminal module, and exchange the Ethernet frame with the optical network unit Ethernet module.

[0192] In this embodiment, the optical line terminal Ethernet module is used to send the Ethernet frame to the optical line terminal module in the downlink direction. The optical network unit Ethernet module is also used to send the Ethernet frame to the optical network unit module in the uplink direction.

[0193] In this embodiment, the optical network unit module and the optical line terminal module are further configured to parse or encapsulate the Ethernet frames. Specifically, in the downlink direction, the optical network unit module encapsulates the port identifier and management control messages into Ethernet frames, and sends these Ethernet frames to the optical line terminal module via the optical network unit Ethernet module and the optical line terminal Ethernet module. The optical line terminal module then parses the Ethernet frames to obtain the port identifier and management control messages. In the uplink direction, the optical line terminal encapsulates the port identifier and management control messages into Ethernet frames, and sends these Ethernet frames to the optical network unit module via the optical line terminal Ethernet module and the optical network unit Ethernet module. The optical network unit module then parses the Ethernet frames to obtain the port identifier and management control messages.

[0194] In this embodiment, the optical network relay module also integrates the Ethernet (ETH) function of the FTTH ONU and the ETH function of the FTTR MFU. Exemplarily, the optical network unit Ethernet module can implement the FTTH ONU ETH function, and the optical line terminal Ethernet module can implement the FTTR MFU ETH function. The optical network unit Ethernet module and the optical line terminal Ethernet module interact via ETH exchange. The optical network unit module and the optical line terminal module interact indirectly through the Ethernet module.

[0195] In this embodiment, the Ethernet addresses of FTTH ONU ETH and FTTR MFU ETH are set by system default and their switching relationships are pre-configured in the ETH switching. Furthermore, the optical line terminal can also configure or pre-configure the switching relationships of Ethernet addresses in the master device.

[0196] In this embodiment, the Port-ID of the FTTR segment and the Port-ID of the FTTH segment can be the same or different. If the port identifiers of the two networks are different, the optical network relay module needs to convert the Port-ID according to the preset port identifier mapping relationship before encapsulation. The identifier allocation process can be referred to the description in the above method embodiment, and will not be repeated here.

[0197] In this embodiment of the application, the relay / forwarding function of the optical network relay module can be enabled or disabled according to the configuration information. For example, the optical line terminal can inform the optical network relay module whether the corresponding management control message needs to be forwarded between FTTR and FTTH by adding ME features or modifying the OMCI / FMCI message format. When the relay function is enabled, the optical network relay module will relay and forward the management control message.

[0198] Figure 13 This is a schematic diagram (fourth) of the main device in one embodiment of this application, as shown below. Figure 13 As shown, the main device includes an optical network relay module 10.

[0199] The optical network relay module 10 includes: an optical network unit module 11, an optical line terminal module 12, and a processing module 15.

[0200] In this embodiment, the processing module 15 may be a central processing unit (CPU), but this application is not limited to this.

[0201] In this embodiment, the processing module is configured to, in the downlink direction, obtain the management control message and the first port identifier from the optical network unit module, determine the second port identifier based on the first port identifier, and send the management control message and the second port identifier to the optical line terminal module. The processing module is further configured to, in the uplink direction, obtain the management control message and the first port identifier from the optical line terminal module, determine the second port identifier based on the first port identifier, and send the management control message and the second port identifier to the optical network unit module.

[0202] In some embodiments, the Ethernet module may be used only for the exchange of service data between FTTH and FTTR, while management control messages (such as OMCI messages) are relayed and forwarded through the processing module.

[0203] In one exemplary embodiment, in the downlink direction, the optical network unit module, based on the equality of the Port-ID and the downstream SFU-ID in the GEM frame, hands over the OMCI message and the Port-ID to the CPU for processing. The CPU then hands over the Port-ID and the OMCI message to the optical line terminal module, which then encapsulates them into an FEM frame and sends it to the SFU.

[0204] In one exemplary embodiment, in the uplink direction, the optical line terminal module receives the FEM frame of the FMCI message, hands over the Port-ID and FMCI message to the CPU for processing, and the CPU then hands it over to the optical network unit module. The optical network unit module encapsulates the OMCI message into a GEM frame and then sends the GEM frame to the FTTH OLT.

[0205] The above embodiments in this application can be used for cases where ONU-ID and SFU-ID are the same, or cases where ONU-ID and SFU-ID are different. If they are different, the master device can also obtain the correspondence between ONU-ID and SFU-ID in advance and perform identifier conversion according to the identifier mapping relationship.

[0206] In this embodiment of the application, the relay / forwarding function of the optical network relay module can be enabled or disabled according to the configuration information. For example, the optical line terminal can inform the optical network relay module whether the corresponding management control message needs to be forwarded between FTTR and FTTH by adding ME features or modifying the OMCI / FMCI message format. When the relay function is enabled, the optical network relay module will relay and forward the management control message.

[0207] In this embodiment, the master device establishes a transparent forwarding channel between the optical line terminal and the FTTR slave device, enabling the relay forwarding of management and control messages between the master device and the FTTR slave device. This solves the problem in related technologies where the FTTH OLT cannot directly or transparently manage the FTTR SFU, thus integrating the FTTR network and the FTTH network into a single entity. This achieves a logically integrated network of FTTH and FTTR. Logically, the slave device and the master device belong to the ONU under the OLT. The FTTR is an extension of the FTTH. The FTTH OLT can directly manage the FTTR slave device, and the FTTR slave device can also directly report information to the FTTH OLT, logically forming a passive optical network where FTTH and FTTR cooperate with each other.

[0208] The modules of the main device in this application embodiment can be implemented in hardware or in software through computer programs, and this application does not impose any restrictions on this.

[0209] Embodiments of this application also provide an optical line terminal for implementing the steps in any of the above-described optical line terminal side method embodiments.

[0210] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is executed by a processor to perform the steps in any of the above method embodiments.

[0211] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0212] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0213] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0214] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0215] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0216] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0217] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method for transmitting management and control messages, applied to a master device, characterized in that, The method includes: Receive a first message from the first device, which carries management control messages and a first port identifier; The second port identifier is determined based on the first port identifier; Send a second message to the second device, carrying the second port identifier and the management control message; Wherein, the first device is an optical line terminal and the second device is an FTTR slave device; or, the first device is the FTTR slave device and the second device is the optical line terminal.

2. The method according to claim 1, characterized in that, The management control messages include at least one of the following: Optical Network Unit Management Control Interface (OMCI) messages, Fiber Optic Management Control Interface (FMCI) messages, or Wireless Management Control Interface (WMCI) messages.

3. The method according to claim 1, characterized in that, The first port identifier is assigned along with the optical network unit identifier, and the second port identifier is assigned along with the slave device identifier; or, the first port identifier is assigned along with the slave device identifier, and the second port identifier is assigned along with the optical network unit identifier. The first port identifier may be the same as or different from the second port identifier.

4. The method according to claim 3, characterized in that, Determining the second port identifier based on the first port identifier includes: If the first port identifier and the second port identifier are different, the second port identifier is determined according to the first port identifier and a pre-established identifier mapping relationship, wherein the identifier mapping relationship is the mapping relationship between the first port identifier and the second port identifier.

5. The method according to claim 4, characterized in that, The method further includes: The optical network unit identifier of the FTTR slave device is determined, wherein the FTTR slave device has a unique slave device serial number; Assign a slave device identifier to the FTTR slave device, wherein the optical network unit identifier may be the same as or different from the slave device identifier; If the optical network unit identifier and the slave device identifier are different, the identifier mapping relationship is established between the optical network unit identifier and the slave device identifier corresponding to the same slave device serial number.

6. The method according to claim 5, characterized in that, Determining the optical network unit identifier of the FTTR slave device includes: Obtain the optical network unit identifier assigned by the optical line terminal to the FTTR slave device; or, Obtain a pre-assigned optical network unit identifier from the optical line terminal, and assign the optical network unit identifier to the FTTR slave device from the pre-assigned optical network unit identifier.

7. The method according to claim 6, characterized in that, The step of obtaining the optical network unit identifier assigned by the optical line terminal to the FTTR slave device includes: The optical line terminal sends the slave device serial number to the optical line terminal and receives the optical network unit identifier from the optical line terminal, wherein the optical network unit identifier is assigned by the optical line terminal to the FTTR slave device corresponding to the slave device serial number.

8. The method according to claim 6, characterized in that, The step of obtaining a pre-allocated optical network unit identifier from the optical line terminal and allocating the optical network unit identifier to the FTTR slave device from the pre-allocated optical network unit identifier includes: Obtain a pre-assigned optical network unit identifier from the optical line terminal, and assign the optical network unit identifier to the FTTR slave device corresponding to the slave device serial number from the pre-assigned optical network unit identifier.

9. The method according to claim 8, characterized in that, After obtaining a pre-assigned optical network unit identifier from the optical line terminal and assigning the optical network unit identifier to the FTTR slave device from the pre-assigned optical network unit identifier, the method further includes: Send the correspondence between the slave device serial number and the optical network unit identifier to the optical line terminal.

10. The method according to claim 5, characterized in that, After assigning the slave device identifier to the FTTR slave device, the method further includes: The slave device identifier is sent to the FTTR slave device corresponding to the slave device serial number.

11. The method according to claim 5, characterized in that, Prior to assigning the slave device identifier to the FTTR slave device, the method further includes: Send a serial number request to the FTTR slave device; The FTTR receives a serial number response carrying the slave device's serial number.

12. The method according to claim 1, characterized in that, The first message is a service encapsulation frame encapsulated according to a preset first standard, and the second message is a service encapsulation frame encapsulated according to a preset second standard, wherein the first port identifier or the second port identifier is located in the port identifier field of the service encapsulation frame, and the management control message is located in the payload of the service encapsulation frame.

13. The method according to claim 12, characterized in that, The preset first standard or the preset second standard includes at least one of the following: GPON standard, symmetrical GPON standard, XG-PON standard, XGS-PON standard, 50G-PON standard, G.fin standard, and FTTR standard.

14. The method according to claim 1, characterized in that, The method further includes: Based on the message type field and / or managed entity attribute field carried in the management control message, determine whether the management control message is a relay message between the FTTH network and the FTTR network; The message type field includes a relay enable field, and / or the managed entity attribute field includes an optical network unit management control channel relay attribute field.

15. The method according to claim 1, characterized in that, The first port identifier and the second port identifier are assigned separately, wherein the first port identifier and the second port identifier may be the same or different.

16. A method for transmitting management and control messages, applied to an optical line terminal, characterized in that, The method includes: Send a third message carrying a management control message and a third port identifier to the master device, so that the master device sends a fourth message carrying the management control message and a fourth port identifier to the FTTR slave device, wherein the fourth port identifier is determined based on the third port identifier; or, The master device receives the third message, wherein the third message is determined by the master device based on the fourth message received from the FTTR slave device.

17. The method according to claim 16, characterized in that, in, The third port identifier is assigned along with the optical network unit identifier, and the fourth port identifier is assigned along with the slave device identifier; or... The third port identifier and the fourth port identifier are assigned independently; The third port identifier may be the same as or different from the fourth port identifier.

18. The method according to claim 17, characterized in that, The method further includes: Obtain the slave device serial number of the FTTR slave device; The optical network unit identifier is assigned to the FTTR slave device, and the slave device serial number and the optical network unit identifier are sent to the master device.

19. The method according to claim 17, characterized in that, The method further includes: The master device assigns a pre-allocated optical network unit identifier to the FTTR slave device and sends the pre-allocated optical network unit identifier to the master device, so that the master device assigns the optical network unit identifier to the FTTR slave device from the pre-allocated optical network unit identifier; The master device receives the correspondence between the slave device serial number of the FTTR slave device and the optical network unit identifier.

20. The method according to claim 16, characterized in that, The management control message carries a message type field, wherein the message type field includes a relay enable field; and / or, The management control message carries a managed entity attribute field, wherein the managed entity attribute field includes an optical network unit management control channel relay attribute field; The message type field and / or the managed entity attribute field are used to indicate whether the management control message is a relay message between the FTTH network and the FTTR network.

21. A main device, characterized in that, include: An optical network relay module is configured to receive a first message carrying a management control message and a first port identifier from a first device, determine a second port identifier based on the first port identifier, and send a second message carrying the second port identifier and the management control message to a second device; wherein the first device is an optical line terminal and the second device is an FTTR slave device; or, the first device is the FTTR slave device and the second device is the optical line terminal.

22. The main equipment according to claim 21, characterized in that, The optical network relay module includes: An optical network unit module is used to receive the first message from the optical line terminal in the downlink direction, parse the first message, and obtain the management control message and the first port identifier, wherein the first port identifier is allocated along with the optical network unit identifier or is allocated independently. An optical line terminal module is used, in the downlink direction, to use the first port identifier as the second port identifier, encapsulate the second port identifier and the management control message into a second message, and send the second message to the FTTR slave device, wherein the second port identifier is assigned along with the slave device identifier or is assigned independently; The optical line terminal module is further configured to receive the first message from the FTTR slave device in the uplink direction, parse the first message, and obtain the management control message and the first port identifier, wherein the first port identifier is assigned along with the slave device identifier or is assigned independently. The optical network unit module is further configured to, in the uplink direction, use the first port identifier as the second port identifier, encapsulate the second port identifier and the management control message into the second message, and send the second message to the optical line terminal, wherein the second port identifier is allocated along with the optical network unit identifier or is allocated independently.

23. The main equipment according to claim 22, characterized in that, The optical network relay module also includes: The optical network unit Ethernet module is used to receive the management control message and the first port identifier encapsulated in an Ethernet frame from the optical network unit module in the downlink direction, and exchange the Ethernet frame with the optical line terminal Ethernet module. An optical line terminal Ethernet module is used to send the Ethernet frame to the optical line terminal module in the downlink direction; The optical line terminal Ethernet module is also used to receive, in the uplink direction, the management control message encapsulated into the Ethernet frame and the first port identifier from the optical line terminal module, and exchange the Ethernet frame to the optical network unit Ethernet module. The optical network unit Ethernet module is also used to send the Ethernet frame to the optical network unit module in the uplink direction; The optical network unit module and the optical line terminal module are also used to parse or encapsulate the Ethernet frame.

24. The main equipment according to claim 22, characterized in that, The optical network relay module also includes: The processing module is configured to, in the downlink direction, obtain the management control message and the first port identifier from the optical network unit module, determine the second port identifier based on the first port identifier, and send the management control message and the second port identifier to the optical line terminal module; The processing module is further configured to, in the uplink direction, obtain the management control message and the first port identifier from the optical line terminal module, determine the second port identifier based on the first port identifier, and send the management control message and the second port identifier to the optical network unit module.

25. The main equipment according to claim 22, characterized in that, The optical network relay module also includes: An internal channel is used to send the management and control message parsed by the optical network unit module and the first port identifier to the optical line terminal module in the downlink direction; The internal channel is also used to send the management control message parsed by the optical line terminal module and the first port identifier to the optical network unit module in the uplink direction.

26. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, wherein the computer program is executed by a processor to perform the method described in any one of claims 1 to 20.

27. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the method as described in any one of claims 1 to 20.

28. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 20.

Images