A method and device for ToD management

Abstract

The present application provides a method and apparatus for ToD management. The method in the OLT includes: obtaining ToD management parameters configured based on the management objects extended in the MIB; generating an OMCI message based on the extended OLT‑G management entity, and sending the OMCI message to the ONU, wherein the OMCI message carries the ToD management parameters. The method in the ONU includes: receiving an OMCI message generated by the extended OLT‑G management entity sent by the OLT, wherein the OMCI message carries the ToD management parameters configured based on the management objects extended in the MIB; performing corresponding ToD management operations according to the ToD management parameters. The present application can achieve flexible and diverse ToD management by extending new management objects in the OLT MIB and extending the OLT‑G ME in the ISAM OMCI specification.

Description

Technical Field

[0001] The present application relates to the technical field of passive optical networks, and in particular to a technical solution for ToD (Time of Day) management. Background Art

[0002] To support mobile services in F5G business scenarios, OLTs (Optical Line Terminals) and ONUs (Optical Network Units) must support time synchronization in the end-to-end network (from the time server to the small base station or endpoint of the mobile service). In the 5G mobile backhaul PON (Passive Optical Networks) deployment scenario, the small base station is connected to the ONU. To support time-sensitive services, ToD information needs to be sent from the ONU to the small base station. The ONU's ToD information is synchronized with the OLT. To keep the ONU and OLT highly synchronized, the OLT will periodically send ToD information to the ONU. When the ONU detects that it has not received ToD information within a specified time period, the ONU will report an out of synchronization alarm to prompt the administrator that the ONU is no longer synchronized with the OLT. The existing technology solutions have the following disadvantages: 1) The existing technology lacks a management solution for ToD; 2) The distribution interval of ToD information on the OLT side is hard-coded and cannot be configured; 3) The ONU software does not know the exact time interval for ToD information distribution on the OLT side, which depends entirely on the agreement reached between the ONU and OLT teams during the design phase; 4) The synchronization loss detection behavior of different ONU vendors is usually different, which will lead to key issues in IOP (interoperability testing) between OLT vendors and ONU vendors. Summary of the Invention

[0003] The purpose of this application is to provide a technical solution for Time-of-Driving (ToD) management. To support and standardize ToD management, this application defines a new management model for OLTs and ONUs. Specifically, new management objects are added to the OLT MIB (Management Information Base) and the OLT-G ME (Management Entity) is expanded in the OMCI (ONU Management and Control Interface) specification. Furthermore, based on these expansions, this application proposes a new synchronization loss alarm mechanism.

[0004] According to one aspect of the present application, a method for ToD management in an OLT is provided, wherein the method includes: obtaining ToD management parameters configured based on an extended management object in an MIB; generating an OMCI message based on an extended OLT-G management entity, and sending the OMCI message to the ONU, wherein the OMCI message carries the ToD management parameters.

[0005] In some embodiments, the ToD management parameters include a ToD distribution time interval and a number of OLT-G message losses, and the method further includes:

[0006] An OLT-G message carrying ToD information is sent to the ONU according to the ToD distribution time interval.

[0007] According to another aspect of the present application, a method for ToD management in an ONU is provided, wherein the method includes:

[0008] Receive the OMCI message generated by the extended OLT-G management entity sent by the OLT, wherein the OMCI message carries the ToD management parameters configured by the management object extended in the MIB;

[0009] Execute corresponding ToD management operations according to the ToD management parameters.

[0010] In some embodiments, performing a corresponding ToD management operation according to the ToD management parameter includes:

[0011] Determining a time interval for triggering an ONU synchronization loss alarm according to the ToD management parameter, and starting an alarm timer, wherein an expiration time of the alarm timer is set to the time interval;

[0012] If an OLT-G message carrying ToD information is received from the OLT before the alarm timer expires, the alarm timer is reset to zero and restarted;

[0013] If the alarm timer times out and the OLT-G message carrying the ToD information sent by the OLT is still not received, a synchronization loss alarm is reported.

[0014] According to another aspect of the present application, a first device for ToD management in an OLT is provided, wherein the first device includes:

[0015] Means for obtaining ToD management parameters configured based on extended management objects in the MIB;

[0016] A device for generating an OMCI message based on an extended OLT-G management entity and sending the OMCI message to the ONU, wherein the OMCI message carries the ToD management parameter.

[0017] According to another aspect of the present application, a second device for ToD management in an ONU is provided, wherein the second device includes:

[0018] Device for receiving an OMCI message generated by an extended OLT-G management entity sent by an OLT, wherein the OMCI message carries a ToD management parameter configured based on an extended management object in an MIB;

[0019] According to another aspect of the present application, an OLT is provided, wherein the OLT includes:

[0020] a memory for storing one or more programs;

[0021] One or more processors connected to the memory,

[0022] When the one or more programs are executed by the one or more processors, the one or more processors are caused to perform the following operations:

[0023] Obtain ToD management parameters configured based on the extended management objects in the MIB;

[0024] An OMCI message is generated based on the extended OLT-G management entity, and the OMCI message is sent to the ONU, wherein the OMCI message carries the ToD management parameter.

[0025] According to another aspect of the present application, an ONU is provided, wherein the ONU includes:

[0026] a memory for storing one or more programs;

[0027] One or more processors connected to the memory,

[0028] When the one or more programs are executed by the one or more processors, the one or more processors are caused to perform the following operations:

[0029] Receive the OMCI message generated by the extended OLT-G management entity sent by the OLT, wherein the OMCI message carries the ToD management parameters configured by the management object extended in the MIB;

[0030] Execute corresponding ToD management operations according to the ToD management parameters.

[0031] According to another aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored. The computer program can be executed by a processor to perform the following operations:

[0032] Obtain ToD management parameters configured based on the extended management objects in the MIB;

[0033] An OMCI message is generated based on the extended OLT-G management entity, and the OMCI message is sent to the ONU, wherein the OMCI message carries the ToD management parameter.

[0034] According to another aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored. The computer program can be executed by a processor to perform the following operations:

[0035] Receive the OMCI message generated by the extended OLT-G management entity sent by the OLT, wherein the OMCI message carries the ToD management parameters configured by the management object extended in the MIB;

[0036] Execute corresponding ToD management operations according to the ToD management parameters.

[0037] Compared with the existing technology, the present application has the following advantages: by extending new management objects in the OLT MIB and extending the OLT-G ME in the ISAM OMCI specification, flexible and diverse ToD management can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Other features, objects and advantages of the present application will become more apparent upon reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0039] Figure 1 A schematic flow chart of a method for ToD management in an OLT according to an embodiment of the present application is shown;

[0040] Figure 2 A schematic diagram showing a new management object extended in the MIB according to an example of the present application is shown;

[0041] Figure 3 A flow chart of a method for ToD management in an ONU according to an embodiment of the present application is shown;

[0042] Figure 4 This document shows the general solution for ToD management and alarm reporting of this application.

[0043] Figure 5A schematic diagram of a process for ToD management and alarm reporting according to an example of the present application is shown;

[0044] Figure 6 A schematic structural diagram of a first device for ToD management in an OLT according to an embodiment of the present application is shown;

[0045] Figure 7 A schematic structural diagram of a second device for ToD management in an ONU according to an embodiment of the present application is shown;

[0046] Figure 8 An exemplary system is shown that can be used to implement the various embodiments described herein.

[0047] The same or similar reference numerals in the drawings represent the same or similar components. DETAILED DESCRIPTION

[0048] Before discussing exemplary implementations in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow charts describe the various operations as sequential processes, many of the operations can be performed in parallel, concurrently, or simultaneously. In addition, the order of the various operations can be rearranged. The process can be terminated when its operations are completed, but can also have additional steps not included in the accompanying drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0049] In this context, "device" refers to an intelligent electronic device that can perform predetermined processing processes such as numerical calculations and / or logical calculations by running predetermined programs or instructions. It may include a processor and a memory, and the processor executes program instructions pre-stored in the memory to perform the predetermined processing process, or the predetermined processing process is performed by hardware such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), or a combination of the above two.

[0050] The methods discussed below (some of which are illustrated by flow charts) can be implemented by hardware, software, firmware, middleware, microcode, hardware description language, or any combination thereof. When implemented by software, firmware, middleware, or microcode, the program code or code segments for performing the necessary tasks can be stored in a machine or computer readable medium (such as a storage medium). (One or more) processors can perform the necessary tasks.

[0051] The specific structural and functional details disclosed herein are merely representative and are for the purpose of describing exemplary embodiments of the present application. However, the present application may be implemented in many alternative forms and should not be construed as being limited to the embodiments set forth herein.

[0052] It should be understood that although the terms "first," "second," and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used solely to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments. The term "and / or" as used herein includes any and all combinations of one or more of the listed associated items.

[0053] The terms used herein are intended only to describe specific embodiments and are not intended to limit exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms "a", "an", "an item" used herein are also intended to include the plural. It should also be understood that the terms "comprise" and / or "include" used herein specify the presence of stated features, integers, steps, operations, units and / or components, and do not preclude the presence or addition of one or more other features, integers, steps, operations, units, components and / or combinations thereof.

[0054] It should also be noted that, in some alternative implementations, the functions / actions mentioned may occur in a different order than that indicated in the accompanying drawings. For example, two figures shown in succession may actually be performed substantially simultaneously or may sometimes be performed in the reverse order, depending on the functions / actions involved.

[0055] The present application is described in further detail below with reference to the accompanying drawings.

[0056] For mobile front / middle / back haul, PON solutions are the primary candidate due to their low cost and high bandwidth. In 5G MxH (Mobile Front / Middle / Back Haul) over PON networks, small cell uplinks connect to ONUs, and ToD information is distributed by the ONUs, fully synchronized with the OLT. Sections 10.4.6 of ITU-T G.984.3 and 13.2 of G.987.3 describe only the time allocation mechanisms at the transport layer for GPON and XG-PON. ToD information is carried in OLT-G messages, which are distributed by the OLT to the ONUs immediately after system startup.

[0057] The present application found that when ToD information is introduced, when the system is operating normally, OLT-G messages need to be distributed at specific time intervals. However, this is not clearly described in ITU-T G.984.4 and ITU-T G.988.4. This means that OLT and ONU vendors will implement it without a standard management interface. This will cause different vendors to implement it with different behaviors, and even for the same vendor, the implementation is not exactly the same, which will cause great trouble for the IOP between OLT and ONU. The present application also found that when supporting end-to-end noise transmission on the xPON (GPON / XG(S)PON / XGSPON) system, there will be strict time accuracy requirements on the ONU side. Due to cost constraints, it is impossible to use a high-precision crystal oscillator as the OLT. Therefore, OLT-G messages need to be distributed from the OLT to the ONU frequently to ensure that the ONU can closely track the OLT. Currently, due to the lack of definition of relevant OMCI, the ToD synchronization distribution method on the OLT and ONU sides is hard-coded, so it is not configurable, making it difficult to monitor and manage the ToD of various ONUs from different vendors. oD synchronization, at the same time, since it is impossible to configure the ToD information distribution speed, the TOD information distribution speed cannot be optimized according to customer needs; when the ONU does not receive the OLT-G message in a specific time slot, the ONU will think that time synchronization is lost and report a synchronization loss alarm (in the prior art, the ONU reports the synchronization loss alarm based on a private algorithm and there is no standard to follow), but the difficulty lies in that the ONU does not know the exact OLT-G message distribution time interval, and the OLT does not know the ONU alarm reporting mechanism. It depends entirely on the agreement reached by the ONU and OLT teams in the design phase, which will make the implementation complicated and difficult to maintain consistency. In the prior art, the usual method is to set the ONU's synchronization loss detection time to be long enough and to suit all OLTs from different manufacturers as much as possible. This will result in the alarm not being reported in time, and due to inconsistent implementation on the ONU side, when the OLT-G message is lost, the alarm reporting time of the same OLT will also be different. In addition, this application also found that the prior art lacks support for ToD management.

[0058] Figure 1 A flow chart of a method for ToD management in an OLT according to one embodiment of the present application is shown, the method comprising steps S11 and S12. In step S11, the OLT obtains ToD management parameters configured based on an extended management object in the MIB; in step S12, the OLT generates an OMCI message based on the extended OLT-G management entity and sends the OMCI message to the ONU, wherein the OMCI message carries the ToD management parameters.

[0059] In step S11, the OLT obtains ToD management parameters configured based on the extended management objects in the MIB. In some embodiments, to achieve universality, configuration data is required from the OLT. This configuration is defined at the system level and applies to all ONUs under the OLT node. This allows all ONUs under an OLT node to use the same configuration to implement ToD management. In some embodiments, the OLT receives configuration from an NMS (Network Management System) or an administrator. In some embodiments, the operation interface used to perform configuration operations can support SNMP (Simple Network Management Protocol), CLI (Command Line Interface), NCY, etc.

[0060] In some embodiments, the ToD management parameters include any parameters used for ToD management. In some embodiments, the ToD management parameters include at least any one of the following: ToD distribution time interval; number of OLT-G message losses; maximum timeout threshold for OLT-G loss; ToD support report indication; ToD enabling information. Among them, the ToD distribution time interval is used to configure the time interval for distributing ToD information to the ONU. For example, if the ToD distribution time interval is configured as 60s, the OLT distributes ToD information to the ONU every 60s; the number of OLT-G message losses is used to configure the maximum number of ToD losses that triggers a synchronization loss alarm; the maximum timeout threshold for OLT-G loss is used to configure the maximum timeout threshold that triggers a synchronization loss alarm; the ToD support report indication is used to indicate whether the ONU reports whether it supports the ToD function; the ToD enabling information is used to indicate whether the ToD function is enabled. It should be noted that the above-mentioned ToD management parameters are only examples, and any parameters used for ToD management should be included in the scope of the ToD management parameters described in this application.

[0061] In some embodiments, the ToD management parameters include the ToD distribution time interval and the number of OLT-G message losses. The following only introduces the definition of SNMP MIB by taking the SNMP management method as an example. Other management methods have similar ideas and will not be introduced in detail here. Figure 2 A schematic diagram of a new management object extended in the MIB of an example of the present application is shown. Two new objects are defined in the NTR MIB for managing ToD distribution in OLT-G messages, namely Figure 2As shown in the ToD Distrbution TimeInterval (67) and ToD LossOfOltgMessageNumber (68). ToD Distrbution TimeInterval corresponds to the time interval for distributing the ToD message of the OLT-G message. In order to closely track the OLT, the ToD information needs to be distributed from the OLT to the ONU regularly. Regardless of the interval, the OLT message will always be distributed during the startup phase. It is applicable to a normal operating system. The OLT-G message will be sent regularly according to the ToD distribution time interval. As an example, the value range of this object is (0,3600), the default value is 60, and the unit is seconds. ToD LossOfOltgMessageNumber corresponds to the number of OLT-G message losses, which is equivalent to the number of ToD information losses, or the threshold for synchronization loss alarm reporting. Once the number of OLT-G messages that the ONU side has not received continuously reaches the value assigned to this object, the ONU will be considered to have lost synchronization with the OLT. As an example, the value range of this object is 1 to 16, and the default value is 3.

[0062] It should be noted that for other ToD management parameters, corresponding management objects can be similarly extended in the MIB, such as extending three management objects corresponding to the OLT-G loss maximum timeout threshold, ToD support report indication, and ToD enabling information in the MIB.

[0063] In step S12, the ONU generates an OMCI message based on the extended OLT-G management entity, and sends the OMCI message to the ONU, wherein the OMCI message carries the ToD management parameter.

[0064] In some embodiments, the ToD management parameters include a ToD distribution time interval and a number of OLT-G message losses. When the ONU comes online during the startup phase, the OLT generates an OMCI message based on an extended OLT-G management entity and sends the OMCI message to the ONU, wherein the OMCI message carries the ToD distribution time interval and the number of OLT-G message losses.

[0065] To deliver configurations for the newly extended management objects to the ONU, the OMCI needs to be updated to support the new configurations. The definition of time information is nearly identical in ITU-T G.984.4 and G.988.4, so only G.988.4 is described in detail here. The OLT-G message carries Time of Day (ToD) information for distribution to the ONU. Based on the OLT-G message structure defined in Section 9.12.2 of G.988.4, new attributes are introduced for each ToD management parameter. It should be noted that, aside from its name, the OLT-G ME is identical to the OLT B-PON ME documented in ITU-T G.983.2. This optional ME identifies the OLT to which the ONU is connected. It provides a way for the ONU to configure itself for operability with a specific OLT. ONUs supporting this ME automatically create an instance of it. After the startup phase, the OLT should immediately configure the ONU to the desired configuration. The interpretation of the attributes is a matter of negotiation between the two vendors involved. Furthermore, an instance of this ME is associated with the ONU management entity.

[0066] As an example, the ToD management parameters include the ToD distribution time interval and the number of lost OLT-G messages. The extended OLT-G attributes include: Managed entity id, OLT vendor id, Equipment id, Version, ToD Distribution Time Interval, Number of lost OLT messages, Actions, and Notifications. Among them, the managed entity id uniquely identifies each instance of this managed entity. There is only one instance here, numbered 0, (R) (mandatory) (2 bytes); the OLT vendor id identifies the OLT vendor. It is the same as the 4 most significant bytes of the ONT serial number specified in [ITU-T G.984.3]. After instantiation, this attribute contains all spaces, (R, W) (mandatory) (4 bytes); the equipment id can be used to identify the specific type of OLT. The default value of all spaces indicates that the equipment ID information is not available or not applicable to the represented OLT, (R, W) (mandatory) (20 bytes); the version identifies the vendor-defined OLT version. The default left-aligned ASCII string "0" (padded with trailing nulls) indicates that the version information is not available or not applicable to the represented OLT, (R, W) (mandatory) (14 bytes). Among them, ToD Distribution Time Interval and Number of loss of OLT message are two newly extended attributes; ToD Distribution Time Interval identifies the ToD distribution time interval, with a default value of 60 seconds and a maximum value of 3600 seconds, (R, W) (mandatory) (2 bytes); Number of loss of OLT message identifies the number of OLT-G message losses on the ONU side. If the ONU cannot receive the configured number of OLT-G messages from the OLT, the ONU will issue a synchronization loss alarm, with a default value of 3 and a maximum value of 16, (R, W) (mandatory) (2 bytes). For other ToD management parameters, the OLT-G ME can be similarly extended to introduce new attributes, which will not be detailed here.

[0067] In some embodiments, the ToD management parameter includes a ToD distribution interval, and the method further includes step S13. In step S13, the OLT sends an OLT-G message carrying ToD information to the ONU according to the ToD distribution interval. For example, if the administrator configures the ToD distribution interval to 60 seconds, the OLT will distribute an OLT-G message carrying ToD information to the ONU every 60 seconds according to this configuration.

[0068] In some embodiments, step S13 further includes: starting an OLT-G distribution timer, setting the expiration time of the OLT-G distribution timer to the ToD distribution interval; and whenever the OLT-G distribution timer times out, sending an OLT-G message carrying ToD information to the ONU and resetting the OLT-G distribution timer to zero and restarting the timer. Thus, the OLT can periodically distribute ToD information to the ONU based on the configured ToD distribution interval, thereby supporting manageable ToD information distribution.

[0069] It should be noted that there is no strict order in which steps S12 and S13 are executed. For example, the OLT may execute step S12 after obtaining configuration data and simultaneously execute step S13 to begin distributing ToD information to the ONU. For another example, the OLT may execute step S12 after obtaining configuration data and then, based on predetermined logic, begin executing step S13 at a certain point in time to distribute ToD information to the ONU.

[0070] In some embodiments, after step S11, the method further comprises step S14. In step S14, the OLT saves the ToD management parameters into a database.

[0071] Figure 3 A schematic flow diagram of a method for ToD management in an ONU according to an embodiment of the present application is shown. The method includes steps S21 and S22. In step S21, the ONU receives an OMCI message generated by an extended OLT-G management entity and sent by the OLT, wherein the OMCI message carries ToD management parameters configured based on extended management objects in the MIB. In step S22, the ONU performs corresponding ToD management operations based on the ToD management parameters.

[0072] In step S21, the ONU receives the OMCI message generated by the extended OLT-G management entity sent by the OLT, wherein the OMCI message carries the ToD management parameters configured by the management object extended in the MIB. The ToD management parameters and the extended OLT-G management entity have been described in detail in the aforementioned embodiment and will not be repeated here.

[0073] In step S22, the ONU performs corresponding ToD management operations according to the ToD management parameters.

[0074] In some embodiments, the ONU synchronizes with the OLT via an OLT-G message and starts an alarm timer to detect a synchronization loss alarm. Step S22 further includes steps S221 , S222 and S223 .

[0075] In step S221, the ONU determines a time interval for triggering an ONU synchronization loss alarm according to the ToD management parameter, and starts an alarm timer, wherein an expiration time of the alarm timer is set to the time interval.

[0076] In some embodiments, the ToD management parameter includes an OLT-G loss maximum timeout threshold, and determining the time interval for triggering the ONU synchronization loss alarm based on the ToD management parameter includes determining the OLT-G loss maximum timeout threshold as the time interval for triggering the ONU synchronization loss alarm. For example, an administrator configures the OLT-G loss maximum timeout threshold to 1200 seconds. The OLT sends this parameter to the ONU, and the ONU starts an alarm timer based on the parameter, with the expiration time of the alarm timer set to 1200 seconds.

[0077] In some embodiments, the ToD management parameters include a ToD distribution time interval and a number of lost OLT-G messages, and determining the time interval for triggering the ONU synchronization loss alarm based on the ToD management parameters includes: calculating the time interval for triggering the ONU synchronization loss alarm based on the ToD distribution time interval and the number of lost OLT-G messages. Preferably, the time interval for triggering the ONU synchronization loss alarm is the product of the ToD distribution time interval and the number of lost OLT-G messages. In some embodiments, the ONU extracts the configured ToD distribution time interval and the number of lost OLT-G messages from the received OMCI message, and then calculates the time interval for triggering the ONU synchronization loss alarm based on the ToD distribution time interval and the number of lost OLT-G messages, and then starts an alarm timer, the expiration time of which is set to the determined time interval. As an example, if the ToD distribution time interval is 60s and the number of lost OLT-G messages is 3, the expiration time of the alarm timer is 60*3=180s. It should be noted that, since the expiration time of the alarm timer is the product of the ToD distribution time interval and the number of OLT-G message losses, if the alarm timer times out and the OLT-G message is still not received, it means that the number of consecutively lost ToD information has reached the configured number of OLT-G message losses, and the alarm reporting procedure can be started at this time. For example, in the above example, if the alarm timer times out, it means that the OLT-G message from the OLT has not been received for 180 seconds, that is, the number of consecutively lost OLT-G messages (or ToD information) has reached 3, and the alarm reporting procedure can be started.

[0078] In some embodiments, the ToD management parameters include not only the ToD distribution time interval and the number of OLT-G message losses, but also the OLT-G loss maximum timeout threshold. The initial time interval can be calculated based on the ToD distribution time interval and the number of OLT-G message losses. Then, based on the initial time interval and the OLT-G loss maximum timeout threshold, the time interval for triggering the ONU synchronization loss alarm is finally determined. For example, the initial time interval is compared with the OLT-G loss maximum timeout threshold. If the initial time interval is greater than or equal to the OLT-G loss maximum timeout threshold, the OLT-G loss maximum timeout threshold is determined as the final time interval; otherwise, the initial time interval is determined as the final time interval.

[0079] In step S222, if the ONU receives an OLT-G message carrying ToD information from the OLT before the alarm timer times out, the ONU resets the alarm timer and restarts the timer. In some embodiments, the ONU resets the alarm timer as long as it receives an OLT-G message from the OLT before the alarm timer times out. In this case, the ONU may not have lost ToD information, or it may have lost ToD information, but the number of consecutive ToD messages lost is less than the configured number of OLT-G message losses, which means that the alarm reporting condition is not met.

[0080] In step S223, if the ONU has not received the OLT-G message carrying the ToD information from the OLT after the alarm timer times out, it reports a synchronization loss alarm. If the OLT has not received the OLT-G message carrying the ToD information from the OLT after the alarm timer times out, it indicates that the number of consecutively lost ToD messages has reached the configured number of OLT-G message losses, i.e., the alarm reporting conditions are met, and a synchronization loss alarm needs to be reported. In some embodiments, the ONU reports the synchronization loss alarm to the OLT, which then reports the synchronization loss alarm to the NMS. In some embodiments, the ONU reports the synchronization loss alarm to the ACS (Auto-Configuration Server). In some embodiments, the ONU reports the synchronization loss alarm to both the OLT and the ACS, which then reports the synchronization loss alarm to the NMS. In some embodiments, the OLT may be unable to successfully transmit the OLT-G message to the ONU due to unexpected reasons such as fiber disconnection or communication loss.

[0081] In some embodiments, the method further includes: if the ONU receives an OLT-G message carrying ToD information from the OLT again after reporting the synchronization loss alarm, the ONU resets the alarm timer and restarts the timer, and clears the synchronization loss alarm. In some embodiments, if the OLT is unable to successfully transmit the OLT-G message to the ONU due to communication loss or fiber disconnection, when communication between the OLT and the ONU is restored or the fiber is reconnected, the ONU receives an OLT-G message from the OLT again, then the ONU resets the alarm timer and restarts the timer, and clears the synchronization loss alarm.

[0082] In certain embodiments, described ToD management parameter comprises ToD supportability report indication, described step S22 comprises: obtain the ToD supportability information corresponding to described ONU, generate OMCI message according to described ToD supportability information, and send the generated OMCI message to described OLT.In certain embodiments, can send described ToD supportability report indication by defining relevant OMCI, as OMCI response message is expanded, add ToD supportability attribute, to carry ToD supportability information.In certain embodiments, can carry ToD supportability information by the reserved field defined in existing OMCI.

[0083] In some embodiments, in order to support manageable ToD distribution and standardize the ToD information loss alarm reporting mechanism, the present application defines a new management model for OLT and ONU, and proposes a general solution for ToD management and alarm reporting. The management model consists of the following three parts: 1) Two new management objects for managing ToD distribution in OLT-G messages are extended in the OLT NTR MIB. Specifically, a new MIB object is defined at the system level for the ToD distribution time interval (which may also be referred to as the "OLT-G distribution time interval" in the context), and another new MIB object is defined at the system level for the number of OLT-G message losses (which may also be referred to as the "synchronization loss alarm reporting counter" in the context). If the ONU detects that the number of consecutive ToD information losses reaches the configured OLT-G message loss number, the ONU will report a synchronization loss alarm to indicate that the ToD information is lost and is no longer synchronized with the OLT; 2) OMCI is defined to manage the ONU. The OLT-G ME is extended in the ISAM OMCI specification. Specifically, two attributes are extended (corresponding to the two management objects extended in the MIB). For example, the new attributes "ToD Distribution Time Interval" and "Number of loss of OLT message" are extended in the OLT-G. "ToDDistribution Time Interval" corresponds to the ToD distribution time interval, and "Number of loss of OLTmessage" corresponds to the number of lost OLT-G messages. 3) The ONU ToD processing mechanism is updated and the configured data is used to report alarms. Specifically: the OMCI library is updated to support the new OLT-G messages; based on the configured ToD information distribution interval, a general algorithm is established for determining the reception of OLT-G messages; if the number of consecutively lost ToD messages on the ONU side reaches the configured number of lost OLT-G messages, a synchronization loss alarm is reported. Figure 4This application presents a universal solution for ToD management and alarm reporting. The OLT defines a MIB for the OLT-G distribution time interval and the out-of-sync alarm report counter, and an OMCI for these two counters to manage the ONUs. The OLT uses the configured OLT-G distribution time interval to distribute OLT-G messages to the ONUs, and the ONUs use the configured data to report out-of-sync alarms. The ONUs: 1) receive the OLT-G distribution time interval and out-of-sync alarm report counter sent by the OLT; 2) update the out-of-sync alarm report timer based on the OLT-G distribution time interval and the out-of-sync alarm report counter; and 3) all ONUs follow this rule, without any local, private, hard-coded configuration. This universal solution is applicable to all GPON / XG(S)PON / XGSPON products that support ToD.

[0084] Figure 5 The flowchart of an example of the present application for ToD management and alarm reporting is shown. The specific process is as follows: 1) The administrator configures the correct ToD distribution time interval (A) and the number of OLT-G message losses (B) for the OLT-G message; 2) The OLT performs the following two operations: a) saves the configuration in the database; b) starts the OLT-G distribution timer T1, and the expiration time of T1 is A; 3) When the ONU goes online during the startup phase, the OLT passes the ToD distribution time interval and the number of OLT-G message losses to the ONU; 4) After the ONU receives the ToD distribution time interval and the number of OLT-G message losses, it starts the alarm timer T2, and the expiration time of T2 is A*B; 5) When T1 expires, the OLT sends an OLT-G message to the ONU, and resets T1 to restart the timing; 6) If the ONU Receive the OLT-G message from the OLT before T2 times out, reset T2 to zero and restart timing; 7) OLT cannot successfully transmit the OLT-G message to the ONU due to unexpected reasons such as fiber disconnection and communication loss; 8) T2 times out, and the ONU still has not received the OLT-G message from the OLT, then the ONU reports the synchronization loss alarm to the NMS and ACS (if any); 9) The ONU sends a synchronization loss alarm notification to the OLT to report the synchronization loss alarm to the NMS through the OLT (operation 9 is the operation of reporting the synchronization loss alarm to the NMS in operation 8); 10) The communication between the OLT and the ONU is restored or the optical fiber is reconnected; 11) The ONU resets the alarm timer to zero and restarts timing, and clears the synchronization loss alarm. It should be noted that, Figure 5 The numbers shown for each operation do not indicate the actual order of execution.

[0085] Based on the above-mentioned universal solution for ToD management and alarm reporting, by extending new management objects in the OLT MIB and the OLT-GME in the ISAM OMCI specification, it is possible to configure the ToD distribution interval and the number of OLT-G message losses, thereby realizing a manageable ToD information distribution and synchronization loss alarm reporting mechanism, which is beneficial to the IOP between OLT and ONU. In addition, this solution allows the sensitivity of alarm reporting to be customized according to customer requirements, which has strong flexibility.

[0086] It should be noted that the above Figure 4 and Figure 5 Only the ToD management parameters including the ToD distribution time interval and the number of OLT-G message losses are used to describe the corresponding ToD management and alarm mechanism. The management based on other ToD management parameters can be implemented using similar management concepts and will not be described in detail here.

[0087] According to the solution of the present application, by extending new management objects in the OLT MIB and extending the OLT-G ME in the ISAM OMCI specification, flexible and diverse ToD management can be achieved.

[0088] Figure 6 A schematic diagram of the structure of a first device for ToD management in an OLT according to one embodiment of the present application is shown. The first device 1 includes a first obtaining device 11 and a first sending device 12. The first obtaining device 11 is configured to obtain ToD management parameters configured based on an extended management object in the MIB; the first sending device 12 is configured to generate an OMCI message based on the extended OLT-G management entity and send the OMCI message to the ONU, wherein the OMCI message carries the ToD management parameters.

[0089] The first obtaining device 11 obtains the ToD management parameters configured based on the management objects extended in the MIB. In some embodiments, in order to achieve universality, it is necessary to configure data from the OLT end. The configuration is defined at the system level and is applicable to all ONUs under the OLT node. Thus, all ONUs under an OLT node can use the same configuration to implement the ToD management mechanism. In some embodiments, the first obtaining device 11 receives the configuration from an NMS (Network Management System) or an administrator. In some embodiments, the operation interface for performing configuration operations can support SNMP (Simple Network Management Protocol), CLI (Command Line Interface), NCY, etc.

[0090] In some embodiments, the ToD management parameters include any parameters used for ToD management. In some embodiments, the ToD management parameters include at least any one of the following: ToD distribution time interval; number of OLT-G message losses; maximum timeout threshold for OLT-G loss; ToD support report indication; ToD enabling information. Among them, the ToD distribution time interval is used to configure the time interval for distributing ToD information to the ONU. For example, if the ToD distribution time interval is configured as 60s, the OLT distributes ToD information to the ONU every 60s; the number of OLT-G message losses is used to configure the maximum number of ToD losses that triggers a synchronization loss alarm; the maximum timeout threshold for OLT-G loss is used to configure the maximum timeout threshold that triggers a synchronization loss alarm; the ToD support report indication is used to indicate whether the ONU reports whether it supports the ToD function; the ToD enabling information is used to indicate whether the ToD function is enabled. It should be noted that the above-mentioned ToD management parameters are only examples, and any parameters used for ToD management should be included in the scope of the ToD management parameters described in this application.

[0091] In some embodiments, the ToD management parameters include the ToD distribution time interval and the number of OLT-G message losses. The following only introduces the definition of SNMP MIB by taking the SNMP management method as an example. Other management methods have similar ideas and will not be introduced in detail here. Figure 2 A schematic diagram of a new management object extended in the MIB of an example of the present application is shown. Two new objects are defined in the NTR MIB for managing ToD distribution in OLT-G messages, namely Figure 2As shown in the ToD Distrbution TimeInterval (67) and ToD LossOfOltgMessageNumber (68). ToD Distrbution TimeInterval corresponds to the time interval for distributing the ToD message of the OLT-G message. In order to closely track the OLT, the ToD information needs to be distributed from the OLT to the ONU regularly. Regardless of the interval, the OLT message will always be distributed during the startup phase. It is applicable to a normal operating system. The OLT-G message will be sent regularly according to the ToD distribution time interval. As an example, the value range of this object is (0,3600), the default value is 60, and the unit is seconds. ToD LossOfOltgMessageNumber corresponds to the number of OLT-G message losses, which is equivalent to the number of ToD information losses, or the threshold for synchronization loss alarm reporting. Once the number of OLT-G messages that the ONU side has not received continuously reaches the value assigned to this object, the ONU will be considered to have lost synchronization with the OLT. As an example, the value range of this object is 1 to 16, and the default value is 3.

[0092] It should be noted that for other ToD management parameters, corresponding management objects can be similarly extended in the MIB, such as extending three management objects corresponding to the OLT-G loss maximum timeout threshold, ToD support report indication, and ToD enabling information in the MIB.

[0093] The first sending device 12 is configured to generate an OMCI message based on the extended OLT-G management entity, and send the OMCI message to the ONU, wherein the OMCI message carries the ToD management parameter.

[0094] In some embodiments, the ToD management parameters include a ToD distribution time interval and a number of lost OLT-G messages. When the ONU comes online during the startup phase, the first sending device 12 generates an OMCI message based on the extended OLT-G management entity and sends the OMCI message to the ONU, wherein the OMCI message carries the ToD distribution time interval and the number of lost OLT-G messages.

[0095] To deliver configurations for the newly extended management objects to the ONU, the OMCI needs to be updated to support the new configurations. The definition of time information is nearly identical in ITU-T G.984.4 and G.988.4, so only G.988.4 is described in detail here. The OLT-G message carries Time of Day (ToD) information for distribution to the ONU. Based on the OLT-G message structure defined in Section 9.12.2 of G.988.4, new attributes are introduced for each ToD management parameter. It should be noted that, aside from its name, the OLT-G ME is identical to the OLT B-PON ME documented in ITU-T G.983.2. This optional ME identifies the OLT to which the ONU is connected. It provides a way for the ONU to configure itself for operability with a specific OLT. ONUs supporting this ME automatically create an instance of it. After the startup phase, the OLT should immediately configure the ONU to the desired configuration. The interpretation of the attributes is a matter of negotiation between the two vendors involved. Furthermore, an instance of this ME is associated with the ONU management entity.

[0096] As an example, the ToD management parameters include the ToD distribution time interval and the number of lost OLT-G messages. The extended OLT-G attributes include: Managed entity id, OLT vendor id, Equipment id, Version, ToD Distribution Time Interval, Number of lost OLT messages, Actions, and Notifications. Among them, the managed entity id uniquely identifies each instance of this managed entity. There is only one instance here, numbered 0, (R) (mandatory) (2 bytes); the OLT vendor id identifies the OLT vendor. It is the same as the 4 most significant bytes of the ONT serial number specified in [ITU-T G.984.3]. After instantiation, this attribute contains all spaces, (R, W) (mandatory) (4 bytes); the equipment id can be used to identify the specific type of OLT. The default value of all spaces indicates that the equipment ID information is not available or not applicable to the represented OLT, (R, W) (mandatory) (20 bytes); the version identifies the vendor-defined OLT version. The default left-aligned ASCII string "0" (padded with trailing nulls) indicates that the version information is not available or not applicable to the represented OLT, (R, W) (mandatory) (14 bytes). Among them, ToD Distribution Time Interval and Number of loss of OLT message are two newly extended attributes; ToD Distribution Time Interval identifies the ToD distribution time interval, with a default value of 60 seconds and a maximum value of 3600 seconds, (R, W) (mandatory) (2 bytes); Number of loss of OLT message identifies the number of OLT-G message losses on the ONU side. If the ONU cannot receive the configured number of OLT-G messages from the OLT, the ONU will issue a synchronization loss alarm, with a default value of 3 and a maximum value of 16, (R, W) (mandatory) (2 bytes). For other ToD management parameters, the OLT-G ME can be similarly extended to introduce new attributes, which will not be detailed here.

[0097] In some embodiments, the ToD management parameter includes a ToD distribution interval, and the first device 1 further includes a second sending device (not shown). The second sending device is configured to send an OLT-G message carrying ToD information to the ONU according to the ToD distribution interval. For example, if the administrator configures the ToD distribution interval to 60 seconds, the second sending device in the OLT will distribute an OLT-G message carrying ToD information to the ONU every 60 seconds according to this configuration.

[0098] In some embodiments, the second sending means further includes: starting an OLT-G distribution timer, wherein the expiration time of the OLT-G distribution timer is set to the ToD distribution interval; and whenever the OLT-G distribution timer times out, sending an OLT-G message carrying ToD information to the ONU, and resetting the OLT-G distribution timer to zero and restarting the timer. Thus, the OLT can periodically distribute ToD information to the ONU based on the configured ToD distribution interval, thereby supporting manageable ToD information distribution.

[0099] It should be noted that there is no strict execution order between the first transmitting device 12 and the second transmitting device. For example, after obtaining configuration data, the OLT may trigger the first transmitting device 12 to perform an operation and simultaneously trigger the second transmitting device to begin distributing ToD information to the ONU. For another example, after obtaining configuration data, the OLT may first trigger the first transmitting device 12 to perform an operation and then, based on predetermined logic, trigger the second transmitting device to begin distributing ToD information to the ONU at a certain time.

[0100] In some embodiments, the first device 1 further includes a storage device (not shown) for performing operations after the first sending device 12, and the storage device is used to save the ToD distribution time interval and the number of OLT-G message losses in a database.

[0101] Figure 7 A schematic diagram of the structure of a second device for ToD management in an ONU according to one embodiment of the present application is shown. The second device 2 includes a receiving device 21 and a management device 22. The receiving device 21 is configured to receive an OMCI message generated by an extended OLT-G management entity and sent by the OLT. The OMCI message carries ToD management parameters configured based on extended management objects in the MIB. The management device 22 is configured to perform corresponding ToD management operations based on the ToD management parameters.

[0102] Receiving device 21 receives the OMCI message generated by the extended OLT-G management entity sent by OLT, wherein the OMCI message carries the ToD management parameters configured by the management object extended in MIB. The ToD management parameters and the extended OLT-G management entity have been described in detail in the aforementioned embodiment and will not be repeated here.

[0103] The management device 22 performs corresponding ToD management operations according to the ToD management parameters.

[0104] In some embodiments, the ONU will synchronize with the OLT through OLT-G messages and start an alarm timer to detect a synchronization loss alarm. The management device 22 further includes a determination device (not shown), a retiming device (not shown) and an alarm device (not shown).

[0105] The determining device determines the time interval for triggering the ONU synchronization loss alarm according to the ToD management parameter, and starts an alarm timer, wherein the expiration time of the alarm timer is set to the time interval.

[0106] In some embodiments, the ToD management parameter includes an OLT-G loss maximum timeout threshold, and determining the time interval for triggering the ONU synchronization loss alarm based on the ToD management parameter includes determining the OLT-G loss maximum timeout threshold as the time interval for triggering the ONU synchronization loss alarm. For example, an administrator configures the OLT-G loss maximum timeout threshold to 1200 seconds. The OLT sends this parameter to the ONU, and the ONU starts an alarm timer based on the parameter, with the expiration time of the alarm timer set to 1200 seconds.

[0107] In some embodiments, the ToD management parameters include a ToD distribution time interval and a number of lost OLT-G messages. Determining the time interval for triggering the ONU synchronization loss alarm based on the ToD management parameters includes calculating the time interval for triggering the ONU synchronization loss alarm based on the ToD distribution time interval and the number of lost OLT-G messages. Preferably, the time interval for triggering the ONU synchronization loss alarm is the product of the ToD distribution time interval and the number of lost OLT-G messages. In some embodiments, the starting device 22 extracts the configured ToD distribution time interval and the number of lost OLT-G messages from the received OMCI message, and then calculates the time interval for triggering the ONU synchronization loss alarm based on the ToD distribution time interval and the number of lost OLT-G messages. Then, an alarm timer is started, and the expiration time of the alarm timer is set to the determined time interval. As an example, if the ToD distribution time interval is 60s and the number of lost OLT-G messages is 3, the expiration time of the alarm timer is 60*3=180s. It should be noted that, since the expiration time of the alarm timer is the product of the ToD distribution time interval and the number of OLT-G message losses, if the alarm timer has not received the OLT-G message until it times out, it means that the number of consecutively lost ToD information has reached the configured number of OLT-G message losses, and the alarm reporting procedure can be started at this time. For example, in the above example, if the alarm timer times out, it means that the OLT-G message from the OLT has not been received for 180 seconds, that is, the number of consecutively lost OLT-G messages (or ToD information) has reached 3, and the alarm reporting procedure can be started.

[0108] In some embodiments, the ToD management parameters include not only the ToD distribution time interval and the number of OLT-G message losses, but also the OLT-G loss maximum timeout threshold. The initial time interval can be calculated based on the ToD distribution time interval and the number of OLT-G message losses. Then, based on the initial time interval and the OLT-G loss maximum timeout threshold, the time interval for triggering the ONU synchronization loss alarm is finally determined. For example, the initial time interval is compared with the OLT-G loss maximum timeout threshold. If the initial time interval is greater than or equal to the OLT-G loss maximum timeout threshold, the OLT-G loss maximum timeout threshold is determined as the final time interval; otherwise, the initial time interval is determined as the final time interval.

[0109] If an OLT-G message carrying ToD information is received from the OLT before the alarm timer times out, the retiming device resets the alarm timer and restarts the timer. In some embodiments, before the alarm timer times out, as long as an OLT-G message is received from the OLT, the retiming device resets the alarm timer. In this case, the ONU may not have lost ToD information, or it may have lost ToD information, but the number of consecutive ToD information losses is less than the configured OLT-G message loss number, which means that the alarm reporting condition is not met.

[0110] If the alarm timer times out and the OLT-G message carrying the ToD information sent by the OLT is still not received, the alarm device reports a synchronization loss alarm. If the alarm timer times out and the OLT-G message carrying the ToD information sent by the OLT is still not received, it means that the number of consecutively lost ToD information has reached the configured number of OLT-G message losses, that is, the alarm reporting conditions are met, and a synchronization loss alarm needs to be reported. In some embodiments, the ONU reports the synchronization loss alarm to the OLT, and the OLT reports the synchronization loss alarm to the NMS after receiving it. In some embodiments, the ONU reports the synchronization loss alarm to the ACS (Auto-Configuration Server). In some embodiments, the ONU reports the synchronization loss alarm to the OLT and the ACS at the same time, and the OLT reports the synchronization loss alarm to the NMS after receiving it. In some embodiments, the OLT may not be able to successfully transmit the OLT-G message to the ONU due to unexpected reasons such as optical fiber disconnection and communication loss.

[0111] In some embodiments, the second device 2 further includes an alarm clearing device (not shown), which is configured to, upon receiving an OLT-G message carrying ToD information from the OLT again after reporting the synchronization loss alarm, reset the alarm timer, restart the timer, and clear the synchronization loss alarm. In some embodiments, if the OLT is unable to successfully transmit the OLT-G message to the ONU due to communication loss or fiber disconnection, when communication between the OLT and the ONU is restored or the fiber is reconnected, and the ONU receives the OLT-G message from the OLT again, the alarm clearing device resets the alarm timer, restarts the timer, and clears the synchronization loss alarm.

[0112] In certain embodiments, described ToD management parameter comprises ToD supportability report indication, described management device 22 comprises the ToD supportability information that is used to obtain described ONU correspondence, generates OMCI message according to described ToD supportability information, and the OMCI message generated is sent to the device of described OLT.In certain embodiments, can send described ToD supportability report indication by defining relevant OMCI, as OMCI response message is expanded, add ToD supportability attribute, to carry ToD supportability information.In certain embodiments, can carry ToD supportability information by the reserved field defined in existing OMCI.

[0113] It should be noted that the names of the various modules or devices involved in this application are only examples and not limitations of this application. Multiple modules or devices can also be implemented by one module or device through software or hardware, and each module or device can also be divided into multiple modules or devices and implemented through software or hardware.

[0114] Figure 8 An exemplary system is shown that can be used to implement the various embodiments described herein.

[0115] In some embodiments, the system 1000 can serve as any of the processing devices described in the embodiments of the present application. In some embodiments, the system 1000 may include one or more computer-readable media (e.g., system memory or NVM / storage device 1020) having instructions and one or more processors (e.g., processor(s) 1005) coupled to the one or more computer-readable media and configured to execute the instructions to implement modules and thereby perform the actions described in the present application.

[0116] For one embodiment, the system control module 1010 may include any suitable interface controller to provide any suitable interface to at least one of the processor(s) 1005 and / or any suitable device or component in communication with the system control module 1010 .

[0117] The system control module 1010 may include a memory controller module 1030 to provide an interface to the system memory 1015. The memory controller module 1030 may be a hardware module, a software module, and / or a firmware module.

[0118] System memory 1015 can be used, for example, to load and store data and / or instructions for system 1000. For one embodiment, system memory 1015 can include any suitable volatile memory, such as suitable DRAM. In some embodiments, system memory 1015 can include double data rate type four synchronous dynamic random access memory (DDR4 SDRAM).

[0119] For one embodiment, the system control module 1010 may include one or more input / output (I / O) controllers to provide interfaces to the NVM / storage device 1020 and the communication interface(s) 1025 .

[0120] For example, NVM / storage 1020 may be used to store data and / or instructions. NVM / storage 1020 may include any suitable non-volatile memory (e.g., flash memory) and / or may include any suitable non-volatile storage device(s) (e.g., one or more hard disk drives (HDDs), one or more compact disk (CD) drives, and / or one or more digital versatile disk (DVD) drives).

[0121] NVM / storage device 1020 may include storage resources that are physically part of the device on which system 1000 is installed, or it may be accessible to the device without being part of the device. For example, NVM / storage device 1020 may be accessed over a network via communication interface(s) 1025.

[0122] Communication interface(s) 1025 may provide an interface for system 1000 to communicate over one or more networks and / or with any other suitable devices. System 1000 may wirelessly communicate with one or more components of a wireless network in accordance with any of one or more wireless network standards and / or protocols.

[0123] For one embodiment, at least one of the processor(s) 1005 may be packaged together with the logic of one or more controllers of the system control module 1010 (e.g., the memory controller module 1030). For one embodiment, at least one of the processor(s) 1005 may be packaged together with the logic of one or more controllers of the system control module 1010 to form a system-in-package (SiP). For one embodiment, at least one of the processor(s) 1005 may be integrated on the same die with the logic of one or more controllers of the system control module 1010. For one embodiment, at least one of the processor(s) 1005 may be integrated on the same die with the logic of one or more controllers of the system control module 1010 to form a system-on-chip (SoC).

[0124] In various embodiments, system 1000 may be, but is not limited to, a server, a workstation, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet computer, a netbook, etc.). In various embodiments, system 1000 may have more or fewer components and / or a different architecture. For example, in some embodiments, system 1000 includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touchscreen display), a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit (ASIC), and a speaker.

[0125] The present application further provides an OLT, wherein the OLT includes:

[0126] a memory for storing one or more programs;

[0127] One or more processors connected to the memory,

[0128] When the one or more programs are executed by the one or more processors, the one or more processors are enabled to perform the method for ToD management in the OLT described in the present application.

[0129] The present application also provides an ONU, wherein the ONU includes:

[0130] a memory for storing one or more programs;

[0131] One or more processors connected to the memory,

[0132] When the one or more programs are executed by the one or more processors, the one or more processors are enabled to perform the method for ToD management in the ONU described in the present application.

[0133] The present application also provides a computer-readable storage medium having a computer program stored thereon, and the computer program can be executed by a processor to perform the method for ToD management described in the present application.

[0134] The present application also provides a computer program product. When the computer program product is executed by a device, the device executes the method for ToD management described in the present application.

[0135] It is obvious to those skilled in the art that the present application is not limited to the details of the above-mentioned exemplary embodiments, and that the present application can be implemented in other specific forms without departing from the spirit or basic characteristics of the present application. Therefore, from any point of view, the embodiments should be regarded as exemplary and non-restrictive, and the scope of the present application is defined by the appended claims rather than the above description, and it is intended that all changes that fall within the meaning and scope of the equivalent elements of the claims are included in the present application. Any figure mark in the claims should not be regarded as limiting the claims involved. In addition, it is obvious that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the system claim may also be implemented by one unit or device through software or hardware. Words such as first and second are used to indicate names and do not indicate any particular order.

Claims

1. A method for ToD management in an OLT, wherein: The method includes: Obtain ToD management parameters configured based on the extended management objects in the MIB; Generate an OMCI message based on the extended OLT-G management entity, and send the OMCI message to the ONU, wherein the OMCI message carries the ToD management parameter; The ToD management parameter includes at least one of the following: ToD distribution interval; Number of OLT-G message losses; OLT-G loss maximum timeout threshold; ToD Supporting Reporting Instructions; ToD enabling information.

2. The method according to claim 1, wherein The ToD management parameter includes a ToD distribution time interval, and the method further includes: An OLT-G message carrying ToD information is sent to the ONU according to the ToD distribution time interval.

3. The method according to claim 2, wherein: The sending an OLT-G message carrying ToD information to the ONU according to the ToD distribution time interval includes: Starting an OLT-G distribution timer, where the expiration time of the OLT-G distribution timer is set to the ToD distribution time interval; Whenever the OLT-G distribution timer times out, an OLT-G message carrying ToD information is sent to the ONU, and the OLT-G distribution timer is reset to zero and restarted.

4. The method according to any one of claims 1 to 3, wherein After the step of obtaining the ToD management parameters configured based on the extended management object in the MIB, the method further includes: The ToD management parameters are saved in a database.

5. A method for ToD management in an ONU, wherein: The method includes: Receive the OMCI message generated by the extended OLT-G management entity sent by the OLT, wherein the OMCI message carries the ToD management parameters configured by the management object extended in the MIB; Perform corresponding ToD management operations according to the ToD management parameters; The ToD management parameter includes at least one of the following: ToD distribution interval; Number of OLT-G message losses; OLT-G loss maximum timeout threshold; ToD Supporting Reporting Instructions; ToD enabling information.

6. The method according to claim 5, wherein: The performing of the corresponding ToD management operation according to the ToD management parameter includes: Determining a time interval for triggering an ONU synchronization loss alarm according to the ToD management parameter, and starting an alarm timer, wherein an expiration time of the alarm timer is set to the time interval; If an OLT-G message carrying ToD information is received from the OLT before the alarm timer expires, the alarm timer is reset to zero and restarted; If the alarm timer times out and the OLT-G message carrying the ToD information sent by the OLT is still not received, a synchronization loss alarm is reported.

7. The method according to claim 6, wherein: The ToD management parameter includes an OLT-G loss maximum timeout threshold, and determining the time interval for triggering an ONU synchronization loss alarm according to the ToD management parameter includes: The OLT-G loss maximum timeout threshold is determined as the time interval for triggering the ONU synchronization loss alarm.

8. The method according to claim 6, wherein: The ToD management parameters include a ToD distribution time interval and a number of lost OLT-G messages, and determining a time interval for triggering an ONU synchronization loss alarm according to the ToD management parameters includes: The time interval for triggering the ONU synchronization loss alarm is calculated according to the ToD distribution time interval and the number of lost OLT-G messages.

9. The method according to any one of claims 6 to 8, wherein The method further includes: If an OLT-G message carrying ToD information is received again from the OLT after the synchronization loss alarm is reported, the alarm timer is reset to zero and restarted, and the synchronization loss alarm is cleared.

10. The method according to claim 5, wherein The ToD management parameter includes a ToD support reporting indication, and performing a corresponding ToD management operation according to the ToD management parameter includes: Obtain ToD support information corresponding to the ONU, generate an OMCI message according to the ToD support information, and send the generated OMCI message to the OLT.

11. A first device for ToD management in an OLT, wherein: The first device comprises: Means for obtaining ToD management parameters configured based on extended management objects in the MIB; For generating an OMCI message based on an extended OLT-G management entity, and sending the OMCI message to an apparatus of an ONU, wherein the OMCI message carries the ToD management parameter; The ToD management parameter includes at least one of the following: ToD distribution interval; Number of OLT-G message losses; OLT-G loss maximum timeout threshold; ToD Supporting Reporting Instructions; ToD enabling information.

12. A second device for ToD management in an ONU, wherein: The second device comprises: Device for receiving an OMCI message generated by an extended OLT-G management entity sent by an OLT, wherein the OMCI message carries a ToD management parameter configured based on an extended management object in an MIB; means for performing corresponding ToD management operations according to the ToD management parameters; The ToD management parameter includes at least one of the following: ToD distribution interval; Number of OLT-G message losses; OLT-G loss maximum timeout threshold; ToD Supporting Reporting Instructions; ToD enabling information.

13. An OLT, wherein: The OLT includes: a memory for storing one or more programs; One or more processors connected to the memory, When the one or more programs are executed by the one or more processors, the one or more processors are caused to perform the following operations: Obtain ToD management parameters configured based on the extended management objects in the MIB; Generate an OMCI message based on the extended OLT-G management entity, and send the OMCI message to the ONU, wherein the OMCI message carries the ToD management parameter; The ToD management parameter includes at least one of the following: ToD distribution interval; Number of OLT-G message losses; OLT-G loss maximum timeout threshold; ToD Supporting Reporting Instructions; ToD enabling information.

14. An ONU, wherein: The ONU includes: a memory for storing one or more programs; One or more processors connected to the memory, When the one or more programs are executed by the one or more processors, the one or more processors are caused to perform the following operations: Receive the OMCI message generated by the extended OLT-G management entity sent by the OLT, wherein the OMCI message carries the ToD management parameters configured by the management object extended in the MIB; Perform corresponding ToD management operations according to the ToD management parameters; The ToD management parameter includes at least one of the following: ToD distribution interval; Number of OLT-G message losses; OLT-G loss maximum timeout threshold; ToD Supporting Reporting Instructions; ToD enabling information.

15. A computer-readable storage medium having a computer program stored thereon, wherein the computer program is operable by a processor to perform the following operations: Obtain ToD management parameters configured based on the extended management objects in the MIB; Generate an OMCI message based on the extended OLT-G management entity and send the OMCI message to the ONU, wherein, The OMCI message carries the ToD management parameter; The ToD management parameter includes at least one of the following: ToD distribution interval; Number of OLT-G message losses; OLT-G loss maximum timeout threshold; ToD Supporting Reporting Instructions; ToD enabling information.

16. A computer-readable storage medium having a computer program stored thereon, wherein the computer program is operable by a processor to execute the following operations: Receive an OMCI message generated by an extended OLT-G management entity and sent by the OLT, wherein: The OMCI message carries the ToD management parameters configured by the management object extended based on the MIB; Perform corresponding ToD management operations according to the ToD management parameters; The ToD management parameter includes at least one of the following: ToD distribution interval; Number of OLT-G message losses; OLT-G loss maximum timeout threshold; ToD Supporting Reporting Instructions; ToD enabling information.

Images