An omci client protocol stack failure processing method and device

Abstract

The present application relates to the field of communication technology, and provides an OMCI client protocol stack fault processing method and device. The method comprises: using a target information base to process a first forwarding message to obtain a second forwarding message; wherein the first forwarding message is obtained by re-encapsulating a downlink OMCI message of an OLT device by a master gateway and is transmitted to a slave gateway; the target information base is transmitted to the slave gateway by the master gateway; the second forwarding message is transmitted to the master gateway, the master gateway re-encapsulates the second forwarding message to obtain a first response message, and the first response message is transmitted to the OLT device. After the OMCI client of the master gateway fails, the target information base is stored in the slave gateway, the communication channel between the master gateway and the slave gateway is reused, and the slave gateway processes the message, so that the slave gateway replaces the master gateway to use the target information base to process the downlink OMCI message of the OLT device, thereby maintaining the normal operation of the FTTR terminal device.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a method and apparatus for handling OMCI client protocol stack faults. Background Technology

[0002] In an FTTR (Fiber to the Room) system, the OMCI (ONU Management and Control Interface) client protocol stack of the main gateway serves as the control medium for the OLT (Optical Line Terminal) central office control of the ONT (Optical Network Terminal) terminal. It not only undertakes the function of establishing and releasing connections between the OLT and the FTTR main gateway, but also provides functions such as control, identification, data collection from the main gateway, and data provision, and supports some fault management and security management functions. The comprehensive management functions of the main gateway OMCI client protocol stack necessitate data interaction with various functional modules. If a functional module malfunctions during business operations, it is highly likely to cause operational abnormalities in the main gateway OMCI client protocol stack, such as a dead or blocked protocol stack. In this case, the main gateway OMCI client protocol stack can no longer properly process downlink OMCI messages from the OLT device and perform configuration distribution or configuration readback operations on the various functional modules of the main gateway. This results in the OLT device being unable to receive the corresponding response messages. When the OLT device detects that downlink OMCI messages have not received a response multiple times, it will add the main gateway to its blacklist, deregister, or even interrupt the service, causing the FTTR terminal device to become unmanaged, experience service interruption, or even go offline.

[0003] Therefore, overcoming the shortcomings of the existing technology is an urgent problem to be solved in this technical field. Summary of the Invention

[0004] The technical problem this invention aims to solve is that when the main gateway OMCI client fails, it cannot reply to OLT messages in a timely manner, leading to the FTTR terminal device becoming unmanaged, experiencing service interruption, or going offline.

[0005] The present invention adopts the following technical solution:

[0006] This invention provides a method for handling OMCI client protocol stack faults, including:

[0007] The first forwarded message is processed using the target information database to obtain the second forwarded message; wherein, the first forwarded message is obtained by the main gateway re-encapsulating the downlink OMCI message of the OLT device and transmitting it to the sub-gateway; the target information database is transmitted from the main gateway to the sub-gateway;

[0008] The second forwarded message is transmitted to the main gateway so that the main gateway can re-encapsulate the second forwarded message to obtain the first response message, and then transmit the first response message to the OLT device.

[0009] Preferably, before processing the first forwarded message using the target information database, the method further includes:

[0010] A first information database synchronization message is sent to the main gateway. The first information database synchronization message carries a preset synchronization identifier so that the main gateway can identify the first information database synchronization message according to the preset synchronization identifier and transmit the target information database to the sub-gateway according to the first information database synchronization message.

[0011] Preferably, after the OMCI client of the main gateway recovers from a failure, the method further includes:

[0012] Receive the second information database synchronization message from the main gateway and parse the second information database synchronization message;

[0013] If the second information database synchronization message is parsed to contain a preset synchronization identifier, the target information database is transmitted to the main gateway so that the main gateway can use the target information database to process subsequent downlink OMCI messages of the OLT device.

[0014] Secondly, the present invention also provides an OMCI client protocol stack fault handling method, which transmits a target information database to a sub-gateway to monitor the fault status of the OMCI client. When a fault is detected in the OMCI client, the method includes:

[0015] The downlink OMCI message from the OLT device is re-encapsulated to obtain the first forwarding message. The first forwarding message is then forwarded to the sub-gateway so that the sub-gateway can process the first forwarding message to obtain the second forwarding message.

[0016] The system receives a second forwarding message from the sub-gateway, re-encapsulates the second forwarding message to obtain a first response message, and transmits the first response message to the OLT device.

[0017] Preferably, the target information database is a shared database between the OMCI client and the OMCI server, and the transmission of the target information database to the sub-gateway specifically includes:

[0018] The OMCI server receives a first information database synchronization message from the sub-gateway and parses the first information database synchronization message;

[0019] If the parsed first information database synchronization message contains a preset synchronization identifier, then the target information database is transmitted to the sub-gateway.

[0020] Preferably, transmitting the target information database to the sub-gateway specifically includes:

[0021] The OMCI server accesses the target information database, calculates the number of instances contained in the first client database, and transmits the number of instances to the sub-gateway so that the sub-gateway can send an instance synchronization message to the OMCI server based on the number of instances.

[0022] The OMCI server receives instance synchronization messages from the sub-gateway, parses the instance sequence number from the instance synchronization message, and transmits the instance corresponding to the instance sequence number to the sub-gateway.

[0023] Preferably, the step of receiving a downlink OMCI message from an OLT device, re-encapsulating the downlink OMCI message to obtain a first forwarding message, and forwarding the first forwarding message to the sub-gateway specifically includes:

[0024] The message transmission and reception control module receives downlink OMCI messages from the OLT device and forwards the downlink OMCI messages to the OMCI server;

[0025] The OMCI server carries a preset identifier in the downlink OMCI message to obtain a first forwarding message, and forwards the first forwarding message to the sub-gateway so that the sub-gateway can identify the first forwarding message according to the preset identifier.

[0026] Preferably, the step of receiving the second forwarded message from the sub-gateway, re-encapsulating the second forwarded message to obtain a first response message, and transmitting the first response message to the OLT device specifically includes:

[0027] The OMCI server receives the second forwarded message from the sub-gateway and parses the second forwarded message;

[0028] If the second forwarding message is parsed to carry a preset identifier, then the preset identifier is removed from the second forwarding message to obtain the first response message, and the first response message is forwarded to the message sending and receiving control module.

[0029] The message transmission and reception control module transmits the first response message to the OLT device.

[0030] Preferably, after detecting a fault in the OMCI client, the method further includes:

[0031] Monitor the fault recovery status of the OMCI client;

[0032] When the OMCI client fault recovery is detected, a second information database synchronization message is sent to the sub-gateway so that the sub-gateway can send the target information database to the main gateway according to the second information database synchronization message;

[0033] The main gateway receives the target information database so that the OMCI client can use the target information database to process subsequent downlink OMCI messages from the OLT device.

[0034] Thirdly, the present invention also provides an OMCI client protocol stack fault handling apparatus for implementing the OMCI client protocol stack fault handling method described in the first or second aspect, the apparatus comprising:

[0035] At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the processor for performing the OMCI client protocol stack fault handling method described in the first aspect.

[0036] Fourthly, the present invention also provides a non-volatile computer storage medium storing computer-executable instructions that are executed by one or more processors to perform the OMCI client protocol stack fault handling method described in the first or second aspect.

[0037] This invention stores a target information database in a sub-gateway after a failure occurs in the OMCI client of the main gateway, and reuses the communication channel between the main gateway and the sub-gateway, as well as the sub-gateway's ability to process messages. This allows the sub-gateway to replace the main gateway in using the target information database to process downlink OMCI messages of the OLT device, thereby maintaining the normal operation of the FTTR terminal device. Attached Figure Description

[0038] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments of the present invention will be briefly described below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0039] Figure 1 This is a schematic diagram illustrating the interaction between a main gateway and a sub-gateway in the prior art, provided by an embodiment of the present invention.

[0040] Figure 2 This is a flowchart illustrating an OMCI client protocol stack fault handling method provided in an embodiment of the present invention;

[0041] Figure 3 This is a schematic diagram illustrating the interaction between a main gateway and a sub-gateway according to an embodiment of the present invention;

[0042] Figure 4 This is a schematic diagram of the format of a temporary message in an OMCI client protocol stack fault handling method provided in an embodiment of the present invention;

[0043] Figure 5 This is a schematic diagram of the format of the first forwarding message and the second forwarding message in an OMCI client protocol stack fault handling method provided in an embodiment of the present invention;

[0044] Figure 6 This is a schematic diagram of the format of the first forwarding message and the second forwarding message in another OMCI client protocol stack fault handling method provided in this embodiment of the invention;

[0045] Figure 7 This is a schematic diagram of the format of the information database synchronization message in an OMCI client protocol stack fault handling method provided in an embodiment of the present invention;

[0046] Figure 8 This is a schematic diagram of the format of the information database synchronization message in another OMCI client protocol stack fault handling method provided in this embodiment of the invention;

[0047] Figure 9 This is a flowchart illustrating another OMCI client protocol stack fault handling method provided in an embodiment of the present invention;

[0048] Figure 10 This is a flowchart illustrating another OMCI client protocol stack fault handling method provided in an embodiment of the present invention;

[0049] Figure 11 This is a schematic diagram illustrating the interaction between a main gateway and a sub-gateway according to an embodiment of the present invention;

[0050] Figure 12 This is a schematic diagram of the architecture of an OMCI client protocol stack fault handling device provided in an embodiment of the present invention. Detailed Implementation

[0051] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0052] To make the technical solution of this invention clearer, this invention also describes the connection architecture of OLT devices, main gateways, and sub-gateways in the prior art, as well as the processing mechanism of downlink OMCI messages in OLT devices in the prior art, such as... Figure 1 The diagram illustrates the connection architecture of an OLT device, a main gateway, and sub-gateways in the prior art. The main gateway includes a message transmission and reception control module, an OMCI client protocol stack, an OMCI server protocol stack, functional modules, and a MIB (Management Information Base) library. The sub-gateways include an OMCI protocol stack and a MIB library. For ease of distinction, in subsequent embodiments, the MIB library in the main gateway will be referred to as the target information library, and the MIB library in the sub-gateways will be referred to as the local information library. The OMCI client protocol stack in the main gateway will be simply referred to as the OMCI client, the OMCI server protocol stack in the main gateway will be simply referred to as the OMCI server, and the OMCI protocol stack in the sub-gateways will be directly referred to as the OMCI protocol stack.

[0053] In an FTTR system, the main gateway connects to the OLT equipment at the central office, providing access bandwidth to households through the operator's network, and registering and managing services for the sub-gateways. The main gateway runs two OMCI protocol stacks: an OMCI client stack and an OMCI server stack. The OMCI client stack handles OMCI interactions with the OLT, while the main gateway's OMCI server stack handles OMCI interactions with the sub-gateway's OMCI stack. Sub-gateways are located in each user's room, connected to the main gateway via fiber optic cable, and providing Wi-Fi, GE, and IPTV ports to various terminal devices for internet access or IPTV services. Each sub-gateway runs only one protocol stack, responsible for OMCI interactions with the main gateway's server stack, completing registration and service activation through OMCI.

[0054] The OMCI client in the main gateway is connected to the functional module and has access to the target information database. The target information database stores all instances of interaction and usage between the OLT device and the main gateway. It includes not only basic device information of the main gateway, such as physical SN, device MAC address, device form information, and status information, but also various service configuration information and statistical information issued by the OLT device. The OMCI client processes the downlink OMCI messages of the OLT device according to the target information database. The downlink OMCI messages are the management messages sent by the OLT device to the main gateway. Similarly, changes in status information and configuration changes between the OLT device and the main gateway are recorded by the main gateway in the target information database. It can be understood that the target information database stores information for processing the downlink OMCI messages of the OLT device.

[0055] Functional modules are used to configure the main gateway or network devices. When a functional module malfunctions, the OMCI client connected to that module is also highly likely to be affected, causing the OMCI client to hang or become blocked. This prevents the OLT from properly processing OMCI messages and performing configuration distribution or configuration readback operations on the main gateway's functional modules. Most of the downlink OMCI messages from the OLT device are management messages used to maintain normal business operations, without involving network device configuration. The processing of these messages usually only requires the target information database and does not require the participation of functional modules. However, when the OMCI client hangs due to a functional module malfunction, it cannot process these messages. The OMCI messages sent by the OLT device need to be responded to in a timely manner. If multiple messages are not responded to, the OLT device will add the main gateway to its blacklist, or deregister it, or even cause service interruption.

[0056] A communication channel is set up between the OMCI server and the OMCI protocol stack of the sub-gateway for interaction between the main gateway and the sub-gateway. The interaction between the two is usually used for the configuration of the sub-gateway. These messages are called interaction messages. The interaction messages transmitted by the OMCI server to the sub-gateway are processed by the OMCI protocol stack according to the local information database.

[0057] In this invention, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0058] Furthermore, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0059] Example 1:

[0060] In existing technologies, when the main gateway OMCI client fails, it cannot promptly reply to OLT messages, leading to the FTTR terminal device becoming unmanaged, experiencing service interruption, or dropping the connection. To address this issue, Embodiment 1 of this invention provides an OMCI client protocol stack fault handling method. The execution subject of this method is a sub-gateway, such as... Figure 2 As shown, it includes:

[0061] In step 201, the first forwarded message is processed using the target information database to obtain a second forwarded message; wherein, the first forwarded message is obtained by the main gateway re-encapsulating the downlink OMCI message of the OLT device and transmitting it to the sub-gateway; the downlink OMCI message is a management message transmitted by the OLT device to the main gateway for processing, and the first forwarded message is transmitted to the sub-gateway by multiplexing the communication channel between the main gateway and the sub-gateway; the target information database is transmitted from the main gateway to the sub-gateway.

[0062] In step 202, the second forwarded message is transmitted to the main gateway so that the main gateway can re-encapsulate the second forwarded message to obtain the first response message, and transmit the first response message to the OLT device. The first response message is the uplink OMCI message used to respond to the downlink OMCI message.

[0063] It should be noted that steps 201 and 202 are executed after a failure occurs in the OMCI client of the main gateway. When the OMCI client of the main gateway does not fail, the main gateway still processes the downlink OMCI messages of the OLT device.

[0064] The re-encapsulation in step 201 and step 202 does not change the core information transmitted by the message, but changes the format of the message or the destination address of the message so that the message can reach the sub-gateway or OLT device and be correctly identified by the sub-gateway or OLT device.

[0065] This embodiment stores the target information database in the sub-gateway after a failure of the OMCI client of the main gateway, and reuses the communication channel between the main gateway and the sub-gateway, as well as the sub-gateway's ability to process messages. This allows the sub-gateway to replace the main gateway in using the target information database to process downlink OMCI messages of the OLT device, thereby maintaining the normal operation of the FTTR terminal device's services.

[0066] In a preferred embodiment, in order to maintain normal interaction between the sub-gateway and the main gateway, such as Figure 3 As shown, the target information database and the local information database are stored separately. The sub-gateway uses the local information database to process interaction messages with the main gateway, and uses the target information database to process the first forwarding message. In this preferred embodiment, since the sub-gateway also receives interaction messages from the main gateway, and the processing methods for the interaction messages and the first forwarding message are different, in order to correctly distinguish whether a message belongs to an interaction message or a first forwarding message, this embodiment provides an optional implementation method, specifically including:

[0067] When a message is received from the main gateway, it is parsed. If the message contains a preset identifier, it is identified as a first forwarding message; otherwise, it is an interactive message. The preset identifier is carried in the first forwarding message by the main gateway when it re-encapsulates the downlink OMCI message to obtain the first forwarding message.

[0068] Correspondingly, in order to facilitate the main gateway in identifying whether a message from a sub-gateway is an interactive message or a second forwarding message, this embodiment also provides an optional implementation method, namely, processing the first forwarding message using the target information database to obtain the second forwarding message specifically includes: processing the first forwarding message using the target information database to obtain a temporary message; carrying a preset identifier in the temporary message to obtain the second forwarding message, so that the main gateway can identify the second forwarding message according to the preset identifier.

[0069] The preset identifier is formed by setting a preset position of the message to a preset value. Both the preset position and the preset value are obtained by those skilled in the art based on the structure and experience of the message. For example, the format of the temporary message is as follows: Figure 4 As shown, it includes a 2-bit TCI (Transaction Correlation Identifier), a 1-byte Message type, a 1-byte Device identifier, a 4-byte Messageidentifier, and 32 bytes of Message contents. In practical applications, it was found that there are still unused free bits in the Message type and Device identifier. Therefore, a portion of the Message type or Device identifier is used as a preset position. For example, the Message type is split, and 1 bit is used as the preset position. Figure 5 The OLT identifier is used as the data structure, with the remaining 7 bits representing the message type. When the OLT identifier value is 1 (the default value is 1), it indicates that the message is either the first or second forwarding message. Alternatively, the Device identifier can be split, with 4 bits used as a default position. Figure 6 The first 4 bits represent the OLT identifier, and the remaining 4 bits represent the OMCI type defined by the OMCI message protocol. When all 4 bits of the OLT identifier are 1, it indicates that the message is either a first forwarding message or a second forwarding message.

[0070] In practical application scenarios, the transmission of the target information database is achieved by the sub-gateway actively sending a corresponding synchronization message to the main gateway, and then synchronizing according to the synchronization message. Specifically, before processing the first forwarding message using the target information database, the method further includes: sending a first information database synchronization message to the main gateway, carrying a preset synchronization identifier in the first information database synchronization message, so that the main gateway can identify the first information database synchronization message according to the preset synchronization identifier, and transmit the target information database to the sub-gateway according to the first information database synchronization message.

[0071] In an optional implementation, sending the first information database synchronization message to the main gateway can be: when the sub-gateway receives the first forwarding message for the first time, it sends the first information database synchronization message to the main gateway.

[0072] The first information database synchronization message can be a MIB upload message, such as... Figure 7 As shown, the Message identifier is split into a 2-byte Entity class and a 2-byte Entity instance. When the value of the Entity instance is 1, it indicates that a preset synchronization identifier is carried, meaning the message is a first-database synchronization message. Alternatively, the preset identifier, i.e., the OLT identifier, can be carried in the Message type, or the Device identifier can be split into two parts, such as... Figure 8 As shown, one part is used to carry the preset identifier, namely the OLT identifier, and the other part is the OMCI type defined by the OMCI message protocol.

[0073] The target information database can be understood as a collection of instances, and the transmission of the target information database to the sub-gateway can be understood as the transmission process of each instance. Specifically, after receiving the first information database synchronization message (i.e., the MIB upload message), the main gateway returns the number of instances contained in the target information database to the sub-gateway in a MIB upload response message. After receiving the MIB upload response message, the sub-gateway sends instance synchronization messages (i.e., MIB upload next messages) to the main gateway in sequence, carrying the sequence number of the corresponding instance in each instance synchronization message. When the main gateway receives the instance synchronization message, it extracts the sequence number from it, encapsulates the instance corresponding to that sequence number in the target information database in a MIBupload next response message, and sends it to the sub-gateway.

[0074] The formats of the MIB upload response message, MIB upload next message, and MIB upload nextresponse message are the same as those of the MIB upload message. The number of instances, instance number, and instance information are all carried in the message contents of the corresponding message. The preset synchronization identifier and preset identifier can also be carried in the message. This process is the same as the process of carrying the preset synchronization identifier and preset identifier in the MIB upload message, and will not be described again here.

[0075] In practical application scenarios, the OMCI client of the main gateway may also fail and recover. In this case, since the information used to process downlink OMCI messages of the OLT device was stored in the sub-gateway (i.e., the target information database) during the failure, to ensure that the OMCI client of the main gateway can process downlink OMCI messages of the OLT device normally after the failure recovery, the information database of the main gateway is also synchronized. That is, after the OMCI client of the main gateway fails and recovers, the method further includes: receiving a second information database synchronization message from the main gateway, parsing the second information database synchronization message; if the parsed second information database synchronization message carries a preset synchronization identifier, then the target information database is transmitted to the main gateway so that the main gateway can use the target information database to process subsequent downlink OMCI messages of the OLT device. In an optional implementation, the format of the second information database synchronization message is consistent with that of the first information database synchronization message.

[0076] Example 2:

[0077] After providing the OMCI client protocol stack fault handling method described in Embodiment 1, this invention will further provide an OMCI client protocol stack fault handling method. The execution subject of the OMCI client protocol stack fault handling method in this embodiment is the main gateway, in order to elaborate on the corresponding method in Embodiment 1 from the perspective of the main gateway, and to further analyze its design principle in depth.

[0078] The OMCI client protocol stack fault handling method described in this embodiment involves transmitting a target information database to the sub-gateway to monitor the fault status of the OMCI client. When a fault is detected in the OMCI client, such as... Figure 9 As shown, it includes:

[0079] In step 301, the downlink OMCI message from the OLT device is re-encapsulated to obtain a first forwarding message, and the first forwarding message is forwarded to the sub-gateway so that the sub-gateway can process the first forwarding message to obtain a second forwarding message.

[0080] In step 302, a second forwarding message is received from the sub-gateway, the second forwarding message is re-encapsulated to obtain a first response message, and the first response message is transmitted to the OLT device.

[0081] The transmission of the target information database to the sub-gateway can be performed after receiving the first information database synchronization message from the sub-gateway. Steps 301-302 are executed only after a failure of the main gateway's OMCI client. When the main gateway's OMCI client is functioning correctly, the downlink OMCI messages of the OLT device are still processed by the main gateway's OMCI client.

[0082] The monitoring of OMCI client fault conditions can be as follows: the message transmission and reception control module monitors whether a second response message is received from the OMCI client within a preset time after transmitting the corresponding downlink OMCI message to the OMCI client. The second response message is the uplink OMCI message used to respond to the downlink OMCI message. If the number of times the second response message is not received from the OMCI client within the first preset time is detected as N consecutive times, then the OMCI client is found to have failed. The preset time and N are obtained by those skilled in the art based on experience.

[0083] The step of forwarding the first forwarding message to the sub-gateway can be to select a sub-gateway that is not currently undergoing an upgrade from among a number of sub-gateways that are stably connected to the main gateway and have been authenticated and authorized by the main gateway, and send the first forwarding message to that sub-gateway.

[0084] This embodiment forwards the target information database and downlink OMCI messages to the sub-gateway, enabling the sub-gateway to process the downlink OMCI messages of the OLT device instead of the main gateway. This maintains the normal operation of the OLT device and prevents the FTTR terminal device from becoming unmanaged or experiencing service outages due to malfunctions in the main gateway's functional modules.

[0085] In an optional implementation, the step of receiving a downlink OMCI message from the OLT device, re-encapsulating the downlink OMCI message to obtain a first forwarding message, and forwarding the first forwarding message to the sub-gateway specifically includes: the message transceiver control module receiving the downlink OMCI message from the OLT device and forwarding the downlink OMCI message to the OMCI server; the OMCI server carrying a preset identifier in the downlink OMCI message to obtain the first forwarding message, and forwarding the first forwarding message to the sub-gateway, so that the sub-gateway can identify the first forwarding message according to the preset identifier. The preset identifier has been described in Embodiment 1 and will not be repeated here.

[0086] The purpose of the OMCI server carrying a preset identifier in the downlink OMCI message is to distinguish it from the interaction messages between the OMCI server and the sub-gateway, so that the sub-gateway can distinguish and identify it. The OMCI server forwards the first forwarding message to the sub-gateway by reusing the communication channel used for transmitting interaction messages with the sub-gateway.

[0087] In practical application scenarios, the process of receiving a second forwarded message from a sub-gateway, re-encapsulating the second forwarded message to obtain a first response message, and transmitting the first response message to the OLT device specifically includes: the OMCI server receiving the second forwarded message from the sub-gateway and parsing the second forwarded message; the parsing of the second forwarded message utilizes the OMCI server's own ability to process interactive messages. If the parsed second forwarded message carries a preset identifier, the preset identifier is removed from the second forwarded message to obtain the first response message, which is then forwarded to the message transmission and reception control module; wherein, the preset identifier in the second forwarded message is used by the OMCI server to distinguish the second forwarded message and the interactive messages between the OMCI server and the sub-gateway, in order to identify the second forwarded message. The message transmission and reception control module identifies all messages from the OMCI server as the first response message. The message transmission and reception control module then transmits the first response message to the OLT device.

[0088] This embodiment also provides an optional implementation for transmitting the client target information database. Specifically, the target information database is a shared database between the OMCI client and the OMCI server, enabling the OMCI server to access and retrieve the target information database. The transmission of the target information database to the sub-gateway is as follows: Figure 10 and Figure 11 As shown, it specifically includes:

[0089] In step 401, the OMCI server receives a first information database synchronization message from the sub-gateway and parses the first information database synchronization message.

[0090] In step 402, if the first information database synchronization message is parsed to contain a preset synchronization identifier, the target information database is transmitted to the sub-gateway.

[0091] In practical use, the transmission of the target information database to the sub-gateway specifically includes: the OMCI server accessing the target information database, calculating the number of instances contained in the first client database, and transmitting the number of instances to the sub-gateway so that the sub-gateway can send an instance synchronization message to the OMCI server based on the number of instances; the OMCI server receiving the instance synchronization message from the sub-gateway, parsing the instance sequence number from the instance synchronization message, and transmitting the instance corresponding to the instance sequence number to the sub-gateway.

[0092] In practical application scenarios, the first information database synchronization message is a MIB upload message, and the instance synchronization message is a MIB upload next message. Both the first information database synchronization message and the instance synchronization message carry the preset synchronization identifier so that the OMCI server can identify the first information database synchronization message and the instance synchronization message.

[0093] In practical use, the OMCI client of the main gateway may also fail and recover. This embodiment provides an optional implementation method after detecting that the OMCI client has failed, namely, the method further includes: monitoring the failure recovery status of the OMCI client; when the failure recovery of the OMCI client is detected, sending a second information database synchronization message to the sub-gateway, so that the sub-gateway can send a target information database to the main gateway according to the second information database synchronization message; the main gateway receives the target information database so that the OMCI client can use the target information database to process subsequent downlink OMCI messages of the OLT device.

[0094] The monitoring of OMCI client fault recovery specifically includes: the message transceiver module forwarding downlink OMCI messages to the OMCI server for processing by the sub-gateway, while simultaneously forwarding downlink OMCI messages to the OMCI client; the message transceiver control module monitoring whether a second response message is received from the OMCI client within a preset time after transmitting the corresponding downlink OMCI message to the OMCI client; if a second response message is received from the OMCI client M times consecutively within the second preset time, then the OMCI client fault recovery is detected, wherein the preset time and M are obtained by those skilled in the art based on experience.

[0095] It should be noted that the specific formats of each message described in Embodiments 1 and 2 are exemplary and explanatory presentations in combination with specific application scenarios, and are not intended to limit this application.

[0096] Example 3:

[0097] Based on the methods described in Embodiments 1 and 2, this invention combines specific application scenarios and uses technical descriptions in relevant scenarios to illustrate the implementation process of the features of this invention in those scenarios.

[0098] The OMCI client protocol stack fault handling method described in this embodiment specifically includes: the message sending and receiving control module of the main gateway ONT performs statistics and forwarding on the OMCI messages received and sent by the OMCI client, monitors in real time whether the client responds to the OLT message in a timely manner (i.e. whether a second response message is generated based on the downlink OMCI message of the OLT device in Embodiment 1), counts the received OLT messages (downlink OMCI messages) and the sent messages (second response messages) in real time, and if more than 3 consecutive failures to respond are detected (i.e., N times in Embodiment 2), it indicates that the OMCI client protocol stack of the main gateway is abnormal or blocked. The OMCI message of the OLT that is received again needs to be copied, one copy is sent to the OMCI client, and the other copy is sent to the OMCI server protocol stack of the main gateway through the message queue.

[0099] The main gateway OMCI server protocol stack receives a message from the OMCI client and modifies the Deviceidentifier field in the OMCI message, using the high 4 bits (unused) to identify that this OMCI message originated from an OLT message. The modified message becomes the first forwarding message. For example... Figure 5 or Figure 6 The image shows an extended OMCI message. The purpose of identifying OLT messages can be achieved by extending either the Deviceidentifier field or the Message type field. This embodiment uses Device identifier extension as an example. The extended value can be uniformly agreed upon by the sub-gateway and the main gateway. In this invention, the high 4 bits of the Device identifier are set to 1 to identify the forwarded OLT OMCI message as an example for functional explanation.

[0100] The main gateway polls all discovered sub-gateways and selects the sub-gateway that has a stable connection to the main gateway, is authenticated and authorized by the main gateway, and has not performed an OMCI upgrade (when the main gateway upgrades a sub-gateway, the sub-gateway needs to process a large number of OMCI messages and is in a busy phase). The main gateway sends the first forwarding message directly to the selected sub-gateway through the packet sending interface of the main gateway's OMCI server protocol stack, and records the sub-gateway's authorization number. As long as the sub-gateway is stably registered and has not been upgraded, subsequent messages are sent directly to that sub-gateway.

[0101] When the sub-gateway OMCI protocol stack receives an OMCI message from the main gateway, if the high 4 bits of the Device identifier are 1, it recognizes this message as the first forwarding message and distributes it to the sub-gateway's OMCI protocol stack for processing. This primarily utilizes the sub-gateway OMCI protocol stack's ability to process OMCI messages.

[0102] If the sub-gateway is processing an OLT message from the master gateway for the first time, the master gateway needs to synchronize the MIB library (i.e., the target information library in Example 1) of the OMCI client protocol stack to the sub-gateway. This synchronization of the MIB library from the master gateway's OMCI client protocol stack to the sub-gateway can be achieved by extending the instance number in the MIB upload message, such as... Figure 7 As shown, the main gateway and sub-gateways agree on an instance number to identify the MIB library of the main gateway's OMCI client protocol stack being synchronized. The main gateway's OMCI client MIB library stores all instances generated and used in the interaction between the OLT device and the main gateway. It includes not only basic device information such as the main gateway's physical serial number, MAC address, device form factor, and status information, but also various service configuration information and statistical information issued by the OLT. Changes in status information and configurations between the OLT device and the main gateway require synchronous updates to the data in the MIB library. The main gateway's OMCI client protocol stack synchronizes the MIB library to the sub-gateways.

[0103] It should be noted that, in this embodiment, synchronizing the MIB library of the main gateway OMCI client to the sub-gateway does not mean using the MIB library of the main gateway OMCI client to synchronize and update the MIB library in the sub-gateway. Instead, the MIB library of the main gateway OMCI client is stored in the sub-gateway as the target information library. The MIB library of the sub-gateway and the target information library occupy different storage spaces and do not affect each other. The MIB library of the sub-gateway is used to process the interaction messages between the sub-gateway and the main gateway, and the target information library is used to process the first forwarding message.

[0104] In the OMCI protocol, the instance number of the MIB upload message type is 0, indicating that the OLT loads the MIB library of the main gateway OMCI client, or the main gateway OMCI protocol side loads the MIB library of the sub-gateway. In this invention, the instance number of the extended MIB upload message is set to 1 as an example to indicate that the sub-gateway loads the MIB library of the main gateway OMCI client protocol stack. The synchronization process follows the MIB upload interaction process in the G.988 standard, specifically including:

[0105] The sub-gateway initiates a MIB upload (i.e., first information database synchronization message) to the main gateway. The main gateway calculates the number of instances contained in the OMCI client's MIB database and replies to the sub-gateway. The sub-gateway then loads all MIB instance data of the main gateway's OMCI client using the MIB upload next message, completing the synchronization of the MIB database of the main gateway's OMCI client protocol stack. For example, to synchronize instance ONU-G (me, number 256), the sequence number of the instance in the main gateway is 1. The sub-gateway uses the MIB upload next message (i.e., instance synchronization message) with sequence number 1. The main gateway receives the MIB upload next message, parses out the sequence number 1, retrieves instance ONU-G (me, number 256) with sequence number 1 from the MIB database, obtains the various attribute values ​​of this instance, and replies to the sub-gateway, completing the synchronization of instance ONU-G (me, number 256).

[0106] The OMCI protocol stack in the sub-gateway parses the first forwarding message of various identified message types, and performs operations such as reading back, setting, creating and deleting MIB database data through the target information database. Finally, it assembles the second forwarding message and sends it to the OMCI server protocol stack of the main gateway.

[0107] The main gateway OMCI service protocol stack receives the OMCI message sent back by the sub-gateway, verifies the Deviceidentifier in the OMCI message, and if the high 4 bits are 1, it is determined that it is the second forwarded message processed by the sub-gateway. The high 4 bits of the Device identifier are restored (reset to 0) to obtain the first response message. The first response message is sent to the message transmission and reception control module through the message queue for processing. The message transmission and reception control module sends the first response message to the OLT to complete the OLT message reply.

[0108] To address scenarios involving OMCI client failure recovery, the method described in this embodiment further includes:

[0109] After the OMCI client protocol station malfunctions or becomes congested, the message transmission and reception control module of the main gateway ONT continues to monitor the OLT message return status of the OMCI client protocol stack. If the message transmission and reception control module of the main gateway ONT receives OLT message responses from the OMCI client protocol stack three times consecutively (i.e., M times in Example 2), it is considered that the OMCI client protocol stack of the main gateway has recovered and can process the OMCI messages of the OLT normally. The message transmission and reception control module of the main gateway ONT no longer copies and forwards the received OLT messages to the OMCI server protocol stack of the main gateway for processing, but directly sends them to the OMCI client protocol stack of the main gateway for processing.

[0110] When the OMCI client recovers from a failure, the OMCI server protocol stack synchronizes the target information database stored on the sub-gateway to the main gateway through the MIB upload message (extended instance number 1) (i.e., the second information database synchronization message). This step is mainly to ensure that the MIB database data of the main gateway OMCI client protocol stack is kept synchronized with the data of the OLT even if the configuration issued by the OLT to the ONU changes during the failure of the main gateway OMCI server protocol stack.

[0111] Based on the synchronized MIB database data, the configuration is redistributed to each functional module, completing the configuration synchronization between the main gateway and the OLT. After the MIB database and configuration synchronization are completed, subsequent received OMCI messages do not need to be processed again.

[0112] After the OMCI server protocol stack of the main gateway parses the OMCI message, it completes the data interaction with the corresponding functional modules based on the parsed data, assembles the OMCI response, sends it to the message transmission and reception control module of the main gateway, and finally sends it to the OLT to complete the message reply from the OLT.

[0113] Example 4:

[0114] like Figure 12 The diagram shown is an architectural schematic of an OMCI client protocol stack fault handling device according to an embodiment of the present invention. This OMCI client protocol stack fault handling device includes one or more processors 21 and a memory 22. Figure 12 Take a processor 21 as an example.

[0115] Processor 21 and memory 22 can be connected via a bus or other means. Figure 12 Taking the example of a connection between China and Israel via a bus.

[0116] The memory 22, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs and non-volatile computer-executable programs, such as the OMCI client protocol stack fault handling method in Embodiment 1 or Embodiment 2. The processor 21 executes the OMCI client protocol stack fault handling method by running the non-volatile software programs and instructions stored in the memory 22.

[0117] Memory 22 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 22 may optionally include memory remotely located relative to processor 21, which can be connected to processor 21 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0118] The program instructions / modules are stored in the memory 22. When executed by one or more processors 21, they perform the OMCI client protocol stack fault handling method in Embodiment 1 or Embodiment 2. When the OMCI client protocol stack fault handling method in Embodiment 1 is executed, the device is a sub-gateway; when the OMCI client protocol stack fault handling method in Embodiment 2 is executed, the device is a master gateway.

[0119] It is worth noting that the information interaction and execution process between the modules and units in the above-mentioned device and system are based on the same concept as the processing method embodiment of the present invention. For details, please refer to the description in the method embodiment of the present invention, and will not be repeated here.

[0120] Those skilled in the art will understand that all or part of the steps in the various methods of the embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, etc.

[0121] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for handling faults in an OMCI client protocol stack, characterized in that, include: The first forwarded message is processed using the target information database to obtain the second forwarded message; wherein, the first forwarded message is obtained by the main gateway re-encapsulating the downlink OMCI message of the OLT device after detecting a failure of the OMCI client, and then transmitting it to the sub-gateway; the target information database is transmitted from the main gateway to the sub-gateway; The second forwarded message is transmitted to the main gateway so that the main gateway can re-encapsulate the second forwarded message to obtain the first response message, and transmit the first response message to the OLT device; The OMCI client is located at the main gateway; the target information database is the management information database in the main gateway.

2. The OMCI client protocol stack fault handling method according to claim 1, characterized in that, Before processing the first forwarded message using the target information database, the method further includes: A first information database synchronization message is sent to the main gateway. The first information database synchronization message carries a preset synchronization identifier so that the main gateway can identify the first information database synchronization message according to the preset synchronization identifier and transmit the target information database to the sub-gateway according to the first information database synchronization message.

3. The OMCI client protocol stack fault handling method according to claim 1 or claim 2, characterized in that, After the OMCI client of the main gateway recovers from a failure, the method further includes: Receive the second information database synchronization message from the main gateway and parse the second information database synchronization message; If the second information database synchronization message is parsed to contain a preset synchronization identifier, the target information database is transmitted to the main gateway so that the main gateway can use the target information database to process subsequent downlink OMCI messages of the OLT device.

4. A method for handling faults in an OMCI client protocol stack, characterized in that, Transmit the target information database to the sub-gateway and monitor the fault status of the OMCI client. When a fault is detected in the OMCI client, the following should be included: The downlink OMCI message from the OLT device is re-encapsulated to obtain the first forwarding message. The first forwarding message is then forwarded to the sub-gateway so that the sub-gateway can use the target information database to process the first forwarding message and obtain the second forwarding message. Receive the second forwarding message from the sub-gateway, re-encapsulate the second forwarding message to obtain the first response message, and transmit the first response message to the OLT device; The OMCI client is located at the main gateway; the target information database is the management information database in the main gateway.

5. The OMCI client protocol stack fault handling method according to claim 4, characterized in that, The target information database is a shared database between the OMCI client and the OMCI server. The transmission of the target information database to the sub-gateway specifically includes: The OMCI server receives a first information database synchronization message from the sub-gateway and parses the first information database synchronization message; If the parsed first information database synchronization message contains a preset synchronization identifier, then the target information database is transmitted to the sub-gateway. The OMCI server is located at the main gateway.

6. The OMCI client protocol stack fault handling method according to claim 5, characterized in that, The step of transmitting the target information database to the sub-gateway specifically includes: The OMCI server accesses the target information database, calculates the number of instances contained in the first client database, and transmits the number of instances to the sub-gateway so that the sub-gateway can send an instance synchronization message to the OMCI server based on the number of instances. The OMCI server receives instance synchronization messages from the sub-gateway, parses the instance sequence number from the instance synchronization message, and transmits the instance corresponding to the instance sequence number to the sub-gateway.

7. The OMCI client protocol stack fault handling method according to claim 4, characterized in that, The process of receiving downlink OMCI messages from the OLT device, re-encapsulating the downlink OMCI messages to obtain a first forwarding message, and forwarding the first forwarding message to the sub-gateway specifically includes: The message transmission and reception control module receives downlink OMCI messages from the OLT device and forwards the downlink OMCI messages to the OMCI server; The OMCI server carries a preset identifier in the downlink OMCI message to obtain a first forwarding message, and forwards the first forwarding message to the sub-gateway so that the sub-gateway can identify the first forwarding message according to the preset identifier.

8. The OMCI client protocol stack fault handling method according to claim 4, characterized in that, The process of receiving a second forwarded message from a sub-gateway, re-encapsulating the second forwarded message to obtain a first response message, and transmitting the first response message to the OLT device specifically includes: The OMCI server receives the second forwarded message from the sub-gateway and parses the second forwarded message; If the second forwarding message is parsed to carry a preset identifier, then the preset identifier is removed from the second forwarding message to obtain the first response message, and the first response message is forwarded to the message sending and receiving control module. The message transmission and reception control module transmits the first response message to the OLT device.

9. The OMCI client protocol stack fault handling method according to any one of claims 4-8, characterized in that, After detecting a failure in the OMCI client, the method further includes: Monitor the fault recovery status of the OMCI client; When the OMCI client fault recovery is detected, a second information database synchronization message is sent to the sub-gateway so that the sub-gateway can send the target information database to the main gateway according to the second information database synchronization message; The main gateway receives the target information database so that the OMCI client can use the target information database to process subsequent downlink OMCI messages from the OLT device.

10. An OMCI client protocol stack fault handling device, characterized in that, The device includes: At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the processor for performing the OMCI client protocol stack fault handling method according to any one of claims 1-3 or the OMCI client protocol stack fault handling method according to any one of claims 4-9.

Images