A message transmission method, comprising a master device, an OLT, and an optical communication system.

Abstract

This application provides a message transmission method, a master device, an OLT, and an optical communication system. This application newly defines the message format for transmission between the master device and the OLT in an FTTR system. In the uplink direction, the master device sends a second message to the OLT based on a first message sent by a slave device, wherein the second message includes a newly added first identifier of the slave device. In the downlink direction, the OLT also adds a first identifier to a third message sent to the master device, so that the master device can send a fourth message to the corresponding slave device based on the third message. In other words, this solution enables the OLT to manage slave devices, which is beneficial for unifying the management method of the FTTR system. Furthermore, the master device and slave device can use existing communication protocols without significant adjustments to achieve OLT management of slave devices, resulting in good application performance.

Description

[0001] This application is a divisional application. The original application has the application number 202310489168.2 and the original application date is April 28, 2023. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of optical communication, and more particularly to a message transmission method, a master device, an OLT, and an optical communication system. Background Technology

[0003] In gigabit passive optical networks (GPON), the optical network terminal management and control interface (OMCI) is a protocol for information exchange between optical line terminals (OLTs) and optical network terminals (ONTs). It is used to enable the OLT to manage the ONTs in the GPON network, including configuration management, fault management, performance management, and security management.

[0004] With the widespread availability of fixed broadband and the emergence of various smart devices, Fiber to the Room (FTTR) technology has been proposed and received considerable attention in order to solve the problem of WiFi coverage in home networks. The main idea of ​​FTTR is to extend fiber optic cables further into the homes of residents, building upon Fiber to the Home (FTTH). However, there is currently no management protocol for FTTR. Summary of the Invention

[0005] This application provides a message transmission method, a master device, an OLT, and an optical communication system. It defines a new message format for transmission between the master device and the OLT in the FTTR system, realizes the OLT's management of slave devices, and facilitates the unification of the management method of the FTTR system.

[0006] In a first aspect, embodiments of this application provide a message transmission method executed by a master device. In the uplink transmission direction, the master device receives a first message sent by a slave device and sends a second message to an OLT based on the first message. Both the first and second messages include a first identifier of the slave device. In the downlink transmission direction, the master device receives a third message sent by the OLT including the first identifier and sends a fourth message to the slave device based on the third message. The third message includes the first identifier of the slave device.

[0007] In this implementation, a new message format for transmission between the master device and the OLT in the FTTR system is defined. A first identifier for the slave device is added to both the second message in the uplink direction and the third message in the downlink direction. This newly defined message format enables the OLT to manage the slave device, facilitating a unified management approach for the FTTR system. Furthermore, the existing communication protocol between the master and slave devices can be used, allowing the OLT to manage the slave device without significant adjustments, resulting in good application performance.

[0008] In some possible implementations, considering that multiple downlink ports of the master device are typically connected to multiple different slave devices, the second and third messages also include a second identifier of the downlink port on the master device associated with the slave device, so as to determine the specific slave gateway by combining the first and second identifiers.

[0009] In some possible implementations, the second and third messages are OMCI messages newly defined in this application. It should be understood that the standard format OMCI message is used to implement OLT management of the master gateway, while the newly defined OMCI message is used to implement OLT management of the slave gateway. The newly defined OMCI message is an extension based on the standard format OMCI message, which facilitates compatibility with existing standards and has better practical effects.

[0010] In some possible implementations, the device identifier field of the newly defined OMCI message indicates whether the OMCI message is a basic OMCI message or an extended OMCI message used to transmit information exchanged between the OLT and the slave device, so as to distinguish between standard format OMCI messages and newly defined OMCI messages through the device identifier field.

[0011] In some possible implementations, the second message also includes a verification field for verifying the integrity of the second message, and the third message also includes a verification field for verifying the integrity of the third message, thereby improving transmission reliability.

[0012] In some possible implementations, the first message includes a third identifier of the OLT. Sending a second message from the master device to the optical line terminal (OLT) based on the first message includes: the master device generating the second message based on the first message and sending the second message to the OLT based on the third identifier. Sending a fourth message from the master device to the slave device based on the third message includes: the master device generating the fourth message based on the third message and sending the fourth message to the slave device based on the first identifier.

[0013] In some possible implementations, the first and second messages have the same message payload, and / or the third and fourth messages have the same message payload. That is, the master device can transmit the message payload of the first message to the OLT via the second message, and the master device can also transmit the message payload of the third message to the slave device via the fourth message. It should be understood that this message payload can be considered as the message content to be transmitted and does not include the first and second identifiers. Optionally, the master device can also generate the message payload to be transmitted according to actual needs; that is, the first and second messages can have different message payloads, and the third and fourth messages can also have different message payloads.

[0014] In some possible implementations, before the master device receives the third message sent by the OLT, the method further includes: the master device sending a fifth message including a first identifier to the OLT, so that the OLT generates the third message based on the fifth message. That is, the master device reports the slave device's information to the OLT through the fifth message, so that the OLT can generate the third message including the first identifier.

[0015] Secondly, embodiments of this application provide a message transmission method executed by an OLT. In the uplink transmission direction, the OLT receives a second message sent by a master device, wherein the second message is generated by the master device based on a first message sent by a slave device, and both the first and second messages include a first identifier of the slave device. In the downlink transmission direction, the OLT sends a third message including the first identifier to the master device, so that the master device sends a fourth message to the slave device based on the third message.

[0016] In some possible implementations, the second and third messages also include a second identifier of the downlink port on the master device associated with the slave device.

[0017] In some possible implementations, the second and third messages are newly defined OMCI messages.

[0018] In some possible implementations, the device identifier field of the OMCI message indicates whether the OMCI message is a basic OMCI message or an extended OMCI message used to transmit information exchanged between the OLT and the slave device.

[0019] In some possible implementations, the second message may also include a verification field for verifying the integrity of the second message, and the third message may also include a verification field for verifying the integrity of the third message.

[0020] In some possible implementations, the first message and the second message have the same message payload, and / or the third message and the fourth message have the same message payload.

[0021] In some possible implementations, before the OLT sends the third message to the master device, the method further includes: the OLT receiving a fifth message including a first identifier sent by the master device. The OLT generates the third message based on the fifth message.

[0022] Thirdly, embodiments of this application provide a master device, which includes a processing unit and a transceiver unit. The transceiver unit is used to receive a first message sent by a slave device, the first message including a first identifier of the slave device. The processing unit is used to generate a second message based on the first message, the second message including the first identifier of the slave device. The transceiver unit is used to send the second message to an optical line terminal (OLT) based on the first message. The transceiver unit is used to receive a third message sent by the OLT, the third message including a first identifier. The processing unit is used to generate a fourth message based on the third message. The transceiver unit is used to send the second message to the slave device based on the third message.

[0023] In some possible implementations, the second and third messages also include a second identifier of the downlink port on the master device associated with the slave device.

[0024] In some possible implementations, the second and third messages are newly defined OMCI messages.

[0025] In some possible implementations, the device identifier field of the OMCI message indicates whether the OMCI message is a basic OMCI message or an extended OMCI message used to transmit information exchanged between the OLT and the slave device.

[0026] In some possible implementations, the second message may also include a verification field for verifying the integrity of the second message, and the third message may also include a verification field for verifying the integrity of the third message.

[0027] In some possible implementations, the first message includes a third identifier of the OLT, and the transceiver unit is specifically used to: send a second message to the OLT according to the third identifier, and send a fourth message to the slave device according to the first identifier.

[0028] In some possible implementations, the first message and the second message have the same message payload, and / or the third message and the fourth message have the same message payload.

[0029] In some possible implementations, before the transceiver unit receives the third message sent by the OLT, the transceiver unit is also used to send a fifth message including a first identifier to the OLT, so that the OLT generates the third message based on the fifth message.

[0030] Fourthly, embodiments of this application provide an OLT, which includes a processing unit and a transceiver unit. The transceiver unit is used to receive a second message sent by a master device, the second message being generated by the master device based on a first message sent by a slave device. The first message includes a first identifier of the slave device, and the second message also includes the first identifier. The processing unit is used to generate a third message, the third message including the first identifier. The transceiver unit is used to send the third message to the master device, so that the master device sends a fourth message to the slave device based on the third message.

[0031] In some possible implementations, the second and third messages also include a second identifier of the downlink port on the master device associated with the slave device.

[0032] In some possible implementations, the second and third messages are newly defined OMCI messages.

[0033] In some possible implementations, the device identifier field of the OMCI message indicates whether the OMCI message is a basic OMCI message or an extended OMCI message used to transmit information exchanged between the OLT and the slave device.

[0034] In some possible implementations, the second message may also include a verification field for verifying the integrity of the second message, and the third message may also include a verification field for verifying the integrity of the third message.

[0035] In some possible implementations, the first message and the second message have the same message payload, and / or the third message and the fourth message have the same message payload.

[0036] In some possible implementations, before the transceiver unit sends the third message to the master device, the transceiver unit is also configured to receive a fifth message including a first identifier sent by the master device, and the processing unit is also configured to generate a third message based on the fifth message.

[0037] Fifthly, embodiments of this application provide an optical communication system comprising a master device as described in any embodiment of the third aspect, an OLT as described in any embodiment of the fourth aspect, and a slave device. Messages are transmitted between the OLT and the slave device through the master device.

[0038] This application provides a message transmission method, a master device, an OLT, and an optical communication system, and newly defines the message format for transmission between the master device and the OLT in an FTTR system. In the uplink direction, the master device sends a second message to the OLT based on a first message sent by a slave device, wherein the second message includes a newly added first identifier of the slave device. In the downlink direction, the OLT also adds a first identifier to a third message sent to the master device, so that the master device can send a fourth message to the corresponding slave device based on the third message. In other words, this solution enables the OLT to manage slave devices, which is beneficial for unifying the management method of the FTTR system. Furthermore, the master device and slave device can use existing communication protocols without significant adjustments to achieve OLT management of slave devices, resulting in good application performance. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of the FTTH system architecture;

[0040] Figure 2 This is a schematic diagram of the FTTR system architecture;

[0041] Figure 3 This is a flowchart illustrating a message transmission method according to an embodiment of this application;

[0042] Figure 4 This is a schematic diagram illustrating a scenario in which the OLT manages the master and slave devices according to an embodiment of this application.

[0043] Figure 5 This is a newly defined basic OMCI message format in the embodiments of this application;

[0044] Figure 6 This is a newly defined extended OMCI message format in the embodiments of this application;

[0045] Figure 7 This is a schematic diagram of the structure of a possible main device in an embodiment of this application;

[0046] Figure 8 This is a schematic diagram of another possible main device in the embodiments of this application;

[0047] Figure 9 This is a schematic diagram of a possible OLT structure in an embodiment of this application;

[0048] Figure 10 This is a schematic diagram of another possible OLT structure in an embodiment of this application. Detailed Implementation

[0049] This application provides a message transmission method, a master device, an OLT, and an optical communication system. It defines a new message format for transmission between the master device and the OLT in the FTTR system, realizes the OLT's management of slave devices, and facilitates the unification of the management method of the FTTR system.

[0050] It should be noted that the terms "first," "second," "third," and "fourth," etc., in this application specification, claims, and the accompanying drawings are used to distinguish similar objects, not to limit a specific order or sequence. It should be understood that the above terms can be used interchangeably where appropriate so that the embodiments described in this application can be implemented in a sequence other than that described in this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or devices.

[0051] Passive optical network (PON) is a technology for implementing optical access networks. PON is a point-to-multipoint optical access technology. Current PON systems are mainly used in fiber-to-the-home (FTTH) scenarios, where each home user has only one optical network unit (ONU).

[0052] Figure 1This is a schematic diagram of the FTTH system architecture. The optical line terminal (OLT) connects to upper-layer network-side devices (such as switches and routers) and lower-layer devices (such as optical distribution networks, ODNs). The ODN includes passive optical splitters for optical power distribution, a backbone fiber connecting the passive optical splitter and the OLT, and branch fibers connecting the passive optical splitter and ONUs. During downlink data transmission, the ODN transmits the downlink data from the OLT to each ONU through the splitter; the ONUs selectively receive downlink data carrying their own identifiers. During uplink data transmission, the ODN combines the optical signals sent by N ONUs into a single optical signal and transmits it to the OLT. The ONU provides a user-side interface for the OAN and is also connected to the ODN. If the ONU also provides user port functionality, such as an Ethernet user port or a plain old telephone service (POTS) user port, it is called an optical network termination (ONT).

[0053] Building upon FTTH, to address the issue of home Wi-Fi coverage, fiber optic cables can be extended further into residents' rooms. Optical terminal equipment providing Wi-Fi access is installed inside the rooms, thus reducing the distance between the user's terminal and the Wi-Fi access point and improving signal quality. This application scenario is called Fiber to the Room (FTTR).

[0054] Figure 2This is a schematic diagram of the FTTR system architecture. FTTR and FTTH networks can be viewed as cascaded PON systems. In FTTH, the OLT is deployed in a central equipment room, and the ONU is deployed in the home's information box. The master device in FTTR can replace the ONU in FTTH, deployed in the home's information box. This master device in the FTTR scenario has similar functions to the OLT in the FTTH scenario, and also similar functions to the ONU in the FTTH scenario. That is to say, the master device in FTTR is a device that combines the functions of both OLT and ONU, acting as a connecting network device between FTTH and FTTR. The slave devices in FTTR can be deployed in each room of the home to connect to user terminals. These slave devices are essentially similar network devices to the ONU in FTTH. The difference is that in FTTH, the ONU is generally deployed in the information box, and there is usually an access point (AP) between it and the user terminal. In FTTR, the slave devices enter each room, and the slave gateway also has the function of an AP, allowing direct WiFi connection to the user terminal.

[0055] It should be understood that multiple slave devices can be deployed in an FTTR, with each slave device connected to a corresponding downlink port on the master device. The master device can achieve unified management and configuration of all slave devices. It should be noted that the master device can also be called a "master gateway," "master optical modem," or "master FTTR device," and the slave device can also be called a "slave gateway," "slave optical modem," or "slave FTTR device," etc. This application does not limit their specific names. For ease of explanation, the terms "master device" and "slave device" will be used consistently below.

[0056] Considering the relatively mature communication protocol between the OLT and the master device in current FTTH scenarios, enabling OLT management of the master device, but the lack of a unified management method for FTTR systems (i.e., the communication protocol between the OLT and slave devices is still immature), this application establishes a communication method between the OLT and the slave gateway by defining a new message format, facilitating the management of both. Specifically, if the communication between the OLT and the master gateway does not involve the slave gateway, they communicate using the existing standard-defined message format. If the communication involves the slave gateway, they communicate using the newly defined message format of this application. The message format between the master gateway and the slave gateway can be either the existing standard-defined format or the newly defined format of this application; no specific limitation is imposed. The message transmission method provided in this application is described in detail below.

[0057] Figure 3This is a flowchart illustrating a message transmission method according to an embodiment of this application. In this example, the message transmission method includes the following steps.

[0058] 101. The device sends the first message to the master device.

[0059] The first message sent from the slave device to the master device includes the slave device's identity (ID), the OLT's ID, and the message contents. It should be understood that this application does not limit the type of the first message. For example, the first message can be an optical network terminal management and control interface (OMCI) message defined in existing standards, or it can be an OMCI message newly defined in this application.

[0060] 102. The master device generates a second message based on the first message.

[0061] It should be noted that the second message includes the slave device's ID, so that the OLT can identify that the message is about a slave device. It should be understood that the master device can communicate with multiple slave devices simultaneously, each slave device connected to a corresponding downlink port on the master device. Optionally, the second message also includes the ID of the downlink port associated with the slave device on the master device, referred to simply as the port ID. That is, the master device determines the downlink port corresponding to the slave device based on the first message and adds the port ID to the second message.

[0062] As an example, the second message carries the same message payload as the first message. This means the master device can pass the message payload from the first message to the OLT via the second message. It should be understood that this message payload can be considered the message content to be transmitted and does not include the slave device's ID and port ID. As another example, the first and second messages can also have different message payloads; that is, the master device can also generate the message payload to be transmitted to the OLT according to actual needs.

[0063] In one possible implementation, the second message is specifically a newly defined OMCI message, which is an extension of the standard format. It should be understood that the standard OMCI message is used only for interaction between the OLT and the master device, and is not associated with the slave gateway. However, the second message sent by the master device to the OLT includes a message payload from the slave gateway. Therefore, new fields for carrying the slave device's ID and the master device's port ID need to be defined on top of the standard OMCI message format to distinguish it from the standard OMCI message. The format of the newly defined OMCI message will be described in detail later with reference to the accompanying drawings.

[0064] It should be noted that the newly defined device identifier field in the OMCI message includes a new definition. In the standard OMCI message format, the device identifier field is defined as 0x0A and 0x0B. 0x0A indicates that the OMCI message is a basic OMCI message used to transmit information between the OLT and the master device, while 0x0B indicates that the OMCI message is an extended OMCI message used to transmit information between the OLT and the master device. In the newly defined OMCI message, the device identifier field is newly defined as 0x1A and 0x1B. 0x1A indicates that the OMCI message is a basic OMCI message used to transmit information between the OLT and the slave device, while 0x1B indicates that the OMCI message is an extended OMCI message used to transmit information between the OLT and the slave device. This allows the OLT to identify whether a message is related to the master gateway or the slave gateway based on the device identifier field in the OMCI message.

[0065] 103. The master device sends a second message to the OLT based on the first message.

[0066] After generating the second message, the master device sends the second message to the OLT based on the OLT ID carried in the first message. In one possible implementation, the second message adopts a newly defined OMCI message format, and the master device specifically sends the second message to the OLT through the optical network unit management and control channel (OMCC).

[0067] 104. The OLT generates a third message.

[0068] It should be noted that the third message includes the slave device's ID and a message payload, which needs to be sent to the slave device. Optionally, the third message also includes the master device's port ID. As an example, the third message uses the newly defined OMCI message format, that is, the third message newly defines fields for carrying the slave device's ID and the master device's port ID.

[0069] Taking the third message using the newly defined OMCI message as an example, the device identifier field in the newly defined OMCI message has two new definitions: 0x1A and 0x1B. 0x1A indicates that the OMCI message is a basic OMCI message used to transmit information exchanged between the OLT and slave devices, while 0x1B indicates that the OMCI message is an extended OMCI message used to transmit information exchanged between the OLT and slave devices. In this way, the master gateway can identify whether the message is about itself or a slave gateway based on the device identifier field in the OMCI message.

[0070] As an example, in a scenario where uplink transmission precedes downlink transmission, since the second message carries the slave device's ID and port ID, the OLT specifically generates a third message that includes the slave device's ID and port ID based on the second message.

[0071] As another example, in a scenario where downlink transmission precedes uplink transmission, step 108 can be executed before step 104. In this step, the master device sends a fifth message to the OLT, reporting information about the slave device. This slave device information includes at least its ID, enabling the OLT to generate a third message containing the slave device's ID. Optionally, the master device may also report the port ID of the downlink port associated with the slave gateway to the OLT via the fifth message, allowing the OLT to generate a third message containing the port ID. It should be understood that the message reported by the master device to the OLT can use existing standard OMCI messages.

[0072] 105. The OLT sends a third message to the master device.

[0073] Taking the third message using the newly defined OMCI message format as an example, the OLT can send the third message to the master device through OMCC.

[0074] 106. The master device generates a fourth message based on the third message.

[0075] In one possible implementation, the fourth message uses a standard OMCI message format. This fourth message does not include the slave device's ID and the master device's port ID; that is, the master device retains the message payload from the third message but removes the slave device's ID and the master device's port ID. In this way, the master and slave devices can continue using the existing communication protocol without significant adjustments, enabling OLT management of the slave device and resulting in better application performance. In another possible implementation, the fourth message uses a newly defined OMCI message. This fourth message includes the slave device's ID and the master device's port ID, essentially meaning the master device forwards the received third message to the slave device.

[0076] As an example, the fourth message carries the same message payload as the third message. This means the master device can pass the message payload from the third message to the OLT via the fourth message. It should be understood that this message payload can be considered the message content to be transmitted and does not include the slave device's ID and port ID. As another example, the fourth and third messages can also have different message payloads; that is, the master device can also generate the message payload to be transmitted to the slave device according to actual needs.

[0077] 107. The master device sends a fourth message to the slave device based on the third message.

[0078] After the master device generates the fourth message, it determines the slave device corresponding to the fourth message based on the slave device ID carried in the third message, and sends the fourth message to the slave device.

[0079] It should be noted that there is no fixed timing relationship between steps 101-103 and steps 104-107. For example, steps 101-103 can be executed first, followed by steps 104-107, i.e., uplink transmission precedes downlink transmission. Alternatively, steps 104-107 can be executed first, followed by steps 101-103, i.e., downlink transmission precedes uplink transmission.

[0080] Figure 4 This is a schematic diagram illustrating a scenario where the OLT manages the master and slave devices in an embodiment of this application. As an example, module 1 of the master device and module 1 of the OLT are both used to generate standard-format OMCI messages, while module 2 of the master device and module 2 of the OLT are both used to generate newly defined OMCI messages. Both the standard-format OMCI messages and the newly defined OMCI messages are transmitted through a pre-defined interaction interface between the master device and the OLT. The OLT manages the master device through standard-format OMCI messages, and the OLT manages the slave devices through the newly defined OMCI messages. It should be understood that modules 1 and 2 in the OLT and modules 1 and 2 in the master device are only logical functional divisions; in practical applications, modules 1 and 2 can be independent or integrated.

[0081] The newly defined OMCI message format in this application is described in detail below. It should be understood that the newly defined OMCI message format is primarily used for the second and third messages transmitted between the OLT and the master gateway. Optionally, the first and fourth messages transmitted between the master gateway and the slave gateway can also use the newly defined OMCI message format. The newly defined OMCI message format includes a newly defined basic OMCI message format and a newly defined extended OMCI message format, which can be flexibly selected according to requirements in practical applications.

[0082] Figure 5 This is a newly defined basic OMCI message format in the embodiments of this application. For example... Figure 5As shown, the newly defined basic OMCI message includes the following fields in sequence: transaction correlation identifier, message type, device identifier, management entity identifier, port identifier, slave device identifier, message contents, and OMCI trailer. Among these, the port identifier and slave device identifier are newly added fields. Furthermore, the device identifier field has been redefined; for example, the device identifier field is 0x1A, used to indicate that the OMCI message is a basic OMCI message used to transmit interaction information between the OLT and the slave device.

[0083] It should be noted that the OMCI tail is used as a check field to verify the integrity of the OMCI message. In GPON systems, the cyclic redundancy check (CRC32) algorithm is used to verify the integrity of the OMCI message. In 10G GPON systems, the message integrity check (MIC) algorithm is used to verify the integrity of the OMCI message. Because the newly defined basic OMCI message format differs from the existing standard basic OMCI message format, the newly defined OMCI tail differs from the standard OMCI tail.

[0084] Table 1 below shows one possible form for the length of each field in the newly defined basic OMCI message format. It should be understood that... Figure 5 Table 1 is just a specific example. In practical applications, the above fields can also have other arrangements and specific lengths. For example, the port identifier field and the slave device identifier field can be swapped. No specific restrictions are made here.

[0085] Table 1

[0086]

[0087] Figure 6 This is a newly defined extended OMCI message format in the embodiments of this application. For example... Figure 6As shown, the newly defined basic OMCI message includes the following fields in sequence: transaction correlation identifier, message type, device identifier, management entity identifier, message contents length, port identifier, slave device identifier, message contents, and message integrity check (MIC). The maximum length of the newly defined extended OMCI message is 1980 bytes, and the maximum supported message contents length is 1964 bytes. The port identifier and slave device identifier are newly added fields. Furthermore, the device identifier field has been redefined; for example, the device identifier field is 0x1B, used to indicate that the OMCI message is an extended OMCI message used to transmit interaction information between the OLT and the slave device.

[0088] It should be noted that the MIC is used as a verification field to verify the integrity of the OMCI message. In GPON systems, the CRC32 algorithm is used to verify the integrity of the OMCI message. In 10G GPON systems, the MIC algorithm is used to verify the integrity of the OMCI message. Because the newly defined extended OMCI message format differs from the existing standard extended OMCI message format, the newly defined MIC field differs from the standard MIC field.

[0089] Table 2 below shows one possible form for the length of each field in the newly defined extended OMCI message format. It should be understood that... Figure 6 Table 2 is just a specific example. In practical applications, the above fields can also have other arrangements and specific lengths. For example, the port identifier field and the slave device identifier field can be swapped. No specific restrictions are made here.

[0090] Table 2

[0091]

[0092]

[0093] As described above, this application defines a new message format for transmission between the master device and the OLT in an FTTR system. In the uplink direction, the master device sends a second message to the OLT based on the first message sent by the slave device, where the second message includes a newly added first identifier for the slave device. In the downlink direction, the OLT also adds the first identifier to the third message sent to the master device, enabling the master device to send a fourth message to the corresponding slave device based on the third message. In other words, this solution enables the OLT to manage slave devices, facilitating a unified management approach for the FTTR system. Furthermore, the master and slave devices can utilize existing communication protocols without significant modifications, resulting in good application performance.

[0094] The main device and OLT provided in the embodiments of this application are described below.

[0095] Figure 7 This is a schematic diagram of the structure of a possible main device in an embodiment of this application. Figure 7 As shown, the main device includes a processing unit 201 and a transceiver unit 202. Specifically, the transceiver unit 202 is used to perform the above-described... Figure 3 In the illustrated embodiment, the master device performs message sending and receiving operations. The processing unit 201 is used to execute the above... Figure 3 The embodiments shown include other operations of the master device besides message sending and receiving.

[0096] Figure 8 This is a schematic diagram of another possible main device in an embodiment of this application. For example... Figure 8 As shown, the main device includes a processor 301 and a transceiver 302, which are interconnected via a line. It should be noted that the transceiver 302 is used to perform the above-described... Figure 3 In the illustrated embodiment, the master device performs message sending and receiving operations. Processor 301 is used to execute the above... Figure 3 The illustrated embodiment includes operations of the host device other than message sending and receiving. In some possible implementations, processor 301 includes the processing unit 201 described above, and transceiver 302 includes the transceiver unit 202 described above. Optionally, the host device may further include memory 303, wherein memory 303 is used to store program instructions and data.

[0097] Figure 9 This is a schematic diagram of a possible OLT structure in an embodiment of this application. Figure 9 As shown, the OLT includes a processing unit 401 and a transceiver unit 402. Specifically, the transceiver unit 402 is used to perform the above-described... Figure 3 In the illustrated embodiment, the OLT performs message sending and receiving operations. The processing unit 401 is used to execute the above... Figure 3The illustrated embodiment includes other OLT operations besides message sending and receiving.

[0098] Figure 10 This is a schematic diagram of another possible OLT structure in an embodiment of this application. Figure 10 As shown, the OLT includes a processor 501 and a transceiver 502, which are interconnected via a line. It should be noted that the transceiver 502 is used to perform the above-described... Figure 3 In the illustrated embodiment, the OLT performs message sending and receiving operations. The processor 501 is used to execute the above... Figure 3 The illustrated embodiment includes other OLT operations besides message sending and receiving. In some possible implementations, processor 501 includes the processing unit 401 described above, and transceiver 502 includes the transceiver unit 402 described above. Optionally, the OLT may also include memory 503, wherein memory 503 is used to store program instructions and data.

[0099] It should be noted that the above Figure 8 and Figure 10 The processor shown can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or at least one integrated circuit, used to execute relevant programs to implement the technical solutions provided in the embodiments of this application. Figure 8 and Figure 10 The memory shown can store the operating system and other applications. When the technical solutions provided in the embodiments of this application are implemented by software or firmware, the program code used to implement the technical solutions provided in the embodiments of this application is stored in the memory and executed by the processor. In one embodiment, the processor may include memory internally. In another embodiment, the processor and the memory are two independent structures.

[0100] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0101] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented in hardware, or instructed by a program to implement related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory or random access memory. Specifically, for example, the processing unit or processor can be a central processing unit, a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0102] When implemented using software, the method steps described in the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

Claims

1. A message transmission method, characterized in that, include: The master device receives a first message sent by the slave device. The first message includes a device identifier field. The value of the device identifier field of the first message is a first value, which indicates that the first message is a message for transmitting interactive information between the slave device and the optical line terminal (OLT). Specifically, the first value is 0x1A, which indicates that the first message is a basic message for transmitting interactive information between the slave device and the OLT; or, the first value is 0x1B, which indicates that the first message is an extended message for transmitting interactive information between the slave device and the OLT. or, The master device sends a fourth message to the slave device. The fourth message includes a device identifier field. The device identifier field of the fourth message takes a second value, which indicates that the fourth message is a message used to transmit interactive information between the slave device and the OLT. Specifically, the second value is 0x1A, which indicates that the fourth message is a basic message used to transmit interactive information between the slave device and the OLT; or, the second value is 0x1B, which indicates that the fourth message is an extended message used to transmit interactive information between the slave device and the OLT.

2. The method according to claim 1, characterized in that, After the master device receives the first message sent by the slave device, the method further includes: The master device generates a second message based on the first message and sends the second message to the OLT. The second message includes a device identifier field, and the value of the device identifier field of the second message is 0x1A or 0x1B. The 0x1A or 0x1B is used to indicate that the second message is a message used to transmit interactive information between the slave device and the OLT.

3. The method according to claim 1 or 2, characterized in that, Before the master device sends the fourth message to the slave device, the method further includes: The master device receives a third message from the OLT. The third message includes a device identifier field. The device identifier field of the third message takes the value 0x1A or 0x1B. The 0x1A or 0x1B is used to indicate that the third message is a message used to transmit interactive information between the slave device and the OLT. The master device generates the fourth message based on the third message.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The master device sends a fifth message to the OLT. The fifth message includes a device identifier field. The device identifier field of the fifth message has a value of 0x0A or 0x0B. The 0x0A or 0x0B is used to indicate that the fifth message is a message used to transmit interactive information between the master device and the OLT.

5. The method according to any one of claims 1 to 3, characterized in that, The first message is a basic message used to transmit interaction information between the slave device and the OLT. The first message further includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload field, and a tail field; or, The fourth message is a basic message used to transmit interaction information between the slave device and the OLT. The fourth message also includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload field, and a tail field.

6. The method according to any one of claims 1 to 3, characterized in that, The first message is an extended message used to transmit interaction information between the slave device and the OLT. The first message further includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload length field, a message payload field, and a message integrity verification field; or, The fourth message is an extended message used to transmit interaction information between the slave device and the OLT. The fourth message also includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload length field, a message payload field, and a message integrity verification field.

7. The method according to any one of claims 1 to 6, characterized in that, The device identifier field has a byte number of 4.

8. The method according to any one of claims 1 to 7, characterized in that, The device identifier field has a length of 1 byte.

9. A message transmission method, characterized in that, include: The slave device sends a first message to the master device. The first message includes a device identifier field. The value of the device identifier field in the first message is a first value, which indicates that the first message is a message used to transmit interactive information between the slave device and the optical line terminal (OLT). Specifically, the first value is 0x1A, which indicates that the first message is a basic message used to transmit interactive information between the slave device and the OLT; or, the first value is 0x1B, which indicates that the first message is an extended message used to transmit interactive information between the slave device and the OLT. or, The slave device receives a fourth message sent by the master device. The fourth message includes a device identifier field, and the device identifier field of the fourth message takes a second value. The second value is used to indicate that the fourth message is a message used to transmit interactive information between the slave device and the OLT. Specifically, the second value is 0x1A, which indicates that the fourth message is a basic message used to transmit interactive information between the slave device and the OLT; or, the second value is 0x1B, which indicates that the fourth message is an extended message used to transmit interactive information between the slave device and the OLT.

10. The method according to claim 9, characterized in that, The first message is a basic message used to transmit interaction information between the slave device and the OLT. The first message further includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload field, and a tail field; or, The fourth message is a basic message used to transmit interaction information between the slave device and the OLT. The fourth message also includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload field, and a tail field.

11. The method according to claim 9 or 10, characterized in that, The first message is an extended message used to transmit interaction information between the slave device and the OLT. The first message further includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload length field, a message payload field, and a message integrity verification field; or, The fourth message is an extended message used to transmit interaction information between the slave device and the OLT. The fourth message also includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload length field, a message payload field, and a message integrity verification field.

12. The method according to any one of claims 9 to 11, characterized in that, The device identifier field has a byte number of 4.

13. The method according to any one of claims 9 to 12, characterized in that, The device identifier field has a length of 1 byte.

14. A main device, characterized in that, The master device includes a transceiver unit, which is used for: A first message sent by a slave device is received. The first message includes a device identifier field. The value of the device identifier field of the first message is a first value, which indicates that the first message is a message for transmitting interactive information between the slave device and the optical line terminal (OLT). Specifically, the first value is 0x1A, which indicates that the first message is a basic message for transmitting interactive information between the slave device and the OLT; or, the first value is 0x1B, which indicates that the first message is an extended message for transmitting interactive information between the slave device and the OLT. or, A fourth message is sent to the slave device. The fourth message includes a device identifier field, and the value of the device identifier field of the fourth message is a second value. The second value is used to indicate that the fourth message is a message for transmitting interaction information between the slave device and the OLT. Specifically, the second value is 0x1A, which indicates that the fourth message is a basic message for transmitting interaction information between the slave device and the OLT; or, the second value is 0x1B, which indicates that the fourth message is an extended message for transmitting interaction information between the slave device and the OLT.

15. The main equipment according to claim 14, characterized in that, The main device further includes a processing unit, which is used for: Generate a second message based on the first message; The transceiver unit is also used for: The second message is sent to the OLT. The second message includes a device identifier field. The value of the device identifier field of the second message is 0x1A or 0x1B. The 0x1A or 0x1B is used to indicate that the second message is a message used to transmit interactive information between the slave device and the OLT.

16. The main equipment according to claim 15, characterized in that, The transceiver unit is also used for: A third message is received from the OLT. The third message includes a device identifier field. The device identifier field of the third message has a value of 0x1A or 0x1B. The 0x1A or 0x1B is used to indicate that the third message is a message used to transmit interactive information between the slave device and the OLT. The processing unit is also used for: The fourth message is generated based on the third message.

17. The main equipment according to any one of claims 14 to 16, characterized in that, The transceiver unit is also used for: A fifth message is sent to the OLT. The fifth message includes a device identifier field. The device identifier field of the fifth message has a value of 0x0A or 0x0B. The 0x0A or 0x0B is used to indicate that the fifth message is a message used to transmit interactive information between the master device and the OLT.

18. The main equipment according to any one of claims 14 to 17, characterized in that, The first message is a basic message used to transmit interaction information between the slave device and the OLT. The first message further includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload field, and a tail field; or, The fourth message is a basic message used to transmit interaction information between the slave device and the OLT. The fourth message also includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload field, and a tail field.

19. The main equipment according to any one of claims 14 to 17, characterized in that, The first message is an extended message used to transmit interaction information between the slave device and the OLT. The first message further includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload length field, a message payload field, and a message integrity verification field; or, The fourth message is an extended message used to transmit interaction information between the slave device and the OLT. The fourth message also includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload length field, a message payload field, and a message integrity verification field.

20. The main equipment according to any one of claims 14 to 19, characterized in that, The device identifier field has a byte number of 4.

21. The main equipment according to any one of claims 14 to 20, characterized in that, The device identifier field has a length of 1 byte.

22. A device, characterized in that, The slave device includes a transceiver unit, the transceiver unit being used for: A first message is sent to the master device. The first message includes a device identifier field. The value of the device identifier field of the first message is a first value, which indicates that the first message is a message for transmitting interactive information between the slave device and the optical line terminal (OLT). Specifically, the first value is 0x1A, which indicates that the first message is a basic message for transmitting interactive information between the slave device and the OLT; or, the first value is 0x1B, which indicates that the first message is an extended message for transmitting interactive information between the slave device and the OLT. or, The system receives a fourth message sent by the master device. The fourth message includes a device identifier field, and the device identifier field of the fourth message takes a second value. The second value is used to indicate that the fourth message is a message used to transmit interaction information between the slave device and the OLT. Specifically, the second value is 0x1A, which indicates that the fourth message is a basic message used to transmit interaction information between the slave device and the OLT; or, the second value is 0x1B, which indicates that the fourth message is an extended message used to transmit interaction information between the slave device and the OLT.

23. The slave device according to claim 22, characterized in that, The first message is a basic message used to transmit interaction information between the slave device and the OLT. The first message further includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload field, and a tail field; or, The fourth message is a basic message used to transmit interaction information between the slave device and the OLT. The fourth message also includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload field, and a tail field.

24. The slave device according to claim 22 or 23, characterized in that, The first message is an extended message used to transmit interaction information between the slave device and the OLT. The first message further includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload length field, a message payload field, and a message integrity verification field; or, The fourth message is an extended message used to transmit interaction information between the slave device and the OLT. The fourth message also includes a transaction-related identifier field, a message type field, a management entity identifier field, a message payload length field, a message payload field, and a message integrity verification field.

25. The slave device according to any one of claims 22 to 24, characterized in that, The device identifier field has a byte number of 4.

26. The slave device according to any one of claims 22 to 25, characterized in that, The device identifier field has a length of 1 byte.

27. A main device, characterized in that, The master device includes a transceiver and a processor, which work together to perform the method as described in any one of claims 1 to 8.

28. A device, characterized in that, The slave device includes a transceiver and a processor, the transceiver and the processor cooperating to perform the method as described in any one of claims 9 to 13.

29. An optical communication system, characterized in that, The optical communication system includes a master device and a slave device, the master device being used to perform the method as described in any one of claims 1 to 8, and the slave device being used to perform the method as described in any one of claims 9 to 13.

Images