Communication method for master device and slave device for fiber to the room (FTTR), and storage medium and electrode apparatus

Abstract

Provided in the embodiments of the present disclosure are a communication method and system for a master device and a slave device for a fiber to the room (FTTR). The method comprises: establishing a corresponding OMCI channel between a master device and a slave device for an FTTR on the basis of an uplink mode of the slave device; the master device receiving an attribute value change (AVC) notification from the slave device by means of the OMCI channel; the master device receiving a serial number of the slave device on the basis of the AVC notification, and completing secondary node (SN) authentication of the slave device; and the master device initiating synchronization of a master information block (MIB) to the slave device on the basis of the SN authentication, so as to perform communication between the master device and the slave device.

Description

Master-slave device communication method, storage medium and electronic device for fiber-to-the-room (FTTR)

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on Chinese patent application CN 202311511866.4, filed on November 14, 2023, entitled “Master-slave device communication method, storage medium and electronic device for fiber-to-the-room FTTR”, and claims the priority of the patent application, and all the disclosed contents thereof are incorporated into this application by reference. Technical Field

[0003] The embodiments of the present disclosure relate to the field of communications, and in particular to a master-slave device communication method, storage medium, and electronic device for fiber-to-the-room (FTTR). Background Art

[0004] Gigabit-capable passive optical network (GPON) technology is a passive optical network access technology based on the ITU-T G.9xx standards. GPON systems include optical line terminals (OLTs) and optical network units (ONUs). ITU-T G.988 is the internationally recognized standard for the ONU management and control interface (OMCI), and the OMCI protocol is a mandatory protocol for OLT management. The OMCI protocol is a low-level management protocol embedded in GPON / XGPON systems, used for basic configuration of the ONU's PON interface and is essential for GPON / XGPON systems.

[0005] The communications industry has been continuously accelerating fiber bandwidth upgrades. Currently, fiber access is now prevalent in most home networks, with fiber-to-the-home penetration reaching an average of 65% globally and as high as 91.3% in China. The continuous improvement of fiber access and other network infrastructure has provided a solid information foundation for the prosperity of internet services. Simultaneously, innovative business applications are emerging one after another, such as ultra-high-definition video, cloud VR, cloud gaming, online education, and remote work, placing increasingly stringent demands on network bandwidth, latency, and jitter.

[0006] Fiber to the Room (FTTR) networks extend fiber to every room and interconnect with home gateways through the deployment of edge optical network units (ONUs), maximizing the high-quality development of new services and applications such as online education, working from home, and home entertainment. Currently, in FTTR networks, the master device can manage the slave gateways for PON uplinks, but lacks effective management of the various uplink methods between the master and slave devices, such as Ethernet and wireless uplinks.

[0007] Summary of the Invention

[0008] The embodiments of the present disclosure provide a master-slave device communication method, a storage medium, and an electronic device for a fiber-to-the-room (FTTR) system.

[0009] According to one embodiment of the present disclosure, a master-slave device communication method for a fiber-to-the-room (FTTR) is provided, comprising: establishing a corresponding passive optical network management and control interface (OMCI) channel between a master device and a slave device of the FTTR according to an uplink mode of the slave device; the master device receiving an attribute value change (AVC) notification from the slave device via the OMCI channel; the master device receiving a serial number of the slave device based on the AVC notification and completing secondary node (SN) authentication of the slave device; and the master device initiating master information block (MIB) synchronization to the slave device based on the SN authentication to enable communication between the master device and the slave device.

[0010] According to another embodiment of the present disclosure, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when running.

[0011] According to another embodiment of the present disclosure, an electronic device is 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 one of the above method embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG1 is a hardware structure block diagram of a mobile terminal of a master-slave device communication method for FTTR according to an embodiment of the present disclosure;

[0013] FIG2 is a network architecture diagram illustrating the operation of the master-slave device communication method for FTTR according to an embodiment of the present disclosure;

[0014] FIG3 is a flow chart of a master-slave device communication method for FTTR according to an embodiment of the present disclosure;

[0015] FIG4 is a structural block diagram of a master-slave device communication apparatus for FTTR according to an embodiment of the present disclosure;

[0016] FIG5 is a schematic diagram of a FTTR master-slave device communication model according to an embodiment of the present disclosure;

[0017] FIG6 is a diagram showing the communication principle of master and slave devices in FTTR based on different uplink modes according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0018] Hereinafter, the embodiments of the present disclosure will be described in detail with reference to the accompanying drawings and in combination with the embodiments.

[0019] It should be noted that the terms "first", "second", etc. in the description and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0020] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking operation on a mobile terminal as an example, FIG1 is a hardware structure block diagram of a mobile terminal of a master-slave device communication method of an FTTR according to an embodiment of the present disclosure. As shown in FIG1 , the mobile terminal may include one or more (only one is shown in FIG1 ) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the mobile terminal may also include a transmission device 106 and an input / output device 108 for communication functions. It will be understood by those skilled in the art that the structure shown in FIG1 is only for illustration and does not limit the structure of the mobile terminal. For example, the mobile terminal may also include more or fewer components than those shown in FIG1 , or have a configuration different from that shown in FIG1 .

[0021] Memory 104 can be used to store computer programs, such as application software programs and modules, such as the computer program corresponding to the master-slave device communication method for FTTR in the embodiments of the present disclosure. Processor 102 executes the computer programs stored in memory 104 to execute various functional applications and data processing, thereby implementing the aforementioned methods. Memory 104 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 104 may further include memory remotely located from processor 102, which can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0022] The transmission device 106 is used to receive or send data via a network. A specific example of the aforementioned network may include a wireless network provided by the mobile terminal's communications provider. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0023] The embodiment of the present application can run on the network architecture shown in Figure 2. Figure 2 is a network architecture diagram of the master-slave device communication method of the FTTR according to the embodiment of the present disclosure. As shown in Figure 2, the network architecture includes: a master device and slave devices 1-3, the master device serves as an OMCI server (OMCI Server), and the slave device serves as an OMCI client (OMCI Client), wherein, Master device: home device, connected to the OLT at the top and the slave device at the bottom. Slave devices 1-3: arranged in each room of the user, connected to the master device in different ways. The following is a specific description of the slave gateway access method: Slave device 1: PON uplink, using GEM frame (GEM frame) to carry OMCI messages. Slave device 2: Ethernet uplink, using Ethernet frame (Ethernet frame) to carry OMCI messages. Slave device 3: Wireless uplink, using Ethernet frame to carry OMCI messages.

[0024] In this embodiment, a master-slave device communication method for FTTR running on the above-mentioned mobile terminal or network architecture is provided. FIG3 is a flow chart of the master-slave device communication method for FTTR according to an embodiment of the present disclosure. As shown in FIG3 , the flow chart includes the following steps:

[0025] Step S302: A corresponding OMCI channel is established between the FTTR master device and the slave device according to the uplink mode of the slave device;

[0026] In an exemplary embodiment, a corresponding passive optical network management and control interface OMCI channel is established according to the uplink mode of the slave device, including: when the uplink mode of the slave device is Ethernet or wireless, the master device establishes a passive optical network management and control interface OMCI channel with the slave device based on the Ethernet frame; when the uplink mode of the slave device is a passive optical network PON, the master device establishes an OMCI channel with the slave device based on the GEM frame.

[0027] Step S304: The master device receives an attribute value change AVC notification from the slave device via the OMCI channel.

[0028] In an exemplary embodiment, the master device receives an attribute value change AVC notification from the slave device through the OMCI channel, including: the master device receives the AVC notification from the slave device through the OMCI channel, and the AVC notification includes at least an operation status attribute field of the access node port entity of the slave device.

[0029] In actual implementation, the operation status attribute field of the AVC notification can be used to indicate whether the status of the slave device is a deactivated state or an activated state.

[0030] In an exemplary embodiment, the types of the access node port entity include at least: an Ethernet access node port entity; a wireless access node port entity; and a PON access node port entity.

[0031] In an exemplary embodiment, an Ethernet access node port entity includes at least: a managed entity number attribute field, an operation status attribute field, a management status attribute field, a maximum bit rate attribute field, a current bit rate attribute field, and a duplex mode attribute field; a wireless access node port entity includes at least: a managed entity number attribute field, an operation status attribute field, a management status attribute field, an access frequency band attribute field, a wireless signal strength attribute field, an access channel attribute field, and an uplink and downlink negotiated rate attribute field; and a PON access node port entity includes at least: a managed entity number attribute field, an operation status attribute field, and a management status attribute field.

[0032] In actual implementation, different types of access node port entities may have different field settings, and the field content may be adjusted according to actual conditions.

[0033] Step S306: The master device receives the serial number of the slave device according to the AVC notification and completes the SN authentication of the slave device's secondary node.

[0034] In an exemplary embodiment, the master device receives the serial number of the slave device based on the AVC notification and completes the SN authentication of the slave device's auxiliary node, including: when the AVC notification indicates that the operating status of the slave device is activated, the master device sends a query message to query the serial number of the slave device; the master device receives the serial number reported by the slave device; and the master device performs SN authentication on the slave device.

[0035] In an exemplary embodiment, the master device performs SN authentication on the slave device, including: if the master device successfully performs SN authentication on the slave device, the master device initiates MIB synchronization to the slave device; if the master device fails to perform SN authentication on the slave device, the master device takes the slave device offline.

[0036] In actual implementation, if the slave device has been registered on the master device, the authentication will be successful; if the slave device has not been registered on the master device, the authentication will fail.

[0037] Step S308: The master device initiates master information block (MIB) synchronization to the slave device based on the SN authentication, so as to enable communication between the master device and the slave device.

[0038] In an exemplary embodiment, after the master device initiates master information block (MIB) synchronization to the slave device, the method further includes: the master device sending a configuration instruction or query message to the slave device; and the master device receiving alarm information or AVC notification reported by the slave device.

[0039] Through the above steps, a master-slave device communication method for fiber-to-the-room (FTTR) is provided, wherein a corresponding OMCI channel is established between the master and slave devices of the FTTR according to the uplink mode of the slave device; the master device receives the AVC notification of attribute value changes from the slave device through the OMCI channel; the master device receives the serial number of the slave device based on the AVC notification and completes the SN authentication of the slave device's auxiliary node; the master device initiates master information block (MIB) synchronization to the slave device based on the SN authentication to communicate with the master device. This solves the problem of the inability to effectively manage multiple uplink modes between master and slave devices in related FTTR communications, and achieves the effect of effectively managing multiple uplink modes between master and slave devices and reducing the complexity of management and control.

[0040] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the embodiment of the present disclosure is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD-ROM), including a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the method described in the embodiment of the present disclosure.

[0041] This embodiment also provides a master-slave communication device for FTTR, which is used to implement the above-mentioned embodiments and preferred implementations. Details already described are omitted for clarity. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. While the devices described in the following embodiments are preferably implemented using software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0042] Figure 4 is a structural block diagram of the master-slave device communication device of the FTTR according to an embodiment of the present disclosure. As shown in Figure 4, the communication device 40 includes: a channel establishment module 410, which is configured to establish a corresponding OMCI channel between the master device and the slave device of the FTTR according to the uplink mode of the slave device; a status notification module 420, which is configured to receive the attribute value change AVC notification from the slave device through the OMCI channel; an authentication module 430, which is configured to receive the serial number of the slave device according to the AVC notification and complete the SN authentication of the slave device auxiliary node; a synchronization module 440, which is configured to initiate master information block MIB synchronization to the slave device according to the SN authentication to facilitate communication between the master device and the slave device.

[0043] In the embodiments of the present disclosure, the communication device can be provided on the master device side, or independently provided outside the master device and the slave device. In actual implementation, the information transmission and reception of the communication device can be adjusted according to actual circumstances, and the communication device can be provided on the slave device side. Those skilled in the art should understand that the module definition and module function division of the communication device described above are merely examples and are not specific limitations. In actual implementation, the module definition and module function division of the communication device can be adjusted according to actual circumstances.

[0044] It should be noted that the above modules can be implemented through software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0045] An embodiment of the present disclosure further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when running.

[0046] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0047] An embodiment of the present disclosure further provides 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 execute the steps in any one of the above method embodiments.

[0048] In an 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.

[0049] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail here.

[0050] Obviously, those skilled in the art should understand that the modules or steps of the above-mentioned embodiments of the present disclosure can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented using program codes executable by the computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be performed in a different order than herein, or they can be made into individual integrated circuit modules, or multiple modules or steps can be made into a single integrated circuit module for implementation. Thus, the embodiments of the present disclosure are not limited to any specific combination of hardware and software.

[0051] In order to enable those skilled in the art to better understand the technical solutions of the embodiments of the present disclosure, they are described below in conjunction with different embodiments.

[0052] Example 1

[0053] In the embodiment of the present disclosure, the master device acts as an OMCI server (OMCI Server), and the slave device acts as an OMCI client (OMCI Client). The master device uniformly manages multiple upstream modes of the slave device and defines the Sub FTTR Unit OMCI Ethernet frame to carry the management and control messages. The slave device automatically discovers and registers multiple upstream modes, defines the sub-fiber to room unit access node interface entity (Sub FTTR Unit Access node interface Port, Sub FTTR Unit ANI Port) management object and AVC notification message. The multiple upstream modes of the slave device are managed by a unified OMCI business management model, and the virtual GEM port (virtual GEM port) and the access node interface instance pointer (ANI Port instance pointer) are defined to construct the slave device business management model.

[0054] Figure 5 is a schematic diagram of the FTTR master-slave device communication model according to an embodiment of the present disclosure. As shown in Figure 5, Ethernet uplink and Wireless uplink messages are carried by the Sub FTTR Unit OMCI Ethernet frame, or Ethernet frame. In Figure 5, "Software image" represents the software image, "ONU-G" represents the optical network unit entity, and "ONT DATA" represents the optical transport network data. In the embodiment of the present disclosure, the Ethernet frame is defined as shown in the following table:

[0055] Table 1 Ethernet frame field definition example table

[0056] The above OMCI message is different from the extended OMCI message on G988. In the embodiment of the present disclosure, the OMCI message is defined as shown in the following table:

[0057] Table 2 OMCI message field definition example

[0058] FIG6 is a diagram showing a master-slave communication principle of an FTTR based on different uplink modes according to an embodiment of the present disclosure, as shown in FIG6 , including the following steps:

[0059] Step 601: An OMCI channel is established between the master device and the slave device based on a Gem frame (applicable to PON uplink) or an Ethernet frame (applicable to Ethernet / Wireless uplink);

[0060] Step 602: After the channel is established, the slave device sends an AVC notification to inform the master device that the slave device status has changed from disabled to enabled. PON upstream slave devices report this through the PON access node port entity (PON ANI Port entity), Ethernet upstream slave devices report this through the Ethernet access node port entity (Ethernet ANI Port entity), and Wireless upstream slave devices report this through the wireless access node port entity (Wireless ANI Port entity).

[0061] Step 603: After receiving the AVC notification sent by the slave device, the master device sends a message to query the serial number of the slave device;

[0062] Step 604: The slave device reports its own serial number.

[0063] Step 605: The slave device SN is successfully authenticated, and the master device initiates MIB synchronization;

[0064] Step 606: After the MIB is synchronized, the master device can initiate a configuration or query message to the slave device;

[0065] Step 607: The slave device reports the alarm and AVC notification to the master device.

[0066] Example 2

[0067] In the second embodiment of the present disclosure, the master-slave device communication in which the uplink mode of the slave device is a passive optical network PON is introduced.

[0068] First, a PON access node port entity (PON ANI Port entity) is defined, as shown in Table 3. In the embodiment of the present disclosure, the ONU automatically creates an instance for each PON physical port.

[0069] Table 3 PON ANI Port entity definition example

[0070] In the embodiment of the present disclosure, the master-slave communication message is constructed based on the Gem frame format, and the uplink mode of the slave device is the master-slave device communication process of the passive optical network PON as follows:

[0071] Step 701: Power on the slave device, connect the optical fiber to the LAN side PON port of the master device, and the master device automatically discovers the slave device and establishes an OMCI channel with the slave device based on the Gem frame.

[0072] Step 702: After the channel is established, the slave device sends an AVC notification of the PON ANI Port entity to inform the master device that the slave device status has changed and the current operating state is active (0).

[0073] Step 703: After receiving the AVC notification from the slave device, the master device sends a message to query the serial number of the slave device.

[0074] In the embodiment of the present disclosure, the above AVC notification may be sent in the form of a list, and the specific definitions are shown in the following table:

[0075] Table 4 AVC notification list example

[0076] Step 704: The slave device reports its own serial number.

[0077] Step 705: The master device receives the slave device SN and determines whether the slave device has been registered on the master device. The master device then proceeds to steps 706 and 707 based on the result.

[0078] Step 706: The slave device has been registered on the master device and has been successfully authenticated. The master device initiates MIB synchronization to the authenticated slave device, and registration is completed.

[0079] Step 707: The slave device has not been registered on the master device, authentication fails, and the master device takes the slave device offline.

[0080] Example 3

[0081] In the third embodiment of the present disclosure, the master-slave device communication in which the uplink mode of the slave device is Ethernet is introduced.

[0082] In the embodiment of the present disclosure, the ONU automatically creates an instance for each Ethernet ANI port. First, the Ethernet access node port entity (Ethernet ANI Port entity) is defined, as shown in Table 5:

[0083] Table 5 Ethernet ANI Port entity definition example

[0084] In the embodiment of the present disclosure, the master-slave communication message is constructed based on the Sub FTTR Unit OMCI Ethernet frame format, that is, the Ethernet frame format.

[0085] The master-slave communication process when the slave device's uplink mode is Ethernet is as follows:

[0086] Step 801: Power on the slave device, connect the LAN ports of the master device and the slave device via a network cable, and the master device automatically discovers the slave device and establishes an OMCI channel with the slave device based on an Ethernet frame.

[0087] Step 802: After the channel is established, the slave device sends an AVC notification of the Ethernet ANI Port entity to inform the master device that the slave device status has changed and the current operating status is active (0).

[0088] In the embodiment of the present disclosure, the above AVC notification may be sent in the form of a list, and the specific definitions are shown in the following table:

[0089] Table 6 AVC notification list example

[0090] The message formats that AVC notifications can take are shown in the following table:

[0091] Table 7 Example of AVC Notification Message Format

[0092] Step 803: After receiving the AVC notification from the slave device, the master device sends a message to query the serial number of the slave device.

[0093] Step 804: The slave device reports its own serial number.

[0094] Step 805: The master device receives the slave device SN and determines whether the slave device has been registered on the master device. The master device then proceeds to steps 806 and 807 based on the result.

[0095] Step 806: The slave device has been registered on the master device and has been successfully authenticated. The master device initiates MIB synchronization to the authenticated slave device, and registration is completed.

[0096] Step 807: The slave device has not been registered on the master device, and the authentication fails. The master device takes the slave device offline.

[0097] Step 808: The master device issues a configuration: set the MTU of the slave device's LAN1 port to 1980 (this step assumes that the slave device has been successfully authenticated).

[0098] Step 809: After receiving the information, the slave device performs corresponding settings and returns the execution result to the master device.

[0099] In step 808, the master device may send configurations in the following message format:

[0100] Table 8 Example of message format for configuration sent by the master device

[0101] Example 4

[0102] In the fourth embodiment of the present disclosure, the master-slave device communication in which the uplink mode of the slave device is wireless uplink is introduced.

[0103] In the disclosed embodiment, the ONU automatically creates an instance for each wireless ANI port.

[0104] First, define the wireless access node port entity (Wireless ANI Port entity), as shown in Table 9:

[0105] Table 9 Wireless ANI Port entity definition example

[0106] In the embodiment of the present disclosure, the master-slave communication message is constructed based on the Sub FTTR Unit OMCI Ethernet frame format, that is, the Ethernet frame format.

[0107] The master-slave communication process when the slave device's uplink mode is wireless is as follows:

[0108] Step 901: The slave device is powered on and connected to the master device via Wireless. The master device automatically discovers the slave device and establishes an OMCI channel with the slave device based on an Ethernet frame.

[0109] Step 902: After the channel is established, the slave device sends an AVC notification of the Wireless ANI Port entity to inform the master device that the slave device status has changed and the current operating state is active (0).

[0110] In the embodiment of the present disclosure, the above AVC notification may be sent in the form of a list, and the specific definitions are shown in the following table:

[0111] Table 10 AVC notification list example

[0112] The message formats that AVC notifications can take are shown in the following table:

[0113] Table 11 Example of AVC Notification Message Format

[0114] Step 903: After receiving the AVC notification from the slave device, the master device sends a message to query the serial number of the slave device.

[0115] Step 904: The slave device reports its own serial number.

[0116] Step 905: The master device receives the slave device SN and determines whether the slave device has been registered on the master device. The master device then proceeds to steps 906 and 907 based on the result.

[0117] Step 906: The slave device has been registered on the master device and has been successfully authenticated. The master device initiates MIB synchronization to the authenticated slave device, and registration is completed.

[0118] Step 907: The slave device has not been registered on the master device, authentication fails, and the master device takes the slave device offline.

[0119] Step 908: The master device queries the software version number of the slave device (the prerequisite for this step is that the slave device has been successfully authenticated);

[0120] Step 909: The slave device returns the current software version number to the master device.

[0121] The message format returned from the device can be as shown in Table 12:

[0122] Table 12 Example of message format for messages returned from the device

[0123] With the emergence of innovative business applications, such as ultra-high-definition video, cloud VR, cloud gaming, online education, and remote work, the requirements for network bandwidth, latency, and jitter are becoming increasingly higher. FTTRs deploy edge ONUs to interconnect with home gateways, ensuring the high-quality development of new business applications such as online education, home office, and home entertainment. The disclosed embodiments provide a master-slave device communication method for FTTRs. This method uses the standard OMCI protocol to uniformly manage slave devices with multiple uplink modes, reducing management complexity, improving user experience, and facilitating interoperability and deployment.

[0124] The above description is merely a preferred embodiment of the present disclosure and is not intended to limit the present disclosure. Those skilled in the art will appreciate that various modifications and variations of the present disclosure are possible. Any modifications, equivalent substitutions, or improvements made within the principles of the present disclosure should be included within the scope of protection of the present disclosure.

Claims

1. A master-slave device communication method of fiber to the room FTTR, comprising: A corresponding passive optical network management and control interface OMCI channel is established between the master device and the slave device of the FTTR according to the uplink mode of the slave device; The master device receives an attribute value change AVC notification from the slave device through the OMCI channel; The master device receives the serial number of the slave device according to the AVC notification, and completes the secondary node SN authentication of the slave device; The master device initiates master information block MIB synchronization to the slave device according to the SN authentication, so as to perform communication between the master device and the slave device.

2. The method according to claim 1, wherein: According to the uplink mode of the slave device, a corresponding passive optical network management and control interface OMCI channel is established, including: When the uplink mode of the slave device is Ethernet or wireless, the master device establishes a passive optical network management and control interface OMCI channel with the slave device based on the Ethernet frame; In the case that the uplink mode of the slave device is a passive optical network PON, the master device establishes an OMCI channel with the slave device based on a gem frame.

3. The method according to claim 1, wherein: The master device receives the attribute value change AVC notification from the slave device through the OMCI channel, including: The master device receives the AVC notification from the slave device through the OMCI channel, where the AVC notification at least includes an operation status attribute field of an access node port entity of the slave device.

4. The method according to claim 3, wherein: The types of the access node port entities include at least: Ethernet access node port entity; Radio access node port entity; PON access node port entity.

5. The method according to claim 4, wherein: The Ethernet access node port entity at least includes: a managed entity number attribute field, an operation status attribute field, a management status attribute field, a maximum bit rate attribute field, a current bit rate attribute field, and a duplex mode attribute field; The wireless access node port entity at least includes: a managed entity number attribute field, an operation status attribute field, a management status attribute field, an access frequency band attribute field, a wireless signal strength attribute field, an access channel attribute field, and an uplink and downlink negotiation rate attribute field; The PON access node port entity at least includes: a managed entity number attribute field, an operation status attribute field, and a management status attribute field.

6. The method according to claim 1, wherein: The master device receives the serial number of the slave device according to the AVC notification, and completes the secondary node SN authentication of the slave device, including: In a case where the AVC notification indicates that the operation state of the slave device is an activated state, the master device sends a query message to query the serial number of the slave device; The master device receives the sequence number reported by the slave device; The master device performs the SN authentication on the slave device.

7. The method according to claim 6, wherein: The master device performs the SN authentication on the slave device, including: When the master device successfully performs the SN authentication on the slave device, the master device initiates MIB synchronization to the slave device; In the case that the master device fails to perform the SN authentication on the slave device, the master device takes the slave device offline.

8. The method according to claim 1, wherein: After the master device initiates master information block MIB synchronization to the slave device, the method further includes: The master device sends a configuration instruction or a query message to the slave device; The master device receives the alarm information or AVC notification reported by the slave device.

9. A computer-readable storage medium having a computer program stored therein, wherein: When the computer program is executed by a processor, the method described in any one of claims 1 to 8 is implemented.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of claims 1 to 8 when executing the computer program.

Images